-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-04-01 at 15:38 +0100, ne... wrote:
it should pick up the Windows installation automagically and add it to grub. The grub for oS11.1 should be installed in the disk's MBR as Carlos said.
Hum... I forgot about Windows. When there is a windows install involved, it is safer to have a "generic boot code" in the MBR, which is what windows installs. It is safer to repair, even with windows tools. The trick is: - have (or leave) generic code in the MBR - mark the Linux partition as bootable with almost any partitioner. Only one partition can be marked, and has to be a primary. - have each Linux install their boot code in their respective root partition. When the system is booted, the generic mbr code looks up on the partition table for which partition is marked as bootable, and boots that one. This partition will have grub there, so grub will run, and will ask what to boot, Linux or windows. Now, suppose a windows tool "repairs" the system, marking the windows partition as bootable. "My Linux is lost!". Calm... just use a windows partitioner tool to mark again the partition where Linux is, and you are back on business. However, if you had grub on the mbr, you have to use a Linux repair disk to reinstall grub, which is more complicated: you need to issue some cryptic grub commands >:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknTg4IACgkQtTMYHG2NR9VAvgCfTi1rzCzflUHm7706KUl8uwJN bfYAn2g1uRmaIQVsgBxu9p1+NEJsBTXx =SgDJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org