From owner-freebsd-current@FreeBSD.ORG Mon Mar 26 16:39:43 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E1CE16A478 for ; Mon, 26 Mar 2007 16:39:43 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id 65DDC13C457 for ; Mon, 26 Mar 2007 16:39:42 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l2QHAIPO016766 for ; Mon, 26 Mar 2007 17:10:18 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l2QHAHjX016765 for freebsd-current@FreeBSD.ORG; Mon, 26 Mar 2007 17:10:18 GMT (envelope-from dunstan) Date: Mon, 26 Mar 2007 17:10:16 +0000 From: "Wojciech A. Koszek" To: freebsd-current@FreeBSD.ORG Message-ID: <20070326171016.GA16746@FreeBSD.czest.pl> Mail-Followup-To: "Wojciech A. Koszek" , freebsd-current@FreeBSD.ORG References: <20070324135333.GA86105@FreeBSD.czest.pl> <200703261347.l2QDl6rM021066@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <200703261347.l2QDl6rM021066@lurza.secnetix.de> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Mon, 26 Mar 2007 17:10:18 +0000 (UTC) Cc: Subject: Re: Improved 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: Mon, 26 Mar 2007 16:39:43 -0000 On Mon, Mar 26, 2007 at 03:47:06PM +0200, Oliver Fromme wrote: > Wojciech A. Koszek wrote: > > Alex Kozlov wrote: > > > Wojciech A. Koszek wrote: > > > > Current implementation of INCLUDE_CONFIG_FILE option has number of > > > > issues. Including it in MAC or SMP configurations will bring only text > > > > of this single file into the kernel file. We're not able to see > > > > configuration of running ("live") kernel, which could be helpful while > > > > tracking users' reports. You can't get easy to use file format, ready > > > > for configuration process. > > > > > > > > In my Perforce wkoszek_kconftxt branch: > > > > > > > > //depot/user/wkoszek/wkoszek_kconftxt/... > > > > > > > > I brought some modifications to existing config(8) and added system > > > > interface that would let us to see configuration of running kernel > > > > (currently -- via kern.conftxt sysctl), as well as other kernel file > > > > through config(8)'s -k option. > > > > > > By the way, any plan to include INCLUDE_CONFIG_FILE in GENERIC? > > > > I'd like to have this enabled by default, and I know there should be no > > strong objections. > > No objection from me, but please fix it so include files > are also included in the kernel. > > Many of my kernel config files have only few lines (e.g. > "options SMP" and "include MYKERNEL"). Currently, the > INCLUDE_CONFIG_FILE feature only includes those two lines, > rendering that feature useless (and even potentially > dangerous if someone relies on his config to be in the > kernel). You'll get full configuration file, no matter what you include. After redirecting it to file, you'll be able to compile the kernel with no additional modifications. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/