From nobody Mon Aug 22 08:56:51 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MB5p52Zltz4Z37x for ; Mon, 22 Aug 2022 08:57:01 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MB5p44MS3z3bxl; Mon, 22 Aug 2022 08:57:00 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from smtpclient.apple (217.29.33.131) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 2C3197; Mon, 22 Aug 2022 10:56:52 +0200 Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Beadm can't create snapshot From: "Patrick M. Hausen" In-Reply-To: Date: Mon, 22 Aug 2022 10:56:51 +0200 Cc: Ryan Moeller , freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1E09DD0A-9F26-4BAD-9CA4-B3593B2DE836@hausen.com> References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> To: Peter Jeremy X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4MB5p44MS3z3bxl X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pmh@hausen.com has no SPF policy when checking 217.29.33.228) smtp.mailfrom=pmh@hausen.com X-Spamd-Result: default: False [-1.60 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[hausen.com]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi, > Am 22.08.2022 um 10:45 schrieb Peter Jeremy : >=20 > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" = wrote: >> Isn't beadm retired in favour of bectl? >=20 > bectl still has a number of bugs: > 1) The output from "bectl list" is in filesystem/bename order rather > than creation date order. This is an issue if you use (eg) git > commit hashes as the name. > 2) "bectl activate" doesn't update /boot/loader.conf so the wrong > root filesystem is mounted. You mean the vfs.root.mountfrom option? I thought that, too, was = deprecated and replaced by the bootfs property of the zpool. I don't have vfs.root.mountfrom anywhere and bectl sets the active BE = just as expected. The bootfs property changes accordingly. Kind regards, Patrick=