X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 1 Dec 2009 19:13:36 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Nasty permissions / pathing bug on 1.7
Message-ID: <20091201181336.GG8059@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-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>  <30397F695F2C4913B332511F9A2E839A AT multiplay DOT co DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <30397F695F2C4913B332511F9A2E839A@multiplay.co.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Dec  1 18:03, Steven Hartland wrote:
> ----- 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?

Win32 path -> No POSIX path -> no POSIX permissions.

There was a thread on this list about this very problem a couple of
months ago.  It was generally agreed that handling Win32 paths this way
consistently is a good thing.

> 2. Surely when performing changes on permissions with a mount mode of
> noacl it should be a fatal error?

No.  "noacl" means that permissions are faked.

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

It's easy.  If you want POSIX permssion handling, stick to the POSIX
world.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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