X-Spam-Check-By: sourceware.org Message-ID: <467F88EF.50909@Leyn.eu> Date: Mon, 25 Jun 2007 11:20:47 +0200 From: Francky Leyn User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: cygwin@cygwin.com, Eric Blake , James Youngman Cc: Francky Leyn Subject: aux as filename Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Dear, I have to restore a DVD with a copy of a UNIX filesystem on, on a Windows NTFS system. I use for that a cygwin cp. One of the problems is that there are files on that filesystem with names like aux.c, aux.h, and aux.gp. This is a problem because aux is a name reserved by Windows, and because Windows makes no difference between *aux* and aux. Whatever cygwin command I issue on those aux.* files, it hangs. cp, find, mv, ls, and so on, they all "hang" whenever they encounter the first aux.* file. Perhaps this is because they use stat, and this underlying stat aux.* hangs. Why is this? Could cygwin stat not handle this exception, so that all these commands no longer hang? Why does it hang? After all, the aux.* file is on an ISO 9660? file system, not on a NTFS file system. Eric Blake wrote: > This is done in cygwin, using the notion of 'managed mounts'. Can someone explain me or give me a pointer to documentation how I can use this in my case? How do we solve this? Due to this exception, I must copy everything manually for the moment. Time consuming, error prone, prehistorically, and not the UNIX blast I'm used to. Best regards, Francky Leyn -- 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/