unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-devel <guix-devel@gnu.org>, guix-science@gnu.org
Cc: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Doing away with CentOS 6 support (Linux faux-2.6)?
Date: Thu, 07 Dec 2023 23:46:50 +0100	[thread overview]
Message-ID: <87msulbpgl.fsf@inria.fr> (raw)

Hello Guix!

We’ve been carrying a libc patch that allows us to potentially run
binaries on systems running the CentOS 6 kernel—a heavily-patched Linux
2.6 that resembles 3.0 but identifies itself as 2.6.32.

  https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/glibc-allow-kernel-2.6.32.patch

Back in 2018, this was deemed important for HPC clusters, where CentOS 6
was then relatively common, as Ricardo explained:

  https://lists.gnu.org/archive/html/guix-devel/2018-02/msg00392.html

Five years later, it seems reasonable to drop the patch (which is likely
untested these days).  If you disagree, now’s the time to make your
voice heard!

With the upcoming glibc upgrade in the ‘core-updates’ branch¹, glibc
would require Linux >= 3.2.0, as is already the case on ‘master’ if we
omit this faux-2.6.32 exception.

It’s still weeks, or perhaps months, before ‘core-updates’ is merged,
but the sooner we discuss this, the better!

Ludo’.

¹ https://issues.guix.gnu.org/67686


             reply	other threads:[~2023-12-07 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 22:46 Ludovic Courtès [this message]
2023-12-08 16:54 ` Doing away with CentOS 6 support (Linux faux-2.6)? Simon Tournier

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87msulbpgl.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix-science@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).