search

marook / tagfs

Fuse tag file system
GNU General Public License v3.0
125 stars 9 forks source link

Please document how to use this tool #5

Open novoid opened 11 years ago

novoid commented 11 years ago

Hi!

I wanted to evaluate tagfs as a tagging tool.

Meanwhile, I am able to mount this thing (by using root and omitting «--home ~/.local» for installation - contrary to the documentation).

But what then?

vk@gary ~2d/2012-12-19-tagfs % ls -la ls: cannot access mountpoint: Permission denied total 24 drwxr-xr-x 4 vk vk 4096 Dec 19 14:27 ./ drwxrwxr-x 34 vk vk 16384 Dec 20 14:13 ../ drwxr-xr-x 2 vk vk 4096 Dec 20 20:03 items/ d????????? ? ? ? ? ? mountpoint/ 1 vk@gary ~2d/2012-12-19-tagfs %

The mountpoint looks very strange and whatever I copy to «items» it does not provoke any action at all. I can not change into «mountpoint» as well.

So either the source code is broken or the tool is not working on my machine.

The documentation needs some basic description on how to use tagfs anyway:

marook commented 11 years ago

I think the weird / missing access rights on the 'mountpoint' directory may be caused by two reasons:

  1. You have mounted a directory using the user root and try to access it with your 'vk' user.
  2. tagfs throws an exception when accessing the mountpoint.

If 1. is then case you should try the fuse -o allow_root or -o allow_other command line flags. As tagfs is based on fuse and fuse is a 'user space file system' one user can by default not access another user's mounts. The same issue occurs for example with sshfs. See http://serverfault.com/questions/188894/denied-root-access-to-user-mounted-fuse-file-system

If 2. is the case then you can set the DEBUG environment variable before mounting. Like this:

$ export DEBUG=1

When the DEBUG variable is set before mounting tagfs will write some logging output to /tmp/tagfs.log I would be very happy to see your log output.

I aggree with you that the documentation is missing some basic information how to apply tags. I put this on my TODO list. Right now there's only an example below https://github.com/marook/tagfs/tree/master/etc/demo/events Look at the .tag files below the directories.

If I understand you right you couldn't install tagfs below the 'vk' user? Did the setup.py process quit or couldn't you execute tagfs after installation?

novoid commented 11 years ago

Hi!

You were right about the mountpoints and its permission. Because my user was not part of group "fuse", I had to mount it using sudo which caused the not-so-intuitive-to-interpret exception.

Solution was: adduser $MYUSER fuse ## add user to group fuse su $MYUSER ## log in with new group

ad install issue:

I installed it using the command provided in the documentation. This command worked out fine but I was not able to start tagfs without errors related to not finding other Python files.

ad usage:

Am I right that the user has to add tags to folders within the item-folder by writing them to files named ".tag"? And am I right that these .tag-files are only read-in during the tagfs-mount command (-i)?

If so, then why are my test items listed only in "mountpoint/.untagged/"?

marook commented 11 years ago

ad install issue: please open another issue with the output when starting tagfs... maybe it's a bug we can fix.

ad usage: I've added some information about how to tag files to the README. Check out the 'Tagging Files' section. Also you are right... tagfs reads the .tag files only during the tagfs mount command. Does it work if you try the commands from the 'Tagging Files' section?