fuse problem

[pstranger]

In the previous fuse version it was being created group "fuse" during rpm installation (I mean fuse_2.7.3-2pclos2007_i586.rpm). To allow ordinary user to have access to /dev/fuse it was needed to add this user to "fuse" group.

Now (fuse-2.8.4-1pclos2010.i586.rpm) group "fuse" isn't being created.

How to make access to /dev/fuse for ordinary user?

fuse: failed to open /dev/fuse: Permission denied

[melodie]

Hi,

Did you update it ? There was a new version theses days. Else, how do you use it ? I mean, what task do you do with it ?

[pstranger]

Sure.

#rpm -q fuse
fuse-2.8.1-1pclos2010

I want to use fusesmb.

[pstranger]

Scripts for fuse-2.7.4-5pclos2009.i586.rpm:

/usr/share/rpm-helper/add-group fuse $1 fuse
/usr/share/rpm-helper/add-service fuse $1 fuse

and nothing for fuse-2.8.4-1pclos2010.i586.rpm

Were they missed?

[pstranger]

PROBLEM:
- during fuse-*pclos2010.i586.rpm installation fuse doesn't start as service and
- group "fuse" is not created.

INFO:
I've read chengelog and there is no mention about significant changes in this packet.

Let's get file list 2.7-release:
rpm -qlp fuse-2.7.4-5pclos2009.i586.rpm >2.7.txt

and 2.8-release:
rpm -qlp fuse-2.8.4-1pclos2010.i586.rpm >2.8.txt

then compare them:
diff 2.7.txt 2.8.txt >fuse.diff

< /etc/rc.d/init.d/fuse
< /etc/udev/devices.d/99-fuse.nodes
< /etc/udev/rules.d/99-fuse.rules
< /lib/libfuse.so.2
< /lib/libfuse.so.2.7.4
< /lib/libulockmgr.so.1
< /lib/libulockmgr.so.1.0.1

So we can see that start script and libs are missed.
So fuse-2.8.1-1pclos2010 (which comes out-of-iso) and the newest updated fuse-2.8.4-1pclos2010 is broken and fuse doesn't work (and didn't work) in 2010.

SOLUTION:
It needs to downgrade fuse rpm or rebuild newest rpm in order to it have worked.

[Texstar]

PROBLEM:
- during fuse-*pclos2010.i586.rpm installation fuse doesn't start as service and
- group "fuse" is not created.

INFO:
I've read chengelog and there is no mention about significant changes in this packet.

Let's get file list 2.7-release:
rpm -qlp fuse-2.7.4-5pclos2009.i586.rpm >2.7.txt

and 2.8-release:
rpm -qlp fuse-2.8.4-1pclos2010.i586.rpm >2.8.txt

then compare them:
diff 2.7.txt 2.8.txt >fuse.diff

< /etc/rc.d/init.d/fuse
< /etc/udev/devices.d/99-fuse.nodes
< /etc/udev/rules.d/99-fuse.rules
< /lib/libfuse.so.2
< /lib/libfuse.so.2.7.4
< /lib/libulockmgr.so.1
< /lib/libulockmgr.so.1.0.1

So we can see that start script and libs are missed
So fuse-2.8.1-1pclos2010 (which comes out-of-iso) and the newest updated fuse-2.8.4-1pclos2010 is broken and fuse doesn't work (and didn't work) in 2010.

SOLUTION:
It needs to downgrade fuse rpm or rebuild newest rpm in order to it works.

There is no service for fuse anymore. There are no more udev rules in /lib/udev or /etc/udev. Fuse kernel driver is loaded from /etc/modprobe.preload. fuse permissions and device is created by /etc/makedev.d/z-fuse.

Please explain why you think it does not work anymore with a real life example that someone can try to duplicate.

[pstranger]

See the first post. The only solution to give access to "/dev/fuse" for ordinary user is to include him to fuse-group. There is no more such group.

[Joble]

Please explain why you think it does not work anymore with a real life example that someone can try to duplicate.

Read the last post.  I can't duplicate your problem.

[muungwana]

running 2010 fully updated, "ls -dl /dev/fuse" command gives

crw-rw-rw- 1 root root 10, 229 2010-05-03 10:51 /dev/fuse

did you want to "execute" on the device?, thats the only thing my permissions say will give a "permission denied" error.  

[pstranger]

OK
$ fusesmb ~/net
fuse: failed to open /dev/fuse: Permission denied (or something like this)

[Joble]

OK, I'm listening:

[joe@localhost ~]$ fusesmb ~/net
bash: fusesmb: command not found
[joe@localhost ~]$ su
Password:
[root@localhost joe]# fusesmb ~/net
bash: fusesmb: command not found
[root@localhost joe]#

What package is this command a part of exactly?

[pstranger]

mkdir ~/net

fusesmb (0.8.7)

No need su command.

[muungwana]

what does "stat /dev/fuse" give you?

[pstranger]

$ stat /dev/fuse
  File: `/dev/fuse'
  Size: 0            Blocks: 0          IO Block: 4096   (special file)
Device: 5h/5d   Inode: 3850        Links: 1     Device type: a,e5
Access: (0755/crwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2010-04-30 13:53:44.657970900 +0600
Modify: 2010-04-30 13:53:44.657970900 +0600
Change: 2010-04-30 13:53:44.657970900 +0600

[muungwana]

This is a character device and i think the only thing you can do with it is to read from it or write to it and your current permissions only allow root to write to it. Creating any group will not change this.

can someone else show what permissions they have, anybody can explain why we have two different permissions?

try to change your writing permissions and see if your problem will go away