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:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=d5gu
	KAAJZ+UM2qLepCIweeF4I2UnJTDhJkB9O2ZYrzAvJX4oVKtptV2E8KKwZoJuEitw
	xSqUcsNpsESisdJY8MSV4ZwgnsGU14BsPhuexdZpaF0cLgKYfeJqVupAvI1l41Xt
	Z4fXZ8uqw3mb3iX0B3Ewhqu6ORQL5JhL2dZuQiI=
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:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=rf7lw7juZ1
	2E/HAUlU5qPBDDfEg=; b=s3bP2KZVkU2WGCDZP+/7qgLs+BIdd9n0YhbNnHnrVt
	ZM9PsgMg2lZbxEAQ4t1msAOystlnMHSaoMyR0sNK4cPMN8KljPjFLSWGYNpcM/C3
	9yDUB9VKL7zUBeuaBJerLD2PrV1ZiSwOuHdpR0bbkm6Y4Q9mRz5LDKZuceBD/yn0
	E=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: Yes, score=5.1 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPAM_BODY,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:949, lurking, wise, Whom
X-HELO: earth.ccil.org
Date: Thu, 14 Apr 2016 21:04:09 -0400
From: John Cowan <cowan AT mercury DOT ccil DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Conflict between Cygwin 1.7 and Ubuntu for Windows 14316
Message-ID: <20160415010409.GF29184@mercury.ccil.org>
References: <898uDoa4k7168S05 DOT 1460681770 AT web05 DOT cms DOT usa DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <898uDoa4k7168S05.1460681770@web05.cms.usa.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-IsSubscribed: yes

KARL BOTTS scripsit:

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

See the long post I just sent out.

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

There may or may not be a defect in UoW in terms of UoW processes not having the
permissions they should have.  On the other hand, Cygwin is definitely creating
strange ACEs that make files it creates inaccessible to UoW.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan AT ccil DOT org
Clear?  Huh!  Why a four-year-old child could understand this report.
Run out and find me a four-year-old child.  I can't make head or tail
out of it.        --Rufus T. Firefly on government reports

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