Tracing NetBSD's journey from its roots in 386BSD in 1993 to becoming the world's most portable operating system, understanding the philosophy that gave birth to the slogan "Of course it runs NetBSD", and the release roadmap from 1.0 to 11.0.

After preparing our environment in episode 0 — understanding the basic skills, setting up a VM, and downloading the installer image — in this episode we'll take a moment away from hands-on work to understand why NetBSD exists. The history and background of an operating system may feel unimportant, yet that's exactly where the reasons for its current design lie.
Why should you understand NetBSD's history? Because NetBSD isn't a system born in a corporate meeting room, but rather from a real need within the early 1990s UNIX community. Understanding its origins will explain many design decisions — why it supports hundreds of architectures, why pkgsrc can run on many OSes, and why code quality and design cleanliness are guarded so strictly. You'll realize that NetBSD is not just "a different Linux", but a system with a unique identity and philosophy.
NetBSD's story begins in the early 1990s, when UNIX was the property of expensive commercial vendors. 386BSD was one of the first attempts to bring BSD UNIX to x86 PCs, and from here a group of developers — including Chris Demetriou, Theo de Raadt, and Adam Glass — made an important decision in 1993: they wanted to focus on code quality and portability.
The new project was named NetBSD, and its first release, NetBSD 1.0, came out in 1993. From the start, its mission was clear and distinct from its siblings: not just running on PCs, but running on as many platforms as possible. From this came the slogan famous to this day: "Of course it runs NetBSD".
Note
Don't get confused: NetBSD (1993) was born from 386BSD, and shortly after, FreeBSD was also born from the same source. The three then branched with different focuses — NetBSD emphasizes portability, FreeBSD emphasizes performance, and OpenBSD (which split from NetBSD in 1995) emphasizes security.
One sentence that sums up NetBSD's entire philosophy is extreme portability. From the start, every line of code that goes in must run on many platforms. This isn't just an aspiration; it's a standard strictly enforced by the developers.
NetBSD supports hundreds of architectures — likely the most of any UNIX-like operating system:
| Category | Architectures |
|---|---|
| Modern desktop/server | x86_64 (amd64), i386 |
| ARM | aarch64 (arm64), evbarm, Raspberry Pi, Pine64 |
| Embedded | evbmips, evbsh3, sandpoint |
| RISC-V | riscv64, riscv32 |
| Consoles | Dreamcast, Amiga, Atari, even Wii |
| Legacy | sparc64, powerpc, mips, m68k, vax |
You can run NetBSD on a modern x86_64 server, on a Raspberry Pi, on old game consoles, even on 30-year-old hardware — all from the same source tree. This is what makes NetBSD the top choice for embedded and legacy hardware revival.
This slogan is more than just a catchphrase. It's living proof of the portability commitment. When a new platform appears — or when a "weird" piece of hardware is found in a warehouse — the NetBSD community flocks to port it, and almost always succeeds. This is also why NetBSD is often used as a research platform: if you want to test a kernel feature, NetBSD is one of the easiest places to test it across many types of hardware.
NetBSD is stewarded by The NetBSD Foundation, a non-profit organization responsible for the code, releases, and community. This approach guarantees that NetBSD remains open and free from the commercial interests of any single vendor. The development model uses CVS and later Git for the official repository, with a structured flow: development happens on the -current branch, which is then frozen to become a release.
NetBSD releases are not chased by marketing deadlines. Major releases come out every 2-3 years, with minor releases containing backported fixes in between. Here's the release roadmap:
| Release | Year | Notes |
|---|---|---|
| 1.x | 1993-2001 | The beginning; portability is the focus |
| 2.x | 2004 | Mature x86 support |
| 3.x | 2005 | Kernel threading |
| 4.x | 2007 | Performance and SMP improvements |
| 5.x | 2009 | Modularization and reentrancy |
| 6.x | 2012 | Major SMP improvements |
| 7.x | 2015 | Mature NPF, virtio |
| 8.x | 2018 | Early NVMM support |
| 9.x | 2020 | Stricter PAX_ASLR, better Wi-Fi |
| 10.x | 2024 | LLVM toolchain, major improvements |
| 11.0 | 2026 | The latest major release as of now |
Each release brings major internal improvements that aren't visible on the surface — proof that NetBSD is maintained with discipline, not merely recycled.
| Scenario | Why NetBSD |
|---|---|
| Embedded & SBC | Broad ARM/RISC-V support, small footprint |
| Router/gateway | Mature NPF, IPv6, and routing |
| Legacy hardware | Support for hundreds of old architectures |
| Source-based builds | build.sh and pkgsrc give full control |
| Research & experimentation platform | rump kernels, NVMM, and design cleanliness |
NetBSD is often compared with FreeBSD and OpenBSD. The core differences:
| Aspect | NetBSD | FreeBSD | OpenBSD |
|---|---|---|---|
| Primary focus | Portability | Performance & storage | Security |
| Package manager | pkgsrc | pkg (prebuilt) + ports | pkg (prebuilt) + ports |
| Main firewall | npf | pf | pf |
| Cloud/VM | NVMM, Xen | bhyve, jails | VMM |
All three share the same BSD ancestry, but each release reaffirms a different path. NetBSD chose the broadest path: one system for all platforms.
| Year | Milestone |
|---|---|
| 1993 | NetBSD 1.0 is born from 386BSD |
| 1995 | OpenBSD branches from NetBSD |
| 1997 | pkgsrc is born from NetBSD packages |
| 2004 | NetBSD 2.0, mature x86 support |
| 2020 | NetBSD 9.0 |
| 2024 | NetBSD 10.0, LLVM toolchain |
| 2026 | NetBSD 11.0 is released |
To verify which release you're currently running, use uname -a:
uname -aNetBSD hostname 11.0 NetBSD 11.0 (GENERIC) #0: Thu Jul 30 12:00:00 UTC 2026In this episode 1, you've traced NetBSD's journey from a need within the 1993 UNIX community — 386BSD — to becoming the most portable operating system in the world with the slogan "Of course it runs NetBSD". You also understand the role of the NetBSD Foundation, the release roadmap from 1.0 to 11.0, and NetBSD's position among FreeBSD and OpenBSD.
Key takeaways:
In the next episode, episode 2, we'll dissect NetBSD's core concepts and main architecture — the base system structure, the role of the modular kernel, userland, rump kernels, and the relationship between -current, stable, and release. We'll also get to know the components that will accompany you throughout the series. See you in episode 2!