Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!TOASTER.SFSU.EDU!eps
From: eps@TOASTER.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Is there such a thing as a uucp daemon?
Message-ID: <9106120113.AA16777@toaster.SFSU.EDU>
Date: 12 Jun 91 01:13:51 GMT
References: <1991Jun6.185715.16350@versyss.uucp> <139@gordius.gordian.com> <8295@auspex.auspex.com>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: eps@cs.SFSU.EDU
Organization: San Francisco State University
Lines: 16

In article <8295@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>Now, as the person who asked the original question is running SVR3.2,
>the above doesn't necessarily apply.  S5R3.2's UUCP has its *own* way of
                   ^^^^^^^^^^^
>doing UUCP over various transport layers; it uses TLI

That's only one of the options.  There are several others
in the source code, including a BSD 4.2-style sockets
implementation that does a getservbyname("uucp", "tcp").
It all depends on what's #defined in parms.h at compile time.

Will it interoperate with BSD uucpd?  Not out of the box.  For
one, AT&T's code uses 'e' protocol rather than 't' protocol over
TCP connections.

					-=EPS=-