Oh, believe me: There are so many messy BIOS and UEFI implementations out there that you can definitely deactivate it in the BIOS for some. Which just introduces even more mess where hibernation triggered on the OS level then fails.
Oh, believe me: There are so many messy BIOS and UEFI implementations out there that you can definitely deactivate it in the BIOS for some. Which just introduces even more mess where hibernation triggered on the OS level then fails.
They actually don’t. They try and it works for some time. And then the next Windows update intentionally fries their dual-boot. Then they go back to Windows.
Or they understood enough about the details and how to minimize the risk (basically running Linux with an linux boot manager that then chain-loads Windows boot files from another disk, so Windows is mostly oblivious about the other OS… and even then Windows likes to screw with the efi record) that they are mainly running linux. And later they tend to ditch Windows completely of just keep a virtual machine if they really need it for some proprietory stuff.
At least those scenarios above cover 95% of all people “dual-booting” I know…
In comparison, dual- or triple-booting Linux is indeed a bit less problematic. But the same thing applies: You mainly run one. And given that Linux distributions are all nearly the same, with just a few differences in pre-configuration and defaults, there’s not much point to it.
The good thing is: They might be big but they are mainly a risk for bees. But not much is actually as obnoxious (or dangerous for humans) as the aggressive assholes that are our domestic common wasps.
There’s one caveat here: The UEFI specification doesn’t strictly require the ability to handle more than one EFI System Partition on a drive, so some simply don’t. So this “use a separate boot partition”-method might fail on some computers that just don’t recognize a second ESP on the same drive and only surely works with a whole separate drive for Linux.