On 9/20/16, 10:33 PM, Mark Geisert wrote:
>On Tue, 20 Sep 2016, Bill Zissimopoulos wrote:
>> Mark, has there been any additional progress on this?
>
>No activity. I was not expecting Dokany to be fully integrated before
>ITPing cygfuse, but I had hoped to hear at least that
On 9/8/16, 1:03 AM, Mark Geisert wrote:
>I've changed Subject: to reflect what's being discussed now. When we
>have a
>consensus cygfuse I'll issue an ITP for it.
>
>I've now updated the cygfuse repository on GitHub so it is more neutral
>about
>FUSE implementations. It can be seen at
>https:/
On 9/8/16, 5:01 AM, Corinna Vinschen wrote:
>On Sep 6 21:13, Bill Zissimopoulos wrote:
>> On 9/5/16, 2:35 AM, Mark Geisert wrote:
>>>I wasn't sure from Corinna's comments a while back (re hosting this
>> >package)
>> >whether she thought cygfuse s
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 Win
On 9/5/16, 2:35 AM, Mark Geisert wrote:
>>While still on vacation I now have reliable access to the Internet and am
>> able to follow up on any issues. Please let me know what the issue you
>>are
>> seeing is and I will try to help.
Mark, I am now back from vacation and should be able to follow
On 8/22/16, 12:43 PM, cygwin-apps-ow...@cygwin.com on behalf of Mark
Geisert wrote:
>>>I was planning to make sure the package Bill supplied met all the
>>> requirements for a Cygwin package. I figure it's real close but there
>>>was
>>> something I wasn't sure about and needed to research furthe
Mark, hi:
On 8/22/16, 12:43 PM, cygwin-apps-ow...@cygwin.com on behalf of Mark
Geisert wrote:
>>>I was planning to make sure the package Bill supplied met all the
>>> requirements for a Cygwin package. I figure it's real close but there
>>>was
>>> something I wasn't sure about and needed to res
On 7/29/16, 1:19 AM, Mark Geisert wrote:
>FWIW I've signed up with GitHub with username mgeisert. I think I need
>to be
>invited to join the cygwin@github org. Then maybe I can transfer your
>repo to
>me? Corrections welcome...
Hey, Mark. I just transferred the cygfuse repo under your name.
Hi, Mark:
On 7/28/16, 10:29 AM, Mark Geisert wrote:
Please be mindful if you intend to test that the current released
binary
of WinFsp does not support Windows 7. This is because the last release
erroneously uses a Windows 8 only API (GetOverlappedResultEx).
>>>
>>> It's your c
On 7/28/16, 5:17 PM, Bill Zissimopoulos wrote:
>On 7/28/16, 5:04 PM, Mark Geisert wrote:
>
>>Bill Zissimopoulos wrote:
>>> On 7/28/16, 1:04 PM, Corinna Vinschen wrote:
>>>
>>>>github Cygwin org?
>>>>
>>>> https://github.com/cy
On 7/28/16, 5:04 PM, Mark Geisert wrote:
>Bill Zissimopoulos wrote:
>> On 7/28/16, 1:04 PM, Corinna Vinschen wrote:
>>
>>>github Cygwin org?
>>>
>>> https://github.com/cygwin
>>>
>>> Every Cygwin-related project is welcome.
>>
On 7/28/16, 1:04 PM, Corinna Vinschen wrote:
>On Jul 28 19:13, Bill Zissimopoulos wrote:
>> Mark:
>>
>> >I agree with how you want to adjust license and transfer ownership. I
>> >don't
>> >have a presence on GitHub but I should be able to grab
>Mark, if at some point you do get a github account, I will be happy to
>transfer ownership of the project as well.
To clarify, I meant: “I will be happy to transfer ownership of the github
repository as well”.
Bill
t you do get a github account, I will be happy to
transfer ownership of the project as well. In the mean time do you have
somewhere where you intend to host it?
Regards,
Bill Zissimopoulos
[CYGFUSE]: https://github.com/billziss-gh/cygfuse
On 7/28/16, 10:29 AM, Mark Geisert wrote:
>>I am going to really try to get that Win 7 supporting build out by the
>>end
>> of Thursday (Pacific time).
>
>That's the timezone I'm in. I'll see what's going on later tonight :) .
Ok, great. Then we should be able to do this today.
>My mistake. I
On 7/28/16, Mark Geisert wrote:
>Bill Zissimopoulos wrote:
>> Please be mindful if you intend to test that the current released binary
>> of WinFsp does not support Windows 7. This is because the last release
>> erroneously uses a Windows 8 only API (GetOverlappedResultE
On 7/27/16, 2:03 AM, Mark Geisert wrote:
>Bill Zissimopoulos writes:
>> To test that things work, clone my sshfs repo from:
>>
>> https://github.com/billziss-gh/sshfs
>>
>> And issue the following commands:
>>
>> $ autoreconf -i
>&g
On 7/26/16, 12:02 PM, Mark Geisert wrote:
>If this turns out to be a workable solution, I am willing to be maintainer
>of the glue library Bill is offering.
I have created a new repository here:
https://github.com/billziss-gh/cygfuse
It contains the following:
- fuse.cygport
- cygfuse.c
On 7/26/16, 1:07 PM, Adrien JUND wrote:
>Excellent idea Bill !
>I am absolutely willing to do it !
>
>Dokan install folder can also be retrieved from the registry so it is
>a way to go with dlopen and dlsym mechanism.
Great. I am glad that this seems like it might work.
>Since I think all fuse
On 7/26/16, 12:02 PM, Mark Geisert wrote:
>Bill Zissimopoulos writes:
>> BTW, here is another alternative that I have been mulling around.
>>
>[...]
>
>Very interesting. I'll need a little more time to investigate; github is
>throwing unicorns at the moment.
Ye
On 7/26/16, 11:13 AM, Mark Geisert wrote:
>Erm, I'm belatedly comprehending it's two independent FUSE
>implementations and not two versions with some common history. OK. If
>there's a documented binary API at some level of the FUSE definition
>that both implementations provide then that's what
On 7/25/16, 11:27 PM, Mark Geisert wrote:
>Bill Zissimopoulos writes:
>> - Rename the package to winfsp-fuse, but have it somehow “satisfy”
>> packages that require “fuse” (e.g. SSHFS, FUSEPY). This would allow
>> multiple *-fuse packages to exist in the setup database an
On 7/25/16, 11:27 PM, Mark Geisert wrote:
>Bill Zissimopoulos writes:
>> - Rename the package to winfsp-fuse, but have it somehow “satisfy”
>> packages that require “fuse” (e.g. SSHFS, FUSEPY). This would allow
>> multiple *-fuse packages to exist in the setup database an
>As I said, I'm not going to refuse your package. I was just pissed
>about this discussion in conjunction with my (now) obvious
>misunderstanding that we're talking about two forks of the same code.
>
>Please go ahead as planned,
Thanks. As I see it there are the following options:
- Accept/rej
On 7/23/16, 10:48 AM, Corinna Vinschen wrote:
>So you quoted my knee-jerk reaction but missed to quote the *real* point
>of my mail. Fixed that for you:
>
>> > Here's an idea: You both slap yourself and start talking to each
>>other.
>> >
>> > For the Windows *and* Cygwin world it would be *mu
On 7/23/16, 3:40 AM, Corinna Vinschen wrote:
>
>no idea what's up between you, but this discussion is gross...
>
>My interest in both of your projects has just dwindled considerably.
Corinna, understood. I think this may have been the point.
I was planning to work for a solution for how to have
On 7/22/16, 11:01 PM, Marco Atzeri wrote:
>On 23/07/2016 02:31, Bill Zissimopoulos wrote:
>>Suppose I have a package XYZ that requires FUSE. Is it possible that the
>> “FUSE” dependency can be satisfied by either winfsp-fuse or dokan-fuse?
>>
>> If that is not possible
On 7/22/16, 12:57 PM, Marco Atzeri wrote:
>On 22/07/2016 19:58, Bill Zissimopoulos wrote:
>>> winfsp-fuse is a reasonable name.
>>> dokan-fuse also (IMHO)
>>
>> In the interest of moving things forward, I am happy to rename the
>> package. Is it possible f
On 7/22/16, 12:56 PM, Adrien JUND wrote:
>For information on your last release: curl -u "username"
>https://api.github.com/repos/billziss-gh/winfsp/releases
>=> winfsp-0.14.16197.msi - "download_count": 24
This is beginning to feel a bit weird. You seem to be rather obsessed with
how many users
>winfsp-fuse is a reasonable name.
>dokan-fuse also (IMHO)
In the interest of moving things forward, I am happy to rename the
package. Is it possible for a package with a name winfsp-fuse to satisfy a
“fuse” dependency?
Bill
On 7/22/16, 12:59 AM, Corinna Vinschen wrote:
>On Jul 21 22:11, Bill Zissimopoulos wrote:
>> On 7/20/16, 1:52 AM, Corinna Vinschen wrote:
>>
>> >We just might still want to change the name to "no+body".
>> >
>> >What do others on this list th
On 7/22/16, 4:59 AM, Adrien JUND wrote:
>The package should be renamed winfsp-fuse for give ability of cygwin
>users to choose which solution they would like to use. Like
>dokan-fuse, cbfs-fuse and other projects that offer the same
>service...
I am not opposed to renaming the package if that’s
On 7/20/16, 1:52 AM, Corinna Vinschen wrote:
>We just might still want to change the name to "no+body".
>
>What do others on this list think? What sounds better?
>
> "nodomain+nobody" or "no+body"
Corinna, hi.
I know you have asked others to chime in, but IMO you should go ahead and
change it t
On 7/19/16, 2:41 AM, Corinna Vinschen wrote:
>
>Let's just try how it looks like. I applied the patch using
>"nodomain+nobody" for now and uploaded a developer snapshot to
>https://cygwin.com/snapshots/
Hi, Corinna:
Here is simple SSHFS output with the patched cygwin1.dll:
billziss@windows
On 7/18/16, 12:43 PM, Bill Zissimopoulos wrote:
>On 7/18/16, 1:19 AM, Corinna Vinschen wrote:
>
>>Btw., I didn't apply it yet because I was still waiting for a mailing
>>list reply to https://cygwin.com/ml/cygwin/2016-06/msg00460.html
>>On second thought, this didn
On 7/18/16, 1:19 AM, Corinna Vinschen wrote:
>On Jul 17 01:02, Bill Zissimopoulos wrote:
>>The alternatives are:
>>
>> 1. Accept the FUSE cygport package as is. Understand that it requires
>> prior installation of WinFsp in order to properly work.
>>
>>
On 7/17/16, 2:18 PM, Marco Atzeri wrote:
>On 17/07/2016 03:02, Bill Zissimopoulos wrote:
>> This package adds FUSE 2.8 support to Cygwin. FUSE is the well-known
>> "Filesystem in Userspace" project for Linux and other platforms: [FUSE].
>>
>>[snip]
>>
This package adds FUSE 2.8 support to Cygwin. FUSE is the well-known
"Filesystem in Userspace" project for Linux and other platforms: [FUSE].
FUSE file systems that use this package usually require minimal changes to
run on Cygwin. For example, here are the pull requests I have submitted to
SSHFS
38 matches
Mail list logo
