Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!nbires!hao!boulder!forys
From: forys@boulder.UUCP (Jeff Forys)
Newsgroups: comp.dcom.lans
Subject: Re: talk problems between SUN and uVAX - (nf)
Message-ID: <315@boulder.UUCP>
Date: Sat, 17-Jan-87 15:22:11 EST
Article-I.D.: boulder.315
Posted: Sat Jan 17 15:22:11 1987
Date-Received: Sun, 18-Jan-87 07:45:11 EST
References: <6300001@iaoobelix.UUCP> <300@boulder.UUCP> <576@brl-sem.ARPA>
Reply-To: forys@boulder.UUCP (Jeff Forys)
Organization: University of Colorado, Boulder
Lines: 18
Summary: "first of it's kind" meant...

In article <576@brl-sem.ARPA> ron@brl-sem.ARPA (Ron Natalie <ron>) writes:
>In article <300@boulder.UUCP>, forys@boulder.UUCP (Jeff Forys) writes:
>> I dont know, certainly by todays standards it's poorly written, but
>> it was probably the first of its kind and it did work pretty well in
>> an all-vax environment...
>
>I'm going to forstall a bunch of discussion on this as the statement
>about TALK being the first of it's kind as being outright wrong.

Yikes!  I never meant to imply that `talk' was the first "communication
program ever written" -- I am not *that* naive!  Hindsight informs me
that I should have wrote "`talk' was probably the first network
communications program written under 4BSD".  Since the origional poster
spoke of byte swap problems between BSD & SUN machines, I didnt think
my statement would cause readers to traverse back to the epoch!
---
Jeff Forys @ UC/Boulder Engineering Research Comp Cntr (303-492-6096)
Forys@Boulder.Colorado.Edu  -or-  ..!{hao|nbires}!boulder!forys