This is the mail archive of the
mailing list for the Cygwin project.
Re: Error accessing mapped drive >2TB?
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Mon, 21 Sep 2015 21:32:59 +0000 (UTC)
- Subject: Re: Error accessing mapped drive >2TB?
- Authentication-results: sourceware.org; auth=none
- References: <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg at mail dot gmail dot com> <712A87EA-64C7-4033-BE7F-39C8C8D527EB at etr-usa dot com> <110723294 dot 20150915064630 at yandex dot ru> <CA+2x6-LtkKk15AOavG5pUD+YwcKKa=TKU1nnHwEy45LKwLkFJg at mail dot gmail dot com> <0C37A612-5E78-48A8-9503-F3A34129BC7B at etr-usa dot com> <CA+2x6-L+dr92-O1b2bnqnaCxOzZ9GCLv1ekXEPcALkuYvFp_yQ at mail dot gmail dot com> <B35CA86C-3AFD-424A-AFE7-7A2B4FE0B421 at etr-usa dot com> <loom dot 20150921T061240-314 at post dot gmane dot org> <1536508568 dot 20150921085631 at yandex dot ru>
Andrey Repin <anrdaemon <at> yandex.ru> writes:
> Greetings, Brian Inglis!
> > $ ls $(cygpath '\\live.sysinternals.com\tools\') # works - list contents
> > About_This_Site.txt ctrl2cap.amd.sys* Eula.txt
> > ...
> > $ ls `cygpath '\\live.sysinternals.com\tools\'` # fails - should be same as
> > above 2
> > ls: cannot access /cygdrive/c/live.sysinternals.com/tools/: No such file or
> > directory
> Not necessarily. This is why using the backticks is discouraged.
> They have weird escaping rules and generally non-obvious.
> Stick to $( ... ).
Never noticed any issues previous to this but generally don't use
backslashes except as escape character, and MS utilities which require
legacy path separators (even under DOS, many non-MS utilities would accept
normal path separators, as the underlying APIs didn't care, and neither do
most of the Windows APIs).
> > Windows Explorer drive mappings are not visible from cmd or mintty/bash
> > windows, but "net use x: \\live.sysinternals.com\tools" mappings are visible
> > from separate cmd and mintty/bash windows as drive X: or /cygdrive/x, but
> > x:\ is not accessible from Windows Explorer.
> Are you sure you're looking from the same user session?
Same user session, different (elevated) cmd and mintty/bash console sessions.
> If you start mintty/cmd elevated, you won't see drives mapped in Explorer
Kind of figures on Windows - I would expect elevated sessions to be able to
see mappings on non-elevated sessions.
> For me, everything works as expected. Drives mapped in batch file on system
> start visible in Explorer without an issue.
Found that when I started using W7 console sessions, net utilities, both MS
and Cygwin nslookup, ping, tracert, etc. could not see the network unless
they were run in elevated sessions, so set up all console sessions to start
elevated. Was that something that happened on early releases and was fixed
later, or some incorrect assumption or setting on my part years ago?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple