5 Ways to Decide on a Linux Distribution
Prejudices and opinions aside, at some point in your career you'll be asked to select a viable Linux distribution for your corporate network. How will you choose? Will you use the same distribution that you use at home or will you do some research and find something that's corporate-ready? Are you up to the task? Do you know what to look for in a distribution to support a corporate environment? |
|
Comments (5)
This article is right up there with his "Fedora isn't relevant" piece. If it was in print it would be suitable for recycling and use as ferret litter or bird cage liner.
Tell me about it, Steven. I've gotten to the point I'm avoiding DaniWeb articles.
And it's not even 5 ways to choose a distribution. It's 5 things a business might want to consider when choosing a distribution. That's not even close to the same thing. And as you point out, there are some things you need support for, but there are many for which you don't.
Quoting: If we know enough to read between the lines and get, " 'commercial support' means only Red Hat Enterprise Linux, Suse Enterprise Linux and maybe, possibly, just maybe Ubuntu qualify," why not just come out and say it?
Or Oracle. Mandriva. Vector. Turbo. Debian (HP). Xandros. Yellow Dog (PPC). ClarkConnect.
Probably more.
Not to mention a growing number of VAR-type businesses supporting Linux, and often concentrating on the free ones like CentOS, Debian or Ubuntu.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Sign up and post (it is free) or Log in and post

If we know enough to read between the lines and get, " 'commercial support' means only Red Hat Enterprise Linux, Suse Enterprise Linux and maybe, possibly, just maybe Ubuntu qualify," why not just come out and say it?
Lumping everything under the "server" category is also a bit too general. File servers, Web servers, print servers ... routers and gateways, firewalls ... and then you have desktops of various types. I imagine there are many different ways to go for each of these uses. You might really need RHEL for a forward-facing Web server (although my shop seems to be moving away from RHEL to CentOS; guess we have a deep enough bench to deal with it ...), but for a print server or even a desktop, it's probably not so critical to have RH a phone call away.
In a related matter, that DaniWeb "join our group" popup that appears before the article displays is annoying. (FF isn't blocking it for some reason.)