# @(#) 39 1.11 src/bos/usr/lpp/bosinst/bosinst.template/bosinst.template, bosinst, bos43K, 9828A_43K 7/8/98 10:06:23 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos43K src/bos/usr/lpp/bosinst/bosinst.template/bosinst.template 1.11 # # Licensed Materials - Property of IBM # # (C) COPYRIGHT International Business Machines Corp. 1993,1994 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # # COMPONENT_NAME: BOSINST # # FUNCTIONS: none # # ORIGINS: 27 # # # (C) COPYRIGHT International Business Machines Corp. 1993,1997 # All Rights Reserved # Licensed Materials - Property of IBM # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # NOTE: After this first comment section ends, COMMENTS WILL NOT BE ALLOWED. # # NOTE: Stanzas follow these rules: # 1. Stanza names must be at the beginning of the line and end in a colon. # 2. Comments may be after the colon, but THAT'S THE ONLY PLACE!!!! other # than here in the header. Even then, don't expect those comments # to be put back where they were after BOS install gets done processing # this file. We reserve the right to mangle and ignore all comments # which are not placed in this header. # 3. Stanza fields are on lines following stanza names, Stanza fields # must NOT begin at the beginning of the line, but must have tabs or # blanks in front of them. # 4. There can be no blank lines between field lines of the same stanza. # 5. A blank line MUST separate each stanza. In other words, after the # last field line of the stanza, a blank line must follow before the # line containing the stanza name of the next stanza. # # NOTE: In this comment section, the values listed in the fields are the # possible ones separated by a comma. You must pick only one if you are # creating stanzas after the comment section. Field options listed in # angle brackets (<...>) are descriptions of the field and not actually # the values which would go in the field. # # CONTROL_FLOW STANZA: # control_flow defines the flow of control during BOS install. # control_flow: # CONSOLE = < Device which will be your console. Passed to chcons. > # INSTALL_METHOD = overwrite, preserve, migrate # PROMPT = yes,no # EXISTING_SYSTEM_OVERWRITE = yes,no,any # INSTALL_X_IF_ADAPTER = yes,no,all # RUN_STARTUP = yes,no # RM_INST_ROOTS = yes,no # ERROR_EXIT = < Command to run when error occurs. Must be in boot image. > # CUSTOMIZATION_FILE = < Command to run after BOS install finishes. > # TCB = yes, no # INSTALL_TYPE = full (same as if blank), client, personal, eserver # BUNDLES = < Fully qualified Bundle file(s) to install after auto install. # Maximum of 139 bytes total. Custom bundle files # provided on a diskette with the bosinst.data file must # prefix the bundle file pathname with /../. # If the list of bundle file names exceeds 139 bytes, # cat all the bundle files together into a single custom bundle # file and specify the name of the single custom bundle # file.> # RECOVER_DEVICES = yes,no # BOSINST_DEBUG = no,yes # # EXISTING_SYSTEM_OVERWRITE field: # Specifies which disks can be overwritten during the BOS install. # This variable is applicable only for a non-prompted overwrite # installation. If the target_disk_data stanza has no field values, # then the EXISTING_SYSTEM_OVERWRITE field is used to determine which # disks to install on. # If EXISTING_SYSTEM_OVERWRITE is set to 'any' any disk can be # used for the install. # If EXISTING_SYSTEM_OVERWRITE is set to 'no' only disks that # contain no volume group can be used during the install. # If EXISTING_SYSTEM_OVERWRITE is set to 'yes' disks that # contain the existing root volume group will be used first, and # if additional disks are needed those containing no volume group # can be used. # # TARGET DISK DATA STANZA: # There can be multiple target_disk_data stanzas. They define which disk(s) # will contain the root volume group. Only one field (PVID, CONNECTION, # LOCATION, SIZE_MB, HDISKNAME) must be non-null for BOS install to choose a # disk. The order of precedence is PVID (Physical Volume ID), then CONNECTION # (parent attribute//connwhere attribute), then LOCATION, then SIZE_MB, # then HDISKNAME. # If PVID is set, BOS install will check to see if a disk matches the value. # If so, other attributes are ignored. # If PVID is empty and CONNECTION is set, then BOS install will see if the # parent and connwhere attributes (separated by "//") match a disk. If so # other attributes are ignored. # If either PVID or CONNECTION is set, and neither value matches a disk # on the target system, and no other attributes are set, then an error message # will be generated and a disk will have to be explicitly selected. If other # attributes are specified, then processing will occur as described below: # # If LOCATION is set, # BOS install will ignore SIZE_MB and HDISKNAME. If LOCATION is not set and # SIZE_MB is, BOS install will select disks based on SIZE_MB and ignore # HDISKNAME. If LOCATION and SIZE_MB are both empty, BOS install will choose # the disk specified in HDISKNAME. If all three are empty, BOS install will # choose for you. # WARNING: Don't leave the target_disk_data stanza(s) empty if PROMPT = no # unless you don't care which disk BOS install overwrites, because # the algorithm for determining the default disk on which to install # is not always predictable. # The SIZE_MB field can contain either a size or the word 'largest'. If a size # is listed, BOS install will do a best-fit on the disks. If the word 'largest' # is in that field, BOS install will pick the largest disk. If there are more # than one target_disk_data stanza, BOS install will pick the two 'largest' # disks, etc. # # target_disk_data: # PVID = # CONNECTION = # LOCATION = # SIZE_MB = # HDISKNAME = # # LOCALE STANZA: # locale: # BOSINST_LANG = # CULTURAL_CONVENTION = # MESSAGES = # KEYBOARD = # # The optional dump stanza defines the sysdumpdev parameters that will be # in effect after install. By default, the dump stanza is not present. # PRIMARY specifies the primary dump device to be set by sysdumpdev # -P -p . Maximum length 127 bytes. # SECONDARY specifies the secondary dump device to be set by sysdumpdev # -P -s . Maximum length 127 bytes. # COPYDIR specifies the directory to which the dump is copied at system boot. # Maximum length 127 bytes. # FORCECOPY specifies whether the system will boot into menus which allow # copy of the dump to external media if the copy fails. # ALWAYS_ALLOW specifies whether the key mode switch can be ignored when # a dump is requested. # # dump: # PRIMARY = # SECONDARY = # COPYDIR = # FORCECOPY = no, yes # ALWAYS_ALLOW = no, yes control_flow: CONSOLE = /dev/lft0 INSTALL_METHOD = overwrite PROMPT = no EXISTING_SYSTEM_OVERWRITE = yes INSTALL_X_IF_ADAPTER = yes RUN_STARTUP = yes RM_INST_ROOTS = no ERROR_EXIT = CUSTOMIZATION_FILE = TCB = no INSTALL_TYPE = BUNDLES = RECOVER_DEVICES = no BOSINST_DEBUG = no target_disk_data: LOCATION = SIZE_MB = HDISKNAME = hdisk0 locale: BOSINST_LANG = en_US CULTURAL_CONVENTION = en_US MESSAGES = en_US KEYBOARD = de_DE