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: Fri, 28 May 2004 15:20:15 -0700 From: Jos Backus To: cygwin@cygwin.com Subject: Re: 1.3.22 -> 1.5.10: chmod behavior change Message-ID: <20040528222037.GA7870@lizzy.catnook.com> Reply-To: jos@catnook.com References: <20040528192536.GA89120@lizzy.catnook.com> <6.1.0.6.0.20040528160424.03234d00@pop.theworld.com> <20040528211453.GB89120@lizzy.catnook.com> <20040528213228.GA632349@Worldnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040528213228.GA632349@Worldnet> User-Agent: Mutt/1.5.6i On Fri, May 28, 2004 at 05:32:28PM -0400, Pierre A dot Humblet wrote: > I think I see what the problem is. Is it correct that you do not have > permission to change the permissions on that drive (even in the File > Properties box)? I'm not sure what you mean. When I open the Properties of file x, I can change its attributes (Read-only in this case) without problems, and Cygwin's ls reflects those changes properly. It's just chmod that doesn't work. > There is no need to have such permission to make the file > readonly, but 1.5.10 doesn't take that case into account. This sounds like a 1.5.10 regression, no? I actually saw the opposite problem first: files that are -r--r--r-- I cannot chmod +w, whereas I can change them using the Properties dialog. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer' -- 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/