Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD (was: Re: PERFORCE change 123040 for review)
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 21:43:43 +0000
A number of observations:
The main problem about hardware monitoring is the lack of a name-space.
The OpenBSD sysctl doesn't get anywhere close to providing that.
Putting stuff in the kernel is not a magic solution to that problem,
as we have seen far too many examples of, starting with the socket(2)
mistake in early BSD UNIX, and reaching a preliminary pinnacle with
the SysV IPC mechanisms.
The first task therefore, must be to design a namespace where all
the assorted pieces of software can contribute their measurements
and registrations.
Once that's designed, we can start to argue if the code should live
in the kernel, userland or in ports.
But please don't import any half-assed "Ohh, I'll just hack this in
there" non-solutions.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD
- From: Constantine A. Murenin
- Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD
- References:
- Prev by Date: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD (was: Re: PERFORCE change 123040 for review)
- Next by Date: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD
- Previous by thread: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD (was: Re: PERFORCE change 123040 for review)
- Next by thread: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD
- Index(es):
Relevant Pages
|
|
