Hacker News new | past | comments | ask | show | jobs | submit login

I’ve been eying FreeBSD for my next project once feature parity is finalized and I begin to lock down the build chain for long term storage. I think one nice thing about FreeBSD is how the entire ecosystem is maintained by the same team of core developers vs. Linux which focuses on the kernel and has a wider more heterogeneous ecosystem. I want something stable, that has great console mode, and has great Ethernet support, and is absolutely rock solid. Does FreeBSD fit the bill there?



Probably fits your requirements. One interesting thing to remember about FreeBSD is that a lot of commercial users of it use it as a base for enterprise appliances (think storage arrays, proxies, DPI boxes, etc). This means that the project as a whole is fairly beholden to these users, who provide a nice chunk of the project's funding and many of its professional committers.

As a result, the project is less focused on desktop use cases and free software/security at any cost ideology than on a) not breaking all the complicated crap built on top of it and b) providing drop-in perf and stability enhancements.

So, yeah, if you want a performant network stack and a consolidated kernel/userland that values stability (both in the "years of uptime" and the no "hey guys, we're jumping to systemd!" senses of the word) FreeBSD is a good option. As a bonus, FreeBSD's manpages are really really nice and give you basically everything you need to get down and do some serious systems programming or box-tuning. Go check out `man 7 tuning`.

Anecdotally, during my years as a sysadmin I ran a bunch of FreeBSD boxes alongside a bunch of Linux boxes - similar hardware, similar tasks. The FreeBSD boxes would routinely run for literal years without a hiccup, while we never got a similar level of stability from any other OS.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: