Specifying the boot device by its label rather than its UUID can be
pretty useful in various situations (e.g. multiple test VMs).
This might have to be adapted a little to meet the coding standards I'm
not familiar with. Please feel free to improve it in any way you want.
This patch works for me
On Sun, Sep 10, 2023 at 09:30:24 +, darkpenguin wrote:
> Specifying the boot device by its label rather than its UUID can be
> pretty useful in various situations (e.g. multiple test VMs).
>
> This might have to be adapted a little to meet the coding standards I'm
> not familiar with. Please f
Unlike UUID, label may contain spaces. AFAICT your code fails with spaces
Le dim. 10 sept. 2023, 11:31, darkpenguin a écrit :
> Specifying the boot device by its label rather than its UUID can be
> pretty useful in various situations (e.g. multiple test VMs).
>
> This might have to be adapted a
On 11/09/23 01:20, Vladimir 'phcoder' Serbinenko wrote:
> Unlike UUID, label may contain spaces. AFAICT your code fails with spaces
Good catch! I'll fix it.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-deve
>> 3) I could not figure out how to source other variables from
>> /etc/defaults/grub and why not all of them are there. :)
>>
>
> This looks to be in util/grub-mkconfig.in (lines 160-162 in git master
> at the time of writing):
>
> if test -f ${sysconfdir}/default/grub ; then
> . ${sys
