iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) NNNNAAAAMMMMEEEE instl_adm - Ignite-UX configuration file syntax DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The Ignite-UX configuration files determine the default system configurations that are available during the process of installing the HP-UX operating system. The Ignite-UX process uses configuration files to bring in default parameters as well as determining how the system will be finally configured. During the installation process, the user is presented with a user interface that allows them to make selections that are implemented inside the configuration files as _v_a_r_i_a_b_l_e_s, _u_s_e _m_o_d_e_l_s, and _s_o_f_t_w_a_r_e _s_e_l_e_c_t_i_o_n_s. The user interface also allows the user to make modifications beyond what is specified by these constructs (such as adding new file systems or volumes). Once the user has approved the configuration, the user-interface writes a configuration file which contains only the changes made in UI. This configuration file is then passed on to another utility that actually performs the system configuration and software loading. OOOOrrrrggggaaaannnniiiizzzzaaaattttiiiioooonnnn aaaannnndddd IIIInnnnddddeeeexxxxiiiinnnngggg ooooffff CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn FFFFiiiilllleeeessss Although all configuration files use the same basic syntax, the information supplied by them is split up into multiple files to allow them to be maintained individually. These configuration files fall into the basic classes of: o+ Default disk and file system layout. Located in ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////RRRReeeellll____{_r_e_l_e_a_s_e}////ccccoooonnnnffffiiiigggg o+ Software description of a single SD depot, or system archive. Located in ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////RRRReeeellll____{_r_e_l_e_a_s_e}////{_f_i_l_e} o+ Local configuration overrides that apply globally. Located in ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ccccoooonnnnffffiiiigggg....llllooooccccaaaallll o+ Named configurations created by saving a configuration via the UI. Located in ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ssssaaaavvvveeeedddd____ccccffffggggssss////**** o+ Client-specific configuration files. Located in ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////cccclllliiiieeeennnnttttssss////0000xxxx{_L_L_A}////ccccoooonnnnffffiiiigggg o+ Boot control parameters and networking information. Located in the first 8K of the file ////oooopppptttt////iiiiggggnnnniiiitttteeee////bbbbooooooootttt////IIIINNNNSSSSTTTTAAAALLLLLLLLFFFFSSSS managed by iiiinnnnssssttttllll____aaaaddddmmmm. In order to completely describe all aspects of a system, it is necessary for Ignite-UX to read multiple configuration files as a combined set. - 1 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) The grouping of the configuration files into sets is accomplished by the use of the INDEX file: ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////IIIINNNNDDDDEEEEXXXX. The INDEX file can contain multiple different sets of configuration files that together describe a unique system configuration. The user interface allows the user to select between the sets of configuration files defined in the INDEX file. The default set of INDEX file sets that come with Ignite-UX are used to define the aspects of each HP-UX release that Ignite-UX supports. A separate INDEX set per HP-UX release is necessary because each HP-UX release has different defaults for file system layout and software bundling. The ability to save a modified configuration through the user interface makes use of the INDEX file sets. When the user interface is used to make modifications to the default configuration, it produces a configuration file that represents what was changed from the defaults. When this delta configuration file is appended to the list of default configuration files, it overrides the defaults with the values the user specified. When a configuration is saved as a named configuration, a new INDEX set is created which contains the default configuration files plus the delta configuration file. Any information stored in the first 8K of the INSTALLFS file as well as the client-specific configuration file is always appended to the list of configuration files, although it is not explicitly listed in the INDEX file set. IIIINNNNDDDDEEEEXXXX FFFFiiiilllleeee CCCCoooonnnntttteeeennnntttt aaaannnndddd SSSSyyyynnnnttttaaaaxxxx INDEX file mentioned above contain configuration file sets, and also may contain a list of scripts that are made available for scheduling from the "Advanced" screen of the user interface. The INDEX file syntax is of the form: ccccffffgggg """"_t_a_g-_s_t_r_i_n_g-_1"""" {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn """"_d_e_s_c_r_i_p_t_i_o_n-_t_e_x_t"""" """"_c_o_n_f_i_g-_f_i_l_e-_p_a_t_h-_1"""" """"_c_o_n_f_i_g-_f_i_l_e-_p_a_t_h-_2..."""" }}}} ccccffffgggg """"_t_a_g-_s_t_r_i_n_g-_2"""" {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn """"_d_e_s_c_r_i_p_t_i_o_n-_t_e_x_t"""" """"_c_o_n_f_i_g-_f_i_l_e-_p_a_t_h-_1"""" """"_c_o_n_f_i_g-_f_i_l_e-_p_a_t_h-_2..."""" }}}} ==== ttttrrrruuuueeee | ffffaaaallllsssseeee ssssccccrrrriiiippppttttssss {{{{ """"_s_c_r_i_p_t-_f_i_l_e-_p_a_t_h-_1"""" """"_s_c_r_i_p_t-_f_i_l_e-_p_a_t_h-_2"""" }}}} - 2 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) In the above example syntax, the ccccffffgggg keyword is used to specify a group of configuration files. The _t_a_g-_s_t_r_i_n_g is what the user interface will see in the selector. The ddddeeeessssccccrrrriiiippppttttiiiioooonnnn keyword supplies additional information that the user interface can see to further describe the selection. After the closing brace, the _c_f_g clause can be selected/unselected by using the ==== ttttrrrruuuueeee|ffffaaaallllsssseeee syntax. This is used to make that particular configuration the default. Only one ccccffffgggg clause can be selected. The last clause that is selected will cause all other clauses to be automatically unselected. See the examples sections on how to set up a ccccffffgggg clause to be conditionally selected. The ssssccccrrrriiiippppttttssss keyword is used to specify a list of file paths to scripts that can be selected and scheduled to run at the end of the system install (See the description of the ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt keyword for more details). GGGGeeeennnneeeerrrraaaallll CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn FFFFiiiilllleeee SSSSttttrrrruuuuccccttttuuuurrrreeee The configuration file is a free-structured file in which white-space is optional and should be used to improve readability. The #### character is used to designate a comment line that extends from the #### character to the end of the line. Some keywords require string arguments. Most keywords that take a string argument may also take a complex string which is a concatenation of strings, variables and system attributes. See below for details. All keywords in the configuration file can be either all lower-case or all capitalized, but not mixed. Variable and use model identifiers are case sensitive. Most keywords, and all variables, that use the ==== assignment operator will also accept the ++++==== operator, which will append the given value to any value that the keyword/variable currently holds. The ++++==== operator has the same effect as ==== when it is the first assignment. Using the ++++==== operator on an integer variable does addition where as string variables/keywords are appended to. There are several constructs in the configuration file syntax where a set of parameters are associated with a specific object. For example, the file system parameters associated with a given file system. If the object being defined has already been defined, then the new parameters will be merged with any parameters previously assigned to the object. It is thus possible to override a small set of parameters while letting the rest be defined in the default configuration file. CCCCoooonnnnssssttttaaaannnnttttssss Integer: Integers can be any set of decimal digits, and can have the - 3 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) suffixes of: MMMMBBBB or KKKKBBBB, which indicates the number is in terms of Megabytes or Kilobytes. An integer can also be in hexadecimal if prefixed by a leading 0000xxxx. String: A string is a text surrounded by double-quote (") characters. If a double-quote is needed inside the string, it must preceded with the back-slash (\) character. No other characters, (including newlines) need to be preceded with a back-slash character. Most keywords also allow for complex strings (_c_p_l_x__s_t_r_i_n_g). Complex strings can be regular quoted strings, or can be a mixture of multiple strings, variable names, mathematical expressions, or system-attribute keywords enclosed with ${} put together using the "+" operator. (For example: "The system contains " + ${num_disks} + " disk drives"). A complex string may also have a format string associated with it to allow for specific formatting to be done when converting the value into a string. The format string is passed directly to sssspppprrrriiiinnnnttttffff. The syntax to specify a format string is as such: mmmmoooodddd____kkkkeeeerrrrnnnneeeellll ++++==== """"mmmmaaaaxxxxddddssssiiiizzzz """" ++++ $$$${{{{""""0000XXXX%%%%XXXX"""" ____mmmmaaaaxxxxddddssssiiiizzzzeeee____vvvvaaaarrrr}}}} (Where "0X%X" is the format string, and causes the value of the variable to be converted to an upper-case hexadecimal value). Boolean: The boolean constants are: ttttrrrruuuueeee////TTTTRRRRUUUUEEEE and ffffaaaallllsssseeee////FFFFAAAALLLLSSSSEEEE. Hardware Path: For keywords that take a hardware path as an index parameter, the hardware path may be a series of more than one digit separated by the .... or //// characters. A complex string or string variable may also be used where a hardware path is expected. VVVVaaaarrrriiiiaaaabbbblllleeeessss The Ignite-UX configuration files support string and integer variables. Variable names must begin with an ____ (underscore) character followed by one or more characters from the set a-z, A-Z, 0-9, or _ (underscore). Integer variables and numeric values are stored internally in KB units when possible. This allows for larger than 4GB values to be operated on and still use a 32 bit value internally . The parser will however convert a value to regular units when addition or subtraction is done using a non-KB value. The parser does not allow a mixture of KB values and non-KB values to be listed as potential values for a variable. When using a variable as part of _c_p_l_x__s_t_r_i_n_g, you may need to add 0 (zero) to the value to force conversion to an non-KB value. For example: "Swap size in bytes: " +${_hp_pri_swap+0} - 4 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) Variables that the user-interface does not recognize as special, will be represented in the _A_d_d_i_t_i_o_n_a_l screen that is available in the advanced user interface from the _B_a_s_i_c tab. From the _A_d_d_i_t_i_o_n_a_l screen the user is allowed to modify the values of any visible variables. Variables do not need to be declared, their type (integer or string) is determined the first time they are assigned, and cannot be assigned a different type later on. Variables may be assigned using two different constructs: iiiinnnniiiitttt __v_a_r_i_a_b_l_e====_v_a_l_u_e Preceding the assignment with the iiiinnnniiiitttt keyword means that the variable is to be initialized to the given value, but the user interface is allowed to alter the value later. __v_a_r_i_a_b_l_e====_v_a_l_u_e When the iiiinnnniiiitttt keyword is not used, then the variable cannot be changed by the user interface. This type of assignment is not recommended for "visible" variables. Variables may be assigned a list of potential values that the user interface can use in generating a selection list that the user can pick from. This is done by using the following syntax: __v_a_r_i_a_b_l_e===={{{{_v_a_l_u_e_1,,,,_v_a_l_u_e_2,,,,............}}}} This sets the list of potential values of the variable to those given. This is for use by the user-interface only, there is no error checking to ensure the resulting value is in the given list. __v_a_r_i_a_b_l_e++++===={{{{_v_a_l_u_e_2,,,,_v_a_l_u_e_3,,,,............}}}} Using the ++++==== operator adds the given values to any existing values specified for that variable. __v_a_r_i_a_b_l_e===={{{{_n_u_m_b_e_r........_n_u_m_b_e_r}}}} A numerical range of potential values may be specified using two numbers (or integer variables/keywords) separated by two dots. __v_a_r_i_a_b_l_e===={{{{ddddiiiisssskkkk[[[[****]]]],,,, ddddiiiisssskkkk[[[[****====_X]]]]}}}} Creates a list of potential values made of of the HW paths of all the disks in the first case, and the first "X" number of disks in the second case. This is useful when a user needs to pick from the list of available disks on the system. Variables who's value should be restricted to one of the list of potential values can be specified as an enumeration variable using the eeeennnnuuuummmm keyword as such: eeeennnnuuuummmm __v_a_r_i_a_b_l_e - 5 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) Variables that should not be displayed in the user interface should be set to invisible using the syntax: __v_a_r_i_a_b_l_e vvvviiiissssiiiibbbblllleeee____iiiiffff ffffaaaallllsssseeee The hhhheeeellllpppp____tttteeeexxxxtttt keyword may be used to specify a longer more descriptive name for the variable that the user-interface can use in the _A_d_d_i_t_i_o_n_a_l screen. The syntax is: __v_a_r_i_a_b_l_e hhhheeeellllpppp____tttteeeexxxxtttt _s_t_r_i_n_g SSSSppppeeeecccciiiiaaaallll VVVVaaaarrrriiiiaaaabbbblllleeeessss There are several variables that are treated specially by the user interface, or other parts of the Ignite-UX process. These are listed below: ____hhhhpppp____pppprrrriiiimmmmaaaarrrryyyy____ppppaaaatttthhhh String variable set during the initial startup of Ignite-UX on the client. The variable is set to the system's primary boot path (as set in stable storage and read with sssseeeettttbbbbooooooootttt). If the system's primary boot path is incorrectly set to a non-existent device, then _hp_primary_path will be set to the empty string (""). ____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk String variable that is set by the UI to contain the hardware path of the disk that the user has chosen to be the root disk. The value is initialized to the value of _hp_primary_path in /opt/ignite/data/Rel_*/config, and can be overridden in other config files. If no config file was to set the initial value, then it would default to the disk with the hardware path with the highest SCSI priority (which was the case in Ignite-UX versions 1.07 and prior). ____hhhhpppp____rrrrooooooootttt____ggggrrrrpppp____ddddiiiisssskkkkssss An integer variable to indicate how many disks to put into the root volume group. ____hhhhpppp____rrrrooooooootttt____ggggrrrrpppp____ssssttttrrrriiiippppeeeedddd A string variable of possible values "YES" and "NO" to indicate if LVM data striping should be used on all disks in the root volume group (in the case that multiple disks are in the root group). ____hhhhpppp____ddddiiiisssskkkk____llllaaaayyyyoooouuuutttt String variable that is set by the UI to indicate which disk layout (LVM, whole-disk, etc) that the user has selected. As configurations are saved, the list of values that it can have will be increased to contain any modified layouts. - 6 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ____hhhhpppp____pppprrrriiii____sssswwwwaaaapppp Integer variable that is set by the UI to indicate how much swap the user desires to have allocated on the root disk/volume-group. The default LVM primary swap volume is defined as a size range with _hp_pri_swap being the desired size and the minimum size is defined by _hp_min_swap. ____hhhhpppp____mmmmiiiinnnn____sssswwwwaaaapppp Integer variable that is used as the minimum size the primary swap volume can be reduced to if there is not enough disk space for all other volumes. This value defaults to an amount that should allow the system to boot and run HP-UX. ____hhhhpppp____aaaaddddddddnnnnllll____ffffssss____ffffrrrreeeeeeee____ppppcccctttt Integer variable used to control the amount of additional free space (or "breathing room") allocated to volumes beyond the space required to load the software. If the variable is not set, it will default to 10 (10%). See the definition for the file system ssssiiiizzzzeeee keyword attribute for more details. ____hhhhpppp____iiiiggggnnnnoooorrrreeee____sssswwww____iiiimmmmppppaaaacccctttt Integer variable that can be set to 1 if you want to disable all effects that the iiiimmmmppppaaaaccccttttssss statements declared in the software selections have on the volume size calculations. This may be helpful if you want to ensure that IUX does not automatically modify the file-system volume sizes. ____hhhhpppp____ccccuuuussssttttoooommmm____ssssyyyyssss String variable that is used in conditional statements surrounding network and system identity information when the GUI writes out a config file. This variable may be used in conditionals in config files to define a multiple sets of network parameters that can be selected from in the "Additional" screen. You can see how this variable is used by doing a "Save As" operation during an install after modifying the parameters under the "System" tab and looking at the resulting file in the /var/opt/ignite/saved_cfgs directory. ____hhhhpppp____ddddeeeeffffaaaauuuulllltttt____ccccuuuurrrr____llllaaaannnn____ddddeeeevvvv String variable set to the LAN device that is enabled during the Ignite-UX process. It is used when a lan device is omitted from keywords that can accept LAN interface specifier. This defaults to the interface that the user picked during the install, or in the non-interactive case, it will default to to the lan device the system booted from or to llllaaaannnn0000 if not a network boot. ____hhhhpppp____ddddeeeeffffaaaauuuulllltttt____ffffiiiinnnnaaaallll____llllaaaannnn____ddddeeeevvvv String variable similar to ____hhhhpppp____ddddeeeeffffaaaauuuulllltttt____ccccuuuurrrr____llllaaaannnn____ddddeeeevvvv, but is used in the case that network information is specified by using the ffffiiiinnnnaaaallll keyword. It will default to ____hhhhpppp____ddddeeeeffffaaaauuuulllltttt____ccccuuuurrrr____llllaaaannnn____ddddeeeevvvv if not set. - 7 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ____hhhhpppp____llllaaaannnnaaaaddddmmmmiiiinnnn____aaaarrrrggggssss If your network requires that the default MTU or speed be changed via the lanadmin(1M) command to operate correctly, you can specify the arguments to the lanadmin command via this variable. This variable setting must be done in the INSTALLFS file using the iiiinnnnssssttttllll____aaaaddddmmmm command. Any changes made with this variable only has effect during the installation and does not get permanently applied to the system. For example to set the MTU size to 1500 the line would be iiiinnnniiiitttt ____hhhhpppp____llllaaaannnnaaaaddddmmmmiiiinnnn____aaaarrrrggggssss====""""----MMMM 1111555500000000"""" To set the speed for a 100-Base-T interface to full duplex (the default is half duplex) you could use the setting: iiiinnnniiiitttt ____hhhhpppp____llllaaaannnnaaaaddddmmmmiiiinnnn____aaaarrrrggggssss====""""----SSSS 1111"""" Note that setting the MTU value with llllaaaannnnaaaaddddmmmmiiiinnnn only works for the NIO/HPPB FDDI interface. A future release of Ignite-UX may not use this config file variable method in order that the appropriate command for the interface will be used. ____hhhhpppp____nnnnffffssss____mmmmoooouuuunnnntttt____ooooppppttttssss String variable that may be set in the INSTALLFS file and used to supply additional options to the NFS mounts that are performed during the installation. This is intended for use when the default options are not appropriate for your network. (See _m_o_u_n_t__n_f_s(1M) for valid options). For example, to set the read and write NFS buffer size to 1K: iiiinnnniiiitttt ____hhhhpppp____nnnnffffssss____mmmmoooouuuunnnntttt____ooooppppttttssss====""""----oooorrrrssssiiiizzzzeeee====1111000022224444 ----oooowwwwssssiiiizzzzeeee====1111000022224444"""" ____hhhhpppp____nnnnffffssss____mmmmoooouuuunnnntttt____rrrreeeettttrrrriiiieeeessss An integer variable used to modify the default number of times that the NFS mounts are retried before failing. If this variable is not set, the mounts will be retried 4 times before giving up. If you need to change this default, this variable should be specified in the INSTALLFS file. For example to set the number of retries to 8: iiiinnnniiiitttt ____hhhhpppp____nnnnffffssss____mmmmoooouuuunnnntttt____rrrreeeettttrrrriiiieeeessss====8888 ____hhhhpppp____ttttffffttttpppp____ccccmmmmddddssss A string variable that can be specified in the INSTALLFS file to supply additional instructions to the ttttffffttttpppp commands that are used to transfer data during an installation. The commands supplied with this variable are passed as input to the ttttffffttttpppp command along with the usual commands supplied by Ignite-UX. The most likely use of this would be to modify the retransmission-timeout (rexmt) and overall timeout (timeout) values. The default values that Ignite-UX uses are: rexmt=2 timeout=25. (See _t_f_t_p(1) for more details). The string assigned to this variable should contain one tftp command statement per line. For example: iiiinnnniiiitttt ____hhhhpppp____ttttffffttttpppp____ccccmmmmddddssss====""""rrrreeeexxxxmmmmtttt 5555 ttttiiiimmmmeeeeoooouuuutttt 44440000"""" - 8 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ____hhhhpppp____llllooooccccaaaalllleeee String variable that the UI sets to the language locale that the user has chosen. If set to the string "ASK_AT_FIRST_BOOT" then the _g_e_o_c_u_s_t_o_m_s(1M) application will be invoked when the installation is complete to allow the user to pick which language is desired. (Note that ggggeeeeooooccccuuuussssttttoooommmmssss is not available prior to the 10.30 HP-UX release). Setting the value to "SET_NULL_LOCALE" leaves the system to default with no LANG variable set, in which case commands will use the internal messages which provide better performance. If ____hhhhpppp____llllooooccccaaaalllleeee is not set, it will be set internally to the first value of the llllooooccccaaaalllleeee keyword for a selected sssswwww____sssseeeellll.... If there are multiple selected sssswwww____sssseeeellllssss which contain llllooooccccaaaalllleeee keywords, the ____hhhhpppp____llllooooccccaaaalllleeee variable is set to the first value of the llllooooccccaaaalllleeee of the first selected sw_sel. ____hhhhpppp____kkkkeeeeyyyybbbbooooaaaarrrrdddd String variable that the UI sets to the keyboard language/mapping desired. The kkkkbbbbddddllllaaaannnngggg keyword that was used for this in past releases is equivalent to this variable. Setting this variable in the INSTALLFS file (via iiiinnnnssssttttllll____aaaaddddmmmm) will prevent the system from prompting for a keyboard type during the install. This information is stored in ////eeeettttcccc////kkkkbbbbddddllllaaaannnngggg on the final system. ____hhhhpppp____hhhhiiiiddddeeee____ooootttthhhheeeerrrr____ddddiiiisssskkkkssss String variable that can be set to one or more space separated hardware paths of disks that should be "hidden" from being configured or otherwise modified during the install. It allows for more disks to be hidden than what is provided by the hhhhiiiiddddeeee____bbbbooooooootttt____ddddiiiisssskkkk keyword. ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll This is an internal string variable that is fundamental in the configuration file management done by Ignite-UX. It is used primarily in the client-specific configuration files. It contains a list of option characters that represent which aspects of the configuration file have been modified by the user interface. This ends up representing the areas of information that the configuration file written by the UI contains. The Ignite-UX process uses this information in the case that it needs to rewrite the configuration file. The configuration file is rewritten both by the user interface and by the client installation process. In these cases, the process uses ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll to know how much information is represented by the configuration file and so it can write out just the minimal amount of information and let the rest be supplied by the other configuration files in the INDEX file set. - 9 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) The option characters recognized in the ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll string that may be found in a client-specific ccccoooonnnnffffiiiigggg file are: ''''iiii'''' Index ccccffffgggg clause selection (file contains the line telling which INDEX file entry should be used). ''''vvvv'''' Variable and use model settings. ''''ssss'''' Software selection settings. ''''SSSS'''' Modified software selection definitions. ''''rrrr'''' Modified software source definitions (depot information). ''''ffff'''' Modified file system information. ''''pppp'''' System identity information. ''''tttt'''' ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt selections settings. ''''hhhh'''' Hardware control information (hhhhwwww____iiiinnnnssssttttaaaannnncccceeee____nnnnuuuummmm statements). ''''llll'''' Other control information (global mod_kernel statements for example). For example, the line: ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll====""""iiiivvvvsssspppp"""" in a client configuration file would indicate that the file contains information about which ccccffffgggg INDEX selection to be used, the variable settings, software selection settings, and system parameters. ____hhhhpppp____ssssaaaavvvveeeedddd____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll This is an internal string variable used in configuration files which have been created by a "Save-As" operation. Like ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll,,,, it contains a list of option characters that represent which aspects of the configuration file have been modified. The format is identical to the ____hhhhpppp____ccccffffgggg____ddddeeeettttaaaaiiiillll____lllleeeevvvveeeellll variable. ____hhhhpppp____oooossss____bbbbiiiittttnnnneeeessssssss String variable used beginning at B.11.00. Starting at B.11.00, HP software is packaged for running on a 32 bit operating system, 64 bit operating system, or both. The ____hhhhpppp____oooossss____bbbbiiiittttnnnneeeessssssss variable is set to either "32" or "64" when an operating system is chosen. This is normally done in a config file by keying off of the sssswwww____sssseeeellll for a 32 or 64 bit operating system. The sssswwww____sssseeeellll statements for certain applications rely on the setting of this variable to tell which version of the application to install. ____hhhhpppp____ffffoooorrrrcccceeee____aaaauuuuttttoooobbbbooooooootttt String variable that can be used to modify Ignite-UX's behavior - 10 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) with respect to stable store's autoboot flag. Ignite-UX's configuration process has two parts separated by a reboot. By default ((((____hhhhpppp____ffffoooorrrrcccceeee____aaaauuuuttttoooobbbbooooooootttt====""""YYYYEEEESSSS"""")))),,,, Ignite-UX will guarantee that autoboot is set during the installation process and then reset to its previous state (if necessary) at the end of the installation. If ____hhhhpppp____ffffoooorrrrcccceeee____aaaauuuuttttoooobbbbooooooootttt====""""NNNNOOOO"""",,,, Ignite-UX will not touch the autoboot flag in stable storage. Note that this may mean that you will have to do a manual boot from the primary path between the two parts of the Ignite-UX installation. UUUUsssseeee MMMMooooddddeeeellll VVVVaaaarrrriiiiaaaabbbblllleeeessss The configuration file parser also supports an older version of variables that existed in previous releases. These are referred to as _u_s_e _m_o_d_e_l_s. They are boolean variables in which the variable itself is a string and its value is either true or false. The variable name is presented in the UI, and the user is allowed to toggle the boolean value. Similar to variables, use models may be made invisible to the UI using the vvvviiiissssiiiibbbblllleeee____iiiiffff keyword. Ignite-UX does not support the sssseeeelllleeeeccccttttaaaabbbblllleeee____iiiiffff or rrrraaaaddddiiiioooo____sssseeeellll keywords that previous releases supported. The rrrraaaaddddiiiioooo____sssseeeellll functionality is replaced by the ability for regular variables to have a list of possible values associated with them. Additionally, the hhhheeeellllpppp____tttteeeexxxxtttt keyword for use models has no effect. Use models use the same iiiinnnniiiitttt keyword as regular variables. When a use model is assigned using the init keyword, this allows the UI to change that variable value. An example of how use models are used is shown below: iiiinnnniiiitttt """"_u_s_e _m_o_d_e_l _n_a_m_e"""" ==== TTTTRRRRUUUUEEEE iiiinnnniiiitttt """"_u_s_e _m_o_d_e_l _n_a_m_e"""" ==== nnnnuuuummmm____ddddiiiisssskkkkssss >>>> 2222 """"_u_s_e _m_o_d_e_l _n_a_m_e"""" vvvviiiissssiiiibbbblllleeee____iiiiffff ((((mmmmeeeemmmmoooorrrryyyy >>>> 66664444MMMMBBBB)))) LLLLooooggggiiiicccc EEEExxxxpppprrrreeeessssssssiiiioooonnnnssss A block of configuration statements may be surrounded by a logic expression and a set of {{{{ }}}} brackets. The logic expression may be made up of variables, use models or system attributes. The following logic operators are recognized (in order of precedence): (((( )))) Parentheses can be used to group expressions in order to force precedence. !!!! Logical not operator. ======== !!!!==== ~~~~ Comparison operators: equal, not-equal and regular expression match, respectively. The ======== and !!!!==== operators compare strings in a case-insensitive manner. The ~~~~ character is a regular expression comparison operator. The right side of ~~~~ is treated - 11 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) as a extended regular expression string when compared to the left side string (See _r_e_g_e_x_p(5)). >>>> <<<< >>>>==== <<<<==== Comparison operators: greater-than, less-than, greater-or-equal, and less-or-equal, respectively. &&&& Logical _a_n_d operator. |||| Logical _o_r operator. Variables in logic expressions must use one of the comparison operators to result in a boolean value. Use model names can appear in logic expressions and are treated as a single boolean value. Following the set of statements surrounded by {{{{ }}}} you may supply an eeeellllsssseeee clause followed by a set of statements enclosed in {{{{ }}}} brackets. You may also have conditional statements within conditional statements. Example: ((((nnnnuuuummmm____ddddiiiisssskkkkssss >>>> 1111 &&&& ddddiiiisssskkkk[[[[____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk]]]]....ssssiiiizzzzeeee <<<< 555500000000MMMMBBBB)))) |||| """"UUUUsssseeee aaaallllllll tttthhhheeee ddddiiiisssskkkkssss"""" |||| hhhhaaaarrrrddddwwwwaaaarrrreeee____mmmmooooddddeeeellll ~~~~ """"9999000000000000////8888....****"""" |||| LLLLLLLLAAAA[[[[]]]] ======== """"000088880000000000009999111155550000333311115555"""" |||| ((((____mmmmyyyy____vvvvaaaarrrr >>>> 22220000MMMMBBBB &&&& ____mmmmyyyy____ssssttttrrrr____vvvvaaaarrrr ~~~~ """"YYYY....****"""")))) {{{{ _s_t_a_t_e_m_e_n_t_s ((((nnnnuuuummmm____ddddiiiisssskkkkssss >>>> 2222)))) {{{{ _s_t_a_t_e_m_e_n_t_s }}}} eeeellllsssseeee {{{{ _s_t_a_t_e_m_e_n_t_s }}}} }}}} MMMMaaaatttthhhheeeemmmmaaaattttiiiiccccaaaallll OOOOppppeeeerrrraaaattttiiiioooonnnnssss The configuration file supports the use of the ****, //// , ++++, and ---- operators when dealing with integer constants, variables, or system attributes that evaluate to an integer value. For example: iiiinnnniiiitttt ____hhhhpppp____pppprrrriiii____sssswwwwaaaapppp ==== MMMMEEEEMMMMOOOORRRRYYYY **** 2222 SSSSyyyysssstttteeeemmmm AAAAttttttttrrrriiiibbbbuuuutttteeee KKKKeeeeyyyywwwwoooorrrrddddssss The system attribute keywords that can be used in logic expression comparisons, mathematical operations (those with integer values), or in complex strings are: ddddiiiisssskkkk[[[[_h_w-_p_a_t_h|_i_n_d_e_x]]]]....ssssiiiizzzzeeee Evaluates to the size (in KB units) of the disk corresponding to the hardware path or index value specified. Either a full hardware path or a single _i_n_d_e_x integer (or integer variable) may be used to specify the disk. The _i_n_d_e_x value may range from 0 to - 12 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) nnnnuuuummmm____ddddiiiisssskkkkssss----1111. If an _i_n_d_e_x is specified equal to or greater than nnnnuuuummmm____ddddiiiisssskkkkssss, the size value will be zero. Example: ddddiiiisssskkkk[[[[2222////0000////1111....6666....0000]]]]....ssssiiiizzzzeeee ddddiiiisssskkkk[[[[____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk]]]]....ssssiiiizzzzeeee ddddiiiisssskkkk[[[[0000]]]]....ssssiiiizzzzeeee ddddiiiisssskkkk[[[[_h_w-_p_a_t_h|_i_n_d_e_x]]]]....mmmmooooddddeeeellll Evaluates to the model string as reported by the disk specified by the hardware address path or index value. ddddiiiisssskkkk[[[[_h_w-_p_a_t_h|_i_n_d_e_x]]]]....ddddrrrriiiivvvveeeerrrr Evaluates to the device driver used to support the disk specified by the hardware address path or index value. ddddiiiisssskkkk[[[[_h_w-_p_a_t_h|_i_n_d_e_x]]]] ddddiiiisssskkkk[[[[****]]]] ddddiiiisssskkkk[[[[****====_N]]]] Evaluates to a string that contains the hardware path(s) of the disk(s) referenced. In the first usage shown above, the string will contain the hardware path of the disk matching the specific _h_w-_p_a_t_h or the _i_n_d_e_x value. In the second usage, the string will be a list of all hardware paths of disks on the system. Similarly, the third usage will result in a string of hardware paths for the first _N disks. The second and third usages may be useful when defining a list of potential values a variable can hold and displayed in the user-interface. For example: eeeennnnuuuummmm ____mmmmyyyy____vvvvaaaarrrr ____mmmmyyyy____vvvvaaaarrrr ==== {{{{ ddddiiiisssskkkk[[[[****]]]] }}}} nnnnuuuummmm____ddddiiiisssskkkkssss Evaluates to the number of disks discovered on the system. ggggrrrraaaapppphhhhiiiiccccssss[[[[[_h_w-_p_a_t_h/_i_n_s_t_a_n_c_e]]]]]....mmmmooooddddeeeellll Evaluates to the model number of the graphics hardware at the given hardware path or instance number. If the _h_w-_p_a_t_h/_i_n_s_t_a_n_c_e is not given then it defaults to instance 0. It will evaluate to an empty string if a device at the specified _h_w-_p_a_t_h/_i_n_s_t_a_n_c_e does not exist. ggggrrrraaaapppphhhhiiiiccccssss[[[[[_h_w-_p_a_t_h/_i_n_s_t_a_n_c_e]]]]]....iiiidddd Evaluates to the ccccrrrrtttt____iiiidddd as reported by the device. This is an integer value and will evaluate to 0 if the device does not exist. This value is obtained using the GCDESCRIBE ioctl. ggggrrrraaaapppphhhhiiiiccccssss[[[[[_h_w-_p_a_t_h/_i_n_s_t_a_n_c_e]]]]]....ppppllllaaaannnneeeessss Evaluates to the number of image planes that the indicated graphics device supports. Will evaluate to 0 if the device does not exist. ggggrrrraaaapppphhhhiiiiccccssss[[[[[_h_w-_p_a_t_h/_i_n_s_t_a_n_c_e]]]]]....rrrreeeessssoooolllluuuuttttiiiioooonnnn____xxxx Evaluates to the number of pixels of resolution in the XXXX direction that the graphics device is currently set to. ggggrrrraaaapppphhhhiiiiccccssss[[[[[_h_w-_p_a_t_h/_i_n_s_t_a_n_c_e]]]]]....rrrreeeessssoooolllluuuuttttiiiioooonnnn____YYYY Evaluates to the number of pixels of resolution in the YYYY direction that the graphics device is currently set to. - 13 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) Graphics example that detects when there is more than one graphics device and gives a note message in that case: ggggrrrraaaapppphhhhiiiiccccssss[[[[1111]]]]....ppppllllaaaannnneeeessss !!!!==== 0000 {{{{ NNNNOOOOTTTTEEEE ++++==== """"SSSSyyyysssstttteeeemmmm hhhhaaaassss mmmmoooorrrreeee tttthhhhaaaannnn oooonnnneeee ggggrrrraaaapppphhhhiiiiccccssss ccccaaaarrrrdddd,,,, sssseeeeccccoooonnnndddd ccccaaaarrrrdddd iiiissss aaaa mmmmooooddddeeeellll:::: """" ++++ $$$${{{{ggggrrrraaaapppphhhhiiiiccccssss[[[[1111]]]]....mmmmooooddddeeeellll}}}} }}}} mmmmeeeemmmmoooorrrryyyy Evaluates to the amount of memory installed on the system. ccccaaaannnn____rrrruuuunnnn____33332222bbbbiiiitttt ccccaaaannnn____rrrruuuunnnn____66664444bbbbiiiitttt Boolean values that indicate if the system's hardware is capable of running 32-bit or 64-bit HP-UX operating system respectively. hhhhaaaarrrrddddwwwwaaaarrrreeee____mmmmooooddddeeeellll Evaluates to a string holding the equivalent of the uuuunnnnaaaammmmeeee ----mmmm command. mmmmooooddddeeeellll Evaluates to a string holding the equivalent of the "model" command which is typically more descriptive than uuuunnnnaaaammmmeeee ----mmmm. nnnnuuuummmm____ccccppppuuuussss Evaluates to the number of active processors discovered on the system. nnnnuuuummmm____llllaaaannnnssss Evaluates to the number of LAN hardware devices discovered on the system. llllllllaaaa[[[[[_h_w-_p_a_t_h/_i_n_t_e_r_f_a_c_e]]]]] Evaluates to a string holding the lan-link address (or station address) of the system. The string will be in the form of a hex number (without a leading 0x). Evaluates to "unknown" if the system does not have a LAN interface. The _h_w-_p_a_t_h/_i_n_t_e_r_f_a_c_e specifier may be omitted (however the square-brackets must still be used), or it can be the full hardware path to the lan device, or it can be a lan interface name. When the specifier is omitted, the value of the variable ____hhhhpppp____ddddeeeeffffaaaauuuulllltttt____ccccuuuurrrr____llllaaaannnn____ddddeeeevvvv is used (see the special variables described above). For example: llllllllaaaa[[[[]]]] ======== """"000088880000000000009999111122223333444455556666"""" |||| llllllllaaaa[[[[2222////0000////2222]]]] ======== """"000088880000000000009999666655554444333322221111"""" |||| llllllllaaaa[[[[""""llllaaaannnn0000""""]]]] ======== """"000088880000000000009999666655554444333322221111"""" {{{{ _s_t_a_t_e_m_e_n_t_s }}}} iiiipppp____aaaaddddddddrrrr[[[[[_h_w-_p_a_t_h/_i_n_t_e_r_f_a_c_e]]]]] Evaluates to a string holding the IP address of the system as set by the user, by DHCP, or by the configuration file. This is the value used during the installation, not the "final" value. If not set in the configuration file, this value will not be set on initial boot, but will be set by the user during an interactive installation. The _h_w-_p_a_t_h/_i_n_t_e_r_f_a_c_e specifier follows the same rules as the llllllllaaaa keyword above. llllaaaannnn[[[[[_h_w-_p_a_t_h/_i_n_t_e_r_f_a_c_e]]]]]....ddddrrrriiiivvvveeeerrrr Evaluates to the device driver string name used to support the specified LAN device (e.g. "lan1", "btlan3", etc). The _h_w- - 14 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) _p_a_t_h/_i_n_t_e_r_f_a_c_e specifier follows the same rules as the llllllllaaaa keyword above. ssssyyyysssstttteeeemmmm____nnnnaaaammmmeeee Evaluates to a string holding the hostname of the system as set by the user, by DHCP, or by the configuration file. This is the value used during the installation, not the "final" value. If not set in the configuration file, this value will not be set on initial boot, but will be set by the user during an interactive installation. ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee Evaluates to a string indicating the type of media being installed from. This can be one of the following: """"DDDDSSSSKKKK"""" (if a CD-ROM), """"MMMMTTTT"""" (if DDS or mag-tape), """"NNNNEEEETTTT"""" (if using a network server). rrrreeeelllleeeeaaaasssseeee A string corresponding to which HP-UX release the configuration file holds the system defaults for. (i.e "B.10.10", "B.10.20", etc). iiiissss____nnnneeeetttt____iiiinnnnffffoooo____tttteeeemmmmppppoooorrrraaaarrrryyyy A boolean value that reflects the choice made by the user in the network information screen, or as set using the keyword of the same name in the configuration file. ((((sssswwww____sssseeeellll _s_t_r_i_n_g)))) A boolean value that reflects whether or not the software selection tag given as _s_t_r_i_n_g has been selected for loading or not. Note: It is not advisable to initialize variables within a sssswwww____sssseeeellll conditional because the variables will not be re- initialized if a user make a change to the sssswwww____sssseeeellll in the user- interface. ((((ccccffffgggg _s_t_r_i_n_g)))) A boolean value that reflects whether or not the INDEX file selection referenced by _s_t_r_i_n_g is the one being used for this installation. FFFFiiiilllleeee SSSSyyyysssstttteeeemmmm CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn The default disk and file system configuration can be specified as a ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk or a vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp. In a ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk configuration, each disk can have a maximum of two partitions. One partition being a file system and the other being swap space. This configuration is also referred to as the "whole disk" layout. The vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp configuration allows one or more disks to be configured into a Logical Volume Manager (LVM) volume group. That volume group can then be split up into one or more logical volumes. Each logical volume can be used for either file system or swap space. A volume group can also be split into one or more physical volume groups, with at least one disk in each physical volume group. The general syntax of the disk and file system configuration is: ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk {{{{ pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ddddiiiisssskkkk[[[[_h_w__p_a_t_h|_i_n_d_e_x]]]] {{{{ _p_h_y_s_i_c_a_l__v_o_l_u_m_e-_a_t_t_r_i_b_u_t_e_s... - 15 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) }}}} ffffssss____ppppaaaarrrrttttiiiittttiiiioooonnnn {{{{ _f_i_l_e-_s_y_s_t_e_m-_a_t_t_r_i_b_u_t_e_s... }}}} sssswwwwaaaapppp____ppppaaaarrrrttttiiiittttiiiioooonnnn {{{{ _s_w_a_p-_a_t_t_r_i_b_u_t_e_s... }}}} }}}} vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp _g_r_o_u_p__n_a_m_e {{{{ _v_o_l_u_m_e__g_r_o_u_p-_a_t_t_r_i_b_u_t_e_s... pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ggggrrrroooouuuupppp "_p_v_g_n_a_m_e" {{{{ pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ddddiiiisssskkkk[[[[_h_w__p_a_t_h|_i_n_d_e_x]]]] {{{{ _p_h_y_s_i_c_a_l__v_o_l_u_m_e-_a_t_t_r_i_b_u_t_e_s... }}}} ... }}}} ... pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ddddiiiisssskkkk[[[[_h_w__p_a_t_h|_i_n_d_e_x]]]] {{{{ _p_h_y_s_i_c_a_l__v_o_l_u_m_e-_a_t_t_r_i_b_u_t_e_s... }}}} ... llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee {{{{ _f_i_l_e-_s_y_s_t_e_m/_s_w_a_p-_a_t_t_r_i_b_u_t_e_s... }}}} llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee "_l_v_n_a_m_e" {{{{ _f_i_l_e-_s_y_s_t_e_m/_s_w_a_p-_a_t_t_r_i_b_u_t_e_s... }}}} ... }}}} The keywords and attributes used for disk configuration are described below: ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk Begins the specification of a disk that can be partitioned into one or two simple partitions. The disk can be used for file system, swap, or file system and swap. This is also referred to as the "whole disk" layout. vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp _g_r_o_u_p__n_a_m_e Begins the specification in which one or more disks can be put into Physical Volume Groups, Logical Volume Group, and then split up into one or more logical volumes. _g_r_o_u_p__n_a_m_e must be a quoted string typically of the form """"vvvvgggg_N_N"""" where _N_N is a two digit number. However the name may be any string representing a valid directory name. - 16 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ggggrrrroooouuuupppp _p_v_g_n_a_m_e Specifies a physical volume group as part of the current vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp. _p_v_g_n_a_m_e must be a quoted string. All disks listed inside the data structure become a member of the physical volume group. At least one disk must be a member. pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee ddddiiiisssskkkk[[[[_h_w__p_a_t_h|_i_n_d_e_x]]]] Specifies the disk to use for the current configuration. _h_w__p_a_t_h is the hardware path of the disk (as reported by _i_o_s_c_a_n(1M)). _h_w__p_a_t_h can also be a string variable such as the special variable ____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk, which will correspond to the disk the user chose from the user interface. The ____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk variable can also be set in the configuration file, but by default is the hw_path of the disk with the highest SCSI priority. _h_w__p_a_t_h can also be the **** character in which case all non- configured disks will be included into the vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp. Or in the case of a partitioned_disk, one non-configured disk will be used. Another form of _h_w__p_a_t_h can be ****====_N where _N is the number of disks that should be put into the vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp. An alternative to using an explicit hardware path is to use a integer (or integer variable) _i_n_d_e_x value. If an _i_n_d_e_x value is used, it should be in the range of 0 to nnnnuuuummmm____ddddiiiisssskkkkssss----1111. Following pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee, can be a block of physical_volume- attributes surrounded by {{{{ }}}} brackets. These attributes will be described in the following sections. ffffssss____ppppaaaarrrrttttiiiittttiiiioooonnnn In a ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk configuration, this keyword starts the specification for the file system partition of the disk. The block following this keyword is surrounded by {{{{ }}}} brackets and consists of file-system-attributes. File-system-attributes will be described in the following sections. sssswwwwaaaapppp____ppppaaaarrrrttttiiiittttiiiioooonnnn In a ppppaaaarrrrttttiiiittttiiiioooonnnneeeedddd____ddddiiiisssskkkk configuration, this keyword starts the specification for the swap partition of the disk. The block following this keyword is surrounded by {{{{ }}}} brackets and consists of subset of the file-system-attributes (namely the ssssiiiizzzzeeee, uuuussssaaaaggggeeee, and optionally the mmmmoooouuuunnnntttt____ppppooooiiiinnnntttt). These-attributes will be described in the following sections. llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee _c_p_l_x__s_t_r_i_n_g Defines a logical volume that should be part of the current vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp. A volume group can contain any number of logical volumes. The logical volume may optionally be given an name by specifying a _c_p_l_x__s_t_r_i_n_g after the llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee keyword. If you do not supply a name, it will use the default of "lvolX", where X is the creation number of the logical volume. Following the llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee statement is a block of file-system/swap- attributes. PPPPhhhhyyyyssssiiiiccccaaaallll VVVVoooolllluuuummmmeeee AAAAttttttttrrrriiiibbbbuuuutttteeeessss Following the specification of a disk using the pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeee keyword, a block of attributes surrounded by {{{{ }}}} brackets may be specified. See _m_k_f_s(1M) for details. These attribute keywords are: - 17 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) nnnnsssseeeecccctttt ==== _n_u_m_b_e_r Specifies the number of sectors per track as _n_u_m_b_e_r. nnnnttttrrrraaaacccckkkk ==== _n_u_m_b_e_r Specifies the number of tracks per cylinder as _n_u_m_b_e_r. rrrrppppmmmm ==== _n_u_m_b_e_r Specifies the revolutions per minute of the disk as _n_u_m_b_e_r. (_n_u_m_b_e_r is converted to RPS before passing it to the nnnneeeewwwwffffssss command). iiiinnnntttteeeerrrrlllleeeeaaaavvvveeee____ffffaaaaccccttttoooorrrr ==== _n_u_m_b_e_r If _n_u_m_b_e_r is other than -1, then this specifies that the mmmmeeeeddddiiiiaaaaiiiinnnniiiitttt command should be run on the disk, and that the interleave factor of _n_u_m_b_e_r should be used. By default mmmmeeeeddddiiiiaaaaiiiinnnniiiitttt is not run on the disk. FFFFiiiilllleeee SSSSyyyysssstttteeeemmmm////SSSSwwwwaaaapppp AAAAttttttttrrrriiiibbbbuuuutttteeeessss The following attributes can be specified inside the blocks following the ffffssss____ppppaaaarrrrttttiiiittttiiiioooonnnn, sssswwwwaaaapppp____ppppaaaarrrrttttiiiittttiiiioooonnnn, and llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee keywords. uuuussssaaaaggggeeee ==== HHHHFFFFSSSS uuuussssaaaaggggeeee ==== VVVVxxxxFFFFSSSS uuuussssaaaaggggeeee ==== SSSSWWWWAAAAPPPP uuuussssaaaaggggeeee ==== SSSSWWWWAAAAPPPP____DDDDUUUUMMMMPPPP uuuussssaaaaggggeeee ==== DDDDUUUUMMMMPPPP uuuussssaaaaggggeeee ==== UUUUnnnnuuuusssseeeedddd Specifies that the volume should be used as one of: HHHHFFFFSSSS (hierarchical file system), VVVVxxxxFFFFSSSS (journaled file system), virtual memory SSSSWWWWAAAAPPPP, both virtual memory SSSSWWWWAAAAPPPP and DDDDUUUUMMMMPPPP (for system core dump storage), DDDDUUUUMMMMPPPP alone, or UUUUnnnnuuuusssseeeedddd. Note that the ////ssssttttaaaannnndddd file system must be HHHHFFFFSSSS. Also note that uuuussssaaaaggggeeee is restricted to the following values for each of these disk and file system configurations: ffffssss____ppppaaaarrrrttttiiiittttiiiioooonnnn can be either HHHHFFFFSSSS or VVVVxxxxFFFFSSSS; sssswwwwaaaapppp____ppppaaaarrrrttttiiiittttiiiioooonnnn must be SSSSWWWWAAAAPPPP; and llllooooggggiiiiccccaaaallll____vvvvoooolllluuuummmmeeee can be either HHHHFFFFSSSS, VVVVxxxxFFFFSSSS, SSSSWWWWAAAAPPPP, SSSSWWWWAAAAPPPP____DDDDUUUUMMMMPPPP, DDDDUUUUMMMMPPPP, or UUUUnnnnuuuusssseeeedddd. ssssiiiizzzzeeee ==== _n_u_m_b_e_r ssssiiiizzzzeeee ==== rrrreeeemmmmaaaaiiiinnnniiiinnnngggg ssssiiiizzzzeeee ==== rrrreeeemmmmaaaaiiiinnnniiiinnnngggg |||| _m_a_x_s_i_z_e ssssiiiizzzzeeee ==== _m_i_n_s_i_z_e |||| rrrreeeemmmmaaaaiiiinnnniiiinnnngggg ssssiiiizzzzeeee ==== _m_i_n_s_i_z_e |||| rrrreeeemmmmaaaaiiiinnnniiiinnnngggg |||| _m_a_x_s_i_z_e Specifies the size of the volume/file system to be _n_u_m_b_e_r. In the case that the size is set to rrrreeeemmmmaaaaiiiinnnniiiinnnngggg, then the volume will be assigned the disk space that is left after allocating all other volumes. If mmmmaaaaxxxxssssiiiizzzzeeee is specified in conjunction with rrrreeeemmmmaaaaiiiinnnniiiinnnngggg, then the remaining disk space, up to _m_a_x_s_i_z_e, is assigned to the volume. If _m_i_n_s_i_z_e is specified, then the size of the volume will be at least that that size if there is sufficient space, and will be larger (up to the _m_a_x_s_i_z_e value) if possible. _n_u_m_b_e_r, _m_i_n_s_i_z_e, and _m_a_x_s_i_z_e can be in units of bytes, or can be in MB or KB (for example: 100MB, 102400KB). Ignite-UX uses the disk space impact information supplied with the software selections in determining the final size requirements for volumes. Ignite-UX will not let a volume size - 18 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) be lower than the space required to load the selected software. If a volume size is specified smaller than what the software requires, the size will automatically be increased. Ignite-UX also tries to ensure that some amount of free space will be left on each volume after the install is complete. The algorithm used when calculating the software impact to volumes is as follows: o+ The minimum size that a volume is allowed to be is the software impact, plus 12% (or the file system minfree percentage if set). o+ In addition to this minimum size, an additional percentage is added to the volumes to ensure sufficient "breathing room" after the system is installed. This percentage is by default 10%, but can be controlled by the config file variable ____hhhhpppp____aaaaddddddddnnnnllll____ffffssss____ffffrrrreeeeeeee____ppppcccctttt. If the disk capacity is insufficient to accommodate this additional free space, this additional percentage value will be continually reduced by 1/2 until a value is found that allows all the volumes to fit. If the volumes will still not fit with 0% additional space, then the install will not be allowed to proceed. ssssiiiizzzzeeee ==== _p_e_r_c_e_n_t %%%%ffffrrrreeeeeeee ssssiiiizzzzeeee ==== _a_m_o_u_n_t ffffrrrreeeeeeee ssssiiiizzzzeeee ==== _m_i_n_s_i_z_e |||| rrrreeeemmmmaaaaiiiinnnniiiinnnngggg |||| _p_e_r_c_e_n_t %%%%ffffrrrreeeeeeee ssssiiiizzzzeeee ==== _m_i_n_s_i_z_e |||| rrrreeeemmmmaaaaiiiinnnniiiinnnngggg |||| _a_m_o_u_n_t ffffrrrreeeeeeee Specifies the size of the volume/file system to be relative to the expected amount of data that will be loaded into that file system. The size can be specified as a the desired percentage of free space, or the number of megabytes desired to be free after the installation. When the size is specified as a range, the size of the volume is allowed to be adjusted down to the _m_i_n_s_i_z_e value in order to fit any other volumes into the amount of disk space available. Examples: size = 100MB size = 150MB | remaining | 20% free size = 30MB free size = remaining mmmmoooouuuunnnntttt____ppppooooiiiinnnntttt ==== _c_p_l_x__s_t_r_i_n_g Specifies the directory that the file system will be mounted under as _c_p_l_x__s_t_r_i_n_g. Specifying a mmmmoooouuuunnnntttt____ppppooooiiiinnnntttt for a swap volume is not necessary, but can be done so that the swap volume can be uniquely identified if it is to be overridden later in the configuration file. - 19 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) mmmmiiiinnnnffffrrrreeeeeeee ==== _n_u_m_b_e_r Sets the percentage of the disk to reserve for root-only use to _n_u_m_b_e_r. ffffiiiilllleeee____lllleeeennnnggggtttthhhh ==== SSSSHHHHOOOORRRRTTTT ffffiiiilllleeee____lllleeeennnnggggtttthhhh ==== LLLLOOOONNNNGGGG Sets the file system filename length. Default is LLLLOOOONNNNGGGG. (This keyword applies to HHHHFFFFSSSS file systems only. VVVVxxxxFFFFSSSS file systems are always capable of long filenames.) bbbbllllkkkkssssiiiizzzzeeee ==== _n_u_m_b_e_r Sets the file system block size to _n_u_m_b_e_r. ffffrrrraaaaggggssssiiiizzzzeeee ==== _n_u_m_b_e_r Sets the file system fragment size to _n_u_m_b_e_r. nnnnccccppppgggg ==== _n_u_m_b_e_r Sets the number of cylinders per group to _n_u_m_b_e_r. nnnnbbbbppppiiii ==== _n_u_m_b_e_r Sets the number of bytes per inode (inode density) to _n_u_m_b_e_r. rrrroooottttaaaattttiiiioooonnnnaaaallll____ddddeeeellllaaaayyyy ==== _n_u_m_b_e_r Sets the rotational delay factor for the file system to _n_u_m_b_e_r. (See _t_u_n_e_f_s(1M)). The following attributes are recognized when the volume is an LVM volume: (See _l_v_c_r_e_a_t_e(1M)). bbbbaaaadddd____bbbblllloooocccckkkk____rrrreeeellllooooccccaaaatttteeee ==== _b_o_o_l_e_a_n |||| nnnnoooonnnneeee Sets the bad block relocation policy to 'y' if _b_o_o_l_e_a_n is ttttrrrruuuueeee or 'n' if _b_o_o_l_e_a_n is ffffaaaallllsssseeee. If nnnnoooonnnneeee is given (restricted to releases B.10.20 and later), sets the bad block relocation policy to 'N'. For correct operation on 10.20, you must install PHCO_10826 and PHKL_11085 or PHKL_11086, or their successors, on your target system. ccccoooonnnnttttiiiigggguuuuoooouuuussss____aaaallllllllooooccccaaaattttiiiioooonnnn ==== _b_o_o_l_e_a_n Sets the contiguous allocation policy to 'y' if _b_o_o_l_e_a_n is ttttrrrruuuueeee or 'n' if _b_o_o_l_e_a_n is ffffaaaallllsssseeee. ssssttttrrrriiiippppeeeessss ==== _n_u_m_b_e_r ssssttttrrrriiiippppeeeessss ==== **** Specifies that the data for this logical volume should be striped across multiple physical disks in the volume group. The number of disks used to stripe the data can be provided by _n_u_m_b_e_r, or if the data should be striped across all the disks in the group, then **** can be specified. Volumes that must be contiguous (////, ////ssssttttaaaannnndddd, and primary swap/dump) cannot be striped. There must be two or more disks configured in the volume group in order to specify a striped volume in that group. - 20 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ssssttttrrrriiiippppeeee____ssssiiiizzzzeeee ==== _n_u_m_b_e_r Specifies the data size of each stripe. This is only used when the logical volume is specified to be striped via the ssssttttrrrriiiippppeeeessss keyword. The default ssssttttrrrriiiipppp____ssssiiiizzzzeeee is equal to the file system block size (which is 8k by default). The allowed values for _n_u_m_b_e_r are 4444KKKKBBBB, 8888KKKKBBBB, 11116666KKKKBBBB, 33332222KKKKBBBB, and 66664444KKKKBBBB. llllaaaarrrrggggeeeeffffiiiilllleeeessss ==== _b_o_o_l_e_a_n Specifies that largefiles are to be enabled or disabled for this volume. It is supported for both HHHHFFFFSSSS and VVVVxxxxFFFFSSSS file systems. This feature is only supported for releases B.10.20 and later. ddddiiiisssskkkk[[[[_h_w-_p_a_t_h]]]] One or more references to a disk may be listed inside a logical volume definition. Doing so will force that volume to have data allocated only from the disk or disks listed. The disks listed inside the logical volume must have been listed as pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooolllluuuummmmeeeessss in the same volume group in which the logical volume exists. Unless the desired disks are listed within the logical volume definition, the logical volume could have data allocated from any of the disks in the volume group. mmmmiiiinnnnoooorrrr____nnnnuuuummmmbbbbeeeerrrr ==== _n_u_m_b_e_r Determines the logical volume number that will be assigned to the associated logical volume, which in turn determines the minor number value for the device file. _n_u_m_b_e_r may range from 0 to 255. If mmmmiiiinnnnoooorrrr____nnnnuuuummmmbbbbeeeerrrr is not specified and the logical volume name is specified and is the form: llllvvvvoooollll_X, then the value _X is used to determine the volume number. Otherwise, the value is assigned in the order the volumes are created. VVVVoooolllluuuummmmeeee GGGGrrrroooouuuupppp AAAAttttttttrrrriiiibbbbuuuutttteeeessss Within the vvvvoooolllluuuummmmeeee____ggggrrrroooouuuupppp block, the following LVM attributes can be set: (See _v_g_c_r_e_a_t_e(1M) for details on meanings and defaults.) mmmmaaaaxxxx____pppphhhhyyyyssssiiiiccccaaaallll____eeeexxxxtttteeeennnnttttssss ==== _n_u_m_b_e_r Sets the maximum number of physical extents that can be allocated from any of the physical volumes in the volume group. mmmmaaaaxxxx____llllooooggggiiiiccccaaaallll____vvvvoooollllssss ==== _n_u_m_b_e_r Sets the maximum number of logical volumes that the volume group is allowed to contain. mmmmaaaaxxxx____pppphhhhyyyyssssiiiiccccaaaallll____vvvvoooollllssss ==== _n_u_m_b_e_r Sets the maximum number of physical volumes that the volume group is allowed to contain. pppphhhhyyyyssssiiiiccccaaaallll____eeeexxxxtttteeeennnntttt____ssssiiiizzzzeeee ==== _n_u_m_b_e_r Sets the number of megabytes in each physical extent, where _n_u_m_b_e_r may range from 1 through 256. - 21 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) mmmmiiiinnnnoooorrrr____nnnnuuuummmmbbbbeeeerrrr ==== _n_u_m_b_e_r Sets the minor number of the volume group control file. Usage of this option is cautioned without fully understanding the consequences. The value of _n_u_m_b_e_r may range from 0 to 255, except when installing 10.* clients. The maximum value of _n_u_m_b_e_r will be lower on 10.* clients with less than 100MB of RAM. This is due to larger values causing the kernel to consume more memory than the system can spare. If this attribute is set, then that _n_u_m_b_e_r is used. Otherwise if the volume group name is of the form """"vvvvgggg_N_N"""" and _N_N is in range and not already declared by a mmmmiiiinnnnoooorrrr____nnnnuuuummmmbbbbeeeerrrr attribute, then the value of _N_N is used. Otherwise the first unused value in the acceptable range is used. SSSSyyyysssstttteeeemmmm IIIIddddeeeennnnttttiiiittttyyyy aaaannnndddd NNNNeeeettttwwwwoooorrrrkkkk CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn The configuration file may set attributes that control the default values for system identity and network configuration. Most of these keywords may have values that are used during the install, and may have ffffiiiinnnnaaaallll values that are applied to the system after the installation. This is to support situations where the system is not being installed on the network of its final destination. When keywords are not proceeded with the ffffiiiinnnnaaaallll keyword, then the information will be used during the installation, and may also be applied to the final system depending on the boolean value of the iiiissss____nnnneeeetttt____iiiinnnnffffoooo____tttteeeemmmmppppoooorrrraaaarrrryyyy keyword. If the ffffiiiinnnnaaaallll keyword is specified, then the information will be applied to the final system, and will override any non-final information that was used during the install. Note that iiiinnnnssssttttllll____aaaaddddmmmm can set some of these non-final values with command line options. The keywords recognized for this are: [ffffiiiinnnnaaaallll] ssssyyyysssstttteeeemmmm____nnnnaaaammmmeeee ==== _c_p_l_x__s_t_r_i_n_g Sets the system's hostname and uname value to _c_p_l_x__s_t_r_i_n_g. [ffffiiiinnnnaaaallll] iiiipppp____aaaaddddddddrrrr ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] iiiipppp____aaaaddddddddrrrr[_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Sets the system's default IP address to _c_p_l_x__s_t_r_i_n_g. If the IP address is to be used on a specific LAN device other than the default, then _l_a_n__d_e_v can be specified within square brackets. _l_a_n__d_e_v can be either a string representing the interface name, ("lan0" for example), or it can be the hardware path to the LAN device (2/0/2 for example). [ffffiiiinnnnaaaallll] nnnneeeettttmmmmaaaasssskkkk ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] nnnneeeettttmmmmaaaasssskkkk[_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Sets the system's default netmask (as used by _i_f_c_o_n_f_i_g(1M)), to _c_p_l_x__s_t_r_i_n_g. _l_a_n__d_e_v can be used to specify which LAN interface it applies to. [ffffiiiinnnnaaaallll] bbbbrrrrooooaaaaddddccccaaaasssstttt____aaaaddddddddrrrr ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] bbbbrrrrooooaaaaddddccccaaaasssstttt____aaaaddddddddrrrr [_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Sets the broadcast address for the specified lan device. - 22 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) [ffffiiiinnnnaaaallll] llllaaaannnnccccoooonnnnffffiiiigggg____aaaarrrrggggssss ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] llllaaaannnnccccoooonnnnffffiiiigggg____aaaarrrrggggssss [_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Specifies the encapsulation method to be passed to the llllaaaannnnccccoooonnnnffffiiiigggg command for the given interface. The default is "ether". ddddhhhhccccpppp____ccccllllaaaassssssss____iiiidddd ==== _c_p_l_x__s_t_r_i_n_g ddddhhhhccccpppp____ccccllllaaaassssssss____iiiidddd [_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Sets the class ID that is used when trying to obtain information for the specified lan interface from a DHCP server. Specifying a ddddhhhhccccpppp____ccccllllaaaassssssss____iiiidddd will limit the responses from DHCP servers to those that have information for the same class that is specified. This is used to isolate systems into different classes. Using the ddddhhhhccccpppp____ccccllllaaaassssssss____iiiidddd is especially useful when temporary IP addresses to be used for installs come from a different server than addresses used by other systems on the network. The ddddhhhhccccpppp____sssseeeerrrrvvvveeeerrrr keyword can also be used for this purpose. ddddhhhhccccpppp____sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g ddddhhhhccccpppp____sssseeeerrrrvvvveeeerrrr [_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Specifies which DHCP server the IP address lease should be obtained from. Specifying the server prevents the client from accepting offers from any other server on the network. Normally this is not set and the client is allowed to accept any offer. ddddhhhhccccpppp____mmmmiiiisssscccc____ooooppppttttssss ==== _c_p_l_x__s_t_r_i_n_g ddddhhhhccccpppp____mmmmiiiisssscccc____ooooppppttttssss [_l_a_n__d_e_v] ==== _c_p_l_x__s_t_r_i_n_g Can be used to specify miscellaneous options to the ddddhhhhccccppppcccclllliiiieeeennnntttt command when it is used to obtain the IP address lease. Common options specified with this keyword are ----GGGG and ----llll.... The ----GGGG option can be used in conjunction with the ddddhhhhccccpppp____ccccllllaaaassssssss____iiiidddd which causes the dhcpclient command to refuse any offers from servers that do not supply the matching class ID string in their reply offer. Normally servers that do not have the same class ID will not respond, however some vendor's implementations do respond and thus the ----GGGG option can be used to force filtering of these replies on the client side. The ----GGGG option only works with DHCP servers that supply the class ID in their response. Servers known to supply the class ID are HP-UX 10.30 and later bootpd (or 10.10/10.20 bootpd with the latest patch applied). The ----llll option can be used to specify debug output from the dhcpclient command. For example: ddddhhhhccccpppp____mmmmiiiisssscccc____ooooppppttttssss ==== """"----llll 7777"""" [ffffiiiinnnnaaaallll] rrrroooouuuutttteeee____ggggaaaatttteeeewwwwaaaayyyy [_i_n_d_e_x] ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] rrrroooouuuutttteeee____ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn [_i_n_d_e_x] ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] rrrroooouuuutttteeee____ccccoooouuuunnnntttt [_i_n_d_e_x] ==== _n_u_m_b_e_r These keywords are use to configure the system's network routing information. If no routing information is given, then the default is to set up a "default" route though the local host. If one or more static routes are to be configured, then the rrrroooouuuutttteeee____ggggaaaatttteeeewwwwaaaayyyy must be set. If rrrroooouuuutttteeee____ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn is not set, then it will default to the string "default". If rrrroooouuuutttteeee____ccccoooouuuunnnntttt is not - 23 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) set, then it will default to 1 if the rrrroooouuuutttteeee____ggggaaaatttteeeewwwwaaaayyyy is not the same as the system's IP address. It will default to 0 if it is the same as the system's IP address. _i_n_d_e_x number should be different for each set of route parameters to be configured (think of it as an array index). The first route specified should have an _i_n_d_e_x of 0. [ffffiiiinnnnaaaallll] ddddnnnnssss____ddddoooommmmaaaaiiiinnnn ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] ddddnnnnssss____nnnnaaaammmmeeeesssseeeerrrrvvvveeeerrrr [_i_n_d_e_x] ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] ddddnnnnssss____sssseeeeaaaarrrrcccchhhh [_i_n_d_e_x] ==== _c_p_l_x__s_t_r_i_n_g Sets the domain name services (DNS) domain, one or more name servers, and optionally, one or more search domains. The _i_n_d_e_x parameter to the ddddnnnnssss____nnnnaaaammmmeeeesssseeeerrrrvvvveeeerrrr and to the ddddnnnnssss____sssseeeeaaaarrrrcccchhhh keywords allows more than one name server and search domain to be configured. The first server and search domain should be assigned using an _i_n_d_e_x of 0, and the second 1, etc. See _r_e_s_o_l_v_e_r(4) for details. [ffffiiiinnnnaaaallll] nnnniiiissss____ddddoooommmmaaaaiiiinnnn ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] nnnniiiissss____sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g [ffffiiiinnnnaaaallll] wwwwaaaaiiiitttt____ffffoooorrrr____nnnniiiissss____sssseeeerrrrvvvveeeerrrr ==== _b_o_o_l_e_a_n Sets NIS domain and NIS server information. The nnnniiiissss____sssseeeerrrrvvvveeeerrrr keyword is optional when configuring NIS. The default for wwwwaaaaiiiitttt____ffffoooorrrr____nnnniiiissss____sssseeeerrrrvvvveeeerrrr is TRUE, meaning that the client will wait at boot time until the server can be contacted. [ffffiiiinnnnaaaallll] nnnnttttppppddddaaaatttteeee____sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g Sets the network time protocol server that the system will use to keep the clock synchronized. See _n_t_p_d_a_t_e(1M) for details. This is currently not used during the installation, only after the system is finished installing. iiiissss____nnnneeeetttt____iiiinnnnffffoooo____tttteeeemmmmppppoooorrrraaaarrrryyyy ==== _b_o_o_l_e_a_n If set to ttttrrrruuuueeee, then the network information supplied during the install will not be assumed to be correct for the system after it is installed. When set to ttttrrrruuuueeee and no ffffiiiinnnnaaaallll parameters have been set, then the sssseeeetttt____ppppaaaarrrrmmmmssss and aaaauuuuttttoooo____ppppaaaarrrrmmmmssss utilities will try to obtain the final information via the ddddhhhhccccppppcccclllliiiieeeennnntttt command using the dynamic host configuration protocol (DHCP), or from the user if DHCP is not available. In addition, if the information used during the installation was originally obtained from a DHCP server, then the IP address lease will be returned at the end of the installation. If set to ffffaaaallllsssseeee, (which is the default), the network information used during the install process will be assumed to be default for the system after the installation is complete. Which means that if the information was obtained via a DHCP server, then the lease information obtained will be kept and used when the system boots. If it was not obtained via DHCP, then the ENABLE_DHCP variable in - 24 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ////eeeettttcccc////rrrrcccc....ccccoooonnnnffffiiiigggg....dddd////nnnneeeettttccccoooonnnnffff will be set to '0' for the specific LAN interface. This will prevent aaaauuuuttttoooo____ppppaaaarrrrmmmmssss from overriding the supplied network information with any possible information from a DHCP server. rrrruuuunnnn____sssseeeettttppppaaaarrrrmmmmssss ==== _b_o_o_l_e_a_n If set to ttttrrrruuuueeee, then the hostname will be removed from the final /etc/rc.conf.d/netconf file which will cause the set_parms application to run upon first boot to query the user for networking information. sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g When the install source is the network, this is used to specify the default IP address of the install server. This is a system that has the Ignite-UX product installed. This system is also where the install process will read the configuration files from. ssssdddd____sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g Specifies the IP address of the system to use as the source for the Software Distributor (SD) sssswwwwiiiinnnnssssttttaaaallllllll utility (See _s_w_i_n_s_t_a_l_l(1M)). This information is only used if the sssswwww____ssssoooouuuurrrrcccceeee does not specify the ssssdddd____sssseeeerrrrvvvveeeerrrr information. ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr ==== _c_p_l_x__s_t_r_i_n_g Sets the default depot directory to be used by the sssswwwwiiiinnnnssssttttaaaallllllll utility. This depot directory is the location that the HP-UX software has been stored on the ssssdddd____sssseeeerrrrvvvveeeerrrr by the sssswwwwccccooooppppyyyy utility. This information is only used if the sssswwww____ssssoooouuuurrrrcccceeee does not specify the ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr information. rrrrooooooootttt____ppppaaaasssssssswwwwoooorrrrdddd ==== _c_p_l_x__s_t_r_i_n_g Specifies _c_p_l_x__s_t_r_i_n_g as being the encrypted password to be stored in the final ////eeeettttcccc////ppppaaaasssssssswwwwdddd file for the root user, or in the protected password file ////ttttccccbbbb////ffffiiiilllleeeessss////aaaauuuutttthhhh////rrrr////rrrrooooooootttt if an archive of a trusted system has been loaded. If a root password is to be applied, any UUUUIIIIDDDD or GGGGIIIIDDDD in the password file that is invalid according to _g_e_t_p_w_e_n_t(3C) will be modified as indicated. See the WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS section in _g_e_t_p_w_e_n_t(3C) for more information. ttttiiiimmmmeeeezzzzoooonnnneeee ==== _c_p_l_x__s_t_r_i_n_g Specifies _c_p_l_x__s_t_r_i_n_g as the timezone to be stored in the ////eeeettttcccc////TTTTIIIIMMMMEEEEZZZZOOOONNNNEEEE file on the final system. sssseeeerrrriiiiaaaallll____nnnnuuuummmmbbbbeeeerrrr ==== _c_p_l_x__s_t_r_i_n_g ccccuuuussssttttoooommmmeeeerrrr ==== _c_p_l_x__s_t_r_i_n_g oooorrrrddddeeeerrrr____nnnnuuuummmmbbbbeeeerrrr ==== _c_p_l_x__s_t_r_i_n_g These three keywords are used to supply information that is displayed on the manifest. They are informational only. CCCCoooonnnnttttrrrroooollll PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss The following parameters can be used to control the behavior of the - 25 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) installation process: rrrruuuunnnn____uuuuiiii ==== _b_o_o_l_e_a_n Specifies whether the installation process should be interactive or not. This may be set to ffffaaaallllsssseeee if you also set ccccoooonnnnttttrrrroooollll____ffffrrrroooommmm____sssseeeerrrrvvvveeeerrrr ==== ttttrrrruuuueeee, or if the configuration file specifies all the necessary information needed to perform the installation. If any information is missing or if any problems are found with the configuration, the installation will switch to interactive mode. In the case of a non-interactive installation, the user is given a default of 10 seconds to stop the process. See eeeennnnvvvv____vvvvaaaarrrrssss on how to adjust this timeout value and also how to specify whether warnings conditions are allowed during non-interactive install. Setting rrrruuuunnnn____uuuuiiii ==== ffffaaaallllsssseeee and not setting ccccoooonnnnttttrrrroooollll____ffffrrrroooommmm____sssseeeerrrrvvvveeeerrrr ==== ttttrrrruuuueeee should be done with extreme caution since the potential for accidental re-installation of system is possible. This would cause all data on one or more disks to be lost. Be aware that a network boot server that is not restricting access can be accidentally booted from. Therefore it is best to either restrict access to the boot server (see _i_n_s_t_l__b_o_o_t_d(1M)), or surround the rrrruuuunnnn____uuuuiiii ==== ffffaaaallllsssseeee statement with a condition that makes it specific to the client's LLLLLLLLAAAA[[[[]]]]. The client's LLA[] can be retrieved from the boot ROMs using the lan_addr command, or by using the llllaaaannnnssssccccaaaannnn HP-UX command. ccccoooonnnnttttrrrroooollll____ffffrrrroooommmm____sssseeeerrrrvvvveeeerrrr ==== _b_o_o_l_e_a_n Setting this value to ttttrrrruuuueeee will cause the client to enter a mode where it will wait for the install server to instruct it how to proceed with the installation (via the ////oooopppptttt////iiiiggggnnnniiiitttteeee////bbbbiiiinnnn////iiiiggggnnnniiiitttteeee application). The default is ffffaaaallllsssseeee, in which case the user interface will run on the client without interaction on the server. This keyword only sets the default, the user has the opportunity to use either mode during the install on the client. When used in combination with the rrrruuuunnnn____uuuuiiii====ffffaaaallllsssseeee keyword, the client can enter the mode where it waits for server instructions immediately after booting (assuming that it can obtain all necessary network information). hhhhaaaalllltttt____wwwwhhhheeeennnn____ddddoooonnnneeee ==== _b_o_o_l_e_a_n When this keyword is set to ttttrrrruuuueeee, then the system will halt when the installation is complete instead of rebooting from the disk that was just installed. The default is ffffaaaallllsssseeee. cccclllleeeeaaaannnn____aaaallllllll____ddddiiiisssskkkkssss ==== _b_o_o_l_e_a_n This keyword should almost always be left to default to ffffaaaallllsssseeee. Setting this to ttttrrrruuuueeee will cause the installation process to write over all disks, even those that are not configured for a file - 26 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) system. Its purpose is to remove prior file system information and make all the unused disks appear as "new". hhhhiiiiddddeeee____bbbbooooooootttt____ddddiiiisssskkkk ==== _b_o_o_l_e_a_n Setting this to ttttrrrruuuueeee prevents the installation process from allowing the boot disk to be configured and/or "cleaned". This is useful only when the Ignite-UX kernel is booted from a dedicated hard disk that you wish to protect from being modified. aaaalllllllloooowwww____ddddiiiisssskkkk____rrrreeeemmmmaaaapppp ==== _b_o_o_l_e_a_n Setting this to ttttrrrruuuueeee allows Ignite-UX to substitute a disk that was specified in the configuration files but that does not exist on the system with a disk that does exist and that was not specified to be used or hidden. This allows for a configuration file generated for one system to be more easily used for a different system that has disks at different hardware paths. This should be used with caution since the remapping algorithm may end up using disks you did not originally wish to use. The remapping algorithm attempts to find substitute disks with the same SCSI ID, and will give priority to finding a substitute for the root disk. If a substitute disk cannot be found, then the volume group will simply be created without that disk, or the file system will not be created. The default for this value is ffffaaaallllsssseeee in the case of a non- interactive install, and ttttrrrruuuueeee in the case of an interactive install. During an interactive install, you are shown which disks are being substituted and can make changes, or cancel the install. rrrreeeeccccoooovvvveeeerrrryyyy____mmmmooooddddeeee ==== _b_o_o_l_e_a_n This keyword defaults to ffffaaaallllsssseeee, and is set to ttttrrrruuuueeee in configuration files created by mmmmaaaakkkkeeee____rrrreeeeccccoooovvvveeeerrrryyyy or mmmmaaaakkkkeeee____nnnneeeetttt____rrrreeeeccccoooovvvveeeerrrryyyy. When set to ttttrrrruuuueeee, this indicates to Ignite-UX that the contents of the archive being used to install the system has files that are specific for the system being installed, and is not a generic archive to be used on any system. When ttttrrrruuuueeee, many files that are specific to a system are preserved as-is from the archive. When set to ffffaaaallllsssseeee, those same files would be copied from the /usr/newconfig directory and modified for the specific system being installed. In addition, when set to ttttrrrruuuueeee, the device files and kernel from the archive are preserved and not removed and recreated. Most of the effects of this keyword are visible and modifiable in the script: ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////ssssccccrrrriiiippppttttssss////oooossss____aaaarrrrcccchhhh____ppppoooosssstttt____llll (search for the iiiiffff statement regarding RECOVERY_MODE in this script). ddddiiiissssaaaabbbblllleeee____ddddhhhhccccpppp ==== _b_o_o_l_e_a_n Setting this to ttttrrrruuuueeee in the INSTALLFS file will prevent the process from attempting to contact a DHCP server for networking - 27 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) information. This may be useful if you do not use DHCP and do not like the delay that searching for a server causes. Setting this to ttttrrrruuuueeee in any config file other than INSTALLFS will allow the initial DHCP request to be done, but the resulting system will have DHCP disabled. This may be useful if you are using BOOTP to supply the IP address and hostname of the clients, but do not require ongoing maintenance of a lease. The BOOTP protocol is a subset of DHCP, and can be used to satisfy a DHCP query but does not require maintenance of a lease. uuuusssseeee____eeeexxxxppppeeeerrrrtttt____uuuuiiii ==== _b_o_o_l_e_a_n When set to ttttrrrruuuueeee, then the advanced user interface is the default rather than the task wizard interface. ssssdddd____ccccoooommmmmmmmaaaannnndddd____lllliiiinnnneeee ==== _c_p_l_x__s_t_r_i_n_g Allows setting of default additional command line options to be passed to the sssswwwwiiiinnnnssssttttaaaallllllll command. The options specified are added to the default options that are required to perform the software load. Any ssssdddd____ccccoooommmmmmmmaaaannnndddd____lllliiiinnnneeee keyword specified in a sssswwww____ssssoooouuuurrrrcccceeee definition appends to the default value. ssssdddd____sssseeeeccccrrrreeeettttssss ==== _c_p_l_x__s_t_r_i_n_g This should be specified only when the file ////vvvvaaaarrrr////aaaaddddmmmm////sssswwww////sssseeeeccccuuuurrrriiiittttyyyy////sssseeeeccccrrrreeeettttssss on the source depot server(s) have been modified to provide additional security. When this is done, all clients that access that server must have an identical sssseeeeccccrrrreeeettttssss file. The ssssdddd____sssseeeeccccrrrreeeettttssss keyword allows you to specify the contents of the sssseeeeccccrrrreeeettttssss file that will get used by the system doing the install. ssssyyyyssssaaaaddddmmmm____mmmmeeeessssssssaaaaggggeeee ==== _c_p_l_x__s_t_r_i_n_g Sets the message that is displayed to users when the system first boots the cold install process. This message is only recognized when stored in the configuration file that exists in the first 8k of the INSTALLFS file. iiiinnnnssssttttllll____aaaaddddmmmm has a special option to make this easy to change. eeeerrrrrrrroooorrrr ==== _c_p_l_x__s_t_r_i_n_g eeeerrrrrrrroooorrrr ++++==== _c_p_l_x__s_t_r_i_n_g Used to indicate an error condition such that the _c_p_l_x__s_t_r_i_n_g is displayed to the user and the installation process is not allowed to proceed. The use of the ++++==== operator adds a new message separate from any others. The ==== operator will clear out any other messages previously added such that _c_p_l_x__s_t_r_i_n_g will be the only message seen. If the ==== operator is used with an empty _c_p_l_x__s_t_r_i_n_g (""), then all error messages using this mechanism are cleared. wwwwaaaarrrrnnnniiiinnnngggg ==== _c_p_l_x__s_t_r_i_n_g wwwwaaaarrrrnnnniiiinnnngggg ++++==== _c_p_l_x__s_t_r_i_n_g Similar to the eeeerrrrrrrroooorrrr keyword described above, however ccccppppllllxxxx____ssssttttrrrriiiinnnngggg - 28 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) will be considered a warning message and will not prevent the installation from proceeding. nnnnooootttteeee ==== _c_p_l_x__s_t_r_i_n_g nnnnooootttteeee ++++==== _c_p_l_x__s_t_r_i_n_g Similar to the eeeerrrrrrrroooorrrr and wwwwaaaarrrrnnnniiiinnnngggg keywords described above, however ccccppppllllxxxx____ssssttttrrrriiiinnnngggg will be considered a notice message and will not prevent the installation from proceeding. mmmmoooodddd____kkkkeeeerrrrnnnneeeellll ==== _c_p_l_x-_s_t_r_i_n_g mmmmoooodddd____kkkkeeeerrrrnnnneeeellll ++++==== _c_p_l_x-_s_t_r_i_n_g This keyword can be used to add drivers or tunable parameters to the system's kernel that is built during the Ignite-UX process. The format of _c_p_l_x-_s_t_r_i_n_g may be either "driver" or "tunable value". The largest of any tunable parameter that exists in either the ////ssssttttaaaannnndddd////ssssyyyysssstttteeeemmmm file or that is specified will be used. Ignite-UX does not compare the values of formulas to discrete numerical values, or two formulas, or hexadecimal values, in order to determine which is larger. It will issue a warning message stating that it will assume the last mmmmoooodddd____kkkkeeeerrrrnnnneeeellll keyword parsed is larger (regardless of whether it is a formula or discrete numerical value) and will apply it. There is no bounds checking done on tunable parameters. Note that any allowable syntax supported by the ccccoooonnnnffffiiiigggg command can be used in mmmmoooodddd____kkkkeeeerrrrnnnneeeellll keywords. This includes formulas. For example, it is possible to use: mmmmoooodddd____kkkkeeeerrrrnnnneeeellll ++++==== """"nnnniiiinnnnooooddddeeee ((((22220000++++8888****MMMMAAAAXXXXUUUUSSSSEEEERRRRSSSS++++nnnnppppttttyyyy++++"""" ++++ $$$${{{{""""%%%%dddd"""" ____iiiinnnncccc}}}} ++++ """"))))"""" assuming ____iiiinnnncccc has been initialized to some value in the config file. The ==== operator will override any prior global mmmmoooodddd____kkkkeeeerrrrnnnneeeellll assignments. The ++++==== operator will add to any prior settings. Notice that mmmmoooodddd____kkkkeeeerrrrnnnneeeellll statements may also be associated with a sssswwww____sssseeeellll definition. The ==== operator does not have any effect on mmmmoooodddd____kkkkeeeerrrrnnnneeeellll assignments made in a sssswwww____sssseeeellll. hhhhwwww____iiiinnnnssssttttaaaannnncccceeee____nnnnuuuummmm ==== _h_w-_p_a_t_h _c_l_a_s_s-_s_t_r_i_n_g _i_n_s_t_a_n_c_e-_n_u_m hhhhwwww____iiiinnnnssssttttaaaannnncccceeee____nnnnuuuummmm ++++==== _h_w-_p_a_t_h _c_l_a_s_s-_s_t_r_i_n_g _i_n_s_t_a_n_c_e-_n_u_m This keyword can be used to force a specific instance number assignment for the specified hardware device. This keyword can be used when specific device file names are desired to produce a system consistent with others regardless of variations in hardware configurations. The examples below will assign the instance number 10 to the external bus (SCSI bus) 2/0/1, and instance number 1 to the LAN device 2/0/2. (Note that the disk device files contain the instance number of the parent "ext_bus" - 29 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) device). hw_instance_num = 2/0/1 "ext_bus" 10 hw_instance_num += 2/0/2 "lan" 1 It can be very confusing when a config file defines the instance number for a LAN device, and also specifies networking information by using the interface name which has the instance number in the string (e.g. ip_addr["lan0"]). In this case the original/default instance numbers are used because the instance number assignment you specify with hhhhwwww____iiiinnnnssssttttaaaannnncccceeee____nnnnuuuummmm does not take place until late in the install process. You can avoid confusion by using the device's hardware path instead of the interface name (e.g ip_addr[2/0/2]). eeeennnnvvvv____vvvvaaaarrrrssss ==== _c_p_l_x__s_t_r_i_n_g eeeennnnvvvv____vvvvaaaarrrrssss ++++==== _c_p_l_x__s_t_r_i_n_g Sets a string of variables of the form "variable=value" that will be sourced into the environment for the duration of the installation process. The format of _c_p_l_x__s_t_r_i_n_g should be one variable assignment per line. The value of the assignment does not need to be quoted (unless quotes need to be part of the value). These variable assignments will also be stored in the file /_t_m_p/_i_n_s_t_a_l_l._v_a_r_s that is left behind on the system after the installation. The use of the ++++==== operator is recommended to ensure that any prior settings are kept and not discarded as is the case when the ==== operator is used. Some special environment variables that can be set inside eeeennnnvvvv____vvvvaaaarrrrssss and are recognized by the cold install process are: IIIINNNNSSSSTTTT____NNNNEEEETTTT____RRRREEEESSSSPPPPOOOONNNNSSSSEEEE____TTTTIIIIMMMMEEEEOOOOUUUUTTTT====_s_e_c_o_n_d_s When booting an install client from the network, this sets the amount of time that the system will wait for a user response before it reboots in assumption that the system booted from the install server accidentally. Setting _s_e_c_o_n_d_s to 0 (zero) will disable the timeout and the system will not prompt for a response. IIIINNNNSSSSTTTT____AAAALLLLLLLLOOOOWWWW____WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS====_s_e_c_o_n_d_s Setting this environment variable is useful for non- interactive install sessions when warnings about disks containing data cause the installation to switch to interactive mode. Setting _s_e_c_o_n_d_s to 1111 will cause all warnings to be ignored and the installation will proceed. Setting _s_e_c_o_n_d_s to greater than 1111 will allow the user that many seconds to read the warning and stop the installation by pressing . - 30 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) IIIINNNNSSSSTTTT____BBBBAAAATTTTCCCCHHHH____MMMMOOOODDDDEEEE____TTTTIIIIMMMMEEEEOOOOUUUUTTTT====_s_e_c_o_n_d_s Sets the amount of time that the user has to interrupt a non-interactive installation. The default is 10 seconds. IIIINNNNSSSSTTTT____EEEENNNNAAAABBBBLLLLEEEE____NNNNEEEETTTTWWWWOOOORRRRKKKK====_1 This may be useful to set in the case where an automated install is to be done from physical media and the network interface needs to be enabled. If the hostname and IP address are not set, the install process will attempt to contact a DHCP/bootpd server to get that information. LLLLOOOOAAAADDDDFFFFIIIILLLLEEEE____RRRREEEETTTTRRRRYYYY____CCCCOOOOUUUUNNNNTTTT====_n_u_m_b_e_r This can be used change the default number of times that the internal loadfile command will retry a failed attempt to retrieve data from the server or media. Usually this retry mechanism is used to overcome tftp transfer problems. The default value is 5. SSSSooooffffttttwwwwaaaarrrreeee SSSSoooouuuurrrrcccceeee aaaannnndddd SSSSeeeelllleeeeccccttttiiiioooonnnnssss Ignite-UX supports a sophisticated mechanism for specifying the software that is available for loading during the installation. It supports loading from multiple sources of various types, primarily SD depots, and tar/cpio archives. The configuration files contain the mapping from what software selections the user sees to the source that contain them. This allows the user to operate on the full list of software selections without needing to know where the source for selections come from. The three constructs for handling software are: sssswwww____ssssoooouuuurrrrcccceeee, sssswwww____sssseeeellll, and sssswwww____ccccaaaatttteeeeggggoooorrrryyyy. A sssswwww____ssssoooouuuurrrrcccceeee specifies an SD depot, or an access method to a server containing archives. The sssswwww____sssseeeellll specifies the software contained in the SD depot, or specifies the path to an archive on the server or media. There are typically one sssswwww____sssseeeellll definition per software bundle, or per archive. The sssswwww____ccccaaaatttteeeeggggoooorrrryyyy is simply a mechanism for grouping the multitude of sssswwww____sssseeeelllls available. The user interface treats some categories special by putting them on the basic screen, or a under a special selector. When setting up an SD depot that uses software _b_u_n_d_l_e_s, (as all software shipped by HP should) you can simply run the mmmmaaaakkkkeeee____ccccoooonnnnffffiiiigggg command against that depot to generate the configuration file describing the software available in terms of these constructs. Setting up a configuration file that allows access to an archive requires manual editing, and the use of the aaaarrrrcccchhhhiiiivvvveeee____iiiimmmmppppaaaacccctttt command. The general structure for specifying software is as follows: sssswwww____ssssoooouuuurrrrcccceeee _s_r_c-_t_a_g-_s_t_r_i_n_g {{{{ _s_o_u_r_c_e-_a_t_t_r_i_b_u_t_e_s... }}}} - 31 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) sssswwww____ccccaaaatttteeeeggggoooorrrryyyy _c_a_t-_t_a_g-_s_t_r_i_n_g {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== _s_t_r_i_n_g }}}} sssswwww____sssseeeellll _s_e_l-_t_a_g-_s_t_r_i_n_g {{{{ sssswwww____ssssoooouuuurrrrcccceeee src-tag-string sssswwww____ccccaaaatttteeeeggggoooorrrryyyy cat-tag-string _s_e_l_e_c_t_i_o_n-_a_t_t_r_i_b_u_t_e_s... }}}} iiiinnnniiiitttt sssswwww____sssseeeellll _s_e_l-_t_a_g-_s_t_r_i_n_g====_b_o_o_l_e_a_n sssswwww____ssssoooouuuurrrrcccceeee _s_r_c-_t_a_g-_s_t_r_i_n_g {{{{ _s_o_u_r_c_e-_a_t_t_r_i_b_u_t_e_s }}}} The software source specifies an SD depot, or an access method to an archive. The _s_r_c-_t_a_g-_s_t_r_i_n_g is used by sssswwww____sssseeeellll to identify which sssswwww____ssssoooouuuurrrrcccceeee it belongs to. The attributes that can be within a sssswwww____ssssoooouuuurrrrcccceeee clause are: ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== _c_p_l_x__s_t_r_i_n_g Provides a description (typically one-line) of what the source represents. This is used when providing feedback to the user. ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee ==== """"NNNNEEEETTTT"""" |||| """"MMMMTTTT"""" |||| """"DDDDSSSSKKKK"""" This is used to override the default source type which corresponds to the type of media that the system was booted from. The source type strings are: network (""""NNNNEEEETTTT""""), magnetic-tape (""""MMMMTTTT""""), and CD-ROM (""""DDDDSSSSKKKK""""), Regardless of the boot sources, the default ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is """"NNNNEEEETTTT"""" when an Ignite-UX server is being used, which can be overridden by this keyword. ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt ==== SSSSDDDD | AAAARRRRCCCCHHHHIIIIVVVVEEEE | CCCCMMMMDDDD Specifies the general format of the source. This determines which information in the sssswwww____ssssoooouuuurrrrcccceeee clause should be used in accessing the source. The default is CCCCMMMMDDDD. When set to SSSSDDDD, and ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is NNNNEEEETTTT, the sssswwwwiiiinnnnssssttttaaaallllllll command is used to load from the specified ssssdddd____sssseeeerrrrvvvveeeerrrr and ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr. If ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is MMMMTTTT, then the sssswwwwiiiinnnnssssttttaaaallllllll command expects to find the depot as the third file on the tape. When set to AAAARRRRCCCCHHHHIIIIVVVVEEEE, and ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is NNNNEEEETTTT, then either the ffffttttpppp____ssssoooouuuurrrrcccceeee, rrrreeeemmmmsssshhhh____ssssoooouuuurrrrcccceeee, or nnnnffffssss____ssssoooouuuurrrrcccceeee keywords must be supplied and any sssswwww____sssseeeelllls that refer to this source will need to specify an aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh. When set to CCCCMMMMDDDD, then only the specified *____ccccmmmmdddd, *____ssssccccrrrriiiipppptttt, and mmmmoooodddd____kkkkeeeerrrrnnnneeeellll keywords are used, and executed at the appropriate time. This allows for a customized method of loading the represented software, or for setting kernel parameters. ssssoooouuuurrrrcccceeee____ppppaaaatttthhhh ==== _c_p_l_x__s_t_r_i_n_g For non-network sources, this keyword sets the default - 32 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) device file path to access the tape or CD-ROM. If not specified then it will default to the device that it booted from. cccchhhhaaaannnnggggeeee____mmmmeeeeddddiiiiaaaa ==== _b_o_o_l_e_a_n For non-network sources, this keyword indicates whether or not Ignite-UX should prompt the user to change media before loading from this source. The ddddeeeessssccccrrrriiiippppttttiiiioooonnnn information is used in the prompt so the user knows which media to insert. ssssdddd____sssseeeerrrrvvvveeeerrrr ==== _c_p_l_x__s_t_r_i_n_g Sets the IP address of the SD/swinstall server to use when ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt====SSSSDDDD. This value overrides the global ssssdddd____sssseeeerrrrvvvveeeerrrr keyword when loading from this source. ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr ==== _c_p_l_x__s_t_r_i_n_g When ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is """"NNNNEEEETTTT"""",,,, ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr sets the depot directory to be used in combination with the ssssdddd____sssseeeerrrrvvvveeeerrrr value when running sssswwwwiiiinnnnssssttttaaaallllllll to load the associated software. When ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee is """"DDDDSSSSKKKK"""",,,, ssssdddd____ddddeeeeppppooootttt____ddddiiiirrrr sets the depot directory to be used on the CD-ROM when running sssswwwwiiiinnnnssssttttaaaallllllll to load the associated software (if not specified, "/" is assumed). ssssdddd____uuuusssseeee____uuuuiiii ==== _b_o_o_l_e_a_n Indicates if the sssswwwwiiiinnnnssssttttaaaallllllll command should be run interactively (on the client console) when loading from this source. The default is false - meaning it will run non- interactively. ssssdddd____ccccoooommmmmmmmaaaannnndddd____lllliiiinnnneeee ==== _c_p_l_x__s_t_r_i_n_g Can be used to specify additional options to be passed to the sssswwwwiiiinnnnssssttttaaaallllllll command. This keyword does not normally need to be specified. ffffttttpppp____ssssoooouuuurrrrcccceeee ==== _c_p_l_x__s_t_r_i_n_g Used when ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt====AAAARRRRCCCCHHHHIIIIVVVVEEEE and the archive that is to be loaded can be obtained via the ffffttttpppp command. The format of _c_p_l_x__s_t_r_i_n_g is """"_u_s_e_r@@@@_s_y_s_t_e_m::::_p_a_s_s_w_d"""". For example: "anonymous@11.23.34.45:Ignite-UX". Use of an anonymous ftp login is recommended so that un-encrypted passwords are not made available in the configuration file. rrrreeeemmmmsssshhhh____ssssoooouuuurrrrcccceeee ==== _c_p_l_x__s_t_r_i_n_g Used when ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt====AAAARRRRCCCCHHHHIIIIVVVVEEEE and the archive that is to be loaded can be obtained via the rrrreeeemmmmsssshhhh command. The format of _c_p_l_x__s_t_r_i_n_g is """"_u_s_e_r@@@@_s_y_s_t_e_m"""". This requires that the server have .rhosts access enabled for the "root" user on all install clients for the _u_s_e_r account specified, or that the string "+ root" is placed in the _u_s_e_r account's .rhosts file. Because of the need to have open access to the - 33 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) server, this method only works in a very relaxed security environment and should be used with caution. nnnnffffssss____ssssoooouuuurrrrcccceeee ==== _c_p_l_x__s_t_r_i_n_g Used when ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt====AAAARRRRCCCCHHHHIIIIVVVVEEEE and the archive that is to be loaded can be obtained by NFS mounting the specified directory. The format of _c_p_l_x__s_t_r_i_n_g is """"_s_y_s_t_e_m::::////_m_o_u_n_t- _p_o_i_n_t"""". The _s_y_s_t_e_m must export the specified _m_o_u_n_t-_p_o_i_n_t to all install clients. The ////eeeettttcccc////eeeexxxxppppoooorrrrttttssss file may specify read-only permissions to aid in security. The path to the archive relative to _m_o_u_n_t-_p_o_i_n_t is provided in the associated sssswwww____sssseeeellll's aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh. llllooooaaaadddd____oooorrrrddddeeeerrrr ==== _n_u_m_b_e_r This can be used to specify the order in which this sssswwww____ssssoooouuuurrrrcccceeee should be accessed relative to any other sources. The default load order is 5. For sources that provide the core HP-UX operating system (regardless of whether it is an SD or ARCHIVE source), the llllooooaaaadddd____oooorrrrddddeeeerrrr must be set to 0 (zero) to ensure it is loaded first, and to trigger some special handling within Ignite-UX. pppprrrreeee____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ffffiiiinnnnaaaallll____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g These keywords specify a shell command string that should be executed at the prescribed points during the installation. See the section CCCCoooommmmmmmmaaaannnndddd aaaannnndddd SSSSccccrrrriiiipppptttt EEEExxxxeeeeccccuuuuttttiiiioooonnnn HHHHooooooookkkkssss for details. pppprrrreeee____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ffffiiiinnnnaaaallll____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g These keywords specify a shell script that should be loaded from the Ignite-UX server via ttttffffttttpppp and executed at at the prescribed points during the installation. See the section CCCCoooommmmmmmmaaaannnndddd aaaannnndddd SSSSccccrrrriiiipppptttt EEEExxxxeeeeccccuuuuttttiiiioooonnnn HHHHooooooookkkkssss for details. sssswwww____ccccaaaatttteeeeggggoooorrrryyyy _c_a_t-_t_a_g-_s_t_r_i_n_g {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== _s_t_r_i_n_g }}}} The sssswwww____ccccaaaatttteeeeggggoooorrrryyyy definition provides a grouping mechanism for sssswwww____sssseeeellll's to reference. The user interface uses the sssswwww____ccccaaaatttteeeeggggoooorrrryyyy to help the user browse the software more easily. There are three values of _c_a_t-_t_a_g-_s_t_r_i_n_g that the user interface treats special. Software that are in these groups are represented in special locations in the user interface. These values are: """"HHHHPPPPUUUUXXXXEEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnnttttssss"""", """"LLLLaaaannnngggguuuuaaaaggggeeeessss"""", and """"UUUUsssseeeerrrrLLLLiiiicccceeeennnnsssseeeessss"""" .The only attribute associated with a sssswwww____ccccaaaatttteeeeggggoooorrrryyyy is a ddddeeeessssccccrrrriiiippppttttiiiioooonnnn. - 34 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) sssswwww____sssseeeellll _s_e_l-_t_a_g-_s_t_r_i_n_g {{{{ _s_e_l_e_c_t_i_o_n-_a_t_t_r_i_b_u_t_e_s }}}} iiiinnnniiiitttt sssswwww____sssseeeellll _s_e_l-_t_a_g-_s_t_r_i_n_g ==== _b_o_o_l_e_a_n The sssswwww____sssseeeellll keyword defines a software selection that the user is allowed to select for loading. A software selection typically refers to an SD bundle, or a single tar/cpio archive. Each sssswwww____sssseeeellll must reference a sssswwww____ssssoooouuuurrrrcccceeee which provides the information needed to access the actual software. A sssswwww____sssseeeellll can be selected/unselected in the configuration file by using the iiiinnnniiiitttt keyword and setting it to a boolean value as shown in the syntax above. If the iiiinnnniiiitttt keyword is not used when doing an assignment, then the UI will not be able to change the value (although it will appear as though it can). The _s_e_l-_t_a_g-_s_t_r_i_n_g is used to reference the sssswwww____sssseeeellll in subsequent assignments. It is possible to assign multiple tag strings to a single sssswwww____sssseeeellll in order to provide aliases for a single selection. In this case, any tag can be used when referencing it within a configuration file. The syntax for specifying multiple tags is: sssswwww____sssseeeellll _t_a_g_1 |||| _t_a_g_2 |||| ...{{{{_s_e_l_e_c_t_i_o_n-_a_t_t_r_i_b_u_t_e_s}}}} The _s_e_l_e_c_t_i_o_n-_a_t_t_r_i_b_u_t_e_s that can be specified for a sssswwww____sssseeeellll are described below. ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== _c_p_l_x-_s_t_r_i_n_g Provides a one-line description of the software to be displayed along with the tag string or the ddddiiiissssppppllllaaaayyyy____nnnnaaaammmmeeee. ddddiiiissssppppllllaaaayyyy____nnnnaaaammmmeeee ==== _c_p_l_x-_s_t_r_i_n_g Specifies a more descriptive name than the tag name for the user interface to display as the product name. sssswwww____ssssoooouuuurrrrcccceeee ==== _s_r_c-_t_a_g-_s_t_r_i_n_g Specifies the sssswwww____ssssoooouuuurrrrcccceeee that this software selection is to be loaded from. The _s_r_c-_t_a_g-_s_t_r_i_n_g must match the tag string used when defining the source. This is a required attribute of a sssswwww____sssseeeellll. sssswwww____ccccaaaatttteeeeggggoooorrrryyyy ==== _c_a_t-_t_a_g-_s_t_r_i_n_g Specifies the software category that this selection is to be grouped with. aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh ==== _c_p_l_x-_s_t_i_n_g Specifies the file path to the associated tar/cpio archive. This is only used when the associated sssswwww____ssssoooouuuurrrrcccceeee sets ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt====AAAARRRRCCCCHHHHIIIIVVVVEEEE. If the sssswwww____ssssoooouuuurrrrcccceeee uses the nnnnffffssss____sssseeeerrrrvvvveeeerrrr access method, then this path must be relative to the NFS mount point. For ffffttttpppp____ssssoooouuuurrrrcccceeee or rrrreeeemmmmsssshhhh____ssssoooouuuurrrrcccceeee access methods, the path may be relative to the given account's home directory, or an absolute path if desired. - 35 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) If ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee====""""MMMMTTTT"""" then the aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh can be a quoted number string which will be used to position the tape device prior to extracting the data. This would provide the _n_u_m_b_e_r argument to the command: mmmmtttt ffffssssffff _n_u_m_b_e_r. If ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee====""""DDDDSSSSKKKK"""" then aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh will be used to access an archive on the CD-ROM when mounted as a file system. In which case, aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh must be a path relative to the top directory of the CD-ROM. When using an archive to contain the core HP-UX operating system (a full system archive), then the archive must be packaged using relative path names. This allows Ignite-UX to extract it to the mounted disk. In addition, the load_order of the sssswwww____ssssoooouuuurrrrcccceeee must be set to 0 (zero). Non- core OS archives may be packaged using either relative or absolute path names. aaaarrrrcccchhhhiiiivvvveeee____ttttyyyyppppeeee ==== [{ccccoooommmmpppprrrreeeesssssssseeeedddd||||ggggzzzziiiipppp}] {ttttaaaarrrr||||ccccppppiiiioooo} Specifies the type of archive that aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh references. The archive may be an uncompressed ttttaaaarrrr or ccccppppiiiioooo archive, or may be compressed using either ccccoooommmmpppprrrreeeessssssss or ggggzzzziiiipppp. The compression type, if specified, may be either of the keywords ccccoooommmmpppprrrreeeesssssssseeeedddd or ggggzzzziiiipppp. The second keyword must be either ttttaaaarrrr or ccccppppiiiioooo. For example: aaaarrrrcccchhhhiiiivvvveeee____ttttyyyyppppeeee ==== ggggzzzziiiipppp ttttaaaarrrr. If ssssoooouuuurrrrcccceeee____ttttyyyyppppeeee====""""MMMMTTTT"""" then the archive will be extracted with a block size dependent on the archive type. If the aaaarrrrcccchhhhiiiivvvveeee____ttttyyyyppppeeee is ttttaaaarrrr then the block size will be 10240 bytes. If the aaaarrrrcccchhhhiiiivvvveeee____ttttyyyyppppeeee is ccccppppiiiioooo then the block size will be 5120 bytes. ssssdddd____ssssooooffffttttwwwwaaaarrrreeee____lllliiiisssstttt ==== _c_p_l_x-_s_t_r_i_n_g Specifies a list of SD software objects (bundles, products, filesets, etc), that are to be loaded via the sssswwwwiiiinnnnssssttttaaaallllllll command. One or more software objects may be specified. iiiimmmmppppaaaaccccttttssss ==== _d_i_r_e_c_t_o_r_y _n_u_m_b_e_r This attribute should be used to specify the amount of disk space impact the associated software will have on the given directory. Multiple iiiimmmmppppaaaaccccttttssss statements may be specified, normally one statement for each top-level directory that the software loads into. However the directory level may be more specific if desired. This information is critical to the way that Ignite-UX does volume size calculations that are based relative on the amount of disk space used by each software selection. The mmmmaaaakkkkeeee____ccccoooonnnnffffiiiigggg command will automatically generate sssswwww____sssseeeellll statements with this information. The aaaarrrrcccchhhhiiiivvvveeee____iiiimmmmppppaaaacccctttt - 36 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) command can be used to generate the iiiimmmmppppaaaaccccttttssss attributes when manually creating sssswwww____sssseeeellll statements that represent a tar/cpio archive. mmmmoooodddd____kkkkeeeerrrrnnnneeeellll [[[[++++]]]]==== _c_p_l_x-_s_t_r_i_n_g Similar to the global mmmmoooodddd____kkkkeeeerrrrnnnneeeellll keyword. This keyword allows addition of kernel drivers or tunable parameters in the case that this sssswwww____sssseeeellll has been selected for loading. llllooooccccaaaalllleeee ==== {{{{_s_t_r_i_n_g_1,,,, _s_t_r_i_n_g_2,,,, ............ }}}} Sets a list of language locales that are supplied to the system when this sssswwww____sssseeeellll is loaded. The list is used by the user interface to give the user a selection of languages to pick from based on what software has been selected. The format of the strings listed is: ````````_l_o_c_a_l_e::::_d_e_s_c_r_i_p_t_i_o_n''''''''.... Where _l_o_c_a_l_e would be something that the LANG environment variable could be set to, and _d_e_s_c_r_i_p_t_i_o_n is a string that briefly describes what the locale is. vvvviiiissssiiiibbbblllleeee____iiiiffff ==== _b_o_o_l_e_a_n Allows the sssswwww____sssseeeellll to be hidden from the user interface when set to false. The default is true. mmmmaaaannnniiiiffffeeeesssstttt____iiiinnnnffffoooo ==== _c_p_l_x-_s_t_r_i_n_g Specifies that the text in the manifest template tagged with the given string should be printed as part of the manifest. See _p_r_i_n_t__m_a_n_i_f_e_s_t(1M) for details. ccccoooorrrreeeeqqqquuuuiiiissssiiiitttteeee [++++]==== _t_a_g-_s_t_r_i_n_g Indicates that the sssswwww____sssseeeellll referred to by _t_a_g-_s_t_r_i_n_g should be loaded along with this sssswwww____sssseeeellll. Multiple corequisites may be listed using one ccccoooorrrreeeeqqqquuuuiiiissssiiiitttteeee statement per, and by using the ++++==== operator. eeeexxxxrrrreeeeqqqquuuuiiiissssiiiitttteeee [++++]==== _t_a_g-_s_t_r_i_n_g Defines an exclusive relationship between the current sssswwww____sssseeeellll and the one referenced by _t_a_g-_s_t_r_i_n_g. This will prevent the referenced sssswwww____sssseeeellll from being selected any time that this sssswwww____sssseeeellll is selected (and vice-versa). The ++++==== operator may be used to define multiple exrequisites. eeeexxxxrrrreeeeqqqquuuuiiiissssiiiitttteeee ==== sssswwww____ccccaaaatttteeeeggggoooorrrryyyy Specifies that this sssswwww____sssseeeellll is to be exclusive with all other software in the same category. This attribute can be used in addition to other exrequisites and does not override them even though the ++++==== operator is not used in this case. llllooooaaaadddd____wwwwiiiitttthhhh____aaaannnnyyyy ==== _t_a_g-_s_t_r_i_n_g [[ |||| _t_a_g-_s_t_r_i_n_g]...] Specifies that when any of the one or more sssswwww____sssseeeelllls listed are selected, that this sssswwww____sssseeeellll should be selected for loading as well. Multiple tags may be listed separated by - 37 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) the |||| character. llllooooaaaadddd____wwwwiiiitttthhhh____aaaannnnyyyy ~~~~ _t_a_g-_r_e_g_e_x_p [[ |||| _t_a_g-_r_e_g_e_x_p ]...] llllooooaaaadddd____wwwwiiiitttthhhh____aaaannnnyyyy ~~~~ _c_a_t_e_g_o_r_y...._t_a_g-_r_e_g_e_x_p ... Similar to above, except that when the ~~~~ operator is used instead of ====, then the sssswwww____sssseeeellll tags listed are treated as _f_n_m_a_t_c_h(3C) regular expressions that can be used to match any selection fitting the given pattern. (Note that this operator uses _f_n_m_a_t_c_h(3C) pattern matching expressions. Other uses of the ~~~~ operator in the configuration file, uses extended regular expressions. This difference is for compatibility with some existing data.) The _c_a_t_e_g_o_r_y string can be specified (with a "." separator) in order to limit the matches to those selections in the specified software category. llllooooaaaadddd____wwwwiiiitttthhhh____aaaallllllll ==== _t_a_g-_s_t_r_i_n_g [[ &&&& _t_a_g-_s_t_r_i_n_g ]...] Specifies that when all the sssswwww____sssseeeelllls listed are selected, then this sssswwww____sssseeeellll should be selected as well. Multiple tags may be listed separated by the &&&& character. If multiple llllooooaaaadddd____wwwwiiiitttthhhh____**** keywords are specified, the list of tag-strings will be added to any already listed for the respective keyword. pppprrrreeee____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ffffiiiinnnnaaaallll____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g These keywords specify a shell command string that should be executed at the prescribed points during the installation if this sssswwww____sssseeeellll has been selected. See the section CCCCoooommmmmmmmaaaannnndddd aaaannnndddd SSSSccccrrrriiiipppptttt EEEExxxxeeeeccccuuuuttttiiiioooonnnn HHHHooooooookkkkssss for details. pppprrrreeee____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g ffffiiiinnnnaaaallll____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g These keywords specify a shell script that should be loaded from the Ignite-UX server via tftp and executed at at the prescribed points during the installation if this sssswwww____sssseeeellll has been selected. See the section CCCCoooommmmmmmmaaaannnndddd aaaannnndddd SSSSccccrrrriiiipppptttt EEEExxxxeeeeccccuuuuttttiiiioooonnnn HHHHooooooookkkkssss for details. CCCCoooommmmmmmmaaaannnndddd aaaannnndddd SSSSccccrrrriiiipppptttt EEEExxxxeeeeccccuuuuttttiiiioooonnnn HHHHooooooookkkkssss Ignite-UX supports mechanisms for user supplied commands and scripts to be inserted into various stages in the installation process. There are two types of keywords that the configuration file supports. The keywords that end in ____ccccmmmmdddd can be used to embed scripts directly in the configuration file. This is useful when the command desired to be executed is short and can be inserted directly into the configuration - 38 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) file without compromising the maintainability of the configuration file. The keywords that end in ____ssssccccrrrriiiipppptttt are used to reference a file that is to be loaded from the Ignite-UX server using the _t_f_t_p(1) service and executed as a stand-alone command. With the exception of the pppprrrreeee____ccccoooonnnnffffiiiigggg____ccccmmmmdddd keyword, the execution hooks can be specified in three different areas of the configuration file. These areas are: o+ Within a sw_source definition. o+ Within a sw_sel definition. o+ At the global level. Although only the ==== assignment operator is shown with these keywords, the ++++==== operator may also be used to add a script or command fragment to any existing assignments made the same keyword in the same context. The ==== operator will overwrite any prior assignments made for that keyword in the same context as where it is used. A separate context for each keyword is kept for the global level, each unique sssswwww____ssssoooouuuurrrrcccceeee and each unique sssswwww____sssseeeellll. The exit code returned by a script will result in different handling by the Ignite-UX process. If the exit code is 0, Ignite-UX will not display any additional messages and will proceed. If the exit code is 1, Ignite-UX will display an additional ERROR message and will proceed. If the exit code is 2, Ignite-UX will display an additional WARNING message and will proceed. If the exit code is 4, Ignite-UX will display an additional ERROR message and will terminate. If the exit code is anything else, the results are undefined. The point in time that the associated commands or scripts are executed are described below. pppprrrreeee____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g pppprrrreeee____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g The global pppprrrreeee____llllooooaaaadddd commands and scripts are executed prior to any software loading, but after the file systems have been created. Those within a sssswwww____ssssoooouuuurrrrcccceeee or a sssswwww____sssseeeellll definition are executed prior to loading any software from the respective source. Those associated with a sssswwww____ssssoooouuuurrrrcccceeee are executed ahead of any associated with a sssswwww____sssseeeellll. ppppoooosssstttt____llllooooaaaadddd____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____llllooooaaaadddd____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g The global ppppoooosssstttt____llllooooaaaadddd commands and scripts are executed after all software has been loaded, but prior to the final system reboot, and software configuration step. Those within a sssswwww____ssssoooouuuurrrrcccceeee or sssswwww____sssseeeellll definition will be executed after all software from the associated source has been loaded, and prior to the global - 39 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ppppoooosssstttt____llllooooaaaadddd commands and scripts. Those associated with a sssswwww____sssseeeellll are executed ahead of any associated with a sssswwww____ssssoooouuuurrrrcccceeee (opposite order of pppprrrreeee____llllooooaaaadddd). This is the correct hook to use if customizations to the kernel via the /stand/system file are to be made beyond what is capable though the mmmmoooodddd____kkkkeeeerrrrnnnneeeellll keyword. ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g The ppppoooosssstttt____ccccoooonnnnffffiiiigggg commands and scripts are executed after all software has been configured and the final system kernel has been built and booted under. It is safe to execute commands in this environment that may have dependencies on the version or modifications of the kernel that was put into place prior to rebooting. The ppppoooosssstttt____ccccoooonnnnffffiiiigggg commands and scripts associated with a sw_source or sw_sel are executed first, and then the global versions last. ffffiiiinnnnaaaallll____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g ffffiiiinnnnaaaallll____ssssccccrrrriiiipppptttt ==== _c_p_l_x__s_t_r_i_n_g The ffffiiiinnnnaaaallll commands and scripts are executed as the very last step before the final system reboot or halt. In fact, these scripts and commands are executed after the log file has been closed and the installation's overall status has been determined. Thus, the exit code from a ffffiiiinnnnaaaallll____ssssccccrrrriiiipppptttt does not influence the outcome of the installation. Also, any information logged from these commands and scripts does not make it into the log file, but is written to the target console. It is safe to execute commands in this environment that may have dependencies on the version or modifications of the kernel that was put into place prior to rebooting. The ffffiiiinnnnaaaallll commands and scripts associated with a sw_source or sw_sel are executed first, and then the global versions last. Note that if a temporary hostname/IP-address is used during the install then all the commands and scripts, (even the final_cmd/script), are executed while that temporary information is in effect. If you require the final networking information to be in effect, then you may need to have it run at the first system boot by loading the script under the /sbin/rc*.d directory and having it remove itself when done. pppprrrreeee____ccccoooonnnnffffiiiigggg____ccccmmmmdddd ==== _c_p_l_x__s_t_r_i_n_g Allows a list of semicolon separated commands to be executed prior to the creation and mounting of file systems. It also runs prior to the Ignite-UX user interface. There are almost no commands available at this stage (not even a shell). Any commands needed have to be loaded in using the llllooooaaaaddddffffiiiilllleeee command that exists in this environment (for command usage, type "loadfile -?" from a recovery shell that can be run instead of installing HP-UX). - 40 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) In addition to the hooks above that can be specified in an Ignite-UX config file, Ignite-UX provides a way for applications that are loaded using an archive to supply scripts to be run. After loading any software from an archive, Ignite-UX recursively searches the ////vvvvaaaarrrr////aaaaddddmmmm////sssswwww////pppprrrroooodddduuuuccccttttssss directory for any scripts called iiiiuuuuxxxx____ppppoooossssttttllllooooaaaadddd and iiiiuuuuxxxx____ppppoooossssttttccccoooonnnnffffiiiigggg.... Any iiiiuuuuxxxx____ppppoooossssttttllllooooaaaadddd scripts provided by the archive will be run immediately after the archive is loaded. Any iiiiuuuuxxxx____ppppoooossssttttccccoooonnnnffffiiiigggg scripts found will be remembered and run after all software is loaded and the system reboots from the final kernel. The order is similar to the ppppoooosssstttt____llllooooaaaadddd____ccccmmmmdddd and ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ccccmmmmdddd keywords described above. These scripts are not executed if they were loaded from an SD depot. The regular SD control scripts are run in this case. When a tar/cpio archive is used to supply the core HP-UX operating system (a full system archive), you will want to use a couple scripts supplied with Ignite-UX. These scripts should be associated with the sssswwww____sssseeeellll that references the system archive. See the example file ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////eeeexxxxaaaammmmpppplllleeeessss////ccccoooorrrreeee....ccccffffgggg. There is one ppppoooosssstttt____llllooooaaaadddd____ssssccccrrrriiiipppptttt (////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////ssssccccrrrriiiippppttttssss////oooossss____aaaarrrrcccchhhh____ppppoooosssstttt____llll) and one ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt (////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////ssssccccrrrriiiippppttttssss////oooossss____aaaarrrrcccchhhh____ppppoooosssstttt____cccc). These shell scripts may require customizations to meet your needs. See the comments in the files for details. CCCCoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn FFFFiiiilllleeee PPPPaaaarrrrssssiiiinnnngggg OOOOrrrrddddeeeerrrr aaaannnndddd PPPPrrrreeeecccceeeeddddeeeennnncccceeee In general, the configuration files are parsed in the order that they are listed inside the INDEX file ccccffffgggg statement that is selected. In addition, the information stored inside the first 8K of the INSTALLFS file and the file named ccccoooonnnnffffiiiigggg in the client-specific directory are parsed after those listed in the INDEX file. Configuration files that are parsed later have precedence over any earlier files and may override values set in earlier files. Thus the client-specific configuration file has highest precedence. One additional source of a configuration file is in the boot LIF area of each disk on the system being installed. If there exists a LIF file named CUSTOM, then that file will be read as a configuration file and parsed after the INSTALLFS contents. This CUSTOM file is normally created as a result of running the llllvvvvmmmmmmmmiiiiggggrrrraaaatttteeee command. Tape and CD-ROM media are in _l_i_f(4) format, and contain an INDEX file, and typically the only file referenced by the INDEX file is called CONFIG. It is this CONFIG file, in addition to the the first 8K of the INSTALLFS file that make up the configuration information for these media types. EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS SSSSeeeettttttttiiiinnnngggg tttthhhheeee ddddeeeeffffaaaauuuulllltttt ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn uuuussssiiiinnnngggg llllooooggggiiiicccc eeeexxxxpppprrrreeeessssssssiiiioooonnnnssss:::: When configurations are saved as a named configuration, the user interface will crate a new INDEX file ccccffffgggg clause for that saved configuration. It may be desirable to create a logic expression to determine which saved configuration is to be applied to a new system. - 41 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) This can be done by setting the ccccffffgggg clause to true/false inside the INSTALLFS file using the ----ffff option to the iiiinnnnssssttttllll____aaaaddddmmmm command. The INSTALLFS file is the best place to do this. The user interface will not preserve this type of information if put in an INDEX file the next time a save operation is done. #### SSSSeeeelllleeeecccctttt tttthhhheeee """"TTTTwwwwoooo ddddiiiisssskkkk ccccffffgggg"""" iiiiffff tttthhhheeee ssssyyyysssstttteeeemmmm hhhhaaaassss 2222 oooorrrr mmmmoooorrrreeee ddddiiiisssskkkkssss ccccffffgggg """"TTTTwwwwoooo ddddiiiisssskkkk ccccffffgggg"""" ==== ((((nnnnuuuummmm____ddddiiiisssskkkkssss >>>>==== 2222)))) #### FFFFoooorrrr aaaa ssssyyyysssstttteeeemmmm wwwwiiiitttthhhh oooonnnnllllyyyy oooonnnneeee ddddiiiisssskkkk,,,, aaaannnndddd ssssmmmmaaaallllllll mmmmeeeemmmmoooorrrryyyy,,,, sssseeeelllleeeecccctttt #### tttthhhheeee """"ssssmmmmaaaallllllll ssssyyyysssstttteeeemmmm ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn"""" nnnnuuuummmm____ddddiiiisssskkkkssss ======== 1111 &&&& mmmmeeeemmmmoooorrrryyyy <<<< 66664444MMMMBBBB {{{{ ccccffffgggg """"ssssmmmmaaaallllllll ssssyyyysssstttteeeemmmm ccccoooonnnnffffiiiigggguuuurrrraaaattttiiiioooonnnn"""" ==== ttttrrrruuuueeee }}}} UUUUssssiiiinnnngggg aaaa ssssooooffffttttwwwwaaaarrrreeee aaaarrrrcccchhhhiiiivvvveeee If you have a set of files packaged in a tar/cpio archive that you would like to have loaded during the installation process you can create a new configuration file such as the one below. This will create a new software selection representing this source. It also conditionally selects this software for loading if the root disk size is more than 1800Mb. sssswwww____ssssoooouuuurrrrcccceeee """"PPPPeeeerrrr----DDDDiiiisssscccciiiipppplllliiiinnnneeee PPPPaaaacccckkkkssss"""" {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== """"SSSSooooffffttttwwwwaaaarrrreeee AAAAppppppppssss ffffoooorrrr IIIInnnnddddiiiivvvviiiidddduuuuaaaallll DDDDiiiisssscccciiiipppplllliiiinnnneeeessss"""" ssssoooouuuurrrrcccceeee____ffffoooorrrrmmmmaaaatttt ==== aaaarrrrcccchhhhiiiivvvveeee nnnnffffssss____ssssoooouuuurrrrcccceeee ==== """"11114444....11112222....99999999....111111113333::::////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////aaaarrrrcccchhhhiiiivvvveeeessss"""" }}}} sssswwww____ccccaaaatttteeeeggggoooorrrryyyy """"DDDDiiiisssscccciiiipppplllliiiinnnneeeessss"""" {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== """"SSSSooooffffttttwwwwaaaarrrreeee ffffoooorrrr IIIInnnnddddiiiivvvviiiidddduuuuaaaallll DDDDiiiisssscccciiiipppplllliiiinnnneeeessss"""" }}}} sssswwww____sssseeeellll """"EEEEEEEE ppppaaaacccckkkk"""" {{{{ ddddeeeessssccccrrrriiiippppttttiiiioooonnnn ==== """"SSSSooooffffttttwwwwaaaarrrreeee AAAAppppppppssss ffffoooorrrr EEEElllleeeeccccttttrrrriiiiccccaaaallll EEEEnnnnggggiiiinnnneeeeeeeerrrriiiinnnngggg"""" sssswwww____ssssoooouuuurrrrcccceeee ==== """"PPPPeeeerrrr----DDDDiiiisssscccciiiipppplllliiiinnnneeee PPPPaaaacccckkkkssss"""" aaaarrrrcccchhhhiiiivvvveeee____ttttyyyyppppeeee ==== ggggzzzziiiipppp ttttaaaarrrr aaaarrrrcccchhhhiiiivvvveeee____ppppaaaatttthhhh ==== """"11110000....22220000____777700000000____eeeeeeee....ggggzzzz"""" sssswwww____ccccaaaatttteeeeggggoooorrrryyyy ==== """"DDDDiiiisssscccciiiipppplllliiiinnnneeeessss"""" #### UUUUsssseeee tttthhhheeee ////oooopppptttt////iiiiggggnnnniiiitttteeee////llllbbbbiiiinnnn////aaaarrrrcccchhhhiiiivvvveeee____iiiimmmmppppaaaaccccttttssss ttttoooooooollll ttttoooo ccccrrrreeeeaaaatttteeee tttthhhheeee #### iiiimmmmppppaaaaccccttttssss ssssiiiizzzzeeee ssssttttaaaatttteeeemmmmeeeennnnttttssss bbbbeeeelllloooowwww:::: iiiimmmmppppaaaaccccttttssss ==== """"////vvvvaaaarrrr"""" 11112222555566668888KKKKbbbb iiiimmmmppppaaaaccccttttssss ==== """"////uuuussssrrrr"""" 22223333444466668888KKKKbbbb iiiimmmmppppaaaaccccttttssss ==== """"////"""" 2222KKKKbbbb }}}} iiiinnnniiiitttt sssswwww____sssseeeellll """"EEEEEEEE ppppaaaacccckkkk"""" ==== ((((ddddiiiisssskkkk[[[[____hhhhpppp____rrrrooooooootttt____ddddiiiisssskkkk]]]]....ssssiiiizzzzeeee >>>> 1111888800000000MMMMbbbb)))) ################ The contents above would be stored in a file such as /var/opt/ignite/data/Rel_B.10.20/ee_apps_cfg and then added to the INDEX file using the command: - 42 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) ////oooopppptttt////iiiiggggnnnniiiitttteeee////bbbbiiiinnnn////mmmmaaaannnnaaaaggggeeee____iiiinnnnddddeeeexxxx ----aaaa \\\\ ----ffff ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////RRRReeeellll____BBBB....11110000....22220000////eeeeeeee____aaaappppppppssss____ccccffffgggg SSSScccchhhheeeedddduuuulllliiiinnnngggg aaaa ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt TTTToooo BBBBeeee RRRRuuuunnnn The ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ccccoooonnnnffffiiiigggg....llllooooccccaaaallll file is a convenient place to set the ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt keyword to run the scripts that should always be run, or that can be run based on a logic expression. This is also a convenient place to put kernel modifications that you want done on all systems you install. The example below schedules one script to always be run, one to be run if the system is a S890, and increases the maxuprc kernel tunable for all systems: ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt ++++==== """"////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ssssccccrrrriiiippppttttssss////ddddoooo____oooouuuurrrr____sssseeeettttuuuupppp"""" HHHHAAAARRRRDDDDWWWWAAAARRRREEEE____MMMMOOOODDDDEEEELLLL ======== """"9999000000000000////888899990000"""" {{{{ ppppoooosssstttt____ccccoooonnnnffffiiiigggg____ssssccccrrrriiiipppptttt ++++==== """"////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ssssccccrrrriiiippppttttssss////SSSS888899990000____sssseeeettttuuuupppp"""" }}}} mmmmoooodddd____kkkkeeeerrrrnnnneeeellll ==== """"mmmmaaaaxxxxuuuupppprrrrcccc 111100000000"""" AAAAUUUUTTTTHHHHOOOORRRR Ignite-UX and the configuration file syntax was developed by Hewlett Packard. FFFFIIIILLLLEEEESSSS ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////IIIINNNNDDDDEEEEXXXX The INDEX file is used on the Ignite-UX server to define what configurations are available, and which configuration files comprise each configuration. ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////RRRReeeellll____{{{{rrrreeeelllleeeeaaaasssseeee}}}} ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////RRRReeeellll____{{{{rrrreeeelllleeeeaaaasssseeee}}}} Each HP-UX release supported by Ignite-UX creates a directory where the configuration files defining the defaults for that releases are stored. In addition, a gzip-compressed tar archive called SSSSYYYYSSSSCCCCMMMMDDDDSSSS is stored in the /opt/ignite/data/Rel_* directory, and is the mini- system that is laid down on the disk and supplies the commands needed to load the rest of the software. The directories /var/opt/ignite/data/Rel_* are the recommended location to hold configuration files created locally and not part of the standard Ignite-UX product. ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ccccoooonnnnffffiiiigggg....llllooooccccaaaallll This configuration file is a place-holder for local modifications to the HP-UX defaults. It is typically included in every INDEX file ccccffffgggg clause after the default configuration files. ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ssssaaaavvvveeeedddd____ccccffffggggssss This directory is where the user interface stores configuration files that the user requests to be saved - 43 - Formatted: January 9, 2002 iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) iiiinnnnssssttttllll____aaaaddddmmmm((((4444)))) a standard configurations. The /var/opt/ignite/INDEX file will be modified to reference the files in this directory. ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////ssssccccrrrriiiippppttttssss ////vvvvaaaarrrr////oooopppptttt////iiiiggggnnnniiiitttteeee////ssssccccrrrriiiippppttttssss These two scripts directories are the recommended locations for scripts that are referenced by configuration files. The first path is used by scripts shipped as part of Ignite-UX. The second path is the recommended location user created scripts. ////oooopppptttt////iiiiggggnnnniiiitttteeee////ddddaaaattttaaaa////eeeexxxxaaaammmmpppplllleeeessss Example configuration files. See the comments in the files for details. SSSSEEEEEEEE AAAALLLLSSSSOOOO ignite(5), instl_adm(1M), make_config(1M), archive_impact(1M), instl_bootd(1M), bootpd(1M), swinstall(1M), swcopy(1M), lvmmigrate(1M). - 44 - Formatted: January 9, 2002