This isn't correct. If you attempt to do an inode lookup for an inode
that doesn't exist yet, devfs will send the name of the file to kmod
which will then load the module.
All that is required is the right alises in /etc/modules.conf
> Now in _theory_ Devfs could intercept any query for the existance
> of a device special file to then use a daemon to automagically create
> device special files with the right permissions owner, and group,
> and then if the permissions are correct, tell kmod to load the
> module. Then if it doesn't work, you get the same behavior as now
> when a device isn't supported by the kernel. And in theory, Devfs
> could then, when the last reference to a particular device special
> file is closed, tell the user space daemon to blow away the file.
None of this is needed. With a properly configured /etc/modules.conf
it all sorts itself out.
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