From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: FUSE, symbolic links and special files
Date: Thu, 25 Aug 2016 15:59:00 -0000 [thread overview]
Message-ID: <20160825152127.GL9783@calimero.vinschen.de> (raw)
In-Reply-To: <4a9aecee-42ae-e28d-90b4-2025df7af9ac@secure-endpoints.com>
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
On Aug 25 10:46, Jeffrey Altman wrote:
> On 8/25/2016 9:16 AM, Corinna Vinschen wrote:
> > On Aug 25 09:04, Jeffrey Altman wrote:
> >> On 8/25/2016 8:45 AM, Corinna Vinschen wrote:
> >>> Since when is this RP method available? Unfortunately the above MSDN
> >>> page doesn't tell... Was it already available with Vista? Does anybody
> >>> know?
> >>
> >> #define IO_REPARSE_TAG_NFS
> >>
> >> was added in the Windows 8.0 DDK.
> >
> > Thank you. Too bad, so we have to stick to the EA method to accommodate
> > Vista and W7.
>
> I don't believe there is any restriction from using this tag on Vista or
> Win7. It will be stored on NTFS just as any other Reparse Tag would be.
> NTFS and ReFS will ignore it just as they would on Win8 or Win10.
Sorry, but I don't grok that. Why would I create a reparse point on
NTFS with this value? This RP type would only be interesting if I can
access the information for files on a non-Windows remote filesystem to
indicate special file types.
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.
Or am I missing something?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-25 15:21 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 [this message]
2016-08-25 19:04 ` Jeffrey Altman
2016-08-25 19:41 ` Bill Zissimopoulos
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=20160825152127.GL9783@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).