On 2017-05-16 15:52, Felix Miata wrote:
Carlos E. R. composed on 2017-05-16 14:31 (UTC+0200):
Felix Miata wrote:
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. No WRT what exactly? Fails in what manner?
I don't know. I was told not to try, it doesn't work with W10.
And Windows service packs (7 to 10, for instance) and other W10 updates fail unless the windows partition is marked bootable.
Boo hoo. How many seconds does it take to move the boot flag elsewhere and back? When necessary, I move it last thing before applying those updates, then move it back when those updates are finished.
Minutes. Hours, if the update fails because I did not change the boot flag. With W10 you do not know when you will get updates, no control over it. Your method means not been able to select the boot system in Grub each time I boot. The method I use is far simpler, once applied: https://nwrickert2.wordpress.com/2015/06/15/generic-boot-code/
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. More difficult than what, rescuing non-bootable systems following updates or new installs allowed to usurp control?
More difficult than just selecting what to boot in a working grub menu.
And will not work on GPT disks.
Again boo hoo. Just because manufacturers are cranking out monster HDs doesn't mean everybody needs them.
I do. About everybody buying computers now do. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))