Date: Mon, 20 Nov 2017 18:31:12 -0500 From: Thomas Laus <lausts@acm.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: Loader.conf problem Message-ID: <20171120233112.GA18443@mail.laus.org> In-Reply-To: <CANCZdfoUdB5TrE3Vc44VSuLzpULKno6F_G42TL0JiEp1fEyjTQ@mail.gmail.com> References: <a4cf592d-3b1b-5b16-3e65-78ce61b91833@acm.org> <CANCZdfrFCbJ6YyysMZaU_S6ua9QEppe9USBFrah8Vrg-%2BQwe=g@mail.gmail.com> <20171120214220.GA18207@mail.laus.org> <CANCZdfoUdB5TrE3Vc44VSuLzpULKno6F_G42TL0JiEp1fEyjTQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh [imp@bsdimp.com] wrote: > > Can you revert this part of the change? Go back to a known-working version > of those files? Let me know if that fixes the problem? Bonus points for > bisecting which one of the few dozen commits I did that caused this > regression... > > I don't have a GELI + ZFS test bed here. > I have another PC that is operational and is running CURRENT last built about a week ago. I'll copy it's gptzfsboot file to a memory stick and try loading it on the non-functioning PC in the morning. I'll let you know how it comes out. 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?20171120233112.GA18443>