X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.6 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: <AANLkTikLOv2xn2RodtrRfgdGnSYYZrMeKyWBfDA67Js1@mail.gmail.com>
References: <AANLkTima5VbUF2XFvv00ptE1L=9c9BT2hOOM8td4hhUN AT mail DOT gmail DOT com> <AANLkTinZs2FvqFtYueGR0-Wg5L9veTLaE7+SJa56R-r4 AT mail DOT gmail DOT com> <i5li5e$tse$1 AT dough DOT gmane DOT org> <AANLkTi=Z8dSKa6fWt6m2dKMG8gVnG4LEZuq+QN1Y=Qb6 AT mail DOT gmail DOT com> <AANLkTinHHFQSrqJuzhnLzUKLw321Pe2qc=2mkao2Z5iU AT mail DOT gmail DOT com> <AANLkTimzCUXnhekxmjDmmgHgw+ocKt-xBh5Ei=HF5QsB AT mail DOT gmail DOT com> <AANLkTikLOv2xn2RodtrRfgdGnSYYZrMeKyWBfDA67Js1 AT mail DOT gmail DOT com>
From: Vasya Pupkin <cygwin AT bsrealm DOT net>
Date: Thu, 2 Sep 2010 06:08:37 +0400
Message-ID: <AANLkTimBGg8vpw9bFcbzvaieTv5DvOSbK5ytJnpLcVP0@mail.gmail.com>
Subject: Re: Fwd: Windows File permissions are not being inherited - Cygwin 1.7 - Windows 7
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Because I prefer to keep things under control. 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. A non-privileged user could modify cygwin
configuration files in /etc and it was not possible to do something
about it. That is when I decided to control permissions myself, but
cygwin setup overwrites permissions on every install, including files
in /etc, messing up everything.

On Thu, Sep 2, 2010 at 12:18 AM, Andy Koppe <andy DOT koppe AT gmail DOT com> wrote:
> On 1 September 2010 15:18, Vasya Pupkin wrote:
>>> Do creating any entries in /etc/passwd =C2=A0or /etc/group or /etc/fstab
>>> files can overcome this...
>>
>> Nothing can overcome thins until setup.exe is modified to support
>> noacl option in /etc/fstab or get a similar comman line parameter or
>> even a checkbox.
>
> Reading /etc/fstab wouldn't work for the initial install. All these
> possibilities require a substantial amount of (voluntary) work, yet so
> far the only reason you've given for it was that you "don't like how
> cygwin works with NTFS permissions and therefore it is disabled
> through /etc/fstab". It shouldn't surprise you that that doesn't put
> it high on anyone's list of priorities.
>
> So why do you care about permissions on files that come with setup.exe
> packages? Setup.exe won't touch /home or anything outside the Cygwin
> install.
>
> Andy
>
> --
> 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