This documents covers the steps necessary to allow a sideARM to run the 
SIAM software immediately after a reboot.

* Add the script '/etc/init.d/rc.local' to do the following at boot

  - chgrp lock /var/lock
  - chmod 775 /var/lock
  - mount -a
  - ntpdate ntp.shore.mbari.org
  - /root/rootsrv/rootsrv
  - rfpower on
  - runppp

  note: comment out the 'ntpdate ntp.shore.mbari.org' if you are not on 
  the MBARI network.
  note: script is kept in cvs under siam/native/arm-linux/scripts
  note: make sure that the script has executable permission
  note: rootsrv is required for managing entry/exit into sleep mode (SleepManager)
        see $SIAM_HOME/docs/SleepManager_setup.txt for more information

* Add the script '/etc/init.d/loadspi' script for loading and unloading the 
  SPI driver.
  note: script is kept in cvs under siam/native/arm-linux/scripts
  note: make sure that the script has executable permission

* Add the script '/etc/init.d/loadgpio' script for loading and unloading the 
  GPIO driver.
  note: script is kept in cvs under siam/native/arm-linux/scripts
  note: make sure that the script has executable permission

* Add the script '/etc/init.d/loadlddio' script for loading and unloading the 
  LDDIO driver.
  note: script is kept in cvs under siam/native/arm-linux/scripts
  note: make sure that the script has executable permission

* Add the script '/usr/sbin/runppp' script which starts the ppp
  daemon, and retries after awhile if connection can't be established
  note: make sure that the script has executable permission

* Add the symbolic link '/etc/rc2.d/S20loadspi -> ../init.d/loadspi'.  This 
  link will cause the loadpsi script to be processed at boot time.

* Add the symbolic link '/etc/rc2.d/S20loadgpio -> ../init.d/loadgpio'.  This 
  link will cause the loadpsi script to be processed at boot time.

* loadspi and loadgpio assume that the modules sa1100spi.o and sa1100gpio.o
  reside in /root. Modify them or place the modules there.

* Add the symbolic link '/etc/rc2.d/S99local -> ../init.d/rc.local'.  This 
  link will cause the 'rc.local' script to be processed at boot time.

* Add character devices for use by the gpio drivers:
  cd /dev
  mknod /dev/spi c 10 223
  mknod /dev/gpio c 10 224
  mknod /dev/lddio c 10 225
  chown root /dev/spi
  chgrp lock /dev/spi
  chmod 664 /dev/spi 
  chown root /dev/gpio
  chgrp lock /dev/gpio
  chmod 664 /dev/gpio
  chown root /dev/lddio
  chgrp lock /dev/lddio
  chmod 664 /dev/lddio
 
* Modify the /etc/fstab file with the entries

  - /dev/hda1                     /mnt/hda            ext2  defaults 0 0
  - tempest:/vol/vol0/users/mrisi /home/mrisi/tempest nfs   bg,soft,nosuid,nodev,exec

  The nfs mount of your home directory is optional.  If you choose to nfs 
  mount your home directory you must have a user account on the sideARM with
  the same user id as your user id on the MBARI UNIX network.  You can 
  determine this id by logging on to a computer such as ocean.shore.mbari.org
  and typing the command 'id'.

* Add the scripts,
	
  - .bash_profile
  - .bashrc

  to the home directory of the user account you plan to execute the SIAM 
  software from.  The .bashrc will have to be modified to match the setup of 
  your environment.  Specifically you will have to


  - Source the appropriate j9env script	(example: '. /j9/j9env')
  - Set your SIAM_HOME var (example: SIAM_HOME=/your/siam/home/dir)
  - Set your SIAM_CLASSPATH var (example: SIAM_CLASSPATH=/your/siam/classes:/more/classes:/you/get/the/idea)

  Use the .bashrc checked into CVS '/siam/native/arm-linux/scripts'
  as an example.



