Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!apple!sun-barr!lll-winken!cheers!uop!nsayer
From: nsayer@uop.EDU (Nick Sayer)
Newsgroups: comp.unix.questions
Subject: SunOS 4.0 - tty??/cua? troubles
Keywords: shut up, getty!
Message-ID: <1497@uop.uop.EDU>
Date: 28 Nov 89 20:01:14 GMT
Organization: University of the Pacific, Stockton, CA
Lines: 31

I have a Sun 2/170 with a standard Hayes compatable modem. I have two
/dev entries for the tty port it resides on, /dev/ttym0 and /dev/cua0.
In the nutshell UUCP book, it says that if I put ttym0 in /etc/ttytab
and /dev/cua0 in /etc/uucp/L-devices that three things will happen:

1. getty will not show up on the tty until a carrier appears.

2. anyone opening /dev/cua0 will steal the line and getty won't show up
until that line is closed.

3. If anyone is on /dev/ttym0, /dev/cua0 will be "busy."

As it turns out, this is happening:

1. getty shows up the instant the line is enabled. I can watch as the modem's
echoing creates the deadly embrace with getty.

2. If I kill the getty process and quickly open /dev/cua0, getty is shut
out, as it should be.

3. Since getty is having an echoing war on /dev/ttym0, /dev/cua0 is always
"busy" unless I turn off its entry in /etc/ttytab.

So the big problem as I see it is to get it so that DTR will be on, but no
getty will appear until DCD comes on (or DSR). RTFM didn't help.

---------------------------------------------------------------------
Nick Sayer | quack!mrapple@uop.edu or cheers!quack!mrapple@apple.com
... or { apple!cheers | pacbell!cogent!uop }!quack!mrapple
Packet radio: N6QQQ @ WB6V | (209) 952-5347 300/1200/2400 - login guest
Disclaimer: The BBC would like to appologise for that announcement