Date: Tue, 18 Dec 2001 01:32:05 -0700 From: Warner Losh <imp@harmony.village.org> To: Paul Richards <paul@freebsd-services.com> Cc: Mike Smith <msmith@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: Anybody working on devd? Message-ID: <200112180832.fBI8W5M83297@harmony.village.org> In-Reply-To: Your message of "Sat, 15 Dec 2001 03:14:55 GMT." <12520000.1008386095@lobster.originative.co.uk> References: <12520000.1008386095@lobster.originative.co.uk> <200111272301.fARN1nj04294@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <12520000.1008386095@lobster.originative.co.uk> Paul Richards writes: : If eventd is a generic handler for all kernel events then all sorts of : things can be hooked into it. What would be needed is an api call in the : kernel to signal an event and then any part of the kernel would have a : mechanism to cause an userland action to occur. I fear this will be too general a daemon to every be written. There are too many modules that will goo up the works. But I suppose that someone will prove me wrong... : I think focussing the design around device type events would be a big : mistake in the long run. I agree, that's why the lowest layers of what we've been working on aren't device centric. At least the /dev/event that I've been working on.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112180832.fBI8W5M83297>