From owner-freebsd-current@freebsd.org Mon Nov 20 20:37:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 705FDDF4DDC for ; Mon, 20 Nov 2017 20:37:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 387316C1DC for ; Mon, 20 Nov 2017 20:37:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id g73so17054829ioj.8 for ; Mon, 20 Nov 2017 12:37:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EjYafATcWmice6MkFIgRhKasDzXFRTxnDW703lVqX1A=; b=gF4vTJMvQaYnNOLx4Egi1Jo8M1wWZ/fERA2/NGOEPEg7A1n3fv+8VRuyKnJKINoHjZ NKumsqz/ZZyXAB9mpsk5J0BLdXNeLJs91TDfPzObVvJBPcYT2zjCGwro5GkVFHjnX63a 5+UwP4/vpaHu5a67vvbTTjvENG5bftRrSQ8GjLhLfwvDDcQchtfvtltaz1jaGyQvFbSk FUdiDHLqjNXMUOtl9YRSdgDcfhbADhyhXzSF1emEPUkJ2kCTS+sJ/Z/COc477ioj5DUD yKYdSU0dglY8EEa/R23e61irdH0mU2/vyXR0VS6myYdnCHPRenOWPcgfRHssDyMSFhzg IWXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EjYafATcWmice6MkFIgRhKasDzXFRTxnDW703lVqX1A=; b=jbJS5pYchF++eiDmmdblkZBNXhEjFfIMKp0+1RagCIfSL9R1xk81I83KFzCjD6BgLb 9EybxWj/BI/IXjnATCNFYXiN8VtyJ6vucMZRehLddULwJAS7ZZg9Uyv1eiEw4nkjs0ns +2lj6ljFr5LlRcohAYj1830slFJ+5ytI1Rz4JDmOdX5zkhkRkhvYceNW8sEf3kou2vj2 oB9kuhoHBdNFkG78QZvuXAJQGdt/POStk2QnMTtA+yCBFMIVPHOmoHj2JFLRbP1bzTXo WU6RSmBMhrHr4sBNSR3TdjKz6NtqVaLV9jg5r00OeV7v006Ld7H3ECgo5laNEZ1umm0t WZvA== X-Gm-Message-State: AJaThX4PZDKImmHoaKZdJMPCL+m4vWGCFT9162l4gBhY8Nm0sn5CWtzO 4iE9yCoJCzCRe1OZJvBVx6Pf/oj6GmH41TPBe09KOQ== X-Google-Smtp-Source: AGs4zMaAcW8kLtfwZ+Pl7tVnj1HjPKFQN2Vdx79bA/1BpxeUfpRBrfa2jUXAdpMRey8Bfqy3rk3fa1UWKgn9ZMZMF9s= X-Received: by 10.107.30.81 with SMTP id e78mr2280994ioe.130.1511210273276; Mon, 20 Nov 2017 12:37:53 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Mon, 20 Nov 2017 12:37:52 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:c91c:5e34:ef38:d5a] In-Reply-To: References: From: Warner Losh Date: Mon, 20 Nov 2017 13:37:52 -0700 X-Google-Sender-Auth: rXiIsE8NQGNWGi2LfwwX7nYIBPo Message-ID: Subject: Re: Loader.conf problem To: lausts@acm.org Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2017 20:37:54 -0000 On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus 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