_______  ______    _______  __    _  ___   __    _  __   __    _______        _______        _______ 
|       ||    _ |  |       ||  |  | ||   | |  |  | ||  |_|  |  |  _    |      |  _    |      |       |
|    _  ||   | ||  |   _   ||   |_| ||   | |   |_| ||       |  | | |   |      | | |   |      |____   |
|   |_| ||   |_||_ |  | |  ||       ||   | |       ||       |  | | |   |      | | |   |       ____|  |
|    ___||    __  ||  |_|  ||  _    ||   | |  _    | |     |   | |_|   | ___  | |_|   | ___  | ______|
|   |    |   |  | ||       || | |   ||   | | | |   ||   _   |  |       ||   | |       ||   | | |_____ 
|___|    |___|  |_||_______||_|  |__||___| |_|  |__||__| |__|  |_______||___| |_______||___| |_______|


The PRONINX: REAL UNIX


PRONINX - UNIX KERNEL & OS

PRONINX is a lightweight, high-performance kernel built for the RISC-V architecture. It is designed for those who value direct hardware control over bloated abstractions. Born from the principles of the classic Unix-way, PRONINX strips away the legacy clutter of POSIX to deliver a pure, transparent, and predictable system.

Core architecture

  1. RISC-V Native: Architected specifically for the 64-bit RISC-V instruction set.
  2. Demand Paging: Advanced memory management that maps pages only upon access, ensuring maximum RAM efficiency.
  3. Lazy Allocation: Smart memory handling that defers physical allocation until the moment of execution.
  4. Unified Monitoring API: A robust internal interface for real-time process and system telemetry (powering tools like top and sp).
  5. Root-Relative Execution: An intuitive shell environment that automatically locates binaries within the root directory.
  6. Based on Xv6-kernel (MIT).

System environment

The PRONINX kernel comes bundled with a custom shell – PRONINX Shell (PSH). It has been written almost entirely from scratch. It replaces the ‘sh’ command in the original Xv6.

PRONINX

Many see an operating system as a collection of random software. We see it as a singular, unified instrument.

PRONINX is currently at an early stage — it is a robust kernel bundled with a shell and a handful of fundamental utilities. While these programs (like ls or mkdir) may seem basic, in PRONINX they are treated as integral organs of the system.

Why this approach? To enforce a bulletproof standard. By baking essential tools into the system's identity, we eliminate fragmentation before it even begins. In PRONINX, there is no room for incompatible variants where basic commands differ. It ensures that any developer or user entering the PRONINX environment finds a consistent, predictable, and immutable interface. We aren't building a bloated OS; we are forging a reliable standard.

GitHub

CLICK ME!!11!!