On Tue, Sep 6, 2016 at 10:26 AM, Allan Jude <allanj...@freebsd.org> wrote: >> The other problem is that as far as I can tell, there is no code that >> creates the EFI boot entry in any case. By default, the installer just >> moves either boot1.efi or loader.efi (not sure) to: >> (ESP)/EFI/bootx64.efi, >> which is the default location for EFI firmware. I was wondering if the >> kernel has the requisite API/driver for adding EFI boot entries yet. On >> (Arch) Linux, you can add an entry to the NVRAM with a tool called bootctl, >> which is part of the sd-boot package. >> >> Also, wondering if FreeBSD has any plan to add something like >> initramfs/EFIStub booting, which allows for much easier bootloader >> configuration with sd-boot than the current FreeBSD EFI bootloader, which >> must be chainloaded and has its configuration stored off of the ESP. >> > > For historic reasons, users expect to configure the loader via > /boot/loader.conf not by modifying files on the ESP.
Not entirely true. We need to support the EFI boot manager protocol (the EFI boot entries) to properly support next boot, as well as supporting booting off any partition. The boot manager protocol is done with EFI environment variables, so there's nothing to change in the ESP. The rub is to set a EFI variable you have to call runtime services, and to do that you have to setup a mapping table before calling ExitBootServices and that's trickier than it sounds. I've been working on this, but haven't finished. Warner _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"