OpenBSD on SGI: A Rollercoaster Story

When you think of OpenBSD, you probably think of rock-solid security, meticulous code, and running on x86_64 or maybe some ARM boards. When you think of SGI (Silicon Graphics, Inc.) machines, you think of massive CG-rendering powerhouses from the 90s, like the ones that brought Jurassic Park dinosaurs to life. Putting OpenBSD on an SGI machine? That sounds like a recipe for a wild ride. And it is.

The Contender: An SGI Indy

My machine of choice for this adventure was an SGI Indy. This was the "low-end" desktop workstation from SGI in the mid-90s. Don't let "low-end" fool you; this thing was still a beast compared to contemporary PCs. It features a MIPS R5000 CPU running at 150 MHz or 180 MHz, a dedicated graphics subsystem, and that iconic, chunky blue case. It was designed to run IRIX, SGI's flavor of UNIX, which was legendary for its graphical capabilities.

The Goal: Purity and Pain

The aim wasn't just to get any UNIX-like system running. The goal was to install a current, official OpenBSD release. This is where the rollercoaster begins. OpenBSD has support for the SGI Indy (known as the 'IP22' architecture), but it's not what you'd call "well-trodden territory." You're dealing with:

• Non-standard boot process: SGI machines don't have a BIOS. They use a boot prom called ARCS. Getting a kernel to load isn't as simple as putting it on a USB stick.
• MIPS Architecture: OpenBSD's MIPS port is stable, but it's a different world from the x86 you're used to.
• Limited RAM: These machines max out at 256 MB or 512 MB of RAM. OpenBSD can run lean, but you feel every megabyte.
• Obsolete Storage: The Indy typically has a SCSI drive. Finding a working, quiet SCSI drive today is a challenge in itself.

The Installation Saga

The installation process is a multi-stage puzzle. It's not for the faint of heart.

1. Preparation: You need a specific boot floppy image (yes, a floppy disk) that contains a small kernel capable of booting from the CD-ROM. You also need the OpenBSD install ISO for SGI.
2. Booting: Insert the floppy, power on the machine, and hope it reads the disk. The ARCS prom will load the kernel from the floppy, which then searches for and boots from the CD-ROM.
3. The Installer: OpenBSD's installer is famously text-based and straightforward. But here, you have to be careful. Partitioning the SCSI drive requires understanding the disklabel for MIPS. A mistake here can mean starting over.
4. Patience: Everything is slow. Copying the file sets from the CD to the hard drive feels like watching paint dry. A successful install is a cause for celebration.

There's a special kind of satisfaction that comes from seeing the OpenBSD boot prompt on a machine that was designed to render 3D graphics for Hollywood movies.

The Payoff: A Secure Jurassic Workstation

Once installed, what do you have? You have a nearly 30-year-old machine running one of the most secure operating systems in the world. It's a fascinating juxtaposition.

• It Works! You get a full, modern-ish OpenBSD system. A complete shell, `ssh`, `tmux`, and a package repository with thousands of ports (if you have the RAM and patience to build them).
• Networking: The onboard Ethernet works, meaning you can `ssh` into your Indy from your modern laptop. It's a surreal experience.
• The Fun Factor: There is no practical reason to do this. It's about the challenge, the history, and the sheer geeky joy of making it work.

Conclusion: Was It Worth It?

Absolutely. Running OpenBSD on an SGI Indy is a deep dive into computing history and a testament to the portability and robustness of the OpenBSD system. It's not a project for someone looking for a quick win. It's a hobbyist project filled with frustration, dead ends, and moments of triumph.

It teaches you about bootloaders, hardware architecture, and the patience required to work with vintage tech. If you have an SGI machine collecting dust and a weekend to spare, give it a try. Just be prepared for a rollercoaster.