From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19738 invoked by alias); 22 Oct 2018 12:05:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 19709 invoked by uid 89); 22 Oct 2018 12:05:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:build, HX-Priority:Normal, terrible, judge X-HELO: forward102j.mail.yandex.net Received: from forward102j.mail.yandex.net (HELO forward102j.mail.yandex.net) (5.45.198.243) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 22 Oct 2018 12:05:05 +0000 Received: from mxback2j.mail.yandex.net (mxback2j.mail.yandex.net [IPv6:2a02:6b8:0:1619::10b]) by forward102j.mail.yandex.net (Yandex) with ESMTP id 2A5875601CAF; Mon, 22 Oct 2018 15:05:02 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback2j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 0p1fmuvVPZ-5170fOrF; Mon, 22 Oct 2018 15:05:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1540209902; bh=ABIURv3UbOnRoIAe1EooVNi2jgmeLneeKnidYkgtpM0=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=Zclsy4bO/gE4Z3E7+tr8bFq2JnNpsH7AFXm+MwgTvOcr7lzsk0zRwkm3DOORtNWw3 IVPr7k4AFA9CqJ5bQuMIn+NZCRTk/diGB4qjQUB+QvHyPCRJg0N7QzVq8YWuTU4YDu UMp3q/Lr/Hr0JMqctuivjL+WP2dXDNcij0/0Igl8= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 9OTI6dTbp6-51IeKLow; Mon, 22 Oct 2018 15:05:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1540209901; bh=ABIURv3UbOnRoIAe1EooVNi2jgmeLneeKnidYkgtpM0=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=jk/2kRiIywY/0TftLl9Rp/Xb3nugqXWbytv3FVvlY1f12STqYE6F/Wz+YrVHEWDqQ bBYnuixrJOe+4H0IZHvFgZ0NDyAZW6K3EHXLKB0CkZ/Rcngf5wQlY0WB+Lo5Ps0kxI rr9XBFvUxOKrNIe/xRPrOVk14DDODnCMhsHESR58= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Mon, 22 Oct 2018 12:02:45 -0000 Date: Mon, 22 Oct 2018 12:05:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <174350011.20181022150245@yandex.ru> To: Michael Enright , cygwin@cygwin.com Subject: Re: Multiple problems (probably) starting up new installation In-Reply-To: References: <164597258.20181022013753@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00172.txt.bz2 Greetings, Michael Enright! >> >> > ----rwx---+ 1 menright Mike Enright 0 Oct 21 15:02 CMakeLists.txt >> >> the "+" says that there's extended ACL present. So, nothing odd. >> > The Windows view of this set of permissions (070 plus whatever is in > the rest of the ACL) This is NOT "windows" view, this is Cygwin view. For ACL, check getfacl . > seems to be that Windows programs can't do very > much with this file. See my previous note about setting noacl flag to increase interoperability with native programs. > So it's odd from that POV and I wonder if that was caused by my renaming the > "Cygwin account". I'm not clear on how exactly renaming was done, so can't comment. > Using cacls I see the > Windows username in some of the entries and I don't see the cygwin > username in any. I know that I can get a workable ACL with chmod but I > can see that executables built by the compiler are not executable, > either by name from cygwin bash or by double click from Windows > Explorer. This is the first few lines from cacls: > $ cacls moneymaker > C:\cygwin64\home\menright\moneymaker NULL SID:(DENY)(special access:) > READ_CONTROL > FILE_READ_EA > FILE_WRITE_EA > FILE_EXECUTE > FILE_DELETE_CHILD This is normal (documented) behavior for less-than-trivial permission setups. However, without a full dump of cacls it's hard to judge correctness of the ACL on a given file. -- With best regards, Andrey Repin Monday, October 22, 2018 14:58:59 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