ports/114198: Make option for using ntfs-3g instead of kernel ntfs

[Rechistov Grigory]

>Number:         114198
>Category:       ports
>Synopsis:       Make option for using ntfs-3g instead of kernel ntfs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 01 21:20:16 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Rechistov Grigory
>Release:        6.2-STABLE
>Organization:
>Environment:
FreeBSD ip82-180.private.rt.mipt.ru 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu Jun  7 01:06:01 UTC 2007     root at ip82-180.private.rt.mipt.ru:/usr/obj/usr/src/sys/DELL_v8  i386

>Description:
At present, FUSE-powered ntfs-3g driver for read-write access to NTFS volumes is quite stable and has a good performance. But HAL has no option to use it. I see that many linux distros have already made incorporated the support of ntfs-3g (e.g. see http://bugs.archlinux.org/task/6525 , http://gentoo-wiki.com/HOWTO_NTFS_write_with_ntfs-3g ), unfortunately they use udev of their own scripts so this is unportable for now. Some changes in hal-storage-mount and .fdi files are required to assure it will work under FreeBSD, I suppose.

It would be great if autodetection of ntfs-3g installed and switching to using it would be availible. Or, a user should decide whether to use ntfs-3g, and to make hal depend on fuse and ntfs-3g ports, or to leave present behaviour at the compilation time.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: