Date: Sun, 24 Mar 2019 20:30:13 -0600 From: Rebecca Cran <rebecca@bluestop.org> To: Warner Losh <imp@bsdimp.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" Message-ID: <4cdd585b-2469-fb19-9ac6-5d0af7b9f607@bluestop.org> In-Reply-To: <CANCZdfrNSd_eoa933j-ouCHgURqCHCqtv1MQ2PYT1dvAzF0uTQ@mail.gmail.com> References: <642fed43-0535-9ae3-6f01-a943650cd511@bluestop.org> <20190324090103.GO1923@kib.kiev.ua> <e6695237-6a22-3ff0-b113-9efeee05a51a@bluestop.org> <20190325000241.GS1923@kib.kiev.ua> <6badde15-d8f4-c4ea-2061-0d3c80c6e82a@bluestop.org> <CANCZdfrNSd_eoa933j-ouCHgURqCHCqtv1MQ2PYT1dvAzF0uTQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/24/19 7:34 PM, Warner Losh wrote: > > Right. We need a standard location (that maybe can be overridden, like you > can with /boot, if you really want), and that's likely the first order of > business. I don't think we should be second guessing, though. And we > shouldn't be touching \efi\boot anything unless specifically instructed to > do so. I'm deeply uncomfortable with guessing whether or not to do > something... I'd be wary of *not* touching \efi\boot, since both Microsoft and Linux installs \efi\boot\bootx64.efi. And with desktop systems often not having an UEFI Shell built in and no option to browse for a boot loader from the BIOS, if the FreeBSD boot entry gets lost somehow they're stuck. I discovered recently that rEFInd at least knows to look for \efi\freebsd\loader.efi, but otherwise recovery could be pretty tricky for people who aren't familiar with UEFI. Perhaps adding an option to the efi-update-loader script to search for and list potential ESPs could help, along with good documentation of efibootmgr etc. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4cdd585b-2469-fb19-9ac6-5d0af7b9f607>