9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about fossil
Date: Mon,  9 Jun 2014 21:24:41 -0700	[thread overview]
Message-ID: <20140610042441.1696DB82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 09 Jun 2014 17:15:39 PDT." <1402359339.64717.YahooMailBasic@web184703.mail.ne1.yahoo.com>

On Mon, 09 Jun 2014 17:15:39 PDT "Brian L. Stuart" <blstuart@bellsouth.net> wrote:
> > With the trick I am talking about, there is nothing to stop
> > you from connecting to N different remote ventis.=A0 In effect
> > your local (by that I mean under your control, not necessarily
> > on the same machine) venti can be treated as just a buffer!
> =20
> I took a look at some things along those lines a few years
> back in the context of file systems aimed at laptops where
> the buffer allowed for operation when disconnected from
> the main server.  It wasn't strictly tied to venti as a back-end.
> There's a paper on it in the proceedings from IWP9 '09.
>
> http://4e.iwp9.org/papers/lapfs.pdf
>
> It would be interesting to build the same sort of thing in
> the fossil-venti connection rather than in the 9P path.

Interesting....  Wouldn't you get roughly the same semantics
(modulo symlinks) with fossil +  a local venti proxy + venti?

(Answering myself) Not really since in your scheme the
fileserver copy can change independent of your local copy and
venti can't deal with that as it implements the "many worlds
interpretation"! Even if A & B start with fossil initialized
to the same score, their further histories would diverge. We
need something more.

Thanks for the reference.



      reply	other threads:[~2014-06-10  4:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 20:39 Riddler
2014-06-07 23:17 ` Steve Simon
2014-06-07 23:49   ` Riddler
2014-06-08  8:04     ` erik quanstrom
2014-06-09 20:25       ` Riddler
2014-06-08  8:30     ` Steve Simon
2014-06-08  8:39       ` erik quanstrom
2014-06-08  7:03 ` Bakul Shah
2014-06-08  7:56   ` erik quanstrom
2014-06-08 16:56     ` Bakul Shah
2014-06-08 17:06       ` erik quanstrom
2014-06-10 10:59       ` Nicolas Bercher
2014-06-09 20:21   ` Riddler
2014-06-09 21:12     ` Lyndon Nerenberg
2014-06-09 21:25       ` erik quanstrom
2014-06-09 21:52         ` Bakul Shah
2014-06-09 22:22           ` erik quanstrom
2014-06-09 22:36             ` Bakul Shah
2014-06-10  0:15               ` Brian L. Stuart
2014-06-10  4:24                 ` Bakul Shah [this message]

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=20140610042441.1696DB82A@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).