DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Oj6mvyIFsBMORgWIcWx1xn4YhSY08PrdzpDgpJRqjlv
	MdGyLzNVM8jl7m91rtGb334zwElkqgM16rSJsWP+QuOrjqImgK5+COlWZKNyfCqj
	nTe7je7w7vcvT0CwiLXAJheTQnWi0kiF2p6pJNpOrePlVsPYX5+bb2xBpblP23lM
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <58A4F95F.1000907@tlinx.org>
Date: Wed, 15 Feb 2017 16:59:11 -0800
From: "L. A. Walsh" <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cannot access volumes mounted with 'mklink /d' which point to a volume UUID
References: <58A4741E DOT 5020408 AT gmail DOT com>
In-Reply-To: <58A4741E.5020408@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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}\
---
    mklink and mklink /d create SYMLINKs (and SYMLINKDs).  To create
MS mount points you need to create them as junctions (mklink /J) and
I think that should work for what you are doing.

    Unfortunately, cygwin breaks MS-mounts by treating them as symlinks,
so if you use standard *nix utils to copy that dir, it won't be read as a
dir, but as a symlink, so when it's written to a destination, it seems like
it would attempt to overwrite the directory with a symlink. 

    I know it messes up being able to keep cygwin dirs on a separate disk
unless you _only_ store 1 cygwin-dir/mount point.

    For example, if you have a cygwin on a "D" drive, you won't be
able to use junctions to mount D:/usr on /usr and D:/bin on /bin without
cygwin destroying the mountpoints when software is installed. 

    Very unfortunate, since linux DOES have the dynamic-mount points
with its 'bind' options.

    Somehow, having users be able to destroy mount-points doesn't seem
that secure.


--
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