I'd still encourage you to at least test with the new version of MacFUSE Core. I really do mean that I'll phase out 0.4.0 very soon, so making *new features* of your package work with it may not be the best use of your time.
On Oct 9, 11:14 am, unsound <[EMAIL PROTECTED]> wrote: > I'm 99,9% sure that the volicon option gets passed to mount_fuse (the > remaining 0.01% should be the possibility that my RAM is corrupting > the data just before mount_fuse gets called ;>). I was just wondering > if that is the only thing that is needed for it to take effect, or if > something else is required. > Anyway, I can't use the prerelease version for my package, as I'm not > including MacFUSE but linking to the official site. > > Also, of course, thanks for the great contribution to the Mac > community that MacFUSE is. I hope the new prerelease version reaches > official status soon. > > - Erik > > On Oct 9, 7:00 pm, Amit Singh <[EMAIL PROTECTED]> wrote: > > > I'd almost certainly be deprecating any and all old versions of > > MacFUSE Core "real soon now", so you should base all future work on > > the prereleases--MacFUSE 0.4.0 is on its way out so its "official" > > status won't hold for long. > > > I haven't played much with ntfs-3g, so I don't know what might be > > happening that the option isn't doing what it should. Since it works > > for you for another file system, my guess would be that something is > > filtering it out before it can be processed in the library. > > > BTW, in the prerelease version, "-o volicon=PATH" is a shortcut for "- > > o modules=volicon,iconpath=PATH". > > > Amit > > > unsound wrote: > > > Hello group.. > > > > I'm maintaining a package for ntfs-3g on Mac OS X > > > (http://macntfs-3g.blogspot.com > > > ), and I'm trying to make ntfs-3g work with the volicon option, but > > > I'm out of luck it seems. > > > I have successfully got volicon to work with another file system > > > module (my own rarfs_fuse), but passing the volicon option to ntfs-3g > > > doesn't seem to make much happen. > > > > With my rarfs_fuse, I'm using the "lazy" fuse_main method of starting > > > up the file system. ntfs-3g on the other hand does some more detailed > > > intialization, but I have concluded that it _at least_ sends the > > > volicon mount option to fuse_mount. Is there anything else it should > > > do to enable the volicon option? > > > > I'm really confused because options like debug and volname get through > > > to MacFUSE without issues, but not volicon. > > > > I'm using the official 0.4.0 package btw. No prerelease here. Also the > > > ntfs-3g version is 1.1004 if you'd want to check that code. > > > > - Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
