DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=WIKh7VGM2JlXosI3
	m5oe+tC9LvrEIvU2pmKZbHUT8GwpEB3ySoC8g4moDuW87JSBsSFXa7UAsgMXNHaJ
	W0hSRRtRFgGIXJ/0TazR59rsuEgO6jTUJELdiYOc+HCoBJa0sSZHKgIPWxmCTHAl
	H7VGFZLDHvMf54scTCv3Y3xfCaQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 28 Dec 2019 16:58:59 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <623944058.20191228165859@yandex.ru>
To: Peter Binney <peter.binney@gmail.com>, cygwin@cygwin.com
Subject: Re: Files created with CYGWIN have "NULL SID:(DENY)" windows ACL, inter alia
In-Reply-To: <CAJiKf6HWP1vv1wN93R0znRnL1A0TNY+5CAm50mny4nrMqcBVPA@mail.gmail.com>
References: <CAJiKf6Ht6DA4hyVHWCocFwC5CNvkWNTMPZvitGdF-YyTgVYYfA@mail.gmail.com>   <1857710854.20191222165411@yandex.ru>  <CAJiKf6HiNckg8rHxibwrP=+n-rxobyVmSTH8kaooRtH8MXXmvA@mail.gmail.com>  <1466141893.20191224121706@yandex.ru>  <CAJiKf6HWP1vv1wN93R0znRnL1A0TNY+5CAm50mny4nrMqcBVPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Peter Binney!

Bottom posting in this list, please.

> Hello Andrey - many thanks again.

> I have added noacl to the default fstab entry, so it reads:
> none /cygdrive cygdrive noacl,binary,posix=0,user 0 0

> and that sorts out the permissions problem, thank you.

> But, bizarrely, it introduced a new one - the WHICH command no longer
> reports non-executable files on the PATH.

> Such files are found and executed OK (presumably because Windows logic
> is adhered to, where execute permission is not required), but WHICH
> doesn't "see" them.

> So I had to build a work-around for WHICH (which I use in various
> scriptware) since I can also find no way to set the execute bit on a
> file ("chmod a+x" doesn't seem to do anything with or without noacl).

This could be actually because you are lacking executable permission on your
files. Which Windows by default always set.


-- 
With best regards,
Andrey Repin
Saturday, December 28, 2019 16:57:49

Sorry for my terrible english...


--
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