X-Spam-Check-By: sourceware.org From: Jonathan Lennox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17882.22803.479825.172122@metro-north.cs.columbia.edu> Date: Mon, 19 Feb 2007 21:12:35 -0500 To: ericblake AT comcast DOT net (Eric Blake) Cc: cygwin AT cygwin DOT com Subject: Re: Surprising results (ls: no such file or directory) with managed mounts In-Reply-To: <022020070054.14241.45DA46CD0000EA95000037A122007503300A050E040D0C079D0A@comcast.net> References: <022020070054 DOT 14241 DOT 45DA46CD0000EA95000037A122007503300A050E040D0C079D0A AT comcast DOT net> X-Mailer: VM 7.19 under Emacs 20.7.1 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tuesday, February 20 2007, "Eric Blake" wrote to "Jonathan Lennox, cygwin AT cygwin DOT com" saying: > > Cygwin managed mounts give surprising (to me) results if a filename that's > > not in its canonical form manages to get below the managed mountpoint: > > The real fix, which I've mentioned before, would be > altering rename() to fail with EXDEV when renaming > files across managed mount points. But as I don't > have copyright assignment in place for cygwin1.dll, > I'm relying on someone else to write such a patch. > In the meantime, just don't do that. True, but these non-canonical filenames can also arise if you do "mount -f -o managed EXISTING-WIN-DIR". The "just don't do that" argument also applies there, of course, but that's an idiom used by many pre-cygport package build scripts. (Cygport leaves off the -f, avoiding the problem.) And, of course, any non-Cygwin program writing to the managed directory can create file names not in the canonical form. -- Jonathan Lennox lennox at cs dot columbia dot edu -- 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/