From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 15:33:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93AB9106566C; Wed, 16 Dec 2009 15:33:04 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 50ECF8FC18; Wed, 16 Dec 2009 15:33:04 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 4F6A56D41B; Wed, 16 Dec 2009 15:33:03 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 1F320844F3; Wed, 16 Dec 2009 16:33:03 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Doug Barton References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <4B25B0CA.1070006@FreeBSD.org> <20091214155853.GC78318@FreeBSD.org> <4B26A4E3.9090200@FreeBSD.org> Date: Wed, 16 Dec 2009 16:33:03 +0100 In-Reply-To: <4B26A4E3.9090200@FreeBSD.org> (Doug Barton's message of "Mon, 14 Dec 2009 12:49:39 -0800") Message-ID: <86ljh3j5n4.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alex Keda , freebsd-current , Robert Watson Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:33:04 -0000 Doug Barton writes: > Wojciech A. Koszek wrote: > > It looks fine for the first glance. I would also reconsider putting it = in > > DEFAULTS, as des@ pointed out. > Ok, no objections on my part. I thought putting it in the file itself > would make it easier for those who wanted to remove it, but I'm also > in agreement with those that believe that there is no real need to > remove it except for extreme cases, and they (generally) already know > what they are doing. :) One could argue that making it hard to disable is a feature... Anyway, adding nooption INCLUDE_CONFIG_FILE to your kernel config will disable it without having to mess with DEFAULTS. I wish we had a global DEFAULTS, though, so you didn't have to add INCLUDE_CONFIG_FILE to N different files. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no