Have you tried testing with the reference (loopback) file system? I just did, and it does work for me, at least on Leopard.
That said, exchangedata support has not been tested thoroughly, so sure, there might be issues. Amit On Jul 23, 12:46 pm, "M. J. Fromberger" <[email protected]> wrote: > Greetings, all, > > I have written a filesystem driver for MacFUSE in which I wish to > support the exchangedata(2) operation. I have supplied an "exchange" > callback in the fuse_operations structure, but as far as I can tell, > this callback is not being invoked by MacFUSE. I am developing > against MacFUSE 2.1.4 on MacOS 10.4.11, though I seem to have the same > problem when I test under MacOS 10.5. > > For development purposes, I log each callback received by my driver. > The fs_usage tool reports that my test program issues the exchangedata > () call, and receives a reply of ENOTSUP (errno 45); however, I never > see a corresponding invocation of "exchange" in my driver's log. My > hypothesis is that MacFUSE is reporting ENOTSUP silently, and ignoring > the available callback. > > Does MacFUSE require special compile-time or runtime options to permit > this callback to be received? Or, has anyone else experienced a > similar problem, and have you found a workaround? > > Curious, > -M > > -- > Michael J. Fromberger <http://spinning-yarns.org/michael/> > > Computers save time like kudzu prevents soil erosion. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
