Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: "Dylan Cuthbert" <dylan AT q-games DOT com>
Subject: Re: Cygwin, Rsync and 8-bit chars (SJIS)
Date: Wed, 17 Sep 2003 10:33:27 +0900
Lines: 115
Message-ID: <bk8dl9$k4f$1@sea.gmane.org>
References: <bk7499$7c9$1 AT sea DOT gmane DOT org> <bk75c6$9nq$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 56 DOT 0309161058290 DOT 12411 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Ok, What's a managed mount when its at home?  I've found lots of messages
talking about its bugs but nothing explaining what it is yet or what about
it that is useful.

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com

"Igor Pechtchanski" <pechtcha AT cs DOT nyu DOT edu> wrote in message
news:Pine DOT GSO DOT 4 DOT 56 DOT 0309161058290 DOT 12411 AT slinky DOT cs DOT nyu DOT edu...
> Dylan,
>
> This seems like a good excuse to try the managed mount mode.  Search the
> August archives for it.  Be aware, though, that this is a *highly*
> experimental feature, and it currently requires a newly-created directory.
> Igor
>
> On Tue, 16 Sep 2003, Dylan Cuthbert wrote:
>
> > After reading up some more about Cygwin's libs, I think the
> > double-backslashes that are appearing are causing cygwin to think the
path
> > is a DOS path, not a posix-style one.
> >
> > The reason the backslashes are there is because SJIS uses them as the
second
> > character in the encoding of some of its double-byte characters, I can't
> > change that unfortunately.
> >
> > If this is the case then I could really do with some secret CYGWIN flag
> > (couldn't find it in the user guide) that can disable the DOS path
parsing
> > temporarily, by using [env CYGWIN=nodospaths tty ntsec rsync "blah"]
for
> > example?
> >
> > Anybody got a clue as to what to do here?  It seems as if Cygwin might
be
> > broken when it comes to SJIS filenames because of this, maybe the "is
this a
> > DOS path" check could be more stringent?  If the path has forward
slashes,
> > even one, maybe it can be left untouched?
> >
> > Regards
> >
> > ---------------------------------
> > Q-Games, Dylan Cuthbert.
> > http://www.q-games.com
> >
> >
> > "Dylan Cuthbert" <dylan AT q-games DOT com> wrote in message
> > news:bk7499$7c9$1 AT sea DOT gmane DOT org...
> > > Hi there,
> > >
> > > I'm having a problem with SJIS encoded (windows) filenames and
rsync'ing
> > > them anywhere.  It doesn't happen for all files and as far as I can
make
> > out
> > > the problem occurs when the filename is fully japanese (as opposed to
some
> > > english text followed by some japanese text).
> > >
> > > One of the bad filenames in question is:
> > >
> > > 'ls -b's output:
> > >
> > > \225\\\216\206.doc
> > >
> > > It has a triple-backslash sequence in it, maybe this is the problem?
I'm
> > > not sure how and why it has a triple backslash sequence as the
filename
> > > displayed is simply 3 japanese characters.  Anyway, rsync chokes, it
says
> > it
> > > cannot find the file and displays the correct (and existing) filename
in
> > > japanese (when using a regular bash window)
> > >
> > > [some time passes]
> > > I just checked all the errors (about 5% of all japanese files) and the
> > > errors occur in the filenames with double-slash or triple-slash
sequences
> > in
> > > them.  Anyone have any ideas 1) how the double/triple-slashes get
there in
> > > the first place, and 2) how to fix the problem? 3) why this problem
occurs
> > > at all, shouldn't rsync be simply getting the file strings and passing
> > them
> > > onto the file system library or does the file system library do some
> > arsing
> > > about with backslashes because of that c:\ conversion to /cygdrive/c
stuff
> > > that cygwin does?  Any way to turn that off if that's the case?
> > >
> > > Regards
> > >
> > > ---------------------------------
> > > Q-Games, Dylan Cuthbert.
> > > http://www.q-games.com
>
> -- 
> http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
> ZZZzz /,`.-'`'    -.  ;-;;,_ igor AT watson DOT ibm DOT com
>      |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski, Ph.D.
>     '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
>
> "I have since come to realize that being between your mentor and his route
> to the bathroom is a major career booster."  -- Patrick Naughton
>



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/