Even though I compiled 2.2.0-final with kmod, the system
startup was
still running kerneld.  This is strange because
/etc/rc.d/rc.sysinit
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
instead
	   echo "/sbin/modprobe" > /proc/sys/kernel/modprobe
       else
	   /sbin/kerneld
	   KERNELD=yes
       fi
   fi

(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
used
anyway.  I notice that the rc.sysinit script in the beta
release looks
a little better on this point.)

What was strange was that kerneld was still running on my
system.

I traced this down to S01kerneld symlinks in the rc.d/rc*.d
directories pointing to a kerneld script in
/etc/rc.d/init.d.  The
kerneld script is owned by modutils.

So, now that kerneld is appropriately started by rc.sysinit,
the
kerneld script & symlinks should be removed from the
modutils package.

This bug exists in 5.2.  I checked the scripts in the beta
release &
the same situation appears to occur, so it looks like it's
also a beta
bug.