6 ms·
I am a bit curious how exactly Microsoft planned to identify that a machine was dual booting linux. Looking for certain files on a random partition? A list of
by nerdjon 2y ago
I am a bit curious how exactly Microsoft planned to identify that a machine was dual booting linux.
Looking for certain files on a random partition? A list of distros and versions? A partition type? Anything seems to be error prone and likely to miss something.
- not_doctorq 2y agoBased on the article, but I’m still not sure if this is the case, it seems like they checked for a specific shim(s), which would be on the EFI partition that everything shares.
- diggan 2y agoMaybe port `os-prober` to Windows? Has been a relatively stable solution for me for probably decades at this point, and hasn't missed anything yet, but maybe I'm not doing enough esoteric setups.
- deleted 2y ago[deleted]
- abhinavk 2y agoCheck the files in EFI partition. https://en.wikipedia.org/wiki/EFI_system_partition https://en.wikipedia.org/wiki/EFI_system_partition
- pepa65 2y agoIn an UEFI-centered world, you can just look where the bios would look.
- mook 2y agoI wonder if they were checking for extra entries in the Windows boot config database instead (i.e. Windows chain loading grub), but most people go the other way?