On 05/15/2017 03:44 PM, Carlos E. R. wrote:
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. The rest must boot from their respective partitions only, under control of the main operating system.
Ie, one grub controls it all.
In a perfect world, this is how it should work, and the grub controlling the whole system would 'ask' upon finding an os before writing the bootloader to the mbr on the newfound disk. I'm encouraged by this thread. If grub2 with osprober didn't automatically overwrite the mbr on Stephen's box, that's progress. I have zypper locks on grub2 just for that reason (having had win10 bootloader on /dev/sda overwritten by a minor grub update to Leap on /dev/sdb) However, on this most recent kernel and grub update, I left the lock in place, installed the kernel and then delayed a week until I physically removed the w10 drive and replaced it with an Arch drive before removing the lock and allowing grub2 to update. This time, grub did not overwrite the mbr on /dev/sda -- that's progress. I'd rather have to tell osprober where to look, rather than having to sort out dual boot issue when it thinks for itself and gets it wrong. This is positive news. (I have added the lock back to grub2) However, if I see another clean upgrade, w/o overwriting /dev/sda, I'm might have the confidence to try with the w10 drive in place :p -- David C. Rankin, J.D.,P.E.