From owner-cvs-all@FreeBSD.ORG Fri Nov 4 16:50:45 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92FFB16A420; Fri, 4 Nov 2005 16:50:45 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA43643D48; Fri, 4 Nov 2005 16:50:44 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1372362 for multiple; Fri, 04 Nov 2005 11:52:46 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA4GocTb082798; Fri, 4 Nov 2005 11:50:39 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Ruslan Ermilov Date: Fri, 4 Nov 2005 11:43:19 -0500 User-Agent: KMail/1.8 References: <20051104093436.GI29387@submonkey.net> <20051104.091549.55832472.imp@bsdimp.com> <20051104163200.GZ63539@ip.net.ua> In-Reply-To: <20051104163200.GZ63539@ip.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511041143.22007.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: cvs-src@FreeBSD.org, ceri@submonkey.net, cvs-all@FreeBSD.org, "M. Warner Losh" , src-committers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/config configvers.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:50:45 -0000 On Friday 04 November 2005 11:32 am, Ruslan Ermilov wrote: > On Fri, Nov 04, 2005 at 09:15:49AM -0700, M. Warner Losh wrote: > > In message: <20051104120642.GL29387@submonkey.net> > > > > Ceri Davies writes: > > : On Fri, Nov 04, 2005 at 12:56:01PM +0200, Ruslan Ermilov wrote: > > : > On Fri, Nov 04, 2005 at 09:34:36AM +0000, Ceri Davies wrote: > > : > > On Fri, Nov 04, 2005 at 09:18:58AM +0200, Ruslan Ermilov wrote: > > : > > > On Fri, Nov 04, 2005 at 04:16:44AM +0000, Warner Losh wrote: > > : > > > > imp 2005-11-04 04:16:44 UTC > > : > > > > > > : > > > > FreeBSD src repository > > : > > > > > > : > > > > Modified files: > > : > > > > usr.sbin/config configvers.h > > : > > > > Log: > > : > > > > since nocpu isn't used in the kernel config base, we don't > > : > > > > need to bump the version. Peter Wemm, John Baldwin and I > > : > > > > hammered this out after the last time I needlessly incremented > > : > > > > the version. > > : > > > > > > : > > > > Revision Changes Path > > : > > > > 1.38 +1 -1 src/usr.sbin/config/configvers.h > > : > > > > > : > > > Our users wanted to *use* the "nocpu" directive in their configs > > : > > > that are based on GENERIC (GENERIC is included), hence I bumped > > : > > > config(8). Otherwise, one day some would scream that "nocpu" > > : > > > doesn't work for them, because they're using the older version > > : > > > of config(8). > > > > I will agree that bumping the config version will force users to > > install a new config. At the same time, a new config cannot be used > > for old kernels, like the ones in 6.0. Since this is the only > > incompatibility between 6.0 and current, it seemed a little > > gratuitous. > > > > There's no documentation about what features are in what versions of > > config. If you don't bump the version, then we can MFC these changes > > and users can use config in 6.x. A nit is that there's no nocpu in > > config.5. config.5 is already a different version though. > > : > > I'd agree that the Makefiles don't need to be bumped, as they don= 't > > : > > actually require the new config, but config has new functionality > > : > > and the version should probably be bumped in the binary. > > : > > > : > You cannot just bump it in one place, the version requirement doesn= 't > > : > understand >=3D, only =3D. > > : > > : Oh. Insert obvious next question here. :) > > : What happens to those people who have already installed 600004 then? > > > > They will need to install a new config if they want to build a new > > kernel. Maybe it is time to change the versioning so that multiple > > versions will work. > > This is all not needed if you're using an official upgrade method: > buildworld/buildkernel, which will take care of updating config(8) > for you. I never do that for test kernels as it is too tedious. :) Also, for my tes= t=20 kernels it is very handy to have the build directory shared over NFS just=20 like my test trees so that if the machine crashes, I still have access to t= he=20 kernel.debug on my NFS server. I think the more useful thing would be to g= et=20 config to understand >=3D for it's version tests though so that version bum= ps=20 aren't quite so painful. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org