Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <416E2B98.34CE5F1@dessent.net> Date: Thu, 14 Oct 2004 00:32:40 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [SOLVED] Re: other services ok, ftp not (was 1.5.11 - tcp problems) References: <4745850620 DOT 20040921112624 AT scenta DOT co DOT uk> <416B3A95 DOT 4010506 AT hq DOT astra DOT ph> <416C92BD DOT 90100 AT hq DOT astra DOT ph> <416CC006 DOT 3D4ECDEF AT dessent DOT net> <416CC105 DOT B1C945CA AT dessent DOT net> <416CF9FA DOT 6010209 AT hq DOT astra DOT ph> <416D0506 DOT D77FEF77 AT dessent DOT net> <416E1B23 DOT 60708 AT hq DOT astra DOT ph> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Carlo Florendo wrote: > On a curious note, why do the inetutils apps like ftp, telnet, etc. > still use getservbyname() and the other getserv functions when, as you > said, > these apps could just have the port and protocol hardcoded or specified > in a config file? As far as I know that traces back to the original TCP/IP networking code in unix, 4.2BSD circa 1983 from what a quick google shows. Back then things were a lot simpler and I suppose it was more straightforward to have one config file that defined all the services the box was running and what ports they were to listen on, and to have each daemon query that file through getservbyname(). As far as I know the tools in inetutils are the direct descendents of the original BSD commands from way back, so the code still uses those methods. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/