You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2006-04-27 21:40:29
- PeteMo
- Member
- From: H'Burg, VA
- Registered: 2006-01-26
- Posts: 191
- Website
fuse and udev rules
Today, for the first time in a long time, I tried using sshfs to mount a shared directory from my server. This used to work fine, but I got an error:
"fusermount: failed to open /dev/fuse: Permission denied"
A quick ls -l /dev/fuse showed that the group was root, instead of fuse. I did have a udev rule for fuse: /etc/udev/rules.d/40-fuse.rules - that I assume was put there when I installed fuse. I fixed the problem by changing the rule from:
KERNEL='fuse", NAME="%k", MODE="0666"to
KERNEL=="fuse", GROUP="fuse"And it seems to be working now. I assume that the rule stopped working with the recent udev updates. Is this something that should be changed in the fuse package its self?
Offline
#2 2006-04-27 23:05:56
- iphitus
- Forum Fellow
- From: Melbourne, Australia
- Registered: 2004-10-09
- Posts: 4,927
Re: fuse and udev rules
File a bug
Offline
#3 2006-04-27 23:16:17
- tomk
- Forum Fellow
- From: Ireland
- Registered: 2004-07-21
- Posts: 9,839
Re: fuse and udev rules
I don't have a fuse group, and never did, and it works fine for me with the 40-fuse rules. MODE="0666" basically means that anyone can read or write to the device, regardless of user or group ownership.
Offline
#4 2006-04-27 23:32:18
- PeteMo
- Member
- From: H'Burg, VA
- Registered: 2006-01-26
- Posts: 191
- Website
Re: fuse and udev rules
I don't have a fuse group, and never did, and it works fine for me with the 40-fuse rules. MODE="0666" basically means that anyone can read or write to the device, regardless of user or group ownership.
Strange. To double check, I reverted back to the original 40-fuse.rules and restarted udev. I got the exact same error as previously. Switching to my new rule allowed me to mount my share fine. Before I file a bug, I'd like to see if anyone else is seeing my error, or if it is just me.
Offline
#5 2006-04-28 10:06:32
- PeteMo
- Member
- From: H'Burg, VA
- Registered: 2006-01-26
- Posts: 191
- Website
Re: fuse and udev rules
Well, my system upgrade this morning included fuse 2.5.3-1, which seems to fix the problem. The rule was changed to:
KERNEL=="fuse", NAME="%k", MODE="0666"The key seems to be the double equal instead of the single equal between KERNEL and "fuse".
Offline
#6 2006-04-28 10:22:06
- brain0
- Developer
- From: Aachen - Germany
- Registered: 2005-01-03
- Posts: 1,382
Re: fuse and udev rules
Yes. Newest udev is stricter with the rule syntax.
Offline
Pages: 1