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 Date: Wed, 8 May 2002 13:29:05 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ftp / inetd problem Message-ID: <20020508172905.GA6152@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <229D7C0FE0BED311A0E800805F0DD471010D2DF9 AT wn01ex DOT wn DOT gb DOT solvay DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020508094140 DOT 027969a8 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20020508094140.027969a8@pop3.cris.com> User-Agent: Mutt/1.3.23.1i On Wed, May 08, 2002 at 09:59:14AM -0700, Randall R Schulz wrote: >>Recent cygwin snapshots should fix this problem. > >But I now that I read Chris's brief reply, I'm uncertain whether the patch >he mentions is to tar or to Cygwin1.dll, but my guess is that it's the >latter. "Recent cygwin snapshots should fix this problem" would sort of preclude the need for guessing that it would be a tar patch. That + Corinna's response: http://cygwin.com/ml/cygwin/2002-04/msg00481.html really should be pretty clear. I don't know if this solves the problem mentioned in this email or not. There is an obvious way to find out if it does. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/