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=tb4xX8+epBTjybw+8oqTWiGxxJO6MuClBivkPvGXSjgW4M+fZbdFG
	XjZZ/ufZqlVwA2Jojxo5xui/2DdopwdBMDCrlpRFuMoO/lINk95yneVAc5KpQil2
	45wnxW5DZtDGLKJUqh8CwodS7b8FYj932+KUnLM3KP8UQdRQGS09YI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 17 Dec 2018 10:34:28 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: symbolic links on Paragon Linux File systems
Message-ID: <20181217093428.GQ28727@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <1823593702.5343751.1545034298027.ref@mail.yahoo.com> <1823593702.5343751.1545034298027@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="FUaywKC54iCcLzqT"
Content-Disposition: inline
In-Reply-To: <1823593702.5343751.1545034298027@mail.yahoo.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

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

On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> Hi all
>=20
> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems f=C3=BCr Windows | Paragon Softwarewhich enable Windows to read an
> write on native ext3-4 volumes.In General cygwin works perfectly on
> such volumes,even named pipes work,
> but Cygwin programs do not interprete those links correctly,which are
> created on such volumes.whilst symbolic links on native NTFS drives
> referring files on such volumeswork perfectly.
> $pwd/cygdrive/e
>=20
> $ echo hallo > source
>=20
> $ ln -s source sl
>=20
> $ cat sl
> !<symlink>=E2=96=92=E2=96=92source

Yes, we can't do that without special knowledge of the FS.  The default
symlinks on Cygwin are only evaluated correctly if the DOS SYSTEM
attribute is set.  The ext4 driver can't do that, obviously.

Are the native symlinks on an ext4 FS converted to NTFS symlinks
on the fly by the driver?  Are they visible as symlinks in Windows
or Cygwin?

If so, you could try setting the environment variable CYGWIN to contain
"winsymlinks:native".  This creates native Windows symlinks rather than
the special Cygwin POSIX symlinks.  If the driver is handling this
correctly, it should transparently convert them to ext4 symlinks and
they should just work.


HTH,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlwXbaQACgkQ9TYGna5E
T6Cx9Q//Z78pirgrQ0CsWy+fSxEK/YKP77yw89V9YBlXxosuK6GtF750fKNvmHUf
EVxSCsj2Et3yDuhTphJCO8IDh055lCMyNzuA+Q9YC1jg08TWBAMgZoQ9zjPobMHx
BQ8H3y+1PM5dtQlRHxF9Cd9VU+T9IxxXbhWGiT8cH6HTKaUpJB67bpveWG2q5BXj
FG5VwVl/BrQQfM0fI74aJZQ15MU58BmdVRK2mS9bs94yyH6iCW6+COTwlrA7o5Mc
9Bn0zb5g4RAYSk33XH+IDeiifPXv9Sufnu4mYBy2PxeU+VICb0fDbk2mX9bAS6mb
ggxZ0fy8XuxkeYIhdwsdBZoVa8L5MB8aKqZC8WferDfDNRhFNymHvuphOJ6epIB4
NBvTfLqDv/PzHGrONnXGHela1YhCIJQd9WOLsplRNq+dKUFfvH1BqmvjEqivSx3i
BdYu5bvtaGjj6B16LOoQhRiel10pxP1UybZx/6XfXDngH4D9LEPgUMCRSQkKQTBR
eGUCjQ7DGtdQtQ3Y/Gij6VTXdklCCxCpywbaUkTdoB8YWRoy6MGL2qgnIEtLYB67
SAc8gpdAm6TILLqJsBuSS80kwkWDZLlwfJyI8EnmLn36DfnKrGzbq8jmh8lfXHyy
JKdXJNjYjfqPjPoVEvcAwJx3z2fOKRJ7l2QXcRwSrLhK1x4lmbo=
=S4xg
-----END PGP SIGNATURE-----

--FUaywKC54iCcLzqT--