Why Solaris Became the Foundation of NASDEV

NASDEV didn't start with a grand plan to build a Solaris-based infrastructure platform.

It started with a desire to build a useful system and, at the same time, keep learning.

Solaris happened to be the operating system that made the most sense for that journey.

And once Solaris became part of NASDEV, it proved remarkably difficult to replace.

A Different Way of Thinking About an Operating System

Today, most people encountering the word "server" probably think of Linux or Windows.

Solaris is less common.

But for anyone who spent time working with enterprise systems, Solaris has a rather different heritage.

It was designed from the ground up as a serious operating environment for systems that were expected to run reliably for long periods of time.

That philosophy appealed to me.

NASDEV was never intended to be a disposable server.

I wanted an environment where the operating system itself was something worth understanding.

Solaris provided exactly that.

ZFS Changed the Storage Equation

One of the biggest reasons Solaris became so important to NASDEV was ZFS.

Traditional storage management often requires thinking about disks, partitions, volumes and filesystems as separate layers.

ZFS changed that model.

Storage could be treated as a pool rather than simply a collection of individual disks.

Filesystems became much easier to create and manage.

Snapshots became a normal part of filesystem management.

And, perhaps most importantly, ZFS brought data integrity much closer to the filesystem itself.

For a project that began as a NAS, that was a very compelling combination.

Storage wasn't just something attached to the operating system.

Storage became part of the operating system architecture.

Solaris Zones

The second major reason Solaris stayed was Zones.

Zones provided a way of separating services without requiring a separate physical server for every application.

This was particularly useful as NASDEV grew.

A service could be given its own environment while still using the underlying Solaris system.

That meant I could experiment with one environment without necessarily disturbing everything else.

Over time this became one of the defining characteristics of NASDEV.

Instead of thinking:

"I need another server."

I could often think:

"I need another zone."

That is a very different way of designing infrastructure.

Stability Matters

There is another reason Solaris remained attractive: stability.

NASDEV is not a system that gets rebuilt every few months.

Some components have been around for many years.

That creates a different set of priorities.

The latest version of something isn't necessarily the most useful version.

A stable platform that is well understood can be considerably more valuable than constantly replacing components simply because newer versions exist.

That doesn't mean NASDEV avoids upgrades.

Quite the opposite.

The system has gone through major Solaris upgrades over its lifetime.

But upgrades are performed because there is a reason to upgrade, rather than simply because a new version exists.

The Learning Factor

There is also a less obvious reason for using Solaris.

It is interesting.

Some operating systems are designed to make everything as invisible as possible.

That's great when the objective is simply to consume a service.

But NASDEV is also an engineering project.

I want to understand what is happening underneath.

Solaris exposes a lot of that underlying architecture.

Zones, SMF, ZFS, networking, services, filesystem management and system administration all provide opportunities to understand how the system actually works.

That makes Solaris a very good learning platform.

Things Don't Always Go to Plan

Of course, choosing a technically interesting operating system comes with consequences.

Solaris has its quirks.

Sometimes the documentation isn't particularly obvious.

Sometimes a seemingly simple change has unexpected consequences.

And sometimes the system gives you an error message that leaves you wondering what the developers were thinking.

But that's also part of the learning process.

Some of the most useful NASDEV articles will probably come from exactly those situations.

A zone that refuses to boot.

A service that enters maintenance.

A configuration that looks completely correct but doesn't work.

A filesystem problem that turns out to have nothing to do with the filesystem.

These are the problems that force you to understand the system.

Why Not Change to Linux?

This is probably the obvious question.

Would NASDEV be easier to run on Linux?

Possibly.

Would there be more readily available software?

Almost certainly.

Would there be more people using the same platform?

Definitely.

But that's not really the point.

NASDEV isn't a commercial hosting platform where the primary objective is minimising operational cost.

It is an engineering project.

Solaris provides capabilities and an architecture that I enjoy working with, and after many years I have a very good understanding of how the environment behaves.

Changing operating systems simply to follow the mainstream would remove one of the interesting aspects of the project.

And there is another consideration:

If it works, why change it?

Solaris Is Part of NASDEV's Identity

At this point Solaris is more than simply the operating system underneath NASDEV.

It has influenced the architecture of the entire project.

ZFS influenced how storage is designed.

Zones influenced how services are separated.

SMF influenced how services are managed.

The Solaris networking model influenced how systems communicate.

And years of working with the platform have influenced how I approach system design and troubleshooting.

That's why Solaris deserves its own section on this site.

Not because it is the only technology NASDEV uses.

But because it has played such an important role in the evolution of the project.

The Future

Will NASDEV always run Solaris?

I don't know.

That's one of the interesting things about long-running engineering projects.

Eventually hardware becomes obsolete.

Software reaches the end of its useful life.

Requirements change.

Better technologies appear.

When that happens, NASDEV will evolve again.

But for now, Solaris remains the foundation.

And after all these years, it still provides an excellent platform for what NASDEV is intended to be:

a working system, an engineering laboratory and a place to learn.