Subject: Re: Trying to talk to tty01 with cu...
To: William R. Dickson <wrd@awenet.com>
From: Bill Studenmund <wrstuden@nas.nasa.gov>
List: port-macppc
Date: 09/01/1999 11:45:00
On Tue, 31 Aug 1999, William R. Dickson wrote:

> Hi all,
> 
> So, I'm trying to set up dial-in on my system.  Ultimately it'll be a PPP
> dial-in, but for now I'd just like to get it to respond with a login
> prompt.  But I can't seem to communicate with the modem at all.  I've tried
> this:
> 
> tty01   "/usr/libexec/getty std.9600"   vt100   off secure
> 
> and this:
> 
> tty01   "/usr/libexec/getty std.9600"   vt100   on insecure
> 
> ...plus various speeds.

I thing mgetty might be better. getty works with modems, but assumes that
the modem is just there. If you need to do AT command setups on the modem,
getty won't do.

> I've kill -HUP'd init each time I've changed /etc/ttys.  But when I try to
> use cu to talk with the modem, I get:
> 
> cu: open (/dev/tty01): Permission denied
> cu: tty01: Line in use
> 
> This happens whether or not a line appears in ps ax indicating that getty
> is waiting for a connection on tty01.

cu has always given me problems. Try tip instead.

Do you have read/write access on /dev/tty01? where's the "permission
denied" comming from?

> If it's relevant, I've got the console on tty00; it works fine.  When I've
> got tty01 turned on in /etc/ttys, the following entry appears in the ps ax
> list:
> 
> 29349 ??  S      0:00.03 /usr/libexec/getty std.38400 tty01
> 
> Any suggestions?  Am I doomed?  Would it be helpful to install mgetty?

I think eventually, yes, about mgetty.

But try tip to talk to the modem. Also, check out /etc/remote - the data
file for tip setup. For twiddling the modem, you want a ":dc" in the setup
line (so tip won't wait for CD to be asserted before talking).

Take care,

Bill