From: Ed Huott <huott@pinebush.com>
To: tyonkman@elementalsoftware.com (Tom Yonkman)
Cc: gnu-win32@cygnus.com
Subject: Re: UNC path syntax
Date: Tue, 01 Apr 1997 10:31:00 -0000 [thread overview]
Message-ID: <199704011828.NAA00937@sol.pinebush.com> (raw)
In-Reply-To: <34035660.1323@elementalsoftware.com>
In message <34035660.1323@elementalsoftware.com>, Tom Yonkman writes:
> Just started using the gnu-win32 package and wonder if ls and friends
> can handle the UNC path syntax in some way? This would allow access to
> machines in my "Network Neighborhood", as the explorer so quaintly
> puts it.
>
No. Nothing built with cygwin32 can deal with UNC path names. The
cygwin32 approach requires that you map a drive to any remote (network
neighborhood) volumes. Inside the bash shell, a mapped network drive
such as N: can then be referenced using the path "//N". This syntax
can, unfortunately, collide with the most logical choice for
referencing a network share, which would be something like:
"//ComputerName/SharedDrive".
There is a unix-like volume mounting scheme that lets you acces a
drive as a sub-directory (i.e. N: ==> /DriveN) something like the old
DOS "join" command, but this works *only* for apps built with
cygwin32.
Lack of UNC support can be a real drawback if you're dealing in an
environment that uses a mix of both native (Windows) and cygwin32
apps.
<ED>
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-04-01 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-31 14:04 Tom Yonkman
1997-04-01 10:31 ` Ed Huott [this message]
1997-04-02 0:37 ` Jim Balter
1997-04-01 23:23 ` Ed Huott
1997-04-01 23:07 ` Beta 18 timeframe, UNC path support Geoffrey Noer
1997-04-04 16:48 UNC path syntax Mikey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199704011828.NAA00937@sol.pinebush.com \
--to=huott@pinebush.com \
--cc=gnu-win32@cygnus.com \
--cc=tyonkman@elementalsoftware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).