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 [EMAIL PROTECTED] http://FreeBSD.czest.pl/dunstan/ _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"