public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Cc: Joe Laffey <joe@laffey.tv>
Subject: GCC mirror changing IPs (fwd)
Date: Sun, 24 Feb 2008 22:10:00 -0000	[thread overview]
Message-ID: <alpine.LSU.1.00.0802242204050.11964@pulcherrima.dbai.tuwien.ac.at> (raw)

Hi Guys,

who of you is familiar with the setup we provide to mirrors?  I remember
we *did* have something special at least at some point in the past, but
don't remember specifics.

Gerald

---------- Forwarded message ----------
From: Joe Laffey <joe@laffey.tv>
To: gcc@gcc.gnu.org
Date: Sun, 24 Feb 2008 11:16:41 -0600 (CST)
Subject: GCC mirror changing IPs

Hi,

We operate a GCC release mirror in St. Louis, MO (mirrors.laffeycomputer.com).

This server has changed IP addresses, which is normally no worry on your end.
But the old IP had special access to the master server to be able to download
the releases right when they came out, and thus take some load off of your
servers. This new IP address does not seem to have that.

The old IP was 66.165.104.114 and the new IP is 71.91.230.170. Both should have
a revers DNS PTR of pong.laffeycomputer.com.

If you could enable the mirror access for the new IP I would appreciate it. Note
that the old IP may be active for a little while as well. I am using it to get
the latest release right now.

Thanks,

--
Joe Laffey                |       Visual Effects for Film and Video
LAFFEY Computer Imaging   |     -------------------------------------
St. Louis, MO             |       Show Reel http://LAFFEY.tv/?e09280
USA                       |     -------------------------------------
.                         |        -*- Digital Fusion Plugins -*-
--------------------------------------------------------------------------

             reply	other threads:[~2008-02-24 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 22:10 Gerald Pfeifer [this message]
2008-02-25  1:01 ` Jonathan Larmour
2008-02-25  3:03   ` Christopher Faylor

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=alpine.LSU.1.00.0802242204050.11964@pulcherrima.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=joe@laffey.tv \
    --cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).