by You might recall that I couldn't get 2.1.99 to work, but I did get 2.1.98
to run - and I noticed that the statement which I put into my rc.d/rc.S
file to enable either kmod or kerneld to run depending on the kernel in
use as follows:
KERNELD=no
if [ ! -f /proc/sys/kernel/modprobe -a -x /sbin/kerneld ]; then
/sbin/kerneld
KERNELD=YES
fi
That above statement DOES not work! It still loads /sbin/kernel in 2.1.98!
On further investigation; I figured out that the kernel hadn't yet
initialised the /proc filesystem by the time it encountered that
statement, and hence it didn't know that /proc/sys/kernel/modprobe
existed! Trouble is, it needs kerneld or kmod to mount the /proc
filesystem. (according to my /etc/fstab, that is)
So, I came up with a hack that seems to work; but might break, should the
boot filesystem be corrupt or if uname and cut does not exist:
KERNELD=no
if [ `uname -r | cut -c1-3` = '2.0' ]; then
/sbin/kerneld
KERNELD=YES
fi
I figure this will work as long as the boot filesystem is mounted, even if
it is read-only. Pretty safe, I think. Of course, if you boot a 1.x
kernel... well.. upgrade!
What do you think, guys?
Cheers,
Alex
--
/\_/\ Legalise * now!
( o.o ) Smoke some * today!
> ^ < Peace, Love, Unity and Respect to all.
http://www.veryComputer.com/