[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RESEND RESEND RESEND PATCH] templates: introduce GRUB_TOP_LEVEL_* v
|
From: |
Oskari Pirhonen |
|
Subject: |
Re: [RESEND RESEND RESEND PATCH] templates: introduce GRUB_TOP_LEVEL_* vars |
|
Date: |
Thu, 29 Sep 2022 01:08:03 -0500 |
On Tue, Sep 27, 2022 at 05:30:45 -0700, Denton Liu wrote:
> A user may wish to use an image that is not sorted as the "latest"
> version as the top-level entry. For example, in Arch Linux, if a user
> has the LTS and regular kernels installed, `/boot/vmlinuz-linux-lts`
> gets sorted as the "latest" compared to `/boot/vmlinuz-linux`. However,
> a user may wish to use the regular kernel as the default with the LTS
> only existing as a backup.
>
> Introduce the GRUB_TOP_LEVEL_LINUX and GRUB_TOP_LEVEL_XEN variables to
> allow users to specify the top-level entry.
>
A couple questions:
- If all you're looking for is /boot/vmlinuz-linux to be booted, is
setting GRUB_DEFAULT in /etc/default/grub "good enough" for your use
case?
- Is it possible to make this solution more universal? Maybe BSD users
would like to set their top level entry.
- What about for os-prober? My understanding is that it creates its own
top level entries as well.
Note with the 1st question: I'm not saying GRUB_TOP_LEVEL_* is a bad
idea. I'm just curious.
- Oskari
signature.asc
Description: PGP signature