"I have a branch of 9front with fossil restored. I have discussed what would be needed to add fossil upstream again, and there was acceptance to the possibility if the issues get worked out _first_."
I took the Fossil sources from whatever was the most readily available distribution and after locating a single duplicated constant (56 * 1024 on one hand and 64 * (2<<10) on the other, I hacked one away), Fossil compiled on 9front without a hitch. Good enough for me to feel I can use it to rescue my "precious" data. My fear was that I would not be able to afford such a rescue if it got much more complex than that. So let's put to bed any delusion that I want Fossil included in 9front, I was quite satisfied with protestations that something no worse than the 9legacy version was in fact available with minimal effort. On the other hand, I am disappointed that the door unlocked by Venti and barely held ajar by Fossil may slam shut to 9front users and to that end I am going to make a new request. Now this is not an "or else" request, nor a promise, merely a wish based on comments in this forum to the effect that failures have been identified in Fossil (and Venti, too). If such a list already exists, that would be extremely welcome (to me, at least). If not, perhaps a summary of the type of triggers that cause failures would be helpful, at least as much as knowing who are the most knowledgeable developers in connection with this aspect. If all that's available is some hazy description, well, that's perfectly OK, if disappointing. Maybe for someone like me that will turn out sufficient to continue Fossil/Venti development. It's tempting to point out that trying to compete with 9front developers would be a mug's game, so not including a version of Fossil/Venti that can be successfully compiled and deployed is not going to handicap any 9legacy development. Again, none of the above is intended to cast aspersions on anyone. I reserve my opinions on the emotional undercurrents in the discussions that are still taking place here, but the value of the emotional baggage involved, in my opinion, is precisely zero, even though I have had quite a few occasions for muttering and even cursing into my beard (or is it under my breath?). Lucio. On Fri, May 17, 2024 at 6:53 PM Noam Preil <[email protected]> wrote: > I have found multiple deadlocks over the last few years, and only > bothered fixing one of them. That patch is in 9legacy, as well, now. > > During my IWP9 talk in which, among other things, I explained why I > intend to replace fossil despite curently using it, I demonstrated one > of the problems with fossil by (attempting to) install Go, which crashes > the file system _every single time_. > > I personally fixed over a dozen issues in Venti, and continue to find > more. To the best of my knowledge, those patches are currently _only_ > present in 9front. I was not aware 9legacy existed when I did that > work. > > I've lost some data to fossil crashes, since if it e.g. loses power > during a sync, it will end up _erasing_ a file rather than preserving > the old version, which has _broken boot_ if the system crashed while I > was editing lib/profile. > > I have a branch of 9front with fossil restored. I have discussed what > would be needed to add fossil upstream again, and there was acceptance > to the possibility if the issues get worked out _first_. > > The hostility on this list is pervasive and comes from all sides. If > your goal is positive engagement, this is not the place to do it. > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tad3dc0c93039a7d2-Mcee5e051d9e2b4e4696d1b06 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
