With Gnome2, in the past two months, somethiing has changed. Here is what I have as a config and what I had and what happens now.
Three hard disks, hda with two partitions W7 for 256g and partition 2 for storing files between Linux and Windows.
hda2 has Fedora 17, Ubuntu 2.4lts, Mint 14
Hda3 has Debian Squeeze.
My boot drive is hda2.
Now, what happens is this, The last operating system installed is the one whose grub.cfg takes control.
Suppose it is Debian
Then when I boot the system, the Debian Grub.cfg gives me the menu, and I select the system I want to boot.
That is the way it worked. prior to recent new software distributions.
Here is what happened..
This weekend, I cleaned out Mint13, and Debian (I do clean installations to eliminate stuff I installed, and no longer wan. From Fedora, using gparted, I delete the files associated with a distribution and leave the space available.).
Mint13 was first. Afer it;s installation Its grub.cfg did not show Fedora17. Wow, what happened. It worked with Mint13.
It is Mint14's Grub.cfg that is active because the mbr points it. (Mint Installer gives no option to not install to mbr)
When I looked, everything appears ok. So I said, I will install the Debian 6.6 following the process I mentioned, and as before it should show all operating systems -- right?
Well, the grub-mkconfig of Debian omits Fedora and Mint13.
Aha, I said, I think there is Grub2 problem.
To fix things up. I manually constructed a grub.cfg and when it worked with all the correct versions of Fedora, Ubuntu, Mint and Debian in the ilst, I backed it up and sat down to think of writing this long story
Can anyone help me so that with Fedora 18, coming in a few weeks, I will not have this problem again?
My next posting is an idea I want to toss out for grub3.
Three hard disks, hda with two partitions W7 for 256g and partition 2 for storing files between Linux and Windows.
hda2 has Fedora 17, Ubuntu 2.4lts, Mint 14
Hda3 has Debian Squeeze.
My boot drive is hda2.
Now, what happens is this, The last operating system installed is the one whose grub.cfg takes control.
Suppose it is Debian
Then when I boot the system, the Debian Grub.cfg gives me the menu, and I select the system I want to boot.
That is the way it worked. prior to recent new software distributions.
Here is what happened..
This weekend, I cleaned out Mint13, and Debian (I do clean installations to eliminate stuff I installed, and no longer wan. From Fedora, using gparted, I delete the files associated with a distribution and leave the space available.).
Mint13 was first. Afer it;s installation Its grub.cfg did not show Fedora17. Wow, what happened. It worked with Mint13.
It is Mint14's Grub.cfg that is active because the mbr points it. (Mint Installer gives no option to not install to mbr)
When I looked, everything appears ok. So I said, I will install the Debian 6.6 following the process I mentioned, and as before it should show all operating systems -- right?
Well, the grub-mkconfig of Debian omits Fedora and Mint13.
Aha, I said, I think there is Grub2 problem.
To fix things up. I manually constructed a grub.cfg and when it worked with all the correct versions of Fedora, Ubuntu, Mint and Debian in the ilst, I backed it up and sat down to think of writing this long story
Can anyone help me so that with Fedora 18, coming in a few weeks, I will not have this problem again?
My next posting is an idea I want to toss out for grub3.