From: ping <songpingemail@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin: how to mount linux FS from cygwin
Date: Thu, 28 Jun 2012 20:57:00 -0000 [thread overview]
Message-ID: <4FECC513.9040902@gmail.com> (raw)
In-Reply-To: <4FECC13C.9060704@gmail.com>
hi Jeremy/all:
the Dokan sshfs works like a charm.
now all set!
thanks!
regards
ping
On 06/28/2012 04:40 PM, ping wrote:
> thanks Jeremy, will give dokan and winsshfs a shot.
> I didn't think this should be fixed from outside of cygwin.
> will post the result...
>
> regards
> ping
>
> On 06/28/2012 04:09 PM, Jeremy Bopp wrote:
>> On 06/28/2012 02:55 PM, Daniel Colascione wrote:
>>> On 6/28/12 12:34 PM, ping wrote:
>>>> I still miss the magic sshfs tool
>>>> in linux...
>>>
>>> You can make it happen. In principle, FUSE should work as well in
>>> Cygwin as it does under Linux, albeit for Cygwin programs only. It'd
>>> just be a matter of writing the glue logic and hooking into Cygwin's
>>> VFS internals.
>>
>> You may have more immediate results by using a Windows-native SSHFS
>> implementation. I haven't used Dokan myself, but it appears promising:
>>
>> http://dokan-dev.net/en/
>>
>> It's basically a FUSE implementation for Windows that includes an SSHFS
>> client. There is also another one that seems related:
>>
>> http://code.google.com/p/win-sshfs/
>>
>> Assuming you can get one of these to work for you, you'll have the
>> advantage of using it not only with Cygwin programs but native ones as
>> well.
>>
>> -Jeremy
>>
>> --
>> Problem reports: http://cygwin.com/problems.html
>> FAQ: http://cygwin.com/faq/
>> Documentation: http://cygwin.com/docs.html
>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-06-28 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 18:01 ping
2012-06-28 18:20 ` K Stahl
2012-06-28 19:35 ` ping
2012-06-28 19:56 ` Daniel Colascione
2012-06-28 20:09 ` Jeremy Bopp
2012-06-28 20:40 ` ping
2012-06-28 20:57 ` ping [this message]
2012-06-28 21:35 ` Andrey Repin
2012-06-29 8:17 ` Thorsten Kampe
2012-06-29 13:32 ` ping
2012-07-11 14:23 ` ping
2012-07-11 14:30 ` Christopher Faylor
2018-10-26 11:28 ` hauck.adrian451
2018-10-26 13:06 ` cyg Simple
2018-10-26 16:03 ` hauck.adrian451
2018-10-26 16:38 ` Marco Atzeri
2018-10-26 22:55 ` hauck.adrian451
2018-10-26 23:54 ` hauck.adrian451
2018-10-27 3:46 ` Brian Inglis
2018-10-28 1:32 ` hauck.adrian451
2018-10-28 21:27 ` Marco Atzeri
2018-10-28 21:54 ` René Berber
2018-10-29 4:36 ` Brian Inglis
2012-08-09 13:56 Tom Schutter
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=4FECC513.9040902@gmail.com \
--to=songpingemail@gmail.com \
--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).