From 4cb9efadae248fc353eb7d33c94d7fcd4d99478b Mon Sep 17 00:00:00 2001 From: jochens Date: Fri, 13 Nov 2026 00:28:08 +0100 Subject: [PATCH] Design 42 zfs-owns-zfs: A-27 to A-29, met in develop --- .../01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md index 03e52c45..c8d90802 100644 --- a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md +++ b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md @@ -92,3 +92,9 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The before its config file, and its package fails while the config file is missing, so the stop would keep a node from restoring its package manager: in this milestone the pacman module's config file moves before its package, and the node-engine's probe test of that restore keeps the pacman module's own resource names, in that order. +- **A-27** (§11, met in develop; principle 7) `snapshots` is an object, so its `none` is the object holding only the + key `none` set to true; keep counts are its other form, and the text `none` is refused as the type refuses it. +- **A-28** (§11, met in develop; principle 3) One refused value refuses the whole config: nothing is converged until + every value is valid, and each refused value is its own `config.refused`. +- **A-29** (§11, §18, met in develop; principle 3) The node's memory is read by the apply and given to the parse; a + memory that cannot be read refuses `arc-max` and `arc-min`, never guesses them.