8df2129c39
The settings dialog used gdk_monitor_get_model() which often returns NULL, generating invalid property paths. The main daemon uses xfw_monitor_get_connector(), causing a mismatch that prevented wallpaper changes. Fix by using GDK APIs to obtain a valid monitor model name, aligning with the daemon's identification logic. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| book | ||
| distro | ||
| kernel | ||
| osdk | ||
| ostd | ||
| test | ||
| tools | ||
| .code-workspace | ||
| .dockerignore | ||
| .gitignore | ||
| .licenserc.yaml | ||
| .typos.toml | ||
| CODEOWNERS | ||
| COPYRIGHT | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Components.toml | ||
| DOCKER_IMAGE_VERSION | ||
| LICENSE-MPL | ||
| Makefile | ||
| OSDK.toml | ||
| README.md | ||
| README_CN.md | ||
| README_JP.md | ||
| RELEASES.md | ||
| VERSION | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| triagebot.toml | ||
README.md
A secure, fast, and general-purpose OS kernel written in Rust and compatible with Linux
News:
- 2025-12-08: FAST 2026 accepted a paper on a novel secure storage solution having been integrated into Asterinas: MlsDisk: Trusted Block Storage for TEEs Based on Layered Secure Logging.
- 2025-10-17: ICSE 2026 accepted yet another paper about Asterinas: RusyFuzz: Unhandled Exception Guided Fuzzing for Rust OS Kernel.
- 2025-10-14: CortenMM: Efficient Memory Management with Strong Correctness Guarantees received the Best Paper Award at SOSP 2025.
- 2025-07-23: SOSP 2025 accepted another Asterinas paper: CortenMM: Efficient Memory Management with Strong Correctness Guarantees.
- 2025-06-18: USENIX ;login: magazine published Asterinas: A Rust-Based Framekernel to Reimagine Linux in the 2020s.
- 2025-04-30: USENIX ATC 2025 accepted two Asterinas papers:
Congratulations to the Asterinas community🎉🎉🎉
Introducing Asterinas
Asterinas is a secure, fast, and general-purpose OS kernel that provides Linux-compatible ABI. It can serve as a seamless replacement for Linux while enhancing memory safety and developer friendliness.
-
Asterinas prioritizes memory safety by employing Rust as its sole programming language and limiting the use of unsafe Rust to a clearly defined and minimal Trusted Computing Base (TCB). This innovative approach, known as the framekernel architecture, establishes Asterinas as a more secure and dependable kernel option.
-
Asterinas surpasses Linux in terms of developer friendliness. It empowers kernel developers to (1) utilize the more productive Rust programming language, (2) leverage a purpose-built toolkit called OSDK to streamline their workflows, and (3) choose between releasing their kernel modules as open source or keeping them proprietary, thanks to the flexibility offered by MPL.
While the journey towards a production-grade OS kernel is challenging, we are steadfastly progressing towards this goal. Over the course of 2024, we significantly enhanced Asterinas's maturity, as detailed in our end-year report. By the end of 2025, we plan to launch Asterinas NixOS, the first distribution for Asterinas. This release will mark Asterinas reaching the Minimum Viable Product (MVP) milestone. In 2026, we aim to make Asterinas production-ready on x86-64 virtual machines and attract real users.
Getting Started
Get yourself an x86-64 Linux machine with Docker installed. Follow the three simple steps below to get Asterinas up and running.
- Download the latest source code.
git clone https://github.com/asterinas/asterinas
- Run a Docker container as the development environment.
docker run -it --privileged --network=host -v /dev:/dev -v $(pwd)/asterinas:/root/asterinas asterinas/asterinas:0.16.2-20251211
- Inside the container, go to the project folder to build and run Asterinas.
make kernel
make run_kernel
If everything goes well, Asterinas is now up and running inside a VM.
The Book
See The Asterinas Book to learn more about the project.
License
Asterinas's source code and documentation primarily use the Mozilla Public License (MPL), Version 2.0. Select components are under more permissive licenses, detailed here. For the rationales behind the choice of MPL, see here.