From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: cygwin@cygwin.com
Subject: Re: FUSE, symbolic links and special files
Date: Thu, 25 Aug 2016 14:52:00 -0000 [thread overview]
Message-ID: <4a9aecee-42ae-e28d-90b4-2025df7af9ac@secure-endpoints.com> (raw)
In-Reply-To: <20160825131647.GH9783@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
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.
The only file system for which this tag is known to be interpreted is
the Microsoft NFS provider that will report its
FILE_REMOTE_PROTOCOL_INFORMATION.Protocol
value as
#define WNNC_NET_MS_NFS 0x00420000
Jeffrey Altman
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4349 bytes --]
next prev parent reply other threads:[~2016-08-25 14:47 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 [this message]
2016-08-25 15:59 ` Corinna Vinschen
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=4a9aecee-42ae-e28d-90b4-2025df7af9ac@secure-endpoints.com \
--to=jaltman@secure-endpoints.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).