From: "L. A. Walsh" <cygwin@tlinx.org>
To: cygwin@cygwin.com
Cc: codespunk+cygwin@gmail.com
Subject: Re: Cannot access volumes mounted with 'mklink /d' which point to a volume UUID
Date: Fri, 24 Feb 2017 21:49:00 -0000 [thread overview]
Message-ID: <58B0AA58.30504@tlinx.org> (raw)
In-Reply-To: <20170216092611.GE3889@calimero.vinschen.de>
Corinna Vinschen wrote:
> This type of directory symlink to a GUID volume path isn't supported
> at all yet in Cygwin.
As I mentioned, symlinks don't support volume destinations
under windows, but Junctions should be used instead. They
half-way work under Cygwin (junctions to volumes look like
mounted file systems look under linux, but junctions to
pathnames get converted by cygwin to symlinks -- losing
information when such junctions are restored.
Corinna -- could you _please_ re-look at supporting both
types of junctions as mount points? Then Cygwin could have
"mount-parity" with linux! ;-)
Thanks!
--
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
next prev parent reply other threads:[~2017-02-24 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 15:30 Matt D.
2017-02-16 0:59 ` L. A. Walsh
2017-02-16 9:26 ` Corinna Vinschen
2017-02-24 21:49 ` L. A. Walsh [this message]
2017-02-28 21:43 ` Corinna Vinschen
2017-03-02 21:43 ` showing all JUNCTIONS as normal dirs as w/linux --bind (was Re: Cannot access volumes mounted with 'mklink...) L. A. Walsh
2017-03-09 4:17 ` Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount L. A. Walsh
2017-03-09 13:50 ` Andrey Repin
2017-03-09 15:48 ` L A Walsh
2017-03-09 16:41 ` Corinna Vinschen
2017-03-09 19:13 ` L A Walsh
2017-03-10 13:20 ` Andrey Repin
2017-02-16 14:05 ` Cannot access volumes mounted with 'mklink /d' which point to a volume UUID Andrey Repin
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=58B0AA58.30504@tlinx.org \
--to=cygwin@tlinx.org \
--cc=codespunk+cygwin@gmail.com \
--cc=cygwin@cygwin.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).