Xref: utzoo comp.protocols.tcp-ip:7635 comp.unix.wizards:17197
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards
Subject: Re: Using the uucp daemon (TCP/IP) on System V.3 with TCP/IP
Keywords: UUCP TCP/IP uucpd uucico sockets BSD4.3 SysV.3
Message-ID: <7242@cbmvax.UUCP>
Date: 9 Jul 89 17:34:01 GMT
References: <1126@ssp15.idca.tds.philips.nl> <656@wrs.wrs.com> <1130@ssp15.idca.tds.philips.nl> <3674@ursa-major.SPDCC.COM>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 19

In article <3674@ursa-major.SPDCC.COM> cspencer@ursa-major.spdcc.COM (Cliff Spencer) writes:
> >>Porting BSD 4.3 UUCP daemon has already been done several times for different 
> >>incarnations of TCP/IP implementations for system V Unix's.  Unfortunately
> >>none of them are "free" that I know of.
> >I only need the patches, I have the BSD4.3 uucpd source...
> 
> What's the big mystery? Doesn't the daemon just spawn /usr/lib/uucp/uucico? 

Well, yes and no.  It plays with sockets doing a listen and opening a
a connection and then simulates a login and finally runs uucico passing
the open sockets as stdin/stdout.  If you have a completely functional
socket-emulation package, it shouldn't be a big deal.  Also, your uucp
is expected to know that it shouldn't try to do all those terminal
oriented ioctls on sockets...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)