X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 22 Apr 2010 11:41:45 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: PLEASE TEST YOUR FS (was Re: 1.7.1: cvs version built in is unstable) Message-ID: <20100422094145.GF1845@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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20100407172659.GH18530@calimero.vinschen.de> 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 7 19:27, Corinna Vinschen wrote: > On Apr 7 19:06, Corinna Vinschen wrote: > > On Apr 7 09:06, Roe, Kevin L. wrote: > > > Corinna, > > > > > > My problem system is the netapp you previously in this thread helped me with (the issue with the cp command). It is not a Samba system. > > > > Ok, back to square one. I add the problem to my TODO list. We need a > > way to allow only DOS filenames on crippled filesystems. Since I don't > > have such a filesystem myself, I'll need to come back to you for testing > > at one point. > > Btw. > > 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. > > For testing, try to create *in Cygwin* a file called "foo." and a file > " foo ". If it works, and if a following `ls' and `rm' on the file > works as well, everything's fine. If some error occurs, especially "No > such file or directory", then that filesystem probably requires special > handling just like netapp. Here's another question to those who can reproduce the problem. What I need is an strace from one netapp and and one nwfs filesystem when trying to create a file with trailing dots and spaces: for the following scenarios: $ strace -o lame_fs.trace touch 'foo.' 'foo ' This will help to create a workaround for those filesystems. I only need straces for the *not* working cases. Thanks, 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