X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 8 Apr 2010 11:04:04 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [bulk] - PLEASE TEST YOUR FS (was Re: 1.7.1: cvs version built in is unstable) Message-ID: <20100408090404.GM18530@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4BBBDA78.10002@cwilson.fastmail.fm> <20100407083403.GD27428@calimero.vinschen.de> <20100407085343.GY18530@calimero.vinschen.de> <20100407170643.GF18530@calimero.vinschen.de> <20100407172659.GH18530@calimero.vinschen.de> <8CCC8F85C5F2784387A32FAD835FB4E602DBF13960@server03> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8CCC8F85C5F2784387A32FAD835FB4E602DBF13960@server03> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Apr 8 07:41, DEWI - N. Zacharias wrote: > > > Hi , > > > Von: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com] > > Gesendet: Mittwoch, 7. April 2010 19:27 > > An: cygwin@cygwin.com > > Betreff: [bulk] - PLEASE TEST YOUR FS (was Re: 1.7.1: cvs version built in is > > unstable) > > > [...] > > > Can anybody reproduce this problem with trailing dots and spaces in > > filenames on other filesytems than netapp? > > > > It would be quite helpful to get feedback from people using filesystems > > which are recognized by Cygwin as nwfs, unixfs, mvfs, or cifs. > > on a Novell Network drive > > $ echo bal > foo. > bash: foo.: No such file or directory > $ > $ echo bal > foo > $ > $ ls -al foo > -rw-r--r-- 1 n-zacharias Kein 5 2010-04-08 07:37 foo Thanks, so we have to add NWFS to the list as well. Oh well. These filename-crippled filesystems are really a chicken/egg problem, codewise. On one hand Cygwin can't open the files and gets an ENOENT kind of error from NT, on the other hand Cygwin needs the open file handle to get information about the underlying filesystem. I'm not sure yet how to solve this problem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple