Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 Jun 2009 10:33:51 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Pieter Donche <Pieter.Donche@ua.ac.be>
Cc:        "mail.list freebsd-questions" <freebsd-questions@freebsd.org>
Subject:   Re: freebsd version numbers
Message-ID:  <4A23A07F.5030809@infracaninophile.co.uk>
In-Reply-To: <alpine.BSF.2.00.0906011017020.19528@macos.cmi.ua.ac.be>
References:  <alpine.BSF.2.00.0906011017020.19528@macos.cmi.ua.ac.be>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig96136470C28158DBE9F92F17
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Pieter Donche wrote:
> I upgraded to Freebsd systems from 7.0 to 7.2
> on the first one, done May 25th, I use the generic kernel
> $ uname -a reports: 7.2-RELEASE #0
>=20
> on the second one, done 3 days later (May 28th)
> on this system I also build and installed a custom kernel after upgrade=
=2E
> $ uname -a reports:  7.2-RELEASE #1
>=20
> Why is this different? (#0 versus #1)
>=20
> What does #Number actually mean: is this the same as -pNumber used in
> the mails from   @daily          root    freebsd-update cron
> "The following files will be updated as part of updating to
> X.Y-RELEASE-pNumber"

No, it's nothing like that.  It's a count of the number of times a
kernel has been built from a particular source tree.  Unless you're
doing active kernel development it doesn't mean anything much.

> If not, what is the difference ?
>=20
> what's the difference between version, level, patchlevel, 'release
> level', 'version level of a release' (any others ?), ...

See

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.=
html

which explains quite a lot of that sort of thing.  Effectively there are
releases made at approximately regular intervals of about 4 months.
These have names like '7.2-RELEASE'.  When significant problems or
security holes are discovered, patches will be produced for any
supported releases. These have names like '7.1-RELEASE-p5' where the
p-number is just a counter showing how many patches there have been
since the actual release.  There may be several major versions with
releases being made from them -- e.g. 6.4-RELEASE and 7.1-RELEASE came
out pretty much simultaneously.  The next release due is 8.0-RELEASE,
but there will be 7.3-RELEASE sometime after that.  There's a new major
version approximately every 18 months, from which there will typically
be 4 or 5 minor version releases).

In addition to the releases there are two types of development streams
that you can track: at the moment that's 8.0-CURRENT also known as HEAD
(the bleeding edge which is not at all suitable for beginners, nor would
any sensible person run anything important on it) and then the various
STABLE streams such as 7.2-STABLE a.k.a RELENG_7 (STABLE here is a
comment on the runtime characteristics of the OS, not on the rate of
change of the code base -- these are active development branches).
Around the time a release is made, the STABLE streams change name to eg.
7.3-PRERELEASE and possibly a few others, but it's all from the same CVS
branch.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       Flat 3
                                                      7 Priory Courtyard
PGP: http://www.infracaninophile.co.uk/pgpkey         Ramsgate
                                                      Kent, CT11 9PW, UK


--------------enig96136470C28158DBE9F92F17
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkojoH8ACgkQ3jDkPpsZ+VbErgCdGeJMxHSyebj/cnBg9pb0aEDJ
UAMAnjDOGalsLfUl+zkW8cPafYyZykVd
=Usk9
-----END PGP SIGNATURE-----

--------------enig96136470C28158DBE9F92F17--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A23A07F.5030809>