Date: Sun, 15 May 2011 18:49:44 -0400 From: Lowell Gilbert <freebsd-stable-local@be-well.ilk.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: Heads up: you'll need to do a fresh "config KERNEL" etc Message-ID: <44tycv4m0n.fsf@lowell-desk.lan> In-Reply-To: <1937391434.347889.1305459865609.JavaMail.root@erie.cs.uoguelph.ca> (Rick Macklem's message of "Sun, 15 May 2011 07:44:25 -0400 (EDT)") References: <1937391434.347889.1305459865609.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Rick Macklem <rmacklem@uoguelph.ca> writes: >> On Sat, May 14, 2011 at 08:05:41PM -0400, Rick Macklem wrote: >> > Just a heads up that after a commit going into stable/8 in a few >> > minutes, you'll need to do a fresh kernel build, starting at >> > "config GENERIC", including rebuilding the NFS related modules. >> >> Rick, >> >> Can you explain why a kernel reconfig would be required if the >> kernel configuration (e.g. GENERIC) hasn't been changed? >> >> http://www.freshbsd.org/?branch=RELENG_8&project=freebsd >> >> Possibly the commit site doesn't have the most recent commits? >> >> I guess what I'm asking is: why is a kernel reconfig required if only >> the NFS code itself changed? A buildworld/buildkernel should be >> sufficient, no? >> > The commit moved the files used for a diskless root NFS from sys/nfsclient > to sys/nfs. As such, sys/conf/files has changed and, therefore, fresh > kernel Makefiles need to be built. I thought that "config KERNEL" is what > does that, but if buildkernel does, then "config KERNEL" isn't needed. It does by default, but the heads-up is still appreciated.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44tycv4m0n.fsf>