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=IpS3rIxliL1k+8quUnJyjSfrY+WEOPMli/i2YzBZXPrYZuqrtbRj7
	tFOTTEKPohfv974ontsrUyXv4UHqVKi7l7ttLZccdk8q3EM5ctsu9Ghc7lNv5uhE
	WSYESEYuSo1TgI5G/rnrksQvmkgcWkbv5CfTPyDDKsMr0/iqmDvyRo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 1 Apr 2019 15:31:49 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin vs. Native Symlinks
Message-ID: <20190401133149.GL3337@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <804XDamMs8784Set DOT 1554122358 AT web03 DOT cms DOT usa DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="ELVYuRnMxQ5nnKRy"
Content-Disposition: inline
In-Reply-To: <804XDamMs8784Set.1554122358@web03.cms.usa.net>
User-Agent: Mutt/1.11.3 (2019-02-01)

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

On Apr  1 07:39, KARL BOTTS wrote:
>=20
> Corinna said:
>=20
> > ... Which lets symlinking with nativestrict fail. "winsymlinks:native"
> > will work, albeit creating a Cygwin symlink then.
>=20
>=20
> I use "winsymlinks:native".  Is there a tool or method with which I can
> create a Cygwin symlink by force?

$ CYGWIN=3D"" ln -s ...

> (I doubt I would actually want to:

Depends on if creating a symlink to a non-existant target is important
in your scenarios.  Just run with "winsymlinks:nativestrict" for a while
to find out.

> I just want to know if I can, and to test behavior of a Cygwin symlink.)
>=20
> Is there a tool which will tell me whether a given symlink is Cygwin or
> native?

Not a single tool, but a few simple checks:

- `ls -l' shows a symlink
- `attrib /l' shows the S bit being set (cygwin symlink) or not
- `cmd /c dir' will not show a cygwin symlink as symlink

> (The output of both readlink and symlinks looks the same, regardless.)

That's the idea of a transparent POSIX layer, the API hiding
the implementation details :)


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyiEsUACgkQ9TYGna5E
T6ALBg//fJ30aFMn4IFoue5I/FyDuvufFy3sQcnuXFnatZzESQzUrCEe4bddiivT
qUerrNnbzV3GU2Zn507u6T7MClPkoDaku779EXjHPlqHChsGGHZ8jyXEBvC6mu4y
A0iSwFne6nNlbq/Shhw0d8lVel9UjfP+9Q2WGNHYs5NFHl7LX/Ji7ukWb86RZEKE
XEXLAcadRuhTNG+UF7NsTZxIRE5VIDdTHBzHuTnkyBQaLzRPC2xTfdHXJ2wn9Rzo
zgPKdauMBNswkNJ/iL6wPAIzsI+iw/CJ1IzrYiMZmwUztuHZa593JuyFxR5isZs3
6hE9ISBOBMQaIMWwr1fVgE14/cG7wMK+ullC+Pry3KNQLj/fVBeOlceFyB0q1U8T
nQfih3/1DcQFhpfZKI052MUKEtv/m7FR/2jWXmeXW5uTcKyqTTPwomDcvlOrPflL
xdslcILy9irQ1NuCgqMM8owni14YIOPVVZhG3NMf3X08jEySxjfqeqKDzMTG0yRL
WwIwT8KWiq0mIm8z52x4SdIVfUPwh32Rt2/KjXYPkArKJaTOEMUPdMNWnHs7H6lo
Y56QTz7whRulL3T/xd/lsdcoW0Sj5nsXCpiCReiUYR6fsU1fkCWwYeO89sipe6RD
hCWGIl22m9boDCsaYWdXFRKD7QC5BV5fSxojVXNEC4SBnh2ZJJQ=
=XbTt
-----END PGP SIGNATURE-----

--ELVYuRnMxQ5nnKRy--