| 1 |
As the one who started this thread, it probably makes sense for me to comment on this a bit, because I agree. Gentoo is a distribution that has a utopian (IMHO) mixture of flexibility and compatibility. It is designed to accommodate such a wide variety of applications, that mailing lists like this one are necessary for certain niches. I would choose Gentoo for a server OS because it is so deeply compatible with hardware, and because of the package management system. Many on this thread have complained about Portage in a server environment, but the default installation only requires the initial emerge --sync- there's no emerge system or emerge world that is mandated or automated. Packages can be masked or blocked at the package level, or the machine level, and it is relatively easy to set up a local rsync mirror to update emerge, which can then be a point of control for all servers on the network, if they are properly configured. I started this thread, not because Gentoo is not ready for the server room, but because I need to learn more before I set it up for server applications. I have experimented with Redhat, CentOS, FC, Arch, DSL, Mandrake/Mandriva, Debian, FreeBSD, and some other distros, but Gentoo has always been the best when applied to my methods and standards. That's why I ask such questions- I need to identify my weak areas to leverage Gentoo's strong ones. |
| 2 |
|
| 3 |
Dan |
| 4 |
|
| 5 |
Computer Systems Manager |
| 6 |
|
| 7 |
-----Original Message----- |
| 8 |
From: Robert Bridge [mailto:robert@××××××××.com] |
| 9 |
Sent: Wednesday, October 01, 2008 10:34 AM |
| 10 |
To: gentoo-server@l.g.o |
| 11 |
Subject: Re: [gentoo-server] Server Packages for Gentoo |
| 12 |
|
| 13 |
On Wed, 1 Oct 2008 11:55:21 +0100 |
| 14 |
"Kerin Millar" <kerframil@×××××.com> wrote: |
| 15 |
|
| 16 |
> Well, this post turned out to be a lot longer than I had anticipated. |
| 17 |
> But I've seen so many comments that allude to Gentoo somehow being |
| 18 |
> unfit for purpose because it doesn't freeze off a so-called "stable" |
| 19 |
> tree so many times that, frankly, I get fed up with it and figured |
| 20 |
> that something had to be said. Gentoo, whilst certainly having its |
| 21 |
> fair share of foibles, doesn't get enough credit for the things that |
| 22 |
> it does well and the things that it does right. If one doesn't like |
| 23 |
> the way that Gentoo does things then there are surely other distros |
| 24 |
> out there that will meet one's expectations, such as they are. |
| 25 |
|
| 26 |
Right, imagine a live server getting hit by the expat problem, or a |
| 27 |
major gcc/glibc change? They hurt, they seriously hurt. |
| 28 |
|
| 29 |
That's what the "static package" people are referring to. A server that |
| 30 |
can be set up, and once running should need minimal updating, for |
| 31 |
security reasons. You can't do that safely in Gentoo. |
| 32 |
|
| 33 |
Some people are happy with regularly changing packages, restarting |
| 34 |
services every month because a new version of the server is in tree, |
| 35 |
dealing with the breakage induced by things like python upgrades, bash |
| 36 |
upgrades, portage upgrades, gcc upgrades, ... |
| 37 |
|
| 38 |
But for a 24/7 uptime on a high load server, most people consider those |
| 39 |
to be unacceptable. Now Gentoo can be got to not do those, but as |
| 40 |
anyone will tell you, updating a Gentoo box after a year is painful, |
| 41 |
and when you have to update to cover a critical security hole? Now try updating a Debian box after a year? |
| 42 |
|
| 43 |
Don't mistake one awkward piece of software which is not supported in |
| 44 |
the other distros for the general properties of those distros. Gentoo |
| 45 |
is good for tweaking, it's good for doing "Your own thing", that does |
| 46 |
not make it automagically better than Debian or RHEL, or SLES in the |
| 47 |
high-stability stakes. And, sorry to say this, one nice anecdote |
| 48 |
doesn't either. |
| 49 |
|
| 50 |
YMMV |
| 51 |
Rob. |
Archives