unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Efraim Flashner <efraim@flashner.co.il>
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: Sat, 05 Jun 2021 14:09:59 -0400	[thread overview]
Message-ID: <875yysgp2l.fsf@netris.org> (raw)
In-Reply-To: <YLc0Pok4dSsZ581Q@3900XT>

Hi Efraim,

Efraim Flashner <efraim@flashner.co.il> writes:
> I don't really understand why
> and how a newer kernel would make things stop working,

Newer kernels _usually_ work fine, but occasionally things break, and
that's much more likely to happen when switching to a newer kernel
series.  It happened to me quite recently, when a couple of us found
that early 5.12.x kernels would lock up a Thinkpad X200 within minutes
of booting.  See <https://bugs.gnu.org/48604>.

For those who can afford to deal with breakage like this at unscheduled
times, the 'linux-libre' variable is likely the best choice.  For those
who prefer stability, I recommend 'linux-libre-X.YY' for some LTS series
X.YY.

The 'linux-libre-lts' variable seems to me the worst of both worlds, and
likely to lead to some people getting burned from unexpected kernel
upgrades that they might not have been expecting.  If 'linux-libre-lts'
is included as an option, I recommend adding text that makes it clear to
users that automatic upgrades to newer LTS series will happen without
warning, years before such upgrades are needed.

What do you think?

     Regards,
       Mark

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


  reply	other threads:[~2021-06-05 18:11 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
2021-06-05 18:09       ` Mark H Weaver [this message]
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=875yysgp2l.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.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 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).