Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!uunet!blackbox!cbradley
From: cbradley@blackbox.lonestar.org (Chris Bradley)
Newsgroups: comp.sys.next
Subject: Re: Modem hookup problems (2400 baud)
Summary: use /dev/cua
Keywords: modem
Message-ID: <1990Nov11.050518.13057@blackbox.lonestar.org>
Date: 11 Nov 90 05:05:18 GMT
References: <1990Nov9.144735.12379@uunet!unhd>
Followup-To: comp.sys.next
Distribution: usa
Organization: Businessland Advanced Systems
Lines: 30

In article <1990Nov9.144735.12379@uunet!unhd> bwb@unh.edu (Brent Benson) writes:
>
>The relevant part of my /etc/ttys file looks like this:
>
>ttya	"/usr/etc/getty std.2400"	unknown	on	secure
>ttyda	"/usr/etc/getty std.2400"	dialup	on
                                               ^^^^

Oh, boy, I've been around on >this< one before.  From your /etc/ttys
setup, I guess that you might be trying to allow both dial-in and dial-out
on the same modem.

Turning on both ttya and ttyda will cause you problems like the ones
you described.  This is because (and I'm not a guru) they are supposed to
be mutually exclusive:  ttya is for activating port A for a terminal
device, and ttyda is for connecting a modem device.  If you specify
in /etc/ttys that both are active at the same time, then my guess is
that getty gets >real< confused.

IF all you want to do is to dial out using tip, cu (or equiv), then
don't turn on either ttya or ttyda in /etc/ttys.  If all you want to 
do is to allow remote logins, then turn on ttya if the remote is a 
terminal through a null-modem cable, or turn on ttyda if the remote
user will be dialing in through a modem.

If your plan is to allow dial-in modem connections, but you also want
to be able to pre-empt the port for dial-out on demand, then turn
on ttyda in /etc/ttys, but use /dev/cua for your calling device in 
your /etc/remote file.  See the man page for zs(4) for a description
of how ttyda and cua interact.