From owner-freebsd-hackers Fri Dec 13 09:54:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA02820 for hackers-outgoing; Fri, 13 Dec 1996 09:54:57 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA02808 for ; Fri, 13 Dec 1996 09:54:51 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vYbjj-0007k5-00; Fri, 13 Dec 1996 10:49:27 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: talk and talkd Cc: freebsd-hackers@freebsd.org (FreeBSD hackers), mgessner@aristar.com In-reply-to: Your message of "Fri, 13 Dec 1996 10:15:42 +0100." <199612130915.KAA17346@uriah.heep.sax.de> References: <199612130915.KAA17346@uriah.heep.sax.de> Date: Fri, 13 Dec 1996 10:49:27 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199612130915.KAA17346@uriah.heep.sax.de> J Wunsch writes: : ytalk is supposed to speak the Sun protocol as well (including the : required byte order changes Sun was so proud to forget). True enough, but that's not FreeBSD's talk :-). All this started back in BSD 4.2 on the vax when they designed a protocol that worked great if you were talking to other vaxen. Then Sun ported talk to their machine, and the size of the message changed, but it was still in host byte order. There are hacks in Sun's talkd to swap bytes when talking to a VAX, but I don't think that they really work (could be wrong). Then in BSD 4.3 they came up with an architecture neutral protocol that was always in network byte order, had good, compiler friendly byte alignment in its structures. Sun never picked up these changes :-(. Warner