From: "Simon Liesenfeld via cygwin" <cygwin@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: symbolic links on Paragon Linux File systems
Date: Mon, 17 Dec 2018 08:11:00 -0000 [thread overview]
Message-ID: <1823593702.5343751.1545034298027@mail.yahoo.com> (raw)
In-Reply-To: <1823593702.5343751.1545034298027.ref@mail.yahoo.com>
Hi all
There is a commercial ext3-4 file system driver for windowsLinux File Systems für 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
$ echo hallo > source
$ ln -s source sl
$ cat sl
!<symlink>▒▒source
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2018-12-17 8:11 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 [this message]
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
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=1823593702.5343751.1545034298027@mail.yahoo.com \
--to=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).