3 ms·
> the kernel which nearly-almost-if-you-squint manages long term compatibility with glibc As far as I know, with a single exception, all glibc releases continu
by amluto 8y ago
> the kernel which nearly-almost-if-you-squint manages long term compatibility with glibc
As far as I know, with a single exception, all glibc releases continue to work on modern kernels. The single exception is that one OpenSUSE release shipped with an egregiously broken glibc that will fail an assertion and give up on modern kernels. Modern kernels have a config option to work around this particular issue, too.
- _wmd 8y agoUpstream still defaults to compatibility, but some distros appear to be doing this now: https://github.com/moby/moby/issues/34301 https://github.com/moby/moby/issues/34301 You could say Linux maintained binary compatibility which it does, but for the same reason you could say it ships with big known ASLR bugs, or you could perhaps even say they broke compatibility but shipped the blame for it downstream. Either way the choice is coping with old security bugs or a broken interface
- amluto 8y agoRight. That’s intentional on the host distro’s part. Making it possible for the vsyscall mode to be different for different processes is on my list, and it was half-way done, but then Meltdown happened.