From owner-freebsd-hackers Mon Feb 16 16:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20489 for freebsd-hackers-outgoing; Mon, 16 Feb 1998 16:49:22 -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 QAA20423 for ; Mon, 16 Feb 1998 16:48:42 -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 TAA21103; Mon, 16 Feb 1998 19:48:08 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Mon, 16 Feb 1998 19:48:08 -0500 (EST) From: "David E. Cross" To: Dmitry Kohmanyuk cc: Mikael Karpberg , freebsd-hackers@FreeBSD.ORG Subject: Re: byte ordering and talk? In-Reply-To: <199802121643.IAA08911@dog.farm.org> 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 On Thu, 12 Feb 1998, Dmitry Kohmanyuk wrote: > In article <199802071416.PAA04586@ocean.campus.luth.se> you wrote: > [...] > > > 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.) > > > Everyone uses ntalk, except for SUN. > > So go install ntalk on the SUN machines, and you'll be fine. > > one consequence of talk brokenness in Solaris is that you cannot talk > from Solaris/sparc to Solaris/x86. (the error message is: > > [Unable to connect with initiator : Address family not supported by protocol fam > ily (124)] > > So, it is a vendor problem not worth to fix in FreeBSD IMHO.... Not exaclty (sorry I have been on vacation, not sure if this has been addressed it... but that is the exact error message that is returned by error #1. The differenec in the socvket structer between BSD and SysV is as follow: BSD: struct { word family; ... } ; SysV: struct { u_char size; u_char family } for AF_INET the size is always 0x10 (16 dec). I am not sure how/if this should be fixed in FreeBSD, but that is the cause of the error. -- David Cross UNIX Systems Administator GE Corporate R&D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message