GNU GRUB - Bugs: bug #60892, Using blscfg /loader/entries from...
You are not allowed to post comments on this tracker with your current authentication level.
bug #60892: Using blscfg /loader/entries from other bootloaders
Submitter: | Mike Beaton <bmju> | ||
Submitted: | Wed 07 Jul 2021 02:28:34 PM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Feature Request |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Mike Beaton |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-07-09 | bmju | Carbon-Copy | - | Added -email is unavailable- | |
2021-07-09 | bmju | Carbon-Copy | - | Added -email is unavailable- | |
Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-f8d8.
Corresponding source code
I was looking at the use of Boot Loader Specification by blscfg, and as documented e.g. at https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault the adherence to the spec is somewhat loose.
Two key differences:
1. The /loader/entries files are on the boot partition itself, and not on either ESP or XBOOTLDR partitions (the only locations allowed in BLSpec).
2. The /loader/entries files can include named variables (e.g. $kernelopts, $tuned_initrd, etc.) which are obtained from various locations (though, in principle, from anywhere within the grub config scripts).
I was hoping that the presence of these /loader/entries files would allow another bootloader to identify the correct boot args to directly start an EFISTUB kernel.
Point 1 helps with this.
Point 2 however currently makes it not possible to successfully parse the files. ($kernelopts can be found within grub2/grubenv, but the $tuned_### vars are unfortunately inlined within the grub config scripts.)
Is there any possibility at all of an update which overcomes this - perhaps either by standardising on a way of specifying (the file locations of) all such variables, so that they can be found and applied by other bootloaders; or simply by expanding out all such variable references in these files?