Date: Fri, 05 Jan 2018 22:04:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224943] Feature Enhancement: Installer support for EFI without boot1 Message-ID: <bug-224943-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224943 Bug ID: 224943 Summary: Feature Enhancement: Installer support for EFI without boot1 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: nwhitehorn@FreeBSD.org Created attachment 189454 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D189454&action= =3Dedit Patches to partition editor to make ESP This is a top-level bug for installer support for "new-style" UEFI booting = in which loader.efi lives on the ESP. I am aware as of Jan. 5 of the following issues: - Installer needs to make/use a real ESP instead of dd'ing boot1.efifat. Pa= tch attached that makes or reuses one and mounts it at /efi. - Installer needs to extract loader.efi to do. This is easily accomplished = by setting it to install to /efi/efi/blah. Two caveats: - This might break the upgrade path for people using boot1.efi. - Scripted installs are currently broken in this configuration as a resul= t of a bug in bsdtar when tarballs are extracted with directory entries that including FAT mountpoints and creation/modification time setting is on. Interactive installs are unaffected as we have a private libarchive fronten= d in the installer that works around the issue. - Installer needs to run efibootmgr in the "bsdinstall bootconfig" step. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224943-8>