Create FAT32 image files through native streaming assembly #9
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/boot-tool#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
ESP creation still depends on external FAT formatting and file-copy utilities. EriX needs an image-file path it can build and run itself, alongside the existing GPT assembly.
Proposed behavior and scope
Add deterministic FAT32 image creation to Boot-tool from explicit directory and file entries. Stream boot records, both FATs and directories through bounded scratch, then reuse the existing checked payload reads and single output publication. Support long UTF-16 names, collision-safe short aliases, explicit geometry, labels, volume IDs and timestamps.
Migrate the product disk recipe, appliance runtime boot volume and raw ESP scenario route in Integration. Preserve their existing metadata tail and payload contracts. Specialized corruption fixtures and independent inspection tools remain separate consumers.
Authority, security and reliability
Use the existing selected READ and output-publication capabilities. No raw block, mount, directory discovery, clock or randomness authority is needed. Validate the complete plan before grants or output effects. Preserve each original operand occurrence, first error, partial output state and independent once-only input/output retirement. A late input failure must preserve the previous published image.
Acceptance criteria
Alternatives and tradeoffs
Whole-image and whole-FAT buffers grow with volume size. An arbitrary output-generator callback would widen the assembly interface. Closed metadata ranges keep generation within the prepared format plan and existing publication owners. Reuse the shared filesystem-name policy instead of adding another Unicode table.
Tracking and rollout
Extends GPT image initialization and partition payload assembly, with Integration adoption tracked by full build and image assembly. The Phase 6 checklist retains the complete guest build requirements. Format references are Microsoft's FAT specification and the UEFI filesystem contract; no third-party implementation is imported.
Implemented locally in signed checkpoints: Boot-tool
97fc50a4, Integrationc2aff569, Fatd6d799054and manuale273014e.The encoder prepares deterministic FAT32 metadata and allocation runs from
explicit entries, then streams sectors and exact file contents through the
shared publication driver. Product ESP, empty runtime boot and raw ESP recipes
use the same selected image-tool artifact and source closure. Specialized
malformed-media fixtures keep their separate tools.
Coherent publication and guest execution remain open.