From owner-freebsd-hackers Sat Jul 31 23:44:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id 00D9A14CFB for ; Sat, 31 Jul 1999 23:44:11 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (kronos-1-145.mdm.mkt.execpc.com [169.207.86.19]) by mailgw01.execpc.com (8.9.1) id BAA15461; Sun, 1 Aug 1999 01:43:58 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 12D5C155; Sun, 1 Aug 1999 01:44:26 -0500 (CDT) To: Doug Cc: Sheldon Hearn , Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services In-reply-to: Your message of "Sat, 31 Jul 1999 23:29:24 PDT." <37A3E944.7F28E91B@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 01:44:26 -0500 From: Jon Hamilton Message-Id: <19990801064426.12D5C155@woodstock.monkey.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37A3E944.7F28E91B@gorean.org>, Doug wrote: } Jon Hamilton wrote: } } > No. ipfw deals with /etc/services only at startup time (any other behavior } on } > its part would be ridiculous). } } That's not entirely true, there are other situations (like adding a rul } e, } etc.) but your point is well taken. And no, I can't provide specific } examples, my point is really much simpler than that. } } > I think you're overestimating the cost by a considerable amount. I'm } > not saying that the cost is zero, but I am saying that it's close enough } > that the value of having the information *right there* outweighs the cost. } } Anyone interested in the information will stay interested long enough t } o } look it up in a man page. Even if the cost to the system is very very } small, I think that adding it to the file is silly when it could just as } easily be added to a man page. It's not "just as easy" for the person looking for the information; it doesn't *get* any easier than having it right there alongside the place you're going to use it. Just because in principle someone can go look up the information somewhere else, doesn't mean that it's not easier and more friendly to [also?] have the information right there in the file. } Of course, there are other benefits to having it in a man page too. The } primary one being that changes/updates to the comments don't require a } change to the file, and would be picked up automatically during a make } world. That is true, but then again this data doesn't change that often. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message