Exploring NetBSD for Stability and Cohesion in IT Operations

htorrado

One of the reasons I've been exploring NetBSD over the past few months is that, after more than 30 years in IT, I've grown increasingly frustrated with how frequently mainstream Linux distributions change the way they handle core systems: boot processes, network management, firewalls, and so on. It feels like I'm constantly relearning how to accomplish the same tasks in countless different ways, and frankly, I'm tired of it.

I’ve come to appreciate the value of working with a cohesive operating system—one where technical decisions are made thoughtfully and not simply to reinvent the wheel.

With that in mind, here’s my question: How often does NetBSD introduce breaking changes to the system? Stability is crucial for my professional work, and I believe NetBSD might be the right choice. I’d love to hear your opinions.

r0ller

I'm just a normal user using it for everyday tasks and development, not any kind of server admin but for me, ten years (since I use it) passed by without noticing any breaking stuff.

htorrado

It's nice to hear something like this nowadays. My most recent issue with Linux involved Red Hat 9. By default, if the network card loses its link for any reason, the system switches to DHCP mode. The problem is that when the link is restored, the system remains in DHCP mode, and you have to manually reconfigure the static IP address.

The other day at work, I accidentally disconnected the network switch, and when I reconnected it, I went crazy trying to figure out what was wrong with the two servers. That was the moment that truly tested my patience.

With every update or new version, critical things seem to change, and I find myself needing to trust my servers again. This is why I really appreciate the UNIX philosophy of the BSDs, especially NetBSD.

kc9udx

This is part of how I ended up with NetBSD and why I keep it. When I felt Solaris wouldn't work for me anymore (I didn't know about pkgsrc!) I switched to Debian which seemed the least offensive of the Linuces, but I absolutely hate the necessity of frequent updates and the fact that something major breaks in a really bad way with each update. My first experience updating Debian (not long after starting to use it) sent me looking for something more like Solaris. I knew about the BSDs through the occasional SysV vs BSD comparison in books. NetBSD was the only one I could get to work. And it turned out to be more like I wanted Solaris to be than even Solaris was.

The only times something breaks in NetBSD, it's either due to my quirky installation and usage, or, something I only encounter due to my usage (which was delightfully fixed in NetBSD recently).

Jay

Check this blog post https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/

I am not expert on professional consultant for that but author of blog has better experience with using NetBSD in professional environments.

htorrado

Jay

Thank you! I read that article several times. It was one of my reasons for starting to mess with NetBSD.

jmcunx

If you know your needs, then check to see if NetBSD has the required packages in pkgsrc.

I have a server running on NetBSD 10.0 as a bridge and downloading and formatting local weather forecasts for my gemini/gopher site on sdf, it has had no issues since I went to 10.0. I expect if NetBSD will do what you need, it will be perfect. Of course you need to know what you need to do 🙂

I chose NetBSD because based upon history, 10.0 will be around for a long time, no worries about major upgrades for a while. With that said, all (point/major) upgrades are easy when they do come around.

Also, www.sdf.org has used NetBSD for quite a while without any issues.