On Oct 30, 2007, at 2:09 AM, David A. Lyons wrote: > The part about launching /sbin/mount strikes me as odd. What happens > if you don't do that, but instead just invoke your MacFUSE executable > (passing in the /dev/diskN mountpoint, and other parameters such as - > ovolname="foo")? I think the mounting is taken care of for you. > > [Apologies if I'm just confused - please set me straight. I'm working > on a MacFUSE filesystem for an old block-based format. I haven't yet > tried to do my disk-arb integration, but I've looked briefly at how > that part of ntfs-3g.fs is set up.]
Turns out that the mount codepath in SAI_udf_util is no longer in use (This FS descends from code originally written for 10.3, and that codepath was in use there). What is happening now (under 10.4) is that both diskutil and MacFuse are calling DiskArbDiskAppearedWithMountpointPing_auto for the same volume. It doesn't appear to be a problem if both calls provide the same information, but you have to be very careful when setting up MacFuse in order to ensure that things work correctly. My experience is that the key parameters to fuse_main are -ofsname=/ dev/diskN, -oallow_other and -olocal. -ofsname provides f_mntfromname to statfs. -oallow_other gives users besides root access to the FS. -olocal sets the MNT_LOCAL flag in the vfs mountpoint. That said, I still haven't gotten things to work quite right - Finder seems to be ignoring (or failing) the Disk Appeared event, and the mount point is not being deleted properly when the volume is unmounted. Ron Aldrich Software Architects, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
