Path: utzoo!attcan!uunet!wuarchive!texbell!root
From: root@texbell.sbc.com (Greg Hackney)
Newsgroups: comp.sys.ncr
Subject: Re: Tower Sys V.3 upgrade
Message-ID: <4780@texbell.sbc.com>
Date: 29 Jul 90 00:43:24 GMT
Lines: 35
Resender: towers@texbell.sbc.com (NCR Tower Mailing List)


>>  WIN provided networked only uucp via TLI/NLS, however. Too bad
>>  they didn't throw in uucpd, as it's easy enough to compile. Sun
>>  provides both UUCPD and TLI/NLS.

> No, they don't.  UUCP in SunOS 4.1 runs only using UUCPD; there's no TLI
> support in 4.1's UUCP (I sure didn't put it in, and the other person
> involved with UUCP there says it wasn't put in).

Sun OS4.1 comes with RFS, including the network listener server programs
(nlsadmin) used by Towers with WIN TCP/IP. The new Sun uucico program also
has the same protocol ('e') used by WIN (in addition to 't'). But, you're
right, TLI support was not added under the -i option of uucico.

It's possible to get the Tower's WIN uucico to talk with the Sun's, with
something like:

  --Systems.tcp--  Use address for port 540
sunsite Any TCP1 - \x0002021c84c82a13

  --Devices.tcp--
TCP1,e tcp - - TLI \D tcp1

  --Dialers.tcp--
tcp1 "" "" nuucp word: sunspassword

And it's possible to get Pyramid's (att) uucico, and AT&T's uucico to talk
with the Tower's WIN uucico with this:

  --Systems--
winsite Any TCP,e 1025 winsite "" NLPS:000:001:101\N\c

However, I can't seem to get the above to work with Sun's 4.1 uucico.
--
Greg