Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeeds.sol.net!hammer.uoregon.edu!csulb.edu!data.ramona.vix.com!nnrp1.crl.com!not-for-mail From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: PANIC: Can not login in Date: Thu, 15 May 1997 05:52:09 -0700 Organization: Walnut Creek CDROM Lines: 32 Message-ID: <337B06F9.ABD322C@FreeBSD.org> References: <01bc60c7$ec1e5320$a299adcf@argus.axxis.com> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-STABLE i386) To: "Q. Wade Billings" <blitz@axxis.com> Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:40934 Q. Wade Billings wrote: > I have a FreeBSD 2.1.5 box that I can not log into, even from console. Well, it might help if you'd 'fess up and first tell us that you *did* to this poor box. :-) This and your other Linux vs BSD posting combine to give me the impression of someone saying "FreeBSD sucks, it didn't stop me from shooting my feet off with this shotgun here!" :-) > I have rebooted into single user mode and found that the owner of inetd may > have been changed, but since I have nothing to compare it to, I have This is where buying the CDROM really helps - you have a fully extracted filesystem on the 2nd CD and you can verify things like this from it (or resurrect the contents therefrom). Anyway, I don't know what you did to your inetd (or why you're even looking at _inetd_ to solve an "I can't log in" problem, but it should be bin.bin, mode 555). In any case, it doesn't sound like inetd is the problem at all since you wouldn't even _get_ a login prompt if inetd was broken (something tells me you're new at this :). I think you've simply spooged your password file somehow, but without actually being there or knowing what actions led to this state of affairs, I can't say what. Verify that /etc/*passwd are in good shape and then try a `vipw', make a null-change (e.g. delete a char and then add it back), and then save and quit. Assuming that your master.passwd file is not hosed, you should have everything properly rebuilt from this action. If it still doesn't work, you might check to see if something got blown out of /usr/lib - I suppose that nuking your DES libraries, assuming that you use DES, would have a similar effect. -- - Jordan Hubbard FreeBSD core team / Walnut Creek CDROM.