On Fri, Oct 07, 2011 at 04:18:09PM -0000, James Hunt wrote: > I've just noticed something odd: if you interrupt the initramfs before > it kills udev and performs the move mount, /root/dev/ contains a ton of > device entries including console, zero, null (I was expecting /root/dev/ > to be empty).
This will vary more or less randomly with the install media. At various points in the past, we either have or haven't pre-created a handful of device nodes in the target /dev "just in case". mount -o bind / /mnt && ls /mnt/dev shows nothing at all here, and I don't see this behavior. But it shouldn't hurt to mount -o bind / /mnt && rm -r /mnt/dev/* to rule it out. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures because 'udevadm exit' does not kill udevd worker threads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/818177/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
