setting up tode to run with a stone not created with gsDevKitHome

[dalehenrich]

http://forum.world.st/tode-st-How-to-run-setUpSys-for-a-remote-stone-tp4850660p4850825.html

[marianopeck]

Here is a bit improved version. Note that I may still find issues so I will try to keep this issue open in case I found improvements:

1. Create a trow-away stone in order to have todeClient and directories strucutres created:

installServer tode 3.1.0.6

2. Since I want to share scripts with different stones, I must give read and write access to everybody

find /opt/gsDevKitHome/gsDevKitHome/tode/sys/stones/debrisTesting -type f -exec chmod 666 {} ;
find /opt/gsDevKitHome/gsDevKitHome/tode/sys/local -type d -exec chmod 777 {} ;

3. For every stone, do:

vim /opt/gsDevKitHome/gsDevKitHome/tode/sys/local/client/descriptions/debrisTesting
cp -r $GS_HOME/tode/sys/stones/tode $GS_HOME/tode/sys/stones/debrisTesting
sudo chown -R debristesting:debristesting $GS_HOME/tode/sys/stones/debrisTesting

4. Stop and start again netldi to be sure GS_HOME is get. Confirm that via the following in tODE shell:

eval {System clientEnvironmentVariable: 'GS_HOME'. System gemEnvironmentVariable: 'GS_HOME'}; edit

If both elements (fist and second) are correct, then we are fine

5. Enter tODE shell and run

script --script=setUpSys

6. Done, confirm we can do things inside tODE like:

cd /home
ls
touch testing
edit testing