Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uakari.primate.wisc.edu!ctrsol!seth
From: seth@ctr.columbia.edu (Seth Robertson)
Newsgroups: news.software.b
Subject: Re: URGENT problem with updatemin
Summary: dbz warning
Message-ID: <1989Aug25.103042.4626@ctr.columbia.edu>
Date: 25 Aug 89 10:30:42 GMT
References: <1989Aug24.191942.5491@utzoo.uucp>
Reply-To: seth@ctr.columbia.edu (Seth Robertson)
Organization: Columbia University Center for Telecommunications Research
Lines: 30


(Those easily bored may skip the first paragraph)

Well after getting my active file trashed by updatemin (and thus
spending several hours watching the dust settle on my terminal while
my program was taking a half-assed stab at rebuilding it) I decided
this was as good a time as any to get dbz working.  I compiled
everything and installed it.  I then noticed that I hadn't gotten any
new news since I installed it.  Nothing in the errlog, nothing, in
fact, in any log.  I tried posting only to have relaynews hang during
startup.  In desperation, I tried rebuilding the history file &&
suddenly news started to flow.  Lets here it for documentation!!!

Summary:  If you are upgrading to dbz from dbm YOU MUST REMAKE THE
HISTORY FILE!!!

Other hints include:
cc -O dbz.c -c
ar rcv libdbz.a dbz.o
ranlib libdbz

&& during the config process, tell the script that your dbm library is
called by '-ldbz' (instead of -ldbm) and tell it to include the
directory which libdbz.a resides in the search path (e.x.
'-L/this/way/to/dbz')

and, one more once, rebuild the history file!!!
-- 
                                        -Seth Robertson
                                         seth@ctr.columbia.edu