Populate ext4 product images from explicit entries #11
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#11
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 native ext4 initializer creates empty journaled filesystems. Product data images still need imported formatting and debugfs installation. A complete native path must install every declared product entry and preserve its metadata before publishing the image.
Proposed behavior and scope
Add typed directories, regular files, hardlinks, literal symlinks, FIFOs and device nodes with explicit ownership, permissions, timestamps and inode generation. Populate an ordinary image file through the existing publisher, then adopt it in the product data-partition recipe. Define and record the product geometry and metadata policy explicitly. Keep existing-media mutations and independent format oracles separate.
Authority, security and reliability
Each unique file source retains its original argv occurrence, expected length and SHA-512 digest. A file spanning block groups keeps one read owner and one hash state across intervening metadata. Hardlinks share the selected inode and input. Image names and device numbers grant no host access. Preparation checks topology, capacity and representable fields before publication authority is acquired. Preserve first errors, partial effects, uncertain replies and independent retirement without replay.
Acceptance criteria
Alternatives and tradeoffs
Retaining imported formatting would require an admitted guest tool and its configuration closure. The native route keeps image creation within the existing file publication protocol. Its product geometry and numeric ownership policy are new explicit choices; imported formatter defaults are not a portable equivalence contract.
Tracking and rollout
Extends journaled ext4 initialization and shares the FAT32 assembly path. Tracked by Phase 6 completion. Full image construction and the EriX and external-toolchain builds inside EriX remain required.