26.6. Parameters for Kickstart Installations
The following parameters can be defined in a parameter file but do not work in a CMS configuration file.
- 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. Refer to Section 28.4, “Automating the Installation with Kickstart” and Section 32.11, “Starting a Kickstart Installation” for more details.]
- 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
cmdlineoption 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=1for fully automatic installations with kickstart. When
RUNKS=1is set, linuxrc automatically continues in case of parameter errors and does not interrupt unattended installations by prompting for user interaction.Leave out the parameter or specify
cmdlineis specified, output on line-mode terminals (such as 3270 under z/VM or operating system messages for LPAR) becomes readable, as the installer disables escape terminal sequences that are only applicable to UNIX-like consoles. This requires installation with a kickstart file that answers all questions, since the installer does not support interactive user input in cmdline mode.
Ensure that your kickstart file contains all required parameters before you use either the
cmdlineoptions. Refer to Chapter 32, Kickstart Installations for details.