The details of the installation are described in Appendix B. The system manager decides where to store the distributed files. You start the program by typing
% ono
If the directory where the program load module is placed is not in your $PATH environment variable, you have to specify the complete path name.
On a UNIX system, it is possible use the symbolic links to shorten the path names of the different O directories. If the database is stored in, say,
/usr/local/o/data
you can create a symbolic link to this directory in your own working directory by typing
% ln -s /usr/local/o/data odat
This will create a soft link (pointer) entry in your directory, to the public directory. Then, you can refer to all the files in this directory like this:
odat/startup.o
Alternatively, the user can make use of an environment variable:
% setenv ODAT /usr/local/o/data
When opening a file, O first tries the given file name, then concatenates the contents of the datablock .odat with the given file name, then the environment variable with the file name. We suggest the environment variable be set in the users .cshrc file together with an alias for the program name.
If you have your own directory for macros and other files that you would like O to find, you can add those directories to the system wide default in a colon separated list (version 5.9.2 and later):
% setenv ODAT $ODAT:/usr/people/morten/o/macros
Likewise, you can add paths on separate lines in the .odat datablock.
You cannot specify paths using the ~ character, since O does not expand
these.