Date: Sat, 30 Mar 2019 10:25:27 -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: <a3eb3fe0-d115-4ab6-a036-ba80341c5495@bluestop.org> In-Reply-To: <CANCZdfq1vb2-R-R4AZyoqi_940GCooMuhXyjCgSkHSusic5p_w@mail.gmail.com> References: <642fed43-0535-9ae3-6f01-a943650cd511@bluestop.org> <20190324090103.GO1923@kib.kiev.ua> <e6695237-6a22-3ff0-b113-9efeee05a51a@bluestop.org> <CANCZdfq1vb2-R-R4AZyoqi_940GCooMuhXyjCgSkHSusic5p_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/24/19 5:57 PM, Warner Losh wrote: > > He's asking for stopping doing a make install in src/stand. I'm thinking > that's a good thing. We should update the ESP's \efi\freebsd\loader.efi, > but leave the\efi\boot\bootXXXX.efi alone as part of this new installloader > phase. Again, only if the ESP is mounted, and we have a default spot for > it. For this script, I don't think hunting for the ESP is the right way to > go... which means we need to define a standard place for the ESP to be > mounted, which we should do before we turn on any of these features. I booted openSUSE Tumbleweed last night on my ASUS ROG Zenith Extreme board for the first time in a while and updated it to the latest revision. This morning I went to boot into FreeBSD and the "FreeBSD" boot entry had disappeared! Fortunately I have rEFInd installed so I could select the "UEFI OS" entry and get back into FreeBSD, but that's another reason we need to be really careful about relying too heavily on the boot manager variables. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a3eb3fe0-d115-4ab6-a036-ba80341c5495>