Instructions for installing JGOFS V2.00 "fresh" (i.e., not upgrading from V1.73) -------------------------------------------------------------------------------- Dennis Schmidt August 28, 2007 The new V2.00 tar file is fleetlink:~dschmidt/jgofs-V2.00ds3.tar . Create a JGOFS root directory, and cd to it. Unpack the V2.00 tar file into the root directory: tar xfv jgofs-V2.00ds3.tar >log_v2_install 2>&1 (In that command, provide a path to the tar file if it's not in the JGOFS root directory.) This will produce, in the log file, a list of the files unpacked. Install src/lib/makefile.jgofs: cp -p src/lib/_makefile_.jgofs src/lib/makefile.jgofs Customize build-env.pl for this server. These are the lines that you are likely to need to edit: line 155: $opsys = "Solaris"; (Warren notes: "If not 'Solaris', 'Irix', or 'linux' editing 'outside the lines' will be required") line 168: $perl_location = "/usr/bin/perl"; line 174: $server_name = "optserv1.whoi.edu"; line 175: $port = 8200 (Change this to "$port = 80") line 184: $button_images_server = "globec.whoi.edu"; line 186: $button_images_dir = "images"; line 198: $background_color="808080"; (The background color for NEC, for example, is c4e5dc) line 205: $dmoname = "Option Server"; Either comment out this line (which will set $dmoname to "$server_name -- " (where $server_name is the string set in line 174)), or change the string as desired line 213: # $program = ""; (It's OK to leave this line commented out except for a node in the JGOFS or GLOBEC program) line 418: $objdir = "/"; Leave unedited if objects are to go directly into the objects directory, or name a subdirectory (following the '/') Build the new server: ./build.pl >>log_v2_install 2>&1 Check the output. Note that it's normal to see several instances of a pair of lines of this form (with various text for the various *s in the path): *** make file */src/*/makefile.* does not contain appropriate *** macro name (CONFIG_FILE) to force makes Test operation from the command line: bin/listvar /test >>log_v2_install 2>&1 should produce a hierarchical list of variables. bin/list -f -n /test >>log_v2_install 2>&1 should produce a "flattened" table of data using those variables.