Files

T

rajamesandClaude Opus 5.5 e177c5c6b3 feat(build): the stick and the data stick, Artemis formatted and signed at build

The stick's increment 3, Task 1 (docs/v4.0.0/plans/2026-10-27-stick-3-images.md;
STICK.md 4). make boot_image TARGET=PC now writes the 2 GiB stick: ESP 64 MiB
(BOOTX64.EFI, startup.nsh, starforth.cfg), StarshipOS identity 500 MiB (zeros),
StarshipOS Artemis to the end. make -f kernel/Makefile ARCH=<arch> datastick
writes the 1.5 GiB data stick, identity and Artemis, fresh every time. Sizes in
kernel/Makefile; every partition on whole MiB.

tools/mkartemis formats and signs an Artemis partition at build with the
kernel's own code -- v3's block_subsystem.c (blk_subsys_confirm_format) and
artemis_sig.c (artemis_sig_genesis_stamp) -- through a blkio device over a byte
range of the image; --check reads one back the same way (read-only). disk_uuid
from getrandom(2): each image its own. mkdiskimage.sh gains --starship,
--mkartemis, --esp-mib; Milk-V and the Pi images are unchanged. The kernel is
not changed.

Red: scripts/check_images.sh FAIL (no datastick, the PC image one partition).
Green: 23/23. Mutation: --check on a range shifted by one block fails.
Accepted: suite EXIT 0; 133146, 133417, 133815, POST 538/538, dict_hash
0xfec8c47cfc6f437f; test-32, 0 failures.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-27 13:46:59 -04:00

board.mk

feat(build): the stick and the data stick, Artemis formatted and signed at build

2026-10-27 13:46:59 -04:00

README.md

boards: the amd64 target is PC -- a generic x86-64 UEFI PC, not the SER5

2026-10-14 17:22:32 -04:00

README.md

PC boot media (generic x86-64, UEFI)

make boot_image TARGET=PC builds build/boards/pc/lithos-pc.img: a GPT disk with one FAT32 EFI System Partition, for any x86-64 PC whose UEFI firmware boots a removable medium. Write it to a USB stick with dd. The partition holds:

EFI/BOOT/BOOTX64.EFI: the amd64 monolithic loader, with the whole kernel embedded. Firmware finds it through the UEFI removable-media path, so no boot entry has to be created.
startup.nsh: runs the loader if the firmware drops into the UEFI shell.
starforth.cfg: the boot arguments -- system=v4 as built; change the word to system=v3 to boot v3 (and KERNEL_ARGS="..." adds to it).

Beside the image, lithos-pc.spdx / .spdx.json: its SBOM, every file on it with its SHA-256.

Nothing in the image is specific to one machine: it follows the generic UEFI/ACPI path in FABRIC-3.md §III. Until 2026-10-14 this target was named SER5, after the first PC to be brought up -- a Beelink SER5 (AMD Ryzen), which is still the one on the bench (boards/BRINGUP.md).

Status: booted in QEMU (q35 + OVMF, from this image as its own disk): v4 as built, v3 with system=v3. Not yet booted on real hardware.