You won't ever see the source of where an operation is coming from because a copy/move is an that application opening one location, reading bits into memory and writing it back at the location you just received. This isn't a MacFUSE problem it is how most VFS layers work, while we might logically think we're copying the VFS layer only sees an open on one file for reading and an open on another file for writing.
Cheers, Sam Moffatt http://pasamio.id.au On Tue, Mar 15, 2011 at 4:48 PM, Joel Reymont <[email protected]> wrote: > Assume I have a file system mounted on /tmp, LoopbackFS, basically. > It seems that none of the MacFUSE callbacks provide me with the source path > of a file being moved, copied, etc. > Does this have to do with having a locally mounted filesystem? > How do I obtain the source path in LoopbackFS? > Thanks, Joel > > -- > 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. > -- 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.
