DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=K2r
	1ntvKcmYPC6MFt9P/uvxSpDYpH7RQC0/Ye/eAtAziWidStpxyDBzGyyszTcoR7J1
	8GApmk8Br4JVfIEY+JSng7RTCGBqJ4FaZ1Vn0suv9vHrul9OpYgTvgFAhTeXcame
	J2y/N+SfrZTCtXoUA1QisEqIcowwOi8AJiUv3VEo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <BLU182-W10FB6B21A2AEC90F71470FD4450@phx.gbl>
From: "Walter L." <bournenoir AT hotmail DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Issues encountered with new Cygwin version
Date: Tue, 22 Sep 2015 19:04:11 -0400
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Hi,

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)

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 the file would be created without the executable bit set (i.e. 644). To be honest, I can't tell if this is caused by the new version of Cygwin or a Windows Update.

[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

This is my first time posting, so please let me know if I need to provide additional information, or if I should split this into 2 separate topics.

Thanks,
~WL
 		 	   		  
--
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