UEFI: How to go about updating the ESP with loader.efi during installworld

[Oliver Pinter]

On 11/4/18, Rebecca Cran <rebecca at bluestop.org> wrote:
> On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote:
>
>> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi
>> is
>> hard one of course. But then again, it is problem only when we can not
>> setup EFI bootmanager variables ? the bootx64.efi is default when bootmgr
>> is not set up.
>
> Yes, I think we should only create efi/boot/boot{x64,ia32,aa64,arm}.efi if
> it
> doesn't already exist in which case we're likely the only OS on the system.

It's a totally working scenario to create OS specific directories on the ESP:

root at opn ~# efibootmgr -v
BootCurrent: 0000
Timeout : 0 seconds
BootOrder : 0000, 0003, 0001
Boot0003* Windows Boot Manager
HD(1,GPT,86fcd8f6-3db7-11e8-ad9f-34e6d749b944,0x28,0x200000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)

ada0p1:/EFI/Microsoft/Boot/bootmgfw.efi
/boot/esp//EFI/Microsoft/Boot/bootmgfw.efi
Boot0000* HardenedBSD 11-STABLE
PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x1,0xffff,0x0)/HD(1,GPT,86fcd8f6-3db7-11e8-ad9f-34e6d749b944,0x28,0x200000)/File(\efi\hardenedbsd\boot1.efi)
                                    ada0p1:/efi/hardenedbsd/boot1.efi
/boot/esp//efi/hardenedbsd/boot1.efi
Boot0001* UEFI: TOSHIBA MQ02ABF050H
PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x1,0xffff,0x0)/HD(1,GPT,86fcd8f6-3db7-11e8-ad9f-34e6d749b944,0x28,0x200000)

VenHw(2d6447ef-3bc9-41a0-ac19-4d51d01b4ce6,20002000200020002000200020002000200020003100200053003800500054003500460054004b000000)

The above is how my esp looks like. In EFI I have two entry: one for
HardenedBSD  and one for Windows. This functionality isn't yet
implemented in the installer, but it's possible to made them by hand.


>
> --
> Rebecca
>
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>