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: Fri, 28 May 2004 17:32:28 -0400 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: 1.3.22 -> 1.5.10: chmod behavior change Message-ID: <20040528213228.GA632349@Worldnet> References: <20040528192536 DOT GA89120 AT lizzy DOT catnook DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040528160424 DOT 03234d00 AT pop DOT theworld DOT com> <20040528211453 DOT GB89120 AT lizzy DOT catnook DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040528211453.GB89120@lizzy.catnook.com> User-Agent: Mutt/1.4.1i On Fri, May 28, 2004 at 02:14:31PM -0700, Jos Backus wrote: > On Fri, May 28, 2004 at 04:06:43PM -0400, Larry Hall wrote: > > Please follow the guidelines outlined here for reporting problems: > > > > >Problem reports: http://cygwin.com/problems.html > > Sorry. `cygcheck -s -v -r' output attached. > > > Without the benefit of the above, I'm forced to ask whether you set > > "smbntsec" in your Cygwin environment variable? > > No. 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)? There is no need to have such permission to make the file readonly, but 1.5.10 doesn't take that case into account. Pierre -- 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/