From owner-freebsd-arch@FreeBSD.ORG Wed Sep 24 16:37:11 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BB5116A4B3; Wed, 24 Sep 2003 16:37:11 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E18443FBF; Wed, 24 Sep 2003 16:37:08 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id JAA15687; Thu, 25 Sep 2003 09:36:56 +1000 Date: Thu, 25 Sep 2003 09:35:31 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: John Baldwin In-Reply-To: Message-ID: <20030925092319.H5418@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: arch@freebsd.org Subject: Re: sys/conf/DEFAULT[S] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 23:37:11 -0000 On Wed, 24 Sep 2003, John Baldwin wrote: > Now that we have 'nooptions' and 'nodevice' in kernel config files as well > as the ability to include other config files, I'd like to tweak config(8) > so that it automatically includes sys/conf/DEFAULT (or DEFAULTS) and > sys/${MACHINE}/conf/DEFAULT (S) when generating a kernel config and then > get rid of all the 'NO_*' options. OK with me. Do we actually gave the abiltity to include other config files? It was quite broken last time I tried to use it for anything more complicated than the example in "SMP". When breaking POLA by renaming options, please use a consistent namespace for the new names... > For example, NO_F00F_HACK could be renamed to a positive FOOF_HACK option. > sys/i386/conf/DEFAULT would contain 'options F00F_HACK' and if people > wanted to disable it they could use 'nooptions F00F_HACK' in their custom > config. In a consistent namespace, it would be CPU_F00F_HACK or maybe CPU_PENTIUM1_F00F_HACK. > Another nice thing, btw, might be to add a sys/conf/GENERIC that the > MD GENERIC's could include that would include common things like > 'ident', 'FFS', 'INET', etc. Too much of this would make it harder to see where things are, especially if there are things toggled back and forth. Something like "make LINT" would be needed to see the final set of directives. Similarly for Makefiles generated by config. It has become hard to temporarily change options by editing the Makefile, since many things are set in .mk files in the source tree. Bruce