On Apr 17, 6:17 am, Forest Bond <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I know direct_io is frowned upon in the MacFUSE camp, but I was hoping to get

Whatever gave you that impression? And I don't know this "camp" that
you speak of!

> 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.)

A file system cannot "disable" mmap() on Mac OS X. However, when you
use direct_io, mmap() will not work, as should be the case, but you
won't get to know that it doesn't work until you try to read/write
that memory--at that point, you'll get a fault. Unfortunate, but like
I said, that's how it is on Mac OS X. Without changing the kernel
itself, this can't be improved.

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

See above.

> 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 
> fromhttp://fuse.sourceforge.net, rather than installing libfuse from MacFUSE. 
>  Could
> this be contributing to the issues that I am seeing?

I am not very familiar with what MacPorts is doing. It's also odd and
incorrect if they call it a "fusefs port". MacFUSE != Linux FUSE. The
kext is a completely different implementation from Linux fusefs; they
just happen to export similar (not even same) user-level interfaces.
The kext's behavior, its nuances, subtleties, features, limitations
are *very* different from Linux fusefs, and are often dictated by
what's possible/impossible and needed/not needed on Mac OS X. "fusefs
port" incorrectly implies otherwise. And libfuse != MacFUSE either.
MacFUSE consists of a kernel extension (fusefs.kext), a user-space
library (libfuse.dylib), programming headers, and a bunch of support
tools/scripts.

I don't know if this is contributing to any of your problems, but the
only binary distribution I can support is the one I make available.

Amit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"macfuse-devel" group.
To post to this group, send email to macfuse-devel@googlegroups.com
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