From owner-freebsd-current  Fri Dec  5 18:46:56 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA08216
          for current-outgoing; Fri, 5 Dec 1997 18:46:56 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from word.smith.net.au (ppp8.portal.net.au [202.12.71.108])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA08207
          for <current@FreeBSD.ORG>; Fri, 5 Dec 1997 18:46:48 -0800 (PST)
          (envelope-from mike@word.smith.net.au)
Received: from word (localhost [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA01232;
	Sat, 6 Dec 1997 13:09:52 +1030 (CST)
Message-Id: <199712060239.NAA01232@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Eivind Eklund <perhaps@yes.no>
cc: Ari Suutari <ari@suutari.iki.fi>, John Kelly <jak@cetlink.net>,
        current@FreeBSD.ORG
Subject: Re: 3.0 -release ? 
In-reply-to: Your message of "05 Dec 1997 02:20:24 BST."
             <86k9dkegbr.fsf@bitbox.follo.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 06 Dec 1997 13:09:51 +1030
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Using htonl() on a port number at least seems to be wrong - port
> numbers are 16 bits.  Signed/unsigned trouble too, perhaps?

Heh.  Port numbers are 16 bits, but they are passed around in ints.  If 
you follow the code through the kernel, you will see htonl() being used 
on a regular basis.

There was a thread "Memory leak in getservbyXXX" on -hackers a while 
back in which this was discussed.  I still haven't attacked the 
manpages to deal with the outcome of this discussion, as the magnitude 
of the obvious task was daunting in the extreme.

mike