well, well. see, how "I" start "bickering". the only thing missing, is that fan girl, following me and telling "he
thinks, I am wrong"... but anyway, just a couple of remarks.
bzt wrote:
Meaning it doesn't matter what's in the M$ FAT specification, EFI specifies it's own file system format.
"non" troll, either show me UEFI FAT specification or you are laughingstock.
for other people, not as "advanced" in parallel reality observing as bzt, and just for the sake of truth - UEFI doesn't specify one and instead clearly refers to the MS spec.
Quote:
The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI defines a specific version of FAT that is explicitly documented and testable. Conformance to the EFI specification and its associate reference documents is the only definition of FAT that needs to be implemented to support EFI. To differentiate the EFI file system from pure FAT, a new partition file system type has been defined.
the EFI specification doesn't contain FAT specification per se and "associate reference documents" in this respect is this one:
Appendix Q References, Q.1 Related Information wrote:
Microsoft Extensible Firmware Initiative FAT32 File System Specification, Version 1.03,
Microsoft Corporation, December 6, 2000,
http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx
the whole "newness" and "difference" of EFI FAT is this one:
Quote:
To differentiate the EFI file system from pure FAT, a new partition file system type has been defined.
summarizing, UEFI FAT is one defined by the MS FAT specification, with the additional requirements regarding its typing and emphasis on using FAT32 for ESP, laid out in the UEFI spec. that's it. there are also notes about using only UCS-2 subset opposed to all UTF-16 and always supporting long names. it's a subset of a thing, specified in A and rules for subsetting, specified in B. where A - is MS FAT spec, B - UEFI spec.
and this one again, I quoted already, but it's you, so, here is yet once:
Quote:
EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable media.
if you cannot grasp this, then sorry.
bzt wrote:
Could we please see your installer (app, script whatever) that does all of this in your build environment? Do you even have an automated workflow for creating a bootable image from your source code?
I don't use "bootable image" for UEFI.