From: SeongTae Yoo <alloying@nownuri.net>
To: Urban Widmark <urban@teststation.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file listing problem in smbfs, kernel 2.4.18
Date: Tue, 19 Mar 2002 12:35:23 +0900 [thread overview]
Message-ID: <3C96B1FB.BFE2C122@nownuri.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0203182148020.15143-100000@cola.teststation.com>
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.
>
> Do you have trouble with this set of files elsewhere?
>
> If you have more than one server, does it make any difference if you copy
> the files to some other server?
I have already tested before the previous posting, but no difference.
However, when the files are copied to a fat32 partition of w2k server,
all files listed.
> Does it matter how deep in the file hierarchy the dir is, for example is
> there any difference between these two:
> //server/share/some/long/path/the-dir-that-fails/
> //server/share/the-dir-that-fails/
The original depth is
//server/e$/1st-dir/2nd-dir/3rd-dir/
tested depths are
//server/e$/2nd-dir/3rd-dir/ or
//server/e$/3rd-dir/
but no difference.
If you need some other tests, I will do it.
next prev parent reply other threads:[~2002-03-19 3:35 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 [this message]
2002-03-19 19:09 ` Urban Widmark
2002-03-20 1:11 ` SeongTae Yoo
2002-03-25 5:51 ` SeongTae Yoo
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=3C96B1FB.BFE2C122@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