Date: Mon, 22 Aug 2022 08:11:43 -0700 From: Kyle Evans <kevans@freebsd.org> To: Ronald Klop <ronald-lists@klop.ws> Cc: Peter Jeremy <peterj@freebsd.org>, freebsd-current@freebsd.org, Ryan Moeller <freqlabs@freebsd.org>, "Patrick M. Hausen" <pmh@hausen.com> Subject: Re: Beadm can't create snapshot Message-ID: <CACNAnaEcr=9Ua8z%2BGC10pOeBAiDhkaOENEA_GQHpu-X1dxRXeQ@mail.gmail.com> In-Reply-To: <623263165.219.1661170200563@localhost> 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> <623263165.219.1661170200563@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop <ronald-lists@klop.ws> wrote: > > > > Van: Peter Jeremy <peterj@freebsd.org> > Datum: maandag, 22 augustus 2022 10:45 > Aan: "Patrick M. Hausen" <pmh@hausen.com> > CC: Ryan Moeller <freqlabs@freebsd.org>, freebsd-current@freebsd.org > Onderwerp: Re: Beadm can't create snapshot > > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <pmh@hausen.com> wrote: > >Isn't beadm retired in favour of bectl? > > 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. > > That said "bectl create" appears to be a workable replacement for > "beadm create" and avoids the current "'snapshots_changed' is > readonly" bugs. > > -- > Peter Jeremy > ________________________________ > > > > > Hi, > > From man bectl: > activate [-t | -T] beName > Activate the given beName as the default boot filesystem. If > the -t flag is given, this takes effect only for the next boot. > Flag -T removes temporary boot once configuration. Without > temporary configuration, the next boot will use zfs dataset > specified in boot pool bootfs property. > > So it uses the bootfs property instead of loader.conf. If beadm used a different mechaniscm it would by nice to mention that in the HISTORY section of the bectl man page. > I was not aware that beadm touches loader.conf, but I find that slightly horrifying. I won't personally make bectl do that, but I guess I could at least document that it doesn't...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaEcr=9Ua8z%2BGC10pOeBAiDhkaOENEA_GQHpu-X1dxRXeQ>