On Fri, May 25, 2007 at 07:59:59PM +0200, Yann E. MORIN wrote: >> so in the BusyBox options i removed the 2.2 and 2.4 old module support >> and the result is that at boot time no module were loaded. >> I investigated a bit and I noticed that OpenWrt 's scripts calls insmod >> without >> a full path, like "insmod tiatm" since BusyBox's insmod scan the whole >> /lib/modules to find the right module. > >The right solution here would be to fix the OpenWRT init scripts. Did you try
Indeed. >to file in a bug there? They might not be aware of the issue either and might >be interested as well to at least know there is an issue. > >> Then I discovered that the code that scans /lib/modules is enabled only in >> 2.4 aware configs, so i've made the attached patch to fix it, but in an ugly >> way. > >Ha! You say yourself it's ugly! Hehehe ;-) Just pulling your leg! :P >> Yann E. MORIN wrote: >> > First of, we must decide wether its the job of insmod or not. Again, plain >> > insmod from module-init-tools does NOT search for modules. Do we want to >> > add >> > this feature that the original code doesn't have? I guess no. > >Guys, what's your opinions? Include such support or not? No. If you want a module loader that searches for mods, there's modprobe. _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
