X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RDNS_NONE X-Spam-Check-By: sourceware.org content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: SV: Cygwin 1.7 cannot access network share Date: Wed, 3 Mar 2010 14:23:06 +0100 Message-ID: From: "Ilya Beylin" To: "Eric Blake" , Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Use POSIX-style paths, to see the difference. > $ ls -l //HERA/shared/benchmarks/test=20 Thank you, but POSIX style paths make no difference=20 Actually I mentioned it in my first mail, but I did not give any example. Here it is:=20 $ ls -l '//HERA/shared/benchmarks/test' ls: cannot access //HERA/shared/benchmarks/test: No such file or directory $ cmd /c DIR '\\hera\shared\benchmarks\test' /b README.txt $ ls -l '//HERA/shared/benchmarks/test' ls: cannot access //HERA/shared/benchmarks/test/README.txt: No such file or directory total 0 -????????? ? ? ? ? ? README.txt And the same if I use X: or /cygdrive/x, or /mnt/shared > Yes, but only after translating POSIX-style names into windows style names > under the hood. Providing windows-style names up front tells cygwin to > take different code paths, and in particular, turns off some ACL work, and > you are on your own if a name with a backslash doesn't do what you wanted. I understand, but I do not think it does apply in my case. Any further ideas? =20 Ilya Beylin=20 -- 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