Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    Compiled From Sources

HAL 0.5.12 will allow specifying alternative filesystem drivers when mounting storage devices. This was done to standardize integration of drivers like NTFS-3G, because distributors were using hacks to integrate it.

The additions to the HAL spec can be found here (look for "volume.fstype.alternative"):
http://cgit.freedesktop.org/~dkukawka/hal/tree/doc/spec/hal-spec-properties.xml

I've made a patch against kdebase 3.5.10 that adds support for these options. In particular:
- MediaManager understands the HAL options. By default, it will honor the preferred driver setting in HAL. The dcop interface is expanded so that the list of available drivers and their mount options can be retrieved, and a new driver can be selected.
- The properties dialog plugin is updated to allow choosing the driver.

The properties dialog had some non-trivial changes because supported options differ between drivers. However both components will work even if the other component is old.

I've been testing it, but more people should before I commit it. You can test it without trying out the alternative drivers feature, just to look for regressions.

To test the new feature, you will first have to:
- install ntfs-3g
- make sure your distribution doesn't link /sbin/mount.ntfs to /sbin/mount.ntfs-3g
- if present, remove the currently installed ntfs-3g fdi file that changes the "ntfs" fstype to "ntfs-3g", which may reside in /etc/hal/fdi/policy
- install a new fdi file to /etc/hal/fdi/policy that registers the ntfs-3g driver in HAL (attached)

After installing the patched version, restart HAL and KDE and when you click on a ntfs drive under media:/ it should mount using ntfs-3g.
Be aware though, the ntfs-3g mount may fail because of issues with HAL:
- The error "TODO: Have to rethink extra options" (http://bugs.freedesktop.org/show_bug.cgi?id=17684)
- The error "wrong fs type, bad option, ..."; that's because you don't use the latest HAL. Try removing the "locale" option
  from the fdi file, but beware this will supress displaying and creating files with non-ascii names (and cause data loss when backing up and deleting folders)

You can choose Properties on the device, and in the Mounting section you should see "Filesystem: ntfs", and be able to choose the filesystem driver (e.g. ntfs and ntfs-3g). "ntfs" must work. Try playing with the options and look for any regressions, also with non-ntfs drives.