From owner-freebsd-stable@FreeBSD.ORG Mon Mar 19 17:54:20 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4971A16A406 for ; Mon, 19 Mar 2007 17:54:20 +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 7BA1D13C4C5 for ; Mon, 19 Mar 2007 17:54:19 +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 l2JIORRj022418; Mon, 19 Mar 2007 18:24:28 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l2JIORt7022417; Mon, 19 Mar 2007 18:24:27 GMT (envelope-from dunstan) Date: Mon, 19 Mar 2007 18:24:26 +0000 From: "Wojciech A. Koszek" To: LI Xin Message-ID: <20070319182426.GA22325@FreeBSD.czest.pl> References: <45FE8EF3.7030400@delphij.net> <028501c76a2b$3c496750$b3db87d4@multiplay.co.uk> <20070319142604.GA21454@FreeBSD.czest.pl> <45FE9CF9.70100@delphij.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <45FE9CF9.70100@delphij.net> 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, 19 Mar 2007 18:24:28 +0000 (UTC) Cc: freebsd-stable@freebsd.org, Steven Hartland , Pete French Subject: Re: Reverting to 6.2-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2007 17:54:20 -0000 On Mon, Mar 19, 2007 at 10:23:53PM +0800, LI Xin wrote: > Wojciech A. Koszek wrote: [..] > >> I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we > >> should add it to DEFAULTS some day... > > > > I did some work in this area, as several system administrators I've met > > also seem to have problem with kernel configuration recovery. In my case > > I came with a method of obtaining a configuration of a running kernel > > via sysctl (kern.conftxt for now) and via config(8) form the kernel file. > > > > Hopefully this work will get more review soon. > > Not sure how useful could it be to expose it via sysctl(8) interface but > sounds interesting to me. Have you posted the patch somewhere? Well, being able to ask about output of: sysctl -a | egrep '(LOCK_PROFILING|WITNESS)' Or any other important options, whose impact isn't directly noticeable is useful, at least for me; even without mentioning, how useful would be to have a feature in our build infrastructure, which could warn a user, that the kernel module which is being compiled separately (e.g: from ports/) doesn't have LOCK_PROFILING, while the running kernel has this option included. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/