Create initialized journaled ext4 image files #10
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#10
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
Image construction still relies on imported ext filesystem tools. A native image-file initializer needs explicit geometry and metadata choices, complete initialization and journaling support before it can become part of a self-hosted image recipe.
Proposed behavior and scope
Add a pure ext4 plan and an ext4-create command that writes an ordinary initialized filesystem image containing root and lost+found. Define a new explicit feature profile, including internal JBD2 journaling and metadata checksums. Stream metadata and zeros through the existing host/native assembly publisher. Full file population and product recipe replacement follow separately; this profile does not claim equivalence with an imported formatter's defaults.
Authority, security and reliability
The caller supplies geometry, identities, labels, seeds, ownership, modes and timestamps. Preparation performs no file discovery, account lookup, device access, mounting, clock or random-source request. Empty initialization needs one output publication and response streams, with no input-file grant. Preserve bounded scratch, original publication custody, first failures and independent cleanup through partial writes, synchronization and commit uncertainty.
Acceptance criteria
Alternatives and tradeoffs
A journal-free image is smaller in scope but leaves an essential product migration requirement unresolved. Importing a formatter still requires a declared configuration, source/runtime closure and guest port. A native initializer provides an independently reviewable format path; complete typed population must also preserve hard links, symlinks, special-file metadata and executable identities before replacing product construction.
Tracking and rollout
Build on GPT assembly and FAT32 creation. Tracked by Phase 6 completion. Keep current product and advanced-fixture tools until their complete entry and persistence contracts have replacements.
ext4-createis implemented in signed local commits. It initializes root and lost+found, group metadata, sparse backups and an internal journal from explicit format choices. Metadata emission shares FAT32’s batched publication path. Typed product-file population is next; the product recipe still uses its imported ext4 construction.