From owner-freebsd-hackers  Mon Aug  2  4:34:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1A3291528A; Mon,  2 Aug 1999 04:34:10 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11BGKr-000Kl9-00; Mon, 02 Aug 1999 13:32:53 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>,
	hackers@FreeBSD.org, committers@FreeBSD.org
Subject: Re: Mentioning RFC numbers in /etc/services 
In-reply-to: Your message of "02 Aug 1999 13:27:44 +0200."
             <xzpn1wa2zin.fsf@flood.ping.uio.no> 
Date: Mon, 02 Aug 1999 13:32:53 +0200
Message-ID: <79802.933593573@axl.noc.iafrica.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On 02 Aug 1999 13:27:44 +0200, Dag-Erling Smorgrav wrote:

> 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.

My application limits the port numbers it'll play with based on what's
in /etc/services, since getservbyname() implies this limitation.

Administrators rely on the fact that only root can play with
/etc/services so that this silly application can't play with ports that
aren't in that file.

No getservbyname() doesn't work the way it used to, and the
administrator is shot in the foot, even though he didn't pull the
trigger.

Ciao,
Sheldon.


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