Date: Sat, 7 Feb 1998 15:16:22 +0100 (CET) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: dec@phoenix.its.rpi.edu (David E. Cross) Cc: adrian@obiwan.creative.net.au, rssh@grad.kiev.ua, freebsd-hackers@FreeBSD.ORG Subject: Re: byte ordering and talk? Message-ID: <199802071416.PAA04586@ocean.campus.luth.se> In-Reply-To: <Pine.BSF.3.96.980207085318.7683A-100000@phoenix.its.rpi.edu> from "David E. Cross" at "Feb 7, 98 08:56:02 am"
next in thread | previous in thread | raw e-mail | index | archive | help
According to David E. Cross: > 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? It's just SUN's 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.) Everyone uses ntalk, except for SUN. So go install ntalk on the SUN machines, and you'll be fine. /Mikael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802071416.PAA04586>