public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KARL BOTTS" <kdbotts@usa.net>
To: <cygwin@cygwin.com>
Subject: Re: Conflict between Cygwin 1.7 and Ubuntu for Windows 14316
Date: Fri, 15 Apr 2016 00:56:00 -0000	[thread overview]
Message-ID: <898uDoa4k7168S05.1460681770@web05.cms.usa.net> (raw)


Did the inability of UoW to read a Cygwin created file ever get explained?

Last I saw was from Evgeny Grin, which contained the iacls dumps.

What jumps out is that the non-Cyg files have X perms, the Cyg file does not. 
I assume others noticed that.  Of course, X perms should not be needed to read
the file.

Also, the perms shown by the UoW ls differ a lot from what the Cyg ls shows,
for the same file.  It would seem they are _interpreting_ Win perms as
different sets of Unix perms.

And the creat() operation may be _assigning_ the Win perms differently, too. 
Maybe differences handling umask values, or maybe different "effective" umask
values, somehow?  Yet somehow I doubt the umask is it; there could be lots of
underlying causes.

I am not a bit surprised things differ.  Who do we think is right, if either?


And then, an interesting question.  Suppose we Cygwin users think we have
identified a defect in UoW.  Do we notify the MS people?  Whom and how?  I
guess I think we should, though I'm not happy about it.  (If they are wise,
they will be lurking here, for exactly this reason...)


Really, I am just curious, no dog in any fight...


---
Karl Botts, kdbotts@usa.net


--
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-04-15  0:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  0:56 KARL BOTTS [this message]
2016-04-15  1:04 ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2016-04-13 17:32 KARL BOTTS
2016-04-13  5:23 John Cowan
2016-04-13 10:02 ` Gerrit Haase
2016-04-13 12:29   ` LLoyd
2016-04-13 13:11     ` John Cowan
2016-04-13 13:36       ` Eliot Moss
2016-04-13 15:44         ` John Cowan
2016-04-13 16:22           ` Gerrit Haase
2016-04-14  9:12             ` Evgeny Grin
2016-04-14  9:35               ` Evgeny Grin
2016-04-15  8:49               ` Gerrit Haase
2016-04-15 11:38                 ` Corinna Vinschen
2016-04-16 18:54                   ` Evgeny Grin
2016-04-18 13:26                   ` Gerrit Haase
2016-04-18 17:14                     ` Gerrit Haase
2016-04-16 18:58                 ` Evgeny Grin
2016-04-15  0:51             ` John Cowan
2016-04-15  8:47               ` Gerrit Haase
2016-04-15 16:23                 ` John Cowan
2016-04-16 12:50                   ` Matt Smith
2016-04-13 22:35           ` Andrey Repin
2016-04-14  8:17         ` Evgeny Grin

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=898uDoa4k7168S05.1460681770@web05.cms.usa.net \
    --to=kdbotts@usa.net \
    --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).