X-Recipient:	archive-cygwin AT delorie DOT com
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=BRQSxFlJOkvjq0zp
	YoOwjGnpq1I2cjcyyzNbyAZhcTIfNj1ehS+49hhYU/AmZwcHG4NdF36TG5Th5/AO
	SdslB3hpq1s9G71Dklgq4iPBz1wKqCSajqum0ECvRK7XmB4mGCOqHWWimMY6JEzZ
	N1duNdsXa2cKAHsY5mgphPXpXfs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=RXiNvIz0sQwao+J1Yafq/N
	P4n7Y=; b=Hpayc5BCAooK0H6686Ci/JvqRz47aTMkL+d2H0PS5FkwcfltNrhQGE
	BGUI+BdumpYqBMpi6eGk7AiZBWhHGRFflZWSa5rGSB70nW8r6fMlppF2xgzWS7vD
	eT+5zMziWa3JLf5dwI8Y3Js4kQsgln29XhaOmTnjzsvFhfQGmwfKM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=4.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,MIME_BASE64_BLANKS,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Wed, 23 Sep 2015 11:15:37 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<154887677.20150923111537@yandex.ru>
To:	"Walter L." <bournenoir AT hotmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Issues encountered with new Cygwin version
In-Reply-To:	<BLU182-W10FB6B21A2AEC90F71470FD4450@phx.gbl>
References:	<BLU182-W10FB6B21A2AEC90F71470FD4450 AT phx DOT gbl>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id t8N8Kelu005373

Greetings, Walter L.!

> I've just performed a fresh install of the latest (2.2.1) Cygwin on 64-bit
> Windows 7 and noticed 2 issues with the new version that I'd like to verify whether or not they are bugs:

> 1) The symlink to protocol file seems incorrect

> [user AT hostname /etc]$ ls -l | grep protocol
> lrwxrwxrwx  1 user Domain Users     50 Sep 22 17:03 protocols ->
> /cygdrive/c/Windows/System32/drivers/etc/protocols
> [user AT hostname /etc]$ ls -l /cygdrive/c/Windows/System32/drivers/etc | grep protocol
> -rwxrwx---+ 1 SYSTEM         SYSTEM  1358 Jun 10  2009 protocol

> I believe the target of the symlink should be "protocol" (i.e. singular)

Err. That is. How did no one found it earlier?

> 2) The 'touch' command creates a file with the executable bit set

> [user AT hostname ~]$ touch newfile.txt
> [user AT hostname ~]$ ls -l newfile.txt
> -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt

> I am fully aware that Windows programs (e.g. Eclipse and Windows Explorer)
> will create files with the executable bit set due to ACL and NTFS
> permissions. However, if I 'touch' a file inside an earlier version of
> Cygwin

Define "earlier" ? The permissions handling has been extensively rewritten
since 1.7.34.

> the file would be created without the executable bit set (i.e. 644).

Which will then prevent opening it from Explorer by file association.

> To be honest, I can't tell if this is caused by the new version of Cygwin or a Windows Update.

Likely it is caused by the change in Cygwin permissions handling.
It now correctly inherit permissions in most cases.

> [user AT hostname ~]$ uname -a
> CYGWIN_NT-6.1-WOW hostname 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin


-- 
With best regards,
Andrey Repin
Wednesday, September 23, 2015 11:12:34

Sorry for my terrible english...

- Raw text -