From owner-freebsd-questions@FreeBSD.ORG Thu Jul 29 16:15:43 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 605A216A4CE for ; Thu, 29 Jul 2004 16:15:43 +0000 (GMT) Received: from smtp.infracaninophile.co.uk (happy-idiot-talk.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96ECC43D45 for ; Thu, 29 Jul 2004 16:15:42 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost.infracaninophile.co.uk [IPv6:::1])i6TGFZCT067270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jul 2004 17:15:35 +0100 (BST) (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost)id i6TGFZ1c067269; Thu, 29 Jul 2004 17:15:35 +0100 (BST) (envelope-from matthew) Date: Thu, 29 Jul 2004 17:15:34 +0100 From: Matthew Seaman To: Cedric GROSS Message-ID: <20040729161534.GB80531@happy-idiot-talk.infracaninophile.co.uk> Mail-Followup-To: Matthew Seaman , Cedric GROSS , freebsd-questions@freebsd.org References: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E4289D@srvw2000-cnv1.cnv.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline In-Reply-To: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E4289D@srvw2000-cnv1.cnv.local> User-Agent: Mutt/1.5.6i X-Greylist: Message not sent from an IPv4 address, not delayed by milter-greylist-1.5.3 (smtp.infracaninophile.co.uk [0.0.0.0]); Thu, 29 Jul 2004 17:15:35 +0100 (BST) X-Virus-Scanned: clamd / ClamAV version devel-20040705, clamav-milter version 0.74a on smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on happy-idiot-talk.infracaninophile.co.uk cc: freebsd-questions@freebsd.org Subject: Re: Updating 5.2.1 Release # X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 16:15:43 -0000 --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--