Date: Mon, 14 Sep 1998 18:57:43 -0700 From: Studded <Studded@dal.net> To: Robert Watson <robert+freebsd@cyrus.watson.org> Cc: freebsd-current@FreeBSD.ORG, obrien@NUXI.com Subject: Re: Plans to upgrade /etc/services? Message-ID: <35FDC997.36B76432@dal.net> References: <Pine.BSF.3.96.980912184459.2876A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > > On Sat, 12 Sep 1998, Studded wrote: > > > Robert Watson wrote: > > > > > > Are there plans to integrate recent additions to the IANA port assignments > > > into /etc/services? > > > > I've had a PR open on this forever. Now that I'm finally done with a > > major FreeBSD project maybe I'll look at this. I doubt it will happen in > > time for the 3.0 release in any case. > > > > > Coda recently acquired IANA port numbers, and we'd > > > love it if the FreeBSD services file included them by default. :) Also, > > > if anyone else's services files included them by default, of course. > > > > > > Would it be best if I just submitted patches? > > > > My take on the situation is that patches for a specific set of things > > submitted in a PR would likely be committed, so I would highly recommend > > that course of action. > > 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 > > http://www.watson.org/~robert/services > > However, I wasn't sure what the formatting requirements for /etc/services > were. They're available in services(5). It is VERY VERY important to stick with the appropriate file format, or else the getservent(3) library will cause all manner of havoc (I found this out the hard way :). The things that are committed so far all look good. > 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. According to the man page, multiple aliases are fine, and there are several examples of this in the current file. Having more than one entry for the same port will cause grief however. > If someone gives me some pointers, I'll patch up those few remaining > issues, and it should be a fairly useful services file (it is up-to-date > as of this afternoon). One other minor problem is apparent -- when I do a > netstat, the service names in general appear fine. Except for ssh in my > version of /etc/services: Hrrmm... I'm not having this problem here, but I'm using the stock services file. David O'Brien, if you want to contact me privately and let me know exactly what you need help with, I'll be glad to do what I can. I have some time this week and I'd love to see this PR closed. Doug -- *** Chief Operations Officer, DALnet IRC network *** "Yes, the president should resign. He has lied to the American people, time and time again, and betrayed their trust. He is no longer an effective leader. Since he has admitted guilt, there is no reason to put the American people through an impeachment. He will serve absolutely no purpose in finishing out his term; the only possible solution is for the president to save some dignity and resign." - William Jefferson Clinton, 1974 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?35FDC997.36B76432>