Date: Mon, 21 Jan 2013 16:26:59 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Bas Smeelen <b.smeelen@ose.nl> Cc: freebsd-doc@freebsd.org Subject: Re: freebsd-update and ports Message-ID: <alpine.BSF.2.00.1301211624310.55046@wonkity.com> In-Reply-To: <50F66D72.20807@ose.nl> References: <alpine.BSF.2.00.1301122210240.11994@wonkity.com> <CAC8HS2FewOpz_SWmwMhz7m2TgW1T7YE%2BjPGPkcSJP-TPjJ9Qng@mail.gmail.com> <alpine.BSF.2.00.1301131304290.17568@wonkity.com> <alpine.BSF.2.00.1301152053070.78271@wonkity.com> <50F66D72.20807@ose.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jan 2013, Bas Smeelen wrote: > On 01/16/2013 04:56 AM, Warren Block wrote: >> A rendered sample of the proposed changes to the freebsd-update section: >> http://www.wonkity.com/~wblock/temp/fupd-ports2.html >> >> The diff: >> http://www.wonkity.com/~wblock/temp/fupd-ports2.diff > > Looks good.. > Note that in section 25.2.3.1.2 Custom Kernels with FreeBSD 9.X and Later the > current custom kernel in /boot/kernel gets overwritten. > It might be better to change this so the GENERIC kernel is installed in > /boot/GENERIC > > I.e. instead of > > tar -C/ -xvf kernel.txz boot/kernel/kernel > > tar -C/ -xvf kernel.txz boot/GENERIC > > and instead of > > make kernel > > make buildkernel > make installkernel DESTDIR=/boot/GENERIC > > or as in the 8.X section > env DESTDIR=/boot/GENERIC make kernel But isn't that required? As I understand it, this whole procedure is to fool freebsd-update into thinking that a GENERIC kernel is being used. In 9.X, it will look for that kernel in the normal installed location, /boot/kernel. And of course the user will have to rebuild their custom kernel after the update anyway.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301211624310.55046>