From 245e25200fbdd24e0fd9c33c65808f1555a2950f Mon Sep 17 00:00:00 2001 From: Sam & Claude Date: Thu, 25 Jun 2026 11:57:24 +0200 Subject: [PATCH] skill(freebsd): clarify fleet vs OSA upgrade paths at top of runbook MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fleet nodes (USB/disk, built from release memstick) use freebsd-update — one command, zero flags. OSA uses pkgbase, carrying the repo-editing + IGNORE_OSVERSION complexity. Make the distinction visible before anyone starts reading steps meant for the other path. --- skills/freebsd-os-upgrade/SKILL.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/skills/freebsd-os-upgrade/SKILL.md b/skills/freebsd-os-upgrade/SKILL.md index 0a7ba25..0255ad6 100644 --- a/skills/freebsd-os-upgrade/SKILL.md +++ b/skills/freebsd-os-upgrade/SKILL.md @@ -67,6 +67,15 @@ pkg update -f && pkg upgrade # ports packages (separate from base here) ## Runbook +**Which path applies to you:** + +- **Fleet (USB/disk nodes)**: `freebsd-update` path — one command, no flags. + `freebsd-update -r 15.1-RELEASE upgrade` handles all cross-release logic. +- **OSA (mother, build host)**: `pkgbase` path — carries the repo-editing + + `IGNORE_OSVERSION` steps below. If OSA were ever unified to freebsd-update, + the entire pkgbase branch disappears. Until then, it's a once-a-year tax on + one host. + 1. **Capture pre-status** for after-the-fact comparison — see *Pre-reboot status capture* in the reference (hostname, `freebsd-version -k` / `-u`, `uname -r`, services, `jls`, `pfctl -s info`). Record