From: Thomas Creutz <thomas.creutz-Mmb7MZpHnFY@public.gmane.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: character-problems
Date: Thu, 01 May 2014 17:08:03 +0200 [thread overview]
Message-ID: <53626353.2030103@gmx.de> (raw)
In-Reply-To: <CAOhYWNL+3+c7nM-zabZ78PK_j5CkuFqOsB66Ej_dk7pcrpM3bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 01.05.2014 15:32, schrieb Jeff Layton:
> I'm not sure then.
>
> The client generally uses the same tables to convert between unicode
> and the local charset in both directions. One thing you could do is
> inspect some traces when you're reproducing this problem. Get a
> capture of both the "ls" and the "stat" (or cp) commands. Are the
> unicode names being sent by the server identical to the ones being
> sent by the client?
Ok, and how can I do this? tcpdump or some other debug ways?
next prev parent reply other threads:[~2014-05-01 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 8:59 character-problems Thomas Creutz
[not found] ` <CAOhYWNKp1QqsebugYqM2yAqOef4yw=t9tNyUmH-9ds59pjygqw@mail.gmail.com>
[not found] ` <CAOhYWNKp1QqsebugYqM2yAqOef4yw=t9tNyUmH-9ds59pjygqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-01 10:48 ` character-problems Thomas Creutz
[not found] ` <CAOhYWN+PNtQ8HMyi3OFyv3KQ-bbvOKcGFNLZw5Jx2zHNdRJ1LQ@mail.gmail.com>
[not found] ` <CAOhYWN+PNtQ8HMyi3OFyv3KQ-bbvOKcGFNLZw5Jx2zHNdRJ1LQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-01 11:11 ` character-problems Thomas Creutz
[not found] ` <CAOhYWNL+3+c7nM-zabZ78PK_j5CkuFqOsB66Ej_dk7pcrpM3bg@mail.gmail.com>
[not found] ` <CAOhYWNL+3+c7nM-zabZ78PK_j5CkuFqOsB66Ej_dk7pcrpM3bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-01 15:08 ` Thomas Creutz [this message]
[not found] ` <53622BD7.7030005-Mmb7MZpHnFY@public.gmane.org>
2014-05-02 2:41 ` character-problems Günter Kukkukk
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=53626353.2030103@gmx.de \
--to=thomas.creutz-mmb7mzphnfy@public.gmane.org \
--cc=jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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