Bug 130980
| Summary: | smbmount does not convert from default DOS character set | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrick Monnerat <patrick> | ||||
| Component: | samba | Assignee: | Jay Fenlason <fenlason> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | CC: | jfeeney, mattdm, redhat-bugzilla | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-10-30 14:19:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
I think this bug is in current development, too. Maybe this bug should be marked as FC2/3 target tracker. Created attachment 103319 [details] Patch to fix bug #130980 Here is my proposed patch. It supports upper/lowercase charset names recognized by the Linux kernel, plus upper/lower "UTF-8". Since charset names are interpreted in the kernel, no iconv alias names may be used. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. FC2 was still hot at the time the bug has been submit... Anyway, reporting this bug (and its solution) to samba people did not make them happy. (See https://bugzilla.samba.org/show_bug.cgi?id=1846). They decided not to fix it, since it is possible to specify "codepage=..." in the smbmount command line options. They claim it is an smbfs problem (they are wrong!) and the kernel default is a sufficient default, although needing kernel recompilation to change it. /etc/samba/smb.conf seems to me more easily configurable... Therefore the bug is still present in FC3. Each mounting utility must then be able to manage "codepage=..." by itself! What a pity :-( If no fix is applied to the smbmount code, it may be appropriate to set cp850 as the default in stock kernels... Please apply the follow-up to this bug report according to your policy (CLOSE/WONTFIX, kernel config, or whatever seems appropriate to you). Thanks. Closing as WONTFIX based on the previous comment. Sorry that upstream prefers to keep the behavior this way. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) Description of problem: On a LAN using CP850 for smb (dos charset in /etc/samba/smb.conf) and FC2 computers configured in UTF-8 (unix charset = UTF-8), smbmount ignores these default configuration parameters and performs no conversion. To make smbmount work, you have to specified -o codepage=cp850 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Configure machine1 as samba server with "dos charset = CP850" and "unix charset = UTF-8". Create a share. In this share, create a file with accentuated characters in its name (i.e.: "sträñgêfìlename"). 2. Configure machine2 as samba client with "dos charset = CP850" and "unix charset = UTF-8". 3. On machine2, "smbmount //machine1/share /mntdir" 4. On machine2, "ls /mntdir" Actual Results: list file as "str??g?f?lename". Expected Results: list file as "sträñgêfìlename". (Show accentuated characters). Additional info: As smbclient forks fine this way, smbmount should use the configuration character set conversion by default rather than performing no conversion at all. I cannot configure "dos charset = UTF-8" on this LAN because some other (old) machines do not support it...