Date: Tue, 6 Nov 2018 19:57:12 +0100 From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= <aram.h@mgk.ro> To: "Steve O'Hara-Smith" <steve@sohara.org> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update(8) and custom kernels Message-ID: <CAEAzY3_xbb76vWYkFKXc3mBOdceBX3GdZ=SXEYyNSNGARvgu_A@mail.gmail.com> In-Reply-To: <20181106174215.43746c0a0f28d86dd4ef0e14@sohara.org> References: <CAEAzY3_BzOH25aoTpTWTREbhJD0V0o8RKCV6A4sVnXtCpRjE3g@mail.gmail.com> <20181106170818.GD88460@mordor.lan> <CAEAzY3_oF94bezhVte7Ym5Y0qfEypu7rabh4BGx6v%2BOFi6cR%2BA@mail.gmail.com> <20181106174215.43746c0a0f28d86dd4ef0e14@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. I still don't understand how this works. To build the new kernel for a newer RELEASE you need both the new binaries (which require the new kernel to boot first), and the new sources (which don't require anything). I assume you run freebsd-update first (which overwrites your kernel with the GENERIC one), then run freebsd-update after you have booted GENERIC (this will install new binaries, and I assume new sources), then recompile and reinstall your custom kernel, and then reboot again? If I guessed correctly you need an extra reboot step, and you need to boot at least once with a GENERIC kernel. Did I understand you correctly? --=20 Aram H=C4=83v=C4=83rneanu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEAzY3_xbb76vWYkFKXc3mBOdceBX3GdZ=SXEYyNSNGARvgu_A>