From: Bill Zissimopoulos <billziss@navimatics.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: FUSE, symbolic links and special files
Date: Thu, 25 Aug 2016 19:41:00 -0000 [thread overview]
Message-ID: <D3E51C0E.AFAC%billziss@navimatics.com> (raw)
In-Reply-To: <223d291e-689f-15f8-cca2-efbe972e123c@secure-endpoints.com>
On 8/25/16, 7:14 PM, Jeffrey Altman wrote:
>On 8/25/2016 11:21 AM, Corinna Vinschen wrote:
>>Granted, it *could* be used by Cygwin on NTFS to indicate Cygwin's own
>> implementations of AF_LOCAL sockets or fifos. Or even for symlinks.
>> But that would only introduce YA symlink type which would be unusable
>> from non-Cygwin applications.
>
>Correct.
>
>With its own reparse tag Cygwin could store exactly the same metadata it
>stores today in the data stream of the .lnk file as reparse tag data.
>The benefit of applying a reparse tag is that the .lnk will no longer be
>confused for a regular file. On file systems that do not support
>reparse points it can continue to store the data in the data stream.
I agree with Jeffrey, and I did think of this as a potential solution for
FUSE for Cygwin (and perhaps Cygwin itself).
But since I learned about the NFS reparse points I find them a very good
solution, especially because they indicate that someone in Microsoft has
already thought about this problem.
Bill
next prev parent reply other threads:[~2016-08-25 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 12:49 Bill Zissimopoulos
2016-08-25 13:04 ` Corinna Vinschen
2016-08-25 13:38 ` Jeffrey Altman
2016-08-25 13:54 ` Corinna Vinschen
2016-08-25 14:52 ` Jeffrey Altman
2016-08-25 15:59 ` Corinna Vinschen
2016-08-25 19:04 ` Jeffrey Altman
2016-08-25 19:41 ` Bill Zissimopoulos [this message]
2016-08-25 21:15 ` Bill Zissimopoulos
2016-08-25 19:15 ` Bill Zissimopoulos
2016-08-26 10:25 ` Corinna Vinschen
2016-08-26 14:35 ` Bill Zissimopoulos
2016-09-20 22:02 ` Bill Zissimopoulos
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=D3E51C0E.AFAC%billziss@navimatics.com \
--to=billziss@navimatics.com \
--cc=cygwin@cygwin.com \
/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).