On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop <ronald-li...@klop.ws> wrote: > > > > Van: Peter Jeremy <pet...@freebsd.org> > Datum: maandag, 22 augustus 2022 10:45 > Aan: "Patrick M. Hausen" <p...@hausen.com> > CC: Ryan Moeller <freql...@freebsd.org>, freebsd-current@freebsd.org > Onderwerp: Re: Beadm can't create snapshot > > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" <p...@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...
