Good practices with bectl

From: Nuno Teixeira <eduardo_at_freebsd.org>
Date: Tue, 20 Sep 2022 22:14:10 UTC
Hello to all,

I will use becl for the first time for current upgrades.
Just to check that I'm thinking correctly:

Create a test environment for upgrade:
> bectl create -r test (should I use '-r'?)
Activate test:
> bectl activate test
> reboot
...
> upgrade OS on test
> reboot
...
if a problem happens, reboot default from BE loader
---
if everything fine destroy default and rename test to default
> bectl destroy -o default
> bectl rename test default
repeat on next upgrade

Don't know if a faster way exists with chroot or bectl jail...

Any hints appreciated.

Thanks,
-- 
Nuno Teixeira
FreeBSD Committer (ports)