Message-ID: <467FB19F.1030608@byu.net>
Date: Mon, 25 Jun 2007 06:14:23 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.12) Gecko/20070509 Thunderbird/1.5.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Francky Leyn <Francky AT Leyn DOT eu>
CC: cygwin AT cygwin DOT com
Subject: Re: aux as filename
References: <467F88EF DOT 50909 AT Leyn DOT eu>
In-Reply-To: <467F88EF.50909@Leyn.eu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Francky Leyn on 6/25/2007 3:20 AM:
> 
> 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.

You're not the first to discover this.

> 
> 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.

By default, unless you use a managed mount, cygwin defers to Windows
filename parsing.  If windows hangs on a special name (which it does on
aux), then so does cygwin, because deep down, cygwin is just a Windows
application.  The aux filename is special to Windows no matter where it is
encountered.

>> 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?

man mount

In short, if you want to expand a tarball that contains a file such as
aux.c, or that has both foo and FOO, or any other problematic combination,
the easiest solution is to:

mkdir managed
mount -o managed "`cygpath -am managed" managed
cd managed
tar xvf problematic.tar

> 
> 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.

Or better yet, don't create such problematic names in the first place when
creating your DVD.  And why aren't managed mounts the default?  Because
they slow down processing (which is already slow, since cygwin is an
emulation layer), and they reduce the already short maximum file name
limitations imposed by Windows.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGf7Gf84KuGfSFAYARAgFBAJ4wm1lXDoliC/udUO83LvxCUECtRwCfZ2Wc
NZS8k+K1BAh75zHZ3P/ybLw=
=gCq2
-----END PGP SIGNATURE-----

--
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/