Message-ID: <30397F695F2C4913B332511F9A2E839A@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: <cygwin@cygwin.com>
References: <BE3716D1FE6B45B6A50DEB1B448E71ED@multiplay.co.uk>  <4B12FB72.9090206@x-ray.at>  <270B141F0B5B480C9A668369AA2C53A3@liv3dworkpc>  <5E63D05B501C4339A7D7F8909505E828@multiplay.co.uk>  <4B15556A.4080108@gmail.com> <20091201173036.GE8059@calimero.vinschen.de>
Subject: Re: Nasty permissions / pathing bug on 1.7
Date: Tue, 1 Dec 2009 18:03:05 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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