This bug was fixed in the package ntfs-3g - 1:2009.2.1-0ubuntu1
---------------
ntfs-3g (1:2009.2.1-0ubuntu1) jaunty; urgency=low
* New upstream version:
- The 'recover' and 'norecover' mount options were introduced.
The former option will casue the driver to recover and repair a
corrupted or inconsistent NTFS volume if it's possible. The
default behaviour is 'recover' (fixes LP: #175503).
- The user extended attribute namespace is supported by default.
- A volume having unclean journal file is recovered and mounted by
default. The 'norecover' mount option can disable this.
* Updated due to SO version bump:
- debian/control, debian/rules, libntfs-3g49.docs,
libntfs-3g49.install, libntfs-3g49-udeb.install,
libntfs-3g-dev.links, ntfs-3g.links
* debian/changes/Changelog:
- Updated to document new upstream changes.
* debian/25-ntfs-3g-policy.fdi:
- Updated to expose new 'recover' and 'norecover' options via HAL.
-- Chris Coulson <[email protected]> Sun, 15 Feb 2009
20:15:24 +0000
** Changed in: ntfs-3g (Ubuntu Jaunty)
Status: Triaged => Fix Released
--
User-friendly automounting of ntfs partitions with an unclean logfile
https://bugs.launchpad.net/bugs/175503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
