basic fuse set up in readme or link to wiki

[ebuchman]

As far as I can tell, fuse is the only thing making this project non purely "go-gettable". Of course it's fine if you don't want to mount, but everyone wants to mount, and I can see this being a staple problem for new users.

[whyrusleeping]

Agreed 150%. And a lot of the problem is that a lot of fuse packages are actually broken by default. Fuse is meant to be accessible and useable by normal (non root) users, and the ubuntu and fedora packages set /dev/fuse to be only accessible by root... (same with /etc/fuse.conf on some distros)

[chriscool]

About Ubuntu and fuse, I think it should be enough to just put your user into the fuse group with something like:

sudo usermod -a -G fuse

and then restart your session and nscd.

No need to sudo chown <username>:<groupname> /etc/fuse.conf /ipfs /ipns

[whyrusleeping]

On some (redhat) systems, the /dev/fuse device was owned by root and had 600 permissions. Im not confident enough in a solution for that yet, but if anyone else runs across it, i would have them try sudo chmod 666 /dev/fuse

[jbenet]

I think these are usually the perms because fuse kexts are not that safe.

—
Sent from Mailbox

On Tue, Nov 4, 2014 at 9:30 AM, Jeromy Johnson [email protected]
wrote:

On some (redhat) systems, the /dev/fuse device was owned by root and had 600 permissions. Im not confident enough in a solution for that yet, but if anyone else runs across it, i would have them try sudo chmod 666 /dev/fuse

Reply to this email directly or view it on GitHub:
#259 (comment)

[whyrusleeping]

I was reading something from canonical earlier about making fuse completely safe and available for non-root users, lets hope that happens soon!

[ebuchman]

@chriscool neat, that might be cleaner but more lines and I haven't tested, though feel free to add alternative steps in the fuse.md if you have tested and it works.

[chriscool]

@ebuchman I would suggest the user to do the following:

sudo usermod -a -G fuse myuser                  # replace myuser with your user
mkdir -p ipfs_mounts/ipfs ipfs_mounts/ipns
cd ipfs_mounts
ipfs init                                       # if it has not been done already
ipfs config Mounts.IPFS "$(pwd)/ipfs"
ipfs config Mounts.IPNS "$(pwd)/ipns"
ipfs mount

If the user really wants to use /ipfs and /ipfs then I would suggest:

sudo usermod -a -G fuse myuser                 # replace myuser with your user
sudo mkdir -p /ipfs /ipns
sudo chown root:fuse /ipfs /ipns
ipfs init                                      # if it has not been done already
ipfs mount

In these last instructions, I suppose that there is no need to write in /ipfs nor in /ipns.
If people can write there, then sudo chmod 775 /ipfs /ipns is needed too.

I haven't really tested the above from scratch but the first instructions are basically what the test suite does.

[whyrusleeping]

This issue (and associated PR) should get some love before the alpha, the guys from eris industries had a couple issues getting the fuse mounting to behave (aside from the recently addressed bugs). We might even go so far as to try and detect an issue for the user and print out helpful messages like "Your /etc/fuse.conf file has bad permissions" or "your user needs to be added to the 'fuse' group".