clawdie/layered-soul
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

skill(freebsd): clarify fleet vs OSA upgrade paths at top of runbook

Browse source 
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.
This commit is contained in:
Sam & Claude 2026-06-25 11:57:24 +02:00
parent bcb769f2e0
commit 245e25200f
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
skills/freebsd-os-upgrade/SKILL.md
View file

@ -67,6 +67,15 @@ pkg update -f && pkg upgrade # ports packages (separate from base here)
## Runbook ## 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 1. **Capture pre-status** for after-the-fact comparison — see
*Pre-reboot status capture* in the reference (hostname, `freebsd-version -k` *Pre-reboot status capture* in the reference (hostname, `freebsd-version -k`
/ `-u`, `uname -r`, services, `jls`, `pfctl -s info`). Record / `-u`, `uname -r`, services, `jls`, `pfctl -s info`). Record