On Jun 23, 2004 at 14:20, Jeff Ratliff in a soothing rage wrote: >On Wed, Jun 23, 2004 at 01:51:53PM -0400, Matt Morgan wrote: >> Honestly, if it were me, I would just run the install, tell it to >> install to that second disk, and let the installer update the MBR & grub >> for me. It'll see the other OS on the other drive and try to handle it >> for you, automatically. I know you're getting advice to do it other >> ways, but I bet just letting the installer handle it will work. >> >> Once I had a problem and had to go fix grub myself. That was a while >> ago, with a RH9 + Windows 98 dual-boot system. It wasn't the hardest >> thing to do, even though I had never tried it before. If your current >> install on disk1 is doing something really important, I would recommend >> reading about grub config first, so you know what to expect, but there's >> a very good chance the installer will just get it right. >> >I recommended installing no bootloader more as a failsafe. You're >right that the installer will most likely get it right. I did the >manual configuration of GRUB when I installed FC2 on a system with >WinXP, because I didn't want to run into the dual boot bug. At the >time I needed my Windows system. > >I guess if you let the installer update GRUB and it doesn't work, >the worst that can happen is you'll have to edit /boot/grub.conf >anyway. It's worth a shot if this isn't a critical system. I kinda recall the OP saying that they need their current system and can play with the new install. I would go the route you suggest, install new FC2 with no bootloader. The OP then has to remember the partition his boot and root is on and then add a stanza to the current grub.conf. N.Emile... -- Registered Linux User # 125653 (http://counter.li.org) Switch to: http://www.speakeasy.net/refer/190653 The good (I am convinced, for one) Is but the bad one leaves undone. Once your reputation's done You can live a life of fun. -- Wilhelm Busch 14:58:11 up 12 days, 8:31, 5 users, load average: 0.00, 0.00, 0.00
