Learn NetBSD - Ecosystem, Alternatives & Final Reflections

#Introduction

In episode 21 we looked at NetBSD 11.0 and its roadmap. Now we've reached the final episode: in this episode we'll close the Learn NetBSD journey with the ecosystem, alternatives, and final reflections — comparing NetBSD with FreeBSD, OpenBSD, DragonFlyBSD, and Linux, deciding when to choose NetBSD, summarizing the production checklist from all 23 episodes, and pointing to official learning resources to continue.

23 episodes have built you up from zero to understanding a complete operating system — installation, kernel, networking, security, even embedded. This closing episode is the map: where NetBSD stands among the giants of operating systems, when it's the right choice, and how to continue the journey after this series.

#NetBSD Among Its Siblings

#FreeBSD

FreeBSD was born from the same ancestors and focuses on performance and storage. Its strengths:

FreeBSD strengths	Details
ZFS	Very mature integration
Jails	Lightweight OS-level virtualization
bhyve	A solid built-in hypervisor
Ports/pkgs	A large binary ecosystem

FreeBSD is a strong choice for storage-heavy servers and clouds that need ZFS and jails.

#OpenBSD

OpenBSD branched from NetBSD in 1995 with a single focus: security. Its strengths:

OpenBSD strengths	Details
pf	A firewall considered one of the best
Code audit	Code continuously re-reviewed
Secure defaults	Secure from the first installation

OpenBSD is the choice for security appliances — firewalls, VPNs, and gateways that need maximum hardening.

#DragonFlyBSD

DragonFlyBSD branched from FreeBSD and developed a unique approach:

DragonFlyBSD strengths	Details
HAMMER2	Multi-volume COW filesystem
LWKT	Lightweight kernel threading for SMP

DragonFlyBSD is a niche choice for filesystem experiments and specialized SMP systems.

#A Quick Comparison

Aspect	NetBSD	FreeBSD	OpenBSD	DragonFlyBSD	Linux
Focus	Portability	Performance/storage	Security	Filesystem/SMP	Broad flexibility
Packages	pkgsrc	ports/pkg	ports/pkg	pkgsrc	per-distro
Firewall	npf	pf	pf	ipfw/pf	nftables
ZFS	via pkg	very mature	via pkg	via pkg	mature (OpenZFS)
Arch portability	Highest	Limited	Limited	Limited	Broad, but fragmented

#When to Choose NetBSD?

From everything you've learned, here's a decision guide:

Need	Choice
Embedded/SBC (RPi, Pine64)	NetBSD — broadest arch support
Legacy hardware (sparc64, vax)	NetBSD — the only realistic option
Router/gateway	NetBSD — npf + routing + IPv6 from the base system
Source-based & custom kernel	NetBSD — the most complete `build.sh`
Storage/ZFS-heavy	FreeBSD
Security-first appliance	OpenBSD
General-user desktop	Linux (driver and software ecosystem)

Choose a system based on needs, not prestige. NetBSD is the most fitting choice when portability, design cleanliness, and total control from source are the priority.

#Journey Recap: 0-21

Phase	Episodes	What You Learned
Preparation	0-2	Skills, history, architecture
Operations	3-7	Installation, pkgsrc, users, services, filesystems
Workload	8-11	Networking, kernel, source builds, backup
Security	12-16	Firewall, SSH, TLS, PaX, IPv6
Advanced	17-19	rump, virtualization, performance
Portability	20-21	Embedded, NetBSD 11.0

Each episode built on the previous one — and you now have the complete picture.

#The Production Checklist

Here's the summary of steps you must complete before a NetBSD server is considered "production-ready" — starting with a version audit with uname -a:

Area	Action
Version	Use a supported branch (`netbsd-11`/`netbsd-10`), not an EOL one
Packages	Update pkgsrc regularly (`pkg_add -u` / `pkg_chk -u`)
Patches	Monitor and apply syspatch/branch fixes
Firewall	NPF active with default deny
SSH	ed25519 keys only, root and passwords disabled
Monitoring	`systat`, `top`, and logs monitored
Backup	Scheduled `dump`/`tar`/`rsync`, tested restore
Kernel	Custom kernel matched to hardware only if needed
Documentation	Record configuration and recovery procedures

Example short audit session

uname -a
sysctl kern.version
pkg_info | wc -l
npfctl show
service sshd status

Example audit output

NetBSD hostname 11.0 ...
42
NPF is active.
sshd is running as pid 1234.

#Official Learning Resources

To continue after this series, here are the most valuable sources:

Source	Content
netbsd.org	Releases, docs, official news
The NetBSD Guide (`netbsd.org/docs/guide/en/`)	The official handbook, highly recommended
man.netbsd.org	Manuals for all commands and drivers
blog.netbsd.org	Announcements and technical articles
The `netbsd-users` mailing list	Community, where to ask questions
pkgsrc.org	pkgsrc framework documentation

#Closing

The 23-episode (0 to 22) Learn NetBSD journey ends here. You've traveled through every layer of the system: from prerequisites and history, architecture and installation, pkgsrc and users, services and filesystems, networking and the kernel, source builds and backup, firewall and SSH, TLS and PaX, IPv6 and rump kernels, virtualization and performance, embedded and NetBSD 11, to the ecosystem and reflections.

If there's one message I'd like to leave you with: NetBSD doesn't teach you how to use an operating system — it teaches you how to think about operating systems. With fully open source, a complete build system, and unmatched portability, NetBSD gives you a level of control almost no other system offers.

Key takeaways:

NetBSD is the best choice for embedded, legacy hardware, router/gateway, and source-based control.
FreeBSD for storage/ZFS, OpenBSD for security-first, Linux for desktop.
Production-ready means: supported branch, regular updates, active firewall, locked-down SSH, tested backups.
Continue with The NetBSD Guide and man pages as your daily reference.

Thank you for sticking with it to the final episode. Build your servers, experiment with rump kernels and build.sh, and make the production checklist above a habit. Share your experience with the community — and always remember: Of course it runs NetBSD. See you in the next series!