Date: Mon, 26 Mar 2007 13:58:06 +0000 From: "Wojciech A. Koszek" <wkoszek@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Improved INCLUDE_CONFIG_FILE Message-ID: <20070326135806.GA13651@FreeBSD.czest.pl> In-Reply-To: <4607523E.50201@freebsd.org> References: <20070324113739.GA41119@ravenloft.kiev.ua> <20070324135333.GA86105@FreeBSD.czest.pl> <20070324153108.P4956@fledge.watson.org> <20070324220041.GI847@turion.vk2pj.dyndns.org> <20070324233307.GA93841@FreeBSD.czest.pl> <20070325153013.E77473@ury.york.ac.uk> <4607523E.50201@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 25, 2007 at 11:55:26PM -0500, Eric Anderson wrote: > On 03/25/07 09:34, Gavin Atkinson wrote: > >On Sat, 24 Mar 2007, Wojciech A. Koszek wrote: > >>On Sun, Mar 25, 2007 at 08:00:41AM +1000, Peter Jeremy wrote: [..] > >strings `sysctl -n kern.bootfile` | grep ^___ | sed -e 's/^___//' > > > >should still work if it was in a .comment section > > > Unless you no longer have the running kernel, or it has changed since > the boot up of the system. A sysctl knob to dump it is *very* useful. The main intention of my work is ask beggining user if he has specific option compiled into the kernel, and do it as easy, as typing "kldstat" for checking, if he has required KLD loaded. Yes, it is useful there. config -k <K>, where the <K> can be either /boot/kernel/kernel or kernel from port-mortem analysisshould be also quite useful. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070326135806.GA13651>