Bug 144600
Summary: | Missing UTF-8 support on vfat devices mounted via HAL/gnome-volume-manager | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dominik Jungo <dominik.jungo> |
Component: | hal | Assignee: | David Zeuthen <davidz> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | davidz, gajownik, mclasen |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.4.6 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-01-20 18:51:05 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: |
Description
Dominik Jungo
2005-01-09 10:58:29 UTC
DaveJ, per our discussion on IRC yesterday, any chance we can change the kernel such that the default iocharset for vfat is UTF-8? If no, please reassign back to hal and I'll deal with it from userspace. I've been thinking about this. Basically if it sits in hal, or in kernel package, its going to be a patch that isn't going to go upstream, ever. However, from a maintainence point of view, the upstream vfat code does change quite regularly, making it a possibility that the patch would need redoing every time I rebase. hal should be less susceptable to such regular changes no? Yeah, it should be painless to maintain in hal; I'll take the bug back :-) This is fixed in hal-0.4.6 which will be in Rawhide and FC3 updates soon. I may be wrong, but you should use utf8 option, not iocharset=utf8. Please refer to /usr/share/doc/kernel-doc-2.6.10/Documentation/filesystems/vfat.txt |