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=lOjbE8pE6HfR+uUv8kSM76ABY+XFUCiYpSc7E4GlQVfO7gWELgCtu
	xgY59hBM0fNHmOVmCtApvKFMJAqbXx+qbTjtGFPwRGUdgileLxLFvywZpjLVRks+
	dhB63IOC+DCC3bRQkSHAQO2ecB/bSCOjlC81uFNFcte65BYmMCznWA=
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=YrWmKmhKtX5XQgkimXExbIb/e8I=; b=DdO0jhrl42k2lByexOBL+IJFXwPp
	PlAhVdEdWerzsXGx5fMQ0bRj4hOmpYoHZtZJXvy3cK9IBYXssH2sSG1CP6+1Be7e
	JY/eL0GtRYqVcI1a2U6OqvQffPHTcxmjJOobqdMxyWLkIVgMydzb2JnBjNf5HeNA
	tc810YrYkqfm8Jc=
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: Tue, 8 Apr 2014 10:39:55 +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: <20140408083955.GA28755@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> <20140407092342 DOT GF2061 AT calimero DOT vinschen DOT de> <1675705369 DOT 20140407220427 AT yandex DOT ru>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg"
Content-Disposition: inline
In-Reply-To: <1675705369.20140407220427@yandex.ru>
User-Agent: Mutt/1.5.21 (2010-09-15)

--gKMricLos+KVdGMg
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  7 22:04, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>=20
> >> 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.
>=20
> > 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?
>=20
> Uhm, there's two ways to look at it.
> You may call it a "symlink", but in fact, Linux equivalent of a reparse p=
oint
> is a mount --bind, or, perhaps, a block-type device mounted at specific
> directory.

No, it's not.  There's a major difference between mount points and
symlinks, which is, mount points are handled inside the kernel, while
symlinks are filesystem objects.  Reparse points are very certainly
filesystem objects.  And bind mounts in Cygwin are handled in the
"kernel" as well.  We can't add reparse points to the mount table
on the fly.


Corinna

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

--gKMricLos+KVdGMg
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTQ7XbAAoJEPU2Bp2uRE+gPl4P/2FcPAxprbwHRUgysgJW6ZRQ
rFDBSfwwjZSqq4oYLoDMXkrLpxTQH8tClb00aKDBooenTpGMLIdx8DbdHR76hp7R
TRD/8tbWz+pkK77n9emzmzC0J6YqhO4VP/Ij+yW5pHnZDSkXGQCQlQTyYiYeYnYa
AnY9B8cWqEjmE1rwHBOm+Vj/SIyz4UU9ruCFybU1p9OUHY63+3waielaE3BN+KYC
k8HakEs3B7s1QXoQRVWjosnvW7u6xgF1BHQHabhWMAAMKtnnW90HTS25uBwO311X
9J3GbMH7C4xlNZj9/Pxx2jRCcA2NP0d1HS8cous2wpAXjLfMYCYHBJFbcJP99fhl
ERcpvWzavFO8ypw0x4gOv7fYfS803n/NEbv/stxJLuAKUp2sZiDC4+Ef83WgdN7K
MX8crafEXTO3WyAgDzoDfEhFdK0BmsdHsEefxTxG1toq/GtvJDgUbsbP2bfdHqxl
G9o3hsj9v00bJCHfIXpdZSJG6FmwnJ7pmkCijym1gzwvhXVkrL4GSGNX2Q/rmGm/
mLiCrqcD3QQvDa754tJ6iMSoTEUSCqG/ZHcUYZzWXQi+pp/KQLrqR839oTF8FzSL
Ec1DGG71TrQ/Z1HlNdyoF+JbvZ13TJsnNXj/jHPamMQXHPGsxXmTVPYZdLjZpVHI
N49Nfo5S71//rwX/RIiz
=sc3h
-----END PGP SIGNATURE-----

--gKMricLos+KVdGMg--