From: Maarten Hoes <hoes.maarten@gmail.com>
To: "Morten Kjærulff" <mortenkjarulff@gmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: sshfs or alike
Date: Fri, 8 May 2020 17:31:56 +0200 [thread overview]
Message-ID: <CAHvU03UBO-HwKvu_BqA2q_grtBfB9uDc77UEjhY85UO-zMSE7w@mail.gmail.com> (raw)
In-Reply-To: <CA+7cx1rv0KjcCmZ5Ctw-3q_9K8vcpMruJsfHmNoUnFBQi+XP_w@mail.gmail.com>
On Fri, May 8, 2020 at 5:08 PM Morten Kjærulff via Cygwin <cygwin@cygwin.com>
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?
> >
> > Adding to the already mentioned points, I should warn you that SSHFS is
> > EXTREMELY SLOW. By design.
> > Enumerating significant amount of files could take minutes. If you can
> use any
> > other tools (like, OpenVPN + CIFS), it will be hundred if not thousand
> times
> > faster.
>
> Would this be cygwin only?
>
> My server is a z/OS mainframe, where we just installed sshd. Anyone
> have good tips?
>
> /Morten
>
Hi,
I don't mean to intrude, or pretend to know what I'm talking about, but ....
Perhaps it would help if you stated what the specific use case is ? I
assUme that you mean to transfer files between z/OS and a PC, but does it
have to be a filesystem ? Would 'scp' suffice ? Is there a rsync port for
z/OS ?
Just thinking out loud here.
Sorry for the noise,
- Maarten
next prev parent reply other threads:[~2020-05-08 15:32 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
2020-05-08 9:46 ` Andrey Repin
2020-05-08 14:29 ` Morten Kjærulff
2020-05-08 15:31 ` Maarten Hoes [this message]
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=CAHvU03UBO-HwKvu_BqA2q_grtBfB9uDc77UEjhY85UO-zMSE7w@mail.gmail.com \
--to=hoes.maarten@gmail.com \
--cc=cygwin@cygwin.com \
--cc=mortenkjarulff@gmail.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).