Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: clarify user_id vs uid for fuse #5958

Merged
merged 6 commits into from Aug 25, 2021
Merged

docs: clarify user_id vs uid for fuse #5958

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
563da00
docs: clarify user_id vs uid for fuse
remyabel2 Aug 18, 2021
4e26e17
Revert "docs: clarify user_id vs uid for fuse"
remyabel2 Aug 19, 2021
de3652c
Address review comments.
remyabel2 Aug 19, 2021
128cccd
Add additional clarity.
remyabel2 Aug 20, 2021
324c99a
Fix typos. Add clarity.
remyabel2 Aug 24, 2021
5d6e9c8
Fix text width.
remyabel2 Aug 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion docs/usage/mount.rst.inc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,16 @@ To allow a regular user to use fstab entries, add the ``user`` option:

For FUSE configuration and mount options, see the mount.fuse(8) manual page.

The man page references ``user_id`` and ``uid``, which are not the same thing.
``user_id`` is set by libfuse (or the filesystem) and contains the effective
user id of the mount owner. ``uid`` on the other hand refers to the actual
owner of the file. While you can pass ``uid`` as a mount option to borg to
change the owner of all of the files (i.e, ``borg mount -o uid=1000,gid=1000``)
it is recommended you use the ``--numeric-ids`` switch instead.

``numeric-ids`` will use the ``uid``s and ``gid``s from the archive instead of
attempting to map username and groupnames to local ids.

This conversation was marked as resolved.
Show resolved Hide resolved
Additional mount options supported by borg:

- versions: when used with a repository mount, this gives a merged, versioned
Expand All @@ -145,4 +155,4 @@ Unmounting in these cases could cause an active rsync or similar process
to unintentionally delete data.

When running in the foreground ^C/SIGINT unmounts cleanly, but other
signals or crashes do not.
signals or crashes do not.