Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!sean
From: sean@ukma.UUCP (Sean Casey)
Newsgroups: net.micro.att,net.unix-wizards
Subject: Re: Bizzare paranoia of /bin/login on 3b2
Message-ID: <2146@ukma.UUCP>
Date: Fri, 6-Sep-85 22:46:49 EDT
Article-I.D.: ukma.2146
Posted: Fri Sep  6 22:46:49 1985
Date-Received: Sat, 7-Sep-85 13:52:23 EDT
References: <174@chinet.UUCP>
Reply-To: sean@ukma.UUCP (Sean Casey)
Organization: The White Tower @ The Univ. of KY
Lines: 29
Xref: watmath net.micro.att:528 net.unix-wizards:14750

In article <174@chinet.UUCP> djc@chinet.UUCP (David J. Carpenter) writes:
>I have experienced a bizzare problem with logging in on the console
>on our 3b2.  Here's what would happen:  Unix: would send  login: , I
>would reply, then Unix would send Login incorrect immediately without
>asking for a password.
>...

We had the same problem here, that is, until our 3b2 died altogether.  I
tracked it down to the routine getpass(), which was returning a null
password because it couldn't open /dev/tty.  For some reason, only the
console couldn't open /dev/tty.  When I talked to AT&T, he explained that
the console was driven by a "pseudodriver" and the problem was probably in
the driver.  When I asked how the driver could suddenly go bad, he
responded "file system corruption", and told me to do a partial restore.
So maybe doing a partial restore would help.  We didn't get to, because
our machine refused to boot from floppy, and a long chain of problems
ended up in a complete reformat and reload, but the reload didn't take
for some reason and now we have a quite dead 3b2.  I really don't buy
the technician's excuse, but at this point, it doesn't really matter.





-- 

-  Sean Casey                           UUCP:   sean@ukma.UUCP   or
-  Department of Mathematics                    {cbosgd,anlams,hasmed}!ukma!sean
-  University of Kentucky               ARPA:   ukma!sean@ANL-MCS.ARPA