What OSes have succeeded or failed here

May 31, 2012

In light of my recent entries, people might wonder how we've fared with operating systems here and which specific OSes have succeeded or failed. The necessary disclaimer is that this is all from my personal perspective; my co-workers might have a somewhat different view of things.

OSes that we've actively done things with while I've been here:

  • OpenBSD: clear success within its domain.

    OpenBSD is our automatic choice for anything to do with firewalls (PF just works) and pretty much the default choice for related networking things like VPN servers, routers, and so on. We have a number of OpenBSD machines running additional simple network-related services and they just go and go without problems.

  • Ubuntu LTS: a success but I'm not enchanted with it.

    Ubuntu LTS is our default Linux and thus our default Unix. Its combination of a long 'support' period and a wide vendor-supplied package collection continue to be unmatched (and be what we need), but it has various flaws and rough edges that leave me not really happy with it. Ubuntu LTS is more something that I put up with than something I actually like.

  • Solaris: failed, as discussed.

    (We continue to build new fileservers with Solaris to match the current ones.)

  • RHEL/CentOS: failed in practice.

    The short summary is that RHEL is not enough better than Ubuntu LTS and it has worse package availability (from Red Hat; we don't entirely trust EPEL, since it's a third party source). We've used RHEL on a few servers but the minor improvements (if any) haven't really been worth running another Linux distribution; the servers could as well run Ubuntu LTS and simplify our lives. I keenly regret this because I like RHEL better than Ubuntu LTS, but I have to face reality here; it's not enough better (and it has its own issues even apart from package availability).

    Our iSCSI backends run RHEL 5 and in theory the long support period is a great advantage for this. In practice they're appliances and we never update them anyways, so it's not clear how much this matters. We might stay with RHEL or CentOS in this specific situation even if we were redoing them from scratch today, just in case.

    (We continue to build new iSCSI backends with RHEL 5 to match the current ones.)

  • Windows: TILT. Not applicable in our environment.

    We have one Windows terminal server for a specific, narrow purpose; to give our non-Windows users a way to run Windows programs (especially the Office suite). There's no interest in using Windows servers for anything else; as far as servers go, we're a Unix shop.

Worth mentioning:

  • FreeBSD: never been seriously considered, would likely fail.

    I don't think we've ever seriously looked at running FreeBSD based servers. FreeBSD kind of fall into the 'RHEL zone', where it's different but without any solidly compelling advantage we've thought of. I've used FreeBSD enough in another environment to feel that it's nothing particularly special as Unixes go.

    It's possible that we'll wind up using FreeBSD as our next generation ZFS platform, but even then I don't think it would spread beyond that unless it turns out to be unbelievably cool.

    (In general, unless Linux somehow gets real native ZFS support I expect that any next generation ZFS platform would end up like Solaris is for us today, ie used as a special purpose appliance and no more. The most I'm hoping for is that the next generation platform is more pleasant than our current Solaris one.)

OSes that were pretty much before my time here:

  • Debian: failed due to being supplanted by Ubuntu LTS.

    The problem with Debian in practice is that the support period is too short unless Debian does releases only very slowly. Beyond that, my impression is that Debian wound up being considered an inferior version of Ubuntu LTS; the few Debian based servers we used to have were replaced with ones based on Ubuntu LTS when we focused on the latter.

    (I actually built a Debian-based server here at one point (before we focused on Ubuntu LTS) but it never made it into production.)

  • Red Hat Linux (now Fedora): failed, I believe in part because the support period is too short. Supplanted by Ubuntu LTS.

I don't think we've ever really looked at other Linux distributions; in general it seems unlikely that they have enough of an advantage over Ubuntu LTS to be attractive.

None of the other commercial Unixes are even on the radar (nor any of the other *BSDs; if we're not considering FreeBSD, they're even further down the list). Mac OS X is not something we run on servers, although we have some Macs and Windows machines around as test clients (since our users need our services to work with both).


Comments on this page:

From 87.6.85.69 at 2012-05-31 17:54:58:

I don't think there is a difference between the EPEL repository of Red Hat and the Contrib repository of Debian/Ubuntu but I agree with you about the worse package availability

From 70.26.85.161 at 2012-05-31 18:53:12:

On the topic of FreeBSD, just this week there was a thread on the "stable" list which asked "Why Are You Using FreeBSD?":

Some of the most popular answers were summarized at:

From 108.60.106.196 at 2012-05-31 19:55:31:

I realize that Debian has a pretty hard update/support timeline, but I've always bristled at Ubuntu. It just seems to be too consumer-ish, and not engineer-ish enough. For example, Debian by default installs nothing you don't actually need... my favorite example is the time I had a new Debian box where I couldn't scroll backward in man pages as I'm used to, and of course the reason was that it had defaulted to /bin/more as a pager since it just hadn't installed anything else.

Ubuntu seems to be more liberal with its default package installation, at least the last time I interacted with it as a server OS (at least 5-6 years ago). This is also the reason I tend to install packages with apt-get instead of aptitude, since aptitude installs suggested and recommended packages by default.

Do you 'put up with' or embrace Ubuntu's consumer-ish bent, or is it better and leaner than I remember? Are you vigilant about keeping your own machines lean?

-Brad (augmentedfourth.com)

By cks at 2012-05-31 23:57:09:

The simple answer is that we install lots of packages anyways, so I don't think we'd particularly notice any Ubuntu non-leanness.

(Defaulting to more instead of less as the basic pager strikes me as a very Debian thing to do, but I also don't think it's the right thing. Time moves on, and so should Unixes.)

From 205.194.74.164 at 2012-06-01 14:21:10:

The reasons to use FreeBSD listed on that web page are all good but not good enough to choose FreeBSD over a Linux. Linux has similar features as well as its own strengths. Where FreeBSD loses is long term support. Ubuntu LTS and RHEL will receive software updates for 5 years. FreeBSD 9.0 will be supported for 1 year. The FreeBSD answer to long term support is to continuously upgrade. The Linux way is just easier for sysadmins.

WRT debian vs ubuntu: At home I use Debian. At work I use Ubuntu. Ubuntu's support and release schedule is predictable. Debian's isn't. (I know I am not the only one still soured by the very delayed Sarge release.)

Software support and predictable releases are not the only criteria for a good OS but it is a big plus. It is easy to choose Ubuntu LTS or RHEL. Both are "good enough," have long term support, and you can plan around the release cycle.

Written on 31 May 2012.
« Thinking about why Solaris has failed here
The secure boot problem »

Page tools: View Source, View Normal, Add Comment.
Search:
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Thu May 31 16:14:18 2012
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.