danos/system
Daniel Samson a01a4f3b3d
init: restart a crashed boot service
init supervises its boot services (spawned against an exit endpoint) but the
child-exit handler was `if (got.isNotification()) continue;` — it silently
dropped a dead service. Now init restarts it: on a child-exit notification it
finds the service, and unless it exited cleanly (chose to stop) or has hit the
crash-loop cap (maximum_restarts), respawns it and logs the death + reason. The
reincarnation half of resilience (docs/resilience.md) at the service level, the
counterpart to the device manager's driver restarts. A `shutting_down` flag
skips restarts during the orderly stop sequence, whose child deaths are expected.
2026-07-14 09:05:10 +01:00
..
devices display: framebuffer handoff primitive + service design (D1) 2026-07-14 00:54:56 +01:00
drivers fat/usb-storage: flush the device cache on close so writes survive power-off 2026-07-13 23:29:15 +01:00
kernel kernel: contain a fatal fault — name the task, release the BKL before halt 2026-07-14 09:05:10 +01:00
services init: restart a crashed boot service 2026-07-14 09:05:10 +01:00
abi.zig display: the compositor service — claim, double-buffer, present (D2) 2026-07-14 01:26:25 +01:00
boot-handoff.zig zig fmt 2026-07-12 16:04:58 +01:00
initial-ramdisk.zig Post-reorg cleanup: POSIX layer, and naming fixes 2026-07-10 13:33:06 +01:00
parameters.zig USB driver stack: xHCI transfers, HID keyboard/mouse, mass storage 2026-07-13 14:11:00 +01:00