Comment 2 for bug 924406

Fair point, Steve!

Let me explain.

My situation is a bit complex and I am trying to find a way out, which I could not so far cuz I have hit problems all the time.

Since I was not able to chainload from grub-legacy (openSUSE 0.97 version) to grub2 (Kubuntu 11.10) this is a reason why I downgraded to grub-legacy on Kubuntu 11.10. But I hit a problem too, this one.

The other reason why I downgraded to grub-legacy is that with grub2 I was not able to boot a cloned disk, as the clone becomes unbootable (grub2's menu does not even display).
Then I downgraded to grub-legacy, thinking it should work as it always had with openSUSE distro, so I thought it would be the same with Kubuntu.

But I get the same problem as grub2 (cloned disk unbootable), so I opened a ticket that you can refer here #923070 https://bugs.launchpad.net/ubuntu/+source/grub/+bug/923070

So I am sort of stuck at the moment. I agree chainload is not a high priority for me, but it makes my testing a lot easier as I don't need to change the menu.lst many times when needed.
I agree grub-legacy will not be supported at some point in time, I am willing to use grub2, but then I had the clone problem and grub-legacy (part of Kubuntu 11.10) has the same problem as well, hence the above ticket 923070 opened.

If grub2 could have 923070 fixed, I would use it.

I am not sure what to do at the moment.