freebsd-update patch not being applied
For some reason when i type uname -a on my desktop, which is running 7.1, all I see is this: $ uname -a FreeBSD me 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 But if i run freebsd-update fetch i get this $ sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.1-RELEASE-p3. Everytime the application has said there are new updates i installed them with `freebsd-update install`, and eventually i got around to restarting, but when I log back in and type `uname -a` I get the same message as above: `7.1-RELEASE #0` Now on a seperate system running 7.0 I have a similar problem where uname -a always reports `7.0-RELEASE-p7 #0` even though freebsd-update reports Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.0-RELEASE-p10. Now I'm new to the BSD world, but i do have a fair amount of experience with Linux. What I am trying to figure out here, is why uname -a reports a different patch number than it should. Thanks James -- James ja...@slohall.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update patch not being applied
On Sun, Mar 01, 2009 at 08:50:48AM -0800, James wrote: For some reason when i type uname -a on my desktop, which is running 7.1, all I see is this: $ uname -a FreeBSD me 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 But if i run freebsd-update fetch i get this $ sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.1-RELEASE-p3. Everytime the application has said there are new updates i installed them with `freebsd-update install`, and eventually i got around to restarting, but when I log back in and type `uname -a` I get the same message as above: `7.1-RELEASE #0` Now on a seperate system running 7.0 I have a similar problem where uname -a always reports `7.0-RELEASE-p7 #0` even though freebsd-update reports Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.0-RELEASE-p10. Now I'm new to the BSD world, but i do have a fair amount of experience with Linux. What I am trying to figure out here, is why uname -a reports a different patch number than it should. This is the normal behaviour for freebsd-update. The patch level number will only bump if an update affects the kernel. The most recent updates for 7.1 didn't touch the kernel, so you still see the previous (somewhat confusing) version number. However, if the next update requires that the kernel be replaced, then you'll see the patch level number increase. Hope this makes sense... Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpra17LS9ofP.pgp Description: PGP signature
Re: freebsd-update patch not being applied
On Sun, 1 Mar 2009 17:46:27 + Daniel Bye danie...@slightlystrange.org wrote: On Sun, Mar 01, 2009 at 08:50:48AM -0800, James wrote: For some reason when i type uname -a on my desktop, which is running 7.1, all I see is this: $ uname -a FreeBSD me 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 But if i run freebsd-update fetch i get this $ sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.1-RELEASE-p3. Everytime the application has said there are new updates i installed them with `freebsd-update install`, and eventually i got around to restarting, but when I log back in and type `uname -a` I get the same message as above: `7.1-RELEASE #0` Now on a seperate system running 7.0 I have a similar problem where uname -a always reports `7.0-RELEASE-p7 #0` even though freebsd-update reports Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.0-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.0-RELEASE-p10. Now I'm new to the BSD world, but i do have a fair amount of experience with Linux. What I am trying to figure out here, is why uname -a reports a different patch number than it should. This is the normal behaviour for freebsd-update. The patch level number will only bump if an update affects the kernel. The most recent updates for 7.1 didn't touch the kernel, so you still see the previous (somewhat confusing) version number. However, if the next update requires that the kernel be replaced, then you'll see the patch level number increase. Hope this makes sense... Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ Makes perfect sense, thanks for replying, i appreciate the help James -- James ja...@slohall.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update patch not being applied
On Sun 2009-03-01 08:50:48 UTC-0800, James (ja...@slohall.com) wrote: For some reason when i type uname -a on my desktop, which is running 7.1, all I see is this: $ uname -a FreeBSD me 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 But if i run freebsd-update fetch i get this $ sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 7.1-RELEASE from update2.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 7.1-RELEASE-p3. Everytime the application has said there are new updates i installed them with `freebsd-update install`, and eventually i got around to restarting, but when I log back in and type `uname -a` I get the same message as above: `7.1-RELEASE #0` This is (probably) normal. uname -a shows the kernel version, however often freebsd-update will patch other (non-kernel) parts of the base system, leaving the kernel alone. eg. the recent bug involving telnetd on 7.x systems only required patching the telnetd binary. AFAIK, each time a patch is required, /usr/src/sys/conf/newvers.sh is updated. $ sudo freebsd-update fetch No updates needed to update system to 6.4-RELEASE-p3. $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE-p1 FreeBSD 6.4-RELEASE-p1 #0: Sun Dec 21 07:56:41 UTC 2008 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 $ grep -v # /usr/src/sys/conf/newvers.sh | head -4 TYPE=FreeBSD REVISION=6.4 BRANCH=RELEASE-p3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org