I think there where two reported issues with fossil. On was a bug in ephermerial shapshots which could cause it to crash, this was fixed about 10 years ago but did exist for an embarassingly long time.
The other was a design decision rather than a bug which was not well communicated. Fossil was designed as a write buffer to be used in conjunction with venti. It could operate as a stand alone filesystem to replace the single user kfs. However if fossil fills up - because more has been written to it than it can hold or because snapshots have been turned on without a venti attached, it will crash badly and can (I believe) lose user data. The third issue with using fossil and venti is it is not very performant, it was reasonable when it was written in the early 2000s but is slow compared to modern Linux filesystems (I don't know how it compares to cwfs or hjfs). I have been using fossil and venti continuiously since 2004 and tend to jump to its defence. Re different kernels As I have understood it (others may correct me) the difference between cpu and terminal kernels is only the value one global variable (cpuserver) in the kernel, and the list of drivers compiled in - traditionally there was no graphics support in cpu kernels for example. -Steve ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T523d6e906a17a7cc-M105752d0fa6af0e964b6b87f Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
