English Urdu (Pakistan)
Kickstart Syntax Reference
This appendix describes commands and options available in Kickstart installations. For general information about Kickstart, see xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart].
Device names are not guaranteed to be consistent across reboots, which can complicate usage in Kickstart scripts. When a Kickstart option calls for a device node name (such as `sda`), you can instead use any item from `/dev/disk`. For example, instead of:
[command]#part / --fstype=xfs --onpart=sda1#
You could use an entry similar to one of the following:
part / --fstype=xfs --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1
part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1
This provides a consistent way to refer to disks that is more meaningful than just `sda`. This is especially useful in large storage environments.
While the general principles of Kickstart installations tend to stay the same, the commands and options can change between major releases. You can use the [command]#ksverdiff# command to display the differences between two versions of the Kickstart syntax. This is useful when updating an existing Kickstart file to be used with a new release. To display a list of changes in syntax between Fedora{nbsp}{PREVVER} and {PRODVER}, use the following command:
$ [command]#ksverdiff -f F{PREVVER} -t F{PRODVER}#
The [option]#-f# option specifies the release to start the comparison with, and the [option]#-t# option to specify the release to end with. For additional information, see the `ksverdiff(1)` man page. Also note that you can not use this to display changes in a release that is newer than your system - the version of [package]*pykickstart* on Fedora{nbsp}{PREVVER} can not display changes in Fedora{nbsp}{PRODVER}.
Additionally, you can review the [citetitle]_Fedora{nbsp}{PRODVER} Release Notes_, available at link:++https://docs.fedoraproject.org/++[], for a list of changes.
In the following sections, if an option is followed by an equals mark (`=`), a value must be specified after it. In the example commands, options in square brackets (`[ ]`) are optional arguments for the command.
Installation Methods and Sources
The following commands control the way Fedora will be installed.
device (optional) - Install Extra Device Drivers
On most PCI systems, the installation program will automatically detect Ethernet and SCSI cards. However, on older systems and some PCI systems, Kickstart requires a hint to find the proper devices. The [command]#device# command, which tells the installation program to install extra modules, uses the following format:
[command]#device _moduleName_ [--opts=]#
Replace _moduleName_ with the name of the kernel module which should be installed.
Options to pass to the installed kernel module. For example: