Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken!uunet!brunix!rca
From: rca@cs.brown.edu (Ronald C.F. Antony)
Newsgroups: comp.sys.next
Subject: Re: device busy errors using tip and kermit
Keywords: cua ttyda ttya tip problems cu
Message-ID: <58115@brunix.UUCP>
Date: 30 Nov 90 21:15:38 GMT
References: <14903@cs.utexas.edu> <1990Nov23.032248.11353@blackbox.lonestar.org>
Sender: news@brunix.UUCP
Reply-To: rca@cs.brown.edu (Ronald C.F. Antony)
Organization: Brown University Department of Computer Science
Lines: 47

In article <1990Nov23.032248.11353@blackbox.lonestar.org>
cbradley@blackbox.lon\
estar.org (Chris Bradley) writes:
>               /dev/ttya       For local terminal connection
>               /dev/ttyda      For connection to modem
>               /dev/cua        For uucp, tip/cu dialout
>all refer to serial port `A' on the back of the machine.  Earlier
>[...]
>If you're trying to set up your cube to allow just outgoing calls, then
>you can forget about /dev/ttya and /dev/cua.  In John's case, he
>should probably set the `dv' macro in /etc/remote to point to /dev/ttyda,
>and turn off the ttyda port in /etc/ttys.  This will allow tip/cu to
>use the `A' port for outgoing calls -- and a Mac modem cable will work
>fine for this.
>If, however, you want to be able to receive incoming calls on port A,
>>and< you would like to occasionally override getty to allow a process
>to dial out, then you should use the /dev/cua interface to port A.
>In the 1.0(a) distribution, the perms for /dev/cua are set mode 600,
>owner uucp.  This is cool as long as uucp owns the process that is
>trying to open the port.  But if it's you, instead, trying to have
>a kermit or tip session, then you won't be able to open the port and
>both tip and kermit will report that the device is `busy' -- couldn't
>be opened.
>To fix this, set the perms for /dev/cua to mode 666.  This allows processes
>owned by users other than uucp to open the port for read/write.



All this is not necessary: using /dev/ttyda in /etc/ttys is enough.
Having turned on /etc/ttyda does not prevent you from using /dev/cua
in kermit for dial out. Thus if you want dial in and out use
/dev/ttyda on in the /etc/ttys file and use /dev/cua for kermit or
tip. The only thing you might need to do is change permissions on
/dev/cua. Main point being: use each device for what is was designed:

cua = Calling Unit A
ttyda = TTY on Dialupline A

Ronald 




------------------------------------------------------------------------------
"The reasonable man adapts himself to the world; the unreasonable one persists
in trying to adapt the world to himself. Therefore all progress depends on the
unreasonable man."   G.B. Shaw   |  rca@cs.brown.edu or antony@browncog.bitnet