https://bugzilla.novell.com/show_bug.cgi?id=635301
https://bugzilla.novell.com/show_bug.cgi?id=635301#c3
Josef Reidinger
Very cute. I didn't "tell" it to touch the MBR; as I recall, the only option I was given was whether to put openSUSE's booter in the MBR or the partition. I told it to put the booter in the partition. If the default was to cream the MBR anyway, I don't recall being told that, let alone being given the chance to overrule it.
Hi, you use just simple option in overview. IT switch between GRUB code in MBR or GRUB code in partition and generic MBR at disc which boots active partition. If you want to not touch MBR at all you must go into details, because it expected experienced user ( because without touching MBR we cannot guaranty that system boot, so user must know what (s-)he doing ). So if you want to not touch MBR go into bootloader details, choose boot from boot and deselect "Write generic boot code to MBR" in Boot Loader Options.
There is no excuse for that being the defasult behavior. But if it is, that's the explanation, so go ahead and close this.
Default behavior is to ensure that system boot ( same behavior has almost all distribution which do some automation so also ubuntu ). And of course you can change it. I suppose you choose to have in GRUB boot code in partition, but keep writing of generic boot code to MBR ( which boot partition which has set active flag ).
This kind of contempt for users shouldn't be a surprise, I suppose, coming from an organization that's such good friends with Microsoft.
Useless sentences which doesn't help anything. Opensuse is just sponsored by novell, not owned, so opensuse community decide what is in product not novell. So if I understand how you use it, it is invalid bug report as it works as expected. If you think that bootloader should print warning about overwrite of MBR, please put it in features for next release - http://features.opensuse.org -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.