# Filesystem Layout This page describes the staged rootfs under `build/rootfs` and the equivalent paths inside a running Den system. ## Runtime Prefix ```text /opt/den ``` The runtime prefix contains conda tooling used to solve, install, archive, and manage Den workspaces. ## System Generations ```text /den/generations//sw ``` Each generation is a locked conda environment installed at its final runtime prefix. The current prototype records generation 1 at: ```text /den/generations/1/sw ``` ## Active Generation ```text /den/current-system ``` This is a relative symlink to the selected generation directory: ```text generations/1 ``` At boot, Den also exposes: ```text /run/current-system ``` Root-level compatibility paths generally point through `/run/current-system/sw`. ## Generation Metadata ```text /den/generations//metadata/conda.toml /den/generations//metadata/conda.lock /den/generations//metadata/generation.toml /den/generations//metadata/packages.txt ``` This is the current generation receipt format. See [Generation Receipt Reference](generation-receipts.md) for the fields and planned extensions. ## Init ```text /init /sbin/init ``` Both paths point into the active generation's `den-stage1` package. ## Rootfs Layout Manifests Den packages install rootfs layout metadata under the generation prefix: ```text /run/current-system/sw/share/den/rootfs-links.d/*.links /run/current-system/sw/share/den/rootfs-files.d/*/rootfs /run/current-system/sw/share/den/rootfs-files.d/*/modes ``` The rootfs builder applies these manifests to create files and symlinks outside the conda prefix. ## Dynamic Loader Compatibility For the current Linux targets, conda-forge binaries expect dynamic loaders in root-level compatibility paths: ```text /lib/ld-linux-aarch64.so.1 /lib64/ld-linux-x86-64.so.2 ``` `sysroot_linux-aarch64` and `sysroot_linux-64` supply those loaders inside the generation. The rootfs contains compatibility links so early conda executables can run before the full userspace is established.