Modified some stuff to cleanup the syscall_server build process
authorROS Developer <ros-dev@core0.(none)>
Mon, 28 Sep 2009 05:05:37 +0000 (07:05 +0200)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 1 Oct 2009 20:09:51 +0000 (22:09 +0200)
commit2f0374a3d8a6f2daa58cb7f048a368b2feab199f
tree917090ce52753f45baa5b5c022a8cb970453ca50
parent4cba50211484f50e188dbb43a72a4d5df656f824
Modified some stuff to cleanup the syscall_server build process

This also involved adding a sandbox directory under the serial_server directory.  All files accessed by ROS will be relative to this sandbox.  There is currently no suport for preventing one from using ".." to break out of the sandbox.  Presumably a real server would run with itself as a user with no priveleges other than to access files in the sandbox directory and nowhere else.
scripts/mergedep.pl
tools/syscall_server/.ros_slave_pty [deleted file]
tools/syscall_server/Makefile
tools/syscall_server/pipe_init.c [new file with mode: 0644]
tools/syscall_server/pty_init.c [new file with mode: 0644]
tools/syscall_server/sandbox/sample [new file with mode: 0644]
tools/syscall_server/syscall_server.c
tools/syscall_server/syscall_server.h
tools/syscall_server/test/input [deleted file]
user/apps/parlib/file_error.c
user/apps/parlib/file_io.c