On Do, 22.06.23 12:24, Jeremy Linton (jeremy.linton(a)arm.com) wrote:
But, IMHO the largest change is moving the boot kernel/initrd to the
ESP,
rather than the use of systemd-boot itself. Given the filesystem layout
remains the same outside of those two items and the BLS entries, all the
common tools (dracut/etc) seem to be able to deal with it, and random other
packages not manipulating kernel/initrd images are behavior should not be
affected anymore than putting reFind/whatever in the boot path.
While putting kernle/initrd (UKIs) into the ESP is a good thing
systemd-boot actually is fine with loading them from a separate boot
partition to, i.e. the XBOOTLDR partition, which in many ways is
similar to traditional /boot/, but must be marked via recognized
XBOOTLDR partition type uuid. (also it must be a firmware recognizable
fs, i.e. vfat)
Such an XBOOTLDR partition is supposed to be the escape hatch if the
ESP is pre-existing and too small to contain multiple full sized
UKIs. But you could also make it an escape hatch for simplifying
transitions from the status quo ante.
Lennart
--
Lennart Poettering, Berlin