From: steve@Nyongwa.CAM.ORG (Steve Z) Subject: Re: More modem login proplems... Date: 14 Jun 1992 13:51:01 GMT
In article <5136.2a372eb0@sunvax.sun.ac.za> abs@sunvax.sun.ac.za writes:
>Hi all,
>
>I have the same problem as mikee@seas.gwu.edu.
>I have getty_ps installed and can't get uugetty or modem line to work
>propperly. The modem is on ttys2 and when some one tries to log in the sytem
>just hangs. Any one who has had success with getty_ps, please send me or
>post your inittab and [uu]gettydef files.
>
>Thanks.
>Andre.
>abs@sunvax.sun.ac.za
>
>Linux is tops! Great stuff Linus and friends!
The inittab file:
As it says in README.linux, the arguments for this getty are reversed from
poe's (the one on the Linux root disk). Thus your inittab should say:
tty1:vt100:/bin/getty tty8 9600
[...]
ttys2:vt100:/bin/uugetty ttys2 9600
The gettydef files:
As far as I can tell, everybody who has had problems with this was using a
modem locked at a particular baud rate, and failed to realise that autobauding
means that getty will change the baud rate of the port from the connect
sequence sent by the modem. If this case applies to you, simply drop the
"\s\A" from the CONNECT string in the default file. Putting in the \A tells
getty to read the baudrate from the connect string sent by the modem and
set the port accordingly, which you don't want.
Another potential problem would be if you have a dumb modem that doesn't
send fancy CONNECT messages. In this case, you need to remove both the
INIT and CONNECT strings from the default file and change the WAITFOR string
from RING to \r (carriage return).
=======================================================================
If anyone else still has a problem with getty_ps not answering the line
correctly, please email me.
=======================================================================
Thank you.
--
Steve Z -- iconoclast at large
"Dyslexics of the world, untie!"
steve@nyongwa.cam.org