This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Issues encountered with new Cygwin version
- From: Walter L. <bournenoir at hotmail dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Tue, 22 Sep 2015 19:04:11 -0400
- Subject: Issues encountered with new Cygwin version
- Authentication-results: sourceware.org; auth=none
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@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@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@hostname ~]$ touch newfile.txt
[user@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@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