On Sunday 28 Aug 2016 10:26:15 Mike Gilbert wrote: > On Sun, Aug 28, 2016 at 6:55 AM, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: --->8 > > ... part of the output of "bootctl status": > > > > Boot Loader Binaries: > > ESP: > > /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5 > > > > File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 231) > > File: └─/EFI/BOOT/BOOTX64.EFI > > > > Those binaries have been built on my system: by what process? > > When you run bootctl install, it copies > /usr/lib/systemd/boot/efi/systemd-bootx64.efi to > /boot/EFI/systemd/systemd-bootx64.efi and /boot/EFI/BOOT/BOOTX64.EFI.
Ah, so when one of those is started, all it does (for present purposes) is to load the kernel specified in the appropriate /boot/loader/entries entry. > BOOTX64.EFI is only there as a fallback; if your EFI variables get > reset for some reason, most EFI firmwares will look for a file by that > name as a failsafe. I think I'd more-or-less inferred that, but thanks for the confirmation. -- Rgds Peter
