-------------------------------------------------- 
README file for the Annex Manager
	--------------------------------------------------
	
	NOTE: You must be root to install Annex Manager. You cannot
	install Annex Manager in the root directory '/'. You must create
	an installation directory. 
0. INTRODUCTION
	 
	 The following installation instructions assume that you have 
	received Annex Manager on tape, cdrom, floppy disk, or you have 
	ftp'ed a tar file from an ftp site. 
	
I.1 MOUNTING CDROM
	
	1. Log in as root to a host with a cdrom drive. This should be
	the same host as your installation host. If the installation host
	does not have a cdrom drive, then login to an NFS accessible
	host. 
	
	2. If necessary Create a mount point for the cdrom:
	 # mkdir /cdrom
	
	 Place Annex Manager distribution on the cdrom. On Solaris 2 
	hosts, if the volume manager mounts the cdrom, you can skip the
	next step. 
	 3. Mount the cdrom
	
	 SunOS4 mount -r -t hsfs /dev/srd0 /cdrom 
	 SunOS5 not required if volume manager is running 
	 HP-UX 9 mount -r -t cdfs /dev/dsk/c3d0s2 /cdrom 
	 AIX 	3/4 mount -o ro -v cdrfs /dev/cd0 /cdrom 
	
	 4. If the cdrom is not on the install host, mount the drive
	remotely on the install host. On the host with the cdrom:
	
	 # /etc/exportfs -i -o ro /cdrom (or equivalent)
	
	 On the install host:
	
	 # mount drive-host:/cdrom /cdrom
	
	 The cdrom will contain the release tar file, this README
	file and the release notes. You do not need to copy the release
	tar file. You can access it directly through the /cdrom mount
	point. 
	 The <tape-dev> will be '/cdrom' (or equivalent). 
	 
I.2 LOADING ANNEX MANAGER FROM TAPE, FLOPPY DISK, or FTP'ED TAR
FILE, or CDROM 
	
	The Annex Manager R2.1 is installed using the same install script
	as the Remote Annex Software. 
	
	
	1. The first step is for the user to create a directory in which
	to extract the setup directory from the media. The setup
	directory will contain the necessary install scripts, release
	notes, and a release version file. The setup directory may be the
	same as the install directory. 
	
	 # mkdir <setup_directory>
	
	2. Change directory to the release directory: 
	
	 # cd <setup_directory>
	
	3.The second step is for the user to extract the setup directory
	from the media. If you are installing from CDROM, the CDROM
	should be in the CDROM drive; if you are installing from tape,
	the tape should be put into the tape drive; if you are installing
	from floppies, the first floppy should be inserted into the
	floppy disk drive; if you are installing from a ftp'd file, the
	<tape-dev> is the full path and name of the tarfile: 
	# tar -xvf <tape-dev> setup
	
II. INSTALLING ANNEX MANAGER
	
	1. To install the Annex Software and/or the Annex Manager,
	execute the setup/install script. 
	dewey# setup/install
	 
	2. The script will prompt the user for information about the type
	of media, and whether to install the Annex Software or the Annex
	Manager. After installing one product, the installation will
	prompt the user to install the other product, or the user may
	quit the installation. 
	
	************************************************************
	* *** It is required that you run this script as root. ***
	************************************************************
	# This command is used to install Annex Software (boot images, security, 
	# command line management) and Annex Manager (X-Motif GUI management 
	# application). 
	#
	#The versions that would be
	#installed are: 
	# Annex Software R11.1
	# Annex Manager R2.1
	#...
	...
	What type of install will be performed?
	1. Floppy Disks
	2. Tape
	3. Tarfile previously copied to hard disk
	4. Reinstall from previously extracted software on hard drive 5.
	Quit
	
	%Enter the install source type [1]: 1
	 
	At this point, the user selects whether to install the Annex
	Software or the Annex Manager. To install the Annex Manager, the
	user enters "2" at the prompt: 
	Indicate desired action:
	1) Install Annex Software
	2) Install Annex Manager
	
	The installation script will continue to install the Annex
	Manager and will prompt the user for information as necessary.
	For more information on the exact questions, please refer to the
	Installation Notes for the Annex Manager. 
	
III. DATA FILES AND FILE PERMISSIONS
	
III.1 DATA FILES CREATED
	
	The following file installed in the bin directory are used by
	Annex Manager at runtime: 
	
	1. users.list contains the user login names that are allowed Set
	privileges during runtime. Only user names listed in the file
	will be allowed to modify Annex paramters. You can use any Unix
	text editor to modify the file. New user names should be added
	one per line. 
	
	2. XKeysymDB_gui_am contains the keyboard bindings. Pleaseuse
	caution if you edit this file to ensure the correct functionality
	of the bindings. Annex Manager searches for XKeysymDB_gui_am
	first in the current directory, then in your home directory then
	in the install directory. 
	
	3. Gui_am is the X resource file. Annex Manager searches for
	Gui_am first in the current directory, then in your home
	directory then in the install directory. 
	
	4. default.chroma contains the default X class name for Annex
	Manager (gui_am_color for Color, gui_am_mono for monochrome.) Use
	the command line options '-mono' or '-color' to override the
	default value. 
	
	5. VERSION, located install directory names, the current version
	of Annex Manager. 
	
III.2 PERMISSIONS
	
	Annex Manager functions with the following directory structure.
	The following permissions are required on the directories and 
	files: 
	DIRECTORY PERMISSIONS
	<install_dir>/bin 775
	<install_dir>/data 775
	<install_dir>/data/anx_scripts 775
	<install_dir>/data/anx_lists 775
	<install_dir>/data/gui_am_data 775
	<install_dir>/data/mdm_cfg 775
	<install_dir>/data/saved_text 775
	
	FILES
	<install_dir>/data/gui_am_data/mib_func.dat 664
	<install_dir>/data/gui_am_data/mib_func_grp.dat 664
	<install_dir>/data/gui_am_data/mib_func_vars.dat 664
	<install_dir>/data/gui_am_data/mib_site_def.dat 664 
	
	You may change the owner, group, or access permissions of these
	directories and files to meet your specific needs. 
	
IV. RUNNING ANNEX MANAGER
	
	1. The following environment variables must be set to run Annex
	Manager: 
	
	GUI_AM_DIR must point to your install directory In csh:% setenv
	GUI_AM_DIR /usr/local/gui_am 
	In sh, ksh:
	$ GUI_AM_DIR=/usr/local/gui_am 
	$ export GUI_AM_DIR
	
	DISPLAY must be set to the proper X display In csh:
	% setenv DISPLAY frog:0.0
	
	In sh, ksh:
	$ DISPLAY=frog:0.0 
	$ export DISPLAY
	
	PATH must include the bin directory in the install directory In
	csh: % set path = ($path $GUI_AM_DIR/bin)
	
	or
	
	% setenv PATH ${PATH}:$GUI_AM_DIR
	
	In sh, ksh:
	$ PATH=$GUI_AM_DIR/bin:$PATH 
	$ export PATH
	
	These environment variables can be set in either your shell's
	startup files (.cshrc,.login,.profile) for your convience. 
	
	2. To run the application, type 'gui_am' at the shell prompt. You
	can supply any of the standard X command line options when
	starting Annex Manager. 
V. UNINSTALLING ANNEX MANAGER
	
	1. If at any time you wish to revert to a previous version of
	Annex Manager, execute the following commands from the install
	directory: 
	# rm bin 
	# rm data 
	# ln -s GUI_AM_<version_number>/bin bin 
	# ln -s GUI_AM_<version_number>/data data 
	# cp GUI_AM_<version_number>/VERSION .
	
	GUI_AM_<version_number> refers to the directory that contains a
	previous release. 
	
