From f9a313f44b32e57280da88e5a20a23b70b957880 Mon Sep 17 00:00:00 2001 From: rajames Date: Mon, 26 Oct 2026 19:46:48 -0400 Subject: [PATCH] docs(v4): the stick's identity partition starts at 500 MiB Captain Bob, 2026-10-26: "64 megabytes does not need to be an engraved in stone size ... start maybe 500 megabytes." Sizes are set in kernel/Makefile and are not fixed by the formats. Co-Authored-By: Claude Opus 5.5 --- docs/v4.0.0/STICK.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/v4.0.0/STICK.md b/docs/v4.0.0/STICK.md index 3df0f314..9bb53068 100644 --- a/docs/v4.0.0/STICK.md +++ b/docs/v4.0.0/STICK.md @@ -84,9 +84,11 @@ gains the partitions below). Three partitions: subsystem) runs unchanged on the partition device. - **Raw identity drives stay accepted:** a device with no valid GPT is read as today (the minted scratch pair in `disk/zuse-scratch/`, any v3 identity drive). -- **Sizes (my call):** the image is a fixed size and does not grow to fill a bigger stick. - Partition sizes are set at build time: ESP 64 MiB, identity 64 MiB (today's identity drive - size), Artemis the rest of a 2 GiB image. Changeable in one place, `kernel/Makefile`. +- **Sizes:** the image is a fixed size and does not grow to fill a bigger stick. Partition sizes are + set at build time, in one place, `kernel/Makefile`, and are not fixed by the formats: ESP 64 MiB, + identity 500 MiB to start (Captain Bob, 2026-10-26: "64 megabytes does not need to be an engraved + in stone size ... start maybe 500 megabytes"; the identity format records its own size, + `homeblocks_sig_t.metadata_devblocks`), Artemis the rest of a 2 GiB image (my call). - **The Artemis partition is formatted when the image is built (my call),** not on first boot: the image builder writes its `STFR` volume header and its `artemis_sig_t` genesis signature, so the kernel never meets a blank Artemis on a stick and never has to decide whether a disk may