From: "Stephen Anderson" <stephen.rhoderson@gmail.com>
To: <cygwin@cygwin.com>
Subject: Re: unzip, find broken by auto handling of .exe file extension
Date: Mon, 12 Sep 2016 20:37:00 -0000 [thread overview]
Message-ID: <493DBECE9DB54588A55BDB6921F73079@skywavemobile.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A704BB9586B@USA7109MB022.na.xerox.net>
Thanks Ken, good observation.
-----Original Message-----
> From: Nellis, Kenneth
> From: Stephen Anderson >
> > See also:
> >
> > http://stackoverflow.com/questions/32467871/unzip-gives-checkdir-error-
> > directory-exists-but-is-not-a-directory#32468314
> >
> > The fact that 7z handles this and unzip does not indicates that the
> > problem is fixable..
> FWIW, it seems that the same issue is present with tar:
> <Ken demonstrates broken tar handling>
This means that you can't reliably extract from a tar or zip archive in
cygwin.
The windoze equivalents do not have this problem.
It looks to me like the approach of equating filenames 'foo' and 'foo.exe'
is dangerous at the stat(2) level - apparently windoze accomplishes the same
trick in a much less destructive way.
sja
--
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
next prev parent reply other threads:[~2016-09-12 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 16:00 Stephen Anderson
2016-09-02 18:40 ` cyg Simple
2016-09-02 20:20 ` Stephen Anderson
2016-09-09 13:18 ` Stephen Anderson
2016-09-09 13:59 ` Nellis, Kenneth
2016-09-12 20:37 ` Stephen Anderson [this message]
2016-09-12 23:30 ` Marco Atzeri
2016-09-12 23:41 ` Stephen Anderson
2016-09-13 1:35 ` Andy Hall
2016-09-13 8:00 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493DBECE9DB54588A55BDB6921F73079@skywavemobile.com \
--to=stephen.rhoderson@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).