Every time I boot a Fedora 27 UEFI installed system it messes with the EFI bootmanager entries. For example:
- As root, I change the boot-order such that Fedora's entry isn't first. And/or I delete the Fedora entry.
- At boot, at the systems UEFI boot menu, I boot a generic harddisk boot entry.
- This boots Fedora fine.
- As root, checking with
efibootmgrI see that Fedora somehow managed to add an entry for itself (if it was deleted before) and to put that entry in front of the boot ordering.
This behavior makes sense for standard installations, but not so much if Fedora is installed on a USB stick you want to boot for rescue work, without implicitly changing the EFI bootmanager entries.
Thus, what Fedora piece is responsible for these boot time changes? And how can this be disabled?
edit: Another experiment:
As root, delete all Fedora boot entries with efibootmgr and change the bootorder to just include one generic entry (000C).
Include efibootmgr into the initramfs (using dracut).
Reboot and drop into the dracut shell.
efibootmgr now prints:
BootCurrent: 000C BootOrder: 000A,0000,... ... Boot000A* Fedora HD(2,GPT,...)/File(\EFI\fedora\shimx64.efi) Boot000C* UEFI Misc Device 2 PciRoot(0x0)/Pci(0x5,0x0)... ...
The BootCurrent is as expected, the change in BootOrder (contains everything now) and the new Fedora entry are unexpected.
Thus, something running between the
shutdown -r now and the initramfs emergency shell has changed the EFI bootmanager configuration.
It's possible that the UEFI firmware did this change but I don't see how it would derive the 'Fedora' name and the