Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!basser.cs.su.oz.au!news.cs.su.oz.au!metro!dmssyd.syd.dms.CSIRO.AU!dmsperth.per.dms.CSIRO.AU!uniwa!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!spool.mu.edu!sgiblab!brunix!cs.brown.edu!Mark_Weaver From: Mark_Weaver@brown.edu Subject: Re: Talk on NetBSD 0.9 In-Reply-To: bhiksha@tifrvax.tifr.res.in's message of Fri, 4 Feb 1994 18:25:59 GMT Message-ID: <MARK_WEAVER.94Feb9190158@localhost.cs.brown.edu> Sender: news@cs.brown.edu Reply-To: Mark_Weaver@brown.edu Organization: Brown University Department of Computer Science References: <4FEB94.18255960@tifrvax.tifr.res.in> Date: Thu, 10 Feb 1994 00:01:58 GMT Lines: 29 In article <4FEB94.18255960@tifrvax.tifr.res.in> bhiksha@tifrvax.tifr.res.in writes: > Doesnt work. > I do a talk to a local user (say, myself) and i get: > [Target machine does not recognize us] > and it comes out. > I do a talk to a remote machine and i get > [Checking of invitation on Caller's machine] > and it stays there till i interrupt it. > > So i use ytalk (perhaps the problem is with talk itself, this happend > on my sunos 4.1.1) and i get: > No talk daemon on 158.144.9.31 (my machine) > The talk daemon is definitely running as a ps shows. > > strange behavior or setup problem? You have to run ytalk on the Sun side also (at least if the Sun side is initiating the chat). The problem is that Sun uses the old talk protocol. It seems to be one of the few vendors that hasn't switched. Even Solaris doesn't use the new talk protocol. The nice thing about ytalk is that it works with both old and new. Mark -------------------------------------------------------------------- Email: Mark_Weaver@brown.edu | Brown University PGP Key: finger mhw@cs.brown.edu | Dept of Computer Science