Darren J Moffat wrote:
Joerg Schilling wrote:
Alan Coopersmith <alan.coopersm...@sun.com> wrote:
Is there a public interface to load a kernel module from user space?
Looking at the modload source, it seems to use the modctl() system call
but I see no man page for that.
I thought that Solaris does not need this because drivers are loaded
automatically when the device is opened. What kind of usecase do you
have in mind?
That was going to be exactly my response as well Joerg, so like you
I'm not sure why Solaris would actually need this.
Is it because these kernel modules would be 'misc' modules with no
other kernel module depending on them and no path_to_inst entry
binding it to a hardware instance ?
Basically I think we are missing the context here.
For automaticly loaded modules, there is always something that pulls the
module into the kernel, be it a dependency from another module or
someone opening a device file. Neither of those is going to pull in a
new standalone module, so that code can be executed.
But I'm with Garrett, modload(1M) would seem to be a fine answer,
especially given that there is preexisting architecture within it for
Linux that is almost identical.
Darren
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
