From: Galevsky <galevsky@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo on the server side
Date: Thu, 29 Nov 2007 14:54:58 +0100 [thread overview]
Message-ID: <d5cfc3af0711290554i7baa42c1g6131a5b2bfd115e7@mail.gmail.com> (raw)
In-Reply-To: <a964044f0711290510t76492382p3106f0c2101dc303@mail.gmail.com>
It mainly depends on your own feelings. I think that a debian stable
is a very good choice for a prod' server, but I really dislike the way
Debian manages daemon and prefer the Gentoo approach. Updates are not
painless...for sure, but you have to consider your needs first (what
tools do you need ? typical web services ? extra lib from different
languages ? any time reserved for maintenance or the server cannot be
off ?). Then, updating is not a must. Believe me, an up-to-date
machine is nice .... when you want brand new lib/features/softwares.
Do your server need to be so.. up-to-date ?
Finally, if you take time to estimate what should be updated prior to
emerge the whole world, you can plan your updates and organize the way
to go back if required.... and updates are not nightmares. (But have a
look at the handbook:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2). You
also need tools like dispatch-conf to undo easily your conf files
changes.
Gal'
On Nov 29, 2007 2:10 PM, Rafael Barrera Oro <borafael@gmail.com> wrote:
> First of all, thanks to everybody for sharing your experiences, very
> helpful information indeed, specially now that i need some guidance.
> For now, the conclusion i can reach is that Gentoo is perfectly adequate
> to use on a server with the only downside of the need to have special care
> with updates.
> Ricardo, i find really encouraging the fact that your lab uses Gentoo for
> their servers. Nevertheless it would be great if you could tell us a little
> about your lab's experience with updates, which seems to be the only issue
> when using Gentoo on a server.
> Another thing i noticed is that some of you recommend to have a secondary
> server to perform tests, i totally agree with this. Unfortunately i do not
> think that having such thing will be possible since the server will be
> charged to a client and i do not think they will agree to buy a second
> server (even if its the right thing to do, which i believe so), in such
> case, would you still recommend Gentoo?.
>
> Again, thanks to everybody for the information.
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-29 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 18:01 [gentoo-user] Gentoo on the server side Rafael Barrera Oro
2007-11-28 21:45 ` Mark Shields
2007-11-28 22:11 ` Arturo 'Buanzo' Busleiman
[not found] ` <474DE646.50708@robertspahr.com>
2007-11-29 5:06 ` Billy Holmes
2007-11-29 13:10 ` Rafael Barrera Oro
2007-11-29 13:40 ` Wayn0
2007-11-29 14:36 ` Billy Holmes
2007-11-29 16:53 ` Derek Bodner
2007-11-29 17:05 ` Neil Bothwick
2007-11-29 13:54 ` Galevsky [this message]
2007-11-28 22:17 ` Jason Carson
2007-11-28 22:49 ` Ricardo Saffi Marques
2007-11-29 0:45 ` Ric de France
2007-11-29 0:37 ` Mark Kirkwood
2007-11-29 16:44 ` Aniruddha
2007-11-29 19:09 ` Dan Farrell
2007-12-01 7:03 ` Alan
2007-12-01 10:29 ` Eray Aslan
2007-12-01 15:01 ` Billy Holmes
2007-12-02 22:58 ` [gentoo-user] PHP 5 masked notice (was: Gentoo on the server side) Jil Larner
2007-12-06 21:35 ` Alan
2007-12-07 16:34 ` Billy Holmes
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=d5cfc3af0711290554i7baa42c1g6131a5b2bfd115e7@mail.gmail.com \
--to=galevsky@gmail.com \
--cc=gentoo-user@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