Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!udel!haven!mimsy!tank!gargoyle!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: comp.unix.i386
Subject: Re: Re: Multiport Serial Boards...
Summary: You're gonna lose; we've got a few things coming soon....
Message-ID: <1990May6.151307.14714@ddsw1.MCS.COM>
Date: 6 May 90 15:13:07 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: karl@mcs.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc. - Wheeling, IL
Lines: 29

In article <407@mtndew.UUCP> friedl@mtndew.UUCP (Steve Friedl) writes:
>I write:
>> Specialix boards are indeed very fast, but they don't do bidirectional
>> modem interlocking -- you're stuck with uugetty (ugh)
>
>Randy Suess writes:
>>  Whoa!  What is wrong with uugetty?  Do you mean with a 
>>  particular ports card, or just in general?
>
>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.

Want to lose a donut?

We're going to have a solution within the next couple of weeks.  uugetty
does stink, for a number of reasons, not the least of which is the lack of
an "issue" file.  We're working on a solution -- a REAL solution, and beating 
on one well-known serial board vendor to make sure their drivers are 
>exactly< right (they aren't right now, but they ARE close, which is why 
they don't get the donut yet!).

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Public Access Data Line: [+1 708 808-7300], Voice: [+1 708 808-7200]
Macro Computer Solutions, Inc.   "Quality Solutions at a Fair Price"