Date: Mon, 25 Mar 2019 20:48:15 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: John Baldwin <jhb@FreeBSD.org> Cc: Warner Losh <imp@bsdimp.com>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Konstantin Belousov <kostikbel@gmail.com>, "freebsd-arch@freebsd.org" <arch@FreeBSD.org>, FreeBSD Hackers <freebsd-hackers@FreeBSD.org>, Rebecca Cran <rebecca@bluestop.org> Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" Message-ID: <201903260348.x2Q3mFEg082866@gndrsh.dnsmgr.net> In-Reply-To: <2c1aef87-5408-7736-9039-7fc6a1214102@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 3/25/19 8:05 AM, Warner Losh wrote: > > We started installing /boot/loader with install world in FreeBSD -3.x and > > it has affected the boot ability that whole time... in the early days of > > loader, the kernel loader handoff protocol was immature enough to need a > > matched kernel. But that period lasted only a few months... loader has > > also been weird in other ways as well, since some embedded systems used the > > one in its, while others needed an extra step. As UEFI support has matured > > we're finding there are several issues around it as well where updating the > > ESP needs to be tied to updating /boot for the system to work sometimes. It > > has grown more complex over time, so we should separate. It's been a little > > weird on all the non x86 platforms to different degrees, but now that our > > main platform is affected it's become clear we may need to change. > > > > But we need to do so carefully as this violates POLA in a huge way, as well > > as needing doc changes in a bajillion places. > > I think we should treat files on the ESP the same way we treat other boot > blocks. installworld should continue to install the latest version into > /boot (e.g. /boot/boot that holds UFS boot1 + boot2), but then some other > tool is used by the user to copy the updated loader.efi into the ESP. > > I think the main difference here is that traditionally other boot blocks > didn't change very often, so no one really needed to update it them > post-install. loader.efi changes often enough we probably need to document > updating the ESP as an optional step in the upgrade process. I think > having an automagical script will probably go sideways, but standardizing > where to mounting the ESP (or ESPs when doing RAID mirroring, etc.) means > we can provide a script with defaults (or instructions) that work with > the standardized approach. Is there anyway to stash an easy to extract "version" in loader.* so that a Makefile/.sh script could easily check to see that your boot code is == `uname -KU` and just emit a warning at the end of installworld? > John Baldwin -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201903260348.x2Q3mFEg082866>