From: Efraim Flashner <efraim@flashner.co.il>
To: Mark H Weaver <mhw@netris.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: Which kernel series to use in the installer and for installed systems?
Date: Wed, 2 Jun 2021 10:33:18 +0300 [thread overview]
Message-ID: <YLc0Pok4dSsZ581Q@3900XT> (raw)
In-Reply-To: <87mtsgq70e.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 2522 bytes --]
On Thu, May 27, 2021 at 04:02:46PM -0400, Mark H Weaver wrote:
> 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
>
IIRC the Debian installer offers linux, linux-major.minor and
linux-major.minor.point in the installer. I don't really understand why
and how a newer kernel would make things stop working, but I could see
offering linux-libre, linux-libre-lts and linux-libre-5.10 (using the
1.3.0 release as the example).
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-02 7:34 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
2021-06-02 7:33 ` Efraim Flashner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YLc0Pok4dSsZ581Q@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
--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 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.