Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!husc6!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.unix.xenix
Subject: Re: TCP/IP on Xenix - summary
Keywords: TCP,IP,Xenix,Ethernet,Excelan
Message-ID: <875@ursa-major.SPDCC.COM>
Date: 14 Dec 89 23:06:44 GMT
References: <157@csinc.UUCP>
Reply-To: dyer@ursa-major.spdcc.COM (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 27

The article quotes someone (Rosenthal?) who is misinformed about SCO's
TCP/IP for XENIX and UNIX.  It certainly DOES run under XENIX 386 as
well as UNIX V/386.  XENIX 386 can optionally run STREAMS, and the
TCP/IP runs as a set of STREAMS modules above this.  Most of the
typical Berkeley applications run on top of a socket emulation
library.

I can say that it appeared to work OK, although I never bothered
wrestling with their sendmail; I was sending and receiving mail on
another of my systems.

Apparently, however, the Lachman TCP/IP which SCO sells contains
a "copy-protection" feature which broadcasts the product's serial
number to a particular UDP port on some regular basis.  If two
different systems have the same serial no., something bad happens.
(Presumably one or both go off-line; I've never tested.)

Needless to say, this is unacceptable in any system which pretends to
be a production system.  The marketeers were unrepentant as of last
August at the SCO Forum.  I don't know whether things have changed
since then.


-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu