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=kDNg7CJXrGkRJKwgpfdY0uzF4PX8jIEYQWE8UNnUj4FsD6E8aRoIa
	Y9MPZ/H358hK1LEqYT9hRDFuNyoN9Z6awI4swSiDU3QrEPjeRC1PDrOFZD+X6ttd
	jj5UETcFAUeNdbKBB25enrnDFg3zAJBPxENtD9rxC4hNCX0AwXE+lE=
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=xqlDMa8HKYpBTNxYN3soWQn2zzc=; b=yA6ab5eltFYS8Kgr/3+db2ffTkbv
	qfeC2Tn/AkENBUmrU0iIzrH7lk9l2Qus5ddjYYTUzExGF9+J2ZDiKnJQqd+bElat
	EYLs944lXSdusR5eBQ2IwHwJ2j0JygAfAhniokGcfciyhZOKIq1mEwWPBdL3oj0L
	RA5Z16fVQI4cjic=
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=-106.2 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=hes, he's, H*f:sk:58C1795, H*i:sk:58C1795
X-HELO: drew.franken.de
Date: Thu, 9 Mar 2017 17:41:13 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount
Message-ID: <20170309164113.GC7716@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <58A4741E DOT 5020408 AT gmail DOT com> <20170216092611 DOT GE3889 AT calimero DOT vinschen DOT de> <58B0AA58 DOT 30504 AT tlinx DOT org> <20170228214321 DOT GB13542 AT calimero DOT vinschen DOT de> <58C0D744 DOT 2030005 AT tlinx DOT org> <1599023500 DOT 20170309163724 AT yandex DOT ru> <58C1795B DOT 5010809 AT tlinx DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU"
Content-Disposition: inline
In-Reply-To: <58C1795B.5010809@tlinx.org>
User-Agent: Mutt/1.7.1 (2016-10-04)

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

On Mar  9 07:48, L A Walsh wrote:
> Andrey Repin wrote:
> > I would argue against all junctions being treated blindly.
> > The difference with bind mounts in Linux is that in Linux you don't have
> > the
> > information available within the filesystem itself, and have no other
> > option,
> > than to treat them as regular directories.
> > Only direct volume junctions cause an issue, and this is what should be
> > fixed,
> > if possible, not sidetracked with questionable workarounds.
> ----
> 	Could you describe the benefits of your proposed solution?
>=20
> 	You do know that MS originally called junctions "mountpoints",
> right?  So why would cygwin treating them as such be a "questionable
> workaround"?

He's right.  The mount point handling in Cygwin is based on the
in-memory mount table.  There's no reasonable way to fake some
reparse point to look like a mount point.  We can either handle it
as normal dir, or as symlink.  Handling it as normal dir is=20
problematic in terms of find/rsync etc, bacause the cross-device
check would fail and files are potentially visited multiple times.


Corinna

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

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYwYWpAAoJEPU2Bp2uRE+goBYP+we/pmZlwD0o7rMiZk6vD6jj
R09tLm2UIhH0KtRnjhmAg6iqx+EFszsFoqAOucVai27ne0FtSoTXHzqn0HApYKtR
OBZTjlVqH8TFio2FHBph4aT6cVWnO6AkMpHBZEjJrnC6kdnKQC4MivM27+Kww/MS
ybDxV4JULZj/iEdGBYsQS3wqLWYUyfF4ZGyaG+xKedPS9cEgU0hYjUQtcrm7cAxQ
/ILLAkseWXsEb6rCjKLL6yaliA3CB46SQhVM04GQu1+z4TaCDnTl5/7nqY+uIeZQ
QOqS3dzvPIg0iYgJ2/tIUJkQxxWWIt1QgO/gSvxTNkVB9YRkakUHqyL6j5GeQJGy
4X3QtXpevcz1jva5MniIWeX0vH3ewKSKxyW3HAcX1V3C0RleRiYm3foRGcIIq1VD
PvPJNcN4Mi9D9DOqUBlx/D77h7CnLBCi95OWj2U4bvJNsv3ofgYy8LzhlCrpIY5w
/rxahSiPiAwLgDy0ex9ebiANv1N7MVaqwxIZSF4AOYlAg0UrV8q4+3WzPH3eEug2
V6imWpdJkDvEpZYsFgSvuqmIZv5yOABsZY//jYkh6frWVdUjat3soT0D3lutXuO3
taiIG6dkn8WStV080lGAMCGLwrz61pc0149ZSGkWNfrWdy6dheolLP94FFYk16Ai
ON55VdVg5AD9j3mA4mmH
=PZAV
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--