is not the invalidation problem more a problem inherent to
ffs' limitations rather than ibrowse itself?
any program that is writing to disk when the computer
crashes will invalidate a ffs partition. I guess
ibrowse does crash a lot though...
So... what happened to the IBrowse New Years Eve
update? Did I miss something?
