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

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. Соглашения по выделению текста

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

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

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

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

2.1. Цели

1. Понять как определить местонахождение дистрибутива Fedora онлайн

2. Создать конфигурацию данных, позволяющую загрузить Fedora

3. Понять как взаимодействовать с установщиком Fedora

4. Выполнить стандарную настройку Fedora после установки

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

2.2. Аудитория

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

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

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

Таблица 2.1. Типы процессоров и архитектур

Если вы не знаете модель процессора, выберите i386.

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. Какие файлы нужно загрузить?

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 → ). 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. Расположение файлов

4.1. Upgrade or Install?

4.2. Is Your Hardware Compatible?

4.3. RAID and Other Disk Devices

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.

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

Несколько жестких дисков в системах Fedora можно объединить в один 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 ».

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

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

• have enough unpartitioned^[1] disk space for the installation of Fedora, or

• убедиться в том, что в системе есть один или несколько разделов, которые можно удалить и, таким образом, освободить дисковое пространство для установки Fedora.

4.5. Selecting an Installation Method

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 on the 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 on the 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 option on the 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 option on the 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

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.

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.

Extract the files from the ISO image of the installation DVD and place them in a directory that is shared over FTP or HTTP.

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

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.

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.

You cannot use ISO files on partitions controlled by LVM (Logical Volume Management).

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

7.1. Starting the Installation Program

Fedora 17 does not support UEFI booting for 32-bit x86 systems. Only BIOS booting is supported.

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/

You can boot the installation program using any one of the following media (depending upon what your system can support):

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.

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

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.

linux updates

linux text updates

7.2. Booting from the Network using PXE

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.

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.1. Installation Method

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.

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.

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.

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:

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

After entering the linux repo= boot command, proceed with Глава 9, Installing using anaconda.

linux repo=nfs:options:server:/path

linux repo=nfsiso:options:server:/path

After entering the linux repo= command, proceed with Глава 9, Installing using anaconda.

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.1. The Text Mode Installation Program User Interface

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

Installing in text mode does not prevent you from using a graphical interface on your system once it is installed.

• 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

• нестандартные схемы хранения данных (LVM, RAID, FCoE, zFCP, iSCSI);

• изменение стандартной схемы разделов;

• изменение конфигурации загрузчика;

• выбор пакетов в процессе установки;

• configuring the installed system with firstboot

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.

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.

9.2. The Graphical Installation Program User Interface

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.

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.3. Language Selection

Рисунок 9.1. Language Configuration

9.4. The Pre-Installation Hub

Рисунок 9.2. The pre-installation hub

9.5. Configuring date and time

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

Рисунок 9.3. Configuring the Time Zone

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

Рисунок 9.4. Keyboard Configuration

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

Рисунок 9.5. Language Configuration

9.8. Installation Source

Рисунок 9.6. Installation source

9.9. Network configuration

Рисунок 9.7. Network 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).

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.10. Software Selection

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

Рисунок 9.14. Software Selection

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.

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:

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.

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.

Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface.

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.

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.

Все установки Fedora включают следующие сетевые службы:

The default installation also provides:

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

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

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

Рисунок 9.18. Устройства хранения

Basic Storage Devices

Select to install Fedora on the following storage devices:

• на напрямую подключенные жесткие диски и твердотельные накопители.

Specialized Storage Devices

Select to install Fedora on the following storage devices:

• в сети хранения данных (SAN, Storage Area Networks);

• Direct access storage devices (DASDs)

• на микропрограммные RAID-устройства;

• на многопутевые устройства.

Use the option to configure Internet Small Computer System Interface (iSCSI) and FCoE (Fiber Channel over Ethernet) connections.

В этом окне показаны все доступные программе anaconda устройства хранения.

Устройства сгруппированы следующим образом:

Если настройка устройств 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) и соответствующие текстовые поля.

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

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.

Выбрав устройства, нажмите кнопку продолжения. Раздел 9.13, «Initializing the Hard Disk» содержит дальнейшую информацию.

9.12. Assign Storage Devices

Рисунок 9.38. Выбор устройств хранения

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

9.13. Initializing the Hard Disk

Рисунок 9.39. Warning screen – initializing hard drive

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

Fedora предоставляет утилиту командной строки preupgrade, позволяющую выполнить обновление существующей установки Fedora до новой версии.

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.

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.

Раздел 18.2, «Finishing an Upgrade» содержит дополнительную информацию о завершении процесса обновления.

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.

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

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.

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.

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.

Рисунок 9.42. Disk Partitioning Setup

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

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.

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, «Достаточно ли дискового пространства?».

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 »

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.

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

Рисунок 9.43. Enter passphrase for encrypted partition

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

Рисунок 9.44. Partitioning on x86, AMD64, and Intel 64 Systems

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.

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

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.

Options are grouped under Create Partition, Create Software RAID and Create LVM as follows:

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

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.

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.

9.18. Write changes to disk

Рисунок 9.52. Writing storage configuration to disk

До этого момента в процессе установки программа установки не сохраняла изменения на вашем компьютере. При нажатии кнопки Сохранить изменения на диск программа установки выделит место на жестком диске и начнет установку 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

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

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. Настройка загрузчика

If you install GRUB, it may overwrite your existing boot loader.

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!

Добавить

Выберите Добавить для добавления другой операционной системы в 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.

Если ваша система находится в безопасном окружении, то есть доступ к ней открыт только авторизованному персоналу, то пароль GRUB можно не задавать. Если же существует вероятность физического доступа к клавиатуре и монитору неавторизованными пользователями, они смогут перезагрузить систему и войти в GRUB. В таких случаях следует задать пароль.

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.

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:

Если вы будете использовать только 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.

http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html

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

For additional information, refer to the Fedora Deployment Guide.

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.

9.20. The Progress Hub

Рисунок 9.55. Packages completed

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

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.

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.

Чтобы изменить пароль 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

10.1. Невозможно загрузить Fedora

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.

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

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 содержит дальнейшую информацию о параметрах загрузки.

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

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

Если anaconda столкнулась с проблемами после начала графической установки, появится информационное окно:

Если после этапа настройки разбиения диска (см. Раздел 9.15, «Disk Partitioning Setup») вы получаете сообщение, подобное следующему:

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

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.

Вне зависимости от выбранного типа установки следует создавать резервную копию данных вашего компьютера.

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.

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:

10.4. Problems After Installation

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.

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.

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.

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.

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» содержит дальнейшую информацию об установке окружения рабочего стола.

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.

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.

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.

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

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.

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

11.1. Configuring the Installation System at the Boot Menu

• язык

• display resolution

• interface type

• Installation method

• network settings

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

Для использования конкретного разрешения экрана введите resolution=значение в качестве параметра загрузки. Например, для разрешения 1024×768 введите:

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.

Для установки 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.

Чтобы задать метод установки в приглашении boot:, используйте параметр repo (см. Таблица 11.1, «Installation methods»).

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:

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

Fedora includes the VNC client vncviewer. To obtain vncviewer, install the tigervnc package.

Чтобы включить удаленный графический доступ к системе установки, в строке приглашения введите два параметра:

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.

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 выберите → → или выполните команду vncviewer в окне терминала. В открывшемся окне введите имя сервера и номер экрана. В приведенном выше примере в качестве VNC-сервера будет выступать узел computer.mydomain.com:1.

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

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

 vncviewer -listen

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

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

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

Чтобы настроить в 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.

11.4. Automating the Installation with Kickstart

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.

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.

Таблица 11.2. Kickstart sources

11.5. Enhancing Hardware Support

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.

To override the automatic hardware detection, use one or more of the following options:

11.6. Using the Maintenance Boot Modes

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

Fedora предоставляет специальное приложение для тестирования памяти — Memtest86+. Чтобы загрузить компьютер в

режим тестирования памяти, выберите в меню загрузки. Первый тест сразу же запустится. Memtest86+ по умолчанию выполняет 10 проверок.

В большинстве случаев одной успешной проверки Memtest86+ достаточно. Но в редких случаях ошибки, которые остались незамеченными при первом проходе, могут появиться на последующих проходах. Чтобы выполнить тщательный тест ОЗУ, оставьте Memtest86+ работать на всю ночь или даже на протяжении нескольких дней.

Чтобы остановить проверку и перезагрузить компьютер, просто нажмите Esc.

Можно загрузить Linux в режиме командной строки как с

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

The rescue disc starts the rescue mode system by default. To load the rescue system with the installation disc, choose 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/.

Существовавший раньше параметр загрузки 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.

13.1. Setting Up cobbler

13.2. Setting Up the Distribution

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

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=дистрибутив

   При импортировании таким образом дистрибутива 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.

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

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.

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.

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.

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.

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

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.1. VNC Viewer

• Your workstation

• Laptop on a datacenter crash cart

• 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

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

14.2. VNC Modes in Anaconda

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:

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:

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.

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

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:

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.

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.

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.

15.1. What are Kickstart Installations?

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?

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.

15.3. Creating the Kickstart File

• Sections must be specified in order. Items within the sections do not have to be in a specific order unless otherwise specified. The section order is:

  • Command section — Refer to Раздел 15.4, «Kickstart Options» for a list of kickstart options. You must include the required options.

  • The %packages section — Refer to Раздел 15.5, «Package Selection» for details.

  • The %pre and %post sections — These two sections can be in any order and are not required. Refer to Раздел 15.6, «Pre-installation Script» and Раздел 15.7, «Post-installation Script» for details.

• Items that are not required can be omitted.

• Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item).

• Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.

• For kickstart upgrades, the following items are required:

  • Language

  • Installation method

  • Device specification (if device is needed to perform the installation)

  • Keyboard setup

  • The upgrade keyword

  • Boot loader configuration

  If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).

15.4. Kickstart Options

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.

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

  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

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.

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.

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

  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.

  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

  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.

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.

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.

  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.

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.

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.

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.