From owner-freebsd-hackers  Mon Aug  2  4:55:58 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id F346315146; Mon,  2 Aug 1999 04:55:07 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id NAA51379;
	Mon, 2 Aug 1999 13:27:44 +0200 (CEST)
	(envelope-from des)
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
	John-Mark Gurney <gurney_j@resnet.uoregon.edu>, hackers@FreeBSD.org,
	committers@FreeBSD.org
Subject: Re: Mentioning RFC numbers in /etc/services
References: <79378.933592867@axl.noc.iafrica.com>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 02 Aug 1999 13:27:44 +0200
In-Reply-To: Sheldon Hearn's message of "Mon, 02 Aug 1999 13:21:07 +0200"
Message-ID: <xzpn1wa2zin.fsf@flood.ping.uio.no>
Lines: 15
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Sheldon Hearn <sheldonh@uunet.co.za> writes:
> If we fix this in inetd, we get what we want. If we fix this in
> getservbyport() we may get something that we don't want, namely
> applications that relay on the existing behaviour of the function stop
> working as intended.

I don't see in what way an application could break if getservbyname()
suddenly accepted numeric port specifications. It won't ``stop working
as intended'', it'll keep on working as it always used to, plus a
little more. It'll also make it a darn sight easier to parse port
specifications e.g. from the command line.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message