From owner-freebsd-current Tue Jul 10 8:17:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from abyssinian.sleepycat.com (abyssinian.sleepycat.com [199.103.241.218]) by hub.freebsd.org (Postfix) with ESMTP id 71B5737B406; Tue, 10 Jul 2001 08:17:26 -0700 (PDT) (envelope-from bostic@abyssinian.sleepycat.com) Received: (from bostic@localhost) by abyssinian.sleepycat.com (8.10.1/8.10.1) id f6AFHMN08697; Tue, 10 Jul 2001 11:17:22 -0400 (EDT) Date: Tue, 10 Jul 2001 11:17:22 -0400 (EDT) From: Keith Bostic Message-Id: <200107101517.f6AFHMN08697@abyssinian.sleepycat.com> To: keramida@ceid.upatras.gr Subject: Re: picking a DB (Re: nvi maintainer?) Cc: current@FreeBSD.ORG, mi@aldan.algebra.com, msmith@FreeBSD.ORG, wes@softweyr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> 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. Regards, --keith =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Keith Bostic Sleepycat Software Inc. bostic@sleepycat.com 118 Tower Rd. +1-781-259-3139 Lincoln, MA 01773 http://www.sleepycat.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message