On Sep 8, 9:50 am, Chris Boone <[EMAIL PROTECTED]> wrote: > Is there any reason O_NONBLOCK is not being passed > to open on macfuse? Linux fuse passes it without > problem.
Yes, there is a reason. MacFUSE provides (for the most part) the FUSE *API*, but the kernel implementation is totally different from that of Linux FUSE. Hardly surprising--the two OSs have quite different architectures. Since the FUSE API was originally conceived and implemented on Linux, there are some aspects/side effects that are difficult/impossible for MacFUSE to replicate on OS X. Part of the reason is that MacFUSE is a kernel extension, so it only has access to the programming interfaces and data structures exported by the kernel. The open() case is an interesting problem, which MacFUSE solves via a compromise. I suggest reading: http://code.google.com/p/macfuse/issues/detail?id=132 http://code.google.com/p/macfuse/issues/detail?id=133 Let me know if you have further questions. 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 -~----------~----~----~----~------~----~------~--~---
