Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: comp.unix.i386
Subject: Re: Multiport Serial Boards...
Message-ID: <15447@bfmny0.UU.NET>
Date: 3 May 90 02:49:06 GMT
References: <2436@crash.cts.com> <511637@nstar.UUCP> <3941@thebes.Thalatta.COM> <1990May1.151500.2372@chinet.chi.il.us> <407@mtndew.UUCP>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Lines: 16

In article <407@mtndew.UUCP> friedl@mtndew.UUCP (Steve Friedl) writes:
>In general, uugetty sucks.  There are real problems with DTR
>contention between the incoming and outgoing devices, and I bet a
>donut that nobody out there actually has it working 100% right
>all of the time.  I have had a dozen people try to claim the
>donut, but *every time* it turned out that they had compromised
>on at least one area.

I have it working perfectly.  AT&T V/386 3.2.1, IPC 802 multiport serial
adapter, uugetty 1.1 3.2 06/24/88.  I prefer hardware flow control.
Incoming and outgoing uucp and logins work fine.

I did write a daemon that sits and clears CLOCAL on unused dialup lines
every so often, because of a bug in the IPC drivers, but that's not
uugetty's fault (UUCICO forgets to clear it if login fails).  No
compromise has been necessary.  It works all the time.