public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthew Langford <langfml@Eng.Auburn.EDU>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, gcc@gnu.org
Subject: Re: http://gcc.gnu.org/mirrors.html
Date: Wed, 12 Dec 2001 17:23:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10112121827310.20025-100000@caspian.eng.auburn.edu> (raw)
In-Reply-To: <20011212190100.A10665@disaster.jaj.com>


On Wed, 12 Dec 2001, Phil Edwards wrote:

> Matthew Langford wrote:
> > You _know_ they are mirroring, and they are mirroring a
> > gzipped release of your software.  Why not mention _them_ on your
> > downloads page?
> 
> Maybe they don't want the entire world downloading from them.
> 
> People choose to mirror software for reasons /other/ than making it
> available to everyone else out there.  I used to mirror a subset of the
> Linux kernel patches repository, but it was for me and my colleagues
> in the same building, not for the rest of the planet.  Listing me as a
> "mirror site" would have been harmful, not helpful.

"They" was a reference to public sites mirroring GNU.  They are already
listed on the GNU mirror web page.  This is a superset of GCC.  If they
are willing to be listed to the world as carrying the entire GNU software
universe (which includes the GCC stuff), they are already mirroring the
main part, the Download, of your distribution.  It would be helpful to
visitors to mention there are alternatives to the very few listed on your
web page.  Or perhaps you like everyone in the US and Canada tagging the
network connections of the poor saps who walked to your ivory tower
and volunteered their mirrors?  

The link to the actual gcc.org download is spelled out but not an active
link.  I suppose this is to strongly encourage people to use the mirrors.
But then, you don't have many mirrors listed:  one for the North American
continent, two for South America, and one for Australia, from what I saw. 
 Oh well, yank it from another continent.


> > You are making people come to you, like it's a special privilege to mirror
> > GCC,
> 
> 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, you could think of it as _distributing_ your
releases, and how to _put_ it on as many servers as possible.  In that
direction, making use of the existing GNU mirroring system (both by
web-mention and by update-seeding) would be most helpful, I think.  From
the first viewpoint you seem to be doing nicely; the second one, you are
adequate only for yourselves, through CVS, and Europe and Japan.



--
MattLangford 

  reply	other threads:[~2001-12-13  1:16 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       ` Matthew Langford [this message]
2001-12-13 11:41         ` http://gcc.gnu.org/mirrors.html Phil Edwards
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=Pine.SOL.4.10.10112121827310.20025-100000@caspian.eng.auburn.edu \
    --to=langfml@eng.auburn.edu \
    --cc=gcc@gnu.org \
    --cc=pedwards@disaster.jaj.com \
    --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).