Date: Mon, 20 Nov 2017 13:37:52 -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: <CANCZdfrFCbJ6YyysMZaU_S6ua9QEppe9USBFrah8Vrg-%2BQwe=g@mail.gmail.com> In-Reply-To: <a4cf592d-3b1b-5b16-3e65-78ce61b91833@acm.org> References: <a4cf592d-3b1b-5b16-3e65-78ce61b91833@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus <lausts@acm.org> wrote: > I recently upgraded my FreeBSD-Current system today and did not fully > understand the impact of changes to loader.conf. My system has a Geli > encrypted ZFS pool. In the past whenever I screwed up, I was able to > use 'Beadm' into boot the most recent good kernel or enter a shell to > reread the UPDATING notes for a clearer understanding of what needs to > be done before rebooting. > > Is my system recoverable or does it require wiping and reloading from a > snapshot? If it is recoverable, how to do? > My changes to the system hasn't changed how things work. Or at least shouldn't have changed anything. If they do, that's likely a bug, and likely my fault. The one exception is if you're booting off GELI + ZFS with UEFI based on boot1.efi changes that were in the tree for a few days... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrFCbJ6YyysMZaU_S6ua9QEppe9USBFrah8Vrg-%2BQwe=g>