public inbox for
 help / color / mirror / Atom feed
From: Mark Geisert <>
To: Cygwin-Apps <>
Subject: Re: fuse
Date: Sun, 9 Jan 2022 22:00:24 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Thomas,

Thomas Wolff wrote:
> What became of the winfsp-fuse project discussed in July 2016?
> I'd like to be able to use ftpfs or sshfs in cygwin.

Integration of the project into Cygwin stalled around that time, or was it 2018? 
ISTR there was an objection from the Dokany FUSE project about whether WinFSP FUSE 
should be the basis for Cygwin's implementation.  I tried to mollify that by 
implementing a poor-man's plugin feature that would allow a user to select which 
underlying FUSE layer to use.  I believe I was waiting for confirmation from 
Dokany that they could work with that plugin architecture.

I think it was my ITP for libfuse that prompted the discussion with Dokany.  In 
any case the ITP was never acted on and the project has since languished.  WinFSP 
itself has been improved over time; I don't know if the improvements would require 
an update to the Cygwin portion.

I would love to have somebody interested in trying out FUSE on Cygwin.  If you 
require a cygfuse package I guess the first step for that would be for me to 
reissue the ITP and make the package real.  Another alternative would be for you 
to build from the Github repo if you're 
feeling adventurous.


  reply	other threads:[~2022-01-10  6:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 22:45 fuse Thomas Wolff
2022-01-10  6:00 ` Mark Geisert [this message]
2022-02-01  3:50   ` fuse Mark Geisert
2022-02-01  6:20     ` fuse ASSI
2022-04-13 19:55       ` fuse Jon Turney
2022-04-15  8:11         ` fuse Mark Geisert
2022-02-04  6:58     ` fuse Mark Geisert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).