From owner-freebsd-hackers Sat Feb 7 05:56:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09836 for hackers-outgoing; Sat, 7 Feb 1998 05:56:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09831 for ; Sat, 7 Feb 1998 05:56:30 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.8/8.8.7) with SMTP id IAA09437; Sat, 7 Feb 1998 08:56:02 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Sat, 7 Feb 1998 08:56:02 -0500 (EST) From: "David E. Cross" To: Adrian Chadd cc: rssh@grad.kiev.ua, freebsd-hackers@FreeBSD.ORG Subject: Re: byte ordering and talk? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" On Sat, 7 Feb 1998, Adrian Chadd wrote: > On Fri, 6 Feb 1998, Ruslan Shevchenko wrote: > > > > (One little problem --- FreeBSD talk not work with machines with another > > byte-order > > in word, so if you need talk with Sun, better get ytalk from ports) > > > > Huh? > Is this a protocol-specific thing with talk protocol or just our talk > implementation? > No, the byte order is fixed in the specification (ntohs, nothl anyone). the problem that you are refferning to is either of 2 problems: 1: slightly different struct sockaddr_in structres (some have a 'lenght' field (AIX), others do not (FreeBSD) 2: ntalk/talk there are 2 differnt talk protocols, everyone uses one (can't remember), sun uses the other. (check /etc/inetd.conf and /etc/services, they bind to different ports.) -- David Cross UNIX Systems Administrator GE Corporate R&D