Re: Good practices with bectl

On 24/09/2022 18:08, Nuno Teixeira wrote: And src/tools/build/beinstall.sh too! … OpenPGP_signature Description: OpenPGP digital signature

Re: Good practices with bectl

On 24/09/2022 14:47, Daniel Tameling wrote: … Would it be possible to add this to the handbook? … FreeBSD bug 263331 – Explain use of bectl (if using ZFS) in the updating FreeBSD section of the FreeBSD Handbook OpenPGP_signature

Re: Good practices with bectl

And src/tools/build/beinstall.sh too! beinstall.sh is just great: `bectl list`: --- BE Active Mountpoint Space Created 14.0-CURRENT-20220924.142841 NR / 110G 2022-09-24 17:48 default - - 2.41G 2021-07-06 11:03 ---

Re: Good practices with bectl

On Wed, Sep 21, 2022 at 12:08:38PM +0100, Nuno Teixeira wrote: > Summary: Using bectl for upgrades > > RELEASE=Whatever > > bectl create ${RELEASE} > > bectl mount ${RELEASE} > BASEDIR=/tmp/be_mount. # Use mount point returned by bectl mount > > [freebsd-update method] > > freebsd-update -b

Re: Good practices with bectl

Summary: Using bectl for upgrades RELEASE=Whatever > bectl create ${RELEASE} > bectl mount ${RELEASE} BASEDIR=/tmp/be_mount. # Use mount point returned by bectl mount [freebsd-update method] > freebsd-update -b ${BASEDIR} -d ${BASEDIR}/var/db/freebsd-update \ upgrade -r ${RELEASE} >

Re: Good practices with bectl

On 20/09/22 19:19, Alan Somers wrote: On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote: 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'?)

Re: Good practices with bectl

Quoting David Wolfskill (from Wed, 21 Sep 2022 03:25:52 -0700): On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote: ... make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs Usually I replace the delete-old-libs with check-old, as I don't want to

Re: Good practices with bectl

On Wed, Sep 21, 2022 at 11:27:06AM +0200, Alexander Leidinger wrote: > ... > make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs > > Usually I replace the delete-old-libs with check-old, as I don't want > to blindly delete them (some ports may depend on them... at

Re: Good practices with bectl

Quoting Alan Somers (from Tue, 20 Sep 2022 16:19:49 -0600): sudo bectl activate ${RELEASE} Failsafe (if the machine is too far away to simply walk over and switch to the old BE): bectl activate -t ${RELEASE} Needs an activate without -t later. Bye, Alexander. --

Re: Good practices with bectl

Quoting Nuno Teixeira (from Wed, 21 Sep 2022 00:11:41 +0100): (...) maybe: > yes | make DESTDIR=${BASEDIR} delete-old delete-old-libs make DESTDIR=${BASEDIR} -DBATCH_DELETE_OLD_FILES delete-old delete-old-libs Usually I replace the delete-old-libs with check-old, as I don't want

Re: Good practices with bectl

* Nuno Teixeira [20220921 00:11]: > (...) > maybe: > > yes | make DESTDIR=${BASEDIR} delete-old delete-old-libs Exactly, DESTDIR is used by all the targets. BTW, you can just set BATCH_DELETE_OLD_FILES=yes (either on the command-line or in make.conf) instead of using "yes" here. -- Felix

Re: Good practices with bectl

On 21/09/2022 01:47, Graham Perrin wrote: On 20/09/2022 23:14, Nuno Teixeira wrote: 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

Re: Good practices with bectl

On 20/09/2022 23:14, Nuno Teixeira wrote: 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 ... >

beinstall(8) (was: Good practices with bectl)

On 21/09/2022 00:17, Paul Mather wrote: … a handy tool in /usr/src/tools/build that can be used as a wrapper to install a SRC build into a new boot environment. It's /usr/src/tools/build/beinstall.sh (see man beinstall(8) for details). … Thanks. FYI: beinstall.sh(8) should be in the FreeBSD

Re: Good practices with bectl

Hi Paul, Really nice! I will test it soon. Cheers Paul Mather escreveu no dia quarta, 21/09/2022 à(s) 00:17: > On Sep 20, 2022, at 6:19 PM, Alan Somers wrote: > > > On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira > wrote: > >> > >> Hello to all, > >> > >> I will use becl for the first time

Re: Good practices with bectl

On Sep 20, 2022, at 6:19 PM, Alan Somers wrote: > On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote: >> >> 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

Re: Good practices with bectl

(...) maybe: > yes | make DESTDIR=${BASEDIR} delete-old delete-old-libs Nuno Teixeira escreveu no dia quarta, 21/09/2022 à(s) 00:09: > Hi Alan, > > This general procedure works just as well if you're upgrading from source, >> too. >> >> sudo make DESTDIR=${BASEDIR} installworld >> sudo

Re: Good practices with bectl

Hi Alan, This general procedure works just as well if you're upgrading from source, > too. > > sudo make DESTDIR=${BASEDIR} installworld > sudo mergemaster -m $PWD -D $BASEDIR -U > (mergemaster -m -D ) using etcupdate: (etcupdate -s -D ), source defaults to /usr/src > etcupdate -D $BASEDIR

Re: Good practices with bectl

On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote: > > 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

Good practices with bectl

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