Date: Wed, 16 Dec 2009 16:33:03 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Doug Barton <dougb@FreeBSD.org> Cc: Alex Keda <admin@lissyara.su>, freebsd-current <freebsd-current@freebsd.org>, Robert Watson <rwatson@freebsd.org> Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? Message-ID: <86ljh3j5n4.fsf@ds4.des.no> In-Reply-To: <4B26A4E3.9090200@FreeBSD.org> (Doug Barton's message of "Mon, 14 Dec 2009 12:49:39 -0800") References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <alpine.BSF.2.00.0912122342110.61723@fledge.watson.org> <4B25B0CA.1070006@FreeBSD.org> <20091214155853.GC78318@FreeBSD.org> <4B26A4E3.9090200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <dougb@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ljh3j5n4.fsf>