public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongTae Yoo <alloying@nownuri.net>
To: Urban Widmark <urban@teststation.com>, linux-kernel@vger.kernel.org
Subject: Re: file listing problem in smbfs, kernel 2.4.18
Date: Mon, 25 Mar 2002 14:51:08 +0900	[thread overview]
Message-ID: <3C9EBACC.1640A37E@nownuri.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0203191959310.27806-100000@cola.teststation.com> <3C97E1D2.369C6A10@nownuri.net>

SeongTae Yoo wrote:
> 
> Urban Widmark wrote:
> >
> > On Tue, 19 Mar 2002, SeongTae Yoo wrote:
> >
> > > Urban Widmark wrote:
> > > >
> > > > You could also try the smbfs unicode patch for 2.4.18, and see if that
> > > > changes anything.
> > > >     http://www.hojdpunkten.ac.se/054/samba/index.html
> > > >     (Note the additional samba patch and mount flags needed)
> > >
> > > I tried it just before, but same result.
> >
> > And you patched samba, enabled unicode with the unicode flag and set the
> > "codepage" to be unicode?
> > (I know, it's a bad interface)
> 
> My mistake! Although I have read your patch page, the w2k ntfs partition is
> mounted in the normal options. When they are mounted with enabled unicode
> option, it seems to be listed very well.
> 
> After some other tests (depth change, other directories with the same problem,
> fat32 partition, etc), I will post the results.

It seems that the problem of file listing is solved in my case.

Thanks.

      reply	other threads:[~2002-03-25  5:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15  8:34 file listing problem in smbfs, kernel 2.4.18 SeongTae Yoo
2002-03-18 22:07 ` Urban Widmark
2002-03-19  3:35   ` SeongTae Yoo
2002-03-19 19:09     ` Urban Widmark
2002-03-20  1:11       ` SeongTae Yoo
2002-03-25  5:51         ` SeongTae Yoo [this message]

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=3C9EBACC.1640A37E@nownuri.net \
    --to=alloying@nownuri.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=urban@teststation.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