Sounds to me like you want fossil to be a true cache -- lazily writing to venti as more space is needed (or at regular intervals) and reading back from venti if something is needed and not in cache.
I wonder if doing so would simplify fossil.... its size would become a function of peformance (to control data spill/fill rates). And one would have to always use fossil+venti and never just fossil. Not to mention venti then becomes the true file server and one can imagine building other front end cache filesystems. > This would be fine with me, however, it seems that, by doing > this, there's no way to get all of my mp3s listed in a single > directory -- they would be archived by snapshot date / number, and I'd > have to search through all of those to get a full list of music. You can always bind(1) all the snapshots under your music directory!
