Devfs will still maintain a namespace, at least for the time
being. And it will be mounted somewhere so you can access the device
node that devfsd uses to talk to devfs. However, if you don't do
anything more with the mounted devfs, then this will save RAM since
the device nodes don't need to be created (only the devfs entries are
created).
Devfsd will support setting permissions on device nodes in devfs,
running programmes, as a minimum. Anything else can be built from
this. I may add built-in mounting and device node creation in a normal
disc-based /dev.
Note that if you have a configuration which uses devfs solely for its
role as an information service provider for devfsd, (i.e. you keep
using a disc-based /dev) then one of the things you loose is the
ability to lookup non-existent device nodes in /dev and have modules
automatically loaded by kmod.
Regards,
Richard....
-
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.altern.org/andrebalsa/doc/lkml-faq.html