| 1 |
On Sun, Aug 28, 2016 at 6:55 AM, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
> On Sunday 28 Aug 2016 10:55:56 Neil Bothwick wrote: |
| 3 |
>> On Sun, 28 Aug 2016 10:43:17 +0100, Peter Humphrey wrote: |
| 4 |
>> > I'd still like to know where the directory /usr/lib64/systemd/boot/efi |
| 5 |
>> > came from though. |
| 6 |
>> |
| 7 |
>> Surely it's from systemd-boot, it is installed by systemd here. What does |
| 8 |
>> qfile tell you? |
| 9 |
>> |
| 10 |
>> $ qfile /usr/lib/systemd/boot/efi |
| 11 |
> |
| 12 |
> Yes, it is. I was puzzling over the wrong thing. Here's part of the output |
| 13 |
> of "bootctl status": |
| 14 |
> |
| 15 |
> Boot Loader Binaries: |
| 16 |
> ESP: /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5 |
| 17 |
> File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 231) |
| 18 |
> File: └─/EFI/BOOT/BOOTX64.EFI |
| 19 |
> |
| 20 |
> Those binaries have been built on my system: by what process? |
| 21 |
|
| 22 |
When you run bootctl install, it copies |
| 23 |
/usr/lib/systemd/boot/efi/systemd-bootx64.efi to |
| 24 |
/boot/EFI/systemd/systemd-bootx64.efi and /boot/EFI/BOOT/BOOTX64.EFI. |
| 25 |
|
| 26 |
BOOTX64.EFI is only there as a fallback; if your EFI variables get |
| 27 |
reset for some reason, most EFI firmwares will look for a file by that |
| 28 |
name as a failsafe. |
Archives