Skip to content
@EmiBSD

EmiBSD

An operating system in Rust: the OpenBSD kernel ported file by file, then redesigned with zero unsafe as the goal. Pre-alpha.

Ferffy, the EmiBSD mascot: a centolla, drawn in line art

EmiBSD

A port of the OpenBSD -current kernel to Rust. An operating system in Rust, grown from the faithful port of the OpenBSD kernel: the same system-call ABI, so OpenBSD's own userland runs on it unmodified, and inside, a kernel rebuilt subsystem by subsystem with zero unsafe as the goal.

Pre-alpha. EmiBSD boots only in QEMU, on arm64. Its crypto, network and storage code is unaudited. Do not use it for anything real.

Repositories

Repository What it is
LandingZone The OpenBSD kernel ported to Rust one C file at a time, keeping the C's shape so every file can be checked against its origin. Fidelity first.
Kernel The redesign: what LandingZone ported, rebuilt with Rust's ownership in place of C's conventions. Crates kernel and abi are #![forbid(unsafe_code)]; only hal may hold unsafe, each site with a written proof.
Userland The base system above the kernel: one tree where every program, library and configuration file sits by what it does, not by where history left it. Its shape is settled; its content is at the start.
DevTools The toolchains, imported and built once from the forks alone: upstream LLVM, one compiler for the C and the backend of rustc, and a pinned stable Rust with its std for aarch64-unknown-openbsd; nothing of it from OpenBSD. Released as artifacts the other repositories consume.
OS Where the system is assembled and released: a manifest pins one commit of Kernel, Userland and DevTools; the recipes fetch them, assemble the sets and media, boot them and tag the release as YEAR.MONTH. Nothing released yet.
Website The website, www.emibsd.org.
Governance What binds the rest: the invariants every repository obeys, the process, the architecture of the repositories, the roadmap across them, the decision log and the policies.

The forks in this organisation (OpenBSD-src, rust, llvm-project, cargo) are read-only mirrors of the sources the repositories pin; nothing of ours is committed to them.

Where it stands

Milestones N0 to N4 (bootstrap, leaves, foundations, memory, processes) are met; N5, the VFS and the file systems, is under way. The Status page has every milestone, the slices of the latest one, and the unsafe count of each crate, at a named commit.

How it is built

The work is carried out by AI coding agents under fixed roles and written rules; one maintainer takes the decisions and approves every commit. The Process page explains the pipeline from the 1:1 port to the redesign; the rules themselves, and every decision that crosses repositories, are in Governance.

Links

Website · About · Contributing · Support the project · News feed

Ferffy, the mascot, is a centolla, the king crab of Chile's southern seas, the child of Ferris and Puffy. EmiBSD is an independent experiment built on OpenBSD's source code. It is not affiliated with or endorsed by the OpenBSD project. New code is ISC; files derived from OpenBSD keep their original licence notices, whole.

Popular repositories Loading

  1. Kernel Kernel Public

    An operating system in Rust, grown from the faithful port of the OpenBSD kernel

    Rust 3

  2. LandingZone LandingZone Public

    The OpenBSD kernel, re-implemented in Rust, one file at a time: the landing zone

    Rust 1

  3. Website Website Public

    CSS 1

  4. Userland Userland Public

    EmiBSD's own userland: the programs, libraries and configuration above the Kernel, written from scratch in Rust

    C 1

  5. rust-osdev-homepage rust-osdev-homepage Public

    Forked from rust-osdev/homepage

    CSS 1

  6. OS OS Public

    Python 1

Repositories

Showing 10 of 16 repositories

Top languages

Loading…

Most used topics

Loading…