Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!vrdxhq!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: tmscp.o =? tk50 / tu81 in ultrix 1.1
Message-ID: <258@hadron.UUCP>
Date: Mon, 10-Feb-86 23:56:25 EST
Article-I.D.: hadron.258
Posted: Mon Feb 10 23:56:25 1986
Date-Received: Thu, 13-Feb-86 17:41:28 EST
References: <2128@brl-tgr.ARPA> <27@mit-eddie.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 11

In article <27@mit-eddie.UUCP> jg@mit-eddie.UUCP (Jim Gettys) writes:
>In article <2128@brl-tgr.ARPA> MRC%PANDA@sumex-aim.arpa (Mark Crispin) writes:
>>     You can't really blame DEC for the lack of TU81 support in
>>System V and 4.2/3BSD.  You do, however, have a point about
>>Ultrix.  DEC has done this [delaying the introduction of products
>>for systems they are trying to kill off] many many times before.

Isn't the tmscp.o driver in Ultrix 1.1 the TU81 and TK50 driver?
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}