Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!csc.ti.com!ti-csl!tilde.csc.ti.com!pearl!pearl!mikep
From: mikep@dirty.csc.ti.com (Michael A. Petonic)
Newsgroups: comp.unix.programmer
Subject: Re: TALK Daemon questions
Message-ID: <MIKEP.90Sep20191929@dirty.csc.ti.com>
Date: 20 Sep 90 13:19:29 GMT
References: <12052@chaph.usc.edu> <EMV.90Sep19221142@picasso.math.lsa.umich.edu>
Sender: news@pearl.dsg.ti.com (System News Administration)
Organization: Texas Instruments, Speech Mushrooms.
Lines: 12
In-Reply-To: emv@math.lsa.umich.edu's message of 20 Sep 90 03:11:42 GMT

In article <EMV.90Sep19221142@picasso.math.lsa.umich.edu> emv@math.lsa.umich.edu (Edward Vielmetti) writes:
> [ On why 4.2 BSD talk(1) is broken between machines. ]
>   My questions are:
>   why do these kinds of things happen?
>
>Byte ordering problems are the culprit here.  The protocol for in.talkd
>on 4.2-based systems is architecture dependent and cannot be relied to
>work between machines of different vendors.

See.  You wouldn't have those problems with OSI....   :-)

-MikeP