Date: Tue, 24 Sep 2024 20:02:08 -0400 From: Thomas Laus <lausts@acm.org> To: freebsd-current@freebsd.org Subject: Re: New console output at boot? Message-ID: <1fa875a0-e76c-48c0-bfe4-beb9be91585b@acm.org> In-Reply-To: <CANCZdfpvC0EtV0wdn2zF=z3HnyCn-zewLxSX50Cjxs4ESAsXQg@mail.gmail.com> References: <CAN6yY1unczee8d4jkiok4KObGg%2BJkCShU_1WgpKbMPX2SWkX_g@mail.gmail.com> <CANCZdfqWm6ynaB4h2KwWOrvCxCe-j8iowuZoLdv2j_x3eXygeA@mail.gmail.com> <5ee4b852-f2a3-4c87-bcaa-7341e34f8bfe@acm.org> <CANCZdfrW3kqaFPAH1caDyLWdVXSoZ-rEn=Dv2KexwTJa1o%2B13A@mail.gmail.com> <CANCZdfpvC0EtV0wdn2zF=z3HnyCn-zewLxSX50Cjxs4ESAsXQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/24/24 15:26, Warner Losh wrote: > > Thinking about it, I found a hole. If gptzfsboot picked the wrong BE > this could happen. And updating it might fix a bug that's causing it. > Knowing when your system last updated the gptzfsboot would be useful... > The last time that my gptzfsboot was updated was 9/16/2024. I copied it to the boot partition this morning before I sent this note to the group. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1fa875a0-e76c-48c0-bfe4-beb9be91585b>