v2.0.0-BETA — i386 — BSD 3-Clause
An open source hobby and research operating system for x86, built from scratch since 2002. Preemptive multitasking, virtual memory, UbixFS, TCP/IP networking, and a growing POSIX userland.
// FEATURES
Monolithic kernel with preemptive multitasking, SMP support, x86 protected mode (ring 0/3), paged virtual memory, and copy-on-write forking.
UbixFS v1/v2 (native), UFS, FAT16/32, and DevFS — all behind a unified VFS abstraction layer. ELF binary loader for standard i386 executables.
lwIP 2.0.3 TCP/IP stack with NE2000 and Lance (PCnet) NIC drivers.
Full socket layer including select(),
sendto, and BSD-compatible APIs.
AT keyboard with TTY line discipline, PIT, PIC (8259), floppy, RS-232 serial, PCI hard disk, mouse, and PCI bus enumeration.
24+ utilities, FreeBSD-derived libc, C++ runtime, runtime dynamic linker (ld.so), Tiny C Compiler, BSD shell, and a graphical SDE.
Custom MPI message passing with named mailboxes, POSIX pipes,
semaphores, and sysctl MIB for runtime kernel
introspection.
// QUICK BUILD
# Clone and build — requires bmake and an x86_64-elf cross-compiler git clone https://github.com/cwolsen7905/UbixOS.git cd UbixOS bmake # Build kernel + world bmake image # Build bootable disk image (ubixos.img) bmake run # Launch in QEMU
Full toolchain requirements and platform-specific setup in BUILDING.md
// IN ACTION
Boot / kernel screenshot coming soon
SDE / userland screenshot coming soon
// RELEASES
ls runs with full lazy PLT resolutionsched_killTreesysctl, uname, mkdir, rmdir, getenv/setenvFirst tracked release. Brought up networking (lwIP + Lance NIC), Software Display Environment, dynamic linker stub, and a working userland shell.
// ROADMAP
// COMMUNITY
Development has been active since 2002. Come see what's happened.
Originally at ubixos.com. Over two decades of kernel hacking, filesystem work, and userland building — still going.
// GET INVOLVED
Drivers, syscalls, filesystem work, userland tools — see
CONTRIBUTING.md for conventions and the PR workflow.
Architecture write-ups, driver guides, build docs. Good documentation is as valuable as code for a project like this.
Browse DocsStar the repo on GitHub and share it with OS dev communities. It's the simplest way to help the project reach more people.
Star on GitHub