Re: kmod/kerneld

CD323 (cider@eidolon.speakeasy.org)
Wed, 11 Mar 1998 14:02:29 -0800 (PST)


>
> What do I do with /sbin/kerneld.
> At present, my rc.S script tests for its presence, and does things if it
> is present.
> My backup boot is 2.0.33 via dos and lodlin, so I can't just get rid of
> it.
> Also, where in the start up scripts should the echos in kmod.txt go?
> If these scripts need to test the kernel version, how do I do that?
> --
> Garst

hi garst -

currently, i have a system with both 2.0.33 and 2.1.90-pre, and this is
how i work around this problem; in any version-critical section of an rc
script, i use:

if [ `uname -r` == "2.0.33" ]
then
/sbin/kerneld ....
etc
fi

the echo's in kmod.txt are not required; you only need to add
these to rc scripts if you want to change the defaults
(/sbin/modprobe for /proc/sys/kernel/modprobe, and "60" for
/proc/sys/kernel/kmod_unload_delay). if you *do* want to change these
defaults on a global basis, i'd put the echo's in your rc scripts as
early as possible. thanks!

-cyrus durgin.
cider@muppetlabs.com.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu