Indeed, the coupling is moderately loose (I found one constant shared in
the code I compiled for 9front - Fossil from somewhere, probably p9p, but
maybe not - the 56000-byte Venti block size, I believe). But Fossil without
Venti is a much less valuable component, as I understand it. And Fossil
Fossil will run without venti, but the moment you connect it to a venti, it
cannot be standalone again, as it stands.
On Sat, 18 May 2024 at 14:50, Lucio De Re wrote:
> Please include me as well. I have an unambitious plan I would like to
> experiment with. And the most advanced version of
Please include me as well. I have an unambitious plan I would like to
experiment with. And the most advanced version of Fossil would fit
nicely into that. Also, am I mistaken in believing that in all of 9legacy,
9front and p9p, Fossil and Venti need to be treated as a bundle, possibly
starting
Just a simple note. When I compared the fossil version posted by Moody in the
original discussion thread to the one I am using (and IIRC it is the one in
the 9legacy git repository), I found that they differed in 2 points. One was
the increase of a msg buffer, which is probably no big issue,
> Responding off list shortly :)
I'd like to be included into the discussion as well.
Thanks.
--
David du Colombier
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T6b867aa3be7bf660-M789b993f6eb5e311f7e78821
Delivery options:
Responding off list shortly :)
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T6b867aa3be7bf660-M3fe517cc779e245e44a024b1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Noam Preil:
> I demonstrated one
> of the problems with fossil by (attempting to) install Go, which crashes
> the file system _every single time_.
This is a useful bit of evidence that needs following up. The go test
suite (which begins by installing and completely rebuilding go) is
running 24/7
