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 21:15:00 -0000 [thread overview]
Message-ID: <D3E51E18.AFC0%billziss@navimatics.com> (raw)
In-Reply-To: <4a9aecee-42ae-e28d-90b4-2025df7af9ac@secure-endpoints.com>
On 8/25/16, 5:46 PM, Jeffrey Altman wrote:
>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
I missed this. Jeffrey do you have a pointer for this information?
Bill
next prev parent reply other threads:[~2016-08-25 19:15 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
2016-08-25 21:15 ` Bill Zissimopoulos [this message]
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=D3E51E18.AFC0%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).