Re: restore /boot directory
"LeRoy M. Dorman" <[email protected]>
| Newsgroups | gmane.linux.redhat.release.shrike |
|---|---|
| Message-ID | <[email protected]> |
Actually it was /dev/sda1. I was typing from my notes, since there was nothing to cut-and-paste from. I had initially set up a partition (on an ide disk) to use as a "boot controller" but I outsmarted myself and blitzed /boot on the Linux disk. I had labeled that partition /boot, totally lacking originality. After my shattered nerves heal I may try to do the separate partition thing again, but not now. BTW, What is the future of shrike? Will it be a Plan 9 thing? What fraction of folks are moving to Fedora or the Enterprise thing. Is the enterprise version really more stable (whatever that means)? LeRoy Steven J. Yellin wrote: > I think you can use those lines as the basis for a revived >/boot/grub/grub.conf. You'll also need a title line, as in > >title RedHat Linux (2.4.20-31.9) > root (hd0,0) > kernel /boot/vmlinuz root=/dev/sda > initrd /boot/initrd-2.4.20-31.9.img > > > Is the / mountpoint really on /dev/sda? It's as if you set up a file >system on /dev/sda without partitioning it. I don't see anything wrong >with that, but it's unusual. > > >Steven Yellin > >On Sun, 24 Oct 2004, LeRoy M. Dorman wrote: > > > >>Thanks to Steven J. Yellin and Brian Brunner's advice, I now can get my >>machine >>to boot into grub, where I execute >>root (hd0,0) >>kernel /boot/vmlinuz root=/dev/sda >>initrd /boot/initrd-2.4.20-31.9.img >>boot >> >>So can I use these as the basis for a revived /boot/grub/grub.conf? >>That is just copy them into the file? >> >>Or is there a way to get anaconda to regenerate the grub.conf file without >>re-installing the system. >> >>THanks, >>lmd >> >> >>-- >>Shrike-list mailing list >>[email protected] >>https://www.redhat.com/mailman/listinfo/shrike-list >> >> >> > > > -- Shrike-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/shrike-list