erXos is an experimental operating system built around the idea that Erlang processes can serve as operating-system processes. Drivers, filesystems, network services and shell sessions run as Erlang processes in isolated domains, with supervision to restart failures. A small capability-based microkernel handles threads, memory, interrupts and CPU grants without knowing about Erlang; each domain runs its own Erlang runtime, and domains can communicate using Erlang’s process mechanisms. The design combines Plan 9-style private namespaces, QNX-like microkernel principles and a UNIX-style shell, while aiming to keep the machine open to live inspection and upgrades. Its security model treats authority as something explicitly granted: knowing a process ID or path alone provides no access.
The system boots on AArch64 QEMU and Raspberry Pi 4, and can also run in a browser without sending commands to a server. Its current features include Erlang-based console, network and storage drivers, a TCP/IP stack, DHCP, HTTPS, SSH, filesystems, graphics, and an Erlang-written rc shell; example applications include a kiosk and native Doom. The browser demo shows file operations, process monitoring, Erlang crashes and recovery, and thousands of concurrent processes. The project remains early: it currently runs over a modified Fiasco kernel, with its own kernel planned, and several features - including USB, Wi-Fi, Bluetooth, Raspberry Pi 5 support and native-program pipelines - are still in development. Correctness efforts include comparison with stock OTP, model checking, memory-model tests, fuzzing and sanitizers, with documented limits on what those checks establish.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.