Request: explain motivation and goals for fuser compared to other rust FUSE libs (e.g. fuse-rs) about fuser

[cberner]

fuser is a fork of fuse-rs. I forked it because fuse-rs doesn't seem to be actively developed anymore. My main goal is to add support for more of the libfuse feature set. I use fuser for a distributed filesystem (fleetfs) myself.

[cberner]

Mostly as a side project for fun, but it might turn into something more real. My main reason is that both of those are hard to operate and scale

[happybeing]

Thanks, good news on both counts. I'm new to Rust which makes it hard to evaluate things - I will do some testing with fuser and polyfuse. The latter was suggested to me because it uses async but I don't know how important that is or what other differences there are. Initially I just need to use this to create a mount for a proof of concept, so we can always switch layer on. The project is safenetwork.tech / https://github.com/maidsafe and I'm helping someone there who is working on using CRDTs to allow a client to mount a replica filesystem that will automatically sync across devices.

fleetfs looks interesting - is it like one big filesystem like IPFS or something else?

[cberner]

Cool, sounds like a neat project. I'll probably add async support to fuser at some point. It hasn't been too important for me yet though.

Fleetfs is more like GlusterFS or Lustre

[happybeing]

Thanks, new area to me. What's the reason for fleetfs?

For ref:

• https://en.m.wikipedia.org/wiki/Gluster#GlusterFS
• https://en.m.wikipedia.org/wiki/Lustre_(file_system)