Hi! I have a test file with all special characters of hungarian language on a windows share: ??????????????????.txt (I hope Your mailer wiill show them correctly :-)) When I use smbclient to connect to share, I see correct characters, I can get the file to local disk and ls shows the correct name too. When I try to mount with smbmount the closest result I produced was: ?I???AuUoO?U?????O.txt cp says no such file or directory... Any ideas? Relevant (I hope all) settings: smbmount ... -o charset=cp852,iocharset=iso8859-2 smb.conf: unix charset = iso8859-2 All locale variables set to en_US In kernel grep NLS .config says: CONFIG_UDF_NLS=y # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-2" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_737=y CONFIG_NLS_CODEPAGE_775=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_CODEPAGE_852=y CONFIG_NLS_CODEPAGE_855=y CONFIG_NLS_CODEPAGE_857=y CONFIG_NLS_CODEPAGE_860=y CONFIG_NLS_CODEPAGE_861=y CONFIG_NLS_CODEPAGE_862=y CONFIG_NLS_CODEPAGE_863=y CONFIG_NLS_CODEPAGE_864=y CONFIG_NLS_CODEPAGE_865=y CONFIG_NLS_CODEPAGE_866=y CONFIG_NLS_CODEPAGE_869=y CONFIG_NLS_CODEPAGE_936=y CONFIG_NLS_CODEPAGE_950=y CONFIG_NLS_CODEPAGE_932=y CONFIG_NLS_CODEPAGE_949=y CONFIG_NLS_CODEPAGE_874=y CONFIG_NLS_ISO8859_8=y CONFIG_NLS_CODEPAGE_1250=y CONFIG_NLS_CODEPAGE_1251=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_ISO8859_2=y CONFIG_NLS_ISO8859_3=y CONFIG_NLS_ISO8859_4=y CONFIG_NLS_ISO8859_5=y CONFIG_NLS_ISO8859_6=y CONFIG_NLS_ISO8859_7=y CONFIG_NLS_ISO8859_9=y CONFIG_NLS_ISO8859_13=y CONFIG_NLS_ISO8859_14=y CONFIG_NLS_ISO8859_15=y CONFIG_NLS_KOI8_R=y CONFIG_NLS_KOI8_U=y CONFIG_NLS_UTF8=y Dobos Sandor IBCnet Hungary Ltd.
>When I use smbclient to connect to share, I see correct characters, I can >get the file to local disk and ls shows the correct name too. >When I try to mount with smbmount the closest result I produced was: >?I???AuUoO?U?????O.txt >cp says no such file or directory... > >Note: cookie cutter response follows: The smbfs module is maintained through the kernel development people, they would best know the answer to your question, or if there is no answer. Old and busted: smbfs New hotness: cifs While the cifs module is also not maintained here either (I'm pretty sure), it's much better and often times solves the issue of the day. Try to use it to mount your share and see what happens.>Any ideas? > >Relevant (I hope all) settings: >smbmount ... -o charset=cp852,iocharset=iso8859-2 > >smb.conf: >unix charset = iso8859-2 > >All locale variables set to en_US > >In kernel grep NLS .config says: >CONFIG_UDF_NLS=y ># CONFIG_SMB_NLS_DEFAULT is not set >CONFIG_NLS=y >CONFIG_NLS_DEFAULT="iso8859-2" >CONFIG_NLS_CODEPAGE_437=y >CONFIG_NLS_CODEPAGE_737=y >CONFIG_NLS_CODEPAGE_775=y >CONFIG_NLS_CODEPAGE_850=y >CONFIG_NLS_CODEPAGE_852=y >CONFIG_NLS_CODEPAGE_855=y >CONFIG_NLS_CODEPAGE_857=y >CONFIG_NLS_CODEPAGE_860=y >CONFIG_NLS_CODEPAGE_861=y >CONFIG_NLS_CODEPAGE_862=y >CONFIG_NLS_CODEPAGE_863=y >CONFIG_NLS_CODEPAGE_864=y >CONFIG_NLS_CODEPAGE_865=y >CONFIG_NLS_CODEPAGE_866=y >CONFIG_NLS_CODEPAGE_869=y >CONFIG_NLS_CODEPAGE_936=y >CONFIG_NLS_CODEPAGE_950=y >CONFIG_NLS_CODEPAGE_932=y >CONFIG_NLS_CODEPAGE_949=y >CONFIG_NLS_CODEPAGE_874=y >CONFIG_NLS_ISO8859_8=y >CONFIG_NLS_CODEPAGE_1250=y >CONFIG_NLS_CODEPAGE_1251=y >CONFIG_NLS_ASCII=y >CONFIG_NLS_ISO8859_1=y >CONFIG_NLS_ISO8859_2=y >CONFIG_NLS_ISO8859_3=y >CONFIG_NLS_ISO8859_4=y >CONFIG_NLS_ISO8859_5=y >CONFIG_NLS_ISO8859_6=y >CONFIG_NLS_ISO8859_7=y >CONFIG_NLS_ISO8859_9=y >CONFIG_NLS_ISO8859_13=y >CONFIG_NLS_ISO8859_14=y >CONFIG_NLS_ISO8859_15=y >CONFIG_NLS_KOI8_R=y >CONFIG_NLS_KOI8_U=y >CONFIG_NLS_UTF8=y > > >Dobos Sandor >IBCnet Hungary Ltd. > > > > > > >-- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: pgienger@ae-solutions.com
dobos_s@ibcnet.hu wrote:> I have a test file with all special characters of hungarian language on a > windows share: ??????????????????.txt > (I hope Your mailer wiill show them correctly :-))It doesn't.> When I use smbclient to connect to share, I see correct characters, I can > get the file to local disk and ls shows the correct name too. > When I try to mount with smbmount the closest result I produced was: > ?I???AuUoO?U?????O.txt > cp says no such file or directory... > > Any ideas?Simply leave your Samba 3 things for Unix/Linux as they are.> Relevant (I hope all) settings: > smbmount ... -o charset=cp852,iocharset=iso8859-2Certainly don't use the above (ugh ;) Just leave things as they are.> smb.conf: > unix charset = iso8859-2NO ;) ugh ugh. This should be left at UTF8, as (should be) the default. Though you don't give your basic OS - mine's Red Hat RHAS3. My default LOCALE is NO_NB. I have NO problems with what you describe using Norwegian characters (???).> All locale variables set to en_USMine is no_NB, which caters for 8-bit UTF (in all shapes and forms). I.e., I have a(n emulated) Norwegian keyboard both in TTY1 and pts/0. Best, --Tonni -- mail: tonye@billy.demon.nl http://www.billy.demon.nl They'll love us, won't they? They feed us, don't they ? ...
>Old and busted: smbfs >New hotness: cifs > >While the cifs module is also not maintained here either (I'm pretty >sure), it's much better and often times solves the issue of the day. >Try to use it to mount your share and see what happens.With mount -t cifs it works! Thanks Dobos Sandor IBCnet Hungary Ltd.
>With mount -t cifs it works!Suddently not. It seems there are windows shares, where some files have characters in their names with iso8859-1 and others with iso8859-2 encodings. If I mount with iocharset=iso8859-x the filenames are ok, but not at the same time. But when I browse that share with windows I see the good characters despite they are not in the same codepage. I dont really need to see (display) the right characters in linux. I only want that rsync, cp and others can reach these files; and if they will be copied back to windows share the filename should not change (this should be a backup solution :-) Can somebody help me? Dobos Sandor IBCnet Hungary Ltd.