Upgraded glibc causes / to mount read-only.
Allan McRae
allan@archlinux.org
Thu Jul 18 22:29:00 GMT 2013
On 19/07/13 08:06, Carlos O'Donell wrote:
> Allan,
>
> I had a user recently report something similar to this:
> https://bbs.archlinux.org/viewtopic.php?id=139079
>
> Do you know what the root cause of the problem was between
> glibc 2.15 -102 and -103 that would cause problems mounting /
> as read-write?
>
> Was this a real problem with glibc?
>
> Did we fix it upstream?
>
Those package look like the ones someone else provides for OpenVPS
systems that require kernel 2.6.18. Arch sets a minimum kernel version
of 2.6.32. There is no way I made more than 100 releases of glibc-2.15!
Looking back at my glibc-2.15 packages, the main patching I did was to
fix issues caused by broken AVX detection, which would appear unrelated.
The last post in that forum thread appears to have an explanation:
https://bbs.archlinux.org/viewtopic.php?pid=1176560#p1176560. In fact,
this thread corresponds the time where our toolchain was built against
Linux 3.3 headers (update from 3.1). So this is probably the cause.
Allan
More information about the Libc-alpha
mailing list