Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1545 comp.os.386bsd.questions:6859
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yarrina.connect.com.au!cleese!cleese!not-for-mail
From: newton@cleese.apana.org.au (Mark Newton)
Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions
Subject: Re: /etc/spwd.db, /dev/klog, and dmesg
Date: 14 Nov 1993 01:02:45 +1030
Organization: cleese.apana.org.au public access UNIX
Lines: 20
Message-ID: <2c2r6r$5ht@cleese.apana.org.au>
References: <CGF2oo.D8F@latcs1.lat.oz.au>
NNTP-Posting-Host: cleese.apana.org.au
Your problem with dmesg reporting "bad magic number" seems to be a bit
too profound to be caused by some dodgy X binaries. But anyway...
In article <CGF2oo.D8F@latcs1.lat.oz.au> wongm@latcs1.lat.oz.au (M.C. Wong) writes:
> I just wonder whether or not any of the following programs do update
>/etc/spwd.db (secure password db), xterm, tcsh, xbiff, xeyes, and xclock,
xterm and xbiff don't update the .db files, but they do try to read them.
That causes the error you're reporting.
I've had to recompile and reinstall xterm. I don't have the source for
xbiff readily at hand, so I'm using xbiff -file /var/mail/newton as a
temporary fix until I get Free86 2.0.
- mark
--
--------------------------------------------------------------------
I tried an internal modem, newton@cleese.apana.org.au
but it hurt when I walked. Mark Newton
----- Voice: +61-8-3224071 --------------- Data: +61-8-3222915 -----