Xref: utzoo comp.sources.wanted:5848 comp.protocols.misc:418 comp.protocols.tcp-ip:5802 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!deimos!cseg!dws From: dws@cseg.uucp (David W. Summers) Newsgroups: comp.sources.wanted,comp.protocols.misc,comp.protocols.tcp-ip Subject: 'Talk' command and protocol Keywords: Is this a standard anywhere? Message-ID: <1468@cseg.uucp> Date: 20 Dec 88 16:46:01 GMT Organization: College of Engineering, University of Arkansas, Fayetteville Lines: 30 Hello NetLanders, We have a 'talk' command on our Harris HCX-7 computer that allows inter- computer 'talk' to take place. We are a binary site and also have a local area EtherNet network with a growing contingent of miscellaneous computers. Recently I 'FTP'ed the 'talk' command and the 'talkd' daemon source code from uunet.uu.net. Then, to my horror (1/2 :-) I found that the CTL_MSG structure defined in was different for the Berkeley version and the Harris version that I found by talking to Harris. This means that the Harris version and the Berkeley version do NOT get along at all and completely ignore each other. To make matters worse, we have a HP 835 (I believe) and I haven't finished testing it yet but it may be different from one or both of the above versions! My main question is: Is there a standard yet for this 'talk' protocol? If so, where could I find it? If not, then why not, and what would it take to produce one? What is strange is that on each of our different types of computers, there was a 'talk 517/udp' entry in the /etc/services file which led me to believe that everyone knew about it. However, I could find NOTHING that even referenced it during my search of the RFC's. My only solution at the moment seems to be to heavily hack the code to work for both Harris and Berkeley versions.....Hopefuly the HP will conform to one of those. As usual, any ideas, suggestions, pointers, or other help would be very much appreciated. Thanks in advance! - David Summers (dws@cseg.uucp)