X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:mime-version:message-id :content-type:content-transfer-encoding; q=dns; s=default; b=yYA dx4l3HuSf0ikPkYAbbZt9gEEPwr9CchsoJzt4T5SkqRKQ5VPnek7eWGIV631xzQC zhiq+H0GuB/8xPlpVnvnyMYzOkAMBspaADMWi43M+KJt1GkE/WIiFsypNq6A4e4a RwAdUF++AQtzdeKuPzzUZvFjbCF6naOTpnfviZgg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:mime-version:message-id :content-type:content-transfer-encoding; s=default; bh=wZpHHgYcI aNbaUNLHvrYdtPSBl0=; b=ukLzdXV4SLRjYh4h6Q/XinBipJ5GtxEV8X4M4tgbA ULgUScwNLDhtvixcRJq9PCtVV3uvx+6lRdR2TMZaET0d8ja8vzoK7IPPkDuvLUP+ KYw147YDc2RMsgBHRXiDY1z3ztgKB7Iz7Wg5W40n2wJ2eaizY1+D+aPpJbAkPxh2 xA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.8 required=5.0 tests=BAYES_50,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_PASS autolearn=no version=3.3.2 spammy=creat, H*M:usa, H*MI:usa, cyg X-HELO: co01.mbox.net X-USANET-Received: from co01.mbox.net [127.0.0.1] by co01.mbox.net via mtad (C8.MAIN.4.02J) with ESMTP id 273uDoa5k3104M01; Fri, 15 Apr 2016 00:56:10 -0000 X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-GWS2-Tenant: usa.net X-USANET-GWS2-Tagid: UNKN X-USANET-Source: 165.212.11.133 OUT kdbotts AT usa DOT net ca33.cms.usa.net CLR X-USANET-MsgId: XID399uDoa5k1687X01 X-USANET-Auth: 165.212.8.205 AUTO kdbotts AT usa DOT net web05.cms.usa.net Date: Thu, 14 Apr 2016 19:56:10 -0500 From: "KARL BOTTS" To: Subject: Re: Conflict between Cygwin 1.7 and Ubuntu for Windows 14316 Mime-Version: 1.0 Message-ID: <898uDoa4k7168S05.1460681770@web05.cms.usa.net> Content-Type: text/plain; charset=ISO-8859-1 Z-USANET-MsgId: XID258uDoa5k5904X33 X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u3F0ud70005514 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 AT usa DOT 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