![]() ![]() ![]() So to summarize: remove local, add streams_interface=openxattr are the changes to be made to the existing patch. Since I haven't dealt with ntfs streams yet, I cannot say anything about them. So you (or Tuxera) suggest(s) adding streams_interface=openxattr to the mount options? If so, let's do it. I am wondering whether EAs are useable for most people though, I'm not used to working with them nor alternate streams. The docs seem to suggest that unless that is used, auto_xattr would not work as expected. Replying to Tuxera's documentation regarding EAs suggests that if you use auto_xattr, then you could expose streams through streams_interface=openxattr. But at least it can be shown on the desktop as a remote drive, which is better than nothing. Unfortunately as per macfuse faq 4.3, there is no way to show up the volume in finder's sidebar then. This might not what most people want, no? There is however a suggestion to make the Finder show networked volumes, perhaps this should be notified to the user during install. Doing so would cause creation of various OS X-specific directories, for instance, just because you mounted the volume. Replying to patch file seems to be fine however, I don't think we should automatically set local as per question 4.1 in the MacFUSE FAQ. I could think of this solution provided as port-variants of ntfs-3g ("+auto_mount=enables auto_mount by ntfs-3g", "+show_in_finder=shows mounts in finder BUT disables ntfs xattr") I'm now using a special "mount_ntfs"-shell-script with the provided volname-patch - and my ntfs-automounts show up in finder.Īnyone with some knowledge about filesystems/ntfs-3g/macfuse can say something this approach? Is "streams_interface=none" really needed? See that directed me to the solution (and also why i think "streams_interface=none" should be used - but i have to little knowledge of ntfs(-3g) and macfuse if it is really necessary) because of auto_xattr, i think the extended attributes of ntfs-3g should be disabled by "-o streams_interface=none" (which is obviously a drawback if you need them).you have to use "-o local,auto_xattr" in addition to the patch to show the volume in finder.the patch above is working: the volname-option is successfully appended to the mount options.will open another ticket for update)Īlright, i got it to work. (so there's an updated version of ntfs-3g out, too: 2010.10.2. Maybe this could be adapted by/added to the ntfs-3g macports version so the volumes show up in finder?ĭon't know whether they use a special macfuse or the "volname"-option is standard.įor reference, the latest source of tuxera ntfs-3g for mac can be found here: : #endif /* defined(_APPLE_) || defined(_DARWIN_) */ ![]() If (strappend(&parsed_options, scrubbed_vol_name)) If (strappend(&parsed_options, ",volname=")) * would interfere with FUSE argument delimiters. * Scrub all ',' characters from the volume name since they Size_t vol_name_len = strlen(ctx->vol->vol_name) Ĭalloc(1, sizeof(char) * (vol_name_len + 1)) * 'volname' option, making the volume name appear in Finder. * If the volume has a volume name, then append the MacFUSE-specific #if defined(_APPLE_) || defined(_DARWIN_) Since there is the ntfs-3g-version for mac from tuxera ( ), where the volumes show up in finder, i searched in their code a little bit and found this in "ntfs-3g.c": This makes ntfs-3g automount my ntfs-volumes. Ln -s /opt/local/bin/ntfs-3g /sbin/mount_ntfs Mv /sbin/mount_ntfs /sbin/mount_ntfs.orig I just got ntfs-3g to automount my volumes by replacing "/sbin/mount_ntfs" by "ntfs-3g"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |