unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>, Dave Love <fx@gnu.org>
Subject: Re: why is linux-libre-headers behind linux-libre?
Date: Mon, 6 Nov 2017 09:51:34 +0100	[thread overview]
Message-ID: <20171106085134.GA24651@thebird.nl> (raw)
In-Reply-To: <87po8vhk3q.fsf@netris.org>

On Mon, Nov 06, 2017 at 03:44:41AM -0500, Mark H Weaver wrote:
> Are you sure about this?  My impression was that binaries compiled with
> newer linux-libre-headers can be run on older kernels.  If you were
> correct, then the binaries we've been building throughout 2017 could be
> reliably run only on linux-libre-4.4 or newer.
> 
> In fact, we've been successfully running these Guix binaries on
> hydra.gnu.org with its old 2.6.x kernel, and on build slaves running
> kernels older than 4.4.  Furthermore, I strongly suspect that many of
> our users (e.g. Trisquel users) have been running Guix on older kernels
> as well, and yet I don't recall seeing any bug reports related to this.
> 
> My recommendation would be to update linux-libre-headers to the latest
> LTS kernel (currently 4.9.x) in every core-updates cycle.
> 
> What do you think?

The Linux kernel API is remarkably stable. It is indeed the reason we
*can* run GNU Guix on older kernels in the first place - the kernel is
our single dependency. The headers do change, but mostly due to kernel
internals which are not used from glibc etc.

I remember for Nix there was a breaking kernel API change at
some point.  But it is extremely rare. Must have been 10 years ago.

Pj.
-- 

  reply	other threads:[~2017-11-06  8:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 12:35 why is linux-libre-headers behind linux-libre? Dave Love
2017-10-31 13:00 ` Vincent Legoll
2017-10-31 19:38   ` Efraim Flashner
2017-11-02 10:16     ` Dave Love
2017-11-05 15:51       ` Ludovic Courtès
2017-11-06  8:44         ` Mark H Weaver
2017-11-06  8:51           ` Pjotr Prins [this message]
2017-11-06 15:18             ` Dave Love
2017-11-06 19:22               ` Mark H Weaver
2017-11-06 21:00                 ` Pjotr Prins
2017-11-07  9:56           ` Ludovic Courtès
2017-11-06 15:16         ` Dave Love

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=20171106085134.GA24651@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=fx@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).