From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 30537@debbugs.gnu.org
Subject: bug#30537: glibc 2.26 refuses to run on CentOS 6.8
Date: Tue, 20 Feb 2018 07:51:36 -0500 [thread overview]
Message-ID: <20180220125136.GA7573@jasmine.lan> (raw)
In-Reply-To: <87woz7rga4.fsf@mdc-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On Tue, Feb 20, 2018 at 01:34:27PM +0100, Ricardo Wurmus wrote:
> The only reason for moving the lower bound to Linux 3.2 is that 2.6 has
> reached EOL. This allows the glibc developers to assume certain
> kernel features and simplify their code.
>
> The RHEL kernels are special, though, in that they are continuously
> patched beyond recognition, backporting features. A RHEL 2.6.32 kernel
> is very different from a stock 2.6.32 kernel.
>
> The patch explicitly permits a *single* extra kernel version (0x020620 =
> 2.6.32) at runtime, not *all* older kernels, so it isn’t as bad as it
> may seem.
Okay, thanks for the clarification.
> For future updates to the glibc we would have to re-evaluate if the
> current RHEL 6.x kernel still supports all features the glibc expects,
> and decide once more if we can justify patching glibc to allow that one
> particular kernel version.
Yes... and this will probably continue for many years. But I do think we
should do something to work around the issue now, and reevaluate our
solution when the pressure is off.
It would be nice if the graft only applied to x86_64-linux, but I've
never considered if that is easy to do or not.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-20 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 18:46 glibc 2.26 refuses to run on CentOS 6.8 Ricardo Wurmus
2018-02-19 18:49 ` Ricardo Wurmus
2018-02-19 19:09 ` Ricardo Wurmus
2018-02-19 19:28 ` Danny Milosavljevic
2018-02-19 21:22 ` Ricardo Wurmus
2018-02-19 22:46 ` Danny Milosavljevic
2018-02-19 19:41 ` Ricardo Wurmus
2018-02-19 20:28 ` bug#30537: " Jan Nieuwenhuizen
2018-02-21 23:12 ` Mark H Weaver
2018-02-21 23:12 ` Mark H Weaver
2018-02-22 20:30 ` Efraim Flashner
2018-02-22 20:30 ` Efraim Flashner
2018-02-23 22:01 ` bug#30537: Grafts vs. early bootstrapping packages Ludovic Courtès
2018-02-19 19:41 ` bug#30537: glibc 2.26 refuses to run on CentOS 6.8 Ricardo Wurmus
2018-02-20 1:22 ` Leo Famulari
2018-02-20 11:52 ` Leo Famulari
2018-02-20 12:34 ` Ricardo Wurmus
2018-02-20 12:51 ` Leo Famulari [this message]
2018-02-20 14:33 ` Ricardo Wurmus
2018-02-20 17:55 ` Ricardo Wurmus
2018-02-20 9:39 ` Efraim Flashner
2018-02-23 22:26 ` Ludovic Courtès
2018-02-23 22:26 ` bug#30537: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180220125136.GA7573@jasmine.lan \
--to=leo@famulari.name \
--cc=30537@debbugs.gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.