That grep for sk98lin didn't turn up anything, bathory.
The installation shell script for the driver compiled several programs extracted from the driver tar file then linked them as module sk98lin.o. I found it using
Code:
find / -type f -name sk98lin.o -print
here
/lib/modules/2.4.31/kernel/drivers/net/sk98lin/sk98lin.o
And as I mentioned before, /etc/modprobe.conf and /etc/modules.conf are empty files, but
Code:
modprobe -c | grep -i eth
finds
alias eth0 off
I just don't know where all the configuration settings for modprobe come from if not from /etc/modprobe.conf.
Anyway, then I found this logic in /etc/rc.d/rc.inet1
Code:
# If the interface isn't in the kernel yet (but there's an alias for it in
# modules.conf), then it should be loaded first:
if ! grep `echo ${1}: | cut -f 1 -d :`: /proc/net/dev 1> /dev/null ; then # no interface yet
if /sbin/modprobe -c | grep -w "alias ${1}" | grep -vw "alias ${1} off" > /dev/null ; then
echo "/etc/rc.d/rc.inet1: /sbin/modprobe ${1}" | $LOGGER
/sbin/modprobe ${1}
fi
I don't entirely understand that, but I'm wondering if this would result in a modprobe eth0 or something like that if the output from the 'modprobe -c' finds the 'alias eth0 off'?
Hey, I still totally clueless, but at least I'm learning a little bit about the initialization process.
