yea, i already thaught about such a parameter too, but mkinitrd -h doesn't show one and man isn't working in rescue mode :-/ anyone outta there with a working system who can check for this parameter for me? thx Quoting "Gordon R. Keehn" <gordonkeehn@xxxxxxxxxxx>: > red_alert@xxxxxxxxxxxxxxxxx wrote: > > >hi > > > >i've lost my initrd file (the only one that existed)...now i can't boot, > because > >it's missing. i've tried to create a new with the CD (linux rescue), but > that > >doesn't work, because mkinitrd doesnt find /lib/modules/<kernel-version> > >because it's mounted as /mnt/sysimage/lib/modules/<kernel-version>. i know, > i > >shoudl chroot /mnt/sysimage, but this doesn't work (i think because the cd > is > >fedora core 1 and the system is updated to the latest development > packages). > > > >any ideas how i could create the needed initrd-file? > > > >regards > >red_alert > > > >ps. i can't burn the latest CDs, because i've no cd burner available atm :( > > > > > > > > > I can't verify this immediately as my Linux box is 12 miles away in > my home, but I recall that mkinitrd accepts a parameter identifying the > assumed root of the file system. Try "mkinitrd -h" and set > /mnt/sysimage as the assumed root. > Cheers, > Gordon Keehn > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
