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