Core v7.0beta2

[Juanito]

Hmm - I tried the test in the opposite sense and do see a change.

terminal 1:

Code: [Select]

$ ls -l /dev/fuse
crw-rw-rwT    1 root     root       10, 229 Jan 22 09:16 /dev/fuse

$ tce-load -i glib2
libffi.tcz: OK
gamin.tcz: OK
glib2.tcz: OK
$ ls -l /dev/fuse
crw------T    1 root     root       10, 229 Jan 22 09:18 /dev/fuse
terminal 2:

Code: [Select]

$ udevadm monitor
...
KERNEL[99.456371] change   /devices/virtual/misc/fuse (misc)
UDEV  [99.530269] change   /devices/virtual/misc/fuse (misc)
I wonder if loading glib2 adds functionality to udev not present at boot time when the permissions of /dev/fuse are set.

@Curaga?

[curaga]

I guess the change action misses the default rule. The rule in fuse.tcz has no action specified, so with fuse.tcz loaded a change shouldn't affect perms.

It currently does, because the startup script in fuse.tcz does not tell udev to reload rules. Adding that, /dev/fuse stays 666.