SamMaEl wrote:
> 
> On Mon, 26 Jan 1998, Colin Wood wrote:
>
[ description of strange things happening and my useless suggestion
  deleted... ] 

> > > 	Has anyone else seen something like this happen? Right now I'm
> > > doing the 1.3 upgrade, hoping this will fix it. I'm in the habit of using
> > > su now, so having to log in as root all the time would/will be a pain. Not
> > > to mention it could screw up my file permission scheme. (I have alot of
> > > different files I have owned by different users, even though I'm the only
> > > one that uses the system, generally... just a habit ;-))
> > 
> > a 1.3 upgrade might fix most of the problems, but if your root partition
> > is really full then untarring over everything may leave you with a bunch
> > of truncated files....quite messy!
> 
> 	No.... master.passwd and passwd look fine. Though, I did not wipe
> them on my upgrade... I copied the 'originals' over the ones that etc.tgz
> copied over them.

You might need to remove spwd.db? and pwd.db and redo a passwd_mkdb (I
think that's the command, perhaps it's pwd_mkdb), or just edit
/etc/master.passwd with vipw and it'll regenerate the databases.  It
sounds like your passwd database files have been corrupted.
 
> 	Now, I just got another error I've never seen, this time from
> identd.	It gave this error:
> 
> identd[511]: /etc/pwd.db" Permission denied
> identd[511]: getpwuid() could not map uid (0) to name

Perhaps the permissions are wrong as well?  I'd definitely try to recreate
the passwd database files.

> 	I logged into a chat program that I run, which runs an ident
> client I wrote. And, it does an ident lookup... which normally does not
> give this error ;-) 
> 
> 	Another bizarre error I got, was when I rebooted the system after
> the upgrade....
> 
> Jan 26 09:36:15 hobbes root: WARNING: $xfs is not set properly.
> Jan 26 09:36:18 hobbes root: WARNING: $xdm is not set properly.
>
> 	I'm not RUNNING XDM, or XFS, and I actually didn't upgrade my /etc
> until after I upgraded everything and rebooted, so I don't know what
> caused THOSE errors...

This sounds like your /etc/rc and /etc/rc.conf are out of sync or
something like that.  Take a look at the end of /etc/rc.conf and see if
xdm and xfs are set...I believe that they were added between NetBSD
1.3_ALPHA and 1.3_RELEASE, although I can't be sure.
 
> 	*sigh* all this and I've been up for like.... too long ;-)

:-)

> 	Ryan
> 
> 	P.S. Does anyone know what changes have been made to grf_iv.c?
> Michael Zucca sent me a patch to hopefully get my q630 machine's internal
> video going properly, but when I patched it (with patch) I got some
> errors... should I just go ahead and download the newest one, or will that
> cause more problems? The sources I have are... hmmm... the newest file in
> /sys/arch/mac68k/dev is from Dec 1st, and the grf_iv.c gives a date of Nov
> 10. Should I just download the newest one? Michael?

If you're going to be running 1.3, you will need kernel sources that match
it, so _please_ download the 1.3 kernel sources if you're going to roll
your own kernel for a 1.3 system.  I assume that Michael's patch will
apply cleanly to it.  BTW, if this is just the sense code thing that
Michael mentioned, a copy of the patch is in the FAQ on puma (and
www.netbsd.org later today).

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.