X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-497910.1 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
X-MDAV-Processed:	mail1.multiplay.co.uk, Tue, 01 Dec 2009 18:03:05 +0000
X-Spam-Processed:	mail1.multiplay.co.uk, Tue, 01 Dec 2009 18:03:04 +0000 (not processed: message from trusted or authenticated source)
X-MDRemoteIP:	213.123.247.160
X-Return-Path:	prvs=158624c46c=killing AT multiplay DOT co DOT uk
X-Envelope-From:	killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To:	cygwin AT cygwin DOT com
Message-ID:	<30397F695F2C4913B332511F9A2E839A@multiplay.co.uk>
From:	"Steven Hartland" <killing AT multiplay DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<BE3716D1FE6B45B6A50DEB1B448E71ED AT multiplay DOT co DOT uk> <4B12FB72 DOT 9090206 AT x-ray DOT at> <270B141F0B5B480C9A668369AA2C53A3 AT liv3dworkpc> <5E63D05B501C4339A7D7F8909505E828 AT multiplay DOT co DOT uk> <4B15556A DOT 4080108 AT gmail DOT com> <20091201173036 DOT GE8059 AT calimero DOT vinschen DOT de>
Subject:	Re: Nasty permissions / pathing bug on 1.7
Date:	Tue, 1 Dec 2009 18:03:05 -0000
MIME-Version:	1.0
X-IsSubscribed:	yes
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

----- Original Message ----- 
From: "Corinna Vinschen"

> That's by design.  When you use Win32 paths, instead of POSIX paths,
> you will get Win32 default permission handling.  Or, in other words,
> for all DOS paths the mount mode is "noacl".

Ok that begs the questions:-
1. What was the reasoning behind this change?
2. Surely when performing changes on permissions with a mount mode of
noacl it should be a fatal error?

#2 I think is imperative as to leave the user thinking all is well
is going to lead to real confusion, just like it did here, especially
as this worked just fine in 1.5.

I know the warning is there but at no point does it mention the fact
it totally breaks anything that tries to manipulate permissions.

    Regards
    Steve


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