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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: AW: 1.5.16-1: chmod problem Date: Wed, 4 May 2005 13:12:24 +0200 Message-ID: From: "Pach Roman (GS-EC/ESA4) *" To: X-OriginalArrivalTime: 04 May 2005 11:12:25.0289 (UTC) FILETIME=[269C4B90:01C5509A] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j44BDHq4001097 Hello Corinna, it's running now !!! Thanks you very much for your fast reaction. Roman -----Ursprüngliche Nachricht----- Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]Im Auftrag von Corinna Vinschen Gesendet: Mittwoch, 4. Mai 2005 11:06 An: cygwin@cygwin.com Betreff: Re: 1.5.16-1: chmod problem On May 4 06:53, Pach Roman (GS-EC/ESA4) * wrote: > I admit I'm stubborn about this topic but I'd like to propose > the change of chmod implementation. > I thing, it would be nice if the 'chmod +/-w' would have in the discussed case the same > functionality as the Windows' command 'attrib'. > See please the appended screenshot. Try the latest snapshot from http://www.cygwin.com/snapshots/. I've tried to workaround a bug in chmod since it was originally meant to work the way you suggest. However, if you don't have the "write attribute" permission set in the file's ACL, you're out of luck. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/ -- 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/