Populate ext4 product images from explicit entries #11

Open
opened 2026-10-24 16:02:53 +02:00 by erikinkinen · 0 comments
Owner

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

  • Prepare every entry type, literal fast and long symlinks, hardlink counts, explicit inode metadata, multiblock directories and indexed file extents without arbitrary node limits or volume-sized buffers.
  • Share one mapped-file driver with contiguous FAT/GPT assembly; preserve source and image progress separately, exact EOF/digest checks and once-only input retirement.
  • Derive the complete product tree from its declarations, validate original file inputs and exact argument storage, and retain all executable, sidecar, alias, manual, Boot and scenario entries.
  • Adopt an explicit versioned product format and metadata policy with complete provenance; remove imported product formatting and installation while preserving existing-fixture overlays and independent oracles.
  • Cover generated media through E2fsd's real reader and journaled mutation paths, including metadata, hardlinks, symlinks, devices and corruption or persistence refusals.
  • Keep mandatory product assertions in both scenario routes, update documentation and add meaningful capacity, partial-I/O, cleanup and product-coverage controls.

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.

## 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 - [ ] Prepare every entry type, literal fast and long symlinks, hardlink counts, explicit inode metadata, multiblock directories and indexed file extents without arbitrary node limits or volume-sized buffers. - [ ] Share one mapped-file driver with contiguous FAT/GPT assembly; preserve source and image progress separately, exact EOF/digest checks and once-only input retirement. - [ ] Derive the complete product tree from its declarations, validate original file inputs and exact argument storage, and retain all executable, sidecar, alias, manual, Boot and scenario entries. - [ ] Adopt an explicit versioned product format and metadata policy with complete provenance; remove imported product formatting and installation while preserving existing-fixture overlays and independent oracles. - [ ] Cover generated media through E2fsd's real reader and journaled mutation paths, including metadata, hardlinks, symlinks, devices and corruption or persistence refusals. - [ ] Keep mandatory product assertions in both scenario routes, update documentation and add meaningful capacity, partial-I/O, cleanup and product-coverage controls. ## 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](https://git.erikinkinen.fi/erix/boot-tool/issues/10) and shares the [FAT32 assembly path](https://git.erikinkinen.fi/erix/boot-tool/issues/9). Tracked by [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Full image construction and the EriX and external-toolchain builds inside EriX remain required.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:34 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/boot-tool#11
No description provided.