str4d

Looks like the UX regression is due to https://github.com/cberner/fuser/pull/122, which I don't entirely understand because I can't find a canonical reference that specifies the requirement of either `allow_other` or `allow_root`.

Aha, this is upstream issue https://github.com/libfuse/libfuse/issues/586. Perhaps this worked for libfuse2 but doesn't for libfuse3. I think the fix is to add `allow_root`, so that we widen access just enough...

Oh, except that `fuser` implements `allow_root` itself, by enabling `allow_other` and then restricting to `owner+root`. So we can't use `auto_unmount` without requiring `rage-mount` users to add `user_allow_other` to their `/etc/fuse.conf`,...

> Thanks for all the comments. > > I'm pretty sure `rage-mount` worked for me the last time I updated the PR. Maybe it was just me not using `auto_unmount`....

> I'd say we keep note in the README about the behavior and reference it to the upstream issue. It's unlikely to get fixed soon. I think what I want...

> I think what I want to do is add `allow_root` to keep the required access minimal, try and detect if the mount fails for this reason, and in that...

Once https://github.com/cberner/fuser/pull/218 is merged and released, the "Error: Success" message will be replaced by "Error: Unknown Error" which is an improvement, but still not great. The blocker on handling this...

I figured out how to retain the current behaviour: by using `spawn_mount` instead of `mount`, and then triggering a channel from both a Ctrl-C handler and `FilesystemMT::destroy`, we can always...

Actually, I'm going to go ahead and merge this, to unblock other PRs. If you encounter any problems, please open new issues. And thank you for the PR!

After discussion at HACS 2020, it is likely that we will create a plugin system where the main implementations communicate with separate plugin binaries via a standard I/O interface. I'm...