use /run instead of /var/run as ROOT

ToT now uses /run in anticipation of a udev uprev, with /var/run
being a symlink for compatibility. fixabslinks assumes no symlink
in the CHROOT variable, so /run should be used directly when
passing paths to fixabslinks.
better setting of ROOT in {un,}mount-chroot
Merge pull request #907 from smibarber/rundir

Use /run instead of /var/run as ROOT
mount chrootfs read-only at ~/Downloads/crouton-*

This patch bind-mounts $CHROOT read-only into ~/Downloads/crouton-$NAME
if we're logged in as a user so that we can access files in the chroot
directly from Chromium OS' "Files" application (e.g. to upload files).

In addition, mounting read-only protects us from the danger of Chromium
OS deleting files randomly from ~/Downloads whenever disk space is low:

  https://support.google.com/chromebook/answer/1061547

In fact, even the root user cannot delete files from or modify files
within a read-only mount without first remounting it as read-write!

CAVEAT: I'm assuming that Chromium OS is not so aggressive in freeing up
disk space that it would find and remount this bind-mount as read-write.