From: Nick Cunningham <nick@monkeydust.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo mail server
Date: Tue, 27 Jan 2009 21:23:41 +0000 [thread overview]
Message-ID: <e99b2eae0901271323w2406abe1x732ad8e612cc0eec@mail.gmail.com> (raw)
In-Reply-To: <1233088701.24106.612.camel@brown.esteem.com>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
2009/1/27 Tom Brown <brown@esteem.com>
> Hey guys,
>
> I've been using gentoo on my desktop for several months now. I works
> great. It cut five minutes off my build time when I build our product
> tree. It went from 20 to 15 minutes.
>
> I setup our email server using Debian. Its been solid as a rock and very
> low maintenance. However, it provides an antiquated environment.
>
> I'm looking at using gentoo for the email so I'll have an up-to-date
> system. Peformance is fine on the Debian system, but hey, faster is
> always better.
>
> I was hoping you guys could give me warm fuzzies about stability and
> maintenance with gentoo when it comes to a production server.
>
> What about major upgrades? If I keep the system updated regularly, is a
> major upgrade necessary?
>
> Thanks!
> Tom
>
>
>
>
If your planning on running a stable server then managing a gentoo server is
probably a bit more time intensive, but will pay of in terms of having it
configured how *you* want and with the services *you* want running, not what
someone else thinks you should have.
As a rule of thumb dont run ~ARCH unless you absolutely need a certain
package (and even then, stick to keyword specific versions rather than
blindly keywording everything). Dont feel that you need to sync and update
every day, but *do* use tools like glsa-check (i think thats the right one
but im not in my gentoo isntall to check atm) to ensure you update programs
where security bugs are known.
Also its worth keeping an eye on things like the forums, and planet as often
when updates to packages are likely to break things, or they need some
manual intervention when updating, you see some signs of this in advance
(although if you see a major update in your emerge list you *should* be
stopping and going off to read up on it before blindly emerging).
Of course, all these things wont stop you causing breakages, but if you work
cautiously and have some idea of what your doing then gentoo does work very
well as a server.
- Nick
[-- Attachment #2: Type: text/html, Size: 2422 bytes --]
next prev parent reply other threads:[~2009-01-27 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 20:38 [gentoo-user] gentoo mail server Tom Brown
2009-01-27 20:56 ` [gentoo-user] " Nikos Chantziaras
2009-01-27 21:03 ` [gentoo-user] " Volker Armin Hemmann
2009-01-27 21:05 ` Alan McKinnon
2009-01-27 21:23 ` Nick Cunningham [this message]
2009-01-28 2:01 ` kashani
2009-01-29 3:32 ` Tom Brown
2009-01-29 16:26 ` [gentoo-user] " James
2009-01-30 18:35 ` kashani
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=e99b2eae0901271323w2406abe1x732ad8e612cc0eec@mail.gmail.com \
--to=nick@monkeydust.net \
--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