Jerry Kreps wrote:
sure thing. sorry i did not mention this obvious detail:
%> modprobe --version modprobe version 2.4.0
I also downloaded, compiled and installed modutils-2.4. I don't understand how modutils is supposed to work, but it looks messed up to me. jerry@JLKreps:~ > /sbin/modprobe -c # Generated by modprobe -c (2.4.0) path[boot]=/lib/modules/boot <--- doesn't exist path[toplevel]=/lib/modules/2.4.0 <--- correct path[toplevel]=/lib/modules/2.4 <--- doesn't exist path[kernel]=/lib/modules/kernel <-- s/b /lib/modules/2.4.0/kernel ??? path[fs]=/lib/modules/fs <-- s/b /lib/modules/2.4.0/fs ??? path[net]=/lib/modules/net <-- s/b /lib/modules/2.4.0/net ??? path[scsi]=/lib/modules/scsi --- same for the rest. ???
Don't worry about it, my 2.4.0 modprobe does this as well, as does my 2.2.2-pre6 and 2.3.11 modprobes. I don't understand it either, but I think it's meant to be like that. Presumably in case someone doesn't keep their modules in the 'standard' place. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\