Hello Charles, <snip>
> > IMHO, the /lib/modules/<kernel> symlink, if present, should be part of > the modules package (ie: not dynamically created), so users can point it > somewhere else if desired. > Thinking about it, maybe the easiest solution is indeed just add an user adjustable symlink in /etc/init.d/modutils. > Also, to me this whole discussion is somewhat pointless. I would > strongly argue that LEAF distributions can *NOT* be assumed to have the > full modules heirarchy (including modules.dep, etc) that you would > normally find on a full linux install. If there are programs that rely > on this structure to be present, they will need to be modified to work > with LEAF. This leaves 'large-format' LEAF systems, which may happen to > have a full modules tree, as a special case of the simpler default > system which only has /lib/modules/<handful of files>. > > I'm more interested in making the full modules directory easy to access > in a similar method to the default accessing of files in /lib/modules > than I am in trying to duplicate the full-blown modprobe functionality > of a full disto. > > -- > Charles Steinkuehler > [EMAIL PROTECTED] > > I fully agree with you about that LEAF distributions can not be assumed to have the full modules hierarchy and I myself only have a minimal set of modules available on my router. But I don't think the whole discussion is pointless, looking at the the "ip_conntrack" modularization you need the following modules available in modules.lrp (and /etc/modules, in the correct order!): ip_conntrack ip_conntrack_ftp ip_conntrack_irc iptable_nat ip_nat_ftp ip_nat_irc ipt_MASQUERADE ipt_REDIRECT ipt_conntrack ipt_helper ipt_state Modularizing all of the kernel netfilter items will make this list even longer. Also other items in the kernel are getting more dependencies, like a lot of NIC drivers now need MII and crc32 (kernel 2.4.24). It's difficult (but doable) to find the correct modules and dependencies, but it gets more and more complicated to not make mistakes with adding them in /etc/modules and keeping the correct order, even with small LEAF systems. One possible solution for this is using kmod/modprobe/depmod and let depmod create the dependency files "on-the-fly", so only for modules that are added by an user in modules.lrp. But maybe there is a better solution, or the "problem" isn't as big as I think :-) Eric Spakman ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
