CeeBee_Eh

Then anyone running a Windows VM would just switch to a Server edition, which is almost exclusively run via a VM.

If you install each OS with it's own drive as the boot device, then you won't see this issue.

Unless you boot Windows via the grub boot menu. If you do that then Windows will see that drive as the boot device.

If you select the OS by using the BIOS boot selection then you won't see this issue.

I was bitten by Windows doing exactly this almost 15 years ago. Since that day if I ever had a need for dual-boot (even if running different distros) each OS will get it's own dedicated drive, and I select what I want to boot through the BBS (BIOS Boot Selection). It's usually invoked with F10 or F11 (but could be a different key combo.

While I generally agree with that, that's not what seems to be happening here. What seems to be happening is that anyone who boots Windows via grub is getting grub itself overwritten.

When you install Linux, boot loaders like grub generally are smart and try to be helpful by scanning all available OSes and provide a boot menu entry for those. This is generally to help new users who install a dual-boot system and help them not think that "Linux erased Windows" when they see the new grub boot loader.

When you boot Windows from grub, Windows treats the drive with grub (where it booted from) as the boot drive. But if you tell your BIOS to boot the Windows drive, then grub won't be invoked and Windows will boot seeing it's own drive as the boot drive.

This is mostly an assumption as this hasn't happened to me and details are still a bit scarce.

That would break 90+% of installations then. And all of Azure.

even if you have two drives, you still have only one bootloader, not?

The idea is to have completely separate boot and OS drives. You select which one you want to boot through the BIOS boot selection (ie. pressing F10 or F11 at the BIOS screen).

This functionally makes each OS "unaware" of the other one.

I don't like btrfs, cause you still sometimes read about people loosing their data.

That was only on RAID setups. So if you have only a singular disk, as opposed to an array, you're fine. And that issue has been fixed for a while now anyways.

I've been running btrfs on my laptop's root partition for well over a year now and it's fine.

The new timeline reboot:

• Blocker: The beginning
• The Blocker Returns
• The Dark Blocker
• Blocker Homecoming
• Rise of the Blockers
• Dawn of the Blockers
• War of the Blockers
• Kingdom of the Blockers

And to bring it full circle:

• Planet of the Blockers