From owner-freebsd-questions Tue Oct 8 11:42:18 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14280 for questions-outgoing; Tue, 8 Oct 1996 11:42:18 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14273 for ; Tue, 8 Oct 1996 11:42:17 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id LAA02070; Tue, 8 Oct 1996 11:42:01 -0700 (PDT) Date: Tue, 8 Oct 1996 11:42:01 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Aleksei Davidenko cc: questions@FreeBSD.ORG Subject: Re: About talk In-Reply-To: <32591748.6E4B@anet.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Oct 1996, Aleksei Davidenko wrote: > I decide used "talk" in my FreeBSD, but occurs unintelligible. > "talk" does not see other party. > In inetd.conf used "ntalk" demon. > Someone uses "talk" in work ? To what kind of computer where you talking? FreeBSD boxes have trouble talking to Linux boxes due to some interaction problems between the talk daemons. Also, I've found if one side is using 'ytalk' then you'll get a line of control characters and you won't be able to talk. ytalk + talk are not compatible. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major