Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!amdahl!rtech!llama!daveb
From: daveb@llama.rtech.UUCP (Crack?  No thanks, I've got a new CD player)
Newsgroups: comp.sys.att
Subject: Re: SYS V.3 for 3B15s, rfs, tcp/ip
Message-ID: <1961@rtech.UUCP>
Date: 14 Apr 88 22:06:28 GMT
References: <5563@spool.cs.wisc.edu> <10227@ulysses.homer.nj.att.com>
Sender: news@rtech.UUCP
Reply-To: daveb@rtech.UUCP (Crack?  No thanks, I've got a new CD player)
Distribution: na
Organization: Relational Technology, Inc. Alameda, CA
Lines: 23
Keywords: SYSV.3 3B15 whereisit?

In article <10227@ulysses.homer.nj.att.com> ekrell@hector (Eduardo Krell) sez:
>In article <5563@spool.cs.wisc.edu> sadler@rocky.WISC.EDU (Jonathan Sadler) writes:
>>     When can I expect to be able to get System V Release 3 for the
>>     3B15?  I understand that this is necessary to get Version 2.1
>>     of Wollingong's TCP/IP up and running.  Seeing that we have a
>>     high interest in gettng RFS up, we need this code.
>
>I don't know about SVR3 for the 3B15, but I want to clarify a point:
>You don't need Wollongong's TCP/IP 2.1 in order to run RFS. RFS will
>run on transport providers other than TCP/IP. You need a TCP/IP
>provider ONLY IF you want to talk RFS with other (non AT&T) SVR3 boxes.
>
>    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

You really think someone outside of AT&T would want Starlan or Datakit
instead of tcp/ip?

-dB

almost forgot:

:-)
"Remember, there's a seeker born every minute."  -- Happy Harry Cox.
{amdahl, cpsc6a, mtxinu, ptsfa, sun, hoptoad}!rtech!daveb daveb@rtech.uucp