Bump to stable release of ntfs-3g. Major features are: # New: Built-in, transparent UTF-8 conversion support. This solves all the problems, described here, and even more with hidden and inaccessible filenames having national characters. # Change: The 'locale=' mount option is not used anymore for filename characterset conversion. Instead filenames are always converted to UTF-8. So there is no longer need for valid_options line in the bundled hal policy file. Renaming ebuild does the job. I'm attaching the new fdi file. Reproducible: Always
Created attachment 179421 [details] 10-ntfs3g.fdi
Created attachment 179424 [details] 10-ntfs3g.fdi Oops, attached testing version by accident
This is quite a major update: * Full core functionality implemented: full index operations, unlimited file and directory creation and transparent UTF-8 support. Moreover shared writable mmap and NFS support via the FUSE kernel module. * Lightweight, integrated FUSE: easier deployment, faster release cycles, smaller footprint, less external dependencies. * New, modern build system. * Strong resistance to file system corruptions and hardware flaws. * POSIX file system test suite ported, extended and maintained. * Advanced NTFS-3G: full ownership, permissions, POSIX ACL, junction points support, access to internal NTFS data, POSIX compliance. http://pagesperso-orange.fr/b.andre/advanced-ntfs-3g.html * Significant performance improvements. * High-performance NTFS-3G driver for embedded devices. Looks good. But I'm not sure if the current ebuild is fully suitable? The changelog mentions a built-in FUSE. Is this on by default? I suspect most people use the system's FUSE, but not sure.
sys-fs/ntfs3g-2009.2.1 is now in portage (released today).
