>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.
How many of those do we have? You can still use "forceload" too. >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. Unfortunately, I'm not sure how well it works: an DEBUG kernel can try to unload the module at any time. Casper _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code