From owner-freebsd-questions Thu Nov 16 11:45:37 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA09334 for questions-outgoing; Thu, 16 Nov 1995 11:45:37 -0800 Received: from hub.org (hub.org [199.166.238.138]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA09325 for ; Thu, 16 Nov 1995 11:45:14 -0800 Received: (from scrappy@localhost) by hub.org (8.7.1/8.7.1) id OAA06541; Thu, 16 Nov 1995 14:44:44 -0500 (EST) Date: Thu, 16 Nov 1995 14:44:40 -0500 (EST) From: "Marc G. Fournier" To: Chuck Robey cc: Donald Burr , FreeBSD Questions Subject: Re: Question about incrementing kernel revision #'s? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Wed, 15 Nov 1995, Chuck Robey wrote: > I think I have this straight ... every time you do a config, unless you > use the -n parameter to config, it wipes out your build directory, > /usr/src/sys/compile/KERNELNAME. If you were to do two builds without > cleaning things out, then you would get the version number rising. This > seems to be controlled by a file vers.c which is built using a script > named newversion.sh, in /usr/src/sys/conf, which extracts all the current > info, and increments the version number (I'm not yet clear on how) > > I've seen so many embarrassing errors go by caused by folks that 'knew > better' not doing cleanouts, that I really wouldn't recommend doing that > config -n unless you're ready to look dumb when you get caught by it. > Possible to put vers.c in some sort of "holding pattern" where it doesn't get removed when you do a 'config