linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: kernel ftp ?
Date: Mon, 16 Jul 2001 11:12:41 -0700	[thread overview]
Message-ID: <20010716111241.M29668@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10107162000360.20223-100000@zirkon.biophys.uni-duesseldorf.de>; from schmitz@zirkon.biophys.uni-duesseldorf.de on Mon, Jul 16, 2001 at 08:01:35PM +0200


On Mon, Jul 16, 2001 at 08:01:35PM +0200, Michael Schmitz wrote:
> > >Which are hosted by montavista:
> > >rsync -avz --delete source.mvista.com::linuxppc_2_4 <directory>
> > >
> > >for the 'stable' 2.4 tree.
> >
> > Those are mirrors, the main repository is hosted by bitmover
> > (ppc.bitkeeper.com). But those mirrors should work fine as well..
>
> Yep, but does the bitmover sire offer rsync access? That's what most of us
> still use ...

No, we do not and will not offer rsync or FTP access.  Those are very
bandwidth intensive services, BK uses a tiny fraction of what they use,
and you can accomplish the same thing with a

	rm -rf /tmp/exported_tree
	bk pull
	bk export -tplain /tmp/exported_tree

That's way, way, way less bytes moved to get you a perfect mirror.
I really don't care if you use BK or not to do development, that is up
to you.  But you should use it to conserve bandwidth and you must use
it if you want the data from us.

I can easily understand you not wanting to learn a new tool, or having
some other reason, valid or otherwise, not to use BK.  That's fine.
But you need to understand that anyone providing a hosting service is
spending money to do so.  We've spent about $25K to date.  Right now,
we're behind a pair of T1 speed DSL lines that cost us about $800/month.
If we fill up those lines the DSL people will shut us down and we'll
have to move to real T1 lines.  That would at least triple our costs.
I think it's a lot more than that, last I checked a fractional T1,
around 400Kbits/sec, was $1000/month.

Our way around this problem is to get you to do one "bk clone" and only
"bk pulls" after that.  That will transfer _only_ the data which has to
be transferred, nothing else.  Even that is a substantial amount when
you multiply it all out by the number of people.  We'll deal with that,
we won't deal with full copies.

I know Mvista offers rsync/ftp access and they're welcome to do so.  They
make (some) money off of Linux/PPC so they can justify it.  I suspect,
however, when they find out that FTP/rsync is filling up a T1 line and they
have to buy more bandwidth, their management may raise a stink.  Money is
money, it's one thing to spend it when there is no other choice, it's quite
another for people to be wasteful.
--
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-16 18:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-15 14:10 kernel ftp ? Giuliano Pochini
2001-07-16  4:22 ` Steven Hanley
2001-07-16  7:38   ` Benjamin Herrenschmidt
2001-07-16 16:54     ` Michael Schmitz
2001-07-16 18:29       ` Benjamin Herrenschmidt
2001-07-16 18:01         ` Michael Schmitz
2001-07-16 18:12           ` Larry McVoy [this message]
2001-07-16 18:38             ` Michael Schmitz
2001-07-16 18:57               ` Larry McVoy
2001-07-22 20:30                 ` Troy Benjegerdes
2001-07-22 22:15                   ` Larry McVoy
2001-07-22 23:32                     ` Lars Magne Ingebrigtsen
2001-07-23  7:07                     ` Geert Uytterhoeven
2001-07-23  9:28                       ` Timothy A. Seufert
  -- strict thread matches above, loose matches on Subject: below --
2001-07-23  9:44 Zehetbauer Thomas
2001-07-23 15:38 ` Larry McVoy
2001-07-23 16:44   ` Troy Benjegerdes

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=20010716111241.M29668@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    --cc=schmitz@zirkon.biophys.uni-duesseldorf.de \
    /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 NNTP newsgroup(s).