rust_os
An experimental operating system kernel written in Rust, featuring a custom object-based syscall API and kernel-provided window manager.
What is rust_os?
Tifflin is an experimental operating system kernel written in Rust, designed to be architecture-independent and non-POSIX. It features a custom object-based syscall API, a kernel-provided window manager, and clear separation between userland and kernel duties. The project explores modern OS design with a focus on safety and modularity using Rust's memory safety features.
Systems programmers, OS researchers, and Rust enthusiasts interested in kernel development, operating system design, and experimental non-POSIX architectures. It is suited for those exploring alternative OS paradigms or learning low-level systems programming in a modern language.
Developers choose Tifflin for its experimental approach to OS design, leveraging Rust's safety features to build a secure and modular kernel. Its unique selling points include a custom object-based syscall API, built-in window manager, and clear user-kernel separation, offering a fresh alternative to traditional POSIX-compliant kernels.
Overview
An OS kernel written in rust. Non POSIX
Use Cases
Best For
- Learning operating system kernel development in Rust
- Experimenting with non-POSIX kernel architectures
- Building custom OSes with integrated graphical interfaces
- Researching object-based syscall APIs
- Developing architecture-independent kernel components
- Exploring user-kernel separation models in modern OS design
Not Ideal For
- Projects requiring POSIX compatibility to run standard Unix/Linux software
- Production environments needing stable, well-documented kernel APIs
- Developers seeking a turnkey OS with extensive hardware driver support
- Educational courses focused on traditional operating systems like Linux or Windows kernels
Pros & Cons
Pros
Supports module loading with dependency resolution during runtime, enabling flexible kernel extensions without recompilation, as highlighted in the design features.
Userland owns the ELF loader while the kernel uses a custom format for init, enforcing a clean boundary of duties to improve security and maintainability.
Provides a structured, object-oriented system call interface for kernel interactions, offering a safer and more organized alternative to traditional POSIX syscalls.
Includes a kernel-provided window manager for built-in GUI support, similar to early Windows architectures, reducing reliance on external components.
Cons
The design is ad-hoc ("designed as I go along"), and experimental features like armv7 support crash in userland, making it unreliable for serious deployment.
Requires numerous tools like nasm, cross-compiled binutils, GCC for ACPICA, and qemu configurations, which can be daunting and time-consuming to configure.
As a non-POSIX kernel, it lacks compatibility with existing applications, forcing developers to build all software from scratch using custom APIs.
The README is brief and lacks detailed API references or comprehensive guides, hindering ease of use and learning beyond basic features.
Frequently Asked Questions
Related Projects
tockA secure embedded operating system for microcontrollers
asterinasAsterinas aims to be a production-grade Linux alternative—memory safe, high-performance, and more.
TheseusTheseus is a modern OS written from scratch in Rust that explores 𝐢𝐧𝐭𝐫𝐚𝐥𝐢𝐧𝐠𝐮𝐚𝐥 𝐝𝐞𝐬𝐢𝐠𝐧: closing the semantic gap between compiler and hardware by maximally leveraging the power of language safety and affine types. Theseus aims to shift OS responsibilities like resource management into the compiler.
moss-kernelRust Linux-compatible kernel
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.