2009/2/20 Zbigniew Baniewski <z...@ispid.com.pl>: > I've replaced syslogd with syslogd-ng - and I noticed, that by every logout > from the console (not xterm) there are several error messages like: > > #v+ > z...@trurl~$ logout > udevd-event[6096]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6097]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6100]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6101]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6105]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6106]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6109]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6110]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6113]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > udevd-event[6114]: rmdir(/System/Kernel/Devices) failed: Device or resource > busy > #v- > > Any ideas, what's going on? It seems, that something wants to delete > /System/Kernel/Devices directory?
As far as I can tell, by looking around, this is a non-fatal message that has troubled other distros as well. I could not find a solution more than this bug report from LFS: http://wiki.linuxfromscratch.org/lfs/ticket/2236 which suggests that the following change: http://wiki.linuxfromscratch.org/lfs/changeset/8662 made the message go away. If anyone else have possibility to look into how this applies on GoboLinux it would be great, as I don't have the resources currently. -- /Jonas _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
