partition.zig gains an exFAT VBR recognizer: the "EXFAT " name (where a FAT BPB keeps its OEM string, so the two never collide) plus the 0x55AA signature, with VolumeSerialNumber (offset 100) as a new exfat_serial identity rung. A `recognize` helper tries exFAT, then FAT, then the MBR disk-signature fallback, and sets each volume's FilesystemKind — so allVolumes/firstVolume and the GPT path all tag a volume with the engine its content needs. volume-map renders exfat-<serial> as the id-path, and filesystems.csv adds the exfat -> /system/services/exfat row: an exFAT stick now spawns the exFAT service, at its own content id-path. Host tests: a bare exFAT volume recognized with its serial; a FAT VBR still recognized as fat (the discrimination); the exfat-<serial> id render. build + zig build test + bounds green.
368 B
368 B
| 1 | # The filesystem map: a probed volume's content signature -> the service binary |
|---|---|
| 2 | # that serves it (docs/file-system-development/storage-architecture.md). The |
| 3 | # volume manager reads this (the policy); a signature no row matches goes |
| 4 | # unserved, never guessed. Adding a filesystem adds a row. |
| 5 | # |
| 6 | # signature, binary |
| 7 | fat, /system/services/fat |
| 8 | exfat, /system/services/exfat |