[SASAG] Linux Server Distro Recommendations

Ski Kacoroski kacoroski at gmail.com
Wed Aug 5 12:22:24 PDT 2009


On Wed, 2009-08-05 at 12:05 -0700, Atom Powers wrote:
> On Wed, Aug 5, 2009 at 10:29 AM, Ski Kacoroski<kacoroski at gmail.com> wrote:
> >
> > On the downside, it does tend to lag behind other distros in terms of
> > newer software so sometimes I have to compile my own software packages
> > or, more often, figure out the correctly Debian perl packages to install
> > to support a vendor's or open source package that I want to use.  A
> > recent example is the OpenLdap servers I just built up.  The Debian
> > packaged version was far enough behind that I decided to compile form
> > source and it took a few hours to get all the correct Debian pieces in
> > place to support the compile (e.g. TLS libraries, etc.).  I find it
> > better to use the Debian pieces where possible rather than compiling
> > everything from scratch because then I get security updates.
> 
> This is a concern.
> If the packages are behind, how do you deal with security updates?
> There are also many times, OpenLDAP 2.4 for example, where a
> point-release has major new functionality that I need; if I can't get
> a /maintained/ package for the software I need then it doesn't matter
> how "good" the OS is.

That is why I build OpenLdap from source.  I do not know of any major
vendor that keeps up-to-date on openldap in their package management
system so the same problem applies to Redhat or Suse.  For me, the
packages I build from scratch are Openldap, configuration management
(puppet, cfengine, etc.), and OpenNMS.  All other software we use is
either mature enough so the package management versions are ok or else
the vendor supplies the software as a complete, self contained installed
(e.g. OpenFire chat server, Splunk) so I do not need anything special
from the operating system.

cheers,

ski

-- 
"When we try to pick out anything by itself, we find it
 connected to the entire universe"            John Muir

Chris "Ski" Kacoroski, kacoroski at gmail.com, 206-501-9803
or ski98033 on most IM services





More information about the Members mailing list