Updating 5.2.1 Release #

[Matthew Seaman]

On Thu, Jul 29, 2004 at 09:37:35AM -0500, Puna Tannehill wrote:
> Scott wrote:

> >uname -a shows:
> >FreeBSD 5.2.1-Release #0:
> >
> >I was expecting the release (version, revision# ?) number to 
> >be greater than #0. I think I've seen where the latest 
> >revision is #9 or so? Do I need to tell it to get the latest 
> >revision somehow? Do I need to change the cvs tag= to 
> >something else to get up to date?
> 
> I thought the #number indicated the number of times the server has been 
> rebooted based upon the last time the kernel was recompiled.  Being that it 
> is #0, it was your first book.  Reboot the machine and check the number 
>  again.

I believe that the #n is the number of times the kernel has been
re-compiled since the last time the system was installed.  It's
probably not a very interesting datum except to kernel hackers who
need to do a lot of recompiling.

What the original poster was thinking of is the patchlevel that gets
incremented every time a new security (or nowadays: errata) patch is
applied to any of the -RELEASE branches.  That modifies the OS name
(ie. the output of 'uname -r'), so instead of:

    5.2.1-RELEASE

it says (at the latest count):

    5.2.1-RELEASE-p9

See /usr/src/sys/conf/newvers.sh for the file that controls all that.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040729/7d639926/attachment.bin