From owner-freebsd-arch@FreeBSD.ORG Thu Jan 14 20:12:28 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F5E41065670; Thu, 14 Jan 2010 20:12:28 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 55EEF8FC1A; Thu, 14 Jan 2010 20:12:28 +0000 (UTC) Received: from [192.168.2.102] (host86-178-254-187.range86-178.btcentralplus.com [86.178.254.187]) by cyrus.watson.org (Postfix) with ESMTPSA id EE0DE46B0D; Thu, 14 Jan 2010 15:12:26 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4B4F7810.2080003@FreeBSD.org> Date: Thu, 14 Jan 2010 20:12:24 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <86625798-F339-4863-8F97-63B5232A6CF7@freebsd.org> References: <4B4E1586.7090102@FreeBSD.org> <20100114.102142.328914705071816274.imp@bsdimp.com> <20100114.105622.457034909117828677.imp@bsdimp.com> <4B4F7810.2080003@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1077) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, freebsd-arch@freebsd.org Subject: Re: INCLUDE_CONFIG_FILE in GENERIC X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jan 2010 20:12:28 -0000 On 14 Jan 2010, at 20:01, Doug Barton wrote: > FWIW, I actually think this makes it worse, not better. The > INCLUDE_CONFIG_FILE option should include everything needed to = recreate > the kernel. If it doesn't, it's worse than worthless, it leads to a > false sense of security which makes it dangerous. I wasn't actually > aware that if you do the config -C trick that you'll get ONLY the one > file, not everything. (...more irritated words stripped like the comments in a config file...) I agree. I see two kinds of users: - Desktop/server users who want their system to work without any special = tuning or magic, and likely feel the comments they put in configuration = files are important - Users who care a about a few hundred bytes of comments due to the = nature of their special embedded hardware target environment As such, I see a reasonable "default" -- i.e., i386/amd64 GENERIC -- be = to fully preserve the configuration and its comments. For the embedded = and appliance crowds, I definitely want them to be able to fully exclude = the configuration (by not including the option). I don't see a lot of = merit to supporting stripping the comments, but if someone wants that = special case, I'm OK with supporting it, but I think it's an unuseful = default for the desktop/server platforms. Robert=