Date: Sun, 8 Mar 1998 18:37:12 +0000 From: "Riley J. McIntire" <chaos@tgci.com> To: "Evan Champion" <evanc@synapse.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Passwords messed up during botched "upgrade" Message-ID: <199803090236.SAA12293@janeway.tgci.com> In-Reply-To: <00d901bd4af7$f2910610$c9252fce@cello.synapse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Should have mentioned I tried that. Didn't work at all. I restored not only the master.passwd but pwd.db. After that I restored the entire /etc. I did do a new sysinstall upgrade using the boot floppy. Got everything except the sources and it worked ok but it was using the old kernel. To build a new one I decide to get the new sources using postconfigure in sysinstall--just the sources--and after a short time lost all passwords again. I'm assuming the binaries that came with 'em hosed the system again??? I really don't understand what's going on. Anyway, I'm going to restore and upgrade again just to get the system stable and working for tomorrow. I'm really sick of this socalled "upgrade". I think the best bet is to backup and just do a completely clean install and then reconfigure. Or probably better to use cvsup, but as I mentioned I had problems with that. Cheers, Riley > From: "Evan Champion" <evanc@synapse.net> > To: <chaos@tgci.com> > Subject: Re: Passwords messed up during botched "upgrade" > Date: Sun, 8 Mar 1998 20:08:58 -0500 > Try doing vipw, then just write and exit without changing anything. > You're likely having problems because the password .db files are out > of data, even though you restored the right master.passwd -- nothing > uses master.passwd, only the .db files that are generated from it. > > Evan > > -----Original Message----- > From: Riley J. McIntire <chaos@tgci.com> > To: freebsd-questions@FreeBSD.ORG <freebsd-questions@FreeBSD.ORG> > Date: Sunday, March 08, 1998 3:14 PM Subject: Passwords messed up > during botched "upgrade" > > > Well, I really screwed this one up. After getting errors installing > cvsup I decided to do an upgrade from 2.2.2-R to 2.2.5-R using > sysinstall. However, I ran it from /stand in multi-user mode as > opposed to either using the boot floppy or (I assume this would > work?) /stand/sysinstall in single user mode. > > Anyway, I started getting weird error messages from sendmail (forgot > to shut it down) and decided to quit and restore from backups. > Problem with that was the backup was no good. :( The last good one > was a couple weeks old. > > This did not seem much of a problem, I'd backed up /etc manually in > a couple places, and /usr was intact, so I restored from the old tar > file the files in root, /dev /bin, /lkm. > > But I could *not* log on! Users seemed to still be there but with > the wrong passwords. I restored master.passwd from /var/backups and > still had trouble. One or two users could log on, but a couple > others couldn't! > > IIRC the username length changes from 2.2.2-R to 2.2.5-R? Is this > causing the passwords to mess up? I assume some binaries were > replaced with 2.2.5 versions and I didn't restore them? Which ones? > > Any suggestions on how to proceed? I'm thinking I'll use sysinstall > from the boot floppy after restoring the system's group and > master.passwd files (again) and proceed from there. > > Help and/or advice would be greatfully appreciated! > > Cheers, > > Riley > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803090236.SAA12293>