According to Jeremy Wiebe: While burning my CPU.
>
>
> Hi Richard,
>
> Attached are the original rc.sysinit and the version that I am using.
> rc.sysinit.backup is the original. As to the /var/modules....that was my
> mistake, it is /lib/modules. I wasn't at my Linux box and forgot the
> path...sorry.
>
> When I was trying to figure the rc.sysinit script out, I found that it
> seemed to be getting the correct version number...2.0.36 but for some reason
> would not find the /lib/modules/2.0.36 directory for the symlink. I got
> tired of looking for it and just removed all of that stuff.
>
Well i took a closer look at the rc.sysinit of yours, i found an
iregularity, but i cant quite understand why its there, and why it works for
some and not for others, further more i dont know if its a good idea to say
do it my way but here goes.
The "if" statement;
if [ "$kernelname" = "/boot/vmlinuz" -a \
-d /lib/modules/$versioninfo -a \
$versioninfo != `uname -r` ]; then
ln -sf $versioninfo /lib/modules/preferred
fi
Is in my opinion not doing what it should because of the exclamation mark,
"!" removeing it makes the script work for me here.
What the statement says is, if kernelname is the same as /boot/vmlinuz and
the directory /lib/modules/2.0.36 exsists and is "NOT" the same as what
'uname-r' returns, then make the preferred symlink, now that cant be correct,
the exclamation mark says if the 2 are NOT the same, but they are the same,
so the desired effect cannot be obtained, removing the ! mark should make the
script create the desired symlink.
So it should work when changed to;
if [ "$kernelname" = "/boot/vmlinuz" -a \
-d /lib/modules/$versioninfo -a \
$versioninfo = `uname -r` ]; then
ln -sf $versioninfo /lib/modules/preferred
fi
I suppose i could be overlooking some point or other, or something else in
the way the distribution sets out the directorys has changed, but i cant
imagen what that would be.
--
Regards Richard.
[EMAIL PROTECTED]
Merry Xmas to all, and may all your troubles be small (ones).
