Date: Thu, 21 Dec 2023 08:35:54 -0700 From: Warner Losh <imp@bsdimp.com> To: Jeffrey Bouquet <jbtakk@iherebuywisely.com> Cc: Nuno Teixeira <eduardo@freebsd.org>, Dimitry Andric <dim@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: symlink to /boot/loader.efi Message-ID: <CANCZdfppFzvXe_2TD2x0GKEU0nev8=0o_EjTvUrE9bVjGDfJSQ@mail.gmail.com> In-Reply-To: <E1rGKny-0003yc-3Q@rmmprod05.runbox> References: <CAFDf7UKxDM1_9DqqHcXZWUc0KYJPfwX0KDn1qzNGQ8GCqU=WqQ@mail.gmail.com> <E1rGKny-0003yc-3Q@rmmprod05.runbox>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Thu, Dec 21, 2023, 8:18 AM Jeffrey Bouquet <jbtakk@iherebuywisely.com> wrote: > I am wondering if all the information in this thread present and future > should be included in > the scenarios at the bottom of /usr/ports/UPDATING with technical > explanations about > how and why? AFAIK the file was created before UEFI and thus in that > regard obsolete. There is more info on updating noe on the man pages, but we likely aren't there yet. A note in UPDATING sounds like a great idea. Warner On Thu, 21 Dec 2023 12:59:54 +0000, Nuno Teixeira <eduardo@freebsd.org> > wrote: > > > Hello Dimitry, > > > > For a moment I forgot that efiboot is a fat system... > > I am inspired on what installworld does to kernel and kernel.old. > > I was thinking in something like it but with efi boot, something > automatic. > > > > Thanks! > > > > Dimitry Andric <dim@freebsd.org> escreveu no dia quinta, 21/12/2023 à(s) > > 12:48: > > > > > On 21 Dec 2023, at 13:22, Nuno Teixeira <eduardo@freebsd.org> wrote: > > > > > > > > On every current upgrade I update efi/freebsd/loader.efi (amd64) and > > > efi/boot/boota64 (aarch64) with new copies on /boot/loader.efi. > > > > For safety reasons I always have a copy of last running loader by > > > appending "-old.efi" to loader or boota64 and use beinstall to get BEs > if > > > needed. > > > > > > > > Is that possible to link, e.g., /boot/efi/efi/freebsd/loader.efi -> > > > /boot/loader.efi ? > > > > > > Symlinks do not work on FAT file systems, so I assume you mean a > symlink > > > placed in /boot (assuming that is UFS or ZFS), which points to > > > /boot/efi/efi/freebsd? > > > > > > At the moment I think installworld would not write 'through' such a > > > symlink. In fact, it makes a hard link from /boot/loader_lua.efi to > > > /boot/loader.efi, unlinking any previous /boot/loader.efi. > > > > > > That said, it would be nice to have some sort of semi-official way of > > > upgrading the real EFI loader through installworld. It would probably > > > require some top-level Makefile magic. > > > > > > -Dimitry > > > > > > > > > > -- > > Nuno Teixeira > > FreeBSD Committer (ports) > > > > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 21, 2023, 8:18 AM Jeffrey Bouquet <<a href="mailto:jbtakk@iherebuywisely.com">jbtakk@iherebuywisely.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am wondering if all the information in this thread present and future should be included in<br> the scenarios at the bottom of /usr/ports/UPDATING with technical explanations about<br> how and why? AFAIK the file was created before UEFI and thus in that regard obsolete.</blockquote></div></div><div dir="auto"><br></div><div dir="auto">There is more info on updating noe on the man pages, but we likely aren't there yet. A note in UPDATING sounds like a great idea.</div><div dir="auto"><br></div><div dir="auto">Warner </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On Thu, 21 Dec 2023 12:59:54 +0000, Nuno Teixeira <<a href="mailto:eduardo@freebsd.org" target="_blank" rel="noreferrer">eduardo@freebsd.org</a>> wrote:<br> <br> > Hello Dimitry,<br> > <br> > For a moment I forgot that efiboot is a fat system...<br> > I am inspired on what installworld does to kernel and kernel.old.<br> > I was thinking in something like it but with efi boot, something automatic.<br> > <br> > Thanks!<br> > <br> > Dimitry Andric <<a href="mailto:dim@freebsd.org" target="_blank" rel="noreferrer">dim@freebsd.org</a>> escreveu no dia quinta, 21/12/2023 à(s)<br> > 12:48:<br> > <br> > > On 21 Dec 2023, at 13:22, Nuno Teixeira <<a href="mailto:eduardo@freebsd.org" target="_blank" rel="noreferrer">eduardo@freebsd.org</a>> wrote:<br> > > ><br> > > > On every current upgrade I update efi/freebsd/loader.efi (amd64) and<br> > > efi/boot/boota64 (aarch64) with new copies on /boot/loader.efi.<br> > > > For safety reasons I always have a copy of last running loader by<br> > > appending "-old.efi" to loader or boota64 and use beinstall to get BEs if<br> > > needed.<br> > > ><br> > > > Is that possible to link, e.g., /boot/efi/efi/freebsd/loader.efi -><br> > > /boot/loader.efi ?<br> > ><br> > > Symlinks do not work on FAT file systems, so I assume you mean a symlink<br> > > placed in /boot (assuming that is UFS or ZFS), which points to<br> > > /boot/efi/efi/freebsd?<br> > ><br> > > At the moment I think installworld would not write 'through' such a<br> > > symlink. In fact, it makes a hard link from /boot/loader_lua.efi to<br> > > /boot/loader.efi, unlinking any previous /boot/loader.efi.<br> > ><br> > > That said, it would be nice to have some sort of semi-official way of<br> > > upgrading the real EFI loader through installworld. It would probably<br> > > require some top-level Makefile magic.<br> > ><br> > > -Dimitry<br> > ><br> > ><br> > <br> > -- <br> > Nuno Teixeira<br> > FreeBSD Committer (ports)<br> <br> <br> <br> </blockquote></div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfppFzvXe_2TD2x0GKEU0nev8=0o_EjTvUrE9bVjGDfJSQ>