Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.mrao.cam.ac.uk/~jsy1001/dimmwit/new_setup.txt Дата изменения: Thu May 6 16:53:23 2004 Дата индексирования: Tue Oct 2 04:47:15 2012 Кодировка: Поисковые слова: lunar module

From dfb@mrao.cam.ac.uk Thu May 6 13:53:23 2004
Date: Fri, 27 Feb 2004 19:17:56 -0700 (Mountain Standard Time)
From: David Buscher
To: Dan Klinglesmith
Cc: bodie@mrao.cam.ac.uk, John Young
Subject: DIMMWIT new setup

Dan,

I have now set up the new ccd drivers on DIMMWIT which should give the
correct exposure times to better than 1%. I have at the same time modified
the setup on dimmwit and dimmwithost in a way I think will make things
easier to use and to upgrade. There are some changes to the old way of
doing things, as follows.

[1] It should no longer matter which order you power up and connect the
laptop and the DIMMWIT computer.

[2] In the laptop terminal window (you should automatically be logged in
as "coast" when it boots), type "ping dimmwit" (and hit return - I assume
this is obvious hereafter) and wait until you get responses back. This
should be about 40 seconds after you switch the dimmwit computer on. Don't
worry if you get error responses before 40 seconds, do worry if you don't
get positive responses after 50 seconds.

[3] Now type "initccd". This initialises the shared network disk and loads
the latest drivers. It needs to be repeated any time you reboot dimmwit.
It should not harm to type it multiple times. The first time you type it
you should get error messages about modules not being loaded, followed by
messages of the form "Using /blah/blah.o". Any subsequent times you should
not get the error messages but you should get the "Using" messages.

[4] Now type "finder": this should bring up a finder with the correct font
size (it is not super big, but readable). You could also type
"ssh -f dimmwit /bin/finder.14pt" to get very big fonts, but these
overflow and are in fact less readable as a result. Note that you no longer have to
type a password for these ssh commands.

[5] That should be all. Run the camera as usual. You should now be able to
see the data in /net/oberon/data/finder on both machines.

Note that I have not tested this with the actual CCD plugged in...

Now for the more technical stuff which you can ignore for now.
*************************************************************************
The driver files and the finder executable files are both stored in
/net/oberon/soft/finder which is actually a link to the directory the
files are stored in. To change the drivers and the finder executable, do
the following:

[1] Make a new terminal window on the laptop (click the "Terminal"
button), click on the new window, type "su" and type in the root
password when it asks.

[2] Type "cd /net/oberon/soft"

[3] Type 'mkdir finder-xxxxxx' where xxxxx is something like 040227 for
February 27, 2004.

[4] Assuming that you put the new finder files on cdrom under the
directory 'fred' and have put the cdrom in the laptop drive, type
"cp /mnt/cdrom/fred/* finder-xxxxxx".

[5] Type "ln -sf finder-xxxxxx finder"

[6] Now go back to your old window (where you are logged in as "coast")
and type "initccd".

[7] That should be all! You can close the window where you are logged in
as root when you are happy everything is ok.

[8] If for some reason the above did not work, you can go back to a
previous set of drivers etc. Assuming you have not closed the root window
above, type "ls" and look for what set of finder-xxxx directories you
see.

[9] Type "ln -sf finder-xxxx finder" where "xxxx" is one of the previous
dates. This should bring things back to the state they were at that date.
Type "initccd" in the other window (where you are logged in as coast)
again.
**************************************************************************

David