bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive)

[jari]

On 2011-12-13 11:52, Ken Brown wrote:
| On 12/13/2011 11:26 AM, jari wrote:
| >Response from Cygwin list:
| >
| >     >      $ ls -la /cygdrive/z/tmp/test-epackage.el
| >     >      -rwxr--r-- 1 ???????? ???????? 437 Dec  9 20:02 
/cygdrive/z/tmp/test-epackage.el
| >
| >     It's not a bug.
| >
| >     If you use winbind and the user accounts are correctly mapped to
| >     Windows accounts, then you would see the Cygwin UIDs/GIDs
| >     correspoding to the SID of the AD user account.
| >
| >     If you don't do that, there's only an invisible mapping from the
| >     Windows SID to the Unix uid/gid.  The actual UNIX account has not
| >     the same mapping back to the Windows SID.  Instead, the SID
| >     returned from Samba to Windows is a fake SID S-1-22-1-UnixUID or
| >     S-1-22-2-UnixGID.  (..)
| >
| >The rest goes into details for setting 1:1 UID, GID mapping.
| 
| You omitted the part of the response that says, "The easiest way to
| workaround this issue is to mount the share with the noacl mount
| option".
| Does this fail to work for some reason?

That would create a new "Cygwin mount". Different path altogether than
what is already in use; mapped by the Windows.

     In Windows: Z:\
     In Cygwin : /cygdrive/z

All paths would change if I would Cygwin mount(1) "//server/login
/mnt/login ..."

    /mnt/login   <!=!>  /cygdrive/z

That would create problems all over the place that now assume certain
locations. Not to mention losing ability to copy/paste paths from
Windows File Exporer to Cygwin[*]

Jari

[*] Cygwin accepts drive letter syntax in single quotes: 'z:\'
See also cygoath(1).