The legacy of Pronin Software Distribution / Proninx.

FNU / OpenProninx

OpenProninx is a native x86-64 operating system under active development, with its own boot code, kernel, userspace, and QEMU disk images. It continues the PRONINX project formerly developed by Pronin Software Distribution; Foundry Tech Inc. is its successor.

The project is deliberately small and explicit about its boundary. It is not a Linux distribution, hypervisor, container runtime, cluster manager, router, or data-centre control plane. Its source is available under the permissive BSD 3-Clause License.

Development software. The current baseline is Core 0.1.6-dev. It is not production-ready and must not be exposed to an untrusted network or used for confidential data.

Current capabilities (Core 0.1.6-dev)

The system starts PSH, the local interactive shell, across 4 Virtual Terminals. The hybrid GPT boot image is fully self-contained — booting identically on legacy BIOS and modern UEFI firmware. Native programs include ls, cat, cp, wc, top, pwd, mkdir, chmod, chown, ping, netinfo, resolve, fbset, fnufetch, and filesystem tests.

Dual BIOS & UEFI boot chain with hybrid GPT partitioning (ESP + fnu-boot + fnu-root).
4 Virtual Terminals (struct vt) switchable via CTRL + ALT + F1..F4 (/dev/tty1..4, /dev/console).
OpenBSD Spleen bitmap fonts (5x8, 8x16, 12x24, 16x32) with automatic width-based selection.
Hardware block drivers: AHCI SATA (spec 10.1.2), NVMe 1.4, IDE/ATA, and rootfs boot module handoff.
status, services, and health provide local system observations.
start health, stop health, and restart health operate the registered health service.
adduser [-w] NAME creates a local account; useradd is an equivalent spelling.
SysVinit-style init and fnusvc supervisor managing per-terminal login and signal teardown.
Networking via Intel E1000 / VirtIO-Net with lwIP — DHCP, DNS, ping, UDP, and TCP.
60 stable-ABI syscalls (65 total syscalls) with frozen numbers and signatures. See the Handbook.

Service snapshots and the supervisor command queue are volatile kernel-state devices. They reset at boot, are not an audit log, and provide no authentication, durability, or concurrent-writer guarantees.