Date: Mon, 22 Aug 2022 10:56:51 +0200 From: "Patrick M. Hausen" <pmh@hausen.com> To: Peter Jeremy <peterj@freebsd.org> Cc: Ryan Moeller <freqlabs@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Beadm can't create snapshot Message-ID: <1E09DD0A-9F26-4BAD-9CA4-B3593B2DE836@hausen.com> In-Reply-To: <YwNCQSL5PmvO2nOs@server.rulingia.com> References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> <C4A81AF9-2C11-4931-B5D9-1B257AB583DF@hausen.com> <YwNCQSL5PmvO2nOs@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Am 22.08.2022 um 10:45 schrieb Peter Jeremy <peterj@freebsd.org>: >=20 > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <pmh@hausen.com> = 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1E09DD0A-9F26-4BAD-9CA4-B3593B2DE836>