mesh-host

Files

T

jochen 3a002f6e7b

mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check fail: its merge-check.sh failed: --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s)

Details

mesh/delivery superseded: a newer head of the same pull request

Details

Refuse a placement or mount at the machine's own trees, and use a found directory as found

A module's places setting could point a directory anywhere, with an owner it
named, and the engine chowned and chmodded whatever it was pointed at as root,
through a link too; its accesses setting could mount any path into a container
(hq issue 339). The engine now refuses, as a failed resource with its reason,
a directory, access or mount source that is or holds one of the machine's
roots, anything placed in the kernel's, the boot loader's, root's or the
engine's own trees, a non-root directory below /etc, /usr or /run, an access
there, another account's directory below a home, and a container mounting
anything it refused, judged with every link resolved. A directory whose last
component is a link is refused, and one found here that the mesh did not make
keeps its owner and mode and is never removed.

2026-10-08 23:58:14 +02:00

declared_test.go

A node that loses its mesh comes back on its own

2026-08-29 20:17:49 +02:00

declared.go

Refuse a declaration for the other mode, or older than the mesh's last, and say what an apply would change first

2026-09-23 23:15:28 +02:00

former_test.go

A take is a comparison: the host's facts, former targets, and strays (hq ADR 0163)

2026-10-01 21:24:37 +02:00

lock_test.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode