When you install more than one Linux distribution at the same time only one of those installations needs to write Grub into the MBR. My request would thus be to allow Mageia either to install Grub into the Mageia partition (in order to chainload that partition) or allow not to install Grub at all. For my configuration that would have been feasible as my Arch loader was already configured to boot Mageia. Actually a low priority issue as you can always chroot back to the other installation and reinstall Grub from there.
... otherwise it would be fine to add support for more distros to the Mageia loader (I have already done that with OpenBSD); it currently did not recognize my Arch installation.
AFAIK it's already possible to install the bootloader to the Mageia partition instead of the MBR, many of us use that. An option to be able to skip bootloader installation altogether might be good for more advanced users indeed.
Assignee: bugsquad => mageiatoolsSource RPM: (none) => drakxtools
Strange; the only possible selection was /dev/sda at me; It was not possible to select /dev/sda2 (a primary) where I had installed Mageia into.
You've the "Do not touch ESP or MBR" advanced option on second screen when using UEFI.
Status: NEW => RESOLVEDCC: (none) => thierry.vignaudResolution: (none) => INVALID
What if you're not using UEFI?
Hmm; I still have BIOS on all my systems (was trying to avoid UEFI since some people including me regard it as a security nightmare; ask at coreboot). Why do you not want to support this feature for BIOS based machines? Why is Mageia behaving that different on BIOS machines? ( Up to now I did not feel a need for anything faster than my Core 2 Quad 3,3Ghz BIOS system; even my 2,26Ghz Quad notebook with somewhat slower RAM/FSB compiles the kernel in no more than an hour though UHD video playback can become hairy there; most videos are still FullHD so I do not need anything faster either. ).
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Comment #4 is migiving, this apply to MBR too obviously
Status: REOPENED => RESOLVEDResolution: (none) => INVALID