Xref: utzoo comp.protocols.tcp-ip:10123 comp.dcom.lans:4265 comp.protocols.tcp-ip.ibmpc:2338
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ico!dougm
From: dougm@ico.isc.com (Doug McCallum)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans,comp.protocols.tcp-ip.ibmpc
Subject: Re: tcp/ip for 386 UNIX
Keywords: UNIX 386 tcp/ip
Message-ID: <1990Feb2.154728.17877@ico.isc.com>
Date: 2 Feb 90 15:47:28 GMT
References: <5645@ncrcae.Columbia.NCR.COM> <1990Feb1.052144.27172@esegue.segue.boston.ma.us>
Reply-To: dougm@ico.ISC.COM (Doug McCallum)
Organization: Interactive Systems Corp., Boulder CO
Lines: 20

In article <1990Feb1.052144.27172@esegue.segue.boston.ma.us> johnl@esegue.segue.boston.ma.us (John R. Levine) writes:
...
>All of the usual 386 Unix vendors ship a tcp/ip package based on Lachman's
>port of BSD TCP/IP.  It works as well as any TCP does.  There is NFS on top
>of it which Interactive is shipping now and SCO will sometime in the near

Not really a true statement.  ISC's TCP/IP is not based on Lachman's in the
386/ix product.  It is based on a port ISC did long before Lachman and ISC
became the same company.

AT&T's TCP/IP is based on the Wollongong port and not the Lachman port.
A number of 386 UNIX vendors are selling this version.

A number of vendors are also using an independent port done by Spider Systems
and a few with the TCP/IP port by Streamlined.

While the Lachman based TCP/IP is probably the most widely distributed, it
isn't the only one.  A major portion of the 386 versions are one of the others.

The NFS implementations probably all come from the LAI base.