On Mon, 2009-01-26 at 08:42 -0500, erik quanstrom wrote: > > That is my *entire* point. If fossil doesn't tell you that > > the data in its buffer was/is corrupted -- you have no > > reason to rollback. > > if you're that worried, you do not need to modify fossil. > why don't you write a sdecc driver that as configuration > another sd device and a blocksize. then you can just > add ecc on the way in and check it on the way out.
This approach will work too. But it seems that asking fossil to verify a checksum when the block is about to go to venti is not that much of an overhead. Thanks, Roman.
