On Mon, Jun 7, 2010 at 14:09, Dotan Cohen wrote:
I can read two things between those lines: 1) Suse does detect and configure Grub1-based systems. 2) Assuming that Suse will one day adopt Grub2, it will detect and configure those systems.
If those two points are correct, then resolution of the bug will involve a move to Grub2. I don't see a mention of that explicitly in the related bug report.
Furthermore, Comment #5 of that bug report indicates that Suse does not detect other Grub1-based systems.
If you have a system you can experiment with, you will find that if you install 11.1 on a computer with multiple OSes you will get a Grub with all OSes in the menu. With 11.2 in the same scenario, you do not - which is why I was involved in the bug report back with 11.2 release candidates. At one point openSuSE DID detect other Grub1 based installs, and now it doesn't.
Because I support tens of users and my personal technical savviness means that their problems fall on me! A couple of minutes here and a couple of minutes there means that I get no paid work done.
I'm in the same situation. Any time a change comes down that significantly disrupts things like the GTK vs QT YaST and the polar opposites in how they work, or this issue with Grub no longer setting up multiboot on install, it impacts me in a rather big way with all the extra support effort I have to do as a result.... so you're not alone in your frustration Dotan. C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org