You are not logged in.
Pages: 1
Ever since the "todo: have to rethink extra options" error started showing up on NTFS-3G, I've been using the /usr/share/hal/fdi/policy/10osvendor/20-ntfs-config-write-policy.fdi fix found at <http://bbs.archlinux.org/viewtopic.php?id=42070> (fifth post down, by Pilli).
That would allow me to mount external NTFS partitions, and by changing the contents of /sbin/mount.ntfs-3g to
#!/bin/bash
/bin/ntfs-3g $1 $2 -o locale=en_GB.UTF-8
and making it executable, I was able to restore UTF-8 support.
On a new Arch install today, I tried mounting my external NTFS drive without using the fix shown at the top of this post. I was overjoyed to find that it mounted, as well as an internal NTFS drive. However, I noticed I did not have UTF-8 support. I tried using the UTF-8 fix shown above but it seems it does not work now. Does anyone know how to restore UTF-8 support with the new NTFS-3G package?
Last edited by tony5429 (2008-10-18 22:16:01)
Offline
Hrm... I tried using the first fix with the second like I always have and it solved the problem. And now I can mount internal NTFS partitions
Offline
yeah, I came up with the same idea.. but had to search the forum to figure out that I had a f*ckin' typo in my script!
anyway, thank you!
Offline
the fix from the first post in this topic worked for me fo far
now when i use this fix, and try to mount a disk there's "unknown error"
christ it's an outrage the hal option doesn't get parsed like it's supposed to after all this time!!
how to make hal automount a ntfs-3g drive with utf-8 locale?
Last edited by _saiko (2008-10-27 23:52:43)
cat.7 - where crosstalk is not an issue anymore :'(
Offline
no one?
i can't believe nobody is interested in this ...
cat.7 - where crosstalk is not an issue anymore :'(
Offline
Pages: 1