Hi, I know direct_io is frowned upon in the MacFUSE camp, but I was hoping to get some clarification as to whether or not mmap is disabled by using direct_io.
(I think have to use direct_io, anyway, so this is not the only reason for turning it on.) In the current development version [1] of pytagsfs [2], I have a test for whether mmap fails or not (initialization of the mmap should fail). It does what it should on my Linux machine, but I'm having a hard time with MacFUSE. I'm using MacPorts to install dependencies, but I have replaced the MacPorts fusefs-1.1 port with a fusefs-1.3 port (I modified the port file and created a new tarball). However, I noticed that MacPorts has libfuse from http://fuse.sourceforge.net, rather than installing libfuse from MacFUSE. Could this be contributing to the issues that I am seeing? BTW, I did turn off direct_io for testing purposes, but I can't seem to avoid inappropriate caching under those circumstances. In any case, I suspect disabling direct_io would lead to other issues due to semantic quirks of the FS that I'd rather not explain in their entirety here. ;) [1] https://code.launchpad.net/~forest-alittletooquiet/pytagsfs/dev [2] http://www.pytagsfs.org Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.pytagsfs.org
signature.asc
Description: Digital signature
