unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Vagrant Cascadian <vagrant@debian.org>,
	Leo Famulari <leo@famulari.name>,
	guix-devel@gnu.org
Subject: Re: Which kernel series to use in the installer and for installed systems?
Date: Thu, 27 May 2021 16:02:46 -0400	[thread overview]
Message-ID: <87mtsgq70e.fsf@netris.org> (raw)
In-Reply-To: <871r9scak2.fsf@ponder>

Hi,

Vagrant Cascadian <vagrant@debian.org> writes:
> Would it be too complicated to include both the latest LTS kernel and
> the most recently packaged kernel in the installer, and default to using
> the same kernel for the installation?

Sounds good to me.  More specifically, I would suggest offering the user
a choice between using the latest stable kernel, or using the latest
kernel from the most recent LTS series at the time of installation.

If the user chooses the latter option, the installer would produce an OS
configuration containing "(kernel linux-libre-X.YY)", where X.YY is
latest LTS series at installation time.

The idea is that if they choose the LTS kernel option today,
'linux-libre-5.10' would be put into their OS config, so they would stay
on the 5.10 kernel series until they explicitly update to a later
series.  This is a good choice for production systems where stability is
more important than running the latest code, and even for ordinary users
who wish to have control over when major kernel updates are done.

I would recommend avoiding the 'linux-libre-lts' variable, because it
fails to provide the primary benefit that LTS kernels are meant to
provide: the ability to postpone potentially disruptive major kernel
upgrades until a time of the user's choosing, when the user is prepared
for possible breakage.  Users who put 'linux-libre-lts' in their OS
configurations should expect that a major kernel upgrade will happen
several years before it is needed, and could happen unexpectedly any
time they upgrade their system.  Unless they carefully inspect the
'guix' command output _every_ time they upgrade their system, users of
the 'linux-libre-lts' variable are unlikely to notice a major kernel
upgrade until it has already been done.

Thoughts?

     Thanks,
       Mark

-- 
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>.


  parent reply	other threads:[~2021-05-27 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 17:17 Which kernel series to use in the installer and for installed systems? Leo Famulari
2021-05-27 18:10 ` Vagrant Cascadian
2021-05-27 18:43   ` Leo Famulari
2021-05-27 19:36     ` Vagrant Cascadian
2021-05-27 20:02   ` Mark H Weaver [this message]
2021-06-02  7:33     ` Efraim Flashner
2021-06-05 18:09       ` Mark H Weaver
2021-06-06  8:43         ` Efraim Flashner

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=87mtsgq70e.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=vagrant@debian.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).