From owner-freebsd-stable Fri Oct 3 16:55:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA20965 for stable-outgoing; Fri, 3 Oct 1997 16:55:43 -0700 (PDT) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA20958 for ; Fri, 3 Oct 1997 16:55:40 -0700 (PDT) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.3/8.8.3a) id QAA00960; Fri, 3 Oct 1997 16:54:49 -0700 (MST) From: "Chad R. Larson" Message-Id: <199710032354.QAA00960@freebie.dcfinc.com> Subject: Re: CVSUP vs. SNAPS To: Hetzels@aol.com Date: Fri, 3 Oct 1997 16:54:47 -0700 (MST) Cc: stable@freebsd.org In-Reply-To: <971003092057_519245415@emout04.mail.aol.com> from "Hetzels@aol.com" at "Oct 3, 97 09:21:54 am" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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. And certainly in the correct spirit of things. However, I have a T1 to the internet, and use CVSup to track the -STABLE branch. Something perhaps a little more universal is needed. Perhaps a hack to CVSup to collect some serialized number, or date/time stamp which can be built into the kernel (part of the uname structure)? Of course, that doesn't cover folks who update the kernel seperately from all the utilities. Or who update one subsystem (sendmail, perhaps). Those people can check the ID of the source files, I guess. And they should know what parts they have mucked with. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com crl22@aol.com DCF, Inc. - 14523 North 49th Place, Scottsdale, Arizona 85254