On Sun, Aug 28, 2016 at 6:55 AM, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > On Sunday 28 Aug 2016 10:55:56 Neil Bothwick wrote: >> On Sun, 28 Aug 2016 10:43:17 +0100, Peter Humphrey wrote: >> > I'd still like to know where the directory /usr/lib64/systemd/boot/efi >> > came from though. >> >> Surely it's from systemd-boot, it is installed by systemd here. What does >> qfile tell you? >> >> $ qfile /usr/lib/systemd/boot/efi > > Yes, it is. I was puzzling over the wrong thing. Here's 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. 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.
