Layering And ABI Boundary¶
Den deliberately separates the early boot ABI from the conda system ABI.
Why There Are Two Layers¶
Linux needs something to run before the conda system exists. It needs a kernel, an initramfs, device setup, a root mount, and a handoff. Buildroot is good at that job. It can produce a small, static early boot layer.
Conda is good at a different job: describing, solving, locking, distributing, and installing a userspace package graph.
Den keeps those jobs separate.
Buildroot Owns The Early Boot ABI¶
The early boot layer is musl/static where possible. It owns:
the kernel,
BusyBox,
the initramfs,
early mounts,
root device discovery,
switch_root,emergency shell behavior.
It should not accumulate general userland packages. Every package added to Buildroot is a package not governed by the conda system package graph.
Conda Owns The System ABI¶
The current conda system generation is glibc-based because conda-forge Linux executables expect that ABI.
For example, many executables expect:
/lib/ld-linux-aarch64.so.1
/lib64/ld-linux-x86-64.so.2
The target sysroot package supplies that loader inside the conda generation. Den projects root-level compatibility links so early binaries can run.
The Rootfs Layout Boundary¶
Rootfs layout manifests bridge the layers:
share/den/rootfs-links.d/*.links
share/den/rootfs-files.d/*/rootfs
The package owns the request. The rootfs builder owns applying it.
That distinction matters. It avoids teaching conda packages to own /
directly, and it keeps rootfs policy auditable in package metadata.
Why Not Put Everything In Buildroot¶
Putting systemd, shells, OpenSSH, coreutils, and Den tools into Buildroot would be simpler in the short term, but it would erase the experiment. Den is only interesting if the system userland comes from conda.
Buildroot is the early boot layer. Conda is the operating system layer.