Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.mrao.cam.ac.uk/~jsy1001/dimmwit/finder/refman.html
Дата изменения: Wed Oct 27 23:46:17 2004 Дата индексирования: Tue Oct 2 10:40:17 2012 Кодировка: |
Finding FinderConfiguring a Finder Computer from Scratch
Installing Finder
Telling Ssh on the Bunker Computers About the New Finder
Alignment
Before You BeginBuilding Finder
Setting Up
Initial Configuration
Installing Linux
Change Default Passwords!
SSH Sshenanigans
Set the Coast User ID
More SSH Sshenanigans
Mounting Oberon as an NFS (Network File System) Drive
The CCD Drivers
The Finder Application
Check it All Works!
Time Synchronisation (optional)
The ApplicationRunning Finder as a Transportable DIMM
The Drivers
IntroductionConverting a HX516 to run in DIMM mode [deprecated]
Setting up your host PC
Connections
Running finder
Shutting down
Actions which have been found to crash finder or the controller (don't do them!)
Actions which will reduce the scientific value of the data
The Finder Configuration File
Enumeration Reference
ssh coast@cstfinderx
(you might get a warning
about authenticity, ignore it).su
.rw
to make the root partition writeable.exit
to become coast.reboot
to get the new settings to
take effect.
The CD in its case.
ssh
secure shell, the vi
editor and networking.
Move this link towards the backup battery.
rw
, this makes the root partition writeable.passwd
.adduser coast
and give the COAST user password.cd /home/arcom
cp .bashrc /home/coast
cp .inputrc /home/coast
cp .inputrc /home/coast
cp .profile /home/coast
cd
deluser arcom
rm -rf /home/arcom
poweroff
to power down
gracefully.cd .ssh
vi known_hosts
ssh
coast@apfinderwhatever
su
. However, you can ssh in as root. There is no
good reason to use telnet with the finders, it is only there as a
backup if ssh fails.rw
to make the root partition writeable.vi /etc/passwd
coast:x:103:103:COAST Admin
Account,,,:/home/coast:/bin/sh
".cd /home/coast
chown coast .*
chown root ..
Logout and check that you can still login as
coast.xauth
to be present, not part of the Arcom
distribution. Also, X11 forwarding needs to be turned on in ssh so that
finder can
be displayed remotely. This is done by sshd, but the version supplied
by Arcom is crippled in this respect. The easiest way to fix this is
to copy these programs from a finder with versions that work (I have
compiled
replacements):scp 172.24.225.211:/etc/ssh/ssh_known_hosts .
cd /usr/X11R6-e/bin
scp 172.24.225.211:/usr/X11R6-e/bin/xauth .
cd /usr/sbin
scp 172.24.225.211:/usr/sbin/sshd sshd.new
mv sshd.new sshd
reboot
xterm
and see if an xterm appears. If you get an
X11 error it might be that you needed the "-X" option to ssh when
logging in (shouldn't be necessary on any of the bunker machines).oberon.ra.phy.cam.ac.uk:/soft /net/oberon/soft nfs
ro,hard,intr,nolock 0 0
oberon.ra.phy.cam.ac.uk:/data2 /net/oberon/data nfs
rw,hard,intr,nolock 0 0
/etc/init.d/mountnfs.sh
ls -l /net/oberon/soft/finder
(you should see
finder, ccd.o and sx_usb.o).cd /etc/rc3.d
ln -s ../init.d/mountnfs.sh S98mountnfs
reboot
scp 172.24.225.211:/sbin/portmap /sbin
adduser -g "Portmapper RPC user" -s /bin/false rpc
rpc:x:32:32:Portmapper
RPC user:/:/bin/false
rpc:x:32:
oberon.ra.phy.cam.ac.uk:/soft /net/oberon/soft nfs
ro,hard,intr 0 0
oberon.ra.phy.cam.ac.uk:/data2 /net/oberon/data nfs
rw,hard,intr 0 0
ps
cd /lib/modules/2.4.18/kernel/drivers/
mkdir usb
mkdir ccd
cd usb
scp
172.24.225.211:/lib/modules/2.4.18/kernel/drivers/usb/hub.o .
scp
172.24.225.211:/lib/modules/2.4.18/kernel/drivers/usb/usb-debug.o .
scp
172.24.225.211:/lib/modules/2.4.18/kernel/drivers/usb/usb-ohci.o .
scp
172.24.225.211:/lib/modules/2.4.18/kernel/drivers/usb/usb.o .
scp
172.24.225.211:/lib/modules/2.4.18/kernel/drivers/usb/usbcore.o .
chmod g+w *.o
cd ../ccd
ln -s /net/oberon/soft/finder/ccd.o ccd.o
ln -s /net/oberon/soft/finder/sx_usb.o sx_usb.o
#! /bin/sh
insmod usbcore
insmod usb-ohci
insmod /net/oberon/soft/finder/ccd.o
# Use "model=5" for the Starlight Xpress MX516
# Use "model=-5" for the HX516.
insmod /net/oberon/soft/finder/sx_usb.o model=-5
chmod ugo+x initccd.sh
cd /etc/rc3.d
ln -s ../init.d/initccd.sh S99initccd
mknod /dev/ccda c 127 0
mknod /dev/ccda1 c 127 16
mknod /dev/ccda2 c 127 32
mknod /dev/ccdA c 127 128
mknod /dev/ccdA1 c 127 144
mknod /dev/ccdA2 c 127 160
mknod /dev/ccdb c 127 1
mknod /dev/ccdb1 c 127 17
mknod /dev/ccdb2 c 127 33
mknod /dev/ccdB c 127 129
mknod /dev/ccdB1 c 127 145
mknod /dev/ccdB2 c 127 161
chmod 0666 /dev/ccda
chmod 0666 /dev/ccda1
chmod 0666 /dev/ccda2
chmod 0666 /dev/ccdA
chmod 0666 /dev/ccdA1
chmod 0666 /dev/ccdA2
chmod 0666 /dev/ccdb
chmod 0666 /dev/ccdb1
chmod 0666 /dev/ccdb2
chmod 0666 /dev/ccdB
chmod 0666 /dev/ccdB1
chmod 0666 /dev/ccdB2
cd /bin
ln -s /net/oberon/soft/finder/finder finder
exit
. You should now be
coast.cd
# Finder configuration file
#
# NOTE: This file is automatically generated! Changes
# made to parameters will be remembered, but comments
# will be overwritten!
#
Name East_Telescope
TelescopeIP apcsttel.phy.private.cam.ac.uk
Port 2703
Crosshair 345 197
Change the name and port to the values for your telescope as described here. More information on the file
format can be found here.dmesg
. If all is well, at the end of the
listing you should see something like this:Registered ccd @ major #127
usb.c: registered new driver starlight-xpress
hub.c: USB new device connect on bus1/2, assigned device number 2
starlight-xpress: probing usb_device 0x0547:0x2131
starlight-xpress: found EZUSB device
starlight-xpress: RESET 8051
starlight-xpress: Download 341 code records
starlight-xpress: un-RESET 8051
usb.c: USB disconnect on device 2
starlight-xpress: disconnect
hub.c: USB new device connect on bus1/2, assigned device number 3
starlight-xpress: probing usb_device 0x4444:0x4220
starlight-xpress: found ECHO2 device
starlight-xpress: read 0xFF model from camera
starlight-xpress: writing 0x05 model to camera
starlight-xpress: camera model is Starlight Xpress HX5/16
Registered CCD mini-driver: Starlight Xpress HX5/16 @ minor #0 and #128
starlight-xpress: camera has 1 serial ports
finder
and watch the user interface
appear. Hit the "connect to CCD" button. If you see a crosshair
appear, you're in business!rw
.cd /usr/sbin/
scp ntp* 172.24.225.211:/usr/sbin
scp tickadj 172.24.225.211:/usr/sbin
cd /etc
scp -r ntp 172.24.225.211:/etc
scp ntp.conf 172.24.225.211:/etc
cd /etc/init.d
scp ntpd 172.24.225.211:/etc/init.d
cd /lib
scp libcap.so.1.10 172.24.225.211:/lib
cd /lib
ln -s libcap.so.1.10 libcap.so
ln -s libcap.so.1.10 libcap.so.1
# Time servers...
131.111.8.74 aquila ntp0.cam.ac.uk
131.111.12.21 janus ntp1.cam.ac.uk
131.111.8.42 chimaera ntp3.cam.ac.uk
131.111.48.8 mraos mraos.ra.phy.cam.ac.uk
Ideally we would just leave NTP running all the time, but it periodically interacts with its servers over the network. If this happens while a DIMM file is being recorded, dropouts in the acquisition can occur. We could use the/etc/init.d/ntpd start
/usr/sbin/ntpq -p
...should return something like...
remote refid st t when poll reach delay offset jitter
==============================================================================
+aquila ntp2.ja.net 2 u 5 256 377 1.177 1.020 0.295
-janus spanner.eng.cam 3 u - 256 377 1.897 -0.166 0.057
*chimaera ntp2.ja.net 2 u 251 256 377 1.136 1.007 0.086
-aptitania spanner.eng.cam 3 u 252 256 377 0.431 -0.090 0.161
+apcstapd spanner.eng.cam 3 u 45 256 377 0.390 0.672 0.048
cron
program to switch on NTP only during
daylight hours, but cron itself wakes up once a minute to see if there
are any tasks that need doing. Again, there is a risk of dropouts. So
instead we tell
oberon to start and stop NTP on the finders during the day and let the
finder
clock run by itself during the night. This way, there are no
unnecessary
processes running during observing hours.super
program on the finder.
cd /bin
scp super 172.24.225.211:/bin
cd /etc
scp super.tab 172.24.225.211:/etc
Finally, oberon needs to know when to start and stop ntpd on the finder. If you are replacing a finder it probably already knows but it doesn't hurt to check.super ntpd stop
super ntpd start
...you should see the ntpd daemon either appear or not when you typeps
.
crontab -e
01 9 * * * ssh apfinder1 super ntpd start >
/dev/null
51 14 * * * ssh apfinder1 super ntpd stop > /dev/null
The first and second columns are the minute and hour of the day
respectively that you want NTP to start and stop. I prefer to start or
stop NTP on
each finder a minute apart so that the load is spread out.
Password:
DEVICE=eth0:1
BOOTPROTO=static
BROADCAST=192.168.20.255
IPADDR=192.168.20.2
NETMASK=255.255.255.0
NETWORK=192.168.20.0
ONBOOT=yes
# DIMMWIT single board computerWhen connected to dimmwit your computer will now use the 192.168.20. subnet and be called "dimmwithost" but when connected to your usual network it will have its usual name and IP.
192.168.20.1 dimmwit
# This machine when talking to DIMMWIT
192.168.20.2 dimmwithost
# Starlight Xpress single board computer
/directory/that/contains/program 192.168.20.1(ro)
/directory/that/contains/data 192.168.20.1(rw)
ssh coast@dimmwit finder
ssh coast@dimmwit remotefinder
Telescope number |
Finder computer name |
IP address |
Foundation |
Beam |
Finder-telescope ethernet port |
1 |
apfinder1 |
172.24.225.211 |
N4 |
4 |
2704 |
2 |
apfinder2 |
172.24.225.212 | C |
1 |
2700 |
3 |
apfinder3 |
172.24.225.213 | E1 |
3 |
2703 |
4 |
apfinder4 |
172.24.225.214 | W7 |
2(W) |
2702 |
5 |
apfinder5 |
172.24.225.215 | W2 |
2(E) |
2701 |
(spare) |
apfinderx |
172.24.225.216 |
(spare) |
(spare) |
(spare) |
reserved IP |
apdimm |
172.24.225.217 |
none |
none |
not connected |