From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Simon Liesenfeld <surgeonde@yahoo.de>
Subject: Re: symbolic links on Paragon Linux File systems
Date: Mon, 17 Dec 2018 19:38:00 -0000 [thread overview]
Message-ID: <20181217192223.GC28727@calimero.vinschen.de> (raw)
In-Reply-To: <768216656.5669803.1545072652503@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Please, do not top-post.
On Dec 17 18:50, Simon Liesenfeld via cygwin wrote:
> Hi Corinna,
> since you answered your own questionsI can better understand my own
> stupidity.I have created now a hard and a soft link with a native
> linux,then I booted Windows, started the paragon driver,then cygwin
> programs as well as any dos program perfectly understood the links.
Not in my testing. I installed the Paragon trial driver and tested
on a filesystem with files and symlinks created by native Linux. The
symlinks are not understood at all. From the Windows perspective they
are just plain files with the name of the target file as content.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-17 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1823593702.5343751.1545034298027.ref@mail.yahoo.com>
2018-12-17 8:11 ` Simon Liesenfeld via cygwin
2018-12-17 9:34 ` Corinna Vinschen
2018-12-17 9:41 ` Corinna Vinschen
2018-12-17 18:45 ` Corinna Vinschen
2018-12-17 18:47 ` Stefan Baur
2018-12-17 18:50 ` Stefan Baur
2018-12-17 19:22 ` Simon Liesenfeld via cygwin
2018-12-17 19:38 ` Corinna Vinschen [this message]
2018-12-17 20:50 ` Simon Liesenfeld via cygwin
2018-12-17 11:35 ` Andrey Repin
2018-12-17 12:04 ` Simon Liesenfeld via cygwin
2018-12-17 12:17 ` Corinna Vinschen
[not found] ` <1283756633.5566453.1545061591859@mail.yahoo.com>
2018-12-17 16:35 ` Simon Liesenfeld via cygwin
2018-12-17 16:57 ` Simon Liesenfeld via cygwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181217192223.GC28727@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=surgeonde@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).