> 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. > 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? - erik
