Commentary

Serdar Yegulalp
 

A Few Cheers For OpenBSD

With all of the hollering about Linux, Ubuntu or otherwise, there's another open-source operating system that just celebrated getting a new 4.2 release out the door.  It's one that hasn't been quite as widely-celebrated as Linux but is still deeply important in its own way: OpenBSD.

With all of the hollering about Linux, Ubuntu or otherwise, there's another open-source operating system that just celebrated getting a new 4.2 release out the door.  It's one that hasn't been quite as widely-celebrated as Linux but is still deeply important in its own way: OpenBSD.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The quick primer, for those not in the know: OpenBSD is one of several common flavors of BSD, another Unix-derived OS.  Linux is of course the other big "Unix-like" OS out there right now, although you quickly find out Unix-derived and Unix-like aren't the same thing.

To wit: OpenBSD was written to be more of a descendant of the "classic" AT&T Unix (and Unix in general); Linux was built from the ground up with many Unix-like features.  As one other wag put it, BSD is what you get when Unix guys port Unix to the PC; Linux is what you get when PC guys write Unix for the PC.  And as knowledgeable Apple fans will be happy to tell you, Mac OS X is itself a derivative of BSD -- or, rather, derived from the NeXTSTEP / OPENSTEP project, in turn mined from BSD.

The differences in design philosophy between BSD and Linux make for markedly different products.  OpenBSD's two big emphases are a) availability of the source code, as the name implies, and b) an unashamed insistence on security, security, security, in a proactive fashion.  By default, out of the box, OpenBSD is heavily locked-down -- and while that means a little more work for the admin to get things opened up, it also means you're that much less likely to get rooted from the git-go.  The developers constantly audit the code for possible security issues as a matter of course and not simply as a response to bug reports phoned in from the outside.

OpenBSD doesn't have the glamour of the major Linux distros.  It's not what you could call a desktop-user-friendly OS, and it works on a smaller subset of supported hardware than Linux.  That said, the 4.2 version adds support for many new devices -- and if you're running OpenBSD for the sake of stability and security, you're probably also going to use hardware that's been in the wild for a while and has proven itself (and most likely has OpenBSD support to begin with).  And most importantly, it's is deeply solid and dependable, and well-suited to tasks that need to be secure from the inside out -- perimeter security, for instance.  Calyptix's Access Enforcer, a firewall/anti-spam/-virus/-spyware/ appliance (one of many such devices) was built using OpenBSD.

So here's a few cheers for OpenBSD's new revision to the right of the decimal point.  With all the noise about Linux, it seems like a good idea to remind folks that it's not the only open-source, Unix-like game in town.  There are always alternatives, even to the alternatives themselves.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links