public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tom Schutter <t.schutter@comcast.net>
To: cygwin@cygwin.com
Subject: Re: cygwin: how to mount linux FS from cygwin
Date: Thu, 09 Aug 2012 13:56:00 -0000	[thread overview]
Message-ID: <20120809130332.GA4688@shadow.schutter.home> (raw)

On Wed, 11 Jul 2012 10:30:28 -0400, cgf wrote:
>On Wed, Jul 11, 2012 at 10:23:29AM -0400, ping wrote:
>>so I'm now using dokan sshfs GUI tool to mount remote linux server FS
>>via ssh, everything (mostly) works, except:
>>
>>1) it's a GUI based tool, I don't see any command line options
>>2) somehow I can't save the previous data, after pressing "save" button,
>>it pop up a warning dialog below.
>>
>>please share some thought if anyone experienced the same.
>
>No, please go somewhere else to get thoughts on the "dokan sshfs GUI tool".
>Presumably, they have a forum for dealing with users.  You should use it.
>
>This is off-topic here.

Actually it is not off-topic.  From the error message that cgf clipped:

  System.ArgumentException: Item has already been added. Key in dictionary: 'tmp' Key being added: 'tmp'
  <cut>
  at System.Xml.Serialization.XmlSerializer..ctor(Type type)

If you read the thread at
http://cygwin.com/ml/cygwin/2012-03/msg00375.html , you will see that
the dokan sshfs tool is crashing while apparently attempting to
process the environment variables setup by Cygwin.  The environment
contains both 'tmp' and 'Tmp' environment variables which is OK in a
*nix context but not expected by Windows applications.

Any .NET application running on a stock Cygwin installation that uses
XmlSerializer will get bit by this bear trap.

One solution is to upgrade to base-files-4.1-2.  The other is to write
a wrapper program that cleans up the environment before calling the
dokan sshfs GUI tool.

-- 
Tom Schutter

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

             reply	other threads:[~2012-08-09 13:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 13:56 Tom Schutter [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=20120809130332.GA4688@shadow.schutter.home \
    --to=t.schutter@comcast.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).