I looked into the corresponding script (/etc/init.d/modutils),
the culprit is probably
echo -n $module -
MODTOLOAD=`find / -name $module.o |sort |sed -n 1p`
if [ $MODTOLOAD = ] ;then
module=` echo $module | cut -c-8`
MODTOLOAD=`find / -name
Alex
At 15:11 29.12.2003 +0100, Alex Rhomberg wrote:
...
It starts its search at /, which is probably fine to detect all
sorts of modules in the directory tree.
This obviously is the part that produces the original error message.
Not looking everywhere for modules might break some setups
Hello Erich Alexm list
This part of the script comes from a time that insmod was not so flexible.
You could only insmod a modules if you gave the complete path.
The idea was that if a module has to be added which could be the case at new
setup, the modules would still be on the boot media (
