unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Which kernel series to use in the installer and for installed systems?
Date: Thu, 27 May 2021 12:36:03 -0700	[thread overview]
Message-ID: <87lf80klzw.fsf@yucca> (raw)
In-Reply-To: <YK/oRy1yDzqyv1vf@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

On 2021-05-27, Leo Famulari wrote:
> On Thu, May 27, 2021 at 11:10:21AM -0700, Vagrant Cascadian wrote:
>> 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?
>
> I'm a bit confused about what you are suggesting? Do you mean, offering
> both of those versions in a menu to the user?

Yes, at the installer's grub (or other bootloader) menu.


>> 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...
>
> The installer does not "include" built packages, aside from what is used
> by the installer's OS.

Yes, but if you're using the installer, it will choose to install *some*
kernel on the installed system, so it could pick the most similar kernel
(e.g. linux-libre vs. linux-libre-lts) on the initial install...

There may be cases where a newer kernel wouldn't run on a particular
piece of hardware, or where the older LTS kernel wouldn't run, so making
it easy to pick between those two seems worth considering if there are
not too many other drawbacks.


So, my answer to the question "which kernel ...?" is ... maybe both!


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2021-05-27 19:37 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 [this message]
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=87lf80klzw.fsf@yucca \
    --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).