Date: Wed, 28 Jul 2021 17:28:04 -0700 From: Chuck Tuffli <ctuffli@gmail.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: freebsd-pkgbase@freebsd.org Subject: Re: best practices for updating? Message-ID: <CAKAYmMJWC8-HFqphuSfukb%2Ba-U5tsg_7MB_U=5dGpksGKcmGCg@mail.gmail.com> In-Reply-To: <20210712120552.88a43820aa40314755eacfae@bidouilliste.com> References: <CAKAYmMKW9Duf8UtQ3ZvzEjozvTrM2_wbc-XJ=zudu9j9g9BxvQ@mail.gmail.com> <20210712120552.88a43820aa40314755eacfae@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the feedback. See below for a couple of questions: On Mon, Jul 12, 2021 at 3:05 AM Emmanuel Vadot <manu@bidouilliste.com> wrote: ... > What I do on my systems is : > > pkg upgrade --fetch-only > bectl create XXX > pkg upgrade FreeBSD-kernel-generic (or FreeBSD-kernel-generic-nodebug > on some machines) > nextboot -o "-s" > shutdown -r now So if I understand this correctly, after the reboot, the system should come up in single user mode, yes? It didn't seem to work, but maybe I confused things with the boot environments. > pkg upgrade FreeBSD-clibs (this takes care on ABI mismatch or new syscalls) Running this from single-user errors out with "pkg: Insufficient privilege to upgrade packages". But this make me suspect I misunderstood the previous instructions. > pkg upgrade FreeBSD-runtime > pkg upgrade -r base > > There is sometimes some others step needed when we move stuff from > packages to packages or creates new packages > (https://cgit.freebsd.org/src/commit/UPDATING?id=1c2ab28f598a9598b3c50d9001c70ff51f88e445 > is a good example of such workaround sometimes needed). > > Cheers, > > -- > Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKAYmMJWC8-HFqphuSfukb%2Ba-U5tsg_7MB_U=5dGpksGKcmGCg>