Installation Source:--

hard drive:-
  Install from a directory of ISO images on a local drive, which must be either vfat or ext2. In addition to this directory, you must also provide the install.img in some way. You can either do this by booting off the boot.iso or by creating an images/ directory in the same directory as the ISO images and placing install.img in there.


BIOS partition to install from (such as 82p2).


Partition to install from (such as, sdb2).


Directory containing both the ISO images and the images/install.img. For example:

harddrive --partition=hdb2 --dir=/tmp/install-tree


Install from the NFS server specified. This can either be an exploded installation tree or a directory of ISO images. In the latter case, the install.img must also be provided subject to the same rules as with the harddrive installation method described above.


Server from which to install (hostname or IP).


Directory containing the Packages/ directory of the installation tree. If doing an ISO install, this directory must also contain images/install.img.


Mount options to use for mounting the NFS export. Any options that can be specified in /etc/fstab for an NFS mount are allowed. The options are listed in the nfs(5) man page. Multiple options are separated with a comma.

For example:

nfs --dir=/tmp/install-tree


Install from an installation tree on a remote server via FTP or HTTP.


The URL to install from.


Specify an HTTP/HTTPS/FTP proxy to use while performing the install. The various parts of the argument act like you would expect.


For a tree on a HTTPS server do not check the server's certificate with what well-known CA validate and do not check the server's hostname matches the certificate's domain name.


Controls anaconda's access to disks attached to the system. Only one of the following two options may be used.

ignoredisk --drives=[disk1,disk2,...]

Specifies those disks that anaconda should not touch when partitioning, formatting, and clearing.

ignoredisk --only-use=[disk1,disk2,...]

Specifies the opposite - only disks listed here will be used during installation.


Specifies additional iSCSI storage to be attached during installation. If you use the iscsi parameter, you must also assign a name to the iSCSI node, using the iscsiname parameter. The iscsiname parameter must appear before the iscsi parameter in the kickstart file.

iscsi --ipaddr= [options]

We recommend that wherever possible you configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the iscsi parameter. *Anaconda* automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the kickstart file.

If you must use the iscsi parameter, ensure that networking is activated at the beginning of the installation, and that the iscsi parameter appears in the kickstart file before you refer to iSCSI disks with parameters such as clearpart or ignoredisk.

--ipaddr= (mandatory)

The IP address of the target to connect to.


The port number to connect to (default, --port=3260).


The username required to authenticate with the target.


The password that corresponds with the username specified for the target.


The username required to authenticate with the initiator from a target that uses reverse CHAP authentication.


The password that corresponds with the username specified for the initiator.

iscsiname (optional)

Assigns a name to an iSCSI node specified by the iscsi parameter. If you use the iscsi parameter in your kickstart file, this parameter is mandatory, and you must specify iscsiname in the kickstart file before you specify iscsi.

iscsiname <iqn>


This required command sets system keyboard type. Here is the list of available keyboards on i386, Itanium, and Alpha machines:

be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2, ru_win, se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup, speakup-lt, sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua, uk, us, us-acentos


lang <id>

This required command sets the language to use during installation and the default language to use on the installed system to <id>. This can be the same as any recognized setting for the $LANG environment variable, though not all languages are supported during installation.

Certain languages (mainly Chinese, Japanese, Korean, and Indic languages) are not supported during text mode installation. If one of these languages is specified using the lang command, installation will continue in English though the running system will have the specified langauge by default.

The file /usr/share/system-config-language/locale-list provides a list the valid language codes in the first column of each line and is part of the system-config-languages package.


Create a logical volume for Logical Volume Management (LVM).

logvol <mntpoint> --vgname=<name> --size=<size> --name=<name> <options>


Use an existing logical volume and do not format it.


Use an existing logical volume and reformat it.


Sets the file system type for the logical volume. Valid values include ext4, ext3, ext2, btrfs, swap, and vfat. Other filesystems may be valid depending on command line arguments passed to anaconda to enable other filesystems. Btrfs is a experimental filesystem. Do take regular backups if you are using it.


Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.


Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting.


The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here, and do not append the number with MB.


Determine the size of the logical volume automatically.


Specify the size of the logical volume as a percentage of available space in the volume group.


Specify that this logical volume should be encrypted.


Specify the passphrase to use when encrypting this logical volume. Without the above --encrypted option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.


Load an X.509 certificate from <url>. Store the data encryption key of this logical volume, encrypted using the certificate, as a file in /root. Only relevant if --encrypted is specified as well.


Only relevant if --escrowcert is specified as well. In addition to storing the data encryption key, generate a random passphrase and add it to this logical volume. Then store the passphrase, encrypted using the certificate specified by --escrowcert, as a file in /root. If more than one LUKS volume uses --backuppassphrase, the same passphrase will be used for all such volumes.

Create the partition first, create the logical volume group, and then create the logical volume. For example:

part pv.01 --size 3000

volgroup myvg pv.01

logvol / --vgname=myvg --size=2000 --name=rootvol


This command controls the error logging of anaconda during installation. It has no effect on the installed system.


Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.


If the remote syslogd process uses a port other than the default, it may be specified with this option.


One of debug, info, warning, error, or critical.

Specify the minimum level of messages that appear on tty3. All messages will still be sent to the log file regardless of this level, however.


If given, this will force anaconda to run mediacheck on the installation media. This command requires that installs be attended, so it is disabled by default.


If the monitor command is not given, anaconda will use X to automatically detect your monitor settings. Please try this before manually configuring your monitor.


Specifies the horizontal sync frequency of the monitor.


Use specified monitor; monitor name should be from the list of monitors in /usr/share/hwdata/MonitorsDB from the hwdata package. The list of monitors can also be found on the X Configuration screen of the Kickstart Configurator. This is ignored if --hsync or --vsync is provided. If no monitor information is provided, the installation program tries to probe for it automatically.


Do not probe the monitor.


Specifies the vertical sync frequency of the monitor.


multipath --name= --device= --rule=


Configures network information for the system. If the kickstart installation does not require networking (in other words, it is not installed over NFS, HTTP, or FTP), networking is not configured for the system. If the installation does require networking and network information is not provided in the kickstart file, the installation program assumes that the installation should be done over eth0 via a dynamic IP address (BOOTP/DHCP), and configures the final, installed system to determine its IP address dynamically. The network option configures networking information for kickstart installations via a network as well as for the installed system.


The default setting is dhcp. bootp and dhcp are treated the same.

The DHCP method uses a DHCP server system to obtain its networking configuration. As you might guess, the BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. 

The static method requires that you enter all the required networking information in the kickstart file. As the name implies, this information is static and will be used during and after the installation. The line for static networking is more complex, as you must include all network configuration information on one line. You must specify the IP address, netmask, gateway, and nameserver. For example: (the \ indicates that it is all one line):

network --bootproto=static --ip= \

--netmask= --gateway= \


If you use the static method, be aware of the following restriction:

All static networking configuration information must be specified on one line; you cannot wrap lines using a backslash, for example.


Used to select a specific Ethernet device for installation. The device can be specified by either a device name (e.g., --device=eth0) or by MAC address (e.g. --device=aa:bb:cc:dd:ee:ff). Note that using --device= will not be effective unless the kickstart file is a local file (such as ks=floppy), since the installation program will configure the network to find the kickstart file. For example:

network --bootproto=dhcp --device=eth0


IP address for the interface.


IPv6 address for the interface. This can be the static address, "auto" for address assignment based on automatic neighbor discovery, or "dhcp" to use the DHCPv6 protocol.


Default gateway as an IP address.


Primary nameserver, as an IP address. Multiple nameservers must be comma separated.


Do not configure any DNS server.


Netmask for the installed system.


Hostname for the installed system.


Specifies additional low-level settings for the network device which will be passed to the ethtool program.


The network ID for wireless networks.


The encryption key for wireless networks.


Whether or not to enable the device a boot time.


The DHCP class.


The MTU of the device.


Disable IPv4 on this device.


Disable IPv6 on this device.