Date: Sat, 12 Sep 1998 20:22:01 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: Robert Watson <robert+freebsd@cyrus.watson.org> Cc: Studded <Studded@dal.net>, freebsd-current@FreeBSD.ORG Subject: Re: Plans to upgrade /etc/services? Message-ID: <199809130122.UAA03396@detlev.UUCP> In-Reply-To: <Pine.BSF.3.96.980912184459.2876A-100000@fledge.watson.org> References: <Pine.BSF.3.96.980912184459.2876A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have taken the IANA port list and reformatted it a bit to use #'s for > comments and so on. There is a copy of it at > However, I wasn't sure what the formatting requirements for /etc/services > were. The IANA list has a number of entries like this: > 0/tcp #Reserved > 0/udp #Reserved > That is, with no actual service name. Will FreeBSD support libraries > care? Should I just comment them out in the style of the current services > file? (there are aroud 20 such instances in the IANA ports list) I would recommend doing so. > Also, the IANA ports list does not include the duplicate names for ports > -- for example, the current services file lists: > imap 143/tcp imap2 imap4 #Interim Mail Access Protocol v2 > IANA just has an entry in the form: > imap 143/tcp #Internet Message Access Protocol > There are a number of cases where IANA has two names for the same port, > and lists them on sequential lines instead of using the BSD extension > format with the additional names before the comment. It would appear to be fairly easy to write a Perl script to merge the two. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809130122.UAA03396>