20.4. Parameters for Kickstart Installations

The following parameters can be defined in a parameter file but do not work in a CMS configuration file.
inst.ks=URL
References a Kickstart file, which usually resides on the network for Linux installations on System z. Replace URL with the full path including the file name of the Kickstart file. This parameter activates automatic installation with Kickstart. See Kickstart Boot Options and Section 26.2.5, “Starting the Kickstart Installation” for more details.
RUNKS=value

Important

This parameter is deprecated. If you use it in a Kickstart file, it will be ignored. Only the inst.ks= parameter is necessary to start a Kickstart installation on IBM System z.
Where value is defined as 1 if you want to run the loader automatically on the Linux console without having to log in over the network with SSH. To use RUNKS=1, the console must either support full-screen or the inst.cmdline option (below) should be used. The latter applies for the 3270 terminal under z/VM or the operating system messages console for LPAR. We recommend RUNKS=1 for fully automatic installations with Kickstart. When RUNKS=1 is set, the installation program automatically continues in case of parameter errors and does not interrupt unattended installations by prompting for user interaction.
Leave out the parameter or specify RUNKS=0 otherwise.
inst.cmdline
When this option is specified, output on line-mode terminals (such as 3270 under z/VM or operating system messages for LPAR) becomes readable, as the installation program disables escape terminal sequences that are only applicable to UNIX-like consoles. This requires installation with a Kickstart file that answers all questions, because the installation program does not support interactive user input in cmdline mode.
Ensure that your Kickstart file contains all required parameters before you use the inst.cmdline option. If a required command is missing, the installation will fail. See Chapter 26, Kickstart Installations for details.