Am 01.05.2014 13:11, schrieb Thomas Creutz:
>
> Am 01.05.2014 12:54, schrieb Jeff Layton:
>> Maybe...
>>
>> For your kernel, what is CONFIG_NLS_DEFAULT set to? I know that ubuntu
>> used to set that to iso9959-1, but I think they recently moved to
>> using utf8. If it's set to iso8559-1 then that may be related to the
>> problem.
>
> No, its not a charset problem.
>
> grep CONFIG_NLS_DEFAULT /boot/config-$(uname -r)
> CONFIG_NLS_DEFAULT="utf8"
>
> because I also told, that the file names have the same problem on the
> server (uploaded over php-scripts). Some scripts use utf-8 others
> iso8...., thats why you will never see all chars right on console/samba
> client.
> But, this problem should get handelt by samba/cifs... the files are also
> useable with a windows client (so the access problem is in the cifs
> client, not the samba server)
i've tested this on clients running
opensuse-12.3 - kernel 3.7.10-1.28-desktop
opensuse-13.1 - kernel 3.11.10-7-desktop
samba server Version 3.6.12-59.19.1-3208-SUSE-SL12.3-x86_64
is running on opensuse-12.3.
Here i don't see that
Kost?me1.jpg (i really used a question mark here)
on the server is changed to
Kost_me1.jpg
on the client.
But in fact i really can't test that sanely here, because what is really
byte coded for "?" in Kost?me1.jpg on the server?
Can you get a hex-representation of that file name?
In addition it could also help when you post your samba server's smb.conf.
Cheers, Günter
--
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
