Date: Sat, 31 Jul 1999 23:14:15 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: Doug <Doug@gorean.org> Cc: Matthew Dillon <dillon@apollo.backplane.com>, hackers@FreeBSD.ORG Subject: Re: Mentioning RFC numbers in /etc/services Message-ID: <69175.933455655@axl.noc.iafrica.com> In-Reply-To: Your message of "Fri, 30 Jul 1999 15:05:14 MST." <Pine.BSF.4.05.9907301459090.7396-100000@dt011n65.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 Jul 1999 15:05:14 MST, Doug wrote: > I still haven't heard anyone answer the two key (IMO) questions. Your questions are easier answered in reverse order: > and how do you justify the additional cost to parse the file for every > single system call that uses it? The information is part of the comments within the file. The cost is in disk space, and it's cheaper than fleabites. > Why is it better to have this in the file than in a man page, Since it costs nothing to have it in /etc/services, why not leave it there along with the information with which it's associated? The alternative is to have a manpage that contains most of the information in /etc/services! > My only concern is that putting it IN the file has more costs than > benefits. What am I missing here, that I don't see a cost? What software scans the lines in /etc/services beyond the comment delimiter, other than null terminator searches? So far, I've had some great advice on this issue (although I think it's time the thread took a long walk off a short pier), so I definitely have my ears open. I'm just having trouble either understanding or believing what I'm hearing. :-) Ciao, Sheldon. 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?69175.933455655>