>>> Merging sys-fs/udev-077-r5 to / (...) >>> /lib/udev/raid-devfs.sh --- /lib/udev/devices/ !!! /lib/udev/devices/null !!! Failed to move /var/tmp/portage/udev-077-r5/image/lib/udev/devices/zero to /lib/udev/devices/zero !!! [Errno 28] No space left on device In my case after that /lib/udev/devices/zero has something about 900 MB and my / is filled completly.
Created attachment 74901 [details] emerge info
Heh, that's pretty funny. But strange, it works fine for me here. And I haven't heard any other complaints. Perhaps a portage issue?
Oh, and can you provide the output of: ls -l /var/tmp/portage/udev-077-r5/image/lib/udev/devices/ please?
On my second box it works fine too and the only big difference is that i use selinux on that one with this error. New details: upto udev-077-r3 everything is ok. r3 and r4 fail with this strange error.
and the output you asked for: $ ls -l /var/tmp/portage/udev-077-r5/image/lib/udev/devices/ total 12K crw------- 1 root tty 5, 1 Oct 22 2000 console crw-rw-rw- 1 root root 1, 3 Oct 22 2000 null crw-rw-rw- 1 root root 1, 5 Oct 22 2000 zero
disabling selinux flag solves the problem.
Disabling the flag when you build udev? Why would that change anything? Does portage do something differently then?
Yes i meant: USE=-selinux emerge -av =udev-077-r5 I've once more tried to compile udev-077-r5 with selinux flag enabled and this time(after successfuly emerging r5 without selinux flag) it succeed. I was really shocked and tried to reproduce earlier error but with no luck. If you want to, I can attach previous emerge logs, but I don't know whether it is any point in doing so.
Quick change of platform in bugzilla. Sorry about the email.
Marking closed, as it isn't reproducable.
*** Bug 128799 has been marked as a duplicate of this bug. ***
