Still broken...

I’ve had zero success in trying to recover from 10.4.10’s brokeness. I’m know going to have to attempt an “Archive and Install” to get 10.4.8 on the system, and then update back to 10.4.9. I thought I left the days of PC stupidity behind. Grrr.

Updating to 10.4.10 on Intel...

In a few words, don’t do it. Many things are now broken on my nice Mac Pro box. USB Flash drive doesn’t work. VMware Fusion is broken (yes, I even tried updating to the 4.1 beta, which doesn’t seem to install correctly). SoftRaid is giving me a warning about needing 10.4.8 or better. It’s not pretty. I was up until midnight last night trying to resolve some of these issues with no luck. How disappointing.

Taking a look at Mercurial

So, now that the dust has settled–to some degree–on distributed version control systems being the answer to every development problem, I decided to try a few out. To be honest, I tried a number of tools out months (a year?) ago, but many of them were still in the early stages of development and had a number of shortcomings. One of the tools I revisited recently was Mercurial.

Another update to fsfsverify...

There was a regression in fsfsverify that prevented it from detecting overflowed windows when the instruction stream wasn’t corrupted. That has been fixed, along with a couple of other minor adjustments. The new version is up and ready for use!

New version of fsfsverify released!

I’ve been hard at work for the past couple of weeks, and I’m proud to announce that an updated fsfsverify script is available. Functionally, the only difference is the addition of svndiff1 support. Underneath, the great majority of the code has changed to make it easier to support different types of svndiff streams. It should also be easier to hack, if you find yourself needing to add a feature. Enjoy!