From owner-freebsd-current Tue May 2 19: 8: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.columbus.rr.com (blizzard.columbus.rr.com [204.210.252.245]) by hub.freebsd.org (Postfix) with ESMTP id C43B037B5A8 for ; Tue, 2 May 2000 19:07:56 -0700 (PDT) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp9595035.columbus.rr.com [24.95.95.35]) by blizzard.columbus.rr.com (8.9.3/8.9.3) with ESMTP id WAA18658 for ; Tue, 2 May 2000 22:07:20 -0400 (EDT) Message-ID: <390F89DD.9798D712@columbus.rr.com> Date: Tue, 02 May 2000 22:07:25 -0400 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current Subject: Re: db 1.85 --> 2.x or 3.x? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the things to consider is the number of places db is used in FreeBSD code. Any bugs in db can manifest in any of these: contrib/bind contrib/global contrib/nvi contrib/perl5 contrib/sendmail crypto/kerberosIV crypto/heimdal lib/libc/gen/devname.c lib/libc/gen/getcap.c lib/libc/gen/getpwent.c lib/libc/gen/ttyname.c libexec/ypxfr sbin/init sys/dev/aic7xxx usr.bin/finger usr.bin/tsort usr.bin/vacation usr.sbin/sa usr.sbin/rpc.yppasswdd usr.sbin/rpc.ypupdated usr.sbin/ypserv contrib/amd contrib/cvs lib/libkvm pr/9350 is an example of db bugs effecting vi. (Would someone PLEASE apply the simple patch and close the damn PR!) -- Danny J. Zerkel dzerkel@columbus.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message