Hi,
adrian15 wrote:
> replace:
> search --set=root --file /live/vmlinuz
> with:
> search --set=root --label \"${LB_ISO_VOLUME}\"
This looks ok for me, as far as GRUB2's work is concerned.
But when the GNU/Linux comes up, it may again be necessary for software
in the initrd to locate the ISO filesystem.
Unarchiving dim memories from last year:
https://lists.debian.org/debian-live/2018/04/msg00005.html
If the initrd indeed looks for marker files, then one should coordinate
both find-the-ISO efforts.
If it has other methods, then one should consider whether they are good
and whether it is possible to join them in GRUB2 .cfg.
-------------------------------------------------------------------------
If you stay with the idea of an earmark file, then the GRUB2 efi.img
and the initrd need to know the name for their version of a live ISO
(or installation ISO).
Any two debian-live ISOs which shall be distinguishable would have to bear
different earmark files.
This imposes some work on tools which want to remaster Debian ISOs and
derive own distingushable versions. The benefit is that those remastered
ISOs can coexist with the originals not only in the firmware's list of
boot devices but also later in the initrd's list of possible storage
devices for mounting the ISO.
Tools which just want to add some packages may maintain the original
earmark and bet on not meeting the original ISO at boot time on the same
machine.
How stupid is the idea to let GRUB2 tell initrd the earmark name in
a kernel parameter ? I.e. in
linux /live/vmlinuz-4.9.0-6-amd64 boot=live earmark="${earmark}" components
"${loopback}"
where "${earmark}" would be set in the GRUB configuration of efi.img ?
Needs possibly coordination with "${loopback}" which already cares for
ISO image files.
If debian-live switches to GRUB2 for BIOS, then "${earmark}" would
have to be known to the .cfg empire in the ISO. But for now it would
suffice to let efi.img tell it to all others.
Have a nice day :)
Thomas
