From: Andreas Dilger <adilger@clusterfs.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bitkeeper-announce] Re: bkbits.net downtime
Date: Fri, 31 Jan 2003 16:52:21 -0700 [thread overview]
Message-ID: <20030131165221.O3904@schatzie.adilger.int> (raw)
In-Reply-To: <20030131224627.GA1686@f00f.org>; from cw@f00f.org on Fri, Jan 31, 2003 at 02:46:27PM -0800
On Jan 31, 2003 14:46 -0800, Chris Wedgwood wrote:
> On Fri, Jan 31, 2003 at 02:50:18PM -0700, Andreas Dilger wrote:
> > Actually, with BK it should be possible to have read only clones on
> > multiple servers, should it not? Not that I'm saying BK should foot
> > the bill to do that, but having read-only clones of the primary
> > kernel trees would avoid most downtime.
>
> At the risk of suggesting something insanely complex...
>
> ... assuming BK read-only copies do work, why not actually have 'bk
> pull' for hosts which can serve RO copies of the trees? You
> could use SRV records to locate these transparently to what has been
> deployed now (I'm not really a fan of rfc2782.txt but nonetheless it
> exists and others are using it, so it's a 'standard' of sorts).
>
> Presumably doing something like this means you could have many people
> voluntarily providing RO trees for different projects and lessen the
> load on the bitmover infrastructure...
That's exactly what I was suggesting, but not very clearly it seems.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-31 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 21:14 Larry McVoy
2003-01-31 21:50 ` Andreas Dilger
2003-01-31 22:46 ` [Bitkeeper-announce] " Chris Wedgwood
2003-01-31 23:06 ` Anders Gustafsson
2003-01-31 23:07 ` Chris Wedgwood
2003-01-31 23:12 ` Anders Gustafsson
2003-01-31 23:52 ` Andreas Dilger [this message]
2003-01-31 22:50 ` Larry McVoy
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=20030131165221.O3904@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®