Begin and Finish Scripts
With the current releases of Web Start Flash and Live Upgrade (LU), the luupgrade command only provides a mechanism to utilize a JumpStart profile. There is no mechanism to specify a JumpStart begin or finish script for execution before or after the luupgrade.
To circumvent this deficiency, use a shell script that contains the LU commands along with any begin or finish scripts. For example, to automatically execute the EE_Lab-Flash.fin script after a LU Flash installation, the following script could be used:
#!/bin/sh # # If /a does not exist, lumount will create it # lumount Solaris8_10-2001 /a SI_CONFIG_DIR=/net/travigne/jumpstart export SI_CONFIG_DIR # Place execution of Begin script here: # sh ${SI_CONFIG_DIR}/Begin/MyBeginScript.beg luumount Solaris8_10-2001 # # Perform the upgrade/Flash install # luupgrade -f -n "Solaris8_10-2001" -s /net/travigne/jumpstart/OS/Solaris_8_2001-10 -j /net/travigne/jumpstart/Profiles/S8_2001-10-server-Flash.profile # # # lumount Solaris8_10-2001 /a # # Place execution of Finish script here: # SI_CONFIG_DIR=/net/travigne/jumpstart export SI_CONFIG_DIR sh ${SI_CONFIG_DIR}/Finish/EE_Lab-Flash.fin luumount Solaris8_10-2001 |
NOTE
This script is for example purposes only. For clarity, this script does not perform error checking.
Note that since the finish script is not executed within the JumpStart technology framework, this script sets the SI_CONFIG_DIR variable for use by the finish script. If other SI_ environment variables were used by the begin or finish script, you would also need to manually set them in the framework script. Also, the ABE file systems are mounted on /a since most finish scripts expect the newly installed file system to be mounted under /a.
You can use this mechanism to execute finish scripts that configure a logical volume manager, such as Solaris Volume Manager (also known as Solstice_ DiskSuite) or VERITAS Volume Manager, and to automatically bring the boot disk under volume-manager control and mirror it.