public inbox for
 help / color / mirror / Atom feed
From: Mark Geisert <>
To: Cygwin-Apps <>
Subject: Re: fuse
Date: Mon, 31 Jan 2022 19:50:34 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Replying to myself...

Mark Geisert wrote:
> 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? 
> 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.

Our fuse package as it stands is not ready for use.  When I last looked at it 
years ago I was too new to both FUSE and project porting to understand what was 
missing.  Currently it's a source package that supplies a glue layer for Cygwin 
apps to make use of WinFSP, a Windows FUSE driver.  It also supplies source for a 
Cygwin sshfs app that demonstrates correct operation of WinFSP via Cygwin.

I've now looked at and installed the most recent WinFSP.  The Cygwin glue layer 
works as well as it always had.  But something is missing: integration with the 
usual shell file manipulation commands.  For example, one can't 'cd' into the 
directory on which a foreign file system has been loaded.  That seems like a major 
issue unless I'm misunderstanding things.

Let me reach out to the WinFSP folks and see if I'm doing something wrong or if 
there's additional work to be done on the Cygwin side.  In any case the project 
needs some smartening up.  I plan to rename it FUSE for the upcoming ITP, to avoid 
name conflict with libfuse* common on Linux.

I see that 'mtr' is another Cygwin package that makes use of a Windows driver via 
libpcap.  Maybe I can use mtr.cygport etc as a guide; I'm unsure whether a Cygwin 
package should be including Windows drivers.
Thanks for reading; advice welcome,


  reply	other threads:[~2022-02-01  3:50 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 ` fuse Mark Geisert
2022-02-01  3:50   ` Mark Geisert [this message]
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).