Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!tmsoft!mason
From: mason@tmsoft.UUCP
Newsgroups: comp.bugs.sys5
Subject: Re: CLOCAL, or catch-22
Message-ID: <166@tmsoft.UUCP>
Date: Mon, 10-Aug-87 09:02:23 EDT
Article-I.D.: tmsoft.166
Posted: Mon Aug 10 09:02:23 1987
Date-Received: Tue, 11-Aug-87 01:08:34 EDT
References: <325@nsta.UUCP> <25073@sun.uucp> <3607@sdcsvax.UCSD.EDU> <326@nsta.UUCP> <1312@killer.UUCP>
Reply-To: mason@tmsoft.UUCP (Dave Mason)
Followup-To: comp.bugs.sys5
Organization: TM Software Associates, Toronto
Lines: 23

In article <1312@killer.UUCP> jfh@killer.UUCP (John Haugh) writes:
:In article <326@nsta.UUCP>, amos@nsta.UUCP (Amos Shapir) writes:
:> The problem  essentially is: How  do you convince  getty to open  a port
:> without  waiting for  carrier, if  you do  not have  the carrier  signal
:> wired, and your terminal driver expects  to see it before proceeding? (I
:> do not claim there is no way, I'm rather new to sys V.3).
:
:Ok, failing the O_NDELAY approach, how about something typically more
:Unix-like.  Try a kluge.
:
:Have a program (that you write) open the port, with O_NDELAY set, and
:then set CLOCAL, close the port and exec getty.  If you get real lucky,
:the driver might just be nice the next time around on the open (when
:getty does it) and not require the O_NDELAY flag.

From Amos' previous postings I was rather surprised that he didn't understand
in the first place.  If he'd mentioned getty....ah well.

Failing John's approach, try something even more Unix-like, write your own :-).
There have been a couple of postings of getty's for modems (for use dialing
out & in on the same line) which would have the base for what you need, but
I expect National has the real getty source anyway :-).
	../Dave