Date: Mon, 20 Nov 2017 16:46:55 -0700 From: Warner Losh <imp@bsdimp.com> To: lausts@acm.org Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Loader.conf problem Message-ID: <CANCZdfqyk6SJkNnK1uuPRYLrKM2iknArijf5McUNwXqhTphEPw@mail.gmail.com> In-Reply-To: <20171120233112.GA18443@mail.laus.org> 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> <20171120233112.GA18443@mail.laus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 20, 2017 at 4:31 PM, Thomas Laus <lausts@acm.org> wrote: > 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. Please do. I fear I screwed something up in the massive rototilling I did, despite efforts to the contrary, and any help you can give me tracking it down would be greatly appreciated. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqyk6SJkNnK1uuPRYLrKM2iknArijf5McUNwXqhTphEPw>