This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [ITP] FUSE 2.8
- From: Bill Zissimopoulos <billziss at navimatics dot com>
- To: "cygwin-apps at cygwin dot com" <cygwin-apps at cygwin dot com>
- Date: Tue, 6 Sep 2016 21:14:57 +0000
- Subject: Re: [ITP] FUSE 2.8
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=billziss at navimatics dot com;
- References: <D3BF7FAD.A9C3%billziss@navimatics.com> <579A4102.9040406@maxrnd.com> <D3BFA5AD.AA0D%billziss@navimatics.com> <20160728200435.GG26311@calimero.vinschen.de> <D3BFC46B.AA41%billziss@navimatics.com> <20160729085141.GK26311@calimero.vinschen.de> <20160817091433.zksukafls6mkk52u@calimero.vinschen.de> <Pine.BSF.4.63.1608220229040.94028@m0.truegem.net> <D3E48B5F.AE86%billziss@navimatics.com> <57CD3C7A.1000902@maxrnd.com> <CAFUnBZi6Rsabd=KMPtifb7V42PAnU4aL+QoqG0rXw_X6im1KZw@mail.gmail.com> <57CDD2A6.8010008@maxrnd.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 9/5/16, 1:16 PM, Mark Geisert wrote:
>Adrien JUND wrote:
>>> Separate from that, it's been a little work disentangling the meaning
>>>of various names used for this project. Here's what I think the names
>>>mean:
>>>
>>> FUSE - a protocol, which exists in different versions
>>> WinFSP - a Windows-native DLL mapping FUSE 2.8 ops to/from Windows
>>>file ops
>>> cygfuse - a Cygwin DLL allowing Cygwin SSHFS and FUSEPY to use WinFSP
>>>
>>> If that's correct, I'd like to regularize the names of things in the
>>>proposed cygfuse package to accurately reflect their meaning. E.g.,
>>>change fuse.cygport to cygfuse.cygport, etc. The doc inside some files
>>>might need updating.
>>
>> About cygfuse description, does the goal of cygfuse is not to wrappe
>> FUSE API for user land file systems like Dokan, WinFSP, CBFS, and
>> others ?
>>
>> I have tried to see how to integrate Dokan in cygfuse and it is
>> currently hard linked to WinFSP and makes hard the integration for
>> others FS.
>> A neutral interface with common operations should be made to fix the
>>situation.
>
>I believe all interested parties have agreed we want to support multiple
>FUSE
>implementations. cygfuse is intended to be the connector between a FUSE
>implementation and Cygwin versions of FUSE apps like SSHFS and FUSEPY.
>The idea
>was to allow different FUSE implementations (e.g., WinFSP, Dokan, etc)
>under the
>hood without having to modify the Cygwin level apps SSHFS, FUSEPY, etc to
>match.
>
>As currently implemented, cygfuse is hardwired to work with WinFSP.
>That's only
>a consequence of cygfuse having been provided by WinFSP's author. The
>plan is
>to extend cygfuse so that it can support multiple FUSE implementations of
>which
>one is selected at runtime.
>
>Currently, if WinFSP is installed on the system (determined by the
>existence of
>a particular registry key) then cygfuse attaches to the WinFSP DLL. This
>code
>needs to be extended to check whether Dokan is installed (determined by
>some
>mechanism TBD) and then attach to Dokan's DLL. And so on for other
>future
>implementations.
>
>I'm trying to get my understanding of the pieces and naming correct in
>order to
>modify the cygfuse code to be more generic and less tied to WinFSP.
Mark, thank you. I agree with everything you said.
Bill