On Mon, Jun 26, 2023 at 12:19:46PM +0200, Lennart Poettering wrote:
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)
NB, Fedora doesn't currently have a supported way to making /boot
be compliant with XBOOTLDR requirements, as anaconda blocks use of
vfat on /boot:
https://bugzilla.redhat.com/show_bug.cgi?id=2106706
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.
With regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|