Redox (operating system)

Redox (operating system)
Name	Redox
Developer	The Redox Project
Released	2016
Latest release	(see project)
Programming language	Rust
Kernel type	Microkernel (inspirational)
License	MIT and Apache-2.0
Website	(project homepage)

Redox (operating system) is a Unix-like operating system implemented primarily in Rust (programming language), aiming to provide memory safety, modern architecture, and a microkernel-inspired design. It draws influence from Unix, Plan 9 from Bell Labs, Minix, and seL4, while engaging communities around Linux kernel, FreeBSD, NetBSD, and OpenBSD for interoperability and tooling. Redox targets developers interested in systems programming, security research, and projects associated with GitHub, Mozilla Foundation, and The Linux Foundation ecosystems.

History

Redox began as an independent project in the mid-2010s with roots in discussions among contributors active in Rust Foundation, Mozilla Corporation, LLVM Project, and Wikimedia Foundation communities, responding to work on Memory safety and incidents like the Heartbleed and Spectre disclosures. Early development paralleled experiments from Minix 3, GNU Hurd, and academic systems such as Singularity (operating system), while leveraging tools from Cargo (software), Clippy, and rustc compilers. The project advanced through contributions by volunteers distributed via GitHub, coordinated with continuous integration practices inspired by Travis CI, GitLab CI, and CircleCI, and achieved initial public releases and demonstrations at events alongside FOSDEM, RustConf, and Linux Plumbers Conference.

Design and Architecture

Redox's architecture emphasizes microkernel principles influenced by seL4 and L4 microkernel family while adopting modern language-level safety from Rust (programming language). The operating system models concepts familiar to Unix, Plan 9 from Bell Labs, and GNU Project users but reimagines userland with components analogous to systemd, init (System V), and launchd replaced by Rust-based services. Its componentization echoes designs from QNX, Minix, and haiku (operating system), with inter-process communication patterns reminiscent of Mach (kernel) and service architectures seen in Kubernetes, Docker, and Flatpak workflows. Filesystem and device abstractions reflect ideas from FUSE, 9P protocol, and ZFS concepts.

Kernel and Microkernel Features

The kernel integrates microkernel-inspired features including capability-based security influenced by seL4 research, IPC mechanisms comparable to Mach (kernel), and privilege separation similar to Windows NT architecture. Scheduling and concurrency borrow concepts from POSIX threads models and academic schedulers such as those evaluated in Erlang and Go (programming language) runtime discussions, while aiming to interface with drivers and services akin to Linux kernel modules and FreeBSD kexts. Formal verification efforts in other projects like seL4 and CompCert inform Redox's emphasis on correctness, while tooling from LLVM Project and clang supports low-level components.

Memory Management and Safety

Memory management relies on language guarantees from Rust (programming language)—ownership, borrowing, and lifetimes—aiming to prevent classes of bugs highlighted by Heartbleed and Meltdown disclosures and studied in Computer security research by groups at MIT, Stanford University, and UC Berkeley. The design reduces reliance on manual memory reclamation approaches common in C (programming language)-based kernels such as Linux kernel and FreeBSD, while still addressing low-level requirements handled by projects like LLVM Project and Valgrind. Redox's safety model benefits from static analysis concepts promoted by Coverity and dynamic instrumentation approaches used in AddressSanitizer and MemorySanitizer.

Filesystem and Storage

Redox implements its own filesystem layer inspired by ideas in Plan 9 from Bell Labs and protocols like 9P protocol, while examining journaling and copy-on-write techniques seen in ZFS, Btrfs, and APFS. It integrates filesystem abstractions analogous to FUSE to enable userland filesystem modules and considers persistent storage strategies explored in LevelDB, RocksDB, and SQLite (software). Storage management design takes lessons from enterprise systems such as Ceph and GlusterFS and desktop designs informed by GNOME and KDE storage APIs.

Device Drivers and Hardware Support

Device support in Redox is evolving, with drivers written to interface with hardware using conventions from PCI Express, ACPI, UEFI, and BIOS specifications, and leveraging development practices common to Linux kernel and FreeBSD driver ecosystems. Community efforts adapt drivers from projects like NetBSD portability layers and use virtualization support compatible with QEMU, VirtualBox, and KVM for testing. Integration with hardware vendors and standards bodies such as Intel, AMD, ARM Limited, and PCI-SIG guides compatibility priorities.

Applications and Ecosystem

The userland includes Rust-based utilities and graphical components influenced by X.Org, Wayland, GTK, and Qt toolkits, alongside package and build tooling models from Cargo (software), Make (software), GNU Autotools, and CMake. The ecosystem interoperates with development workflows on GitHub, GitLab, and Bitbucket, and benefits from CI/CD patterns established by Travis CI and Jenkins. Projects and contributors from academic and industrial institutions such as Mozilla Foundation, Microsoft Research, Google Research, and university labs contribute to tooling, testing, and research that inform Redox's roadmap.

Category:Operating systems