From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: sshfs or alike
Date: Wed, 6 May 2020 13:33:54 -0600 [thread overview]
Message-ID: <80e31ca3-1949-a8a0-84ab-eddeb1d9ef52@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+7cx1qZwDFbmx7BWZ9UdR0NFcRPvQU6NRgntdKwpHU2+O1dfg@mail.gmail.com>
On 2020-05-06 12:14, Morten Kjærulff via Cygwin wrote:
> As I understand, you can get sshfs to work with cygwin, but you have
> to install some non-cygwin tools also.
>
> Can I get sshfs or something like that with only cygwin tools?
Not unless Windows provides a user file system interface that Cygwin can access.
The code for that:
https://github.com/billziss-gh/winfsp
was developed in consultation with Cygwin maintainers, and the Cygwin components
are provided as Cygwin packages within the repo.
The FUSE interface is provided for Windows by the File System Proxy package:
http://www.secfs.net/winfsp/
and the Cygwin packages are provided in the primary Download winfsp.msi Windows
installer package:
http://www.secfs.net/winfsp/rel/
where SSH FS ports prepackaged for 64 and 32 bit programs and a 32 bit port of
NFS are also available.
Extra steps are required to install the Cygwin packages under each Cygwin 32/64
bit installation:
http://www.secfs.net/winfsp/rel/#for-cygwin-users
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-05-06 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 18:14 Morten Kjærulff
2020-05-06 19:22 ` Marco Atzeri
2020-05-06 19:33 ` Brian Inglis [this message]
2020-05-08 9:46 ` Andrey Repin
2020-05-08 14:29 ` Morten Kjærulff
2020-05-08 15:31 ` Maarten Hoes
2020-05-08 17:17 ` Brian Inglis
2020-05-08 20:24 ` Andrey Repin
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=80e31ca3-1949-a8a0-84ab-eddeb1d9ef52@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@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).