Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3D47E74C.2060908@upb.de> Date: Wed, 31 Jul 2002 15:34:04 +0200 From: =?ISO-8859-1?Q?Sven_K=F6hler?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721 X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problems with CPAN References: <31CB870AD5AA384BB5419025DD9F7A84104355 AT dailymail DOT cfs DOT ac DOT uk> <31CB870AD5AA384BB5419025DD9F7A8410435A AT dailymail DOT cfs DOT ac DOT uk> <20020731114049 DOT D3921 AT cygbert DOT vinschen DOT de> <3D47BC77 DOT 9090405 AT upb DOT de> <20020731151259 DOT K3921 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Jul 2002 13:32:11.0056 (UTC) FILETIME=[AC86CB00:01C23896] >>but: shouldn't there be a better conversion of NT-ACLs to unix-perms? >>perhaps a POSIX-ACL implementation? > > We have a Solaris compatible implementation of ACLs. Look into > /usr/include/cygwin/acl.h (which is called from sys/acl.h). This > is e. g. used to implement access(2) and the tools setfacl(3) and > getfacl(3). It's an official part of the Cygwin API since two > years or so. oops - shame on me - didn't know we had an ACL-implementation already. > 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? -- 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/