T> However, even if you use this type of approach for /devfs, it's still a
T> cumbersome interface. Consider that with a /proc/devices-style
T> approach, a one or two read()'s will allow you to get all of the
T> information you need.
T> With a /devfs approach, you will still need to readdir() through all of
T> /devfs, figure out what changed, and then stat the device to see what
T> has differed.
The current devfs patches have a special device file (/dev/.devfsd)
for devfsd to listen to for changes. It doesn't have to scan the
/dev directory for _that_ reason. At least that's what the docs say--
I haven't looked at the code.
-- Scott Henry <scotth@sgi.com> / Help! My disclaimer is missing! IRIX MTS, / GIGO *really* means: Garbage in, Gospel Out Silicon Graphics, Inc / http://reality.sgi.com/scotth/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/