Date: Fri, 7 Oct 2011 13:33:55 +0200 From: n dhert <ndhertbsd@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: FBSD82 sec patch -p4, uname still -p3 Message-ID: <CAEFCw4s2jfgWja47ptPgUWPUOxojSr-UKh9k3iBnuhUWoUWPCw@mail.gmail.com> In-Reply-To: <4E8EC7EE.80505@gmail.com> References: <CAEFCw4v9v5f3fatEhff60LdLjhcMcsAAbWeWzh5GiMin9SsXYA@mail.gmail.com> <20111007070114.GA46357@eggman.experts-exchange.com> <4E8EC7EE.80505@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe the reason is the following: The changes were to /boot/GENERIC/linux.ko and /boot/GENERIC/linux.ko.symbols and NOT to the *freebsd* kernel /boot/GENERIC/kernel ... So,the freebsd kernel didn't change, uname -a gets its info from the linux kernel (not directly from the /usr/src/sys/conf/newvers.sh file), this is unchanged, hence it still reports -p3 On another system where I have a custom kernel (QUOTA support), as always, I did a makebuild from sources (although stricktly spreaking it in *this* case it was not necessary), did a makeinstall, rebooted, and there uname -a is -p4, which makes sense, since rebuilding the kernel from source files wrote the information contained in /usr/src/sys/conf/newvers.sh into the kernel binary, from which uname -a extracts the patch version .. 2011/10/7 Michael Schaefer <utf128@googlemail.com> > On 07.10.2011 09:01, Jason Helfman wrote: > > If your kernel wasn't touched during the update, then uname won't bump. > > but as -p4 for 8.2 fixes FreeBSD-SA-11:05.unix, it should have touched the > kernel, shouldn't it? > > regards - Michael > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEFCw4s2jfgWja47ptPgUWPUOxojSr-UKh9k3iBnuhUWoUWPCw>