public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Bridge <robert@robbieab.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Server Packages for Gentoo
Date: Wed, 1 Oct 2008 15:34:04 +0100	[thread overview]
Message-ID: <20081001153404.5b01b1e6@robbieab.com> (raw)
In-Reply-To: <279fbba40810010355q5da249b0k47edad2306422afc@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]

On Wed, 1 Oct 2008 11:55:21 +0100
"Kerin Millar" <kerframil@gmail.com> wrote:

> Well, this post turned out to be a lot longer than I had anticipated.
> But I've seen so many comments that allude to Gentoo somehow being
> unfit for purpose because it doesn't freeze off a so-called "stable"
> tree so many times that, frankly, I get fed up with it and figured
> that something had to be said. Gentoo, whilst certainly having its
> fair share of foibles, doesn't get enough credit for the things that
> it does well and the things that it does right. If one doesn't like
> the way that Gentoo does things then there are surely other distros
> out there that will meet one's expectations, such as they are.

Right, imagine a live server getting hit by the expat problem, or a
major gcc/glibc change? They hurt, they seriously hurt.

That's what the "static package" people are referring to. A server that
can be set up, and once running should need minimal updating, for
security reasons. You can't do that safely in Gentoo.

Some people are happy with regularly changing packages, restarting
services every month because a new version of the server is in tree,
dealing with the breakage induced by things like python upgrades, bash
upgrades, portage upgrades, gcc upgrades, ... 

But for a 24/7 uptime on a high load server, most people consider those
to be unacceptable. Now Gentoo can be got to not do those, but as
anyone will tell you, updating a Gentoo box after a year is painful,
and when you have to update to cover a critical security hole? Now try updating a Debian box after a year?

Don't mistake one awkward piece of software which is not supported in
the other distros for the general properties of those distros. Gentoo
is good for tweaking, it's good for doing "Your own thing", that does
not make it automagically better than Debian or RHEL, or SLES in the
high-stability stakes. And, sorry to say this, one nice anecdote
doesn't either.

YMMV
Rob.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-01 14:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 16:17 [gentoo-server] Server Packages for Gentoo BRM
2008-09-30 17:28 ` Robert Bridge
2008-10-01 10:55   ` Kerin Millar
2008-10-01 14:34     ` Robert Bridge [this message]
2008-10-01 14:48       ` Spahn, Daniel
2008-10-01 15:23       ` Kerin Millar
2008-10-02  9:20       ` Pavel Labushev
2008-10-03 14:35       ` kashani
  -- strict thread matches above, loose matches on Subject: below --
2008-10-01 14:51 BRM
2008-10-01 15:10 ` Arturo 'Buanzo' Busleiman
2008-10-01 13:16 BRM
2008-09-30 17:36 BRM
2008-09-30 18:10 ` Spahn, Daniel
2008-09-30 20:51 ` Ajai Khattri
2008-09-30 14:43 BRM
2008-09-30 15:05 ` Graham Murray
2008-09-29 17:48 Spahn, Daniel
2008-09-30  8:28 ` Ramon van Alteren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081001153404.5b01b1e6@robbieab.com \
    --to=robert@robbieab.com \
    --cc=gentoo-server@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox