System Abstract

OPERATOR NOTE: This system assumes familiarity with Unix conventions, the C toolchain, BSD make, and manual page navigation. New users should begin with the Xirtux Handbook (man xirtux) after installation.

Operating Principles

1. FIG. P1 — Small kernel, readable tree. The kernel source tree is deliberately constrained. Every subsystem must justify its presence. The goal is a kernel an experienced operator can read and understand in a reasonable period.
2. FIG. P2 — Conservative networking stack. Network protocols are implemented defensively. No experimental congestion algorithms, no hidden telemetry, no auto-negotiated cloud services. The network stack serves the operator, not the network.
3. FIG. P3 — Local-first tooling philosophy. All system tools operate on the local machine by default. Remote operations require explicit operator intent. The system never assumes an internet connection.
4. FIG. P4 — Source-visible system architecture. Every component of the base system ships with complete source code. The build process is documented, reproducible, and does not require binary bootstrap blobs. Operators are encouraged to read the source.
5. FIG. P5 — No decorative complexity. Features are added only when they solve a demonstrated problem for system operators. Cosmetic enhancements, animation, transparency effects, and graphical boot splashes are not part of the base system.
6. FIG. P6 — Operator owns the machine. The operator has root access, unrestricted file system control, and full authority over every installed component. The system does not hide configuration behind automated tools. Manual pages are the authoritative interface.

SYSTEM CONSTRAINT: These principles are not marketing. They are engineering constraints enforced by the build system and the project governance document (see src/SYS_CONSTRAINTS). Each principle is illustrated in the diagrams that follow.

Small Kernel, Readable Tree

FIG. P1 — Kernel subsystem approval model. Solid lines: justified subsystems accepted into the tree. Dashed red: rejected proposals. Kernel targets ~18,000 lines of C — readable by an experienced operator in a single session.

Conservative Networking Stack

FIG. P2 — Conservative networking stack. Each layer applies operator-configured filters. No protocol auto-negotiation, no hidden telemetry, no cloud dependency. Rejected external influences crossed out on the right.

Local-First Tooling Philosophy

FIG. P3 — Local-first tooling architecture. Left: local machine with tools defaulting to local operation. Right: remote boundary only reachable through EXPLICIT INTENT barrier. The system never assumes an internet connection.

Source-Visible System Architecture

FIG. P4 — Source-visible build pipeline. Every component ships with source. Build is documented and reproducible. Binary blob bootstrap rejected (crossed out). Ports integrate via pkgsrc where upstream source is available.

No Decorative Complexity

FIG. P5 — Feature gate. Every proposal passes through the DEMONSTRATED PROBLEM? diamond. Green path: real problems → approved. Red path: cosmetic features (boot splashes, animations, rounded corners, color output) → /dev/null. The irony of this diagram existing on an elaborately styled website is noted.

Operator Owns the Machine

FIG. P6 — Operator sovereignty. The operator (root) has unrestricted authority. Three pillars: filesystem control, plain-text configuration, manual pages as the authoritative interface. Rejected below: hidden config, automated tools, subscription models. The machine serves the operator.

System Architecture

FIG. 2A — Simplified component diagram. Solid lines indicate direct API linkage. Dashed lines represent build-time or packaging relationships. Click any component for related documentation.

Command Demonstration

The following examples illustrate the core Xirtux UNIX System operator commands. These are not emulated or containerized — each command interacts directly with the system it runs on.

operator@xirtux:~ $ xpkg audit

[xpkg] scanning installed package database
[xpkg] checking against pkgsrc-vulns-2026Q3.db
[xpkg] 0 known vulnerabilities in 847 installed packages
[xpkg] system integrity: NOMINAL

operator@xirtux:~ $ xsys rebuild

[xsys] rebuilding base system from /usr/src
[xsys] target: amd64
[xsys] kernel:       OK  (38s)
[xsys] userland:     OK  (142s)
[xsys] release:      OK  (17s)
[xsys] build complete — artifacts in /usr/obj

operator@xirtux:~ $ man xirtux
XIRTUX(7)          Xirtux UNIX System Manual          XIRTUX(7)

operator@xirtux:~ $ rcctl show
sshd          enabled   running
ntpd          enabled   running
syslogd       enabled   running
xirtuxd       enabled   running
httpd         disabled  stopped

OPERATOR NOTE: All commands use manual pages as authoritative documentation. Run man xirtux-intro for a guided introduction to the system toolchain.

Compatibility Matrix

Subsystem support status across target platforms for revision 0.7-BETA.

SYSTEM CONSTRAINT: Support classifications evaluated quarterly by the Xirtus Systems Research Group.

Download & Build

Xirtux UNIX System is distributed as a single installable ISO image. The complete source tree is available for local building. No network registration, activation key, or account required.

$ ftp https://cdn.xirtux.org/pub/xirtux/0.7-BETA/src.tar.xz
$ tar xJf src.tar.xz -C /usr/src
$ cd /usr/src
$ make build
[xsys] rebuilding Xirtux UNIX System 0.7-BETA
[xsys] operator confirmation required — see make(1) and xsys(8)

No warranty. No telemetry. No cloud requirement. Provided by the Xirtus Systems Research Group under the BSD 2-Clause License. Operators assume full responsibility for their systems. Read the manual. Understand your machine.