X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.9 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Date: Fri, 13 Jul 2012 04:55:28 +0400
From: Andrey Repin <anrdaemon AT freemail DOT ru>
Reply-To: Andrey Repin <cygwin AT cygwin DOT com>
Message-ID: <903788857.20120713045528@mtu-net.ru>
To: "Andy Hall" <fixpertise-consulting AT comcast DOT net>, cygwin AT cygwin DOT com
Subject: Re: tar won't extract all files when a file with exe extension precedes the same without extension inside the archive
In-Reply-To: <EEF3431C30314B69B826B954F2D49B64@ahallpc>
References: <BLU152-W148807FCA9B75410CB8F1FCED10 AT phx DOT gbl> <92B65842B4224F3FA65CE40F3608F7DF AT multiplay DOT co DOT uk> <20120712010353 DOT GB14112 AT ednor DOT casa DOT cgf DOT cx> <447894CEE2E7427F8E0AFC5A206BAD92 AT multiplay DOT co DOT uk> <981681190 DOT 20120712160313 AT mtu-net DOT ru> <4FFED62A DOT 7060106 AT cygwin DOT com> <EEF3431C30314B69B826B954F2D49B64 AT ahallpc>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Greetings, Andy Hall!

> At the risk of adding more fuel to the fire, let me add my 2 cents worth to
> this.

> 1.  As a long time and frequent user of tar and rsync to transfer files and
> directories between Windows and various UNIX flavors, I have been astonished
> (and severely burned) by the fact that transferring  files back and forth
> between Windows and other UNIX machines via tar, rsync, cp -r or other
> similar mechanisms are not idempotent operations, at least with respect to
> file names and contents.  This violates the "principle of least
> astonishment" not to mention that it breaks things in not so obvious and
> surprising ways when it happens.  

This is to be expected. The ways *NIX and Windows store file metadata are
different. Very different. Starting from differences in sets of allowed
character for file names, and to the subtle difference in ACL handling.
With all that lie in between.

> 2.  Since this is a "Windows thing", is there some reason why the execution
> of "file" or "file.exe" isn't handled as a special case in the exec call
> (and all its flavors) and no place else?

It actually have VERY simple answer.

test -x file && command

> For example, it would seem that if exec is asked to run "file" with no .exe
> extension and that file does not exist or is not executable, then it could
> try "file.exe" if that exists and is executable.


--
WBR,
Andrey Repin (anrdaemon AT freemail DOT ru) 13.07.2012, <04:51>

Sorry for my terrible english...


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