Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!brl-adm!seismo!mcnc!ece-csc!ncrcae!ncr-sd!se-sd!kdj
From: kdj@se-sd.UUCP
Newsgroups: comp.os.minix,comp.mail.uucp
Subject: Re: uucp source copyright status - IMPORTANT
Message-ID: <1011@se-sd.UUCP>
Date: Tue, 31-Mar-87 14:12:15 EST
Article-I.D.: se-sd.1011
Posted: Tue Mar 31 14:12:15 1987
Date-Received: Thu, 2-Apr-87 03:54:17 EST
References: <480@gouldsd.UUCP> <43183@beno.seismo.CSS.GOV>
Reply-To: kdj@se-sd.UUCP (Doug Johnston x6243)
Distribution: comp.os.minix
Organization: NCR Corporation, SE - San Diego
Lines: 31
Keywords: copyright uucp uucico
Xref: utgpu comp.os.minix:466 comp.mail.uucp:385

In article <7319@boring.mcvax.cwi.nl> jack@boring.UUCP (Jack Jansen) writes:
>In article <2495@felix.UUCP> zemon@felix.UUCP (Art Zemon) writes:
>>
>>'Scuse me.  You're right, I "mispoke."  The point I was
>>making is valid, however.  It should be easy to write a
>>UUCP replacement using the Kermit protocol, which is well
>>documented and understood.  The program could be given away
>>for use under Minix.
>>
>At last! Someone who agrees with me!
>
     . . .
>
>The point is, why should we use those icky uucp protocols that are
>hardly documented, and unused except in some proprietary sofware
>(forgetting uulink and uuslave, for the moment).
>
>The *only* things we need are a way to reach another system, and some
>way to get files across to it (with a reasonable guarantee that they
>will be the same after transmission:-).
>
>-- 
>	Jack Jansen, jack@cwi.nl (or jack@mcvax.uucp)
The point is that UUCP is already being used and what many people want is
a way to communicate with what is already on systems.  The commentary above
makes it look like UUCP is only used in a few places and rather than 
thousands of Unix systems.  I agree that kermit is a better solution but 
that is , in many cases, irrelevent.

  Doug Johnston
  kdj@se-sd.SanDiego.NCR.COM