max / alloy
1 file changed,
+10 insertions,
-0 deletions
| @@ -1,5 +1,15 @@ | |||
| 1 | 1 | # Cutover runbook: fw13, Pop!_OS to Alloy | |
| 2 | 2 | ||
| 3 | + | > **Phases 2 and 3 below are void, 2026-09-03.** They describe a shrink of `nvme0n1p3` or an | |
| 4 | + | > external root, with Pop kept bootable as the way back. Max ruled out dual boot on 2026-08-27 | |
| 5 | + | > and ruled out buying a drive on 2026-09-03: fw13 is a standard destructive swap on its current | |
| 6 | + | > drive, and the way back is the data hot potato, not a partition. Do not shrink anything on | |
| 7 | + | > this machine. The plan of record is wiki `alloy-fleet-cutover`; this file is rewritten to it | |
| 8 | + | > under GoingsOn alloy `5892fc62`. | |
| 9 | + | > | |
| 10 | + | > Two figures below are also stale, measured 2026-09-03: `/` is 94% full with 107G free, not | |
| 11 | + | > 798G, and fprintd plus fprintd-pam are in the image (`Containerfile:1637`) rather than absent. | |
| 12 | + | ||
| 3 | 13 | This file answers one question. What is the order of operations that moves fw13 from Pop!_OS 24.04 to Alloy without stopping releases, and what is the way back at each step if it goes wrong. | |
| 4 | 14 | ||
| 5 | 15 | Companion to [HARDWARE-FW13.md](HARDWARE-FW13.md), which records what the machine is, and to [IMAGE.md](IMAGE.md), which records how the image is built. The migration ordering and the two genuinely unknown hardware facts come from wiki `alloy-fw13-migration`. The build-host gap list is GoingsOn alloy task `c4eb6d5e`. |