Granted, accepted and think it is better. I did not think of this angle that modules may not keep pace. In some cases, due to sequence of loading, older modules might replace newer ones.
Maybe be check while loading using lsmod to see if appropriate/ required module is loaded would be preferable. Mohan -----Original Message----- From: Tom Eastep [mailto:[EMAIL PROTECTED]] Sent: 19 February 2003 08:49 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [leaf-user] Update: Short term LEAF project goals S Mohan wrote: > While I'm not that aware of various options, I think a few modules are > mandatory or have to go with some packages. E.g. ipsec.o with > ipsec(509).lrp, bridge.o with bridge.lrp, netfilter with tc.lrp etc. I > was looking at this. In addition, 90-95% of the users would use a common > combination. Dial up connections use PPP over serial ports etc. Such > popular combinations can also be packaged to gether. > I rather favor a mechanism whereby package->module dependencies can be expressed in the package. Including kernel modules in .lrp's like ppp, pppoa or shorwall (just to name one) will yield nightmarish results when we try to introduce a new kernel version. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ [EMAIL PROTECTED] ------------------------------------------------------- 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
