cygwin 1.7.9, problem with cygwin1.dll, path_conv::check, has_acls()? (Windows 7)

Larry Hall (Cygwin)
Wed Sep 14 21:02:00 GMT 2011

On 9/14/2011 4:31 PM, John Ruckstuhl wrote:
> Larry Hall wrote:
>> On 9/14/2011 1:56 PM, Thorsten Kampe wrote:
>>> The obvious way to troubleshoot this would be to use a network drive (Z:
>>> for instance) instead of UNC or to mount the share and see if that
>>> works. Naturally it would also make sense to test the latest Cygwin
>>> snapshot and to see if you get the same result if you use //localhost/C
>>> $.
>> Right.  I was thinking this could fall into the category of a network
>> share that needs to have the "noacl" mount option set.  So another
>> option is to try mounting the UNC path to a Cygwin path (in /etc/fstab)
>> and specify the "noacl" option.
> ------------------------------------------------------------------------
> Both of your comments are a bit over my head.
> I'll put in an honest effort to figure out what you mean, and then reply
> with results.
> It seems you are suspicious of the mount... that a defective mount WOULD
> interfere when the target is expressed one way, and WOULDNOT interfere
> when the target is expressed the other way.

Not defective, no.  In my case, I'm suggesting that you turn off POSIX
permissions.  These sometimes cause problems for network drives.  So
do something like this:

   mkdir /foo
   mount -o noacl,binary,notexec //hyperdisk/Data/Engineering/ruck /foo

Then try the same tests using /foo as the root path.

You can find more information about mount options here:




A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list