Date: Wed, 11 Jul 2007 13:40:46 -0400 From: Gary Palmer <gpalmer@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Rui Paulo <rpaulo@fnop.net>, Shteryana Shopova <syrinx@FreeBSD.org>, "Constantine A. Murenin" <cnst@FreeBSD.org>, Robert Watson <rwatson@FreeBSD.org>, freebsd-arch@FreeBSD.org Subject: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD Message-ID: <20070711174046.GB91325@in-addr.com> In-Reply-To: <56223.1184152780@critter.freebsd.dk> References: <20070711115332.I67691@fledge.watson.org> <56223.1184152780@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 11, 2007 at 11:19:40AM +0000, Poul-Henning Kamp wrote: > In message <20070711115332.I67691@fledge.watson.org>, Robert Watson writes: > >On Wed, 11 Jul 2007, Poul-Henning Kamp wrote: > > > >So it sounds like it would be useful for Constantine to help flesh out a few > >pieces of understanding: > > Add to this: > > - Is it possible to correctly identify the hardware platform, so that we know > where to find the sensors and know what they measure, without bloating the > kernel with a lot of tables. Why would the tables have to be in the kernel? Even if they are in the kernel, what is stopping something loading the correct table on boot based on some userland tool run out of /etc/rc.d? I'm also not sure what the benefit to having the tables in the kernel would be. A userland tool which watches the data from the sensors (however they are presented, whether it is a sysctl MIB or data passed via RFC 1149) and acts appropriately would appear to be a more flexible solution (ala devd)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070711174046.GB91325>