Move mote device hierarchy to /var/run/remote

Having the device hierarchy in /dev/remote seemed practical when UDEV was
introduced, since the tty symlinks and other files created by UDEV are kept
one place. However, as with issue 20 it does not live up to the file
hierarchy standard and worse it can potentially be misleading.

The fix is to move the "runtime" files, such as mote path and files related
to issue 3 and issue 6, to /var/run/remote (should be configurable via an
option). This directory should also be used for holding the event pipe,
mote program, and PID files. A first step could be for MCH to create the
directory at startup and put the event pipe there.

Original issue reported on code.google.com by jonas.fonseca on 19 Nov 2007 at 6:43

rdmenezes / remote-testbed

Move mote device hierarchy to /var/run/remote #23