fuse.md: Linux-related clarifications
Marcin Rataj committed
Apr 6, 2015 at 23:26 UTC
6903e631404520dadd9dbc10c334cd6294129930
1 file changed
+12
-5
docs/fuse.md
+12
-5
@@ -44,18 +44,22 @@ sudo chown <username>:<groupname> /etc/fuse.conf
44
45
## Troubleshooting
46
47
-### Getting `Permission denied` or `fusermount: user has no write access to mountpoint` error
47
+### Getting `Permission denied` or `fusermount: user has no write access to mountpoint` error in Linux
48
49
Verify that the config file can be read by your user:
50
```sh
51
-ls -l /etc/fuse.conf
51
+sudo ls -l /etc/fuse.conf
52
-rw-r----- 1 root fuse 216 Jan 2 2013 /etc/fuse.conf
53
```
54
-In most distributions group named `fuse` will be created during installation.
54
+In most distributions group named `fuse` will be created during installation. You can check with:
55
56
-If that is the case, just add your regular user to the `fuse` group:
56
```sh
58
-usermod -G fuse -a <username>
57
+sudo grep -q fuse /etc/group && echo fuse_group_present || echo fuse_group_missing
58
+```
59
+
60
+If group is present, just add your regular user to the `fuse` group:
61
+```sh
62
+sudo usermod -G fuse -a <username>
63
```
64
65
If not, create `fuse` group (add your regular user to it) and set necessary permissions, for example:
@@ -66,6 +70,9 @@ sudo chgrp fuse /ipfs /ipns
70
sudo chmod g+rw /ipfs /ipns
71
```
72
73
+Note that the use of `fuse` group is optional and may depend on your operating system.
74
+It is okay to use a different group as long as proper permissions are set for user running `ipfs mount` command.
75
+
76
### Mount command crashes and mountpoint gets stuck
77
78
```