X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: From: Vasya Pupkin Date: Thu, 2 Sep 2010 09:49:26 +0400 Message-ID: Subject: Re: Fwd: Windows File permissions are not being inherited - Cygwin 1.7 - Windows 7 To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 No, it wasn't a mess of my own making. I did not ever touch permissions, and it was a clean install. I don't know where these permissions came from, but ls -l displayed something like that for most files: drwxr-xr-x+ 1 user group 0 2010-09-02 09:32 tests This "+" sign after permissions string indicated non-cygwin permissions which was impossible to remove using cygwin's chmod. And since permissions are not inherited, it was not possible to mass remove them using windows either. So, I just removed all permissions and forced their inheritance. That solved all problems, until I updated installation using setup.exe. Believe me or not, but I really did not touch any permissions until I noticed that strange behaviour. And I am the only administrator. Machine is not a part of any domains. So, unless it's a kind of black magic, there was (and maybe still is) some issue with permissions in cygwin. That is why I don't want to use them. On Thu, Sep 2, 2010 at 9:10 AM, Andy Koppe wrote: > On 2 September 2010 03:08, Vasya Pupkin wrote: >> Because I prefer to keep things under control > > Oh $DEITY. > >> And I don't think it >> will require a huge amount of work to disable working with permissions >> in setup.exe with command line switch. I started to worry about it >> because cygwin failed so much with permissions, having both >> cygwin-specific and inherited ones (copied) at the same time, >> resulting in complete mess. > > That appears to be a mess of your own making. Otherwise, concrete bug > reports please. The OP's complaint here was that permissions aren't > inherited, so I've got no idea what you're on about. > >> A non-privileged user could modify cygwin >> configuration files in /etc and it was not possible to do something >> about it. > > Well, I don't know what you did, but I install Cygwin as administrator > and work as an ordinary user, and no, I can't modify anything in /etc. > And that's no accident of course, because a lot of work has gone into > mapping POSIX permissions to NTFS permissions in a sensible way. > > Andy > > > ps: Please don't top-post. http://www.cygwin.com/acronyms/#TOFU > > -- > Problem reports: =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/problems.html > FAQ: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http:= //cygwin.com/faq/ > Documentation: =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://cygwin.com/docs.html > Unsubscribe info: =C2=A0 =C2=A0 =C2=A0http://cygwin.com/ml/#unsubscribe-s= imple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple