[FEATURE] Initialize regular GPT image files with boot-tool #7
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#7
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 creates GPT metadata and queries geometry through sgdisk. EriX has its own caller-buffer GPT writer, but the builder cannot invoke it as a native file operation.
Proposed behavior and scope
Add boot-tool gpt-create on Linux and EriX. Explicit arguments select an ordinary output file, logical block size, disk length, GUIDs, table/header capacities and indexed partitions. Stream metadata and zero-filled gaps through one publication. Print versioned numeric geometry from the same checked plan after successful publication and retirement.
Adopt this command in Integration's real image recipe. Filesystem formatting and partition-file dd overlays remain separate work.
Authority, security and reliability
The original prepared invocation selects one exact Publish14 file occurrence and no READ grant. No device, mount, entropy, service lookup or signing-key authority is added. Preflight geometry, storage and complete u64 byte length before Begin. Retain the original owners, packets, first error and separate cleanup evidence. Never replay uncertain effects; Status observes only the original commit. Keep Linux stable-parent and best-effort temporary-cleanup limits explicit.
Acceptance criteria
Alternatives and tradeoffs
A separate tool would duplicate command admission and native entry. Sequential initialization needs no seek/truncate ABI: six metadata/gap segments use bounded memory and the existing linear initialization cost.
Tracking and rollout
Depends on the GPT metadata writer. Land Boot-tool, then its measured Integration supplier and host producer. Full partition-payload assembly, native filesystem formatting and complete self-hosting remain follow-up work.
The GPT initializer and image-builder changes are committed locally. The command prepares metadata before native authority binding, streams six byte/zero segments through one publication, and returns geometry after commit and grant retirement. The builder selects the original owned tool and binds its complete compiler source vector to the packaged revisions.
Coordinated publication is pending. Partition-file overlays and filesystem formatting remain separate work. The shared GPT writer is available.