Even though I compiled 2.2.0-final with kmod, the system
still running kerneld. This is strange because
seems to take pains to not run kerneld if kmod is supported:
if [ -x /sbin/kerneld -a -n "$USEMODULES" ]; then
if [ -f /proc/sys/kernel/modprobe ]; then
# /proc/sys/kernel/modprobe indicates built-in kmod
echo "/sbin/modprobe" > /proc/sys/kernel/modprobe
(BTW, note the ugly use of -x /sbin/kerneld to detect
whether or not
the module package is installed, without which kmod can't be
anyway. I notice that the rc.sysinit script in the beta
a little better on this point.)
What was strange was that kerneld was still running on my
I traced this down to S01kerneld symlinks in the rc.d/rc*.d
directories pointing to a kerneld script in
kerneld script is owned by modutils.
So, now that kerneld is appropriately started by rc.sysinit,
kerneld script & symlinks should be removed from the
This bug exists in 5.2. I checked the scripts in the beta
the same situation appears to occur, so it looks like it's
also a beta
The startup script for kerneld that comes with modutils
is the same as in 5.2; if the user requests that
kerneld be started (via ntsysv/chkconfig), it will be.
It can be changed so it defaults to off, though.
fixed so kerneld isn't started by default in modutils-2.1.121-5,
although any old settings will still get honored.
actually, the initscript is now toast, since initscripts takes
care of kerneld.
initscript put back in, since people might want it for module
unloading. (I should stop talking to myself.)