gnome-mount actually replace pmount, and so it use a different method.
Basically, gnome-mount support ntfs-3g, as soon as you tell hal to use ntfs-3g for all ntfs device. This can be done by an .fdi file.
If you install my modified pmount package (even if you don't need pmount anymore), you get this kind of file, and it's probably why it works automatically.
The problem is that, ntfs-3g use a different local option than the kernel driver.
- With the kernel driver, a simple "utf8" is enough, and this is what do gnome-mount
- ntfs-3g use a "local=××_××.××" option (ex : en_US.utf8, fr_FR.utf8), and so this option may change with your configuration.
pmount set the local in the program, so you can get the local by calling setlocale( LC_ALL, "" ) and setting it for ntfs-3g. But as far as i know, gnome-mount use a config file, so setting automatically the local option is a bit tricky.
Any idea martin ? I don't run yet feisty, so i can't really investigate the problem.
Hi,
gnome-mount actually replace pmount, and so it use a different method.
Basically, gnome-mount support ntfs-3g, as soon as you tell hal to use ntfs-3g for all ntfs device. This can be done by an .fdi file.
If you install my modified pmount package (even if you don't need pmount anymore), you get this kind of file, and it's probably why it works automatically.
The problem is that, ntfs-3g use a different local option than the kernel driver.
- With the kernel driver, a simple "utf8" is enough, and this is what do gnome-mount
- ntfs-3g use a "local=××_××.××" option (ex : en_US.utf8, fr_FR.utf8), and so this option may change with your configuration.
pmount set the local in the program, so you can get the local by calling setlocale( LC_ALL, "" ) and setting it for ntfs-3g. But as far as i know, gnome-mount use a config file, so setting automatically the local option is a bit tricky.
Any idea martin ? I don't run yet feisty, so i can't really investigate the problem.