Date: Thu, 29 Jul 2004 17:15:34 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Cedric GROSS <cedric.gross@cnv.fr> Cc: freebsd-questions@freebsd.org Subject: Re: Updating 5.2.1 Release # Message-ID: <20040729161534.GB80531@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E4289D@srvw2000-cnv1.cnv.local> References: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E4289D@srvw2000-cnv1.cnv.local>
next in thread | previous in thread | raw e-mail | index | archive | help
--ftEhullJWpWg/VHq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jul 29, 2004 at 05:51:57PM +0200, Cedric GROSS wrote:
> So what is the diff between uname -r and uname -v, which produce for me
> :
>=20
> Uname -r : 5.2.1-RELEASE
> Uname -v : FreeBSD 5.2.1-RELEASE #0: Mon Jun 14 14:52:08 CEST 2004
> root@bruce.cnv.local:/usr/obj/usr/src/sys/CNV_TOTAL
>=20
> Extract from man page :
> -r Write the current release level of the operating system
> -v Write the version level of this release of the operating system
>=20
> So that's mean that there are several Release ( as relesase level) and
> inside each release level there are several version level, am'I
> understanding well ?
The different flags to uname(1) basically select different bits out of
the uname data -- so 'uname -a' gives you *all* of the data, 'uname
-r' gives you the release level, 'uname -m' gives you the hardware
architecture, etc. etc.
Note that this command isn't FreeBSD specific -- the behaviour of
uname(1) is part of the POSIX.2 specification, which means it will
work the same way on any current unixoid OS you care to mention. Of
course, different development groups do tend to have slightly
different interpretations of exactly what it is POSIX.2 mandates
should be printed out in each case.
Under FreeBSD, 'uname -v' attempts to give you as unambiguous as
possible identification of exactly what kernel/OS setup you have.
Since FreeBSD has quite a number of different code branches, and
several of those branches are under continuous development, and
kernels can be compiled in various different configurations by various
different people, it takes quite a complicated string to identify all
of that. Other OSes tend to be somewhat more terse, especially those
where the development process isn't exposed to the public: for
instance Solaris just gives you the OS version number and the relevant
patch id (if any) where patching has involved replacing the kernel
image.
Cheers,
Matthew
--=20
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
--ftEhullJWpWg/VHq
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBCSKmiD657aJF7eIRAiXhAJ9pqzv+oB2OHm3ICGgPyuy/I0GcGQCghn/4
r8UgFWeTJwX5UYTquZOOLG4=
=iRQD
-----END PGP SIGNATURE-----
--ftEhullJWpWg/VHq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040729161534.GB80531>