D82 recorded (09 §3 decision 307): a household's box may remove old kernels after two real night removals on each ring-0 box
gates / gates (push) Successful in 2m2s
gates / gates (push) Successful in 2m2s
This commit is contained in:
1 parent
8955b4e55f
commit
327a7668e6
3 files changed
+11
-2
No files matched your search
@@ -1265,6 +1265,16 @@ Recorded before the work (`audits/space-list-2026-11-10/README.md` §5 held the
|
||||
Hetzner and the mail service are read from source and documents only: no hub database read, no account call.
|
||||
*Operator, 2026-11-10 12:22.*
|
||||
|
||||
### 2026-11-14 (16:06, operator) — D82: a household's box may remove its old kernels
|
||||
|
||||
307. **D82 = yes: a household's box (ring 1) may remove its old kernels by itself — after two REAL removals at night on
|
||||
each of the two ring-0 boxes (the N100 and demo-hp).** A quiet night with nothing to remove does not count. How the
|
||||
count is read: a kernel-layer report with mode `kernel-cleanup` and outcome `cleaned`, trigger `night`, per box
|
||||
(the hub's stored reports; the box's own journal line „old kernels removed” is the second channel). It needs a
|
||||
later agent release to switch it on; nothing is built for it in release 2a. **Cost of the other option:** a
|
||||
household's box keeps every kernel, about 1 GB each, until someone removes them by hand. R-1368.
|
||||
*Operator, 2026-11-14 16:06.*
|
||||
|
||||
### 2026-11-14 (09:55, operator, planning chat) — D80, D81, the N100's time service, the build order
|
||||
|
||||
Recorded before any build. **None of these is built at the time of writing.** The questions were D80 and D81 in
|
||||
|
||||
Reference in new issue
Block a user