>> Nvi needs some of the features of Berkeley DB 3.X (transactional
>> logging) in order to fix long-standing bugs in the application.
> Is DB 3.x the only workaround for these bugs?

Pretty much.  To make a long story short, all known versions of vi
(including the original) will lose changes if they crash at the
wrong time due to corrupted recover files.  The obvious solution is
to use standard transactional techniques like write-ahead logging
and recovery to ensure that the vi recover file isn't ever corrupt.
Berkeley DB 3.X has that infrastructure, but it's complex stuff.


Keith Bostic
Sleepycat Software Inc.         [EMAIL PROTECTED]
118 Tower Rd.                   +1-781-259-3139
Lincoln, MA 01773               http://www.sleepycat.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to