On Jun 23, Joey Hess [EMAIL PROTECTED] wrote:
I have reproduced this on two machines, both running 2.6.25-2.
A third machine, running 2.6.24, got /dev/fuse chgrped correctly.
Can you still reproduce this? I can't see anything wrong with the events
nor with the rules. Upgrading to 0.124-3 will
Marco d'Itri wrote:
Can you still reproduce this? I can't see anything wrong with the events
nor with the rules. Upgrading to 0.124-3 will hopefully not hurt...
I can't reproduce it with 2.6.25-2 and 0.124-2.
--
see shy jo
signature.asc
Description: Digital signature
Am 24.06.2008, 20:54 Uhr, schrieb Marco d'Itri [EMAIL PROTECTED]:
On Jun 24, Michael Hofmann [EMAIL PROTECTED]
wrote:
Had the same problem on 2.6.24-1 and udev 0.114-2. Solved it by adding
line:
KERNEL==fuse, NAME=%k
This is just a no-op.
Yes, you are right. But, the
On Jun 25, Michael Hofmann [EMAIL PROTECTED] wrote:
The real problem seem to be, that the GROUP entry of fuse in
/etc/udev/permissions.rules is ignored if the group fuse doesn't
exist (while the config is parsed). But, the fuse group is first
created by the fuse-utils package.
This is a
Had the same problem on 2.6.24-1 and udev 0.114-2. Solved it by adding
line:
KERNEL==fuse, NAME=%k
to /etc/udev/udev.rules . Now, the already exisiting line:
KERNEL==fuse, GROUP=fuse
in /etc/udev/permissions.rules seems to take effect.
On Jun 24, Michael Hofmann [EMAIL PROTECTED] wrote:
Had the same problem on 2.6.24-1 and udev 0.114-2. Solved it by adding
line:
KERNEL==fuse, NAME=%k
This is just a no-op.
--
ciao,
Marco
signature.asc
Description: Digital signature
Package: udev
Version: 0.114-2
Severity: normal
I installed fuse-utils and ssh, and am in group fuse.
fuse: failed to open /dev/fuse: Permission denied
/dev/fuse is:
crw-rw 1 root root 10, 229 Jun 23 15:00 /dev/fuse
I'm not sure why this is happening; /etc/udev/permissions.rules has a
7 matches
Mail list logo
