Re: Issues encountered with new Cygwin version

[Andrey Repin <anrdaemon@yandex.ru>]

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

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

> 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

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