Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 31 Jul 2002 15:45:38 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problems with CPAN Message-ID: <20020731154538.M3921@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <31CB870AD5AA384BB5419025DD9F7A84104355@dailymail.cfs.ac.uk> <31CB870AD5AA384BB5419025DD9F7A8410435A@dailymail.cfs.ac.uk> <20020731114049.D3921@cygbert.vinschen.de> <3D47BC77.9090405@upb.de> <20020731151259.K3921@cygbert.vinschen.de> <3D47E74C.2060908@upb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3D47E74C.2060908@upb.de> User-Agent: Mutt/1.3.22.1i On Wed, Jul 31, 2002 at 03:34:04PM +0200, Sven Köhler wrote: > >I thought about implementing POSIX-ACLs once but the POSIX implementation > >requires a lot of rework and I'm not sure if it's worth the effort since > >POSIX IEEE Std. 1003.1e has been withdrawn. > > hmm - i just thought about the stat() call and why it could fail on a > file - shouldn't this happen too on an ACL using UNIX-System in some > cases? and how do these systems overcome this problem? They don't. It's not the problem of the system but of the tools. Non-ACL aware tools will always have this sort of problem. I assume that vendors as Sun are reviewing the tools which are part of their OS releases to support ACLs. As you can see, sometimes it's easy as in Cygwin to use access(2) instead of stat(2) but it's all up to the tool maintainer. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/