On Fri, May 27, 2011 at 5:07 PM, Marco d'Itri <m...@linux.it> wrote: >> Curious thing is that even if the directory does not exist, >> /proc/mounts displays it as mounted... > I would say "impossibile", even.
Is it ? However, it's the state after bootup with udev-168.2 and initscripts-2.88dsf-13.2, if the /run directory is not present on rootfs. If rootfs does not contain /run, default behavior of initramfs init script is: 1) Move /run/udev and /run/initramfs to /dev/.udev and /dev/.initramfs 2) Umount /run The problem on 2) is that udevd keeps /run directory busy (managing /run/udev/queue.bin, even deleted); it can't be unmounted. After chroot, /proc/mounts still displays /run, which is not present on the rootfs. Note that the latest initscripts does not even let the system boot if the /run directory is not here. Now I have to figure when and what process should normally have created that directory on my system, and why it didn't. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
