> Will setting the flag right before fuse_main() do the trick, or does > it absolutely HAVE to be after mounting but before DiskArb > notification? On that note, can/should I set the flag and notify > DiskArb within the fuse initialize callback? I would like to somehow > integrate the icon into the FUSE mounting process, not as an after-the- > fact routine.
Unfortunately, you cannot. Before the FS is mounted, all /Volumes/ Test's metadata is stored in root HFS+ filesystem because /Volumes/ Test is an ordinary directory. When you mount your FS, the /Volumes/ Test becomes a root node of your FS. All attributes set for HFS+ node are now discarded till unmount. Apple provides a mechanism for FSes with no attributes support, so setting the attributes right after mounting the FS does the thing. The sample I've posted should be used with -onoping_diskarb option. In that case the sequence is the following: 1) Call fuse_main(). The mount point is being created but not shown in Fider (since no noping_diskarb was specified). 2) Call IconizeAndShowVfs() from the sample (from another thread, do not forget to wait until FS actually mounts). It sets the corresponding attributes and shows your FS in finder. The alternative is to include something similiar to IconizeAndShowVfs() in FUSE core just before ping_diskarb implementation (try searching FUSE source for DiskArbDiskAppearedWithMountpointPing_auto). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
