Made with PublicanCompany Website

Fedora Draft Documentation

Руководство по установке

Установка Fedora 17 на архитектуры x86, AMD64 и Intel 64

Редакция 17.0.1

Команда документации Fedora

Fedora Документация


Юридическое уведомление

Copyright © 2012 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 http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/Legal:Trademark_guidelines.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
All other trademarks are the property of their respective owners.
Аннотация
Руководство по процессу установки.

Preface
1. Соглашения документа
1.1. Типографические соглашения
1.2. Соглашения по выделению текста
1.3. Примечания и предупреждения
2. Нам нужны ваши отзывы!
3. Acknowledgments
Введение
1. Предыстория
1.1. О Fedora
1.2. Получение дополнительно помощи
2. Об этом руководстве
2.1. Цели
2.2. Аудитория
1. Quick Start for Experts
1.1. Overview
1.2. Download Files
1.3. Prepare for Installation
1.4. Install Fedora
1.5. Perform Post-installation Steps
2. Получение Fedora
2.1. Загрузка Fedora
2.1.1. Как загрузить установочные файлы?
2.1.2. Как узнать архитектуру моего компьютера?
2.1.3. Какие файлы нужно загрузить?
2.2. Получение Fedora на CD/DVD
3. Making Media
3.1. Making an installation DVD
3.2. Preparing a USB flash drive as an installation source
3.2.1. Making Fedora USB Media on a Windows Operating System
3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems
3.3. Making Minimal Boot Media
3.3.1. UEFI-based systems
I. Installation and Booting
4. Планирование установки на платформе x86
4.1. Upgrade or Install?
4.2. Is Your Hardware Compatible?
4.3. RAID and Other Disk Devices
4.3.1. Hardware RAID
4.3.2. Software RAID
4.3.3. FireWire and USB Disks
4.4. Достаточно ли дискового пространства?
4.5. Selecting an Installation Method
4.6. Choose a boot method
5. Preparing for Installation
5.1. Preparing for a Network Installation
5.1.1. Preparing for FTP and HTTP installation
5.1.2. Подготовка к NFS-установке
5.2. Preparing for a Hard Drive Installation
6. System Specifications List
7. Booting the Installer
7.1. Starting the Installation Program
7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems
7.1.2. The Boot Menu
7.1.3. Additional Boot Options
7.2. Booting from the Network using PXE
8. Configuring Installation Source
8.1. Installation Method
8.1.1. Installing from DVD
8.1.2. Installing from a Hard Drive
8.1.3. Installing via NFS
8.1.4. Installing via FTP or HTTP
9. Installing using anaconda
9.1. The Text Mode Installation Program User Interface
9.1.1. Using the Keyboard to Navigate
9.2. The Graphical Installation Program User Interface
9.2.1. Screenshots during installation
9.2.2. A Note about Virtual Consoles
9.3. Language Selection
9.4. The Pre-Installation Hub
9.5. Configuring date and time
9.6. Keyboard Configuration
9.7. Language Selection
9.8. Installation Source
9.9. Network configuration
9.9.1. Изменение сетевых подключений
9.10. Software Selection
9.10.1. Installing from Additional Repositories
9.10.2. Core Network Services
9.11. Устройства хранения
9.11.1. Окно выбора устройств хранения
9.12. Assign Storage Devices
9.13. Initializing the Hard Disk
9.14. Upgrading an Existing System
9.14.1. Экран обновления системы
9.14.2. Upgrading Using the Installer
9.14.3. Upgrading Boot Loader Configuration
9.15. Disk Partitioning Setup
9.16. Encrypt Partitions
9.17. Creating a Custom Layout or Modifying the Default Layout
9.17.1. Create Storage
9.17.2. Adding Partitions
9.17.3. Create Software RAID
9.17.4. Create LVM Logical Volume
9.17.5. Recommended Partitioning Scheme
9.18. Write changes to disk
9.19. Настройка загрузчика на платформах x86, AMD64 и Intel 64
9.19.1. Advanced Boot Loader Configuration
9.19.2. Rescue Mode
9.19.3. Alternative Boot Loaders
9.20. The Progress Hub
9.20.1. Set the Root Password
9.21. Installation Complete
10. Диагностика проблем при установке в системах Intel и AMD
10.1. Невозможно загрузить Fedora
10.1.1. Are You Unable to Boot With Your RAID Card?
10.1.2. Is Your System Displaying Signal 11 Errors?
10.2. Trouble Beginning the Installation
10.2.1. Problems with Booting into the Graphical Installation
10.3. Проблемы во время установки
10.3.1. Ошибка: Не найдены устройства для установки Fedora
10.3.2. Сохранение сообщений отладки
10.3.3. Trouble with Partition Tables
10.3.4. Using Remaining Space
10.3.5. Other Partitioning Problems
10.4. Problems After Installation
10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?
10.4.2. Blocked by a GRUB command line after upgrading?
10.4.3. Booting into a Graphical Environment
10.4.4. Problems with the X Window System (GUI)
10.4.5. Problems with the X Server Crashing and Non-Root Users
10.4.6. Problems When You Try to Log In
10.4.7. Is Your RAM Not Being Recognized?
10.4.8. Your Printer Does Not Work
10.4.9. Apache HTTP Server or Sendmail stops responding during startup
II. Advanced installation options
11. Boot Options
11.1. Configuring the Installation System at the Boot Menu
11.1.1. Specifying the Language
11.1.2. Configuring the Interface
11.1.3. Updating anaconda
11.1.4. Specifying the Installation Method
11.1.5. Specifying the Network Settings
11.2. Enabling Remote Access to the Installation System
11.2.1. Enabling Remote Access with VNC
11.2.2. Connecting the Installation System to a VNC Listener
11.2.3. Enabling Remote Access with ssh
11.3. Logging to a Remote System During the Installation
11.3.1. Configuring a Log Server
11.4. Automating the Installation with Kickstart
11.5. Enhancing Hardware Support
11.5.1. Overriding Automatic Hardware Detection
11.6. Using the Maintenance Boot Modes
11.6.1. Загрузка режима тестирования памяти (ОЗУ)
11.6.2. Verifying boot media
11.6.3. Booting Your Computer with the Rescue Mode
11.6.4. Upgrading your computer
12. Installing Without Media
12.1. Retrieving Boot Files
12.2. Editing the GRUB Configuration
12.3. Booting to Installation
13. Setting Up an Installation Server
13.1. Setting Up cobbler
13.2. Setting Up the Distribution
13.3. Mirroring a Network Location
13.4. Importing the Distribution
13.5. Manually configure a PXE server
13.5.1. Setting up the Network Server
13.5.2. PXE Boot Configuration
13.5.3. Starting the tftp Server
13.5.4. Adding a Custom Boot Message
13.5.5. Performing the PXE Installation
14. Installing Through VNC
14.1. VNC Viewer
14.2. VNC Modes in Anaconda
14.2.1. Direct Mode
14.2.2. Connect Mode
14.3. Installation Using VNC
14.3.1. Installation Example
14.3.2. Kickstart Considerations
14.3.3. Firewall Considerations
14.4. References
15. Kickstart Installations
15.1. What are Kickstart Installations?
15.2. How Do You Perform a Kickstart Installation?
15.3. Creating the Kickstart File
15.4. Kickstart Options
15.4.1. Advanced Partitioning Example
15.5. Package Selection
15.6. Pre-installation Script
15.6.1. Example
15.7. Post-installation Script
15.7.1. Example
15.8. Making the Kickstart File Available
15.8.1. Creating Kickstart Boot Media
15.8.2. Making the Kickstart File Available on the Network
15.9. Making the Installation Tree Available
15.10. Starting a Kickstart Installation
16. Kickstart Configurator
16.1. Basic Configuration
16.2. Installation Method
16.3. Boot Loader Options
16.4. Partition Information
16.4.1. Creating Partitions
16.5. Network Configuration
16.6. Authentication
16.7. Firewall Configuration
16.7.1. SELinux Configuration
16.8. Display Configuration
16.9. Package Selection
16.10. Pre-Installation Script
16.11. Post-Installation Script
16.11.1. Chroot Environment
16.11.2. Use an Interpreter
16.12. Saving the File
III. After installation
17. Firstboot
17.1. License Agreement
17.2. Create User
17.2.1. Authentication Configuration
17.3. Date and Time
17.4. Hardware Profile
18. Your Next Steps
18.1. Updating Your System
18.2. Finishing an Upgrade
18.3. Switching to a Graphical Login
18.3.1. Активация доступа к репозиториям из командной строки
18.4. Подписка на объявления и новости Fedora
18.5. Документация и поддержка
18.6. Вступление в сообщество Fedora
19. Basic System Recovery
19.1. Rescue Mode
19.1.1. Common Problems
19.1.2. Booting into Rescue Mode
19.1.3. Booting into Single-User Mode
19.1.4. Booting into Emergency Mode
19.2. Using rescue mode to fix or work around driver problems
19.2.1. Using RPM to add, remove, or replace a driver
19.2.2. Blacklisting a driver
20. Upgrading Your Current System
20.1. Determining Whether to Upgrade or Re-Install
20.2. Upgrading Your System
21. Удаление Fedora
21.1. Fedora является единственной операционной системой
21.2. Двойная загрузка: Fedora и другая операционная система
21.2.1. Настроена двойная загрузка (Fedora и Microsoft Windows)
21.2.2. Двойная загрузка: Fedora и Mac OS X
21.2.3. Двойная загрузка: Fedora и другой дистрибутив Linux
21.3. Замена Fedora ранними версиями Microsoft Windows и MS-DOS
IV. Technical appendixes
A. An Introduction to Disk Partitions
A.1. Hard Disk Basic Concepts
A.1.1. It is Not What You Write, it is How You Write It
A.1.2. Partitions: Turning One Drive Into Many
A.1.3. Partitions within Partitions — An Overview of Extended Partitions
A.1.4. Выделение места для Fedora
A.1.5. Partition Naming Scheme
A.1.6. Disk Partitions and Other Operating Systems
A.1.7. Disk Partitions and Mount Points
A.1.8. How Many Partitions?
B. ISCSI disks
B.1. iSCSI disks in anaconda
B.2. iSCSI disks during start up
C. Disk Encryption
C.1. What is block device encryption?
C.2. Encrypting block devices using dm-crypt/LUKS
C.2.1. Overview of LUKS
C.2.2. How will I access the encrypted devices after installation? (System Startup)
C.2.3. Choosing a Good Passphrase
C.3. Creating Encrypted Block Devices in Anaconda
C.3.1. What Kinds of Block Devices Can Be Encrypted?
C.3.2. Saving Passphrases
C.3.3. Creating and Saving Backup Passphrases
C.4. Creating Encrypted Block Devices on the Installed System After Installation
C.4.1. Create the block devices
C.4.2. Optional: Fill the device with random data
C.4.3. Format the device as a dm-crypt/LUKS encrypted device
C.4.4. Create a mapping to allow access to the device's decrypted contents
C.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device
C.4.6. Add the mapping information to /etc/crypttab
C.4.7. Add an entry to /etc/fstab
C.5. Common Post-Installation Tasks
C.5.1. Set a randomly generated key as an additional way to access an encrypted block device
C.5.2. Add a new passphrase to an existing device
C.5.3. Remove a passphrase or key from a device
D. Understanding LVM
E. The GRUB Boot Loader
E.1. Boot Loaders and System Architecture
E.2. GRUB
E.2.1. GRUB and the boot process on BIOS-based x86 systems
E.2.2. GRUB and the boot process on UEFI-based x86 systems
E.2.3. Features of GRUB
E.3. Installing GRUB
E.4. GRUB Terminology
E.4.1. Device Names
E.4.2. File Names and Blocklists
E.4.3. The Root File System and GRUB
E.5. GRUB Interfaces
E.5.1. Interfaces Load Order
E.6. GRUB Commands
E.7. GRUB Menu Configuration File
E.7.1. Configuration File Structure
E.7.2. Configuration File Directives
E.8. Changing Runlevels at Boot Time
E.9. Additional Resources
E.9.1. Installed Documentation
E.9.2. Useful Websites
F. Boot Process, Init, and Shutdown
F.1. The Boot Process
F.2. A Detailed Look at the Boot Process
F.2.1. The firmware interface
F.2.2. UEFI-based x86 systems
F.3. The Boot Loader
F.3.1. The GRUB2 boot loader for x86 systems
F.3.2. Boot Loaders for Other Architectures
F.4. The Kernel
F.5. Booting with systemd
F.6. systemd units
F.7. systemd targets
F.8. Running Additional Programs at Boot Time
F.9. Administering services with systemd
F.9.1. Checking up on services
F.9.2. Starting and stopping services
F.9.3. Running services automatically
F.9.4. Killing and Masking services
F.9.5. Getting more from systemd
G. Logging the Installation
G.1. Log files and formats
G.1.1. Logging on the installed system
G.2. Remote logging with rsyslog
G.3. Remote logging via virtio
H. Other Technical Documentation
I. Contributors and production methods
I.1. Contributors
I.2. Production methods
J. Revision History
Предметный указатель

Preface

1. Соглашения документа

В этом руководстве используются различные стили для выделения текста.
В PDF и бумажной версиях руководства используются шрифты семейства Liberation. Эти же шрифты будут использоваться для отображения HTML-версии, если они установлены в вашей системе. В противном случае будут использоваться аналогичные шрифты. Red Hat Enterprise Linux 5 и более поздние версии включают в свой состав комплект Liberation по умолчанию.

1.1. Типографические соглашения

Для выделения текста используются четыре стиля, которые будут перечислены далее.
Моноширинный жирный шрифт
Используется для выделения вводимого текста, включая команды оболочки, а также имен файлов, путей и комбинаций клавиш. Пример:
Чтобы просмотреть содержимое файла my_next_bestselling_novel в текущем каталоге, в строке приглашения оболочки введите cat my_next_bestselling_novel и нажмите Enter для выполнения этой команды.
Приведенный текст содержит имя файла, команду оболочки и имя клавиши, которые выделены моноширинным жирным шрифтом.
Для разделения клавиш в составе комбинаций используется дефис. Пример:
Нажмите Enter для исполнения команды.
Нажмите Ctrl+Alt+F2 для перехода в первый виртуальный терминал. Нажмите Ctrl+Alt+F1 , чтобы вернуться в сессию X-Windows.
В первом примере жирным шрифтом выделено название отдельной клавиши, во втором — комбинаций клавиш.
Этим же шрифтом выделяются имена классов, методов, функций, переменных и возвращаемые ими значения. Пример:
Классы файлов включают filesystem для файловых систем, file для файлов, dir для каталогов. Каждому классу соответствует набор разрешений.
Пропорциональный жирный
Выделяет системные слова и фразы, что включает имена приложений, текст диалогов, названия меню, текст кнопок, флажков и других элементов графического интерфейса. Пример:
В главном меню выберите СистемаПараметры Мышь для запуска утилиты Настройки мыши. На вкладке Кнопки установите флажок Настроить мышь под левую руку и нажмите кнопку Закрыть, чтобы настроить мышь для левши.
Чтобы вставить специальный символ в файл gedit, выберите ПриложенияСтандартные Таблица символов. Затем в меню выберите ПоискПоиск…, введите имя символа и нажмите кнопку Найти следующее. Найденный символ будет выделен в таблице символов. Дважды щелкните на этом символе, чтобы вставить его в поле Текст для копирования и нажмите кнопку Копировать. Теперь вернитесь к вашему документу и в меню выберите ПравкаВставить.
Приведенный выше текст содержит имя приложения, названия меню, кнопок и текста элементов графического интерфейса.
Моноширинный жирный курсив или пропорциональный жирный курсив
Оба типа выделения обозначают изменяемый или заменяемый текст. Курсив сообщает о том, что не следует вводить приведенный текст напрямую, а изменить в соответствии с вашими настройками. Пример:
Для подключения к удаленной машине с помощью SSH в строке приглашения выполните ssh имя_пользователя@имя_домена. Скажем, имя удаленной машины – example.com, а ваше имя пользователя – john, тогда команда будет выглядеть так: ssh john@example.com.
Команда mount -o remount файловая_система повторно подключит заданную файловую систему. Например, для /home команда будет выглядеть так: mount -o remount /home.
Чтобы просмотреть версию установленного пакета, выполните команду rpm -q пакет. Результат команды будет представлен в формате пакет-версия-выпуск.
В приведенных примерах жирным курсивом выделяются имя пользователя, имя домена, файловой системы, пакет, его версия и выпуск.
Также курсивом выделяются термины, которые встречаются в тексте документа впервые. Пример:
Publican — система публикации DocBook.

1.2. Соглашения по выделению текста

Вывод экрана и листинг исходного кода будут отделены от окружающего текста.
Для отображения текста, который вы увидите на экране, используется моноширинный шрифт:
books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs
Для отображения содержимого исходного кода используется моноширинный шрифт:
package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
}

1.3. Примечания и предупреждения

Наконец, чтобы привлечь внимание читателя к важной информации, используются три стиля.

Примечание

Примечания обычно содержат дополнительную информацию. Если вы их проигнорируете, это не критично, но вы можете пропустить совет, который, возможно, поможет сэкономить время при выполнении задания.

Важно

На информацию, отмеченную как важную, следует обратить особое внимание. Она может включать изменения настроек текущего сеанса или, например, перечень служб, которые нужно запустить, прежде чем обновления вступят в силу. Ознакомление с важной информацией значительно облегчит вашу работу.

Предупреждение

Не стоит игнорировать предупреждения, так как они содержат важную информацию, которая позволит избежать потери данных.

2. Нам нужны ваши отзывы!

Если вы нашли опечатку в этом руководстве, или у вас есть идеи по его усовершенствованию, мы будем рады их выслушать. Пожалуйста, оставьте сообщение в Bugzilla по адресу http://bugzilla.redhat.com/bugzilla/, выбрав компонент Fedora Documentation.
Не забудьте указать в запросе идентификатор данного руководства: install-guide.
Если у вас есть предложения по улучшению этого руководства, постарайтесь описать их как можно подробнее. Если же вы нашли ошибку, пожалуйста, укажите номер раздела и окружающий текст, чтобы мы могли быстро ее найти.

3. Acknowledgments

Certain portions of this text first appeared in the Red Hat Enterprise Linux Installation Guide, copyright © 2011 Red Hat, Inc. and others, published by Red Hat at http://docs.redhat.com/docs.

Введение

Данное руководство охватывает вопрос установки Fedora — дистрибутива Linux, созданногона основе свободного и открытого программного обеспечения. Данное руководство поможет вам установиь Fedora на рабочий компьютер, ноутбук или сервер. Программа установки проста в использовании даже, если у вас нет предварительных знаний о Linux или компьютерных сетях. Если вы выберете настройки по умолчанию, то получите готовую к использованию операционную систему, iвключающую производительные приложения и инструменты для работы.
В этом документе подробно рассматриваются все варианты настоек при установке, включая те, которые используются при очень специфических обстоятельствах. ВКраткой инструкции по установке Fedora 17 представлены более сжатые сведения о скачивании Fedora, создании установочного диска и установке Fedora на стандартный рабочий компьютер или ноутбук. Краткая инструкция по установке Fedora 17 Installation Quick Start Guide доступна по ссылке http://docs.fedoraproject.org/installation-quick-start-guide/.

1. Предыстория

1.1. О Fedora

Посетите сайт http://fedoraproject.org/, чтобы узнать больше о Fedora. Документацию по другим вопросам, связанным с Fedora, можно найти по адресу http://docs.fedoraproject.org/.

1.2. Получение дополнительно помощи

Посетите страницу http://fedoraproject.org/wiki/Communicate, чтобы узнать о том, где можно получить помощь.

2. Об этом руководстве

2.1. Цели

Данное руководство помогает читателю:
  1. Понять как определить местонахождение дистрибутива Fedora онлайн
  2. Создать конфигурацию данных, позволяющую загрузить Fedora
  3. Понять как взаимодействовать с установщиком Fedora
  4. Выполнить стандарную настройку Fedora после установки

Другие источники документации

Это руководство не охватывает вопросы использования Fedora. Чтобы узнать как работать с установленной системой Fedora, см. http://docs.fedoraproject.org/ на предмет другой документации.

2.2. Аудитория

Это руководство ориентировано на пользователей Fedora с разным опытом. Однако, процесс установки и параметры этого процесса рассматриваются в нем намного подробней, чем того бы хотели начинающие пользователи. Нет необходимости читать и понимать этот документ, чтобы установить Fedora на компьютер. Он скорее создан помочь опытным пользователям в проведении улучшенных и необычных вариантов установки.

Глава 1. Quick Start for Experts

This section offers a very brief overview of installation tasks for experienced readers who are eager to get started. Note that many explanatory notes and helpful hints appear in the following chapters of this guide. If an issue arises during the installation process, consult the appropriate chapters in the full guide for help.

Experts Only

This section is intended only for experts. Other readers may not be familiar with some of the terms in this section, and should move on to Глава 2, Получение Fedora instead.

1.1. Overview

The installation procedure is fairly simple, and consists of only a few steps:
  1. Download files to make media or another bootable configuration.
  2. Prepare system for installation.
  3. Boot the computer and run the installation process.
  4. Reboot and perform post-installation configuration.

1.2. Download Files

Do any one of the following:

Verify your downloads

Downloads may fail for any number of reasons. Always verify the sha256sum of the downloaded files.
  1. Download the ISO image for a Live image. Create CD media from the ISO file using your preferred application. You may also use the livecd-tools package to write the image to other bootable media such as a USB flash disk. To install the distribution to your hard disk, use the shortcut on the desktop after you log in.
  2. Download the ISO images for the full distribution on DVD. Create DVD media from the ISO files using your preferred application, or put the images on a Windows FAT32 or Linux ext2, ext3, or ext4 partition.
  3. Download the boot.iso image for a minimal boot CD or USB flash drive. Write the image to the approriate physical media to create bootable media. The boot media contains no packages but must be pointed at a hard disk or online repository to complete the installation.
  4. Download the vmlinuz kernel file and the initrd.img ramdisk image from the distribution's isolinux/ directory. Configure your operating system to boot the kernel and load the ramdisk image. For further information on installation without media, refer to Глава 12, Installing Without Media.
    For information on setting up a network boot server from which you can install Fedora, refer to Глава 13, Setting Up an Installation Server.
To learn how to turn ISO images into CD or DVD media, refer to Making Fedora Discs available from http://docs.fedoraproject.org/readme-burning-isos/.

1.3. Prepare for Installation

Back up any user data you need to preserve.

Resizing Partitions

The installation program provides functions for resizing ext2, ext3, ext4, and NTFS formatted partitions. Refer to Раздел 9.17, « Creating a Custom Layout or Modifying the Default Layout » for more information.

1.4. Install Fedora

Boot from the desired media, with any options appropriate for your hardware and installation mode. Refer to Глава 11, Boot Options for more information about boot options. If you boot from the Live CD, select the Install to Hard Disk option from the desktop to run the installation program. (Alternatively, the option can be found in ApplicationsSystem Tools.) If you boot from minimal media or a downloaded kernel, select a network or hard disk resource from which to install.
Proceed through all the steps of the installation program. The installation program does not change your system until you make a final confirmation to proceed. When installation is finished, reboot your system.

1.5. Perform Post-installation Steps

After the system reboots, it displays additional configuration options. Make appropriate changes to your system and proceed to the login prompt.
Refer to Глава 17, Firstboot or the Firstboot page on the Fedora wiki: http://fedoraproject.org/wiki/FirstBoot for more detail.

Глава 2. Получение Fedora

This chapter explains how to get the files you need to install and run Fedora on your computer. Concepts in this chapter may be new, especially if this is your first free and open source operating system. If you have any trouble with this chapter, find help by visiting the Fedora Forums at http://www.fedoraforum.org/.
Проект Fedora предоставляет множество способов получения дистрибутива, в большинстве своем, бесплатных и открытых для загрузки. Наиболее распространенный способ установки — с помощью CD или DVD, включая:
  • Полный комплект программ на DVD
  • Live-образы, с помощью которых можно познакомиться с Fedora, а уже потом выполнить установку, если Fedora вам понравилась
  • Загрузочные образы CD и USB-накопителей небольшого размера, с помощью которых можно выполнить установку Fedora по сети
  • Исходный код на DVD
Most users want the Fedora Live image or the full set of installable software on DVD. The reduced bootable images are suitable for use with a fast Internet connection and install Fedora on one computer. Source code discs are not used for installing Fedora, but are resources for experienced users and software developers.
Пользователи с доступом к широкополосному Интернету могут загрузить ISO-образы дисков CD/DVD или USB-носителей. ISO-образ представляет собой копию целого диска в формате, достаточном для прямой записи на CD или DVD. Образ USB — копия, готовая для записи на флэш-накопитель.
For more information on burning CDs and DVDs, refer to Глава 3, Making Media.
If downloading the Fedora ISO images and burning them to CD or DVD is impossible or impractical for you, refer to Раздел 2.2, «Получение Fedora на CD/DVD» to learn about other ways that you can obtain Fedora.

2.1. Загрузка Fedora

2.1.1. Как загрузить установочные файлы?

Ссылки для загрузки

To follow a Web-based guide to downloading, visit http://get.fedoraproject.org/. For guidance on which architecture to download, refer to Раздел 2.1.2, «Как узнать архитектуру моего компьютера?».
Программное обеспечение Fedora доступно для бесплатной загрузки. Способы:

2.1.1.1. Зеркало

The Fedora installation files are freely available from web servers located in many parts of the world. These servers mirror the files available from the Fedora Project. If you visit http://download.fedoraproject.org/, you are redirected to a mirror, based on a calculation of which mirror is likely to offer you the best download speed. Alternatively, you can choose a mirror from the list maintained at http://mirrors.fedoraproject.org/publiclist. 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 17 distribution normally appears in the directory fedora/linux/releases/17/. 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 17 for x86_64 at fedora/linux/releases/17/Fedora/x86_64/iso/Fedora-17-x86_64-DVD.iso.

2.1.1.2. BitTorrent

BitTorrent позволяет загрузить файлы при взаимодействии с другими компьютерами. Каждый компьютер в группе получает информацию по частям от раздающих компьютеров. Если загрузка данных завершена, то компьютер переходит на сторону раздачи, то есть предоставляет эти данные другим компьютерам для загрузки.
If your computer does not have software installed for BitTorrent, visit the BitTorrent home page at http://www.bittorrent.com/download/ to download it. BitTorrent client software is available for Windows, Mac OS, Linux, and many other operating systems.
You do not need to find a special mirror for BitTorrent files. The BitTorrent protocol ensures that your computer participates in a nearby group. To download and use the Fedora BitTorrent files, visit http://torrent.fedoraproject.org/.

Минимальные загрузочные образы

Образы минимальных загрузочных CD и USB недоступны в сети BitTorrent.

Verify your download

Once you have downloaded an ISO, verify it for security and integrity. To follow a web-based guide, visit https://fedoraproject.org/en/verify.

2.1.2. Как узнать архитектуру моего компьютера?

Архитектура, по большому счету, определяет тип процессора. Ниже приведена таблица, которая поможет узнать архитектуру компьютера исходя из типа процессора, который, в свою очередь, можно определить, обратившись к документации его производителя.
Таблица 2.1. Типы процессоров и архитектур
Производитель процессора и его модель Тип архитектуры для 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
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

i386 подходит для большинства Windows-совместимых компьютеров

Если вы не знаете модель процессора, выберите i386.
The exception is if your computer is a non-Intel based Apple Macintosh. Refer to http://fedoraproject.org/wiki/Architectures/PowerPC for more information on using Fedora on these systems.

Архитектуры Intel Atom могут отличаться

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 thex86_64 architecture. Refer to http://ark.intel.com/products/family/29035 for more details.

2.1.3. Какие файлы нужно загрузить?

Ниже будут рассмотрены способы загрузки Fedora.
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 17 for x86_64 is named Fedora-17-x86_64-DVD.iso. Refer to Раздел 2.1.2, «Как узнать архитектуру моего компьютера?» if you are unsure of your computer's architecture.
  1. Полный дистрибутив на DVD
    Если в вашем распоряжении есть быстрое Интернет-соединение, свободное время и желание получить максимальную свободу в выборе программ, загрузите полную DVD-версию. Создайте загрузочный диск, записав полученный образ на DVD. В случае проблем этот диск также может служить как восстанавливающий. Полную версию можно загрузить с зеркального сервера или через BitTorrent.
  2. Live-образ
    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. The Live image also provides an Install to Hard Disk desktop shortcut (alternatively, the shortcut can be found in ApplicationsSystem Tools). If you decide you like what you see, and want to install it, simply activate the selection to copy Fedora to your hard disk. 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.
  3. Минимальный загрузочный носитель
    Если у вас есть быстрое Интернет-соединение, но вы не ходите загружать весь дистрибутив, можно загрузить загрузочный образ CD для минимального окружения Fedora, позволяющего выполнить сетевую установку. И хотя этот метод подразумевает загрузку достаточно большого объема информации, он все же не превысит размер полного дистрибутива. По желанию, программы можно добавить или удалить после установки.

    Размер загрузки

    Установка стандартного набора пакетов Fedora по Интернету требует больше времени чем образ Live, но меньше чем целый дистрибутив на DVD. Конечно, влияние окажет и сетевой трафик, и программное обеспечение, которое вы выбрали для установки.
В приведенной ниже таблице перечислены образы с файлами на зеркальном сервере. Вместо архитектура укажите архитектуру компьютера.
Таблица 2.2. Расположение файлов
Тип носителя Расположение файлов
Полный дистрибутив на DVD fedora/linux/releases/17/Fedora/arch/iso/Fedora-17-arch-DVD.iso
Live-образ fedora/linux/releases/17/Live/архитектура/iso/Fedora-17-архитектура-Live.iso, fedora/linux/releases/17/Live/архитектура/iso/Fedora-17-KDE-архитектура-Live.iso
Минимальный загрузочный CD fedora/linux/releases/17/Fedora/arch/os/images/boot.iso

2.2. Получение Fedora на CD/DVD

If you do not have a fast Internet connection, or if you have a problem creating boot media, downloading may not be an option. Fedora DVD and CD distribution media is available from a number of online sources around the world at a minimal cost. Use your favorite Web search engine to locate a vendor, or refer to http://fedoraproject.org/wiki/Distribution.

Глава 3. 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.
Таблица 3.1. Boot and installation media
Architecture Installation DVD Installation USB flash drive Boot CD or boot DVD Boot USB flash drive
BIOS-based 32-bit x86 x86 DVD ISO image file x86 DVD ISO image file boot.iso boot.iso
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) boot.iso boot.iso
UEFI-based AMD64 and Intel 64 x86_64 DVD ISO image file Not available Not available efiboot.img (from x86_64 DVD ISO image file)

3.1. Making an installation DVD

You can make an installation DVD using the disc burning software on your computer.
The exact series of steps that produces a DVD from an ISO image file varies greatly from computer to computer, depending on the operating system and disc burning software installed. Use this procedure as a general guide. You might be able to omit certain steps on your computer, or might have to perform some of the steps in a different order from the order described here.
Make sure that your disc burning software is capable of burning discs from image files. Although this is true of most disc burning software, exceptions exist.
In particular, note that the disc burning feature built into Windows XP and Windows Vista cannot burn DVDs; and that earlier Windows operating systems did not have any disc burning capability installed by default at all. Therefore, if your computer has a Windows operating system prior to Windows 7 installed on it, you need a separate piece of software for this task. Examples of popular disc burning software for Windows that you might already have on your computer include Nero Burning ROM and Roxio Creator.
The Disk Utility software installed by default with Mac OS X on Apple computers has the capability to burn discs from images built into it already. Most widely-used DVD burning software for Linux, such as Brasero and K3b, also includes this capability.
  1. Download an ISO image file of a Fedora 17 disc as described in Глава 2, Получение Fedora.
  2. Insert a blank, writeable disc into your computer's disc burner. On some computers, a window opens and displays various options when you insert the disc. If you see a window like this, look for an option to launch your chosen disc burning program. If you do not see an option like this, close the window and launch the program manually.
  3. Launch your disc burning program. On some computers, you can do this by right-clicking (or control-clicking) on the image file and selecting a menu option with a label like Copy image to DVD, or Copy CD or DVD image. Other computers might provide you with a menu option to launch your chosen disc burning program, either directly or with an option like Open With. If none of these options are available on your computer, launch the program from an icon on your desktop, in a menu of applications such as the Start menu on Windows operating systems, or in the Mac Applications folder.
  4. In your disc burning program, select the option to burn a DVD from an image file. For example, in Nero Burning ROM, this option is called Burn Image and is located on the File menu.
    Note that you can skip this step when using certain DVD burning software; for example, Disk Utility on Mac OS X does not require it.
  5. Browse to the ISO image file that you downloaded previously and select it for burning.
  6. Click the button that starts the burning process.
On some computers, the option to burn a disc from an ISO file is integrated into a context menu in the file browser. For example, when you right-click an ISO file on a computer with a Linux or UNIX operating system that runs the GNOME desktop, the Nautilus file browser presents you with the option to Write to disk.

3.2. Preparing a USB flash drive as an installation source

Unusual USB Media

In a few cases with oddly formatted or partitioned USB media, image writing may fail.
You can install Fedora on 32-bit x86 systems and BIOS-based AMD64 and Intel 64 systems using a USB flash drive, provided that your hardware supports booting from this type of device. Note that you cannot install Fedora on UEFI-based AMD64 and Intel 64 systems from a USB flash drive, although you can use a USB flash drive to boot the Fedora installer on UEFI-based AMD64 and Intel 64 systems — refer to Раздел 3.3, «Making Minimal Boot Media».

3.2.1. Making Fedora USB Media on a Windows Operating System

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.
The most straightforward way to place a Fedora image on USB media using a Windows operating system is to transfer the Fedora live image to the USB device with the LiveUSB Creator tool.
Note that the dd tool discussed in Раздел 3.2.2, «Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems» is also available for Windows. Follow the instructions in that section to use an implementation of dd for Windows operating systems. The instructions in this section assume that you will use LiveUSB Creator.
  1. Download the LiveUSB Creator program for Windows from http://fedorahosted.org/liveusb-creator.
  2. LiveUSB Creator can create live USB media either from an image file that you downloaded previously, as described in Раздел 2.1.3, «Какие файлы нужно загрузить?», 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.
  3. Click Create Live USB.

3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems

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 Раздел 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

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 Раздел 3.2.2.1.2, «Making Fedora USB Media with livecd-tools» and Раздел 3.2.2.1.3, «Making Fedora USB Media with dd».
3.2.2.1.1. Making Fedora USB Media with a graphical tool

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 http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 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'
  2. Plug in your USB media.
  3. 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.
  4. LiveUSB Creator can create live USB media either from an image file that you downloaded previously, as described in Раздел 2.1.3, «Какие файлы нужно загрузить?», 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.
  5. Click Create Live USB.
3.2.2.1.2. Making Fedora USB Media with 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 http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 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'
  2. Plug in your USB media.
  3. Find the device name for your USB media. If the media has a volume name, use it to look up the device name in /dev/disk/by-label, or use the findfs:
    su -c 'findfs LABEL="MyLabel"'
    If the media does not have a volume name, or you do not know it, consult the /var/log/messages log for details:
    su -c 'less /var/log/messages'
  4. 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

Следование этим инструкциям может повредить данные

Все данные на используемом USB-накопителе будут удалены. Убедитесь, что устройство указано правильно и не содержит важных данных.

Примечание

The Fedora Project recommends using livecd-tools rather than dd for creating USB media whenever possible.
  1. Вставьте USB-носитель в разъем.
  2. Become root:
    su -
  3. Your flash drive must have a single partition with a vfat file system. To determine how it is formatted, find the name of this partition and the device itself by running dmesg shortly after connecting the drive. The device name (similar to /dev/sdc) and the partition name (similar to /dev/sdc1) both appear in several lines towards the end of the output.
  4. Use the partition name to ensure that the file system type of the USB flash drive is vfat.
    # blkid partition
    You should now see a message similar to:
    LABEL="LIVE" UUID="6676-27D3" TYPE="vfat"
    If TYPE is anything other than vfat (for example, TYPE="iso9660"), clear the first blocks of the USB flash drive:
    # dd if=/dev/zero of=partition bs=1M count=100
  5. Use the dd command to transfer the boot ISO image to the USB device:
    # dd if=path/image_name.iso of=device
    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, not the partition name. For example:
    # dd if=~/Download/Fedora-17-x86_64-DVD.iso of=/dev/sdc

3.2.2.2. Making Fedora USB Media in other Linux Distributions

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

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 Раздел 2.1.3, «Какие файлы нужно загрузить?»
  2. Plug in your USB media.
  3. Find the device name for your USB media. If the media has a volume name, look up the name in /dev/disk/by-label, or use the findfs:
    su -c 'findfs LABEL="MyLabel"'
    If the media does not have a volume name, or you do not know it, consult the /var/log/messages log for details:
    su -c 'less /var/log/messages'
  4. 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.
  5. At a command line, type su - to become root, and enter the root password when your system prompts you.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
Пример 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-17-i686-Live.iso, to a folder named Downloads in your home directory. You have a USB flash drive plugged into your computer, 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-17-i686-Live.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 your flash drive and make the flash drive bootable:
./livecd-iso-to-disk /home/Username/Downloads/Fedora-17-i686-Live.iso /dev/sdc1

3.2.2.2.2. Making Fedora USB Media with dd

Следование этим инструкциям может повредить данные

Все данные на используемом USB-накопителе будут удалены. Убедитесь, что устройство указано правильно и не содержит важных данных.

Примечание

The Fedora Project recommends using livecd-tools rather than dd for creating USB media whenever possible.
Use this method for the distribution image, the minimal boot media image, or on systems with a UNIX operating system (including Mac OX X).
  1. Вставьте USB-носитель в разъем.
  2. Become root:
    su -
  3. Your flash drive must have a single partition with a vfat file system. To determine how it is formatted, find the name of this partition and the device itself by running dmesg shortly after connecting the drive. The device name (similar to /dev/sdc) and the partition name (similar to /dev/sdc1) both appear in several lines towards the end of the output.
  4. Use the partition name to ensure that the file system type of the USB flash drive is vfat.
    # blkid partition
    You should now see a message similar to:
    LABEL="LIVE" UUID="6676-27D3" TYPE="vfat"
    If TYPE is anything other than vfat (for example, TYPE="iso9660"), clear the first blocks of the USB flash drive:
    # dd if=/dev/zero of=partition bs=1M count=100
  5. Use the dd command to transfer the boot ISO image to the USB device:
    # dd if=path/image_name.iso of=device
    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, not the partition name. For example:
    # dd if=~/Download/Fedora-17-x86_64-DVD.iso of=/dev/sdc

3.3. Making Minimal Boot Media

A piece of minimal boot media is a CD, DVD, or USB flash drive that contains the software to boot the system and launch the installation program, but which does not contain the software that must be transferred to the system to create a Fedora installation.
Use minimal boot media:
  • to boot the system to install Fedora over a network
  • to boot the system to install Fedora from a hard drive
  • to use a kickstart file during installation (refer to Раздел 15.8.1, «Creating Kickstart Boot Media»
  • to commence a network or hard-drive installation or to use an anaconda update or a kickstart file with a DVD installation.
You can use minimal boot media to start the installation process on 32-bit x86 systems, AMD64 or Intel 64 systems, and POWER systems. The process by which you create minimal boot media for systems of these various types is identical except in the case of AMD64 and Intel 64 systems with UEFI firmware interfaces — refer to Раздел 3.3.1, «UEFI-based systems».
To make minimal boot media for 32-bit x86 systems, BIOS-based AMD64 or Intel 64 systems, and POWER systems:
  1. Download the ISO image file named boot.iso that is available at the same location as the images of the Fedora 17 installation DVD — refer to Глава 2, Получение Fedora.
  2. Burn boot.iso to a blank CD or DVD using the same procedure detailed in Раздел 3.1, «Making an installation DVD» for the installation disc, or transfer the boot.iso file to a USB device with the dd command as detailed in Раздел 3.2, «Preparing a USB flash drive as an installation source». As the boot.iso file is only around 200 MB in size, you do not need an especially large USB flash drive.

3.3.1. UEFI-based systems

The Fedora Project does not provide an image to produce minimal boot CDs or DVDs for UEFI-based systems. Use a USB flash drive (as described in this section) to boot the Fedora 17 installer. The full DVD installation image should function as expected.
Use the efidisk.img file in the images/ directory on the Fedora 17 installation DVD to produce a bootable USB flash drive for UEFI-based systems.
  1. Download an ISO image file of the Fedora 17 installation DVD as described in Глава 2, Получение Fedora.
  2. Become root:
    su -
  3. Create a mount point for the ISO image file:
    # mkdir /mnt/dvdiso
  4. Mount the image file:
    # mount DVD.iso /mnt/dvdiso -o loop
    Where DVD.iso is the name of the ISO image file, for example Fedora17-x86_64-DVD.iso.
  5. Transfer efidisk.img from the ISO image file to your USB flash drive:
    # dd if=/mnt/dvdiso/images/efidisk.img of=/dev/device_name
    For example:
    # dd if=/mnt/dvdiso/images/efidisk.img of=/dev/sdc
  6. Unmount the ISO image file:
    # umount /mnt/dvdiso

Часть I. Installation and Booting

This part of the Fedora Installation Guide details the installation process itself, from various methods of booting the installer up to the point where the computer must restart to finalize the installation. This part of the manual also includes a chapter on troubleshooting problems with the installation process.

Содержание

4. Планирование установки на платформе x86
4.1. Upgrade or Install?
4.2. Is Your Hardware Compatible?
4.3. RAID and Other Disk Devices
4.3.1. Hardware RAID
4.3.2. Software RAID
4.3.3. FireWire and USB Disks
4.4. Достаточно ли дискового пространства?
4.5. Selecting an Installation Method
4.6. Choose a boot method
5. Preparing for Installation
5.1. Preparing for a Network Installation
5.1.1. Preparing for FTP and HTTP installation
5.1.2. Подготовка к NFS-установке
5.2. Preparing for a Hard Drive Installation
6. System Specifications List
7. Booting the Installer
7.1. Starting the Installation Program
7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems
7.1.2. The Boot Menu
7.1.3. Additional Boot Options
7.2. Booting from the Network using PXE
8. Configuring Installation Source
8.1. Installation Method
8.1.1. Installing from DVD
8.1.2. Installing from a Hard Drive
8.1.3. Installing via NFS
8.1.4. Installing via FTP or HTTP
9. Installing using anaconda
9.1. The Text Mode Installation Program User Interface
9.1.1. Using the Keyboard to Navigate
9.2. The Graphical Installation Program User Interface
9.2.1. Screenshots during installation
9.2.2. A Note about Virtual Consoles
9.3. Language Selection
9.4. The Pre-Installation Hub
9.5. Configuring date and time
9.6. Keyboard Configuration
9.7. Language Selection
9.8. Installation Source
9.9. Network configuration
9.9.1. Изменение сетевых подключений
9.10. Software Selection
9.10.1. Installing from Additional Repositories
9.10.2. Core Network Services
9.11. Устройства хранения
9.11.1. Окно выбора устройств хранения
9.12. Assign Storage Devices
9.13. Initializing the Hard Disk
9.14. Upgrading an Existing System
9.14.1. Экран обновления системы
9.14.2. Upgrading Using the Installer
9.14.3. Upgrading Boot Loader Configuration
9.15. Disk Partitioning Setup
9.16. Encrypt Partitions
9.17. Creating a Custom Layout or Modifying the Default Layout
9.17.1. Create Storage
9.17.2. Adding Partitions
9.17.3. Create Software RAID
9.17.4. Create LVM Logical Volume
9.17.5. Recommended Partitioning Scheme
9.18. Write changes to disk
9.19. Настройка загрузчика на платформах x86, AMD64 и Intel 64
9.19.1. Advanced Boot Loader Configuration
9.19.2. Rescue Mode
9.19.3. Alternative Boot Loaders
9.20. The Progress Hub
9.20.1. Set the Root Password
9.21. Installation Complete
10. Диагностика проблем при установке в системах Intel и AMD
10.1. Невозможно загрузить Fedora
10.1.1. Are You Unable to Boot With Your RAID Card?
10.1.2. Is Your System Displaying Signal 11 Errors?
10.2. Trouble Beginning the Installation
10.2.1. Problems with Booting into the Graphical Installation
10.3. Проблемы во время установки
10.3.1. Ошибка: Не найдены устройства для установки Fedora
10.3.2. Сохранение сообщений отладки
10.3.3. Trouble with Partition Tables
10.3.4. Using Remaining Space
10.3.5. Other Partitioning Problems
10.4. Problems After Installation
10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?
10.4.2. Blocked by a GRUB command line after upgrading?
10.4.3. Booting into a Graphical Environment
10.4.4. Problems with the X Window System (GUI)
10.4.5. Problems with the X Server Crashing and Non-Root Users
10.4.6. Problems When You Try to Log In
10.4.7. Is Your RAM Not Being Recognized?
10.4.8. Your Printer Does Not Work
10.4.9. Apache HTTP Server or Sendmail stops responding during startup

Глава 4. Планирование установки на платформе x86

4.1. Upgrade or Install?

Глава 20, Upgrading Your Current System содержит информацию, которая поможет сделать выбор в пользу обновления или переустановки.

4.2. Is Your Hardware Compatible?

Совместимость оборудования имеет большое значение, если у вас довольно старая система или вы собрали ее сами. Fedora 17 совместима с большей частью оборудования в системах, выпущенных в течение последних двух лет. Однако спецификации оборудования меняются практически ежедневно, поэтому трудно гарантировать, что ваше оборудование совместимо на 100%.
Обновленный список поддерживаемого оборудования можно найти в замечаниях к выпуску Fedora 17 по адресу http://docs.fedoraproject.org/release-notes .
At the end of a successful Fedora installation process, the installation program offers you the option to provide details of your hardware configuration anonymously to the Fedora Project (refer to Раздел 17.4, «Hardware Profile»). You can view the statistics gathered by this method at http://smolt.fedoraproject.org/static/stats/devices.html. Viewing the list of hardware that makes up systems on which other people have successfully installed Fedora might help you determine how suitable your hardware is.

4.3. RAID and Other Disk Devices

Важно: системы с наборами Intel BIOS RAID

Fedora 17 uses mdraid instead of dmraid for installation onto Intel BIOS RAID sets. These sets are detected automatically, and devices with Intel ISW metadata are recognized as mdraid instead of dmraid. Note that the device node names of any such devices under mdraid are different from their device node names under dmraid. Therefore, special precautions are necessary when you migrate systems with Intel BIOS RAID sets.
Local modifications to /etc/fstab, /etc/crypttab or other configuration files which refer to devices by their device node names will not work in Fedora 17. Before migrating these files, you must therefore edit them to replace device node paths with device UUIDs instead. You can find the UUIDs of devices with the blkid command.

4.3.1. Hardware RAID

Массив RAID (Redundant Array of Independent Disks) обеспечивает функционирование группы или массива дисков как единого целого. Прежде чем приступить к процессу установки, настройте все доступные параметры RAID. В Fedora каждый активный массив RAID будет представлен как отдельный диск.
Несколько жестких дисков в системах Fedora можно объединить в один RAID-массив, исключая тем самым необходимость в дополнительном оборудовании.

4.3.2. Software RAID

You can use the Fedora installation program to create Linux software RAID arrays, where RAID functions are controlled by the operating system rather than dedicated hardware. These functions are explained in detail in Раздел 9.17, « Creating a Custom Layout or Modifying the Default Layout ».

4.3.3. FireWire and USB Disks

Некоторые жесткие диски FireWire и USB могут быть не распознаны механизмом установки Fedora. Если настройка этих дисков в процессе установки не так уж важна, отсоедините их во избежание путаницы.

Post-installation Usage

You can connect and configure external FireWire and USB hard disks after installation. Most such devices are recognized by the kernel and available for use at that time.

4.4. Достаточно ли дискового пространства?

Nearly every modern-day operating system (OS) uses disk partitions, and Fedora is no exception. When you install Fedora, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to Приложение A, An Introduction to Disk Partitions before proceeding.
The disk space used by Fedora must be separate from the disk space used by other OSes you may have installed on your system, such as Windows, OS/2, or even a different version of Linux. For x86, AMD64, and Intel 64 systems, at least two partitions (/ and swap) must be dedicated to Fedora.
Before you start the installation process, you must
  • have enough unpartitioned[1] disk space for the installation of Fedora, or
  • убедиться в том, что в системе есть один или несколько разделов, которые можно удалить и, таким образом, освободить дисковое пространство для установки Fedora.
Раздел 9.17.5, «Recommended Partitioning Scheme» поможет определить необходимый объем пространства.
If you are not sure that you meet these conditions, or if you want to know how to create free disk space for your Fedora installation, refer to Приложение A, An Introduction to Disk Partitions.

4.5. Selecting an Installation Method

What type of installation method do you wish to use? The following installation methods are available:
DVD
If you have a DVD drive and the Fedora DVD you can use this method. Refer to Раздел 8.1.1, «Installing from DVD», for DVD installation instructions.
If you booted the installation from a piece of media other than the installation DVD, you can specify the DVD as the installation source with the linux repo=cdrom:device:/device boot option, or by selecting Local CD/DVD on the Installation Method menu (refer to Раздел 8.1, «Installation Method»).
Live CD
If you have a CD drive and the Fedora live CD you can use this method. The live CD desktop includes an icon labeled Install to Hard Drive. Refer to Раздел 8.1.1, «Installing from DVD» for CD installation instructions.
Hard Drive
If you have copied the Fedora ISO images to a local hard drive, you can use this method. You need a boot CD-ROM (use the linux repo=hd:device:/path boot option), or by selecting Hard drive on the Installation Method menu (refer to Раздел 8.1, «Installation Method»). Refer to Раздел 8.1.2, «Installing from a Hard Drive», for hard drive installation instructions.
NFS
If you are installing from an NFS server using ISO images or a mirror image of Fedora, you can use this method. You need a boot CD-ROM (use the linux repo=nfs:server :options:/path boot option, or the NFS directory option on the Installation Method menu described in Раздел 8.1, «Installation Method»). Refer to Раздел 8.1.3, «Installing via NFS» for network installation instructions. Note that NFS installations may also be performed in GUI mode.
URL
If you are installing directly from an HTTP (Web) server or FTP server, use this method. You need a boot CD-ROM (use the linux repo=ftp://user:password@host/path, or linux repo=http://host/path boot option, or the URL option on the Installation Method menu described in Раздел 8.1, «Installation Method»). Refer to Раздел 8.1.4, «Installing via FTP or HTTP», for FTP and HTTP installation instructions.

4.6. Choose a boot method

You can use several methods to boot Fedora.
Для установки с дисков CD/DVD потребуется наличие CD или DVD-дисков Fedora 17 и привод CD/DVD в системе, поддерживающей загрузку с CD/DVD.
Для загрузки с CD/DVD может потребоваться изменить настройки BIOS (см. Раздел 7.1.1, «Booting the Installation Program on x86, AMD64, and Intel 64 Systems»).
Other than booting from an installation CD or DVD, you can also boot the Fedora installation program from minimal boot media in the form of a bootable CD or USB flash drive. After you boot the system with a piece of minimal boot media, you complete the installation from a different installation source, such as a local hard drive or a location on a network. Refer to Раздел 3.3, «Making Minimal Boot Media» for instructions on making boot CDs and USB flash drives.
Наконец, программу установки можно загрузить по сети с сервера PXE (Preboot Execution environment). Глава 13, Setting Up an Installation Server содержит подробную информацию. После успешной загрузки выполните установку по сети или локально с жесткого диска.


[1] Unpartitioned disk space means that available disk space on the hard drives you are installing to has not been divided into sections for data. When you partition a disk, each partition behaves like a separate disk drive.

Глава 5. Preparing for Installation

5.1. Preparing for a Network Installation

Примечание

Make sure no installation DVD (or any other type of DVD or CD) is in your system's CD or DVD drive if you are performing a network-based installation. Having a DVD or CD in the drive might cause unexpected errors.
Проверьте наличие загрузочного CD/DVD-диска или USB-носителя.
The Fedora installation medium must be available for either a network installation (via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if you are performing an NFS, FTP, or HTTP installation.
The NFS, FTP, or HTTP server to be used for installation over the network must be a separate, network-accessible server. It must provide the complete contents of the installation DVD-ROM.

Примечание

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

Примечание

The public directory used to access the installation files over FTP, NFS, or HTTP is mapped to local storage on the network server. For example, the local directory /var/www/inst/Fedora17 on the network server can be accessed as http://network.server.com/inst/Fedora17.
In the following examples, the directory on the installation staging server that will contain the installation files will be specified as /location/of/disk/space. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as /publicly_available_directory. For example, /location/of/disk/space may be a directory you create called /var/isos. /publicly_available_directory might be /var/www/html/Fedora17, for an HTTP install.
Далее потребуется образ ISO, содержащий точную копию содержимого DVD. Чтобы создать образ диска DVD, выполните команду
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.
Чтобы скопировать файлы с установочного DVD на компьютер Linux, который будет выполнять функции сервера установки, выполните действия, описанные в следующих секциях (см. Раздел 5.1.1, «Preparing for FTP and HTTP installation», Раздел 5.1.2, «Подготовка к NFS-установке»).

5.1.1. Preparing for FTP and HTTP installation

Extract the files from the ISO image of the installation DVD and place them in a directory that is shared over FTP or HTTP.
Проверьте доступ: попробуйте подключиться к нему с сервера и любой другой машины, принадлежащей той же сети, где будет выполняться установка.

5.1.2. Подготовка к NFS-установке

For NFS installation it is not necessary to extract all the files from the ISO image. It is sufficient to make the ISO image available on the network server via NFS.
  1. Скопируйте образ ISO в экспортируемый каталог. Для этого в Linux выполните команду
    mv /path_to_image/name_of_image.iso /publicly_available_directory/
    where path_to_image is the path to the ISO image file, name_of_image is the name of the ISO image file, and publicly_available_directory is a directory that is available over NFS or that you intend to make available over NFS.
  2. Проверьте контрольную сумму SHA256 носителя. Для этой цели существует множество программ для разных операционных систем. Так, в Linux можно выполнить:
    $ sha256sum образ.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 http://fedoraproject.org/en/keys. The two hashes should be identical.
  3. 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.
    Чтобы экспортировать каталог в конкретную систему:
    /publicly_available_directory client.ip.address (ro)
    Чтобы экспортировать каталог во все системы:
    /publicly_available_directory * (ro)
  4. On the network server, start the NFS daemon (on a Fedora system, use /sbin/service nfs start). If NFS is already running, reload the configuration file (on a Fedora system use /sbin/service nfs reload).
  5. Be sure to test the NFS share following the directions in the Fedora Deployment Guide. Refer to your NFS documentation for details on starting and stopping the NFS server.

Примечание

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

Поддерживаются не все файловые системы

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.
Проверить тип файловой системы в Windows можно с помощью системной программы управления дисками, а в Linux — с помощью fdisk.

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.
При наличии этих файлов на жестком диске можно выполнить установку с жесткого диска (см. Раздел 8.1, «Installation Method»).
Проверьте наличие загрузочного CD/DVD-диска или USB-носителя.
Подготовка жесткого диска в качестве источника установки включает следующее:
  1. Obtain an ISO image of the Fedora installation DVD (refer to Глава 2, Получение 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.
  2. Скопируйте образ на жесткий диск.
    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.
  3. Проверьте контрольную сумму SHA256 носителя. Для этой цели существует множество программ для разных операционных систем. Так, в Linux можно выполнить:
    $ sha256sum образ.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 http://fedoraproject.org/en/keys. The two hashes should be identical.

Примечание

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

Глава 6. System Specifications List

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 Раздел 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.
  • Если Fedora устанавливается в качестве дополнительной операционной системы поверх существующей, запишите следующее:
    • 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 Раздел 9.5, «Configuring date and time» may cause unexpected behavior in Fedora.
  • If you plan to install from an image on a local hard drive:
    • Жесткий диск и каталог, содержащий образ.
  • If you plan to install from a network location, or install on an iSCSI target:
    • 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:
  • If you plan to install on an iSCSI target:
    • Расположение цели iSCSI. В зависимости от сети может потребоваться имя пользователя CHAP, пароль, обратное имя пользователя и пароль (см. Раздел 9.11.1.1, « Advanced Storage Options »).
  • 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.

Глава 7. Booting the Installer

Important — UEFI for 32-bit x86 systems

Fedora 17 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 17 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 17, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from http://www.uefi.org/specs/agreement/
To start the installation program from a Fedora DVD or from minimal boot media, follow this procedure:
  1. Disconnect any external FireWire or USB disks that you do not need for installation. Refer to Раздел 4.3.3, « FireWire and USB Disks » for more information.
  2. Power on your computer system.
  3. Insert the media in your computer.
  4. Power off your computer with the boot media still inside.
  5. Power on your computer system.
You might need to press a specific key or combination of keys to boot from the media. On most computers, a message appears briefly on the screen very soon after you turn on the computer. Typically, it is worded something like Press F10 to select boot device, although the specific wording and the key that you must press varies widely from computer to computer. Consult the documentation for your computer or motherboard, or seek support from the hardware manufacturer or vendor. On Apple computers, the C key boots the system from the DVD drive. On older Apple hardware you might need to press Cmd+Opt+Shift+Del to boot from the DVD drive.
If your computer does not allow you to select a boot device as it starts up, you might need to configure your system's Basic Input/Output System (BIOS) to boot from the media.
To change your BIOS settings on an x86, AMD64, or Intel 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings.
Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the DVD is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the DVD drive for bootable media; if it does not find bootable media on the DVD drive, it then checks your hard drive or diskette drive.
Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system.

Примечание: прерывание установки

To abort the installation, either press Ctrl +Alt+Del or power off your computer with the power switch. You may abort the installation process without consequence at any time prior to selecting Write changes to disk on the Write partitioning to disk screen. Fedora makes no permanent changes to your computer until that point. Please be aware that stopping the installation after partitioning has begun can leave your computer unusable.

7.1. Starting the Installation Program

Important — UEFI for 32-bit x86 systems

Fedora 17 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 17 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 17, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from http://www.uefi.org/specs/agreement/
To start, first make sure that you have all necessary resources for the installation. If you have already read through Глава 4, Планирование установки на платформе x86, and followed the instructions, you should be ready to start the installation process. When you have verified that you are ready to begin, boot the installation program using the Fedora DVD or any boot media that you have created.

7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 Systems

You can boot the installation program using any one of the following media (depending upon what your system can support):
  • Fedora DVD — Your machine supports a bootable DVD drive and you have the Fedora installation DVD.
  • Fedora live CD — Your machine supports a bootable CD drive and you have a Fedora live CD.
  • Boot CD-ROM — Your machine supports a bootable CD-ROM drive and you want to perform network or hard drive installation.
  • USB flash drive — Your machine supports booting from a USB device.
  • PXE boot via network — Your machine supports booting from the network. This is an advanced installation path. Refer to Глава 13, Setting Up an Installation Server for additional information on this method.
To create a boot CD-ROM or to prepare your USB flash drive for booting or installation, refer to Раздел 3.3, «Making Minimal Boot Media».
Insert the boot media and reboot the system.
You might need to press a specific key or combination of keys to boot from the media. On most computers, a message appears briefly on the screen very soon after you turn on the computer. Typically, it is worded something like Press F10 to select boot device, although the specific wording and the key that you must press varies widely from computer to computer. Consult the documentation for your computer or motherboard, or seek support from the hardware manufacturer or vendor. On Apple computers, the C key boots the system from the DVD drive. On older Apple hardware you might need to press Cmd+Opt+Shift+Del to boot from the DVD drive.
If your computer does not allow you to select a boot device as it starts up, you might need to configure your system's Basic Input/Output System (BIOS) to boot from the media.
To change your BIOS settings on an x86, AMD64, or Intel 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings.
Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the DVD is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the DVD drive for bootable media; if it does not find bootable media on the DVD drive, it then checks your hard drive or diskette drive.
Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system.
After a short delay, the graphical boot screen appears, which contains information on a variety of boot options. Installation program automatically begins if you take no action within the first minute. For a description of the options available on this screen, refer to Раздел 7.1.2, «The Boot Menu».
Alternatively, press the Esc key to access the boot: prompt, at which you can enter additional boot options as described in Раздел 7.1.3, «Additional Boot Options».

7.1.2. The Boot Menu

The boot media displays a graphical boot menu with two options:
Install or upgrade an existing system
This option is the default. Choose this option to install Fedora onto your computer system using the graphical installation program.
Troubleshooting
This option leads to a menu with several additional boot options.
If no key is hit within 60 seconds, the default boot option runs. To choose the default, either wait for the timer to run out or hit Enter on the keyboard. To choose another option, use the arrow keys on your keyboard and hit Enter when Troubleshooting is highlighted. If you want to customize the boot options for a particular option, press the Tab key. To access the boot: prompt at which you can specify custom boot options, press the Esc key and refer to Раздел 7.1.3, «Additional Boot Options».
The boot screen
The boot screen
Рисунок 7.1. The boot screen

For a listing and explanation of common boot options, refer to Глава 11, Boot Options.
The boot options in the Troubleshooting menu are:
Install Fedora in basic graphics mode
This option allows you to install Fedora in graphical mode even if the installation program is unable to load the correct driver for your video card. If your screen appears distorted or goes blank when using the Install or upgrade an existing system option, restart your computer and try this option instead.
Rescue a Fedora system
Choose this option to repair a problem with your installed Fedora system that prevents you from booting normally. Although Fedora is an exceptionally stable computing platform, it is still possible for occasional problems to occur that prevent booting. The rescue environment contains utility programs that allow you fix a wide variety of these problems.
Run a memory test
This option runs an exhaustive test on the memory on your system. For more information, refer to Раздел 11.6.1, «Загрузка режима тестирования памяти (ОЗУ)».
Boot from local drive
This option boots the system from the first installed disk. If you booted this disc accidentally, use this option to boot from the hard disk immediately without starting the installer.

7.1.3. Additional Boot Options

While it is easiest to boot using a DVD and perform a graphical installation, sometimes there are installation scenarios where booting in a different manner may be needed. This section discusses additional boot options available for Fedora.
To pass options to the boot loader on an x86, AMD64, or Intel 64 system, press the Esc key at boot time. The boot: prompt appears, at which you can use the boot loader options described below.
Refer to Глава 8, Configuring Installation Source for boot options to specify your installation source, or to Глава 11, Boot Options for additional boot options not covered in this section.
  • To perform a text mode installation, at the installation boot prompt, type:
    linux text
  • ISO images have an SHA256 checksum embedded in them. To test the checksum integrity of an ISO image, at the installation boot prompt, type:
    linux rd.live.check
    This checksum operation can be performed on any Fedora DVD. It is strongly recommended to perform this operation on any Fedora DVD that was created from downloaded ISO images. This command works with the DVD, hard drive ISO, and NFS ISO installation methods.
  • If you need to perform the installation in serial mode, type the following command:
    linux console=<device>
    For text mode installations, use:
    linux text console=<device>
    In the above command, <device> 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

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 Раздел 9.19, «Настройка загрузчика на платформах x86, AMD64 и Intel 64» for more information).
For more information on kernel options refer to Глава 11, Boot Options.

7.2. Booting from the Network using PXE

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 Глава 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.
  2. Switch on the computer.
  3. 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.

PXE-установка при наличии нескольких сетевых интерфейсов

Cерверы с несколькими сетевыми интерфейсами могут не присвоить имя «eth0» первому интерфейсу. Это может привести к тому, что установщик будет пытаться использовать другой интерфейс, а не тот, который используется PXE. Чтобы это изменить, в файл конфигурации pxelinux.cfg/* добавьте следующее:
IPAPPEND 2
APPEND ksdevice=bootif
Эти параметры заставят установщик использовать сетевой интерфейс, который уже используется BIOS и PXE. Также можно определить следующий параметр:
ksdevice=link
This option causes the installer to use the first network device it finds that is linked to a network switch.

Глава 8. Configuring Installation Source

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

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

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 the Write changes to disk screen. Refer to Раздел 9.18, «Write changes to disk» 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

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:
Таблица 8.1. Location of ISO images for different partition types
Partition type Volume Original path to files Directory to use
VFAT D:\ D:\Downloads\Fedora17 /Downloads/Fedora17
ext2, ext3, ext4 /home /home/user1/Fedora17 /user1/Fedora17

If the ISO images are in the root (top-level) directory of a partition, enter a /. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/, and the images are in /home/new/, you would enter /new/.

Use a leading slash

An entry without a leading slash may cause the installation to fail.
After entering the linux repo= boot command, proceed with Глава 9, Installing using anaconda.

8.1.3. Installing via NFS

To specify an installation source for Fedora accessible by NFS, use the linux repo= boot option. To specify an expanded tree of installation files, type:
linux repo=nfs:options:server:/path
To specify an ISO image file, type:
linux repo=nfsiso:options:server:/path
  • options — specify any NFS mount options that you require. Refer to the man pages for mount and nfs for a comprehensive list of options.
  • server — enter the domain name or IP address of your NFS server. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com.
  • path — the path to the exported directory.
    • If the NFS server is exporting a mirror of the Fedora installation tree, enter the directory which contains the root of the installation tree.
    • If the NFS server is exporting the ISO image of the Fedora DVD, enter the directory which contains the ISO image.
    If you followed the setup described in Раздел 5.1.2, «Подготовка к NFS-установке», the exported directory is the one that you specified as publicly_available_directory.
After entering the linux repo= command, proceed with Глава 9, Installing using anaconda.

8.1.4. Installing via FTP or HTTP

Important — you must specify the protocol

When you provide a URL to an installation source, you must explicitly specify http:// or ftp:// as the protocol.
To specify an installation source for Fedora that is available over the Internet, use the linux repo= boot option:
linux repo={ftp|http}://URL
For URL, enter the name or IP address of the FTP or HTTP site from which you are installing, and the name of the directory that contains the /images directory for your architecture. For example:
http://name.example.com/mirrors/fedora/F-17/Server/i386/
If your FTP or HTTP server requires user authentication, specify user and password as part of the URL as follows:
{ftp|http}://<user>:<password>@<hostname>[:<port>]/<directory>/
For example:
http://install:fedora17pw@name.example.com/mirrors/fedora/F-17/Server/i386/
After entering the linux repo= command, proceed with Глава 9, Installing using anaconda.

Глава 9. Installing using anaconda

This chapter describes an installation using the graphical user interface of anaconda.

9.1. The Text Mode Installation Program User Interface

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 Глава 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 Глава 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:
  • нестандартные схемы хранения данных (LVM, RAID, FCoE, zFCP, iSCSI);
  • изменение стандартной схемы разделов;
  • изменение конфигурации загрузчика;
  • выбор пакетов в процессе установки;
  • configuring the installed system with firstboot
If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation. Refer to Раздел 18.3, «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 Раздел 11.1, «Configuring the Installation System at the Boot Menu» for instructions.

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

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

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

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 Раздел 15.3, «Creating the Kickstart File» for details of configuring a Kickstart file.

9.2.2. A Note about Virtual Consoles

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 Таблица 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.
Таблица 9.1. Console, Keystrokes, and Contents
console keystrokes contents
1 Ctrl+alt+f1 graphical display
2 Ctrl+alt+f2 shell prompt
3 Ctrl+alt+f3 install log (messages from installation program)
4 Ctrl+alt+f4 system-related messages
5 Ctrl+alt+f5 other messages

9.3. Language Selection

At the Welcome screen, use your mouse to select the language (for example, English (United States)) you would prefer to use for the installation and as the system default.
Alternatively, type your preferred language into the search box (refer to the figure below).
Once you have made your selection, click Continue.
Language Configuration
Language selection screen
Рисунок 9.1. Language Configuration

9.4. The Pre-Installation Hub

The Pre-Installation Hub is the central screen for setting up an installation.
The pre-installation hub
Pre-installation hub screen
Рисунок 9.2. The pre-installation hub

Instead of directing you through consecutive screens, anaconda allows you to configure your installation in the order you choose.
Use your mouse to select a section. When you have completed configuring a section, or if you would like to complete that section later, click Done.
Sections that still require your attention are marked with a warning symbol. If any required work is outstanding, a note at the bottom of the screen warns you that these sections must be completed before you can continue.
Once all required sections are complete, click Begin Installation.
To cancel the installation, click Quit.

9.5. Configuring date and time

Select Date and Time from the Pre-Installation Hub.
Set your time zone by selecting the city closest to your computer's physical location.
Specify a time zone even if you plan to use NTP (Network Time Protocol) to maintain the accuracy of the system clock.
From here there are two ways for you to select your time zone:
  • Using your mouse, click on the interactive map to select a specific city. A red pin appears indicating your selection.
  • You can also scroll through the Region and City drop-down menus at the top of the screen to select your time zone.
Configuring the Time Zone
Time zone configuration screen.
Рисунок 9.3. Configuring the Time Zone

To set the date and time using NTP, leave the Network Time switch in the ON position and click the configuration icon to select which NTP servers Fedora should use. To set the date and time manually, move the switch to the OFF position. The system clock should use your time zone selection to display the correct date and time at the bottom of the screen. If they are still incorrect, adjust them manually.
Once you have made your selection, click Done to return to the pre-installation hub.

Примечание

To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool.
Type the system-config-date command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue.

9.6. Keyboard Configuration

Select Keyboard from the Pre-Installation Hub.
The language you selected in Раздел 9.3, «Language Selection» will be listed in the left-hand pane and serves as the default keyboard layout. To add additional layouts for other languages, click the + button and select from the list. Click the - button to delete layouts. Use the arrow buttons to arrange the layouts in order of preference.
For a visual preview of the keyboard layout, select it and click the keyboard button. To test a layout, select it and then use the mouse to click inside the text box at the right. Type some text to confirm that your selection functions correctly.
If you choose multiple keyboard layouts, you will be able to toggle between keyboard layouts in Fedora using the Alt+Shift keystroke combination. To choose a different combination, click Options to open the Layout Switching Options dialog. Choose a combination from the list by selecting its check box.
Once you have made your selection, click Done to return to the pre-installation hub.
Keyboard Configuration
Keyboard configuration screen
Рисунок 9.4. Keyboard Configuration

Fedora includes support for more than one keyboard layout for many languages. In particular, most European languages include a latin1 option, which uses dead keys to access certain characters, such as those with diacritical marks. When you press a dead key, nothing will appear on your screen until you press another key to "complete" the character. For example, to type é on a latin1 keyboard layout, you would press (and release) the ' key, and then press the E key. By contrast, you access this character on some other keyboards by pressing and holding down a key (such as Alt-Gr) while you press the E key. Other keyboards might have a dedicated key for this character.

Note

To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool.
Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue.

9.7. Language Selection

The language currently selected for the installation and as the system default is displayed on the Pre-Installation Hub, under Language.
If you need to change the language – perhaps if you accepted the default of English (United States) in error – select Language from the Pre-Installation Hub.
Use your mouse to select the language (for example, English (United States)) you would prefer to use for the installation and as the system default.
Alternatively, type your preferred language into the search box (refer to the figure below).
Once you have made your selection, click Done to return to the Pre-Installation Hub.
Language Configuration
Language selection screen
Рисунок 9.5. Language Configuration

9.8. Installation Source

Specify the location you would like to install Fedora from. Choose between an ISO file or a network location.
Installation source
Installation source screen
Рисунок 9.6. Installation source

If you initiated the installation using a full DVD ISO, the installer will detect the ISO and display it under Auto-detected install media. Select the ISO to use it as the installation source.
If an ISO has not been detected automatically, specify a locally-stored ISO file. Click Choose an ISO and browse to the file's location on your system. After selecting an ISO, click Verify to check that the file is suitable for installation.
To specify a network location, choose from the following options in the drop-down menu: Closest mirror, http://, https://, ftp://, and nfs.
Using your selection as the start of the location URL, type the rest into the address box. (If you selected Closest mirror, an address is not required.)
If you choose NFS, the address box will be grayed out. Another box will appear for you to specify any NFS mount options.
To configure a proxy, click Proxy setup unless you are installing via FTP and NFS. Proxies are unavailable for these methods.
Check Enable HTTP proxy and type the URL into the Proxy URL box. If your proxy requires authentication, check Use Authentication and enter a username and password. Click Add.
Check the Updates option if you do not want to install the latest available updates and would prefer to install the default versions from your specified installation source.
Once you have selected your installation source, click Back to return to the Pre-Installation Hub.

9.9. Network configuration

Появится запрос ввода имени узла либо в виде полностью квалифицированного имени домена, либо в формате узел.домен, либо можно просто указать имя_узла. Многие сети используют протокол DHCP (Dynamic Host Configuration Protocol) для автоматического назначения системе доменного имени. При этом пользователю остается только указать имя узла.
Network configuration
Network configuration
Рисунок 9.7. Network configuration

Если система Fedora напрямую подключена к Интернету, примите во внимание правила вашего провайдера. Их обсуждение выходит за рамки этого документа.

Modem Configuration

The installation program does not configure modems. Configure these devices after installation with the Network utility. The settings for your modem are specific to your particular Internet Service Provider (ISP).

9.9.1. Изменение сетевых подключений

Important — Manual configuration is often needed

When a Fedora 17 installation boots for the first time, it activates any network interfaces that you configured during the installation process. However, the installer does not prompt you to configure network interfaces on some common installation paths, for example, when you install Fedora from a DVD to a local hard drive.
When you install Fedora from a local installation source to a local storage device, be sure to configure at least one network interface manually if you require network access when the system boots for the first time.

Примечание

Чтобы изменить настройки сетевых подключений после завершения установки, воспользуйтесь программой настройки сети.
Выполните в приглашении оболочки команду system-config-network для ее запуска. Если вы не являетесь пользователем root, для продолжения будет предложено ввести пароль root.
To configure the selected network connection manually, click the button Configure. A Network Manager dialog appears that allows you to configure the selected connection. The configuration options presented will depend on whether the connection is wired, wireless, mobile broadband, VPN, or DSL. A full description of all configurations possible with NetworkManager is beyond the scope of this guide. This section only details the most typical scenario of how to configure wired connections during installation. Configuration of other types of network is broadly similar, although the specific parameters that you must configure are necessarily different.
When you have finished editing network settings, click Save to save the new configuration. If you reconfigured a device that was already active during installation, you must restart the device to use the new configuration — refer to Раздел 9.9.1.6, «Restart a network device».

9.9.1.1. Аналогичные параметры для разных типов подключений

Некоторые параметры совпадают для всех типов соединений.
Заполните поле Название соединения.
Select Connect automatically to start the connection automatically when the system boots.
When NetworkManager runs on an installed system, the Available to all users option controls whether a network configuration is available system-wide or not. During installation, ensure that Available to all users remains selected for any network interface that you configure.

9.9.1.2. The Ethernet tab

Use the Ethernet tab to specify or change the media access control (MAC) address for the network adapter, and set the maximum transmission unit (MTU, in bytes) that can pass through the interface either manually or automatically.
The Ethernet tab
The Ethernet tab
Рисунок 9.8. The Ethernet tab

9.9.1.3. Вкладка защиты 802.1x

На вкладке Защита 802.1x можно настроить контроль сетевого доступа в зависимости от порта. Для этого выберите Использовать защиту 802.1X для этого соединения и введите необходимые данные. Параметры настройки включают:
Аутентификация
Выберите метод аутентификации:
  • TLS (Transport Layer Security);
  • Туннельный TLS (TTLS или EAP-TTLS);
  • Защищенный EAP (PEAP) (Protected Extensible Authentication Protocol).
Идентификация
Введите данные сервера.
Сертификат пользователя
Путь к файлу сертификата X.509, закодированному с помощью правил DER (Distinguished Encoding Rules) или PEM (Privacy Enhanced Mail).
Сертификат CA
Путь к файлу сертификата CA, закодированному с помощью правил DER (Distinguished Encoding Rules) или PEM (Privacy Enhanced Mail).
Секретный ключ
Путь к файлу секретного ключа, закодированному с помощью правил DER (Distinguished Encoding Rules), PEM (Privacy Enhanced Mail) или PKCS#12 (Personal Information Exchange Syntax Standard).
Пароль к секретному ключу
Пароль для ключа, заданного в поле Секретный ключ. Отметьте Показывать пароль, чтобы видеть вводимый пароль.
Вкладка защиты 802.1x
Вкладка защиты 802.1x
Рисунок 9.9. Вкладка защиты 802.1x

9.9.1.4. The IPv4 Settings tab

На вкладке параметров IPv4 можно изменить настройки существующего соединения.
В меню Профиль выберите настройки, которые будут определяться службой DHCP.
Автоматически (DHCP)
Параметры IPv4 определяются службой DHCP.
Автоматические адреса (DHCP)
Адрес IPv4, маска сети и адрес шлюза настраиваются службой DHCP, но серверы имен и домены поиска должны быть настроены вручную.
Manual
Параметры IPv4 для статической конфигурации определяются вручную.
Link-Local Only
Интерфейсу будет назначен локальный адрес в диапазоне 169.254/16.
Общий с другими компьютерами
В этом случае система будет предоставлять доступ к сети для других компьютеров. Интерфейсу будет назначен адрес в диапазоне 10.42.x.1/24. Серверы DHCP и DNS будут запущены, а при подключении интерфейса к системе с NAT (Network Address Translation) будут использоваться настройки по умолчанию.
Не указывать адрес
IPv4 отключен.
При выборе профиля, для которого необходимо настроить параметры вручную, в поле адреса укажите IP-адрес интерфейса, маску сети и шлюз. Для добавления и удаления адресов используются одноименные кнопки. В поле Серверы DNS введите список серверов, разделив их запятой, а в поле Домены поиска перечислите домены, которые будут участвовать в поиске сервера имен.
Или можно ввести имя сетевого соединения в поле ID клиента DHCP. Значение должно быть уникально в пределах подсети.
Отмените выбор Требовать адресацию IPv4 для этого соединения, чтобы разрешить это соединение в сети IPv6. Используется в случаях, если настройка IPv4 завершилась неудачей, а настройка IPv6 удалась.
The IPv4 Settings tab
The IPv4 Settings tab
Рисунок 9.10. The IPv4 Settings tab

9.9.1.4.1. Изменение маршрутов IPv4
Red Hat Enterprise Linux выполняет автоматическую настройку маршрутов на основе IP-адресов устройства. Чтобы добавить дополнительные маршруты, нажмите кнопку Маршруты. Появится диалог Изменение маршрутов IPv4.
Диалог изменения маршрутов IPv4
Диалог изменения маршрутов IPv4
Рисунок 9.11. Диалог изменения маршрутов IPv4

Click Add to add the IP address, netmask, gateway address, and metric for a new static route.
Выберите Игнорировать автоматически полученные маршруты, чтобы использовать только заданные здесь маршруты.
Select Use this connection only for resources on its network to restrict connections only to the local network.

9.9.1.5. Вкладка параметров IPv6

На вкладке Параметры IPv6 можно изменить настройки IPv6 для выбранного соединения.
В меню Профиль выберите настройки, которые будут определяться службой DHCP.
Игнорировать
Игнорировать IPv6 для заданного соединения.
Автоматически
NetworkManager uses router advertisement (RA) to create an automatic, stateless configuration.
Автоматически, только адреса
NetworkManager uses RA to create an automatic, stateless configuration, but DNS servers and search domains are ignored and must be configured manually.
Automatic, DHCP only
NetworkManager does not use RA, but requests information from DHCPv6 directly to create a stateful configuration.
Manual
Параметры IPv6 для статической конфигурации определяются вручную.
Link-Local Only
Интерфейсу будет назначен локальный адрес с префиксом fe80::/10.
При выборе профиля, для которого необходимо настроить параметры вручную, в поле адреса укажите IP-адрес интерфейса, маску сети и шлюз. Для добавления и удаления адресов используются одноименные кнопки. В поле Серверы DNS введите список серверов, разделив их запятой, а в поле Домены поиска перечислите домены, которые будут участвовать в поиске сервера имен.
Или можно ввести имя сетевого соединения в поле ID клиента DHCP. Значение должно быть уникально в пределах подсети.
Отмените выбор Требовать адресацию IPv6 для этого соединения, чтобы разрешить это соединение в сети IPv4. Используется в случаях, если настройка IPv6 завершилась неудачей, а настройка IPv4 удалась.
Вкладка параметров IPv6
Вкладка параметров IPv6
Рисунок 9.12. Вкладка параметров IPv6

9.9.1.5.1. Изменение маршрутов IPv6
Fedora configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the Routes button. The Editing IPv6 routes dialog appears.
Диалог изменения маршрутов IPv6
Диалог изменения маршрутов IPv6
Рисунок 9.13. Диалог изменения маршрутов IPv6

Click Add to add the IP address, netmask, gateway address, and metric for a new static route.
Select Use this connection only for resources on its network to restrict connections only to the local network.

9.9.1.6. Restart a network device

If you reconfigured a network that was already in use during installation, you must disconnect and reconnect the device in anaconda for the changes to take effect. Anaconda uses interface configuration (ifcfg) files to communicate with NetworkManager. A device becomes disconnected when its ifcfg file is removed, and becomes reconnected when its ifcfg file is restored, as long as ONBOOT=yes is set. Refer to the Fedora Deployment Guide available from http://docs.fedoraproject.org/en-US/index.html for more information about interface configuration files.
  1. Press Ctrl+Alt+F2 to switch to virtual terminal tty2.
  2. Move the interface configuration file to a temporary location:
    mv /etc/sysconfig/network-scripts/ifcfg-device_name /tmp
    where device_name is the device that you just reconfigured. For example, ifcfg-eth0 is the ifcfg file for eth0.
    The device is now disconnected in anaconda.
  3. Open the interface configuration file in the vi editor:
    vi /tmp/ifcfg-device_name
  4. Verify that the interface configuration file contains the line ONBOOT=yes. If the file does not already contain the line, add it now and save the file.
  5. Exit the vi editor.
  6. Move the interface configuration file back to the /etc/sysconfig/network-scripts/ directory:
    mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/
    The device is now reconnected in anaconda.
  7. Press Ctrl+Alt+F6 to return to anaconda.

9.10. Software Selection

Installing in text mode

При установке Fedora в текстовом режиме выбор пакетов для установки будет недоступен. Установщик автоматически выберет из основной группы пакеты, необходимые для работы системы после завершения процесса установки и обеспечения ее готовности к установке новых пакетов и обновлений. После завершения установки изменить набор пакетов можно с помощью специального приложения добавления и удаления программ.
Software Selection
Choose which environment and add-ons you want to install.
Рисунок 9.14. Software Selection

By default, Fedora installs the GNOME Desktop Environment, but in Software Selection you can choose from a range of other environments and customise additional packages to be installed as add-ons. Available environments are listed in the left-hand pane. To select an environment, click the radio button that corresponds to one of the following options:
Graphical Desktops (multiple options)
Fedora offers a variety of graphical desktop environments, which can be enhanced with add-ons such as the LibreOffice productivity suite, graphical tools such as the GIMP, and multimedia applications. The available environments are:
  • GNOME Desktop
  • KDE Plasma Workspaces
  • Xfce Desktop
  • LXDE Desktop
  • Cinnamon Desktop
  • MATE Desktop
  • Sugar Desktop Environment
Development and Creative Workstation
This option provides the necessary tools to compile software and develop graphics and other content on your Fedora system.
Web Server
Эта опция позволяет установить веб-сервер Apache.
Infrastructure Server
This option provides a server for operating network infrastructure services.
Basic X Window System
This option provides the X Window System without a full graphical desktop environment.
Minimal Install
This option provides only the packages essential to run Fedora. A minimal installation provides the basis for a single-purpose server or desktop appliance and maximizes performance and security on such an installation.
Fedora will automatically install the base and mandatory packages for the environment you select, but you can select additional package groups, or add-ons, from the right-hand pane. The list of add-ons is refreshed when a new environment is selected. Add-ons range from common utilities such as Administrative Tools and LibreOffice to specialist tools such as Medical Applications and Robotics
To specify add-ons for installation as part of the environment, select the check box next to each add-on.
Once you have selected an environment and any additional packages you may wish to install, click Done to return to the pre-installation hub.
The packages that you select are not permanent. After you boot your system, use the Add/Remove Software tool to either install new software or remove installed packages. To run this tool, from the main menu, select SystemAdministrationAdd/Remove Software. The Fedora software management system downloads the latest packages from network servers, rather than using those on the installation discs.

9.10.1. Installing from Additional Repositories

You can define additional repositories to increase the software available to your system during installation. A repository is a network location that stores software packages along with metadata that describes them. Many of the software packages used in Fedora require other software to be installed. The installer uses the metadata to ensure that these requirements are met for every piece of software you select for installation.
The basic options are:
  • Репозиторий установки будет выбран автоматически. Он включает программное обеспечение для установочного CD/DVD.
  • Fedora 17 - i386 содержит полную коллекцию программ Fedora 17 плюс стабильные версии дополнительных программ. При выполнении установки Fedora 17 с набора дисков CD или DVD эта опция не предложит дополнительных функций, но при установке с LiveCD вы получите доступ к широкому диапазону пакетов. Для этого компьютер должен иметь доступ к Интернету.
  • Репозиторий Fedora 17 - i386 - Updates содержит полную коллекцию пакетов Fedora 17 плюс стабильные версии дополнительных программ. Этот вариант не только установит выбранное программное обеспечение, но и гарантирует наличие последних версий. Для этого компьютер должен иметь доступ к Интернету.
For more information about clustering with Fedora 17, refer to the Fedora 17 Cluster Suite Overview, available from https://access.redhat.com/knowledge/docs/manuals/.
Adding a software repository
Enter the details of additional software repositories.
Рисунок 9.15. Adding a software repository

To include software from extra repositories, select Add additional software repositories and provide the location of the repository.
To edit an existing software repository location, select the repository in the list and then select Modify repository.

Network Access Required

If you change the repository information during a non-network installation, such as from a Fedora DVD, the installer prompts you for network configuration information.
If you change the repository information during a non-network installation, such as from a Fedora DVD, the installer prompts you for network configuration information.
Select network interface
The Select network interface dialog.
Рисунок 9.16. Select network interface

  1. Select an interface from the drop-down menu.
  2. Click OK.
Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface.
Сетевые соединения
Настройка сетевых соединений.
Рисунок 9.17. Сетевые соединения

For details of how to use NetworkManager, refer to Раздел 9.9, «Network configuration»
If you select Add additional software repositories, the Edit repository dialog appears. Provide a Repository name and the Repository URL for its location.

Fedora Software Mirrors

To find a Fedora software mirror near you, refer to http://mirrors.fedoraproject.org/publiclist/.
Once you have located a mirror, to determine the URL to use, find the directory on the mirror that contains a directory named repodata.
Once you provide information for an additional repository, the installer reads the package metadata over the network. Software that is specially marked is then included in the package group selection system.

Backtracking Removes Repository Metadata

If you choose Back from the package selection screen, any extra repository data you may have entered is lost. This allows you to effectively cancel extra repositories. Currently there is no way to cancel only a single repository once entered.

9.10.2. Core Network Services

Все установки Fedora включают следующие сетевые службы:
  • centralized logging through syslog
  • email through SMTP (Simple Mail Transfer Protocol)
  • network file sharing through NFS (Network File System)
  • remote access through SSH (Secure SHell)
  • resource advertising through mDNS (multicast DNS)
The default installation also provides:
  • network file transfer through HTTP (HyperText Transfer Protocol)
  • printing through CUPS (Common UNIX Printing System)
  • remote desktop access through VNC (Virtual Network Computing)
Некоторые автоматизированные процессы в Fedora для отправки отчетов и сообщений системному администратору используют электронную почту. Службы электронной почты, журналирования и печати по умолчанию не принимают подключения из других систем. Fedora устанавливает компоненты совместного доступа NFS, HTTP и VNC, но не активирует их по умолчанию.
Можно настроить систему Fedora так, чтобы она предоставляла службы электронной почты, совместного доступа, журналирования, печати и доступа к удаленному рабочему столу. SSH в Fedora активируется по умолчанию. Для доступа к файлам, расположенным в другой системе, можно использовать NFS без необходимости активации службы совместного доступа NFS.

9.11. Устройства хранения

You can install Fedora on a large variety of storage devices. This screen allows you to select either basic or specialized storage devices.
Устройства хранения
Окно выбора стандартных или специализированных устройств хранения
Рисунок 9.18. Устройства хранения

Basic Storage Devices
Select Basic Storage Devices to install Fedora on the following storage devices:
  • на напрямую подключенные жесткие диски и твердотельные накопители.
Specialized Storage Devices
Select Specialized Storage Devices to install Fedora on the following storage devices:
  • в сети хранения данных (SAN, Storage Area Networks);
  • Direct access storage devices (DASDs)
  • на микропрограммные RAID-устройства;
  • на многопутевые устройства.
Use the Specialized Storage Devices option to configure Internet Small Computer System Interface (iSCSI) and FCoE (Fiber Channel over Ethernet) connections.
Если вы выбрали пункт Стандартные накопители, anaconda автоматически обнаружит подключенное устройство. Раздел 9.9, «Network configuration» содержит дальнейшую информацию.

9.11.1. Окно выбора устройств хранения

В этом окне показаны все доступные программе anaconda устройства хранения.
Выбор устройств хранения. Стандартные устройства
The Basic Devices tab
Рисунок 9.19. Выбор устройств хранения. Стандартные устройства

Выбор устройств хранения. Многопутевые устройства.
Вкладка многопутевых устройств
Рисунок 9.20. Выбор устройств хранения. Многопутевые устройства.

Выбор устройств хранения. Другие устройства SAN.
Вкладка других устройств SAN
Рисунок 9.21. Выбор устройств хранения. Другие устройства SAN.

Устройства сгруппированы следующим образом:
Basic Devices
Это устройства, напрямую подключенные в локальную систему (например, жесткие диски).
Firmware RAID
Накопители, подключенные к микропрограммному RAID-контроллеру.
Multipath Devices
Storage devices accessible through more than one path, such as through multiple SCSI controllers or Fiber Channel ports on the same system.

Important — device serial numbers must be 16 or 32 characters

The installer only detects multipath storage devices with serial numbers that are 16 or 32 characters in length.
Other SAN Devices
Любые другие устройства в сети хранения данных.
Если настройка устройств iSCSI и FCoE не требуется, нажмите кнопку Добавить (см. Раздел 9.11.1.1, « Advanced Storage Options »).
To assign non-friendly multipath device names, click Device Options and uncheck Use friendly names for multipath devices.
Экран выбора устройств содержит вкладку поиска, где можно отфильтровать устройства хранения по идентификатору WWID (World Wide Identifier), порту, цели или номеру LUN (Logical Unit Number).
Вкладка поиска устройств хранения
В раскрывающемся списке можно выбрать критерий поиска (порт, цель, LUN, WWID) и соответствующие ему текстовые поля.
Рисунок 9.22. Вкладка поиска устройств хранения

На этой вкладке вы увидите раскрывающееся меню, где можно выбрать критерий поиска (порт, цель, LUN, WWID) и соответствующие текстовые поля.
На каждой вкладке будет представлен список обнаруженных программой anaconda устройств и критерии, помогающие их идентифицировать. Справа от заголовков столбцов расположено небольшое раскрывающееся меню, где можно выбрать характеристики устройства для просмотра. Например, в меню на вкладке Многопутевые устройства можно дополнительно показать WWID, емкость, поставщик, взаимосвязь, пути.
Выбор столбцов
Раскрытое меню
Рисунок 9.23. Выбор столбцов

Each device is presented on a separate row, with a checkbox to its left. Click the checkbox to make a device available during the installation process, or click the radio button at the left of the column headings to select or deselect all the devices listed in a particular screen. Later in the installation process, you can choose to install Fedora onto any of the devices selected here, and can choose to automatically mount any of the other devices selected here as part of the installed system.
Обратите внимание, что выбранные здесь устройства не будут очищены автоматически. Сам по себе выбор устройства на этом экране не подвергает его данные риску. Также стоит заметить, что даже если устройства не выбраны на этом этапе, их можно будет добавить в систему после установки, отредактировав файл /etc/fstab.

Important — chain loading

Any storage devices that you do not select on this screen are hidden from anaconda entirely. To chain load the Fedora boot loader from a different boot loader, select all the devices presented in this screen.
Выбрав устройства, нажмите кнопку продолжения. Раздел 9.13, «Initializing the Hard Disk» содержит дальнейшую информацию.

9.11.1.1. Advanced Storage Options

From this screen you can configure an iSCSI (SCSI over TCP/IP) target or FCoE (Fibre channel over ethernet) SAN (storage area network). Refer to Приложение B, ISCSI disks for an introduction to iSCSI.
Advanced Storage Options
Advanced Storage Options.
Рисунок 9.24. Advanced Storage Options

9.11.1.1.1. Select and configure a network interface
If a network interface is not already active on the system, anaconda must activate one through which to connect to the storage devices. If your system has only a single network interface, anaconda automatically activates it. However, if your system has more than one network interface available, anaconda prompts you with the Select network interface dialog to choose one to use during installation.
Select network interface
The Select network interface dialog.
Рисунок 9.25. Select network interface

  1. Select an interface from the drop-down menu.
  2. Click OK.
Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface.
Сетевые соединения
Настройка сетевых соединений.
Рисунок 9.26. Сетевые соединения

For details of how to use NetworkManager, refer to Раздел 9.9, «Network configuration»
9.11.1.1.2. Configure iSCSI parameters
To use iSCSI storage devices for the installation, anaconda must be able to discover them as iSCSI targets and be able to create an iSCSI session to access them. Each of these steps might require a username and password for CHAP (Challenge Handshake Authentication Protocol) authentication. Additionally, you can configure an iSCSI target to authenticate the iSCSI initiator on the system to which the target is attached (reverse CHAP), both for discovery and for the session. Used together, CHAP and reverse CHAP are called mutual CHAP or two-way CHAP. Mutual CHAP provides the greatest level of security for iSCSI connections, particularly if the username and password are different for CHAP authentication and reverse CHAP authentication.
Repeat the iSCSI discovery and iSCSI login steps as many times as necessary to add all required iSCSI storage. However, you cannot change the name of the iSCSI initiator after you attempt discovery for the first time. To change the iSCSI initiator name, you must restart the installation.
Процедура 9.1. iSCSI discovery
Use the iSCSI Discovery Details dialog to provide anaconda with the information that it needs to discover the iSCSI target.
The iSCSI Discovery Details dialog
The iSCSI Discovery Details dialog. It shows an example target IP address of 192.168.0.108 and an example iSCSI initiator name of iqn.1994-05.com.domain:01b1b85d.
Рисунок 9.27. The iSCSI Discovery Details dialog

  1. Enter the IP address of the iSCSI target in the Target IP Address field.
  2. Provide a name in the iSCSI Initiator Name field for the iSCSI initiator in iSCSI qualified name (IQN) format.
    A valid IQN contains:
    • the string iqn. (note the period)
    • a date code that specifies the year and month in which your organization's Internet domain or subdomain name was registered, represented as four digits for the year, a dash, and two digits for the month, followed by a period. For example, represent September 2010 as 2010-09.
    • your organization's Internet domain or subdomain name, presented in reverse order with the top-level domain first. For example, represent the subdomain storage.example.com as com.example.storage
    • a colon followed by a string that uniquely identifies this particular iSCSI initiator within your domain or subdomain. For example, :diskarrays-sn-a8675309.
    A complete IQN therefore resembles: iqn.2010-09.storage.example.com:diskarrays-sn-a8675309, and anaconda pre-populates the iSCSI Initiator Name field with a name in this format to help you with the structure.
    For more information on IQNs, refer to 3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI) available from http://tools.ietf.org/html/rfc3720#section-3.2.6 and 1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery available from http://tools.ietf.org/html/rfc3721#section-1.
  3. Use the drop-down menu to specify the type of authentication to use for iSCSI discovery:
    iSCSI discovery authentication
    The three types of discovery authentication available: no credentials, CHAP pair, and CHAP pair and a reverse pair.
    Рисунок 9.28. iSCSI discovery authentication

    • no credentials
    • CHAP pair
    • CHAP pair and a reverse pair
    • If you selected CHAP pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields.
      CHAP pair
      The iSCSI Discovery Details dialog with CHAP pair selected as the authentication type. Fields are displayed for username and password.
      Рисунок 9.29. CHAP pair

    • If you selected CHAP pair and a reverse pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password field and the username and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
      CHAP pair and a reverse pair
      The iSCSI Discovery Details dialog with CHAP pair and a reverse pair selected as the authentication type. Fields are displayed for CHAP username, CHAP password, reverse CHAP username, and reverse CHAP password.
      Рисунок 9.30. CHAP pair and a reverse pair

  4. Click Start Discovery. Anaconda attempts to discover an iSCSI target based on the information that you provided. If discovery succeeds, the iSCSI Discovered Nodes dialog presents you with a list of all the iSCSI nodes discovered on the target.
  5. Each node is presented with a checkbox beside it. Click the checkboxes to select the nodes to use for installation.
    The iSCSI Discovered Nodes dialog
    The iSCSI Discovered Nodes dialog displays a list of nodes with checkboxes beside them. This example shows only a single node, discovered at iqn.2009-02.com.example:for.all.
    Рисунок 9.31. The iSCSI Discovered Nodes dialog

  6. Click Login to initiate an iSCSI session.
Процедура 9.2. Starting an iSCSI session
Use the iSCSI Nodes Login dialog to provide anaconda with the information that it needs to log into the nodes on the iSCSI target and start an iSCSI session.
The iSCSI Nodes Login dialog
The iSCSI Nodes Login dialog.
Рисунок 9.32. The iSCSI Nodes Login dialog

  1. Use the drop-down menu to specify the type of authentication to use for the iSCSI session:
    iSCSI session authentication
    The three types of session authentication available: no credentials, CHAP pair, and CHAP pair and a reverse pair, plus the option to use the same credentials that were used for iSCSI discovery.
    Рисунок 9.33. iSCSI session authentication

    • no credentials
    • CHAP pair
    • CHAP pair and a reverse pair
    • Use the credentials from the discovery step
    If your environment uses the same type of authentication and same username and password for iSCSI discovery and for the iSCSI session, select Use the credentials from the discovery step to reuse these credentials.
    • If you selected CHAP pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields.
      CHAP pair
      The iSCSI Node Login dialog with CHAP pair selected as the authentication type. Fields are displayed for username and password.
      Рисунок 9.34. CHAP pair

    • If you selected CHAP pair and a reverse pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields and the username and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
      CHAP pair and a reverse pair
      The iSCSI Node Login dialog with CHAP pair and a reverse pair selected as the authentication type. Fields are displayed for CHAP username, CHAP password, reverse CHAP username, and reverse CHAP password.
      Рисунок 9.35. CHAP pair and a reverse pair

  2. Click Login. Anaconda attempts to log into the nodes on the iSCSI target based on the information that you provided. The iSCSI Login Results dialog presents you with the results.
    The iSCSI Login Results dialog
    The iSCSI Login Results dialog displays a list of attached nodes. This example shows only a single node attached, iqn.2009-02.com.example:for.all.
    Рисунок 9.36. The iSCSI Login Results dialog

  3. Click OK to continue.
9.11.1.1.3. Configure FCoE Parameters
To configure an FCoE SAN, select Add FCoE SAN and click Add Drive.
On the menu that appears in the next dialog box, select the network interface that is connected to your FCoE switch and click Add FCoE Disk(s).
Configure FCoE Parameters
Configure FCoE Parameters
Рисунок 9.37. Configure FCoE Parameters

Data Center Bridging (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Enable or disable the installer's awareness of DCB with the checkbox in this dialog.

9.12. Assign Storage Devices

If you selected more than one storage device on the storage devices selection screen (refer to Раздел 9.11, «Устройства хранения»), anaconda asks you to select which of these devices should be available for installation of the operating system, and which should only be attached to the file system for data storage. If you selected only one storage device, anaconda does not present you with this screen.
В процессе установки диски, выбранные на данном этапе в качестве устройств хранения, будут смонтированы без форматирования и создания разделов.
Выбор устройств хранения
Окно выбора устройств хранения для выполнения установки или хранения данных
Рисунок 9.38. Выбор устройств хранения

The screen is split into two panes. The left pane contains a list of devices to be used for data storage only. The right pane contains a list of devices that are to be available for installation of the operating system.
Each list contains information about the devices to help you to identify them. A small drop-down menu marked with an icon is located to the right of the column headings. This menu allows you to select the types of data presented on each device. Reducing or expanding the amount of information presented might help you to identify particular devices.
Move a device from one list to the other by clicking on the device, then clicking either the button labeled with a left-pointing arrow to move it to the list of data storage devices or the button labeled with a right-pointing arrow to move it to the list of devices available for installation of the operating system.
The list of devices available as installation targets also includes a radio button beside each device. Use this radio button to specify the device that you want to use as the boot device for the system.

Important — chain loading

If any storage device contains a boot loader that will chain load the Fedora boot loader, include that storage device among the Install Target Devices. Storage devices that you identify as Install Target Devices remain visible to anaconda during boot loader configuration.
Storage devices that you identify as Install Target Devices on this screen are not automatically erased by the installation process unless you selected the Use All Space option on the partitioning screen (refer to Раздел 9.15, «Disk Partitioning Setup»).
When you have finished identifying devices to be used for installation, click Next to continue.

9.13. Initializing the Hard Disk

If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive.
The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the Ignore all button or Re-initialize all button to apply the same answer to all devices.
Warning screen – initializing hard drive
Warning screen – initializing hard drive.
Рисунок 9.39. Warning screen – initializing hard drive

Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect.
To enable automatic initializing of hard disks for which it turns out to be necessary, use the kickstart command clearpart --initlabel (refer to Глава 15, Kickstart Installations)

Detach Unneeded Disks

If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation.

9.14. Upgrading an Existing System

Preupgrade

Fedora предоставляет утилиту командной строки preupgrade, позволяющую выполнить обновление существующей установки Fedora до новой версии.
The installation system automatically detects any existing installation of Fedora. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later.
Обратите внимание, что установочный носитель может не содержать все пакеты для обновления.

9.14.1. Экран обновления системы

If your system contains a Fedora installation, a dialog appears asking whether you want to upgrade that installation. To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select Next.
Экран обновления системы
Экран обновления системы
Рисунок 9.40. Экран обновления системы

Manually Installed Software

Software you have installed manually on your existing Fedora system may behave differently after an upgrade. You may need to manually reinstall or recompile this software after an upgrade to ensure it performs correctly on the updated system.

Re-installing Fedora

If you are re-installing the same version of Fedora, preserve your user data by placing it on a separate /home partition.

9.14.2. Upgrading Using the Installer

Installations are Recommended

In general, the Fedora Project recommends that you keep user data on a separate /home partition and perform a fresh installation. For more information on partitions and how to set them up, refer to Раздел 9.15, «Disk Partitioning Setup».
If you choose to upgrade your system using the installation program, any software not provided by Fedora that conflicts with Fedora software is overwritten. Before you begin an upgrade this way, make a list of your system's current packages for later reference:
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' > ~/old-pkglist.txt
After installation, consult this list to discover which packages you may need to rebuild or retrieve from sources other than the Fedora Project.
Next, make a backup of any system configuration data:
su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc' 
su -c 'mv /tmp/etc-*.tar.gz /home'
Make a complete backup of any important data before performing an upgrade. Important data may include the contents of your entire /home directory as well as content from services such as an Apache, FTP, or SQL server, or a source code management system. Although upgrades are not destructive, if you perform one improperly there is a small possibility of data loss.

Storing Backups

Note that the above examples store backup materials in a /home directory. If your /home directory is not a separate partition, you should not follow these examples verbatim! Store your backups on another device such as CD or DVD discs or an external hard disk.
Раздел 18.2, «Finishing an Upgrade» содержит дополнительную информацию о завершении процесса обновления.

9.14.3. Upgrading Boot Loader Configuration

Your completed Fedora installation must be registered in the boot loader to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to Приложение E, The GRUB Boot Loader for more information about boot loaders.
Диалог обновления загрузчика
Диалог содержит три переключателя: Обновить настройку загрузчика, Пропустить обновление загрузчика, Создать новую конфигурацию загрузчика.
Рисунок 9.41. Диалог обновления загрузчика

If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new Fedora system. To update the existing Linux boot loader, select Update boot loader configuration. This is the default behavior when you upgrade an existing Fedora installation.
GRUB is the standard boot loader for Fedora on 32-bit and 64-bit x86 architectures. If your machine uses another boot loader, such as BootMagic, System Commander, or the loader installed by Microsoft Windows, then the Fedora installation system cannot update it. In this case, select Skip boot loader updating. When the installation process completes, refer to the documentation for your product for assistance.
Install a new boot loader as part of an upgrade process only if you are certain you want to replace the existing boot loader. If you install a new boot loader, you may not be able to boot other operating systems on the same machine until you have configured the new boot loader. Select Create new boot loader configuration to remove the existing boot loader and install GRUB.
Сделав выбор, нажмите кнопку продолжения. Прочитайте Раздел 9.19, «Настройка загрузчика на платформах x86, AMD64 и Intel 64», если вы выбрали пункт Создать новую конфигурацию загрузчика. Если же вы решили обновить загрузчик или вообще пропустить его настройку, процесс установки продолжит работу.

9.15. Disk Partitioning Setup

Warning — Back up your data

It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your storage devices. Mistakes do happen and can result in the loss of all your data.

Important — Installing in text mode

If you install Fedora in text mode, you can only use the default partitioning schemes described in this section. You cannot add or remove partitions or file systems beyond those that the installer automatically adds or removes. If you require a customized layout at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation.
Furthermore, advanced options such as LVM, encrypted filesystems, and resizable filesystems are available only in graphical mode and kickstart.

Important — Booting from RAIDs

If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the /boot/ partition must be created on a 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.
A /boot/ partition is also necessary for software RAID setups.
If you have chosen to automatically partition your system, you should select Review and manually edit your /boot/ partition.
Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not sure how you want your system to be partitioned, read Приложение A, An Introduction to Disk Partitions for more information.
Disk Partitioning Setup
Choose automatic partitioning or manual partitioning.
Рисунок 9.42. Disk Partitioning Setup

On this screen you can choose to create the default partition layout in one of four different ways, or choose to partition storage devices manually to create a custom layout.
The first four options allow you to perform an automated installation without having to partition your storage devices yourself. If you do not feel comfortable with partitioning your system, choose one of these options and let the installation program partition the storage devices for you. Depending on the option that you choose, you can still control what data (if any) is removed from the system.
Your options are:
Use All Space
Select this option to remove all partitions on your hard drives (this includes partitions created by other operating systems such as Windows VFAT or NTFS partitions).

Warning

If you select this option, all data on the selected hard drives is removed by the installation program. Do not select this option if you have information that you want to keep on the hard drives where you are installing Fedora.
In particular, do not select this option when you configure a system to chain load the Fedora boot loader from another boot loader.
Replace Existing Linux System(s)
Select this option to remove only partitions created by a previous Linux installation. This does not remove other partitions you may have on your hard drives (such as VFAT or FAT32 partitions).
Shrink Current System
Select this option to resize your current data and partitions manually and install a default Fedora layout in the space that is freed.

Warning

If you shrink partitions on which other operating systems are installed, you might not be able to use those operating systems. Although this partitioning option does not destroy data, operating systems typically require some free space in their partitions. Before you resize a partition that holds an operating system that you might want to use again, find out how much space you need to leave free.
Use Free Space
Select this option to retain your current data and partitions and install Fedora in the unused space available on the storage drives. Ensure that there is sufficient space available on the storage drives before you select this option — refer to Раздел 4.4, «Достаточно ли дискового пространства?».

Warning

If your 64-bit x86 system uses UEFI instead of BIOS, you will need to manually create a /boot partition. This partition must have an ext3 file system. If you choose to partition automatically, your system will not boot.
Create Custom Layout
Select this option to partition storage devices manually and create customized layouts. Refer to Раздел 9.17, « Creating a Custom Layout or Modifying the Default Layout »
Choose your preferred partitioning method by clicking the radio button to the left of its description in the dialog box.
Select Encrypt system to encrypt all partitions except the /boot partition. Refer to Приложение C, Disk Encryption for information on encryption.
Select Use LVM to enable Logical Volume Management. Refer to Приложение D, Understanding LVM for information on LVM.
To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you by anaconda appear. You can make modifications to these partitions if they do not meet your needs.

Important — chain loading

To configure the Fedora boot loader to chain load from a different boot loader, you must specify the boot drive manually. If you chose any of the automatic partitioning options, you must now select the Review and modify partitioning layout option before you click Next or you cannot specify the correct boot drive.

Important — Mixing multipath and non-multipath devices

When you install Fedora on a system with multipath and non-multipath storage devices, the automatic partitioning layout in the installer might create volume groups that contain a mix of multipath and non-multipath devices. This defeats the purpose of multipath storage.
We advise that you select only multipath or only non-multipath devices on the disk selection screen that appears after selecting automatic partitioning. Alternatively, select custom partitioning.
Сделав выбор, нажмите Далее для продолжения установки.

9.16. Encrypt Partitions

If you selected the Encrypt System option, the installer prompts you for a passphrase with which to encrypt the partitions on the system.
Partitions are encrypted using the Linux Unified Key Setup — refer to Приложение C, Disk Encryption for more information.
Enter passphrase for encrypted partition
The dialog contains text boxes to enter a passphrase and to confirm it.
Рисунок 9.43. Enter passphrase for encrypted partition

Choose a passphrase and type it into each of the two fields in the dialog box. You must provide this passphrase every time that the system boots.

Warning — Do not lose this passphrase

If you lose this passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase.
Note that if you perform a kickstart installation of Fedora, you can save encryption passphrases and create backup encryption passphrases during installation. Refer to Раздел C.3.2, «Saving Passphrases» and Раздел C.3.3, «Creating and Saving Backup Passphrases».

9.17. Creating a Custom Layout or Modifying the Default Layout

If you chose one of the four automatic partitioning options and did not select Review, skip ahead to Раздел 9.10, «Software Selection».
If you chose one of the automatic partitioning options and selected Review, you can either accept the current partition settings (click Next), or modify the setup manually in the partitioning screen.
If you chose to create a custom layout, you must tell the installation program where to install Fedora. This is done by defining mount points for one or more disk partitions in which Fedora is installed. You may also need to create and/or delete partitions at this time.
If you have not yet planned how to set up your partitions, refer to Приложение A, An Introduction to Disk Partitions and Раздел 9.17.5, «Recommended Partitioning Scheme». At a bare minimum, you need an appropriately-sized root partition, and usually a swap partition appropriate to the amount of RAM you have on the system.
Anaconda can handle the partitioning requirements for a typical installation.
Partitioning on x86, AMD64, and Intel 64 Systems
The main partitioning screen.
Рисунок 9.44. Partitioning on x86, AMD64, and Intel 64 Systems

The partitioning screen contains two panes. The top pane contains a graphical representation of the hard drive, logical volume, or RAID device selected in the lower pane.
Above the graphical representation of the device, you can review the name of the drive (such as /dev/sda or LogVol00), its size (in MB), and its model as detected by the installation program.
Using your mouse, click once to highlight a particular field in the graphical display. Double-click to edit an existing partition or to create a partition out of existing free space.
The lower pane contains a list of all drives, logical volumes, and RAID devices to be used during installation, as specified earlier in the installation process — refer to Раздел 9.12, « Assign Storage Devices »
Devices are grouped by type. Click on the small triangles to the left of each device type to view or hide devices of that type.
Anaconda displays several details for each device listed:
Device
the name of the device, logical volume, or partition
Size (MB)
the size of the device, logical volume, or partition (in MB)
Mount Point/RAID/Volume
the mount point (location within a file system) on which a partition is to be mounted, or the name of the RAID or logical volume group of which it is a part
Type
the type of partition. If the partition is a standard partition, this field displays the type of file system on the partition (for example, ext4). Otherwise, it indicates that the partition is a physical volume (LVM), or part of a software RAID
Format
A check mark in this column indicates that the partition will be formatted during installation.
Beneath the lower pane are four buttons: Create, Edit, Delete, and Reset.
Select a device or partition by clicking on it in either the graphical representation in the upper pane of in the list in the lower pane, then click one of the four buttons to carry out the following actions:
Create
create a new partition, logical volume, or software RAID
Edit
change an existing partition, logical volume, or software RAID. Note that you can only shrink partitions with the Resize button, not enlarge partitions.
Delete
remove a partition, logical volume, or software RAID
Reset
undo all changes made in this screen

9.17.1. Create Storage

The Create Storage dialog allows you to create new storage partitions, logical volumes, and software RAIDs. Anaconda presents options as available or unavailable depending on the storage already present on the system or configured to transfer to the system.
Creating Storage
Creating new storage
Рисунок 9.45. Creating Storage

Options are grouped under Create Partition, Create Software RAID and Create LVM as follows:
Create Partition
Refer to Раздел 9.17.2, «Adding Partitions» for details of the Add Partition dialog.
Create Software RAID
  • RAID Partition — create a partition in unallocated space to form part of a software RAID device. To form a software RAID device, two or more RAID partitions must be available on the system.
  • RAID Device — combine two or more RAID partitions into a software RAID device. When you choose this option, you can specify the type of RAID device to create (the RAID level). This option is only available when two or more RAID partitions are available on the system.
Create LVM Logical Volume
  • LVM Physical Volume — create a physical volume in unallocated space.
  • LVM Volume Group — create a volume group from one or more physical volumes. This option is only available when at least one physical volume is available on the system.
  • LVM Logical Volume — create a logical volume on a volume group. This option is only available when at least one volume group is available on the system.

9.17.2. Adding Partitions

Для создания нового раздела нажмите кнопку Создать. Появится диалоговое окно (см. Рисунок 9.46, «Создание нового раздела»).

Примечание

You must dedicate at least one partition for this installation, and optionally more. For more information, refer to Приложение A, An Introduction to Disk Partitions.
Создание нового раздела
Создание нового раздела.
Рисунок 9.46. Создание нового раздела

  • Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter /; enter /boot for the /boot partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set — setting the filesystem type to swap is sufficient.
  • File System Type: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to Раздел 9.17.2.1, «File System Types».
  • Доступные устройства: В этом поле содержится список жестких дисков, установленных в вашей системе. Если жесткий диск выделен, значит требуемый раздел может быть создан на этом диске. Если диск не выделен, раздел на этом диске не может быть создан. С помощью различных настроек можно добиться того, чтобы anaconda разместила разделы там, где вам нужно, или позволить anaconda решать, где должны быть разделы.
  • Size (MB): Enter the size (in megabytes) of the partition. Note, this field starts with 200 MB; unless changed, only a 200 MB partition will be created.
  • Дополнительные опции размера: Определите, будет ли этот раздел иметь фиксированный размер, или вы позволите ему "вырасти" (заполнить все свободное дисковое пространство) до определенного размера, или же занять без ограничений все доступное на диске пространство.
    If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use.
  • Шифрование: позволяет зашифровать раздел. Тогда доступ к данным в этом разделе можно будет получить только при наличии парольной фразы. При выборе этой опции программа установки запросит ввод парольной фразы. Приложение C, Disk Encryption содержит подробную информацию о шифровании устройств хранения.
  • OK: Select OK once you are satisfied with the settings and wish to create the partition.
  • Cancel: Select Cancel if you do not want to create the partition.

9.17.2.1. File System Types

Fedora allows you to create different partition types and file systems. The following is a brief description of the different partition types and file systems available, and how they can be used.
Типы разделов
  • стандартный раздел может содержать файловую систему, пространство подкачки или может служить в качестве основы для создания программного RAID-массива или физического тома LVM.
  • swap — Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. Refer to the Fedora Deployment Guide for additional information.
  • software RAID — Creating two or more software RAID partitions allows you to create a RAID device. For more information regarding RAID, refer to the chapter RAID (Redundant Array of Independent Disks) in the Fedora Deployment Guide.
  • physical volume (LVM) — Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. For more information regarding LVM, refer to the Fedora Deployment Guide.
File systems
  • ext4 — The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journaling. The ext4 file system is selected by default and is highly recommended.
  • ext3 — The ext3 file system is based on the ext2 file system and has one main advantage — journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to fsck [2] the file system.
  • ext2 — An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters.
  • xfs — XFS is a highly scalable, high-performance file system that supports filesystems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes) and directory structures containing tens of millions of entries. XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file system can also be defragmented and resized while mounted and active.
  • vfat — файловая система Linux, совместимая с FAT и поддерживающая длинные имена файлов Microsoft Windows.

Примечание

The Btrfs file system is unavailable in Fedora 17.

9.17.3. Create Software RAID

Redundant arrays of independent disks (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and — in some configurations — greater fault tolerance. Refer to the Fedora Deployment Guide for a description of different kinds of RAIDs.
To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, select RAID to join the software RAID partitions into a RAID device.
RAID Partition
Choose this option to configure a partition for software RAID. This option is the only choice available if your disk contains no software RAID partitions. This is the same dialog that appears when you add a standard partition — refer to Раздел 9.17.2, «Adding Partitions» for a description of the available options. Note, however, that File System Type must be set to software RAID
Create a software RAID partition
The create a software RAID partition dialog.
Рисунок 9.47. Create a software RAID partition

RAID Device
Choose this option to construct a RAID device from two or more existing software RAID partitions. This option is available if two or more software RAID partitions have been configured.
Create a RAID device
The create a RAID device dialog.
Рисунок 9.48. Create a RAID device

Select the file system type as for a standard partition.
Anaconda automatically suggests a name for the RAID device, but you can manually select names from md0 to md15.
Click the checkboxes beside individual storage devices to include or remove them from this RAID.
The RAID Level corresponds to a particular type of RAID. Choose from the following options:
  • RAID 0 — distributes data across multiple storage devices. Level 0 RAIDs offer increased performance over standard partitions, and can be used to pool the storage of multiple devices into one large virtual device. Note that Level 0 RAIDS offer no redundancy and that the failure of one device in the array destroys the entire array. RAID 0 requires at least two RAID partitions.
  • RAID 1 — mirrors the data on one storage device onto one or more other storage devices. Additional devices in the array provide increasing levels of redundancy. RAID 1 requires at least two RAID partitions.
  • RAID 4 — distributes data across multiple storage devices, but uses one device in the array to store parity information that safeguards the array in case any device within the array fails. Because all parity information is stored on the one device, access to this device creates a bottleneck in the performance of the array. RAID 4 requires at least three RAID partitions.
  • RAID 5 — distributes data and parity information across multiple storage devices. Level 5 RAIDs therefore offer the performance advantages of distributing data across multiple devices, but do not share the performance bottleneck of level 4 RAIDs because the parity information is also distributed through the array. RAID 5 requires at least three RAID partitions.
  • RAID 6 — level 6 RAIDs are similar to level 5 RAIDs, but instead of storing only one set of parity data, they store two sets. RAID 6 requires at least four RAID partitions.
  • RAID 10 — level 10 RAIDs are nested RAIDs or hybrid RAIDs. Level 10 RAIDs are constructed by distributing data over mirrored sets of storage devices. For example, a level 10 RAID constructed from four RAID partitions consists of two pairs of partitions in which one partition mirrors the other. Data is then distributed across both pairs of storage devices, as in a level 0 RAID. RAID 10 requires at least four RAID partitions.

9.17.4. Create LVM Logical Volume

Important — LVM Unavailable in Text-Mode Installations

LVM initial set up is not available during text-mode installation. If you need to create an LVM configuration from scratch, press Alt+F2 to use a different virtual console, and run the lvm command. To return to the text-mode installation, press Alt+F1.
Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space, such as a hard drives or LUNs. Partitions on physical storage are represented as physical volumes that can be grouped together into volume groups. Each volume group can be divided into multiple logical volumes, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks.
To read more about LVM, refer to the Fedora Deployment Guide. Note, LVM is only available in the graphical installation program.
LVM Physical Volume
Choose this option to configure a partition or device as an LVM physical volume. This option is the only choice available if your storage does not already contain LVM Volume Groups. This is the same dialog that appears when you add a standard partition — refer to Раздел 9.17.2, «Adding Partitions» for a description of the available options. Note, however, that File System Type must be set to physical volume (LVM)
Create an LVM Physical Volume
The Create an LVM Physical Volume dialog.
Рисунок 9.49. Create an LVM Physical Volume

Make LVM Volume Group
Choose this option to create LVM volume groups from the available LVM physical volumes, or to add existing logical volumes to a volume group.
Make LVM Volume Group
The Make LVM Volume Group dialog.
Рисунок 9.50. Make LVM Volume Group

To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the Add, Edit and Delete options.
You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes.
Make Logical Volume
Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong.
Make Logical Volume
The Make Logical Volume dialog.
Рисунок 9.51. Make Logical Volume

9.17.5. Recommended Partitioning Scheme

9.17.5.1. x86, AMD64, and Intel 64 systems

Unless you have a reason for doing otherwise, we recommend that you create the following partitions for x86, AMD64, and Intel 64 systems:
  • A swap partition
  • A /boot partition
  • A / partition
  • A /home partition
  • Раздел подкачки (swap) (по меньшей мере 256 МБ) используется для поддержки виртуальной памяти. Данные попадают в раздел подкачки, когда вашей системе не хватает оперативной памяти для обработки данных.
    In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system.
    Swap space is usually designated during installation, but determining the memory workload of a system at this point can be difficult. During a kickstart installation, you can request that the amount of swap space be set automatically (refer to Раздел 15.4, «Kickstart Options».
    However, this setting is not precisely calibrated for your system, so use the following table if you require the amount of swap space to be set more precisely.
    Таблица 9.2. Рекомендуемый размер пространства подкачки
    Объем ОЗУ Рекомендуемый объем пространства подкачки
    до 4 ГБ ОЗУ минимум 2 ГБ для пространства подкачки
    от 4 до 16 ГБ ОЗУ минимум 4 ГБ для пространства подкачки
    от 16 до 64 ГБ ОЗУ минимум 8 ГБ для пространства подкачки
    от 64 до 256 ГБ ОЗУ минимум 16 ГБ для пространства подкачки
    от 256 до 512 ГБ ОЗУ минимум 32 ГБ для пространства подкачки

    Можно повысить производительность, распределив пространство подкачки между несколькими устройствами хранения. Разница будет особенно заметна в системах с быстрыми дисками, контроллерами и интерфейсами.
  • A /boot/ partition (250 MB)
    The partition mounted on /boot/ contains the operating system kernel (which allows your system to boot Fedora), along with files used during the bootstrap process. For most users, a 250 MB boot partition is sufficient.

    Important — Supported file systems

    The GRUB bootloader in Fedora 17 supports only the ext2, ext3, and ext4 (recommended) file systems. You cannot use any other file system for /boot, such as Btrfs, XFS, or VFAT.

    Note

    If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a /boot/ partition if you want the / (root) partition to use all of the remaining space on your hard drive.

    Note

    If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the /boot/ partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
  • A root partition (3.0 GB - 5.0 GB)
    This is where "/" (the root directory) is located. In this setup, all files (except those stored in /boot) are on the root partition.
    A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.

    Root and /root

    The / (or root) partition is the top of the directory structure. The /root directory/root (sometimes pronounced "slash-root") directory is the home directory of the user account for system administration.
  • A home partition (at least 100 MB)
    To store user data separately from system data, create a dedicated partition within a volume group for the /home directory. This will enable you to upgrade or reinstall Fedora without erasing user data files.
Many systems have more partitions than the minimum listed above. Choose partitions based on your particular system needs. Refer to Раздел 9.17.5.1.1, «Advice on Partitions» for more information.
If you create many partitions instead of one large / partition, upgrades become easier. Refer to the description of the Edit option in Раздел 9.17, « Creating a Custom Layout or Modifying the Default Layout » for more information.
The following table summarizes minimum partition sizes for the partitions containing the listed directories. You do not have to make a separate partition for each of these directories. For instance, if the partition containing /foo must be at least 500 MB, and you do not make a separate /foo partition, then the / (root) partition must be at least 500 MB.
Таблица 9.3. Minimum partition sizes
Directory Minimum size
/ 250 MB
/usr 250 MB, but avoid placing this on a separate partition
/tmp 50 MB
/var 384 MB
/home 100 MB
/boot 250 MB

Leave Excess Capacity Unallocated

Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur. To learn about a more flexible method for storage management, refer to Приложение D, Understanding LVM.
If you are not sure how best to configure the partitions for your computer, accept the default partition layout.
9.17.5.1.1. Advice on Partitions
Optimal partition setup depends on the usage for the Linux system in question. The following tips may help you decide how to allocate your disk space.
  • Рассмотрите возможность шифрования разделов, содержащих важные данные, для их защиты от неавторизованного доступа. Как минимум рекомендуется зашифровать раздел /home.
  • Each kernel installed on your system requires approximately 10 MB on the /boot partition. Unless you plan to install a great many kernels, the default partition size of 250 MB for /boot should suffice.

    Important — Supported file systems

    The GRUB bootloader in Fedora 17 supports only the ext2, ext3, and ext4 (recommended) file systems. You cannot use any other file system for /boot, such as Btrfs, XFS, or VFAT.
  • The /var directory holds content for a number of applications, including the Apache web server. It also is used to store downloaded update packages on a temporary basis. Ensure that the partition containing the /var directory has enough space to download pending updates and hold your other content.

    Warning

    The PackageKit update software downloads updated packages to /var/cache/yum/ by default. If you partition the system manually, and create a separate /var/ partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
  • Каталог /usr содержит основную часть программного обеспечения Fedora. Для установки стандартного набора пакетов потребуется примерно 4 ГБ пространства. Программистам, планирующим использовать Fedora для разработки ПО, рекомендуется как минимум удвоить это число.

    Do not place /usr on a separate file system

    If /usr is on a separate file system from /, the boot process becomes much more complex because /usr contains boot-critical components. In some situations (like installations on iSCSI drives), the boot process might not work at all.
  • Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other partitions to reallocate storage.
  • Распределение подкаталогов между разными разделами позволит сохранить их содержимое в случае переустановки Fedora. Например, если база данных MySQL хранится в /var/lib/mysql, можно поместить этот каталог в отдельный раздел, тогда ее не надо будет восстанавливать при переустановке.
  • If you are creating a custom partition layout on a non-EFI x86 system, you are strongly advised to create a separate, 1MB BIOS boot partition. This is only recommended on the disk you are installing the bootloader on and if any of the following conditions apply:
    • The disk contains a GPT partition table.
    • The installer has already initialized the disk for you.
    • You selected Use All Space in the Disk Partitioning Setup.
    This boot partition will be used by the GRUB boot loader for storage.
The following table is a possible partition setup for a system with a single, new 80 GB hard disk and 1 GB of RAM. Note that approximately 10 GB of the volume group is unallocated to allow for future growth.

Example Usage

This setup is not optimal for all use cases.
Пример 9.1. Example partition setup
Таблица 9.4. Example partition setup
Partition Size and type
/boot 250 МБ, ext3
swap 2 GB swap
LVM physical volume Remaining space, as one LVM volume group

The physical volume is assigned to the default volume group and divided into the following logical volumes:
Таблица 9.5. Example partition setup: LVM physical volume
Partition Size and type
/ 13 GB ext4
/var 4 GB ext4
/home 50 GB ext4


9.18. Write changes to disk

Программа установки попросит подтвердить выбранные настройки разбиения диска. Нажмите Сохранить изменения на диск для продолжения установки.
Writing storage configuration to disk
The Writing storage configuration to disk dialog box lets you choose to Write changes to disk or to Go back.
Рисунок 9.52. Writing storage configuration to disk

If you are certain that you want to proceed, click Write changes to disk.

Last chance to cancel safely

До этого момента в процессе установки программа установки не сохраняла изменения на вашем компьютере. При нажатии кнопки Сохранить изменения на диск программа установки выделит место на жестком диске и начнет установку Fedora. В зависимости от выбранной схемы разбиения диска на разделы, этот процесс может включать удаление существующих данных.
To revise any of the choices that you made up to this point, click Go back. To cancel installation completely, switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds.
После того, как вы нажали Записать изменения на диск, отменить установку будет невозможно. Если установка была прервана (например, компьютер был выключен), Вы не сможете использовать свой компьютер до тех пор, пока не перезапустите и не завершите процесс установки или пока не установите другую ОС.

9.19. Настройка загрузчика на платформах x86, AMD64 и Intel 64

To boot the system without boot media, you usually need to install a boot loader. A boot loader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel software. The kernel, in turn, initializes the rest of the operating system.

Installing in text mode

При выполнении установки в текстовом режиме загрузчик будет настроен автоматически и в процессе установки его настройки нельзя будет изменить.
GRUB (GRand Unified Bootloader), which is installed by default, is a very powerful boot loader. GRUB can load a variety of free operating systems, as well as proprietary operating systems with chain-loading (the mechanism for loading unsupported operating systems, such as Windows, by loading another boot loader). Note that Fedora 17 uses GRUB 2. GRUB Legacy is no longer actively developed.[3]

The GRUB boot menu

The GRUB menu defaults to being hidden, except on dual-boot systems. To show the GRUB menu during system boot, press and hold the Shift key before the kernel is loaded. (Any other key works as well but the Shift key is the safest to use.)
Настройка загрузчика
Настройте удобную вам загрузку системы.
Рисунок 9.53. Настройка загрузчика

Если на компьютере нет других операционных систем, программа установки установит загрузчик GRUB. Раздел 9.10, «Software Selection» содержит дальнейшую информацию.
You may have a boot loader installed on your system already. An operating system may install its own preferred boot loader, or you may have installed a third-party boot loader. If your boot loader does not recognize Linux partitions, you may not be able to boot Fedora. Use GRUB as your boot loader to boot Linux and most other operating systems. Follow the directions in this chapter to install GRUB.

Installing GRUB

If you install GRUB, it may overwrite your existing boot loader.
By default, the installation program installs GRUB in the master boot record or MBR, of the device for the root file system. To decline installation of a new boot loader, unselect Install boot loader on /dev/sda.

Warning

If you choose not to install GRUB for any reason, you will not be able to boot the system directly, and you must use another boot method (such as a commercial boot loader application). Use this option only if you are sure you have another way of booting the system!
Если на компьютере установлены другие операционные системы, Fedora попытается автоматически определить их и настроить GRUB для их загрузки. Это можно сделать самостоятельно, если GRUB не обнаружил системы.
Для добавления, удаления или изменения обнаруженных операционных систем воспользуйтесь соответствующими опциями.
Добавить
Выберите Добавить для добавления другой операционной системы в GRUB.
Из списка выберите раздел диска, содержащий операционную систему, и присвойте ему метку. GRUB будет показывать эту метку в меню загрузки.
Изменить
Для изменения записи в меню GRUB необходимо выбрать запись и нажать кнопку Изменить.
Удалить
Для удаления записи из меню GRUB необходимо ее выбрать и нажать кнопку Удалить.
Отметьте флажок По умолчанию напротив предпочитаемого раздела, чтобы выбрать систему, загружаемую по умолчанию. Если вы не выберете образ, загружаемый по умолчанию, вы не сможете продолжить установку.

Примечание

The Label column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system.
Once you have loaded the GRUB boot screen, use the arrow keys to choose a boot label or type e for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
Boot loader passwords provide a security mechanism in an environment where physical access to your server is available.
Если вы установили загрузчик, рекомендуется определить пароль для защиты системы. Если пароль загрузчика не задан, пользователи, имеющие доступ к компьютеру, могут передать ядру параметры и взломать защиту. Если пароль загрузчика установлен, для изменения его параметров сначала потребуется ввести пароль. Но если у кого-то есть физический доступ к компьютеру, то все же возможно его загрузить с дискеты, CD, DVD или устройства USB при условии поддержки BIOS. План по обеспечению безопасности систем также должен учитывать альтернативные методы загрузки.

GRUB Passwords Not Required

Если ваша система находится в безопасном окружении, то есть доступ к ней открыт только авторизованному персоналу, то пароль GRUB можно не задавать. Если же существует вероятность физического доступа к клавиатуре и монитору неавторизованными пользователями, они смогут перезагрузить систему и войти в GRUB. В таких случаях следует задать пароль.
If you choose to use a boot loader password to enhance your system security, be sure to select the checkbox labeled Use a boot loader password.
Once selected, enter a password and confirm it.
Whenever you are required to enter this password, you will also be asked for a username, which is root.
GRUB stores the password in encrypted form, so it cannot be read or recovered. If you forget the boot password, boot the system normally and then change the password entry in the /etc/grub.d/00_header file. Then, run grub2-mkconfig with root privileges to update the grub.cfg file with your updated password. If you cannot boot, you may be able to use the rescue mode on the Fedora installation DVD to reset the GRUB password.
You can later change the username in the /etc/grub.d/01_users file.

GRUB recognizes only the QWERTY keyboard layout

When selecting a GRUB password, be aware that GRUB recognizes only the QWERTY keyboard layout, regardless of the keyboard actually attached to the system. If you use a keyboard with a significantly different layout, it might be more effective to memorize a pattern of keystrokes rather than the word that the pattern produces.
To configure more advanced boot loader options, such as changing the drive order or passing options to the kernel, be sure Configure advanced boot loader options is selected before clicking Next.

9.19.1. Advanced Boot Loader Configuration

Now that you have chosen which boot loader to install, you can also determine where you want the boot loader to be installed. You may install the boot loader in one of two places:
  • Основная загрузочная запись (MBR, Master Boot Record) — рекомендуемое размещение загрузчика, если только в MBR не установлен другой загрузчик операционных систем, например System Commander. MBR — специальная область на диске, которую BIOS вашего компьютера автоматически загружает и передает ей управление процессом загрузки в первую очередь. При установке загрузчика в MBR, сразу после включения компьютера GRUB покажет строку приглашения, откуда можно загрузить Fedora или любую другую настроенную операционную систему.
  • The first sector of your boot partition — This is recommended if you are already using another boot loader on your system. In this case, your other boot loader takes control first. You can then configure that boot loader to start GRUB, which then boots Fedora.

    GRUB as a Secondary Boot Loader

    If you install GRUB as a secondary boot loader, you must reconfigure your primary boot loader whenever you install and boot from a new kernel. The kernel of an operating system such as Microsoft Windows does not boot in the same fashion. Most users therefore use GRUB as the primary boot loader on dual-boot systems.
Boot Loader Installation
Choose where to install a boot loader and how to configure it.
Рисунок 9.54. Boot Loader Installation

Примечание

If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the boot loader should not be installed on the MBR of the RAID array. Rather, the boot loader should be installed on the MBR of the same drive as the /boot/ partition was created.
Если вы будете использовать только Fedora, выберите MBR.
Click the Change Drive Order button if you would like to rearrange the drive order or if your BIOS does not return the correct drive order. Changing the drive order may be useful if you have multiple SCSI adapters, or both SCSI and IDE adapters, and you want to boot from the SCSI device.

If installing from USB, ensure boot loader is installed to hard drive

If you are installing Fedora from a USB, the boot loader will by default be installed to the MBR on the USB rather than the MBR on the hard drive. This will prevent the system booting once the installation is complete. To avoid this, select Change Device and reverse the order of the BIOS drives. /dev/sda is typically the hard drive and should be first in the BIOS Drive Order.

Примечание

While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the /boot Linux partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
In parted, 1024 cylinders equals 528MB. For more information, refer to:
http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html

9.19.2. Rescue Mode

Режим восстановления позволяет загрузить минимальное окружение Fedora целиком с загрузочного носителя вместо жесткого диска. Бывают ситуации, когда вы не можете полностью запустить Fedora, и не можете получить доступ к файлам на жестком диске компьютера. В режиме восстановления вы можете обращаться к файлам на жестком диске компьютера, даже если вы не смогли запустить Fedora с этого диска. Если нужно воспользоваться режимом восстановления, это можно сделать следующим способом:
  • Загрузить компьютер x86, AMD64 или Intel® 64 с выбранного установочного носителя (CD, DVD, USB, PXE) и ввести в строке приглашения загрузчика команду linux rescue. Глава 19, Basic System Recovery содержит подробную информацию о режиме восстановления.
For additional information, refer to the Fedora Deployment Guide.

9.19.3. Alternative Boot Loaders

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.20. The Progress Hub

Once you have completed all the required sections of the Pre-Installation Hub, click Continue and the installation will begin. How quickly this happens depends on the number of packages you have selected and your computer's speed.
Fedora reports the installation progress on the screen as it writes the selected packages to your system.
Packages completed
The Packages Completed progress bar
Рисунок 9.55. Packages completed

For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system.
While the packages are being installed, more configuration is required. Above the installation progress bar are items that need to be configured for Fedora to be fully installed. These items can be configured either while the packages are being installed or afterwards, but you will not be able to complete the installation process until they have been configured.
When you have configured the required items, click Finish configuration to complete the installation process.

9.20.1. Set the Root Password

Определение учетной записи и пароля root является одним из важнейших этапов установки системы. Учетная запись root подобна учетной записи администратора в Microsoft Windows и используется для установки, обновления пакетов и обслуживания системы. При входе в систему в режиме root пользователь получает полный контроль над системой.

Примечание

The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done only to perform system maintenance or administration.
Root Password
Setting your root password.
Рисунок 9.56. Root Password

Use the root account only for system administration. Create a non-root account for your general use and use the su command to change to root only when you need to perform tasks that require superuser authorization. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.

Примечание

To become root, type su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
The installation program requires you to set a root password[4] for your system. . You cannot proceed to the installation itself without entering a root password.
The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again.
You should make the root password something you can remember, but not something that is easy for someone else to guess. Your name, your phone number, qwerty, password, root, 123456, and anteater are all examples of bad passwords. Good passwords mix numerals with upper and lower case letters and do not contain dictionary words: Aard387vark or 420BMttNT, for example. Remember that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create.

Примечание

Do not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk.
Чтобы изменить пароль root после завершения установки, можно использовать утилиту настройки пароля root.
Выполните в приглашении оболочки команду system-config-users. Если вы не являетесь пользователем root, для продолжения будет предложено ввести пароль root.
Enter the root password into the Root Password field. Fedora displays the characters as asterisks for security. Type the same password into the Confirm field to ensure it is set correctly. After you set the root password, select Back to return to the Pre-Installation Hub.

9.21. Installation Complete

Congratulations! Now that you have configured the remaining settings, your Fedora installation is now complete!
Click Reboot to reboot your system and begin using Fedora. Remember to remove any installation media if it is not ejected automatically upon reboot.
After your computer's normal power-up sequence has completed, Fedora loads and starts. By default, the start process is hidden behind a graphical screen that displays a progress bar. Eventually, a login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears.
The first time you start your Fedora system in run level 5 (the graphical run level), the FirstBoot tool appears, which guides you through the Fedora configuration. Using this tool, you can set your system time and date, install software, configure your machine to receive software updates, and more. FirstBoot lets you configure your environment at the beginning, so that you can get started using your Fedora system quickly.


[2] The fsck application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
[4] 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.

Глава 10. Диагностика проблем при установке в системах Intel и AMD

В этой секции обсуждаются некоторые общие проблемы установки и их решения.
В целях отладки anaconda сохраняет журналы установки в каталог /tmp. Файлы включают:
/tmp/anaconda.log
общие сообщения anaconda
/tmp/program.log
все внешние программы, которые выполняет anaconda
/tmp/storage.log
информация о модулях хранения
/tmp/yum.log
сообщения установки с помощью yum
/tmp/syslog
сообщения об оборудовании
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. Невозможно загрузить Fedora

10.1.1. Are You Unable to Boot With Your RAID Card?

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?

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.
Если во время установки получена критическая ошибка «signal 11», возможно, это связано с аппаратной ошибкой памяти системной шины. Аппаратные сбои памяти могут быть вызваны ошибками программ или сбоями оборудования. Так же, как и другие операционные системы, Fedora выдвигает свои требования к оборудованию. Некоторые типы оборудования могут не соответствовать этим требованиям, даже если они корректно работали с другой операционной системой.
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:
	http://www.bitwizard.nl/sig11/

10.2. Trouble Beginning the Installation

10.2.1. Problems with Booting into the Graphical Installation

There are some video cards that have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it tries to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode.
В качестве решения попробуйте использовать стандартный видеодрайвер в процессе установки. Для этого в меню загрузки выберите Установить систему со стандартным видеодрайвером или в строке приглашения загрузчика укажите параметр xdriver=vesa. Также можно явно задать разрешение экрана с помощью параметра загрузки resolution=. Этот параметр особенно поможет пользователям ноутбуков. Кроме того, можно указать драйвер с помощью параметра driver=. Если это поможет, пожалуйста, сообщите в систему регистрации ошибок Bugzilla о том, что установщик не смог автоматически определить вашу видеокарту. Глава 11, Boot Options содержит дальнейшую информацию о параметрах загрузки.

Примечание

To disable frame buffer support and allow the installation program to run in text mode, try using the nofb boot option. This command may be necessary for accessibility with some screen reading hardware.

10.3. Проблемы во время установки

10.3.1. Ошибка: Не найдены устройства для установки Fedora

Если вы получили сообщение об ошибке, сообщающее о том, что не найдено устройств, пригодных для установки Fedora, возможно, SCSI-контроллер не распознан программой установки.

10.3.2. Сохранение сообщений отладки

Если anaconda столкнулась с проблемами после начала графической установки, появится информационное окно:
Окно создания отчета для сбоя
Произошло необработанное исключение. Вероятно, это ошибка. Пожалуйста, скопируйте полный текст исключения и заполните подробный отчет об ошибке Anaconda на по адресу https://bugzilla.redhat.com/bugzilla
Рисунок 10.1. Окно создания отчета для сбоя

Debug
показывает подробную информацию об ошибке:
Подробности сбоя
Трассировка и подробная информация о сбое
Рисунок 10.2. Подробности сбоя

Save
сохраняет информацию об ошибке на локальный или удаленный ресурс:
Exit
завершает процесс установки.
If you select Save from the main dialog, you can choose from the following options:
Report destination
Possible destinations for the error report: Red Hat Global Support, Red Hat Global Support (FTP), ftp, local, scp, Cancel.
Рисунок 10.3. Report destination

Red Hat Global Support
helps you to create a new support case for the issue that you encountered, or to append the details of the issue to an existing support case. Click Create Case or Attach to Existing Case as appropriate, or click Cancel to abandon sending details of the incident to Red Hat Global Support.
Open or Update a case with Red Hat Global Support
Red Hat Global Support selected, with options to Create Case, Attach to Existing Case, or Cancel.
Рисунок 10.4. Open or Update a case with Red Hat Global Support

Red Hat Global Support (FTP)
automatically saves details of the error to a location within Red Hat Global Support using FTP.
Save Crash Report to Red Hat Global Support (FTP)
Red Hat Global Support (FTP) selected, displaying location to which the report was uploaded.
Рисунок 10.5. Save Crash Report to Red Hat Global Support (FTP)

ftp
saves details of the error to a remote directory using FTP.
Сохранить отчет о сбое на удаленный сервер
ftp selected, displaying the field for the URL of the destination directory.
Рисунок 10.6. Сохранить отчет о сбое на удаленный сервер

local
saves details of the error to the local hard drive, in a directory that you select:
Сохранить отчет о сбое на локальный диск
Local disk selected, the field for the location in which to store the error report.
Рисунок 10.7. Сохранить отчет о сбое на локальный диск

scp
saves details of the error to a remote host using SCP.
Сохранить отчет о сбое на удаленный сервер
scp selected, displaying the field for the address of the destination host.
Рисунок 10.8. Сохранить отчет о сбое на удаленный сервер

Cancel
cancels saving the error report.

10.3.3. Trouble with Partition Tables

Если после этапа настройки разбиения диска (см. Раздел 9.15, «Disk Partitioning Setup») вы получаете сообщение, подобное следующему:
Таблица разделов на устройстве hda нечитаема. Для создания новых разделов устройство должно быть инициализировано. ВСЕ ДАННЫЕ на этом устройстве будут утеряны.
возможно, на диске отсутствует таблица разделов или эта таблица не опознается используемой программой разбиения диска.
Users who have used programs such as EZ-BIOS have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began) that could not be recovered.
Вне зависимости от выбранного типа установки следует создавать резервную копию данных вашего компьютера.

10.3.4. Using Remaining Space

You have a swap and a / (root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.
If your hard drive is more than 1024 cylinders, you must create a /boot partition if you want the / (root) partition to use all of the remaining space on your hard drive.

10.3.5. Other Partitioning Problems

If you create partitions manually, but cannot move to the next screen, you probably have not created all the partitions necessary for installation to proceed.
You must have the following partitions as a bare minimum:
  • A / (root) partition
  • A <swap> partition of type swap

Примечание

Определив тип раздела как swap, не назначайте ему точку подключения. Anaconda назначит точку подключения такого диска автоматически.

10.4. Problems After Installation

10.4.1. Trouble With the Graphical GRUB Screen on an x86-based System?

If you are experiencing problems with GRUB, you may need to disable the graphical boot screen. To do this, temporarily alter the setting at boot time before changing it permanently.
At boot time, press Esc to reach the GRUB splash screen. Select the GRUB line, and type e.
Edit the kernel line to remove rhgb.
Press Enter to exit the editing mode.
Once the boot loader screen has returned, type b to boot the system.
If your problems with GRUB are now resolved and you want to make the change permanent, become the root user and edit the /etc/default/grub file.
Within the grub file, comment out the line which begins with GRUB_TERMINAL=console by inserting the # character at the beginning of the line.
Refresh the grub.cfg file by running grub2-mkconfig with root privileges. The changes you have made will then take effect.
You may re-enable the graphical boot screen by uncommenting (or adding) the above line back into the /etc/default/grub file.

10.4.2. Blocked by a GRUB command line after upgrading?

If you have restarted your machine after upgrading Fedora but cannot progress beyond the GRUB command line, you will need to issue commands to boot the operating system and then make the changes persistent once Fedora has loaded.
  1. At the GRUB command line, display the superseded GRUB configuration file with the following command:
    cat (hdpartitionnumber,drivenumber)/grub/grub.conf
    partitionnumber and drivenumber refer to the location of your Fedora /boot directory. If you do not know the location, boot the machine using a Fedora live CD to find out and then reboot to return to the GRUB command line. Refer to Раздел E.4.1, «Device Names» for help with partition numbering.
  2. 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
  3. Run the boot command.
  4. Once Fedora has loaded, refresh the GRUB configuration file to make the changes persistent:
    grub2-mkconfig -o /boot/grub2/grub.cfg

10.4.3. Booting into a Graphical Environment

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 edit one file, /etc/inittab, by changing just one number in the runlevel section. When you are finished, reboot the computer. The next time you log in, you are presented with a graphical login prompt.
Open a shell prompt. If you are in your user account, become root by typing the su command.
Now, type gedit /etc/inittab to edit the file with gedit. The file /etc/inittab opens. Within the first screen, a section of the file which looks like the following appears:
# Default runlevel. The runlevels used are: 
#   0 - halt (Do NOT set initdefault to this) 
#   1 - Single user mode 
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking) 
#   3 - Full multiuser mode 
#   4 - unused 
#   5 - X11 
#   6 - reboot (Do NOT set initdefault to this) 
#
id:3:initdefault:
To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5.

Warning

Change only the number of the default runlevel from 3 to 5.
Your changed line should look like the following:
	 id:5:initdefault: 
When you are satisfied with your change, save and exit the file using the Ctrl+Q keys. A window appears and asks if you would like to save the changes. Click Save.
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)

If you are having trouble getting X (the X Window System) to start, you may not have installed it during your installation.
Если вам нужна система X, вы можете либо установить пакеты с установочных носителей Fedora, либо выполнить обновление.
If you elect to upgrade, select the X Window System packages, and choose GNOME, KDE, or both, during the upgrade package selection process.
Раздел 18.3, «Switching to a Graphical Login» содержит дальнейшую информацию об установке окружения рабочего стола.

10.4.5. Problems with the X Server Crashing and Non-Root Users

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

If you did not create a user account in the firstboot screens, 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?

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.
  2. Reboot, and once you have loaded the GRUB boot screen, type e for edit.
  3. 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.
  4. At the end of the kernel line, add
    mem=xxM
    where xx equals the amount of RAM in your system, then press Enter to exit edit mode.
  5. Once the boot loader screen has returned, type b to boot the system.
  6. Run cat /proc/meminfo again. If the known amount of RAM in your system is now displayed, add the following line to the /etc/grub.d/10_linux file to make the change permanent:
    mem=xxM
    Replace xx with the amount of RAM you have in megabytes.
  7. To update the grub.cfg file so that the change will take effect, run grub2-mkconfig with root privileges.
In 10_linux, the above example would look similar to the following:
default=0 
timeout=30 
splashimage=(hd0,1)/grub/splash.xpm.gz 
menuentry 'Fedora Linux, with Linux 3.1.0-0.rc6.git0.3.fc16.x86_64'
set root=(hd0,1)
linux /vmlinuz-(2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 mem=8192M
initrd /initrd-(2.6.32.130.el6.i686.img

10.4.8. Your Printer Does Not Work

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

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

Часть II. 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.

Содержание

11. Boot Options
11.1. Configuring the Installation System at the Boot Menu
11.1.1. Specifying the Language
11.1.2. Configuring the Interface
11.1.3. Updating anaconda
11.1.4. Specifying the Installation Method
11.1.5. Specifying the Network Settings
11.2. Enabling Remote Access to the Installation System
11.2.1. Enabling Remote Access with VNC
11.2.2. Connecting the Installation System to a VNC Listener
11.2.3. Enabling Remote Access with ssh
11.3. Logging to a Remote System During the Installation
11.3.1. Configuring a Log Server
11.4. Automating the Installation with Kickstart
11.5. Enhancing Hardware Support
11.5.1. Overriding Automatic Hardware Detection
11.6. Using the Maintenance Boot Modes
11.6.1. Загрузка режима тестирования памяти (ОЗУ)
11.6.2. Verifying boot media
11.6.3. Booting Your Computer with the Rescue Mode
11.6.4. Upgrading your computer
12. Installing Without Media
12.1. Retrieving Boot Files
12.2. Editing the GRUB Configuration
12.3. Booting to Installation
13. Setting Up an Installation Server
13.1. Setting Up cobbler
13.2. Setting Up the Distribution
13.3. Mirroring a Network Location
13.4. Importing the Distribution
13.5. Manually configure a PXE server
13.5.1. Setting up the Network Server
13.5.2. PXE Boot Configuration
13.5.3. Starting the tftp Server
13.5.4. Adding a Custom Boot Message
13.5.5. Performing the PXE Installation
14. Installing Through VNC
14.1. VNC Viewer
14.2. VNC Modes in Anaconda
14.2.1. Direct Mode
14.2.2. Connect Mode
14.3. Installation Using VNC
14.3.1. Installation Example
14.3.2. Kickstart Considerations
14.3.3. Firewall Considerations
14.4. References
15. Kickstart Installations
15.1. What are Kickstart Installations?
15.2. How Do You Perform a Kickstart Installation?
15.3. Creating the Kickstart File
15.4. Kickstart Options
15.4.1. Advanced Partitioning Example
15.5. Package Selection
15.6. Pre-installation Script
15.6.1. Example
15.7. Post-installation Script
15.7.1. Example
15.8. Making the Kickstart File Available
15.8.1. Creating Kickstart Boot Media
15.8.2. Making the Kickstart File Available on the Network
15.9. Making the Installation Tree Available
15.10. Starting a Kickstart Installation
16. Kickstart Configurator
16.1. Basic Configuration
16.2. Installation Method
16.3. Boot Loader Options
16.4. Partition Information
16.4.1. Creating Partitions
16.5. Network Configuration
16.6. Authentication
16.7. Firewall Configuration
16.7.1. SELinux Configuration
16.8. Display Configuration
16.9. Package Selection
16.10. Pre-Installation Script
16.11. Post-Installation Script
16.11.1. Chroot Environment
16.11.2. Use an Interpreter
16.12. Saving the File

Глава 11. Boot Options

Система установки Fedora включает целый ряд возможностей и опций для администраторов. Для использования параметров загрузки введите linux параметр в приглашении boot:.
To access the boot: prompt on a system that displays a graphical boot screen, press the Esc key while the graphical boot screen is displayed.
If you specify more than one option, separate each of the options by a single space. For example:
linux option1 option2 option3

Anaconda Boot Options

Программа установки Anaconda имеет множество параметров загрузки, большая часть которых перечислена на вики-странице http://fedoraproject.org/wiki/Anaconda/Options.

Kernel Boot Options

На странице http://fedoraproject.org/wiki/KernelCommonProblems перечислены типичные параметры загрузки ядра. Полный список параметров содержится в файле /usr/share/doc/kernel-doc-версия/Documentation/kernel-parameters.txt, который устанавливается вместе с пакетом kernel-doc.

Rescue Mode

The Fedora installation and rescue discs may either boot with rescue mode, or load the installation system. For more information on rescue discs and rescue mode, refer to Раздел 11.6.3, «Booting Your Computer with the Rescue Mode».

11.1. Configuring the Installation System at the Boot Menu

You can use the boot menu to specify a number of settings for the installation system, including:
  • язык
  • display resolution
  • interface type
  • Installation method
  • network settings

11.1.1. Specifying the Language

To set the language for both the installation process and the final system, specify the ISO code for that language with the lang option. Use the keymap option to configure the correct keyboard layout.
For example, the ISO codes el_GR and gr identify the Greek language and the Greek keyboard layout:
linux lang=el_GR keymap=gr

11.1.2. Configuring the Interface

Для использования конкретного разрешения экрана введите resolution=значение в качестве параметра загрузки. Например, для разрешения 1024x768 введите:
linux resolution=1024x768
To run the installation process in text mode, enter:
linux text
To enable support for a serial console, enter serial as an additional option.
Use display=ip:0 to allow remote display forwarding. In this command, ip should be replaced with the IP address of the system on which you want the display to appear.
On the system you want the display to appear on, you must execute the command xhost +remotehostname, where remotehostname is the name of the host from which you are running the original display. Using the command xhost +remotehostname limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.

11.1.3. Updating anaconda

Для установки Fedora можно использовать новую версию программы установки anaconda, возможно, более новую по сравнению с версией на вашем установочном носителе.
The boot option
  linux updates
покажет запрос дискеты с обновлениями anaconda. Не требуется задавать этот параметр, если вы выполняете установку по сети и уже поместили содержимое образа с обновлениями в rhupdates/ на сервере.
To load the anaconda updates from a network location instead, use:
  linux updates=
followed by the URL for the location where the updates are stored.

11.1.4. Specifying the Installation Method

askmethod and asknetwork are deprecated.

The askmethod and asknetwork options are no longer available. Use root= to specify the installation method, and see Раздел 11.1.5, «Specifying the Network Settings» to configure network interfaces.
Чтобы задать метод установки в приглашении boot:, используйте параметр repo (см. Таблица 11.1, «Installation methods»).
Таблица 11.1. Installation methods
Installation method Option format
привод CD/DVD repo=cdrom:устройство
Hard Drive repo=hd:устройство/путь
HTTP Server repo=http://узел/путь
FTP Server repo=ftp://пользователь:пароль@узел/путь
NFS Server repo=nfs:сервер:/путь
ISO images on an NFS Server repo=nfsiso:сервер:/путь

11.1.5. Specifying the Network Settings

Normally, anaconda prompts you to configure a network interface if one is needed during installation. However, if your network cannot be configured automatically via DHCP and you need a network connection from the beginning of the installation, you can provide network settings with options at the boot: prompt. Such a connection may be required if you need to access an updates.img or kickstart file over a network, for example.
The available network configuration boot options include:
ip
the IP address for system
netmask
the netmask for the system
gateway
the IP address of the network gateway
dns
the IP address of the network DNS server
ksdevice
the network device to use with these settings
This example configures the network settings for an installation system that uses the IP address 192.168.1.10 for interface eth0:
linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.3 ksdevice=eth0
If you specify the network configuration and network device at the boot: prompt, these settings are used for the installation process and the Networking Devices and Configure TCP/IP dialogs do not appear.

11.2. Enabling Remote Access to the Installation System

You may access a graphical interface for the installation system from any other system. To remotely access the graphical display of an installation system, use client software that supports the VNC (Virtual Network Computing) display protocol.

Установка клиента VNC в Fedora

Fedora includes the VNC client vncviewer. To obtain vncviewer, install the tigervnc package.
The installation system supports two methods of establishing a VNC connection. You may start the installation, and manually login to the graphical display with a VNC client on another system. Alternatively, you may configure the installation system to automatically connect to a VNC client on the network that is running in listening mode.

11.2.1. Enabling Remote Access with VNC

Чтобы включить удаленный графический доступ к системе установки, в строке приглашения введите два параметра:
linux vnc vncpassword=qwerty
The vnc option enables the VNC service. The vncpassword option sets a password for remote access. The example shown above sets the password as qwerty.

VNC Passwords

The VNC password must be at least six characters long.
Specify the language, keyboard layout and network settings for the installation system with the screens that follow. You may then access the graphical interface through a VNC client. The installation system displays the correct connection setting for the VNC client:
Starting VNC...
The VNC server is now running.
Please connect to computer.mydomain.com:1 to begin the install...
Starting graphical installation...
Press <enter> for a shell
Затем вы можете войти в систему установки с помощью клиента VNC. Для запуска клиента vncviewer в Fedora выберите ПриложенияСтандартныеVNC Viewer или выполните команду vncviewer в окне терминала. В открывшемся окне введите имя сервера и номер экрана. В приведенном выше примере в качестве VNC-сервера будет выступать узел computer.mydomain.com:1.

11.2.2. Connecting the Installation System to a VNC Listener

Чтобы система установки автоматически подключалась к VNC-клиенту, сначала запустите клиент в режиме прослушивания . В Fedora используйте параметр -listen для запуска vncviewer в режиме прослушивания. В окне терминала выполните:
 vncviewer -listen

Firewall Reconfiguration Required

By default, vncviewer uses TCP port 5500 when in listening mode. To permit connections to this port from other systems, choose SystemAdministration Firewall. Select Other ports, and Add. Enter 5500 in the Port(s) field, and specify tcp as the Protocol.
Once the listening client is active, start the installation system and set the VNC options at the boot: prompt. In addition to vnc and vncpassword options, use the vncconnect option to specify the name or IP address of the system that has the listening client. To specify the TCP port for the listener, add a colon and the port number to the name of the system.
For example, to connect to a VNC client on the system desktop.mydomain.com on the port 5500, enter the following at the boot: prompt:
linux vnc vncpassword=qwerty vncconnect=desktop.mydomain.com:5500

11.2.3. Enabling Remote Access with ssh

To enable remote access to a text mode installation to monitor and debug the installer, use the sshd=1 option at the boot: prompt:
linux sshd=1
You can then connect to the installation system with the ssh utility. The ssh command requires the name or IP address of the installation system, and a password if you specified one (for example, in a kickstart file).

11.3. Logging to a Remote System During the Installation

By default, the installation process sends log messages to the console as they are generated. You may specify that these messages go to a remote system that runs a syslog service.
To configure remote logging, add the syslog option. Specify the IP address of the logging system, and the UDP port number of the log service on that system. By default, syslog services that accept remote messages listen on UDP port 514.
For example, to connect to a syslog service on the system 192.168.1.20, enter the following at the boot: prompt:
linux syslog=192.168.1.20:514

11.3.1. Configuring a Log Server

Службу syslog в Fedora предоставляет rsyslog. Стандартная настройка rsyslog не принимает сообщения от удаленных систем.

Only Enable Remote Syslog Access on Secured Networks

The rsyslog configuration detailed below does not make use of any of the security measures available in rsyslog Crackers may slow or crash systems that permit access to the logging service, by sending large quantities of false log messages. In addition, hostile users may intercept or falsify messages sent to the logging service over the network.
Чтобы настроить в Fedora прием сообщений журналирования из других систем в сети, потребуется внести изменения в файл /etc/rsyslog.conf. Для его редактирования нужны привилегии root. Снимите комментарий со следующих строк, удалив символ «решетки» в начале каждой строки:
$ModLoad imudp.so
	$UDPServerRun 514
Restart the rsyslog service to apply the change:
su -c '/sbin/service rsyslog restart'
По запросу введите пароль пользователя root.

Firewall Reconfiguration Required

By default, the syslog service listens on UDP port 514. To permit connections to this port from other systems, choose SystemAdministration Firewall. Select Other ports, and Add. Enter 514 in the Port(s) field, and specify udp as the Protocol.

11.4. Automating the Installation with Kickstart

You can allow an installation to run unattended by using Kickstart. A Kickstart file specifies settings for an installation. Once the installation system boots, it can read a Kickstart file and carry out the installation process without any further input from a user.

Every Installation Produces a Kickstart File

The Fedora installation process automatically writes a Kickstart file that contains the settings for the installed system. This file is always saved as /root/anaconda-ks.cfg. You may use this file to repeat the installation with identical settings, or modify copies to specify settings for other systems.

Important — Kickstart installations and firstboot

Firstboot does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the user option in the Kickstart file before installing additional systems from it (refer to Раздел 15.4, «Kickstart Options» for details) or log into the installed system with a virtual console as root and add users with the adduser command.
Fedora включает в свой состав графическое приложение для создания и редактирования кикстарт-файлов путем выбора требуемых параметров. Для его установки используйте пакет system-config-kickstart. Чтобы запустить редактор, выберите ПриложенияСистемные утилитыKickstart.
Kickstart files list installation settings in plain text, with one option per line. This format lets you modify your Kickstart files with any text editor, and write scripts or applications that generate custom Kickstart files for your systems.
To automate the installation process with a Kickstart file, use the ks option to specify the name and location of the file:
 linux ks=location/kickstart-file.cfg
Допускается использовать файлы, расположенные на съемных устройствах хранения, жестком диске или сервере в сети (см. Таблица 11.2, «Kickstart sources»).
Таблица 11.2. Kickstart sources
Kickstart source Option format
привод CD/DVD ks=cdrom:/каталог/ks.cfg
Hard Drive ks=hd:/устройство/каталог/ks.cfg
Other Device ks=файл:/устройство/каталог/ks.cfg
HTTP Server ks=http://server.mydomain.com/каталог/ks.cfg
FTP Server ks=ftp://server.mydomain.com/каталог/ks.cfg
NFS Server ks=nfs:server.mydomain.com:/каталог/ks.cfg

To obtain a Kickstart file from a script or application on a Web server, specify the URL of the application with the ks= option. If you add the option kssendmac, the request also sends HTTP headers to the Web application. Your application can use these headers to identify the computer. This line sends a request with headers to the application http://server.mydomain.com/kickstart.cgi:
linux ks=http://server.mydomain.com/kickstart.cgi kssendmac

11.5. Enhancing Hardware Support

По умолчанию Fedora пытается автоматически определить и настроить поддержку всех компонентов компьютера. Fedora поддерживает большинство типов оборудования с помощью программных драйверов, которые поставляются с операционной системой. Для поддержки других устройств вы можете предоставить дополнительные драйверы во время процесса установки или позже.

11.5.1. Overriding Automatic Hardware Detection

For some models of device automatic hardware configuration may fail, or cause instability. In these cases, you may need to disable automatic configuration for that type of device, and take additional steps to manually configure the device after the installation process is complete.

Check the Release Notes

Refer to the Release Notes for information on known issues with specific devices.
To override the automatic hardware detection, use one or more of the following options:
Таблица 11.3. Hardware Options
Compatibility Option
Disable all hardware detection noprobe
Disable graphics, keyboard, and mouse detection headless
Disable passing keyboard and mouse information to stage 2 of the installation program nopass
Use basic VESA driver for video xdriver=vesa
Disable shell access on virtual console 2 during installation noshell
Disable advanced configuration and power interface (ACPI) acpi=off
Disable machine check exception (MCE) CPU self-diagnosis. nomce
Disable non-uniform memory access on the AMD64 architecture numa-off
Force kernel to detect a specific amount of memory, where xxx is a value in megabytes mem=xxxm
Enable DMA only for IDE and SATA drives libata.dma=1
Disable BIOS-assisted RAID nodmraid
Disable Firewire device detection nofirewire
Disable parallel port detection noparport
Disable PC Card (PCMCIA) device detection nopcmcia
Disable all probing of network hardware nonet

Additional Screen

The isa option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer.

Важно

Other kernel boot options have no particular meaning for anaconda and do not affect the installation process. However, if you use these options to boot the installation system, anaconda will preserve them in the bootloader configuration.

11.6. Using the Maintenance Boot Modes

11.6.1. Загрузка режима тестирования памяти (ОЗУ)

Сбои в модулях памяти могут привести к непредсказуемому зависанию или падению системы. Иногда сбои памяти могут приводить к появлению ошибок лишь при определенных сочетаниях программного обеспечения. По этой причине следует проверить память компьютера перед установкой Fedora в первый раз, даже если на нем ранее работали другие операционные системы.
Fedora предоставляет специальное приложение для тестирования памяти — Memtest86+. Чтобы загрузить компьютер в режим тестирования памяти, выберите Memory test в меню загрузки. Первый тест сразу же запустится. Memtest86+ по умолчанию выполняет 10 проверок.
В большинстве случаев одной успешной проверки Memtest86+ достаточно. Но в редких случаях ошибки, которые остались незамеченными при первом проходе, могут появиться на последующих проходах. Чтобы выполнить тщательный тест ОЗУ, оставьте Memtest86+ работать на всю ночь или даже на протяжении нескольких дней.
For more information on using Memtest86+, refer to the Memtest86+ FAQ available at http://forum.canardpc.com/showthread.php?t=28864.
Чтобы остановить проверку и перезагрузить компьютер, просто нажмите Esc.

11.6.2. Verifying boot media

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.
Fedora offers you two ways to test installation ISOs:
  • select OK at the prompt to test the media before installation when booting from the Fedora DVD
  • boot Fedora with the rd.live.check option.

11.6.3. Booting Your Computer with the Rescue Mode

Можно загрузить Linux в режиме командной строки как с диска восстановления, так и с установочного диска без необходимости установки Fedora. Это даст возможность использовать утилиты и функции работающей Linux-системы для изменения или восстановления систем, которые уже установлены на вашем компьютере.
The rescue disc starts the rescue mode system by default. To load the rescue system with the installation disc, choose Rescue installed system from the boot menu.
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/.

11.6.4. Upgrading your computer

Существовавший раньше параметр загрузки upgrade удален, так как в процессе установки в любом случае вам будет предложено обновить или переустановить предыдущие версии Fedora.
However, the installation program may not correctly detect a previous version of Fedora if the contents of the /etc/redhat-release file have changed. The boot option upgradeany relaxes the test that the installation program performs and allows you to upgrade a Fedora installation that the installation program has not correctly identified.

Глава 12. Installing Without Media

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

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

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 Глава 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 grub2-mkconfig with root privileges and open the grub.cfg file 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

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 Раздел 11.2, «Enabling Remote Access to the Installation System» for assistance in connecting to the remote system.

Глава 13. Setting Up an Installation 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.
Итак, для выполнения сетевой PXE-установки сетевая карта клиента отправит широковещательный запрос информации DHCP. DHCP-сервер предоставит IP-адрес, а также необходимую информацию о сети, в том числе сведения о сервере имен, IP-адрес или имя узла сервера tftp (который предоставляет необходимые для начала установки файлы), расположение файлов на сервере tftp. Это осуществляется за счет PXELINUX в составе пакета syslinux.
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 Раздел 13.5, «Manually configure a PXE server».
Для выполнения перечисленных в этой секции действий сначала исполните команду su - для перехода в режим root или каждую команду вводите в формате su -c 'команда'.

13.1. Setting Up 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
Измените настройки в файле /etc/cobbler/settings так, чтобы они отражали IP-адрес сервера (как минимум потребуется изменить параметры server и next_server, хотя оба значения могут содержать один и тот же адрес).
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-version/syslinux.doc and /usr/share/doc/syslinux-version/pxelinux.doc.

13.2. Setting Up the Distribution

Чтобы настроить DVD или ISO-образ в качестве источника установки, следуйте приведенным ниже шагам.

Network Locations

Раздел 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 /путь/к/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.
  2. 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:
    /sbin/service rpcbind start /sbin/service nfs start
  3. 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/дистрибутив

13.3. Mirroring a Network Location

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.
Найдите расположение дистрибутива в сети. Он может быть расположен в локальной сети или на удаленном сайте (FTP, HTTP, rsync).

13.4. Importing the Distribution

Чтобы обеспечить несколько доступных способов установки, можно их импортировать, присвоив каждому способу имя. Это имя будет показано в меню загрузки клиента, поэтому рекомендуется сделать его понятным.
  1. To import the DVD disc or ISO distribution into cobbler, run this command:
    cobbler import --path=/mnt/dvd --name=дистрибутив
    For distro_name, substitute a meaningful name for the distribution.
    Следующая команда позволяет импортировать локальный или удаленный дистрибутив. Замените URI ссылкой из предыдущей секции (см. Раздел 13.3, «Mirroring a Network Location») и укажите описательное имя дистрибутива:
    cobbler import --path=URI --name=дистрибутив

    Importing a Source

    При импортировании таким образом дистрибутива cobbler будет копировать файлы в локальную систему, что может занять некоторое время.
    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=дистрибутив --available-as=URI
    cobbler import --path=URI --name=дистрибутив --available-as=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.
  2. 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

    В зависимости от конфигурации сервера может понадобиться выполнить команду system-config-securitylevel для разрешения доступа к следующим сетевым службам:
    • 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

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.
  2. Configure the files on the tftp server necessary for PXE booting.
  3. Configure which hosts are allowed to boot from the PXE configuration.
  4. Start the tftp service.
  5. Configure DHCP.
  6. Boot the client, and start the installation.

13.5.1. Setting up the Network Server

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 Раздел 5.1, «Preparing for a Network Installation» for detailed instructions.

13.5.2. PXE Boot Configuration

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

  1. If tftp-server is not yet installed, run yum install tftp-server.
  2. In the tftp-server config file at /etc/xinet.d/tftp, change the disabled parameter from yes to no.
  3. 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 Deployment 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;
              }
      }
    
  4. You now need the pxelinux.0 file from the SYSLINUX package installed with Fedora. Create a pxelinux directory within tftpboot and copy pxelinux.0 into it:
    mkdir /var/lib/tftpboot/pxelinux
    cp /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/pxelinux
  5. Create a pxelinux.cfg directory within pxelinux:
    mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
  6. 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 inst.repo=http://dl.fedoraproject.org/pub/fedora/linux/development/17/x86_64/os/
    label vesa
      menu label Install system with ^basic video driver
      kernel vmlinuz
      append initrd=initrd.img xdriver=vesa nomodeset
    label rescue
      menu label ^Rescue installed system
      kernel vmlinuz
      append initrd=initrd.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 Глава 8, Configuring Installation Source
  7. Copy the splash image into your tftp root directory:
    cp /boot/grub/splash.xpm.gz /var/lib/tftpboot/pxelinux/splash.xpm.gz
  8. Copy the boot images into your tftp root directory:
     cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/rawhide-x86_64/
  9. Reboot the system, and select the network device as your boot device when prompted.

13.5.2.2. Configuring for EFI

  1. If tftp-server is not yet installed, run yum install tftp-server.
  2. In the tftp-server config file at /etc/xinet.d/tftp, change the disabled parameter from yes to no.
  3. Create a directory path within tftpboot for the EFI boot images, and then copy them from your boot directory:
    mkdir /var/lib/tftpboot/pxelinux
    mkdir /var/lib/tftpboot/pxelinux/bootx64.efi
    cp /boot/efi/EFI/redhat/grub.efi /var/lib/tftpboot/pxelinux/bootx64.efi
  4. 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 Deployment 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;
              }
      }
    
  5. Create a pxelinux.cfg directory within pxelinux:
    mkdir /var/lib/tftpboot/pxelinux/pxelinux.cfg
  6. 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
    splashimage=(nd)/splash.xpm.gz
    hiddenmenu
    title RHEL
            root (nd)
            kernel /rawhide-x86_64/vmlinuz
            initrd /rawhide-x86_64/initrd.img
    
    For instructions on how to specify the installation source, refer to Глава 8, Configuring Installation Source
  7. Copy the splash image into your tftp root directory:
    cp /boot/grub/splash.xpm.gz /var/lib/tftpboot/pxelinux/splash.xpm.gz
  8. Copy the boot images into your tftp root directory:
     cp /path/to/x86_64/os/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/rawhide-x86_64/
  9. Reboot the system, and select the network device as your boot device when prompted.

13.5.3. Starting the tftp Server

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

Optionally, modify /tftpboot/linux-install/msgs/boot.msg to use a custom boot message.

13.5.5. Performing the PXE Installation

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 gPXE bootloader. The Fedora Project does not distribute gPXE — refer to the Etherboot Project website at http://etherboot.org/wiki/start for more information.
Глава 9, Installing using anaconda описывает дальнейшие действия после запуска программы установки.

Глава 14. Installing Through VNC

The Fedora installer (anaconda) offers you two interactive modes of operation. The original mode is a text-based interface. The newer mode uses GTK+ and runs in the X Window environment. This chapter explains how you can use the graphical installation mode in environments where the system lacks a proper display and input devices typically associated with a workstation. This scenario is typical of systems in datacenters, which are often installed in a rack environment and do not have a display, keyboard, or mouse. Additionally, a lot of these systems even lack the ability to connect a graphical display. Given that enterprise hardware rarely needs that ability at the physical system, this hardware configuration is acceptable.
Even in these environments, however, the graphical installer remains the recommended method of installation. The text mode environment lacks a lot of capabilities found in the graphical mode. Many users still feel that the text mode interface provides them with additional power or configuration ability not found in the graphical version. The opposite is true. Much less development effort is put in to the text-mode environment and specific things (for example, LVM configuration, partition layout, package selection, and bootloader configuration) are deliberately left out of the text mode environment. The reasons for this are:
  • Less screen real estate for creating user interfaces similar to those found in the graphical mode.
  • Difficult internationalization support.
  • Desire to maintain a single interactive installation code path.
Anaconda therefore includes a Virtual Network Computing (VNC) mode that allows the graphical mode of the installer to run locally, but display on a system connected to the network. Installing in VNC mode provides you with the full range of installation options, even in situations where the system lacks a display or input devices.

14.1. VNC Viewer

Performing a VNC installation requires a VNC viewer running on your workstation or other terminal computer. Locations where you might want a VNC viewer installed:
  • Your workstation
  • Laptop on a datacenter crash cart
VNC is open source software licensed under the GNU General Public License.
  • VNC clients are available in the repositories of most Linux distributions. Use your package manager to search for a client for your chosen distribution. For example, on Fedora, install the tigervnc package:
    # yum install tigervnc
  • TightVNC is available for Windows at http://www.tightvnc.com/
  • MacOS X includes built-in VNC support as of version 10.5. In the Finder, click the Go menu and choose Connect to Server. In the server address field, you can type vnc://SERVER:DISPLAY, where SERVER is the IP address or DNS host name of the VNC server you wish to connect to and DISPLAY is the VNC display number (usually 1), and click Connect.
Once you have verified you have a VNC viewer available, it's time to start the installation.

14.2. VNC Modes in Anaconda

Anaconda offers two modes for VNC installation. The mode you select will depend on the network configuration in your environment.

14.2.1. Direct Mode

Direct mode VNC in anaconda is when the client initiates a connection to the VNC server running in anaconda. Anaconda will tell you when to initiate this connection in the VNC viewer. Direct mode can be activated by either of the following commands:
  • Specify vnc as a boot argument.
  • Specify the vnc command in the kickstart file used for installation.
When you activate VNC mode, anaconda will complete the first stage of the installer and then start VNC to run the graphical installer. The installer will display a message on the console in the following format:
Запускается Anaconda ВЕРСИЯ, программа установки ОС, подождите, пожалуйста.
Anaconda will also tell you the IP address and display number to use in your VNC viewer. At this point, you need to start the VNC viewer and connect to the target system to continue the installation. The VNC viewer will present anaconda to you in graphical mode.
There are some disadvantages to direct mode, including:
  • Requires visual access to the system console to see the IP address and port to connect the VNC viewer to.
  • Requires interactive access to the system console to complete the first stage of the installer.
If either of these disadvantages would prevent you from using direct mode VNC in anaconda, then connect mode is probably more suited to your environment.

14.2.2. Connect Mode

Certain firewall configurations or instances where the target system is configured to obtain a dynamic IP address may cause trouble with the direct VNC mode in anaconda. In addition, if you lack a console on the target system to see the message that tells you the IP address to connect to, then you will not be able to continue the installation.
Режим подключения изменяет способ запуска VNC. То есть в этом случае не Anaconda не ожидает вашего подключения после запуска, а автоматически подключается сама. Таким образом, не требуется знать IP-адрес целевой системы.
To activate the VNC connect mode, pass the vnc vncconnect boot parameter:
boot: linux vnc vncconnect=HOST[:port]
Replace HOST with your VNC viewer's IP address or DNS host name. Specifying the port is optional. Before starting the installation process on the target system, start up your VNC viewer and have it wait for an incoming connection.
Start the installation and when your VNC viewer displays the graphical installer, you are ready to go.

14.3. Installation Using VNC

Now that you have installed a VNC viewer application and selected a VNC mode for use in anaconda, you are ready to begin the installation.

14.3.1. Installation Example

The easiest way to perform an installation using VNC is to connect another computer directly to the network port on the target system. The laptop on a datacenter crash cart usually fills this role. If you are performing your installation this way, make sure you follow these steps:
  1. Connect the laptop or other workstation to the target system using a crossover cable. If you are using regular patch cables, make sure you connect the two systems using a small hub or switch. Most recent Ethernet interfaces will automatically detect if they need to be crossover or not, so it may be possible to connect the two systems directly using a regular patch cable.
  2. Configure the VNC viewer system to use a RFC 1918 address with no gateway. This private network connection will only be used for the purpose of installation. Configure the VNC viewer system to be 192.168.100.1/24. If that address is in use, just pick something else in the RFC 1918 address space that is available to you.
  3. Start the installation on the target system.
    1. Загрузка установочного DVD
      При загрузке с установочного DVD не забудьте добавить параметр загрузки vnc. Для передачи параметров процессу загрузки необходимо, чтобы к целевой системе была подключена консоль. В строке приглашения введите:
      boot: linux vnc
    2. Boot over the network.
      If the target system is configured with a static IP address, add the vnc command to the kickstart file. If the target system is using DHCP, add vnc vncconnect=HOST[:port] to the boot arguments for the target system. HOST is the IP address or DNS host name of the VNC viewer system. Specifying the port is optional. Enter the following at the prompt:
      boot: linux vnc vncconnect=HOST[:port]
  4. When prompted for the network configuration on the target system, assign it an available RFC 1918 address in the same network you used for the VNC viewer system. For example, 192.168.100.2/24.

    Примечание

    This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer.
  5. Once the installer indicates it is starting anaconda, you will be instructed to connect to the system using the VNC viewer. Connect to the viewer and follow the graphical installation mode instructions found in the product documentation.

14.3.2. Kickstart Considerations

If your target system will be booting over the network, VNC is still available. Just add the vnc command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file.
If you are using DHCP for the target system, the reverse vnc vncconnect method may work better for you. Rather than adding the vnc boot parameter to the kickstart file, add the vnc vncconnect=HOST[:port] parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. Specifying the port is optional. See the next section for more details on using the vncconnect mode.

14.3.3. Firewall Considerations

If you are performing the installation where the VNC viewer system is a workstation on a different subnet from the target system, you may run in to network routing problems. VNC works fine so long as your viewer system has a route to the target system and ports 5900 and 5901 are open. If your environment has a firewall, make sure ports 5900 and 5901 are open between your workstation and the target system.
In addition to passing the vnc boot parameter, you may also want to pass the vncpassword parameter in these scenarios. While the password is sent in plain text over the network, it does provide an extra step before a viewer can connect to a system. Once the viewer connects to the target system over VNC, no other connections are permitted. These limitations are usually sufficient for installation purposes.

Important

Be sure to use a temporary password for the vncpassword option. It should not be a password you use on any systems, especially a real root password.
If you continue to have trouble, consider using the vnc vncconnect parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass vnc vncconnect=HOST[:port] at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address). Specifying the port is optional.

14.4. References

Глава 15. Kickstart Installations

15.1. What are Kickstart Installations?

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?

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.
  2. Create a boot media with the kickstart file or make the kickstart file available on the network.
  3. Make the installation tree available.
  4. Start the kickstart installation.
This chapter explains these steps in detail.

15.3. Creating the Kickstart 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:
  • 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

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 Глава 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-2.x.x/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 — To set up the SHA-256 hashing algorithm, run the command authconfig --passalgo=sha256 --kickstart.
    To set up the SHA-512 hashing algorithm, run authconfig --passalgo=sha512 --kickstart.
    Remove the --enablemd5 option if it is present.
autopart (optional)
Automatically create partitions — 1 GB or more root (/) partition, a swap partition, and an appropriate boot partition for the architecture. One or more of the default partition sizes can be redefined with the part directive.
  • --encrypted — Should all devices with support be encrypted by default? This is equivalent to checking the Encrypt checkbox on the initial partitioning screen.
  • --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.
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.

Важно

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
  • --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).
  • --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.
  • --md5pass= — If using GRUB, similar to --password= except the password should already be encrypted.
  • --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.
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.
  • --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 <moduleName> --opts=<options>
  • <moduleName> — 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 diskettes can be used during kickstart installations. You must copy the driver diskettes'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 <partition> --source=<url> --biospart=<biospart> [--type=<fstype>]
Alternatively, a network location can be specified for the driver diskette:
driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/img
  • <partition> — Partition containing the driver disk.
  • <url> — URL for the driver disk. NFS locations can be given in the form nfs:host:/path/to/img.
  • <biospart> — 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=] <device> [--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.
  • <incoming> — 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.
firstboot (optional)
Determine whether the firstboot starts the first time the system is booted. If enabled, the firstboot package must be installed. If not specified, this option is disabled by default.
  • --enable or --enabled — The Setup Agent is started the first time the system boots.
  • --disable or --disabled — The Setup Agent is not started the first time the system boots.
  • --reconfig — Enable the Setup Agent to start at boot time in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
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
  • 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://<server>/<dir>
    or:
    url --url ftp://<username>:<password>@<server>/<dir>
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)
Sets the default keyboard type for the system. The available keyboard types are:
  • 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.
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.
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 <mntpoint> --vgname=<name> --size=<size> --name=<name> <options>
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.
  • --label= — assign a label to an individual volume.
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 Раздел 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.

Примечание

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
    2. the device activated automatically to fetch the kickstart file
    3. 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 or 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.
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.

Предупреждение

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.

Важно

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 Раздел 15.4.1, «Advanced Partitioning Example».
  • <mntpointmultipath --name= --device= --rule=> — The <mntpoint> is where the partition is mounted and must be of one of the following forms:
    • /<path>
      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.
      If you wish to set the swap partition more precisely, refer to Раздел 9.17.5, «Recommended Partitioning Scheme».
    • raid.<id>
      The partition is used for software RAID (refer to raid).
    • pv.<id>
      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 Раздел 9.17.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).
  • --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 <mntpoint> --level=<level> --device=<mddevice> <partitions*>
  • <mntpoint> — 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 <partitions*> (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 Раздел 15.4.1, «Advanced Partitioning Example».
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.

Примечание

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=<repoid> [--baseurl=<url>| --mirrorlist=<url>]
  • --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.
rootpw (required)
Sets the system's root password to the <password> argument.
rootpw [--iscrypted] <password>
  • --iscrypted — If this is present, the password argument is assumed to already be encrypted.
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 Deployment 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=<name> <password> [--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 Раздел 11.2.3, «Enabling Remote Access with ssh» 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.

Важно

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 <timezone> which may be any of the time zones listed by timeconfig.
timezone [--utc] <timezone>
  • --utc — If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
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=<username> [--groups=<list>] [--homedir=<homedir>] [--password=<password>] [--iscrypted] [--shell=<shell>] [--uid=<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/<username>.
  • --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=<hostname>] [--port=<port>] [--password=<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 <name> <partition> <options>
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 Раздел 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

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

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

15.6. Pre-installation Script

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 Раздел 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

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

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 Раздел 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

Пример 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.

15.8. Making the Kickstart File Available

A kickstart file must be placed in one of the following locations:
  • On removable media, such as a floppy disk, optical disk, or USB flash drive
  • On a hard drive
  • On a network
Normally a kickstart file is copied to the removable media or hard drive, or made available on the network. The network-based approach is most commonly used, as most kickstart installations tend to be performed on networked computers.
Let us take a more in-depth look at where the kickstart file may be placed.

15.8.1. Creating Kickstart Boot Media

To perform a kickstart installation using removable media, the kickstart file must be named ks.cfg and must be located in the top-level directory of the disc.
Diskette-based booting is no longer supported in Fedora. Installations must use CD-ROM or flash memory products for booting. However, the kickstart file may still reside on a diskette's top-level directory, and must be named ks.cfg. Separate boot media will be required.
Refer to Раздел 3.3, «Making Minimal Boot Media» for instructions on creating boot media.
To perform a pen-based flash memory kickstart installation, the kickstart file must be named ks.cfg and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the ks.cfg file.
Refer to Раздел 3.3, «Making Minimal Boot Media» for instructions on creating live USB media using the Fedora-version-architecture-format.iso image file that you can download from the Fedora Project site at http://download.fedoraproject.org/.

Note

Creation of USB flashdrives for booting is possible, but is heavily dependent on system hardware BIOS settings. Refer to your hardware manufacturer to see if your system supports booting to alternate devices.

15.8.2. Making the Kickstart File Available on the Network

Network installations using kickstart are quite common, because system administrators can quickly and easily automate the installation on many networked computers. In general, the approach most commonly used is for the administrator to have both a BOOTP/DHCP server and an NFS server on the local network. The BOOTP/DHCP server is used to give the client system its networking information, while the actual files used during the installation are served by the NFS server. Often, these two servers run on the same physical machine, but they are not required to.
Include the ks kernel boot option in the append line of a target in your pxelinux.cfg/default file to specify the location of a kickstart file on your network. The syntax of the ks option in a pxelinux.cfg/default file is identical to its syntax when used at the boot prompt. Refer to Раздел 15.10, «Starting a Kickstart Installation» for a description of the syntax and refer to Пример 15.2, «Using the ks option in the pxelinux.cfg/default file» for an example of an append line.
If the dhcpd.conf file on the DHCP server is configured to point to /tftpboot/pxelinux.0 on the BOOTP server (whether on the same physical machine or not), systems configured to boot over the network can load the kickstart file and commence installation.
Пример 15.2. Using the ks option in the pxelinux.cfg/default file
For example, if foo.ks is a kickstart file available on an NFS share at 192.168.0.200:/export/kickstart/, part of your pxelinux.cfg/default file might include:
label 1
  kernel Fedora17/vmlinuz
  append initrd=Fedora17/initrd.img ramdisk_size=10000 ks=nfs:192.168.0.200:/export/kickstart/foo.ks

15.9. Making the Installation Tree Available

The kickstart installation must access an installation tree. An installation tree is a copy of the binary Fedora DVD with the same directory structure.
If you are performing a DVD-based installation, insert the Fedora installation DVD into the computer before starting the kickstart installation.
If you are performing a hard drive installation, make sure the ISO images of the binary Fedora DVD are on a hard drive in the computer.
If you are performing a network-based (NFS, FTP, or HTTP) installation, you must make the installation tree or ISO image available over the network. Refer to Раздел 5.1, «Preparing for a Network Installation» for details.

15.10. Starting a Kickstart Installation

Important — Kickstart installations and firstboot

Firstboot does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the user option in the Kickstart file before installing additional systems from it (refer to Раздел 15.4, «Kickstart Options» for details) or log into the installed system with a virtual console as root and add users with the adduser command.
To begin a kickstart installation, you must boot the system from boot media you have made or the Fedora DVD, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the ks command line argument is passed to the kernel.
DVD and local storage
The linux ks= command also works if the ks.cfg file is located on a vfat or ext2 file system on local storage and you boot from the Fedora DVD.
With Driver Disk
If you need to use a driver disk with kickstart, specify the dd option as well. For example, if installation requires a kickstart file on a local hard drive and also requires a driver disk, boot the system with:
linux ks=hd:partition:/path/ks.cfg dd
Boot CD-ROM
If the kickstart file is on a boot CD-ROM as described in Раздел 15.8.1, «Creating Kickstart Boot Media», insert the CD-ROM into the system, boot the system, and enter the following command at the boot: prompt (where ks.cfg is the name of the kickstart file):
linux ks=cdrom:/ks.cfg
Other options to start a kickstart installation are as follows:
autostep
Make kickstart non-interactive.
debug
Start up pdb immediately.
dd
Use a driver disk.
dhcpclass=<class>
Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier".
dns=<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=<gw>
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>
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=<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:<server>:/<path>
The installation program looks for the kickstart file on the NFS server <server>, as file <path>. 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://<server>/<path>
The installation program looks for the kickstart file on the HTTP server <server>, as file <path>. 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:<device>:/<file>
The installation program mounts the file system on <device> (which must be vfat or ext2), and looks for the kickstart configuration file as <file> in that file system (for example, ks=hd:sda3:/mydir/ks.cfg).
ks=bd:<biosdev>:/<path>
The installation program mounts the file system on the specified partition on the specified BIOS device <biosdev>, and looks for the kickstart configuration file specified in <path> (for example, ks=bd:80p3:/mydir/ks.cfg). Note this does not work for BIOS RAID sets.
ks=file:/<file>
The installation program tries to read the file <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:/<path>
The installation program looks for the kickstart file on CD-ROM, as file <path>.
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=<device>
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:<server>:/<path> 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=<lang>
Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command.
loglevel=<level>
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=<nm>
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://<path>
Use <path> for an FTP installation.
repo=hd:<dev>:<path>
Use <path> on <dev> for a hard drive installation.
repo=http://<path>
Use <path> for an HTTP installation.
repo=nfs:<path>
Use <path> for an NFS installation.
rescue
Run rescue environment.
resolution=<mode>
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=<host>[:<port>]
Once installation is up and running, send log messages to the syslog process on <host>, and optionally, on port <port>. Requires the remote syslog process to accept connections (the -r option).
text
Force text mode install.

Важно

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://<path>
Image containing updates over FTP.
updates=http://<path>
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=<host>[:<port>]
Connect to the vnc client named <host>, and optionally use port <port>.
Requires 'vnc' option to be specified as well.
vncpassword=<password>
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.

Глава 16. Kickstart Configurator

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 17. 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 ApplicationsSystem ToolsKickstart on the GNOME desktop or Kickoff Application Launcher+ApplicationsSystemKickstart on the KDE desktop.
As you are creating a kickstart file, you can click FilePreview at any time to review your current selections.
To start with an existing kickstart file, select FileOpen and select the existing file.

16.1. Basic Configuration

Basic Configuration
Basic Configuration
Рисунок 16.1. Basic Configuration

Choose the language to use during the installation and as the default language to be used after installation from the Default Language menu.
Select the system keyboard type from the Keyboard menu.
From the Time Zone menu, choose the time zone to use for the system. To configure the system to use UTC, select Use UTC clock.
Enter the desired root password for the system in the Root Password text entry box. Type the same password in the Confirm Password text box. The second field is to make sure you do not mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select Encrypt root password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it. Because a kickstart file is a plain text file that can be easily read, it is recommended that an encrypted password be used.
Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation.
Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation.
Choosing Reboot system after installation reboots your system automatically after the installation is finished.
Kickstart installations are performed in graphical mode by default. To override this default and use text mode instead, select the Perform installation in text mode option.
You can perform a kickstart installation in interactive mode. This means that the installation program uses all the options pre-configured in the kickstart file, but it allows you to preview the options in each screen before continuing to the next screen. To continue to the next screen, click the Next button after you have approved the settings or change them before continuing the installation. To select this type of installation, select the Perform installation in interactive mode option.

16.2. Installation Method

Installation Method
Kickstart Installation Method
Рисунок 16.2. Installation Method

The Installation Method screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the Partition Information and Package Selection options are disabled. They are not supported for kickstart upgrades.
Choose the type of kickstart installation or upgrade from the following options:
  • DVD — Choose this option to install or upgrade from the Fedora DVD.
  • NFS — Choose this option to install or upgrade from an NFS shared directory. In the text field for the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the variant directory of the installation tree. For example, if the NFS server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/ for the NFS directory.
  • FTP — Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the variant directory. For example, if the FTP server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the FTP directory. If the FTP server requires a username and password, specify them as well.
  • HTTP — Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the variant directory. For example, if the HTTP server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/redhat/i386/Server/ for the HTTP directory.
  • Hard Drive — Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an md5sum program as well as the linux rd.live.check boot option as discussed in Раздел 11.6.2, «Verifying boot media». Enter the hard drive partition that contains the ISO images (for example, /dev/hda1) in the Hard Drive Partition text box. Enter the directory that contains the ISO images in the Hard Drive Directory text box.

16.3. Boot Loader Options

Boot Loader Options
Boot Loader Options
Рисунок 16.3. Boot Loader Options

Please note that this screen will be disabled if you have specified a target architecture other than x86 / x86_64.
GRUB is the default boot loader for Fedora on x86 / x86_64 architectures. If you do not want to install a boot loader, select Do not install a boot loader. If you choose not to install a boot loader, make sure you create a boot diskette or have another way to boot your system, such as a third-party boot loader.
You must choose where to install the boot loader (the Master Boot Record or the first sector of the /boot partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
To pass any special parameters to the kernel to be used when the system boots, enter them in the Kernel parameters text field. For example, if you have an IDE CD-ROM Writer, you can tell the kernel to use the SCSI emulation driver that must be loaded before using cdrecord by configuring hdd=ide-scsi as a kernel parameter (where hdd is the CD-ROM device).
You can password protect the GRUB boot loader by configuring a GRUB password. Select Use GRUB password, and enter a password in the Password field. Type the same password in the Confirm Password text field. To save the password as an encrypted password in the file, select Encrypt GRUB password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. If the password you typed was already encrypted, unselect the encryption option.
Whenever you are required to enter this password, you will also be asked for a username, which is root.
If Upgrade an existing installation is selected on the Installation Method page, select Upgrade existing boot loader to upgrade the existing boot loader configuration, while preserving the old entries.

16.4. Partition Information

Partition Information
Kickstart Partition Information
Рисунок 16.4. Partition Information

Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions.
To initialize the disk label to the default for the architecture of the system (for example, msdos for x86), select Initialize the disk label if you are installing on a brand new hard drive.

Примечание

Although anaconda and kickstart support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the Kickstart Configurator.

16.4.1. Creating Partitions

To create a partition, click the Add button. The Partition Options window shown in Рисунок 16.5, «Creating Partitions» appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following:
  • In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
  • Force the partition to be created as a primary partition.
  • Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk (/dev/hda), specify hda as the drive. Do not include /dev in the drive name.
  • Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk (/dev/hda1), specify hda1 as the partition. Do not include /dev in the partition name.
  • Format the partition as the chosen file system type.
Creating Partitions
Creating Partitions for Kickstart
Рисунок 16.5. Creating Partitions

To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Рисунок 16.5, «Creating Partitions», except it reflects the values for the selected partition. Modify the partition options and click OK.
To delete an existing partition, select the partition from the list and click the Delete button.

16.4.1.1. Creating Software RAID Partitions

To create a software RAID partition, use the following steps:
  1. Click the RAID button.
  2. Select Create a software RAID partition.
  3. Configure the partitions as previously described, except select Software RAID as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use.
Creating a Software RAID Partition
Software RAID Partition
Рисунок 16.6. Creating a Software RAID Partition

Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions.
After creating all the partitions needed to form a RAID device, follow these steps:
  1. Click the RAID button.
  2. Select Create a RAID device.
  3. Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device.
    Creating a Software RAID Device
    Software RAID Device
    Рисунок 16.7. Creating a Software RAID Device

  4. Click OK to add the device to the list.

16.5. Network Configuration

Network Configuration
Network Configuration for Kickstart
Рисунок 16.8. Network Configuration

If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the Network Configuration page.
Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the Network Administration Tool (system-config-network). Refer to the Fedora Deployment Guide for details.
For each Ethernet card on the system, click Add Network Device and select the network device and network type for the device. Select eth0 to configure the first Ethernet card, eth1 for the second Ethernet card, and so on.

16.6. Authentication

Authentication
Authentication for Kickstart
Рисунок 16.9. Authentication

In the Authentication section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default.
The Authentication Configuration options allow you to configure the following methods of authentication:
  • NIS
  • LDAP
  • Kerberos 5
  • Hesiod
  • SMB
  • Name Switch Cache
These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to Enable, and enter the appropriate information for the authentication method. Refer to the Fedora Deployment Guide for more information about the options.

16.7. Firewall Configuration

The Firewall Configuration window is similar to the screen in the installation program and the Security Level Configuration Tool.
Firewall Configuration
Firewall Configuration for Kickstart
Рисунок 16.10. Firewall Configuration

If Disable firewall is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied.
Selecting Enable firewall configures the system to 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 required, you can choose to allow specific services through the firewall.
Only devices configured in the Network Configuration section are listed as available Trusted devices. Connections from any devices selected in the list are accepted by the system. For example, if eth1 only receives connections from internal system, you might want to allow connections from it.
If a service is selected in the Trusted services list, connections for the service are accepted and processed by the system.
In the Other ports text field, list any additional ports that should be opened for remote access. Use the following format: port:protocol. For example, to allow IMAP access through the firewall, specify imap:tcp. Numeric ports can also be specified explicitly; to allow UDP packets on port 1234 through the firewall, enter 1234:udp. To specify multiple ports, separate them with commas.

16.7.1. SELinux Configuration

Kickstart can set SELinux to enforcing, permissive or disabled mode. Finer grained configuration is not possible at this time.

16.8. Display Configuration

If you are installing the X Window System, you can configure it during the kickstart installation by checking the Configure the X Window System option on the Display Configuration window as shown in Рисунок 16.11, «X Configuration». If this option is not chosen, the X configuration options are disabled and the skipx option is written to the kickstart file.
X Configuration
X Configuration for Kickstart
Рисунок 16.11. X Configuration

Select whether to start the Setup Agent the first time the installed system boots. The Setup Agent is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.

16.9. Package Selection

Package Selection
Package Selection for Kickstart
Рисунок 16.12. Package Selection

The Package Selection window allows you to choose which package groups to install.
Package resolution is carried out automatically.
Currently, Kickstart Configurator does not allow you to select individual packages. To install individual packages, modify the %packages section of the kickstart file after you save it. Refer to Раздел 15.5, «Package Selection» for details.

16.10. Pre-Installation Script

Pre-Installation Script
Pre-Installation Script for Kickstart
Рисунок 16.13. Pre-Installation Script

You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area.
To specify a scripting language to use to execute the script, select the Use an interpreter option and enter the interpreter in the text box beside it. For example, /usr/bin/python2.6 can be specified for a Python script. This option corresponds to using %pre --interpreter /usr/bin/python2.6 in your kickstart file.
Only the most commonly used commands are available in the pre-installation environment:
arping, awk, basename, bash, bunzip2, bzcat, cat, chattr, chgrp, chmod, chown, chroot, chvt, clear, cp, cpio, cut, date, dd, df, dirname, dmesg, du, e2fsck, e2label, echo, egrep, eject, env, expr, false, fdisk, fgrep, find, fsck, fsck.ext2, fsck.ext3, ftp, grep, gunzip, gzip, hdparm, head, hostname, hwclock, ifconfig, insmod, ip, ipcalc, kill, killall, less, ln, load_policy, login, losetup, ls, lsattr, lsmod, lvm, md5sum, mkdir, mke2fs, mkfs.ext2, mkfs.ext3, mknod, mkswap, mktemp, modprobe, more, mount, mt, mv, nslookup, openvt, pidof, ping, ps, pwd, readlink, rm, rmdir, rmmod, route, rpm, sed, sh, sha1sum, sleep, sort, swapoff, swapon, sync, tail, tar, tee, top, touch, true, tune2fs, umount, uniq, vconfig, vi, wc, wget, xargs, zcat.

Важно

Do not include the %pre command. It is added for you.

Примечание

The pre-installation script is run after the source media is mounted and stage 2 of the bootloader has been loaded. For this reason it is not possible to change the source media in the pre-installation script.

16.11. Post-Installation Script

Post-Installation Script
Post-Installation Script for Kickstart
Рисунок 16.14. Post-Installation Script

You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area.

Важно

Do not include the %post command. It is added for you.
For example, to change the message of the day for the newly installed system, add the following command to the %post section:
echo "Hackers will be punished" > /etc/motd

Note

More examples can be found in Раздел 15.7.1, «Example».

16.11.1. Chroot Environment

To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the Post-Installation window. This is equivalent to using the --nochroot option in the %post section.
To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/.
For example, if you select Run outside of the chroot environment, the previous example must be changed to the following:
echo "Hackers will be punished" > /mnt/sysimage/etc/motd

16.11.2. Use an Interpreter

To specify a scripting language to use to execute the script, select the Use an interpreter option and enter the interpreter in the text box beside it. For example, /usr/bin/python2.2 can be specified for a Python script. This option corresponds to using %post --interpreter /usr/bin/python2.2 in your kickstart file.

16.12. Saving the File

To review the contents of the kickstart file after you have finished choosing your kickstart options, select File => Preview from the pull-down menu.
Preview
Preview
Рисунок 16.15. Preview

To save the kickstart file, click the Save to File button in the preview window. To save the file without previewing it, select File => Save File or press Ctrl+S . A dialog box appears. Select where to save the file.
After saving the file, refer to Раздел 15.10, «Starting a Kickstart Installation» for information on how to start the kickstart installation.

Часть III. After installation

This part of the Fedora Installation Guide covers finalizing the installation, as well as some installation-related tasks that you might perform at some time in the future. These include:
  • using a Fedora installation disk to rescue a damaged system.
  • upgrading to a new version of Fedora.
  • removing Fedora from your computer.

Содержание

17. Firstboot
17.1. License Agreement
17.2. Create User
17.2.1. Authentication Configuration
17.3. Date and Time
17.4. Hardware Profile
18. Your Next Steps
18.1. Updating Your System
18.2. Finishing an Upgrade
18.3. Switching to a Graphical Login
18.3.1. Активация доступа к репозиториям из командной строки
18.4. Подписка на объявления и новости Fedora
18.5. Документация и поддержка
18.6. Вступление в сообщество Fedora
19. Basic System Recovery
19.1. Rescue Mode
19.1.1. Common Problems
19.1.2. Booting into Rescue Mode
19.1.3. Booting into Single-User Mode
19.1.4. Booting into Emergency Mode
19.2. Using rescue mode to fix or work around driver problems
19.2.1. Using RPM to add, remove, or replace a driver
19.2.2. Blacklisting a driver
20. Upgrading Your Current System
20.1. Determining Whether to Upgrade or Re-Install
20.2. Upgrading Your System
21. Удаление Fedora
21.1. Fedora является единственной операционной системой
21.2. Двойная загрузка: Fedora и другая операционная система
21.2.1. Настроена двойная загрузка (Fedora и Microsoft Windows)
21.2.2. Двойная загрузка: Fedora и Mac OS X
21.2.3. Двойная загрузка: Fedora и другой дистрибутив Linux
21.3. Замена Fedora ранними версиями Microsoft Windows и MS-DOS

Глава 17. Firstboot

Important — Firstboot not available after text-mode installation

Firstboot is only available on systems after a graphical installation or after a kickstart installation where a desktop and the X window system were installed and graphical login was enabled. If you performed a text-mode installation or a kickstart installation that did not include a desktop and the X window system, the Firstboot configuration tool does not appear.
Firstboot launches the first time that you start a new Fedora system. Use Firstboot to configure the system for use before you log in.
Firstboot welcome screen
Firstboot welcome screen
Рисунок 17.1. Firstboot welcome screen

Select Forward to start Firstboot.

17.1. License Agreement

This screen displays the overall licensing terms for Fedora. Each software package in Fedora is covered by its own license. All licensing guidelines for Fedora are located at http://fedoraproject.org/wiki/Legal/Licenses.
Firstboot license screen
Firstboot license screen
Рисунок 17.2. Firstboot license screen

If you agree to the terms of the licence, select Yes, I agree to the License Agreement and click Forward.

17.2. Create User

Create a user account for yourself with this screen. Always use this account to log in to your Fedora system, rather than using the root account.
Firstboot create user screen
Firstboot create user screen
Рисунок 17.3. Firstboot create user screen

Enter a user name and your full name, and then enter your chosen password. Type your password once more in the Confirm Password box to ensure that it is correct.
Check the Add to Administrators group box if you would like administrative privileges. This will place you in the wheel group, which gives you access to all administrative functions, including installing and updating software, creating and altering configuration files, and administering other users.
To configure Fedora to use network services for authentication of user information, click Use Network Login. Refer to Раздел 17.2.1, «Authentication Configuration» for further details.
To create additional users or customise your first user account, click Advanced to open the User Manager.
User Manager
Firstboot user manager screen
Рисунок 17.4. User Manager

In User Manager you can edit various properties, such as a private group for the user, the preferred login shell, and user and group IDs.

Important — Create at least one user account

If you do not create at least one user account in this step, you will not be able to log in to the Fedora graphical environment. If you skipped this step during installation, refer to Раздел 10.4.3, «Booting into a Graphical Environment».

Note — Creating Extra User Accounts

To add additional user accounts to your system after the installation is complete, choose SystemAdministrationUsers & Groups.

17.2.1. Authentication Configuration

If you clicked Use Network Login on the Create User screen, you must now specify how users are to be authenticated on the system. Use the drop-down menu to select from the following types of user database:
  • Local accounts only (for use when the user database on the network is not accessible)
  • LDAP (Lightweight Directory Access Protocol)
  • NIS (Network Information Service)
  • Winbind (for use with Microsoft Active Directory)
Firstboot Authentication Configuration screen
Firstboot Authentication Configuration screen
Рисунок 17.5. Firstboot Authentication Configuration screen

When you select the type of user database appropriate for your network, you must provide additional details relevant to that database type. For example, if you select LDAP, you must specify the base distinguished name for LDAP searches, and the address of the LDAP server. You must also select an Authentication Method relevant to the type of user database that you chose, for example, a Kerberos password, LDAP password, or NIS password.
The Advanced Options tab lets you enable other authentication mechanisms, including fingerprint readers, smart cards, and local access control in /etc/security/access.conf.
Firstboot authentication Advanced Options screen
Firstboot authentication Advanced Options screen
Рисунок 17.6. Firstboot authentication Advanced Options screen

The Password Options tab lets you set format requirements for user passwords, including minimum length and required character classes such as lower case, upper case, and numbers.
Firstboot authentication Password Options screen
Firstboot authentication Password Options screen
Рисунок 17.7. Firstboot authentication Password Options screen

17.3. Date and Time

Use this screen to adjust the date and time of the system clock. To change these settings after installation, click SystemAdministrationDate & Time.
Firstboot date and time screen
Firstboot date and time screen
Рисунок 17.8. Firstboot date and time screen

Click the Synchronize date and time over the network checkbox to configure your system to use Network Time Protocol (NTP) servers to maintain the accuracy of the clock. NTP provides time synchronization service to computers on the same network. Many public NTP servers are available on the Internet.

17.4. Hardware Profile

Firstboot displays a screen that allows you to submit your hardware information anonymously to the Fedora Project. Developers use these hardware details to guide further support efforts. You can read more about this project and its development at http://smolts.org/.
Firstboot hardware profile screen
Firstboot hardware profile screen
Рисунок 17.9. Firstboot hardware profile screen

To opt in to this important work, select Send Profile. If you choose not to submit any profile data, do not change the default. Select Finish to continue to the login screen.

Update Your System

To ensure the security of your system, run a package update after the installation completes. Глава 18, Your Next Steps explains how to update your Fedora system.

Глава 18. Your Next Steps

18.1. Updating Your System

The Fedora Project releases updated software packages for Fedora throughout the support period of each version. Updated packages add new features, improve reliability, resolve bugs, or remove security vulnerabilities. To ensure the security of your system, update regularly, and as soon as possible after a security announcement is issued. Refer to Раздел 18.4, «Подписка на объявления и новости Fedora» for information on the Fedora announcements services.
Апплет обновлений устанавливается в Fedora по умолчанию и будет напоминать о наличии доступных обновлений в любых настроенных репозиториях. Этот апплет выполняется в фоновом режиме. При наличии обновлений он покажет уведомление, которое можно просто нажать для их получения.
Чтобы обновить программное обеспечение вручную, используйте программу обновления:
Обновление системы
Экран обновления системы
Рисунок 18.1. Обновление системы

  1. В системном меню выберите СистемаАдминистрированиеОбновить систему.
  2. Нажмите Просмотр для просмотра списка обновленных пакетов.
  3. Нажмите Обновить систему, чтобы начать процесс обновления.
  4. Если обновления требуют перезагрузки системы, будет показано окно диалога, где можно будет выбрать перезагрузку. В противном случае нажмите кнопку отмены.
  5. Если перезагрузка не требуется, после завершения обновления появится окно, сообщающее об этом. Нажмите кнопку Закрыть.
Пакеты можно обновить из командной строки с помощью утилиты yum. Например, команда полного обновления системы будет выглядеть так:
su -c 'yum update'
По запросу введите пароль пользователя root.
Refer to http://docs.fedoraproject.org/yum/ for more information on yum.

Обязательно наличие подключения к сети

Прежде чем приступить к обновлению, убедитесь, что система подключена к сети, так как в процессе обновления пакеты будут загружаться с сетевых серверов.
If your Fedora system has a permanent network connection, you may choose to enable daily system updates. To enable automatic updates, follow the instructions on the webpage http://docs.fedoraproject.org/yum/sn-updating-your-system.html.

18.2. Finishing an Upgrade

System Updates Recommended

После обновления и перезагрузки системы рекомендуется выполнить обновление вручную (см. Раздел 18.1, «Updating Your System»).
If you chose to upgrade your system from a previous release ratherthan perform a fresh installation, you may want to examine the differences in the package set. Раздел 9.14.2, « Upgrading Using the Installer » advised you to create a package listing for your original system. You can now use that listing to determine how to bring your new system close to the original system state.
Most software repository configurations are stored in packages that end with the term release. Check the old package list for the repositories that were installed:
awk '{print $1}' ~/old-pkglist.txt | grep 'release$'
If necessary, retrieve and install these packages from their original sources on the Internet. Follow the instructions at the originating site to install the repository configuration packages for use by yum and other software management tools on your Fedora system.
Then run the following commands to make a list of other missing software packages:
awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt
rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt
diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt
Now use the file /tmp/pkgs-to-install.txt with the yum command to restore most or all of your old software:
su -c 'yum install `cat /tmp/pkgs-to-install.txt`'

Missing Software

Вследствие различий между наборами пакетов в различных версиях Fedora не исключено, что это не восстановит все пакеты. Можно еще раз сравнить перечень пакетов, используя описанную выше методику, и исправить найденные недостатки.

18.3. Switching to a Graphical Login

Если нужен доступ к репозиториям пакетов

To switch to a graphical environment, you might need to install extra software from a repository. You can access Fedora repositories through the Internet or use a Fedora installation DVD as a repository. Refer to Раздел 18.3.1, «Активация доступа к репозиториям из командной строки».
If you installed using a text login and wish to switch to a graphical login, follow this procedure.
  1. Перейдите в режим root:
    su -
    Provide the administrator password when prompted.
  2. При необходимости установите систему X Window и графическое окружение рабочего стола. Например, команда установки GNOME выглядит так:
    yum groupinstall "X Window System" Desktop
    Команда установки KDE:
    yum groupinstall "X Window System" "KDE Desktop"
    Загрузка и установка дополнительных программ может занять некоторое время. В зависимости от используемого источника установки, возможно, потребуется вставить установочный носитель.
  3. Run the following commands to change the run level:
      rm -f /etc/systemd/system/default.target
      ln -s /lib/systemd/system/graphical.target
      /etc/systemd/system/default.target
Выполните команду reboot для перезагрузки системы.

18.3.1. Активация доступа к репозиториям из командной строки

The usual way to install new software on a Fedora system is through a software repository. You can access Fedora repositories through the Internet, or use a Fedora installation DVD as a repository. The software that you access through online repositories is more up-to-date than what is available on an installation DVD. Furthermore, configuring a Fedora system to access online repositories is generally easier than configuring the system to use an installation DVD as a repository, as long as you have an existing, wired network connection available.

18.3.1.1. Активация доступа к репозиториям через Интернет

By default, every Fedora installation is already configured to access Fedora repositories through the Internet. Therefore, all you must do is ensure that the system can access the Internet. If you have an existing, wired network connection available, this process is straightforward:
  1. Перейдите в режим root:
    su -
  2. Убедитесь, что компьютер физически подключен к сети. В данном случае сеть может состоять как минимум из самого компьютера и модема или маршрутизатора.
  3. Выполните команду system-config-network для запуска утилиты настройки сети.
  4. Select Device configuration and press Enter. The network configuration tool displays the Select A Device screen with a list of network interfaces present on your system. The first interface is named eth0 by default.
  5. Выберите интерфейс и нажмите Enter. Откроется окно настроек.
  6. В этом окне можно вручную задать статический адрес IP, шлюз и серверы DNS или оставить поля пустыми и принять стандартные значения. Завершив, нажмите OK, чтобы вернуться к окну выбора устройств.
  7. Выберите Сохранить и нажмите Enter для возврата к окну выбора действий.
  8. Выберите Сохранить и выйти и нажмите Enter, чтобы завершить работу программы.
  9. Выполните команду ifup интерфейс, указав только что настроенный интерфейс. Пример: ifup eth0.
Настройка коммутируемого и беспроводного соединения гораздо сложнее и ее описание выходит за рамки этого руководства.

18.3.1.2. Using a Fedora Installation DVD as a Software Repository

To use a Fedora installation DVD as a software repository, either in the form of a physical disc, or in the form of an ISO image file.
  1. If you are using a physical DVD, insert the disc into your computer.
  2. Перейдите в режим root:
    su -
  3. Создайте точку подключения (монтирования):
    mkdir -p /путь/к/репозиторию
    укажите путь к репозиторию, например /mnt/repo
  4. Mount the DVD on the mount point that you just created. If you are using a physical disc, you need to know the device name of your DVD drive. You can find the names of any CD or DVD drives on your system with the command cat /proc/sys/dev/cdrom/info. The first CD or DVD drive on the system is typically named sr0. When you know the device name, mount the DVD:
    mount -r -t iso9660 /dev/устройство /путь/к/репозиторию
    Пример: mount -r -t iso9660 /dev/sr0 /mnt/repo
    Ниже приведен пример команды подключения ISO-образа.
    mount -r -t iso9660 -o loop /путь/к/образу.iso /путь/к/репозиторию
    For example: mount -r -o loop /home/root/Downloads/Fedora17-Server-i386-DVD.iso /mnt/repo
    Стоит отметить, что монтирование образа возможно только если смонтировано содержащее его устройство. Например, если файл образа расположен на жестком диске, который не был смонтирован автоматически при загрузке системы, потребуется смонтировать этот диск, после чего можно будет смонтировать образ. Так, например, если жесткий диск /dev/sdb не был автоматически смонтирован при загрузке, а образ расположен на этом диске в каталоге Downloads, то:
    mkdir /mnt/temp
    mount /dev/sdb1 /mnt/temp
    mkdir /mnt/repo
    mount -r -t iso9660 -o loop /mnt/temp/Downloads/Fedora-17-i386-DVD.iso /mnt/repo
    Если вы не уверены, подключен ли накопитель, выполните команду mount для получения списка подключенных устройств. Команда fdisk -l поможет определить имя устройства и номер раздела.
  5. Create a new repo file in the /etc/yum.repos.d/ directory. The name of the file is not important, as long as it ends in .repo. For example, dvd.repo is an obvious choice.
    1. Choose a name for the repo file and open it as a new file with the vi text editor. For example:
      vi /etc/yum.repos.d/dvd.repo
    2. Нажмите клавишу I для перехода в режим вставки.
    3. Supply the details of the repository. For example:
      [dvd]
      baseurl=file:///mnt/repo/Server
      enabled=1
      gpgcheck=1
      gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
      The name of the repository is specified in square brackets — in this example, [dvd]. The name is not important, but you should choose something that is meaningful and recognizable.
      The line that specifies the baseurl should contain the path to the mount point that you created previously, suffixed with /Server for a Fedora server installation DVD, or with /Client for a Fedora client installation DVD.
    4. Нажмите Esc для выхода из режима вставки.
    5. Введите :wq и нажмите Enter, чтобы сохранить изменения и выйти из редактора vi.
    6. After installing or upgrading software from the DVD, delete the repo file that you created.

18.4. Подписка на объявления и новости Fedora

Чтобы получать последнюю информацию об обновлениях пакетов, подпишитесь на RSS-канал или рассылку объявлений.
Список рассылки объявлений Проекта Fedora
RSS-каналы Проекта Fedora
Рассылка объявлений также предоставляет новости Fedora и сообщества.

Объявления безопасности

Ключевое слово [SECURITY] в заголовке объявления значит, что обновления пакетов решают проблемы безопасности.

18.5. Документация и поддержка

Сообщество Fedora обеспечивает поддержку посредством почтовых рассылок, Интернет-форумов и пользовательских групп по интересам (ГпИ) по всему миру.
The Web site for the formally endorsed forums is http://forums.fedoraforum.org/.
Информационные ресурсы Fedora:
Many other organizations and individuals also provide tutorials and HOWTOs for Fedora on their Web sites.

18.6. Вступление в сообщество Fedora

Проект Fedora полностью находится под управлением энтузиастов, вносящих свой вклад в различных областях. Участники сообщества обеспечивают поддержку других пользователей, предоставляют документацию, принимают активное участие в усовершенствовании программного обеспечения Fedora, начиная с тестирования программ и заканчивая их разработкой совместно с программистами Red Hat. Результаты работы сообщества открыты всем.
Хотите принять участие? Начните здесь:

Глава 19. Basic System Recovery

When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system.

19.1. Rescue Mode

19.1.1. Common Problems

You might need to boot into one of these recovery modes for any of the following reasons:
  • Невозможно загрузить Fedora обычным образом (на уровне выполнения 3 или 5).
  • Возникли программные или аппаратные проблемы и необходимо извлечь важные файлы с жесткого диска компьютера.
  • You forgot the root password.

19.1.1.1. Не удается загрузить Fedora

Эта проблема часто возникает в результате установки другой операционной системы после установки Fedora. Некоторые операционные системы предполагают, что никакие другие операционные системы на компьютере не установлены, и переписывают основную загрузочную запись (MBR, Master Boot Record), до этого содержащую загрузчик GRUB. Если загрузчик переписан, вы не сможете загрузить Fedora до тех пор, пока вы не перейдете в режим восстановления и не перенастроите загрузчик.
Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your / partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the /etc/grub.d/10_linux file.
Раздел 19.1.2.1, «Reinstalling the Boot Loader» содержит инструкции по переустановке загрузчика GRUB в окружении восстановления.

19.1.1.2. Hardware/Software Problems

В эту категорию входят самые разные ситуации. Например, это может быть сбой жестких дисков или указание неверного ядра или корневого устройства в файле конфигурации загрузчика. В любой из этих ситуаций вы не сможете загрузить Fedora. Но если вы загрузитесь в режиме восстановления системы, возможно, проблему можно будет решить или как минимум создать копии важных файлов.

19.1.1.3. Root Password

What can you do if you forget your root password? To reset it to a different password, boot into rescue mode or single-user mode, and use the passwd command to reset the root password.

19.1.2. Booting into Rescue Mode

Режим восстановления предоставляет возможность загрузить минимальное окружение целиком с CD-ROM или иным способом вместо загрузки с жесткого диска.
Как и следует из названия, этот режим предусмотрен для восстановления в случае сбоя. В штатном режиме система Fedora использует файлы, размещенные на жестком диске компьютера для запуска программ, хранения файлов и прочих операций.
Однако бывают ситуации, когда вы не можете полностью запустить Fedora, и, таким образом, не получаете доступ к файлам на жестком диске компьютера. В режиме восстановления можно обращаться к файлам на жестком диске, даже если вы не смогли запустить Fedora с этого диска.
To boot into rescue mode, you must be able to boot the system using one of the following methods[5]:
  • Загрузка системы с загрузочного диска CD/DVD.
  • By booting the system from other installation boot media, such as USB flash devices.
  • By booting the system from the Fedora installation DVD.
Once you have booted using one of the described methods, add the keyword rescue as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt:
linux rescue
Будет предложено ответить на некоторые базовые вопросы, в частности, выбрать используемый язык и расположение корректного образа восстановления. Выберите Локальный CD-ROM, Жесткий диск, Образ NFS, FTP или HTTP. В указанном месте должно находиться подходящее дерево установки той же версии Fedora, что и версия на компакт-диске Fedora, с которого вы загрузились. Если вы используете для запуска режима восстановления загрузочный компакт-диск или другой носитель, это должно быть то же дерево установочных каталогов, из которого создавался носитель. За дополнительными сведениями о настройке дерева установки на жестком диске, NFS, FTP или HTTP-сервере, обратитесь к предыдущей секции данного руководства.
If you select a rescue image that does not require a network connection, you are asked whether or not you want to establish a network connection. A network connection is useful if you need to backup files to a different computer or install some RPM packages from a shared network location, for example.
The following message is displayed:
The rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage. You can then make any changes required to your system. If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'. If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.
If you select Continue, it attempts to mount your file system under the directory /mnt/sysimage/. If it fails to mount a partition, it notifies you. If you select Read-Only, it attempts to mount your file system under the directory /mnt/sysimage/, but in read-only mode. If you select Skip, your file system is not mounted. Choose Skip if you think your file system is corrupted.
Once you have your system in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2 (use the Ctrl-Alt-F1 key combination to access VC 1 and Ctrl-Alt-F2 to access VC 2):
sh-3.00b#
If you selected Continue to mount your partitions automatically and they were mounted successfully, you are in single-user mode.
Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5). If you selected to mount your file system and it mounted successfully, you can change the root partition of the rescue mode environment to the root partition of your file system by executing the following command:
chroot /mnt/sysimage
This is useful if you need to run commands such as rpm that require your root partition to be mounted as /. To exit the chroot environment, type exit to return to the prompt.
If you selected Skip, you can still try to mount a partition or LVM2 logical volume manually inside rescue mode by creating a directory such as /foo, and typing the following command:
mount -t ext4 /dev/mapper/VolGroup00-LogVol02 /foo
In the above command, /foo is a directory that you have created and /dev/mapper/VolGroup00-LogVol02 is the LVM2 logical volume you want to mount. If the partition is of type ext2 or ext3 replace ext4 with ext2 or ext3 respectively.
If you do not know the names of all physical partitions, use the following command to list them:
fdisk -l
If you do not know the names of all LVM2 physical volumes, volume groups, or logical volumes, use the following commands to list them:
pvdisplay
vgdisplay
lvdisplay
From the prompt, you can run many useful commands, such as:
  • ssh, scp, and ping if the network is started
  • dump and restore for users with tape drives
  • parted and fdisk for managing partitions
  • rpm for installing or upgrading software
  • vi for editing text files

19.1.2.1. Reinstalling the Boot Loader

In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems.
The following steps detail the process on how GRUB is reinstalled on the master boot record:
  • Boot the system from an installation boot medium.
  • Type linux rescue at the installation boot prompt to enter the rescue environment.
  • Type chroot /mnt/sysimage to mount the root partition.
  • Type /sbin/grub-install bootpart to reinstall the GRUB boot loader, where bootpart is the boot partition (typically, /dev/sda).
  • Review the /etc/grub.d/10_linux file, as additional entries may be needed in the /etc/grub.d/40_custom for GRUB to control additional operating systems.
  • Reboot the system.

19.1.3. Booting into Single-User Mode

One of the advantages of single-user mode is that you do not need a boot CD-ROM; however, it does not give you the option to mount the file systems as read-only or not mount them at all.
If your system boots, but does not allow you to log in when it has completed booting, try single-user mode.
In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell. Unlike rescue mode, single-user mode automatically tries to mount your file system. Do not use single-user mode if your file system cannot be mounted successfully. You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted.
On an x86 system using GRUB, use the following steps to boot into single-user mode:
  1. Press the Esc key at boot time to load the GRUB splash screen, then press any key to enter the GRUB interactive menu.
  2. Выберите Fedora с версией ядра, которую вы хотите загрузить, и нажмите a для добавления новой строки.
  3. Go to the end of the line and type single as a separate word (press the Spacebar and then type single). Press Enter to exit edit mode.

19.1.4. Booting into Emergency Mode

In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the init files are not loaded. If init is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation.
Чтобы загрузиться в аварийном режиме, выполните действия для входа в монопольный режим, описанные в предыдущей секции (см. Раздел 19.1.3, «Booting into Single-User Mode»), но вместо слова single укажите emergency.

19.2. Using rescue mode to fix or work around driver problems

A malfunctioning or missing driver can prevent a system from booting normally. Rescue mode provides an environment in which you can add, remove, or replace a driver even when the system fails to boot. Wherever possible, we recommend that you use the RPM package manager to remove malfunctioning drivers or to add updated or missing drivers. If you cannot remove a malfunctioning driver for some reason, you can instead blacklist the driver so that it does not load at boot time.
Note that when you install a driver from a driver disc, the driver disc updates all initramfs images on the system to use this driver. If a problem with a driver prevents a system from booting, you cannot rely on booting the system from another initramfs image.

19.2.1. Using RPM to add, remove, or replace a driver

In rescue mode, you can use RPM to install, remove, or update packages from the installed system, even though you did not boot the installed system. To remove a malfunctioning driver:
  1. Boot the system into rescue mode with the linux rescue command at the boot prompt, or the linux rescue dd command if you need to load a third-party driver from a driver disc. Follow the instructions in Раздел 19.1.2, «Booting into Rescue Mode» and do not choose to mount the installed system as read only.
  2. Change the root directory to /mnt/sysimage/:
    chroot /mnt/sysimage/
  3. Use the rpm -e command to remove the driver package. For example, to remove the kmod-foobar driver package, run:
    rpm -e kmod-foobar
  4. Exit the chroot environment:
    exit
Installing a driver is a similar process, but the RPM package that contains the driver must be available on the system.
  1. Boot the system into rescue mode with the linux rescue command at the boot prompt, or the linux rescue dd command if you need to load a third-party driver from a driver disc. Follow the instructions in Раздел 19.1.2, «Booting into Rescue Mode» and do not choose to mount the installed system as read only.
  2. Make the RPM package that contains the driver available. For example, mount a CD or USB flash drive and copy the RPM package to a location of your choice under /mnt/sysimage/, for example: /mnt/sysimage/root/drivers/.
  3. Change the root directory to /mnt/sysimage/:
    chroot /mnt/sysimage/
  4. Use the rpm -ivh command to install the driver package. For example, to install the kmod-foobar driver package from /root/drivers/, run:
    rpm -­ivh /root/drivers/kmod-foobar-­1.2.0­4.17.el6.i686
    Note that /root/drivers/ in this chroot environment is /mnt/sysimage/root/drivers/ in the original rescue environment.
When you have finished removing and installing drivers, reboot the system.

19.2.2. Blacklisting a driver

As described in Раздел 19.1.2, «Booting into Rescue Mode», the rdblacklist kernel option blacklists a driver at boot time. To continue to blacklist the driver on subsequent boots, add the rdblacklist option to the line in /etc/grub.d/10_linux that describes your kernel. To blacklist the driver when the root device is mounted, add a blacklist entry in a file under /etc/modprobe.d/.
  1. Boot the system into rescue mode with the command linux rescue rdblacklist=name_of_driver, where name_of_driver is the driver that you need to blacklist. Follow the instructions in Раздел 19.1.2, «Booting into Rescue Mode» and do not choose to mount the installed system as read only.
  2. Open the /mnt/sysimage/etc/grub.d/10_linux file with the vi text editor:
    vi /mnt/sysimage/etc/grub.d/10_linux
  3. Identify the default kernel used to boot the system. Each kernel is specified in the 10_linux file with a group of lines that begins menuentry. The default kernel is specified by the default parameter in /etc/default/grub. A value of 0 refers to the first menu entry in the custom script files in /etc/grub.d, a value of 1 refers to the second menu entry, and higher values refer to subsequent kernels in turn. Check the script prior to 10_linux, named 00_header, to ensure you specify the correct kernel.
  4. Edit the linux line of the menu entry to include the option rdblacklist=name_of_driver, where name_of_driver is the driver that you need to blacklist. For example, to blacklist the driver named foobar:
    linux /vmlinuz-2.6.32-71.18-2.el6.i686 ro root=/dev/sda1 rhgb quiet rdblacklist=foobar
  5. Save the file and exit vi.
  6. Create a new file under /etc/modprobe.d/ that contains the command blacklist name_of_driver. Give the file a descriptive name that will help you find it in future, and use the filename extension .conf. For example, to continue to blacklist the driver foobar when the root device is mounted, run:
    echo "blacklist foobar" >> /mnt/sysimage/etc/modprobe.d/blacklist-foobar.conf
  7. Reboot the system. You no longer need to supply rdblacklist manually as a kernel option until you next update the default kernel. If you update the default kernel before the problem with the driver has been fixed, you must edit 10_linux again to ensure that the faulty driver is not loaded at boot time.


[5] Refer to the earlier sections of this guide for more details.

Глава 20. Upgrading Your Current System

В этой главе рассматриваются различные способы обновления предыдущих версий Fedora.

20.1. Determining Whether to Upgrade or Re-Install

Before upgrading to Fedora 17 you should first bring your current version up to date. However, it is not then necessary to upgrade to intermediate versions. For example, you can upgrade from Fedora 14 to Fedora 17 directly.
Такой рекомендуемый способ переустановки поможет достичь максимальной стабильности системы.
If you currently use Fedora 16, you can perform a traditional, installation program-based upgrade.
However, before you chose to upgrade your system, there are a few things you should keep in mind:
  • Individual package configuration files may or may not work after performing an upgrade due to changes in various configuration file formats or layouts.
  • Third party or ISV applications may not work correctly following the upgrade.
  • If you have additional third-party package repositories (such as rpmfusion) enabled, note that software installed from those repositories may not function properly after a system upgrade. Fedora does not maintain third-party packages and cannot guarantee that such repositories are up-to-date.
Upgrading your system installs updated versions of the packages which are currently installed on your system.
The upgrade process preserves existing configuration files by renaming them with an .rpmsave extension (for example, sendmail.cf.rpmsave). The upgrade process also creates a log of its actions in /root/upgrade.log.

Warning

As software evolves, configuration file formats can change. It is very important to carefully compare your original configuration files to the new files before integrating your changes.

Примечание

Рекомендуется создать резервную копию всех данных. Например, при обновлении системы или создании двойной загрузки, следует сделать копию необходимых данных на всех жестких дисках, так как ошибки могут привести к потере всех данных.
Some upgraded packages may require the installation of other packages for proper operation. If you choose to customize your packages to upgrade, you may be required to resolve dependency problems. Otherwise, the upgrade procedure takes care of these dependencies, but it may need to install additional packages which are not on your system.
Depending on how you have partitioned your system, the upgrade program may prompt you to add an additional swap file. If the upgrade program does not detect a swap file that equals twice your RAM, it asks you if you would like to add a new swap file. If your system does not have a lot of RAM (less than 256 MB), it is recommended that you add this swap file.

20.2. Upgrading Your System

В большинстве случае проще всего выполнить модернизацию существующей версии Fedora можно с помощью утилиты preupgrade, которая загрузит все необходимые пакеты и приступит к обновлению.
Установить preupgrade можно с помощью менеджера пакетов или выполнив команду yum install preupgrade.
Для запуска программы preupgrade просто выполните команду preupgrade в строке приглашения.
You can also upgrade a Fedora installation by starting the installation process by any of the methods described in Глава 9, Installing using anaconda. If the installer detects a previous Fedora installation on the system, it will ask you whether you want to upgrade that installation — refer to Раздел 9.14.1, «Экран обновления системы»
The Upgrade Examine screen appears if you have instructed the installation program to perform an upgrade.

Примечание

Если содержимое файла /etc/fedora-release отличается от стандартного, при попытке обновления до Fedora 17 установка Fedora может быть не найдена.
You can relax some of the checks against this file by booting with the following boot command:
linux upgradeany
Выполните команду linux upgradeany, если при установке Fedora возможность обновления отсутствует.
To perform an upgrade, select Perform an upgrade of an existing installation. Click Next when you are ready to begin your upgrade.
To re-install your system, select Perform a new Fedora installation and refer to Глава 9, Installing using anaconda for further instructions.

Глава 21. Удаление Fedora

Мы уважаем свободу выбора операционной системы для вашего компьютера. В этой секции рассказано, как удалить Fedora.

These instructions may destroy data!

Если вы хотите сохранить важные данные из удаляемой версии Fedora, создайте их резервную копию. Запишите их на CD, DVD, внешний жесткий диск или другое устройство хранения.
As a precaution, also back up data from any other operating systems that are installed on the same computer. Mistakes do happen and can result in the loss of all your data.
Если вы создаете резервную копию данных Fedorа для их последующего переноса в другую операционную систему, убедитесь, что носитель данных может быть прочитан в новой операционной системе. Например, Microsoft Windows не сможет прочитать внешний диск, если он был отформатирован в Fedora как ext2, ext3, ext4. Для его чтения потребуется установить дополнительные программы.
Чтобы удалить Fedora из систем x86, необходимо удалить информацию загрузчика Fedora из MBR и разделы, содержащие операционную систему. Способы удаления Fedora на разных компьютерах могут отличаться в зависимости от того, является ли Fedora единственной установленной операционной системой или компьютер использует двойную загрузку.
Приведенные инструкции не могут охватить все возможные конфигурации компьютеров. Если ваш компьютер допускает загрузку больше двух операционных систем или его схема разделов довольно специфична, рассматривайте эту информацию лишь как общее руководство по удалению разделов. В таких случаях также потребуется настроить выбранный загрузчик. Приложение E, The GRUB Boot Loader содержит общую информацию, подробное описание выходит за рамки данного документа.

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 Раздел 21.3, «Замена Fedora ранними версиями Microsoft Windows и MS-DOS» for alternative removal methods for use with MS-DOS and these versions of Windows.

21.1. Fedora является единственной операционной системой

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.
Стоит отметить, что некоторые производители компьютеров хоть и включают предустановленную систему Microsoft Windows, но не предоставляют установочный диск Windows, вместо этого предоставляя собственный «диск восстановления системы» или программы для его создания. Иногда для хранения программ восстановления выделяется отдельный раздел. Если вы уверены, был ли предоставлен установочный диск, обратитесь к документации компьютера.
When you have located the installation media for your chosen operating system:
  1. Back up any data that you want to keep.
  2. Shut down the computer.
  3. Boot your computer with the installation disk for the replacement operating system.
  4. Следуйте инструкциям процесса установки. Установочные диски Windows, OS X и большинства систем Linux обычно позволяют создавать разделы вручную при установке или предложат удалить все разделы и создать разделы заново. Удалите все существующие разделы или разрешите установщику удалить их автоматически. Диски восстановления систем для компьютеров с предустановленной системой Microsoft Windows могут создать схему разделов автоматически без вашего участия.

    Предупреждение

    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.

21.2. Двойная загрузка: Fedora и другая операционная система

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: Раздел 21.1, «Fedora является единственной операционной системой»

21.2.1. Настроена двойная загрузка (Fedora и Microsoft Windows)

21.2.1.1. Windows 2000, Windows Server 2000, Windows XP, and Windows Server 2003

Предупреждение

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.
Восстановление этих систем полагается на среду восстановления Windows, для загрузки которой требуется наличие установочного диска Windows. Если вы начали такое восстановление, но не завершили его, может оказаться так, что компьютер будет невозможно загрузить. Поставляемые с некоторыми компьютерами Windows диски восстановления системы не всегда включают это окружение.
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. Удалите разделы Fedora
    1. Boot your computer into your Microsoft Windows environment.
    2. Click Start>Run..., type diskmgmt.msc and press Enter. The Disk Management tool opens.
      В окне будет представлена графическая диаграмма диска с разделами. Первый раздел обычно соответствует диску C: и отмечен как NTFS. Кроме него должно быть показано как минимум два раздела Fedora. Windows не покажет тип файловой системы разделов Fedora, но может назначить букву диска.
    3. Выберите раздел Fedora и откройте контекстное меню, нажав правую клавишу мыши, выберите пункт Удалить раздел и нажмите Да для подтверждения своего выбора. Повторите эти действия для других разделов. По мере их удаления Windows будет отмечать ранее занятое место как свободное.
  2. Разрешите Windows использовать освобожденное после удаления Fedora пространство (необязательно).

    Примечание

    Этот шаг не требуется для удаления Fedora. Но если его пропустить, часть пространства на жестком диске будет недоступна Windows.
    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

    Примечание

    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.
    2. Введите list volume и нажмите Enter. Будет показан список системных разделов с номерами томов, буквами устройств, метками томов, типами файловых систем и размерами. Найдите в списке раздел Windows, который будет занимать освободившееся после удаления Fedora пространство, и запомните его номер тома (например, «Volume 0»).
    3. 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.
    2. 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.
  3. 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:
      Нажмите любую клавишу для загрузки с CD
      Press any key while the message is still showing and the Windows installation software will load.
    2. 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.
    3. 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.
    4. 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.
    5. At the prompt, type the command fixmbr and press the Enter. The fixmbr tool now restores the Master Boot Record for the system.
    6. When the prompt reappears, type exit and press the Enter key.
    7. Your computer will restart and boot your Windows operating system.

21.2.1.2. Windows Vista and Windows Server 2008

Предупреждение

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.
Восстановление этих систем полагается на среду восстановления Windows, для загрузки которой требуется наличие установочного диска Windows. Если вы начали такое восстановление, но не завершили его, может оказаться так, что компьютер будет невозможно загрузить. Поставляемые с некоторыми компьютерами Windows диски восстановления системы не всегда включают это окружение.
  1. Удалите разделы Fedora
    1. Boot your computer into your Microsoft Windows environment.
    2. Click Start then type diskmgmt.msc into the Start Search box and press Enter. The Disk Management tool opens.
      В окне будет представлена графическая диаграмма диска с разделами. Первый раздел обычно соответствует диску C: и отмечен как NTFS. Кроме него должно быть показано как минимум два раздела Fedora. Windows не покажет тип файловой системы разделов Fedora, но может назначить букву диска.
    3. Выберите раздел Fedora и откройте контекстное меню, нажав правую клавишу мыши, выберите пункт Удалить раздел и нажмите Да для подтверждения своего выбора. Повторите эти действия для других разделов. По мере их удаления Windows будет отмечать ранее занятое место как свободное.
  2. Разрешите Windows использовать освобожденное после удаления Fedora пространство (необязательно).

    Примечание

    Этот шаг не требуется для удаления Fedora. Но если его пропустить, часть пространства на жестком диске будет недоступна Windows.
    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.
    2. 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.
    2. 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.
  3. 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:
      Нажмите любую клавишу для загрузки с CD или DVD
      Press any key while the message is still showing and the Windows installation software will load.
    2. In the Install Windows dialog, select a language, time and currency format, and keyboard type. Click Next
    3. Click Repair your computer.
    4. 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.
    5. Click Command prompt. A command window will open.
    6. Type bootrec /fixmbr and press Enter.
    7. When the prompt reappears, close the command window, then click Restart.
    8. Your computer will restart and boot your Windows operating system.

21.2.2. Двойная загрузка: Fedora и Mac OS X

Порядок удаления Fedora из таких систем зависит от того, установлен ли Boot Camp:
Если Boot Camp не установлен
  1. В /Applications/Utilities откройте Disk Utility.
  2. Слева выберите запись тома с Fedora.
  3. Перейдите на вкладку разделов в правой части окна.
  4. Выберите разделы Fedora и нажмите минус под диаграммой разделов.
  5. Измените размер раздела OS X так, чтобы он включал освобожденное место.
Если Boot Camp установлен
  1. В /Applications/Utilities откройте Boot Camp Assistant.
  2. Выберите опцию создания или удаления раздела Windows и нажмите кнопку продолжения.
  3. При наличии единственного внутреннего диска нажмите кнопку восстановления.
  4. При наличии нескольких внутренних дисков выберите диск Linux и Restore to a single Mac OS partition. Нажмите кнопку продолжения.

21.2.3. Двойная загрузка: Fedora и другой дистрибутив 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. Процедура 21.1. Удаление разделов Fedora
    1. Boot your Fedora installation.
    2. 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)
    3. Ensure that any data on this system that you still require is backed up to another system or storage location.
    4. Shut down the system and boot the Linux distribution that you want to keep on the system.
    5. 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.
    6. Remove any unwanted and unnecessary partitions, for example, with fdisk for standard partitions, or lvremove and vgremove to remove logical volumes and volume groups.
  2. Удалите записи Fedora из загрузчика

    Example only

    Приведенные инструкции предполагают, что система использует загрузчик GRUB. За информацией о других загрузчиках (например, LILO) обратитесь к их документации и удалите записи Fedora из списка загрузки.
    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.
    2. Type gedit etc/grub.d/10_linux and press Enter. This opens the 10_linux file in the gedit text editor.
    3. A typical Fedora entry in the 10_linux file consists of four lines:
      Пример 21.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

      Depending on the configuration of your system, there may be multiple Fedora entries in 10_linux, each corresponding to a different version of the Linux kernel. Delete each of the Fedora entries from these files
      Save the updated 10_linux file and close gedit.
    4. Type gedit etc/default/grub and press Enter.
    5. The file etc/default/grub contains a line that specifies the default operating system to boot, in the format default=N where N is a number equal to or greater than 0. If N is set to 0, GRUB will boot the first operating system in the list. If N is set to 1, it will boot the second operating system, and so forth. Alternatively, the default value can be the full menu entry.
      Identify the entry for the operating system that you want GRUB to boot by default and note its place in the order within the list.
      Make sure that the default= line contains the number one below the number of your chosen default operating system in the list.
      Save the updated grub file and close gedit. If you have Fedora entries in the other script files in the /etc/grub.d directory, use this procedure to remove them in the same way.
  3. Make space available to your operating system

    Примечание

    Этот шаг не требуется для удаления Fedora. Но если его пропустить, часть пространства на жестком диске будет недоступна другим операционным системам Linux.

    Примечание

    To carry out this step, you require live media for a Linux distribution, for example, the Fedora Live CD or the Knoppix DVD.
    Методы освобождения места за счет удаления разделов Fedora, доступных другой операционной системе, отличаются в зависимости от того, установлена ли выбранная операционная система в разделах LVM или нет.
    • If you do not use LVM
      1. Boot your computer from Linux live media, and install parted if it is not already present.
      2. As root or with sudo, run parted disk, where disk is the device name of the disk that contains a partition that you want to resize, for example, /dev/sda.
      3. At the (parted) prompt, enter print. The parted tool displays information about the partitions on your system, including their partition numbers, their sizes, and their positions on the disk.
      4. At the (parted) prompt, enter resize number start end, where number is the partition number, start is the location on the disk at which the partition begins, and end is the location on the disk at which you want the partition to end. Use the start position that you previously obtained with the print command, and refer to the parted documentation for different ways to specify the end parameter.
      5. When parted finishes resizing the partition, enter quit at the (parted) prompt.
      6. Run e2fsck partition, where partition is the partition that you just resized. For example, if you just resized /dev/sda3, enter e2fsck /dev/sda3.
        Linux now checks the file system of the newly-resized partition.
      7. When the file system check finishes, type resize2fs partition at a command line and press Enter, where partition is the partition that you just resized. For example, if you just resized /dev/sda3, type resize2fs /dev/sda3.
        Linux now resizes your file system to fill the newly-resized partition.
      8. Restart your computer. The extra space is now available to your Linux installation.
    • If you use LVM
      1. Boot your computer from Linux live media and install fdisk and lvm2 if they are not already present.
      2. Create a new partition in the free space on the disk
        1. As root or with sudo, run fdisk disk, where disk is the device name of the disk where you want to create new space, for example, /dev/sda.
        2. At the prompt Command (m for help):, enter n to create a new partition. Refer to the fdisk documentation for options.
      3. Change the partition type identifier
        1. At the prompt Command (m for help):, enter t to change a partition type.
        2. At the prompt Partition number (1-4):, type the number of the partition that you just created. For example, if you just created partition /dev/sda3, type the number 3 and press Enter. This identifies the partition whose type fdisk will change.
        3. At the prompt Hex code (type L to list codes):, enter 8e to create a Linux LVM partition.
        4. At the prompt Command (m for help):, enter w to write the changes to disk and exit fdisk.
      4. Expand the volume group
        1. At the command prompt, type lvm and press Enter to start the lvm2 tool.
        2. At the lvm> prompt, type pvcreate partition and press Enter, where partition is the partition that you recently created. For example, pvcreate /dev/sda3. This creates /dev/sda3 as a physical volume in LVM.
        3. At the lvm> prompt, type vgextend VolumeGroup partition and press Enter, where VolumeGroup is the LVM volume group on which Linux is installed and partition is the partition that you recently created. For example, if Linux is installed on /dev/VolumeGroup00, you would type vgextend /dev/VolumeGroup00 /dev/sda3 to extend that volume group to include the physical volume at /dev/sda3.
        4. At the lvm> prompt, type lvextend -l +100%FREE LogVol and press Enter, where LogVol is the logical volume that contains your Linux filesystem. For example, to extend LogVol00 to fill the newly-available space in its volume group, VolGroup00, type lvextend -l +100%FREE /dev/VolGroup00/LogVol00.
        5. At the lvm> prompt, type exit and press Enter to exit lvm2
      5. Type e2fsck LogVol at the command line and press Enter, where LogVol is the logical volume that you just resized. For example, if you just resized /dev/VolumeGroup00/LogVol00, you would type e2fsck /dev/VolumeGroup00/LogVol00.
        Linux now checks the file system of the newly-resized logical volume.
      6. When the file system check finishes, type resize2fs LogVol at a command line and press Enter, where LogVol is the partition that you just resized. For example, if you just resized /dev/VolumeGroup00/LogVol00, you would type resize2fs /dev/VolumeGroup00/LogVol00.
        Linux now resizes your file system to fill the newly-resized logical volume.
      7. Restart your computer. The extra space is now available to your Linux installation.

21.3. Замена Fedora ранними версиями Microsoft Windows и MS-DOS

In DOS and Windows, use the Windows fdisk utility to create a new MBR with the undocumented flag /mbr. This ONLY rewrites the MBR to boot the primary DOS partition. The command should look like the following:
fdisk /mbr
If you need to remove Linux from a hard drive and have attempted to do this with the default DOS (Windows) fdisk, you will experience the Partitions exist but they do not exist problem. The best way to remove non-DOS partitions is with a tool that understands partitions other than DOS.
To begin, insert the Fedora DVD and boot your system. When the boot prompt appears, type: linux rescue. This starts the rescue mode program.
Будет предложено выбрать клавиатуру и язык. Определите эти значения так же как и во время установки Fedora.
Затем появится экран, сообщающий, что программа попытается найти установку Fedora для восстановления. Выберите Пропустить.
After selecting Skip, you are given a command prompt where you can access the partitions you would like to remove.
First, type the command list-harddrives. This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes.

Warning

Будьте внимательны при удалении разделов Fedora. Случайное удаление других разделов может привести к потере данных или выходу системы из строя.
To remove partitions, use the partitioning utility parted. Start parted, where /dev/hda is the device on which to remove the partition:
parted /dev/hda
Using the print command, view the current partition table to determine the minor number of the partition to remove:
print
Команда print также покажет тип раздела (например, linux-swap, ext2, ext3, ext4). Это поможет принять решение при удалении разделов.
Remove the partition with the command rm. For example, to remove the partition with minor number 3:
rm 3

Important

The changes start taking place as soon as you press [Enter], so review the command before committing to it.
After removing the partition, use the print command to confirm that it is removed from the partition table.
Once you have removed the Linux partitions and made all of the changes you need to make, type quit to quit parted.
After quitting parted, type exit at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If it does not, you can reboot your computer using Control+Alt+Delete .

Часть IV. Technical appendixes

The appendixes in this section do not contain instructions that tell you how to install Fedora. Instead, they provide technical background that you might find helpful to understand the options that Fedora offers you at various points in the installation process.

Содержание

A. An Introduction to Disk Partitions
A.1. Hard Disk Basic Concepts
A.1.1. It is Not What You Write, it is How You Write It
A.1.2. Partitions: Turning One Drive Into Many
A.1.3. Partitions within Partitions — An Overview of Extended Partitions
A.1.4. Выделение места для Fedora
A.1.5. Partition Naming Scheme
A.1.6. Disk Partitions and Other Operating Systems
A.1.7. Disk Partitions and Mount Points
A.1.8. How Many Partitions?
B. ISCSI disks
B.1. iSCSI disks in anaconda
B.2. iSCSI disks during start up
C. Disk Encryption
C.1. What is block device encryption?
C.2. Encrypting block devices using dm-crypt/LUKS
C.2.1. Overview of LUKS
C.2.2. How will I access the encrypted devices after installation? (System Startup)
C.2.3. Choosing a Good Passphrase
C.3. Creating Encrypted Block Devices in Anaconda
C.3.1. What Kinds of Block Devices Can Be Encrypted?
C.3.2. Saving Passphrases
C.3.3. Creating and Saving Backup Passphrases
C.4. Creating Encrypted Block Devices on the Installed System After Installation
C.4.1. Create the block devices
C.4.2. Optional: Fill the device with random data
C.4.3. Format the device as a dm-crypt/LUKS encrypted device
C.4.4. Create a mapping to allow access to the device's decrypted contents
C.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device
C.4.6. Add the mapping information to /etc/crypttab
C.4.7. Add an entry to /etc/fstab
C.5. Common Post-Installation Tasks
C.5.1. Set a randomly generated key as an additional way to access an encrypted block device
C.5.2. Add a new passphrase to an existing device
C.5.3. Remove a passphrase or key from a device
D. Understanding LVM
E. The GRUB Boot Loader
E.1. Boot Loaders and System Architecture
E.2. GRUB
E.2.1. GRUB and the boot process on BIOS-based x86 systems
E.2.2. GRUB and the boot process on UEFI-based x86 systems
E.2.3. Features of GRUB
E.3. Installing GRUB
E.4. GRUB Terminology
E.4.1. Device Names
E.4.2. File Names and Blocklists
E.4.3. The Root File System and GRUB
E.5. GRUB Interfaces
E.5.1. Interfaces Load Order
E.6. GRUB Commands
E.7. GRUB Menu Configuration File
E.7.1. Configuration File Structure
E.7.2. Configuration File Directives
E.8. Changing Runlevels at Boot Time
E.9. Additional Resources
E.9.1. Installed Documentation
E.9.2. Useful Websites
F. Boot Process, Init, and Shutdown
F.1. The Boot Process
F.2. A Detailed Look at the Boot Process
F.2.1. The firmware interface
F.2.2. UEFI-based x86 systems
F.3. The Boot Loader
F.3.1. The GRUB2 boot loader for x86 systems
F.3.2. Boot Loaders for Other Architectures
F.4. The Kernel
F.5. Booting with systemd
F.6. systemd units
F.7. systemd targets
F.8. Running Additional Programs at Boot Time
F.9. Administering services with systemd
F.9.1. Checking up on services
F.9.2. Starting and stopping services
F.9.3. Running services automatically
F.9.4. Killing and Masking services
F.9.5. Getting more from systemd
G. Logging the Installation
G.1. Log files and formats
G.1.1. Logging on the installed system
G.2. Remote logging with rsyslog
G.3. Remote logging via virtio
H. Other Technical Documentation

An Introduction to Disk Partitions

Примечание

This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
If you are reasonably comfortable with disk partitions, you could skip ahead to Раздел A.1.4, «Выделение места для Fedora», for more information on the process of freeing up disk space to prepare for a Fedora installation. This section also discusses the partition naming scheme used by Linux systems, sharing disk space with other operating systems, and related topics.

A.1. Hard Disk Basic Concepts

Hard disks perform a very simple function — they store data and reliably retrieve it on command.
При обсуждении таких тем как разбиение диска, важно немного знать об оборудовании, чтобы не запутаться в деталях. Поэтому в этом приложении использована упрощенная схема диска, помогающая понять, что же собственно происходит при разбиении диска. Рисунок A.1, «An Unused Disk Drive» демонстрирует совершенно новый пустой диск.
An Unused Disk Drive
Image of an unused disk drive.
Рисунок A.1. An Unused Disk Drive

Not much to look at, is it? But if we are talking about disk drives on a basic level, it is adequate. Say that we would like to store some data on this drive. As things stand now, it will not work. There is something we need to do first.

A.1.1. It is Not What You Write, it is How You Write It

Опытные пользователи компьютера понимают это достаточно быстро. Нам нужно отформатировать диск. Форматирование (или "создание файловой системы") записывает информацию на диск, задавая в пустом месте неформатированного диска определенный порядок.
Disk Drive with a File System
Image of a formatted disk drive.
Рисунок A.2. Disk Drive with a File System

Как демонстрирует Рисунок A.2, «Disk Drive with a File System», такая организация выдвигает некоторые ограничения:
  • Небольшой процент свободного дискового пространства тратится на хранение данных о файловой системе, что является дополнительными накладными расходами.
  • Файловая система разбивает оставшееся место на небольшие сегменты одинакового размера, которые в Linux называются блоками. [6]
Given that file systems make things like directories and files possible, these trade-offs are usually seen as a small price to pay.
It is also worth noting that there is no single, universal file system. As Рисунок A.3, «Disk Drive with a Different File System», shows, a disk drive may have one of many different file systems written on it. As you might guess, different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. This last statement is not a hard-and-fast rule, however. For example, Fedora supports a wide variety of file systems (including many commonly used by other operating systems), making data interchange between different file systems easy.
Disk Drive with a Different File System
Image of a disk drive with a different file system.
Рисунок A.3. Disk Drive with a Different File System

Of course, writing a file system to disk is only the beginning. The goal of this process is to actually store and retrieve data. Let us take a look at our drive after some files have been written to it.
Disk Drive with Data Written to It
Image of a disk drive with data written to it.
Рисунок A.4. Disk Drive with Data Written to It

Как демонстрирует Рисунок A.4, «Disk Drive with Data Written to It», некоторые незаполненные ранее блоки теперь содержат данные. Однако просто посмотрев на этот рисунок, нельзя точно определить, сколько файлов находится на этом диске. Это может быть и один файл, и несколько, так как файлы используют минимум один блок, а могут использовать и больше. Также необходимо заметить, что занятые блоки не должны находиться рядом; занятые и свободные блоки могут перемежаться. Это называется фрагментацией. Фрагментация может сказаться при попытке изменить размер существующего раздела.
As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used.

A.1.2. Partitions: Turning One Drive Into Many

As disk drive capacities soared, some people began to wonder if having all of that formatted space in one big chunk was such a great idea. This line of thinking was driven by several issues, some philosophical, some technical. On the philosophical side, above a certain size, it seemed that the additional space provided by a larger drive created more clutter. On the technical side, some file systems were never designed to support anything above a certain capacity. Or the file systems could support larger drives with a greater capacity, but the overhead imposed by the file system to track files became excessive.
The solution to this problem was to divide disks into partitions. Each partition can be accessed as if it was a separate disk. This is done through the addition of a partition table.

Примечание

While the diagrams in this chapter show the partition table as being separate from the actual disk drive, this is not entirely accurate. In reality, the partition table is stored at the very start of the disk, before any file system or user data. But for clarity, they are separate in our diagrams.
Disk Drive with Partition Table
Image of an unused disk drive with a partition table.
Рисунок A.5. Disk Drive with Partition Table

Как демонстрирует Рисунок A.5, «Disk Drive with Partition Table», таблица разделов состоит из четырех секций или четырех основных разделов. Основной раздел — это раздел жесткого диска, содержащий только один логический диск (или секцию). В каждой секции хранится информация, определяющая один раздел, таким образом, в таблице разбиения разделов нельзя определить больше четырех разделов.
Each partition table entry contains several important characteristics of the partition:
  • The points on the disk where the partition starts and ends
  • Определение "активности" раздела
  • Тип раздела
Далее эти параметры будут рассмотрены более конкретно. Координаты начала и конца раздела определяют размер раздела и его расположение на диске. Флаг "активный" используется некоторыми загрузчиками операционных систем. Другими словами, операционная система находится в разделе, помеченном как "активный".
Дополнительного разъяснения требует параметр тип раздела. Тип раздела - это число, определяющее ожидаемое использование раздела. Возможно, это определение покажется немного расплывчатым; причина этого в том, что понятие типа раздела само по себе расплывчато. Некоторые операционные системы используют тип раздела для определения типа файловой системы, другие обозначают, что данный раздел связан с этой операционной системой, а третьи обозначают, что он содержит загружаемую операционную систему. В некоторых же случаях имеет место комбинация всех трех способов.
Ознакомившись с этой таблицей, возможно, вы удивитесь, как вообще можно использовать такую излишне сложную структуру (см. Рисунок A.6, «Disk Drive With Single Partition»).
Disk Drive With Single Partition
Image of a disk drive with a single partition.
Рисунок A.6. Disk Drive With Single Partition

In many cases, there is only a single partition spanning the entire disk, essentially duplicating the method used before partitions. The partition table has only one entry used, and it points to the start of the partition.
We have labeled this partition as being of the "DOS" type. Although it is only one of several possible partition types listed in Таблица A.1, «Partition Types», it is adequate for the purposes of this discussion.
Таблица A.1, «Partition Types» содержит список нескольких популярных типов разделов с соответствующими им шестнадцатеричными числовыми значениями.
Таблица A.1. Partition Types
Partition Type Value Partition Type Value
Empty 00 Novell Netware 386 65
DOS 12-bit FAT 01 PIC/IX 75
XENIX root 02 Old MINIX 80
XENIX usr 03 Linux/MINUX 81
DOS 16-bit <=32M 04 Linux swap 82
Extended 05 Linux native 83
DOS 16-bit >=32 06 Linux extended 85
OS/2 HPFS 07 Amoeba 93
AIX 08 Amoeba BBT 94
AIX bootable 09 BSD/386 a5
OS/2 Boot Manager 0a OpenBSD a6
Win95 FAT32 0b NEXTSTEP a7
Win95 FAT32 (LBA) 0c BSDI fs b7
Win95 FAT16 (LBA) 0e BSDI swap b8
Win95 Extended (LBA) 0f Syrinx c7
Venix 80286 40 CP/M db
Novell 51 DOS access e1
PReP Boot 41 DOS R/O e3
GNU HURD 63 DOS secondary f2
Novell Netware 286 64 BBT ff

A.1.3. Partitions within Partitions — An Overview of Extended Partitions

Of course, over time it became obvious that four partitions would not be enough. As disk drives continued to grow, it became more and more likely that a person could configure four reasonably-sized partitions and still have disk space left over. There needed to be some way of creating more partitions.
Enter the extended partition. As you may have noticed in Таблица A.1, «Partition Types», there is an "Extended" partition type. It is this partition type that is at the heart of extended partitions.
When a partition is created and its type is set to "Extended," an extended partition table is created. In essence, the extended partition is like a disk drive in its own right — it has a partition table that points to one or more partitions (now called logical partitions, as opposed to the four primary partitions) contained entirely within the extended partition itself. Рисунок A.7, «Disk Drive With Extended Partition», shows a disk drive with one primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space).
Disk Drive With Extended Partition
Image of a disk drive with an extended partition.
Рисунок A.7. Disk Drive With Extended Partition

As this figure implies, there is a difference between primary and logical partitions — there can only be four primary partitions, but there is no fixed limit to the number of logical partitions that can exist. However, due to the way in which partitions are accessed in Linux, you should avoid defining more than 12 logical partitions on a single disk drive.
Теперь давайте разберемся, как применить эти знания при установке Fedora.

A.1.4. Выделение места для Fedora

The following list presents some possible scenarios you may face when attempting to repartition your hard disk:
  • Unpartitioned free space is available
  • An unused partition is available
  • Free space in an actively used partition is available
Let us look at each scenario in order.

Примечание

Не забывайте, что следующие инструкции упрощены для большей ясности и не учитывают точного расположения разделов, которое вы увидите при установке Fedora.

A.1.4.1. Using Unpartitioned Free Space

В этой ситуации уже созданные разделы занимают не весь жесткий диск, оставляя нераспределенным пространство, не относящееся ни к одному из разделов. Рисунок A.8, «Disk Drive with Unpartitioned Free Space» иллюстрирует пример такой ситуации.
Disk Drive with Unpartitioned Free Space
Image of a disk drive with unpartitioned free space, where 1 represents an undefined partition with unallocated space and 2 represents a defined partition with allocated space.
Рисунок A.8. Disk Drive with Unpartitioned Free Space

На рисунке (см. Рисунок A.8, «Disk Drive with Unpartitioned Free Space») цифрой 1 обозначена незанятая область диска, а 2 обозначает созданный раздел, занявший эту область.
If you think about it, an unused hard disk also falls into this category. The only difference is that all the space is not part of any defined partition.
In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for Fedora). Most pre-installed operating systems are configured to take up all available space on a disk drive (refer to Раздел A.1.4.3, «Using Free Space from an Active Partition»).
Next, we will discuss a slightly more common situation.

A.1.4.2. Using Space from an Unused Partition

В этом случае, вероятно, у вас есть один или несколько разделов, которые вам больше не нужны. Возможно, вы перестали использовать какую-то операционную систему и выделенные ей разделы. Рисунок A.9, «Disk Drive With an Unused Partition» демонстрирует именно такую ситуацию.
Disk Drive With an Unused Partition
Image of a disk drive with an unused partition, where 1 represents an unused partition and 2 represents reallocating an unused partition for Linux.
Рисунок A.9. Disk Drive With an Unused Partition

На рисунке 1 обозначает неиспользуемый раздел, а 2 демонстрирует использование этого раздела для Linux (см. Рисунок A.9, «Disk Drive With an Unused Partition»).
If you find yourself in this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place. You can delete the unused partition and manually create new partitions during the installation process.

A.1.4.3. Using Free Space from an Active Partition

This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data.
Aside from adding a new hard drive to your system, you have two choices:
Создание разделов с разрушением
Basically, you delete the single large partition and create several smaller ones. As you might imagine, any data you had in the original partition is destroyed. This means that making a complete backup is necessary. For your own sake, make two backups, use verification (if available in your backup software), and try to read data from your backup before you delete the partition.

Warning

If there was an operating system of some type installed on that partition, it needs to be reinstalled as well. Be aware that some computers sold with pre-installed operating systems may not include the CD-ROM media to reinstall the original operating system. The best time to notice if this applies to your system is before you destroy your original partition and its operating system installation.
After creating a smaller partition for your existing operating system, you can reinstall any software, restore your data, and start your Fedora installation. Рисунок A.10, «Disk Drive Being Destructively Repartitioned» shows this being done.
Disk Drive Being Destructively Repartitioned
Image of a disk drive being destructively repartitioned, where 1 represents before and 2 represents after.
Рисунок A.10. Disk Drive Being Destructively Repartitioned

На рисунке 1 показывает состояние до, а 2 демонстрирует состояние после операции (см. Рисунок A.10, «Disk Drive Being Destructively Repartitioned»).

Warning

Как иллюстрирует Рисунок A.10, «Disk Drive Being Destructively Repartitioned», все данные в этом разделе будут потеряны, если вы не создадите резервную копию.
Создание разделов без разрушения существующих
Here, you run a program that does the seemingly impossible: it makes a big partition smaller without losing any of the files stored in that partition. Many people have found this method to be reliable and trouble-free. What software should you use to perform this feat? There are several disk management software products on the market. Do some research to find the one that is best for your situation.
While the process of non-destructive repartitioning is rather straightforward, there are a number of steps involved:
  • Compress and backup existing data
  • изменение размера существующего раздела;
  • создание новых разделов.
Next we will look at each step in a bit more detail.
A.1.4.3.1. Compress existing data
As Рисунок A.11, «Disk Drive Being Compressed», shows, the first step is to compress the data in your existing partition. The reason for doing this is to rearrange the data such that it maximizes the available free space at the "end" of the partition.
Disk Drive Being Compressed
Image of a disk drive being compressed, where 1 represents before and 2 represents after.
Рисунок A.11. Disk Drive Being Compressed

На рисунке 1 показывает состояние до, а 2 демонстрирует состояние после операции.
This step is crucial. Without it, the location of your data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved. If this is the case (and it severely restricts the size of your new partition(s)), you may be forced to destructively repartition your disk.
A.1.4.3.2. изменение размера существующего раздела;
Рисунок A.12, «Disk Drive with Partition Resized» иллюстрирует процесс изменения размера раздела. Хотя окончательный результат уменьшения раздела зависит от используемой программы, в большинстве случаев освобожденное место используется для создания неформатированного раздела того же типа, что и исходный.
Disk Drive with Partition Resized
Image of a disk drive with a resized partition, where 1 represents before and 2 represents after.
Рисунок A.12. Disk Drive with Partition Resized

На рисунке 1 показывает состояние до, а 2 демонстрирует состояние после операции.
It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case we have illustrated, it would be best to delete the new DOS partition and create the appropriate Linux partition(s).
A.1.4.3.3. создание новых разделов.
Как было упомянуто ранее, может потребоваться создать новые разделы. Если используемая вами программа не рассчитана на Linux, скорее всего, понадобится удалить раздел, созданный при уменьшении раздела (см. Рисунок A.13, «Disk Drive with Final Partition Configuration»).
Disk Drive with Final Partition Configuration
Image of a disk drive with final partition configuration, where 1 represents before and 2 represents after.
Рисунок A.13. Disk Drive with Final Partition Configuration

На рисунке 1 показывает состояние до, а 2 демонстрирует состояние после операции.

Примечание

The following information is specific to x86-based computers only.
As a convenience to our customers, we provide the parted utility. This is a freely available program that can resize partitions.
If you decide to repartition your hard drive with parted, it is important that you be familiar with disk storage and that you perform a backup of your computer data. You should make two copies of all the important data on your computer. These copies should be to removable media (such as tape, CD-ROM, or diskettes), and you should make sure they are readable before proceeding.
Если вы решите использовать parted, помните, что после работы parted оставляет два раздела: один, размер которого вы уменьшали, и другой, созданный в освобожденной области. Если вы планируете установить Fedora в этой области, нужно удалить новый раздел либо с помощью программы разбиения дисков в вашей операционной системе, либо при настройке разделов во время установки.

A.1.5. Partition Naming Scheme

Linux обращается к дисковым разделам, используя комбинации букв и цифр, что сначала может показаться странным, особенно если вы представляете диски как диск C, диск D и т.д. В мире DOS/ Windows разделы именуются следующим образом:
  • Тип каждого раздела проверяется на совместимость с DOS/ Windows.
  • Если раздел совместим , ему присваивается буква. Буквы дисков начинаются с «C» и продолжаются по алфавиту.
  • The drive letter can then be used to refer to that partition as well as the file system contained on that partition.
В Fedora используется более гибкая и информативная схема, чем предлагаемая другими операционными системами, которая основана на схеме именования файлов, где имена имеют вид /dev/xxyN.
Here is how to decipher the partition naming scheme:
/dev/
This is the name of the directory in which all device files reside. Since partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in /dev/.
xx
The first two letters of the partition name indicate the type of device on which the partition resides, usually either hd (for IDE disks) or sd (for SCSI disks).
y
This letter indicates which device the partition is on. For example, /dev/hda (the first IDE hard disk) or /dev/sdb (the second SCSI disk).
N
The final number denotes the partition. The first four (primary or extended) partitions are numbered 1 through 4. Logical partitions start at 5. So, for example, /dev/hda3 is the third primary or extended partition on the first IDE hard disk, and /dev/sdb6 is the second logical partition on the second SCSI hard disk.

Примечание

В этой схеме именования не указан тип раздела; в отличие от DOS/ Windows, в Fedora могут быть идентифицированы все разделы. Конечно, это не означает, что Fedora может обращаться к данным разделов любого типа, но в большинстве случаев получить доступ к данным другой операционной системы все же возможно.
Возьмите эту информацию на заметку, так как это поможет понять, как создавать разделы, необходимые для работы Fedora.

A.1.6. Disk Partitions and Other Operating Systems

Если разделы Fedora расположены на одном диске с разделами, используемыми другими операционными системами, скорее всего, это не вызовет никаких проблем. Однако существуют определенные комбинации Linux и других операционных систем, которые требуют особого внимания.

A.1.7. Disk Partitions and Mount Points

Пользователи, начинающие знакомство с Linux, часто путаются в том, как Linux использует разделы и обращается к ним. В DOS/Windows это относительно несложно: каждому разделу соответствует буква диска. Вы можете использовать соответствующую букву диска для ссылки на файлы и каталоги, расположенные в этом разделе.
This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. The main difference is that each partition is used to form part of the storage necessary to support a single set of files and directories. This is done by associating a partition with a directory through a process known as mounting. Mounting a partition makes its storage available starting at the specified directory (known as a mount point).
For example, if partition /dev/hda5 is mounted on /usr/, that would mean that all files and directories under /usr/ physically reside on /dev/hda5. So the file /usr/share/doc/FAQ/txt/Linux-FAQ would be stored on /dev/hda5, while the file /etc/gdm/custom.conf would not.
Continuing our example, it is also possible that one or more directories below /usr/ would be mount points for other partitions. For instance, a partition (say, /dev/hda7) could be mounted on /usr/local/, meaning that /usr/local/man/whatis would then reside on /dev/hda7 rather than /dev/hda5.

A.1.8. How Many Partitions?

На этом этапе подготовки к установке Fedora вы должны определиться с числом и размером разделов, которые будут использоваться новой операционной системой. Вопрос «сколько же разделов создавать?» постоянно поднимается в спорах в Linux-сообществе, и этим спорам не видно конца, поэтому лучше будет просто сказать, что число вариантов разбиения диска равно числу мнений людей, обсуждающих эту тему.
Не забывая об этом, придерживайтесь следующей рекомендации: если вы не видите причин сделать по-другому, создайте как минимум разделы swap, /boot/ и / (корневой).
Раздел 9.17.5, «Recommended Partitioning Scheme» содержит дополнительную информацию.


[6] На самом деле, блоки имеют постоянный размер в отличие от приведенного на иллюстрациях. Также учтите, что обычный диск состоит из тысяч таких блоков. Все эти небольшие неточности были допущены ради доступности изложения.

ISCSI disks

Internet Small Computer System Interface (iSCSI) is a protocol that allows computers to communicate with storage devices by SCSI requests and responses carried over TCP/IP. Because iSCSI is based on the standard SCSI protocols, it uses some terminology from SCSI. The device on the SCSI bus to which requests get sent (and which answers these requests) is known as the target and the device issuing requests is known as the initiator. In other words, an iSCSI disk is a target and the iSCSI software equivalent of a SCSI controller or SCSI Host Bus Adapter (HBA) is called an initiator. This appendix only covers Linux as an iSCSI initiator: how Linux uses iSCSI disks, but not how Linux hosts iSCSI disks.
Linux has a software iSCSI initiator in the kernel that takes the place and form of a SCSI HBA driver and therefore allows Linux to use iSCSI disks. However, as iSCSI is a fully network-based protocol, iSCSI initiator support needs more than just the ability to send SCSI packets over the network. Before Linux can use an iSCSI target, Linux must find the target on the network and make a connection to it. In some cases, Linux must send authentication information to gain access to the target. Linux must also detect any failure of the network connection and must establish a new connection, including logging in again if necessary.
The discovery, connection, and logging in is handled in userspace by the iscsiadm utility, and the error handling is also handled in userspace by iscsid.
Both iscsiadm and iscsid are part of the iscsi-initiator-utils package under Fedora.

B.1. iSCSI disks in anaconda

Anaconda can discover (and then log in to) iSCSI disks in two ways:
  1. When anaconda starts, it checks if the BIOS or add-on boot ROMs of the system support iSCSI Boot Firmware Table (iBFT), a BIOS extension for systems which can boot from iSCSI. If the BIOS supports iBFT, anaconda will read the iSCSI target information for the configured boot disk from the BIOS and log in to this target, making it available as an installation target.
  2. If you select the Specialized Storage Devices option during installation, the storage device selection screen presents you with an Add Advanced Target button. If you click this button, you can add iSCSI target information like the discovery IP address. Anaconda probes the given IP address and logs in to any targets that it finds. See Раздел 9.11.1.1, « Advanced Storage Options » for the details that you can specify for iSCSI targets.
While anaconda uses iscsiadm to find and log into iSCSI targets, iscsiadm automatically stores any information about these targets in the iscsiadm iSCSI database. Anaconda then copies this database to the installed system and marks any iSCSI targets not used for / so that the system will automatically log in to them when it starts. If / is placed on an iSCSI target, initrd will log into this target and anaconda does not include this target in start up scripts to avoid multiple attempts to log into the same target.
If / is placed on an iSCSI target, anaconda sets NetworkManager to ignore any network interfaces that were active during the installation process. These interfaces will also be configured by initrd when the system starts. If NetworkManager were to reconfigure these interfaces, the system would lose its connection to /.

B.2. iSCSI disks during start up

ISCSI-related events might occur at a number of points while the system starts:
  1. The init script in the initrd will log in to iSCSI targets used for / (if any). This is done using the iscsistart utility (which can do this without requiring iscsid to run).
  2. When the root filesystem has been mounted and the various service initscripts get run, the iscsid initscript will get called. This script will then start iscsid if any iSCSI targets are used for /, or if any targets in the iSCSI database are marked to be logged in to automatically.
  3. After the classic network service script has been run (or would have been run if enabled) the iscsi initscript will run. If the network is accessible, this will log in to any targets in the iSCSI database which are marked to be logged in to automatically. If the network is not accessible, this script will exit quietly.
  4. When using NetworkManager to access the network (instead of the classic network service script), NetworkManager will call the iscsi initscript. See: /etc/NetworkManager/dispatcher.d/04-iscsi

    Важно

    Because NetworkManager is installed in /usr, you cannot use it to configure network access if /usr is on network-attached storage such as an iSCSI target.
If iscsid is not needed as the system starts, it will not start automatically. If you start iscsiadm, iscsiadm will start iscsid in turn.

Disk Encryption

C.1. What is block device encryption?

Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication. This provides additional security beyond existing OS security mechanisms in that it protects the device's contents even if it has been physically removed from the system.

C.2. Encrypting block devices using dm-crypt/LUKS

Linux Unified Key Setup (LUKS) is a specification for block device encryption. It establishes an on-disk format for the data, as well as a passphrase/key management policy.
LUKS uses the kernel device mapper subsystem via the dm-crypt module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the cryptsetup utility.

C.2.1. Overview of LUKS

  • What LUKS does:
    • LUKS encrypts entire block devices
      • LUKS is thereby well-suited for protecting the contents of mobile devices such as:
        • Removable storage media
        • Laptop disk drives
    • The underlying contents of the encrypted block device are arbitrary.
      • This makes it useful for encrypting swap devices.
      • This can also be useful with certain databases that use specially formatted block devices for data storage.
    • LUKS uses the existing device mapper kernel subsystem.
      • This is the same subsystem used by LVM, so it is well tested.
    • LUKS provides passphrase strengthening.
      • This protects against dictionary attacks.
    • LUKS devices contain multiple key slots.
      • This allows users to add backup keys/passphrases.
  • What LUKS does not do:
    • LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device.
    • LUKS is not well-suited for applications requiring file-level encryption.
More detailed information about LUKS is available from the project website at http://code.google.com/p/cryptsetup/.

C.2.2. How will I access the encrypted devices after installation? (System Startup)

During system startup you will be presented with a passphrase prompt. After the correct passphrase has been provided the system will continue to boot normally. If you used different passphrases for multiple encrypted devices you may need to enter more than one passphrase during the startup.

Tip

Consider using the same passphrase for all encrypted block devices in a given system. This will simplify system startup and you will have fewer passphrases to remember. Just make sure you choose a good passphrase!

C.2.3. Choosing a Good Passphrase

While dm-crypt/LUKS supports both keys and passphrases, the anaconda installer only supports the use of passphrases for creating and accessing encrypted block devices during installation.
LUKS does provide passphrase strengthening but it is still a good idea to choose a good (meaning "difficult to guess") passphrase. Note the use of the term "passphrase", as opposed to the term "password". This is intentional. Providing a phrase containing multiple words to increase the security of your data is important.

C.3. Creating Encrypted Block Devices in Anaconda

You can create encrypted devices during system installation. This allows you to easily configure a system with encrypted partitions.
To enable block device encryption, check the "Encrypt System" checkbox when selecting automatic partitioning or the "Encrypt" checkbox when creating an individual partition, software RAID array, or logical volume. After you finish partitioning, you will be prompted for an encryption passphrase. This passphrase will be required to access the encrypted devices. If you have pre-existing LUKS devices and provided correct passphrases for them earlier in the install process the passphrase entry dialog will also contain a checkbox. Checking this checkbox indicates that you would like the new passphrase to be added to an available slot in each of the pre-existing encrypted block devices.

Tip

Checking the "Encrypt System" checkbox on the "Automatic Partitioning" screen and then choosing "Create custom layout" does not cause any block devices to be encrypted automatically.

Tip

You can use kickstart to set a separate passphrase for each new encrypted block device.

C.3.1. What Kinds of Block Devices Can Be Encrypted?

Most types of block devices can be encrypted using LUKS. From anaconda you can encrypt partitions, LVM physical volumes, LVM logical volumes, and software RAID arrays.

C.3.2. Saving Passphrases

If you use a kickstart file during installation, you can automatically save the passphrases used during installation to an encrypted file (an escrow packet) on the local file system. To use this feature, you must have an X.509 certificate available at a location that anaconda can access. To specify the URL of this certificate, add the --escrowcert parameter to any of the autopart, logvol, part or raid commands. During installation, the encryption keys for the specified devices are saved in files in /root, encrypted with the certificate.
You can save escrow packets during installation only with the use of a kickstart file — refer to Глава 15, Kickstart Installations for more detail. You cannot save an escrow packet during an interactive installation, although you can create one on an installed system with the volume_key tool. The volume_key tool also allows you to use the information stored in an escrow packet to restore access to an encrypted volume. Refer to the volume_key manpage for more information.

C.3.3. Creating and Saving Backup Passphrases

If you use a kickstart file during installation, anaconda can add a randomly generated backup passphrase to each block device on the system and save each passphrase to an encrypted file on the local file system. Specify the URL of this certificate with the --escrowcert parameter as described in Раздел C.3.2, «Saving Passphrases», followed by the --backuppassphrase parameter for each of the kickstart commands that relate to the devices for which you want to create backup passphrases.
Note that this feature is available only while performing a kickstart installation. Refer to Глава 15, Kickstart Installations for more detail.

C.4. Creating Encrypted Block Devices on the Installed System After Installation

Encrypted block devices can be created and configured after installation, using either the following method or Disk Utility.

C.4.1. Create the block devices

Create the block devices you want to encrypt by using parted, pvcreate, lvcreate and mdadm.

C.4.2. Optional: Fill the device with random data

Filling <device> (eg: /dev/sda3) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time.

Warning

The commands below will destroy any existing data on the device.
  • The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems):
    dd if=/dev/urandom of=<device>
  • Fastest way, which provides lower quality random data:
    badblocks -c 10240 -s -w -t random -v <device>

C.4.3. Format the device as a dm-crypt/LUKS encrypted device

Warning

The command below will destroy any existing data on the device.
cryptsetup luksFormat <device>

Примечание

For more information, read the cryptsetup(8) man page.
After supplying the passphrase twice the device will be formatted for use. To verify, use the following command:
cryptsetup isLuks <device> && echo Success
To see a summary of the encryption information for the device, use the following command:
cryptsetup luksDump <device>

C.4.4. Create a mapping to allow access to the device's decrypted contents

To access the device's decrypted contents, a mapping must be established using the kernel device-mapper.
It is useful to choose a meaningful name for this mapping. LUKS provides a UUID (Universally Unique Identifier) for each device. This, unlike the device name (eg: /dev/sda3), is guaranteed to remain constant as long as the LUKS header remains intact. To find a LUKS device's UUID, run the following command:
cryptsetup luksUUID <device>
An example of a reliable, informative and unique mapping name would be luks-<uuid>, where <uuid> is replaced with the device's LUKS UUID (eg: luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8). This naming convention might seem unwieldy but is it not necessary to type it often.
cryptsetup luksOpen <device> <name>
There should now be a device node, /dev/mapper/<name>, 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

Use the mapped device node (/dev/mapper/<name>) 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:

Важно

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

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

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/<name> 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-<luks_uuid> 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

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

These sections are about generating keys and adding keys.

C.5.1.1. Gen