Xref: utzoo comp.protocols.tcp-ip:12015 comp.unix.questions:23478 Path: utzoo!attcan!uunet!aplcen!samsung!interlan.InterLan.COM!interlan.interlan.com!towfiq From: towfiq@interlan.Interlan.COM (Mark Towfigh) Newsgroups: comp.protocols.tcp-ip,comp.unix.questions Subject: Multiple versions of TALK? (was: Major bug in TALK on WIN/TCP for VMS) Message-ID: Date: 3 Jul 90 13:56:02 GMT References: <28296.2689c707@vaxb.acs.unt.edu> <4875@sunquest.UUCP> <1990Jul3.040115.12000@hayes.fai.alaska.edu> Followup-To: comp.protocols.tcp-ip Organization: Racal Interlan Inc., Boxborough, MA Lines: 28 In-reply-to: wisner@hayes.fai.alaska.edu's message of 3 Jul 90 04:01:15 GMT Note the followup group is comp.protocols.tcp-ip, as I don't read comp.unix.questions. In article <1990Jul3.040115.12000@hayes.fai.alaska.edu> wisner@hayes.fai.alaska.edu (Bill Wisner) writes: There is no RFC for talk. I know this is true -- it's a problem because there are incompatible versions of TALK out there. Specifically, it seems there was a change between the 4.2BSD talk/talkd and the one in 4.3BSD. I have a few questions: does the current TALK daemon support both the old and new versions? And what about the client? As far as I can make out, the new talkd can tell the difference between the two protocols, and when a remote user requests a connection, the local TALK daemon figures out whether they are TALKing 4.2-style or 4.3-style, and then tells the local user to run one of two programs, either /usr/ucb/talk or /usr/old/talk. All this aside, I have never seen this work with the 4.2 TALK, only the 4.3 flavor. Is there anyone out there running a system which can talk in both styles, and deal with incoming and outgoing TALK requests? -- Mark Towfigh, Racal InterLan, Inc. towfiq@interlan.Interlan.COM W: (508) 263-9929 H: (617) 488-2818 uunet!interlan!towfiq "The Earth is but One Country, and Mankind its Citizens" -- Baha'u'llah