public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo mail server
Date: Tue, 27 Jan 2009 22:03:51 +0100	[thread overview]
Message-ID: <200901272203.52335.volkerarmin@googlemail.com> (raw)
In-Reply-To: <1233088701.24106.612.camel@brown.esteem.com>

On Dienstag 27 Januar 2009, Tom Brown wrote:
> 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

a) always build with buildpkg - for backups
b) look into demerge
c) scan the logs with elogv
d) think twice before updating

I have gentoo on a small dns/dhcp/web server here for our 'dormitory' and it 
works well. 




  parent reply	other threads:[~2009-01-27 21:04 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 ` Volker Armin Hemmann [this message]
2009-01-27 21:05 ` [gentoo-user] " Alan McKinnon
2009-01-27 21:23 ` Nick Cunningham
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=200901272203.52335.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.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