This note outlines how to configure the computers needed to run DIMMWIT. It is possible to use one of two private network configurations.
The original DIMMWIT configuration, consisting of two computers:
The two computers are linked by a cross-over ethernet cable (to avoid the need for a hub). This can be a long (50ft) cable to allow remote operation.
This more complicated setup allows the observer to analyse DIMMWIT data while other data is being recorded.
The two-computer (laptop and ICE) private network described above is no good for this because mouse events (even motion) are transmitted via the X protocol from the machine displaying finder to the machine running finder, causing dropouts in the data.
One solution that is relatively simple and cheap to implement is to have a three-computer private network, using a switched hub.
The names and roles of these three computers are as follows:
The three computers are each linked to the same switched ethernet hub by a standard non-cross-over ethernet cable. A switched hub is needed to ensure that dimmwit does not see X events due to the observer analysing the data. The cable from dimmwit to the hub can be a long (50ft) one to allow remote operation.
These notes are very brief for now. However, they should be sufficient if you are an experienced Linux sysadmin.
/home/coast/binand ensure that its in coast's PATH
mkdir -p /data/oberon/data/finder
chown coast:coast /data/oberon/data/finder
mkdir -p /data/oberon/soft
mkdir -p /net/oberon/data
ln -sf /data/oberon/data/finder /net/oberon/data/finder
ln -sf /data/oberon/soft /net/oberon/soft
sx_usb.o) from date DD/MM/YY in directories
cd /net/oberon/soft; ln -sf finder-YYMMDD/ finder
/data 192.168.20.1(rw) 192.168.20.3(ro)
Ensure that portmap access is enabled in
portmap: LOCAL, 10.0.100., 192.168.20.
Make sure that there are no entries in
that would stop NFS working. For the same reason, disable any firewall
running on dimmwithost (iptables/ipchains).
/net/oberon/data/findercan be mounted read-only by any client in 192.168.20. The workgroup should be 'ASMS'
ForwardX11 yes CheckHostIP no StrictHostKeyChecking no Protocol 2,1
ssh-keygen -t rsa, entering a blank passphrase
ssh root@dimmwit rw
scp /home/coast/.ssh/id_rsa.pub coast@dimmwit:.ssh/authorized_keys2 scp /home/coast/.ssh/id_rsa.pub root@dimmwit:.ssh/authorized_keys2
With both dimmwit and dimmwithost connected to the private network, and the CCD camera connected and powered up: