Date: Tue, 6 Nov 2018 17:42:15 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: freebsd-update(8) and custom kernels Message-ID: <20181106174215.43746c0a0f28d86dd4ef0e14@sohara.org> In-Reply-To: <CAEAzY3_oF94bezhVte7Ym5Y0qfEypu7rabh4BGx6v%2BOFi6cR%2BA@mail.gmail.com> References: <CAEAzY3_BzOH25aoTpTWTREbhJD0V0o8RKCV6A4sVnXtCpRjE3g@mail.gmail.com> <20181106170818.GD88460@mordor.lan> <CAEAzY3_oF94bezhVte7Ym5Y0qfEypu7rabh4BGx6v%2BOFi6cR%2BA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Nov 2018 18:28:21 +0100 Aram Hăvărneanu <aram.h@mgk.ro> wrote: > > I usually use: > > $> freebsd-update fetch > > $> freebsd-update install > > $> make kernel KERNCONF=MYKERNEL > > $> reboot > > That works for installing updates to the same release, but I don't > see how it would work for upgrading to a new release > (freebsd-update -r XX.Y-RELEASE upgrade). You need to boot up > the new kernel before installing the new binaries. Indeed, > freebsd-update does a two stage process. I have used this procedure for upgrading several times now (most recently from 11.1 to 11.2 - and that box started on 9.<something> so it's been through two major version upgrades). There's an extra freebsd-update install after the reboot but other than that it's fine IME, YMMV of course. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181106174215.43746c0a0f28d86dd4ef0e14>