public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Zube <Zube@stat.colostate.edu>
To: cygwin@cygwin.com
Subject: Re: wget 1.17.x creates odd permissions on downloaded files
Date: Thu, 23 Jun 2016 11:55:00 -0000	[thread overview]
Message-ID: <20160623114806.GA138493@quantum.stat.colostate.edu> (raw)
In-Reply-To: <1615080910.20160623133417@yandex.ru>

On Thu Jun 23 01:34:17 PM, Andrey Repin wrote:

> Greetings, Zube!

Thanks very much for taking the time to reply.

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

Cheers,
Zube

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

  reply	other threads:[~2016-06-23 11:48 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 [this message]
2016-06-23 13:05     ` Andrey Repin

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=20160623114806.GA138493@quantum.stat.colostate.edu \
    --to=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).