Path: utzoo!attcan!uunet!cs.utexas.edu!lib!watson!sob From: sob@watson.tmc.edu (Stan Barber) Newsgroups: news.sysadmin Subject: Re: Stuck with .UUCP forever? Message-ID: <195@lib.tmc.edu> Date: 20 Jun 89 06:00:50 GMT References: <444@logicon.arpa> <9415@b-tech.ann-arbor.mi.us> <57064@uunet.UU.NET> <9426@b-tech.ann-arbor.mi.us> <300@capmkt.COM> <9436@b-tech.ann-arbor.mi.us> <13756@ncoast.ORG> <13757@ncoast.ORG> Sender: usenet@lib.tmc.edu Reply-To: sob@watson.bcm.tmc.edu (Stan Barber) Organization: Baylor College of Medicine, Houston, TX Lines: 21 In article <13757@ncoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery) writes: >But UUCP doesn't work like the IP protocol; >it can't handle IP packets, and IP protocols can't handle UUCP packets, not >just because the protocols have different packet configurations but because >UUCP isn't designed to be running constantly and ignoring data not addressed >to the local system. The two do not work in the same way at all. > Not strictly true, Brandon. There are many sites that to UUCP over TCP/IP. For some sites, it's the only way they do TCP/IP. It's sorta like the experiments with RSCS that are being done with the BITNET II Project. The Internet provides what appears to be a leased-line for UUCP or RSCS to address the other site. It is correct that the design of UUCP is different that TCP/IP. STAN Stan internet: sob@bcm.tmc.edu Manager, Networking Olan uucp: {rutgers,mailrus}!bcm!sob Information Technology Barber Opinions expressed are only mine. Baylor College of Medicine