unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Raghav Gururajan <rg@raghavgururajan.name>, guix-devel@gnu.org
Subject: Re: Linux-Libre-LTS
Date: Thu, 24 Dec 2020 05:15:45 -0500	[thread overview]
Message-ID: <877dp7ik5v.fsf@netris.org> (raw)
In-Reply-To: <cc0da93a-f58d-339a-f771-87d363725a80@raghavgururajan.name>

Hi Raghav,

Raghav Gururajan <rg@raghavgururajan.name> writes:

> I think it is good to have a package-variable "linux-libre-lts", as 
> mentioned in the table at https://jxself.org/linux-libre/
>
> This way, users don't have to remember and change the version numbers in 
> their operating-system-configuration or package-manifest, whenever there 
> is new LTS release.
>
> Thoughts?

I have one concern.

It seems to me that the main reason to specify an LTS kernel is to avoid
the unscheduled breakage that can occur when updating to a new kernel
release series (i.e. to a new major+minor version).  Using
"linux-libre-lts" would fail to avoid these unscheduled updates; it
would merely reduce their frequency.

The only way to reliably avoid unscheduled major+minor kernel updates is
to specify "linux-libre-5.10" or similar.  The cost of this approach is
trivial: editing a few characters in the OS configuration when one
wishes to update to a newer LTS series.  The benefit is that the user
gains control over when these updates will happen, and thus when any
associated breakage will occur.

To my mind, the benefit of this approach is so compelling, and its cost
so trivial, that I can hardly understand why anyone who wishes to use an
LTS kernel would choose otherwise.

If we add "linux-libre-lts" to Guix, I worry that some users would use
it without understanding what they are sacrificing, and later get burned
by breakage when we modify its binding next year, or in some future
year.

A user who does not understand Guix in depth might reasonably expect
that when choosing "linux-libre-lts", upgrades to a later LTS series
would be postponed until the user gives explicit consent.  In theory,
Guix could be modified to behave this way, although I doubt it would be
worth the added complexity.  In any case, since it *could* be done, a
user might reasonably expect it.

If the goal is to solve the problem of users forgetting to update to
newer LTS kernels, I suggest exploring other approaches.  Perhaps we
could implement some system where Guix provides periodic reminders to
consider upgrading, when an older LTS kernel is specified in the OS
configuration and a newer LTS is available.  There'd need to be a way to
silence the warnings though.

What do you think?

      Regards,
        Mark


  parent reply	other threads:[~2020-12-24 10:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  3:32 Linux-Libre-LTS Raghav Gururajan
2020-10-29  7:47 ` Linux-Libre-LTS Efraim Flashner
2020-11-03  3:41   ` Linux-Libre-LTS Raghav Gururajan
2020-12-24  3:54   ` Linux-Libre-LTS Raghav Gururajan
2020-12-26 18:09     ` Linux-Libre-LTS Efraim Flashner
2020-10-29  8:24 ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-10-29 14:16   ` Linux-Libre-LTS Leo Famulari
2020-11-03  3:44   ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 10:56     ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-11-03 19:54       ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 20:06         ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-12-24 10:15 ` Mark H Weaver [this message]
2020-12-24 10:37   ` Linux-Libre-LTS Jonathan Brielmaier
2020-12-25  2:24     ` Linux-Libre-LTS Mark H Weaver
2020-12-27  5:24       ` Linux-Libre-LTS Leo Famulari
2020-12-27 13:27       ` Linux-Libre-LTS Bengt Richter
2020-12-27 17:09   ` Linux-Libre-LTS Raghav Gururajan
2020-12-29 20:52     ` Linux-Libre-LTS Leo Famulari
2020-12-30 16:08       ` Linux-Libre-LTS Raghav Gururajan
2020-12-30 21:18         ` Linux-Libre-LTS Raghav Gururajan
2020-12-31  0:24           ` Linux-Libre-LTS Leo Famulari
2020-12-31  3:19           ` Linux-Libre-LTS Leo Famulari
2020-12-30 15:47 ` Linux-Libre-LTS Jonathan Brielmaier

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=877dp7ik5v.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=rg@raghavgururajan.name \
    /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).