From: Mark H Weaver <mhw@netris.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>, guix-devel@gnu.org
Subject: Re: Linux-Libre-LTS
Date: Thu, 24 Dec 2020 21:24:17 -0500 [thread overview]
Message-ID: <877dp6ipw3.fsf@netris.org> (raw)
In-Reply-To: <86bbed0c-3b57-f276-81a5-c0f1c1b6858e@web.de>
Hi Jonathan,
Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:
> On 24.12.20 11:15, Mark H Weaver wrote:
>>> 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.
>
> It sums up, the more systems you maintain the more sums up this trivial
> work. Defining "linux-libre-lts" is the same we do for Icecat or
> Icedove. Yes, there can be breakage when they got update from one ESR
> branch to the newer one.
Well, one key difference is that IceCat only supports one ESR branch at
a time, which essentially leaves the user with no choice about when to
upgrade to a new ESR branch (assuming they want security updates). Even
upstream Mozilla only supports one ESR branch most of the time, except
for 3 months per ESR cycle when they briefly support two ESR branches.
The situation with LTS kernels is radically different, because each LTS
series is supported for about 5 years beyond when they are superceded by
a newer LTS, and therefore users have a 5-year window from which to
choose their preferred time to update. Users of "linux-libre-5.10"
could update to the following LTS near the end of 2021, or they could
wait at late as 2026 if they prefer.
> So there are reasons to use always the newest LTS/ESR software version...
The thing is, if they can tolerate unscheduled breakage, then why are
they using an LTS kernel? That's the part I don't quite understand.
> So I support this addition.
Okay. If there are users who want the stability of LTS kernels, but
prefer to lose control over when the upgrades happen in order to save
themselves a few edits per year, then we can add the variable. I don't
have a strong argument against the _existence_ of this variable.
However, I think we should add a comment near its definition, warning
that by using "linux-libre-lts" in their configuration, they will
effectively lose control over when the update to a new LTS series will
happen. If, in the future, this variable is advertised in the manual,
that should include a warning as well.
Moreover, I would prefer for any relevant comments/documentation to
state that the recommended practice when using LTS kernels is to use a
variable like "linux-libre-5.10", and to explain the reasons why.
This is based on my expectation that Guix users who can tolerate
unscheduled breakage from kernel updates will probably just use our
default "linux-libre" kernel, and that users who would choose
"linux-libre-lts" are probably doing so because they wish to avoid being
caught off guard by unscheduled breakage. Does that make sense?
What do you think?
Thanks,
Mark
next prev parent reply other threads:[~2020-12-25 2:26 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 ` Linux-Libre-LTS Mark H Weaver
2020-12-24 10:37 ` Linux-Libre-LTS Jonathan Brielmaier
2020-12-25 2:24 ` Mark H Weaver [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dp6ipw3.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=jonathan.brielmaier@web.de \
/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.