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 15:36:20 -0700	[thread overview]
Message-ID: <20140609223620.3E87FB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 09 Jun 2014 18:22:26 EDT." <8ce6a63b2511227ae6a36f78781c78b3@brasstown.quanstro.net>

On Mon, 09 Jun 2014 18:22:26 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > Over the weekend I was playing with fossil and "copied" my
> > fossil partition using its last score, swapped the two disks
> > (under virtualbox) and rebooted.  df now shows 1MB in use! So
> > if you init fossil from the score of an existing installation,
> > you can make do with a lot less space -- only depends on how
> > much new stuff you create every day! Even there you can
> > probably write a script that watches df and when it reaches
> > some limit creates an archival snapshot or just snapshot
> > every hour or so!
>
> i am not sure i follow along.  to me, 1g of disk space is a trival
> amount, and  in cases where space might be a bit tight, like on
> a sd card, i would think reliablity would push one to put venti
> on another media.

Just pointing out that 512MB or whatever is the new
requirement only applies to a fresh install.

> > This idea can drastically reduce new installation time.
> > Someone (vsrinivas?) has created vtrc.c, a venti proxy, a
> > variation of Russ's venti/ro.c. This can probably be enhanced
> > so that if a block is not found in your local venti, it asks a
> > public venti (and writes back that block to the local venti).
>
> isn't this is trading a one-time small cost for a ongoing cost, and
> a set of new problems.  what if the public venti is out-of-sync, or
> gone?

Just pointing out that we haven't explored venti enough!
Other solutions are possible (with their own problems).

With the trick I am talking about, there is nothing to stop
you from connecting to N different remote ventis.  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!

In spirit this is like much like what bittorrent does but much
more flexible.  Like in bittorrent you pull all the stuff you
depend on (but that can be done in background). You can even
start streaming your remotely stored video right away!



  reply	other threads:[~2014-06-09 22:36 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 [this message]
2014-06-10  0:15               ` Brian L. Stuart
2014-06-10  4:24                 ` Bakul Shah

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=20140609223620.3E87FB827@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).