From owner-freebsd-stable  Fri Oct  3 06:22:30 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA12961
          for stable-outgoing; Fri, 3 Oct 1997 06:22:30 -0700 (PDT)
Received: from emout04.mail.aol.com (emout04.mx.aol.com [198.81.11.95])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12954
          for <freebsd-stable@freebsd.org>; Fri, 3 Oct 1997 06:22:26 -0700 (PDT)
From: Hetzels@aol.com
Received: (from root@localhost)
	  by emout04.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0)
	  id JAA12559;
	  Fri, 3 Oct 1997 09:21:54 -0400 (EDT)
Date: Fri, 3 Oct 1997 09:21:54 -0400 (EDT)
Message-ID: <971003092057_519245415@emout04.mail.aol.com>
To: chad@dcfinc.com
cc: freebsd-stable@freebsd.org
Subject: Re: CVSUP vs. SNAPS
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In a message dated 97-10-02 20:37:36 EDT, chad@freebie.dcfinc.com writes:
>  
>  > I've got several systems around here that are nearly
>  > impossible to determine what rev is on them because they all say
>  > 2.2-STABLE, even though some of them are from the 2.2.0 time frame,
>  > and others are 2 hours old.  If I can't tell the difference, then
>  > autoconfig scripts that use uname can't either.
>  
>  Ah, but that's a different problem (and one I raised a couple of weeks
ago).
>  
>  There should be some easy way (perhaps through "uname") to know where
>  along the STABLE continuum a particular system resides.
>  

I've come up with a fix for this problem that uses the CTM number to indicate
the systems current status.  See my message "CTM patch level added to
newvers.sh" for the patch.

Scot W. Hetzel