From 9f3f9ee638e0a82960446f74345e9ee99bfec474 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 21:11:01 -0500 Subject: Rename the default base snapshot from "ready" to "default" "ready" read as a status word rather than a label for what's actually a mutable pointer to "the current recommended base image," re-tagged as it evolves - the exact operation we did twice this session. "default" names that role directly: it's the value --base-snapshot falls back to, nothing more claimed. Co-Authored-By: Claude Sonnet 5 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 88b1d93..bff2a78 100644 --- a/README.md +++ b/README.md @@ -79,13 +79,14 @@ Unmount devfs and snapshot once the image can actually build and run apps: ``` # umount /skiff/base/dev -# zfs snapshot zroot/skiff/base@ready +# zfs snapshot zroot/skiff/base@default # zfs create -o mountpoint=none zroot/skiff/appbase # zfs create -o mountpoint=none zroot/skiff/appdata # mkdir -p /skiff/apps ``` -`ready` is the snapshot every app's dataset gets cloned from. Re-snapshot +`default` is the snapshot every app's dataset gets cloned from unless +`--base-snapshot` says otherwise. Re-snapshot under a new tag after patching the base (e.g. `security-2026-08`) and pass `--base-snapshot` to `new-app` to pick it up. -- cgit v1.3