kmod: failed to exec /sbin/modprobe -s -k <modulename>
The system is designed such that during boot an initial ramdrive is loaded and
never exited... much like installer floppies, etc. If the failed modprobe
command is executed from the command line, it works fine.
The system uses a BusyBox init, full bash shell and the modprobe version is
2.4.18.
-- Joshua Jackson jjackson@vortech.net http://www.coyotelinux.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/