Independent operating-system project

Two kernels. Built from scratch.

I started JefeOS to see how far one person and AI collaborators could take a new operating system. The answer now includes bootable C++ and Rust kernels, their own userspace, networking, filesystems, and a growing Linux compatibility layer.

Choose a kernel

The C++ release is ahead; the Rust release matches the frozen 1.0 baseline.

C++ kernel · current release

JefeOS 1.1.2

The current C++ release includes a shell, experimental framebuffer desktop, network stack, SSH, NTFS read/write, and a WSL1-style Linux ABI layer. Version 1.1.2 is a focused user/kernel-boundary hotfix.

Verify this release
SHA-256
b6efbf4ead7fb4a69a77f2ae2ad489c7509e0db54a3fc4c57cd6edb0fb2bc2df
Checksum
jefeos-1.1.2.iso.sha256
Release commit
18f99039d22d3a640fb00276900a7783ca02413b
Tag
v1.1.2 · private source repository
Gate
Jenkins App-Runs Gate #5 · GREEN
Boot it in a VM

The ISO runs live; there is no installer. Use QEMU, Hyper-V Generation 1, or VirtualBox.

qemu-system-x86_64 -cdrom jefeos-1.1.2.iso -m 512

At the shell, try help or version.

Get the examples disk

The optional VHD provides an NTFS root filesystem, native programs under /programs, and test fixtures.

Download examples archive · 1.9 MB ZIP →

SHA-256
3f289e2a64bf4d72d8483e069f542cf1fdb6eddc24d87f2237a44564e1d3e8ae
Build guide
Build programs for JefeOS
qemu-system-x86_64 -cdrom jefeos-1.1.2.iso -drive file=jefeos-examples.vhd,format=raw,if=ide -m 512

For Hyper-V, extract the VHD, attach it at IDE 0:0, and add a Legacy Network Adapter if you want networking.

Rust kernel · baseline release

JefeRust 1.0.0

An independent kernel with its own boot path, memory manager, scheduler, drivers, filesystems, networking, shell, and userspace. It implements all 55 features frozen at the JefeOS 1.0 baseline, not everything on current C++ master.

Verify this release
SHA-256
777391232a5fe42e80ef19b71ab869fdebe555dc24983561868477f3a65f158b
Checksum
jeferust-1.0.0.iso.sha256
Source
1273bcbabf63058b5087a2c3689272e1b711f1f5
Tag
jeferust-1.0.0 · private source repository
Boot it in a VM

Use QEMU or a Hyper-V Generation 1 VM with 1 GiB of memory.

qemu-system-x86_64 -cdrom jeferust-1.0.0.iso -m 1024

JefeRust 1.0 includes experimental in-kernel framebuffer work, but a functional GUI was not a 1.0 release goal or runtime gate.

Get userspace examples and bot source

Userspace examples · 358 KB →

SHA-256
7b703d52ae176b4083a81d4afcd46d53b69b408c4706e6798b5ad36b485b7a15
Checksum
Examples checksum
Source
1273bcbabf63058b5087a2c3689272e1b711f1f5

Extract the archive, verify JefeRust's SSH fingerprint from its trusted console, then run .\install.ps1 -Target <address> -HostKey 'SHA256:...' with PuTTY psftp available. Do not attach the JefeOS NTFS examples VHD as JefeRust's first disk: JefeRust may format an unrecognized first disk and destroy its contents.

Sanitized Node bot source · 63 KB →

SHA-256
af28ce668e459c3ddee07f4a85feeff7576f7e204a022bcfe9a490effa236da0
Checksum
Bot source checksum
Terms
The copyright owner publishes this source for inspection and direct use under the included UNLICENSED and private: true package terms; no downstream redistribution license is granted.
Dependency
Exact ws 8.21.0 pin; bring your own configuration and credentials.
Technical snapshotA concise view of the shipped foundation.
  • Ring-3 userspace, ELF64 loading, preemptive scheduling, per-process address spaces, and each kernel's own libc.
  • Ethernet through TCP, DNS, DHCP, TLS 1.3, SSH/SFTP, and HTTP/S clients.
  • NTFS read/write and FAT32 read-only on JefeOS; JefeFS and storage support in the separate Rust implementation.
  • Linux syscall translation capable of running selected static and dynamic Linux binaries.
  • A real Node.js bot workload has run under JefeOS with Xylem supervision.

See the detailed status and test evidence →

Where are the rough edges?This is a working hobby OS, not a general-purpose replacement.

SMP, complete POSIX coverage, and full Alpine boot remain unfinished. JefeRust 1.0 matches the frozen JefeOS 1.0 feature baseline; it does not claim parity with newer C++ work. The source repositories are private.

See what is shipped, active, and planned →

What is Xylem?The longer bet: move workload supervision into the OS.

Xylem is the project's clustered-OS direction. Both kernels now have membership and failure detection. The C++ kernel also has a Service object with local reconciliation and a stateless, deterministic-primary singleton failover primitive. Fenced production-workload failover, Rust service parity, migration, and durable distributed state remain open.

Read the Xylem whitepaper →

Go deeperThe detail belongs on the pages built for it.