well I know about the newvers.sh. But as far as I understand the advisory (and
the patch) the file sys/kern/uipc_usrreq.c is modified. I'm not that much into
the FreeBSD kernel code. However, isn't this affecting the kernel image?
regards - Michael
On 07.10.2011 13:33, n dhert wrote:
> I believe
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
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@
On Fri, Oct 07, 2011 at 08:55:26AM +0200, n dhert thus spake:
I just applied security patch -p4 (last week -p3) to a freebsd 8.2 system
(generic kernel)
# freebsd-update fetch
# freebsd-update install
# ls -la /usr/src/sys/conf/newvers.sh
has date of today and contains
REVISION="8.2"
BRANCH="RELE
I just applied security patch -p4 (last week -p3) to a freebsd 8.2 system
(generic kernel)
# freebsd-update fetch
# freebsd-update install
# ls -la /usr/src/sys/conf/newvers.sh
has date of today and contains
REVISION="8.2"
BRANCH="RELEASE-p4"
reboot
# uname -r
8.2-RELEASE-p3
still shows -p3 not -p4
