Hi,
This problem is common when there is no real device behind the file
system. When you eject a file system from Finder, the 'fsname' specified
(see http://code.google.com/p/macfuse/wiki/OPTIONS ) is taken into
account, and if you have specified an actual device as fsname,
/dev/diskXsY, then Finder behaves correctly and asks you whether you
want to eject other mounted partitions on /dev/diskX.
If the 'fsname' is not recognized by Finder, then it seems to group it
together with all other 'local' mounted devices that don't have a
recognizable 'fsname'. So if you have two 'local' mounts with no valid
fsname, then it will notify you about the others when unmounting.
I haven't found a workaround for this, but maybe it's possible using
some other specially formatted fsname.
The 'local' option is not really meant to be used with file systems
where there is no underlying physical device (some would argue it's not
suitable for MacFUSE mounted file systems at all, but I wouldn't agree),
so I guess you'll have to live with these issues if you're going to
continue using the 'local' option.
- Erik
On 2010-04-14 06:13, Jim wrote:
I have two MacFuse file systems which are mounted simultaneously with
the local flag set. When I try to eject one of them I get the Finder
Warning (10.6.x) that there are two partitions on the same device
along with the offer to eject them all. This isn't desired behavior.
It looks like maybe the Finder is using the mountFrom location and
just looking to see if they are the same except for the last digits.
Since mount shows the mountFrom as m...@fuse0 and m...@fuse1 this is
going to be a problem.
Has anyone else looked into why this is going on?
Thanks,
Jim
--
You received this message because you are subscribed to the Google Groups
"MacFUSE" 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?hl=en.
