# Installation Guide {#idm2190000}
## Installing Fedora 20 on 32 and 64-bit Intel-compatible computers
###
### Fedora Documentation Project
Copyright © 2013 Red Hat, Inc. and others.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at .
## 2\. About This Document {#sn-about-document}
### 2\.1. Goals {#sn-goals}
This guide helps a reader:
1. Understand how to locate the Fedora distribution online
1. Create configuration data that allows a computer to boot Fedora
1. Understand and interact with the Fedora installation program
1. Complete basic post-installation configuration of a Fedora system
### Other Sources of Documentation
This guide does not cover use of Fedora. To learn how to use an installed Fedora system, refer to . This page lists mirrors according to geographic location. The mirrors geographically closest to you are likely to provide you with the fastest downloads. If the company or organization that provides your internet access maintains a mirror, this mirror is likely to provide you with the fastest downloads of all.
Mirrors publish Fedora software under a well-organized hierarchy of folders. For example, the Fedora 20 distribution normally appears in the directory `fedora/linux/releases/20/`. This directory contains a folder for each architecture supported inside that folder, in a folder called `iso/`. For example, you can find the file for the DVD distribution of Fedora 20 for x86\_64 at `fedora/linux/releases/20/Fedora/x86_64/iso/Fedora-20-x86_64-DVD.iso`.
#### 2\.1.1.2. From BitTorrent {#sn-which-download-bt}
BitTorrent is a way to download information in cooperation with other computers. Each computer cooperating in the group downloads pieces of the information in a particular torrent from other peers in the group. Computers that have finished downloading all the data in a torrent remain in the swarm to _seed_, or provide data to other peers. If you download using BitTorrent, as a courtesy you should seed the torrent at least until you have uploaded the same amount of data you downloaded.
If your computer does not have software installed for BitTorrent, visit the BitTorrent home page at .
### 2\.1.2. Which Architecture Is My Computer? {#sn-which-arch}
Releases are separated by _architecture_, or type of computer processor. Use the following table to determine the architecture of your computer according to the type of processor. Consult your manufacturer's documentation for details on your processor, if necessary.
Table 2.1. Processor and architecture types
|Processor manufacturer and model|Architecture type for Fedora|
|-|
|Intel Atom (see note below,) Core series, Pentium 4, and recent vintage Xeon; AMD Athlon, Duron, some Semprons; and older; VIA C3, C7|`i386` (32-bit)|
|Intel Atom (See note below), Core 2 series, Core i series and Xeon; AMD: Athlon 64, Athlon II, Sempron64, Phenom series, Fusion series, Bulldozer series and Opteron; Apple MacBook, MacBook Pro, and MacBook Air|`x86_64` (64-bit)|
for more information on using Fedora on these systems.
### Intel Atom Processor Architectures Vary
The Z Series and N200 Series Atom processors are based on the `i386` architecture. The 230 and 330 Series and the rest of the N Series Atom processors are based on the `x86_64` architecture. Refer to for more details.
### Fedora supports UEFI only on 64bit systems
Fedora only supports UEFI booting on 64-bit systems. Users with 32bit systems or those who wish to use 32-bit Fedora on a 64-bit system will need to use BIOS-style or `CSM>` boot methods. This change is made in the system firmware's menu, refer to your manufacturer's documentation for details.
### 2\.1.3. Which Files Do I Download? {#sn-which-files}
You have several options to download Fedora. Read the options below to decide the best one for you.
Each file available for download in a Fedora distribution includes the architecture type in the file name. For example, the file for the DVD distribution of Fedora 20 for x86\_64 is named `Fedora-20-x86_64-DVD.iso`. Refer to [Section 2.1.2, “Which Architecture Is My Computer?”](#sn-which-arch "2.1.2. Which Architecture Is My Computer?") if you are unsure of your computer's architecture.
1. Full Distribution on DVD. If you have plenty of time, a fast Internet connection, and wish a broader choice of software on the install media, download the full DVD version. Once burned to DVD, the media is bootable and includes an installation program. The DVD version contains a mode to perform rescue operations on your Fedora system in an emergency. You can download the DVD version directly from a mirror, or via BitTorrent.
1. Live Image. If you want to try Fedora before you install it on your computer, download the Live image version. If your computer supports booting from CD or USB, you can boot the operating system without making any changes to your hard disk. If you decide you like what you see, and want to install it, select `Install to Hard Drive` on the desktop to copy Fedora to your hard disk (alternatively, in GNOME, a shortcut can be found in the Activities menu). You can download the Live image directly from a mirror, or using BitTorrent.
For more detailed instructions on setting up a Live image installation, including selecting a language for the installation process, refer to the _Fedora Installation Quick Start Guide_.
1. Minimal Boot Media. If you have a fast Internet connection but do not want to download the entire distribution, you can download a small boot image. Fedora offers images for a minimal boot environment on CD. Once you boot your system with the minimal media, you can install Fedora directly over the Internet. Although this method still involves downloading a significant amount of data over the Internet, it is almost always much less than the size of the full distribution media. Once you have finished installation, you can add or remove software to your system as desired.
### Download Size
Installing the default software for Fedora over the Internet requires more time than the Live image, but less time than the entire DVD distribution. Actual results depend on the software you select and network traffic conditions.
You can also download the images directly from a mirror, instead of browsing through The following table explains where to find the desired files on a mirror site. Replace _`arch`_ with the architecture of the computer being installed. If you don't have a preferred mirror, the url `http://download.fedoraproject.org` will automatically resolve one.
Table 2.2. Locating files
|Media type|File locations|
|-|
|Full distribution on DVD|``fedora/linux/releases/20/Fedora/_`arch`_/iso/Fedora-20-_`arch`_-DVD.iso``|
|Live image|``fedora/linux/releases/20/Live/_`arch`_/iso/Fedora-Live-Desktop-_`arch`_-20-1.iso``, ``fedora/linux/releases/20/Live/_`arch`_/iso/Fedora-Live-KDE-_`arch`_-20-1.iso``|
|Minimal CD boot media|``fedora/linux/releases/20/Fedora/_`arch`_/iso/Fedora-20-_`arch`_-netinst.iso``|
.
# Chapter 3. Making Media {#sn-making-media}
Use the methods described in this section to create the following types of installation and boot media:
* an installation DVD
* a USB flash drive to use as an installation source
* a minimal boot CD or DVD that can boot the installer
* a USB flash drive to boot the installer
The following table indicates the types of boot and installation media available for different architectures and notes the image file that you need to produce the media.
Table 3.1. Boot and installation media
|Architecture|Installation DVD|Installation USB flash drive|Boot CD or boot DVD|Boot USB flash drive|Live image DVD or USB flash drive|
|-|
|BIOS-based 32-bit x86|x86 DVD ISO image file|x86 DVD ISO image file|x86 netinst ISO image file|x86 netinst ISO image file|x86 Live ISO image file|
|UEFI-based 32-bit x86|Not available|
|BIOS-based AMD64 and Intel 64|x86\_64 DVD ISO image file (to install 64-bit operating system) or x86 DVD ISO image file (to install 32-bit operating system)|x86\_64 DVD ISO image file (to install 64-bit operating system) or x86 DVD ISO image file (to install 32-bit operating system)|x86\_64 netinst ISO image file|x86\_64 netinst ISO image file|x86\_64 Live ISO image file|
|UEFI-based AMD64 and Intel 64|x86\_64 DVD ISO image file|x86\_64 DVD ISO image file|x86\_64 netinst ISO image file|x86\_64 netinst ISO image file|x86\_64 Live ISO image file|
.
1. LiveUSB Creator can create live USB media either from an image file that you downloaded previously, as described in [Section 2.1.3, “Which Files Do I Download?”](#sn-which-files "2.1.3. Which Files Do I Download?"), or it can download an image file from the Internet. Either:
* click the Browse button under the Use existing LiveCD label, browse to the location where you previously downloaded a Fedora Live ISO file, and select that file.
* select a Fedora Live ISO file from the drop-down menu that LiveUSB Creator presents under the Download Fedora label. Note that image files are large and that it is probably impractical to use LiveUSB Creator to download an image file if you do not have a broadband connection to the Internet.
1. Click Create Live USB.
### 3\.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems {#Making_USB_Media-UNIX_Linux}
A graphical tool is available to create Fedora USB media on systems that run Fedora or operating systems derived from Fedora. To create Fedora USB media on other UNIX or Linux operating systems (including Mac OS X), use the command-line method described in [Section 3.2.2.1.3, “Making Fedora USB Media with dd”](#Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd "3.2.2.1.3. Making Fedora USB Media with dd").
#### 3\.2.2.1. Creating Fedora USB Media in Fedora and similar Linux distributions {#Making_USB_Media-UNIX_Linux-RHEL_Fedora}
Graphical and command-line tools are available to create Fedora USB media on computers that run Fedora and Linux distributions derived from Fedora. The command line tools work with both Fedora DVD and live images, but the graphical tool works only with live images. To create Fedora USB media from the distribution image or minimal boot media image, use one of the command line methods described in [Section 3.2.2.1.2, “Making Fedora USB Media with livecd-tools”](#Making_USB_Media-UNIX_Linux-RHEL_Fedora-livecd-tools "3.2.2.1.2. Making Fedora USB Media with livecd-tools") and [Section 3.2.2.1.3, “Making Fedora USB Media with dd”](#Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd "3.2.2.1.3. Making Fedora USB Media with dd").
##### 3\.2.2.1.1. Making Fedora USB Media with a graphical tool {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-graphical}
### Important — Enable Extra Packages for Enterprise Linux
To perform this procedure on Linux distributions derived from Fedora, enable the _Extra Packages for Enterprise Linux_ (EPEL) repository. Refer to for instructions.
### Note — This Method Is Not Destructive
This method is not destructive, so existing data on the media is not harmed. Nevertheless, it is always a good idea to back up important data before performing sensitive disk operations.
1. Install the liveusb-creator on your system with your graphical package manager, or the following command:
**su -c 'yum -y install liveusb-creator'**
1. Plug in your USB media.
1. Launch LiveUSB Creator, either from a menu or by entering **liveusb-creator** on the command line. Enter the root password for your system when LiveUSB Creator prompts you for it.
1. LiveUSB Creator can create live USB media either from an image file that you downloaded previously, as described in [Section 2.1.3, “Which Files Do I Download?”](#sn-which-files "2.1.3. Which Files Do I Download?"), or it can download an image file from the Internet. Either:
* click the Browse button under the Use existing LiveCD label, browse to the location where you previously downloaded a Fedora Live ISO file, and select that file.
* select a Fedora Live ISO file from the drop-down menu that LiveUSB Creator presents under the Download Fedora label. Note that image files are large and that it is probably impractical to use LiveUSB Creator to download an image file if you do not have a broadband connection to the Internet.
1. Click Create Live USB.
##### 3\.2.2.1.2. Making Fedora USB Media with livecd-tools {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-livecd-tools}
### Important — Enable Extra Packages for Enterprise Linux
To perform this procedure on Linux distributions derived from Fedora, enable the _Extra Packages for Enterprise Linux_ (EPEL) repository. Refer to for instructions.
### Note — This Method Is Not Destructive
This method is not destructive, so existing data on the media is not harmed. Nevertheless, it is always a good idea to back up important data before performing sensitive disk operations.
1. Install the livecd-tools package on your system with your graphical package manager, or the following command:
**su -c 'yum -y install livecd-tools'**
1. Plug in your USB flash drive.
1. Find the flash drive's device name. If the media has a volume name, use it to look up the device name in `/dev/disk/by-label`, or use the **findfs** command:
**findfs LABEL=_`MyLabel`_**
If the media does not have a volume name or you do not know it, you can also use the **dmesg** command shortly after connecting the media to your computer. After running the command, the device name (such as `sdb` or `sdc`) should appear in several lines towards the end of the output.
1. Use the **livecd-iso-to-disk** command to write the ISO image to the media:
**su -c 'livecd-iso-to-disk _`the_image.iso`_/dev/_`sdX1`_'**
Replace _`sdX1`_ with the device name for the partition on the USB media. Most flash drives and external hard disks use only one partition. If you have changed this behavior or have oddly partitioned media, you may need to consult other sources of help.
##### 3\.2.2.1.3. Making Fedora USB Media with dd {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd}
### Warning — These instructions could destroy data
When you perform this procedure any data on the USB flash drive is destroyed with no warning. Make sure that you specify the correct USB flash drive, and make sure that this flash drive does not contain any data that you want to keep.
### Note
The Fedora Project recommends using livecd-tools rather than dd for creating USB media whenever possible.
1. Plug in your USB flash drive.
1. Find the flash drive's device name. If the media has a volume name, use it to look up the device name in `/dev/disk/by-label`, or use the **findfs** command:
**findfs LABEL=_`MyLabel`_**
If the media does not have a volume name or you do not know it, you can also use the **dmesg** command shortly after connecting the media to your computer. After running the command, the device name (such as `sdb` or `sdc`) should appear in several lines towards the end of the output.
1. Use the **dd** command to transfer the boot ISO image to the USB device:
**su -c 'dd if=_`path/image_name`_.iso of=/dev/_`device`_ bs=_`block size`_'**
where _`path/image_name`_.iso is the boot ISO image file that you downloaded and ``_`device`_`` is the device name for the USB flash drive. Ensure you specify the device name (such as `sdc`), not the partition name (such as `sdc1`). The `bs` option specifies the block size; it can be omitted, but specifying it will speed up the process. For example:
**su -c 'dd if=~/Downloads/Fedora-Live-Desktop-x86_64-20-1.iso of=/dev/sdc bs=512k'**
#### 3\.2.2.2. Making Fedora USB Media in other Linux Distributions {#Making_USB_Media-UNIX_Linux-other}
To create Fedora USB media from a DVD or live image on a computer that uses a Linux distribution other than Fedora and those derived from Fedora, use one of the command-line procedures detailed in this section.
##### 3\.2.2.2.1. Making Fedora USB Media with livecd-tools {#Making_USB_Media-UNIX_Linux-other_livecd-tools}
### Note — This Method Is Not Destructive
This method is not destructive, so existing data on the media is not harmed. Nevertheless, it is always a good idea to back up important data before performing sensitive disk operations.
This method works only on Linux operating systems.
1. Download a DVD or live ISO image for Fedora as shown in [Section 2.1.3, “Which Files Do I Download?”](#sn-which-files "2.1.3. Which Files Do I Download?")
1. Plug in your USB flash drive.
1. Find the flash drive's device name. If the media has a volume name, use it to look up the device name in `/dev/disk/by-label`, or use the **findfs** command:
**findfs LABEL=_`MyLabel`_**
If the media does not have a volume name or you do not know it, you can also use the **dmesg** command shortly after connecting the media to your computer. After running the command, the device name (such as `sdb` or `sdc`) should appear in several lines towards the end of the output.
1. Many Linux distributions automatically _mount_ USB media devices when you connect the device to your computer. If this is the case, unmount the device. The specific method to do this varies widely between Linux distributions and desktops. Some common methods include:
* select File > Unmount if the operating system presents you with a window that displays the contents of the device.
* right-click on an icon of the device and click Unmount.
* click on an icon that represents ejecting the media — commonly, an upward-pointing triangle.
1. At a command line, type **su -** to become root, and enter the root password when your system prompts you.
1. Create a _mount point_ for the image that you downloaded. For example, to use `/tmp/livecd` as the mount point, type **mkdir /tmp/livecd** and press **Enter**.
1. Mount the image with the following command: **mount -o loop _`/path/to/image/file/imagefile.iso`_ _`/path/to/mount/point`_**, where _`/path/to/image/file`_ is the location of the image file that you downloaded, `imagefile.iso` is the image file, and _`/path/to/mount/point`_ is the mount point that you just created.
1. Change directory to the `LiveOS` directory of the image that you just mounted. mount point where you just mounted the Fedora image. For example, **cd /tmp/livecd/LiveOS**.
1. Run the following command: **./livecd-iso-to-disk _`/path/to/image/file/imagefile.iso`_ _`device`_**, where ``_`/path/to/image/file`_`` is the location of the image file that you downloaded, ``_`imagefile.iso`_`` is the image file, and ``_`device`_`` is the USB media device.
Example 3.1. Mounting a Fedora live image file and using livecd-iso-to-disk to create live USB media
You have downloaded a Fedora live image, `Fedora-Live-Desktop-x86_64-20-1.iso`, to a folder named `Downloads` in your home directory. You have a USB flash drive plugged into your computer, named `/dev/sdc`, with a partition named `/dev/sdc1`
Become root:
su -
Make a mount point for the image:
mkdir /mnt/livecd
Mount the image:
mount -o loop /home/_`Username`_/Downloads/Fedora-Live-Desktop-x86_64-20-1.iso /mnt/livecd
Change into the `LiveOS` directory of the live CD image:
cd /mnt/livecd/LiveOS
Run livecd-iso-to-disk to transfer the live image to the partition on your flash drive and make the flash drive bootable:
./livecd-iso-to-disk /home/_`Username`_/Downloads/Fedora-Live-Desktop-x86_64-20-1.iso /dev/sdc1
.|
|_Seek Support_ at [http://fedoraproject.org/wiki/Communicating\_and\_getting\_help](http://fedoraproject.org/wiki/Communicating_and_getting_help)|
|_Check online compatibility lists,_ such as and . The two hashes should be identical.
1. Ensure that an entry for the publicly available directory exists in the `/etc/exports` file on the network server so that the directory is available via NFS.
To export a directory read-only to a specific system, use:
**_`/publicly_available_directory`_ _`client.ip.address`_ (ro)**
To export a directory read-only to all systems, use:
**_`/publicly_available_directory`_ * (ro)**
1. On the network server, start the NFS daemon (use **systemctl start nfs**). If NFS is already running, reload the configuration file (use **systemctl reload nfs**).
1. Be sure to test the NFS share following the directions in the _Fedora System Administrators Guide_. Refer to your NFS documentation for details on starting and stopping the NFS server.
### Note
The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned discs). To use this test, type the following command at the `boot:` prompt:
**`linux rd.live.check`**
## 5\.2. Preparing for a Hard Drive Installation {#s1-steps-hd-installs-x86}
### Note — Not all file systems supported
Hard drive installations only work from ext2, ext3, ext4, or FAT file systems. You cannot use a hard drive formatted for any other file system as an installation source for Fedora.
To check the file system of a hard drive partition on a Windows operating system, use the Disk Management tool. To check the file system of a hard drive partition on a Linux operating system, use the fdisk tool.
### Cannot Install from LVM Partitions
You cannot use ISO files on partitions controlled by LVM (Logical Volume Management).
Use this option to install Fedora on systems without a DVD drive or network connection.
Hard drive installations use an _ISO image_ of the installation DVD. An ISO image is a file that contains an exact copy of the content of a DVD.
With these files present on a hard drive, you can choose Hard drive as the installation source when you boot the installation program (refer to [Section 8.1, “Installation Method”](#s1-installationmethod-x86 "8.1. Installation Method")).
Ensure that you have boot media available on CD, DVD, or a USB storage device such as a flash drive.
To prepare a hard drive as an installation source, follow these steps:
1. Obtain an ISO image of the Fedora installation DVD (refer to [Chapter 2, _Obtaining Fedora_](#ch-new-users "Chapter 2. Obtaining Fedora")). Alternatively, if you have the DVD on physical media, you can create an image of it with the following command on a Linux system:
**dd if=/dev/_`dvd`_ of=/_`path_to_image`_/_`name_of_image`_.iso**
where _`dvd`_ is your DVD drive device, _`name_of_image`_ is the name you give to the give to the resulting ISO image file, and _`path_to_image`_ is the path to the location on your system where the resulting ISO image will be stored.
1. Transfer the ISO image to the hard drive.
The ISO image must be located on a hard drive that is either internal to the computer on which you will install Fedora, or on a hard drive that is attached to that computer by USB.
1. Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run:
**$ sha256sum _`name_of_image`_.iso**
where _`name_of_image`_ is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a _hash_. Compare this hash to the hash displayed for this particular image on the GPG Keys page on the Fedora Project site at . The two hashes should be identical.
### Note
The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned discs). To use this test, type the following command at the `boot:` prompt:
**`linux rd.live.check`**
## Chapter 6. System Specifications List {#ch-ent-table}
The installation program automatically detects and installs your computer's hardware. Although you should make sure that your hardware meets the minimum requirements to install Fedora (refer to [Section 4.2, “Is Your Hardware Compatible?”](#sn-Is_Your_Hardware_Compatible-x86 "4.2. Is Your Hardware Compatible?")) you do not usually need to supply the installation program with any specific details about your system.
However, when performing certain types of installation, some specific details might be useful or even essential.
* If you plan to use a customized partition layout, record:
* The model numbers, sizes, types, and interfaces of the hard drives attached to the system. For example, Seagate ST3320613AS 320 GB on SATA0, Western Digital WD7500AAKS 750 GB on SATA1. This will allow you to identify specific hard drives during the partitioning process.
* If you are installing Fedora as an additional operating system on an existing system, record:
* The mount points of the existing partitions on the system. For example, `/boot` on `sda1`, `/` on `sda2`, and `/home` on `sdb1`. This will allow you to identify specific partitions during the partitioning process.
* Whether the hardware clock uses local time or UTC. In Linux systems, this information can be found in `/etc/adjtime`. Changing the hardware clock setting in [Section 9.5, “Date and time”](#s1-timezone-x86 "9.5. Date and time") may cause unexpected behavior in Fedora.
* If you plan to install from an image on a local hard drive:
* The hard drive and directory that holds the image.
* If you plan to install from a network location:
* The make and model numbers of the network adapters on your system. For example, Netgear GA311. This will allow you to identify adapters when manually configuring the network.
* IP, DHCP, and BOOTP addresses
* Netmask
* Gateway IP address
* One or more name server IP addresses (DNS)
If any of these networking requirements or terms are unfamiliar to you, contact your network administrator for assistance.
* If you plan to install from a network location:
* The location of the image on an FTP server, HTTP (web) server, or NFS server – see [Section 8.1.4, “Installing via FTP or HTTP”](#s1-begininstall-url-x86 "8.1.4. Installing via FTP or HTTP") and [Section 8.1.3, “Installing via NFS”](#s1-begininstall-nfs-x86 "8.1.3. Installing via NFS") for examples.
* If your computer is part of a domain:
* You should verify that the domain name will be supplied by the DHCP server. If not, you will need to input the domain name manually during installation.
## Chapter 7. Booting the Installer {#ch-Boot-x86}
### Important — UEFI for 32-bit x86 systems
Fedora 20 does not support UEFI booting for 32-bit x86 systems. Only BIOS booting is supported.
### Important — UEFI for AMD64 and Intel 64
Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI.
Fedora 20 supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 of the UEFI specification or later should boot and operate with Fedora 20, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from `_``**
For text mode installations, use:
**``linux text console=_``_``**
In the above command, _``_ should be the device you are using (such as ttyS0 or ttyS1). For example, **linux text console=ttyS0**.
Text mode installations using a serial terminal work best when the terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, Kermit '95 works well. Non-UTF-8 capable terminals works as long as only English is used during the installation process. An enhanced serial display can be used by passing the **utf8** command as a boot-time option to the installation program. For example:
**linux console=ttyS0 utf8**
#### 7\.1.3.1. Kernel Options {#s3-x86-starting-kernelopts}
Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a USB storage device enter:
**`linux updates`**
For text mode installations, use:
**`linux text updates`**
This command results in a prompt for the path to the device that contains updates for anaconda. It is not needed if you are performing a network installation and have already placed the updates image contents in **rhupdates/** on the server.
After entering any options, press **Enter** to boot using those options.
If you need to specify boot options to identify your hardware, please write them down. The boot options are needed during the boot loader configuration portion of the installation (refer to [Section 9.11.2, “x86, AMD64, and Intel 64 Boot Loader Installation”](#s1-x86-bootloader "9.11.2. x86, AMD64, and Intel 64 Boot Loader Installation") for more information).
For more information on kernel options refer to [Chapter 11, _Boot Options_](#ap-admin-options "Chapter 11. Boot Options").
## 7\.2. Booting from the Network using PXE {#sn-booting-from-pxe-x86}
To boot with PXE, you need a properly configured server, and a network interface in your computer that supports PXE. For information on how to configure a PXE server, refer to [Chapter 13, _Setting Up an Installation Server_](#ap-install-server "Chapter 13. Setting Up an Installation Server").
Configure the computer to boot from the network interface. This option is in the BIOS, and may be labeled `Network Boot` or `Boot Services`. Once you properly configure PXE booting, the computer can boot the Fedora installation system without any other media.
To boot a computer from a PXE server:
1. Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on.
1. Switch on the computer.
1. A menu screen appears. Press the number key that corresponds to the desired option.
If your PC does not boot from the netboot server, ensure that the BIOS is configured to boot first from the correct network interface. Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. Refer to your hardware documentation for more information.
### Note — Multiple NICs and PXE installation
Some servers with multiple network interfaces might not assign eth0 to the first network interface as the firmware interface knows it, which can cause the installer to try to use a different network interface from the one that was used by PXE. To change this behavior, use the following in `pxelinux.cfg/*` config files:
IPAPPEND 2
APPEND ksdevice=bootif
These configuration options above cause the installer to use the same network interface the firmware interface and PXE use. You can also use the following option:
ksdevice=link
This option causes the installer to use the first network device it finds that is linked to a network switch.
## Chapter 8. Configuring Installation Source {#ch-Installation_Phase_2-x86}
Before the graphical installation program starts, you may need to configure the installation source depending on the method you are using.
## 8\.1. Installation Method {#s1-installationmethod-x86}
If you are installing from DVD, additional configuration will not be required unless the DVD drive is not detected. If you booted the installation from minimal boot media, use a boot prompt to select an installation method.
### 8\.1.1. Installing from DVD {#s1-begininstall-cd-inst-x86}
To install Fedora from a DVD, place the DVD in your DVD drive and boot your system from the DVD. Even if you booted from alternative media, you can still install Fedora from DVD media.
The installation program then probes your system and attempts to identify your DVD drive. It starts by looking for an IDE (also known as an ATAPI) DVD drive.
### Note
To abort the installation process at this time, reboot your machine and then eject the boot media. You can safely cancel the installation at any point before you select Begin Installation on the Installation Summary Menu. Refer to [Section 9.15, “Begin installation”](#Begin_installation-x86 "9.15. Begin installation") for more information.
If your DVD drive is not detected, and it is a SCSI DVD, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most drivers detect your SCSI adapter automatically.
If you booted the installer from other media and wish to use a DVD as your installation source, use the following boot option:
**``linux repo=cdrom:_`device`_``**
If you later encounter problems with the installer, you should reboot and perform the media check by running the boot option **linux rd.live.check** before seeking support.
### 8\.1.2. Installing from a Hard Drive {#s1-begininstall-hd-x86}
To specify a partition from which to install Fedora, use the **linux repo=** boot option:
**``linux repo=hd:_`device`_``**
Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with `/dev/sd`. Each individual drive has its own letter, for example `/dev/sda`. Each partition on a drive is numbered, for example `/dev/sda1`.
Also specify the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information:
Table 8.1. Location of ISO images for different partition types
|Partition type|Volume|Original path to files|Directory to use|
|-|
|VFAT|D:\\|D:\\Downloads\\Fedora20|/Downloads/Fedora20|
|ext2, ext3, ext4|/home|/home/user1/Fedora20|/user1/Fedora20|
:@[:]//`
For example:
`http://install:fedora20pw@name.example.com/fedora/linux/releases/20/Fedora/x86_64/iso/`
After entering the **linux repo=** command, proceed with [Chapter 9, _Using the Fedora installer_](#ch-guimode-x86 "Chapter 9. Using the Fedora installer").
## Chapter 9. Using the Fedora installer {#ch-guimode-x86}
This chapter describes an installation using the graphical user interface of anaconda.
## 9\.1. The Text Mode Installation Program User Interface {#idp17933248}
### Important — Graphical installation recommended
We recommend that you install Fedora using the graphical interface. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection – see [Chapter 14, _Installing Through VNC_](#vncwhitepaperadded "Chapter 14. Installing Through VNC"). If anaconda detects that you are installing in text mode on a system where installation over a VNC connection might be possible, anaconda asks you to verify your decision to install in text mode even though your options during installation are limited.
If your system has a graphical display, but graphical installation fails, try booting with the **xdriver=vesa** option – refer to [Chapter 11, _Boot Options_](#ap-admin-options "Chapter 11. Boot Options")
### Important — Graphical Interface on the Installed System
Installing in text mode does not prevent you from using a graphical interface on your system once it is installed.
Apart from the graphical installer, anaconda also includes a text-based installer.
If one of the following situations occurs, the installation program uses text mode:
* The installation system fails to identify the display hardware on your computer
* You choose the text mode installation by entering the following command at the `boot:` prompt
**`linux text`**
While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined installation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include:
* configuring advanced storage methods such as LVM and RAID.
* customizing the partition layout
* customizing the bootloader layout
* selecting packages during installation
If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation. Refer to [Section 17.2, “Switching to a Graphical Login”](#sn-switching-to-gui-login "17.2. Switching to a Graphical Login") for instructions.
To configure options not available in text mode, consider using a boot option. For example, the **linux ip** option can be used to configure network settings. Refer to [Section 11.1, “Configuring the Installation System at the Boot Menu”](#sn-bootoptions-installer "11.1. Configuring the Installation System at the Boot Menu") for instructions. Alternatively, consider a kickstart installation. Refer to [Section 15.4, “Kickstart Options”](#s1-kickstart2-options "15.4. Kickstart Options") for available kickstart options.
### Note
Not every language supported in graphical installation mode is also supported in text mode. Specifically, languages written with a character set other than the Latin or Cyrillic alphabets are not available in text mode. If you choose a language written with a character set that is not supported in text mode, the installation program will present you with the English versions of the screens.
### 9\.1.1. Using the Keyboard to Navigate {#idm29012592}
Navigation through the installation dialogs is performed through a simple set of keystrokes. To move the cursor, use the **Left**, **Right**, **Up**, and **Down** arrow keys. Use **Tab**, and **Shift**-**Tab** to cycle forward or backward through each widget on the screen. Along the bottom, most screens display a summary of available cursor positioning keys.
To "press" a button, position the cursor over the button (using **Tab**, for example) and press **Space** or **Enter**. To select an item from a list of items, move the cursor to the item you wish to select and press **Enter**. To select an item with a checkbox, move the cursor to the checkbox and press **Space** to select an item. To deselect, press **Space** a second time.
Pressing **F12** accepts the current values and proceeds to the next dialog; it is equivalent to pressing the OK button.
### Warning
Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior).
## 9\.2. The Graphical Installation Program User Interface {#s1-guimode-interface-x86}
If you have used a _graphical user interface (GUI)_ before, you are already familiar with this process; use your mouse to navigate the screens, click buttons, or enter text fields.
You can also navigate through the installation using the keyboard. The **Tab** key allows you to move around the screen, the Up and Down arrow keys to scroll through lists, **+** and **-** keys expand and collapse lists, while **Space** and **Enter** selects or removes from selection a highlighted item. You can also use the **Alt**+**_`X`_** key command combination as a way of clicking on buttons or making other screen selections, where **_`X`_** is replaced with any underlined letter appearing within that screen.
### 9\.2.1. Screenshots during installation {#sect-adminoptions-screenshots}
Anaconda allows you to take screenshots during the installation process. At any time during installation, press **Shift**+**Print Screen** and anaconda will save a screenshot to `/root/anaconda-screenshots`.
If you are performing a Kickstart installation, use the `autostep --autoscreenshot` option to generate a screenshot of each step of the installation automatically. Refer to [Section 15.3, “Creating the Kickstart File”](#s1-kickstart2-file "15.3. Creating the Kickstart File") for details of configuring a Kickstart file.
### 9\.2.2. A Note about Virtual Consoles {#sn-guimode-virtual-consoles-x86}
The Fedora installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five _virtual consoles_, among which you can switch using a single keystroke combination.
A virtual console is a shell prompt in a non-graphical environment, accessed from the physical machine, not remotely. Multiple virtual consoles can be accessed simultaneously.
These virtual consoles can be helpful if you encounter a problem while installing Fedora. Messages displayed on the installation or system consoles can help pinpoint a problem. Refer to [Table 9.1, “Console, Keystrokes, and Contents”](#tb-guimode-console-x86 "Table 9.1. Console, Keystrokes, and Contents") for a listing of the virtual consoles, keystrokes used to switch to them, and their contents.
Generally, there is no reason to leave the default console (virtual console #6) for graphical installations unless you are attempting to diagnose installation problems.
Table 9.1. Console, Keystrokes, and Contents
|console|keystrokes|contents|
|-|
|1|**Ctrl**+**alt**+**f1**|standard output|
|2|**Ctrl**+**alt**+**f2**|shell prompt|
|3|**Ctrl**+**alt**+**f3**|installation log|
|4|**Ctrl**+**alt**+**f4**|storage log|
|5|**Ctrl**+**alt**+**f5**|external program log|
|6|**Ctrl**+**alt**+**f6**|localhost login|
|7|**Ctrl**+**alt**+**f6**|graphical display|
and _1\. iSCSI Names and Addresses_ in _RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery_ available from .
1. Use the drop-down menu to specify the type of authentication to use for iSCSI discovery:
Figure 9.22. iSCSI discovery authentication
![iSCSI discovery authentication][23]
#### 9\.11.2.1. Alternative Boot Loaders {#s2-x86-bootloader-alt}
GRUB is the default bootloader for Fedora, but is not the only choice. A variety of open-source and proprietary alternatives to GRUB are available to load Fedora, including LILO, SYSLINUX, and Acronis Disk Director Suite.
### Important
The Fedora Project does not support third-party boot loaders.
## 9\.12. Encrypt Partitions {#encrypt-x86}
If you selected the Encrypt my data option, when you click to proceed to the next screen the installer will prompt you for a passphrase with which to encrypt the partitions on the system.
Partitions are encrypted using the _Linux Unified Key Setup_ — refer to [Appendix C, _Disk Encryption_](#Disk_Encryption_Guide "Appendix C. Disk Encryption") for more information.
Figure 9.28. Enter passphrase for encrypted partition
![Enter passphrase for encrypted partition][29]
[[3] ](#idp44334192) The **fsck** application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
[[4] ](#idm21864208) A root password is the administrative password for your Fedora system. You should only log in as root when needed for system maintenance. The root account does not operate within the restrictions placed on normal user accounts, so changes made as root can have implications for your entire system.
## Chapter 10. Troubleshooting Installation on an Intel or AMD System {#ch-trouble-x86}
This section discusses some common installation problems and their solutions.
For debugging purposes, anaconda logs installation actions into files in the `/tmp` directory. These files include:
`/tmp/anaconda.log`
: general anaconda messages
`/tmp/program.log`
: all external programs run by anaconda
`/tmp/storage.log`
: extensive storage module information
`/tmp/yum.log`
: yum package installation messages
`/tmp/syslog`
: hardware-related system messages
If the installation fails, the messages from these files are consolidated into ``/tmp/anaconda-tb-_`identifier`_``, where _`identifier`_ is a random string.
All of the files above reside in the installer's ramdisk and are thus volatile. To make a permanent copy, copy those files to another system on the network using **scp** on the installation image (not the other way round).
## 10\.1. You are unable to boot Fedora {#idp2790624}
### 10\.1.1. Are You Unable to Boot With Your RAID Card? {#idp69728496}
If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently.
Some BIOSes do not support booting from RAID cards. At the end of an installation, a text-based screen showing the boot loader prompt (for example, `GRUB:` ) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
Whether you choose automatic or manual partitioning, you must install your `/boot` partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
You must also install your preferred boot loader (GRUB or LILO) on the MBR of a drive that is outside of the RAID array. This should be the same drive that hosts the `/boot/` partition.
Once these changes have been made, you should be able to finish your installation and boot the system properly.
### 10\.1.2. Is Your System Displaying Signal 11 Errors? {#idp2122272}
A signal 11 error, commonly known as a _segmentation fault_, means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
If you receive a fatal signal 11 error during your installation, it is probably due to a hardware error in memory on your system's bus. Like other operating systems, Fedora places its own demands on your system's hardware. Some of this hardware may not be able to meet those demands, even if they work properly under another OS.
Ensure that you have the latest installation updates and images. Review the online errata to see if newer versions are available. If the latest images still fail, it may be due to a problem with your hardware. Commonly, these errors are in your memory or CPU-cache. A possible solution for this error is turning off the CPU-cache in the BIOS, if your system supports this. You could also try to swap your memory around in the motherboard slots to check if the problem is either slot or memory related.
Another option is to perform a media check on your installation DVD. Anaconda, the installation program, has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. The Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the `boot:` or `yaboot:` prompt:
**`linux rd.live.check`**
For more information concerning signal 11 errors, refer to:
. After entering your credentials, click OK.
Figure 10.4. Configure Bugzilla
![Configure Bugzilla][47]
for help with partition numbering.
1. In the GRUB configuration file, locate the first `linux` and `initrd` lines and paste them as individual commands. For example:
**linux /vmlinuz-3.3.0-1.fc17.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_LVM_LV=VolGroup/lv_root rd_LVM_LV=VolGroup/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet**
**initrd /initramfs-3.3.0-1.fc17.x86_64.img**
1. Run the **boot** command.
1. Once Fedora has loaded, refresh the GRUB configuration file to make the changes persistent:
**grub2-mkconfig --output=/boot/grub2/grub.cfg**
### 10\.4.3. Booting into a Graphical Environment {#Trouble_After_Booting-GUI}
If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start the X Window System graphical interface using the command **startx**.
Once you enter this command and press **Enter**, the graphical desktop environment is displayed.
Note, however, that this is just a one-time fix and does not change the log in process for future log ins.
To set up your system so that you can log in at a graphical login screen, you must set the graphical systemd boot target as the default target. The system boots to the target described in the `default.target` file, which is a symbolic link (or _symlink_) to a specific target file.
Open a shell prompt. If you are in your user account, become root by typing the **su** command.
Now, type the following command to create a new symlink to the graphical target, which we will call `default2`:
** ln -s /lib/systemd/system/graphical.target /etc/systemd/system/default2.target **
Then, overwrite the current `default.target` symlink with the new symlink:
** mv /etc/systemd/system/default2.target /etc/systemd/system/default.target **
You will be prompted to confirm whether the file should be overwritten. Press **y** followed by **Enter**.
The next time you log in after rebooting your system, you are presented with a graphical login prompt.
### 10\.4.4. Problems with the X Window System (GUI) {#idp59289408}
If you are having trouble getting X (the X Window System) to start, you may not have installed it during your installation.
If you want X, you can either install the packages from the Fedora installation media or perform an upgrade.
If you elect to upgrade, select the X Window System packages, and choose GNOME, KDE, or both, during the upgrade package selection process.
Refer to [Section 17.2, “Switching to a Graphical Login”](#sn-switching-to-gui-login "17.2. Switching to a Graphical Login") for more detail on installing a desktop environment.
### 10\.4.5. Problems with the X Server Crashing and Non-Root Users {#idm15222912}
If you are having trouble with the X server crashing when anyone logs in, you may have a full file system (or, a lack of available hard drive space).
To verify that this is the problem you are experiencing, run the following command:
df -h
The **df** command should help you diagnose which partition is full. For additional information about **df** and an explanation of the options available (such as the `-h` option used in this example), refer to the **df** man page by typing **man df** at a shell prompt.
A key indicator is 100% full or a percentage above 90% or 95% on a partition. The `/home/` and `/tmp/` partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
### 10\.4.6. Problems When You Try to Log In {#idp45851744}
If you did not create a user account in the Configuration Menu and Progress Screen, switch to a console by pressing **Ctrl**+**Alt**+**F2**, log in as root and use the password you assigned to root.
If you cannot remember your root password, boot your system as **linux single**.
If you are using an x86-based system and GRUB is your installed boot loader, type **e** for edit when the GRUB boot screen has loaded. You are presented with a list of items in the configuration file for the boot label you have selected.
Choose the line that starts with `kernel` and type **e** to edit this boot entry.
At the end of the `kernel` line, add:
**`single`**
Press **Enter** to exit edit mode.
Once the boot loader screen has returned, type **b** to boot the system.
Once you have booted into single user mode and have access to the `#` prompt, you must type **passwd root**, which allows you to enter a new password for root. At this point you can type **shutdown -r now** to reboot the system with the new root password.
If you cannot remember your user account password, you must become root. To become root, type **su -** and enter your root password when prompted. Then, type **passwd <username>**. This allows you to enter a new password for the specified user account.
If the graphical login screen does not appear, check your hardware for compatibility issues.
### 10\.4.7. Is Your RAM Not Being Recognized? {#s2-trouble-ram}
### Only showing 3.5GB?
If you have 4GB or more memory installed, but Fedora only shows around 3.5GB or 3.7GB, you have probably installed a 32bit version of Fedora on a 64bit kernel. For modern systems, the 64bit version of Fedora is recommended. Refer to [Section 2.1.2, “Which Architecture Is My Computer?”](#sn-which-arch "2.1.2. Which Architecture Is My Computer?") for more details.
Sometimes, the kernel does not recognize all of your memory (RAM). The following procedure will allow you to confirm this and then adjust the kernel if necessary.
1. Run the **cat /proc/meminfo** command and verify that the displayed quantity is the same as the known amount of RAM in your system. If they are not equal, you can first make a temporary change to confirm whether editing the kernel will be effective.
1. Reboot, and once you have loaded the GRUB boot screen, type **e** for edit.
1. You are presented with a list of items in the configuration file for the boot label you have selected. Move to the line that starts with `linux` or `linuxefi`.
1. At the end of the `kernel` line, add
**``mem=_`xx`_M``**
where _`xx`_ equals the amount of RAM in your system in megabytes, then press **F10** to boot the system.
1. Run **cat /proc/meminfo** again. If the known amount of RAM in your system is now displayed, add the following to the `GRUB_CMDLINE_LINUX` line in `/etc/default/grub`, inside the quotes, to make the change permanent:
**``mem=_`xx`_M``**
Replace _`xx`_ with the amount of RAM you have in megabytes.
1. To update the `grub.cfg` file so that the change will take effect, run the following command with root privileges.
# for BIOS systems
**grub2-mkconfig --output=/boot/grub2/grub.cfg**
# for UEFI systems
**grub2-mkconfig --output=/boot/efi/EFI/fedora/grub.cfg**
The resulting grub menu entry might look like this:
menuentry 'Fedora (3.16.0-0.rc2.git2.1.fc21.x86_64) 21 (Rawhide)' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2 b34a57d9-03d7-415f-94f6-91689404d951
else
search --no-floppy --fs-uuid --set=root b34a57d9-03d7-415f-94f6-91689404d951
fi
linuxefi /vmlinuz-3.16.0-0.rc2.git2.1.fc21.x86_64 root=UUID=ece86abc-6419-4f29-84b6-1b810128f98d ro rootflags=subvol=root vconsole.font=latarcyrheb-sun16 vconsole.keymap=us LANG=en_US.UTF-8 mem=8192M
initrdefi /initramfs-3.16.0-0.rc2.git2.1.fc21.x86_64.img
}
### 10\.4.8. Your Printer Does Not Work {#idm13758800}
If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the Printer Configuration Tool.
Type the **system-config-printer** command at a shell prompt to launch the Printer Configuration Tool. If you are not root, it prompts you for the root password to continue.
### 10\.4.9. Apache HTTP Server or Sendmail stops responding during startup {#idp11141664}
If Apache HTTP Server (httpd) or Sendmail stops responding during startup, make sure the following line is in the `/etc/hosts` file:
127.0.0.1 localhost.localdomain localhost
# Part II. Advanced installation options {#pt-Advanced_installation_options}
This part of the _Fedora Installation Guide_ covers more advanced or uncommon methods of installing Fedora, including:
* boot options.
* installing without media.
* installing through VNC.
* using kickstart to automate the installation process.
## Chapter 11. Boot Options {#ap-admin-options}
The Fedora installation system includes a range of functions and options for administrators. To use boot options, append them to the boot command line. To access the command line on a system that displays a graphical boot screen, press the **Tab** key while one of the boot options on the screen is highlighted, or press the **Esc** key at any point in the boot menu. Multiple options added to the boot line need to be separated by a single space.
Throughout this chapter, some options are presented ending an "equals" sign ('`=`'). These options require a value to be specified. For example, the `inst.vncpassword=` option must also contain a password — for example, `inst.vncpassword=testpasswd`. Other options are presented without the `=` sign; these options are booleans. This means that you either use them without specifying a value, or you can append either `=1` or `=0` to enable or disable them, respectively. For example, the `rd.live.check` option is the same as `rd.live.check=1`, and using `rd.live.check=0` is exactly the same as not using the option at all.
### Note
The Fedora installation can either boot with _rescue mode_, or load the installation system. For more information on rescue mode, see [Section 11.3.3, “Booting Your Computer in Rescue Mode”](#sect-boot-options-rescue "11.3.3. Booting Your Computer in Rescue Mode").
## 11\.1. Configuring the Installation System at the Boot Menu {#sn-bootoptions-installer}
The `boot:` prompt always expects the first option to specify the image file to be loaded. When using custom boot options with the Anaconda installer, the `linux` option will come first in most cases. A valid command in the boot prompt will therefore almost always look like the following:
`boot:```linux _`options`_``
This only applies to the actual boot prompt, which is accessed by pressing the **Esc** key in the boot menu. If you are only modifying an existing set of options (accessed by highliting a choice in the boot menu and pressing the **Tab** key), the `linux` option is not displayed, but it is implied. A valid set of boot options will then be:
`>```_`options`_``
In addition to the options described in this chapter, the boot prompt also accepts valid dracut kernel options. A list of these options is available as the `dracut.cmdline(7)` man page.
### Note
Boot options specific to the installer always start with `inst.` in this guide. Currently, this prefix is optional, for example, `inst.resolution=` will work exactly the same as `resolution=`. However, it is expected that Anaconda will require the `inst.` prefix in future releases.
Specifying the Installation Source
`inst.repo=`
: Specifies the installation source — that is, a location where the installer can find the images and packages it needs. For example:
inst.repo=cdrom
The target must be either:
* an installable tree, which is a directory structure containing the installer's images, packages and repodata as well as a valid `.treeinfo` file
* a mounted DVD (either a physical DVD in a DVD drive or a loopback-mounted image)
This option allows for the configuration of different installation methods using different formats. The syntax is described in the table below.
Table 11.1. Installation Sources
|Installation source|Option format|
|-|
|Any CD/DVD drive|`inst.repo=cdrom`|
|Specific CD/DVD drive|``inst.repo=cdrom:_`device`_``|
|Hard Drive|``inst.repo=hd:_`device`_/_`path`_``|
|HTTP Server|``inst.repo=http://_`host`_/_`path`_``|
|HTTPS Server|``inst.repo=https://_`host`_/_`path`_``|
|FTP Server|``inst.repo=ftp://_`username`_:_`password`_@_`host`_/_`path`_``|
|NFS Server|``inst.repo=nfs:[_`options`_:]_`server`_:/_`path`_`` [[a]](#ftn.idm21992880)|
|[[a] ](#idm21992880) This option uses NFS protocol version 3 by default. To use a different version, add ``+nfsvers=_`X`_`` to _`options`_.|
.
To halt the tests and reboot your computer, enter **Esc** at any time.
### Note
Memtest86+ only works on BIOS installations and is not available on UEFI systems.
### 11\.3.2. Verifying Boot Media {#sect-boot-options-mediacheck}
You can test the integrity of an ISO-based installation source before using it to install Fedora. These sources include DVD, and ISO images stored on a hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation.
To test the checksum integrity of an ISO image, append the `rd.live.check` to the boot loader command line. Note that this option is used automatically if you select the default installation option from the boot menu (Test this media & install Fedora).
### 11\.3.3. Booting Your Computer in Rescue Mode {#sect-boot-options-rescue}
You may boot a command-line Linux system from an installation disc without actually installing Fedora on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on the system.
To load the rescue system with the installation disc, choose Rescue a Fedora system from the Troubleshooting submenu in the boot menu, or use the `inst.rescue` boot option.
Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer.
By default, rescue mode attaches an existing operating system to the rescue system under the directory `/mnt/sysimage/`.
## Chapter 12. Installing Without Media {#ap-medialess-install}
### Linux Required
This procedure assumes you are already using Fedora or another relatively modern Linux distribution, and the GRUB boot loader. It also assumes you are a somewhat experienced Linux user.
This section discusses how to install Fedora on your system without making any additional physical media. Instead, you can use your existing GRUB boot loader to start the installation program.
## 12\.1. Retrieving Boot Files {#sn-medialess-getting-files}
To perform an installation without media or a PXE server, your system must have two files stored locally, a kernel and an initial RAM disk.
Copy the `vmlinuz` and `initrd.img` files from a Fedora DVD (or DVD image) to the `/boot/` directory, renaming them to `vmlinuz-install` and `initrd.img-install`. You must have `root` privileges to write files into the `/boot/` directory.
## 12\.2. Editing the GRUB Configuration {#sn-medialess-editing-grub-conf}
The GRUB boot loader uses the configuration files `/etc/default/grub` and the scripts in `etc/grub.d/`. To configure GRUB to boot from the new files, add a boot stanza to `/etc/grub.d/40_custom` that refers to them.
A minimal boot stanza looks like the following listing:
menuentry "Fedora Linux" {
set root=(hd0,1)
linux /vmlinuz-install
initrd /initrd.img-install
}
You will also need to specify the location of the second stage installer image by adding an option to the end of the `linux` line of the boot stanza. For example:
linux /vmlinuz-install stage2=http://my.internal.server/17/x86_64/os/
If the second stage image and the package repositories you will be downloading from are on the same server, use the **repo=** option instead.
You may wish to add additional options to the end of the `linux` line, which will set preliminary options in Anaconda that the user normally sets interactively. For a list of available installer boot options, refer to [Chapter 11, _Boot Options_](#ap-admin-options "Chapter 11. Boot Options").
The following options are generally useful for medialess installations:
* `ip=`
* `repo=`
* `lang=`
* `keymap=`
* `ksdevice=` (if installation requires an interface other than eth0)
* `vnc` and `vncpassword=` for a remote installation
When you are finished, run the following command with root privileges to refresh the `grub.cfg` file:
**grub2-mkconfig --output=/boot/grub2/grub.cfg**
Next, open `grub.cfg` to view the updated configuration. Locate your new menu entry stanza and determine its place in the stanza order.
Finally, change the `GRUB_DEFAULT` option in `/etc/default/grub` to point to the new stanza you added. 0 will refer to the first stanza, 1 to the second, and so on. For example:
GRUB_DEFAULT=0
Alternatively, specify the menu entry title. This is particularly useful if you have a number of menu entries across the various script files.
GRUB_DEFAULT="Fedora Linux"
## 12\.3. Booting to Installation {#sn-medialess-booting}
Reboot the system. GRUB boots the installation kernel and RAM disk, including any options you set. You may now refer to the appropriate chapter in this guide for the next step. If you chose to install remotely using VNC, refer to [Enabling Remote Access](#list-boot-options-vnc "Enabling Remote Access") for assistance in connecting to the remote system.
## Chapter 13. Setting Up an Installation Server {#ap-install-server}
### Experience Required
This appendix is intended for users with previous Linux experience. If you are a new user, you may want to install using minimal boot media or the distribution DVD instead.
### Warning
The instructions in this appendix configures an automated install server. The default configuration includes destruction of all existing data on all disks for hosts that install using this method. This is often different from other network install server configurations which may provide for an interactive installation experience.
Fedora allows for installation over a network using the NFS, FTP, or HTTP protocols. A network installation can be started from a boot CD-ROM, a bootable flash memory drive, or by using the `repo=` boot option with the Fedora DVD. Alternatively, if the system to be installed contains a network interface card (NIC) with Pre-Execution Environment (PXE) support, it can be configured to boot from files on another networked system rather than local media such as a DVD.
For a PXE network installation, the client's NIC with PXE support sends out a broadcast request for DHCP information. The DHCP server provides the client with an IP address, other network information such as name server, the IP address or hostname of the **tftp** server (which provides the files necessary to start the installation program), and the location of the files on the **tftp** server. This is possible because of PXELINUX, which is part of the `syslinux` package.
In the past, administrators needed to perform a great deal of manual configuration to produce an installation server. However, if you have a server running Fedora or a similar operating system on your local network, you can use cobbler to perform these tasks. To configure a PXE server manually, see [Section 13.5, “Manually configure a PXE server”](#sn-pxe-server-manual "13.5. Manually configure a PXE server").
To perform the tasks in this section, switch to the `root` account with the command **su -**. As an alternative, you can run a command with the `-c` option, using the form **su -c '_`command`_'**.
## 13\.1. Setting Up cobbler {#sn-install-cobbler}
To install cobbler use the following command:
**yum -y install cobbler**
The **cobbler** command can check its own settings for validity and report the results. Run the following command to check the settings:
**cobbler check**
Verify SELinux is configured for cobbler:
**setsebool -P httpd_can_network_connect_cobbler 1**
Other SELinux booleans may apply, and can be listed with:
**getsebool -a|grep cobbler**
Change the settings in the `/etc/cobbler/settings` file to reflect the IP address information for the server. You must change at least the `server` and `next_server` options, although these options may point to the same IP address.
If you are not already running a DHCP server, you should also change the `manage_dhcp` option to **`1`**. If you are running a DHCP server, configure it according to the instructions found in the syslinux package documentation. For more information, refer to your local files `/usr/share/doc/syslinux/syslinux.doc` and `/usr/share/doc/syslinux/pxelinux.doc`.
## 13\.2. Setting Up the Distribution {#sn-cobbler-setup-distro}
To set up a distribution from a full Fedora DVD or ISO image, use this procedure.
### Network Locations
To create a local mirror from an existing network source, skip this section and refer instead to [Section 13.3, “Mirroring a Network Location”](#sn-cobbler-mirror "13.3. Mirroring a Network Location").
1. If you are using a DVD disc or ISO image, Create a directory mount point:
**mkdir /mnt/dvd**
To mount a physical DVD disc, use the following command:
**mount -o context=system_u:object_r:httpd_sys_content_t:s0 /dev/dvd /mnt/dvd**
To mount a DVD ISO image, use the following command:
**mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd**
### If SELinux enabled, use the default label
If SELinux is enabled, use the default **iso9660\_t** label instead of **httpd\_sys\_content\_t**.
1. To support NFS installation, create a file `/etc/exports` and add the following line to it:
/mnt/dvd *(ro,async)
Start the NFS server using the following commands:
**systemctl start rpcbind**
**systemctl start nfs**
1. To support HTTP installation, use **yum** to install the Apache web server if it is not already installed:
**yum -y install httpd**
Make a link to the mounted disc in the Apache public content area:
**ln -s /mnt/dvd /var/www/html/_`distro`_**
## 13\.3. Mirroring a Network Location {#sn-cobbler-mirror}
If you do not have discs or ISO images for a distribution, you can use **cobbler** to create an installation server. The **cobbler** command can fetch the distribution over the network as part of the import process.
Locate the distribution on the network. The location may be on the local network or reached at a remote site via FTP, HTTP, or rsync protocols.
## 13\.4. Importing the Distribution {#sn-cobbler-import}
To offer a distribution through more than one installation method, perform additional **cobbler import** tasks using a different name for each method. For best results, use the installation method as part of the name, so it appears in the client's boot menu.
1. To import the DVD disc or ISO distribution into **cobbler**, run this command:
**cobbler import --path=/mnt/dvd --name=_`distro_name`_**
For _`distro_name`_, substitute a meaningful name for the distribution.
To import a local or remote network distribution into **cobbler**, run this command. Replace _`network_URI`_ with the URI you found in [Section 13.3, “Mirroring a Network Location”](#sn-cobbler-mirror "13.3. Mirroring a Network Location"), and _`distro_name`_ as above:
**cobbler import --path=_`network_URI`_ --name=_`distro_name`_**
### Importing a Source
When **cobbler** imports a distribution with the commands above, it copies all the files to the server's local storage, which may take some time.
If you do not want to make local copies of the distribution because clients can already reach its location, use the `--available-as` option.
**cobbler import --path=/mnt/dvd --name=_`distro_name`_ --available-as=_`network_URI`_**
**cobbler import --path=_`network_URI`_ --name=_`distro_name`_ --available-as=_`network_URI`_**
For _`nework_URI`_, substitute the appropriate network location of the distribution. This URI indicates how the server makes the distribution available to its clients. The examples above assume that your **cobbler** server reaches the mirror location at the same URI as the clients. If not, substitute an appropriate URI for the `--path` option. The following examples are URI locations that work if you have been following the procedures in this section, and your server's IP address is `192.168.1.1`:
* nfs://_`192.168.1.1`_:/mnt/dvd
* http://_`192.168.1.1`_:/distro
If necessary, replace _`192.168.1.1`_ with the IP address for your **cobbler** server.
1. Run the command **cobbler sync** to apply the changes. To check that your **cobbler** server is listening on the correct ports, use the **netstat -lp** command.
### Firewall Considerations
Depending on your server's configuration, you may need to use the **system-config-securitylevel** command to permit access to some or all of these network services:
* 67 or bootps, for the DHCP/BOOTP server
* 69 or tftp, for providing the PXE loader
* 80 or http, if the **cobbler** server is to provide HTTP installation service
* 20 and 21 or ftp, if the **cobbler** server is to provide FTP installation service
* 111 or sunrpc, if the **cobbler** server is to provide NFS installation service
## 13\.5. Manually configure a PXE server {#sn-pxe-server-manual}
The following steps must be performed to prepare for a PXE installation:
1. Configure the network (NFS, FTP, HTTP) server to export the installation tree.
1. Configure the files on the **tftp** server necessary for PXE booting.
1. Configure which hosts are allowed to boot from the PXE configuration.
1. Start the **tftp** service.
1. Configure DHCP.
1. Boot the client, and start the installation.
### 13\.5.1. Setting up the Network Server {#s1-netboot-netserver}
First, configure an NFS, FTP, or HTTP server to export the entire installation tree for the version and variant of Fedora to be installed. Refer to [Section 5.1, “Preparing for a Network Installation”](#s1-steps-network-installs-x86 "5.1. Preparing for a Network Installation") for detailed instructions.
### 13\.5.2. PXE Boot Configuration {#s1-netboot-pxe-config}
The next step is to copy the files necessary to start the installation to the **tftp** server so they can be found when the client requests them. The **tftp** server is usually the same server as the network server exporting the installation tree.
BIOS and EFI configuration differs for this procedure.
#### 13\.5.2.1. Configuring for BIOS {#s1-netboot-pxe-config-bios}
1. If tftp-server is not yet installed, run **yum install tftp-server**.
1. In the tftp-server config file at `/etc/xinet.d/tftp`, change the _`disabled`_ parameter from `yes` to `no`.
1. Start the xinetd service, and enable it to persist across reboots:
**systemctl start xinetd**
**systemctl enable xinetd**
**systemctl status xinetd**
1. Configure your DHCP server to use the boot images packaged with SYSLINUX. (If you do not have a DHCP server installed, refer to the _DHCP Servers_ chapter in the _Fedora System Administrators Guide_.)
A sample configuration in `/etc/dhcp/dhcpd.conf` might look like:
option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.254;
range 10.0.0.2 10.0.0.253;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 10.0.0.1;
if option arch = 00:06 {
filename "pxelinux/bootia32.efi";
} else if option arch = 00:07 {
filename "pxelinux/bootx64.efi";
} else {
filename "pxelinux/pxelinux.0";
}
}
host example-ia32 {
hardware ethernet XX:YY:ZZ:11:22:33;
fixed-address 10.0.0.2;
}
}
1. You now need the `pxelinux.0` file from the SYSLINUX package installed with Fedora. Create a `pxelinux` directory within `tftpboot` and copy `pxelinux.0` and `vesamenu.c32`into it:
**mkdir /var/lib/tftpboot/pxelinux**
**cp /usr/share/syslinux/{pxelinux.0, vesamenu.c32} /var/lib/tftpboot/pxelinux**
1. Create a `pxelinux.cfg` directory within `pxelinux`:
**mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg**
1. Add a config file to this directory. The file should either be named `default` or named after the IP address. For example, if your machine's IP address is 10.0.0.1, the filename would be `0A000001`.
A sample config file at `/var/lib/tftpboot/pxelinux/pxelinux.cfg/default` might look like:
default vesamenu.c32
prompt 1
timeout 600
display boot.msg
label linux
menu label ^Install or upgrade an existing system
menu default
kernel vmlinuz
append initrd=initrd.img repo=http://dl.fedoraproject.org/pub/fedora/linux/releases
/20/Fedora/x86_64/os/
label vesa
menu label Install system with ^basic video driver
kernel vmlinuz
append initrd=initrd.img xdriver=vesa nomodeset repo=http://dl.fedoraproject.org
/pub/fedora/linux/releases/20/Fedora/x86_64/os/
label rescue
menu label ^Rescue installed system
kernel vmlinuz
append initrd=initrd.img root=live:http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/LiveOS/squashfs.img rescue
label local
menu label Boot from ^local drive
localboot 0xffff
label memtest86
menu label ^Memory test
kernel memtest
append -
If both the stage 2 installer image and the package repositories you intend to download from are on the same server, use the **repo=** boot option. If they are on separate servers, use **stage2=** instead.
For instructions on how to specify the installation source, refer to [Chapter 8, _Configuring Installation Source_](#ch-Installation_Phase_2-x86 "Chapter 8. Configuring Installation Source")
1. Copy the boot images into your **tftp** root directory:
** cp /_`path/to`_/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/**
1. Reboot the system, and select the network device as your boot device when prompted.
#### 13\.5.2.2. Configuring for EFI {#s1-netboot-pxe-config-efi}
1. If tftp-server is not yet installed, run **yum install tftp-server**.
1. In the tftp-server config file at `/etc/xinet.d/tftp`, change the _`disabled`_ parameter from `yes` to `no`.
1. Create a directory path within `tftpboot` for the EFI boot images, and then copy them from your installation media:
**mkdir /var/lib/tftpboot/pxelinux**
**mkdir /var/lib/tftpboot/pxelinux/bootx64.efi**
**cp _`/path/to/image/`_os/EFI/BOOT/grubx64.efi /var/lib/tftpboot/pxelinux/**
1. Start the xinetd service, and enable it to persist across reboots
**systemctl start xinetd**
**systemctl enable xinetd**
**systemctl status xinetd**
1. Configure your DHCP server to use the EFI boot images packaged with GRUB. (If you do not have a DHCP server installed, refer to the _DHCP Servers_ chapter in the _Fedora System Administrators Guide_.)
A sample configuration in `/etc/dhcp/dhcpd.conf` might look like:
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.254;
range 10.0.0.2 10.0.0.253;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 10.0.0.1;
if option arch = 00:06 {
filename "pxelinux/bootia32.efi";
} else if option arch = 00:07 {
filename "pxelinux/bootx64.efi";
} else {
filename "pxelinux/pxelinux.0";
}
}
host example-ia32 {
hardware ethernet XX:YY:ZZ:11:22:33;
fixed-address 10.0.0.2;
}
}
Configuring a DHCP server for IPv6 differs slightly. Crucially, the `filename` option must be replaced with a `bootfile-url` string. Both identify the boot file that the PXE **tftp** process should download, but each is specific to the version of the IP protocol being used. `bootfile-url` specifies an IPv6 network location for the boot file.
A sample configuration in `/etc/dhcp/dhcpd6.conf` might look like:
default-lease-time 2592000;
preferred-lifetime 604800;
option dhcp-renewal-time 3600;
option dhcp-rebinding-time 7200;
option dhcp6.name-servers 3ffe:501:ffff:100:200:ff:fe00:3f3e;
option dhcp6.domain-search "test.example.com","example.com";
option dhcp6.info-refresh-time 21600;
dhcpv6-lease-file-name "/var/lib/dhcpd/dhcpd6.leases";
subnet6 3ffe:501:ffff:100::/64 {
range6 3ffe:501:ffff:100::10 3ffe:501:ffff:100::;
range6 3ffe:501:ffff:100:: temporary;
prefix6 3ffe:501:ffff:100:: 3ffe:501:ffff:111:: /64;
option dhcp6.bootfile-url "tftp://[3ffe:501:ffff:100::1]/grubx64.efi";
option dhcp6.name-servers 3ffe:501:ffff:100::1;
}
In a Secure Boot environment, the configuration file must specify that the shim utility be downloaded rather than the GRUB image. No other file can be downloaded via **tftp** in Secure Boot mode. shim is specified using the `filename` option in IPv4 configurations and the `bootfile-url` option in IPv6 configurations.
Once the shim utility is downloaded and validated, it will automatically download the GRUB image. This image must be named either `grub.efi` or `grubx64.efi` and be available at the same location as shim and be accessible by **tftp**.
The shim-signed package is available in the Fedora yum repository. For more information on Secure Boot, refer to the _Fedora UEFI Secure Boot Guide_.
1. Create a `pxelinux.cfg` directory within `pxelinux`:
**mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg**
1. Add a config file to this directory. The file should either be named `efidefault` or named after the IP address. For example, if your machine's IP address is 10.0.0.1, the filename would be `0A000001`.
A sample config file at `/var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault` might look like:
default=0
timeout=1
hiddenmenu
title Fedora
root (nd)
kernel vmlinuz
initrd initrd.img inst.repo=nfs:10.0.0.1:/path/to/tree
For instructions on how to specify the installation source, refer to [Chapter 8, _Configuring Installation Source_](#ch-Installation_Phase_2-x86 "Chapter 8. Configuring Installation Source")
1. Copy the boot images into your **tftp** root directory:
** cp /_`path/to/image/`_os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/**
1. Reboot the system, and select the network device as your boot device when prompted.
### 13\.5.3. Starting the **tftp** Server {#idp18359696}
On the DHCP server, verify that the `tftp-server` package is installed with the command **rpm -q tftp-server**.
**tftp** is an xinetd-based service. Configure xinetd to process tftp requests by editing `/etc/xinetd.d/tftp` so that `disable = no`.
Start the **tftp** service with the following commands:
**systemctl start xinetd.service**
**systemctl enable xinetd.service**
These commands configure the **tftp** and **xinetd** services to immediately turn on and also configure them to start at boot.
### 13\.5.4. Adding a Custom Boot Message {#s2-netboot-custom-msg}
Optionally, modify `/tftpboot/linux-install/msgs/boot.msg` to use a custom boot message.
### 13\.5.5. Performing the PXE Installation {#netboot-performing}
For instructions on how to configure the network interface card with PXE support to boot from the network, consult the documentation for the NIC. It varies slightly per card.
If your NIC does not support PXE booting, you can still PXE boot your system by using the iPXE bootloader. The Fedora Project does not distribute iPXE — refer to the project website at
* TigerVNC:
* Anaconda boot options:
* Kickstart documentation:
## Chapter 15. Kickstart Installations {#ch-kickstart2}
## 15\.1. What are Kickstart Installations? {#s1-kickstart2-whatis}
Many system administrators would prefer to use an automated installation method to install Fedora on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
Kickstart files can be kept on a single server system and read by individual computers during the installation. This installation method can support the use of a single kickstart file to install Fedora on multiple machines, making it ideal for network and system administrators.
Kickstart provides a way for users to automate a Fedora installation.
All kickstart scriptlets and the log files of their execution are stored in the `/tmp` directory to assist with debugging installation failures.
### Note — /tmp/netinfo no longer used
Anaconda now configures network interfaces with NetworkManager. Consequently, kickstart users that referenced the network settings located in `/tmp/netinfo` in previous versions of Fedora must now source the `ifcfg` files in `/etc/sysconfig/network-scripts`.
## 15\.2. How Do You Perform a Kickstart Installation? {#s1-kickstart2-howuse}
Kickstart installations can be performed using a local DVD, a local hard drive, or via NFS, FTP, or HTTP.
To use kickstart, you must:
1. Create a kickstart file.
1. Create a boot media with the kickstart file or make the kickstart file available on the network.
1. Make the installation tree available.
1. Start the kickstart installation.
This chapter explains these steps in detail.
## 15\.3. Creating the Kickstart File {#s1-kickstart2-file}
The kickstart file is a simple text file, containing a list of items, each identified by a keyword. You can create it by using the Kickstart Configurator application, or writing it from scratch. The Fedora installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file `/root/anaconda-ks.cfg`. You should be able to edit it with any text editor or word processor that can save files as ASCII text.
First, be aware of the following issues when you are creating your kickstart file:
* Sections must be specified _in order_. Items within the sections do not have to be in a specific order unless otherwise specified. The section order is:
* Command section — Refer to [Section 15.4, “Kickstart Options”](#s1-kickstart2-options "15.4. Kickstart Options") for a list of kickstart options. You must include the required options.
* The **%packages** section — Refer to [Section 15.5, “Package Selection”](#s1-kickstart2-packageselection "15.5. Package Selection") for details.
* The **%pre** and **%post** sections — These two sections can be in any order and are not required. Refer to [Section 15.6, “Pre-installation Script”](#s1-kickstart2-preinstallconfig "15.6. Pre-installation Script") and [Section 15.7, “Post-installation Script”](#s1-kickstart2-postinstallconfig "15.7. Post-installation Script") for details.
* Items that are not required can be omitted.
* 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 continues unattended (unless it finds another missing item).
* Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.
* For kickstart _upgrades_, the following items are required:
* Language
* Installation method
* Device specification (if device is needed to perform the installation)
* Keyboard setup
* The **upgrade** keyword
* Boot loader configuration
If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).
## 15\.4. Kickstart Options {#s1-kickstart2-options}
The following options can be placed in a kickstart file. If you prefer to use a graphical interface for creating your kickstart file, use the Kickstart Configurator application. Refer to [Chapter 16, _Kickstart Configurator_](#ch-redhat-config-kickstart "Chapter 16. Kickstart Configurator") for details.
### Note
If the option is followed by an equals mark (=), a value must be specified after it. In the example commands, options in brackets ([]) are optional arguments for the command.
**auth** or **authconfig** (required)
: Sets up the authentication options for the system. It is similar to the **authconfig** command, which can be run after the install. By default, passwords are normally encrypted and are not shadowed.
* **--enablenis** — Turns on NIS support. By default, **--enablenis** uses whatever domain it finds on the network. A domain should almost always be set by hand with the **--nisdomain=** option.
* **--nisdomain=** — NIS domain name to use for NIS services.
* **--nisserver=** — Server to use for NIS services (broadcasts by default).
* **--useshadow** or **--enableshadow** — Use shadow passwords.
* **--enableldap** — Turns on LDAP support in `/etc/nsswitch.conf`, allowing your system to retrieve information about users (for example, their UIDs, home directories, and shells) from an LDAP directory. To use this option, you must install the `nss-pam-ldapd` package. You must also specify a server and a base _DN_ (distinguished name) with **--ldapserver=** and **--ldapbasedn=**.
* **--enableldapauth** — Use LDAP as an authentication method. This enables the `pam_ldap` module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the `nss-pam-ldapd` package installed. You must also specify a server and a base DN with **--ldapserver=** and **--ldapbasedn=**. If your environment does not use _TLS_ (Transport Layer Security), use the **--disableldaptls** switch to ensure that the resulting configuration file works.
* **--ldapserver=** — If you specified either **--enableldap** or **--enableldapauth**, use this option to specify the name of the LDAP server to use. This option is set in the `/etc/ldap.conf` file.
* **--ldapbasedn=** — If you specified either **--enableldap** or **--enableldapauth**, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is set in the `/etc/ldap.conf` file.
* **--enableldaptls** — Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.
* **--disableldaptls** — Do not use TLS (Transport Layer Security) lookups in an environment that uses LDAP for authentication.
* **--enablekrb5** — Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the **/usr/sbin/useradd** command. If you use this option, you must have the `pam_krb5` package installed.
* **--krb5realm=** — The Kerberos 5 realm to which your workstation belongs.
* **--krb5kdc=** — The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, separate their names with commas (,).
* **--krb5adminserver=** — The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.
* **--enablehesiod** — Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in `/usr/share/doc/glibc/README.hesiod`, which is included in the `glibc` package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.
* **--hesiodlhs** and **--hesiodrhs** — The `Hesiod` LHS (left-hand side) and RHS (right-hand side) values, set in `/etc/hesiod.conf`. The `Hesiod` library uses these values to search DNS for a name, similar to the way that LDAP uses a base DN.
To look up user information for the username `jim`, the Hesiod library looks up ``jim.passwd<_`LHS`_><_`RHS`_>``, which should resolve to a TXT record that contains a string identical to an entry for that user in the `passwd` file: `jim:*:501:501:Jungle Jim:/home/jim:/bin/bash`. To look up groups, the Hesiod library looks up ``jim.group<_`LHS`_><_`RHS`_>`` instead.
To look up users and groups by number, make `501.uid` a CNAME for `jim.passwd`, and `501.gid` a CNAME for `jim.group`. Note that the library does not place a period (`.`) in front of the LHS and RHS values when performing a search. Therefore, if the LHS and RHS values need to have a period placed in front of them, you must include the period in the values you set for **--hesiodlhs** and **--hesiodrhs**.
* **--enablesmbauth** — Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the workstation by enabling LDAP, NIS, or Hesiod or by using the **/usr/sbin/useradd** command.
* **--smbservers=** — The name of the servers to use for SMB authentication. To specify more than one server, separate the names with commas (,).
* **--smbworkgroup=** — The name of the workgroup for the SMB servers.
* **--enablecache** — Enables the **nscd** service. The **nscd** service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using NIS, LDAP, or Hesiod.
* **--passalgo=** — specify **sha256** to set up the SHA-256 hashing algorithm or **sha512** to set up the SHA-512 hashing algorithm.
**autopart** (optional)
: Automatically creates partitions — a root (`/`) partition (1 GB or bigger), a `/swap` partition, and an appropriate `/boot` partition for the architecture. On large enough drives, this also creates a `/home` partition.
### Note
Note that the `autopart` option cannot be used together with the `part/partition`, `raid`, `logvol`, or `volgroup` options in the same kickstart file.
* **--encrypted** — Should all devices with support be encrypted by default? This is equivalent to checking the Encrypt checkbox on the initial partitioning screen.
* **--cipher=** — Specifies which type of encryption will be used if the anaconda default aes-xts-plain64 is not satisfactory. You must use this option together with the **--encrypted** option; by itself it has no effect. Available types of encryption are listed in the _Red Hat Enterprise Linux Security Guide_, but Red Hat strongly recommends using either aes-xts-plain64 or aes-cbc-essiv:sha256.
* **--passphrase=** — Provide a default system-wide passphrase for all encrypted devices.
* **--escrowcert=_`URL_of_X.509_certificate`_** — Store data encryption keys of all encrypted volumes as files in `/root`, encrypted using the X.509 certificate from the URL specified with _`URL_of_X.509_certificate`_. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if **--encrypted** is specified.
* **--backuppassphrase=** — Add a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in `/root`, encrypted using the X.509 certificate specified with **--escrowcert**. This option is only meaningful if **--escrowcert** is specified.
* **--type=** — Select one of the predefined automatic partitioning scheme you want to use. Accepts the following values:
* `lvm`: The LVM partitioning scheme.
* `btrfs`: The BTRFS partitioning scheme.
* `thinp`: The LVM Thin Provisioning partitioning scheme.
* `plain`: Regular partitions with no LVM or BTRFS.
For a description of the available partition schemes, see [Section 9.14.1.1, “File System Types”](#s3-diskpartitioning-file-x86 "9.14.1.1. File System Types").
* **--nolvm** — Do not use LVM or BTRFS for automatic partitioning. This option is equal to **--type=plain**.
**autostep** (optional)
: Similar to **interactive** except it goes to the next screen for you. It is used mostly for debugging.
* **--autoscreenshot** — Take a screenshot at every step during installation and copy the images over to **/root/anaconda-screenshots** after installation is complete. This is most useful for documentation.
**bootloader** (required)
: Specifies how the boot loader should be installed. This option is required for both installations and upgrades.
### Important
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and anaconda cannot prompt you for missing information. If you do not provide choices for these options, anaconda will stop the installation process.
* **--append=** — Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:
bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"
* **--driveorder** — Specify which drive is first in the BIOS boot order. For example:
bootloader --driveorder=sda,hda
* **--boot-drive=** — Specifies which drive the bootloader is installed to.
* **--location=** — Specifies where the boot record is written. Valid values are the following: **mbr** (the default), **partition** (installs the boot loader on the first sector of the partition containing the kernel), or **none** (do not install the boot loader).
* **--leavebootorder=** — Boot the drives in their existing order, to override the default of booting into the newly installed drive on Power Systems servers and EFI systems. This is useful for systems that, for example, should network boot first before falling back to a local boot.
* **--md5pass=** — If using GRUB, similar to **--password=** except the password should already be encrypted.
* **--password=** — If using GRUB, sets the GRUB boot loader password to the one specified with this option. This should be used to restrict access to the GRUB shell, where arbitrary kernel options can be passed.
* **--timeout=** — Specify the number of seconds before the bootloader times out and boots the default option. Specifying 0 will tell GRUB not to display these menus.
* **--upgrade** — Upgrade the existing boot loader configuration, preserving the old entries. This option is only available for upgrades.
* **--extlinux** — install and use the extlinux bootloader.
**btrfs** (optional)
: Create a BTRFS volume or subvolume. For a volume, the syntax is:
btrfs _``_ --data=_``_ --metadata=_``_ --label=_``_ _``_
_``_ denotes that multiple partitions can be listed and should list the BTRFS identifiers to add to the BTRFS volume.
For a subvolume, the syntax is:
btrfs _``_ --subvol --name=_``_ _``_
_``_ should be the identifier of the subvolume's parent volume.
None of the following options apply to subvolumes.
* **--data=** — RAID level to use for filesystem data (such as 0, 1, or 10).
* **--metadata=** — RAID level to use for filesystem/volume metadata (such as 0, 1, or 10).
* **--label=** — Specify a label for the BTRFS filesystem.
* **--noformat** — Use an existing BTRFS volume and do not reformat the filesystem.
**clearpart** (optional)
: Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
### Note
If the **clearpart** command is used, then the **--onpart** command cannot be used on a logical partition.
* **--all** — Erases all partitions from the system.
* **--drives=** — Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:
clearpart --drives=hda,hdb --all
To clear a multipath device that does not use _logical volume management_ (LVM), use the format ``disk/by-id/dm-uuid-mpath-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to clear a disk with WWID `2416CD96995134CA5D787F00A5AA11017`, use:
clearpart --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017
Multipath devices that use LVM are not assembled until after anaconda has parsed the kickstart file. Therefore, you cannot specify these devices in the format `dm-uuid-mpath`. Instead, to clear a multipath device that uses LVM, use the format ``disk/by-id/scsi-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to clear a disk with WWID `58095BEC5510947BE8C0360F604351918`, use:
clearpart --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918
### Warning — Never specify multipath devices by device names like `mpatha`
Device names like `mpatha` are not specific to a particular disk. The disk named `/dev/mpatha` during installation might not be the one that you expect it to be. Therefore, the **clearpart** command could target the wrong disk.
* **--list=** — Specifies individual partitions to be removed. For example, the following removes the first partition on the `hda` drive and the second partition on the `hdb` drive:
clearpart --list=hda1,hdb2
* **--initlabel** — Initializes the disk label to the default for your architecture (for example **msdos** for x86). It is useful so that the installation program does not ask if it should initialize the disk label if installing to a brand new hard drive.
* **--linux** — Erases all Linux partitions.
* **--none** (default) — Do not remove any partitions.
**cmdline** (optional)
: Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install.
**device** (optional)
: On most PCI systems, the installation program autoprobes for Ethernet and SCSI cards properly. On older systems and some PCI systems, however, kickstart needs a hint to find the proper devices. The **device** command, which tells the installation program to install extra modules, is in this format:
device _``_ --opts=_``_
* _``_ — Replace with the name of the kernel module which should be installed.
* **--opts=** — 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.
**driverdisk** (optional)
: Driver disks can be used during kickstart installations. 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 **driverdisk** command to tell the installation program where to look for the driver disk.
driverdisk _``_ --source=_``_ --biospart=_``_ [--type=_``_]
Alternatively, a network location can be specified for the driver disk:
driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/img
* _``_ — Partition containing the driver disk.
* _``_ — URL for the driver disk. NFS locations can be given in the form ``nfs:_`host`_:/_`path/to/img`_``.
* _``_ — BIOS partition containing the driver disk (for example, `82p2`).
* **--type=** — File system type (for example, vfat or ext2).
**firewall** (optional)
: This option corresponds to the Firewall Configuration screen in the installation program:
firewall --enabled|--disabled [--trust=] _``_ [--port=]
* **--enabled** or **--enable** — Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
* **--disabled** or **--disable** — Do not configure any iptables rules.
* **--trust=** — Listing a device here, such as eth0, allows all traffic coming from that device to go through the firewall. To list more than one device, use **--trust eth0 --trust eth1**. Do NOT use a comma-separated format such as **--trust eth0, eth1**.
* _``_ — Replace with one or more of the following to allow the specified services through the firewall.
* **--ssh**
* **--smtp**
* **--http**
* **--ftp**
* **--port=** — You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify **imap:tcp**. Numeric ports can also be specified explicitly; for example, to allow UDP packets on port 1234 through, specify **1234:udp**. To specify multiple ports, separate them by commas.
**graphical** (optional)
: Perform the kickstart installation in graphical mode. This is the default.
**halt** (optional)
: Halt the system after the installation has successfully completed. This is similar to a manual installation, where anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, this option is used as the default.
The **halt** option is equivalent to the **shutdown -h** command.
For other completion methods, refer to the **poweroff**, **reboot**, and **shutdown** kickstart options.
**ignoredisk** (optional)
: Causes the installer to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored. For example, without `ignoredisk`, attempting to deploy on a SAN-cluster the kickstart would fail, as the installer detects passive paths to the SAN that return no partition table.
The syntax is:
ignoredisk --drives=_`drive1,drive2`_,...
where _`driveN`_ is one of `sda`, `sdb`,..., `hda`,... etc.
To ignore a multipath device that does not use _logical volume management_ (LVM), use the format ``disk/by-id/dm-uuid-mpath-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to ignore a disk with WWID `2416CD96995134CA5D787F00A5AA11017`, use:
ignoredisk --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017
Multipath devices that use LVM are not assembled until after anaconda has parsed the kickstart file. Therefore, you cannot specify these devices in the format `dm-uuid-mpath`. Instead, to ignore a multipath device that uses LVM, use the format ``disk/by-id/scsi-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to ignore a disk with WWID `58095BEC5510947BE8C0360F604351918`, use:
ignoredisk --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918
### Warning — Never specify multipath devices by device names like `mpatha`
Device names like `mpatha` are not specific to a particular disk. The disk named `/dev/mpatha` during installation might not be the one that you expect it to be. Therefore, the **ignoredisk** command could target the wrong disk.
* **--only-use** — specifies a list of disks for the installer to use. All other disks are ignored. For example, to use disk `sda` during installation and ignore all other disks:
ignoredisk --only-use=sda
To include a multipath device that does not use LVM:
ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017
To include a multipath device that uses LVM:
ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918
**install** (optional)
: Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from **cdrom**, **harddrive**, **nfs**, or **url** (for FTP or HTTP installations). The **install** command and the installation method command must be on separate lines.
* **cdrom** — Install from the first optical drive on the system.
* **harddrive** — Install from a Fedora installation tree on a local drive, which must be either vfat or ext2.
* **--biospart=**
BIOS partition to install from (such as 82).
* **--partition=**
Partition to install from (such as sdb2).
* **--dir=**
Directory containing the ``_`variant`_`` directory of the installation tree.
For example:
harddrive --partition=hdb2 --dir=/tmp/install-tree
* **liveimg** — Install a disk image instead of packages. The image can be the `squashfs.img` file from a live image or a bare image from any existing filesystem mountable by the installation media, such as ext4. The image will be downloaded to the target drive after it has been partitioned.
* **--url=_``_** — specify where the live image should be downloaded from. HTTP, HTTPS, FTP, and local file access are all supported.
* **--proxy=[protocol://]\[username[:password]@]host[:port]** — specify a HTTP, HTTPS, or FTP proxy, if desired.
* **--checksum=** — pass the optional sha256 image checksum before files are copied to the target system.
* **--noverifyssl** — skip checking the SSL certificate if downloading via HTTPS.
For example:
liveimg --url=https://_``_/_``_ [--checksum=sha256] [--noverifyssl]
### Important
The disk image must have the necessary utilities that anaconda needs to complete the installation, so livemedia-creator is recommended for creating the disk image.
* **nfs** — Install from the NFS server specified.
* **--server=**
Server from which to install (hostname or IP).
* **--dir=**
Directory containing the ``_`variant`_`` directory of the installation tree.
* **--opts=**
Mount options to use for mounting the NFS export. (optional)
For example:
nfs --server=nfsserver.example.com --dir=/tmp/install-tree
* **url** — Install from an installation tree on a remote server via FTP or HTTP.
For example:
url --url http://_``_/_``_
or:
url --url ftp://_``_:_`@`_/_``_
**iscsi** (optional)
: iscsi --ipaddr= [options].
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 _earlier_ in the kickstart file.
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`_.
* **--port=** (mandatory) — the port number (typically, **--port=3260**)
* **--user=** — the username required to authenticate with the target
* **--password=** — the password that corresponds with the username specified for the target
* **--reverse-user=** — the username required to authenticate with the initiator from a target that uses reverse CHAP authentication
* **--reverse-password=** — 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, you must specify _`iscsiname`_ _earlier_ in the kickstart file.
**keyboard** (required)
: Set the available keyboard layouts for the system and how to switch between them with the following syntax:
keyboard --vckeymap=_``_|--xlayouts=_``_,...,_``_|_``_ [--switch=_``_,..._``_]
* **--vckeymap=_``_** — specify a VConsole keymap to serve as the keyboard layout. Available keymap names are listed in ``/usr/lib/kbd/keymaps/_`architecture`_`` with the `.map.gz` extension removed.
* **--xlayouts=** — specify a list of X layouts as a comma-separated list with no spaces. Layouts come in one of the following formats: _`layout`_ and _`'layout (variant)'`_. For example:
keyboard --xlayouts=cz,'cz (qwerty)'
Refer to for the available layouts.
* **_``_** — an earlier format for specifying the keyboard layout. This format is still supported and accepts both VConsole keymap names and X layouts.
* **--switch=** — specify keyboard shortcuts for switching between layouts. The list should be comma-separated with no spaces. Refer to for the available options.
**lang** (required)
: Sets the language to use during installation and the default language to use on the installed system. For example, to set the language to English, the kickstart file should contain the following line:
lang en_US
The file `/usr/share/system-config-language/locale-list` provides a list of the valid language codes in the first column of each line and is part of the `system-config-language` package.
Certain languages (for example, Chinese, Japanese, Korean, and Indic languages) are not supported during text-mode installation. If you specify one of these languages with the **lang** command, the installation process continues in English, but the installed system uses your selection as its default language.
* **--addsupport** — Set additional languages to be supported on the installed system.
**langsupport** (deprecated)
: The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the **%packages** section of your kickstart file. For instance, adding support for French means you should add the following to **%packages**:
@french-support
**logvol** (optional)
: Create a logical volume for Logical Volume Management (LVM) with the syntax:
logvol _``_ --vgname=_``_ --size=_``_ --name=_``_ _``_
The options are as follows:
* **--noformat** — Use an existing logical volume and do not format it.
* **--useexisting** — Use an existing logical volume and reformat it.
* **--fstype=** — Sets the file system type for the logical volume. Valid values are **xfs**, **ext2**, **ext3**, **ext4**, **swap**, **vfat**, and **hfs**.
* **--fsoptions=** — 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.
* **--grow=** — Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting.
* **--maxsize=** — The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as `500` (do not include the unit).
* **--recommended=** — Determine the size of the logical volume automatically.
* **--percent=** — Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option must be used in conjunction with the `--size` and `--grow` options for **logvol**.
* **--encrypted** — Specifies that this logical volume should be encrypted, using the passphrase provided in the **--passphrase** option. If you do not specify a passphrase, anaconda uses the default, system-wide passphrase set with the **autopart --passphrase** command, or stops the installation and prompts you to provide a passphrase if no default is set.
* **--passphrase=** — Specifies the passphrase to use when encrypting this logical volume. You must use this option together with the **--encrypted** option; by itself it has no effect.
* **--escrowcert=_`URL_of_X.509_certificate`_** — Store data encryption keys of all encrypted volumes as files in `/root`, encrypted using the X.509 certificate from the URL specified with _`URL_of_X.509_certificate`_. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if **--encrypted** is specified.
* **--backuppassphrase=** — Add a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in `/root`, encrypted using the X.509 certificate specified with **--escrowcert**. This option is only meaningful if **--escrowcert** is specified.
* **--thinpool=** — Create a thin pool logical volume. (Use a mountpoint of "none")
* **--metadatasize=_`size`_** — Specify the metadata area size (in MiB) for a new thin pool device.
* **--chunksize=_`size`_** — Specify the chunk size (in KiB) for a new thin pool device.
* **--thin** — Create a thin logical volume. (Requires use of --poolname)
* **--poolname=_`name`_** — Specify the name of the thin pool in which to create a thin logical volume. (Requires --thin)
* **--resize** — Resize an existing partition. This option must be used in conjunction with the `--size=` to specify the new size and `--useexisting`.
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
Create the partition first, create the logical volume group, and then create the logical volume to occupy 90% of the remaining space in the volume group. For example:
part pv.01 --size 1 --grow
volgroup myvg pv.01
logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90
**logging** (optional)
: This command controls the error logging of anaconda during installation. It has no effect on the installed system.
* **--host=** — Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.
* **--port=** — If the remote syslogd process uses a port other than the default, it may be specified with this option.
* **--level=** — 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.
**mediacheck** (optional)
: 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.
**monitor** (optional)
: 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.
* **--hsync=** — Specifies the horizontal sync frequency of the monitor.
* **--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.
* **--noprobe=** — Do not try to probe the monitor.
* **--vsync=** — Specifies the vertical sync frequency of the monitor.
**mouse** (deprecated)
: The mouse keyword is deprecated.
**network** (optional)
: Configures network information for the target system and activates network devices in the installer environment. The device specified in the first **network** command is activated automatically if network access is required during installation, for example, during a network installation or installation over VNC. You can also explicitly require device to activate in the installer environment with the `--activate` option.
### How to manually input network settings
If you need to manually specify network settings during an otherwise-automated kickstart installation, do not use **network**. Instead, enter your network settings at the boot prompt (refer to [Section 15.10, “Starting a Kickstart Installation”](#s1-kickstart2-startinginstall "15.10. Starting a Kickstart Installation") for available boot options).
Once the network connection is established, you can only reconfigure network settings with those specified in your kickstart file.
### Note
You will only be prompted for information about your network:
* before fetching the kickstart file if you are using the **asknetwork** boot option
* when the network is first accessed once the kickstart file has been fetched, if the network was not used to fetch it and you have provided no kickstart network commands
* **--activate** — activate this device in the installer environment.
If you use the `--activate` option on a device that has already been activated (for example, an interface you configured with boot options so that the system could retrieve the kickstart file) the device is reactivated to use the details specified in the kickstart file.
Use the **--nodefroute** option to prevent the device from using the default route.
The **activate** option is new in Fedora 16.
* **--biosdevname=0** — disables _consistent network device naming_ (refer to _Appendix A_ in the _Fedora System Administrators Guide_).
* **--bootproto=** — One of **dhcp**, **bootp**, **ibft**, or **static**.
The **ibft** option is new in Fedora 16.
The **bootproto** option defaults to **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. To direct a system to use DHCP:
network --bootproto=dhcp
To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the kickstart file:
network --bootproto=bootp
To direct a machine to use the configuration specified in iBFT, use:
network --bootproto=ibft
The static method requires that you specify the IP address, netmask, gateway, and nameserver in the kickstart file. As the name implies, this information is static and is used during and after the installation.
All static networking configuration information must be specified on _one_ line; you cannot wrap lines using a backslash as you can on a command line. A line that specifies static networking in a kickstart file is therefore more complex than lines that specify DHCP, BOOTP, or iBFT. Note that the examples on this page have line breaks in them for presentation reasons; they would not work in an actual kickstart file.
network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0
--gateway=10.0.2.254 --nameserver=10.0.2.1
You can also configure multiple nameservers here. To do so, specify them as a comma-delimited list in the command line.
network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0
--gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
* **--device=** — specifies the device to be configured (and eventually activated) with the **network** command. For the first **network** command, **--device=** defaults (in order of preference) to one of:
1. the device specified by the `ksdevice` boot option
1. the device activated automatically to fetch the kickstart file
1. the device selected in the Networking Devices dialog
The behavior of any subsequent **network** command is unspecified if its **--device** option is missing. Take care to specify a **--device** option for any network command beyond the first.
You can specify a device in one of five ways:
* the device name of the interface, for example, `eth0`
* the MAC address of the interface, for example, `00:12:34:56:78:9a`
* the keyword `link`, which specifies the first interface with its link in the `up` state
* the keyword `bootif`, which uses the MAC address that pxelinux set in the _`BOOTIF`_ variable. Set `IPAPPEND 2` in your `pxelinux.cfg` file to have pxelinux set the _`BOOTIF`_ variable.
* the keyword `ibft`, which uses the MAC address of the interface specified by iBFT
network --bootproto=dhcp --device=eth0
* **--ip=** — IP address of the device.
* **--ipv6=** — IPv6 address of the device, or **auto** to use automatic neighbor discovery, or **dhcp** to use DHCPv6.
* **--gateway=** — Default gateway as a single IPv4 address.
* **--ipv6gateway=** — Default gateway as a single IPv6 address.
* **--nameserver=** — Primary nameserver, as an IP address. Multiple nameservers must each be separated by a comma.
* **--nodefroute** — Prevents the interface being set as the default route. Use this option when you activate additional devices with the **--activate=** option, for example, a NIC on a separate subnet for an iSCSI target.
The **nodefroute** option is new in Fedora 16.
* **--nodns** — Do not configure any DNS server.
* **--netmask=** — Network mask of the device.
* **--hostname=** — Hostname for the installed system.
* **--ethtool=** — Specifies additional low-level settings for the network device which will be passed to the ethtool program.
* **--onboot=** — Whether or not to enable the device at boot time.
* **--dhcpclass=** — The DHCP class.
* **--mtu=** — The MTU of the device.
* **--noipv4** — Disable IPv4 on this device.
* **--noipv6** — Disable IPv6 on this device.
* **--vlanid** — Specifies virtual LAN ID number (802.1q tag).
**part** or **partition** (required for installs, ignored for upgrades)
: Creates a partition on the system.
If more than one Fedora installation exists on the system on different partitions, the installation program prompts the user and asks which installation to upgrade.
### Warning
As of Fedora 16, you need a biosboot partition in order to successfully install the bootloader on a disk that contains a GPT/GUID partition table. This includes disks initialized by the installer. This partition can be created with the kickstart option **part biosboot --fstype=biosboot --size=1**.
However, if the disk already has a biosboot partition, adding a **"part biosboot"** option is unnecessary.
### Warning
All partitions created are formatted as part of the installation process unless **--noformat** and **--onpart** are used.
### Important
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and anaconda cannot prompt you for missing information. If you do not provide choices for these options, anaconda will stop the installation process.
For a detailed example of **part** in action, refer to [Section 15.4.1, “Advanced Partitioning Example”](#s2-kickstart2-options-part-examples "15.4.1. Advanced Partitioning Example").
* _``_ — The _``_ is where the partition is mounted and must be of one of the following forms:
* ``/_``_``
For example, **/**, **/usr**, **/home**
* **swap**
The partition is used as swap space.
To determine the size of the swap partition automatically, use the **--recommended** option:
swap --recommended
The size assigned will be effective but not precisely calibrated for your system.
To determine the size of the swap partition automatically but also allow extra space for your system to hibernate, use the **--hibernation** option:
swap --hibernation
The size assigned will be equivalent to the swap space assigned by **--recommended** plus the amount of RAM on your system.
For the swap sizes assigned by these commands, refer to [Section 9.14.5, “Recommended Partitioning Scheme”](#s2-diskpartrecommend-x86 "9.14.5. Recommended Partitioning Scheme")
* **raid._``_**
The partition is used for software RAID (refer to **raid**).
* **pv._``_**
The partition is used for LVM (refer to **logvol**).
* **--size=** — The minimum partition size in megabytes. Specify an integer value here such as `500` (do not include the unit).
### Important - **--size** value must be high
If the **--size** value is too small, the installation will fail. Set the **--size** value as the minimum amount of space you require. For size recommendations, refer to [Section 9.14.5, “Recommended Partitioning Scheme”](#s2-diskpartrecommend-x86 "9.14.5. Recommended Partitioning Scheme").
* **--grow** — Tells the partition to grow to fill available space (if any), or up to the maximum size setting.
### Note
If you use **--grow=** without setting **--maxsize=** on a swap partition, Anaconda will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.
* **--maxsize=** — The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here such as `500` (do not include the unit).
* **--resize** — Resize an existing partition. This option must be used in conjunction with the `--size=` to specify the new size and `--onpart=` to specify the partition.
* **--noformat** — Specifies that the partition should not be formatted, for use with the **--onpart** command.
* **--onpart=** or **--usepart=** — Specifies the device on which to place the partition. For example:
partition /home --onpart=hda1
puts `/home` on `/dev/hda1`.
The device must already exist on the system; the **--onpart** option will not create it.
* **--ondisk=** or **--ondrive=** — Forces the partition to be created on a particular disk. For example, **--ondisk=sdb** puts the partition on the second SCSI disk on the system.
To specify a multipath device that does not use _logical volume management_ (LVM), use the format ``disk/by-id/dm-uuid-mpath-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to specify a disk with WWID `2416CD96995134CA5D787F00A5AA11017`, use:
part / --fstype=ext3 --grow --asprimary --size=100 --ondisk=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017
Multipath devices that use LVM are not assembled until after anaconda has parsed the kickstart file. Therefore, you cannot specify these devices in the format `dm-uuid-mpath`. Instead, to specify a multipath device that uses LVM, use the format ``disk/by-id/scsi-_`WWID`_``, where _`WWID`_ is the _world-wide identifier_ for the device. For example, to specify a disk with WWID `58095BEC5510947BE8C0360F604351918`, use:
part / --fstype=ext3 --grow --asprimary --size=100 --ondisk=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918
### Warning — Never specify multipath devices by device names like `mpatha`
Device names like `mpatha` are not specific to a particular disk. The disk named `/dev/mpatha` during installation might not be the one that you expect it to be. Therefore, the **part** command could target the wrong disk or partition.
* **--asprimary** — Forces automatic allocation of the partition as a primary partition, or the partitioning fails.
* **--type=** (replaced by **fstype**) — This option is no longer available. Use **fstype**.
* **--fsoptions** — 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.
* **--fsprofile** — Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For ext2, ext3, and ext4, this configuration file is `/etc/mke2fs.conf`.
* **--fstype=** — Sets the file system type for the partition. Valid values are **xfs**, **ext2**, **ext3**, **ext4**, **swap**, **vfat**, and **hfs**.
* **--recommended** — Determine the size of the partition automatically.
* **--onbiosdisk** — Forces the partition to be created on a particular disk as discovered by the BIOS.
* **--encrypted** — Specifies that this partition should be encrypted, using the passphrase provided in the **--passphrase** option. If you do not specify a passphrase, anaconda uses the default, system-wide passphrase set with the **autopart --passphrase** command, or stops the installation and prompts you to provide a passphrase if no default is set.
* **--passphrase=** — Specifies the passphrase to use when encrypting this partition. You must use this option together with the **--encrypted** option; by itself it has no effect.
* **--escrowcert=_`URL_of_X.509_certificate`_** — Store data encryption keys of all encrypted partitions as files in `/root`, encrypted using the X.509 certificate from the URL specified with _`URL_of_X.509_certificate`_. The keys are stored as a separate file for each encrypted partition. This option is only meaningful if **--encrypted** is specified.
* **--backuppassphrase=** — Add a randomly-generated passphrase to each encrypted partition. Store these passphrases in separate files in `/root`, encrypted using the X.509 certificate specified with **--escrowcert**. This option is only meaningful if **--escrowcert** is specified.
* **--label=** — assign a label to an individual partition.
### Note
If partitioning fails for any reason, diagnostic messages appear on virtual console 3.
**poweroff** (optional)
: Shut down and power off the system after the installation has successfully completed. Normally during a manual installation, anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion method is specified, the **halt** option is used as default.
The **poweroff** option is equivalent to the **shutdown -p** command.
### Note
The **poweroff** option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.
For other completion methods, refer to the **halt**, **reboot**, and **shutdown** kickstart options.
**raid** (optional)
: Assembles a software RAID device. This command is of the form:
raid _``_ --level=_``_ --device=_``_ _``_
* _``_ — Location where the RAID file system is mounted. If it is `/`, the RAID level must be 1 unless a boot partition (`/boot`) is present. If a boot partition is present, the `/boot` partition must be level 1 and the root (`/`) partition can be any of the available types. The _``_ (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
* **--level=** — RAID level to use (0, 1, or 5).
* **--device=** — Name of the RAID device to use (such as md0 or md1). RAID devices range from md0 to md15, and each may only be used once.
* **--spares=** — Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.
* **--grow=** — Only supported for RAID0. Tells the RAID device to grow to fill available space (if any), or up to the maximum size setting.
* **--fsprofile** — Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For ext2, ext3, and ext4, this configuration file is `/etc/mke2fs.conf`.
* **--fstype=** — Sets the file system type for the RAID array. Valid values are **xfs**, **ext2**, **ext3**, **ext4**, **swap**, **vfat**, and **hfs**.
* **--fsoptions=** — 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.
* **--noformat** — Use an existing RAID device and do not format the RAID array.
* **--useexisting** — Use an existing RAID device and reformat it.
* **--encrypted** — Specifies that this RAID device should be encrypted, using the passphrase provided in the **--passphrase** option. If you do not specify a passphrase, anaconda uses the default, system-wide passphrase set with the **autopart --passphrase** command, or stops the installation and prompts you to provide a passphrase if no default is set.
* **--passphrase=** — Specifies the passphrase to use when encrypting this RAID device. You must use this option together with the **--encrypted** option; by itself it has no effect.
* **--escrowcert=_`URL_of_X.509_certificate`_** — Store the data encryption key for this device in a file in `/root`, encrypted using the X.509 certificate from the URL specified with _`URL_of_X.509_certificate`_. This option is only meaningful if **--encrypted** is specified.
* **--backuppassphrase=** — Add a randomly-generated passphrase to this device. Store the passphrase in a file in `/root`, encrypted using the X.509 certificate specified with **--escrowcert**. This option is only meaningful if **--escrowcert** is specified.
The following example shows how to create a RAID level 1 partition for `/`, and a RAID level 5 for `/usr`, assuming there are three SCSI disks on the system. It also creates three swap partitions, one on each drive.
part raid.01 --size=60 --ondisk=sda
part raid.02 --size=60 --ondisk=sdb
part raid.03 --size=60 --ondisk=sdc
part swap --size=128 --ondisk=sda
part swap --size=128 --ondisk=sdb
part swap --size=128 --ondisk=sdc
part raid.11 --size=1 --grow --ondisk=sda
part raid.12 --size=1 --grow --ondisk=sdb
part raid.13 --size=1 --grow --ondisk=sdc
raid / --level=1 --device=md0 raid.01 raid.02 raid.03
raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
For a detailed example of **raid** in action, refer to [Section 15.4.1, “Advanced Partitioning Example”](#s2-kickstart2-options-part-examples "15.4.1. Advanced Partitioning Example").
**realm** (optional)
: Join Active Directory or IPA domains, with the syntax:
realm join _``_ _``_
The options are as follows:
* **--client-software=** — Only join realms that can run this client software. Valid values include **sssd** or **winbind**. Not all realms support all values. By default, the client software is chosen automatically.
* **--server-software=** — Only join realms that can run this server software. Possible values include **active-directory** or **freeipa**.
* **--membership-software= ** — Use this software when joining the realm. Valid values include **samba** and **adcli**. Not all realms support all values. By default, the membership software is chosen automatically.
* **--one-time-password=** — Join using a one-time password. This is not possible with all types of realm.
* **--no-password** — Join automatically without a password.
* **--computer-ou OU=** — provide the distinguished name of an organizational unit in order to create the computer account. The exact format of the distinguished name depends on the client software and membership software. The root DSE portion of the distinguished name can typically be left out.
**reboot** (optional)
: Reboot after the installation is successfully completed (no arguments). Normally, kickstart displays a message and waits for the user to press a key before rebooting.
The **reboot** option is equivalent to the **shutdown -r** command.
For other completion methods, refer to the **halt**, **poweroff**, and **shutdown** kickstart options.
The **halt** option is the default completion method if no other methods are explicitly specified in the kickstart file.
### Note
Use of the **reboot** option _may_ result in an endless installation loop, depending on the installation media and method.
**repo** (optional)
: Configures additional yum repositories that may be used as sources for package installation. Multiple repo lines may be specified.
repo --name=_``_ [--baseurl=_``_| --mirrorlist=_``_]
* **--name=** — The repo id. This option is required.
* **--baseurl=** — The URL for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --mirrorlist, not both.
* **--mirrorlist=** — The URL pointing at a list of mirrors for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --baseurl, not both.
* **--cost=** — An integer value to assign a cost to this repository. If multiple repositories provide the same packages, this number will be used to prioritize which repository will be used before another. Repositories with a lower cost take priority over repositories with higher cost.
* **--excludepkgs=** — A comma-separated list of package names and globs that must _not_ be pulled from this repository. This is useful if multiple repositories provide the same package and you want to make sure it comes from a particular repository.
* **--include=** — A comma-separated list of package names and globs that must be pulled from this repository. This is useful if multiple repositories provide the same package and you want to make sure it comes from this repository.
* **--proxy=[_`protocol`_://]\[_`username`_[:_`password`_]@]_`host`_[:_`port`_]** — Specify an HTTP/HTTPS/FTP proxy to use just for this repository. This setting does not affect any other repositories, nor how the install.img is fetched on HTTP installs. The various parts of the argument act like you would expect.
* **--ignoregroups=true** — This option is used when composing installation trees and has no effect on the installation process itself. It tells the compose tools to not look at the package group information when mirroring trees so as to avoid mirroring large amounts of unnecessary data.
* **--noverifyssl** — For a https repo 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.
### Important
Repositories used for installation must be stable. The installation may fail if a repository is modified before the installation concludes.
**rootpw** (required)
: Sets the system's root password to the _``_ argument.
rootpw [--iscrypted|--allow-changes|--frozen] _``_
* **--iscrypted** — If this is present, the password argument is assumed to already be encrypted.
* **--allow-changes** — If this is present, the password argument can be changed with no additional actions required.
* **--frozen** — If this is present, the password argument cannot be changed.
**selinux** (optional)
: Sets the state of SELinux on the installed system. SELinux defaults to enforcing in anaconda.
selinux [--disabled|--enforcing|--permissive]
* **--enforcing** — Enables SELinux with the default targeted policy being enforced.
### Note
If the **selinux** option is not present in the kickstart file, SELinux is enabled and set to **--enforcing** by default.
* **--permissive** — Outputs warnings based on the SELinux policy, but does not actually enforce the policy.
* **--disabled** — Disables SELinux completely on the system.
For more information regarding SELinux for Fedora, refer to the _Fedora Security Guide_.
**services** (optional)
: Modifies the default set of services that will run under the default runlevel. The list of disabled services is processed before the list of enabled services. Therefore, if a service appears on both lists, it is enabled.
* **--disabled** — Disable the services given in the comma separated list.
* **--enabled** — Enable the services given in the comma separated list.
### Do not include spaces in the list of services
If you include spaces in the comma-separated list, kickstart will enable or disable only the services up to the first space. For example:
**services --disabled auditd, cups,smartd, nfslock**
will disable only the auditd service. To disable all four services, this entry should include no spaces between services:
**services --disabled auditd,cups,smartd,nfslock**
**shutdown** (optional)
: Shut down the system after the installation has successfully completed. During a kickstart installation, if no completion method is specified, the **halt** option is used as default.
The **shutdown** option is equivalent to the **shutdown** command.
For other completion methods, refer to the **halt**, **poweroff**, and **reboot** kickstart options.
**skipx** (optional)
: If present, X is not configured on the installed system.
### Package selection might configure X
If you install a display manager among your package selection options, this package will create an X configuration, and the installed system will default to run level 5. The effect of the skipx option is overridden.
**sshpw** (optional)
: During installation, you can interact with anaconda and monitor its progress over an SSH connection. Use the **sshpw** command to create temporary accounts through which to log on. Each instance of the command creates a separate account that exists only in the installation environment. These accounts are not transferred to the installed system.
sshpw --username=_``_ _``_ [--iscrypted|--plaintext] [--lock]
* **--username** — Provides the name of the user. This option is required.
* **--iscrypted** — Specifies that the password is already encrypted.
* **--plaintext** — Specifies that the password is in plain text and not encrypted.
* **--lock** — If this is present, the new user account is locked by default. That is, the user will not be able to login from the console.
### Important — You must boot with sshd=1
By default, the ssh server is not started during installation. To make `ssh` available during installation, boot the system with the kernel boot option _`sshd=1`_. Refer to [Console, Environment and Display Options](#list-boot-options-display "Console, Environment and Display Options") for details of how to specify this kernel option at boot time.
**text** (optional)
: Perform the kickstart installation in text mode. Kickstart installations are performed in graphical mode by default.
### Important
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and anaconda cannot prompt you for missing information. If you do not provide choices for these options, anaconda will stop the installation process.
**timezone** (required)
: Sets the system time zone to _``_. Refer to for a list of supported timezones.
timezone [--utc] [--nontp] [--ntpservers=_``_,_``_,...,_``_] _``_
* **--utc** — If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
* **--nontp** — Disable the automatic activation of the NTP service.
* **--ntpservers=** — Specify a list of NTP servers to be used, separated by commas without spaces.
**upgrade** (optional)
: Tells the system to upgrade an existing system rather than install a fresh system. You must specify one of **cdrom**, **harddrive**, **nfs**, or **url** (for FTP and HTTP) as the location of the installation tree. Refer to **install** for details.
**user** (optional)
: Creates a new user on the system.
user --name=_``_ [--groups=_``_] [--homedir=_``_] [--password=_``_] [--iscrypted] [--shell=_``_] [--uid=_``_]
* **--name=** — Provides the name of the user. This option is required.
* **--groups=** — In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created.
* **--homedir=** — The home directory for the user. If not provided, this defaults to /home/_``_.
* **--password=** — The new user's password. If not provided, the account will be locked by default.
* **--iscrypted=** — Is the password provided by --password already encrypted or not?
* **--shell=** — The user's login shell. If not provided, this defaults to the system default.
* **--uid=** — The user's UID. If not provided, this defaults to the next available non-system UID.
**vnc** (optional)
: Allows the graphical installation to be viewed remotely via VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installs. With no options, this command will start a VNC server on the machine with no password and will print out the command that needs to be run to connect a remote machine.
vnc [--host=_``_] [--port=_``_] [--password=_``_]
* **--host=** — Instead of starting a VNC server on the install machine, connect to the VNC viewer process listening on the given hostname.
* **--port=** — Provide a port that the remote VNC viewer process is listening on. If not provided, anaconda will use the VNC default.
* **--password=** — Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
**volgroup** (optional)
: Use to create a Logical Volume Management (LVM) group with the syntax:
volgroup _``_ _``_ _``_
The options are as follows:
* **--noformat** — Use an existing volume group and do not format it.
* **--useexisting** — Use an existing volume group and reformat it.
* **--pesize=** — Set the size of the physical extents.
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
For a detailed example of **volgroup** in action, refer to [Section 15.4.1, “Advanced Partitioning Example”](#s2-kickstart2-options-part-examples "15.4.1. Advanced Partitioning Example").
**xconfig** (optional)
: Configures the X Window System. If you install the X Window System with a kickstart file that does not include the **xconfig** command, you must provide the X configuration manually during installation.
Do not use this command in a kickstart file that does not install the X Window System.
* **--driver** — Specify the X driver to use for the video hardware.
* **--videoram=** — Specifies the amount of video RAM the video card has.
* **--defaultdesktop=** — Specify either GNOME or KDE to set the default desktop (assumes that GNOME Desktop Environment and/or KDE Desktop Environment has been installed through **%packages**).
* **--startxonboot** — Use a graphical login on the installed system.
**zerombr** (optional)
: If **zerombr** is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables.
Note that this command was previously specified as **zerombr yes**. This form is now deprecated; you should now simply specify **zerombr** in your kickstart file instead.
**%include** (optional)
: Use the **%include _`/path/to/file`_** command to include the contents of another file in the kickstart file as though the contents were at the location of the **%include** command in the kickstart file.
### 15\.4.1. Advanced Partitioning Example {#s2-kickstart2-options-part-examples}
The following is a single, integrated example showing the **clearpart**, **raid**, **part**, **volgroup**, and **logvol** kickstart options in action:
clearpart --drives=hda,hdc --initlabel
# Raid 1 IDE config
part raid.11 --size 1000 --asprimary --ondrive=hda
part raid.12 --size 1000 --asprimary --ondrive=hda
part raid.13 --size 2000 --asprimary --ondrive=hda
part raid.14 --size 8000 --ondrive=hda
part raid.15 --size 16384 --grow --ondrive=hda
part raid.21 --size 1000 --asprimary --ondrive=hdc
part raid.22 --size 1000 --asprimary --ondrive=hdc
part raid.23 --size 2000 --asprimary --ondrive=hdc
part raid.24 --size 8000 --ondrive=hdc
part raid.25 --size 16384 --grow --ondrive=hdc
# You can add --spares=x
raid / --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21
raid /safe --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22
raid swap --fstype swap --device md2 --level=RAID1 raid.13 raid.23
raid /usr --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24
raid pv.01 --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25
# LVM configuration so that we can resize /var and /usr/local later
volgroup sysvg pv.01
logvol /var --vgname=sysvg --size=8000 --name=var
logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse
logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal
This advanced example implements LVM over RAID, as well as the ability to resize various directories for future growth.
## 15\.5. Package Selection {#s1-kickstart2-packageselection}
### Warning — do not install every available package
You can use a kickstart file to install every available package by specifying `@Everything` or simply `*` in the %packages section. However, using a kickstart file in this way will introduce package and file conflicts onto the installed system
Use the **%packages** command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
You can specify packages by _group_ or by their package names. The installation program defines several groups that contain related packages. Refer to the ``_`variant`_/repodata/comps-*.xml`` file on the Fedora DVD for a list of groups; alternatively, you can use the **yum grouplist hidden -v** command to obtain a list of package groups if you have a working installation available already. Each group has an id, user visibility value, name, description, and package list. If the group is selected for installation, the packages marked `mandatory` in the package list are always installed, the packages marked `default` are installed if they are not specifically excluded elsewhere, and the packages marked `optional` must be specifically included elsewhere even when the group is selected.
Specify groups, one entry to a line, starting with an `@` symbol, a space, and then the full group name or group id as given in the `comps.xml` file or in the **yum grouplist hidden -v** command's output. For example:
%packages
@ X Window System
@ Desktop
@ Sound and Video
Note that the **Core** and **Base** groups are always selected by default, so it is not necessary to specify them in the **%packages** section.
Specify individual packages by name, one entry to a line. You can use asterisks as wildcards to glob package names in entries. For example:
sqlite
curl
aspell
docbook*
The `docbook*` entry includes the packages docbook-dtds, docbook-simple, docbook-slides and others that match the pattern represented with the wildcard.
Use a leading dash to specify packages or groups to exclude from the installation. For example:
-@ Graphical Internet
-autofs
-ipa*fonts
Using a kickstart file to install every available package by specifying `*` will introduce package and file conflicts onto the installed system. Packages known to cause such problems are assigned to the ``@Conflicts (_`variant`_)`` group, where _`variant`_ is `Client`, `ComputeNode`, `Server` or `Workstation`. If you specify `*` in a kickstart file, be sure to exclude ``@Conflicts (_`variant`_)`` or the installation will fail:
*
-@Conflicts (Server)
Note that the Fedora Project does not support the use of `*` in a kickstart file, even if you exclude ``@Conflicts (_`variant`_)``.
The following options are available for the **%packages** option:
**--nobase**
: Do not install the @Base group. Use this option to perform a minimal installation, for example, for a single-purpose server or desktop appliance.
**--ignoremissing**
: Ignore the missing packages and groups instead of halting the installation to ask if the installation should be aborted or continued. For example:
%packages --ignoremissing
**--multilib**
: Set the `multilib_policy` in `/etc/yum.conf` to "all", so that all architectural variants of a package are installed. The default is "best", where yum only installs the most suitable architectural variant available.
**--resolvedeps**
: The --resolvedeps option has been deprecated. Dependencies are now always resolved automatically.
**--ignoredeps**
: The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
## 15\.6. Pre-installation Script {#s1-kickstart2-preinstallconfig}
You can add commands to run on the system immediately after the `ks.cfg` has been parsed. This section must be placed towards the end of the kickstart file, after the kickstart commands described in [Section 15.4, “Kickstart Options”](#s1-kickstart2-options "15.4. Kickstart Options"), and must start with the **%pre** command. If your kickstart file also includes a **%post** section, the order of the **%pre** and **%post** sections does not matter.
You can access the network in the **%pre** section; however, _name service_ has not been configured at this point, so only IP addresses work.
### Note
Note that the pre-install script is not run in the change root environment.
**--interpreter _`/usr/bin/python`_**
: Allows you to specify a different scripting language, such as Python. Replace _`/usr/bin/python`_ with the scripting language of your choice.
### 15\.6.1. Example {#s2-kickstart2-prescript-example}
Here is an example **%pre** section:
%pre
#!/bin/sh
hds=""
mymedia=""
for file in /proc/ide/h* do
mymedia=`cat $file/media`
if [ $mymedia == "disk" ] ; then
hds="$hds `basename $file`"
fi
done
set $hds
numhd=`echo $#`
drive1=`echo $hds | cut -d' ' -f1`
drive2=`echo $hds | cut -d' ' -f2`
#Write out partition scheme based on whether there are 1 or 2 hard drives
if [ $numhd == "2" ] ; then
#2 drives
echo "#partitioning scheme generated in %pre for 2 drives" > /tmp/part-include
echo "clearpart --all" >> /tmp/part-include
echo "part /boot --fstype ext3 --size 75 --ondisk hda" >> /tmp/part-include
echo "part / --fstype ext3 --size 1 --grow --ondisk hda" >> /tmp/part-include
echo "part swap --recommended --ondisk $drive1" >> /tmp/part-include
echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" >> /tmp/part-include
else
#1 drive
echo "#partitioning scheme generated in %pre for 1 drive" > /tmp/part-include
echo "clearpart --all" >> /tmp/part-include
echo "part /boot --fstype ext3 --size 75" >> /tmp/part-include
echo "part swap --recommended" >> /tmp/part-include
echo "part / --fstype ext3 --size 2048" >> /tmp/part-include
echo "part /home --fstype ext3 --size 2048 --grow" >> /tmp/part-include
fi
This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the kickstart file, include the line:
%include /tmp/part-include
The partitioning commands selected in the script are used.
### Note
The pre-installation script section of kickstart _cannot_ manage multiple install trees or source media. This information must be included for each created ks.cfg file, as the pre-installation script occurs during the second stage of the installation process.
## 15\.7. Post-installation Script {#s1-kickstart2-postinstallconfig}
You have the option of adding commands to run on the system once the installation is complete. This section must be placed towards the end of the kickstart file, after the kickstart commands described in [Section 15.4, “Kickstart Options”](#s1-kickstart2-options "15.4. Kickstart Options"), and must start with the **%post** command. If your kickstart file also includes a **%pre** section, the order of the **%pre** and **%post** sections does not matter.
This section is useful for functions such as installing additional software and configuring an additional nameserver.
### Note
If you configured the network with static IP information, including a nameserver, you can access the network and resolve IP addresses in the **%post** section. If you configured the network for DHCP, the `/etc/resolv.conf` file has not been completed when the installation executes the **%post** section. You can access the network, but you can not resolve IP addresses. Thus, if you are using DHCP, you must specify IP addresses in the **%post** section.
### Note
The post-install script is run in a chroot environment; therefore, performing tasks such as copying scripts or RPMs from the installation media do not work.
**--nochroot**
: Allows you to specify commands that you would like to run outside of the chroot environment.
The following example copies the file `/etc/resolv.conf` to the file system that was just installed.
%post --nochroot
cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
**--interpreter _`/usr/bin/python`_**
: Allows you to specify a different scripting language, such as Python. Replace _`/usr/bin/python`_ with the scripting language of your choice.
**--log _`/path/to/logfile`_**
: Logs the output of the post-install script. Note that the path of the log file must take into account whether or not you use the `--nochroot` option. For example, without `--nochroot`:
%post --log=/root/ks-post.log
with `--nochroot`:
%post --nochroot --log=/mnt/sysimage/root/ks-post.log
### 15\.7.1. Example {#s2-kickstart2-post-examples}
Example 15.1. Run a script named `runme` from an NFS share:
mkdir /mnt/temp
mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp
openvt -s -w -- /mnt/temp/runme
umount /mnt/temp
NFS file locking is _not_ supported while in kickstart mode, therefore **-o nolock** is required when mounting an NFS mount.
`_**
: Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier".
**dns=_``_**
: Comma separated list of nameservers to use for a network installation.
**driverdisk**
: Same as 'dd'.
**expert**
: Turns on special features:
* allows partitioning of removable media
* prompts for a driver disk
**gateway=_``_**
: Gateway to use for a network installation.
**graphical**
: Force graphical install. Required to have ftp/http use GUI.
**isa**
: Prompt user for ISA devices configuration.
**ip=_``_**
: IP to use for a network installation, use 'dhcp' for DHCP.
**ipv6=auto**, **ipv6=dhcp**
: IPv6 configuration for the device. Use `auto` to specify automatic neighbor discovery or `dhcp` for a stateful configuration with DHCPv6. You cannot specify a static IPv6 address.
**keymap=_``_**
: Keyboard layout to use. Valid layouts include:
* `be-latin1` — Belgian
* `bg_bds-utf8` — Bulgarian
* `bg_pho-utf8` — Bulgarian (Phonetic)
* `br-abnt2` — Brazilian (ABNT2)
* `cf` — French Canadian
* `croat` — Croatian
* `cz-us-qwertz` — Czech
* `cz-lat2` — Czech (qwerty)
* `de` — German
* `de-latin1` — German (latin1)
* `de-latin1-nodeadkeys` — German (latin1 without dead keys)
* `dvorak` — Dvorak
* `dk` — Danish
* `dk-latin1` — Danish (latin1)
* `es` — Spanish
* `et` — Estonian
* `fi` — Finnish
* `fi-latin1` — Finnish (latin1)
* `fr` — French
* `fr-latin9` — French (latin9)
* `fr-latin1` — French (latin1)
* `fr-pc` — French (pc)
* `fr_CH` — Swiss French
* `fr_CH-latin1` — Swiss French (latin1)
* `gr` — Greek
* `hu` — Hungarian
* `hu101` — Hungarian (101 key)
* `is-latin1` — Icelandic
* `it` — Italian
* `it-ibm` — Italian (IBM)
* `it2` — Italian (it2)
* `jp106` — Japanese
* `ko` — Korean
* `la-latin1` — Latin American
* `mk-utf` — Macedonian
* `nl` — Dutch
* `no` — Norwegian
* `pl2` — Polish
* `pt-latin1` — Portuguese
* `ro` — Romanian
* `ru` — Russian
* `sr-cy` — Serbian
* `sr-latin` — Serbian (latin)
* `sv-latin1` — Swedish
* `sg` — Swiss German
* `sg-latin1` — Swiss German (latin1)
* `sk-qwerty` — Slovak (qwerty)
* `slovene` — Slovenian
* `trq` — Turkish
* `uk` — United Kingdom
* `ua-utf` — Ukrainian
* `us-acentos` — U.S. International
* `us` — U.S. English
The file `/usr/lib/python2.6/site-packages/system_config_keyboard/keyboard_models.py` on 32-bit systems or `/usr/lib64/python2.6/site-packages/system_config_keyboard/keyboard_models.py` on 64-bit systems also contains this list and is part of the system-config-keyboard package.
**ks=nfs:_``_:/_``_**
: The installation program looks for the kickstart file on the NFS server _``_, as file _``_. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share `/mydir/ks.cfg`, the correct boot command would be **ks=nfs:server.example.com:/mydir/ks.cfg**.
**ks=http://_``_/_``_**
: The installation program looks for the kickstart file on the HTTP server _``_, as file _``_. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory `/mydir/ks.cfg`, the correct boot command would be **ks=http://server.example.com/mydir/ks.cfg**.
**ks=hd:_``_:/_``_**
: The installation program mounts the file system on _``_ (which must be vfat or ext2), and looks for the kickstart configuration file as _``_ in that file system (for example, **ks=hd:sda3:/mydir/ks.cfg**).
**ks=bd:_``_:/_``_**
: The installation program mounts the file system on the specified partition on the specified BIOS device _``_, and looks for the kickstart configuration file specified in _``_ (for example, **ks=bd:80p3:/mydir/ks.cfg**). Note this does not work for BIOS RAID sets.
**ks=file:/_``_**
: The installation program tries to read the file _``_ from the file system; no mounts are done. This is normally used if the kickstart file is already on the `initrd` image.
**ks=cdrom:/_``_**
: The installation program looks for the kickstart file on CD-ROM, as file _``_.
**ks**
: If **ks** is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from NFS server specified by DHCP option server-name. The name of the kickstart file is one of the following:
* If DHCP is specified and the boot file begins with a `/`, the boot file provided by DHCP is looked for on the NFS server.
* If DHCP is specified and the boot file begins with something other than a `/`, the boot file provided by DHCP is looked for in the `/kickstart` directory on the NFS server.
* If DHCP did not specify a boot file, then the installation program tries to read the file `/kickstart/1.2.3.4-kickstart`, where _`1.2.3.4`_ is the numeric IP address of the machine being installed.
**ksdevice=_``_**
: The installation program uses this network device to connect to the network. You can specify the device in one of five ways:
* the device name of the interface, for example, `eth0`
* the MAC address of the interface, for example, `00:12:34:56:78:9a`
* the keyword `link`, which specifies the first interface with its link in the `up` state
* the keyword `bootif`, which uses the MAC address that pxelinux set in the _`BOOTIF`_ variable. Set `IPAPPEND 2` in your `pxelinux.cfg` file to have pxelinux set the _`BOOTIF`_ variable.
* the keyword `ibft`, which uses the MAC address of the interface specified by iBFT
For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command **ks=nfs:_``_:/_``_ ksdevice=eth1** at the `boot:` prompt.
**kssendmac**
: Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems. Includes MAC address of all nics in CGI environment variables of the form: "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".
**lang=_``_**
: Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command.
**loglevel=_``_**
: Set the minimum level required for messages to be logged. Values for <level> are debug, info, warning, error, and critical. The default value is info.
**mediacheck**
: Activates loader code to test integrity of install source (if an ISO-based method).
**netmask=_``_**
: Netmask to use for a network installation.
**nofallback**
: If GUI fails exit.
**nofb**
: Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
**nofirewire**
: Do not load support for firewire devices.
**noipv6**
: Disable IPv6 networking during installation.
### This option is not available during PXE installations
During installations from a PXE server, IPv6 networking might become active before anaconda processes the Kickstart file. If so, this option will have no effect during installation.
**nomount**
: Don't automatically mount any installed Linux partitions in rescue mode.
**nonet**
: Do not auto-probe network devices.
**noparport**
: Do not attempt to load support for parallel ports.
**nopass**
: Do not pass information about the keyboard and mouse from anaconda stage 1 (the loader) to stage 2 (the installer).
**nopcmcia**
: Ignore PCMCIA controller in system.
**noprobe**
: Do not automatically probe for hardware; prompt the user to allow anaconda to probe for particular categories of hardware.
**noshell**
: Do not put a shell on tty2 during install.
**repo=cdrom**
: Do a DVD based installation.
**repo=ftp://_``_**
: Use <path> for an FTP installation.
**repo=hd:_``_:_``_**
: Use <path> on <dev> for a hard drive installation.
**repo=http://_``_**
: Use <path> for an HTTP installation.
**repo=nfs:_``_**
: Use <path> for an NFS installation.
**rescue**
: Run rescue environment.
**resolution=_``_**
: Run installer in mode specified, '1024x768' for example.
**serial**
: Turns on serial console support.
**skipddc**
: Do not probe the _Data Display Channel_ (DDC) of the monitor. This option provides a workaround if the DDC probe causes the system to stop responding.
**syslog=_``_[:_``_]**
: Once installation is up and running, send log messages to the syslog process on _``_, and optionally, on port _``_. Requires the remote syslog process to accept connections (the -r option).
**text**
: Force text mode install.
### Important
If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and anaconda cannot prompt you for missing information. If you do not provide choices for these options, anaconda will stop the installation process.
**updates**
: Prompt for storage device containing updates (bug fixes).
**updates=ftp://_``_**
: Image containing updates over FTP.
**updates=http://_``_**
: Image containing updates over HTTP.
**upgradeany**
: Offer to upgrade any Linux installation detected on the system, regardless of the contents or the existence of the `/etc/redhat-release` file.
**vnc**
: Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
**vncconnect=_``_[:_``_]**
: Connect to the vnc client named _``_, and optionally use port _``_.
Requires 'vnc' option to be specified as well.
**vncpassword=_``_**
: Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
Requires 'vnc' option to be specified as well.
## Chapter 16. Kickstart Configurator {#ch-redhat-config-kickstart}
Kickstart Configurator allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file.
Kickstart Configurator is not installed by default on Fedora 20. Run **su - yum install system-config-kickstart** or use your graphical package manager to install the software.
To launch Kickstart Configurator, boot your system into a graphical environment, then run **system-config-kickstart**, or click Applications → System Tools → Kickstart on the GNOME desktop or Kickoff Application Launcher+Applications → System → Kickstart on the KDE desktop.
As you are creating a kickstart file, you can click File → Preview at any time to review your current selections.
To start with an existing kickstart file, select File → Open and select the existing file.
## 16\.1. Basic Configuration {#s1-redhat-config-kickstart-basic}
Figure 16.1. Basic Configuration
![Basic Configuration][51]
Fedora Project RSS feeds
:
* The documents available from the Fedora Documentation Project Web site
: aggregates posts from many members of the Fedora community, and you can find helpful content there often.
You can also visit to participate in `Question and Answer` style support with the Fedora community.
## 17\.5. Joining the Fedora Community {#sn-community}
The Fedora Project is driven by the individuals that contribute to it. Community members provide support and documentation to other users, help to improve the software included in Fedora by testing, and develop new software alongside the programmers employed by Red Hat. The results of this work are available to all.
To make a difference, start here:
and the relevant Fedora Wiki page at [http://fedoraproject.org/wiki/GRUB\_2](http://fedoraproject.org/wiki/GRUB_2) for more information.
### Legacy versions of Microsoft operating systems
Fdisk, the disk partitioning tool provided with MS-DOS and Microsoft Windows, is unable to remove the file systems used by Fedora. MS-DOS and versions of Windows prior to Windows XP (except for Windows 2000) have no other means of removing or modifying partitions. Refer to [Section 19.3, “Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows”](#sn-x86-uninstall-legacy "19.3. Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows") for alternative removal methods for use with MS-DOS and these versions of Windows.
## 19\.1. Fedora is the only operating system on the computer {#sn-x86-uninstall-single}
If Fedora is the only operating system on your computer, use the installation media for the replacement operating system to remove Fedora. Examples of installation media include the Windows XP installation CD, Windows Vista installation DVD, or the installation CD, CDs, or DVD of another Linux distribution.
Note that some manufacturers of factory-built computers pre-installed with Microsoft Windows do not supply the Windows installation CD or DVD with the computer. The manufacturer may instead have supplied their own "system restore disk", or have included software with the computer that allowed you to create your own "system restore disk" when you first started the computer. In some cases, the system restore software is stored on a separate partition on the system's hard drive. If you cannot identify the installation media for an operating system that was pre-installed on your computer, consult the documentation supplied with the machine, or contact the manufacturer.
When you have located the installation media for your chosen operating system:
1. Back up any data that you want to keep.
1. Shut down the computer.
1. Boot your computer with the installation disk for the replacement operating system.
1. Follow the prompts presented during the installation process. Windows, OS X, and most Linux installation disks allow you to manually partition your hard drive during the installation process, or will offer you the option to remove all partitions and start with a fresh partition scheme. At this point, remove any existing partitions that the installation software detects or allow the installer to remove the partitions automatically. "System restore" media for computers pre-installed with Microsoft Windows might create a default partition layout automatically without input from you.
### Warning
If your computer has system restore software stored on a partition on a hard drive, take care when removing partitions while installing an operating system from other media. Under these circumstances, you could destroy the partition holding the system restore software.
## 19\.2. Your computer dual-boots Fedora and another operating system {#sn-x86-uninstall-dual}
If your computer is configured to dual-boot Fedora and another operating system, removing Fedora without removing the partitions containing the other operating system and its data is more complicated. Specific instructions for a number of operating systems are set out below. To keep neither Fedora nor the other operating system, follow the steps described for a computer with only Fedora installed: [Section 19.1, “Fedora is the only operating system on the computer”](#sn-x86-uninstall-single "19.1. Fedora is the only operating system on the computer")
### 19\.2.1. Your computer dual-boots Fedora and a Microsoft Windows operating system {#sn-x86-uninstall-dual-windows}
#### 19\.2.1.1. Windows 2000, Windows Server 2000, Windows XP, and Windows Server 2003 {#sn-x86-uninstall-dual-windows-2000xp2003}
### Warning
Once you commence this process, your computer may be left in an unbootable state until you complete the entire set of instructions. Carefully read the steps below before beginning the removal process. Consider opening these instructions on another computer or printing them so that you have access to them at all times during the process.
This procedure relies on the Windows Recovery Console that loads from the Windows installation disk, so you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the Windows Recovery Console.
During the process outlined in these instructions, the Windows Recovery Console will prompt you for the Administrator password for your Windows system. Do not follow these instructions unless you know the Administrator password for your system or are certain that an Administrator password has never been created, even by the computer manufacturer.
1. Remove the Fedora partitions
1. Boot your computer into your Microsoft Windows environment.
1. Click Start>Run..., type **diskmgmt.msc** and press **Enter**. The Disk Management tool opens.
The tool displays a graphical representation of your disk, with bars representing each partition. The first partition is usually labeled `NTFS` and corresponds to your `C:` drive. At least two Fedora partitions will be visible. Windows will not display a file system type for these partitions, but may allocate drive letters to some of them.
1. Right-click on one of the Fedora partitions, then click Delete Partition and click Yes to confirm the deletion. Repeat this process for the other Fedora partitions on your system. As you delete partitions, Windows labels the space on the hard drive previously occupied by those partitions as `unallocated`.
1. Enable Windows to use the space on your hard drive vacated by Fedora (optional)
### Note
This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a significant portion of the storage capacity of the drive.
Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.
Extending an existing Windows partition
### Note
The diskpart tool used in this step is installed as part of the Windows XP and Windows 2003 operating systems. If you are performing this step on a computer running Windows 2000 or Windows Server 2000, you can download a version of diskpart for your operating system from the Microsoft website.
1. Click Start>Run..., type **diskpart** and press **Enter**. A command window appears.
1. Type **list volume** and press **Enter**. Diskpart displays a list of the partitions on your system with a volume number, its drive letter, volume label, filesystem type, and size. Identify the Windows partition that you would like to use to occupy the space vacated on your hard drive by Fedora and take note of its volume number (for example, your Windows `C:` drive might be "Volume 0").
1. Type **select volume _`N`_** (where _`N`_ is the volume number for the Windows partition that you want to extend) and press **Enter**. Now type **extend** and press **Enter**. Diskpart now extends your chosen partition to fill the remaining space on your hard drive. It will notify you when the operation is complete.
Adding a new Windows partition
1. In the `Disk Management` window, right-click on disk space that Windows labels as `unallocated` and select `New Partition` from the menu. The New Partition Wizard starts.
1. Follow the prompts presented by the New Partition Wizard. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
1. Restore the Windows bootloader
1. Insert the Windows installation disk and restart your computer. As your computer starts, the following message will appear on the screen for a few seconds:
Press any key to boot from CD
Press any key while the message is still showing and the Windows installation software will load.
1. When the `Welcome to Setup` screen appears, you can start the Windows Recovery Console. The procedure is slightly different on different versions of Windows:
* On Windows 2000 and Windows Server 2000, press the **R** key, then the **C** key.
* On Windows XP and Windows Server 2003, press the **R** key.
1. The Windows Recovery Console scans your hard drives for Windows installations, and assigns a number to each one. It displays a list of Windows installations and prompts you to select one. Type the number corresponding to the Windows installation that you want to restore.
1. The Windows Recovery Console prompts you for the Administrator password for your Windows installation. Type the Administrator password and press the **Enter** key. If there is no administrator password for this system, press only the **Enter** key.
1. At the prompt, type the command **fixmbr** and press the **Enter**. The fixmbr tool now restores the Master Boot Record for the system.
1. When the prompt reappears, type **exit** and press the **Enter** key.
1. Your computer will restart and boot your Windows operating system.
#### 19\.2.1.2. Windows Vista and Windows Server 2008 {#sn-x86-uninstall-dual-windows-vista2008}
### Warning
Once you commence this process, your computer may be left in an unbootable state until you complete the entire set of instructions. Carefully read the steps below before beginning the removal process. Consider opening these instructions on another computer or printing them so that you have access to them at all times during the process.
This procedure relies on the Windows Recovery Environment that loads from the Windows installation disk and you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the Windows Recovery Environment.
1. Remove the Fedora partitions
1. Boot your computer into your Microsoft Windows environment.
1. Click Start then type **diskmgmt.msc** into the Start Search box and press **Enter**. The Disk Management tool opens.
The tool displays a graphical representation of your disk, with bars representing each partition. The first partition is usually labeled `NTFS` and corresponds to your `C:` drive. At least two Fedora partitions will be visible. Windows will not display a file system type for these partitions, but may allocate drive letters to some of them.
1. Right-click on one of the Fedora partitions, then click Delete Partition and click Yes to confirm the deletion. Repeat this process for the other Fedora partitions on your system. As you delete partitions, Windows labels the space on the hard drive previously occupied by those partitions as `unallocated`.
1. Enable Windows to use the space on your hard drive vacated by Fedora (optional)
### Note
This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a significant portion of the storage capacity of the drive.
Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.
Extending an existing Windows partition
1. In the Disk Management window, right-click on the Windows partition that you want to extend and select Extend Volume from the menu. The Extend Volume Wizard opens.
1. Follow the prompts presented by the Extend Volume Wizard. If you accept the defaults that it offers you, the tool will extend the selected volume to fill all available space on the hard drive.
Adding a new Windows partition
1. In the `Disk Management` window, right-click on disk space that Windows labels as `unallocated` and select `New Simple Volume` from the menu. The New Simple Volume Wizard starts.
1. Follow the prompts presented by the New Simple Volume Wizard. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
1. Restore the Windows bootloader
1. Insert the Windows installation disk and restart your computer. As your computer starts, the following message will appear on the screen for a few seconds:
Press any key to boot from CD or DVD
Press any key while the message is still showing and the Windows installation software will load.
1. In the Install Windows dialog, select a language, time and currency format, and keyboard type. Click Next
1. Click Repair your computer.
1. The Windows Recovery Environment (WRE) shows you the Windows installations that it can detect on your system. Select the installation that you want to restore, then click Next.
1. Click Command prompt. A command window will open.
1. Type **bootrec /fixmbr** and press **Enter**.
1. When the prompt reappears, close the command window, then click Restart.
1. Your computer will restart and boot your Windows operating system.
### 19\.2.2. Your computer dual-boots Fedora and Mac OS X {#sn-x86-uninstall-dual-mac}
The procedure to remove Fedora from a system that dual-boots Fedora and Mac OS X varies depending on whether you have installed Boot Camp on your computer:
You are not using Boot Camp on your computer
1. Open the Disk Utility in `/Applications/Utilities`.
1. Select the entry on the left for the disk volume containing Fedora.
1. Click the Partition tab on the right side of the dialog.
1. Select the Fedora partitions and click the minus button below the partition layout diagram.
1. Resize your OS X partition to include the newly freed space.
You are using Boot Camp on your computer
1. Open the Boot Camp Assistant in `/Applications/Utilities`.
1. Select Create or remove a Windows partition and click Next.
1. If your computer has a single internal disk, click Restore.
1. If your computer has multiple internal disks, select the Linux disk, and then select Restore to a single Mac OS partition. Click Continue.
### 19\.2.3. Your computer dual-boots Fedora and a different Linux distribution {#sn-x86-uninstall-dual-linux}
Because of the differences between the many different Linux distributions, these instructions are a general guide only. Specific details vary according to he configuration of your particular system and the Linux distribution that dual-boots with Fedora.
1. Procedure 19.1. Remove Fedora partitions
1. Boot your Fedora installation.
1. As root or with sudo, run mount. Note the partitions that are mounted. In particular, note the partition that is mounted as the root of the filesystem. The output of **mount** on a system where the root of the filesystem is on a standard partition such as `/dev/sda2` might resemble:
/dev/sda2 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
The output of **mount** on a system where the root of the filesystem is on a logical volume might resemble:
/dev/mapper/VolGroup00-LogVol00 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
1. Ensure that any data on this system that you still require is backed up to another system or storage location.
1. Shut down the system and boot the Linux distribution that you want to keep on the system.
1. As root or with sudo, run mount. If any of the partitions that you previously noted as used for Fedora are mounted, review the contents of these partitions. If you no longer require the contents of these partitions, unmount them with the **umount** command.
1. Remove any unwanted and unnecessary partitions, for example, with fdisk for standard partitions, or lvremove and vgremove to remove logical volumes and volume groups.
1. Remove Fedora entries from your bootloader
### Example only
These instructions assume that your system uses the GRUB bootloader. If you use a different bootloader (such as LILO) consult the documentation for that software to identify and remove Fedora entries from its list of boot targets and to ensure that your default operating system is correctly specified.
1. At the command line, type **su -** and press **Enter**. When the system prompts you for the root password, type the password and press **Enter**.
1. Type **gedit etc/grub.d/10\_linux** and press **Enter**. This opens the `10_linux` file in the gedit text editor.
1. A typical Fedora entry in the `10_linux` file consists of four lines:
Example 19.1. Example Fedora entry in `10_linux`
menuentry "Fedora (2.6.32.130.el6.i686)"
set root=(hd0,1)
linux /vmlinuz-2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet
initrd /initrd-2.6.32.130.el6.i686.img
`, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device.
To see some information about the mapped device, use the following command:
dmsetup info <name>
### Tip
For more information, read the **dmsetup(8)** man page.
### C.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device {#idp17031392}
Use the mapped device node (`/dev/mapper/`) as any other block device. To create an **ext2** filesystem on the mapped device, use the following command:
mke2fs /dev/mapper/<name>
To mount this filesystem on `/mnt/test`, use the following command:
### Important
The directory `/mnt/test` must exist before executing this command.
mount /dev/mapper/<name> /mnt/test
### C.4.6. Add the mapping information to `/etc/crypttab` {#idp9381296}
In order for the system to set up a mapping for the device, an entry must be present in the `/etc/crypttab` file. If the file doesn't exist, create it and change the owner and group to root (**root:root**) and change the mode to **0744**. Add a line to the file with the following format:
<name> <device> none
The <device> field should be given in the form "UUID=<luks\_uuid>", where <luks\_uuid> is the LUKS uuid as given by the command **cryptsetup luksUUID <device>**. This ensures the correct device will be identified and used even if the device node (eg: `/dev/sda5`) changes.
### Tip
For details on the format of the `/etc/crypttab` file, read the **crypttab(5)** man page.
### C.4.7. Add an entry to `/etc/fstab` {#idp74345568}
Add an entry to /etc/fstab. This is only necessary if you want to establish a persistent association between the device and a mountpoint. Use the decrypted device, `/dev/mapper/` in the `/etc/fstab` file.
In many cases it is desirable to list devices in `/etc/fstab` by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: `/dev/sda4`) changes. LUKS device names in the form of `/dev/mapper/luks-` are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in `/etc/fstab`.
### Title
For details on the format of the `/etc/fstab` file, read the **fstab(5)** man page.
## C.5. Common Post-Installation Tasks {#idm13543632}
The following sections are about common post-installation tasks.
### C.5.1. Set a randomly generated key as an additional way to access an encrypted block device {#new_key}
These sections are about generating keys and adding keys.
#### C.5.1.1. Generate a key {#idp22331632}
This will generate a 256-bit key in the file `$HOME/keyfile`.
dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1
chmod 600 $HOME/keyfile
#### C.5.1.2. Add the key to an available keyslot on the encrypted device {#idp14859392}
cryptsetup luksAddKey <device> ~/keyfile
### C.5.2. Add a new passphrase to an existing device {#idp13033312}
cryptsetup luksAddKey <device>
After being prompted for any one of the existing passphrases for authentication, you will be prompted to enter the new passphrase.
### C.5.3. Remove a passphrase or key from a device {#idp71358352}
cryptsetup luksRemoveKey <device>
You will be prompted for the passphrase you wish to remove and then for any one of the remaining passphrases for authentication.
## Appendix D. Understanding LVM {#sn-partitioning-lvm}
LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as _physical volumes_. One or more physical volumes are combined to form a _volume group_. Each volume group's total storage is then divided into one or more _logical volumes_. The logical volumes function much like standard partitions. They have a file system type, such as `ext4`, and a mount point.
To understand LVM better, imagine the physical volume as a pile of _blocks_. A block is simply a storage unit used to store data. Several piles of blocks can be combined to make a much larger pile, just as physical volumes are combined to make a volume group. The resulting pile can be subdivided into several smaller piles of arbitrary size, just as a volume group is allocated to several logical volumes.
An administrator may grow or shrink logical volumes without destroying data, unlike standard disk partitions. If the physical volumes in a volume group are on separate drives or RAID arrays then administrators may also spread a logical volume across the storage devices.
You may lose data if you shrink a logical volume to a smaller capacity than the data on the volume requires. To ensure maximum flexibility, create logical volumes to meet your current needs, and leave excess storage capacity unallocated. You may safely grow logical volumes to use unallocated space, as your needs dictate.
### LVM and the Default Partition Layout
By default, the installation process creates `/` and swap partitions within LVM volumes, with a separate `/boot` partition.
## Appendix E. Logging the Installation {#anaconda_logging}
Anaconda tracks all of its activities in logs. This includes:
* Changing installation steps. The steps roughly correspond to the different screens in the graphical installer.
* Detection and manipulation of storage devices.
* Installation media detection.
* Network initialization.
* Kernel messages
* Calls to critical methods within anaconda.
* Calls to external programs.
## E.1. Log files and formats {#anaconda_logging-logformats}
### E.1.1. Logging on the installed system {#anaconda_logging-logformats-files}
During the installation, logs are stored in the `/tmp` directory. After the installation, the files can be found in the `/var/log/anaconda` directory. Another set of logs is stored in in the `/root` directory of the target filesystem, and can be found at `/mnt/sysimage/root` during the installation. Some logs are also written to the virtual terminals.
Table E.1. anaconda log files
|Logs in /tmp, /var/log/anaconda|
|Filename|TTY|Usage|
|-|
|`anaconda.log`|`/dev/tty3`|General installation information, including the step changes.|
|`storage.log`|`/dev/tty3`|Detection and manipulation of storage devices, including RAID, LVM, and partitioning actions.|
|`program.log`||Calls to external programs, and their output.|
|`syslog`|`/dev/tty4`|Messages from the kernel and external programs, such as NetworkManager.|
|`yum.log`||Yum's internal log.||Logs in /root, /mnt/sysimage/root|
|Filename|Usage|
|-|
|`install.log`|The log of the package installation process|
|`install.log.syslog`|Messages from installation chroot logged through the system's syslog. Mostly information about users and groups created during yum's package installation.|
` section:
<channel type='tcp'>
<source mode='connect' host='127.0.0.1' service='6080'/>
<target type='virtio' name='org.fedoraproject.anaconda.log.0'/>
</channel>
### E.2.3. Listening for `virtio` logs {#anaconda_logging-virtio_listening}
Start the listening rsyslogd on the host:
** eval `analog -p 6080 -o rsyslogd.conf -s _`/path/to/logdir`_` **
Or, view the raw logs using nc
** nc -l 0.0.0.0 6080 **
rsyslog is also used in this way for `tcp` logging, but separate rsyslog instances must be used if logging by both methods.
## Appendix F. Other Technical Documentation {#ap-techref}
To learn more about anaconda, the Fedora installation program, visit the project Web page: .
Both **anaconda** and Fedora systems use a common set of software components. For detailed information on key technologies, refer to the Web sites listed below:
Boot Loader
: Fedora uses the **GRUB** boot loader. Refer to .
Graphics System
: Both the installation system and Fedora use the **Xorg** suite to provide graphical capabilities. Components of **Xorg** manage the display, keyboard and mouse for the desktop environments that users interact with. Refer to .
Command-line Interface
: By default, Fedora uses the GNU **bash** shell to provide a command-line interface. The GNU Core Utilities complete the command-line environment. Refer to for more information on **bash**. To learn more about the GNU Core Utilities, refer to .
Firewall
: The Linux kernel used by Fedora incorporates the **netfilter** framework to provide firewall features. The Netfilter project website provides documentation for both **netfilter**, and the **iptables** administration facilities: .
Software Installation
: Fedora uses **yum** to manage the RPM packages that make up the system. Refer to