From owner-freebsd-hackers Wed Jul 28 18: 8:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B34641551E for ; Wed, 28 Jul 1999 18:08:40 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA65216; Wed, 28 Jul 1999 18:07:45 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 18:07:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199907290107.SAA65216@apollo.backplane.com> To: Doug Cc: Dag-Erling Smorgrav , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Sheldon Hearn writes: :> > I plan to mention in the comments for each service in /etc/services, the :> > latest RFC describing the service. :> :> Good idea. : : Hmmmm... I'm not sure what this gets us. Wouldn't it be better to :place this kind of information in the man page that you suggest below? As :often as /etc/services gets read, do we really want to bloat it with :non-functional information? :... :Doug I kinda like the idea of putting the RFC numbers in comments in /etc/services. It makes the comments more meaningful. : If you really want to improve /etc/services, the first commit :should be to delete all the extraneous whitespace at the end of the lines. : :23$ grep -c ' $' /etc/services :173 : :25$ grep -c '^I$' /etc/services :97 :... It would be nice if we DBM'd /etc/services. /etc/services is 61KB+ now, I think DBMing it in a manner similar to how some of the other system files which are DBM'd would be worthwhile. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message