Hi,
Thanks for all reply to my question. They helped me to find the solution.
Here's this solution for the next person with the same problem :)
If the parametter "character set" is not set, Samba2 don't convert
filenames' charset, and write them "as they arrive from the client". My
files also have theyr names in CodePage 850 :x , on an system configured to
work with ISO8859-1
Samba3 can't work like this (or if it can... I didn't found how).
There are 2 solutions :
A/ Rebuilding Samba3 with Lib-iconv , and adding
unix charset = CP850
in the samba config.
B/ Converting all filenames from CP850 to the real unix charset (eg UTF8 or
ISO8859-1 or ... I don't know your system :), and adding
unix charset = LOCALE
in the samba config . To do this, you can use convmv (
http://j3e.de/linux/convmv/ - thanks goes to Nicholas Brealey for the link).
Or mix these 2 solutions in a "migration plan". (I will do the A/ first, and
ii the future the B/ ... )
The B/ is great, because your files are now realy in the system's charset,
and special chars are displayed fine, even in a simple text console, but
it's an heavy operation and can be difficult to do if you have a huge volume
of files and lot of users working on them.
Julien AILHAUD
From: Tom Schaefer <[EMAIL PROTECTED]>
To: samba@lists.samba.org
CC: [EMAIL PROTECTED]
Subject: [Samba] Re: Unicode, ASCII, and Samba3 ...
Date: Wed, 2 Nov 2005 07:43:27 -0600
I work at a university and when I upgraded from 2 to 3 only 1 user ever
complained, a professor in the foreign languages department. I started
to go down the road of conversion utilities and fiddling with code pages
and character sets. Then a potential easy solution occurred to me. We
have several Samba servers and the Unix boxes have a lot of disk in
common; I still had Samba 2 on some systems. On the UNIX side I moved
her files to where they where once again being shared by a Samba 2
server. As would be expected, from the client side, MS Windows, all the
file names where instantly intact again. I copied all her files down
from the Samba 2 server to local disk of a MS Windows box. From the MS
Windows box I then copied the files up to the Samba 3 server. Ta da. Now
they where on the Samba 3 server with file names intact.
Of course doing something like that may not be feasible in your case.
Good luck.
Tom Schaefer
On Wed, 26 Oct 2005 16:57:56 +0200
"Julien Ailhaud" <[EMAIL PROTECTED]> wrote:
>
>
> Problem summary :
> Files created with samba2 are now unreadable with samba3. I tested all
> possible settings in samba, rebuild it with libiconv, already posted
here
> without reply ... without success.
>
> Today I analyzed the traffic between my station and the server, and I
found an
> interresting thing :
>
> With both version, filenames are transmited in ascii
> code 130 gives "é"
> code 135 gives "ç"
> code 151 gives "ù"
>
> But ...
>
> In packets exchanged by my Samba2 server and the stastion, the flag
"unicode
> strings" is set to Zero ( --> ASCII )
>
> In packets exchanged by my Samba3 server and the stastion, the flag
"unicode
> strings" is set to One ( --> UNICODE )
>
>
> I think that the problem is here, but I can't find how to change it,
forcing
> my Samba to use ASCII there.
>
> Any Idea ??
>
> Thanks.
_________________________________________________________________
Une chance par jour de gagner un voyage au soleil avec Magic Search !
http://www.magicsearch.fr
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
