[SASAG] Linux Server Distro Recommendations
tres at apollonian.net
Wed Aug 19 16:41:19 PDT 2009
I completely agree.
There will be shortcomings in any OS -- something will always be done
better in another OS; it's just a matter of where the development
teams want to put the limited resources they have. Now that said, I
can see the effectiveness of using the right OS in the right place
(i.e. OpenBSD is a good choice for packet filtering router); however,
the point of the tongue-in-cheek quoted comment and the post itself
was that the point of diminishing returns at most sites is reached
very quickly. In my experience, dealing with the shortcomings of any
particular OS choice is the most effective way to maintain low
entropy. Each new OS introduces a whole new set of "unknown unknowns"
to deal with, and in the end there's a whole new set of shortcomings
to learn to handle.
In the end, like most other things having to do with systems
engineering it's not about finding the right way, but about finding
the best-possible-under-the-circumstances way of doing things. :)
On Aug 19, 2009, at 10:31 AM, Lamont Granquist wrote:
> On Thu, 13 Aug 2009, Tres Wong-Godfrey wrote:
>> But if you do find that Debian is 'the one,' please let me know.
> The first principle that I use when evaluating operating systems is
> a simple one: all Operating Systems royally suck ass.
> Trying to find one that is "elegant" or "clean" or "the one" or
> something like that is avoiding evaluating OSen on the basis of what
> business requirements they satisfy.
> It used to be the case that apt-get really made Debian superior to
> RedHat in terms of package management, but yum has levelled that
> field. Beyond that I only see business reasons to use RedHat-based
> distros and minor annoyances (which your employer is paying you to
> work around).
> Members mailing list
> Members at lists.sasag.org
More information about the Members