> 1) The disk icon is incorrect, and eject messages are not sent to the  
> disk drive when the volume is ejected.  How do I indicate to MacFuse  
> that the volume is associated with a particular disk device?

Incorrect how? What should it be? Do you have a custom volume icon
that you want to show up on the Desktop? If so, you should look into
the 'volicon' mount-time option.

MacFUSE doesn't care where your /actual/ backing storage is--that's
entirely up to the user-space program implementing the file system.
Sounds like one option you have would be to implement the destroy
method in your file system and cause it to eject the physical disc.

> 2) The volume cannot be renamed.  Is there a way to support this?

The FUSE API has no concept of volume names (and hence volume
renaming). Even though MacFUSE has numerous things that are different
from, or in addition to what the Linux implementation has, volume
renaming is not one of them.

> 3) Cluster mapped I/O is not supported.  Will implementing bmap  
> resolve this?  Is there a sample anywhere which implements bmap?

MacFUSE doesn't support bmap. On Linux, bmap is an inode-level
operation that the Linux vfs calls to map a logical block offset to a
physical block number. It's used (or was used the last I saw) by the
swapper on Linux, but its use is deprecated there. What exactly do you
mean by "not supported"? What's your use case that you want to work?

> 4) Named attributes are not supported (setxattr, etc...).  Are these  
> methods used under Mac OS X 10.4?

Not supported where/how? Both Mac OS X (yes, including 10.4) and
MacFUSE support extended attributes (setxattr, etc.).

Amit


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to