Date: Sat, 31 Jul 1999 23:29:24 -0700 From: Doug <Doug@gorean.org> To: Jon Hamilton <hamilton@pobox.com> Cc: Sheldon Hearn <sheldonh@uunet.co.za>, Matthew Dillon <dillon@apollo.backplane.com>, hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services Message-ID: <37A3E944.7F28E91B@gorean.org> References: <19990801061937.874C5135@woodstock.monkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 rule, 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 to 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. 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. Now you'll have to excuse me while I go sharpen my lance... Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37A3E944.7F28E91B>