From: Andrey Repin <anrdaemon@yandex.ru>
To: Zube <Zube@stat.colostate.edu>, cygwin@cygwin.com
Subject: Re: wget 1.17.x creates odd permissions on downloaded files
Date: Thu, 23 Jun 2016 13:05:00 -0000 [thread overview]
Message-ID: <152111082.20160623152647@yandex.ru> (raw)
In-Reply-To: <20160623114806.GA138493@quantum.stat.colostate.edu>
Greetings, Zube!
>> This is how Cygwin works around certain incompatibilities between
>> Windows and POSIX permission models. Do NOT fall into a trap
>> and believe that Explorer trying to drag you to. The permissions
>> are correct, it's just that Explorer is unable to deal with them,
>> because all it knows is so-called "canonical" order.
> OK.
>> If you want Windows behavior, use noacl flag on non-Cygwin mounts.
> Thank you. As you might have seen in my follow-up, it was simply
> a change in behavior that I wasn't expecting. Now that I expect
> it, I can certainly set the execute bit on whatever executables
> I download.
Yeah, that caught me not once, too, on new installations. But I was expecting
something like that, knowing how Cygwin handles file permissions in general.
(Read: same as Linux.)
The actual fix in each case depends on the typical usage of a given Cygwin
install. There's no silver bullet.
--
With best regards,
Andrey Repin
Thursday, June 23, 2016 15:23:31
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
prev parent reply other threads:[~2016-06-23 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 19:05 Zube
2016-06-22 19:36 ` Larry Hall (Cygwin)
2016-06-22 20:39 ` Zube
2016-06-22 19:43 ` Warren Young
2016-06-23 10:54 ` Andrey Repin
2016-06-23 18:20 ` Warren Young
2016-06-23 19:37 ` Andrey Repin
2016-06-24 3:23 ` Warren Young
2016-06-25 12:37 ` Andrey Repin
2016-06-23 11:32 ` Andrey Repin
2016-06-23 11:55 ` Zube
2016-06-23 13:05 ` Andrey Repin [this message]
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=152111082.20160623152647@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=Zube@stat.colostate.edu \
--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).