You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote a filesystem layout spec for image-based systems, the Dualayer Hierarchy Standard (DHS 1.1), and it has a working reference implementation: Zainium OS, an independent distro that boots and runs with this layout today. I'm not asking anyone to adopt it. I'd like feedback from people who work on image-based Linux, especially on how it relates to UAPI.9 (Linux File System Hierarchy).
In short:
no /usr, /etc or /bin at the root; the system lives in /overlayer
three layers with one owner each: the vendor base, what the user installs, and the boot files, joined with OverlayFS at boot
the base is sealed with fs-verity and updated as one unit, with rollback
musl and glibc side by side, each with its own loader, libraries and toolchain in a directory named after its target triplet
FHS software works through build-time path rewriting and run-time path resolution
Where it differs from UAPI.9:
UAPI.9 keeps one /usr for the vendor and uses multiarch tuples for architectures. DHS instead splits the vendor's files and the user's installed software into separate layers, and covers something UAPI.9 doesn't: two C libraries on one system. It also tries to answer the question in #220 (where third-party software goes) with a layer of its own.
Known weak points: one implementation so far, no /usr at the root means every package has to be adapted, statically linked programs that hardcode /usr, and the sealed overlay needs a small OverlayFS patch that isn't upstream yet.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I wrote a filesystem layout spec for image-based systems, the Dualayer Hierarchy Standard (DHS 1.1), and it has a working reference implementation: Zainium OS, an independent distro that boots and runs with this layout today. I'm not asking anyone to adopt it. I'd like feedback from people who work on image-based Linux, especially on how it relates to UAPI.9 (Linux File System Hierarchy).
In short:
Where it differs from UAPI.9:
UAPI.9 keeps one /usr for the vendor and uses multiarch tuples for architectures. DHS instead splits the vendor's files and the user's installed software into separate layers, and covers something UAPI.9 doesn't: two C libraries on one system. It also tries to answer the question in #220 (where third-party software goes) with a layer of its own.
Known weak points: one implementation so far, no /usr at the root means every package has to be adapted, statically linked programs that hardcode /usr, and the sealed overlay needs a small OverlayFS patch that isn't upstream yet.
Questions:
Spec: https://zainiumdynamics.tech/dhs
Reference implementation: https://zainiumdynamics.tech
Source: https://github.com/Zainium-Dynamics/dualayer-hierarchy-standard
DOI: https://doi.org/10.5281/zenodo.24283743
Thanks,
Ali Zain
All reactions