public inbox for
 help / color / mirror / Atom feed
From: Mark Geisert <>
To: Cygwin-Apps <>
Subject: Re: fuse
Date: Thu, 3 Feb 2022 22:58:54 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

One final reply to myself on this topic..

>> 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'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.

This turned out to be an issue in Cygwin 3.3.3 but not 3.3.4 or the upcoming 
3.4.0.  WinFSP is ready to be used from Cygwin.

> I plan to rename it FUSE for the upcoming ITP, to avoid
> name conflict with libfuse* common on Linux.

Nah, there will be two upcoming ITPs, cygfuse and sshfs.  The first will provide 
the glue layers (libfuse and libfuse3) that ride on top of WinFSP, and also a 
'fusermount' command.  The second ITP will be a port of the latest sshfs reference 
implementation to Cygwin.  sshfs is known to clean-compile against the glue layer 


      parent reply	other threads:[~2022-02-04  6:58 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   ` 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     ` Mark Geisert [this message]

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