From 98a345c017a01533ed0e62b0ca871c52cc056cec Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sat, 8 Aug 2026 00:52:14 -0700 Subject: [PATCH] Update OEM comments to the renamed factory-reset command Reference omarchy-system-factory-reset (was omarchy-reset-computer) in the orchestrator comments and the plan. Co-Authored-By: Claude Fable 5 --- .../usr/share/omarchy-iso/orchestrator/phases_impl.py | 4 ++-- plans/oem-install.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/configs/airootfs/usr/share/omarchy-iso/orchestrator/phases_impl.py b/configs/airootfs/usr/share/omarchy-iso/orchestrator/phases_impl.py index 81a17de..5aa2c85 100644 --- a/configs/airootfs/usr/share/omarchy-iso/orchestrator/phases_impl.py +++ b/configs/airootfs/usr/share/omarchy-iso/orchestrator/phases_impl.py @@ -1150,7 +1150,7 @@ def run_system_finalizer(ctx: InstallContext) -> None: # ───────────────────────────────────────────────────────────────────────────── # stage_oem_state: produce the on-disk "OEM state" the runtime's first-boot -# setup (omarchy-oem-setup) and factory reset (omarchy-reset-computer) consume. +# setup (omarchy-oem-setup) and factory reset (omarchy-system-factory-reset) consume. # # Every install stashes the bundled Node tarball in /var/lib/omarchy/oem/ # so a later factory reset can finalize the new owner's user offline. OEM-mode @@ -1784,7 +1784,7 @@ def _validate_pre_mounted_filesystems(ctx: InstallContext) -> None: # create_factory_snapshot: read-only snapshot of @ kept at the btrfs top level # as @factory — outside snapper's .snapshots, so cleanup timers and the Limine # snapshot menu never touch it. Zero bytes at creation; grows only with drift. -# Taken at the end of every install, it is what makes omarchy-reset-computer a +# Taken at the end of every install, it is what makes omarchy-system-factory-reset a # true factory reset. # ───────────────────────────────────────────────────────────────────────────── diff --git a/plans/oem-install.md b/plans/oem-install.md index 726148d..42ddd4a 100644 --- a/plans/oem-install.md +++ b/plans/oem-install.md @@ -102,12 +102,12 @@ user's password. ## Runtime-side changes (omarchy repo) - `omarchy-oem-setup` + `omarchy-oem-setup.service` (the OOBE above). -- `omarchy-reset-computer` (below). +- `omarchy-system-factory-reset` (below). - Relax `omarchy-setup-system`: when the install user doesn't exist yet, the three `usermod -aG` scripts append to `/var/lib/omarchy/oem/groups` instead of failing the getent check. -## Reset: `omarchy-reset-computer` +## Reset: `omarchy-system-factory-reset` Behind a very explicit confirmation (typed, not y/n): @@ -154,7 +154,7 @@ on it existing. So: - VM: OEM install (encrypted + unencrypted) → reboot → OOBE → session; verify LUKS passphrase is the user's, throwaway key gone, groups applied, `omarchy-finalize-user` state marker present. -- VM: normal install → use system → `omarchy-reset-computer` → OOBE as new +- VM: normal install → use system → `omarchy-system-factory-reset` → OOBE as new user; verify no trace of prior user (home, NM connections, tailscale, machine-id, host keys, snapper snapshots). - Autoinstall: cidata drive with `oem` marker and no credentials → unattended