Manu

Yes. IIRC those mount options aren't available on every platform/FUSE implementation. So we made it optional.

How can we solve this? I prefer keeping this an option. Are there 2 options in total? If the text is bad, let's improve the text.

Currently we have 2 options: 1. Mount with the same permissions as original files. This works well on the same computer. 2. Override user and permissions. This is needed when...

Hmm. `alllow_other` seems to do something different on macFUSE. This talks about permissions **after** mounting the volume. > With `allow_other`, the volume will be accessible normally to all users. [1](https://raw.githubusercontent.com/wiki/osxfuse/osxfuse/Mount-options.md)...

There is an option to override some permissions in the _Misc_ tab. This works, if normal perms are used, but not for ACLs in some cases (Synology).

Syno is a special case. They have standard perms all set to deny and only use ACLs.

You can filter or view to pull a single file. Borgmatic even lets you search for a filename. Else you need a Linux machine, because the ACL stuff won't work...

How would this look in detail? Like a status message with the path when there is an error? Are we logging errors currently? Would logging only be enough?

> `pkg_resources.DistributionNotFound: The 'pyparsing>=2.0.2' distribution was not found and is required by packaging` Looks like a missing PyPi package. Maybe something changed there. Need to compare it with the official...

What's the current best practice for error handling? My goal is to find the most meaningful error on why something went wrong. Currently I use this as "wrapper": (lightly edited)...