fyi i have been running a fossil/venti pair since 2004 and it has been solid.
what is too big - honest question.
i thought the biggest issues are:
performance - the elegance and generality sacrifice some performance, though this is not a problem for me.
lack of a tls fs interface - there is (imho) no excuse for a lack of tls these days.
no way for a user in (say) the ventidump group to request an immediate dump - handy for checkpointing a code release, though justing copying the release to a new dir is ok.
no way to push a vac score into the /archive hierarchy - nice for migrating in other backups.
all these are fixable and on my todo list but none have happened.
> On 10 Jan 2020, at 9:37 pm, hiro <23hiro@gmail.com> wrote:
>
>
>>
>> The major fly in the ointment is the outdated sha1 hash function used by venti
>
> major? fly? there's no problem with how sha1 is used by venti right now.
>
> a more substantial complaint would be that the venti/fossil system is
> way too big.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Ta5071137bc09d294-M7a56202f84a795cc3e7d9a1e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription