On Fri, 7 Mar 2003, Kent Borg wrote:
> On Thu, Mar 06, 2003 at 04:28:49PM -0600, Mikkel L. Ellertson wrote:
> > Well, it apears the system boots just fine without the initial
> > ramdisk, so what I would try is commenting out the initrd lines, and
> > see if that helps.
>
> Yes, that fixes it. So what happened? Why did rpm-ing in the new
> kernel change this? Checking my previous RCS version of grub.conf
> shows I did have initrd in there. How did it become a boot-preventer,
> even for my own 2.4.19 kernel?
>
>
> Thanks,
>
> -kb
>
What is think happened is that your initrd images became corrupted for
some reasion. So the boot was hanging when trying to access them.
Because your setup doesn't require anything in the initrd to boot,
removing them was the simple fix. If you had needed to load drivers to
access the root file system, we would have had to rebuild them to get
the system booting again.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
