Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!sdcsvax!ucsdhub!udiego!stokes
From: stokes@udiego.UUCP
Newsgroups: comp.sys.att
Subject: uucp over tcp/ip
Message-ID: <641@udiego.UUCP>
Date: Mon, 23-Nov-87 12:48:55 EST
Article-I.D.: udiego.641
Posted: Mon Nov 23 12:48:55 1987
Date-Received: Thu, 26-Nov-87 05:47:28 EST
Organization: Univ. of San Diego, San Diego CA
Lines: 32
Keywords: brief summary of responses

I'd liketo thank the many of you who responded to my posting about
running uucp over tcp/ip.

The WIN TCP/IP 1.x is being replaced with 2.0 which is streams
based. 1.x does not pass eight bits of data and news/mail does
occasioanlly like to set the eighth bit.  This is why rlogin and
other 1.x utilities/programs will occasionally bomb.

Rewrites of uucp seeem to be a fairly widespread solution. I hope
AT&T adds 2.0 to the donation list for universities before I get
around to hacking uucp.

The people from AT&T who are working with the 'new' TCP/IP also hinted
(and some blabed) that other thingsare being written for a 
future update of the software that will make me very glad I
didn't shell out the $ for STARLAN. NAmely RFS (and a non AT&T
person told me about a NFS project but wouldn't give details and
the e-mail keeps bouncing back to me).

It also appears that the HoneyDanber folks wrote a uucp daemon. I
haven't gotten a look at this daemon but it sounds good. But I
already have a bunch of daemons running and hate to add more.

I post any more infor that I get. I'll also try to get a set of diffs
on the uucp code that I'll be playing with.


-- 
David Stokes                   "USD where the future is tomorrow
Academic Computing Department   and today is slightly behind schedule"
University of San Diego
(619) 260-4810 or {sdcsvax, sdsu, ucsdhub}!udiego!stokes