From: Jonathan Larmour <jifl@eCosCentric.com>
To: Joe Laffey <joe@laffey.tv>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, overseers@gcc.gnu.org
Subject: Re: GCC mirror changing IPs (fwd)
Date: Mon, 25 Feb 2008 01:01:00 -0000 [thread overview]
Message-ID: <47C1EB1E.9050106@eCosCentric.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802242204050.11964@pulcherrima.dbai.tuwien.ac.at>
> ---------- 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.
Looking at the current mirror setup, there's already an entry in the
mirrors class:
From *.laffeycomputer.com
However looking more closely, all the mirrors only help access to cygwin
releases, not any others. There is no priority access for GCC releases (at
least not in the FTPD configuration), and the timestamp on the file is
July last year so this has been the case at least since then, but probably
ever.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------ Opinions==mine
next prev parent reply other threads:[~2008-02-24 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 22:10 Gerald Pfeifer
2008-02-25 1:01 ` Jonathan Larmour [this message]
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=47C1EB1E.9050106@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=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).