From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] sshfs 3.7.2-1
Date: Mon, 4 Apr 2022 07:03:58 +0200 [thread overview]
Message-ID: <5ab73431-cd1f-5f1c-1139-184e532548f0@towo.net> (raw)
In-Reply-To: <13b453e6-6739-ab33-c049-f566435ae5f8@maxrnd.com>
Am 04.04.2022 um 01:20 schrieb Mark Geisert:
> Hi Thomas,
>
> Thomas Wolff wrote:
>> Am 03.04.2022 um 08:48 schrieb Mark Geisert:
>>> The following package has been uploaded to the Cygwin distribution:
>>>
>>> * sshfs-3.7.2-1
>>>
>>> This is a port of the reference version of sshfs. It allows access to
>>> local or remote file folders via an ssh (more precisely, sftp)
>>> connection.
>>> The folder appears as a local folder on the user's system.
>>>
>>> Sshfs requires cygfuse and a Windows FUSE provider to function.
>>>
>>> Please send questions or concerns to the main Cygwin mailing list as
>>> usual.
>> Thanks for building this package.
>
> You're welcome. Thank YOU for your patience.
>
>>> cygfuse: initialization failed: winfsp-x64.dll not found
>> I suggest to add a hint to WinFSP installation to this message.
>
> I had thought the hint on the cygfuse announcement was enough :-) But
> no trouble to add it on any FUSE apps that are ported. Thanks.
>
>> Then:
>>> /mnt> mkdir servmount
>>> /mnt> sshfs 192.168.178.75: servmount
>>> Cannot create WinFsp-FUSE file system: mount point in use.
>>> /mnt>
>> it fails to mount.
>
> A couple of things. Windows differs from Unix/Linux (yet again!) in
> that directories mounted upon cannot exist beforehand. So if you
> rmdir servmount,
> sshfs 192.168.178.75: servmount
> ought to succeed, but instead you will get "read: Software caused
> connection abort", so supply a username@hostname and it should work.
> The abort is some sort of problem with sshfs which I'll investigate.
> On my machine,
> sshfs mark@m0: /mnt/servmount
> works fine.
Yes, that works. Thank you, great feature. Maybe another interactive
hint in this case would help.
Thomas
next prev parent reply other threads:[~2022-04-04 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 6:48 Mark Geisert
2022-04-03 7:48 ` Thomas Wolff
2022-04-03 23:20 ` Mark Geisert
2022-04-04 5:03 ` Thomas Wolff [this message]
2022-04-04 5:42 ` 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:
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=5ab73431-cd1f-5f1c-1139-184e532548f0@towo.net \
--to=towo@towo.net \
--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).