> I'm referring to only packaging meaning having within the same lrp. > Additionally, the package installer should load all modules that are > tarred within the package as they are deemed necessary for the > utilities to work. I'm not suggesting that the module be compiled or > integrated. Can we do away with manual steps when it is obviously > needed. That is all. Sorry if my earlier posts have conveyed > otherwise. It would probably be enough if a lrp package could have a "init" script on load that did whatever the module wanted setting on load - that way a module could insmod anything it wanted to. The only real danger here would be when modified packages were written away - does the .o get written twice (wasting space) or not at all (leaving you with a broken system). For that matter - does a .o need to be in /lib/modules once it is loaded? could we get away with copying it from module-specific space to /lib/modules, loading it then deleting it?
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
