Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Red Hat Enterprise Linux 9 Essentials Book now available.

Purchase a copy of Red Hat Enterprise Linux 9 (RHEL 9) Essentials

Red Hat Enterprise Linux 9 Essentials Print and eBook (PDF) editions contain 34 chapters and 298 pages

Preview Book

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.10, “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 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, 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 RUNKS=0 otherwise.
When cmdline is 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 RUNKS or cmdline options. Refer to Chapter 32, Kickstart Installations for details.

  Published under the terms of the Creative Commons License Design by Interspire