Sarja

Engineering

How the system is built.

Sarja Software works below the application layer. This is how Iron Linux is produced and checked — drawn from the project's own repository.

  1. 01

    Configuration as source

    auto/config holds the canonical live-build invocation, so the whole build is reproducible from a clean checkout — no undocumented flags.

  2. 02

    Package lists with reasons

    Four package lists (core, desktop, apps, live) and a written rationale for every choice in docs/PACKAGES.md.

  3. 03

    Pre-build validation

    Scripts lint the package lists and check XML, GTK-CSS and JSON configuration, script interpreters and the installer module sequence before a ten-minute build is spent.

  4. 04

    Structural image checks

    The built ISO is checked for BIOS and UEFI El Torito structure; the Raspberry Pi image for partition layout, arm64 rootfs and boot files.

  5. 05

    Recorded test scope

    A boot, login, install and reboot flow exercised end to end in QEMU — and a list of exactly what that did not cover.

Iron Linux does not include an Iron-specific package repository; Debian's archive is the only APT source.