From owner-freebsd-questions@freebsd.org Wed Aug 19 19:06:51 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DBB603C7604 for ; Wed, 19 Aug 2020 19:06:51 +0000 (UTC) (envelope-from doug@safeport.com) Received: from bucksport.safeport.com (bucksport.safeport.com [198.74.231.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BWy225X12z4RKQ; Wed, 19 Aug 2020 19:06:50 +0000 (UTC) (envelope-from doug@safeport.com) Received: from bucksport.safeport.com (bucksport.safeport.com [198.74.231.101]) by bucksport.safeport.com (8.14.5/8.14.5) with ESMTP id 07JJ6ij6028975; Wed, 19 Aug 2020 15:06:44 -0400 (EDT) (envelope-from doug@safeport.com) Date: Wed, 19 Aug 2020 15:06:44 -0400 (EDT) From: Doug Denault To: Allan Jude cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update - Cannot identify running kernel In-Reply-To: <9fcb5ad6-7a73-007d-4fde-ff240ee6275b@freebsd.org> Message-ID: References: <9fcb5ad6-7a73-007d-4fde-ff240ee6275b@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (bucksport.safeport.com [198.74.231.101]); Wed, 19 Aug 2020 15:06:44 -0400 (EDT) X-Rspamd-Queue-Id: 4BWy225X12z4RKQ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of doug@safeport.com designates 198.74.231.101 as permitted sender) smtp.mailfrom=doug@safeport.com X-Spamd-Result: default: False [-0.50 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.50)[-0.500]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:198.74.231.101]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[safeport.com]; NEURAL_SPAM_SHORT(0.10)[0.102]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_ONE(0.00)[1]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11288, ipnet:198.74.228.0/22, country:US]; MAILMAN_DEST(0.00)[freebsd-questions]; ONCE_RECEIVED(0.10)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2020 19:06:51 -0000 On Wed, 19 Aug 2020, Allan Jude wrote: > You likely want to migrate away from having a separate bootpool, as > described here: > > https://ftfl.ca/blog/2016-09-17-zfs-fde-one-pool-conversion.html > > You can't really use boot environments with a separate boot pool. It was > only necessary in the paste when the FreeBSD boot code did not support > reading from encrypted disks. > > -- > Allan Jude Ah thanks for the info. I've already left that configuration behind. freebsd-update tossed in bootpool in the going back and forth I mentioned earlier. I spent some time trying (without any success) to figure out how I broke booting to single user mode. I've reinstalled from a REL 12.1 image. It's time to do some actual work on this system. I found the 12.1 guided install pretty logical. I will try to figure out later if one-size fits all is the right way to go if one does not work for yahoo or netflix. ZFS mastery is not as hard to read as the derivation of the universal constant, but close enough :) _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277