Description of problem: When I am installing mageia 6 sta2, at the end, in the summary window, the mageia installer only allow me to choose grub2 installer with gui or text mode, I can not choose grub1 or lilo to choose the partition on my hard disk where I want to install the bootloader. I DO NOT WANT that grub2 erase my windows bootloader on the first partition because I have a partition with Bitlocker and when mageia installer install the bootloader on the first partition on my harddisk, the windows partition with bitlocker is locked !!! Add in the mageia installer the choice : * to choose grub1 ou lilo , and a specific partition for the bootloader (like /dev/sda7) * or to add for grub2, an option to choose a specific partition for the bootloader (like /dev/sda7) Version-Release number of selected component (if applicable): mageia 6 sta2 installer How reproducible: Steps to Reproduce: 1. 2. 3.
Note: Hardware : Lenovo L560 with HDD SSD ATA LITEON LCH-256V2
We don't offer LILO & grub-legacy for new install as: - they're no more maintained (eg: latest grub legacy, 0.97, was released in early 2005!) - grub-legacy do not support neither new ext4 as formatted by e2fsprogs 1.43 (bug #18583) nor new xfs metadata (bug #19790, #18472, #18583) - we already deprecated lilo more than 10+ years, installing grub by default, keeping lilo as an alternative for a few users - lilo has started having issues with bigger kernels to load (bug #15109) - we need grub2 for UEFI systems - all the other main distros are dropping support for those legacy unsupported bootloaders So we only keep them for upgrades as in that case, the file systems were formatted with older tools that did not enabled the new metadata and thus are supported. And for new install, we only offer the supported grub2. See https://wiki.mageia.org/en/Mageia_6_Release_Notes#Grub2_used_as_boot_loader_by_default
Status: NEW => RESOLVEDCC: (none) => thierry.vignaudResolution: (none) => WONTFIX
*** Bug 20437 has been marked as a duplicate of this bug. ***
*** Bug 20541 has been marked as a duplicate of this bug. ***
CC: (none) => richard.j.walker