Comment 5 for bug 908614

This was all done using apt-get. After do-release-upgrade had failed to find an upgrade path, I ran `find /etc/apt -type f -exec sed -i -e 's/lucid/precise/g'` and then I manually went through and downgraded a few packages to help satisfy dependencies.

I understand that /run is likely needed in cases where /var is on another file system from root. However I believe that /tmp/shm/run would be a better candidate as / should be mostly read-only. /var/run should have symbolic links pointed to /tmp/shm/run for use after boot and applications that run during boot should be configured to make use of /tmp/shm/run and then create these links after /var is mounted for it's brethren.

This seams like a cleaner solution then for parts of /var to be mapped to a filesystem for which they don't belong.

As for how things got this way, it has to be because one package created one of these symbolic links and another package created the other. I would look for a package that creates a /run -> var/run link.