Hi Adam, ntfs-3g 2009.1.1 is now in Ubuntu. The files can be found in these locations:
https://launchpad.net/ubuntu/jaunty/+source/ntfs-3g/1:2009.1.1-0ubuntu1/+files/ntfs-3g_2009.1.1.orig.tar.gz https://launchpad.net/ubuntu/jaunty/+source/ntfs-3g/1:2009.1.1-0ubuntu1/+files/ntfs-3g_2009.1.1-0ubuntu1.diff.gz https://launchpad.net/ubuntu/jaunty/+source/ntfs-3g/1:2009.1.1-0ubuntu1/+files/ntfs-3g_2009.1.1-0ubuntu1.dsc It was a quite straightforward update (SO version bump + changelog), but I've had to make a change to the HAL fdi file that was introduced in to Debian recently, and you might be interested in the changes to this. The history of this is documented in Ubuntu bug 300443 [1]. Basically, HAL changed recently (0.5.12) so that when you mount a filesystem now, the filesystem driver has to be specified in the properties "volume.fstype" or "volume.fstype.alternative" for the particular volume. This constraint didn't seem to exist with HAL 0.5.11, so that we could mount volumes where "volume.fstype=ntfs" with the ntfs-3g driver. The HAL fdi file (20-ntfs-2g-policy.fdi) introduced in to Debian changed "volume.fstype" to "ntfs-3g" for removable NTFS volumes only. This meant that once HAL had been updated to the new version, users could no longer mount internal volumes with the ntfs-3g driver (but they could mount removable volumes ok). What I have done with the FDI file is made the ntfs-3g driver as the default for all NTFS volumes, but allowed the user to mount volumes with the old read-only ntfs driver if they want too. I also had to rename the FDI file from "20-ntfs-3g-policy.fdi" to "25-ntfs-3g-policy.fdi", as it is important that these rules are applied after "20-storage-methods.fdi". Hope all this makes sense! Regards Chris [1] - https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/300443
signature.asc
Description: This is a digitally signed message part
