From: Adrien JUND <liryna.stark@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] FUSE 2.8
Date: Mon, 05 Sep 2016 11:20:00 -0000 [thread overview]
Message-ID: <CAFUnBZi6Rsabd=KMPtifb7V42PAnU4aL+QoqG0rXw_X6im1KZw@mail.gmail.com> (raw)
In-Reply-To: <57CD3C7A.1000902@maxrnd.com>
> 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.
next prev parent reply other threads:[~2016-09-05 11:20 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 11:59 Adrien JUND
2016-07-22 17:55 ` Bill Zissimopoulos
2016-07-22 19:56 ` Adrien JUND
2016-07-23 0:23 ` Bill Zissimopoulos
2016-07-23 10:40 ` Corinna Vinschen
2016-07-23 16:44 ` Bill Zissimopoulos
2016-07-23 17:48 ` Corinna Vinschen
2016-07-23 18:34 ` Bill Zissimopoulos
2016-07-25 7:35 ` Corinna Vinschen
2016-07-25 21:20 ` Bill Zissimopoulos
2016-07-26 6:28 ` Mark Geisert
2016-07-26 8:45 ` Herbert Stocker
2016-07-26 12:40 ` Adrien JUND
2016-07-26 18:13 ` Mark Geisert
2016-07-26 18:41 ` Bill Zissimopoulos
2016-07-26 17:23 ` Bill Zissimopoulos
2016-07-26 18:38 ` Bill Zissimopoulos
2016-07-26 19:02 ` Mark Geisert
2016-07-26 19:10 ` Bill Zissimopoulos
2016-07-26 23:22 ` Bill Zissimopoulos
2016-07-27 9:03 ` Mark Geisert
2016-07-27 17:45 ` Bill Zissimopoulos
2016-07-28 9:17 ` Mark Geisert
2016-07-28 16:36 ` Bill Zissimopoulos
2016-07-28 17:29 ` Mark Geisert
2016-07-28 17:43 ` Bill Zissimopoulos
2016-07-28 19:14 ` Bill Zissimopoulos
2016-07-28 19:21 ` Bill Zissimopoulos
2016-07-28 19:59 ` Mark Geisert
2016-07-28 20:08 ` Corinna Vinschen
2016-07-28 20:04 ` Corinna Vinschen
2016-07-28 21:18 ` Bill Zissimopoulos
2016-07-29 0:05 ` Mark Geisert
2016-07-29 0:17 ` Bill Zissimopoulos
2016-07-29 0:27 ` Bill Zissimopoulos
2016-07-29 8:19 ` Mark Geisert
2016-07-29 8:51 ` Corinna Vinschen
2016-07-29 9:15 ` Mark Geisert
2016-07-29 9:48 ` Corinna Vinschen
2016-08-16 17:32 ` Corinna Vinschen
2016-08-17 8:27 ` Mark Geisert
2016-08-17 9:14 ` Corinna Vinschen
2016-08-22 9:43 ` Mark Geisert
2016-08-22 11:54 ` Corinna Vinschen
2016-08-25 8:49 ` Bill Zissimopoulos
2016-09-05 9:36 ` Mark Geisert
2016-09-05 11:20 ` Adrien JUND [this message]
2016-09-05 20:16 ` Mark Geisert
2016-09-06 21:15 ` Bill Zissimopoulos
2016-09-07 5:22 ` Herbert Stocker
2016-09-08 8:13 ` Mark Geisert
2016-09-06 22:07 ` Mark Geisert
2016-09-08 8:03 ` cygfuse (was Re: [ITP] FUSE 2.8) Mark Geisert
2016-09-20 21:12 ` Bill Zissimopoulos
2016-09-21 5:33 ` cygfuse Mark Geisert
2016-09-21 6:01 ` cygfuse Bill Zissimopoulos
2016-09-21 6:13 ` cygfuse (was Re: [ITP] FUSE 2.8) Adrien JUND
2016-09-06 21:13 ` [ITP] FUSE 2.8 Bill Zissimopoulos
2016-09-08 12:01 ` Corinna Vinschen
2016-09-08 16:58 ` Bill Zissimopoulos
2016-08-25 8:58 ` Bill Zissimopoulos
2016-07-29 15:35 ` Bill Zissimopoulos
2016-07-29 18:35 ` Mark Geisert
2016-07-29 7:50 ` Bill Zissimopoulos
2016-07-29 8:02 ` Mark Geisert
2016-07-26 20:07 ` Adrien JUND
2016-07-26 20:56 ` Bill Zissimopoulos
-- strict thread matches above, loose matches on Subject: below --
2016-07-17 1:03 Bill Zissimopoulos
2016-07-17 15:43 ` David Stacey
2016-07-17 21:18 ` Marco Atzeri
2016-07-18 19:15 ` Bill Zissimopoulos
2016-07-18 8:19 ` Corinna Vinschen
2016-07-18 19:43 ` Bill Zissimopoulos
2016-07-18 19:52 ` Bill Zissimopoulos
2016-07-19 9:41 ` Corinna Vinschen
2016-07-19 17:27 ` Bill Zissimopoulos
2016-07-20 8:52 ` Corinna Vinschen
2016-07-21 22:12 ` Bill Zissimopoulos
2016-07-22 7:59 ` Corinna Vinschen
2016-07-22 12:30 ` Adrien JUND
2016-07-22 12:53 ` Marco Atzeri
2016-07-22 13:41 ` Corinna Vinschen
2016-07-22 17:58 ` Bill Zissimopoulos
2016-07-22 19:58 ` Marco Atzeri
2016-07-23 0:31 ` Bill Zissimopoulos
2016-07-23 6:02 ` Marco Atzeri
2016-07-23 6:33 ` Bill Zissimopoulos
2016-07-22 17:55 ` 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='CAFUnBZi6Rsabd=KMPtifb7V42PAnU4aL+QoqG0rXw_X6im1KZw@mail.gmail.com' \
--to=liryna.stark@gmail.com \
--cc=cygwin-apps@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).