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: Sun, 6 Jun 2021 11:43:46 +0300 [thread overview]
Message-ID: <YLyKwtXVanPniqwP@3900XT> (raw)
In-Reply-To: <875yysgp2l.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
On Sat, Jun 05, 2021 at 02:09:59PM -0400, Mark H Weaver wrote:
> 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
>
I know if I were using the zfs kernel module I'd want to use the most
recent lts release. I like the idea of labeling it something like:
* linux-libre (tracks the latest kernel release)
* linux-libre-lts (tracks most recent long-term support release, with
upgrades to newer versions automatically)
* linux-libre-5.10 (current long-term support release, supported until
December 2026)
I know upstream uses 'stable' to mean the current release, but I
personally find the terminology confusing.
--
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 --]
prev parent reply other threads:[~2021-06-06 8:45 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
2021-06-06 8:43 ` Efraim Flashner [this message]
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=YLyKwtXVanPniqwP@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.