> So it looks like its ok. Do file the kmod: failed to exec report in
> https://bugzilla.redhat.com/bugzilla however. Regardless of it not being
> a problem in your case it does want fixing
It appears that recent RH build initrd files w/o all of the stuff in
modules.conf. Perhaps only the first SCSI adaptor, perhaps just ignoring
the ones which don't match the build hardware. I suspect the latter, since
even using --with= in a manual mkinitrd failed (silently) to include the
modules. I can't tell you how much that sucks if you build kernels for
multiple machines on a compile server.
Also, I installed 2.4.18-18.8.0 and it put a bunch of overlong label=
statements in lilo.conf, then ran lilo and didn't check the status. Since
it had deleted the old kernel that left a totally unbootable system. Guess
RH really likes grub and only tests upgrades and such with that.
I will report this later tonight when I'm willing to take the time to
prepare a proper bug report.
-- bill davidsen <firstname.lastname@example.org> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/