Skip to content

Requests for Comments

Design stage Project PyrixOS Process RFC first

PyrixOS is designed before it is built. Every component, interface and file format is first proposed in a numbered RFC, discussed in public, and accepted or revised. Implementation of a component starts only once its RFC is accepted, and an accepted RFC is the reference against which that implementation is reviewed and tested.

RFC Title Status Covers
0001 PyrixOS Architecture Draft PyBonsai language, derivations, build sandbox, immutable store, dependency database, garbage collector, profiles and stacks, binary caches, measurement
0002 Bootstrap Draft Binary seed fetched by digest, unpack, stage builds of the toolchain from source, rebuilding and checking the seed
0003 Configuration System Draft Trellis: Kconfig subset, encoding into clauses, resolution, explanations of conflicts, defconfig and config.pyb
0004 System Configuration Draft A whole machine in PyBonsai: users, file systems, services, /etc, boot entries, config.pyb, activation and lattice switch
0005 Package Set and Images Draft The package set in layers, the standard environment, the packages of 1.0, Rust from mrustc as an option, disk and installer images, and the public cache
0006 Architectures, Images and Boot Draft RISC-V 64 and ARM64 through the ARCH option, ISO, network boot, virtual machine and WSL images, and systemd-boot, GRUB and U-Boot

Read RFC 0001 Introduction to PyrixOS

Status values

Status Meaning
Draft Open for comment. The design may still change in any part.
Accepted The design is agreed. Implementation may begin, and later changes need a new RFC or an amendment.
Implemented The accepted design has been built and its tests pass.
Superseded Replaced by a later RFC, which is named in the RFC header.

Commenting

Comments on an RFC in Draft are made through issues on the PyrixOS repository, with the RFC number and section in the title, for example RFC 0001 ยง9.2 sandbox /proc mount. Proposals for a new RFC follow the structure of RFC 0001: summary, motivation, goals and non-goals, specification, security considerations, alternatives and open questions.