# Check Den Status And Plan Updates Use `den` when you need to inspect a Den rootfs or image without changing it. ## Check A Running Den System Inside a Den system: ```bash den status den doctor den generations current den generations list den update --dry-run den channels list den seed status den ssh keys den boot status ``` `den doctor` exits with status code `1` if it finds a critical failure. Warnings are printed but do not make the command fail. ## Check A Staged Rootfs From the repository root: ```bash build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs status build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs doctor build/rootfs/den/generations/1/sw/usr/lib/den/den --root build/rootfs update --dry-run ``` The `--root` option points `den` at a mounted or staged filesystem tree. Absolute paths in the output still describe the paths as they would appear inside the Den machine. ## Install From A Workspace Archive `den update` expects an existing conda workspace archive. In the repository workflow, `ct run workspace-archive` creates `build/den-workspace.tar.zst`. Inside a running Den system: ```bash den update --archive /var/cache/den/den-workspace.tar.zst ``` The update command uses `/var/cache/den/pkgs` as conda's package cache. It replaces an inherited `/opt/den/pkgs` setting, while preserving an explicitly different `CONDA_PKGS_DIRS`. Keep that cache on a Linux filesystem when testing from macOS bind mounts so conda package verification sees the same file layout it will see in a real image. The archive install runs through the public conda-workspaces `WorkspaceArchive` API in the Den runtime environment. For a mounted or staged rootfs, run the command inside a compatible target environment or container. The local smoke target does this for the Linux/AArch64 rootfs: ```bash ct run generation-smoke ``` Use `--no-activate` to install and validate the next generation without switching `/den/current-system`. ## Check The OCI Inspection Image Build and smoke-test the local OCI image: ```bash ct run oci-smoke ``` The smoke target checks: - `den status`, - `den doctor`, - `den generations current`, - `den update --dry-run`, - `den channels list`, - `den seed status`, - `den ssh keys`, - `den boot status`, - `den prune --keep 1`, - `conda den --help`, - the conda runtime configuration. ## Use The Conda Plugin Form The runtime prefix also installs `den` as a conda plugin: ```bash conda den --help ``` Use the top-level `den` command inside a running or mounted Den image. Use `conda den` when you are already working through conda and want the same command surface.