Date: Mon, 25 Mar 2019 03:36:33 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: James Wright <james.wright@jigsawdezign.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" Message-ID: <201903251036.x2PAaXsA079263@gndrsh.dnsmgr.net> In-Reply-To: <6fcddcfe-8d0e-d493-7a1b-2ba093dacabb@jigsawdezign.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > FYI... I run a quad boot (OSX, FreeBSD, Debian, Win10) setup on a > MacbookAir using rEFInd. Nothing annoys me more than the OSX, Linux, and > Win10 updates that decide without warning to replace the boot loader on > the ESP. FreeBSD was the only OS that doesn't do this (I'm fine with > updating /efi/freebsd/loader.efi manually), please could we not mess > about replacing boot loaders on the ESP unless explicitly asked to? I absolutely agree with this possition. As one who at any time may have various disk drives mounted that have nothing to do with my currently running system code that mucks with bootcode that is not explicityly invoked by me is very likely to make a mess of things. I very often have more than one boot type drive attached to a system. > On 25/03/2019 02:30, Rebecca Cran via freebsd-hackers wrote: > > 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. > > > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201903251036.x2PAaXsA079263>