X-Spam-Check-By: sourceware.org Date: Mon, 8 Jan 2007 10:52:20 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe?? Message-ID: <20070108095220.GB22258@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200701051934.l05JYbCj030969@tigris.pounder.sol.net> <20070107112341.GC10586@calimero.vinschen.de> <200701072018.l07KIwnk022580@tigris.pounder.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701072018.l07KIwnk022580@tigris.pounder.sol.net> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jan 7 14:18, Tom Rodman wrote: > On Sun 1/7/07 12:23 +0100 cygwin@cygwin.com wrote: > > On Jan 5 13:34, Tom Rodman wrote: > > > setfacl -m u:jdoe:rwx foo > > > > > > Above command returns 0 but jdoe can not write. The cause appears to > > > be that the windows RO file attribute is not unset by setfacl. > > > > I see the point. That old DOS R/O attribute is SO crappy on a file > > system which supports real permissions. Oh well... > > theory - these 2 steps will make *any* windows NTFS file, > no matter what it's owner, group, perms, or file attributes are, > writable by user "jdoe" (assuming it's not "in use"): > > setfacl -m u:jdoe:rwx foo > # running as administrator "jdoe" > cmd /c attrib -R foo > # setacl step above allows the 'attrib' to work for user "jdoe" > > I appreciate the power in setfacl. :-> I've applied a patch to Cygwin yesterday which resets the R/O attribute if one ACE sets write permission. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/