public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: Matthew Langford <langfml@eng.auburn.edu>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, gcc@gnu.org
Subject: Re: http://gcc.gnu.org/mirrors.html
Date: Thu, 13 Dec 2001 11:41:00 -0000	[thread overview]
Message-ID: <20011213143953.A14040@disaster.jaj.com> (raw)
In-Reply-To: <Pine.SOL.4.10.10112121827310.20025-100000@caspian.eng.auburn.edu>; from langfml@eng.auburn.edu on Wed, Dec 12, 2001 at 07:14:42PM -0600

On Wed, Dec 12, 2001 at 07:14:42PM -0600, Matthew Langford wrote:
> "They" was a reference to public sites mirroring GNU.  They are already
> listed on the GNU mirror web page.

Ah, now I see what you're saying.  Pronouns missing an antecedent are fun...

Yes, there is not as much communication between the GNU sysadmins and us
as could be hoped for.  Mostly it's nothing more than a lack of time on
the part of the volunteers at either end.  No hoarding, no ivory-tower
syndrome, just lack of time.

If you'd like to contact the sysadmins of ftp.gnu.org and ask them whether
the mirror list is up-to-date, and if it is, provide a patch to mirrors.html,
that would be a good way to contribute.


> > In a way it is:  known mirror sites are allowed to bypass some (all?) of
> > the connection limits on the FTP server.
> 
> Maybe you are looking at things completely backward.  Instead of guarding
> the software, and worrying about who is coming in to steal the software
> and rob your bandwidth,

I'll ignore the rest of your flames and just explain this:  gcc.gnu.org
is extremely overloaded.  For that reason anonymous FTP has been severely
restricted (and I think it's been disallowed completely on some of the
more popular projects).  We're trying to move anonymous CVS access off
onto another system also.  It's not about "robbing bandwidth," it's about
having some bandwidth left over so that the developers can actually check
in code changes.  :-)  Right now CVS commits of multiple files can often
get dropped partway through.  That doesn't benefit /anyone/.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2001-12-13 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 14:11 http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-07  7:04 ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer
2001-12-07 14:20   ` http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-12 16:54     ` http://gcc.gnu.org/mirrors.html Phil Edwards
2001-12-12 17:23       ` http://gcc.gnu.org/mirrors.html Matthew Langford
2001-12-13 11:41         ` Phil Edwards [this message]
2001-12-13 15:28           ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer
2001-12-13 16:26             ` http://gcc.gnu.org/mirrors.html Phil Edwards
2001-12-13 16:59             ` http://gcc.gnu.org/mirrors.html Matthew Langford
  -- strict thread matches above, loose matches on Subject: below --
2000-05-31  0:28 http://gcc.gnu.org/mirrors.html Joerg Faschingbauer
2000-05-31 11:30 ` http://gcc.gnu.org/mirrors.html Gerald Pfeifer

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=20011213143953.A14040@disaster.jaj.com \
    --to=pedwards@disaster.jaj.com \
    --cc=gcc@gnu.org \
    --cc=langfml@eng.auburn.edu \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).