novox/hq
6
0
Fork 0
Code Issues Pull Requests 5 Releases Wiki Activity

Design 52: until it is adopted, the workstation's fstab line still mounts at boot (review follow-up) #229

Merged
mesh-admin merged 1 commits from fix/shares-review-followups into main 2026-10-08 19:37:04 +00:00
Conversation 1 Commits 1 Files Changed 1
+12 -4
mesh-admin commented 2026-10-08 19:14:43 +00:00
Contributor
Copy Link
Copy Source

A follow-up to #221 from the review of the shares work (ADR 0263).

Design 52 §5 said a reboot "does not wait" from step 3 onward. That is not true until step 5. The workstation's hand-written fstab line still makes the mount wanted by remote-fs.target, so at boot the module's .mount (which now carries that mount point) is started directly. It can hold the boot for up to its 30 s mount timeout, and fails when the home server is unreachable.

The changes:

  • Step 2 now says so, and says why step 5 follows soon after.
  • Step 3 checks a reboot that waits while the line stands.
  • Step 5 says that from the next boot only an access mounts the share.

merge-check.sh passes locally. Not to be merged before review.

A follow-up to #221 from the review of the shares work (ADR 0263). Design 52 §5 said a reboot "does not wait" from step 3 onward. That is not true until step 5. The workstation's hand-written fstab line still makes the mount wanted by `remote-fs.target`, so at boot the module's `.mount` (which now carries that mount point) is started directly. It can hold the boot for up to its 30 s mount timeout, and fails when the home server is unreachable. The changes: - Step 2 now says so, and says why step 5 follows soon after. - Step 3 checks a reboot that waits while the line stands. - Step 5 says that from the next boot only an access mounts the share. `merge-check.sh` passes locally. Not to be merged before review.
mesh-admin added 1 commit 2026-10-08 19:14:44 +00:00
Design 52: say the workstation's fstab line still mounts at boot until it is adopted, and can hold the boot 30 s
mesh/delivery-group group fix/shares-review-followups delivered: every member is delivered
Details
mesh/delivery delivered
Details
mesh/merge-gate pass: the change touches no module of the mesh's graph
Details
mesh/repo-check pass: its merge-check.sh passed
Details
4dd52cace6
mesh-admin commented 2026-10-08 19:14:54 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/hq@4dd52cace6fb — delivered since 2026-10-08T19:37:16Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Group fix/shares-review-followups, in order: novox/hq@4dd52cace6 → novox/mesh-controller@5d7d8ee2d6 → novox/mesh-catalog@68b158d523 → novox/mesh-host@fedd9dcf35

Transitions

  • 2026-10-08 19:14 (new) → proposed (announced): novox/hq#229's head announced
  • 2026-10-08 19:15 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 19:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 19:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 19:37 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@4dd52cace6fb` — **delivered** since 2026-10-08T19:37:16Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `fix/shares-review-followups`, in order: novox/hq@4dd52cace6fb → novox/mesh-controller@5d7d8ee2d64c → novox/mesh-catalog@68b158d5238f → novox/mesh-host@fedd9dcf350e - novox/mesh-controller@5d7d8ee2d64c before novox/mesh-catalog@68b158d5238f: built by - novox/mesh-controller@5d7d8ee2d64c before novox/mesh-host@fedd9dcf350e: built by, over engine before controller - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-08 19:14 (new) → proposed (announced): novox/hq#229's head announced - 2026-10-08 19:15 proposed → checked (checked): the verdict names this commit - 2026-10-08 19:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 19:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 19:37 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin merged commit a1c85c6de5 into main 2026-10-08 19:37:04 +00:00
mesh-admin deleted branch fix/shares-review-followups 2026-10-08 19:37:04 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#229