Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site bbncc5.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bbnccv!bbncc5!sdyer
From: sdyer@bbncc5.UUCP (Steve Dyer)
Newsgroups: net.unix-wizards
Subject: Re: ULTRIX 1.1 TCP/IP
Message-ID: <570@bbncc5.UUCP>
Date: Sun, 6-Oct-85 13:21:06 EDT
Article-I.D.: bbncc5.570
Posted: Sun Oct  6 13:21:06 1985
Date-Received: Tue, 8-Oct-85 03:44:09 EDT
References: <994@sdcsla.UUCP>
Distribution: net
Organization: Bolt Beranek and Newman, Cambridge, MA
Lines: 24

> There have been these rumors that TCP/IP is "broken"
> under ULTRIX 1.1.  We are about to bring up a 785
> possibly running ULTRIX and would like to understand
> just what this means.  I.e., is it fixed/fixable (we'll
> have source)?

Yes, it was "broken" in the process of installing DECnet under Ultrix 1.1.
Only DEC's DEUNA board continued to work.  The ACC LH/DH-11 driver (and
presumably other network drivers like the Interlan driver) no longer could
communicate with the net (although the boot-time probe continued to find
the device.)  If you simply use DEC's DEUNA, then 1.1 should work just fine.
Hosts needing other devices, such as those directly connected to the
ARPAnet via an LH/DH-11, should hold off.

We fixed this and returned the sources to DEC Ultrix development in
Merrimack.  Frankly, I don't know what DEC's plans are regarding this
problem: their means of fixing bugs seems to be the software release, a
process which is inherently slow to address critical problems.  I will
check with them and see whether it is kosher to post a set of diffs to the
net.
-- 
/Steve Dyer
{harvard,seismo}!bbnccv!bbncc5!sdyer
sdyer@bbncc5.ARPA