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=F9XyLSGtFUEFnYgLaWXgDv5jC82bOkYfcoNIYxjdM21Yr8ZfHRdtf
	MSB8YYZqGE7TkDTZ84WIw5r/dvy/P0vw+1KykBZ/cUNnhVFR0umeQWEslI5heIby
	EHaLOBECCxTTV/66LgpIZPr9Pyx+woGYPY5mUX/jyK3aXqgkvADrFQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 12 Mar 2017 12:15:18 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Junctions != Symlinks; Treat Junctions as MS-FS mounts; MS-symlinks are symlinks
Message-ID: <20170312111518.GD3340@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <58C31431.1020408@tlinx.org> <5110401945.20170311210154@yandex.ru> <58C48EF9.4050106@tlinx.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN"
Content-Disposition: inline
In-Reply-To: <58C48EF9.4050106@tlinx.org>
User-Agent: Mutt/1.7.1 (2016-10-04)

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

On Mar 11 15:57, L A Walsh wrote:
> Andrey Repin wrote:
> > Greetings, L A Walsh!
> > >     You say that throwing out the MS-designed ability
> > > to mount a filesystem subtree and treat them the same as another
> > > feature they added, "symlinks", is a benefit?
> >=20
> > Where did I said that?
> ---
> 	Are you not suggesting treating JUNCTIONs the same
> as SYMLINKs and treating them *both* as 'symlinks' in Cygwin?
>=20
>=20
> > >     They added symlinks in Vista to create a feature,
> > > similar to *nix symlinks.  I don't see how throwing out mount
> > > points is anything but a BUG -- a removal of a useful feature.
> >=20
> > You're insinuating.
> ---
> 	Please clarify -- but it seems you want to
> disregard the differences between JUNCTIONs and SYMLINK[D]s.
> Is that not so?  How is that insinuating?
>=20
>=20
> > That's a reason for bug reporting.
> ---
> 	I have brought it up before.  It is considered
> standard for some installers to check where they are being
> installed.  As near as I can tell it's cygwin treating JUNCTIONs
> as *nix "symlinks" that is the problem -- thus my request that
> JUNCTIONs not be treated identically as Win SYMLINKs.
>=20
>=20
>=20
> > We're not talking Linux or VirtualBox issues here, do we?
> ---
> 	I'm, talking parallel features and parallel problems.
> Installing products on Linux or cygwin may check for and
> complain about symlinks leading to their installation directory.
>=20
> 	The cure in both is to use bind-type mounts and
> remove any symlink usage in their base path.

As I wrote (multiple times now?), we can handle dir junctions as
symlinks or as normal directories.  We can not handle them as mounts or
bind mounts, unless you do this explicaitly in /etc/fstab or
/etc/fstab.d/$USER


Corinna

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

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

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

iQIcBAEBCAAGBQJYxS3FAAoJEPU2Bp2uRE+gxkkQAIz+hefUduihdvFTsbSAuqk5
o7cUqTkr7C/AQPbobERNv0NhHi5uYoH6x0CFqRaTIux7D0g1MT1/0xZcd2KQr8pH
/fkxz3N/MuMnRfuo19MwKWZ7svERLIU5oX7c79N3UWc1JS3NFG319X0nJ81BNq9G
9da8xd5GbVAEMaRKLvhU9p9x4c8IX0mfoR9UyfXiiNtdvFMh3paeDW5RIWPRfENQ
KbINF3+nS7XBsWmbR/9sHd49uAGQYcVmcyMmrqLPf/4nCvTTMIY4asLmxywdBpZ6
Fo7TtaJf2f6koYCDa4vo2t3Q6a6IHHxzeMfnGJiWps8rDTIfupIh428Wn/zDURP7
FhkF2p9axqDw45ThRYQF9cGKP2d98O/u0PlBb9SVRpWKkxySiayAdeTv0MyTmmyO
Gf2V0hWnf0jjUB36/p4NxXATWej+fZABa4+dv2JkDnaCyCGwELCGT3mcDAj1zbGc
++ZFg5mrfJMbcfXTe+6IV8MeZHMvU4p3zjmtmRoPp9Wp5TiGwQIO33uXHjKuYvxB
gKIsAl9a12+E4soBCXSPx2tIhYRMqnUJ2fSAl5W6XZuzbOFq4jdoNq544+HrRO1p
QThQ2rk8Ntg3JYEbDWaTWhRdAUiLkqvHH767V+9ahgAAJSuzu4PxZGJ7Lu0EFYJP
pAEujjoQEsRXOzt9vHDe
=qElu
-----END PGP SIGNATURE-----

--J/dobhs11T7y2rNN--