Hi > As you stated, I would really like to see a fix in itables for this.
Check very latest iptables - the number of modprobes is now reduced to just 1 in most cases (regardless of whether that 1 module is already in the kernel). Also on anything before 2.6.39 you might get a second modprobe for ipset However, whilst this is a bit of a cover-up, it doesn't solve the root issue that calling modprobe is very slow under busybox (regardless of whether it does something). I still leave a small amount of my kernel as modules because it has a significant speedup for boot time in my case, the odd modprobe here and there is now bearable, but it's eating perhaps 1/2 to 1 second of my boot. This is bearable, but equally it would be reasonably high up the list of things to fix if faster boot times became a higher priority. I do get that kernel modules are generally less used for embedded devices, but I think some of the replies are missing the point that several bits of software still call modprobe even needlessly and this can make things very slow if you use the busybox modprobe? (ie even without having any modules in your system...) Thanks Ed W _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
