The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not push the repository. Could not update the repository.
English Czech
On a *hard drive* connected to the installation system
Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation will continue. Note that if the system you are installing has no display, you will not be able to see the prompt, and the installation will appear to have failed.
Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
Making the Kickstart File Available
Make the Kickstart file available on removable media, a hard drive, or a network location.
Lines starting with a pound sign (`#`) are treated as comments and are ignored.
Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows the you to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying {PRODUCT} on a large number of systems at once.
Kickstart installations can be performed using a local DVD, a local hard drive, or via NFS, FTP, HTTP, or HTTPS.
Keep in mind that the validation tool has its limitations. The Kickstart file can be very complicated; [application]*ksvalidator* can make sure the syntax is correct and that the file does not include removed options, but it cannot guarantee the installation will be successful. It also does not attempt to validate the [command]#%pre#, [command]#%post# and [command]#%packages# sections of the Kickstart file.
How to Perform a Kickstart Installation
For more information about this tool, see the `ksvalidator(1)` man page.
# dnf install pykickstart
Creating a Kickstart File
Create boot media or configure a network boot (PXE) server which will be used to begin the installation.
Create a Kickstart file.
Automating the Installation with Kickstart
All Kickstart scripts and the log files of their execution are stored in the `/tmp` directory to assist with debugging installation issues.
After installing the package, you can validate a Kickstart file using the following command:
$ [command]#ksvalidator _/path/to/kickstart.ks_#