[FEATURE] Stream partition payloads into GPT image files #8
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#8
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
The image recipe writes formatted partition files into an existing disk image with dd. Native image assembly needs a file-only path that streams those payloads without allocating a complete image or acquiring device and mount authority.
Proposed behavior and scope
Extend boot-tool gpt-create with explicitly indexed partition files, byte lengths and SHA-512 digests. Prepare the complete output layout before native authority binding. Stream metadata, zero gaps and selected payloads through one publication on Linux and EriX; require exact input EOF, length and digest before commit. Adopt this path in the product image recipe and remove its partition-file dd overlays.
Authority, security and reliability
Keep the initializer without payloads Publish-only. Payload operations add only their original argument-bound READ occurrences. A retained reader and publisher share the same explicit driver and finite caller buffers; data descriptions and callbacks cannot acquire authority. Keep the derived broker, output and current input receipts distinct. Retire each input positively before reusing its destination. Preserve the first failure, confirmed prefixes and separate cleanup outcomes; uncertain effects cannot be replayed. A late input refusal must preserve the previously published destination.
Acceptance criteria
Alternatives and tradeoffs
A second file driver or a callback hidden in the output description would complicate original-handle custody. A closed pump alternates reads and writes on one driver. Sequential assembly avoids a seek or raw-block interface and keeps memory proportional to metadata and caller buffers.
Tracking and rollout
Depends on GPT image initialization. Land the shared reader, Boot-tool assembly and coordinated Integration adoption. Native filesystem formatting and complete build-within-EriX acceptance remain separate requirements.
The retained reader, Boot assembly path and product recipe are implemented and committed locally. Partition files stream through one publication with exact length, EOF and SHA-512 checks; each input retires before its receipt is reused. The recipe finishes both filesystem artifacts before assembling the image, preserves the previous destination on refusal, and removes both partition-file dd overlays.
The component and technical manuals are updated. Coordinated publication remains pending; native filesystem formatting and full self-hosting remain separate work.