cjlesh wrote:
Hey all:
OK, I'm not exactly sure how to describe the problem I'm
having, but I had FC3 installed on my first partition, and I had a
swap partition, and some free space.
So I installed FC4T1 into the free space, into a partition I created
during the installl process. I didn't install grub, but added
FC4T1 to the grub.conf from my FC3 install.
This doesn't work, and somehow my FC4T1 install is picking up
information from my FC3 install, like the user I created in FC3 is
available in FC4.
I have no idea what I'm doing here, but it seems like maybe
there is a problem with the whole partition label scheme?
Could anyone point me towards some info on how to dual boot fedora
and fedora?
-cjlesh
I'm not sure how you created your entries for FC4T1 without installing
grub somewhere and copying the correct entry from the FC4T1
/etc/grub.conf file.
I normally install grub to the boot record of the partition that I'm
installing the new system to and then copy the entry from the new
system's grub.conf file into my master grub.conf file for the system I
have controlling the MBR. Others will tell you different ways to do
this, like using chain loading to secondary grub installs.
The partition label can be replaced with an actual reference to the
device. Below is part of my grub.conf. Note that the first three
systems refer to the boot partition with a label, but the next two refer
to the boot partion as /dev/hdxx. Both will work. You need to know the
particular label for the partition to use the label, whereas you only
need to know the device name for the other technique.
=============
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/hda1
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora Core 3 (2.6.10-1.770_FC3)
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-1.770_FC3 ro root=LABEL=/ rhgb quiet
acpi=off ide0=ata66 idebus=66
initrd /boot/initrd-2.6.10-1.770_FC3.img
title Fedora Core 4T1 (2.6.11-1.1185_FC4)
root (hd0,6)
kernel /boot/vmlinuz-2.6.11-1.1185_FC4 ro root=LABEL=/1234 rhgb quiet
initrd /boot/initrd-2.6.11-1.1185_FC4.img
title Fedora Core 2 -> 3 (2.6.10-1.770_FC3)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-1.770_FC3 ro root=LABEL=/123 ide0=ata66
idebus=66
initrd /boot/initrd-2.6.10-1.770_FC3.img
title Suse Linux 9.2
kernel (hd0,1)/boot/vmlinuz root=/dev/hde2 vga=0x31a selinux=0
splash=silent resume=/dev/hde9 desktop elevator=as showopts
initrd (hd0,1)/boot/initrd
title Ubuntu, kernel 2.6.8.1-5-686
root (hd0,7)
kernel /boot/vmlinuz-2.6.8.1-5-686 root=/dev/hda8 ro quiet splash
initrd /boot/initrd.img-2.6.8.1-5-686
title Scientific Linux SL Release 3.0.3 (SL) (2.4.21-27.0.2.EL)
root (hd0,9)
kernel /boot/vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/12 hdc=ide-scsi
hdd=ide-scsi
initrd /boot/initrd-2.4.21-27.0.2.EL.img
==============
Note: some of the lines above have been wordwrapped in this message.
Hope this helps.
Gerry