public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Brown <brown@esteem.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo mail server
Date: Wed, 28 Jan 2009 19:32:48 -0800	[thread overview]
Message-ID: <1233199968.24106.698.camel@brown.esteem.com> (raw)
In-Reply-To: <497FBC7D.2080801@badapple.net>

Freakin awesome guys!

Thank you very much for your replies. This is what I got out of it:

1) Gentoo evolves. There are no major upgrades. This is a huge "go with
gentoo" point. I've never seen an operating system that didn't have
issues after a major upgrade. This means an updated system with gentoo,
all the time. No 'reinstall from scratch' every two years. Oh yeah, I've
got software that won't work after a major upgrade.

2) Gentoo requires attention. These are production servers I'm talking
about. What sysadmin doesn't check in their production servers on
regular basis? Yeah, I check in the the debian servers all the time.
That's on top of the automated emails I get reporting on the health of
the system. Ok, I don't have to do anything to them. So, I'll have to be
carefully before doing an update. I don't see that as too much to ask if
I don't have to reinstall from scratch!

Thanks guys!
Tom





  reply	other threads:[~2009-01-29  3:32 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
2009-01-28  2:01 ` kashani
2009-01-29  3:32   ` Tom Brown [this message]
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=1233199968.24106.698.camel@brown.esteem.com \
    --to=brown@esteem.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