On Wed, Mar 18, 2009 at 11:21, Matthias Schwarzott <zzam@xxxxxxxxxx> wrote: > This time I have a very strange error. I tried what happens when using > # udevadm test /sys/class/mem/null > > and strange, a bit later some user processes had problems accessing /dev/null. > A quick check showed, that the permissions of /dev were destroyed. > > # ls -ld /dev /dev/null > drw-rw---- 16 root root 4280 18. Mär 11:14 /dev > crw-rw-rw- 1 root root 1, 3 17. Mär 08:05 /dev/null > > Changing it back to 775 and retrying showed, that it must be udevadm test that > destroys it. > > # ls -ld /dev /dev/null > drwxrwxr-x 16 root root 4280 18. Mär 11:05 /dev > crw-rw-rw- 1 root root 1, 3 17. Mär 08:05 /dev/null > > # udevadm test /sys/class/mem/null/ > udev_device_read_db: device 0x8d122c8 filled with db symlink data '/dev/' ... > udev_node_add: creating device node '/dev/', devnum=1:3, mode=0660, uid=0, gid=0 > udev_node_mknod: atomically replace existing file '/dev/' Hmm, strange. What happended to your device node name? I get: udev_device_read_db: device 0x62d3d0 filled with db symlink data '/dev/null' ... udev_node_add: creating device node '/dev/null', devnum=1:3, mode=0666, uid=0, gid=0 Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
