I did the update/dist-upgrade but the situation did not change. > No, /etc/init.d/umountroot should unconditionally nuke /var/run on reboot.
So I would suspect it does not get executed at all > Is your /etc/init.d/umountroot the unmodified version from the package? I didn't change it, md5sum is 36d5098f8a3965dce172a1c8f75e1429. > Do you have any mount points *under* /var/run, that would prevent the rm -rf /var/run in this shutdown script from succeeding? According to the output of "mount" nothing is mounted below /var/run. (Please see also my previous attachment) >Did /var/lock get turned successfully into a symlink, or is it still a directory like /var/run? eduard@phenom:~$ ls -ld /var/lock drwxrwxrwt 4 root root 4096 2011-07-15 19:30 /var/lock No, still a directory. I think this is also a indication that /etc/init.d/umountroot doesn't get executed on reboot. Just for clarification: I definitely know how to set the symlinks myself, and get the system running again. I just want to investigate this issue, so that other people don't run into the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807306 Title: [oneiric] Keyboard & mouse not working in X - incomplete migration to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/807306/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
