Re: FC4_64 : Grub Is not Working on Dual boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I don't think that this would be something that is only particular to the
> 64bit kernel. Today I installed from scratch on one machine with a single
> 80GB SATA drive:
> 
> W*ndows XP Profesional
> Fedora Core3
> Fedora Core4t3
> 
> Drive is now partitioned as follows:
> 
> /dev/sda1			NTFS		20480
> /dev/sda2	/boot		ext3		102
> /dev/sda3	VolGroup00	LVM PV	20379
>  VolGroup00
> 	LogVol00	/	ext3		18368
> 	LogVol01		swap		1952
> /dev/sda4			Extended	35354
> /dev/sda5	/boot		ext3		102
> /dev/sda6	VolGroup01	LVM PV	20379
>  VolGroup01
> 	LogVol00	/	ext3		18368
> 	LogVol01		swap		1952
> 
> Remaining 15GB are unclaimed at the moment(will use for other distros). My
> /etc/grub.conf is as follows:
> 
> # 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 (hd0,4)
> #          kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00
> #          initrd /initrd-version.img
> #boot=/dev/sda
> default=0
> timeout=5
> splashimage=(hd0,4)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora Core4 (2.6.11-1.1286_FC4smp)
> 	root (hd0,4)
> 	kernel /vmlinuz-2.6.11-1.1286_FC4smp ro
> root=/dev/VolGroup01/LogVol00 rhgb quiet
> 	initrd /initrd-2.6.11-1.1286_FC4smp.img
> title Fedora Core4-up (2.6.11-1.1286_FC4)
> 	root (hd0,4)
> 	kernel /vmlinuz-2.6.11-1.1286_FC4 ro root=/dev/VolGroup01/LogVol00
> rhgb quiet
> 	initrd /initrd-2.6.11-1.1286_FC4.img
> title Fedora Core3 (2.6.9-1.667smp)
>         root (hd0,1)
>         kernel /vmlinuz-2.6.9-1.667smp ro root=/dev/VolGroup00/LogVol00 rhgb
> quiet
>         initrd /initrd-2.6.9-1.667smp.img
> title Fedora Core3-up (2.6.9-1.667)
>         root (hd0,1)
>         kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb
> quiet
>         initrd /initrd-2.6.9-1.667.img
> title Windows XP Profesional
>         rootnoverify (hd0,0)
>         chainloader +1
> 
>  System boots just fine to every O/S, the only issue I have is who is
> controlling Grub? From the way it looks I will have to manually modify
> grub.conf with each kernel update on both releases, as I had to do this
> after installing FC4t3(luckily I copied FC3's grub.conf to floppy before
> installing FC4t3). If anyone has a better answer please let me know.
> 
> Thanx,
> Don
I don't see how you comments above were attached to the precious posts
since this is on a different topic. But when you install a new kernel
through yum for example the grub.conf is automatically modified to
include the new kernel as the default kernel of the next boot.
=======================================================================
You can always tell luck from ability by its duration.
-------------------------------------------
Aaron Konstam
Computer Science
Trinity University
telephone: (210)-999-7484


[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]