From owner-freebsd-hackers Wed Sep 13 13:52:32 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA26120 for hackers-outgoing; Wed, 13 Sep 1995 13:52:32 -0700 Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA26112 for ; Wed, 13 Sep 1995 13:52:29 -0700 Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0ssynC-0009XmC; Wed, 13 Sep 95 13:52 PDT Date: Wed, 13 Sep 1995 13:52:26 -0700 (PDT) From: Jake Hamby To: Jeffrey Hsu cc: hackers@freebsd.org Subject: Re: 'talk' doesn't work! Did it ever? In-Reply-To: <199509132015.NAA25075@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk On Wed, 13 Sep 1995, Jeffrey Hsu wrote: > What's the byte-order of the target machine? There's a byte-order related > bug in old talk programs. Usually bites you when trying to talk to SunOS > machines. > Yeah, I was trying to talk to a SunOS box (and a Solaris box) as test cases. The problem is that there is an ntalk daemon in /etc/inetd.conf but no talkd! And it looks like both SunOS and Solaris only support the old protocol on port 517 but FreeBSD only supports the new protocol on port 518. Talking to a Linux machine worked okay. Which brings me to this question: If Linux uses the talk daemon out of BSD, and Linux can talk to Solaris/SunOS boxes (well some of the time) then what is it doing right? I think the answer lies in the fact that I normally use ytalk on Linux but hadn't gotten around to compiling it for FreeBSD, and ytalk does falls back to the old talk protocol if ntalk doesn't work. I'll compile ytalk for FreeBSD and see if that helps matters any. Oh, and sorry for posting to hackers when I should've posted to questions... But, since the FreeBSD->Sun compatibility problem hasn't been solved yet, perhaps this is a -hackers problem after all! ---Jake Hamby jehamby@lightside.com