Re: [PATCH] Add support for specifying the boot device by label

[Vladimir 'phcoder' Serbinenko]

Le lun. 11 sept. 2023, 13:16, darkpenguin <darkpenguin@posteo.de> a écrit :

Hmmm, this is actually a good idea. Grub does determine the boot device
by analyzing fstab, doesn't it?

No it doesn't 

Why does it then use either UUIDs or
device paths, based on a configuration in a separate file, instead of
simply reusing exactly what it has found specified in fstab? That would
have been understandable in the past, when maybe Grub did not support
UUIDs or labels, so the algorithm would have been "find the specified
device, then find its path and use that". But now we can simply reuse
exactly what's specified in fstab, can't we? (Though I'm afraid figuring
out that process is beyond my skill or capacity at the moment.)


On 11/09/23 14:44, Olaf Hering wrote:
> Sun, 10 Sep 2023 09:30:24 +0000 darkpenguin <darkpenguin@posteo.de>:
>
>> Specifying the boot device by its label rather than its UUID can be
>> pretty useful in various situations (e.g. multiple test VMs).
>
> Yes, this is very true.
>
> It is up to the local admin to decide how the various block devices
> are supposed to be mounted. The details how it must be done is
> configured by the local admin via the well establish file /etc/fstab,
> and of course other block device related configuration files.
>
> As you have noted, any such decision is outright ignored by grub2.
>
> So instead of adding more to the existing arrogance, please remove
> the offending code and implement something that respects the local
> configuration files.
>
> Thank you.
>
>
> Olaf
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel