As part of our mission statement, we first want “to build modern, ergonomic and high-performance tooling and infrastructure for distribution engineering.”
Simply put, we are building the tooling and infrastructure that will deliver, as an output, “an atomic operating system that is fast, predictable, reliable and a joy to use and maintain.”
Rather than relying entirely on existing distribution tooling, we are developing our own tools in-house, primarily in Rust.
By taking a ground up approach, we are able to build the focused tooling we want and need to deliver the type of atomic distribution we want without any prior technical debt.
The code is therefore focused, maintainable and efficient leading to a better experience for our developers and eventually a better user experience also.
Our primary tooling that make the foundation of aerynOS:
moss - Package and System State Manager
moss manages the installation and removal of software through atomic transactions. Behind moss we have a deduplicated content-addressable store (CAS) that enables files to be shared between system states (transactions) which in turn enables aerynOS to store as many previous system states for easy rollbacks as free disk space allows.
Learn more about moss
boulder - Package Building
boulder turns YAML based package recipes into .stone packages for moss to install on aerynOS systems. It has been designed to include a consistent build environment, reusable packaging macros, dependency handling and caching to help our maintainers package and update our growing software repository.
Learn more about boulder
blsforme - Boot Management
Nobody should need to manage their boot configuration manually. That’s exactly why moss leverages the blsforme project to automatically manage the EFI System Partition (and XBOOTLDR..) and manage boot entries.
Learn more about blsforme
We are building our tools so that they work together to become more than the sum of their individual parts:
-
Our recipes repository contains the YAML based recipes that we use to describe how software is packaged for aerynOS.
-
boulder uses these recipes to build and emit .stone package archives.
-
Our build infrastructure coordinates which tasks from the centrally managed build queue are sent to which builders and in which order.
-
Once built, packages are immediately published to our volatile repository. After a period of testing, packages are then promoted to our unstable repository. The repository makes package versions and their associated metadata available to moss-based installs.
-
moss checks for available updates to the repositories it is subscribed to. When updates are available, moss will download the corresponding .stone package archives, extract them to its CAS and then create a new system state which it will swap to as part of its atomic transaction.
-
blsforme works within the wider context of an installed aerynOS system to handle boot management to ensure the system is bootable regardless of underlying updates.