RELEASE_NOTES

  "@(#) $Id: RELEASE_NOTES,v 1.1 2004/10/18 15:38:51 bjeram Exp $"

Module: lcuboot - LCU boot enabler

Changes:
	1.22	SPR 960399 (man-page does not mention error-files) fixed.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version: 1.21 (JUN96)

Documents:
	VLT-MAN-ESO-17210-0855, 1.0, Environments Common Configuration U.M.

From: Stefan Sandrock <ssandroc@eso.org>

Configuration Requirements:
	VxWorks 5.2
	LCC DEC95

Changes:
	1.21:	-
	1.20:	added support for MODROOT environment variable.
	1.19:	Functions for loading ERROR files added.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version: 1.18 (DEC95)

Documents:
	VLT-MAN-ESO-17210-0375, 2.1, LCU Driver Development Guide [updated]

From: Stefan Sandrock <ssandroc@eso.org>

Configuration Requirements:
	VxWorks 5.2
	LCC DEC95

Changes:
	1.18:	-
	1.17:	added CONFIGPATH environment variable.
	1.16:	clean-up of remaining boot files.
	1.15:	adapted to separate VLTROOT/VLTDATA directory branches;
		moved driver/lqs/inducer boot-script to respective modules.
	1.14:	Up to 24 mcon/ampl devices are now supported by default.
	1.13:	UNIX-like PATH environment variables are now used to locate
		binaries and module-boot-scripts; to avoid hardcoded paths.
	1.12:	SPR 950473: increased number of default dev channels to 25.
	1.11:
	- mcon.boot: SPR 950469 (Incorrect address in mcon.boot)
	- lqs.boot: assumes now by default an Rtap boot-env, rather than qsemu.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Version: 1.10 (JUL95)

Documents:
	VLT-MAN-ESO-17210-0375, 2.0, LCU Driver Development Guide [updated]

From: Stefan Sandrock <ssandroc@eso.org>

Configuration Requirements:
	VxWorks 5.1.1
	LCC 2.2

Comments:

The "LCU boot enabler" shall make the creation and maintenance of LCU 
boot-scripts easier. The main features are:

	. Automatic driver and device installation
	. Common module-specific sub-boot-scripts
	. 90% automatic LCU environment variables setup
	. Implementation of a search-path for module loading



	How to convert existing boot-scripts for "lcuboot"?
	---------------------------------------------------

1. Make a backup of your current LCU's bootScript, or rename it:

	cd $VLTROOT/vw/BOOT/<LCU-Env-Name>	(or in INTROOT respectively)
	mv bootScript bootScript.bak

2. Copy the provided `bootScript' template:

	cp $VLTROOT/vw/bin/bootScript .

3. Edit this bootScript to update the "::: ROOT :::" section, e.g.:

	#:::   ROOT   :::
	putenv "VLTROOT=/vlt"
	putenv "INTROOT=/diskb/ssandroc/vlt/INTROOT"	(your own INTROOT)
	putenv "BOOTROOT=/vlt"

4. If you don't need all USER-modules, remove the lines with the corresponding
   module-names in the "::: MODULES :::" and "::: USER :::" sections, 
   e.g. to remove "xntpd":

	lcubootAutoLoad 1,"xntpd",0			REMOVE THIS LINE
	(...)
	lcubootAutoCdBoot 1,"xntpd.boot"		REMOVE THIS LINE
	< xntpd.boot					REMOVE THIS LINE
	

5. Reboot the LCU.
   All devices should be installed automatically, provided that you follow
   the board setups as described in the man-pages acro(4), aio(4), etc.


These steps cover only the most general case. The `userScript' will still be
sourced, so that it might require some adjustment.

Note that there is also a graphical panel provided named `vccConfigLcu',
which allows an easier (?) configuration - for those who like GUIs.



	How to setup module-boot-scripts for your network?
	--------------------------------------------------

Some module-specific boot-scripts (those with ".boot" extension) might require
some network-specific adjustments that are common to all LCUs in it.
The most probable candidates for such a customization are "lqs.boot" 
and "xntpd.boot", where some node-names and IP-addresses must be defined.

1. Copy the respective module-boot-script to the BOOT directory:

	cd $VLTROOT/vw/BOOT			(or in INTROOT respectively)
	cp ../bin/<module>.boot .

2. Edit this copy according to your specific needs. It will have priority
   over the original in "vw/bin".

Refer to the man-pages <module>.boot(5) for more information.



	How to setup module-boot-scripts for a single LCU?
	--------------------------------------------------

If you have the rare case that an LCU needs a different setup for a certain
module than all other LCUs in the network, then:

1. Copy the respective module-boot-script to the LCU's boot-directory:

	cd $VLTROOT/vw/BOOT/<LCU-Env-Name>	(or in INTROOT respectively)
	cp ../../bin/<module>.boot .

2. Edit this copy according to your specific needs. It will have priority
   over the files in "vw/bin" and possibly "vw/BOOT".

Refer to the man-pages <module>.boot(5) for more information.


				___oOo___
