Depending on your hardware, you normally have two options: a. leave your MBR as it is on sda, and add in a boot entry in your /boot/grub/menu.lst to boot up your 10.2. b. from BIOS - boot tab, select which drive to boot up. In this instance, you will have to write the MBR on sdb.
Hope that helps. -----Original Message----- From: Brian S. Schang [mailto:[EMAIL PROTECTED] Sent: 28 January 2007 12:12 To: [email protected] Subject: [opensuse] Install SuSE 102 along side 10.1 - What happens? Hello: I'm writing in an attempt to understand how the SuSE installer will accommodate my existing installation. Background: (1) I have SuSE 10.1 successfully installed. (2) I have three hard drives connected: - /dev/sda : the "main" hard drive with SuSE 10.1 and swap - /dev/sdb : a new drive that is blank - /dev/sdc : data (3) I want to leave my SuSE 10.1 intact (untouched) on sda and want to install SuSE 10.2 on sdb. OK, the easy part. I can boot from the SuSE 10.2 DVD and install on sdb. This should be a piece of cake. Presumably an install of SuSE 10.2 on sdb will not touch sda or sdc. Now, the question -- what happens to the boot sequence?? For my setup today (if I understand this properly), I'll boot from sda. Upon boot the master boot record (MBR) will be read from sda and will launch grub on /dev/sda2/boot. The menu.lst file will define the "presets" and default that I have. What happens when I install SuSE 10.2 on sdb? - Will the machine still load the MBR from sda? [I think this is a hardware/BIOS issue?] - Will the machine still load grub from /dev/sda2/boot? - What will happen to my existing menu.lst file? Will it be overwritten (to only contain a 10.2 option) or will it be modified/appended (10.1 and 10.2 options)? The bottom line is that I don't much care, but I do want the option to boot into my working/existing 10.1 versus my experimental 10.2 setup. Will the install program handle this for me? Will I need to make some manual configuration changes after the SuSE 10.2 install? Thank you. Brian Schang -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
