# Inspect Den With The System Manager This tutorial shows how to inspect the staged Den rootfs with the `den` command. You will build the rootfs, check the active generation, run the health checks, and print the first update plan. The commands operate on `build/rootfs`. They do not modify host boot settings. ## Build The Rootfs Start with the rootfs smoke. This consumes the configured Den package channel, stages the runtime prefix, stages generation 1, records generation metadata, and runs userland checks. ```bash ct run smoke ``` ## Check The System Status Run `den status` against the staged rootfs: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs status ``` The output summarizes: - the Den release metadata, - the active generation, - the runtime prefix under `/opt/den`, - the system prefix under `/den/generations/1/sw`, - configured channels, - boot artifact metadata, - whether the active generation validates. ## Run The Health Checks Run `den doctor`: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs doctor ``` Diagnostics use three statuses: ```text ok warn fail ``` Warnings are expected for some image states. For example, SSH host keys may be created at first boot rather than baked into the image. ## Inspect Generations Print the current generation: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs generations current ``` List available generations: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs generations list ``` Validate generation 1: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs generations validate 1 ``` ## Print An Update Plan Print the dry-run transaction plan: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs update --dry-run ``` This reports the next generation number and the target install prefix. It does not create `/den/generations/2`, change `/den/current-system`, or install packages. ## Check Operational State Inspect channels and image state: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs channels list build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs seed status build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs ssh keys build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs boot status ``` These commands do not mutate the rootfs. `seed status` and `ssh keys` may show first-boot state that is intentionally absent from a freshly assembled image. ## What You Have At the end of this tutorial, `den` is acting as the first user-facing Den system manager. It provides status, diagnostics, dry-run planning, archive-based updates, activation, rollback, generation diffs, pruning plans, channel edits, and focused boot/seed/SSH inspection commands.