On 2017-05-16 04:20, Felix Miata wrote:
Carlos E. R. composed on 2017-05-15 22:44 (UTC+0200):
John Andersen wrote:
Dual Boot has become a minefield of late. Dueling Distros. Battling boot loaders. Any one system can put your entire multiboot installation at risk. And that's before Windows 10 shenanigans kick in.
The only notable thing Win10 changed here is it refuses to assign anything other than C: to its system partition. Its system partitions are still on logical volumes, but it assigns D: to the primary partition containing its boot paraphernalia, which like Vista, 7 and XP before them, can chainload a Grub or Lilo installed to a primary partition for booting Linux. I've not had reason to try, but I suspect the Win10 boot manager might even be able to launch a FOSS bootloader installed to a logical partition.
No, I understand it is broken. EasyBCD, which was the tool used mostly in the past, now fails. And Windows service packs (7 to 10, for instance) and other W10 updates fail unless the windows partition is marked bootable.
It is in fact doable and simple.
You need to have all distributions boot from its own partitions. Do not allow any operating system, except one, to write to the MBR. Choose one system to write and control the MBR, only one. Or none, doing the controlling yourself, as has been done here for in excess of two decades. They're my machines, so I get to decide what goes in the MBR, which excludes Grub, Lilo and every other bootloader that wasn't originally designed to boot DOS on a 16 bit IBM PC.
That's more difficult. And will not work on GPT disks. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))