Date: Sat, 3 Sep 2022 17:21:35 +0100 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: remnants after major upgrade Message-ID: <YxN/D/%2Bnp5klewvT@void.f-m.fm> In-Reply-To: <EA733418-60FA-4D1A-B542-CB390FCEB9ED@gromit.dlib.vt.edu> References: <YxM1dIkZNsluqq50@void.f-m.fm> <YxM8NJijWlUFgRfP@mail.bsd4all.net> <YxNNgRUqAfuRtuPi@void.f-m.fm> <EA733418-60FA-4D1A-B542-CB390FCEB9ED@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 03, 2022 at 10:45:20AM -0400, Paul Mather wrote: > >It's not clear to me the context of how your current system got installed. >However, bectl is part of the FreeBSD 13 base system, so if you installed >FreeBSD 13.1, then that is where that software will have originated. > >Also, it's been the case for a while that following the ZFS install >option will get you a BE-friendly setup. I've noticed that >freebsd-update now creates BEs on ZFS, too. I had no idea till now. I also have a 13-stable amd64 desktop without BE-anything, but this has been freebsd since freebsd-10 and has always followed -stable. It doesn't have zfs-on-root. The rpi4 is zfs-on-root. I have since removed -current and did a fresh 13.1-p2 install and it has a "normal" bectl output. The system arrived at its broken configuration (wrt BE-thing) because it went from 13R-p2 to -current and I did the upgrade in the usual source upgrade way. I guess now there's extra step(s) that were missed. I don't usually run zfs-on-root. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YxN/D/%2Bnp5klewvT>