I installed the modules package v2.0.0, and my machine wouldn't
boot past kerneld. It seems kerneld's behaviour on startup has
been changed (my guess is that it is waiting to write to the root fs).
Since I start kerneld from /etc/inttab (sysinit), the machine was
dead in the water.
Fix = Since I want kerneld to run before almost everything else,
I wanted to keep it as a sysinit entry. The solution was simple:
kd::sysinit:/sbin/kerneld &
Intstead of kerneld being PID 5 and freezing the machine, it ends
up as PID 10 as soon as the root fs is mounted, and before the other
fs are mounted (which need modules).
I'm sure this isn't perfect or proper, but it works for me.
-- Andrew E. Mileski mailto:aem@ott.hookup.net My home page http://www.redhat.com/~aem/ Linux Plug-and-Play Project Leader. See URL http://www.redhat.com/pnp/Red Hat Software sponsors these pages - I have no other affilitation with Red Hat Software, and I have never used any of their products.