One note of caution:
Make sure that you install the fusefs-kmod 0.3.9.p1.20080208_5 port.
There is a known issue where the fusefs write buffer does not perform a writeback in a timely fashion. According to PR/122907, uncommitted data can remain in the buffer for as long as 15 minutes.
When a system shutdown is initiated, fusefs scrambles to commit data when partitions are hit with a umount command. Unfortunately, if there is too much data, it cannot be written in time before the system is halted. The result is lost data and/or lost files.
The patchlevel 5 fix introduces a safe mode in the rc.d shutdown script that makes sure that the fuse.ko module has been safely halted before allowing the rest of the system shutdown to continue. The module won't halt till the write buffers are empty, so it is a smart check.
The current pre-compiled package version (as of 12/12) is only patchlevel 2. If you have that version, manually unmounting your fusefs partitions before you halt is highly recommended.
Having said that, the patch does nothing to stop data loss in the event of a power failure or kernel panic. Also, the ntfs-3g daemon doesn't fully support journaling [yet], so your filesystem can be left in an inconsistent state afterward. I personally had to boot into XP and run "chkdsk /F" to repair the filesystem after my experience.
