The read call is *eventually* handled by the operating system, but MacFUSE (or any other file system for that matter) does need to do a whole bunch of work to make named pipes and devices work. allow_other, allow_root, defer_permissions etc. have nothing to do with this.
As you can see in macfuse/core/10.5/fusefs/common/fuse_param.h: #define M_MACFUSE_ENABLE_FIFOFS 0 #define M_MACFUSE_ENABLE_SPECFS 0 That is, in the binary release of MacFUSE, I don't enable support for named pipes and devices. This is both because it can be a security concern and also because I've not tested this part much, so I consider it experimental. If you want to experiment, just change the define and recompile. Amit On Nov 30, 6:05 pm, "Jeff I. Ragland" <[EMAIL PROTECTED]> wrote: > Hello list, I'm testing the use of named pipes (FIFOs) > within macfuse. In my filesystem I've created a file that > reports itself as a FIFO, with permissions 0666. I can getattr > it without a problem but when I try to read or write to it I > get an Operation not permitted error. > > If I understand correctly the read call is being handled by > the OS and not by FUSE. But why am I getting the error? The > errno after the read is EPERM. > > From FUSE's point of view the trace is: > getattr > open > flush > release > > and they all return 0. > > I've also tried various combinations of allow_other, allow_root > and defer_permissions without any success. I use macfuse 1.1.1. > > Any ideas? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
