Comment by nnq | Hacker News Reader

Comment by nnq | Hacker News Reader

Parent Full thread

...can you elaborate on why? really, I'm interested. I mean I get that having the same OS for a server and for a desktop simplifies things, but... how did you arrive at OpenBSD? ...did you first go through FreeBSD? I'm sure other people will be thankful too if you'd blog about your experience!

(Note: I'm currently investigating a "cheapest to maintain" solution, and by this I mean man-hours, not upfront costs, so I could choose Windows Server just as well - not that I would do that - for both my personal server and the servers of a bunch of NGOs that I help with sysadmin stuff for free... and was wondering if something like FreeBSD was better than Ubuntu Server LTS ...I want something that I could just "drop it there and leave it running for 5 years", but at the same time there will be some packages - like webserver and related that I will want to keep to the latest stable versions, like upgrading every few months or so; and yes, I do care about security, so being of to date on all security fixes and at the same time not having to keep fixing an recompiling stuff...)

Yeah I had FreeBSD on the route before OpenBSD. FreeBSD was a very disappointing experience for me. This is some years back so the situation may be better. Back then, a lot of ports were broken. It felt that every second port did not compile. The second thing was that FreeBSD is like most Linux distributions: It tries to support everything and that is bad. If you have a problem and ask how you solve that with FreeBSD you mostly get the answer: you can use X or Y or Z. X has this disadvantages, Y was not updated for years and Z has no documentation. I also tried to try NetBSD but it panic'ed on all my machines during boot.

Disclaimer: I am an OpenBSD fanboy because it opened my eyes. OpenBSD's base system already solves 90% of my problems with exactly one, perfectly maintained and documented solution. You want a firewall? Choose between pf, netfilter or something else on FreeBSD. On OpenBSD the answer is "use pf" (which is btw by far the best paket filter I every experienced). The port system just works, is up-to-date and has good default configurations (and I never missed a package). Maintenance is very easy. It is not as easy as apt-get update && upgrade but the release upgrade (every 6 months) never broke anything on my systems (and takes just 10 minutes). Besides that, there is nearly nothing to do. Here is the bug/update list of the current release (5 months old): http://openbsd.org/errata51.html The last thing I want to mention now is the consistency in all tools. For network configuration there is ifconfig which can just handle everything (e.g. on linux you have to use special tools for wlan). You have great manual pages. The manual pages are real manual pages with introductions to the systems, various high level topics down to device nodes etc. They are completely up-to-date and the best source for all informations.

Fantastic! I love fanboyish opinions. :) OpenBSD installation this weekend for me. I love to try out distros/OSes.

Thanks for the quick answer. I'll definitely put some time aside for researching OpenBSD and see if it can fit my needs. Though you got to admit that the OpenBSD folks really don't know how to "sell" their product... I mean I know that in the OS world marketing if for the mindshare and not for the money, but that that's even more reason to do it right... their horrible website and throwing things about crypto and export restriction first really made me think they are not even remotely solving the types of problem I have...

Reply on news.ycombinator.com