A short history: from SunOS to solnix

solnix did not appear from nowhere. It is the newest link in a chain that runs back more than forty years, through some of the most influential operating- system engineering ever done. Knowing the lineage makes the rest of this handbook click into place — why the commands look the way they do, why ZFS and DTrace and zones all live in one coherent system, and what solnix is (and isn’t).

SunOS — the BSD years (early 1980s)

Sun Microsystems shipped its first workstations running SunOS, a Unix built on BSD (the Berkeley variant of AT&T Unix). Through the 1980s SunOS was a BSD-flavored system — bsd-style tooling, the fast filesystem, sockets — tuned for Sun’s hardware. This is the root of the family tree: solnix is, at bottom, a descendant of BSD Unix.

SunOS 5 / Solaris — the SVR4 rewrite (1992)

In 1992 Sun made a decisive break. Together with AT&T it moved to System V Release 4 (SVR4) — the “unification” of the BSD and System V Unix branches — and shipped it as SunOS 5, marketed as Solaris 2. (Confusingly, “SunOS” became the kernel/version name reported by uname, while “Solaris” was the product.) This SVR4 heritage is why illumos — and therefore solnix — uses SVR4 conventions: /usr layout, the packaging model that became IPS, service and device frameworks, and much of the userland shape a Linux admin finds slightly unfamiliar.

The Solaris innovations (late 1990s–2000s)

Over the next fifteen years Solaris became a laboratory for operating-system ideas that the rest of the industry later imitated. The ones solnix inherits directly:

ZFS — a pooled-storage filesystem and volume manager with end-to-end checksums, cheap snapshots, and clones. See ZFS storage.
DTrace — safe, production-grade dynamic tracing of the whole system, kernel and userland, from one language. See DTrace.
SMF — the Service Management Facility: a dependency-aware init system and service supervisor with a fault boundary. See SMF services.
Zones — OS-level virtualization years before Linux containers. See Zones.
Crossbow — network virtualization: virtual NICs, virtual switches, and bandwidth controls in the kernel. See Networking (Crossbow).
FMA — the Fault Management Architecture: hardware and software errors diagnosed into faults with stable message IDs. See illumos features.

Any one of these would have been a notable system. Solaris shipped all of them, integrated, in one OS — which is exactly the platform solnix builds on.

OpenSolaris — the open-sourcing (2005)

In 2005 Sun released most of Solaris as open source under the CDDL, the OpenSolaris project. For the first time the kernel, ZFS, DTrace, SMF, and zones were all public, buildable source. A community of developers and downstream distributions grew around it.

Oracle closes Solaris (2010)

Oracle acquired Sun in early 2010 and, later that year, effectively ended OpenSolaris — Solaris development continued behind closed doors as a proprietary product. The open source drops stopped. The community that had grown around OpenSolaris was suddenly without an upstream.

The community forks: illumos (2010)

Rather than let the open codebase die, the community forked the last open OpenSolaris drop into a new project: illumos. The name nods to illumination and to the ON (“OS/Net”) consolidation it descends from. illumos replaced the last few closed-source bits Oracle had never opened, and became a fully open, community-maintained continuation of the OpenSolaris kernel and core userland — what this handbook calls the illumos gate. See How solnix is built.

illumos is not Solaris and is not owned by Oracle. It is the open, living branch of the same tree; Oracle’s Solaris is the closed one.

The illumos distribution ecosystem

Just as Linux is a kernel that many distributions package, illumos is a gate that several distributions build on:

OpenIndiana — a general-purpose desktop/server distribution, the most direct OpenSolaris successor.
OmniOS — a minimal, stable server distribution.
SmartOS (Joyent/MNX) — a hypervisor-focused distribution that runs everything in zones and pioneered the modern LX-branded zone (running Linux binaries on the illumos kernel — see LX-branded zones).
Tribblix — a retro-flavored distribution with its own lightweight package manager.

Each takes the same gate and differs mostly in packaging, defaults, and focus.

And finally: solnix

solnix — the solnix Operating System — is the newest illumos distribution, and it differs in one specific way: instead of a traditional package manager (IPS, or SmartOS’s pkgsrc), it uses Nix and the NixOS module system to build and manage the whole system declaratively. It is designed as a first-class OS across four CPU targets — x86_64, aarch64, RISC-V, and SPARC — for both server and desktop use, and optimized for virtualized hosting on the major cloud platforms. Each configuration change produces a new, atomically-activated system backed by a ZFS boot environment; rollback is instant.

To be precise about what solnix is and isn’t:

solnix is illumos — the same kernel, ZFS, DTrace, SMF, zones, Crossbow, and FMA described above — packaged and managed with Nix.
solnix is not Linux. It does not use the Linux kernel, glibc, or systemd.
solnix is not NixOS. It reuses NixOS’s evaluator and module system, but targets the illumos kernel and userland, not Linux.
solnix is not Oracle Solaris. It descends from the open illumos branch, not Oracle’s closed product.

Status. solnix is early — a first preview image just landed (see Introduction). The history above is real and settled; solnix’s own place in it is just beginning.

The solnix handbook