Date: Tue, 01 Jan 2008 11:59:34 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Karsten Behrmann <BearPerson@gmx.net> Cc: freebsd-arch@freebsd.org Subject: Re: kernel features MIB Message-ID: <477A1D16.2090605@FreeBSD.org> In-Reply-To: <20080101033620.4050569c@Karsten.Behrmanns.Kasten> References: <200712271704.44796.jhb@FreeBSD.org> <4774DBB2.5060707@FreeBSD.org> <20080101033620.4050569c@Karsten.Behrmanns.Kasten>
index | next in thread | previous in thread | raw e-mail
Karsten Behrmann wrote: > On Fri, 28 Dec 2007 12:19:14 +0100, Kris Kennaway wrote: >> John Baldwin wrote: >>> One of the things we have at work is a kern.features sysctl MIB that contains >>> nodes to indicate if a named feature is present. For example, on i386 we >>> have kern.features.pae and we auto enable -DPAE for kernel modules if the >>> currently running kernel is using PAE using that sysctl. >>> [...] >>> Any objections to the idea? >> I have wanted something like this for a long time. In ports land they >> often need to know this kind of thing, e.g. is compat4x support enabled >> in the kernel, etc. > > Hmm. But will everyone be running a kernel and system that the stuff they > build will later run on? (when upgrading, or when building > kernel and tools to be installed via NFS and pals) > > Mind, it could be a good heuristic for the common cases, and directly > useful for some libraries, but I'm thinking that we may need some easily- > accessible override knobs. I could be wrong, though. It would just be used to display informational messages about the need to recompile the kernel, etc. Krishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?477A1D16.2090605>