NomadBSD does not respect BE-flags

NomadBSD Development
1

before starting a big package update on NomadBSD-1.4, I created a boot environment (BE) before initiating the task

% sudo bectl create 2021-07-21_bf-pkg-upgrade

later I wanted to boot into this BE again

% sudo bectl activate 2021-07-21_bf-pkg-upgrade

But I ended up in the BE named nomadbsd-1.4

% bectl list
BE Active Mountpoint Space Created
2021-07-21_bf-pkg-upgrade R - 14.4G 2021-07-21 13:20
210414-225354 - - 3.14G 2021-04-14 22:54
nomadbsd-1.4 N / 4.58G 2021-04-14 22:32

also pressing [7] to the first boot-menu and choosing (the already chosen) 2021-07-21_bf-pkg-upgrade-BE still ended up booting the nomadbsd-1.4-BE???

The only way I can boot into my created BE is to rename the nomadbsd-1.4-BE to something else and rename my BE to nomadbsd-1.4 :thinking:

Is this behavior to be expected?

2

FOUND IT!
The boot environment is locked down in /boot/loader.conf
(overriding even the bootup-menu)

> cat /boot/loader.conf | grep ‘vfs.root.mountfrom’
vfs.root.mountfrom=“zfs:zroot/ROOT/nomadbsd-5806f915”

This can probably be relaxed a bit - to late to “experiment” now…

2 Likes