From owner-freebsd-hackers Tue Jul 1 08:33:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA04326 for hackers-outgoing; Tue, 1 Jul 1997 08:33:35 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA04321 for ; Tue, 1 Jul 1997 08:33:31 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wj4vd-0006AC-00; Tue, 1 Jul 1997 09:33:17 -0600 To: David Dawes Subject: Re: Determining FreeBSD versions Cc: hackers@freebsd.org In-reply-to: Your message of "Tue, 01 Jul 1997 19:03:53 +1000." <19970701190353.50830@rf900.physics.usyd.edu.au> References: <19970701190353.50830@rf900.physics.usyd.edu.au> Date: Tue, 01 Jul 1997 09:33:17 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970701190353.50830@rf900.physics.usyd.edu.au> David Dawes writes: : branch, and as a consequence, 'uname -r' now reports "2.1-STABLE" rather Hmmm. Why not report 2.1.x-STABLE? Where x is incremented whenever a release happens. Then people know that things are newer than 2.1.x or 2.2.x or whatever. I'm not completely sure that parsing osversion.h (or is that osreldate.h) is the right answer here. Warner