All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: coreteam@netfilter.org
Cc: Netfilter Mailinglist <netfilter@lists.netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: [ADMINISTRATIVE] scheduled downtime for new netfilter.org machine
Date: Tue, 3 Aug 2004 15:43:11 +0200	[thread overview]
Message-ID: <20040803134311.GD26969@sunbeam2> (raw)

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Hi!

As the current netfilter.org server setup of two old UltraSPARC boxes
(vishnu.netfilter.org, lakshmi.netfilter.org) is running at it's
performance limit, we're going to replace one of them with a Dual G5
(PPC64) machine, called durga.netfilter.org.

I'll be mounting the machine into the hosting rack next Monday
(2004-08-09), after which I will gradually migrate individual services 
to the new box.  

First step of migration is to move the mailinglist explosion from
lakshmi to durga.  Please expect some delays in mail delivery.

If anyone encounters unexpected problems, please send me email to my
non-netfilter account: laforge@gnumonks.org

Thanks for your patience,
	Harald
-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-08-03 13:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040803134311.GD26969@sunbeam2 \
    --to=laforge@netfilter.org \
    --cc=coreteam@netfilter.org \
    --cc=laforge@gnumonks.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.