News for hackers. Stuff that matters.
Re:Code rot and why I picked OpenBSD by ams6110 on Sunday January 04, 2015 @06:26PM (#8836333)
I love OpenBSD and I use it as my desktop OS at work and at home. But there are a couple of inaccuracies in this piece.

In OpenBSD you are encouraged to run current.

What they actually say[1] is:

  The name -stable refers ONLY to the API and
  operations of OpenBSD not changing, not the
  overall reliability of the system. In fact,
  if things go as desired, the -current flavor
  of OpenBSD, on its way to becoming the next
  -release, will be an improvement in reliability,
  security and overall quality over the previous
  -release and -stable.
What is implied is that sometimes things don't go as desired; -current sometimes has issues. They are almost always quickly fixed, but if you depend on as near as possible certainty that an update won't break anything, you should run -stable.

If OpenBSD states that something is configured then it works and will remain working flawlessly or will only get better over time.

Not guaranteed. I remember somewhere in the 4.x series my NIC driver was removed from the release build. I updated, and suddenly had no network access. My fault for not reading the release notes, but they don't always support old/obscure hardware forever. More recently, support for some older Microsoft VPN protocols was removed. It was because they were insecure, but this changed the way I had to interoperate with one of my client's internal networks.

[1]: http://www.openbsd.org/stable.html

There are no comments on this comment yet.