From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trying SRC_URI first during fetching
Date: Tue, 9 Jun 2009 15:48:26 +0200 [thread overview]
Message-ID: <200906091548.27007.volkerarmin@googlemail.com> (raw)
In-Reply-To: <200906091534.33767.alan.mckinnon@gmail.com>
On Dienstag 09 Juni 2009, Alan McKinnon wrote:
> On Tuesday 09 June 2009 15:04:54 Stroller wrote:
> > On 9 Jun 2009, at 05:16, Nikos Chantziaras wrote:
> > > Normally, portage will try fetching from GENTOO_MIRRORS during an
> > > emerge and SRC_URI comes last. I want to reverse this; try SRC_URI
> > > first and if that fails, only then proceed to fetch from
> > > GENTOO_MIRRORS. Doable?
> >
> > This is undesirable behaviour - te mirrors exist because SRC_URI may
> > often have limited bandwidth.
> >
> > The package's hosting may be donated to the software's author, for
> > instance, by a 3rd party, so when you go directly to SRC_URI, avoiding
> > mirrors, you wear out the author's welcome.
> >
> > Mirrors are hosted by people with gallons & gallons of bandwidth to
> > spare, who expect you to use it.
> >
> > It makes sense to use the mirrors FIRST.
>
> Definitely.
>
> I have to beat users over the head (metaphorically) with a stick to get
> them to use my mirror. They somehow have the idea that SRC_URI has better
> quality bits than my ftp server...
>
> By going to SRC_URI every time, they use up precious international
> bandwidth instead of local (of which there is heaps). Every six months,
> when Fedora or Ubuntu does a release, those users can saturate the entire
> pipe into this *country* - just to get isos that I already have publicly
> available and am begging them to use.
my university has a nice volume cap for all students. But everything
downloaded from its own network - including the ftp servers is 'free' - only
outside traffic counts.
Luckily, my university hosts a major gentoo mirror. Not rsync, but distfiles.
They also have ubuntu, suse, fedora stuff. Windows updates.. and still people
don't use it. Annoying.
next prev parent reply other threads:[~2009-06-09 13:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 4:16 [gentoo-user] Trying SRC_URI first during fetching Nikos Chantziaras
2009-06-09 7:41 ` Neil Bothwick
2009-06-09 13:04 ` Stroller
2009-06-09 13:28 ` Neil Bothwick
2009-06-09 13:34 ` Alan McKinnon
2009-06-09 13:48 ` Volker Armin Hemmann [this message]
2009-06-09 14:01 ` Alan McKinnon
2009-06-09 23:36 ` [gentoo-user] " Nikos Chantziaras
2009-06-10 7:11 ` Neil Bothwick
2009-06-10 7:19 ` Nikos Chantziaras
2009-06-10 7:25 ` Neil Bothwick
2009-06-09 15:56 ` [gentoo-user] " Arttu V.
2009-06-09 16:08 ` Alan McKinnon
2009-06-09 18:26 ` Volker Armin Hemmann
2009-06-09 18:49 ` Alan McKinnon
2009-06-09 21:57 ` Neil Bothwick
2009-06-09 22:10 ` Alan McKinnon
2009-06-09 22:17 ` Volker Armin Hemmann
2009-06-09 22:35 ` Alan McKinnon
2009-06-09 22:53 ` Volker Armin Hemmann
2009-06-09 23:27 ` Neil Bothwick
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=200906091548.27007.volkerarmin@googlemail.com \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.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