X-Recipient: archive-cygwin AT delorie DOT com
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=LERbpcQHFixOsGnlT8QYYK0/fauDPN13kPdSCwdw7A1
	Zgp06MmUm5hlw8jwyGDmJEqVoLS/pBkOUxQBoKcpjEL11brcmghuaUAbC8hcn3Vl
	7TorQT1KkjEPBPwo5BNGRVDcY0n7Hc+8bVpOeVjqI26jcJKrvFxZk1Q3T9nypVMU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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;
	 s=default; bh=pBQmuziderZsPkpkgNRRs5vMkpM=; b=nK4KPEDtWVwIIZqVv
	j+1840AFPdtnkinBXVEWc9ofRlGlmIss56KTs8Q5oFXfipno7T67tK/P8LkYTyaP
	1pKpoSXuOCQWe12UiAvSNGMSGhmiHywAgvlyaibAuYnQDTEpcY2cmFdoprJtR7fI
	45vHZ27a3z2EOhTgh024j/N6Yg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: Ishtar.tlinx.org
Message-ID: <533AEBD6.3040209@tlinx.org>
Date: Tue, 01 Apr 2014 09:39:50 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Request for Junctions be treated consistently
References: <5336C0DF DOT 5080102 AT tlinx DOT org> <5336C23B DOT 2070309 AT tlinx DOT org> <20140331102745 DOT GD23383 AT calimero DOT vinschen DOT de>
In-Reply-To: <20140331102745.GD23383@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Corinna Vinschen wrote:
> On Mar 29 05:53, Linda Walsh wrote:
>> Linda Walsh wrote:
>>> If you use the 'mountvol' you a *local* root folder
>>> mounted at some drive letter that can be maintained over
>>> boots. is listed as a JUNCTION and treated by cygwin
>>> as a regular dir.
>>>
>>> For some reason the other type of directory hookup made
>>> by "linkd" which also created a JUNKTION
>>> vs. (mklink creating a SYMLINK or SYMLINKD) is shown
>>> as a soft-pointer .
>> ---- hit send instead of save...Sigh...
>>
>> What I would like to see is restoring the native
>> directory look to 'linkd' so that it could be use as
>> a weaker sybling of linux's 'bind' command. Since there is no way to
>> namespaces or have symlinks
>> honored with out this, I would really be beneficial to not have
>> those lumped in with SYMLINKs, as they are really JUNCTIONS.
>>
>> So could it be seen by cygwin as a dir and not a symlink.
>>
>> Ideal cygwin would be able to tell there was a 'mount' there, but
>> symlinks are just walked all over these days..
> 
> If you create a directory junction to an existing dir and treat it as
> directory, the directory shows up twice under the same device number.
> Find or tar will enumerate (and archive) the dir twice.
> 
> A mount junction is typically used to mount devices.  The mount point
> will be visible because the device number changes at the mount dir.
----
If I mount a device using mount vol in 2 different places, will they
have different device numbers the same?

I.e. fallback position is to use a small partition for common elements
and mount it multiple times in the hierarchy.

Seems like mounting the same vol on a subdir of itself would cause
a look if the device number doesn't change -- but not sure why the
device number would change.???

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