1Here are some very skeletal instructions for using 2the client test code. 3 4on server (assumes BSD style LD_LIBRARY_PATH): 5 6mkdir /tmp/foo 7cd lib9p 8env LD_LIBRARY_PATH=. LIB9P_LOGGING=stderr example/server -h localhost -p 12345 /tmp/foo 9 10(this can be run as a non-root user for now, but some things 11only work when run as root) 12 13on client (same machine as server, but can always be run as 14non-root user): 15 16cd lib9p/pytest 17ONE TIME ONLY: copy testconf.ini.sample to testconf.ini, adjust to taste 18./client.py 19 20TODO: rework ./client so it can locate the .ini file better 21 22######## 23 24IF USING diod (http://github.com/chaos/diod) AS THE SERVER ON 25A LINUX MACHINE: 26 27 - The instructions for running the server are (or were): 28 sudo ./diod -f -d 1 -n -e /tmp/9 29 - You must mkdir the exported 9pfs file system (e.g., mkdir /tmp/9). 30 - While uname is not really used, aname (the attach name) IS used 31 and must match the exported file system, e.g., testconf.ini 32 must have "aname = /tmp/9". 33