- 	<productnumber>23</productnumber>

- 									an ISO image of the full &PRODUCT; installation DVD, placed on a hard drive or a network location accessible from the installation system

- 											Specific CD/DVD drive

- 									File system label, for example <systemitem>LABEL=Flash</systemitem> or <systemitem>LABEL=RHEL7</systemitem>

- 								You should never attempt to perform a driver update during the installation unless a missing our faulty driver is preventing you from completing the installation. Updating drivers which are not essential during the installation should always be performed after the system is installed.

- 							Sets the language to be used during the installation. Language codes are the same as the ones used in the <command>lang</command> Kickstart command as described in <xref linkend="sect-kickstart-commands-lang" />. On systems where the <package>system-config-language</package> package is installed, a list of valid values can also be find in <filename>/usr/share/system-config-language/locale-list</filename>.

- 						<screen><option>vlan=vlan5:em1</option></screen>

- 							The above will set up a VLAN device named <literal>vlan5</literal> on the <literal>em1</literal> interface. The <replaceable>name</replaceable> can take the following forms:

- 											<literal>vlan0005</literal>

- 											<literal>vlan5</literal>

- 											<literal>em1.0005</literal>.

- 											<literal>em1.5</literal>.

- 							Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode.

- 							This option controls the usage of <firstterm>zRAM</firstterm> swap during the installation. It creates a compressed block device inside the system RAM and uses it for swap space instead of the hard drive. This allows the installer to essentially increase the amount of memory available, which makes the installation faster on systems with low memory.

- 							By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabled on systems with more than 2 GB of memory. You can use this option to change this behavior - on a system with more than 2 GB RAM, use <option>inst.zram=1</option> to enable it, and on systems with 2 GB or less memory, use <option>inst.zram=0</option> to disable this feature.

- 							Turns the <application>Kdump</application> installer add-on <literal>on</literal> or <literal>off</literal> (the add-on is off by default). If you use <option>inst.kdump_addon=on</option>, a new screen, which allows you to configure the <application>Kdump</application> kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see <xref linkend="sect-installation-gui-kdump" />). Enabling this add-on is also necessary to use the <xref linkend="sect-kickstart-commands-kdump" /> Kickstart command.

- 							Once the installation starts, this option sends log messages to the syslog process on the specified host. The remote syslog process must be configured to accept incoming connections. <!-- TODO: Where do we document remote logging? -->

- 					</table>

- 					<important> <!-- TODO: check BZ#1085310 -->

- 						<para>

- 							When performing a Kickstart installation, booting from local media and having the Kickstart file on local media as well, the network will not be initialized. This means that any other Kickstart options requiring network access, such as pre-installation or post-installation scripts accessing a network location, will cause the installation to fail. This is a known issue; see BZ#<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=1085310">1085310</ulink> for details.

- 						</para>

- 						<para>

- 							To work around this issue, either use the <option>ksdevice=link</option> boot option, or add the <option>--device=link</option> option to the <command>network</command> command in your Kickstart file.

- 						</para>

- 					</important>

- 				</listitem>

- 			<note>

- 				<para>

- 					<application>Memtest86+</application> only works on systems with BIOS firmware. Support for UEFI systems is currently unavailable.

- 				</para>

- 			</note>

- 						On Mac hardware, hold down the <keycap>Option</keycap> key to enter the boot media selection menu.

- 			</para>

- 			When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press <keycap>Enter</keycap> on BIOS or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> on UEFI to boot the installer using your customized options.

- 					The Rescan Disks dialog, showing a completed scan. Pressing OK now will take you back to the Installation Destination screen.

- 		If such a message is displayed, go back and fix any issues found by the installer; otherwise you will not be able to proceed with the installation. You can also press <guilabel>Done</guilabel> again to return to the <guilabel>Installation Summary</guilabel> anyway, but a storage configuration error will prevent you from starting the actual installation process.

- 					The configuration dialog does not allow you to specify the size of the volume group's <firstterm>physical extents</firstterm>. The size will always be set to the default value of 4 MiB. If you want to create a volume group with different physical extents, create it manually by switching to an interactive shell and using the <command>vgcreate</command> command, or use a Kickstart file with the <command>volgroup --pesize=<replaceable>size</replaceable></command> command. 

- 				In the <guilabel>Device(s)</guilabel> section on the right side of the screen, you can see that the partition has been assigned to one or more hard drives. Click the <guilabel>Modify</guilabel> button to configure on which drive this partition will be created.

- 				In the <guilabel>Configure Mount Point</guilabel> dialog, you can specify which physical devices (disks) this volume <emphasis>may</emphasis> reside on. You can select one or more disks which will be used to hold this volume by holding down <keycap>Ctrl</keycap> and clicking each disk in the list. If you select multiple disks here, <application>Anaconda</application> will determine where exactly the partition should be created based on how you configured the rest of the installation. If you want to make sure that this partition is placed on a specific hard drive, select only that drive and unselect all others.

- 				<guilabel>LVM Thin Provisioning</guilabel> - Using thin provisioning, you can manage a storage pool of free space, known as a <firstterm>thin pool</firstterm>, which can be allocated to an arbitrary number of devices when needed by applications. The thin pool can be expanded dynamically when needed for cost-effective allocation of storage space.

- 				<guilabel>BTRFS</guilabel> - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See <xref linkend="sect-installation-gui-manual-partitioning-btrfs" /> for more information about creating Btrfs volumes. 

- 				<guilabel>swap</guilabel> - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created; see <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details such as the recommended size.

- 				<guilabel>xfs</guilabel> - XFS is a highly scalable, high-performance file system that supports file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and directory structures containing tens of millions of entries. XFS also supports metadata journaling, which facilitates quicker crash recovery. The maximum supported size of a single XFS file system is 500 TB. Starting with &PRODUCT;&nbsp;22, XFS is the default and recommended file system on &PRODUCT; Server.

- 					Note that the size of an XFS file system can not currently be reduced without destroying and recreating the file system. If you expect that you will need to adjust the sizes of your file systems often, using XFS is not recommended, as it makes administration substantially more time-consuming.

- 				Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the <filename class="directory">/boot</filename> directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and <filename class="directory">/usr</filename> can not be on a Btrfs subvolume.

- 				Each kernel installed on your system requires approximately 20 MB on the <filename class="directory">/boot</filename> partition. The default partition size of 500 MB for <filename class="directory">/boot</filename> should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time.

- 				The contents of the <filename class="directory">/var</filename> directory usually change very often. This may cause problems with older solid state drives (SSDs), as they can handle a lower number of read/write cycles before becoming unusable. If your system root is on an SSD, consider creating a separate mount point for <filename class="directory">/var</filename> on a classic (platter) HDD.

- 					For a minimal installation, a 5 GB root partition will be sufficient. However, for most common installations which include extra packages and a graphical user interface, the root partition should be at least 10 GB; with 20 GB being sufficient for most common use cases.

- 					To store user data separately from system data, create a dedicated mount point for the <filename>/home</filename> directory. This partition should be sized based on the amount of data that will be stored locally, number of users, and so on. This will allow you to upgrade or reinstall &PRODUCT; without erasing user data files. During the installation, a separate <filename class="directory">/home</filename> partition will be created if there are 50 GB or more free space for your &PRODUCT; installation.

- 					When the system runs out of swap space, the kernel terminates processes as the system RAM memory is exhausted. Configuring too much swap space results in storage devices being allocated but idle and is a poor use of resources. Too much swap space can also hide memory leaks. The maximum size for a swap partition and other additional information can be found in the <systemitem>mkswap(8)</systemitem> man page. 

- 						A small percentage of the driver's available space is used to store file system-related data and can be considered as overhead.

- 				Note that there is no single, universal file system. As <xref linkend="figu-partitions-different-file-system" />, shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, &PRODUCT; supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windows), making data interchange between different file systems easy.

- 						Logical separation of the operating system data from the user data

- 						Ability to run multiple operating systems on one machine

- 					There must be a BIOS boot partition for the boot loader to be installed successfully onto a disk that contains a GPT (GUID Partition Table). This includes disks initialized by <application>Anaconda</application>. If the disk already contains a BIOS boot partition, it can be reused.

- 			<figure id="figu-partitions-unused-partition">

- 					The Fedora Server netinstall image is a universal one, and can be used to install any Fedora flavor or your own set of favorite packages.

- 					The tiny images at <ulink url="https://boot.fedoraproject.org/" /> are written to CDs, USB drives, or even floppy disks. The BFO image loads installation media from Fedora's servers and directly loads an installation environment, like the netinstall ISO.

- <!ENTITY NEXTVER "24">

- <!ENTITY PRODVER "23">

- <!ENTITY PREVVER "22">

- <!ENTITY YEAR "2015">

- 								<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> <keycap>1</keycap>

- 								<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> <keycap>2</keycap>

- 								<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> <keycap>3</keycap>

- 								<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> <keycap>4</keycap>

- 								<keycombo><keycap>Ctrl</keycap><keycap>b</keycap></keycombo> <keycap>5</keycap>

- 					The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation.

- 					The Kdump configuration screen, showing 128 MB reserved

- 		To enable <application>Kdump</application> on the installed system, check <guilabel>Enabled</guilabel>. Then, select either <guilabel>Automatic</guilabel> or <guilabel>Manual</guilabel> memory reservation settings, and if you selected <guilabel>Manual</guilabel>, enter the amount of memory to be reserved in megabytes into the <guilabel>Memory to be reserved</guilabel> field.

- 		The amount of memory which you should reserve is determined based on your system's architecture (AMD64 and Intel&nbsp;64 will have different requirements than IBM Power, for example) as well as the total amount of system memory. In most cases, automatic reservation will be satisfactory. If you insist on manual settings, see the <ulink url="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Crash_Dump_Guide/appe-supported-kdump-configurations-and-targets.html#sect-kdump-memory-requirements">Red&nbsp;Hat Enterprise&nbsp;Linux&nbsp;7 Kernel Crash Dump Guide</ulink> for guidelines. This document also contains more in-depth information about how <application>Kdump</application> works, how to configure additional settings, and how to analyze a saved crash dump.

- 		The <guilabel>Usable System Memory</guilabel> readout below the reservation input field shows how much memory will be accessible to your main system once your selected amount of RAM is reserved.

- 				The up and down buttons can be used to move the highlighted layout up or down in the list.

- 			</para>

- 		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.

- 						</listitem>

- 			<screen><prompt>$</prompt> <command>ksvalidator <replaceable>/path/to/kickstart.ks</replaceable></command></screen>

- <command>part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1</command>

- 		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> 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:

- 	<section id="sect-kickstart-commands-installation">

- 		<title>Installation Methods and Sources</title>

- 		<para>

- 			The following commands control the way Fedora will be installed.

- 		</para>

- 

- 		<section id="sect-kickstart-commands-device">

- 			<title>device (optional) - Install Extra Device Drivers</title>

- 			<para>

- 				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> command, which tells the installation program to install extra modules, uses the following format:

- 			</para>

- 			<programlisting><command>device <replaceable>moduleName</replaceable> [--opts=]</command></programlisting>

- 			<para>

- 				Replace <replaceable>moduleName</replaceable> with the name of the kernel module which should be installed.

- 			</para>

- 			<variablelist>

- 				<varlistentry>

- 					<term><option>--opts=</option></term>

- 					<listitem>

- 						<para>

- 							Options to pass to the installed kernel module. For example:

- 						</para>

- 						<programlisting><command>device i2c_piix4 --opts="aic152x=0x340 io=11"</command></programlisting>

- 					</listitem>

- 				</varlistentry>

- 			</variablelist>

- 		</section>

- 

- 		<section id="sect-kickstart-commands-driverdisk">

- 			<title>driverdisk (optional) - Use a Driver Disk</title>

- 			<para>

- 				Driver disks can be used during Kickstart installations to provide additional drivers not included by default. You must copy the driver disks's contents to the root directory of a partition on the system's hard drive. Then, you must use the <command>driverdisk</command> command to specify that the installation program should look for a driver disk and its location.

- 			</para>

- 			<programlisting><command>driverdisk <replaceable>partition</replaceable> | --source= | --biospart=</command></programlisting>

- 			<variablelist>

- 				<varlistentry>

- 					<term><replaceable>partition</replaceable></term>

- 					<listitem>

- 						<para>

- 							Search for the driver disk image on a local partition. Replace <replaceable>partition</replaceable> with the name of the partition containing the driver disk. Note that the partition must be specified as a full path. For example:

- 						</para>

- 						<programlisting><command>driverdisk /dev/sdb1</command></programlisting>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 					<term><option>--source=</option></term>

- 					<listitem>

- 						<para>

- 							Search for the driver disk in a network location instead of a local partition. For example:

- 						</para>

- 						<programlisting><command>driverdisk --source=ftp://<replaceable>path/to/dd.img</replaceable></command></programlisting>

- 						<programlisting><command>driverdisk --source=http://<replaceable>path/to/dd.img</replaceable></command></programlisting>

- 						<programlisting><command>driverdisk --source=nfs:<replaceable>hostname</replaceable>:/<replaceable>path/to/dd.img</replaceable></command></programlisting>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 					<term><option>--biospart=</option></term>

- 					<listitem>

- 						<para>

- 							BIOS partition containing the driver disk (for example, <literal>82p2</literal>).

- 						</para>

- 					</listitem>

- 				</varlistentry>

- 			</variablelist>

- 		</section>

- 

- 		<section id="sect-kickstart-commands-install">

- 				Automatically creates partitions: a root (<filename class="partition">/</filename>) partition (1 GB or larger), a <filename class="partition">swap</filename> partition, and an appropriate <filename class="partition">/boot</filename> partition for the architecture. On large enough drives (50&nbsp;GB and larger), this also creates a <filename class="partition">/home</filename> partition.

- 							Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.

- 					<term><option>--boot-drive=</option></term>

- 					<listitem>

- 						<para>

- 							Specifies which drive the boot loader should be written to, and therefore which drive the computer will boot from. If you use a multipath device as the boot drive, specify only one member of the device.

- 						</para>

- 						<important>

- 							<para>

- 								The <option>--boot-drive=</option> option is currently being ignored in &PRODUCT; installations on IBM System&nbsp;z systems using the <application>zipl</application> boot loader. When <application>zipl</application> is installed, it determines the boot drive on its own.

- 							</para>

- 						</important>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 				<varlistentry>

- 					<term><option>--default=</option></term>

- 					<listitem>

- 						<para>

- 							Sets the default boot image in the boot loader configuration.

- 						</para>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 					<term><option>--extlinux</option></term>

- 					<listitem>

- 						<para>

- 							Use the <application>extlinux</application> boot loader instead of <application>GRUB2</application>. This option only works on systems supported by <application>extlinux</application>.

- 						</para>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 					<term><option>--disabled</option></term>

- 					<listitem>

- 						<para>

- 							Do not attempt to install a boot loader. This option overrides all other boot loader configuration; all other boot loader options will be ignored and no boot loader packages will be installed.

- 						</para>

- 					</listitem>

- 				</varlistentry>

- 				<varlistentry>

- 					<term><option>--nombr</option></term>

- 					<listitem>

- 						<para>

- 							Install the boot loader configuration and support files, but do not modify the MBR.

- 						</para>

- 					</listitem>

- 				</varlistentry>

- 			</variablelist>

- 		</section>

- 

- 					<listitem>

- 						<para>

- 							Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.

- 						</para>

- 						<important>

- 							<para>

- 								This option can only be used for partitions which result in a file system such as the <filename>/boot</filename> partition and <systemitem>swap</systemitem> space. It can not be used to create partitionsm, LVM physical or logical volumes or RAID members.

- 							</para>

- 						</important>

- 					</listitem>

- 				<varlistentry>

- 					<listitem>

- 							Specifies that this logical volume should be encrypted, using the passphrase provided in the <option>--passphrase=</option> option. If you do not specify a passphrase, the installation program will use the default, system-wide passphrase set with the <command>autopart --passphrase</command> command, or stop the installation and prompt you to provide a passphrase if no default is set.

- 							Specifies which type of encryption will be used if the <application>Anaconda</application> default <systemitem>aes-xts-plain64</systemitem> is not satisfactory. You must use this option together with the <option>--encrypted</option> option; by itself it has no effect. Available types of encryption are listed in the <citetitle>Fedora Security Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. Using either <systemitem>aes-xts-plain64</systemitem> or <systemitem>aes-cbc-essiv:sha256</systemitem> is strongly recommended.

- 					<term><option>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></option></term>

- 			<variablelist>

- 				This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the <systemitem>root</systemitem> password, user passwords and LUKS (disk encryption) password.

- 				Use this command to add a specified <systemitem>SSH</systemitem> key to an user's <filename>authorized_keys</filename> file. The specified user must either be <systemitem>root</systemitem>, or it must be created in the Kickstart file - either automatically by an installed package, or using <xref linkend="sect-kickstart-commands-user" />.

- 		</section>