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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=FGPXV2KAFsq/h4GiMcfWwpAKof1MqKUsyNzQcQixmTJG0+BUav2SW
	Pq0ECjVacv0t8iP59qVHzZGO+zhrmyKfyBIthkBTA4f1w1aGz4K7yKpf8upg+X/s
	EaAabra/wr20LpbtkYAHQvQT+bbe434dRj2MOPr7mBI+/8JD5o2twQ=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=6+4myhrmtaIqqOXEUGaIBqUy8lU=; b=HeeGfMwtCaMzLWkmRFIg76EO70lj
	n3hEdIQyZ1uDUr2aPS6ddmEosopY/DVsgDJJKUUX1ZZPUyEJSdE+zNRcyrTivEr7
	yKDTG8CglI9uctf1z+auAxUndzPyrnKgCtyIUBBgMYK7U+NJpyk6wW7nFP3oilvc
	j1445BfISQqJCsY=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 7 Apr 2014 11:23:42 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Request for Junctions be treated consistently
Message-ID:	<20140407092342.GF2061@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5336C0DF DOT 5080102 AT tlinx DOT org> <5336C23B DOT 2070309 AT tlinx DOT org> <20140331102745 DOT GD23383 AT calimero DOT vinschen DOT de> <533AEBD6 DOT 3040209 AT tlinx DOT org> <20140402084026 DOT GM2508 AT calimero DOT vinschen DOT de> <533FE56D DOT 5010809 AT tlinx DOT org>
MIME-Version:	1.0
In-Reply-To:	<533FE56D.5010809@tlinx.org>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--Zs/RYxT/hKAHzkfQ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  5 04:13, Linda Walsh wrote:
> Corinna Vinschen wrote:
> >On Apr  1 09:39, Linda Walsh wrote:
> >>If I mount a device using mount vol in 2 different places, will they
> >>have different device numbers the same?
> >
> >The same, just as on Linux.
> ---
> 	Why special case junctions created with 'linkd' to return
> as symlinks but not 'mountvol' if they both suffer from the same
> possibilities of circular mounting?  I.e. creating circular loops
> is no reason for linux to force the 'bind' command to look like
> a 'symlink', but the same conditions exist.  I
> [...]
> -----------------
> >Sorry, but I really don't understand your question here.
> ----
> You said:
> >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.
> ---
> Under similar circumstances, it's not a problem on linux -- they
> are the same device numbers but the above utilities don't loop
> infinitely.

I didn't talked about loops.

> I don't think your original concern is as big a problem as you
> think, as is indicated by the above setup on linux.
>=20
> I.e. is there some other reason to not treat "linkd" mounts
> the same as "mountvol" mounts -- in a manner equivalent to linux's
> 'bind' mounts?
>=20
> I.e. I don't see that that linkd which creates a junction-mount
> point, should be treated as a symlink.  It would provide valuable
> benefit in cygwin terms in being able to setup directories at
> multiple place like 'bind' does on linux, and be resistant to being
> overwritten like symlinks.

Look, directory reparse points are, by and large, symlinks to another,
real directory entry.  The directory has a primary path, which is its
own path under which it has been created, and the reparse point is just
a pointer to this directory.  If that's not a symlink, what is?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--Zs/RYxT/hKAHzkfQ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTQm6eAAoJEPU2Bp2uRE+g1OcP/2VgnPX43bHmdBRK9c+IAmq0
RXNVYy68vFdNq+QBgsI249nl2BO+A/OTupktliylqgE8y2Aaj7o75gOCX8YkIRJ7
8x+Cu+0Z2rabnazLW//hmYmEOz9fvZeROOyKBbcLrxuSboiHTL476VwgMOPHMITH
f9WVmftRYtIySc7ziow79w4r4ICRr+GgpY4vJNtq8pvOsNCYUOZcNRiu5fgDYZ00
xZChSTUSwtgvMXLqM03exwrG6aXzGQKK98762pviMJc3eeSkp4NGYlA9hHdh+MRg
NpIfrVFXgVA47DCgYktSF73LVaCsbqJHpLeVmNh8Z6Bb1HqKcUmszmRqrJuJo/DG
S8tbYk/GbsTwnR8clda6V/9aRQYg8bPkoPMaZ99WgUe432B7xpX5aTL1ZFKzx3H+
X6RTI0o8dO5qbSq9vUzm3NKLyZx3wgm6639Z/tRElVytJmsydu900RmgjPTrFnwR
Q9+eUwwnwYR7r/SeSI3sgfwePPNImAr26S+sGNwrW13slVcvBL23SOBr7Y7+N5sc
CEfav71GvA9ouLjN7rp3Fg+TBVoFKaJfshhI8bs6d0DKnGoM07Ngo7sN6osNphFb
TqlTG4M0bNs5h8IBUU5ChH2payQEHLgx3h23EUn9rL8CNz5lXPesKmhBO4a+ceXG
J7ny8l8eeejFt/y89jT3
=4b3w
-----END PGP SIGNATURE-----

--Zs/RYxT/hKAHzkfQ--

- Raw text -