🚀 go-pugleaf

OK, I give up.  I _cannot_ get uugetty to work.  Either I'm doing something
very obscurely wrong, or HDB uucp is totally braindead.

I'm running ISC 386/ix, which is SVR3, with HDB uucp.  I have two flavors of
COM2 defined:  /dev/tty01, which has no modem control, and /dev/ttyM01,
which has modem control.

If I run uugetty on /dev/tty01, then shortly after Ring Indicate blinks on,
uugetty drops DTR.  Since the modem has just answered the phone at this
point, this means uugetty conveniently hangs up as soon as it answers.

If I run uugetty on /dev/ttyM01, uugetty answers the phone OK, but uugetty
and uucico trample each other, because uucico creates a lock file called
LCK..tty01 while uugetty looks for LCK..ttyM01.  So uucico comes along and
prods the modem awake, then the modem and uugetty scream at each other for a
while, making the whole system very unhappy.

If I tell uucp to use /dev/ttyM01, then uucico dutifully waits for carrier
to come up...  forever, because the open won't complete until carrier comes
up...  at which point the poor guy trying to dial in gets really confused
when uucico starts dialing at him.

Am I screwed?  Or is it possible to dial in and out on the same line?
-- 
Larry Campbell                          The Boston Software Works, Inc.
campbell@bsw.com                        120 Fulton Street
wjh12!redsox!campbell                   Boston, MA 02146