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 Date: Wed, 5 Nov 2003 11:52:05 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.5: opendir opens directory without `r' permissions. Message-ID: <20031105165205.GA2533@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3FA90F35 DOT 1020101 AT ximbiot DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA90F35.1020101@ximbiot.com> User-Agent: Mutt/1.4.1i On Wed, Nov 05, 2003 at 09:54:45AM -0500, Derek Robert Price wrote: >This doesn't appear to be correct behaviour on most other UNIX >platforms. On most platforms the opendir fails and sets an errno that >resolves to "Permission denied". This can be illustrated with the >following short script: > >~ mkdir test >~ touch test/file >~ chmod a= test >~ ls test > >The `ls' will return a blank line under Cygwin bash. On most platform >`ls' will return: > >~ ls: test: Permission denied > >I don't think you'll need my cygcheck output to reproduce this, but say >the word and I will send it. I will add a patch to fix this but making cygwin work 100% like unix/linux will be difficult since unix historically also recognizes the 'x' bit in a directory to control access as well. I'm not going to do that for cygwin, though, since it would impose a burden on every file access. Btw, I'm not asking for anyone to send email clarifying how linux deals with directory protections. I'm pretty clear on how it works and on the difficulty level for getting this working on cygwin. cgf -- 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/