2 ms·
You're fighting an uphill fucking battle, Linux Foundation and here's why: UEFI, the standard, is so loosey-goosey, with so many bits unspecified, that the only
by bitwize 14y ago
You're fighting an uphill fucking battle, Linux Foundation and here's why: UEFI, the standard, is so loosey-goosey, with so many bits unspecified, that the only real test of whether the system is compliant that actually matters is "does it boot Windows". It's rather like the Web back in the day, when we had HTML and CSS and all of that but the only standard that people applied was "does it look nice and work in IE5". We've already seen one UEFI implementation from Samsung that can brick the machine when a non-Microsoft (or even sometimes a Microsoft) OS is installed on it; and one from Lenovo that actually searches the strings of the boot image looking for either "Windows" or "Red Hat Linux" and refuses to boot otherwise. Expect more cock-ups of this sort, whether due to malice or incompetence, to follow. This isn't about a hardware-verifiable boot process, it's about multiple vendor-specific boot processes, the only thing they can be guaranteed to have in common is their capability to boot into a Microsoft OS. Those of us disinclined to trust Microsoft will see this as a largely successful attempt to decommoditize the boot protocol, as per the Halloween Documents.