polyfuse
polyfuse copied to clipboard
ubnt-intrepid
A FUSE (Filesystem in Userspace) library for Rust
This change fixes the issue building against musl. There were mainly 2 issues that prevented me from building this against musl - the type of `msg_controllen` for both libc and...
When using the hello example I was unable to list the contents of the created filesystem due to a missing OpenDir request handler mapping.
This addresses issue #150 that I raised by adding the missing OpenDir request mapping. It also adds a warn! message to stdout when an unmapped operation is attempted against the...
The crate builds now, but the passthrough example and the tests do not.
commit 1 replace unsafe `set_len` with a new struct SubVec Here all that is needed is restricted access only the data tha is actually been read. This extra implementation allows...
... such as ``` Error: too short control message length ``` It was reported in https://github.com/ubnt-intrepid/polyfuse/issues/83#issuecomment-770389984.
Does it depend on availablity of `libfuse` library or C code in general? Does it talk directly to `/dev/fuse` after mounting?
`cargo run -p polyfuse-example-passthrough -- -s junk mnt` and in other terminal ``` ➜ polyfuse git:(master) ls -1 junk | wc -l 0 ➜ polyfuse git:(master) ls -1 mnt |...
According to libfuse: * When `FUSE_SPLICE_READ` flag is set (and `write_buf` is supplied), it [attempts to `splice` at first](https://github.com/libfuse/libfuse/blob/fuse-3.9.0/lib/fuse_lowlevel.c#L2769) and transfer a request message into the pipe. * If the...
The current library implementation focuses on porting the libfuse's low-level API (described in `fuse_lowlevel.h`). and the convenience from the perspective of the user's side of the filesystem implementors is not...
Metadata
Owner
Metadata
A FUSE (Filesystem in Userspace) library for Rust