On Mon, 09 Jun 2014 18:22:26 EDT erik quanstrom <quans...@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!
