If the installer is creating a new ESP, then this directory will not
exist and the subsequent cp will fail silently. This is usually of no
consequence if /EFI/freebsd/loader.efi is set up correctly.
Details
Details
- Reviewers
imp bcran - Commits
- rG676b7d077c2c: bsdinstall: create /efi/boot directory in ESP
bsdinstall to a blank disk, verify that /EFI/BOOT/BOOT${arch}.EFI is present on the ESP.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 36226 Build 33115: arc lint + arc unit
Event Timeline
Comment Actions
The dirname got me thinking and that lead to these larger suggestions, as well as moving it earlier.
usr.sbin/bsdinstall/scripts/bootconfig | ||
---|---|---|
134 | BOOTDIR="/efi/boot" | |
151 | mkdir -p "${mntpt}/${FREEBSD_BOOTDIR}" "${mntpt}/${BOOTDIR}" | |
152 | "${mntpt}/${FREEBSD_BOOTDIR}/loader.efi | |
166 | This is too late. I'd suggest above. |
usr.sbin/bsdinstall/scripts/bootconfig | ||
---|---|---|
166 | Yep, that is much better. Will update shortly. |
Comment Actions
One further simplification, use $FREEBSD_BOOTNAME instead of $FREEBSD_BOOTDIR/loader.efi.