On 08/09/12 08:42, michael@actrix.gen.nz wrote:
I too would like to know the official/safe way to switch an upgraded system from grub to grub2.
1) Will Yast2 just get it right?
2) In the event that something goes wrong, what's the best procedure for recovering from a broken opensuse grub2 install?
I'm fairly clear on how to setup and fix grub1, but would like to switch to grub2 to future-proof my setup.
Dunno if this will help, but here's what I did re Grub2 and oS 12.2 Aim was a clean install in new partitions while keeping oS 12.1 (and other installations) intact. I've normally kept at least two successive versions of openSUSE operational on this machine, each with its own /boot partition, as well as a Vista installation. In this case Grub legacy (from oS 12.1) was was installed to the MBR, and the other systems were chainloaded accordingly. I'd actually experimented with a pre-release drop of oS 12.2 with its Grub2 installed into the 12.2 /boot partition, and I had to change some entries the 12.1 Grub legacy menu.lst to point to core.img in the new 12.2 Grub2 /boot partition. This was the wisdom of the time, and it worked. So, expecting to have to do the same thing, for 12.2 final I left menu.lst like that. Wrong. All I'd done was outsmart myself (or perhaps the devs had outsmarted me). Indeed in 12.2 there is no core.img - or none that I could find. Instead, with 12.1's Grub legacy retained in the MBR and Grub2 now in 12.2's /boot partition, the old familiar and standard chainloader entries in menu.lst work fine, from which setup 12.2 boots smoothly (and runs very well). (We'll cross the bridge on how to make Grub2 the principal bootloader, when we get to it, but we're not quite there yet.) -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org