From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cannot access volumes mounted with 'mklink /d' which point to a volume UUID
Date: Thu, 16 Feb 2017 09:26:00 -0000 [thread overview]
Message-ID: <20170216092611.GE3889@calimero.vinschen.de> (raw)
In-Reply-To: <58A4741E.5020408@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On Feb 15 07:30, Matt D. wrote:
> On Windows you can create symbolic links which point to volume UUIDs as a
> way of mounting and unmounting them without having to use the administrative
> disk management tools.
>
> For example, in cmd:
>
> mountvol
> ...
> \\?\Volume{079b79c9-0000-0000-0000-100000000000}\
> C:\
> ...
> mklink /d test \\?\Volume{079b79c9-0000-0000-0000-100000000000}\
> ...
> dir test
>
> I call mounvol to get a list of volumes and create a symbolic link 'test'
> which points to the C:\ UUID. When I then 'dir test' it will list all files
> on that volume.
>
> If I try to access it through Cygwin Bash I get the following error:
>
> $ dir test/
> dir: cannot access 'test/': No such file or directory
>
> This makes it difficult to work with unmounted volumes as it's not always
> possible to access the administrative disk management snap-in and the
> mountvol/mklink has always been my go-to for this type of functionality. It
> would be great if Cygwin would support it.
This type of directory symlink to a GUID volume path isn't supported
at all yet in Cygwin. However, you can access the directory directly
without having to go through MKLINK. In Cygwin:
$ cd /proc/sys/GLOBAL\?\?/Volume{079b79c9-0000-0000-0000-100000000000}/
or
$ ln -s \
/proc/sys/GLOBAL\?\?/Volume\{079b79c9-0000-0000-0000-100000000000}/ \
my_vol
$ cd my_vol
Note the trailing slash. Volume{079b79c9-0000-0000-0000-100000000000}
without the slash is the block device.
Volume{079b79c9-0000-0000-0000-100000000000}/ with trailing slash is the
filesystem on the block device.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-16 9:26 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 [this message]
2017-02-24 21:49 ` L. A. Walsh
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=20170216092611.GE3889@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).