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:mime-version
	:content-type; q=dns; s=default; b=Yf/7LRl5b8uJrQel/Ef5J8siOCj/R
	2pZ03luMUTVrV9TVH0evAReesXUZLCWqbTAgg7u5DoXI5+Mac4y9/Bn4IJ9pBx0Y
	OjufxrHkFwnBxW6+8lUtXMJr/Q+AHKCxs5EV/d5HqBgnx2I8lwatMU03w3EzpLqP
	U05S34PLKCRqwI=
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:mime-version
	:content-type; s=default; bh=Xu6WSZuOzuaK2A4TY2YoXzA+vI0=; b=Yr/
	nx6SKZ/f3EpStwD/FxaX6kJFk1GXoJry9D2JuToOLm1qtiC/UnKpV4DmTc5sZQ7u
	aWQ+hzOIiIqwHRov1qKMxvs7oh+fwCUB957z08wlnX6dCxW4iXA8lkUg1+CBjfgT
	EWh7aoV3+JOjyn7j8SnJFtI1++dArF06+2FTWrBA=
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:	No, score=-0.9 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=username, H*u:1.5.20, H*UA:1.5.20, cmdexe
X-HELO:	earth.ccil.org
Date:	Wed, 13 Apr 2016 01:22:58 -0400
From:	John Cowan <cowan AT mercury DOT ccil DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Conflict between Cygwin 1.7 and Ubuntu for Windows 14316
Message-ID:	<20160413052257.GB28803@mercury.ccil.org>
MIME-Version:	1.0
User-Agent:	Mutt/1.5.20 (2009-06-14)
X-IsSubscribed:	yes

After many years as a contented Cygwin user, I decided to check out
the new Ubuntu on Windows (UoW) product from Microsoft.  I promptly
ran into a nasty problem.  I have filed it with the MS Feedback Hub,
but I thought I should post here as well.

When a file is created under Cygwin, it can neither be read nor written
by UoW.  Any attempt to do so returns EACCES.  It does not matter
whether the UoW user is root or not, and it does not matter what the
file permissions are as seen by UoW, or whether the file is in the UoW
root (which is really C:\Users\<username>\AppData\Local\lxss\rootfs)
or elsewhere on C: (which is mounted by UoW at /mnt/c).  It also does
not matter who has written to the file (Win32, Cygwin, or UoW).
Directories are not affected by this problem.

Is Cygwin creating ordinary files with some kind of magic that's different
from creating a file, say, by output redirection in cmd.exe, or in a Win32
application?  This is not about file names with funny characters, either.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan AT ccil DOT org
C'est la` pourtant que se livre le sens du dire, de ce que, s'y conjuguant
le nyania qui bruit des sexes en compagnie, il supplee a ce qu'entre eux,
de rapport nyait pas.               --Jacques Lacan, "L'Etourdit"

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

- Raw text -