To Whomever:
a new-to-grub/linux question:
I just installed rh7.3 on one drive, and rh9.0 on another. win2k is
on a third hd.
Among other perhaps notable happenings, during both linux installs, grub
did not see more than the win2k disk and the disk currently being
formatted.
In the end, I don't know if i should edit the grub.conf to resemble its
rh7.3 origins, or i should make the addition of the hd2 titles and actions
resemble what is in fstab on hd2.
Before installing rh7.3, trying to use grub-install i managed to cause
kernel panic and wound up having to re-install rh9. I am trying to figure
out what to do to avoid the same outcome now as I modify the
/etc/grub.conf on the rh7.3 hd.
That is, instead of mentioning devices, hd2 uses LABELS (since both fstab
and grub seem similar I was not inclined to change anything there -- but i
don't know if i should reflect that difference in the grub.conf i need to
ultimately create.
Note: The only linux disk I can access is the rh7.3 disk. The attachment
reflects the rh7.3 method...but i really think the reference to hd2 should
be re-vised to the rh9 version below...
rh9 version for hd2
title rh9DB (2.4.20-8smp)
root (hd2,0)
kernel vmlinuz-2.4.20-8smp ro root=LABEL=/1 hda=ide-scsi
initrd /initrd-2.4.20-8smp.img
title rh9DB (2.4.20-8)
root (hd2,0)
kernel vmlinuz-2.4.20-8 ro root=LABEL=/1 hda=ide-scsi
initrd /initrd-2.4.20-8.img
rh7.3 version of hd2
title rh9DB (2.4.20-8smp)
root (hd2,0)
kernel vmlinuz-2.4.20-8smp ro root=/dev/sdc2 hda=ide-scsi
initrd /initrd-2.4.20-8smp.img
title rh9DB (2.4.20-8)
root (hd2,0)
kernel vmlinuz-2.4.20-8 ro root=/dev/sdc2 hda=ide-scsi
initrd /initrd-2.4.20-8.img
again, dunno which method to use
do i reflect the hd2 fstab, or the rh7.3 grub overwrite method by
mentioning device names?
I am about to run grub-install hd0 (hd0 -> win2K, with the mbr), but am
worried.
if anyone might advise me, I would really appreciate it...
PS I assume, once i make the corrections in the /etc/grub.conf on hd1 that
i run grub-install hd0? Thanks
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/sdb3
# initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=20
splashimage=(hd1,0)/grub/splash.xpm.gz
password --md5 $1$ö9åönrH/$HBGdCZREsZ99.YA0WMG2b1
title Red Hat Linux (2.4.18-3smp)
root (hd1,0)
kernel /vmlinuz-2.4.18-3smp ro root=/dev/sdb3 hda=ide-scsi
initrd /initrd-2.4.18-3smp.img
title Red Hat Linux-up (2.4.18-3)
root (hd1,0)
kernel /vmlinuz-2.4.18-3 ro root=/dev/sdb3 hda=ide-scsi
initrd /initrd-2.4.18-3.img
title win2K
rootnoverify (hd0,0)
chainloader +1
title Red Hat Linux (2.4.18-8smp)
root (hd2,0)
kernel /vmlinuz-2.4.20-8smp ro root=/dev/sdc2 hda=ide-scsi
initrd /initrd-2.4.20-8smp.img
title Red Hat Linux-up (2.4.20-8)
root (hd2,0)
kernel /vmlinuz-2.4.20-8 ro root=/dev/sdc2 hda=ide-scsi
initrd /initrd-2.4.20-8.img
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
