GRUB question 2256
On Sun, 20 Aug 2006 21:27:31 UTC Robert Hull
If I may jump into this thread with what may be similar to the original problem:
On a new laptop I am experimenting with different Linux distros. The drive contains parbreastions for the original Windows XP, OS-2, and several parbreastions capable of holding usable installations of the various Linux distributions. I use the IBM Boot Manager to select between the various options. So far, so good but...
On Sun, 30 Jul 2006, in the Usenet newsgroup comp.os.linux.misc, in article I'm not exactly sure why - the difference between a 486SX and 486DX was that the SX lacks the math-coprocessor...
When installing Suse 10.1, it insists on using GRUB and over-writes the MBR. That wouldn't be necessarily bane, but GRUB also fails to pick up or erroneously picks up the other boot options, especially the Boot Manager. It shows up as an option on the GRUB menu but fails when trying to chain to it. I can hack the problem as a workaround but I would like to be able to make it play nice.
To get back to usability, I have to re-write the MBR and set the BM parbreastion as the active primary. Once I do that, I can access all the desired boot targets, including the Suse installation that bit me in the first place. How do I configure GRUB to leave the MBR alone?
-- Will Honea