Den Documentation¶
Den is a bootable Linux distribution experiment where conda owns the system package graph. Buildroot supplies a small early boot layer, then the machine switches into a conda-owned root filesystem with systemd, package generations, and rollback.
The current proven artifact path is intentionally narrow: a hosted conda channel, native Linux arm64 and amd64 image workflows, QEMU boot bundles, local OCI inspection images, and UEFI raw/qcow2 disks for QEMU. Candidate and promotion workflows now implement signed OCI images and verifiable release directories, but those remain unproven until the first public release passes. Den asks whether conda can grow from a developer-environment tool into a locked package graph for a whole operating system.
Documentation Layout¶
These docs follow the Diataxis model:
Tutorials teach by walking you through a contained learning path.
How-to guides give task-focused commands for people already oriented.
Reference records facts about commands, files, packages, and artifacts.
Explanation gives the design context and tradeoffs.
This mirrors the shape of the conda-workspaces documentation: a fast entry point, task-oriented pages, exact command/reference material, and explanation for motivation and design.
Tutorials¶
How-To Guides¶
Reference¶
Explanation¶
Current Status¶
The prototype can:
consume Den-owned conda packages built and published by
den-os/den-forge,stage a runtime prefix under
/opt/den,stage a system generation under
/den/generations/1/sw,apply boot-critical rootfs layout manifests from package metadata,
build a Buildroot kernel and initramfs early boot layer,
boot in QEMU through Den stage1,
boot packaged systemd as PID 1,
record, validate, activate, and roll back system generations,
inspect Den status and generation health with
den,print a non-mutating update plan with
den update --dry-run,install and activate a new generation from an existing workspace archive with
den update --archive,consume the hosted Den package channel at
packages.den-os.org,authenticate pushes to the zot registry at
registry.den-os.org,build and smoke-test the staged rootfs from that hosted release channel,
package the QEMU AArch64 prototype as
den-qemu-aarch64.tar.zst,model a QEMU x86_64 target for linux-64 package and image work,
build and smoke-test a local Docker/OCI image named
den:dev,expose
den sandboxexecution paths for QEMU, Docker, Podman, and Applecontainer, with signed Den release image verification before execution,build and smoke-test a GRUB-backed UEFI raw/qcow2 disk for QEMU.
The prototype still cannot:
publish a signed, mirrored, multi-region package channel,
boot through systemd-boot,
install itself onto a disk,
act as a provider-ready cloud image across real provider metadata services,
sign boot artifacts or package locks,
prove signed OCI release images and SBOM attachments end to end,
prove complete SBOM, license, source, and provenance evidence through a promoted public release,
solve, lock, and build a workspace archive directly from a running machine.