svn commit: r192535 - head/sys/kern

[Poul-Henning Kamp]

In message <20090521.101537.864824728.imp at bsdimp.com>, "M. Warner Losh" writes:

>Right now, the devctl_notify() is what gets it into devd.  However,
>I'd always viewed devd as having multiple event sources and not just
>from the /dev/devctl device.

Correct, but kqueuing /dev is not nearly as expressiv as devctl,
where the protocol has space where the device driver could pass
useful information to devd(8).

For instance, I find the regexp matching of ethernet drivers very,
very silly: the device driver should just tell devd(8) that it is
an ethernet, so that we don't have this non-documented registry of
device driver names.

Poul-Henning

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.