🚀 go-pugleaf

I modified uucp to run on a Purdue EE net channel.  As Brad Templeton
said, the basic change was to add a new connection protocol to
conn.c.  However, a few other mods were necessary; in particular, cico.c
had some code that *knew* it was talking to a tty -- a few ioctl() calls,
for example.  I moved those to someplace harmless and/or ignored the
return codes.  Then it would transmit fine, but wouldn't terminate cleanly.
The problem was the flow control protocol used by the network.  Specifically,
when a buffer is written, any further writes will block until that buffer
is read.  At close time, the packet driver writes a series of close messages,
and then waits for even one response.  Here, it never got to look for one,
because the second write hung.  The other end, of course, was doing the same
thing.