From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Which kernel series to use in the installer and for installed systems?
Date: Thu, 27 May 2021 11:10:21 -0700 [thread overview]
Message-ID: <871r9scak2.fsf@ponder> (raw)
In-Reply-To: <YK/UMtKGZQxMpbAI@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On 2021-05-27, Leo Famulari wrote:
> I'm not sure exactly how the situation could be improved. Maybe the
> installer and the operating-system declarations that it generates could
> instead use one of the "longterm" [1] kernel series?
>
> I'm not totally comfortable steering users to these longterm kernels
> series, since they are more buggy and less featureful than newer kernel
> series, but at least they do not change very much.
>
> What do you think?
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?
Then, if one kernel didn't work for someone, they could try the install
with the other kernel without having to download a separate image.
Of course, it bloats the installer having a second kernel on it... and
maybe the increased complexity to explain which to choose would be too
much...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-05-27 18:13 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 [this message]
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
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=871r9scak2.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.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).