Mark Boolootian wrote:
I've done a couple of fresh installs on 7.0-RELEASE today, and
subsequently run freebsd-update. freebsd-update reports:
The following files will be updated as part of updating to 7.0-RELEASE-p3:
which leads me to conclude I've got -p3, including the BIND update.
However 'uname -a' says something else:
FreeBSD mumble.ucsc.edu 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18
07:33:20 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
And although /usr/sbin/named has been updated, it appears not to have
$ /usr/sbin/named -v
You've got p3, don't worry. There was no kernel update in p3, hence you
got the p2 GENERIC kernel. If you want uname to actually show p3, you
will have to recompile your kernel, using something like this (assuming
you got the kernel sources installed and intend to keep using GENERIC):
make buildkernel installkernel KERNCONF=GENERIC
and then reboot
However the only difference will be in the -p number, nothing else so
you don't have to do it.
FWIW, the /usr/src/sys/conf/newvers.sh contains the -p number you see in
uname, and this changes everytime freebsd-update fetches updates -
whether they include kernel updates or not. Some people (especially
those responsible for large number of machines) will recompile the
kernel anyway, so they can easily see their patchlevel using uname.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"