> Do we even need a daemon running all the time? We've just changed
> module handling so that module requests simply invoke modprobe
> directly rather than using a kludgy communication method with
> kerneld. Is there something to be learned here?
Actually I've been trying to figure out if pre and post scripts from
modprobe could be used to do the device creation/destruction, then a
daemon may not be needed.
The minor number could be passed to modprobe from the kernel, since
modprobe _should_ already know the major number, but the device _names_
could be determined by a modified modprobe, perhapsby referencing another
field in conf.modules.
Richard, what are your thoughts on this? I can't think of why this
wouldn't work, but I may be missing something.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Andrew Anderson http://amelia.db.erau.edu/~andrew/
if(!(family_tree=fork())){redneck=TRUE;}
-
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