>GPT partition uuid's with the "mixed endianess" from Windows COM From the wikipedia[1]: >The binary encoding of UUIDs varies between systems. Variant 1 UUIDs

>GPT partition uuid's with the "mixed endianess" from Windows COM From the wikipedia[1]: >The binary encoding of UUIDs varies between systems. Variant 1 UUIDs, nowadays the most common variant, are encoded in a big-endian format. >Variant 2 UUIDs, historically used in Microsoft's COM/OLE libraries, use a little-endian format, but appear mixed-endian with the first three components of the UUID as little-endian and last two big-endian, due to the missing byte dashes when formatted as a string In other words, there are 2 variants, 2 is for Microsoft's COM/OLE, so it's not designed by Microsoft. >ESP is the FAT filesystem, developed in 1977 for DOS >LFS vfat extensions so the ESP can have directory entries with lowercase letters or longer than 11 characters. This also pulls in the UCS-2 encoding. Stuff from Windows 95. FAT is not govern by Microsoft, despite them being the original author, and even then FAT32 patents have expired[2]. >EFI executables are actually windows PE executables You would need to provide proper source for this, the only source I can only talks about boot loaders, which I would imagine is written with the OS in mind[3]. [1]https://en.wikipedia.org/wiki/Universally_unique_identifier#Encoding https://en.wikipedia.org/wiki/Universally_unique_identifier#... [2]https://en.wikipedia.org/wiki/File_Allocation_Table#Patents https://en.wikipedia.org/wiki/File_Allocation_Table#Patents [3]https://en.wikipedia.org/wiki/UEFI#Applications https://en.wikipedia.org/wiki/UEFI#Applications