Hi Phil,
Quoting Philip Rhoades via Grub-devel (2023-04-22 07:37:45)
> People,
>
> My Fedora WS has 4 drive bays and I access old boot and other HDs in
> bays 2-4. I just did a clean install of Fedora Sway to /dev/sda -
> everything is fine and the system boots OK but I am confused:
>
> - cat /etc/os-release
>
> NAME="Fedora Linux"
> VERSION="38 (Sway)"
> .
> PRETTY_NAME="Fedora Linux 38 (Sway)"
> ANSI_COLOR="0;38;2;60;110;180"
> .
> VARIANT="Sway"
> VARIANT_ID=sway
>
> - The install picked up old Fedora boot setups which show up in
> /boot/grub2/grub.conf like this:
>
> menuentry 'Fedora Linux 37 (KDE Plasma) (on /dev/sde3)' --class
> gnu-linux --class gnu --class os $menuentry_id_option
> 'osprober-gnulinux-/boot/vmlinuz-6.0.7-301.fc37.x86_64--f6f43412-e6ed-4dff-808b-fe013691c3b6'
> {
>
> - but why is there is not a line like this in /boot/grub2/grub.conf for
> Fedora 38 Sway?
>
> I can see that the appropriate other Sway files are in the /boot tree so
> I am guessing that grub2 somehow knows the proper, default boot image -
> even though the default does not have a menuentry in grub.cfg?
>
> A pointer to a link for info would be great . .
Recent Fedora installs use drop-in files unter /boot/loader/entries
instread of adding menu entries to grub.cfg directly.
For example on my Fedora I see this:
# ls /boot/loader/entries
74d1214a68a2411c9641304cc418fd37-0-rescue.conf
74d1214a68a2411c9641304cc418fd37-6.2.10-300.fc38.x86_64.conf
74d1214a68a2411c9641304cc418fd37-6.2.13-300.fc38.x86_64.conf
74d1214a68a2411c9641304cc418fd37-6.2.8-300.fc38.x86_64.conf
- Oliver
>
>
> Thanks!
>
> Phil.
> --
> Philip Rhoades
>
> PO Box 896
> Cowra NSW 2794
> Australia
> E-mail: p...@pricom.com.au
>
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
