From looking to sources it looks to me like all of these library ports communicaticate with kernel using similar interface as Linux = some device file descriptor (/dev/fuse).
OK, in that case your option number 3 (kernel interface messages and a dedicated FUSE server) is not so out of place as I previously thought. But you still won't be able to use the vanilla libfuse in HelenOS, because there will be no kernel counterpart to talk to. You'd have to redirect the kernel interface messages to the FUSE server, thus altering the libfuse substantially.
Therefore I still consider the option 2 (low-level API) to be a better joining point. Nobody should care that the communication between the FUSE layer and the VFS layer is using different messages than in Linux. The point is to preserve the compatibility between the FUSE layer and the FUSE file system end-providers.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
