fungOSInstall and first boot
Start with an isolated QEMU guest on a Linux KVM host. The public fungOS repository contains the generic rootfs builder; boot assembly and secure enrollment are separate integration steps. There is no public ready-to-flash installer image in this slice.
Choose a target
| Target | Starting point | Remaining work |
|---|---|---|
| Existing Linux/macOS machine | Mycelium on the existing OS | This enrolls a host; it does not install fungOS |
| QEMU/KVM | Generic rootfs plus matching boot components | Persistent disk, kernel/initramfs, enrollment and signed applications |
| Raspberry Pi | arm64 rootfs | Board firmware, kernel/modules, disk assembly and hardware qualification |
| Cloud VM | Cloud rootfs profile | Provider boot image and provisioning integration |
Mycelium owns machine identity and service/update policy. Genesis owns bootstrap/disk provisioning where used. Unibus owns application transport. The distribution should not replace these owners with a parallel implementation.
First boot runbook
- Build and inspect the chosen runtime profile on a Linux build host.
- Assemble a new persistent boot target with a matching kernel and public recovery SSH key. Never clone another enrolled machine's private identity.
- Install one first-contact adapter. Provide its machine-specific claim through an owner-only, protected single-use channel.
- Boot and verify enrollment independently from Linux startup. A successful boot is not evidence that a claim was redeemed.
- Remove consumed claim media and plaintext bootstrap logs; retain the persistent root disk.
- Install signed application packages and local service bindings using the chosen activation owner.
- Configure explicit update policy, verify application-owned readiness and reboot without the claim media.
The generic first-contact adapter receives an environment file path, not embedded authority. A Mycelium adapter consumes an owner-only claim file. Do not deliver a secret through TFTP, public iPXE text or kernel arguments.
Verify the installed guest
Run these only where the corresponding Mycelium CLI and edge bindings are installed:
mycelium node status --json
mycelium software reconcile --dry-run --json
mycelium update policy status --json
systemctl is-active mycelium mycelium-update.timer
# Display-edge bindings:
systemctl is-active unibus-router canvas-compositor canvas canvas-edge
Compare enrolled-certificate, machine-ID and SSH-host-public-key hashes before and after reboot. Inspect the actual framebuffer as well as the native units. A healthy service process is not proof of visible scanout.
What has been qualified
The public docs/edge-dogfood.md records an amd64 persistent QEMU edge boot on 8 October 2026: enrolled identity retained, Canvas wallpaper/workspace retained through restart and reboot, and same-version Unibus service repair. Its update runner selected no new release; this is not evidence of an upgrade.
The separate offline visual rollback fixture records recovery from signed failing Canvas and Unibus candidates. It is not a procedure to run on a personal machine or fleet node. See updates for scope.
Recovery
Inspect failed units and their journals. Preserve the previous verified artifact and a public-key SSH recovery route. Correct service or network drift without re-enrolling an otherwise healthy identity. Check certificate names rather than bypassing TLS verification.
Do not infer Pi hardware readiness, fresh PXE enrollment, encrypted-root unlock, GPU passthrough or TV media delivery from the QEMU test. Sources: public fungOS README.md, base/interfaces.md, docs/edge-dogfood.md.