Branch 'f11-tx' - po/ca.po

Transifex System User transif at fedoraproject.org
Tue Jun 16 19:26:26 UTC 2009


 po/ca.po |29491 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 29491 insertions(+)

New commits:
commit 67cb6eeddb8f3081a3e9d670ae0ea19c3622dc00
Author: xconde <xconde at fedoraproject.org>
Date:   Tue Jun 16 19:26:21 2009 +0000

    Sending translation for po/ca.po

diff --git a/po/ca.po b/po/ca.po
new file mode 100644
index 0000000..fe8544f
--- /dev/null
+++ b/po/ca.po
@@ -0,0 +1,29491 @@
+# Catalan translation for docs-install-guide
+# Copyright © 2009 The Free Software Foundation, Inc.
+# This file is distributed under the same license as the docs-install-guide
+# package.
+# This file is translated according to the glossary and style guide of
+# Softcatalà. If you plan to modify this file, please read first the page
+# of the Catalan translation team for the Fedora project at:
+# http://www.softcatala.org/projectes/fedora/
+# and contact the previous translator
+# Aquest fitxer s'ha de traduir d'acord amb el recull de termes i la guia
+# d'estil de Softcatalà. Si voleu modificar aquest fitxer, llegiu si
+# us plau la pàgina de catalanització del projecte Fedora a:
+# http://www.softcatala.org/projectes/fedora/
+# i contacteu l'anterior traductor/a.
+# Xavier Conde Rueda <xavi.conde at gmail.com>, 2009.
+
+# 
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-04-30 03:52+0000\n"
+"PO-Revision-Date: 2009-06-14 03:56+0200\n"
+"Last-Translator: Xavier Conde Rueda <xavi.conde at gmail.com>\n"
+"Language-Team: Catalan <fedora at sofcatala.net>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-xml2pot; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: para
+#: Account_Configuration_common-para-6.xml:8
+#, no-c-format
+msgid ""
+"Enter the <systemitem class=\"username\">root</systemitem> password into the "
+"<guilabel>Root Password</guilabel> field. Fedora displays the characters as "
+"asterisks for security. Type the same password into the <guilabel>Confirm</"
+"guilabel> field to ensure it is set correctly. After you set the root "
+"password, select <guibutton>Next</guibutton> to proceed."
+msgstr ""
+
+#. Tag: primary
+#: Account_Configuration-common.xml:12
+#, no-c-format
+msgid "password"
+msgstr "contrasenya"
+
+#. Tag: secondary
+#: Account_Configuration-common.xml:13
+#, no-c-format
+msgid "setting root"
+msgstr "establir el root"
+
+#. Tag: para
+#: Account_Configuration-common.xml:15
+#, no-c-format
+msgid ""
+"Setting up a root account and password is one of the most important steps "
+"during your installation. Your root account is similar to the administrator "
+"account used on Microsoft Windows machines. The root account is used to "
+"install packages, upgrade RPMs, and perform most system maintenance. Logging "
+"in as root gives you complete control over your system."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:22
+#, no-c-format
+msgid ""
+"The root user (also known as the superuser) has complete access to the "
+"entire system; for this reason, logging in as the root user is best done "
+"<emphasis>only</emphasis> to perform system maintenance or administration."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:29
+#, no-c-format
+msgid "Setting your root password."
+msgstr "Establir la contrasenya del root."
+
+#. Tag: para
+#: Account_Configuration-common.xml:35
+#, no-c-format
+msgid ""
+"Use the root account only for system administration. Create a non-root "
+"account for your general use and <command>su -</command> to root when you "
+"need to fix something quickly. These basic rules minimize the chances of a "
+"typo or an incorrect command doing damage to your system."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:40
+#, no-c-format
+msgid ""
+"To become root, type <command>su -</command> at the shell prompt in a "
+"terminal window and then press <keycap>Enter</keycap>. Then, enter the root "
+"password and press <keycap>Enter</keycap>."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:44
+#, no-c-format
+msgid ""
+"The installation program prompts you to set a root password<footnote> <para> "
+"A root password is the administrative password for your Fedora system. You "
+"should only log in as root when needed for system maintenance. The root "
+"account does not operate within the restrictions placed on normal user "
+"accounts, so changes made as root can have implications for your entire "
+"system. </para> </footnote> for your system. <emphasis>You cannot proceed to "
+"the next stage of the installation process without entering a root password."
+"</emphasis>"
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:53
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:57
+#, no-c-format
+msgid ""
+"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, <firstterm>qwerty</firstterm>, <firstterm>password, root</"
+"firstterm>, <firstterm>123456</firstterm>, and <firstterm>anteater</"
+"firstterm> are all examples of bad passwords. Good passwords mix numerals "
+"with upper and lower case letters and do not contain dictionary words: "
+"<firstterm>Aard387vark</firstterm> or <firstterm>420BMttNT</firstterm>, 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."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:66
+#, no-c-format
+msgid ""
+"Do not use one of the example passwords offered in this manual. Using one of "
+"these passwords could be considered a security risk."
+msgstr ""
+"No feu servir les contrasenyes d'exemple que es donen en aquest manual. Fer-ho "
+"és considerat un risc de seguretat."
+
+#. Tag: para
+#: Account_Configuration-common.xml:71
+#, no-c-format
+msgid ""
+"To change your root password after you have completed the installation, use "
+"the <application>Root Password Tool</application>."
+msgstr ""
+
+#. Tag: para
+#: Account_Configuration-common.xml:74
+#, no-c-format
+msgid ""
+"Type the <command>system-config-rootpassword</command> command in a shell "
+"prompt to launch the <application>Root Password Tool</application>. If you "
+"are not root, it prompts you for the root password to continue."
+msgstr ""
+
+#. Tag: title
+#: Account_Configuration_common-title.xml:5
+#, no-c-format
+msgid "Set the Root Password"
+msgstr ""
+
+#. Tag: application
+#: Adding_Partitions_common-indexterm-1.xml:9
+#, no-c-format
+msgid "Disk Partitioner"
+msgstr ""
+
+#. Tag: title
+#: Adding_Partitions_common-title-1.xml:8
+#, no-c-format
+msgid "Adding Partitions"
+msgstr ""
+
+#. Tag: primary
+#: Adding_Partitions-section-2-indexterm-1.xml:9
+#, no-c-format
+msgid "file system types"
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>Btrfs</guilabel> — Btrfs is under development as a file "
+"system capable of addressing and managing more files, larger files, and "
+"larger volumes than the ext2, ext3, and ext4 file systems. Btrfs is designed "
+"to make the file system tolerant of errors, and to facilitate the detection "
+"and repair of errors when they occur. It uses checksums to ensure the "
+"validity of data and metadata, and maintains snapshots of the file system "
+"that can be used for backup or repair."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml:9
+#, no-c-format
+msgid ""
+"Because Btrfs is still experimental and under development, the installation "
+"program does not offer it by default. If you want to create a Btrfs "
+"partition on a drive, you must commence the installation process with the "
+"boot option <command> icantbelieveitsnotbtr</command>. Refer to <xref "
+"linkend=\"ap-admin-options\"/> for instructions."
+msgstr ""
+
+#. Tag: title
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml:13
+#, no-c-format
+msgid "Btrfs is still experimental"
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml:14
+#, no-c-format
+msgid ""
+"Fedora &PRODVER; includes Btrfs as a technology preview to allow you to "
+"experiment with this file system. You should not choose Btrfs for partitions "
+"that will contain valuable data or that are essential for the operation of "
+"important systems."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml:8
+#, no-c-format
+msgid ""
+"<guilabel>ext2</guilabel> — An ext2 file system supports standard Unix "
+"file types (regular files, directories, symbolic links, etc). It provides "
+"the ability to assign long file names, up to 255 characters."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>ext4</guilabel> — The ext4 file system is based on the ext3 "
+"file system and features a number of improvements. These include support for "
+"larger file systems and larger files, faster and more efficient allocation "
+"of disk space, no limit on the number of subdirectories within a directory, "
+"faster file system checking, and more robust journalling. The ext4 file "
+"system is selected by default and is highly recommended."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>ext3</guilabel> — The ext3 file system is based on the ext2 "
+"file system and has one main advantage — journaling. Using a "
+"journaling file system reduces time spent recovering a file system after a "
+"crash as there is no need to <command>fsck</command> <footnote> <para> The "
+"<command>fsck</command> application is used to check the file system for "
+"metadata consistency and optionally repair one or more Linux file systems. </"
+"para> </footnote> the file system."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>physical volume (LVM)</guilabel> — Creating one or more "
+"physical volume (LVM) partitions allows you to create an LVM logical volume. "
+"LVM can improve performance when using physical disks."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>software RAID</guilabel> — Creating two or more software "
+"RAID partitions allows you to create a RAID device."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>swap</guilabel> — Swap partitions are used to support "
+"virtual memory. In other words, data is written to a swap partition when "
+"there is not enough RAM to store the data your system is processing."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml:9
+#, no-c-format
+msgid ""
+"<guilabel>vfat</guilabel> — The VFAT file system is a Linux file "
+"system that is compatible with Microsoft Windows long filenames on the FAT "
+"file system. This file system must be used for the <filename>/boot/efi/</"
+"filename> partition on Itanium systems."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-section-2-para-1.xml:5
+#, no-c-format
+msgid ""
+"Fedora allows you to create different partition types, based on the file "
+"system they will use. The following is a brief description of the different "
+"file systems available, and how they can be utilized."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-x86.xml:15
+#, no-c-format
+msgid ""
+"To add a new partition, select the <guibutton>New</guibutton> button. A "
+"dialog box appears (refer to <xref linkend=\"fig-diskpartitioning-part-add-"
+"x86\"/>)."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-x86.xml:22
+#, no-c-format
+msgid ""
+"You must dedicate at least one partition for this installation, and "
+"optionally more. For more information, refer to <xref linkend=\"ch-"
+"partitions-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Adding_Partitions-x86.xml:27
+#, no-c-format
+msgid "Creating a New Partition"
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-x86.xml:30
+#, no-c-format
+msgid "Creating a new partition."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-x86.xml:42
+#, no-c-format
+msgid ""
+"<guilabel>File System Type</guilabel>: Using the pull-down menu, select the "
+"appropriate file system type for this partition. For more information on "
+"file system types, refer to <xref linkend=\"s3-diskpartitioning-file-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions-x86.xml:57
+#, no-c-format
+msgid ""
+"<guilabel>Force to be a primary partition</guilabel>: Select whether the "
+"partition you are creating should be one of the first four partitions on the "
+"hard drive. If unselected, the partition is created as a logical partition. "
+"Refer to <xref linkend=\"s2-partitions-overview-extended-x86\"/>, for more "
+"information."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-1.xml:9
+#, no-c-format
+msgid ""
+"<guilabel>Mount Point</guilabel>: Enter the partition's mount point. For "
+"example, if this partition should be the root partition, enter <userinput>/</"
+"userinput>; enter <userinput>/boot</userinput> for the <filename>/boot</"
+"filename> partition, and so on. You can also use the pull-down menu to "
+"choose the correct mount point for your partition. For a swap partition the "
+"mount point should not be set - setting the filesystem type to swap is "
+"sufficient."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-2.xml:6
+#, no-c-format
+msgid ""
+"<guilabel>Allowable Drives</guilabel>: This field contains a list of the "
+"hard disks installed on your system. If a hard disk's box is highlighted, "
+"then a desired partition can be created on that hard disk. If the box is "
+"<emphasis>not</emphasis> checked, then the partition will <emphasis>never</"
+"emphasis> be created on that hard disk. By using different checkbox "
+"settings, you can have <application>anaconda</application> place partitions "
+"where you need them, or let <application>anaconda</application> decide where "
+"partitions should go."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-3.xml:9
+#, no-c-format
+msgid ""
+"<guilabel>Size (MB)</guilabel>: Enter the size (in megabytes) of the "
+"partition. Note, this field starts with 100 MB; unless changed, only a 100 "
+"MB partition will be created."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-4.xml:9
+#, no-c-format
+msgid ""
+"<guilabel>Additional Size Options</guilabel>: Choose whether to keep this "
+"partition at a fixed size, to allow it to \"grow\" (fill up the available "
+"hard drive space) to a certain point, or to allow it to grow to fill any "
+"remaining hard drive space available."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-4.xml:14
+#, no-c-format
+msgid ""
+"If you choose <guilabel>Fill all space up to (MB)</guilabel>, you must give "
+"size constraints in the field to the right of this option. This allows you "
+"to keep a certain amount of space free on your hard drive for future use."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-5.xml:9
+#, no-c-format
+msgid ""
+"<guibutton>OK</guibutton>: Select <guibutton>OK</guibutton> once you are "
+"satisfied with the settings and wish to create the partition."
+msgstr ""
+
+#. Tag: para
+#: Adding_Partitions_x86_ppc-listitem-6.xml:9
+#, no-c-format
+msgid ""
+"<guibutton>Cancel</guibutton>: Select <guibutton>Cancel</guibutton> if you "
+"do not want to create the partition."
+msgstr ""
+
+#. Tag: title
+#: Adding_Partitions_x86_ppc-title-2.xml:8
+#, no-c-format
+msgid "File System Types"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:8
+#, no-c-format
+msgid "Boot Options"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:9
+#, no-c-format
+msgid ""
+"The Fedora installation system includes a range of functions and options for "
+"administrators. To use boot options, enter <userinput>linux "
+"<replaceable>option</replaceable></userinput> at the <prompt>boot:</prompt> "
+"prompt."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:17
+#, no-c-format
+msgid ""
+"If you specify more than one option, separate each of the options by a "
+"single space. For example:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:21
+#, no-c-format
+msgid ""
+"<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</"
+"replaceable> <replaceable>option3</replaceable></userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:23
+#, no-c-format
+msgid "Anaconda Boot Options"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:25
+#, no-c-format
+msgid ""
+"The anaconda installer has many boot options, most are listed on the wiki "
+"<ulink url=\"http://fedoraproject.org/wiki/Anaconda/Options\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:31
+#, no-c-format
+msgid "Kernel Boot Options"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:33
+#, no-c-format
+msgid ""
+"The <ulink url=\"http://fedoraproject.org/wiki/KernelCommonProblems\"></"
+"ulink> page lists many common kernel boot options. The full list of kernel "
+"options is in the file /usr/share/doc/kernel-doc-<replaceable>version</"
+"replaceable>/Documentation/kernel-parameters.txt, which is installed with "
+"the kernel-doc package."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:43
+#, no-c-format
+msgid ""
+"The Fedora installation and <firstterm>rescue discs</firstterm> may either "
+"boot with <firstterm>rescue mode</firstterm>, or load the installation "
+"system. For more information on rescue discs and rescue mode, refer to <xref "
+"linkend=\"sn-mode-rescue\"/>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:51
+#, no-c-format
+msgid "Configuring the Installation System at the Boot Menu"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:53
+#, no-c-format
+msgid ""
+"You can use the boot menu to specify a number of settings for the "
+"installation system, including:"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:65
+#, no-c-format
+msgid "display resolution"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:70
+#, no-c-format
+msgid "interface type"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:75
+#, no-c-format
+msgid "<para>Installation method</para>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:80
+#, no-c-format
+msgid "network settings"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:87
+#, no-c-format
+msgid "Specifying the Language"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:89
+#, no-c-format
+msgid ""
+"To set the language for both the installation process and the final system, "
+"specify the ISO code for that language with the <option>lang</option> "
+"option. Use the <option>keymap</option> option to configure the correct "
+"keyboard layout."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:96
+#, no-c-format
+msgid ""
+"For example, the ISO codes <userinput>el_GR</userinput> and <userinput>gr</"
+"userinput> identify the Greek language and the Greek keyboard layout:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:101
+#, no-c-format
+msgid ""
+"<userinput>linux lang=<replaceable>el_GR</replaceable> "
+"keymap=<replaceable>gr</replaceable></userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:105
+#, no-c-format
+msgid "Configuring the Interface"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:107
+#, no-c-format
+msgid ""
+"You may force the installation system to use the lowest possible screen "
+"resolution (640x480) with the <option>lowres</option> option. To use a "
+"specific display resolution, enter <option>resolution=<replaceable>setting</"
+"replaceable></option> as a boot option. For example, to set the display "
+"resolution to 1024x768, enter:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:115
+#, no-c-format
+msgid ""
+"<userinput>linux resolution=<replaceable>1024x768</replaceable></userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:116
+#, no-c-format
+msgid ""
+"To run the installation process in <indexterm> <primary>text interface</"
+"primary> </indexterm> <option>text</option> mode, enter:"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:124
+#, no-c-format
+msgid ""
+"To enable support for a <indexterm> <primary>serial console</primary> </"
+"indexterm> serial console, enter <option>serial</option> as an additional "
+"option."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:133
+#, no-c-format
+msgid ""
+"Use <option>display=<replaceable>ip</replaceable>:0</option> to allow remote "
+"display forwarding. In this command, <replaceable>ip</replaceable> should be "
+"replaced with the IP address of the system on which you want the display to "
+"appear."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:137
+#, no-c-format
+msgid ""
+"On the system you want the display to appear on, you must execute the "
+"command <command>xhost +<replaceable>remotehostname</replaceable></command>, "
+"where <replaceable>remotehostname</replaceable> is the name of the host from "
+"which you are running the original display. Using the command <command>xhost "
+"+<replaceable>remotehostname</replaceable></command> limits access to the "
+"remote display terminal and does not allow access from anyone or any system "
+"not specifically authorized for remote access."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:144
+#, no-c-format
+msgid "Updating anaconda"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:145
+#, no-c-format
+msgid ""
+"You can install Fedora with a newer version of the <application>anaconda</"
+"application> installation program than the one supplied on your installation "
+"media."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:148
+#, no-c-format
+msgid "The boot option"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:152
+#, no-c-format
+msgid ""
+"presents you with a prompt that asks you for a floppy disk containing "
+"<application>anaconda</application> updates. You do not need to specify this "
+"option if you are performing a network installation and have already placed "
+"the updates image contents in <filename>rhupdates/</filename> on the server."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:155
+#, no-c-format
+msgid ""
+"To load the <application>anaconda</application> updates from a network "
+"location instead, use:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:158
+#, no-c-format
+msgid "<userinput>linux updates=</userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:159
+#, no-c-format
+msgid "followed by the URL for the location where the updates are stored."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:165
+#, no-c-format
+msgid "Specifying the Installation Method"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:167
+#, no-c-format
+msgid ""
+"Use the <option>askmethod</option> option to display additional menus that "
+"enable you to specify the installation method and network settings. You may "
+"also configure the installation method and network settings at the "
+"<prompt>boot:</prompt> prompt itself."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:176
+#, no-c-format
+msgid ""
+"To specify the installation method from the <prompt>boot:</prompt> prompt, "
+"use the <option>method</option> option. Refer to <xref linkend=\"tb-"
+"installmethods\"/> for the supported installation methods."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:183
+#, no-c-format
+msgid "Installation methods"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:189
+#, no-c-format
+msgid "<entry>Installation method</entry>"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:190 adminoptions.xml:578 adminoptions.xml:706
+#, no-c-format
+msgid "Option format"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:195 adminoptions.xml:583
+#, no-c-format
+msgid "CD or DVD drive"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:196
+#, no-c-format
+msgid "method=<replaceable>cdrom</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:200
+#, no-c-format
+msgid "method=<replaceable>hd://device/</replaceable>"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:203 adminoptions.xml:595 adminoptions.xml:715
+#, no-c-format
+msgid "HTTP Server"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:204
+#, no-c-format
+msgid "method=<replaceable>http://server.mydomain.com/directory/</replaceable>"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:207 adminoptions.xml:599 adminoptions.xml:719
+#, no-c-format
+msgid "FTP Server"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:208
+#, no-c-format
+msgid "method=<replaceable>ftp://server.mydomain.com/directory/</replaceable>"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:211 adminoptions.xml:603 adminoptions.xml:723
+#, no-c-format
+msgid "NFS Server"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:212
+#, no-c-format
+msgid "method=<replaceable>nfs:server.mydomain.com:/directory/</replaceable>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:219
+#, no-c-format
+msgid "Manually Configuring the Network Settings"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:220
+#, no-c-format
+msgid ""
+"By default, the installation system uses DHCP to automatically obtain the "
+"correct network settings. To manually configure the network settings "
+"yourself, either enter them in the <guilabel>Configure TCP/IP</guilabel> "
+"screen, or at the <prompt>boot:</prompt> prompt. You may specify the "
+"<option>ip</option> address, <option>netmask</option>, <option>gateway</"
+"option>, and <option>dns</option> server settings for the installation "
+"system at the prompt. If you specify the network configuration at the "
+"<prompt>boot:</prompt> prompt, these settings are used for the installation "
+"process, and the <guilabel>Configure TCP/IP</guilabel> screen does not "
+"appear."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:236
+#, no-c-format
+msgid ""
+"This example configures the network settings for an installation system that "
+"uses the IP address <systemitem class=\"ipaddress\">192.168.1.10</"
+"systemitem>:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:241
+#, no-c-format
+msgid ""
+"<userinput>linux ip=<replaceable>192.168.1.10</replaceable> "
+"netmask=<replaceable>255.255.255.0</replaceable> "
+"gateway=<replaceable>192.168.1.1</replaceable> "
+"dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:243
+#, no-c-format
+msgid "Configuring the Installed System"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:245
+#, no-c-format
+msgid ""
+"Use the Network Configuration screen to specify the network settings for the "
+"new system. Refer to <xref linkend=\"sn-networkconfig-fedora_manual-"
+"configuration\"/> for more information on configuring the network settings "
+"for the installed system."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:255
+#, no-c-format
+msgid "Enabling Remote Access to the Installation System"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:257
+#, no-c-format
+msgid ""
+"You may access either graphical or text interfaces for the installation "
+"system from any other system. Access to a text mode display requires "
+"<application>telnet</application>, which is installed by default on Fedora "
+"systems. To remotely access the graphical display of an installation system, "
+"use client software that supports the <indexterm> <primary>VNC (Virtual "
+"Network Computing)</primary> </indexterm> VNC (Virtual Network Computing) "
+"display protocol. A number of providers offer VNC clients for Microsoft "
+"Windows and Mac OS, as well as UNIX-based systems."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:270
+#, no-c-format
+msgid "Installing a VNC Client on Fedora"
+msgstr ""
+
+#. Tag: primary
+#: adminoptions.xml:273 adminoptions.xml:296
+#, no-c-format
+msgid "VNC (Virtual Network Computing)"
+msgstr ""
+
+#. Tag: secondary
+#: adminoptions.xml:274
+#, no-c-format
+msgid "installing client"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:275
+#, no-c-format
+msgid ""
+"Fedora includes <application>vncviewer</application>, the client provided by "
+"the developers of VNC. To obtain <application>vncviewer</application>, "
+"install the <filename>vnc</filename> package."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:282
+#, no-c-format
+msgid ""
+"The installation system supports two methods of establishing a VNC "
+"connection. You may start the installation, and manually login to the "
+"graphical display with a VNC client on another system. Alternatively, you "
+"may configure the installation system to automatically connect to a VNC "
+"client on the network that is running in <firstterm>listening mode</"
+"firstterm>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:292
+#, no-c-format
+msgid "Enabling Remote Access with VNC"
+msgstr ""
+
+#. Tag: secondary
+#: adminoptions.xml:297
+#, no-c-format
+msgid "enabling"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:298
+#, no-c-format
+msgid ""
+"To enable remote graphical access to the installation system, enter two "
+"options at the prompt:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:302
+#, no-c-format
+msgid ""
+"<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></"
+"userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:303
+#, no-c-format
+msgid ""
+"The <option>vnc</option> option enables the VNC service. The "
+"<option>vncpassword</option> option sets a password for remote access. The "
+"example shown above sets the password as <userinput>qwerty</userinput>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:311
+#, no-c-format
+msgid "VNC Passwords"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:313
+#, no-c-format
+msgid "The VNC password must be at least six characters long."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:318
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:325
+#, no-c-format
+msgid ""
+"Starting VNC...\n"
+"The VNC server is now running.\n"
+"Please connect to computer.mydomain.com:1 to begin the install...\n"
+"Starting graphical installation...\n"
+"Press <enter> for a shell"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:326
+#, no-c-format
+msgid ""
+"You may then login to the installation system with a VNC client. To run the "
+"<application>vncviewer</application> client on Fedora, choose <menuchoice> "
+"<guimenu>Applications</guimenu> <guisubmenu>Accessories</"
+"guisubmenu><guimenuitem>VNC Viewer</guimenuitem></menuchoice>, or type the "
+"command <application>vncviewer</application> in a terminal window. Enter the "
+"server and display number in the <guilabel>VNC Server</guilabel> dialog. For "
+"the example above, the <guilabel>VNC Server</guilabel> is "
+"<userinput>computer.mydomain.com:1</userinput>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:341
+#, no-c-format
+msgid "Connecting the Installation System to a VNC Listener"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:343
+#, no-c-format
+msgid ""
+"To have the installation system automatically connect to a VNC client, first "
+"start the client in <indexterm> <primary>VNC (Virtual Network Computing)</"
+"primary> <secondary>listening mode</secondary> </indexterm> listening mode. "
+"On Fedora systems, use the <option>-listen</option> option to run "
+"<application>vncviewer</application> as a listener. In a terminal window, "
+"enter the command:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:355
+#, no-c-format
+msgid "<userinput>vncviewer -listen</userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:357 adminoptions.xml:501
+#, no-c-format
+msgid "Firewall Reconfiguration Required"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:359
+#, no-c-format
+msgid ""
+"By default, <application>vncviewer</application> uses TCP port 5500 when in "
+"listening mode. To permit connections to this port from other systems, "
+"choose <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</"
+"guisubmenu> <guimenuitem> Firewall</guimenuitem> </menuchoice>. Select "
+"<guilabel>Other ports</guilabel>, and <guibutton>Add</guibutton>. Enter "
+"<userinput>5500</userinput> in the <guilabel>Port(s)</guilabel> field, and "
+"specify <userinput>tcp</userinput> as the <guilabel>Protocol</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:374
+#, no-c-format
+msgid ""
+"Once the listening client is active, start the installation system and set "
+"the VNC options at the <prompt>boot:</prompt> prompt. In addition to "
+"<option>vnc</option> and <option>vncpassword</option> options, use the "
+"<option>vncconnect</option> 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."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:386
+#, no-c-format
+msgid ""
+"For example, to connect to a VNC client on the system <systemitem class="
+"\"systemname\">desktop.mydomain.com</systemitem> on the port 5500, enter the "
+"following at the <prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:394
+#, no-c-format
+msgid ""
+"<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> "
+"vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:398
+#, no-c-format
+msgid "Enabling Remote Access with Telnet"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:400
+#, no-c-format
+msgid ""
+"To enable remote access to a text mode installation, use the <indexterm> "
+"<primary>Telnet</primary> </indexterm> <option>telnet</option> option at the "
+"<prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:410
+#, no-c-format
+msgid "<userinput>linux text telnet</userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:411
+#, no-c-format
+msgid ""
+"You may then connect to the installation system with the <command>telnet</"
+"command> utility. The <command>telnet</command> command requires the name or "
+"IP address of the installation system:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:417
+#, no-c-format
+msgid "<userinput>telnet computer.mydomain.com</userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:419
+#, no-c-format
+msgid "Telnet Access Requires No Password"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:421
+#, no-c-format
+msgid ""
+"To ensure the security of the installation process, only use the "
+"<option>telnet</option> option to install systems on networks with "
+"restricted access."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:430
+#, no-c-format
+msgid "Logging to a Remote System During the Installation"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:432
+#, no-c-format
+msgid ""
+"By default, the installation process sends log messages to the console as "
+"they are generated. You may specify that these messages go to a remote "
+"system that runs a <indexterm> <primary>syslog</primary> </indexterm> "
+"<firstterm>syslog</firstterm> service."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:442
+#, no-c-format
+msgid ""
+"To configure remote logging, add the <option>syslog</option> option. Specify "
+"the IP address of the logging system, and the UDP port number of the log "
+"service on that system. By default, syslog services that accept remote "
+"messages listen on UDP port 514."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:449
+#, no-c-format
+msgid ""
+"For example, to connect to a syslog service on the system <systemitem class="
+"\"ipaddress\">192.168.1.20</systemitem>, enter the following at the "
+"<prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:457
+#, no-c-format
+msgid ""
+"<userinput>linux syslog=<replaceable>192.168.1.20:514</replaceable></"
+"userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:459
+#, no-c-format
+msgid "Configuring a Log Server"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:461
+#, no-c-format
+msgid ""
+"Fedora uses <command>rsyslog</command> to provide a syslog service. The "
+"default configuration of <command>rsyslog</command> rejects messages from "
+"remote systems."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:468
+#, no-c-format
+msgid "Only Enable Remote Syslog Access on Secured Networks"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:470
+#, no-c-format
+msgid ""
+"The <command>rsyslog</command> configuration detailed below does not make "
+"use of any of the security measures available in <command>rsyslog</command> "
+"Crackers may slow or crash systems that permit access to the logging "
+"service, by sending large quantities of false log messages. In addition, "
+"hostile users may intercept or falsify messages sent to the logging service "
+"over the network."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:481
+#, no-c-format
+msgid ""
+"To configure a Fedora system to accept log messages from other systems on "
+"the network, edit the file <filename>/etc/rsyslog.conf</filename>. You must "
+"use <systemitem class=\"username\">root</systemitem> privileges to edit the "
+"file <filename>/etc/rsyslog.conf</filename>. Uncomment the following lines "
+"by removing the hash preceding them:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:488
+#, no-c-format
+msgid ""
+"<computeroutput>$ModLoad imudp.so</computeroutput>\n"
+"        <computeroutput>$UDPServerRun 514</computeroutput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:490
+#, no-c-format
+msgid "Restart the <command>rsyslog</command> service to apply the change:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:494
+#, no-c-format
+msgid "<userinput>su -c '/sbin/service rsyslog restart'</userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:503
+#, no-c-format
+msgid ""
+"By default, the syslog service listens on UDP port 514. To permit "
+"connections to this port from other systems, choose <menuchoice> "
+"<guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> "
+"<guimenuitem> Firewall</guimenuitem> </menuchoice>. Select <guilabel>Other "
+"ports</guilabel>, and <guibutton>Add</guibutton>. Enter <userinput>514</"
+"userinput> in the <guilabel>Port(s)</guilabel> field, and specify "
+"<userinput>udp</userinput> as the <guilabel>Protocol</guilabel>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:519
+#, no-c-format
+msgid "Automating the Installation with Kickstart"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:521
+#, no-c-format
+msgid ""
+"A <indexterm> <primary>Kickstart</primary> </indexterm> "
+"<firstterm>Kickstart</firstterm> file specifies settings for an "
+"installation. Once the installation system boots, it can read a Kickstart "
+"file and carry out the installation process without any further input from a "
+"user."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:532
+#, no-c-format
+msgid "Every Installation Produces a Kickstart File"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:533
+#, no-c-format
+msgid ""
+"The Fedora installation process automatically writes a Kickstart file that "
+"contains the settings for the installed system. This file is always saved as "
+"<filename>/root/anaconda-ks.cfg</filename>. You may use this file to repeat "
+"the installation with identical settings, or modify copies to specify "
+"settings for other systems."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:542
+#, no-c-format
+msgid ""
+"Fedora includes a graphical application to create and modify Kickstart files "
+"by selecting the options that you require. Use the package <filename>system-"
+"config-kickstart</filename> to install this utility. To load the Fedora "
+"Kickstart editor, choose <menuchoice> <guimenu>Applications</guimenu> "
+"<guisubmenu>System Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></"
+"menuchoice>."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:551
+#, no-c-format
+msgid ""
+"Kickstart files list installation settings in plain text, with one option "
+"per line. This format lets you modify your Kickstart files with any text "
+"editor, and write scripts or applications that generate custom Kickstart "
+"files for your systems."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:558
+#, no-c-format
+msgid ""
+"To automate the installation process with a Kickstart file, use the "
+"<option>ks</option> option to specify the name and location of the file:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:563
+#, no-c-format
+msgid ""
+"<userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></"
+"userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:564
+#, no-c-format
+msgid ""
+"You may use Kickstart files that are held on either removable storage, a "
+"hard drive, or a network server. Refer to <xref linkend=\"tb-kssources\"/> "
+"for the supported Kickstart sources."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:571
+#, no-c-format
+msgid "Kickstart sources"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:577
+#, no-c-format
+msgid "Kickstart source"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:584
+#, no-c-format
+msgid "ks=<replaceable>cdrom:/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:588
+#, no-c-format
+msgid "ks=<replaceable>hd:/device/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:591
+#, no-c-format
+msgid "Other Device"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:592
+#, no-c-format
+msgid "ks=<replaceable>file:/device/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:596
+#, no-c-format
+msgid ""
+"ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:600
+#, no-c-format
+msgid ""
+"ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:604
+#, no-c-format
+msgid "ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:609
+#, no-c-format
+msgid ""
+"To obtain a Kickstart file from a script or application on a Web server, "
+"specify the URL of the application with the <option>ks=</option> option. If "
+"you add the option <option>kssendmac</option>, the request also sends HTTP "
+"headers to the Web application. Your application can use these headers to "
+"identify the computer. This line sends a request with headers to the "
+"application <wordasword>http://server.mydomain.com/kickstart.cgi</"
+"wordasword>:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:619
+#, no-c-format
+msgid ""
+"<userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</"
+"userinput>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:622
+#, no-c-format
+msgid "Enhancing Hardware Support"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:624
+#, no-c-format
+msgid ""
+"By default, Fedora attempts to automatically detect and configure support "
+"for all of the components of your computer. Fedora supports the majority of "
+"hardware in common use with the software <firstterm>drivers</firstterm> that "
+"are included with the operating system. To support other devices you may "
+"supply additional drivers during the installation process, or at a later "
+"time."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:635
+#, no-c-format
+msgid "Adding Hardware Support with Driver Disks"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:637
+#, no-c-format
+msgid ""
+"The installation system can load drivers from disks, pen drives, or network "
+"servers to configure support for new devices. After the installation is "
+"complete, remove any driver disks and store them for later use."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:644
+#, no-c-format
+msgid ""
+"Hardware manufacturers may supply <indexterm> <primary>driver disks</"
+"primary> </indexterm> driver disks for Fedora with the device, or provide "
+"image files to prepare the disks. To obtain the latest drivers, download the "
+"correct file from the website of the manufacturer."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:655
+#, no-c-format
+msgid "Driver Disks Supplied as Zipped Files"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:657
+#, no-c-format
+msgid ""
+"Driver disk images may be distributed as compressed archives, or zip files. "
+"For identification, the names of zip files include the extensions <filename>."
+"zip</filename>, or <filename>.tar.gz</filename>. To extract the contents of "
+"a zipped file with a Fedora system, choose <menuchoice> "
+"<guimenu>Applications</guimenu> <guisubmenu>Accessories</"
+"guisubmenu><guimenuitem>Archive Manager</guimenuitem></menuchoice>."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:668
+#, no-c-format
+msgid ""
+"To format a disk or pen drive with an image file, use the <command>dd</"
+"command> utility. For example, to prepare a diskette with the image file "
+"<filename>drivers.img</filename>, enter this command in a terminal window:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:674
+#, no-c-format
+msgid "<userinput>dd if=drivers.img of=/dev/fd0</userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:675
+#, no-c-format
+msgid ""
+"To use a driver disk in the installation process, specify the <option>dd</"
+"option> option at the <prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: screen
+#: adminoptions.xml:681
+#, no-c-format
+msgid "<userinput>linux dd</userinput>"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:683
+#, no-c-format
+msgid ""
+"Note that the <option>dd</option> option is interchangeable with the "
+"<option>driverdisk</option> option."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:687
+#, no-c-format
+msgid ""
+"When prompted, select <guibutton>Yes</guibutton> to provide a driver disk. "
+"Choose the drive that holds the driver disk from the list on the "
+"<guilabel>Driver Disk Source</guilabel> text screen."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:693
+#, no-c-format
+msgid ""
+"The installation system can also read drivers from disk images that are held "
+"on network servers. Refer to <xref linkend=\"tb-driversources\"/> for the "
+"supported sources of driver disk image files."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:699
+#, no-c-format
+msgid "Driver disk image sources"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:705
+#, no-c-format
+msgid "Image source"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:711
+#, no-c-format
+msgid "Select a drive or device"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:712
+#, no-c-format
+msgid "<option>dd</option>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:716
+#, no-c-format
+msgid ""
+"dd=<replaceable>http://server.mydomain.com/directory/drivers.img</"
+"replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:720
+#, no-c-format
+msgid ""
+"dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable>"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:724
+#, no-c-format
+msgid ""
+"dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable>"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:731
+#, no-c-format
+msgid "Overriding Automatic Hardware Detection"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:733
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:741
+#, no-c-format
+msgid "Check the Release Notes"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:742
+#, no-c-format
+msgid ""
+"Refer to the Release Notes for information on known issues with specific "
+"devices."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:747
+#, no-c-format
+msgid ""
+"To override the automatic hardware detection, use one or more of the "
+"following options:"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:752
+#, no-c-format
+msgid "Hardware Options"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:758
+#, no-c-format
+msgid "Compatibility"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:759
+#, no-c-format
+msgid "Option"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:764
+#, no-c-format
+msgid "Disable all hardware detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:768
+#, no-c-format
+msgid "Disable graphics, keyboard, and mouse detection"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:769
+#, no-c-format
+msgid "headless"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:772
+#, no-c-format
+msgid ""
+"Disable passing keyboard and mouse information to stage 2 of the "
+"installation program"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:776
+#, no-c-format
+msgid "Use basic VESA driver for video"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:777
+#, no-c-format
+msgid "xdriver=vesa"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:780
+#, no-c-format
+msgid "Disable shell access on virtual console 2 during installation"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:784
+#, no-c-format
+msgid "Disable advanced configuration and power interface (ACPI)"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:785
+#, no-c-format
+msgid "acpi=off"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:788
+#, no-c-format
+msgid "Disable machine check exception (MCE) CPU self-diagnosis."
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:789
+#, no-c-format
+msgid "nomce"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:792
+#, no-c-format
+msgid "Disable non-uniform menory access on the AMD64 architecture"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:793
+#, no-c-format
+msgid "numa-off"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:796
+#, no-c-format
+msgid ""
+"Force kernel to detect a specific amount of memory, where <replaceable>xxx</"
+"replaceable> is a value in megabytes"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:797
+#, no-c-format
+msgid "mem=<replaceable>xxx</replaceable>m"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:800
+#, no-c-format
+msgid "Enable DMA only for IDE and SATA drives"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:801
+#, no-c-format
+msgid "libata.dma=1"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:804
+#, no-c-format
+msgid "Disable BIOS-assisted RAID"
+msgstr ""
+
+#. Tag: option
+#: adminoptions.xml:805
+#, no-c-format
+msgid "nodmraid"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:808
+#, no-c-format
+msgid "Disable Firewire device detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:812
+#, no-c-format
+msgid "Disable parallel port detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:816
+#, no-c-format
+msgid "Disable PC Card (PCMCIA) device detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:820
+#, no-c-format
+msgid "Disable USB storage device detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:824
+#, no-c-format
+msgid "Disable all USB device detection"
+msgstr ""
+
+#. Tag: entry
+#: adminoptions.xml:828
+#, no-c-format
+msgid "Disable all probing of network hardware"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:835
+#, no-c-format
+msgid "Additional Screen"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:837
+#, no-c-format
+msgid ""
+"The <option>isa</option> option causes the system to display an additional "
+"text screen at the beginning of the installation process. Use this screen to "
+"configure the ISA devices on your computer."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:846
+#, no-c-format
+msgid ""
+"Other kernel boot options have no particular meaning for "
+"<application>anaconda</application> and do not affect the installation "
+"process. However, if you use these options to boot the installation system, "
+"<application>anaconda</application> will preserve them in the bootloader "
+"configuration."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:855
+#, no-c-format
+msgid "Using the Maintenance Boot Modes"
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:858
+#, no-c-format
+msgid "Loading the Memory (RAM) Testing Mode"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:860
+#, no-c-format
+msgid ""
+"Faults in memory modules may cause your system to freeze or crash "
+"unpredictably. In some cases, memory faults may only cause errors with "
+"particular combinations of software. For this reason, you should test the "
+"memory of a computer before you install Fedora for the first time, even if "
+"it has previously run other operating systems."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:869
+#, no-c-format
+msgid ""
+"Fedora includes the <application>Memtest86</application> memory testing "
+"application. To boot your computer in <indexterm> <primary>memory testing "
+"mode</primary> </indexterm> memory testing mode, choose <guimenuitem>Memory "
+"test</guimenuitem> at the boot menu. The first test starts immediately. By "
+"default, <application>Memtest86</application> carries out a total of ten "
+"tests."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:880
+#, no-c-format
+msgid ""
+"To halt the tests and reboot your computer, enter <keycap>Esc</keycap> at "
+"any time."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:887
+#, no-c-format
+msgid "Verifying boot media"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:888
+#, no-c-format
+msgid ""
+"You can test the integrity of an ISO-based installation source before using "
+"it to install Fedora. These sources include CD, DVD, and ISO images stored "
+"on a local hard drive or on an NFS server. Verifying that the ISO images are "
+"instace before you attempt an installation helps to avoid problems that are "
+"often encountered during installation."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:891
+#, no-c-format
+msgid "Fedora offers you three ways to test installation ISOs:"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:896
+#, no-c-format
+msgid ""
+"select the <guilabel>Verify and Boot</guilabel> option on the Fedora Live "
+"CD. To access the Live CD boot menu, press any key within ten seconds of the "
+"splash screen appearing."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:901
+#, no-c-format
+msgid ""
+"select <guilabel>OK</guilabel> at the prompt to test the media before "
+"installation when booting from the Fedora distribution CD set or DVD"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:906
+#, no-c-format
+msgid "boot Fedora with the option <option>mediacheck</option> option."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:914
+#, no-c-format
+msgid "Booting Your Computer with the Rescue Mode"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:918
+#, no-c-format
+msgid ""
+"You may boot a command-line Linux system from either a <indexterm> "
+"<primary>rescue discs</primary> </indexterm> rescue disc or an installation "
+"disc, without installing Fedora on the computer. This enables you to use the "
+"utilities and functions of a running Linux system to modify or repair "
+"systems that are already installed on your computer."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:929
+#, no-c-format
+msgid ""
+"The rescue disc starts the rescue mode system by default. To load the rescue "
+"system with the installation disc, choose <guimenuitem>Rescue installed "
+"system</guimenuitem> from the boot menu."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:935
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:942
+#, no-c-format
+msgid ""
+"By default, rescue mode attaches an existing operating system to the rescue "
+"system under the directory <filename>/mnt/sysimage/</filename>."
+msgstr ""
+
+#. Tag: title
+#: adminoptions.xml:950
+#, no-c-format
+msgid "Upgrading your computer"
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:952
+#, no-c-format
+msgid ""
+"A previous boot option, <option>upgrade</option>, has been superceded by a "
+"stage in the installation process where the installation program prompts you "
+"to upgrade or reinstall earlier versions of Fedora that it detects on your "
+"system."
+msgstr ""
+
+#. Tag: para
+#: adminoptions.xml:956
+#, no-c-format
+msgid ""
+"However, the installation program may not correctly detect a previous "
+"version of Fedora if the contents of the <filename>/etc/fedora-release</"
+"filename> file have changed. The boot option <option>upgradeany</option> "
+"relaxes the test that the installation program performs and allows you to "
+"upgrade a Fedora installation that the installation program has not "
+"correctly identified."
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:7
+#, no-c-format
+msgid "Advice on Partitions"
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:8
+#, no-c-format
+msgid ""
+"Optimal partition setup depends on the usage for the Linux system in "
+"question. The following tips may help you decide how to allocate your disk "
+"space."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:14
+#, no-c-format
+msgid ""
+"If you expect that you or other users will store data on the system, create "
+"a separate partition for the <filename>/home</filename> directory within a "
+"volume group. With a separate <filename>/home</filename> partition, you may "
+"upgrade or reinstall Fedora without erasing user data files."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:23
+#, no-c-format
+msgid ""
+"Each kernel installed on your system requires approximately 10 MB on the "
+"<filename class=\"partition\">/boot</filename> partition. Unless you plan to "
+"install a great many kernels, the default partition size of 100 MB for "
+"<filename class=\"partition\">/boot</filename> should suffice."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:31
+#, no-c-format
+msgid ""
+"The <application>GRUB</application> bootloader does not support the ext4 or "
+"Btrfs file systems. You cannot use an ext4 or btrfs partition for <filename>/"
+"boot</filename>."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:37
+#, no-c-format
+msgid ""
+"The <filename class=\"directory\">/var</filename> directory holds content "
+"for a number of applications, including the <application>Apache</"
+"application> web server. It also is used to store downloaded update packages "
+"on a temporary basis. Ensure that the partition containing the <filename "
+"class=\"directory\">/var</filename> directory has enough space to download "
+"pending updates and hold your other content."
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:46
+#, no-c-format
+msgid "Pending Updates"
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:47
+#, no-c-format
+msgid ""
+"Because Fedora is a rapidly progressing collection of software, many updates "
+"may be available late in a release cycle. You can add an update repository "
+"to the sources for installation later to minimize this issue. Refer to <xref "
+"linkend=\"sn-additional-repos\"/> for more information."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:56
+#, no-c-format
+msgid ""
+"The <filename class=\"directory\">/usr</filename> directory holds the "
+"majority of software content on a Fedora system. For an installation of the "
+"default set of software, allocate at least 4 GB of space. If you are a "
+"software developer or plan to use your Fedora system to learn software "
+"development skills, you may want to at least double this allocation."
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:64
+#, no-c-format
+msgid ""
+"Do not place <filename class=\"directory\">/usr</filename> on a separate "
+"partition"
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:65
+#, no-c-format
+msgid ""
+"If <filename class=\"directory\">/usr</filename> is on a separate partition "
+"from <filename class=\"directory\">/</filename>, the boot process becomes "
+"much more complex, and in some situations (like installations on iSCSI "
+"drives), might not work at all."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:69
+#, no-c-format
+msgid ""
+"Consider leaving a portion of the space in an LVM volume group unallocated. "
+"This unallocated space gives you flexibility if your space requirements "
+"change but you do not wish to remove data from other partitions to "
+"reallocate storage."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:76
+#, no-c-format
+msgid ""
+"If you separate subdirectories into partitions, you can retain content in "
+"those subdirectories if you decide to install a new version of Fedora over "
+"your current system. For instance, if you intend to run a "
+"<application>MySQL</application> database in <filename class=\"directory\">/"
+"var/lib/mysql</filename>, make a separate partition for that directory in "
+"case you need to reinstall later."
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:86
+#, no-c-format
+msgid ""
+"The following table is a possible partition setup for a system with a "
+"single, new 80 GB hard disk and 1 GB of RAM. Note that approximately 10 GB "
+"of the volume group is unallocated to allow for future growth."
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:91
+#, no-c-format
+msgid "Example Usage"
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:92
+#, no-c-format
+msgid "This setup is not optimal for all use cases."
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:95 Advice_on_Partitions.xml:97
+#, no-c-format
+msgid "Example partition setup"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:101 Advice_on_Partitions.xml:129
+#, no-c-format
+msgid "Partition"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:102 Advice_on_Partitions.xml:130
+#, no-c-format
+msgid "Size and type"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:108
+#, no-c-format
+msgid "100 MB <systemitem class=\"filesystem\">ext3</systemitem> partition"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:113
+#, no-c-format
+msgid "2 GB swap"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:116
+#, no-c-format
+msgid "LVM physical volume"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:117
+#, no-c-format
+msgid "Remaining space, as one LVM volume group"
+msgstr ""
+
+#. Tag: para
+#: Advice_on_Partitions.xml:123
+#, no-c-format
+msgid ""
+"The physical volume is assigned to the default volume group and divided into "
+"the following logical volumes:"
+msgstr ""
+
+#. Tag: title
+#: Advice_on_Partitions.xml:125
+#, no-c-format
+msgid "Example partition setup: LVM physical volume"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:136
+#, no-c-format
+msgid "13 GB ext4"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:140
+#, no-c-format
+msgid "4 GB ext4"
+msgstr ""
+
+#. Tag: entry
+#: Advice_on_Partitions.xml:144
+#, no-c-format
+msgid "50 GB ext4"
+msgstr ""
+
+#. Tag: author
+#: Author_Group.xml:5
+#, no-c-format
+msgid ""
+"<firstname>Fedora</firstname> <surname>Documentation Project</surname> "
+"<email>fedora-docs-list at redhat.com</email>"
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-caution-1.xml:11
+#, no-c-format
+msgid ""
+"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 drive(s). Mistakes do happen and "
+"can result in the loss of all your data."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-figure-1.xml:8
+#, no-c-format
+msgid "Automatic partitioning."
+msgstr ""
+
+#. Tag: secondary
+#: Automatic_Partitioning_common-indexterm-1.xml:11
+#, no-c-format
+msgid "automatic"
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-itemizedlist-1.xml:7
+#, no-c-format
+msgid ""
+"<guilabel>Remove all partitions on selected drives and create default "
+"layout</guilabel> — select this option to remove all partitions on "
+"your hard drive(s) (this includes partitions created by other operating "
+"systems such as Windows VFAT or NTFS partitions)."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-itemizedlist-1.xml:13
+#, no-c-format
+msgid ""
+"If you select this option, all data on the selected hard drive(s) is removed "
+"by the installation program. Do not select this option if you have "
+"information that you want to keep on the hard drive(s) where you are "
+"installing Fedora."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-itemizedlist-1.xml:20
+#, no-c-format
+msgid ""
+"<guilabel>Remove Linux partitions on selected drives and create default "
+"layout</guilabel> — select this option to remove only Linux partitions "
+"(partitions created from a previous Linux installation). This does not "
+"remove other partitions you may have on your hard drive(s) (such as VFAT or "
+"FAT32 partitions)."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-itemizedlist-1.xml:29
+#, no-c-format
+msgid ""
+"<guilabel>Use free space on selected drives and create default layout</"
+"guilabel> — select this option to retain your current data and "
+"partitions, assuming you have enough free space available on your hard drive"
+"(s)."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-note-1.xml:8
+#, no-c-format
+msgid ""
+"If you install Fedora in text mode, you can only use the default "
+"partitioning schemes described in this section. Therefore, although you can "
+"choose to use a whole drive, to remove existing Linux partitions, or to use "
+"the free space on the drive, you cannot customize the partition layout. That "
+"is, 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."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-note-1.xml:12
+#, no-c-format
+msgid ""
+"Furthermore, advanced options such as LVM, encrypted filesystems, and "
+"resizable filesystems are available only in graphical mode and kickstart."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"Create default layout allows you to have some control concerning what data "
+"is removed (if any) from your system. Your options are:"
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-2.xml:5
+#, no-c-format
+msgid ""
+"Using your mouse, choose the storage drive(s) on which you want Fedora to be "
+"installed. If you have two or more drives, you can choose which drive(s) "
+"should contain this installation. Unselected drives, and any data on them, "
+"are not touched."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-3.xml:5
+#, no-c-format
+msgid ""
+"To review and make any necessary changes to the partitions created by "
+"automatic partitioning, select the <guilabel>Review</guilabel> option. After "
+"selecting <guilabel>Review</guilabel> and clicking <guibutton>Next</"
+"guibutton> to move forward, the partitions created for you by "
+"<application>anaconda</application> appear. You can make modifications to "
+"these partitions if they do not meet your needs."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-4.xml:8
+#, no-c-format
+msgid ""
+"Click <guibutton>Next</guibutton> once you have made your selections to "
+"proceed."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-5.xml:6
+#, no-c-format
+msgid ""
+"Select <guilabel>Encrypt system</guilabel> to encrypt all partitions except "
+"the <filename class=\"partition\">/boot</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-6.xml:6
+#, no-c-format
+msgid "Use the <guilabel>Advanced storage options</guilabel> option if:"
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-6.xml:10
+#, no-c-format
+msgid ""
+"You want to install Fedora to a drive connected through the "
+"<firstterm>iSCSI</firstterm> protocol. Select <guilabel>Advanced storage "
+"options</guilabel>, then select <guilabel>Add iSCSI target</guilabel>, then "
+"select <guilabel>Add drive</guilabel>. Provide an IP address and the iSCSI "
+"initiator name, and select <guilabel>Add drive</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_common-para-6.xml:21
+#, no-c-format
+msgid ""
+"You want to disable a <firstterm>dmraid</firstterm> device that was detected "
+"at boot time."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_x86_ppc-tip-para-1.xml:8
+#, no-c-format
+msgid ""
+"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 <filename>/boot/</filename> "
+"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."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_x86_ppc-tip-para-2.xml:8
+#, no-c-format
+msgid ""
+"A <filename>/boot/</filename> partition is also necessary for software RAID "
+"setups."
+msgstr ""
+
+#. Tag: para
+#: Automatic_Partitioning_x86_ppc-tip-para-3.xml:8
+#, no-c-format
+msgid ""
+"If you have chosen to automatically partition your system, you should select "
+"<guilabel>Review</guilabel> and manually edit your <filename>/boot/</"
+"filename> partition."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Hard_Disk_common-note-1.xml:6
+#, no-c-format
+msgid "Cannot Install from LVM Partitions"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-note-1.xml:7
+#, no-c-format
+msgid ""
+"You cannot use ISO files on partitions controlled by LVM (Logical Volume "
+"Management)."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Hard_Disk_common-note-2.xml:6
+#, no-c-format
+msgid "Use a leading slash"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-note-2.xml:7
+#, no-c-format
+msgid "An entry without a leading slash may cause the installation to fail."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-10.xml:5
+#, no-c-format
+msgid ""
+"Also specify the <guilabel>Directory holding images</guilabel>. Enter 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:"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-11.xml:5
+#, no-c-format
+msgid ""
+"Select <guibutton>OK</guibutton> to continue. Proceed with <xref linkend="
+"\"sn-welcome-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"The <guilabel>Select Partition</guilabel> screen applies only if you are "
+"installing from a disk partition (that is, if you selected <guimenuitem>Hard "
+"Drive</guimenuitem> in the <guilabel>Installation Method</guilabel> dialog). "
+"This dialog allows you to name the disk partition and directory from which "
+"you are installing Fedora."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-3.xml:8
+#, no-c-format
+msgid ""
+"If the ISO images are in the root (top-level) directory of a partition, "
+"enter a <filename>/</filename>. 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 <filename>/home/</filename>, and the "
+"images are in <filename>/home/new/</filename>, you would enter <filename>/"
+"new/</filename>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-5.xml:5
+#, no-c-format
+msgid ""
+"The ISO files must be located on a hard drive that is either internal to the "
+"computer, or attached to the machine by USB. In addition the "
+"<filename>install.img</filename> file from within the ISO files must be "
+"copied to a directory named <filename class=\"directory\">images</filename> "
+"Use this option to install Fedora on computers that are without a network "
+"connection or CD/DVD drives."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-6.xml:5
+#, no-c-format
+msgid ""
+"To extract the <filename>install.img</filename> from the ISO follow the "
+"procedure:"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-8.xml:5
+#, no-c-format
+msgid ""
+"Before you begin installation from a hard drive, check the partition type to "
+"ensure that Fedora can read it. To check a partition's file system under "
+"Windows, use the <application>Disk Management</application> tool. To check a "
+"partition's file system under Linux, use the <command>fdisk</command> "
+"utility."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_common-para-9.xml:5
+#, no-c-format
+msgid ""
+"Select the partition containing the ISO files from the list of available "
+"partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with "
+"<filename>/dev/sd</filename>. Each individual drive has its own letter, for "
+"example <filename>/dev/sda</filename>. Each partition on a drive is "
+"numbered, for example <filename>/dev/sda1</filename>."
+msgstr ""
+
+#. Tag: screen
+#: Beginning_Installation_Hard_Disk_common-screen-1.xml:5
+#, no-c-format
+msgid ""
+"<command><![CDATA[mount -t iso9660 /path/to/Fedora11.iso /mnt/point -o loop,"
+"ro]]></command>\n"
+"  <command><![CDATA[cp -pr /mnt/point/images /path/images/]]></command>\n"
+"  <command><![CDATA[umount /mnt/point]]></command>"
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:5
+#, no-c-format
+msgid "Location of ISO images for different partition types"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:9
+#, no-c-format
+msgid "Partition type"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:10
+#, no-c-format
+msgid "Volume"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:11
+#, no-c-format
+msgid "Original path to files"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:12
+#, no-c-format
+msgid "Directory to use"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:17
+#, no-c-format
+msgid "VFAT"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:18
+#, no-c-format
+msgid "<entry>D:\\</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:19
+#, no-c-format
+msgid "D:\\Downloads\\F&PRODVER;"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:20
+#, no-c-format
+msgid "/Downloads/F&PRODVER;"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:23
+#, no-c-format
+msgid "ext2, ext3, ext4"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:25
+#, no-c-format
+msgid "/home/user1/F&PRODVER;"
+msgstr ""
+
+#. Tag: entry
+#: Beginning_Installation_Hard_Disk_common-table-1.xml:26
+#, no-c-format
+msgid "/user1/F&PRODVER;"
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Hard_Disk_common-title-1.xml:8
+#, no-c-format
+msgid "Installing from a Hard Drive"
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml:8
+#, no-c-format
+msgid "Selecting Partition Dialog for Hard Drive Installation"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml:11
+#, no-c-format
+msgid "Selecting partition dialog for a hard drive installation."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Network-x86.xml:31
+#, no-c-format
+msgid "TCP/IP Configuration"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network-x86.xml:34
+#, no-c-format
+msgid "Configure the network device address(es) for installation."
+msgstr ""
+
+#. Tag: primary
+#: Beginning_Installation_Network_x86_ppc-indexterm-2.xml:6
+#, no-c-format
+msgid "TCP/IP configuration"
+msgstr ""
+
+#. Tag: primary
+#: Beginning_Installation_Network_x86_ppc-indexterm-3.xml:6
+#, no-c-format
+msgid "NFS (Network File System)"
+msgstr ""
+
+#. Tag: secondary
+#: Beginning_Installation_Network_x86_ppc-indexterm-3.xml:7
+#, no-c-format
+msgid "install from"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-list-1.xml:7
+#, no-c-format
+msgid ""
+"If you are installing via NFS, proceed to <xref linkend=\"s1-begininstall-"
+"nfs-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-list-1.xml:13
+#, no-c-format
+msgid ""
+"If you are installing via Web or FTP, proceed to <xref linkend=\"s1-"
+"begininstall-url-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-1.xml:5
+#, no-c-format
+msgid ""
+"If you are performing a network installation, the <guilabel>Configure TCP/"
+"IP</guilabel> dialog appears. This dialog asks for your IP and other network "
+"addresses. You can choose to configure the IP address and Netmask of the "
+"device via DHCP or manually."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-2.xml:5
+#, no-c-format
+msgid ""
+"Enter the IP address you are using during installation and press "
+"<keycap>Enter</keycap>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-3.xml:5
+#, no-c-format
+msgid ""
+"The installation program is network-aware and can use network settings for a "
+"number of functions. For instance, you can install Fedora from a network "
+"server using FTP, HTTP, or NFS protocols. You can also instruct the "
+"installation program to consult additional software repositories later in "
+"the process."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-4.xml:5
+#, no-c-format
+msgid ""
+"By default, the installation program uses DHCP to automatically provide "
+"network settings. If you use a cable or DSL modem, router, firewall, or "
+"other network hardware to communicate with the Internet, DHCP is a suitable "
+"option. If your network has no DHCP server, clear the check box labeled "
+"<guilabel>Use dynamic IP configuration (DHCP)</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-5.xml:5
+#, no-c-format
+msgid ""
+"The installation program supports only the IPv4 protocol. Refer also to "
+"<xref linkend=\"sn-networkconfig-fedora\"/> for more information on "
+"configuring your network."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-6.xml:5
+#, no-c-format
+msgid ""
+"When the installation process completes, it will transfer these settings to "
+"your system."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-7.xml:5
+#, no-c-format
+msgid ""
+"You can install from a Web, FTP, or NFS server either on your local network "
+"or, if you are connected, on the Internet. You may install Fedora from your "
+"own private mirror, or use one of the public mirrors maintained by members "
+"of the community. To ensure that the connection is as fast and reliable as "
+"possible, use a server that is close to your own geographical location."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_Network_x86_ppc-para-8.xml:5
+#, no-c-format
+msgid ""
+"The Fedora Project maintains a list of Web and FTP public mirrors, sorted by "
+"region, at <ulink url=\"http://fedoraproject.org/wiki/Mirrors\"></ulink>. To "
+"determine the complete directory path for the installation files, add "
+"<filename>/&PRODVER;/Fedora/<replaceable>architecture</replaceable>/os/</"
+"filename> to the path shown on the web page. A correct mirror location for "
+"an <systemitem>i386</systemitem> system resembles the URL <literal>http://"
+"mirror.example.com/pub/fedora/linux/releases/&PRODVER;/Fedora/i386/os</"
+"literal>."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_Network_x86_ppc-title.xml:7
+#, no-c-format
+msgid "Performing a Network Installation"
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_NFS_common-figure-1.xml:8
+#, no-c-format
+msgid "NFS Setup Dialog"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS_common-figure-1.xml:11
+#, no-c-format
+msgid "NFS setup dialog."
+msgstr ""
+
+#. Tag: tertiary
+#: Beginning_Installation_NFS_common-indexterm-3.xml:11
+#, no-c-format
+msgid "<tertiary>NFS</tertiary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Beginning_Installation_NFS_common-indexterm-4.xml:11
+#, no-c-format
+msgid "server information"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"The NFS dialog applies only if you are installing from an NFS server (if you "
+"selected <guimenuitem>NFS Image</guimenuitem> in the <guilabel>Installation "
+"Method</guilabel> dialog)."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS_common-para-2.xml:8
+#, no-c-format
+msgid ""
+"Enter the domain name or IP address of your NFS server. For example, if you "
+"are installing from a host named <filename>eastcoast</filename> in the "
+"domain <filename>example.com</filename>, enter <filename>eastcoast.example."
+"com</filename> in the <guilabel>NFS Server</guilabel> field."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS_common-para-4.xml:6
+#, no-c-format
+msgid ""
+"If the NFS server is exporting a mirror of the Fedora installation tree, "
+"enter the directory which contains the root of the installation tree. You "
+"will enter an Installation Key later on in the process which will determine "
+"which subdirectories are used to install from. If everything was specified "
+"properly, a message appears indicating that the installation program for "
+"Fedora is running."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS_common-para-5.xml:5
+#, no-c-format
+msgid ""
+"If the NFS server is exporting the ISO images of the Fedora CD-ROMs, enter "
+"the directory which contains the ISO images."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_NFS_common-title-1.xml:8
+#, no-c-format
+msgid "Installing via NFS"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_NFS-x86.xml:22
+#, no-c-format
+msgid ""
+"Next, enter the name of the exported directory. If you followed the setup "
+"described in <xref linkend=\"s1-steps-network-installs-x86\"/>, you would "
+"enter the directory <filename><replaceable>/export/directory/</replaceable></"
+"filename>."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:7
+#, no-c-format
+msgid "Beginning the Installation"
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:10
+#, no-c-format
+msgid "Aborting the Installation"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:11
+#, no-c-format
+msgid ""
+"To abort the installation, either press <keycombo><keycap>Ctrl </"
+"keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo> or power off your "
+"computer with the power switch. You may abort the installation process "
+"without consequence at any time prior to selecting <guibutton>Write changes "
+"to disk</guibutton> on the <guilabel>Write partitioning to disk</guilabel> "
+"screen. Fedora makes no permanent changes to your computer until that point. "
+"Please be aware that stopping the installation after partitioning has begun "
+"can leave your computer unusable."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:24
+#, no-c-format
+msgid "The Boot Menu"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:25
+#, no-c-format
+msgid ""
+"The boot media displays a graphical boot menu with several options. If no "
+"key is hit within 60 seconds, the default boot option runs. To choose the "
+"default, either wait for the timer to run out or hit <keycap>Enter</keycap> "
+"on the keyboard. To select a different option than the default, use the "
+"arrow keys on your keyboard, and hit <keycap>Enter</keycap> when the correct "
+"option is highlighted. If you want to customize the boot options for a "
+"particular option, hit the <keycap>Tab</keycap> key."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:34
+#, no-c-format
+msgid "Using Boot Options"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:35
+#, no-c-format
+msgid ""
+"For a listing and explanation of common boot options, refer to <xref linkend="
+"\"ap-admin-options\"/>."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:38
+#, no-c-format
+msgid ""
+"When using Fedora Live media, press any key during the initial boot "
+"countdown to bring up the <guilabel>Boot Options</guilabel> menu. The boot "
+"options include:"
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:44
+#, no-c-format
+msgid "Boot"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:45
+#, no-c-format
+msgid ""
+"This option is the default. If you select this option, only the kernel and "
+"startup programs load into memory. This option takes less time to load. As "
+"you use programs, they are loaded from the disc, which takes more time. This "
+"mode can be used on machines with less total memory."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:54
+#, no-c-format
+msgid "Verify and Boot"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:55
+#, no-c-format
+msgid ""
+"This option lets you verify the disc before you run the Live CD environment. "
+"Refer to <xref linkend=\"sn-verifying-media\"/> for more information on the "
+"verification process."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:63 beginninginstallation.xml:122
+#, no-c-format
+msgid "Memory Test"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:64
+#, no-c-format
+msgid ""
+"This option runs an exhaustive test on the memory on your system. For more "
+"information, refer to <xref linkend=\"sn-memtest\"/>."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:73 beginninginstallation.xml:114
+#, no-c-format
+msgid "Boot from local drive"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:74
+#, no-c-format
+msgid ""
+"This option boots the system from the first installed disk. If you booted "
+"this disc accidentally, use this option to boot from the hard disk "
+"immediately without starting the installer."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:83
+#, no-c-format
+msgid ""
+"If you boot the DVD, rescue CD, or minimal boot media, the boot menu options "
+"include:"
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:88
+#, no-c-format
+msgid "Install or upgrade an existing system"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:89
+#, no-c-format
+msgid ""
+"This option is the default. Choose this option to install Fedora onto your "
+"computer system using the graphical installation program."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:96
+#, no-c-format
+msgid "Install system with basic video driver"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:97
+#, no-c-format
+msgid ""
+"This option allows you to install Fedora in graphical mode even if the "
+"installation program is unable to load the correct driver for your video "
+"card. If your screen appears distorted or goes blank when using the the "
+"<guilabel>Install or upgrade an existing system</guilabel> option, restart "
+"your computer and try this option instead."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:102
+#, no-c-format
+msgid "Rescue installed system"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:103
+#, no-c-format
+msgid ""
+"Choose this option to repair a problem with your installed Fedora system "
+"that prevents you from booting normally. Although Fedora is an exceptionally "
+"stable computing platform, it is still possible for occasional problems to "
+"occur that prevent booting. The rescue environment contains utility programs "
+"that allow you fix a wide variety of these problems."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:115 beginninginstallation.xml:123
+#, no-c-format
+msgid "(as for Live CD)"
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:131
+#, no-c-format
+msgid "Installing from a Different Source"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:132
+#, no-c-format
+msgid ""
+"All boot media except the distribution DVD present a menu that allows you to "
+"choose the installation source, such as the network or a hard disk. If you "
+"are booting the distribution DVD and do not want to install from the DVD, "
+"hit <keycap>Tab</keycap> at the boot menu. Add a space and the option "
+"<option>linux askmethod</option> to the end of the line that appears below "
+"the menu."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:138
+#, no-c-format
+msgid ""
+"You can install Fedora from the ISO images stored on hard disk, or from a "
+"network using NFS, FTP, or HTTP methods. Experienced users frequently use "
+"one of these methods because it is often faster to read data from a hard "
+"disk or network server than from a CD or DVD."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:143
+#, no-c-format
+msgid ""
+"The following table summarizes the different boot methods and recommended "
+"installation methods to use with each:"
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:145
+#, no-c-format
+msgid "Boot methods and installation methods"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:149
+#, no-c-format
+msgid "Boot method"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:155
+#, no-c-format
+msgid "<entry>DVD</entry>"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:156
+#, no-c-format
+msgid "DVD, network, or hard disk"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:159
+#, no-c-format
+msgid "Minimal boot CD or USB, rescue CD"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:160
+#, no-c-format
+msgid "Network or hard disk"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:163
+#, no-c-format
+msgid "Live CD or USB"
+msgstr ""
+
+#. Tag: entry
+#: beginninginstallation.xml:164
+#, no-c-format
+msgid "<application>Install to Hard Disk</application> application"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:170
+#, no-c-format
+msgid ""
+"contains detailed information about installing from alternate locations."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:176
+#, no-c-format
+msgid "Verifying Media"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:177
+#, no-c-format
+msgid ""
+"The distribution DVD media and the Live CD media offer an option to verify "
+"the integrity of the media. Recording errors sometimes occur while producing "
+"CD or DVD media in home computer equipment. An error in the data for package "
+"chosen in the installation program can cause the installation to abort. To "
+"minimize the chances of data errors affecting the installation, verify the "
+"media before installing."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:192
+#, no-c-format
+msgid "Verifying the Live CD"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:193
+#, no-c-format
+msgid ""
+"If you boot from the Live CD, choose <guilabel>Verify and Boot</guilabel> "
+"from the boot menu. The verification process runs automatically during the "
+"boot process, and if it succeeds, the Live CD continues loading. If the "
+"verification fails, create a new Live CD using the ISO image you downloaded "
+"earlier."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:201
+#, no-c-format
+msgid "Verifying the DVD"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:202
+#, no-c-format
+msgid ""
+"If you boot from the Fedora distribution DVD, the option to verify the media "
+"appears after you choose to install Fedora. If the verification succeeds, "
+"the installation process proceeds normally. If the process fails, create a "
+"new DVD using the ISO image you downloaded earlier."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:211
+#, no-c-format
+msgid "Booting from the Network using PXE"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:213
+#, no-c-format
+msgid ""
+"To boot with <indexterm> <primary>PXE (Pre-boot eXecution Environment)</"
+"primary> </indexterm> PXE, you need a properly configured server, and a "
+"network interface in your computer that supports PXE. For information on how "
+"to configure a PXE server, refer to <xref linkend=\"ap-install-server\"/>."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:222
+#, no-c-format
+msgid ""
+"Configure the computer to boot from the network interface. This option is in "
+"the BIOS, and may be labeled <option>Network Boot</option> or <option>Boot "
+"Services</option>. Once you properly configure PXE booting, the computer can "
+"boot the Fedora installation system without any other media."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:230
+#, no-c-format
+msgid "To boot a computer from a PXE server:"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:236
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:243
+#, no-c-format
+msgid "Switch on the computer."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:248
+#, no-c-format
+msgid ""
+"A menu screen appears. Press the number key that corresponds to the desired "
+"option."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:256
+#, no-c-format
+msgid "PXE Troubleshooting"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:257
+#, no-c-format
+msgid ""
+"If your PC does not boot from the netboot server, ensure that the BIOS is "
+"configured to boot first from the correct network interface. Some BIOS "
+"systems specify the network interface as a possible boot device, but do not "
+"support the PXE standard. Refer to your hardware documentation for more "
+"information."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:266
+#, no-c-format
+msgid "Multiple NICs and PXE installation"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:267
+#, no-c-format
+msgid ""
+"Some servers with multiple network interfaces may not assign eth0 to the "
+"first network interface as BIOS knows it, which can cause the installer to "
+"try using a different network interface than was used by PXE. To change this "
+"behavior, use the following in <filename>pxelinux.cfg/*</filename> config "
+"files:"
+msgstr ""
+
+#. Tag: option
+#: beginninginstallation.xml:274
+#, no-c-format
+msgid "IPAPPEND 2"
+msgstr ""
+
+#. Tag: option
+#: beginninginstallation.xml:276
+#, no-c-format
+msgid "APPEND ksdevice=bootif"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:278
+#, no-c-format
+msgid ""
+"The configuration options above causes the installer to use the same network "
+"interface as BIOS and PXE use. You can also use the following option:"
+msgstr ""
+
+#. Tag: option
+#: beginninginstallation.xml:281
+#, no-c-format
+msgid "ksdevice=link"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:283
+#, no-c-format
+msgid ""
+"This option causes the installer to use the first network device it finds "
+"that is linked to a network switch."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:289
+#, no-c-format
+msgid "Graphical and Text Interfaces"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:290
+#, no-c-format
+msgid ""
+"Fedora &PRODVER; supports graphical and text-based installations. However, "
+"the installer image must either fit in RAM or appear on local storage, such "
+"as the installation DVD or Live Media. Therefore, only systems with more "
+"than 192 MB of RAM or that boot from the installation DVD or Live Media "
+"can use the graphical installer. Systems with 192 MB RAM or less "
+"automatically scale back to using the text-based installer. Note that you "
+"must still have a minimum of 64 MB of RAM for installation to proceed "
+"in text mode. If you prefer to use the text-based installer, type "
+"<option>linux text</option> at the <prompt>boot:</prompt> prompt."
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:298
+#, no-c-format
+msgid ""
+"If one of the following situations occurs, the installation program uses a "
+"text mode:"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:302
+#, no-c-format
+msgid ""
+"The installation system fails to identify the display hardware on your "
+"computer"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:306
+#, no-c-format
+msgid "Your computer has less than 192 MB of RAM"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:309
+#, no-c-format
+msgid "You choose the text mode installation from the boot menu"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:313
+#, no-c-format
+msgid ""
+"The text screens provide most of the same functions as the standard screens, "
+"although disk partitioning is simplified, and bootloader configuration and "
+"package selection are handled automatically in text mode. If you choose to "
+"install Fedora in text mode, you can still configure your system to use a "
+"graphical interface after installation."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:317
+#, no-c-format
+msgid "Graphical Interface Usage"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:318
+#, no-c-format
+msgid ""
+"Installing in text mode does <emphasis role=\"strong\">not</emphasis> "
+"prevent you from using a graphical interface on your system once it is "
+"installed. If you have trouble configuring your system for graphical "
+"interface use, consult other sources for troubleshooting help as shown in "
+"<xref linkend=\"sn-additional-help\"/>."
+msgstr ""
+
+#. Tag: title
+#: beginninginstallation.xml:326
+#, no-c-format
+msgid "Installation requires at least 64 MB of RAM"
+msgstr ""
+
+#. Tag: para
+#: beginninginstallation.xml:327
+#, no-c-format
+msgid ""
+"If your system has less than 64 MB of RAM, installation will not continue."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_URL-common-figure-1.xml:5
+#, no-c-format
+msgid "URL Setup Dialog"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_URL-common-figure-1.xml:8
+#, no-c-format
+msgid "URL setup dialog."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_URL-common-para-1.xml:5
+#, no-c-format
+msgid ""
+"The URL dialog applies only if you are installing from a FTP or HTTP server "
+"(if you selected <guimenuitem>URL</guimenuitem> in the "
+"<guilabel>Installation Method</guilabel> dialog). This dialog prompts you "
+"for information about the FTP or HTTP server from which you are installing "
+"Fedora."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_URL-common-para-2-Fedora.xml:6
+#, no-c-format
+msgid ""
+"Enter the name or IP address of the FTP or HTTP site you are installing "
+"from, and the name of the directory containing your architecture. For "
+"example, if the FTP or HTTP site contains the directory <filename>/mirrors/"
+"Fedora/<replaceable>arch</replaceable>/</filename>, enter <filename>/mirrors/"
+"Fedora/<replaceable>arch</replaceable>/</filename> (where <replaceable>arch</"
+"replaceable> is replaced with the architecture type of your system, such as "
+"i386). If everything was specified properly, a message box appears "
+"indicating that files are being retrieved from the server."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_URL-common-title-1.xml:5
+#, no-c-format
+msgid "Installing via FTP or HTTP"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation-x86.xml:28
+#, no-c-format
+msgid ""
+"The installation program then probes your system and attempts to identify "
+"your CD-ROM drive. It starts by looking for an IDE (also known as an ATAPI) "
+"CD-ROM drive."
+msgstr ""
+
+#. Tag: secondary
+#: Beginning_Installation-x86.xml:36
+#, no-c-format
+msgid "aborting"
+msgstr ""
+
+#. Tag: primary
+#: Beginning_Installation-x86.xml:39
+#, no-c-format
+msgid "canceling the installation"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation-x86.xml:41
+#, no-c-format
+msgid ""
+"To abort the installation process at this time, reboot your machine and then "
+"eject the boot media. You can safely cancel the installation at any point "
+"before the <guilabel>About to Install</guilabel> screen. Refer to <xref "
+"linkend=\"s1-preparetoinstall-x86\"/> for more information."
+msgstr ""
+
+#. Tag: secondary
+#: Beginning_Installation-x86.xml:49
+#, no-c-format
+msgid "SCSI"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation-x86.xml:55
+#, no-c-format
+msgid ""
+"If the DVD/CD-ROM drive is found and the driver loaded, the installer will "
+"present you with the option to perform a media check on the DVD/CD-ROM. This "
+"will take some time, and you may opt to skip over this step. However, if you "
+"later encounter problems with the installer, you should reboot and perform "
+"the media check before calling for support. From the media check dialog, "
+"continue to the next stage of the installation process (refer to <xref "
+"linkend=\"sn-welcome-x86\"/>)."
+msgstr ""
+
+#. Tag: primary
+#: Beginning_Installation_x86_ppc-indexterm-10.xml:9
+#, no-c-format
+msgid "ATAPI CD-ROM"
+msgstr ""
+
+#. Tag: secondary
+#: Beginning_Installation_x86_ppc-indexterm-11.xml:10
+#, no-c-format
+msgid "problems"
+msgstr ""
+
+#. Tag: tertiary
+#: Beginning_Installation_x86_ppc-indexterm-11.xml:11
+#, no-c-format
+msgid "IDE CD-ROM related"
+msgstr ""
+
+#. Tag: secondary
+#: Beginning_Installation_x86_ppc-indexterm-6.xml:10
+#, no-c-format
+msgid "installation from"
+msgstr ""
+
+#. Tag: primary
+#: Beginning_Installation_x86_ppc-indexterm-9.xml:9
+#, no-c-format
+msgid "IDE CD-ROM"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-itemizedlist-1.xml:10
+#, no-c-format
+msgid "<command>a</command> — first IDE controller, master"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-itemizedlist-1.xml:16
+#, no-c-format
+msgid "<command>b</command> — first IDE controller, slave"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-itemizedlist-1.xml:22
+#, no-c-format
+msgid "<command>c</command> — second IDE controller, master"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-itemizedlist-1.xml:28
+#, no-c-format
+msgid "<command>d</command> — second IDE controller, slave"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-para-1.xml:5
+#, no-c-format
+msgid ""
+"To install Fedora from a DVD/CD-ROM, place the DVD or CD #1 in your DVD/CD-"
+"ROM drive and boot your system from the DVD/CD-ROM. Even if you booted from "
+"alternative media, you can still install Fedora from CD or DVD media."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-para-3.xml:8
+#, no-c-format
+msgid ""
+"If your CD-ROM drive is not detected, and it is a SCSI CD-ROM, 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."
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-para-4.xml:8
+#, no-c-format
+msgid ""
+"If you have an IDE (ATAPI) DVD/CD-ROM but the installation program fails to "
+"find it and asks you what type of DVD/CD-ROM drive you have, try the "
+"following boot command. Restart the installation, and at the <prompt>boot:</"
+"prompt> prompt enter <userinput>linux hd<replaceable>X</replaceable>=cdrom</"
+"userinput>. Replace <userinput><replaceable>X</replaceable></userinput> with "
+"one of the following letters, depending on the interface the unit is "
+"connected to, and whether it is configured as master or slave (also known as "
+"primary and secondary):"
+msgstr ""
+
+#. Tag: para
+#: Beginning_Installation_x86_ppc-para-5.xml:8
+#, no-c-format
+msgid ""
+"If you have a third and/or fourth controller, continue assigning letters in "
+"alphabetical order, going from controller to controller, and master to slave."
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_x86_ppc-title-1.xml:8
+#, no-c-format
+msgid "Installing from DVD/CD-ROM"
+msgstr ""
+
+#. Tag: title
+#: Beginning_Installation_x86_ppc-title-2.xml:9
+#, no-c-format
+msgid "What If the IDE CD-ROM Was Not Found?"
+msgstr ""
+
+#. Tag: title
+#: Book_Info.xml:5
+#, no-c-format
+msgid "Installation Guide"
+msgstr ""
+
+#. Tag: subtitle
+#: Book_Info.xml:6
+#, no-c-format
+msgid ""
+"Installing Fedora 11 on x86, AMD64, and <trademark class=\"registered"
+"\">Intel</trademark> 64 architectures"
+msgstr ""
+
+#. Tag: para
+#: Book_Info.xml:12
+#, no-c-format
+msgid "Provides documentation for the installation process."
+msgstr ""
+
+#. Tag: phrase
+#: Book_Info.xml:19
+#, no-c-format
+msgid "Logo"
+msgstr ""
+
+#. Tag: holder
+#: Book_Info.xml:24
+#, no-c-format
+msgid "&HOLDER;"
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:5
+#, no-c-format
+msgid "Boot Process, Init, and Shutdown"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:10
+#, no-c-format
+msgid ""
+"An important and powerful aspect of Fedora is the open, user-configurable "
+"method it uses for starting the operating system. Users are free to "
+"configure many aspects of the boot process, including specifying the "
+"programs launched at boot-time. Similarly, system shutdown gracefully "
+"terminates processes in an organized and configurable way, although "
+"customization of this process is rarely required."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:13
+#, no-c-format
+msgid ""
+"Understanding how the boot and shutdown processes work not only allows "
+"customization, but also makes it easier to troubleshoot problems related to "
+"starting or shutting down the system."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:17
+#, no-c-format
+msgid "The Boot Process"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:20 Boot_Init_Shutdown.xml:80
+#: Boot_Init_Shutdown.xml:108 Boot_Init_Shutdown.xml:113
+#: Boot_Init_Shutdown.xml:151 Boot_Init_Shutdown.xml:259
+#: Boot_Init_Shutdown.xml:296
+#, no-c-format
+msgid "stages of"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:22
+#, no-c-format
+msgid "Below are the basic stages of the boot process for an x86 system:"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:28
+#, no-c-format
+msgid ""
+"The system BIOS checks the system and launches the first stage boot loader "
+"on the MBR of the primary hard disk."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:34
+#, no-c-format
+msgid ""
+"The first stage boot loader loads itself into memory and launches the second "
+"stage boot loader from the <filename>/boot/</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:40
+#, no-c-format
+msgid ""
+"The second stage boot loader loads the kernel into memory, which in turn "
+"loads any necessary modules and mounts the root partition read-only."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:46
+#, no-c-format
+msgid ""
+"The kernel transfers control of the boot process to the <command>/sbin/init</"
+"command> program."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:52
+#, no-c-format
+msgid ""
+"The <command>/sbin/init</command> program loads all services and user-space "
+"tools, and mounts all partitions listed in <filename>/etc/fstab</filename>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:58
+#, no-c-format
+msgid ""
+"The user is presented with a login screen for the freshly booted Linux "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:64
+#, no-c-format
+msgid ""
+"Because configuration of the boot process is more common than the "
+"customization of the shutdown process, the remainder of this chapter "
+"discusses in detail how the boot process works and how it can be customized "
+"to suite specific needs."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:69
+#, no-c-format
+msgid "A Detailed Look at the Boot Process"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:72
+#, no-c-format
+msgid "for x86"
+msgstr ""
+
+#. Tag: see
+#: Boot_Init_Shutdown.xml:84 Boot_Init_Shutdown.xml:127
+#, no-c-format
+msgid "<see>MBR</see>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:88 Boot_Init_Shutdown.xml:103
+#: Boot_Init_Shutdown.xml:122 Boot_Init_Shutdown.xml:131
+#, no-c-format
+msgid "<secondary>definition of</secondary>"
+msgstr ""
+
+#. Tag: seealso
+#: Boot_Init_Shutdown.xml:89 Boot_Init_Shutdown.xml:104
+#: Boot_Init_Shutdown.xml:123 Boot_Init_Shutdown.xml:288
+#: Boot_Init_Shutdown.xml:292
+#, no-c-format
+msgid "<seealso>boot process</seealso>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:91
+#, no-c-format
+msgid ""
+"The beginning of the boot process varies depending on the hardware platform "
+"being used. However, once the kernel is found and loaded by the boot loader, "
+"the default boot process is identical across all architectures. This chapter "
+"focuses primarily on the x86 architecture."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:96
+#, no-c-format
+msgid "The BIOS"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:98
+#, no-c-format
+msgid "Extensible Firmware Interface shell"
+msgstr ""
+
+#. Tag: see
+#: Boot_Init_Shutdown.xml:99
+#, no-c-format
+msgid "<see>EFI shell</see>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:102
+#, no-c-format
+msgid "<primary>EFI shell</primary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:109
+#, no-c-format
+msgid "<tertiary>BIOS</tertiary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:114
+#, no-c-format
+msgid "<tertiary>EFI shell</tertiary>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:117
+#, no-c-format
+msgid "Basic Input/Output System"
+msgstr ""
+
+#. Tag: see
+#: Boot_Init_Shutdown.xml:118
+#, no-c-format
+msgid "<see>BIOS</see>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:121
+#, no-c-format
+msgid "<primary>BIOS</primary>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:134
+#, no-c-format
+msgid ""
+"When an x86 computer is booted, the processor looks at the end of system "
+"memory for the <firstterm>Basic Input/Output System</firstterm> or "
+"<firstterm>BIOS</firstterm> program and runs it. The BIOS controls not only "
+"the first step of the boot process, but also provides the lowest level "
+"interface to peripheral devices. For this reason it is written into read-"
+"only, permanent memory and is always available for use."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:138
+#, no-c-format
+msgid ""
+"Other platforms use different programs to perform low-level tasks roughly "
+"equivalent to those of the BIOS on an x86 system. For instance, Itanium-"
+"based computers use the <firstterm>Extensible Firmware Interface</firstterm> "
+"(<firstterm>EFI</firstterm>) <firstterm>Shell</firstterm>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:142
+#, no-c-format
+msgid ""
+"Once loaded, the BIOS tests the system, looks for and checks peripherals, "
+"and then locates a valid device with which to boot the system. Usually, it "
+"checks any diskette drives and CD-ROM drives present for bootable media, "
+"then, failing that, looks to the system's hard drives. In most cases, the "
+"order of the drives searched while booting is controlled with a setting in "
+"the BIOS, and it looks on the master IDE device on the primary IDE bus. The "
+"BIOS then loads into memory whatever program is residing in the first sector "
+"of this device, called the <firstterm>Master Boot Record</firstterm> or "
+"<firstterm>MBR</firstterm>. The MBR is only 512 bytes in size and contains "
+"machine code instructions for booting the machine, called a boot loader, "
+"along with the partition table. Once the BIOS finds and loads the boot "
+"loader program into memory, it yields control of the boot process to it."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:148
+#, no-c-format
+msgid "The Boot Loader"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:155 Boot_Init_Shutdown.xml:159
+#, no-c-format
+msgid "GRUB"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:156 Boot_Init_Shutdown.xml:168
+#: Boot_Init_Shutdown.xml:264 Boot_Init_Shutdown.xml:287
+#, no-c-format
+msgid "role in boot process"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:163 Boot_Init_Shutdown.xml:167
+#, no-c-format
+msgid "LILO"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:170
+#, no-c-format
+msgid ""
+"This section looks at the default boot loader for the x86 platform, GRUB. "
+"For more information about configuring and using GRUB, see <xref linkend="
+"\"ch-grub\"/>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:174
+#, no-c-format
+msgid ""
+"A boot loader for the x86 platform is broken into at least two stages. The "
+"first stage is a small machine code binary on the MBR. Its sole job is to "
+"locate the second stage boot loader and load the first part of it into "
+"memory."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:178
+#, no-c-format
+msgid ""
+"GRUB has the advantage of being able to read ext2 and ext3 <footnote> <para> "
+"GRUB reads ext3 file systems as ext2, disregarding the journal file. Refer "
+"to the chapter titled <citetitle>The ext3 File System</citetitle> in the "
+"<citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle> for more "
+"information on the ext3 file system. </para> </footnote> partitions and load "
+"its configuration file — <filename>/boot/grub/grub.conf</filename> "
+"— at boot time. Refer to <xref linkend=\"s1-grub-configfile\"/> for "
+"information on how to edit this file."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:187
+#, no-c-format
+msgid ""
+"The <application>GRUB</application> bootloader does not support the ext4 or "
+"Btrfs file systems."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:192
+#, no-c-format
+msgid ""
+"If upgrading the kernel using the <application>Red Hat Update Agent</"
+"application>, the boot loader configuration file is updated automatically. "
+"More information on Red Hat Network can be found online at the following "
+"URL: <ulink url=\"https://rhn.redhat.com/\">https://rhn.redhat.com/</ulink>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:196
+#, no-c-format
+msgid ""
+"Once the second stage boot loader is in memory, it presents the user with a "
+"graphical screen showing the different operating systems or kernels it has "
+"been configured to boot. On this screen a user can use the arrow keys to "
+"choose which operating system or kernel they wish to boot and press "
+"<keycap>Enter</keycap>. If no key is pressed, the boot loader loads the "
+"default selection after a configurable period of time has passed."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:212
+#, no-c-format
+msgid ""
+"Once the second stage boot loader has determined which kernel to boot, it "
+"locates the corresponding kernel binary in the <filename>/boot/</filename> "
+"directory. The kernel binary is named using the following format — "
+"<filename>/boot/vmlinuz-<replaceable><kernel-version></replaceable></"
+"filename> file (where <filename><replaceable><kernel-version></"
+"replaceable></filename> corresponds to the kernel version specified in the "
+"boot loader's settings)."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:216
+#, no-c-format
+msgid ""
+"For instructions on using the boot loader to supply command line arguments "
+"to the kernel, refer to <xref linkend=\"ch-grub\"/>. For information on "
+"changing the runlevel at the boot loader prompt, refer <xref linkend=\"s1-"
+"grub-runlevels\"/>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:220
+#, no-c-format
+msgid ""
+"The boot loader then places one or more appropriate <firstterm>initramfs</"
+"firstterm> images into memory. Next, the kernel decompresses these images "
+"from memory to <filename>/sysroot/</filename>, a RAM-based virtual file "
+"system, via <command>cpio</command>. The <filename>initramfs</filename> is "
+"used by the kernel to load drivers and modules necessary to boot the system. "
+"This is particularly important if SCSI hard drives are present or if the "
+"systems use the ext3 or ext4 file system."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:224
+#, no-c-format
+msgid ""
+"Once the kernel and the <filename>initramfs</filename> image(s) are loaded "
+"into memory, the boot loader hands control of the boot process to the kernel."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:228
+#, no-c-format
+msgid ""
+"For a more detailed overview of the GRUB boot loader, refer to <xref linkend="
+"\"ch-grub\"/>."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:256
+#, no-c-format
+msgid "The Kernel"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:260
+#, no-c-format
+msgid "<tertiary>kernel</tertiary>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:263
+#, no-c-format
+msgid "<primary>kernel</primary>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:266
+#, no-c-format
+msgid ""
+"When the kernel is loaded, it immediately initializes and configures the "
+"computer's memory and configures the various hardware attached to the "
+"system, including all processors, I/O subsystems, and storage devices. It "
+"then looks for the compressed <filename>initramfs</filename> image(s) in a "
+"predetermined location in memory, decompresses it directly to <filename>/"
+"sysroot/</filename>, and loads all necessary drivers. Next, it initializes "
+"virtual devices related to the file system, such as LVM or software RAID, "
+"before completing the <filename>initramfs</filename> processes and freeing "
+"up all the memory the disk image once occupied."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:270
+#, no-c-format
+msgid ""
+"The kernel then creates a root device, mounts the root partition read-only, "
+"and frees any unused memory."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:274
+#, no-c-format
+msgid ""
+"At this point, the kernel is loaded into memory and operational. However, "
+"since there are no user applications that allow meaningful input to the "
+"system, not much can be done with the system."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:278
+#, no-c-format
+msgid ""
+"To set up the user environment, the kernel executes the <command>/sbin/init</"
+"command> program."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:284
+#, no-c-format
+msgid "The <command>/sbin/init</command> Program"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:286 Boot_Init_Shutdown.xml:291
+#: Boot_Init_Shutdown.xml:418 Boot_Init_Shutdown.xml:423
+#: Boot_Init_Shutdown.xml:428 Boot_Init_Shutdown.xml:452
+#, no-c-format
+msgid "<primary><command>init</command> command</primary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:297
+#, no-c-format
+msgid "<command>/sbin/init</command> command"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:299
+#, no-c-format
+msgid ""
+"The <command>/sbin/init</command> program (also called <command>init</"
+"command>) coordinates the rest of the boot process and configures the "
+"environment for the user."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:303
+#, no-c-format
+msgid ""
+"When the <command>init</command> command starts, it becomes the parent or "
+"grandparent of all of the processes that start up automatically on the "
+"system. First, it runs the <filename>/etc/rc.d/rc.sysinit</filename> script, "
+"which sets the environment path, starts swap, checks the file systems, and "
+"executes all other steps required for system initialization. For example, "
+"most systems use a clock, so <filename>rc.sysinit</filename> reads the "
+"<filename>/etc/sysconfig/clock</filename> configuration file to initialize "
+"the hardware clock. Another example is if there are special serial port "
+"processes which must be initialized, <filename>rc.sysinit</filename> "
+"executes the <filename>/etc/rc.serial</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:308
+#, no-c-format
+msgid ""
+"The <command>init</command> command then runs the <filename>/etc/inittab</"
+"filename> script, which describes how the system should be set up in each "
+"<firstterm>SysV init runlevel</firstterm>. Runlevels are a state, or "
+"<firstterm>mode</firstterm>, defined by the services listed in the SysV "
+"<filename>/etc/rc.d/rc<replaceable><x></replaceable>.d/</filename> "
+"directory, where <replaceable><x></replaceable> is the number of the "
+"runlevel. For more information on SysV init runlevels, refer to <xref "
+"linkend=\"s1-boot-init-shutdown-sysv\"/>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:312
+#, no-c-format
+msgid ""
+"Next, the <command>init</command> command sets the source function library, "
+"<filename>/etc/rc.d/init.d/functions</filename>, for the system, which "
+"configures how to start, kill, and determine the PID of a program."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:316
+#, no-c-format
+msgid ""
+"The <command>init</command> program starts all of the background processes "
+"by looking in the appropriate <filename>rc</filename> directory for the "
+"runlevel specified as the default in <filename>/etc/inittab</filename>. The "
+"<filename>rc</filename> directories are numbered to correspond to the "
+"runlevel they represent. For instance, <filename>/etc/rc.d/rc5.d/</filename> "
+"is the directory for runlevel 5."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:322
+#, no-c-format
+msgid ""
+"When booting to runlevel 5, the <command>init</command> program looks in the "
+"<filename>/etc/rc.d/rc5.d/</filename> directory to determine which processes "
+"to start and stop."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:326
+#, no-c-format
+msgid ""
+"Below is an example listing of the <filename>/etc/rc.d/rc5.d/</filename> "
+"directory:"
+msgstr ""
+
+#. Tag: screen
+#: Boot_Init_Shutdown.xml:329
+#, no-c-format
+msgid ""
+"K05innd -> ../init.d/innd \n"
+"K05saslauthd -> ../init.d/saslauthd \n"
+"K10dc_server -> ../init.d/dc_server \n"
+"K10psacct -> ../init.d/psacct \n"
+"K10radiusd -> ../init.d/radiusd \n"
+"K12dc_client -> ../init.d/dc_client \n"
+"K12FreeWnn -> ../init.d/FreeWnn \n"
+"K12mailman -> ../init.d/mailman \n"
+"K12mysqld -> ../init.d/mysqld \n"
+"K15httpd -> ../init.d/httpd \n"
+"K20netdump-server -> ../init.d/netdump-server \n"
+"K20rstatd -> ../init.d/rstatd \n"
+"K20rusersd -> ../init.d/rusersd \n"
+"K20rwhod -> ../init.d/rwhod \n"
+"K24irda -> ../init.d/irda \n"
+"K25squid -> ../init.d/squid \n"
+"K28amd -> ../init.d/amd \n"
+"K30spamassassin -> ../init.d/spamassassin \n"
+"K34dhcrelay -> ../init.d/dhcrelay \n"
+"K34yppasswdd -> ../init.d/yppasswdd \n"
+"K35dhcpd -> ../init.d/dhcpd \n"
+"K35smb -> ../init.d/smb \n"
+"K35vncserver -> ../init.d/vncserver \n"
+"K36lisa -> ../init.d/lisa \n"
+"K45arpwatch -> ../init.d/arpwatch \n"
+"K45named -> ../init.d/named \n"
+"K46radvd -> ../init.d/radvd \n"
+"K50netdump -> ../init.d/netdump \n"
+"K50snmpd -> ../init.d/snmpd \n"
+"K50snmptrapd -> ../init.d/snmptrapd \n"
+"K50tux -> ../init.d/tux \n"
+"K50vsftpd -> ../init.d/vsftpd \n"
+"K54dovecot -> ../init.d/dovecot \n"
+"K61ldap -> ../init.d/ldap \n"
+"K65kadmin -> ../init.d/kadmin \n"
+"K65kprop -> ../init.d/kprop \n"
+"K65krb524 -> ../init.d/krb524 \n"
+"K65krb5kdc -> ../init.d/krb5kdc \n"
+"K70aep1000 -> ../init.d/aep1000 \n"
+"K70bcm5820 -> ../init.d/bcm5820 \n"
+"K74ypserv -> ../init.d/ypserv \n"
+"K74ypxfrd -> ../init.d/ypxfrd \n"
+"K85mdmpd -> ../init.d/mdmpd \n"
+"K89netplugd -> ../init.d/netplugd \n"
+"K99microcode_ctl -> ../init.d/microcode_ctl \n"
+"S04readahead_early -> ../init.d/readahead_early \n"
+"S05kudzu -> ../init.d/kudzu \n"
+"S06cpuspeed -> ../init.d/cpuspeed \n"
+"S08ip6tables -> ../init.d/ip6tables \n"
+"S08iptables -> ../init.d/iptables \n"
+"S09isdn -> ../init.d/isdn \n"
+"S10network -> ../init.d/network \n"
+"S12syslog -> ../init.d/syslog \n"
+"S13irqbalance -> ../init.d/irqbalance \n"
+"S13portmap -> ../init.d/portmap \n"
+"S15mdmonitor -> ../init.d/mdmonitor \n"
+"S15zebra -> ../init.d/zebra \n"
+"S16bgpd -> ../init.d/bgpd \n"
+"S16ospf6d -> ../init.d/ospf6d \n"
+"S16ospfd -> ../init.d/ospfd \n"
+"S16ripd -> ../init.d/ripd \n"
+"S16ripngd -> ../init.d/ripngd \n"
+"S20random -> ../init.d/random \n"
+"S24pcmcia -> ../init.d/pcmcia \n"
+"S25netfs -> ../init.d/netfs \n"
+"S26apmd -> ../init.d/apmd \n"
+"S27ypbind -> ../init.d/ypbind \n"
+"S28autofs -> ../init.d/autofs \n"
+"S40smartd -> ../init.d/smartd \n"
+"S44acpid -> ../init.d/acpid \n"
+"S54hpoj -> ../init.d/hpoj \n"
+"S55cups -> ../init.d/cups \n"
+"S55sshd -> ../init.d/sshd \n"
+"S56rawdevices -> ../init.d/rawdevices \n"
+"S56xinetd -> ../init.d/xinetd \n"
+"S58ntpd -> ../init.d/ntpd \n"
+"S75postgresql -> ../init.d/postgresql \n"
+"S80sendmail -> ../init.d/sendmail \n"
+"S85gpm -> ../init.d/gpm \n"
+"S87iiim -> ../init.d/iiim \n"
+"S90canna -> ../init.d/canna \n"
+"S90crond -> ../init.d/crond \n"
+"S90xfs -> ../init.d/xfs \n"
+"S95atd -> ../init.d/atd \n"
+"S96readahead -> ../init.d/readahead \n"
+"S97messagebus -> ../init.d/messagebus \n"
+"S97rhnsd -> ../init.d/rhnsd \n"
+"S99local -> ../rc.local"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:330
+#, no-c-format
+msgid ""
+"As illustrated in this listing, none of the scripts that actually start and "
+"stop the services are located in the <filename>/etc/rc.d/rc5.d/</filename> "
+"directory. Rather, all of the files in <filename>/etc/rc.d/rc5.d/</filename> "
+"are <firstterm>symbolic links</firstterm> pointing to scripts located in the "
+"<filename>/etc/rc.d/init.d/</filename> directory. Symbolic links are used in "
+"each of the <filename>rc</filename> directories so that the runlevels can be "
+"reconfigured by creating, modifying, and deleting the symbolic links without "
+"affecting the actual scripts they reference."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:334
+#, no-c-format
+msgid ""
+"The name of each symbolic link begins with either a <computeroutput>K</"
+"computeroutput> or an <computeroutput>S</computeroutput>. The "
+"<computeroutput>K</computeroutput> links are processes that are killed on "
+"that runlevel, while those beginning with an <computeroutput>S</"
+"computeroutput> are started."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:338
+#, no-c-format
+msgid ""
+"The <command>init</command> command first stops all of the "
+"<computeroutput>K</computeroutput> symbolic links in the directory by "
+"issuing the <command>/etc/rc.d/init.d/<replaceable><command></"
+"replaceable> stop</command> command, where <replaceable><command></"
+"replaceable> is the process to be killed. It then starts all of the "
+"<computeroutput>S</computeroutput> symbolic links by issuing <command>/etc/"
+"rc.d/init.d/<replaceable><command></replaceable> start</command>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:342
+#, no-c-format
+msgid ""
+"After the system is finished booting, it is possible to log in as root and "
+"execute these same scripts to start and stop services. For instance, the "
+"command <command>/etc/rc.d/init.d/httpd stop</command> stops the Apache HTTP "
+"Server."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:346
+#, no-c-format
+msgid ""
+"Each of the symbolic links are numbered to dictate start order. The order in "
+"which the services are started or stopped can be altered by changing this "
+"number. The lower the number, the earlier it is started. Symbolic links with "
+"the same number are started alphabetically."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:353
+#, no-c-format
+msgid ""
+"One of the last things the <command>init</command> program executes is the "
+"<filename>/etc/rc.d/rc.local</filename> file. This file is useful for system "
+"customization. Refer to <xref linkend=\"s1-boot-init-shutdown-run-boot\"/> "
+"for more information about using the <filename>rc.local</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:358
+#, no-c-format
+msgid ""
+"After the <command>init</command> command has progressed through the "
+"appropriate <filename>rc</filename> directory for the runlevel, the "
+"<filename>/etc/inittab</filename> script forks an <command>/sbin/mingetty</"
+"command> process for each virtual console (login prompt) allocated to the "
+"runlevel. Runlevels 2 through 5 have all six virtual consoles, while "
+"runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The "
+"<command>/sbin/mingetty</command> process opens communication pathways to "
+"<firstterm>tty</firstterm> devices<footnote> <para> Refer to the Red Hat "
+"Enterprise Linux Deployment Guide for more information about <filename>tty</"
+"filename> devices. </para> </footnote>, sets their modes, prints the login "
+"prompt, accepts the user's username and password, and initiates the login "
+"process."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:366
+#, no-c-format
+msgid ""
+"In runlevel 5, the <filename>/etc/inittab</filename> runs a script called "
+"<filename>/etc/X11/prefdm</filename>. The <filename>prefdm</filename> script "
+"executes the preferred X display manager<footnote> <para> Refer to the Red "
+"Hat Enterprise Linux Deployment Guide for more information about display "
+"managers. </para> </footnote> — <command>gdm</command>, <command>kdm</"
+"command>, or <command>xdm</command>, depending on the contents of the "
+"<filename>/etc/sysconfig/desktop</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:374
+#, no-c-format
+msgid ""
+"Once finished, the system operates on runlevel 5 and displays a login screen."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:380
+#, no-c-format
+msgid "Running Additional Programs at Boot Time"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:382
+#, no-c-format
+msgid "programs"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:383
+#, no-c-format
+msgid "running at boot time"
+msgstr ""
+
+#. Tag: filename
+#: Boot_Init_Shutdown.xml:386
+#, no-c-format
+msgid "rc.local"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:388
+#, no-c-format
+msgid "modifying"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:391
+#, no-c-format
+msgid "<primary><command>setserial</command> command</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:392
+#, no-c-format
+msgid "configuring"
+msgstr ""
+
+#. Tag: filename
+#: Boot_Init_Shutdown.xml:395
+#, no-c-format
+msgid "rc.serial"
+msgstr ""
+
+#. Tag: seealso
+#: Boot_Init_Shutdown.xml:397
+#, no-c-format
+msgid "<seealso><command>setserial</command> command</seealso>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:400
+#, no-c-format
+msgid "serial ports"
+msgstr ""
+
+#. Tag: see
+#: Boot_Init_Shutdown.xml:401
+#, no-c-format
+msgid "<see><command>setserial</command> command</see>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:403
+#, no-c-format
+msgid ""
+"The <filename>/etc/rc.d/rc.local</filename> script is executed by the "
+"<command>init</command> command at boot time or when changing runlevels. "
+"Adding commands to the bottom of this script is an easy way to perform "
+"necessary tasks like starting special services or initialize devices without "
+"writing complex initialization scripts in the <filename>/etc/rc.d/init.d/</"
+"filename> directory and creating symbolic links."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:407
+#, no-c-format
+msgid ""
+"The <filename>/etc/rc.serial</filename> script is used if serial ports must "
+"be setup at boot time. This script runs <command>setserial</command> "
+"commands to configure the system's serial ports. Refer to the "
+"<command>setserial</command> man page for more information."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:412
+#, no-c-format
+msgid "SysV Init Runlevels"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:414
+#, no-c-format
+msgid "<primary>SysV init</primary>"
+msgstr ""
+
+#. Tag: see
+#: Boot_Init_Shutdown.xml:415 Boot_Init_Shutdown.xml:449
+#, no-c-format
+msgid "<see><command>init</command> command</see>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:419
+#, no-c-format
+msgid "<secondary>runlevels</secondary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:420
+#, no-c-format
+msgid "directories for"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:424
+#, no-c-format
+msgid "<secondary>SysV init</secondary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Boot_Init_Shutdown.xml:425
+#, no-c-format
+msgid "<tertiary>definition of</tertiary>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:429
+#, no-c-format
+msgid "configuration files"
+msgstr ""
+
+#. Tag: filename
+#: Boot_Init_Shutdown.xml:430
+#, no-c-format
+msgid "/etc/inittab"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:433
+#, no-c-format
+msgid ""
+"The SysV init runlevel system provides a standard process for controlling "
+"which programs <command>init</command> launches or halts when initializing a "
+"runlevel. SysV init was chosen because it is easier to use and more flexible "
+"than the traditional BSD-style init process."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:437
+#, no-c-format
+msgid ""
+"The configuration files for SysV init are located in the <filename>/etc/rc.d/"
+"</filename> directory. Within this directory, are the <filename>rc</"
+"filename>, <filename>rc.local</filename>, <filename>rc.sysinit</filename>, "
+"and, optionally, the <filename>rc.serial</filename> scripts as well as the "
+"following directories:"
+msgstr ""
+
+#. Tag: screen
+#: Boot_Init_Shutdown.xml:440
+#, no-c-format
+msgid ""
+"<computeroutput>init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/</"
+"computeroutput>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:441
+#, no-c-format
+msgid ""
+"The <filename>init.d/</filename> directory contains the scripts used by the "
+"<command>/sbin/init</command> command when controlling services. Each of the "
+"numbered directories represent the six runlevels configured by default under "
+"Fedora."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:446
+#, no-c-format
+msgid "Runlevels"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:448 Boot_Init_Shutdown.xml:543
+#, no-c-format
+msgid "<primary>runlevels</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:453
+#, no-c-format
+msgid "runlevels accessed by"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:455
+#, no-c-format
+msgid ""
+"The idea behind SysV init runlevels revolves around the idea that different "
+"systems can be used in different ways. For example, a server runs more "
+"efficiently without the drag on system resources created by the X Window "
+"System. Or there may be times when a system administrator may need to "
+"operate the system at a lower runlevel to perform diagnostic tasks, like "
+"fixing disk corruption in runlevel 1."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:459
+#, no-c-format
+msgid ""
+"The characteristics of a given runlevel determine which services are halted "
+"and started by <command>init</command>. For instance, runlevel 1 (single "
+"user mode) halts any network services, while runlevel 3 starts these "
+"services. By assigning specific services to be halted or started on a given "
+"runlevel, <command>init</command> can quickly change the mode of the machine "
+"without the user manually stopping and starting services."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:463
+#, no-c-format
+msgid "The following runlevels are defined by default under Fedora:"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:468
+#, no-c-format
+msgid "<command>0</command> — Halt"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:474
+#, no-c-format
+msgid "<command>1</command> — Single-user text mode"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:480
+#, no-c-format
+msgid "<command>2</command> — Not used (user-definable)"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:486
+#, no-c-format
+msgid "<command>3</command> — Full multi-user text mode"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:492
+#, no-c-format
+msgid "<command>4</command> — Not used (user-definable)"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:498
+#, no-c-format
+msgid ""
+"<command>5</command> — Full multi-user graphical mode (with an X-based "
+"login screen)"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:504
+#, no-c-format
+msgid "<command>6</command> — Reboot"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:510
+#, no-c-format
+msgid ""
+"In general, users operate Fedora at runlevel 3 or runlevel 5 — both "
+"full multi-user modes. Users sometimes customize runlevels 2 and 4 to meet "
+"specific needs, since they are not used."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:514
+#, no-c-format
+msgid ""
+"The default runlevel for the system is listed in <filename>/etc/inittab</"
+"filename>. To find out the default runlevel for a system, look for the line "
+"similar to the following near the top of <filename>/etc/inittab</filename>:"
+msgstr ""
+
+#. Tag: screen
+#: Boot_Init_Shutdown.xml:518
+#, no-c-format
+msgid "<computeroutput>id:5:initdefault:</computeroutput>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:519
+#, no-c-format
+msgid ""
+"The default runlevel listed in this example is five, as the number after the "
+"first colon indicates. To change it, edit <filename>/etc/inittab</filename> "
+"as root."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:526
+#, no-c-format
+msgid ""
+"Be very careful when editing <filename>/etc/inittab</filename>. Simple typos "
+"can cause the system to become unbootable. If this happens, either use a "
+"boot diskette, enter single-user mode, or enter rescue mode to boot the "
+"computer and repair the file."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:530
+#, no-c-format
+msgid ""
+"For more information on single-user and rescue mode, refer to the chapter "
+"titled <citetitle>Basic System Recovery</citetitle> in the <citetitle>Red "
+"Hat Enterprise Linux Deployment Guide</citetitle>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:535
+#, no-c-format
+msgid ""
+"It is possible to change the default runlevel at boot time by modifying the "
+"arguments passed by the boot loader to the kernel. For information on "
+"changing the runlevel at boot time, refer to <xref linkend=\"s1-grub-"
+"runlevels\"/>."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:541
+#, no-c-format
+msgid "Runlevel Utilities"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:544
+#, no-c-format
+msgid "configuration of"
+msgstr ""
+
+#. Tag: seealso
+#: Boot_Init_Shutdown.xml:545 Boot_Init_Shutdown.xml:550
+#: Boot_Init_Shutdown.xml:560 Boot_Init_Shutdown.xml:575
+#, no-c-format
+msgid "<seealso>services</seealso>"
+msgstr ""
+
+#. Tag: application
+#: Boot_Init_Shutdown.xml:548
+#, no-c-format
+msgid "Services Configuration Tool"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:553 Boot_Init_Shutdown.xml:563
+#: Boot_Init_Shutdown.xml:568
+#, no-c-format
+msgid "<primary>services</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:554
+#, no-c-format
+msgid "configuring with <application>Services Configuration Tool</application>"
+msgstr ""
+
+#. Tag: application
+#: Boot_Init_Shutdown.xml:558
+#, no-c-format
+msgid "ntsysv"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:564
+#, no-c-format
+msgid "configuring with <application>ntsysv</application>"
+msgstr ""
+
+#. Tag: secondary
+#: Boot_Init_Shutdown.xml:569
+#, no-c-format
+msgid "configuring with <command>chkconfig</command>"
+msgstr ""
+
+#. Tag: command
+#: Boot_Init_Shutdown.xml:573
+#, no-c-format
+msgid "chkconfig"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:577
+#, no-c-format
+msgid ""
+"One of the best ways to configure runlevels is to use an "
+"<firstterm>initscript utility</firstterm>. These tools are designed to "
+"simplify the task of maintaining files in the SysV init directory hierarchy "
+"and relieves system administrators from having to directly manipulate the "
+"numerous symbolic links in the subdirectories of <filename>/etc/rc.d/</"
+"filename>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:581
+#, no-c-format
+msgid "Fedora provides three such utilities:"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:587
+#, no-c-format
+msgid ""
+"<command>/sbin/chkconfig</command> — The <command>/sbin/chkconfig</"
+"command> utility is a simple command line tool for maintaining the "
+"<filename>/etc/rc.d/init.d/</filename> directory hierarchy."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:593
+#, no-c-format
+msgid ""
+"<application>/usr/sbin/ntsysv</application> — The ncurses-based "
+"<application>/sbin/ntsysv</application> utility provides an interactive text-"
+"based interface, which some find easier to use than <command>chkconfig</"
+"command>."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:599
+#, no-c-format
+msgid ""
+"<application>Services Configuration Tool</application> — The graphical "
+"<application>Services Configuration Tool</application> (<command>system-"
+"config-services</command>) program is a flexible utility for configuring "
+"runlevels."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:605
+#, no-c-format
+msgid ""
+"Refer to the chapter titled <citetitle>Controlling Access to Services</"
+"citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</"
+"citetitle> for more information regarding these tools."
+msgstr ""
+
+#. Tag: title
+#: Boot_Init_Shutdown.xml:611
+#, no-c-format
+msgid "Shutting Down"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:613
+#, no-c-format
+msgid "<primary>shutdown</primary>"
+msgstr ""
+
+#. Tag: seealso
+#: Boot_Init_Shutdown.xml:614
+#, no-c-format
+msgid "<seealso>halt</seealso>"
+msgstr ""
+
+#. Tag: primary
+#: Boot_Init_Shutdown.xml:617
+#, no-c-format
+msgid "<primary>halt</primary>"
+msgstr ""
+
+#. Tag: seealso
+#: Boot_Init_Shutdown.xml:618
+#, no-c-format
+msgid "<seealso>shutdown</seealso>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:620
+#, no-c-format
+msgid ""
+"To shut down Fedora, the root user may issue the <command>/sbin/shutdown</"
+"command> command. The <command>shutdown</command> man page has a complete "
+"list of options, but the two most common uses are:"
+msgstr ""
+
+#. Tag: screen
+#: Boot_Init_Shutdown.xml:623
+#, no-c-format
+msgid ""
+"<command>/sbin/shutdown -h now</command> <command>/sbin/shutdown -r now</"
+"command>"
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:624
+#, no-c-format
+msgid ""
+"After shutting everything down, the <command>-h</command> option halts the "
+"machine, and the <command>-r</command> option reboots."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:628
+#, no-c-format
+msgid ""
+"PAM console users can use the <command>reboot</command> and <command>halt</"
+"command> commands to shut down the system while in runlevels 1 through 5. "
+"For more information about PAM console users, refer to the Red Hat "
+"Enterprise Linux Deployment Guide."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:632
+#, no-c-format
+msgid ""
+"If the computer does not power itself down, be careful not to turn off the "
+"computer until a message appears indicating that the system is halted."
+msgstr ""
+
+#. Tag: para
+#: Boot_Init_Shutdown.xml:636
+#, no-c-format
+msgid ""
+"Failure to wait for this message can mean that not all the hard drive "
+"partitions are unmounted, which can lead to file system corruption."
+msgstr ""
+
+#. Tag: para
+#: Complete_common-para-1.xml:5
+#, no-c-format
+msgid "Congratulations! Your Fedora installation is now complete!"
+msgstr ""
+
+#. Tag: title
+#: Complete_common-title-1.xml:8
+#, no-c-format
+msgid "Installation Complete"
+msgstr ""
+
+#. Tag: para
+#: Complete_x86-para-2.xml:8
+#, no-c-format
+msgid ""
+"The installation program prompts you to prepare your system for reboot. "
+"Remember to remove any installation media if it is not ejected automatically "
+"upon reboot."
+msgstr ""
+
+#. Tag: title
+#: Contributors_and_production_methods.xml:8
+#, no-c-format
+msgid "Contributors and production methods"
+msgstr ""
+
+#. Tag: title
+#: Contributors_and_production_methods.xml:10
+#, no-c-format
+msgid "Contributors"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:13
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Fab\">Fabian Affolter</"
+"ulink> (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:18
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/AmanAlam\">Amanpreet Singh Alam</"
+"ulink> (translator - Punjabi)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:23
+#, no-c-format
+msgid "Jean-Paul Aubry (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:28
+#, no-c-format
+msgid "David Barzilay (translator - Brazilian Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:33
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Beckerde\">Domingo Becker</"
+"ulink> (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:38
+#, no-c-format
+msgid "Subhransu Behera (translator - Oriya)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:43
+#, no-c-format
+msgid "Michał Bentkowski (translator - Polish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:48
+#, no-c-format
+msgid "Rahul Bhalerao (translator - Marathi)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:53
+#, no-c-format
+msgid "Runa Bhattacharjee (translator - Bengali (India))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:58
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/TetaBilianou\">Teta Bilianou</"
+"ulink> (translator - Greek)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:63
+#, no-c-format
+msgid "Lucas Brausch (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:68
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Logan\">Hector Daniel "
+"Cabrera </ulink> (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:73
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/DavidCantrell\">David Cantrell</"
+"ulink> (writer - VNC installation)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:78
+#, no-c-format
+msgid "Guido Caruso (translator - Italian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:83
+#, no-c-format
+msgid "Guillaume Chardin (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:88
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/NikosCharonitakis\">Nikos "
+"Charonitakis</ulink> (translator - Greek)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:93
+#, no-c-format
+msgid "Chester Cheng (translator - Chinese (Traditional))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:98
+#, no-c-format
+msgid "Glaucia Cintra (translator - Brazilian Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:103
+#, no-c-format
+msgid "Fabien Decroux (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:108
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/HansdeGoede\">Hans De Goede</"
+"ulink> (writer - iSCSI)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:113
+#, no-c-format
+msgid "Claudio Rodrigo Pereyra Diaz (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:118
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/PiotrDr%C4%85g\">Piotr DrÄ…g</"
+"ulink> (translator - Polish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:123
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/DamienDurand\">Damien Durand</"
+"ulink> (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:128
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/StuartEllis\"> Stuart Ellis</"
+"ulink> (writer, editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:133
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Fakoor\"> Ali Fakoor</ulink> "
+"(translator - Persian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:138
+#, no-c-format
+msgid "Felix I (translator - Tamil)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:143
+#, no-c-format
+msgid "Tony Fu (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:148
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Pfrields\"> Paul W. "
+"Frields</ulink> (writer, editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:153
+#, no-c-format
+msgid "Paul Gampe (translator - Japanese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:158
+#, no-c-format
+msgid "Sree Ganesh (translator - Telugu)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:163
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/DimitrisGlezos\">Dimitris Glezos</"
+"ulink> (translator - Greek)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:168
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/GuillermoGomez\">Guillermo Gómez</"
+"ulink> (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:173
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/RuiGouveia\">Rui Gouveia</ulink> "
+"(translator - Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:178
+#, no-c-format
+msgid "Kiyoto James Hashida (translator - Japanese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:183
+#, no-c-format
+msgid "Severin Heiniger (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:188
+#, no-c-format
+msgid "Xi Huang (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:193
+#, no-c-format
+msgid "Ryuichi Hyugabaru (translator - Japanese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:198
+#, no-c-format
+msgid "Jayaradha N (translator - Tamil)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:203
+#, no-c-format
+msgid "Chris Johnson (writer)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:208
+#, no-c-format
+msgid "Eunju Kim (translator - Korean)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:213
+#, no-c-format
+msgid "Michelle J Kim (translator - Korean)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:218
+#, no-c-format
+msgid ""
+"<ulink url=\"http://translate.fedoraproject.org/people/kmilos\">Miloš "
+"Komarčević</ulink> (translator - Serbian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:223
+#, no-c-format
+msgid "Alexey Kostyuk (translator - Russian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:228
+#, no-c-format
+msgid "Daniela Kugelmann (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:233
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Rlandmann\">Rüdiger "
+"Landmann</ulink> (writer, editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://translate.fedoraproject.org/people/raada\">Magnus "
+"Larsson</ulink> (translator - Swedish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:243
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/ChristopherusLaurentius"
+"\">Christopherus Laurentius</ulink> (translator - Indonesian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:248
+#, no-c-format
+msgid "Florent Le Coz (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:253
+#, no-c-format
+msgid "Erick Lemon (writer)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:258
+#, no-c-format
+msgid "Andy Liu (translator - Chinese (Traditional))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:263
+#, no-c-format
+msgid "Wei Liu (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:268
+#, no-c-format
+msgid "Yelitza Louze (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:273
+#, no-c-format
+msgid "Gan Lu (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:278
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/IgorMiletic\">Igor Miletić</"
+"ulink> (translator - Serbian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:283
+#, no-c-format
+msgid "Noriko Mizumoto (translator - Japanese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:288
+#, no-c-format
+msgid "Jeremy W. Mooney (writer)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:293
+#, no-c-format
+msgid "Enikő Nagy (translator - Hungarian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:298
+#, no-c-format
+msgid "Igor Nestorović (translator - Serbian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:303
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:ke4qqq\"> David Nalley</"
+"ulink> (writer, editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:308
+#, no-c-format
+msgid "John Nguyen (writer)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:313
+#, no-c-format
+msgid "Manuel Ospina (translator - Spanish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:318
+#, no-c-format
+msgid "Janis Ozolins (translator - Latvian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:323
+#, no-c-format
+msgid "Ankit Patel (translator - Gujarati)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:328
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Dpaulo\">Davidson Paulo</"
+"ulink> (translator - Brazilian Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:333
+#, no-c-format
+msgid "Ani Peter (translator - Malayalam)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:338
+#, no-c-format
+msgid ""
+"<ulink url=\"https://translate.fedoraproject.org/people/aphukan\">Amitakhya "
+"Phukan</ulink> (translator - Assamese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:343
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Perplex\">Silvio Pierro</"
+"ulink> (translator - Italian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:348
+#, no-c-format
+msgid "Micha Pietsch (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:353
+#, no-c-format
+msgid "José Nuno Pires (translator - Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:358
+#, no-c-format
+msgid "Piotr Podgórski (translator - Polish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:363
+#, no-c-format
+msgid "Yulia Poyarkova (translator - Russian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:368
+#, no-c-format
+msgid "Shankar Prasad (translator - Kannada)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:373
+#, no-c-format
+msgid "Rajesh Ranjan (translator - Hindi)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:378
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/TommyReynolds\"> Tommy Reynolds "
+"</ulink> (writer)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:383
+#, no-c-format
+msgid "Tim Richert (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:388
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/DominikSandjaja\">Dominik "
+"Sandjaja</ulink> (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:393
+#, no-c-format
+msgid ""
+"<ulink url=\"http://translate.fedoraproject.org/people/szaman\">Sharuzzaman "
+"Ahmat Raslan</ulink> (translator - Malay)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:398
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Saeedi\">Mohsen Saeedi</"
+"ulink> (translator - Persian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:403
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Tiansworld\">Tian Shixiong</"
+"ulink> (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:408
+#, no-c-format
+msgid "Audrey Simons (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:413
+#, no-c-format
+msgid "Keld Simonsen (translator - Danish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:418
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Jsmith\"> Jared K. Smith</"
+"ulink> (writer, editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:423
+#, no-c-format
+msgid "Espen Stefansen (translator - Norwegian Bokmål)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:428
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Peti\"> Sulyok Péter</"
+"ulink> (translator - Hungarian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:433
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Zoli73\"> Sümegi Zoltán</"
+"ulink> (translator - Hungarian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:438
+#, no-c-format
+msgid ""
+"<ulink url=\"https://fedoraproject.org/wiki/User:Tombo\">Francesco "
+"Tombolini</ulink> (translator - Italian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:443
+#, no-c-format
+msgid "Timo Trinks (translator - German)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:448
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/DimitriosTypaldos\">Dimitris "
+"Typaldos</ulink> (translator - Greek)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:453
+#, no-c-format
+msgid "Göran Uddeborg (translator - Swedish)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:458
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/MichaelUghetto\">Michaël Ughetto</"
+"ulink> (translator - French)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:463
+#, no-c-format
+msgid "Francesco Valente (translator - Italian)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:468
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/KarstenWade\"> Karsten Wade</"
+"ulink> (writer, editor, publisher)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:473
+#, no-c-format
+msgid "Sarah Saiying Wang (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:478
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/GeertWarrink\">Geert Warrink</"
+"ulink> (translator - Dutch)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:483
+#, no-c-format
+msgid "Elizabeth Ann West (editor)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:488
+#, no-c-format
+msgid "Tyronne Wickramarathne (translator - Sinhalese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:493
+#, no-c-format
+msgid "Ben Wu (translator - Chinese (Traditional))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:498
+#, no-c-format
+msgid "Xiaofan Yang (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:503
+#, no-c-format
+msgid ""
+"<ulink url=\"http://translate.fedoraproject.org/people/bbbush\">Yuan Yijun</"
+"ulink> (translator - Chinese (Simplified))"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:508
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/DiegoZacarao\">Diego Búrigo "
+"Zacarão</ulink> (translator - Brazilian Portuguese)"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:513
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/User:Izaac\">Izaac Zavaleta</"
+"ulink> (translator - Spanish)"
+msgstr ""
+
+#. Tag: ulink
+#: Contributors_and_production_methods.xml:520
+#, no-c-format
+msgid "http://docs.fedoraproject.org/install-guide/"
+msgstr ""
+
+#. Tag: title
+#: Contributors_and_production_methods.xml:523
+#, no-c-format
+msgid "Production methods"
+msgstr ""
+
+#. Tag: para
+#: Contributors_and_production_methods.xml:524
+#, no-c-format
+msgid ""
+"Writers produce the Install Guide directly in DocBook XML in a revision "
+"control repository. They collaborate with other subject matter experts "
+"during the beta release phase of Fedora to explain the installation process. "
+"The editorial team ensures consistency and quality of the finished guide. At "
+"this point, the team of translators produces other language versions of the "
+"release notes, and then they become available to the general public as part "
+"of Fedora. The publication team also makes the guide, and subsequent errata, "
+"available via the Web."
+msgstr ""
+
+#. Tag: para
+#: Deleting_Partitions-x86.xml:18
+#, no-c-format
+msgid ""
+"For further installation instructions for x86, AMD64, and <trademark class="
+"\"registered\">Intel</trademark> 64 systems, skip to <xref linkend=\"s1-x86-"
+"bootloader\"/>."
+msgstr ""
+
+#. Tag: secondary
+#: Deleting_Partitions_x86_ppc-indexterm-1.xml:8
+#, no-c-format
+msgid "deleting partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Deleting_Partitions_x86_ppc-indexterm-2.xml:10
+#, no-c-format
+msgid "deleting"
+msgstr ""
+
+#. Tag: para
+#: Deleting_Partitions_x86_ppc-para-1.xml:8
+#, no-c-format
+msgid ""
+"To delete a partition, highlight it in the <guilabel>Partitions</guilabel> "
+"section and click the <guibutton>Delete</guibutton> button. Confirm the "
+"deletion when prompted."
+msgstr ""
+
+#. Tag: title
+#: Deleting_Partitions_x86_ppc-title.xml:8
+#, no-c-format
+msgid "Deleting a Partition"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:5
+#, no-c-format
+msgid "Disk Encryption Guide"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:11
+#, no-c-format
+msgid "What is block device encryption?"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:12
+#, no-c-format
+msgid ""
+"Block device encryption protects the data on a block device by encrypting "
+"it. To access the device's decrypted contents, a user must provide a "
+"passphrase or key as authentication. This provides additional security "
+"beyond existing OS security mechanisms in that it protects the device's "
+"contents even if it has been physically removed from the system."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:15
+#, no-c-format
+msgid "Encrypting block devices using dm-crypt/LUKS"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:16
+#, no-c-format
+msgid ""
+"<ulink url=\"http://luks.endorphin.org\"> LUKS</ulink> (Linux Unified Key "
+"Setup) is a specification for block device encryption. It establishes an on-"
+"disk format for the data, as well as a passphrase/key management policy."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:18
+#, no-c-format
+msgid ""
+"LUKS uses the kernel device mapper subsystem via the <command>dm-crypt</"
+"command> module. This arrangement provides a low-level mapping that handles "
+"encryption and decryption of the device's data. User-level operations, such "
+"as creating and accessing encrypted devices, are accomplished through the "
+"use of the <command>cryptsetup</command> utility."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:21
+#, no-c-format
+msgid "Overview of LUKS"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:24
+#, no-c-format
+msgid "What LUKS does:"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:27
+#, no-c-format
+msgid "LUKS encrypts entire block devices"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:30
+#, no-c-format
+msgid ""
+"LUKS is thereby well-suited for protecting the contents of mobile devices "
+"such as:"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:33
+#, no-c-format
+msgid "Removable storage media"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:36
+#, no-c-format
+msgid "Laptop disk drives"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:45
+#, no-c-format
+msgid "The underlying contents of the encrypted block device are arbitrary."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:48
+#, no-c-format
+msgid "This makes it useful for encrypting <command>swap</command> devices."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:51
+#, no-c-format
+msgid ""
+"This can also be useful with certain databases that use specially formatted "
+"block devices for data storage."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:57
+#, no-c-format
+msgid "LUKS uses the existing device mapper kernel subsystem."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:60
+#, no-c-format
+msgid "This is the same subsystem used by LVM, so it is well tested."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:66
+#, no-c-format
+msgid "LUKS provides passphrase strengthening."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:69
+#, no-c-format
+msgid "This protects against dictionary attacks."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:75
+#, no-c-format
+msgid "LUKS devices contain multiple key slots."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:78
+#, no-c-format
+msgid "This allows users to add backup keys/passphrases."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:87
+#, no-c-format
+msgid "What LUKS does <emphasis>not</emphasis> do:"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:90
+#, no-c-format
+msgid ""
+"LUKS is not well-suited for applications requiring many (more than eight) "
+"users to have distinct access keys to the same device."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:93
+#, no-c-format
+msgid ""
+"LUKS is not well-suited for applications requiring file-level encryption."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:101
+#, no-c-format
+msgid ""
+"How will I access the encrypted devices after installation? (System Startup)"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:102
+#, no-c-format
+msgid ""
+"During system startup you will be presented with a passphrase prompt. After "
+"the correct passphrase has been provided the system will continue to boot "
+"normally. If you used different passphrases for multiple encypted devices "
+"you may need to enter more than one passphrase during the startup."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:104 DiskEncryptionUserGuide.xml:121
+#: DiskEncryptionUserGuide.xml:126 DiskEncryptionUserGuide.xml:184
+#: DiskEncryptionUserGuide.xml:206 DiskEncryptionUserGuide.xml:234
+#, no-c-format
+msgid "<title>Tip</title>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:105
+#, no-c-format
+msgid ""
+"Consider using the same passphrase for all encrypted block devices in a "
+"given system. This will simplify system startup and you will have fewer "
+"passphrases to remember. Just make sure you choose a good passphrase!"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:110
+#, no-c-format
+msgid "Choosing a Good Passphrase"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:111
+#, no-c-format
+msgid ""
+"While dm-crypt/LUKS supports both keys and passphrases, the anaconda "
+"installer only supports the use of passphrases for creating and accessing "
+"encrypted block devices during installation."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:112
+#, no-c-format
+msgid ""
+"LUKS does provide passphrase strengthening but it is still a good idea to "
+"choose a good (meaning \"difficult to guess\") passphrase. Note the use of "
+"the term \"passphrase\", as opposed to the term \"password\". This is "
+"intentional. Providing a phrase containing multiple words to increase the "
+"security of your data is important."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:117
+#, no-c-format
+msgid "Creating Encrypted Block Devices in Anaconda"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:118
+#, no-c-format
+msgid ""
+"You can create encrypted devices during system installation. This allows you "
+"to easily configure a system with encrypted partitions."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:119
+#, no-c-format
+msgid ""
+"To enable block device encryption, check the \"Encrypt System\" checkbox "
+"when selecting automatic partitioning or the \"Encrypt\" checkbox when "
+"creating an individual partition, software RAID array, or logical volume. "
+"After you finish partitioning, you will be prompted for an encryption "
+"passphrase. This passphrase will be required to access the encrypted "
+"devices. If you have pre-existing LUKS devices and provided correct "
+"passphrases for them earlier in the install process the passphrase entry "
+"dialog will also contain a checkbox. Checking this checkbox indicates that "
+"you would like the new passphrase to be added to an available slot in each "
+"of the pre-existing encrypted block devices."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:122
+#, no-c-format
+msgid ""
+"Checking the \"Encrypt System\" checkbox on the \"Automatic Partitioning\" "
+"screen and then choosing \"Create custom layout\" does not cause any block "
+"devices to be encrypted automatically."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:127
+#, no-c-format
+msgid ""
+"You can use <command>kickstart</command> to set a separate passphrase for "
+"each new encrypted block device."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:131
+#, no-c-format
+msgid "What Kinds of Block Devices Can Be Encrypted?"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:132
+#, no-c-format
+msgid ""
+"Most types of block devices can be encrypted using LUKS. From anaconda you "
+"can encrypt partitions, LVM physical volumes, LVM logical volumes, and "
+"software RAID arrays."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:135
+#, no-c-format
+msgid "Limitations of Anaconda's Block Device Encryption Support"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:136
+#, no-c-format
+msgid "This section is about Anaconda's Block Device Encryption Support"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:149
+#, no-c-format
+msgid ""
+"Creating Encrypted Block Devices on the Installed System After Installation"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:150
+#, no-c-format
+msgid ""
+"Encrypted block devices can be created and configured after installation."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:152
+#, no-c-format
+msgid "Create the block devices"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:153
+#, no-c-format
+msgid ""
+"Create the block devices you want to encrypt by using <command>parted</"
+"command>, <command>pvcreate</command>, <command>lvcreate</command> and "
+"<command>mdadm</command>."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:156
+#, no-c-format
+msgid "Optional: Fill the device with random data"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:157
+#, no-c-format
+msgid ""
+"Filling <device> (eg: <filename>/dev/sda3</filename>) with random data "
+"before encrypting it greatly increases the strength of the encryption. The "
+"downside is that it can take a very long time."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:160
+#, no-c-format
+msgid "The commands below will destroy any existing data on the device."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:165
+#, no-c-format
+msgid ""
+"The best way, which provides high quality random data but takes a long time "
+"(several minutes per gigabyte on most systems):"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:165
+#, no-c-format
+msgid "dd if=/dev/urandom of=<device>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:169
+#, no-c-format
+msgid "Fastest way, which provides lower quality random data:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:169
+#, no-c-format
+msgid "badblocks -c 10240 -s -w -t random -v <device>"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:175
+#, no-c-format
+msgid "Format the device as a dm-crypt/LUKS encrypted device"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:178
+#, no-c-format
+msgid "The command below will destroy any existing data on the device."
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:181
+#, no-c-format
+msgid "cryptsetup luksFormat <device>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:185
+#, no-c-format
+msgid ""
+"For more information, read the <command>cryptsetup(8)</command> man page."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:187
+#, no-c-format
+msgid ""
+"After supplying the passphrase twice the device will be formatted for use. "
+"To verify, use the following command:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:188
+#, no-c-format
+msgid "cryptsetup isLuks <device> && echo Success"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:189
+#, no-c-format
+msgid ""
+"To see a summary of the encryption information for the device, use the "
+"following command:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:190
+#, no-c-format
+msgid "cryptsetup luksDump <device>"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:193
+#, no-c-format
+msgid "Create a mapping to allow access to the device's decrypted contents"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:194
+#, no-c-format
+msgid ""
+"To access the device's decrypted contents, a mapping must be established "
+"using the kernel <command>device-mapper</command>."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:194
+#, no-c-format
+msgid ""
+"It is useful to choose a meaningful name for this mapping. LUKS provides a "
+"UUID (Universally Unique Identifier) for each device. This, unlike the "
+"device name (eg: <filename>/dev/sda3</filename>), is guaranteed to remain "
+"constant as long as the LUKS header remains intact. To find a LUKS device's "
+"UUID, run the following command:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:195
+#, no-c-format
+msgid "cryptsetup luksUUID <device>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:197
+#, no-c-format
+msgid ""
+"An example of a reliable, informative and unique mapping name would be "
+"<command>luks-<uuid></command>, where <uuid> is replaced with "
+"the device's LUKS UUID (eg: <command>luks-50ec957a-5b5a-47ee-85e6-"
+"f8085bbc97a8</command>). This naming convention might seem unwieldy but is "
+"it not necessary to type it often."
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:198
+#, no-c-format
+msgid "cryptsetup luksOpen <device> <name>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:200
+#, no-c-format
+msgid ""
+"There should now be a device node, <filename>/dev/mapper/<name></"
+"filename>, which represents the decrypted device. This block device can be "
+"read from and written to like any other unencrypted block device."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:201
+#, no-c-format
+msgid ""
+"To see some information about the mapped device, use the following command:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:203
+#, no-c-format
+msgid "dmsetup info <name>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:207
+#, no-c-format
+msgid "For more information, read the <command>dmsetup(8)</command> man page."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:212
+#, no-c-format
+msgid ""
+"Create filesystems on the mapped device, or continue to build complex "
+"storage structures using the mapped device"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:213
+#, no-c-format
+msgid ""
+"Use the mapped device node (<filename>/dev/mapper/<name></filename>) "
+"as any other block device. To create an <command>ext2</command> filesystem "
+"on the mapped device, use the following command:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:215
+#, no-c-format
+msgid "mke2fs /dev/mapper/<name>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:217
+#, no-c-format
+msgid ""
+"To mount this filesystem on <filename>/mnt/test</filename>, use the "
+"following command:"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:220
+#, no-c-format
+msgid ""
+"The directory <filename>/mnt/test</filename> must exist before executing "
+"this command."
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:223
+#, no-c-format
+msgid "mount /dev/mapper/<name> /mnt/test"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:227
+#, no-c-format
+msgid "Add the mapping information to <filename>/etc/crypttab</filename>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:228
+#, no-c-format
+msgid ""
+"In order for the system to set up a mapping for the device, an entry must be "
+"present in the <filename>/etc/crypttab</filename> file. If the file doesn't "
+"exist, create it and change the owner and group to root (<command>root:root</"
+"command>) and change the mode to <command>0744</command>. Add a line to the "
+"file with the following format:"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:230
+#, no-c-format
+msgid "<name>  <device>  none"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:232
+#, no-c-format
+msgid ""
+"The <device> field should be given in the form \"UUID=<luks_uuid>"
+"\", where <luks_uuid> is the LUKS uuid as given by the command "
+"<command>cryptsetup luksUUID <device></command>. This ensures the "
+"correct device will be identified and used even if the device node (eg: "
+"<filename>/dev/sda5</filename>) changes."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:235
+#, no-c-format
+msgid ""
+"For details on the format of the <filename>/etc/crypttab</filename> file, "
+"read the <command>crypttab(5)</command> man page."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:240
+#, no-c-format
+msgid "Add an entry to <filename>/etc/fstab</filename>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:241
+#, no-c-format
+msgid ""
+"Add an entry to /etc/fstab. This is only necessary if you want to establish "
+"a persistent association between the device and a mountpoint. Use the "
+"decrypted device, <filename>/dev/mapper/<name></filename> in the "
+"<filename>/etc/fstab</filename> file."
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:242
+#, no-c-format
+msgid ""
+"In many cases it is desirable to list devices in <filename>/etc/fstab</"
+"filename> by UUID or by a filesystem label. The main purpose of this is to "
+"provide a constant identifier in the event that the device name (eg: "
+"<filename>/dev/sda4</filename>) changes. LUKS device names in the form of "
+"<filename>/dev/mapper/luks-<luks_uuid></filename> are based only on "
+"the device's LUKS UUID, and are therefore guaranteed to remain constant. "
+"This fact makes them suitable for use in <filename>/etc/fstab</filename>."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:244
+#, no-c-format
+msgid "Title"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:245
+#, no-c-format
+msgid ""
+"For details on the format of the <filename>/etc/fstab</filename> file, read "
+"the <command>fstab(5)</command> man page."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:251
+#, no-c-format
+msgid "Common Post-Installation Tasks"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:252
+#, no-c-format
+msgid "The following sections are about common post-installation tasks."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:254
+#, no-c-format
+msgid ""
+"Set a randomly generated key as an additional way to access an encrypted "
+"block device"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:255
+#, no-c-format
+msgid "These sections are about generating keys and adding keys."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:257
+#, no-c-format
+msgid "Generate a key"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:258
+#, no-c-format
+msgid ""
+"This will generate a 256-bit key in the file <filename>$HOME/keyfile</"
+"filename>."
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:260
+#, no-c-format
+msgid ""
+"dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1\n"
+"                chmod 600 $HOME/keyfile"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:263
+#, no-c-format
+msgid "Add the key to an available keyslot on the encrypted device"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:264
+#, no-c-format
+msgid "cryptsetup luksAddKey <device> ~/keyfile"
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:269
+#, no-c-format
+msgid "Add a new passphrase to an existing device"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:271
+#, no-c-format
+msgid "cryptsetup luksAddKey <device>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:273
+#, no-c-format
+msgid ""
+"After being prompted for any one of the existing passprases for "
+"authentication, you will be prompted to enter the new passphrase."
+msgstr ""
+
+#. Tag: title
+#: DiskEncryptionUserGuide.xml:276
+#, no-c-format
+msgid "Remove a passphrase or key from a device"
+msgstr ""
+
+#. Tag: programlisting
+#: DiskEncryptionUserGuide.xml:278
+#, no-c-format
+msgid "cryptsetup luksRemoveKey <device>"
+msgstr ""
+
+#. Tag: para
+#: DiskEncryptionUserGuide.xml:280
+#, no-c-format
+msgid ""
+"You will be prompted for the passphrase you wish to remove and then for any "
+"one of the remaining passphrases for authentication."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Advanced_Storage_common-figure-1.xml:8
+#, no-c-format
+msgid "Advanced Storage Options."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Advanced_Storage_common-figure-2.xml:5
+#, no-c-format
+msgid "Configure ISCSI Parameters"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Advanced_Storage_common-figure-2.xml:8
+#, no-c-format
+msgid "Configure ISCSI Parameters."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Advanced_Storage_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"From this screen you can choose to disable a dmraid device, in which case "
+"the individual elements of the dmraid device will appear as separate hard "
+"drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target. "
+"See <xref linkend=\"ISCSI_disks\"/> for an introduction to iSCSI."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Advanced_Storage_common-para-2.xml:5
+#, no-c-format
+msgid ""
+"To configure an ISCSI target invoke the 'Configure ISCSI Parameters' dialog "
+"by selecting 'Add ISCSI target' and clicking on the 'Add Drive' button. Fill "
+"in the details for the ISCSI target IP and provide a unique ISCSI initiator "
+"name to identify this system. If the ISCSI target uses CHAP (Challenge "
+"Handshake Authentication Protocol) for authentication, enter the CHAP "
+"username and password. If your enviroment uses 2-way CHAP (also called "
+"\"Mutual CHAP\"), also enter the reverse CHAP username and password. Click "
+"the 'Add target' button to attempt connection to the ISCSI target using this "
+"information."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Advanced_Storage_common-para-3.xml:8
+#, no-c-format
+msgid ""
+"Please note that you will be able to reattempt with a different ISCSI target "
+"IP should you enter it incorrectly, but in order to change the ISCSI "
+"initiator name you will need to restart the installation."
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Advanced_Storage-indexterm2.xml:8
+#, no-c-format
+msgid "dmraid"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"With the exception of certain esoteric situations, <application>anaconda</"
+"application> can handle the partitioning requirements for a typical "
+"installation."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_common-title-1.xml:8
+#, no-c-format
+msgid "Partitioning Your System"
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Disk_Druid_common-indexterm-1.xml:8
+#, no-c-format
+msgid "buttons"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_common_listitem-para-1.xml:8
+#, no-c-format
+msgid ""
+"<guibutton>Edit</guibutton>: Used to modify attributes of the partition "
+"currently selected in the <guilabel>Partitions</guilabel> section. Selecting "
+"<guibutton>Edit</guibutton> opens a dialog box. Some or all of the fields "
+"can be edited, depending on whether the partition information has already "
+"been written to disk."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"These buttons are used to change the attributes of a partition (for example "
+"the file system type and mount point) and also to create RAID devices. "
+"Buttons on this screen are also used to accept the changes you have made, or "
+"to exit the partitioning screen. For further explanation, take a look at "
+"each button in order:"
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid_common-title.xml:5
+#, no-c-format
+msgid "The partitioning screen"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-delete.xml:6
+#, no-c-format
+msgid ""
+"<guibutton>Delete</guibutton>: Used to remove the partition currently "
+"highlighted in the <guilabel>Current Disk Partitions</guilabel> section. You "
+"will be asked to confirm the deletion of any partition."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-delete.xml:9
+#, no-c-format
+msgid ""
+"To delete an LVM physical volume, first delete any volume groups of which "
+"that physical volume is a member."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-delete.xml:13
+#, no-c-format
+msgid ""
+"If you make a mistake, use the <guilabel>Reset</guilabel> option to abandon "
+"all the changes you have made."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-LVM.xml:6
+#, no-c-format
+msgid ""
+"<guibutton>LVM</guibutton>: Allows you to create an LVM logical volume. The "
+"role of LVM (Logical Volume Manager) is to present a simple logical view of "
+"underlying physical storage space, such as a hard drive(s). LVM manages "
+"individual physical disks — or to be more precise, the individual "
+"partitions present on them. <emphasis>It should only be used if you have "
+"experience using LVM.</emphasis> Note, LVM is only available in the "
+"graphical installation program."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-LVM.xml:10
+#, no-c-format
+msgid ""
+"To assign one or more physical volumes to a volume group, first name the "
+"volume group. Then select the physical volumes to be used in the volume "
+"group. Finally, configure logical volumes on any volume groups using the "
+"<guilabel>Add</guilabel>, <guilabel>Edit</guilabel> and <guilabel>Delete</"
+"guilabel> options."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-LVM.xml:18
+#, no-c-format
+msgid ""
+"You may not remove a physical volume from a volume group if doing so would "
+"leave insufficient space for that group's logical volumes. Take for example "
+"a volume group made up of two 5 GB LVM physical volume partitions, which "
+"contains an 8 GB logical volume. The installer would not allow you to remove "
+"either of the component physical volumes, since that would leave only 5 GB "
+"in the group for an 8 GB logical volume. If you reduce the total size of any "
+"logical volumes appropriately, you may then remove a physical volume from "
+"the volume group. In the example, reducing the size of the logical volume to "
+"4 GB would allow you to remove one of the 5 GB physical volumes."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid-listitem-LVM.xml:33
+#, no-c-format
+msgid "LVM Unavailable in Text Installs"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-LVM.xml:34
+#, no-c-format
+msgid ""
+"LVM initial set up is not available in a text-mode installation. The "
+"installer allows you to edit pre-configured LVM volumes. If you need to "
+"create an LVM configuration from scratch, hit <keycombo> <keycap function="
+"\"alt\">Alt</keycap> <keycap function=\"other\" otherfunction=\"F2\">F2</"
+"keycap> </keycombo> to use the terminal, and run the <command>lvm</command> "
+"command. To return to the text-mode installation, hit <keycombo> <keycap "
+"function=\"alt\">Alt</keycap> <keycap function=\"other\" otherfunction=\"F1"
+"\">F1</keycap> </keycombo>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:6
+#, no-c-format
+msgid ""
+"<guibutton>RAID</guibutton>: Used to provide redundancy to any or all disk "
+"partitions. <emphasis>It should only be used if you have experience using "
+"RAID.</emphasis>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:10
+#, no-c-format
+msgid ""
+"To make a RAID device, you must first create software RAID partitions. Once "
+"you have created two or more software RAID partitions, select "
+"<guibutton>RAID</guibutton> to join the software RAID partitions into a RAID "
+"device."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:14
+#, no-c-format
+msgid "RAID options"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:17
+#, no-c-format
+msgid "The RAID options dialog."
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:26
+#, no-c-format
+msgid "<guilabel>Create a software RAID partition</guilabel>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:29
+#, no-c-format
+msgid ""
+"Choose this option to add a partition for software RAID. This option is the "
+"only choice available if your disk contains no software RAID partitions."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:35
+#, no-c-format
+msgid "<title>Create a software RAID partition</title>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:38
+#, no-c-format
+msgid "The create a software RAID partition dialog."
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:51
+#, no-c-format
+msgid "<guilabel>Create a RAID device</guilabel>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:53
+#, no-c-format
+msgid ""
+"Choose this option to construct a RAID device from two or more existing "
+"software RAID partitions. This option is available if two or more software "
+"RAID partitions have been configured."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:60
+#, no-c-format
+msgid "<title>Create a RAID device</title>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:63
+#, no-c-format
+msgid "The create a RAID device dialog."
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:74
+#, no-c-format
+msgid "Clone a drive to create a RAID device"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:77
+#, no-c-format
+msgid ""
+"Choose this option to set up a RAID <firstterm>mirror</firstterm> of an "
+"existing disk. This option is available if two or more disks are attached to "
+"the system."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:84
+#, no-c-format
+msgid "Clone a RAID device"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-makeraid.xml:87
+#, no-c-format
+msgid "The clone a RAID device dialog."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid-listitem-reset.xml:6
+#, no-c-format
+msgid ""
+"<guibutton>Reset</guibutton>: Used to restore the partitioning screen to its "
+"original state. All changes made will be lost if you <guibutton>Reset</"
+"guibutton> the partitions."
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Disk_Druid-x86-indexterm-1.xml:7
+#, no-c-format
+msgid "creating a software RAID"
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Disk_Druid-x86-indexterm-2.xml:7
+#, no-c-format
+msgid "partitioning a RAID"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:6
+#, no-c-format
+msgid ""
+"<guibutton>New</guibutton>: Select this option to add a partition or LVM "
+"physical volume to the disk. In the <guilabel>Add partition</guilabel> "
+"dialog, choose a mount point and a partition type. If you have more than one "
+"disk on the system, choose which disks the partition may inhabit. Indicate a "
+"size in megabytes for the partition. If you wish to encrypt the partition, "
+"select that option."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:17
+#, no-c-format
+msgid "Illegal Partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:22
+#, no-c-format
+msgid "illegal"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:23
+#, no-c-format
+msgid ""
+"You cannot create separate partitions for the <filename>/bin/</filename>, "
+"<filename>/dev/</filename>, <filename>/etc/</filename>, <filename>/lib/</"
+"filename>, <filename>/proc/</filename>, <filename>/root/</filename>, and "
+"<filename>/sbin/</filename> directories. These directories must reside on "
+"the <indexterm> <primary>partition</primary> <secondary>root</secondary> </"
+"indexterm> <filename>/</filename> (root) partition."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:34
+#, no-c-format
+msgid ""
+"The <filename>/boot</filename> partition may not reside on an LVM volume "
+"group. Create the <filename>/boot</filename> partition before configuring "
+"any volume groups. Furthermore, you cannot use the ext4 or btrfs filesystems "
+"for the <filename>/boot</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:40
+#, no-c-format
+msgid ""
+"Avoid placing <filename>/usr</filename> on a separate partition. If "
+"<filename>/usr</filename> does not reside on the <filename>/</filename> "
+"(root) partition, the boot process becomes more complex and some systems "
+"(for example, those with iSCSI storage) will fail to boot."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:45
+#, no-c-format
+msgid "You may also choose from three options for sizing your partition:"
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:51
+#, no-c-format
+msgid "Fixed size"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:53
+#, no-c-format
+msgid "Use a fixed size as close to your entry as possible."
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:60
+#, no-c-format
+msgid "Fill all space up to"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:62
+#, no-c-format
+msgid "Grow the partition to a maximum size of your choice."
+msgstr ""
+
+#. Tag: guilabel
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:69
+#, no-c-format
+msgid "Fill to maximum allowable size"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:72
+#, no-c-format
+msgid "Grow the partition until it fills the remainder of the selected disks."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:80
+#, no-c-format
+msgid "Partition Sizes"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:82
+#, no-c-format
+msgid ""
+"The actual partition on the disk may be slightly smaller or larger than your "
+"choice. Disk geometry issues cause this effect, not an error or bug."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:88
+#, no-c-format
+msgid ""
+"Select the <guilabel>Encrypt partition</guilabel> option to encrypt all "
+"information on the disk partition."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-1.xml:92
+#, no-c-format
+msgid ""
+"After you enter the details for your partition, select <guibutton>OK</"
+"guibutton> to continue. If you chose to encrypt the partition, the installer "
+"prompts you to assign a passphrase by typing it twice. For hints on using "
+"good passphrases, refer to <xref linkend=\"sn-account_configuration\"/>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-2.xml:9
+#, no-c-format
+msgid ""
+"To make a RAID device, you must first create (or reuse existing) software "
+"RAID partitions. Once you have created two or more software RAID partitions, "
+"select <guibutton>Make RAID</guibutton> to join the software RAID partitions "
+"into a RAID device."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Disk_Druid_x86_ppc-listitem-para-2.xml:8
+#, no-c-format
+msgid ""
+"You can also edit free space as represented in the graphical display to "
+"create a new partition within that space. Either highlight the free space "
+"and then select the <guibutton>Edit</guibutton> button, or double-click on "
+"the free space to edit it."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Fields-common.xml:6
+#, no-c-format
+msgid "Partition Fields"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:8
+#, no-c-format
+msgid ""
+"Above the partition hierarchy are labels which present information about the "
+"partitions you are creating. The labels are defined as follows:"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:14
+#, no-c-format
+msgid ""
+"<guilabel>Device</guilabel>: This field displays the partition's device name."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:20
+#, no-c-format
+msgid ""
+"<guilabel>Mount Point/RAID/Volume</guilabel>: A mount point is the location "
+"within the directory hierarchy at which a volume exists; the volume is "
+"\"mounted\" at this location. This field indicates where the partition is "
+"mounted. If a partition exists, but is not set, then you need to define its "
+"mount point. Double-click on the partition or click the <guibutton>Edit</"
+"guibutton> button."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:27
+#, no-c-format
+msgid ""
+"<guilabel>Type</guilabel>: This field shows the partition's file system type "
+"(for example, ext2, ext3, ext4, or vfat)."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:33
+#, no-c-format
+msgid ""
+"<guilabel>Format</guilabel>: This field shows if the partition being created "
+"will be formatted."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:39
+#, no-c-format
+msgid ""
+"<guilabel>Size (MB)</guilabel>: This field shows the partition's size (in "
+"MB)."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:45
+#, no-c-format
+msgid ""
+"<guilabel>Start</guilabel>: This field shows the cylinder on your hard drive "
+"where the partition begins."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:51
+#, no-c-format
+msgid ""
+"<guilabel>End</guilabel>: This field shows the cylinder on your hard drive "
+"where the partition ends."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Fields-common.xml:57
+#, no-c-format
+msgid ""
+"<guilabel>Hide RAID device/LVM Volume Group members</guilabel>: Select this "
+"option if you do not want to view any RAID device or LVM Volume Group "
+"members that have been created."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Graphical_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"Using your mouse, click once to highlight a particular field in the "
+"graphical display. Double-click to edit an existing partition or to create a "
+"partition out of existing free space."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Graphical_common-para-2.xml:8
+#, no-c-format
+msgid ""
+"Above the display, you can review the <guilabel>Drive</guilabel> name (such "
+"as /dev/hda), the <guilabel>Geom</guilabel> (which shows the hard disk's "
+"geometry and consists of three numbers representing the number of cylinders, "
+"heads, and sectors as reported by the hard disk), and the <guilabel>Model</"
+"guilabel> of the hard drive as detected by the installation program."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Graphical_x86_ppc-para-1.xml:5
+#, no-c-format
+msgid ""
+"The partitioning screen offers a graphical representation of your hard drive"
+"(s)."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Graphical_x86_ppc-title.xml:8
+#, no-c-format
+msgid "Graphical Display of Hard Drive(s)"
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Scheme_common-indexterm-1.xml:9
+#, no-c-format
+msgid "swap partition"
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Scheme_common-indexterm-2.xml:11
+#, no-c-format
+msgid "recommended"
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Scheme_common-indexterm-3.xml:9
+#, no-c-format
+msgid "<filename>/boot/</filename> partition"
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Scheme_common-indexterm-4.xml:9
+#, no-c-format
+msgid "<filename>/var/</filename> partition"
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Scheme_common-indexterm-5.xml:6
+#, no-c-format
+msgid "root <filename>/</filename> partition"
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Scheme_common-listitem-1.xml:7
+#, no-c-format
+msgid "A <filename>root</filename> partition (3.0 GB - 5.0 GB)"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Scheme_common-listitem-1.xml:7
+#, no-c-format
+msgid ""
+"This is where \"<filename>/</filename>\" (the root directory) is located. In "
+"this setup, all files (except those stored in <filename>/boot</filename>) "
+"are on the root partition."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Scheme_common-listitem-1.xml:13
+#, no-c-format
+msgid ""
+"A 3.0 GB partition allows you to install a minimal installation, while a 5.0 "
+"GB root partition lets you perform a full installation, choosing all package "
+"groups."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Scheme_common-listitem-1.xml:18
+#, no-c-format
+msgid "Root and <filename class=\"directory\">/root</filename>"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Scheme_common-listitem-1.xml:20
+#, no-c-format
+msgid ""
+"The <filename class=\"partition\">/</filename> (or root) partition is the "
+"top of the directory structure. The <filename class=\"directory\">/root</"
+"filename> directory<filename class=\"directory\">/root</filename> (sometimes "
+"pronounced \"slash-root\") directory is the home directory of the user "
+"account for system administration."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Scheme_common-title.xml:8
+#, no-c-format
+msgid "Recommended Partitioning Scheme"
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_Scheme_x86_s390-para-1.xml:6
+#, no-c-format
+msgid "A <filename>/boot/</filename> partition (100 MB)"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Scheme_x86_s390-para-1.xml:7
+#, no-c-format
+msgid ""
+"The partition mounted on <filename>/boot/</filename> contains the operating "
+"system kernel (which allows your system to boot Fedora), along with files "
+"used during the bootstrap process. Due to limitations, creating a native "
+"ext3 partition to hold these files is required. For most users, a 100 MB "
+"boot partition is sufficient."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-figure-1.xml:8
+#, no-c-format
+msgid "Choose automatic partitioning or manual partitioning."
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Setup_common-indexterm-1.xml:9
+#, no-c-format
+msgid "disk partitioning"
+msgstr ""
+
+#. Tag: primary
+#: Disk_Partitioning_Setup_common-indexterm-7.xml:6
+#, no-c-format
+msgid "array"
+msgstr ""
+
+#. Tag: secondary
+#: Disk_Partitioning_Setup_common-indexterm-8.xml:7
+#, no-c-format
+msgid "software"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"On this screen you can choose to create the default layout or choose to "
+"manual partition using the <guimenuitem>Create custom layout</guimenuitem> "
+"option."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-para-2.xml:8
+#, no-c-format
+msgid ""
+"The first three options allow you to perform an automated installation "
+"without having to partition your drive(s) yourself. If you do not feel "
+"comfortable with partitioning your system, it is recommended that you "
+"<emphasis>do not</emphasis> choose to create a custom layout and instead let "
+"the installation program partition for you."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-warning-1.xml:8
+#, no-c-format
+msgid ""
+"The <application>PackageKit</application> update software downloads updated "
+"packages to <filename>/var/cache/yum/</filename> by default. If you "
+"partition the system manually, and create a separate <filename>/var/</"
+"filename> partition, be sure to create the partition large enough (3.0 GB or "
+"more) to download package updates."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-warning-para-1.xml:8
+#, no-c-format
+msgid ""
+"If you receive an error after the <guilabel>Disk Partitioning Setup</"
+"guilabel> phase of the installation saying something similar to:"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup_common-warning-para-2.xml:8
+#, no-c-format
+msgid ""
+"\"The partition table on device hda was unreadable. To create new partitions "
+"it must be initialized, causing the loss of ALL DATA on this drive.\""
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup-x86.xml:16
+#, no-c-format
+msgid ""
+"Partitioning allows you to divide your hard drive into isolated sections, "
+"where each section behaves as its own hard drive. Partitioning is "
+"particularly useful if you run multiple operating systems. If you are not "
+"sure how you want your system to be partitioned, read <xref linkend=\"ch-"
+"partitions-x86\"/> for more information."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup-x86.xml:26
+#, no-c-format
+msgid ""
+"You can configure an iSCSI target for installation, or disable a dmraid "
+"device from this screen by clicking on the 'Advanced storage configuration' "
+"button. For more information refer to <xref linkend=\"s1-advanced-storage-x86"
+"\"/>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup-x86.xml:36
+#, no-c-format
+msgid ""
+"If you choose to create a custom layout, refer to <xref linkend=\"s1-"
+"diskpartitioning-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_Setup-x86.xml:53
+#, no-c-format
+msgid ""
+"Users who have used programs such as <application>EZ-BIOS</application> have "
+"experienced similar problems, causing data to be lost (assuming the data was "
+"not backed up before the installation began)."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_X86_Partitions.xml:4
+#, no-c-format
+msgid ""
+"x86, AMD64, and <trademark class=\"registered\">Intel</trademark> 64 systems"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:5
+#, no-c-format
+msgid ""
+"<emphasis>Unless you have a reason for doing otherwise, we recommend that "
+"you create the following partitions for x86, AMD64, and <trademark class="
+"\"registered\">Intel</trademark> 64 systems</emphasis>:"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:11
+#, no-c-format
+msgid "A <systemitem class=\"filesystem\">swap</systemitem> partition"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:16
+#, no-c-format
+msgid "A <filename class=\"partition\">/boot</filename> partition"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:21
+#, no-c-format
+msgid "A <filename class=\"partition\">/</filename> partition"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:41
+#, no-c-format
+msgid ""
+"The <application>GRUB</application> bootloader does not support the ext4 or "
+"Btrfs file systems. You cannot use an ext4 or Btrfs partition for /boot/."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:46
+#, no-c-format
+msgid ""
+"If your hard drive is more than 1024 cylinders (and your system was "
+"manufactured more than two years ago), you may need to create a <filename>/"
+"boot/</filename> partition if you want the <filename>/</filename> (root) "
+"partition to use all of the remaining space on your hard drive."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:52
+#, no-c-format
+msgid ""
+"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 <filename>/boot/</filename> "
+"partition must be created on a partition outside of the RAID array, such as "
+"on a separate hard drive."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:65
+#, no-c-format
+msgid ""
+"Many systems have more partitions than the minimum listed above. Choose "
+"partitions based on your particular system needs. For example, consider "
+"creating a separate <filename class=\"partition\">/home</filename> partition "
+"on systems that store user data. Refer to <xref linkend=\"sn-partitioning-"
+"advice\"/> for more information."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:74
+#, no-c-format
+msgid ""
+"If you create many partitions instead of one large <filename class="
+"\"partition\">/</filename> partition, upgrades become easier. Refer to the "
+"description the Edit option in <xref linkend=\"s2-diskpartitioning-dd-x86\"/"
+"> for more information."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:82
+#, no-c-format
+msgid ""
+"The following table summarizes minimum partition sizes for the partitions "
+"containing the listed directories. You <emphasis>do not</emphasis> have to "
+"make a separate partition for each of these directories. For instance, if "
+"the partition containing <filename class=\"directory\">/foo</filename> must "
+"be at least 500 MB, and you do not make a separate <filename class="
+"\"partition\">/foo</filename> partition, then the <filename class=\"partition"
+"\">/</filename> (root) partition must be at least 500 MB."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_X86_Partitions.xml:94
+#, no-c-format
+msgid "Minimum partition sizes"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:98
+#, no-c-format
+msgid "Directory"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:99
+#, no-c-format
+msgid "Minimum size"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:105
+#, no-c-format
+msgid "250 MB"
+msgstr ""
+
+#. Tag: filename
+#: Disk_Partitioning_X86_Partitions.xml:108
+#, no-c-format
+msgid "/usr"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:109
+#, no-c-format
+msgid "250 MB, but avoid placing this on a separate partition"
+msgstr ""
+
+#. Tag: filename
+#: Disk_Partitioning_X86_Partitions.xml:112
+#, no-c-format
+msgid "/tmp"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:113
+#, no-c-format
+msgid "50 MB"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:117
+#, no-c-format
+msgid "384 MB"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:121
+#, no-c-format
+msgid "100 MB"
+msgstr ""
+
+#. Tag: entry
+#: Disk_Partitioning_X86_Partitions.xml:125
+#, no-c-format
+msgid "75 MB"
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning_X86_Partitions.xml:133
+#, no-c-format
+msgid "Leave Excess Capacity Unallocated"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:134
+#, no-c-format
+msgid ""
+"Only assign storage capacity to those partitions you require immediately. "
+"You may allocate free space at any time, to meet needs as they occur. To "
+"learn about a more flexible method for storage management, refer to <xref "
+"linkend=\"sn-partitioning-lvm\"/>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_X86_Partitions.xml:143
+#, no-c-format
+msgid ""
+"If you are not sure how best to configure the partitions for your computer, "
+"accept the default partition layout."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning-x86.xml:16
+#, no-c-format
+msgid ""
+"If you chose one of the three automatic partitioning options and did not "
+"select <guilabel>Review</guilabel>, skip ahead to <xref linkend=\"s1-"
+"pkgselection-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning-x86.xml:26
+#, no-c-format
+msgid ""
+"If you chose to create a custom layout, you must tell the installation "
+"program where to install Fedora. This is done by defining mount points for "
+"one or more disk partitions in which Fedora is installed. You may also need "
+"to create and/or delete partitions at this time."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning-x86.xml:33
+#, no-c-format
+msgid ""
+"If you have not yet planned how to set up your partitions, refer to <xref "
+"linkend=\"ch-partitions-x86\"/> and <xref linkend=\"s2-diskpartrecommend-x86"
+"\"/>. At a bare minimum, you need an appropriately-sized root partition, and "
+"a swap partition equal to twice the amount of RAM you have on the system. "
+"Itanium system users should have a <filename>/boot/efi/</filename> partition "
+"of approximately 100 MB and of type FAT (VFAT), a swap partition of at least "
+"512 MB, and an appropriately-sized root (<filename>/</filename>) partition."
+msgstr ""
+
+#. Tag: title
+#: Disk_Partitioning-x86.xml:39
+#, no-c-format
+msgid ""
+"Partitioning on x86, AMD64, and <trademark class=\"registered\">Intel</"
+"trademark> 64 Systems"
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning-x86.xml:42
+#, no-c-format
+msgid "The main partitioning screen."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_x86_ppc-note-1.xml:6
+#, no-c-format
+msgid ""
+"Please note that in the text mode installation it is not possible to work "
+"with LVM (Logical Volumes) beyond viewing the existing setup. LVM can only "
+"be set up during graphical installation."
+msgstr ""
+
+#. Tag: para
+#: Disk_Partitioning_x86_ppc-para-1.xml:5
+#, no-c-format
+msgid ""
+"If you chose one of the automatic partitioning options and selected "
+"<guilabel>Review</guilabel>, you can either accept the current partition "
+"settings (click <guibutton>Next</guibutton>), or modify the setup manually "
+"in the partitioning screen."
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk-x86.xml:5
+#, no-c-format
+msgid ""
+"Driver Media for <trademark class=\"registered\">Intel</trademark> and AMD "
+"Systems"
+msgstr ""
+
+#. Tag: primary
+#: Driver_Disk-x86.xml:7 Driver_Disk-x86.xml:55 Driver_Disk-x86.xml:69
+#: Driver_Disk-x86.xml:82 Driver_Disk-x86.xml:122
+#, no-c-format
+msgid "driver media"
+msgstr ""
+
+#. Tag: primary
+#: Driver_Disk-x86.xml:10
+#, no-c-format
+msgid "diskette"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:11
+#, no-c-format
+msgid "media"
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk-x86.xml:14
+#, no-c-format
+msgid "Why Do I Need Driver Media?"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:35
+#, no-c-format
+msgid ""
+"There is no driver available for a piece of hardware that is necessary for "
+"installation to proceed."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:40
+#, no-c-format
+msgid ""
+"If you run the installation program by entering <userinput>linux dd</"
+"userinput> at the installation boot prompt."
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk-x86.xml:53
+#, no-c-format
+msgid "How Do I Obtain Driver Media?"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:56
+#, no-c-format
+msgid "produced by Red Hat"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:70
+#, no-c-format
+msgid "produced by others"
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk-x86.xml:80
+#, no-c-format
+msgid "Creating a Driver Diskette from an Image File"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:83
+#, no-c-format
+msgid "creating diskette from image"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:85
+#, no-c-format
+msgid "To create a driver diskette from a driver diskette image using Linux:"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:91
+#, no-c-format
+msgid "Insert a blank, formatted diskette into the first diskette drive."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:97
+#, no-c-format
+msgid ""
+"From the same directory containing the driver diskette image, such as "
+"<filename><replaceable>drvnet.img</replaceable></filename>, type <command>dd "
+"if=<replaceable>drvnet.img</replaceable> of=/dev/fd0</command> as root."
+msgstr ""
+
+#. Tag: primary
+#: Driver_Disk-x86.xml:105
+#, no-c-format
+msgid "USB pen card"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:106
+#, no-c-format
+msgid "driver image"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:108
+#, no-c-format
+msgid ""
+"The installation program supports using an external flash drive as a way to "
+"add driver images during the installation process. The best way to do this "
+"is to mount the flash drive and copy the desired <filename>driverdisk.img</"
+"filename> onto the flash drive. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Driver_Disk-x86.xml:111
+#, no-c-format
+msgid "dd if=driverdisk.img of=/dev/sda"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:112
+#, no-c-format
+msgid ""
+"You are then prompted during the installation to select the partition and "
+"specify the file to be used."
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk-x86.xml:120
+#, no-c-format
+msgid "Using a Driver Image During Installation"
+msgstr ""
+
+#. Tag: secondary
+#: Driver_Disk-x86.xml:123
+#, no-c-format
+msgid "using a driver image"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk-x86.xml:128
+#, no-c-format
+msgid ""
+"For example, to specifically load a driver diskette that you have created, "
+"begin the installation process by booting from the Fedora DVD (or using boot "
+"media you have created). For x86-based systems, at the <prompt>boot:</"
+"prompt> prompt, enter <userinput>linux dd</userinput> if using an x86 or x86-"
+"64 system. Refer to <xref linkend=\"s2-x86-starting-booting\"/> for details "
+"on booting the installation program."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-para-1.xml:5
+#, no-c-format
+msgid ""
+"While the Fedora installation program is loading, a screen may appear asking "
+"you for driver media. The driver media screen is most often seen in the "
+"following scenarios:"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-para-2.xml:5
+#, no-c-format
+msgid ""
+"Driver images may be available from a hardware or software vendor's website. "
+"If you suspect that your system may require one of these drivers, you should "
+"create a driver diskette or CD-ROM before beginning your Fedora installation."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-para-5.xml:8
+#, no-c-format
+msgid ""
+"If you need to use a driver image, such as during a PCMCIA device or NFS "
+"installation, the installation program prompts you to insert the driver (as "
+"a diskette, CD-ROM, or file name) when it is needed."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-para-7.xml:5
+#, no-c-format
+msgid ""
+"The installation program asks you to insert the driver diskette. Once the "
+"driver diskette is read by the installation program, it can apply those "
+"drivers to hardware discovered on your system later in the installation "
+"process."
+msgstr ""
+
+#. Tag: title
+#: Driver_Disk_x86_ppc-section-2.xml:6
+#, no-c-format
+msgid "So What Is Driver Media Anyway?"
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-section-2.xml:8
+#, no-c-format
+msgid ""
+"Driver media can add support for hardware that may or may not be supported "
+"by the installation program. Driver media could include a driver diskette or "
+"image produced by Red Hat, it could be a diskette or CD-ROM you make "
+"yourself from driver images found on the Internet, or it could be a diskette "
+"or CD-ROM that a hardware vendor includes with a piece of hardware."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-section-2.xml:12
+#, no-c-format
+msgid ""
+"Driver media is used if you need access to a particular device to install "
+"Fedora. Drivers can be used for non-standard, very new, or uncommon devices."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-section-2.xml:19
+#, no-c-format
+msgid ""
+"If an unsupported device is not needed to install Fedora on your system, "
+"continue with the installation and add support for the new piece of hardware "
+"once the installation is complete."
+msgstr ""
+
+#. Tag: para
+#: Driver_Disk_x86_ppc-tip-1.xml:9
+#, no-c-format
+msgid ""
+"It is also possible to use a driver image via a network file. Instead of "
+"using the <command>linux dd</command> boot command, use the <command>linux "
+"dd=<replaceable>url</replaceable></command> command, where <replaceable>url</"
+"replaceable> is replaced by an HTTP, FTP, or NFS address of the driver image "
+"to be used."
+msgstr ""
+
+#. Tag: title
+#: Editing_Partitions-common.xml:6
+#, no-c-format
+msgid "Editing Partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Editing_Partitions-common.xml:10
+#, no-c-format
+msgid "editing partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Editing_Partitions-common.xml:14
+#, no-c-format
+msgid "editing"
+msgstr ""
+
+#. Tag: para
+#: Editing_Partitions-common.xml:16
+#, no-c-format
+msgid ""
+"To edit a partition, select the <guibutton>Edit</guibutton> button or double-"
+"click on the existing partition."
+msgstr ""
+
+#. Tag: para
+#: Editing_Partitions-common.xml:23
+#, no-c-format
+msgid ""
+"If the partition already exists on your disk, you can only change the "
+"partition's mount point. To make any other changes, you must delete the "
+"partition and recreate it."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:6
+#, no-c-format
+msgid "Quick Start for Experts"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:7
+#, no-c-format
+msgid ""
+"This section offers a very brief overview of installation tasks for "
+"experienced readers who are eager to get started. Note that many explanatory "
+"notes and helpful hints appear in the following chapters of this guide. If "
+"an issue arises during the installation process, consult the appropriate "
+"chapters in the full guide for help."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:13
+#, no-c-format
+msgid "Experts Only"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:14
+#, no-c-format
+msgid ""
+"This section is intended only for experts. Other readers may not be familiar "
+"with some of the terms in this section, and should move on to <xref linkend="
+"\"ch-new-users\"/> instead."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:19
+#, no-c-format
+msgid "Overview"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:20
+#, no-c-format
+msgid ""
+"The installation procedure is fairly simple, and consists of only a few "
+"steps:"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:24
+#, no-c-format
+msgid "Download files to make media or another bootable configuration."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:28
+#, no-c-format
+msgid "Prepare system for installation."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:31
+#, no-c-format
+msgid "Boot the computer and run the installation process."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:34
+#, no-c-format
+msgid "Reboot and perform post-installation configuration."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:39
+#, no-c-format
+msgid "Download Files"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:40
+#, no-c-format
+msgid "Do any one of the following:"
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:42
+#, no-c-format
+msgid "Verify your downloads"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:43
+#, no-c-format
+msgid ""
+"Downloads may fail for any number of reasons. Always verify the sha1sum of "
+"the downloaded files."
+msgstr ""
+
+#. Tag: primary
+#: expert-quickstart.xml:49
+#, no-c-format
+msgid "ISO images"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:52
+#, no-c-format
+msgid ""
+"Download the ISO image for a Live image. Create CD media from the ISO file "
+"using your preferred application. You may also use the <package>livecd-"
+"tools</package> package to write the image to other bootable media such as a "
+"USB flash disk. To install the distribution to your hard disk, use the "
+"shortcut on the desktop after you log in."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:60
+#, no-c-format
+msgid ""
+"Download the ISO images for the full distribution on CD or DVD. Create CD or "
+"DVD media from the ISO files using your preferred application, or put the "
+"images on a Windows FAT32 or Linux ext2/ext3 partition."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:66
+#, no-c-format
+msgid ""
+"Download the <filename>boot.iso</filename> image for a minimal boot CD or "
+"USB flash drive. Write the image to the approriate physical media to create "
+"bootable media. The boot media contains no packages but must be pointed at a "
+"hard disk or online repository to complete the installation."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:73
+#, no-c-format
+msgid ""
+"Download the <filename>netinst.iso</filename> image for a reduced-size boot "
+"CD. Write the image to the appropriate physical media to create bootable "
+"media."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:78
+#, no-c-format
+msgid ""
+"Download the <filename>vmlinuz</filename> kernel file and the "
+"<filename>initrd.img</filename> ramdisk image from the distribution's "
+"<filename class=\"directory\">isolinux/</filename> directory. Configure your "
+"operating system to boot the kernel and load the ramdisk image. For further "
+"information on installation without media, refer to <xref linkend=\"ap-"
+"medialess-install\"/>."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:85
+#, no-c-format
+msgid ""
+"For information on setting up a network boot server from which you can "
+"install Fedora, refer to <xref linkend=\"ap-install-server\"/>."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:92
+#, no-c-format
+msgid "Prepare for Installation"
+msgstr ""
+
+#. Tag: primary
+#: expert-quickstart.xml:94
+#, no-c-format
+msgid "NTFS partitions"
+msgstr ""
+
+#. Tag: secondary
+#: expert-quickstart.xml:95
+#, no-c-format
+msgid "resizing"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:97
+#, no-c-format
+msgid "Back up any user data you need to preserve."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:99
+#, no-c-format
+msgid "Resizing Partitions"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:100
+#, no-c-format
+msgid ""
+"The installation program provides functions for resizing ext2, ext3, ext4, "
+"and NTFS formatted partitions. Refer to <xref linkend=\"s1-diskpartitioning-"
+"x86\"/> for more information."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:106
+#, no-c-format
+msgid "Install Fedora"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:107
+#, no-c-format
+msgid ""
+"Boot from the desired media, with any options appropriate for your hardware "
+"and installation mode. Refer to <xref linkend=\"ap-admin-options\"/> for "
+"more information about boot options. If you boot from the Live CD, select "
+"the \"Install to Hard Disk\" option from the desktop to run the installation "
+"program. If you boot from minimal media or a downloaded kernel, select a "
+"network or hard disk resource from which to install."
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:114
+#, no-c-format
+msgid ""
+"Proceed through all the steps of the installation program. The installation "
+"program does not change your system until you make a final confirmation to "
+"proceed. When installation is finished, reboot your system."
+msgstr ""
+
+#. Tag: title
+#: expert-quickstart.xml:120
+#, no-c-format
+msgid "Perform Post-installation Steps"
+msgstr ""
+
+#. Tag: para
+#: expert-quickstart.xml:121
+#, no-c-format
+msgid ""
+"After the system reboots, it displays additional configuration options. Make "
+"appropriate changes to your system and proceed to the login prompt."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:9
+#, no-c-format
+msgid "<title>Firstboot</title>"
+msgstr ""
+
+#. Tag: primary
+#: firstboot.xml:11
+#, no-c-format
+msgid "<primary>Firstboot</primary>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:13
+#, no-c-format
+msgid ""
+"<application>Firstboot</application> launches the first time that you start "
+"a new Fedora system. Use <application>Firstboot</application> to configure "
+"the system for use before you log in."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:19
+#, no-c-format
+msgid "<title>Firstboot welcome screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:22
+#, no-c-format
+msgid "<para>Firstboot welcome screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:29
+#, no-c-format
+msgid ""
+"Select <guibutton>Forward</guibutton> to start the <application>Firstboot</"
+"application>."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:34
+#, no-c-format
+msgid "Graphical Interface Required"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:36
+#, no-c-format
+msgid ""
+"<application>Firstboot</application> requires a graphical interface. If you "
+"did not install one, or if Fedora has trouble starting it, you may see a "
+"slightly different setup screen."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:43
+#, no-c-format
+msgid "License Agreement"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:45
+#, no-c-format
+msgid ""
+"This screen displays the overall licensing terms for Fedora. Each software "
+"package in Fedora is covered by its own license. All licensing guidelines "
+"for Fedora are located at <ulink url=\"http://fedoraproject.org/wiki/Legal/"
+"Licenses\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:52
+#, no-c-format
+msgid "<title>Firstboot license screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:55
+#, no-c-format
+msgid "<para>Firstboot license screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:63
+#, no-c-format
+msgid ""
+"If you agree to the terms of the licence, select <guibutton>Forward</"
+"guibutton>."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:68
+#, no-c-format
+msgid "System User"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:70
+#, no-c-format
+msgid ""
+"Create a user account for yourself with this screen. Always use this account "
+"to log in to your Fedora system, rather than using the <systemitem class="
+"\"username\">root</systemitem> account."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:76
+#, no-c-format
+msgid "<title>Firstboot create user screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:79
+#, no-c-format
+msgid "<para>Firstboot create user screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:87
+#, no-c-format
+msgid ""
+"Enter a user name and your full name, and then enter your chosen password. "
+"Type your password once more in the <guilabel>Confirm Password</guilabel> "
+"box to ensure that it is correct. Refer to <xref linkend=\"sn-"
+"account_configuration\"/> for guidelines on selecting a secure password."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:95
+#, no-c-format
+msgid "Creating Extra User Accounts"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:96
+#, no-c-format
+msgid ""
+"To add additional user accounts to your system after the installation is "
+"complete, choose <menuchoice> <guimenu>System</guimenu> "
+"<guisubmenu>Administration</guisubmenu> <guimenuitem>Users & Groups</"
+"guimenuitem> </menuchoice>."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:104
+#, no-c-format
+msgid ""
+"To configure Fedora to use network services for authentication or user "
+"information, select <guibutton>Use Network Login...</guibutton>."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:112
+#, no-c-format
+msgid "Date and Time"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:114
+#, no-c-format
+msgid ""
+"If your system does not have Internet access or a network time server, "
+"manually set the date and time for your system on this screen. Otherwise, "
+"use <indexterm> <primary>NTP (Network Time Protocol)</primary> </indexterm> "
+"<firstterm>NTP</firstterm> (Network Time Protocol) servers to maintain the "
+"accuracy of the clock. NTP provides time synchronization service to "
+"computers on the same network. The Internet contains many computers that "
+"offer public NTP services."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:127
+#, no-c-format
+msgid ""
+"The initial display enables you to set the date and time of your system "
+"manually."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:132
+#, no-c-format
+msgid "<title>Firstboot date and time screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:135
+#, no-c-format
+msgid "<para>Firstboot date and time screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:143
+#, no-c-format
+msgid ""
+"Select the <guilabel>Network Time Protocol</guilabel> tab to configure your "
+"system to use NTP servers instead."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:148
+#, no-c-format
+msgid "Setting the Clock"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:149
+#, no-c-format
+msgid ""
+"To change these settings later, choose <menuchoice> <guimenu>System</"
+"guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Date & "
+"Time</guimenuitem> </menuchoice>."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:156
+#, no-c-format
+msgid ""
+"To configure your system to use network time servers, select the "
+"<guilabel>Enable Network Time Protocol</guilabel> option. This option "
+"disables the settings on the <guilabel>Date and Time</guilabel> tab and "
+"enables the other settings on this screen."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:163
+#, no-c-format
+msgid "<title>Firstboot Network Time Protocol screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:166
+#, no-c-format
+msgid "<para>Firstboot Network Time Protocol screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:174
+#, no-c-format
+msgid ""
+"By default, Fedora is configured to use three separate groups, or "
+"<firstterm>pools</firstterm>, of time servers. Time server pools create "
+"redundancy, so if one time server is unavailable, your system synchronizes "
+"with another server."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:181
+#, no-c-format
+msgid ""
+"To use an additional time server, select <guilabel>Add</guilabel>, and type "
+"the DNS name of the server into the box. To remove a server or server pool "
+"from the list, select the name and click <guilabel>Delete</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:187
+#, no-c-format
+msgid ""
+"If your machine is always connected to the Internet through a wired "
+"connection, select the <guilabel>Synchronize system clock before starting "
+"service</guilabel> option. This option may cause a short delay during "
+"startup but ensures accurate time on your system even if the clock is "
+"significantly wrong at boot time."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:194
+#, no-c-format
+msgid "Laptops and NTP"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:195
+#, no-c-format
+msgid ""
+"Do not use this option with laptop computers that sometimes use wireless "
+"networks."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:198
+#, no-c-format
+msgid ""
+"If the hardware clock in your computer is highly inaccurate, you may turn "
+"off your local time source entirely. To turn off the local time source, "
+"select <guilabel>Show advanced options</guilabel> and then deselect the "
+"<guilabel>Use Local Time Source</guilabel> option. If you turn off your "
+"local time source, the NTP servers take priority over the internal clock."
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:207
+#, no-c-format
+msgid ""
+"If you enable the <guilabel>Enable NTP Broadcast</guilabel> advanced option, "
+"Fedora attempts to automatically locate time servers on the network."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:214
+#, no-c-format
+msgid "Hardware Profile"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:215
+#, no-c-format
+msgid ""
+"<application>Firstboot</application> displays a screen that allows you to "
+"submit your hardware information anonymously to the Fedora Project. "
+"Developers use these hardware details to guide further support efforts. You "
+"can read more about this project and its development at <ulink url=\"http://"
+"smolts.org/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:223
+#, no-c-format
+msgid "<title>Firstboot hardware profile screen</title>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:226
+#, no-c-format
+msgid "<para>Firstboot hardware profile screen</para>"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:234
+#, no-c-format
+msgid ""
+"To opt in to this important work, select <guilabel>Send Profile</guilabel>. "
+"If you choose not to submit any profile data, do not change the default. "
+"Select <guilabel>Finish</guilabel> to continue to the login screen."
+msgstr ""
+
+#. Tag: title
+#: firstboot.xml:241
+#, no-c-format
+msgid "Update Your System"
+msgstr ""
+
+#. Tag: para
+#: firstboot.xml:243
+#, no-c-format
+msgid ""
+"To ensure the security of your system, run a package update after the "
+"installation completes. <xref linkend=\"ch-next-steps\"/> explains how to "
+"update your Fedora system."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-1.xml:10
+#, no-c-format
+msgid "Becoming familiar with the installation program's user interface"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-1.xml:16
+#, no-c-format
+msgid "Starting the installation program"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-1.xml:22
+#, no-c-format
+msgid "Selecting an installation method"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-1.xml:28
+#, no-c-format
+msgid ""
+"Configuration steps during the installation (language, keyboard, mouse, "
+"partitioning, etc.)"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-1.xml:34
+#, no-c-format
+msgid "Finishing the installation"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-1.xml:9
+#, no-c-format
+msgid ""
+"Window — Windows (usually referred to as <firstterm>dialogs</"
+"firstterm> in this manual) appear on your screen throughout the installation "
+"process. At times, one window may overlay another; in these cases, you can "
+"only interact with the window on top. When you are finished in that window, "
+"it disappears, allowing you to continue working in the window underneath."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-2.xml:9
+#, no-c-format
+msgid ""
+"Checkbox — Checkboxes allow you to select or deselect a feature. The "
+"box displays either an asterisk (selected) or a space (unselected). When the "
+"cursor is within a checkbox, press <keycap>Space</keycap> to select or "
+"deselect a feature."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-3.xml:9
+#, no-c-format
+msgid ""
+"Text Input — Text input lines are regions where you can enter "
+"information required by the installation program. When the cursor rests on a "
+"text input line, you may enter and/or edit information on that line."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-4.xml:9
+#, no-c-format
+msgid ""
+"Text Widget — Text widgets are regions of the screen for the display "
+"of text. At times, text widgets may also contain other widgets, such as "
+"checkboxes. If a text widget contains more information than can be displayed "
+"in the space reserved for it, a scroll bar appears; if you position the "
+"cursor within the text widget, you can then use the <keycap>Up</keycap> and "
+"<keycap>Down</keycap> arrow keys to scroll through all the information "
+"available. Your current position is shown on the scroll bar by a <guiicon>#</"
+"guiicon> character, which moves up and down the scroll bar as you scroll."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-5.xml:9
+#, no-c-format
+msgid ""
+"Scroll Bar — Scroll bars appear on the side or bottom of a window to "
+"control which part of a list or document is currently in the window's frame. "
+"The scroll bar makes it easy to move to any part of a file."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-list-item-6.xml:9
+#, no-c-format
+msgid ""
+"Button Widget — Button widgets are the primary method of interacting "
+"with the installation program. You progress through the windows of the "
+"installation program by navigating these buttons, using the <keycap>Tab</"
+"keycap> and <keycap>Enter</keycap> keys. Buttons can be selected when they "
+"are highlighted."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-note-1.xml:8
+#, no-c-format
+msgid ""
+"While text mode installations are not explicitly documented, those using the "
+"text mode installation program can easily follow the GUI installation "
+"instructions. However, because text mode presents you with a simpler, more "
+"streamlined insatallation process, certain options that are available in "
+"graphical mode are not also available in text mode. These differences are "
+"noted in the description of the installation process in this guide, and "
+"include: <itemizedlist> <listitem> <para> customizing the partition layout. "
+"</para> </listitem> <listitem> <para> customizing the bootloader "
+"configuration. </para> </listitem> <listitem> <para> selecting packages "
+"during installation. </para> </listitem> </itemizedlist> Note also that "
+"manipulation of LVM (Logical Volume Management) disk volumes is only "
+"possible in graphical mode. In text mode it is only possible to view and "
+"accept the default LVM setup."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-note-2.xml:8
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"If you have used a <firstterm>graphical user interface (GUI)</firstterm> "
+"before, you are already familiar with this process; use your mouse to "
+"navigate the screens, click buttons, or enter text fields."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-para-2.xml:8
+#, no-c-format
+msgid ""
+"You can also navigate through the installation using the keyboard. The "
+"<keycap>Tab</keycap> key allows you to move around the screen, the Up and "
+"Down arrow keys to scroll through lists, <keycap>+</keycap> and <keycap>-</"
+"keycap> keys expand and collapse lists, while <keycap>Space</keycap> and "
+"<keycap>Enter</keycap> selects or removes from selection a highlighted item. "
+"You can also use the <keycombo><keycap>Alt</keycap><keycap><replaceable>X</"
+"replaceable></keycap> </keycombo> key command combination as a way of "
+"clicking on buttons or making other screen selections, where "
+"<keycap><replaceable>X</replaceable></keycap> is replaced with any "
+"underlined letter appearing within that screen."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_common-section-2.xml:9
+#, no-c-format
+msgid "Using the Keyboard to Navigate"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_common-section-2.xml:12
+#, no-c-format
+msgid "keyboard navigation"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_common-section-2.xml:16
+#, no-c-format
+msgid "navigating the installation program using"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-section-2.xml:18
+#, no-c-format
+msgid ""
+"Navigation through the installation dialogs is performed through a simple "
+"set of keystrokes. To move the cursor, use the <keycap>Left</keycap>, "
+"<keycap>Right</keycap>, <keycap>Up</keycap>, and <keycap>Down</keycap> arrow "
+"keys. Use <keycap>Tab</keycap>, and <keycap>Shift</keycap>-<keycap>Tab</"
+"keycap> to cycle forward or backward through each widget on the screen. "
+"Along the bottom, most screens display a summary of available cursor "
+"positioning keys."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-section-2.xml:23
+#, no-c-format
+msgid ""
+"To \"press\" a button, position the cursor over the button (using "
+"<keycap>Tab</keycap>, for example) and press <keycap>Space</keycap> or "
+"<keycap>Enter</keycap>. To select an item from a list of items, move the "
+"cursor to the item you wish to select and press <keycap>Enter</keycap>. To "
+"select an item with a checkbox, move the cursor to the checkbox and press "
+"<keycap>Space</keycap> to select an item. To deselect, press <keycap>Space</"
+"keycap> a second time."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-section-2.xml:29
+#, no-c-format
+msgid ""
+"Pressing <keycap>F12</keycap> accepts the current values and proceeds to the "
+"next dialog; it is equivalent to pressing the <guibutton>OK</guibutton> "
+"button."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_common-section-2.xml:36
+#, no-c-format
+msgid ""
+"Unless a dialog box is waiting for your input, do not press any keys during "
+"the installation process (doing so may result in unpredictable behavior)."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml:3
+#, no-c-format
+msgid ""
+"If you are using an x86, AMD64, or <trademark class=\"registered\">Intel</"
+"trademark> 64 system, and you do not wish to use the GUI installation "
+"program, the text mode installation program is also available. To start the "
+"text mode installation program, press the <keycap>Esc</keycap> key while the "
+"Fedora boot menu is displayed, then use the following command at the "
+"<prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml:9
+#, no-c-format
+msgid ""
+"Refer to <xref linkend=\"sn-boot-menu\"/> for a description of the Fedora "
+"boot menu and to <xref linkend=\"s1-guimode-textinterface-x86\"/> for a "
+"brief overview of text mode installation instructions."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml:8
+#, no-c-format
+msgid ""
+"It is highly recommended that installs be performed using the GUI "
+"installation program. The GUI installation program offers the full "
+"functionality of the Fedora installation program, including LVM "
+"configuration which is not available during a text mode installation."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml:9
+#, no-c-format
+msgid ""
+"Users who must use the text mode installation program can follow the GUI "
+"installation instructions and obtain all needed information."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-common-section-1.xml:6
+#, no-c-format
+msgid "The Text Mode Installation Program User Interface"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86-common-section-1.xml:10
+#, no-c-format
+msgid "text mode user interface"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86-common-section-1.xml:13
+#, no-c-format
+msgid "user interface, text mode"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:18
+#, no-c-format
+msgid ""
+"Graphical installation remains the recommended method for installing Fedora. "
+"If you are installing Fedora on a system that lacks a graphical display, "
+"consider performing the installation over a VNC connection – see <xref "
+"linkend=\"vncwhitepaperadded\"/>."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:21
+#, no-c-format
+msgid ""
+"If your system has a graphical display, but graphical installation fails, "
+"try booting with the <command>xdriver=vesa</command> option – see"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:26
+#, no-c-format
+msgid ""
+"The Fedora text mode installation program uses a screen-based interface that "
+"includes most of the on-screen <wordasword>widgets</wordasword> commonly "
+"found on graphical user interfaces. <xref linkend=\"fig-install-widget1-x86"
+"\"/>, and <xref linkend=\"fig-install-widget2-x86\"/>, illustrate the "
+"screens that appear during the installation process."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:30
+#, no-c-format
+msgid ""
+"The cursor is used to select (and interact with) a particular widget. As the "
+"cursor is moved from widget to widget, it may cause the widget to change "
+"color, or the cursor itself may only appear positioned in or next to the "
+"widget."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-common-section-1.xml:37
+#, no-c-format
+msgid ""
+"<title>Installation Program Widgets as seen in <guilabel>Boot Loader "
+"Configuration</guilabel></title>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:40
+#, no-c-format
+msgid ""
+"<para>Installation Program Widgets as seen in <guilabel>Boot Loader "
+"Configuration</guilabel></para>"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-common-section-1.xml:48
+#: Graphical_Installation_x86-common-section-1.xml:70
+#, no-c-format
+msgid "Legend"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-common-section-1.xml:59
+#, no-c-format
+msgid ""
+"<title>Installation Program Widgets as seen in the partitioning screen</"
+"title>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-common-section-1.xml:62
+#, no-c-format
+msgid ""
+"<para>Installation Program Widgets as seen in the partitioning screen</para>"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-Installation-methods.xml:6
+#, no-c-format
+msgid "Selecting an Installation Method"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_x86-Installation-methods.xml:9
+#: Graphical_Installation_x86-Installation-methods.xml:17
+#: Graphical_Installation_x86-Installation-methods.xml:35
+#: Graphical_Installation_x86-Installation-methods.xml:49
+#: Graphical_Installation_x86-Installation-methods.xml:63
+#, no-c-format
+msgid "method"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:12
+#, no-c-format
+msgid ""
+"What type of installation method do you wish to use? The following "
+"installation methods are available:"
+msgstr ""
+
+#. Tag: term
+#: Graphical_Installation_x86-Installation-methods.xml:22
+#, no-c-format
+msgid "DVD/CD-ROM"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:24
+#, no-c-format
+msgid ""
+"If you have a DVD/CD-ROM drive and the Fedora CD-ROMs or DVD you can use "
+"this method. Refer to <xref linkend=\"s1-begininstall-cd-inst-x86\"/>, for "
+"DVD/CD-ROM installation instructions."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:38
+#, no-c-format
+msgid ""
+"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 <command>linux askmethod</"
+"command> boot option). Refer to <xref linkend=\"s1-begininstall-hd-x86\"/>, "
+"for hard drive installation instructions."
+msgstr ""
+
+#. Tag: term
+#: Graphical_Installation_x86-Installation-methods.xml:45
+#, no-c-format
+msgid "<term>NFS</term>"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86-Installation-methods.xml:50
+#, no-c-format
+msgid "NFS image"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:52
+#, no-c-format
+msgid ""
+"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 "
+"<command>linux askmethod</command> boot option). Refer to <xref linkend=\"s1-"
+"begininstall-nfs-x86\"/> for network installation instructions. Note that "
+"NFS installations may also be performed in GUI mode."
+msgstr ""
+
+#. Tag: term
+#: Graphical_Installation_x86-Installation-methods.xml:59
+#, no-c-format
+msgid "<term>URL</term>"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86-Installation-methods.xml:64
+#, no-c-format
+msgid "<tertiary>URL</tertiary>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:66
+#, no-c-format
+msgid ""
+"If you are installing directly from an HTTP (Web) server or FTP server, use "
+"this method. You need a boot CD-ROM (use the <command>linux askmethod</"
+"command> boot option). Refer to <xref linkend=\"s1-begininstall-url-x86\"/>, "
+"for FTP and HTTP installation instructions."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:73
+#, no-c-format
+msgid ""
+"If you booted the distribution DVD and did not use the alternate "
+"installation source option <option>askmethod</option>, the next stage loads "
+"automatically from the DVD. Proceed to <xref linkend=\"sn-welcome-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86-Installation-methods.xml:78
+#, no-c-format
+msgid "CD/DVD Activity"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-Installation-methods.xml:79
+#, no-c-format
+msgid ""
+"If you boot any Fedora installation media, the installation program loads "
+"its next stage from that disc. This happens regardless of which installation "
+"method you choose, unless you eject the disc before you proceed. The "
+"installation program still downloads <emphasis>package data</emphasis> from "
+"the source you choose."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86-para-5.xml:6
+#, no-c-format
+msgid ""
+"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 <xref linkend=\"tb-guimode-console-x86"
+"\"/> for a listing of the virtual consoles, keystrokes used to switch to "
+"them, and their contents."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation-x86.xml:5
+#, no-c-format
+msgid ""
+"Installing on <trademark class=\"registered\">Intel</trademark> and AMD "
+"Systems"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation-x86.xml:8
+#, no-c-format
+msgid "<secondary>GUI</secondary>"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation-x86.xml:19
+#, no-c-format
+msgid "The Graphical Installation Program User Interface"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation-x86.xml:23
+#, no-c-format
+msgid "graphical user interface"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation-x86.xml:26
+#, no-c-format
+msgid "user interface, graphical"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation-x86.xml:44
+#, no-c-format
+msgid "A Note about Virtual Consoles"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation-x86.xml:47
+#, no-c-format
+msgid "consoles, virtual"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation-x86.xml:51
+#, no-c-format
+msgid "<primary>virtual consoles</primary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation-x86.xml:57
+#, no-c-format
+msgid "<tertiary>virtual consoles</tertiary>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:82
+#, no-c-format
+msgid "console"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:86
+#, no-c-format
+msgid "keystrokes"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:90
+#, no-c-format
+msgid "contents"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:97
+#, no-c-format
+msgid "<entry>1</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:102
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f1</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:106
+#, no-c-format
+msgid "installation dialog"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:112
+#, no-c-format
+msgid "<entry>2</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:117
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f2</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:121
+#, no-c-format
+msgid "shell prompt"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:127
+#, no-c-format
+msgid "<entry>3</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:132
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f3</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:136
+#, no-c-format
+msgid "install log (messages from installation program)"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:142
+#, no-c-format
+msgid "<entry>4</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:147
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f4</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:151
+#, no-c-format
+msgid "system-related messages"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:157
+#, no-c-format
+msgid "<entry>5</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:162
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f5</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:166
+#, no-c-format
+msgid "other messages"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:172
+#, no-c-format
+msgid "<entry>6</entry>"
+msgstr ""
+
+#. Tag: keycombo
+#: Graphical_Installation-x86.xml:177
+#, no-c-format
+msgid "<keycap>ctrl</keycap><keycap>alt</keycap><keycap>f6</keycap>"
+msgstr ""
+
+#. Tag: entry
+#: Graphical_Installation-x86.xml:181
+#, no-c-format
+msgid "graphical display"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_ppc-para-1.xml:8
+#, no-c-format
+msgid ""
+"This chapter explains how to perform a Fedora installation from the DVD/CD-"
+"ROM, using the graphical, mouse-based installation program. The following "
+"topics are discussed:"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_ppc-para-3.xml:5
+#, no-c-format
+msgid ""
+"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 <firstterm>virtual "
+"consoles</firstterm>, among which you can switch using a single keystroke "
+"combination."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_ppc-para-4.xml:8
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_ppc-para-6.xml:8
+#, no-c-format
+msgid ""
+"Generally, there is no reason to leave the default console (virtual console "
+"#6) for graphical installations unless you are attempting to diagnose "
+"installation problems."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86_ppc-table-1-title.xml:8
+#, no-c-format
+msgid "Console, Keystrokes, and Contents"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86_Starting.xml:6
+#, no-c-format
+msgid "Starting the Installation Program"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86_Starting.xml:10
+#, no-c-format
+msgid "<tertiary>starting</tertiary>"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86_Starting.xml:13
+#, no-c-format
+msgid "<primary>starting</primary>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:16
+#, no-c-format
+msgid ""
+"To start, first make sure that you have all necessary resources for the "
+"installation. If you have already read through <xref linkend=\"ch-steps-x86"
+"\"/>, and followed the instructions, you should be ready to start the "
+"installation process. When you have verified that you are ready to begin, "
+"boot the installation program using the Fedora DVD or CD-ROM #1 or any boot "
+"media that you have created."
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86_Starting.xml:23
+#, no-c-format
+msgid "driver diskette"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:25
+#, no-c-format
+msgid ""
+"Occasionally, some hardware components require a <firstterm>driver diskette</"
+"firstterm> during the installation. A driver diskette adds support for "
+"hardware that is not otherwise supported by the installation program. Refer "
+"to <xref linkend=\"ch-driverdisk-x86\"/> for more information."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86_Starting.xml:31
+#, no-c-format
+msgid ""
+"Booting the Installation Program on x86, AMD64, and <trademark class="
+"\"registered\">Intel</trademark> 64 Systems"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86_Starting.xml:33
+#, no-c-format
+msgid "<primary>installation program</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_x86_Starting.xml:34
+#, no-c-format
+msgid ""
+"<secondary>x86, AMD64 and <trademark class=\"registered\">Intel</trademark> "
+"64</secondary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86_Starting.xml:35
+#, no-c-format
+msgid "<tertiary>booting</tertiary>"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86_Starting.xml:38
+#, no-c-format
+msgid "<primary>booting</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_x86_Starting.xml:39
+#, no-c-format
+msgid "<secondary>installation program</secondary>"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86_Starting.xml:40
+#, no-c-format
+msgid ""
+"<tertiary>x86, AMD64 and <trademark class=\"registered\">Intel</trademark> "
+"64</tertiary>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:42
+#, no-c-format
+msgid ""
+"You can boot the installation program using any one of the following media "
+"(depending upon what your system can support):"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:48
+#, no-c-format
+msgid ""
+"<emphasis>Fedora DVD/CD-ROM</emphasis> — Your machine supports a "
+"bootable DVD/CD-ROM drive and you have the Fedora CD-ROM set or DVD."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:54
+#, no-c-format
+msgid ""
+"<emphasis>Boot CD-ROM</emphasis> — Your machine supports a bootable CD-"
+"ROM drive and you want to perform network or hard drive installation."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:60
+#, no-c-format
+msgid ""
+"<emphasis>USB pen drive</emphasis> — Your machine supports booting "
+"from a USB device."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:66
+#, no-c-format
+msgid ""
+"<emphasis>PXE boot via network</emphasis> — Your machine supports "
+"booting from the network. This is an advanced installation path. Refer to "
+"<xref linkend=\"ap-install-server\"/> for additional information on this "
+"method."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:72
+#, no-c-format
+msgid ""
+"To create a boot CD-ROM or to prepare your USB pen drive for installation, "
+"refer to <xref linkend=\"s2-steps-make-cd\"/>."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:76
+#, no-c-format
+msgid ""
+"Insert the boot media and reboot the system. Your BIOS settings may need to "
+"be changed to allow you to boot from the CD-ROM or USB device."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:80
+#, no-c-format
+msgid ""
+"To change your BIOS settings on an x86, AMD64, or <trademark class="
+"\"registered\">Intel</trademark> 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."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:83
+#, no-c-format
+msgid ""
+"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 CD-ROM 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 CD-ROM drive for bootable media; if it "
+"does not find bootable media on the CD-ROM drive, it then checks your hard "
+"drive or diskette drive."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:86
+#, no-c-format
+msgid ""
+"Save your changes before exiting the BIOS. For more information, refer to "
+"the documentation that came with your system."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:90
+#, no-c-format
+msgid ""
+"After a short delay, a screen containing the <prompt>boot:</prompt> prompt "
+"should appear. The screen contains information on a variety of boot options. "
+"Each boot option also has one or more help screens associated with it. To "
+"access a help screen, press the appropriate function key as listed in the "
+"line at the bottom of the screen."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:95
+#, no-c-format
+msgid "As you boot the installation program, be aware of two issues:"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:101
+#, no-c-format
+msgid ""
+"Once the <prompt>boot:</prompt> prompt appears, the installation program "
+"automatically begins if you take no action within the first minute. To "
+"disable this feature, press one of the help screen function keys."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:107
+#, no-c-format
+msgid ""
+"If you press a help screen function key, there is a slight delay while the "
+"help screen is read from the boot media."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:113
+#, no-c-format
+msgid ""
+"Normally, you only need to press <keycap>Enter</keycap> to boot. Be sure to "
+"watch the boot messages to review if the Linux kernel detects your hardware. "
+"If your hardware is properly detected, continue to the next section. If it "
+"does not properly detect your hardware, you may need to restart the "
+"installation and use one of the boot options provided in <xref linkend=\"ap-"
+"admin-options\"/>."
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86_Starting.xml:122
+#, no-c-format
+msgid "Additional Boot Options"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:126
+#, no-c-format
+msgid ""
+"While it is easiest to boot using a CD-ROM or 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."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:139
+#, no-c-format
+msgid ""
+"To pass options to the boot loader on an x86, AMD64, or <trademark class="
+"\"registered\">Intel</trademark> 64 system, use the instructions as provided "
+"in the boot loader option samples below."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:146
+#, no-c-format
+msgid ""
+"Refer to <xref linkend=\"ap-admin-options\"/> for additional boot options "
+"not covered in this section."
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_x86_Starting.xml:156
+#: Graphical_Installation_x86_Starting.xml:160
+#, no-c-format
+msgid "text mode"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:161
+#, no-c-format
+msgid ""
+"To perform a text mode installation, at the installation boot prompt, type:"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:180
+#, no-c-format
+msgid ""
+"ISO images have an md5sum embedded in them. To test the checksum integrity "
+"of an ISO image, at the installation boot prompt, type:"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:184
+#, no-c-format
+msgid ""
+"The installation program prompts you to insert a CD or select an ISO image "
+"to test, and select <guibutton>OK</guibutton> to perform the checksum "
+"operation. This checksum operation can be performed on any Fedora CD and "
+"does not have to be performed in a specific order (for example, CD #1 does "
+"not have to be the first CD you verify). It is strongly recommended to "
+"perform this operation on any Fedora CD that was created from downloaded ISO "
+"images. This command works with the CD, DVD, hard drive ISO, and NFS ISO "
+"installation methods."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:198
+#, no-c-format
+msgid ""
+"Also in the <filename>images/</filename> directory is the <filename>boot."
+"iso</filename> file. This file is an ISO image than can be used to boot the "
+"installation program. To use the <filename>boot.iso</filename>, your "
+"computer must be able to boot from its CD-ROM drive, and its BIOS settings "
+"must be configured to do so. You must then burn the <filename>boot.iso</"
+"filename> file onto a recordable/rewriteable CD-ROM."
+msgstr ""
+
+#. Tag: secondary
+#: Graphical_Installation_x86_Starting.xml:206
+#: Graphical_Installation_x86_Starting.xml:210
+#: Graphical_Installation_x86_Starting.xml:214
+#: Graphical_Installation_x86_Starting.xml:219
+#, no-c-format
+msgid "serial mode"
+msgstr ""
+
+#. Tag: tertiary
+#: Graphical_Installation_x86_Starting.xml:215
+#: Graphical_Installation_x86_Starting.xml:220
+#, no-c-format
+msgid "UTF-8"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:221
+#, no-c-format
+msgid ""
+"If you need to perform the installation in <firstterm>serial mode</"
+"firstterm>, type the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Graphical_Installation_x86_Starting.xml:224
+#, no-c-format
+msgid ""
+"<userinput>linux console=<replaceable><device></replaceable></"
+"userinput>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:225
+#: Graphical_Installation_x86_Starting.xml:250
+#, no-c-format
+msgid "For text mode installations, use:"
+msgstr ""
+
+#. Tag: screen
+#: Graphical_Installation_x86_Starting.xml:228
+#, no-c-format
+msgid ""
+"<userinput>linux text console=<replaceable><device></replaceable></"
+"userinput>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:229
+#, no-c-format
+msgid ""
+"In the above command, <replaceable><device></replaceable> should be "
+"the device you are using (such as ttyS0 or ttyS1). For example, "
+"<command>linux text console=ttyS0</command>."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:233
+#, no-c-format
+msgid ""
+"Text mode installations using a serial terminal work best when the terminal "
+"supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, "
+"Kermit '95 works well. Non-UTF-8 capable terminals works as long as only "
+"English is used during the installation process. An enhanced serial display "
+"can be used by passing the <command>utf8</command> command as a boot-time "
+"option to the installation program. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Graphical_Installation_x86_Starting.xml:236
+#, no-c-format
+msgid "<command>linux console=ttyS0 utf8</command>"
+msgstr ""
+
+#. Tag: title
+#: Graphical_Installation_x86_Starting.xml:241
+#, no-c-format
+msgid "Kernel Options"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:243
+#, no-c-format
+msgid ""
+"Options can also be passed to the kernel. For example, to apply updates for "
+"the anaconda installation program from a floppy disk enter:"
+msgstr ""
+
+#. Tag: primary
+#: Graphical_Installation_x86_Starting.xml:247
+#, no-c-format
+msgid "kernel options"
+msgstr ""
+
+#. Tag: screen
+#: Graphical_Installation_x86_Starting.xml:253
+#, no-c-format
+msgid "<userinput>linux text updates</userinput>"
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:254
+#, no-c-format
+msgid ""
+"This command will prompt you to insert a floppy diskette containing updates "
+"for anaconda. It is not needed if you are performing a network installation "
+"and have already placed the updates image contents in <command>rhupdates/</"
+"command> on the server."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:258
+#, no-c-format
+msgid ""
+"After entering any options, press <keycap>Enter</keycap> to boot using those "
+"options."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:262
+#, no-c-format
+msgid ""
+"If you need to specify boot options to identify your hardware, please write "
+"them down. The boot options are needed during the boot loader configuration "
+"portion of the installation (refer to <xref linkend=\"s1-x86-bootloader\"/> "
+"for more information)."
+msgstr ""
+
+#. Tag: para
+#: Graphical_Installation_x86_Starting.xml:266
+#, no-c-format
+msgid ""
+"For more information on kernel options refer to <xref linkend=\"ap-admin-"
+"options\"/>."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:6
+#, no-c-format
+msgid "The GRUB Boot Loader"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:12
+#, no-c-format
+msgid ""
+"When a computer running Linux is turned on, the operating system is loaded "
+"into memory by a special program called a <firstterm>boot loader</"
+"firstterm>. A boot loader usually exists on the system's primary hard drive "
+"(or other media device) and has the sole responsibility of loading the Linux "
+"kernel with its required files or (in some cases) other operating systems "
+"into memory."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:157
+#, no-c-format
+msgid ""
+"This appendix discusses commands and configuration options for the GRUB boot "
+"loader included with Fedora for the x86 architecture."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:162
+#, no-c-format
+msgid "<title>GRUB</title>"
+msgstr ""
+
+#. Tag: seealso
+#: Grub.xml:169 Grub.xml:763
+#, no-c-format
+msgid "<seealso>GRUB</seealso>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:171
+#, no-c-format
+msgid ""
+"The <firstterm>GNU GRand Unified Boot loader</firstterm> (GRUB) is a program "
+"which enables the selection of the installed operating system or kernel to "
+"be loaded at system boot time. It also allows the user to pass arguments to "
+"the kernel."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:176
+#, no-c-format
+msgid "GRUB and the x86 Boot Process"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:179
+#, no-c-format
+msgid "<secondary>boot process</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:183
+#, no-c-format
+msgid "direct loading"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:187
+#, no-c-format
+msgid "chain loading"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:189
+#, no-c-format
+msgid ""
+"This section discusses the specific role GRUB plays when booting an x86 "
+"system. For a look at the overall boot process, refer to <xref linkend=\"s1-"
+"boot-init-shutdown-process\"/>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:193
+#, no-c-format
+msgid "GRUB loads itself into memory in the following stages:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:199
+#, no-c-format
+msgid ""
+"<emphasis>The Stage 1 or primary boot loader is read into memory by the BIOS "
+"from the MBR <footnote> <para> For more on the system BIOS and the MBR, "
+"refer to <xref linkend=\"s2-boot-init-shutdown-bios\"/>. </para> </footnote>."
+"</emphasis> The primary boot loader exists on less than 512 bytes of disk "
+"space within the MBR and is capable of loading either the Stage 1.5 or Stage "
+"2 boot loader."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:209
+#, no-c-format
+msgid ""
+"<emphasis>The Stage 1.5 boot loader is read into memory by the Stage 1 boot "
+"loader, if necessary.</emphasis> Some hardware requires an intermediate step "
+"to get to the Stage 2 boot loader. This is sometimes true when the "
+"<filename>/boot/</filename> partition is above the 1024 cylinder head of the "
+"hard drive or when using LBA mode. The Stage 1.5 boot loader is found either "
+"on the <filename>/boot/</filename> partition or on a small part of the MBR "
+"and the <filename>/boot/</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:217
+#, no-c-format
+msgid ""
+"<emphasis>The Stage 2 or secondary boot loader is read into memory.</"
+"emphasis> The secondary boot loader displays the GRUB menu and command "
+"environment. This interface allows the user to select which kernel or "
+"operating system to boot, pass arguments to the kernel, or look at system "
+"parameters."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:224
+#, no-c-format
+msgid ""
+"<emphasis>The secondary boot loader reads the operating system or kernel as "
+"well as the contents of <filename>/boot/sysroot/</filename> into memory.</"
+"emphasis> Once GRUB determines which operating system or kernel to start, it "
+"loads it into memory and transfers control of the machine to that operating "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:231
+#, no-c-format
+msgid ""
+"The method used to boot Linux is called <firstterm>direct loading</"
+"firstterm> because the boot loader loads the operating system directly. "
+"There is no intermediary between the boot loader and the kernel."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:235
+#, no-c-format
+msgid ""
+"The boot process used by other operating systems may differ. For example, "
+"the <trademark class=\"registered\">Microsoft</trademark> <trademark class="
+"\"registered\">Windows</trademark> operating system, as well as other "
+"operating systems, are loaded using <firstterm>chain loading</firstterm>. "
+"Under this method, the MBR points to the first sector of the partition "
+"holding the operating system, where it finds the files necessary to actually "
+"boot that operating system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:240
+#, no-c-format
+msgid ""
+"GRUB supports both direct and chain loading boot methods, allowing it to "
+"boot almost any operating system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:247
+#, no-c-format
+msgid ""
+"During installation, Microsoft's DOS and Windows installation programs "
+"completely overwrite the MBR, destroying any existing boot loaders. If "
+"creating a dual-boot system, it is best to install the Microsoft operating "
+"system first."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:254
+#, no-c-format
+msgid "Features of GRUB"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:257
+#, no-c-format
+msgid "features"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:259
+#, no-c-format
+msgid ""
+"GRUB contains several features that make it preferable to other boot loaders "
+"available for the x86 architecture. Below is a partial list of some of the "
+"more important features:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:265
+#, no-c-format
+msgid ""
+"<emphasis>GRUB provides a true command-based, pre-OS environment on x86 "
+"machines.</emphasis> This feature affords the user maximum flexibility in "
+"loading operating systems with specified options or gathering information "
+"about the system. For years, many non-x86 architectures have employed pre-OS "
+"environments that allow system booting from a command line."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:272
+#, no-c-format
+msgid ""
+"<emphasis>GRUB supports <firstterm>Logical Block Addressing (LBA)</"
+"firstterm> mode.</emphasis> LBA places the addressing conversion used to "
+"find files in the hard drive's firmware, and is used on many IDE and all "
+"SCSI hard devices. Before LBA, boot loaders could encounter the 1024-"
+"cylinder BIOS limitation, where the BIOS could not find a file after the "
+"1024 cylinder head of the disk. LBA support allows GRUB to boot operating "
+"systems from partitions beyond the 1024-cylinder limit, so long as the "
+"system BIOS supports LBA mode. Most modern BIOS revisions support LBA mode."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:280
+#, no-c-format
+msgid ""
+"<emphasis>GRUB can read ext2 partitions.</emphasis> This functionality "
+"allows GRUB to access its configuration file, <filename>/boot/grub/grub."
+"conf</filename>, every time the system boots, eliminating the need for the "
+"user to write a new version of the first stage boot loader to the MBR when "
+"configuration changes are made. The only time a user needs to reinstall GRUB "
+"on the MBR is if the physical location of the <filename>/boot/</filename> "
+"partition is moved on the disk. For details on installing GRUB to the MBR, "
+"refer to <xref linkend=\"s1-grub-installing\"/>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:295
+#, no-c-format
+msgid ""
+"If GRUB was not installed during the installation process, it can be "
+"installed afterward. Once installed, it automatically becomes the default "
+"boot loader."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:299
+#, no-c-format
+msgid ""
+"Before installing GRUB, make sure to use the latest GRUB package available "
+"or use the GRUB package from the installation CD-ROMs."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:304
+#, no-c-format
+msgid ""
+"Once the GRUB package is installed, open a root shell prompt and run the "
+"command <command>/sbin/grub-install <replaceable><location></"
+"replaceable></command>, where <replaceable><location></replaceable> is "
+"the location that the GRUB Stage 1 boot loader should be installed. For "
+"example, the following command installs GRUB to the MBR of the master IDE "
+"device on the primary IDE bus:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:308
+#, no-c-format
+msgid "<command>/sbin/grub-install /dev/hda</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:309
+#, no-c-format
+msgid ""
+"The next time the system boots, the GRUB graphical boot loader menu appears "
+"before the kernel loads into memory."
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:317
+#, no-c-format
+msgid "system unbootable after disk failure"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:320
+#, no-c-format
+msgid ""
+"If GRUB is installed on a RAID 1 array, the system may become unbootable in "
+"the event of disk failure."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:330
+#, no-c-format
+msgid "GRUB Terminology"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:333 Grub.xml:343 Grub.xml:412 Grub.xml:460
+#, no-c-format
+msgid "terminology"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:335
+#, no-c-format
+msgid ""
+"One of the most important things to understand before using GRUB is how the "
+"program refers to devices, such as hard drives and partitions. This "
+"information is particularly important when configuring GRUB to boot multiple "
+"operating systems."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:340
+#, no-c-format
+msgid "Device Names"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:344
+#, no-c-format
+msgid "devices"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:346
+#, no-c-format
+msgid ""
+"When referring to a specific device with GRUB, do so using the following "
+"format (note that the parentheses and comma are very important "
+"syntactically):"
+msgstr ""
+
+#. Tag: command
+#: Grub.xml:351
+#, no-c-format
+msgid ""
+"(<replaceable><type-of-device><bios-device-number></replaceable>,"
+"<replaceable><partition-number></replaceable>)"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:354
+#, no-c-format
+msgid ""
+"The <replaceable><type-of-device></replaceable> specifies the type of "
+"device from which GRUB boots. The two most common options are <command>hd</"
+"command> for a hard disk or <command>fd</command> for a 3.5 diskette. A "
+"lesser used device type is also available called <command>nd</command> for a "
+"network disk. Instructions on configuring GRUB to boot over the network are "
+"available online at <ulink url=\"http://www.gnu.org/software/grub/manual/"
+"\">http://www.gnu.org/software/grub/manual/</ulink>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:360
+#, no-c-format
+msgid ""
+"The <replaceable><bios-device-number></replaceable> is the BIOS device "
+"number. The primary IDE hard drive is numbered <command>0</command> and a "
+"secondary IDE hard drive is numbered <command>1</command>. This syntax is "
+"roughly equivalent to that used for devices by the kernel. For example, the "
+"<command>a</command> in <command>hda</command> for the kernel is analogous "
+"to the <command>0</command> in <command>hd0</command> for GRUB, the "
+"<command>b</command> in <command>hdb</command> is analogous to the "
+"<command>1</command> in <command>hd1</command>, and so on."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:366
+#, no-c-format
+msgid ""
+"The <replaceable><partition-number></replaceable> specifies the number "
+"of a partition on a device. Like the <replaceable><bios-device-number>"
+"</replaceable>, most types of partitions are numbered starting at "
+"<command>0</command>. However, BSD partitions are specified using letters, "
+"with <command>a</command> corresponding to <command>0</command>, <command>b</"
+"command> corresponding to <command>1</command>, and so on."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:372
+#, no-c-format
+msgid ""
+"The numbering system for devices under GRUB always begins with <command>0</"
+"command>, not <command>1</command>. Failing to make this distinction is one "
+"of the most common mistakes made by new users."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:376
+#, no-c-format
+msgid ""
+"To give an example, if a system has more than one hard drive, GRUB refers to "
+"the first hard drive as <command>(hd0)</command> and the second as <command>"
+"(hd1)</command>. Likewise, GRUB refers to the first partition on the first "
+"drive as <command>(hd0,0)</command> and the third partition on the second "
+"hard drive as <command>(hd1,2)</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:381
+#, no-c-format
+msgid ""
+"In general the following rules apply when naming devices and partitions "
+"under GRUB:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:387
+#, no-c-format
+msgid ""
+"It does not matter if system hard drives are IDE or SCSI, all hard drives "
+"begin with the letters <command>hd</command>. The letters <command>fd</"
+"command> are used to specify 3.5 diskettes."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:393
+#, no-c-format
+msgid ""
+"To specify an entire device without respect to partitions, leave off the "
+"comma and the partition number. This is important when telling GRUB to "
+"configure the MBR for a particular disk. For example, <command>(hd0)</"
+"command> specifies the MBR on the first device and <command>(hd3)</command> "
+"specifies the MBR on the fourth device."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:400
+#, no-c-format
+msgid ""
+"If a system has multiple drive devices, it is very important to know how the "
+"drive boot order is set in the BIOS. This is a simple task if a system has "
+"only IDE or SCSI drives, but if there is a mix of devices, it becomes "
+"critical that the type of drive with the boot partition be accessed first."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:409
+#, no-c-format
+msgid "File Names and Blocklists"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:413
+#, no-c-format
+msgid "files"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:415
+#, no-c-format
+msgid ""
+"When typing commands to GRUB that reference a file, such as a menu list, it "
+"is necessary to specify an absolute file path immediately after the device "
+"and partition numbers."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:419
+#, no-c-format
+msgid "The following illustrates the structure of such a command:"
+msgstr ""
+
+#. Tag: command
+#: Grub.xml:424
+#, no-c-format
+msgid ""
+"(<replaceable><device-type><device-number></replaceable>,"
+"<replaceable><partition-number></replaceable>)<replaceable></path/"
+"to/file></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:427
+#, no-c-format
+msgid ""
+"In this example, replace <replaceable><device-type></replaceable> with "
+"<command>hd</command>, <command>fd</command>, or <command>nd</command>. "
+"Replace <replaceable><device-number></replaceable> with the integer "
+"for the device. Replace <replaceable></path/to/file></replaceable> "
+"with an absolute path relative to the top-level of the device."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:431
+#, no-c-format
+msgid ""
+"It is also possible to specify files to GRUB that do not actually appear in "
+"the file system, such as a chain loader that appears in the first few blocks "
+"of a partition. To load such files, provide a <firstterm>blocklist</"
+"firstterm> that specifies block by block where the file is located in the "
+"partition. Since a file is often comprised of several different sets of "
+"blocks, blocklists use a special syntax. Each block containing the file is "
+"specified by an offset number of blocks, followed by the number of blocks "
+"from that offset point. Block offsets are listed sequentially in a comma-"
+"delimited list."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:437
+#, no-c-format
+msgid "The following is a sample blocklist:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:440
+#, no-c-format
+msgid "<command>0+50,100+25,200+1</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:441
+#, no-c-format
+msgid ""
+"This sample blocklist specifies a file that starts at the first block on the "
+"partition and uses blocks 0 through 49, 100 through 124, and 200."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:445
+#, no-c-format
+msgid ""
+"Knowing how to write blocklists is useful when using GRUB to load operating "
+"systems which require chain loading. It is possible to leave off the offset "
+"number of blocks if starting at block 0. As an example, the chain loading "
+"file in the first partition of the first hard drive would have the following "
+"name:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:449
+#, no-c-format
+msgid "<command>(hd0,0)+1</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:450
+#, no-c-format
+msgid ""
+"The following shows the <command>chainloader</command> command with a "
+"similar blocklist designation at the GRUB command line after setting the "
+"correct device and partition as root:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:453 Grub.xml:632
+#, no-c-format
+msgid "<command>chainloader +1</command>"
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:457
+#, no-c-format
+msgid "The Root File System and GRUB"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:461
+#, no-c-format
+msgid "root file system"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:463
+#, no-c-format
+msgid ""
+"The use of the term <emphasis>root file system</emphasis> has a different "
+"meaning in regard to GRUB. It is important to remember that GRUB's root file "
+"system has nothing to do with the Linux root file system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:467
+#, no-c-format
+msgid ""
+"The GRUB root file system is the top level of the specified device. For "
+"example, the image file <command>(hd0,0)/grub/splash.xpm.gz</command> is "
+"located within the <filename>/grub/</filename> directory at the top-level "
+"(or root) of the <command>(hd0,0)</command> partition (which is actually the "
+"<filename>/boot/</filename> partition for the system)."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:472
+#, no-c-format
+msgid ""
+"Next, the <command>kernel</command> command is executed with the location of "
+"the kernel file as an option. Once the Linux kernel boots, it sets up the "
+"root file system that Linux users are familiar with. The original GRUB root "
+"file system and its mounts are forgotten; they only existed to boot the "
+"kernel file."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:477
+#, no-c-format
+msgid ""
+"Refer to the <command>root</command> and <command>kernel</command> commands "
+"in <xref linkend=\"s1-grub-commands\"/> for more information."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:483
+#, no-c-format
+msgid "GRUB Interfaces"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:486 Grub.xml:490 Grub.xml:495 Grub.xml:508 Grub.xml:584
+#, no-c-format
+msgid "interfaces"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:491
+#, no-c-format
+msgid "menu"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:496
+#, no-c-format
+msgid "menu entry editor"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:500
+#, no-c-format
+msgid "changing runlevels with"
+msgstr ""
+
+#. Tag: primary
+#: Grub.xml:503
+#, no-c-format
+msgid "runlevels"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:504
+#, no-c-format
+msgid "changing with GRUB"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:509
+#, no-c-format
+msgid "command line"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:511
+#, no-c-format
+msgid ""
+"GRUB features three interfaces which provide different levels of "
+"functionality. Each of these interfaces allows users to boot the Linux "
+"kernel or another operating system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:515
+#, no-c-format
+msgid "The interfaces are as follows:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:522
+#, no-c-format
+msgid ""
+"The following GRUB interfaces can only be accessed by pressing any key "
+"within the three seconds of the GRUB menu bypass screen."
+msgstr ""
+
+#. Tag: emphasis
+#: Grub.xml:529
+#, no-c-format
+msgid "Menu Interface"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:531
+#, no-c-format
+msgid ""
+"This is the default interface shown when GRUB is configured by the "
+"installation program. A menu of operating systems or preconfigured kernels "
+"are displayed as a list, ordered by name. Use the arrow keys to select an "
+"operating system or kernel version and press the <keycap>Enter</keycap> key "
+"to boot it. If you do nothing on this screen, then after the time out period "
+"expires GRUB will load the default option."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:535
+#, no-c-format
+msgid ""
+"Press the <keycap>e</keycap> key to enter the entry editor interface or the "
+"<keycap>c</keycap> key to load a command line interface."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:539
+#, no-c-format
+msgid ""
+"Refer to <xref linkend=\"s1-grub-configfile\"/> for more information on "
+"configuring this interface."
+msgstr ""
+
+#. Tag: emphasis
+#: Grub.xml:546
+#, no-c-format
+msgid "Menu Entry Editor Interface"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:548
+#, no-c-format
+msgid ""
+"To access the menu entry editor, press the <keycap>e</keycap> key from the "
+"boot loader menu. The GRUB commands for that entry are displayed here, and "
+"users may alter these command lines before booting the operating system by "
+"adding a command line (<keycap>o</keycap> inserts a new line after the "
+"current line and <keycap>O</keycap> inserts a new line before it), editing "
+"one (<keycap>e</keycap>), or deleting one (<keycap>d</keycap>)."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:554
+#, no-c-format
+msgid ""
+"After all changes are made, the <keycap>b</keycap> key executes the commands "
+"and boots the operating system. The <keycap>Esc</keycap> key discards any "
+"changes and reloads the standard menu interface. The <keycap>c</keycap> key "
+"loads the command line interface."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:559
+#, no-c-format
+msgid ""
+"For information about changing runlevels using the GRUB menu entry editor, "
+"refer to <xref linkend=\"s1-grub-runlevels\"/>."
+msgstr ""
+
+#. Tag: emphasis
+#: Grub.xml:567
+#, no-c-format
+msgid "Command Line Interface"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:569
+#, no-c-format
+msgid ""
+"The command line interface is the most basic GRUB interface, but it is also "
+"the one that grants the most control. The command line makes it possible to "
+"type any relevant GRUB commands followed by the <keycap>Enter</keycap> key "
+"to execute them. This interface features some advanced shell-like features, "
+"including <keycap>Tab</keycap> key completion based on context, and "
+"<keycap>Ctrl</keycap> key combinations when typing commands, such as "
+"<keycombo><keycap>Ctrl</keycap><keycap>a</keycap> </keycombo> to move to the "
+"beginning of a line and <keycombo><keycap>Ctrl</keycap><keycap>e</keycap> </"
+"keycombo> to move to the end of a line. In addition, the arrow, "
+"<keycap>Home</keycap>, <keycap>End</keycap>, and <keycap>Delete</keycap> "
+"keys work as they do in the <command>bash</command> shell."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:573
+#, no-c-format
+msgid ""
+"Refer to <xref linkend=\"s1-grub-commands\"/> for a list of common commands."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:581
+#, no-c-format
+msgid "Interfaces Load Order"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:585
+#, no-c-format
+msgid "order of"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:587
+#, no-c-format
+msgid ""
+"When GRUB loads its second stage boot loader, it first searches for its "
+"configuration file. Once found, the menu interface bypass screen is "
+"displayed. If a key is pressed within three seconds, GRUB builds a menu list "
+"and displays the menu interface. If no key is pressed, the default kernel "
+"entry in the GRUB menu is used."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:592
+#, no-c-format
+msgid ""
+"If the configuration file cannot be found, or if the configuration file is "
+"unreadable, GRUB loads the command line interface, allowing the user to type "
+"commands to complete the boot process."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:596
+#, no-c-format
+msgid ""
+"If the configuration file is not valid, GRUB prints out the error and asks "
+"for input. This helps the user see precisely where the problem occurred. "
+"Pressing any key reloads the menu interface, where it is then possible to "
+"edit the menu option and correct the problem based on the error reported by "
+"GRUB. If the correction fails, GRUB reports an error and reloads the menu "
+"interface."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:603
+#, no-c-format
+msgid "GRUB Commands"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:606
+#, no-c-format
+msgid "commands"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:608
+#, no-c-format
+msgid ""
+"GRUB allows a number of useful commands in its command line interface. Some "
+"of the commands accept options after their name; these options should be "
+"separated from the command and other options on that line by space "
+"characters."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:612
+#, no-c-format
+msgid "The following is a list of useful commands:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:618
+#, no-c-format
+msgid ""
+"<command>boot</command> — Boots the operating system or chain loader "
+"that was last loaded."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:624
+#, no-c-format
+msgid ""
+"<command>chainloader <replaceable></path/to/file></replaceable></"
+"command> — Loads the specified file as a chain loader. If the file is "
+"located on the first sector of the specified partition, use the blocklist "
+"notation, <command>+1</command>, instead of the file name."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:629
+#, no-c-format
+msgid "The following is an example <command>chainloader</command> command:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:636
+#, no-c-format
+msgid ""
+"<command>displaymem</command> — Displays the current use of memory, "
+"based on information from the BIOS. This is useful to determine how much RAM "
+"a system has prior to booting it."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:642
+#, no-c-format
+msgid ""
+"<command>initrd <replaceable></path/to/initrd></replaceable></command> "
+"— Enables users to specify an initial RAM disk to use when booting. An "
+"<filename>initrd</filename> is necessary when the kernel needs certain "
+"modules in order to boot properly, such as when the root partition is "
+"formatted with the ext3 or ext4 file system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:647
+#, no-c-format
+msgid "The following is an example <command>initrd</command> command:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:650
+#, no-c-format
+msgid "<command>initrd /initrd-2.6.8-1.523.img</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:654
+#, no-c-format
+msgid ""
+"<command>install <replaceable><stage-1></replaceable> <replaceable><"
+"install-disk></replaceable> <replaceable><stage-2></replaceable> "
+"<option>p</option> <replaceable>config-file</replaceable></command> — "
+"Installs GRUB to the system MBR."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:661
+#, no-c-format
+msgid ""
+"<command><replaceable><stage-1></replaceable></command> — "
+"Signifies a device, partition, and file where the first boot loader image "
+"can be found, such as <command>(hd0,0)/grub/stage1</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:667
+#, no-c-format
+msgid ""
+"<command><replaceable><install-disk></replaceable></command> — "
+"Specifies the disk where the stage 1 boot loader should be installed, such "
+"as <command>(hd0)</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:673
+#, no-c-format
+msgid ""
+"<command><replaceable><stage-2></replaceable></command> — Passes "
+"the stage 2 boot loader location to the stage 1 boot loader, such as "
+"<command>(hd0,0)/grub/stage2</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:679
+#, no-c-format
+msgid ""
+"<option>p</option> <command><replaceable><config-file></replaceable></"
+"command> — This option tells the <command>install</command> command to "
+"look for the menu configuration file specified by <command><replaceable><"
+"config-file></replaceable></command>, such as <command>(hd0,0)/grub/grub."
+"conf</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:689
+#, no-c-format
+msgid ""
+"The <command>install</command> command overwrites any information already "
+"located on the MBR."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:696
+#, no-c-format
+msgid ""
+"<command>kernel <replaceable></path/to/kernel></replaceable> "
+"<replaceable><option-1></replaceable> <replaceable><option-N></"
+"replaceable></command> ... — Specifies the kernel file to load when "
+"booting the operating system. Replace <replaceable></path/to/kernel></"
+"replaceable> with an absolute path from the partition specified by the root "
+"command. Replace <replaceable><option-1></replaceable> with options "
+"for the Linux kernel, such as <command>root=/dev/VolGroup00/LogVol00</"
+"command> to specify the device on which the root partition for the system is "
+"located. Multiple options can be passed to the kernel in a space separated "
+"list."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:702
+#, no-c-format
+msgid "The following is an example <command>kernel</command> command:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:705
+#, no-c-format
+msgid ""
+"<command>kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00</"
+"command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:706
+#, no-c-format
+msgid ""
+"The option in the previous example specifies that the root file system for "
+"Linux is located on the <command>hda5</command> partition."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:712 Grub.xml:872
+#, no-c-format
+msgid ""
+"<command>root (<replaceable><device-type></"
+"replaceable><replaceable><device-number></replaceable>,"
+"<replaceable><partition></replaceable>)</command> — Configures "
+"the root partition for GRUB, such as <command>(hd0,0)</command>, and mounts "
+"the partition."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:717
+#, no-c-format
+msgid "The following is an example <command>root</command> command:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:720
+#, no-c-format
+msgid "<command>root (hd0,0)</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:724 Grub.xml:879
+#, no-c-format
+msgid ""
+"<command>rootnoverify (<replaceable><device-type></"
+"replaceable><replaceable><device-number></replaceable>,"
+"<replaceable><partition></replaceable>)</command> — Configures "
+"the root partition for GRUB, just like the <command>root</command> command, "
+"but does not mount the partition."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:731
+#, no-c-format
+msgid ""
+"Other commands are also available; type <command>help --all</command> for a "
+"full list of commands. For a description of all GRUB commands, refer to the "
+"documentation available online at <ulink url=\"http://www.gnu.org/software/"
+"grub/manual/\">http://www.gnu.org/software/grub/manual/</ulink>."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:737
+#, no-c-format
+msgid "GRUB Menu Configuration File"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:740 Grub.xml:800
+#, no-c-format
+msgid "menu configuration file"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:742
+#, no-c-format
+msgid ""
+"The configuration file (<filename>/boot/grub/grub.conf</filename>), which is "
+"used to create the list of operating systems to boot in GRUB's menu "
+"interface, essentially allows the user to select a pre-set group of commands "
+"to execute. The commands given in <xref linkend=\"s1-grub-commands\"/> can "
+"be used, as well as some special commands that are only available in the "
+"configuration file."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:748
+#, no-c-format
+msgid "Configuration File Structure"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:751 Grub.xml:756
+#, no-c-format
+msgid "configuration file"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:752
+#, no-c-format
+msgid "structure"
+msgstr ""
+
+#. Tag: filename
+#: Grub.xml:757
+#, no-c-format
+msgid "/boot/grub/grub.conf"
+msgstr ""
+
+#. Tag: filename
+#: Grub.xml:761
+#, no-c-format
+msgid "grub.conf"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:765
+#, no-c-format
+msgid ""
+"The GRUB menu interface configuration file is <filename>/boot/grub/grub."
+"conf</filename>. The commands to set the global preferences for the menu "
+"interface are placed at the top of the file, followed by stanzas for each "
+"operating kernel or operating system listed in the menu."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:770
+#, no-c-format
+msgid ""
+"The following is a very basic GRUB menu configuration file designed to boot "
+"either Fedora or Microsoft Windows Vista:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:775
+#, no-c-format
+msgid ""
+"default=0 \n"
+"timeout=10 \n"
+"splashimage=(hd0,0)/grub/splash.xpm.gz \n"
+"hiddenmenu \n"
+"title Fedora (2.6.27.19-170.2.35.fc10.i686)\n"
+"root (hd0,1)\n"
+"kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-"
+"b207-002689545705 rhgb quiet\n"
+"initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img \n"
+"\n"
+"# section to load Windows \n"
+"title Windows         \n"
+"rootnoverify (hd0,0)         \n"
+"chainloader +1"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:777
+#, no-c-format
+msgid ""
+"This file configures GRUB to build a menu with Fedora as the default "
+"operating system and sets it to autoboot after 10 seconds. Two sections are "
+"given, one for each operating system entry, with commands specific to the "
+"system disk partition table."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:785
+#, no-c-format
+msgid ""
+"Note that the default is specified as an integer. This refers to the first "
+"<command>title</command> line in the GRUB configuration file. For the "
+"<command>Windows</command> section to be set as the default in the previous "
+"example, change the <command>default=0</command> to <command>default=1</"
+"command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:791
+#, no-c-format
+msgid ""
+"Configuring a GRUB menu configuration file to boot multiple operating "
+"systems is beyond the scope of this chapter. Consult <xref linkend=\"s1-grub-"
+"additional-resources\"/> for a list of additional resources."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:797
+#, no-c-format
+msgid "Configuration File Directives"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:801
+#, no-c-format
+msgid "directives"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:803
+#, no-c-format
+msgid ""
+"The following are directives commonly used in the GRUB menu configuration "
+"file:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:809
+#, no-c-format
+msgid ""
+"<command>chainloader <replaceable></path/to/file></replaceable></"
+"command> — Loads the specified file as a chain loader. Replace "
+"<replaceable></path/to/file></replaceable> with the absolute path to "
+"the chain loader. If the file is located on the first sector of the "
+"specified partition, use the blocklist notation, <command>+1</command>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:816
+#, no-c-format
+msgid ""
+"<command>color <replaceable><normal-color></replaceable> "
+"<replaceable><selected-color></replaceable></command> — Allows "
+"specific colors to be used in the menu, where two colors are configured as "
+"the foreground and background. Use simple color names such as <command>red/"
+"black</command>. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:820
+#, no-c-format
+msgid "<command>color red/black green/blue</command>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:824
+#, no-c-format
+msgid ""
+"<command>default=<replaceable><integer></replaceable></command> "
+"— Replace <replaceable><integer></replaceable> with the default "
+"entry title number to be loaded if the menu interface times out."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:830
+#, no-c-format
+msgid ""
+"<command>fallback=<replaceable><integer></replaceable></command> "
+"— Replace <replaceable><integer></replaceable> with the entry "
+"title number to try if the first attempt fails."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:836
+#, no-c-format
+msgid ""
+"<command>hiddenmenu</command> — Prevents the GRUB menu interface from "
+"being displayed, loading the <command>default</command> entry when the "
+"<command>timeout</command> period expires. The user can see the standard "
+"GRUB menu by pressing the <keycap>Esc</keycap> key."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:843
+#, no-c-format
+msgid ""
+"<command>initrd <replaceable></path/to/initrd></replaceable></command> "
+"— Enables users to specify an initial RAM disk to use when booting. "
+"Replace <replaceable></path/to/initrd></replaceable> with the absolute "
+"path to the initial RAM disk."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:850
+#, no-c-format
+msgid ""
+"<command>kernel <replaceable></path/to/kernel></replaceable> "
+"<replaceable><option-1></replaceable> <replaceable><option-N></"
+"replaceable></command> — Specifies the kernel file to load when "
+"booting the operating system. Replace <replaceable></path/to/kernel></"
+"replaceable> with an absolute path from the partition specified by the root "
+"directive. Multiple options can be passed to the kernel when it is loaded."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:857
+#, no-c-format
+msgid ""
+"<command>password=<replaceable><password></replaceable></command> "
+"— Prevents a user who does not know the password from editing the "
+"entries for this menu option."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:861
+#, no-c-format
+msgid ""
+"Optionally, it is possible to specify an alternate menu configuration file "
+"after the <command>password=<replaceable><password></replaceable></"
+"command> directive. In this case, GRUB restarts the second stage boot loader "
+"and uses the specified alternate configuration file to build the menu. If an "
+"alternate menu configuration file is left out of the command, a user who "
+"knows the password is allowed to edit the current configuration file."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:866
+#, no-c-format
+msgid ""
+"For more information about securing GRUB, refer to the chapter titled "
+"<citetitle>Workstation Security</citetitle> in the <citetitle>Red Hat "
+"Enterprise Linux Deployment Guide</citetitle>."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:886
+#, no-c-format
+msgid ""
+"<command>timeout=<replaceable><integer></replaceable></command> "
+"— Specifies the interval, in seconds, that GRUB waits before loading "
+"the entry designated in the <command>default</command> command."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:892
+#, no-c-format
+msgid ""
+"<command>splashimage=<replaceable><path-to-image></replaceable></"
+"command> — Specifies the location of the splash screen image to be "
+"used when GRUB boots."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:898
+#, no-c-format
+msgid ""
+"<command>title <replaceable>group-title</replaceable></command> — "
+"Specifies a title to be used with a particular group of commands used to "
+"load a kernel or operating system."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:904
+#, no-c-format
+msgid ""
+"To add human-readable comments to the menu configuration file, begin the "
+"line with the hash mark character (<command>#</command>)."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:910
+#, no-c-format
+msgid "<title>Changing Runlevels at Boot Time</title>"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:913
+#, no-c-format
+msgid "<secondary>Changing Runlevels at Boot Time</secondary>"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:915
+#, no-c-format
+msgid ""
+"Under Fedora, it is possible to change the default runlevel at boot time."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:919
+#, no-c-format
+msgid ""
+"To change the runlevel of a single boot session, use the following "
+"instructions:"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:925
+#, no-c-format
+msgid ""
+"When the GRUB menu bypass screen appears at boot time, press any key to "
+"enter the GRUB menu (within the first three seconds)."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:931
+#, no-c-format
+msgid ""
+"Press the <keycap>a</keycap> key to append to the <command>kernel</command> "
+"command."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:937
+#, no-c-format
+msgid ""
+"Add <command><space><replaceable><runlevel></replaceable></"
+"command> at the end of the boot options line to boot to the desired "
+"runlevel. For example, the following entry would initiate a boot process "
+"into runlevel 3:"
+msgstr ""
+
+#. Tag: screen
+#: Grub.xml:940
+#, no-c-format
+msgid ""
+"<command>grub append> ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3</"
+"command>"
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:945
+#, no-c-format
+msgid "Additional Resources"
+msgstr ""
+
+#. Tag: secondary
+#: Grub.xml:948 Grub.xml:958 Grub.xml:980 Grub.xml:1010
+#, no-c-format
+msgid "additional resources"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:950
+#, no-c-format
+msgid ""
+"This chapter is only intended as an introduction to GRUB. Consult the "
+"following resources to discover more about how GRUB works."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:955
+#, no-c-format
+msgid "Installed Documentation"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:959
+#, no-c-format
+msgid "installed documentation"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:963
+#, no-c-format
+msgid ""
+"<filename>/usr/share/doc/grub-<replaceable><version-number></"
+"replaceable>/</filename> — This directory contains good information "
+"about using and configuring GRUB, where <replaceable><version-number></"
+"replaceable> corresponds to the version of the GRUB package installed."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:969
+#, no-c-format
+msgid ""
+"<command>info grub</command> — The GRUB info page contains a tutorial, "
+"a user reference manual, a programmer reference manual, and a FAQ document "
+"about GRUB and its usage."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:977
+#, no-c-format
+msgid "Useful Websites"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:981
+#, no-c-format
+msgid "useful websites"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:985
+#, no-c-format
+msgid ""
+"<ulink url=\"http://www.gnu.org/software/grub\">http://www.gnu.org/software/"
+"grub/</ulink> — The home page of the GNU GRUB project. This site "
+"contains information concerning the state of GRUB development and an FAQ."
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:991
+#, no-c-format
+msgid ""
+"<ulink url=\"http://kbase.redhat.com/faq/docs/DOC-6864\">http://kbase.redhat."
+"com/faq/docs/DOC-6864</ulink> — Details booting operating systems "
+"other than Linux."
+msgstr ""
+
+#. Tag: title
+#: Grub.xml:1007
+#, no-c-format
+msgid "Related Books"
+msgstr ""
+
+#. Tag: tertiary
+#: Grub.xml:1011
+#, no-c-format
+msgid "related books"
+msgstr ""
+
+#. Tag: para
+#: Grub.xml:1015
+#, no-c-format
+msgid ""
+"<citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>; Red Hat, "
+"Inc. — The <citetitle>Workstation Security</citetitle> chapter "
+"explains, in a concise manner, how to secure the GRUB boot loader."
+msgstr ""
+
+#. Tag: primary
+#: Initializing_Hard_Disk_common-indexterm.xml:6
+#, no-c-format
+msgid "Hard disk"
+msgstr ""
+
+#. Tag: secondary
+#: Initializing_Hard_Disk_common-indexterm.xml:7
+#, no-c-format
+msgid "initializing"
+msgstr ""
+
+#. Tag: title
+#: Initializing_Hard_Disk_common-note-1.xml:6
+#, no-c-format
+msgid "Detach Unneeded Disks"
+msgstr ""
+
+#. Tag: para
+#: Initializing_Hard_Disk_common-note-1.xml:7
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Initializing_Hard_Disk_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"If no readable partition tables are found on existing hard disks, the "
+"installation program asks to initialize the hard disk. This operation makes "
+"any existing data on the hard disk unreadable. If your system has a brand "
+"new hard disk with no operating system installed, or you have removed all "
+"partitions on the hard disk, answer <guilabel>Yes</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: Initializing_Hard_Disk_common-para-2.xml:5
+#, no-c-format
+msgid ""
+"Certain RAID systems or other nonstandard configurations may be unreadable "
+"to the installation program and the prompt to initialize the hard disk may "
+"appear. The installation program responds to the physical disk structures it "
+"is able to detect."
+msgstr ""
+
+#. Tag: title
+#: Initializing_Hard_Disk_common-title.xml:5
+#, no-c-format
+msgid "Initializing the Hard Disk"
+msgstr ""
+
+#. Tag: title
+#: Initializing_Hard_Disk-x86.xml:17
+#, no-c-format
+msgid "Warning screen – initializing hard drive"
+msgstr ""
+
+#. Tag: para
+#: Initializing_Hard_Disk-x86.xml:20
+#, no-c-format
+msgid "Warning screen – initializing hard drive."
+msgstr ""
+
+#. Tag: title
+#: Installation_Guide.xml:12
+#, no-c-format
+msgid "Before you begin"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:14
+#, no-c-format
+msgid ""
+"This part of the <citetitle>Fedora Installation Guide</citetitle> covers "
+"decisions that you should make and resources that you should gather before "
+"installing Fedora, including:"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:19
+#, no-c-format
+msgid ""
+"the decision whether to upgrade an existing installation of Fedora or "
+"install a new copy."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:24
+#, no-c-format
+msgid ""
+"hardware considerations, and hardware details that you may need during "
+"installation."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:29
+#, no-c-format
+msgid "preparing to install Fedora over a network."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:34
+#, no-c-format
+msgid "preparing driver media."
+msgstr ""
+
+#. Tag: title
+#: Installation_Guide.xml:45
+#, no-c-format
+msgid "The installation process"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:47
+#, no-c-format
+msgid ""
+"This part of the <citetitle>Fedora Installation Guide</citetitle> details "
+"the installation process itself, from various methods of booting the "
+"installer up to the point where the computer must restart to finalize the "
+"installation. This part of the manual also includes a chapter on "
+"troubleshooting problems with the installation process."
+msgstr ""
+
+#. Tag: title
+#: Installation_Guide.xml:56
+#, no-c-format
+msgid "Advanced installation options"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:58
+#, no-c-format
+msgid ""
+"This part of the <citetitle>Fedora Installation Guide</citetitle> covers "
+"more complex and uncommon methods of installing Fedora, including:"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:63
+#, no-c-format
+msgid "boot options."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:68
+#, no-c-format
+msgid "installing without media."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:73
+#, no-c-format
+msgid "installing through VNC."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:78
+#, no-c-format
+msgid ""
+"using <application>kickstart</application> to automate the installation "
+"process."
+msgstr ""
+
+#. Tag: title
+#: Installation_Guide.xml:92
+#, no-c-format
+msgid "After installation"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:94
+#, no-c-format
+msgid ""
+"This part of the <citetitle>Fedora Installation Guide</citetitle> covers "
+"finalizing the installation, as well as some installation-related tasks that "
+"you might perform at some time in the future. These include:"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:99
+#, no-c-format
+msgid "using a Fedora installation disk to rescue a damaged system."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:104
+#, no-c-format
+msgid "upgrading to a new version of Fedora."
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:109
+#, no-c-format
+msgid "removing Fedora from your computer."
+msgstr ""
+
+#. Tag: title
+#: Installation_Guide.xml:123
+#, no-c-format
+msgid "Technical appendixes"
+msgstr ""
+
+#. Tag: para
+#: Installation_Guide.xml:125
+#, no-c-format
+msgid ""
+"The appendixes in this section do not contain instructions that tell you how "
+"to install Fedora. Instead, they provide technical background that you might "
+"find helpful to understand the options that Fedora offers you at various "
+"points in the installation process."
+msgstr ""
+
+#. Tag: para
+#: Installing_Packages_common-note-1.xml:8
+#, no-c-format
+msgid ""
+"If you install from a Fedora Live image, no reboot prompt appears. You may "
+"continue to use the Live image as desired, and reboot the system at any time "
+"to enjoy the newly installed Fedora system."
+msgstr ""
+
+#. Tag: para
+#: Installing_Packages_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"At this point there is nothing left for you to do until all the packages "
+"have been installed. How quickly this happens depends on the number of "
+"packages you have selected and your computer's speed."
+msgstr ""
+
+#. Tag: para
+#: Installing_Packages_common-para-2.xml:6
+#, no-c-format
+msgid ""
+"Fedora reports the installation progress on the screen as it writes the "
+"selected packages to your system. Network and DVD installations require no "
+"further action. If you are using CDs to install, Fedora prompts you to "
+"change discs periodically. After you insert a disc, select <guibutton>OK</"
+"guibutton> to resume the installation."
+msgstr ""
+
+#. Tag: para
+#: Installing_Packages_common-para-3.xml:6
+#, no-c-format
+msgid ""
+"After installation completes, select <guibutton>Reboot</guibutton> to "
+"restart your computer. Fedora ejects any loaded discs before the computer "
+"reboots."
+msgstr ""
+
+#. Tag: title
+#: Installing_Packages_common-title.xml:8
+#, no-c-format
+msgid "Installing Packages"
+msgstr ""
+
+#. Tag: title
+#: intro.xml:7
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:8
+#, no-c-format
+msgid ""
+"This guide covers installation of Fedora, a Linux distribution built on free "
+"and open source software. This manual helps you install Fedora on desktops, "
+"laptops, and servers. The installation system is easy to use even if you "
+"lack previous knowledge of Linux or computer networks. If you select default "
+"options, Fedora provides a complete desktop operating system, including "
+"productivity applications, Internet utilities, and desktop tools."
+msgstr ""
+
+#. Tag: para
+#: intro.xml:16
+#, no-c-format
+msgid ""
+"This document does not detail all of the features of the installation system."
+msgstr ""
+
+#. Tag: title
+#: intro.xml:19
+#, no-c-format
+msgid "Background"
+msgstr ""
+
+#. Tag: title
+#: intro.xml:21
+#, no-c-format
+msgid "About Fedora"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:22
+#, no-c-format
+msgid ""
+"To find out more about Fedora, refer to <ulink url=\"http://fedoraproject."
+"org/\"></ulink>. To read other documentation on Fedora related topics, refer "
+"to <ulink url=\"http://docs.fedoraproject.org/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: intro.xml:26
+#, no-c-format
+msgid "Getting Additional Help"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:27
+#, no-c-format
+msgid ""
+"For information on additional help resources for Fedora, visit <ulink url="
+"\"http://fedoraproject.org/wiki/Communicate\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: intro.xml:32
+#, no-c-format
+msgid "About This Document"
+msgstr ""
+
+#. Tag: title
+#: intro.xml:34
+#, no-c-format
+msgid "Goals"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:35
+#, no-c-format
+msgid "This guide helps a reader:"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:38
+#, no-c-format
+msgid "Understand how to locate the Fedora distribution online"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:42
+#, no-c-format
+msgid "Create configuration data that allows a computer to boot Fedora"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:46
+#, no-c-format
+msgid "Understand and interact with the Fedora installation program"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:50
+#, no-c-format
+msgid "Complete basic post-installation configuration of a Fedora system"
+msgstr ""
+
+#. Tag: title
+#: intro.xml:55
+#, no-c-format
+msgid "Other Sources of Documentation"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:56
+#, no-c-format
+msgid ""
+"This guide does not cover use of Fedora. To learn how to use an installed "
+"Fedora system, refer to <ulink url=\"http://docs.fedoraproject.org/\"></"
+"ulink> for other documentation."
+msgstr ""
+
+#. Tag: title
+#: intro.xml:62
+#, no-c-format
+msgid "Audience"
+msgstr ""
+
+#. Tag: para
+#: intro.xml:63
+#, no-c-format
+msgid ""
+"This guide is intended for new and intermediate Fedora users. Advanced "
+"Fedora users with questions about detailed operation of expert installation "
+"features should consult the Anaconda development mailing list at <ulink url="
+"\"http://www.redhat.com/archives/anaconda-devel-list/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: iSCSI.xml:7
+#, no-c-format
+msgid "ISCSI disks"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:8
+#, no-c-format
+msgid ""
+"<firstterm>Internet Small Computer System Interface</firstterm> (iSCSI) is a "
+"protocol that allows computers to communicate with storage devices by SCSI "
+"requests and responses carried over TCP/IP. Because iSCSI is based on the "
+"standard SCSI protocols, it uses some terminology from SCSI. The device on "
+"the SCSI bus to which requests get sent (and which answers these requests) "
+"is known as the <firstterm>target</firstterm> and the device issuing "
+"requests is known as the <firstterm>initiator</firstterm>. In other words, "
+"an iSCSI disk is a target and the iSCSI software equivalent of a SCSI "
+"controller or SCSI Host Bus Adapter (HBA) is called an initiator. This "
+"appendix only covers Linux as an iSCSI initiator: how Linux uses iSCSI "
+"disks, but not how Linux hosts iSCSI disks."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:10
+#, no-c-format
+msgid ""
+"Linux has a software iSCSI initiator in the kernel that takes the place and "
+"form of a SCSI HBA driver and therefore allows Linux to use iSCSI disks. "
+"However, as iSCSI is a fully network-based protocol, iSCSI initiator support "
+"needs more than just the ability to send SCSI packets over the network. "
+"Before Linux can use an iSCSI target, Linux must find the target on the "
+"network and make a connection to it. In some cases, Linux must send "
+"authentication information to gain access to the target. Linux must also "
+"detect any failure of the network connection and must establish a new "
+"connection, including logging in again if necessary."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:12
+#, no-c-format
+msgid ""
+"The discovery, connection, and logging in is handled in userspace by the "
+"<application>iscsiadm</application> utility, and the error handling is also "
+"handled in userspace by <application>iscsid</application>."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:14
+#, no-c-format
+msgid ""
+"Both <application>iscsiadm</application> and <application>iscsid</"
+"application> are part of the <application>iscsi-initiator-utils</"
+"application> package under Fedora."
+msgstr ""
+
+#. Tag: title
+#: iSCSI.xml:18
+#, no-c-format
+msgid "iSCSI disks in <application>anaconda</application>"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:19
+#, no-c-format
+msgid ""
+"<application>Anaconda</application> can discover (and then log in to) iSCSI "
+"disks in two ways:"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:23
+#, no-c-format
+msgid ""
+"When anaconda starts, it checks if the BIOS or add-on boot ROMs of the "
+"system support <firstterm>iSCSI Boot Firmware Table</firstterm> (iBFT), a "
+"BIOS extension for systems which can boot from iSCSI. If the BIOS supports "
+"iBFT, <application>anaconda</application> will read the iSCSI target "
+"information for the configured boot disk from the BIOS and log in to this "
+"target, making it available as an installation target."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:26
+#, no-c-format
+msgid ""
+"The initial partitioning screen presents you with an <guilabel>Advanced "
+"storage configuration</guilabel> button that allows you to add iSCSI target "
+"information like the discovery IP-address. <application>Anaconda</"
+"application> will probe the given IP-address and log in to any targets that "
+"it finds. See <xref linkend=\"s1-advanced-storage-x86\"/> for the details "
+"that you can specify for iSCSI targets."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:30
+#, no-c-format
+msgid ""
+"While <application>anaconda</application> uses <application>iscsiadm</"
+"application> to find and log into iSCSI targets, <application>iscsiadm</"
+"application> automatically stores any information about these targets "
+"iscsiadm iSCSI database. <application>Anaconda</application> then copies "
+"this database to the installed system and marks any iSCSI targets not used "
+"for <filename>/</filename> so that the system will automatically log in to "
+"them when it starts. If <filename>/</filename> is placed on an iSCSI target, "
+"<application>initrd</application> will log into this target and "
+"<application>anaconda</application> does not include this target in start up "
+"scripts to avoid multiple attempts to log into the same target."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:32
+#, no-c-format
+msgid ""
+"If <filename>/</filename> is placed on an iSCSI target, "
+"<application>anaconda</application> sets <application>NetworkManager</"
+"application> to ignore any network interfaces that were active during the "
+"installation process. These interfaces will also be configured by "
+"<application>initrd</application> when the system starts. If "
+"<application>NetworkManager</application> were to reconfigure these "
+"interfaces, the system would lose its connection to <filename>/</filename>."
+msgstr ""
+
+#. Tag: title
+#: iSCSI.xml:37
+#, no-c-format
+msgid "iSCSI disks during start up"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:38
+#, no-c-format
+msgid ""
+"ISCSI-related events might occur at a number of points while the system "
+"starts:"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:42
+#, no-c-format
+msgid ""
+"The init script in the <application>initrd</application> will log in to "
+"iSCSI targets used for <filename>/</filename> (if any). This is done using "
+"the <application>iscsistart</application> utility (which can do this without "
+"requiring <application>iscsid</application> to run)."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:45
+#, no-c-format
+msgid ""
+"When the root filesystem has been mounted and the various service "
+"initscripts get run, the <application>iscsid</application> initscript will "
+"get called. This script will then start <application>iscsid</application> if "
+"any iSCSI targets are used for <filename>/</filename>, or if any targets in "
+"the iSCSI database are marked to be logged in to automatically."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:48
+#, no-c-format
+msgid ""
+"After the classic network service script has been run (or would have been "
+"run if enabled) the iscsi initscript will run. If the network is accessible, "
+"this will log in to any targets in the iSCSI database which are marked to be "
+"logged in to automatically. If the network is not accessible, this script "
+"will exit quietly."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:51
+#, no-c-format
+msgid ""
+"When using <application>NetworkManager</application> to access the network "
+"(instead of the classic network service script), "
+"<application>NetworkManager</application> will call the iscsi initscript. "
+"See: <filename>/etc/NetworkManager/dispatcher.d/04-iscsi</filename>"
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:53
+#, no-c-format
+msgid ""
+"Because <application>NetworkManager</application> is installed in <filename>/"
+"usr</filename>, you cannot use it to configure network access if <filename>/"
+"usr</filename> is on network-attached storage such as an iSCSI target."
+msgstr ""
+
+#. Tag: para
+#: iSCSI.xml:58
+#, no-c-format
+msgid ""
+"If <application>iscsid</application> is not needed as the system starts, it "
+"will not start automatically. If you start <application>iscsiadm</"
+"application>, <application>iscsiadm</application> will start "
+"<application>iscsid</application> in turn."
+msgstr ""
+
+#. Tag: para
+#: Key_Board_Configuration-x86.xml:16
+#, no-c-format
+msgid ""
+"Using your mouse, select the correct layout type (for example, U.S. English) "
+"for the keyboard you would prefer to use for the installation and as the "
+"system default (refer to the figure below)."
+msgstr ""
+
+#. Tag: para
+#: Key_Board_Configuration-x86.xml:26
+#, no-c-format
+msgid "Keyboard configuration screen"
+msgstr ""
+
+#. Tag: primary
+#: Key_Board_Configuration_x86_ppc-indexterm-1.xml:9
+#, no-c-format
+msgid "keymap"
+msgstr ""
+
+#. Tag: secondary
+#: Key_Board_Configuration_x86_ppc-indexterm-1.xml:10
+#, no-c-format
+msgid "selecting type of keyboard"
+msgstr ""
+
+#. Tag: para
+#: Key_Board_Configuration_x86_ppc-para-1.xml:8
+#, no-c-format
+msgid ""
+"Once you have made your selection, click <guibutton>Next</guibutton> to "
+"continue."
+msgstr ""
+
+#. Tag: para
+#: Key_Board_Configuration_x86_ppc-para-2.xml:9
+#, no-c-format
+msgid ""
+"To change your keyboard layout type after you have completed the "
+"installation, use the <application>Keyboard Configuration Tool</application>."
+msgstr ""
+
+#. Tag: para
+#: Key_Board_Configuration_x86_ppc-para-2.xml:12
+#, no-c-format
+msgid ""
+"Type the <command>system-config-keyboard</command> command in a shell prompt "
+"to launch the <application>Keyboard Configuration Tool</application>. If you "
+"are not root, it prompts you for the root password to continue."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:5
+#, no-c-format
+msgid "Kickstart Installations"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:8
+#, no-c-format
+msgid "<secondary>kickstart</secondary>"
+msgstr ""
+
+#. Tag: see
+#: Kickstart2.xml:9
+#, no-c-format
+msgid "<see>kickstart installations</see>"
+msgstr ""
+
+#. Tag: primary
+#: Kickstart2.xml:12 Kickstart2.xml:73 Kickstart2.xml:1155 Kickstart2.xml:2671
+#: Kickstart2.xml:2709 Kickstart2.xml:2721 Kickstart2.xml:2732
+#: Kickstart2.xml:2760 Kickstart2.xml:2803 Kickstart2.xml:2818
+#: Kickstart2.xml:2832 Kickstart2.xml:2849 Kickstart2.xml:2880
+#, no-c-format
+msgid "<primary>kickstart installations</primary>"
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:15
+#, no-c-format
+msgid "What are Kickstart Installations?"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:17
+#, no-c-format
+msgid ""
+"Many system administrators would prefer to use an automated installation "
+"method to install Fedora on their machines. To answer this need, Red Hat "
+"created the kickstart installation method. Using kickstart, a system "
+"administrator can create a single file containing the answers to all the "
+"questions that would normally be asked during a typical installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:21
+#, no-c-format
+msgid ""
+"Kickstart files can be kept on a single server system and read by individual "
+"computers during the installation. This installation method can support the "
+"use of a single kickstart file to install Fedora on multiple machines, "
+"making it ideal for network and system administrators."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:25
+#, no-c-format
+msgid "Kickstart provides a way for users to automate a Fedora installation."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:30
+#, no-c-format
+msgid "How Do You Perform a Kickstart Installation?"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:32
+#, no-c-format
+msgid ""
+"Kickstart installations can be performed using a local CD-ROM, a local hard "
+"drive, or via NFS, FTP, or HTTP."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:36
+#, no-c-format
+msgid "To use kickstart, you must:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:42
+#, no-c-format
+msgid "Create a kickstart file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:48
+#, no-c-format
+msgid ""
+"Create a boot media with the kickstart file or make the kickstart file "
+"available on the network."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:54
+#, no-c-format
+msgid "Make the installation tree available."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:60
+#, no-c-format
+msgid "Start the kickstart installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:66
+#, no-c-format
+msgid "This chapter explains these steps in detail."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:71
+#, no-c-format
+msgid "Creating the Kickstart File"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:74
+#, no-c-format
+msgid "file format"
+msgstr ""
+
+#. Tag: primary
+#: Kickstart2.xml:77 Kickstart2.xml:81 Kickstart2.xml:191 Kickstart2.xml:195
+#: Kickstart2.xml:219 Kickstart2.xml:248 Kickstart2.xml:275 Kickstart2.xml:296
+#: Kickstart2.xml:301 Kickstart2.xml:468 Kickstart2.xml:528 Kickstart2.xml:593
+#: Kickstart2.xml:607 Kickstart2.xml:642 Kickstart2.xml:677 Kickstart2.xml:758
+#: Kickstart2.xml:802 Kickstart2.xml:825 Kickstart2.xml:839 Kickstart2.xml:848
+#: Kickstart2.xml:996 Kickstart2.xml:1008 Kickstart2.xml:1065
+#: Kickstart2.xml:1090 Kickstart2.xml:1104 Kickstart2.xml:1129
+#: Kickstart2.xml:1146 Kickstart2.xml:1239 Kickstart2.xml:1279
+#: Kickstart2.xml:1293 Kickstart2.xml:1336 Kickstart2.xml:1349
+#: Kickstart2.xml:1502 Kickstart2.xml:1518 Kickstart2.xml:1523
+#: Kickstart2.xml:1731 Kickstart2.xml:1763 Kickstart2.xml:1863
+#: Kickstart2.xml:1897 Kickstart2.xml:1939 Kickstart2.xml:1963
+#: Kickstart2.xml:2012 Kickstart2.xml:2060 Kickstart2.xml:2082
+#: Kickstart2.xml:2096 Kickstart2.xml:2112 Kickstart2.xml:2136
+#: Kickstart2.xml:2152 Kickstart2.xml:2215 Kickstart2.xml:2253
+#: Kickstart2.xml:2301 Kickstart2.xml:2356 Kickstart2.xml:2373
+#: Kickstart2.xml:2426 Kickstart2.xml:2430 Kickstart2.xml:2443
+#: Kickstart2.xml:2460 Kickstart2.xml:2536 Kickstart2.xml:2540
+#: Kickstart2.xml:2595 Kickstart2.xml:2599 Kickstart2.xml:2713
+#: Kickstart2.xml:2725 Kickstart2.xml:2736 Kickstart2.xml:2764
+#: Kickstart2.xml:2822
+#, no-c-format
+msgid "kickstart file"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:78
+#, no-c-format
+msgid "format of"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:82
+#, no-c-format
+msgid "what it looks like"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:84
+#, no-c-format
+msgid ""
+"The kickstart file is a simple text file, containing a list of items, each "
+"identified by a keyword. You can create it by using the "
+"<application>Kickstart Configurator</application> application, or writing it "
+"from scratch. The Fedora installation program also creates a sample "
+"kickstart file based on the options that you selected during installation. "
+"It is written to the file <filename>/root/anaconda-ks.cfg</filename>. You "
+"should be able to edit it with any text editor or word processor that can "
+"save files as ASCII text."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:88
+#, no-c-format
+msgid ""
+"First, be aware of the following issues when you are creating your kickstart "
+"file:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:94
+#, no-c-format
+msgid ""
+"Sections must be specified <emphasis>in order</emphasis>. Items within the "
+"sections do not have to be in a specific order unless otherwise specified. "
+"The section order is:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:100
+#, no-c-format
+msgid ""
+"Command section — Refer to <xref linkend=\"s1-kickstart2-options\"/> "
+"for a list of kickstart options. You must include the required options."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:106
+#, no-c-format
+msgid ""
+"The <command>%packages</command> section — Refer to <xref linkend=\"s1-"
+"kickstart2-packageselection\"/> for details."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:112
+#, no-c-format
+msgid ""
+"The <command>%pre</command> and <command>%post</command> sections — "
+"These two sections can be in any order and are not required. Refer to <xref "
+"linkend=\"s1-kickstart2-preinstallconfig\"/> and <xref linkend=\"s1-"
+"kickstart2-postinstallconfig\"/> for details."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:121
+#, no-c-format
+msgid "Items that are not required can be omitted."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:127
+#, no-c-format
+msgid ""
+"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)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:134
+#, no-c-format
+msgid ""
+"Lines starting with a pound (also known as hash) sign (#) are treated as "
+"comments and are ignored."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:140
+#, no-c-format
+msgid ""
+"For kickstart <emphasis>upgrades</emphasis>, the following items are "
+"required:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:146
+#, no-c-format
+msgid "Language"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:158
+#, no-c-format
+msgid "Device specification (if device is needed to perform the installation)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:164
+#, no-c-format
+msgid "Keyboard setup"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:170
+#, no-c-format
+msgid "The <command>upgrade</command> keyword"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:176
+#, no-c-format
+msgid "Boot loader configuration"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:182
+#, no-c-format
+msgid ""
+"If any other items are specified for an upgrade, those items are ignored "
+"(note that this includes package selection)."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:189
+#, no-c-format
+msgid "Kickstart Options"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:192 Kickstart2.xml:2444
+#, no-c-format
+msgid "options"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:198
+#, no-c-format
+msgid ""
+"The following options can be placed in a kickstart file. If you prefer to "
+"use a graphical interface for creating your kickstart file, use the "
+"<application>Kickstart Configurator</application> application. Refer to "
+"<xref linkend=\"ch-redhat-config-kickstart\"/> for details."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:206
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:214
+#, no-c-format
+msgid "<command>autopart</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:220
+#, no-c-format
+msgid "autopart"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:222
+#, no-c-format
+msgid ""
+"Automatically create partitions — 1 GB or more root (<filename>/</"
+"filename>) 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 <command>part</command> directive."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:228
+#, no-c-format
+msgid ""
+"<command>--encrypted</command> — Should all devices with support be "
+"encrypted by default? This is equivalent to checking the <guilabel>Encrypt</"
+"guilabel> checkbox on the initial partitioning screen."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:233
+#, no-c-format
+msgid ""
+"<command>--passphrase=</command> — Provide a default system-wide "
+"passphrase for all encrypted devices."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:243
+#, no-c-format
+msgid "<command>ignoredisk</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:249
+#, no-c-format
+msgid "ignoredisk"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:251
+#, no-c-format
+msgid ""
+"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 <literal>ignoredisk</literal>, 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:255
+#, no-c-format
+msgid ""
+"The <literal>ignoredisk</literal> option is also useful if you have multiple "
+"paths to your disks."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:259
+#, no-c-format
+msgid "The syntax is:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:262
+#, no-c-format
+msgid "ignoredisk --drives=<replaceable>drive1,drive2</replaceable>,..."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:263
+#, no-c-format
+msgid ""
+"where <replaceable>driveN</replaceable> is one of <literal>sda</literal>, "
+"<literal>sdb</literal>,..., <literal>hda</literal>,... etc."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:270
+#, no-c-format
+msgid "<command>autostep</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:276 Kickstart2.xml:2906
+#, no-c-format
+msgid "autostep"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:278
+#, no-c-format
+msgid ""
+"Similar to <command>interactive</command> except it goes to the next screen "
+"for you. It is used mostly for debugging."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:283
+#, no-c-format
+msgid ""
+"<command>--autoscreenshot</command> — Take a screenshot at every step "
+"during installation and copy the images over to <command>/root/anaconda-"
+"screenshots</command> after installation is complete. This is most useful "
+"for documentation."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:292
+#, no-c-format
+msgid "<command>auth</command> or <command>authconfig</command> (required)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:297
+#, no-c-format
+msgid "auth"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:302
+#, no-c-format
+msgid "authconfig"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:304
+#, no-c-format
+msgid ""
+"Sets up the authentication options for the system. It is similar to the "
+"<command>authconfig</command> command, which can be run after the install. "
+"By default, passwords are normally encrypted and are not shadowed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:311
+#, no-c-format
+msgid ""
+"<command>--enablemd5</command> — Use md5 encryption for user passwords."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:317
+#, no-c-format
+msgid ""
+"<command>--enablenis</command> — Turns on NIS support. By default, "
+"<command>--enablenis</command> uses whatever domain it finds on the network. "
+"A domain should almost always be set by hand with the <command>--nisdomain=</"
+"command> option."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:323
+#, no-c-format
+msgid ""
+"<command>--nisdomain=</command> — NIS domain name to use for NIS "
+"services."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:329
+#, no-c-format
+msgid ""
+"<command>--nisserver=</command> — Server to use for NIS services "
+"(broadcasts by default)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:335
+#, no-c-format
+msgid ""
+"<command>--useshadow</command> or <command>--enableshadow</command> — "
+"Use shadow passwords."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:341
+#, no-c-format
+msgid ""
+"<command>--enableldap</command> — Turns on LDAP support in <filename>/"
+"etc/nsswitch.conf</filename>, allowing your system to retrieve information "
+"about users (UIDs, home directories, shells, etc.) from an LDAP directory. "
+"To use this option, you must install the <filename>nss_ldap</filename> "
+"package. You must also specify a server and a base DN (distinguished name) "
+"with <command>--ldapserver=</command> and <command>--ldapbasedn=</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:348
+#, no-c-format
+msgid ""
+"<command>--enableldapauth</command> — Use LDAP as an authentication "
+"method. This enables the <filename>pam_ldap</filename> module for "
+"authentication and changing passwords, using an LDAP directory. To use this "
+"option, you must have the <filename>nss_ldap</filename> package installed. "
+"You must also specify a server and a base DN with <command>--ldapserver=</"
+"command> and <command>--ldapbasedn=</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:358
+#, no-c-format
+msgid ""
+"<command>--ldapserver=</command> — If you specified either <command>--"
+"enableldap</command> or <command>--enableldapauth</command>, use this option "
+"to specify the name of the LDAP server to use. This option is set in the "
+"<filename>/etc/ldap.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:365
+#, no-c-format
+msgid ""
+"<command>--ldapbasedn=</command> — If you specified either <command>--"
+"enableldap</command> or <command>--enableldapauth</command>, use this option "
+"to specify the DN in your LDAP directory tree under which user information "
+"is stored. This option is set in the <filename>/etc/ldap.conf</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:372
+#, no-c-format
+msgid ""
+"<command>--enableldaptls</command> — Use TLS (Transport Layer "
+"Security) lookups. This option allows LDAP to send encrypted usernames and "
+"passwords to an LDAP server before authentication."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:378
+#, no-c-format
+msgid ""
+"<command>--enablekrb5</command> — 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 <command>/usr/"
+"sbin/useradd</command> command. If you use this option, you must have the "
+"<filename>pam_krb5</filename> package installed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:385
+#, no-c-format
+msgid ""
+"<command>--krb5realm=</command> — The Kerberos 5 realm to which your "
+"workstation belongs."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:391
+#, no-c-format
+msgid ""
+"<command>--krb5kdc=</command> — The KDC (or KDCs) that serve requests "
+"for the realm. If you have multiple KDCs in your realm, separate their names "
+"with commas (,)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:397
+#, no-c-format
+msgid ""
+"<command>--krb5adminserver=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:403
+#, no-c-format
+msgid ""
+"<command>--enablehesiod</command> — 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 <filename>/usr/share/doc/glibc-2.x.x/"
+"README.hesiod</filename>, which is included in the <filename>glibc</"
+"filename> package. Hesiod is an extension of DNS that uses DNS records to "
+"store information about users, groups, and various other items."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:410
+#, no-c-format
+msgid ""
+"<command>--hesiodlhs</command> — The Hesiod LHS (\"left-hand side\") "
+"option, set in <filename>/etc/hesiod.conf</filename>. This option is used by "
+"the Hesiod library to determine the name to search DNS for when looking up "
+"information, similar to LDAP's use of a base DN."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:417
+#, no-c-format
+msgid ""
+"<command>--hesiodrhs</command> — The Hesiod RHS (\"right-hand side\") "
+"option, set in <filename>/etc/hesiod.conf</filename>. This option is used by "
+"the Hesiod library to determine the name to search DNS for when looking up "
+"information, similar to LDAP's use of a base DN."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:422
+#, no-c-format
+msgid ""
+"To look up user information for \"jim\", the Hesiod library looks up "
+"<emphasis>jim.passwd<LHS><RHS></emphasis>, which should resolve "
+"to a TXT record that looks like what his passwd entry would look like "
+"(<computeroutput>jim:*:501:501:Jungle Jim:/home/jim:/bin/bash</"
+"computeroutput>). For groups, the situation is identical, except "
+"<emphasis>jim.group<LHS><RHS></emphasis> would be used."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:426
+#, no-c-format
+msgid ""
+"Looking up users and groups by number is handled by making \"501.uid\" a "
+"CNAME for \"jim.passwd\", and \"501.gid\" a CNAME for \"jim.group\". Note "
+"that the library does not place a period <keycap>.</keycap> in front of the "
+"LHS and RHS values when performing a search. Therefore the LHS and RHS "
+"values need to have a period placed in front of them in order if they "
+"require this."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:433
+#, no-c-format
+msgid ""
+"<command>--enablesmbauth</command> — 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 <command>/usr/"
+"sbin/useradd</command> command to make their accounts known to the "
+"workstation. To use this option, you must have the <filename>pam_smb</"
+"filename> package installed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:441
+#, no-c-format
+msgid ""
+"<command>--smbservers=</command> — The name of the server(s) to use "
+"for SMB authentication. To specify more than one server, separate the names "
+"with commas (,)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:447
+#, no-c-format
+msgid ""
+"<command>--smbworkgroup=</command> — The name of the workgroup for the "
+"SMB servers."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:453
+#, no-c-format
+msgid ""
+"<command>--enablecache</command> — Enables the <command>nscd</command> "
+"service. The <command>nscd</command> 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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:464
+#, no-c-format
+msgid "<command>bootloader</command> (required)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:469
+#, no-c-format
+msgid "bootloader"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:471
+#, no-c-format
+msgid ""
+"Specifies how the boot loader should be installed. This option is required "
+"for both installations and upgrades."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:481
+#, no-c-format
+msgid ""
+"<command>--append=</command> — Specifies kernel parameters. To specify "
+"multiple parameters, separate them with spaces. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:484
+#, no-c-format
+msgid "bootloader --location=mbr --append=\"hdd=ide-scsi ide=nodma\""
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:488
+#, no-c-format
+msgid ""
+"<command>--driveorder</command> — Specify which drive is first in the "
+"BIOS boot order. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:491
+#, no-c-format
+msgid "bootloader --driveorder=sda,hda"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:495
+#, no-c-format
+msgid ""
+"<command>--location=</command> — Specifies where the boot record is "
+"written. Valid values are the following: <command>mbr</command> (the "
+"default), <command>partition</command> (installs the boot loader on the "
+"first sector of the partition containing the kernel), or <command>none</"
+"command> (do not install the boot loader)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:502
+#, no-c-format
+msgid ""
+"<command>--password=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:508
+#, no-c-format
+msgid ""
+"<command>--md5pass=</command> — If using GRUB, similar to <command>--"
+"password=</command> except the password should already be encrypted."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:514
+#, no-c-format
+msgid ""
+"<command>--upgrade</command> — Upgrade the existing boot loader "
+"configuration, preserving the old entries. This option is only available for "
+"upgrades."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:524
+#, no-c-format
+msgid "<command>clearpart</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:529
+#, no-c-format
+msgid "clearpart"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:531
+#, no-c-format
+msgid ""
+"Removes partitions from the system, prior to creation of new partitions. By "
+"default, no partitions are removed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:538
+#, no-c-format
+msgid ""
+"If the <command>clearpart</command> command is used, then the <command>--"
+"onpart</command> command cannot be used on a logical partition."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:547
+#, no-c-format
+msgid "<command>--all</command> — Erases all partitions from the system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:553
+#, no-c-format
+msgid ""
+"<command>--drives=</command> — 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:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:556
+#, no-c-format
+msgid "clearpart --drives=hda,hdb --all"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:560
+#, no-c-format
+msgid ""
+"<command>--initlabel</command> — Initializes the disk label to the "
+"default for your architecture (for example <command>msdos</command> for x86 "
+"and <command>gpt</command> for Itanium). 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:570
+#, no-c-format
+msgid "<command>--linux</command> — Erases all Linux partitions."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:579
+#, no-c-format
+msgid ""
+"<command>--none</command> (default) — Do not remove any partitions."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:589
+#, no-c-format
+msgid "<command>cmdline</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:594
+#, no-c-format
+msgid "cmdline"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:596
+#, no-c-format
+msgid ""
+"Perform the installation in a completely non-interactive command line mode. "
+"Any prompts for interaction halts the install. This mode is useful on IBM "
+"System z systems with the x3270 console."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:603
+#, no-c-format
+msgid "<command>device</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:608
+#, no-c-format
+msgid "device"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:610
+#, no-c-format
+msgid ""
+"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 <command>device</"
+"command> command, which tells the installation program to install extra "
+"modules, is in this format:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:614
+#, no-c-format
+msgid ""
+"device <replaceable><type></replaceable> <replaceable><"
+"moduleName></replaceable> --opts=<replaceable><options></"
+"replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:618
+#, no-c-format
+msgid ""
+"<replaceable><type></replaceable> — Replace with either "
+"<command>scsi</command> or <command>eth</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:624
+#, no-c-format
+msgid ""
+"<replaceable><moduleName></replaceable> — Replace with the name "
+"of the kernel module which should be installed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:630
+#, no-c-format
+msgid ""
+"<command>--opts=</command> — Mount options to use for mounting the NFS "
+"export. Any options that can be specified in <filename>/etc/fstab</filename> "
+"for an NFS mount are allowed. The options are listed in the <command>nfs(5)</"
+"command> man page. Multiple options are separated with a comma."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:638
+#, no-c-format
+msgid "<command>driverdisk</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:643 Kickstart2.xml:2951
+#, no-c-format
+msgid "driverdisk"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:645
+#, no-c-format
+msgid ""
+"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 <command>driverdisk</command> "
+"command to tell the installation program where to look for the driver disk."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:649
+#, no-c-format
+msgid ""
+"driverdisk <replaceable><partition></replaceable> [--"
+"type=<replaceable><fstype></replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:650
+#, no-c-format
+msgid ""
+"Alternatively, a network location can be specified for the driver diskette:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:653
+#, no-c-format
+msgid ""
+"driverdisk --source=ftp://path/to/dd.img\n"
+"driverdisk --source=http://path/to/dd.img\n"
+"driverdisk --source=nfs:host:/path/to/img"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:657
+#, no-c-format
+msgid ""
+"<replaceable><partition></replaceable> — Partition containing "
+"the driver disk."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:663
+#, no-c-format
+msgid ""
+"<command>--type=</command> — File system type (for example, vfat or "
+"ext2)."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:673
+#, no-c-format
+msgid "<command>firewall</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:678
+#, no-c-format
+msgid "firewall"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:680
+#, no-c-format
+msgid ""
+"This option corresponds to the <guilabel>Firewall Configuration</guilabel> "
+"screen in the installation program:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:683
+#, no-c-format
+msgid ""
+"firewall --enabled|--disabled [--trust=] <replaceable><device></"
+"replaceable> [--port=]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:686
+#, no-c-format
+msgid ""
+"<command>--enabled</command> or <command>--enable</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:692
+#, no-c-format
+msgid ""
+"<command>--disabled</command> or <command>--disable</command> — Do not "
+"configure any iptables rules."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:698
+#, no-c-format
+msgid ""
+"<command>--trust=</command> — 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 <command>--trust eth0 --trust eth1</command>. "
+"Do NOT use a comma-separated format such as <command>--trust eth0, eth1</"
+"command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:705
+#, no-c-format
+msgid ""
+"<replaceable><incoming></replaceable> — Replace with one or more "
+"of the following to allow the specified services through the firewall."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:712
+#, no-c-format
+msgid "--ssh"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:718
+#, no-c-format
+msgid "--telnet"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:724
+#, no-c-format
+msgid "--smtp"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:730
+#, no-c-format
+msgid "--http"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:736
+#, no-c-format
+msgid "--ftp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:743
+#, no-c-format
+msgid ""
+"<command>--port=</command> — 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 <command>imap:tcp</command>. "
+"Numeric ports can also be specified explicitly; for example, to allow UDP "
+"packets on port 1234 through, specify <command>1234:udp</command>. To "
+"specify multiple ports, separate them by commas."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:754
+#, no-c-format
+msgid "<command>firstboot</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:759
+#, no-c-format
+msgid "firstboot"
+msgstr ""
+
+#. Tag: application
+#: Kickstart2.xml:763
+#, no-c-format
+msgid "Setup Agent"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:765
+#, no-c-format
+msgid "via Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:766
+#, no-c-format
+msgid ""
+"Determine whether the <application>Setup Agent</application> starts the "
+"first time the system is booted. If enabled, the <command>firstboot</"
+"command> package must be installed. If not specified, this option is "
+"disabled by default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:775
+#, no-c-format
+msgid ""
+"<command>--enable</command> or <command>--enabled</command> — The "
+"<application>Setup Agent</application> is started the first time the system "
+"boots."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:781
+#, no-c-format
+msgid ""
+"<command>--disable</command> or <command>--disabled</command> — The "
+"<application>Setup Agent</application> is not started the first time the "
+"system boots."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:787
+#, no-c-format
+msgid ""
+"<command>--reconfig</command> — Enable the <application>Setup Agent</"
+"application> 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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:798
+#, no-c-format
+msgid "<command>halt</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:803
+#, no-c-format
+msgid "halt"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:805
+#, no-c-format
+msgid ""
+"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, the <command>reboot</"
+"command> option is used as default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:810
+#, no-c-format
+msgid ""
+"The <command>halt</command> option is roughly equivalent to the "
+"<command>shutdown -h</command> command."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:814
+#, no-c-format
+msgid ""
+"For other completion methods, refer to the <command>poweroff</command>, "
+"<command>reboot</command>, and <command>shutdown</command> kickstart options."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:821
+#, no-c-format
+msgid "<command>graphical</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:826 Kickstart2.xml:2991
+#, no-c-format
+msgid "graphical"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:828
+#, no-c-format
+msgid ""
+"Perform the kickstart installation in graphical mode. This is the default."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:835
+#, no-c-format
+msgid "<command>install</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:840
+#, no-c-format
+msgid "install"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:842
+#, no-c-format
+msgid ""
+"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 <command>cdrom</command>, <command>harddrive</"
+"command>, <command>nfs</command>, or <command>url</command> (for FTP or HTTP "
+"installations). The <command>install</command> command and the installation "
+"method command must be on separate lines."
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:849
+#, no-c-format
+msgid "installation methods"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:857
+#, no-c-format
+msgid ""
+"<command>cdrom</command> — Install from the first CD-ROM drive on the "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:866
+#, no-c-format
+msgid ""
+"<command>harddrive</command> — Install from a Red Hat installation "
+"tree on a local drive, which must be either vfat or ext2."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:873
+#, no-c-format
+msgid "--biospart="
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:876
+#, no-c-format
+msgid "BIOS partition to install from (such as 82)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:882
+#, no-c-format
+msgid "--partition="
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:885
+#, no-c-format
+msgid "Partition to install from (such as sdb2)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:892 Kickstart2.xml:928
+#, no-c-format
+msgid "--dir="
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:895 Kickstart2.xml:931
+#, no-c-format
+msgid ""
+"Directory containing the <filename><replaceable>variant</replaceable></"
+"filename> directory of the installation tree."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:901 Kickstart2.xml:947 Kickstart2.xml:961
+#, no-c-format
+msgid "For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:904
+#, no-c-format
+msgid "harddrive --partition=hdb2 --dir=/tmp/install-tree"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:911
+#, no-c-format
+msgid "<command>nfs</command> — Install from the NFS server specified."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:918
+#, no-c-format
+msgid "--server="
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:921
+#, no-c-format
+msgid "Server from which to install (hostname or IP)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:938
+#, no-c-format
+msgid "--opts="
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:941
+#, no-c-format
+msgid "Mount options to use for mounting the NFS export. (optional)"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:950
+#, no-c-format
+msgid "nfs --server=nfsserver.example.com --dir=/tmp/install-tree"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:957
+#, no-c-format
+msgid ""
+"<command>url</command> — Install from an installation tree on a remote "
+"server via FTP or HTTP."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:964
+#, no-c-format
+msgid ""
+"url --url http://<replaceable><server></replaceable>/<replaceable><"
+"dir></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:965
+#, no-c-format
+msgid "<para>or:</para>"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:968
+#, no-c-format
+msgid ""
+"url --url ftp://<replaceable><username></replaceable>:<replaceable><"
+"password>@<server></replaceable>/<replaceable><dir></"
+"replaceable>"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:991
+#, no-c-format
+msgid "<command>interactive</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:999
+#, no-c-format
+msgid ""
+"Uses the information provided in the kickstart file during the installation, "
+"but allow for inspection and modification of the values given. You are "
+"presented with each screen of the installation program with the values from "
+"the kickstart file. Either accept the values by clicking <guibutton>Next</"
+"guibutton> or change the values and click <guibutton>Next</guibutton> to "
+"continue. Refer to the <command>autostep</command> command."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1005
+#, no-c-format
+msgid "<command>iscsi</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1011
+#, no-c-format
+msgid "issci --ipaddr= [options]."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1018
+#, no-c-format
+msgid "<command>--target</command> —"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1024
+#, no-c-format
+msgid "<command>--port=</command> —"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1030
+#, no-c-format
+msgid "<command>--user=</command> —"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1036
+#, no-c-format
+msgid "<command>--password=</command> —"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1062
+#, no-c-format
+msgid "<command>key</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1066
+#, no-c-format
+msgid "<command>key</command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1068
+#, no-c-format
+msgid ""
+"Specify an installation key, which is needed to aid in package selection and "
+"identify your system for support purposes. This command is specific to Red "
+"Hat Enterprise Linux; it has no meaning for Fedora and will be ignored."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1075
+#, no-c-format
+msgid ""
+"<command>--skip</command> — Skip entering a key. Usually if the key "
+"command is not given, anaconda will pause at this step to prompt for a key. "
+"This option allows automated installation to continue if you do not have a "
+"key or do not want to provide one."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1085
+#, no-c-format
+msgid "<command>keyboard</command> (required)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1093
+#, no-c-format
+msgid ""
+"Sets system keyboard type. Here is the list of available keyboards on i386, "
+"Itanium, and Alpha machines:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1095
+#, no-c-format
+msgid ""
+"be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, \n"
+"de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, \n"
+"fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, \n"
+"is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, \n"
+"pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2,  ru_win, \n"
+"se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup,  speakup-lt, \n"
+"sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua,  uk, us, us-acentos"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1096
+#, no-c-format
+msgid ""
+"The file <filename>/usr/lib/python2.2/site-packages/rhpl/keyboard_models.py</"
+"filename> also contains this list and is part of the <filename>rhpl</"
+"filename> package."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1103
+#, no-c-format
+msgid "<command>lang</command> (required)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1105
+#, no-c-format
+msgid "lang"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1109
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1113
+#, no-c-format
+msgid "lang en_US"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1114
+#, no-c-format
+msgid ""
+"The file <filename>/usr/share/system-config-language/locale-list</filename> "
+"provides a list of the valid language codes in the first column of each line "
+"and is part of the <filename>system-config-language</filename> package."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1119
+#, no-c-format
+msgid ""
+"Certain languages (mainly Chinese, Japanese, Korean, and Indic languages) "
+"are not supported during text mode installation. If one of these languages "
+"is specified using the lang command, installation will continue in English "
+"though the running system will have the specified langauge by default."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1127
+#, no-c-format
+msgid "<command>langsupport</command> (deprecated)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1130
+#, no-c-format
+msgid "langsupport"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1135
+#, no-c-format
+msgid ""
+"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 <command>%packages</"
+"command> section of your kickstart file. For instance, adding support for "
+"French means you should add the following to <command>%packages</command>:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1139
+#, no-c-format
+msgid "@french-support"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1145
+#, no-c-format
+msgid "<command>logvol</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1147
+#, no-c-format
+msgid "logvol"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:1152
+#, no-c-format
+msgid "with kickstart"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:1156
+#, no-c-format
+msgid "<secondary>LVM</secondary>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1160
+#, no-c-format
+msgid ""
+"Create a logical volume for Logical Volume Management (LVM) with the syntax:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1163
+#, no-c-format
+msgid ""
+"logvol <replaceable><mntpoint></replaceable> --vgname=<replaceable><"
+"name></replaceable> --size=<replaceable><size></replaceable> --"
+"name=<replaceable><name></replaceable> <replaceable><options></"
+"replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1164 Kickstart2.xml:2260
+#, no-c-format
+msgid "The options are as follows:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1172
+#, no-c-format
+msgid ""
+"<command>--noformat</command> — Use an existing logical volume and do "
+"not format it."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1179
+#, no-c-format
+msgid ""
+"<command>--useexisting</command> — Use an existing logical volume and "
+"reformat it."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1185
+#, no-c-format
+msgid ""
+"<command>--fstype=</command> — Sets the file system type for the "
+"logical volume. Valid values are <command>xfs</command>, <command>ext2</"
+"command>, <command>ext3</command>, <command>ext4</command>, <command>swap</"
+"command>, <command>vfat</command>, and <command>hfs</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1192
+#, no-c-format
+msgid ""
+"<command>--fsoptions=</command> — Specifies a free form string of "
+"options to be used when mounting the filesystem. This string will be copied "
+"into the <filename>/etc/fstab</filename> file of the installed system and "
+"should be enclosed in quotes."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1198
+#, no-c-format
+msgid ""
+"<command>--bytes-per-inode=</command> — Specifies the size of inodes "
+"on the filesystem to be made on the logical volume. Not all filesystems "
+"support this option, so it is silently ignored for those cases."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1204
+#, no-c-format
+msgid ""
+"<command>--grow=</command> — Tells the logical volume to grow to fill "
+"available space (if any), or up to the maximum size setting."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1210
+#, no-c-format
+msgid ""
+"<command>--maxsize=</command> — The maximum size in megabytes when the "
+"logical volume is set to grow. Specify an integer value here, and do not "
+"append the number with MB."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1216
+#, no-c-format
+msgid ""
+"<command>--recommended=</command> — Determine the size of the logical "
+"volume automatically."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1222
+#, no-c-format
+msgid ""
+"<command>--percent=</command> — Specify the size of the logical volume "
+"as a percentage of available space in the volume group."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1230 Kickstart2.xml:2286
+#, no-c-format
+msgid ""
+"Create the partition first, create the logical volume group, and then create "
+"the logical volume. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1233
+#, no-c-format
+msgid ""
+"part pv.01 --size 3000 \n"
+"volgroup myvg pv.01\n"
+"logvol / --vgname=myvg --size=2000 --name=rootvol"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1238
+#, no-c-format
+msgid "<command>logging</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1240
+#, no-c-format
+msgid "logging"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1245
+#, no-c-format
+msgid ""
+"This command controls the error logging of anaconda during installation. It "
+"has no effect on the installed system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1252
+#, no-c-format
+msgid ""
+"<command>--host=</command> — Send logging information to the given "
+"remote host, which must be running a syslogd process configured to accept "
+"remote logging."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1258
+#, no-c-format
+msgid ""
+"<command>--port=</command> — If the remote syslogd process uses a port "
+"other than the default, it may be specified with this option."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1264
+#, no-c-format
+msgid ""
+"<command>--level=</command> — One of debug, info, warning, error, or "
+"critical."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1268
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1278
+#, no-c-format
+msgid "<command>mediacheck</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1285
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1292
+#, no-c-format
+msgid "<command>monitor</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1299
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1306
+#, no-c-format
+msgid ""
+"<command>--hsync=</command> — Specifies the horizontal sync frequency "
+"of the monitor."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1312
+#, no-c-format
+msgid ""
+"<command>--monitor=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1318
+#, no-c-format
+msgid "<command>--noprobe=</command> — Do not try to probe the monitor."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1325
+#, no-c-format
+msgid ""
+"<command>--vsync=</command> — Specifies the vertical sync frequency of "
+"the monitor."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1335
+#, no-c-format
+msgid "<command>mouse</command> (deprecated)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1337
+#, no-c-format
+msgid "mouse"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1342
+#, no-c-format
+msgid "The mouse keyword is deprecated."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1348
+#, no-c-format
+msgid "<command>network</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1355
+#, no-c-format
+msgid ""
+"Configures network information for the system. If the kickstart installation "
+"does not require networking (in other words, it is not installed over NFS, "
+"HTTP, or FTP), networking is not configured for the system. If the "
+"installation does require networking and network information is not provided "
+"in the kickstart file, the installation program assumes that the "
+"installation should be done over eth0 via a dynamic IP address (BOOTP/DHCP), "
+"and configures the final, installed system to determine its IP address "
+"dynamically. The <command>network</command> option configures networking "
+"information for kickstart installations via a network as well as for the "
+"installed system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1362
+#, no-c-format
+msgid ""
+"<command>--bootproto=</command> — One of <command>dhcp</command>, "
+"<command>bootp</command>, or <command>static</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1366
+#, no-c-format
+msgid ""
+"It defaults to <command>dhcp</command>. <command>bootp</command> and "
+"<command>dhcp</command> are treated the same."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1370
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1373
+#, no-c-format
+msgid "network --bootproto=dhcp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1374
+#, no-c-format
+msgid ""
+"To direct a machine to use BOOTP to obtain its networking configuration, use "
+"the following line in the kickstart file:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1377
+#, no-c-format
+msgid "network --bootproto=bootp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1378
+#, no-c-format
+msgid ""
+"The static method requires that you enter all the required networking "
+"information in the kickstart file. As the name implies, this information is "
+"static and are used during and after the installation. The line for static "
+"networking is more complex, as you must include all network configuration "
+"information on one line. You must specify the IP address, netmask, gateway, "
+"and nameserver. For example: (the \"\\\" indicates that this should be read "
+"as one continuous line):"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1381
+#, no-c-format
+msgid ""
+"network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 \\\n"
+"--gateway=10.0.2.254 --nameserver=10.0.2.1"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1382
+#, no-c-format
+msgid ""
+"If you use the static method, be aware of the following two restrictions:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1388
+#, no-c-format
+msgid ""
+"All static networking configuration information must be specified on "
+"<emphasis>one</emphasis> line; you cannot wrap lines using a backslash, for "
+"example."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1395
+#, no-c-format
+msgid ""
+"You can also configure multiple nameservers here. To do so, specify them as "
+"a comma-delimited list in the command line. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1397
+#, no-c-format
+msgid ""
+"network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 \\\n"
+"--gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1406
+#, no-c-format
+msgid ""
+"<command>--device=</command> — Used to select a specific Ethernet "
+"device for installation. Note that using <command>--device=</command> is not "
+"effective unless the kickstart file is a local file (such as "
+"<command>ks=floppy</command>), since the installation program configures the "
+"network to find the kickstart file. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1409
+#, no-c-format
+msgid "network --bootproto=dhcp --device=eth0"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1413
+#, no-c-format
+msgid ""
+"<command>--ip=</command> — IP address for the machine to be installed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1419
+#, no-c-format
+msgid "<command>--gateway=</command> — Default gateway as an IP address."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1425
+#, no-c-format
+msgid ""
+"<command>--nameserver=</command> — Primary nameserver, as an IP "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1431
+#, no-c-format
+msgid "<command>--nodns</command> — Do not configure any DNS server."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1437
+#, no-c-format
+msgid "<command>--netmask=</command> — Netmask for the installed system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1443
+#, no-c-format
+msgid ""
+"<command>--hostname=</command> — Hostname for the installed system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1449
+#, no-c-format
+msgid ""
+"<command>--ethtool=</command> — Specifies additional low-level "
+"settings for the network device which will be passed to the ethtool program."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1455
+#, no-c-format
+msgid ""
+"<command>--essid=</command> — The network ID for wireless networks."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1461
+#, no-c-format
+msgid ""
+"<command>--wepkey=</command> — The encryption key for wireless "
+"networks."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1467
+#, no-c-format
+msgid ""
+"<command>--onboot=</command> — Whether or not to enable the device at "
+"boot time."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1473
+#, no-c-format
+msgid "<command>--class=</command> — The DHCP class."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1479
+#, no-c-format
+msgid "<command>--mtu=</command> — The MTU of the device."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1485
+#, no-c-format
+msgid "<command>--noipv4</command> — Disable IPv4 on this device."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1491
+#, no-c-format
+msgid "<command>--noipv6</command> — Disable IPv6 on this device."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1501
+#, no-c-format
+msgid "<command>multipath</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1503
+#, no-c-format
+msgid "multipath"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1508
+#, no-c-format
+msgid "multipath --name= --device= --rule="
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1519
+#, no-c-format
+msgid "part"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1526
+#, no-c-format
+msgid ""
+"<command>part</command> or <command>partition</command> (required for "
+"installs, ignored for upgrades)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1529
+#, no-c-format
+msgid "Creates a partition on the system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1533
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1540
+#, no-c-format
+msgid ""
+"All partitions created are formatted as part of the installation process "
+"unless <command>--noformat</command> and <command>--onpart</command> are "
+"used."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1548
+#, no-c-format
+msgid ""
+"For a detailed example of <command>part</command> in action, refer to <xref "
+"linkend=\"s2-kickstart2-options-part-examples\"/>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1556
+#, no-c-format
+msgid ""
+"<replaceable><mntpoint></replaceable> — The <replaceable><"
+"mntpoint></replaceable> is where the partition is mounted and must be of "
+"one of the following forms:"
+msgstr ""
+
+#. Tag: filename
+#: Kickstart2.xml:1563
+#, no-c-format
+msgid "/<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1566
+#, no-c-format
+msgid ""
+"For example, <command>/</command>, <command>/usr</command>, <command>/home</"
+"command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1576
+#, no-c-format
+msgid "The partition is used as swap space."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1580
+#, no-c-format
+msgid ""
+"To determine the size of the swap partition automatically, use the "
+"<command>--recommended</command> option:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1583
+#, no-c-format
+msgid "swap --recommended"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1585
+#, no-c-format
+msgid ""
+"The recommended maximum swap size for machines with less than 2GB of RAM is "
+"twice the amount of RAM. For machines with 2GB or more, this recommendation "
+"changes to 2GB plus the amount of RAM."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1591
+#, no-c-format
+msgid "raid.<replaceable><id></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1594
+#, no-c-format
+msgid ""
+"The partition is used for software RAID (refer to <command>raid</command>)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1601
+#, no-c-format
+msgid "pv.<replaceable><id></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1604
+#, no-c-format
+msgid "The partition is used for LVM (refer to <command>logvol</command>)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1612
+#, no-c-format
+msgid ""
+"<command>--size=</command> — The minimum partition size in megabytes. "
+"Specify an integer value here such as 500. Do not append the number with MB."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1618
+#, no-c-format
+msgid ""
+"<command>--grow</command> — Tells the partition to grow to fill "
+"available space (if any), or up to the maximum size setting."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1624
+#, no-c-format
+msgid ""
+"If you use <command>--grow=</command> without setting <command>--maxsize=</"
+"command> on a swap partition, <application>Anaconda</application> 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1630
+#, no-c-format
+msgid ""
+"<command>--maxsize=</command> — The maximum partition size in "
+"megabytes when the partition is set to grow. Specify an integer value here, "
+"and do not append the number with MB."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1636
+#, no-c-format
+msgid ""
+"<command>--noformat</command> — Tells the installation program not to "
+"format the partition, for use with the <command>--onpart</command> command."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1642
+#, no-c-format
+msgid ""
+"<command>--onpart=</command> or <command>--usepart=</command> — Put "
+"the partition on the <emphasis>already existing</emphasis> device. For "
+"example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1645
+#, no-c-format
+msgid "partition /home --onpart=hda1"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1646
+#, no-c-format
+msgid ""
+"puts <filename>/home</filename> on <filename>/dev/hda1</filename>, which "
+"must already exist."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1652
+#, no-c-format
+msgid ""
+"<command>--ondisk=</command> or <command>--ondrive=</command> — Forces "
+"the partition to be created on a particular disk. For example, <command>--"
+"ondisk=sdb</command> puts the partition on the second SCSI disk on the "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1658
+#, no-c-format
+msgid ""
+"<command>--asprimary</command> — Forces automatic allocation of the "
+"partition as a primary partition, or the partitioning fails."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1664
+#, no-c-format
+msgid ""
+"<command>--type=</command> (replaced by <command>fstype</command>) — "
+"This option is no longer available. Use <command>fstype</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1670
+#, no-c-format
+msgid ""
+"<command>--fstype=</command> — Sets the file system type for the "
+"partition. Valid values are <command>xfs</command>, <command>ext2</command>, "
+"<command>ext3</command>, <command>ext4</command>, <command>swap</command>, "
+"<command>vfat</command>, and <command>hfs</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1676
+#, no-c-format
+msgid ""
+"<command>--start=</command> — Specifies the starting cylinder for the "
+"partition. It requires that a drive be specified with <command>--ondisk=</"
+"command> or <command>ondrive=</command>. It also requires that the ending "
+"cylinder be specified with <command>--end=</command> or the partition size "
+"be specified with <command>--size=</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1683
+#, no-c-format
+msgid ""
+"<command>--end=</command> — Specifies the ending cylinder for the "
+"partition. It requires that the starting cylinder be specified with "
+"<command>--start=</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1689
+#, no-c-format
+msgid ""
+"<command>--bytes-per-inode=</command> — Specifies the size of inodes "
+"on the filesystem to be made on the partition. Not all filesystems support "
+"this option, so it is silently ignored for those cases."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1695
+#, no-c-format
+msgid ""
+"<command>--recommended</command> — Determine the size of the partition "
+"automatically."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1701
+#, no-c-format
+msgid ""
+"<command>--onbiosdisk</command> — Forces the partition to be created "
+"on a particular disk as discovered by the BIOS."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1707
+#, no-c-format
+msgid ""
+"<command>--encrypted</command> — Specifies that this partition should "
+"be encrypted."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1713
+#, no-c-format
+msgid ""
+"<command>--passphrase=</command> — Specifies the passphrase to use "
+"when encrypting this partition. Without the above <command>--encrypted</"
+"command> option, this option does nothing. If no passphrase is specified, "
+"the default system-wide one is used, or the installer will stop and prompt "
+"if there is no default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1722
+#, no-c-format
+msgid ""
+"If partitioning fails for any reason, diagnostic messages appear on virtual "
+"console 3."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1732
+#, no-c-format
+msgid "poweroff"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1734
+#, no-c-format
+msgid "<command>poweroff</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1737
+#, no-c-format
+msgid ""
+"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 "
+"<command>reboot</command> option is used as default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1742
+#, no-c-format
+msgid ""
+"The <command>poweroff</command> option is roughly equivalent to the "
+"<command>shutdown -p</command> command."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1749
+#, no-c-format
+msgid ""
+"The <command>poweroff</command> 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1755
+#, no-c-format
+msgid ""
+"For other completion methods, refer to the <command>halt</command>, "
+"<command>reboot</command>, and <command>shutdown</command> kickstart options."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1764
+#, no-c-format
+msgid "raid"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:1769
+#, no-c-format
+msgid "<secondary>kickstart installations</secondary>"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1770
+#, no-c-format
+msgid "<command>raid</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1773
+#, no-c-format
+msgid "Assembles a software RAID device. This command is of the form:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1776
+#, no-c-format
+msgid ""
+"raid <replaceable><mntpoint></replaceable> --level=<replaceable><"
+"level></replaceable> --device=<replaceable><mddevice></replaceable> "
+"<replaceable><partitions*></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1780
+#, no-c-format
+msgid ""
+"<replaceable><mntpoint></replaceable> — Location where the RAID "
+"file system is mounted. If it is <filename>/</filename>, the RAID level must "
+"be 1 unless a boot partition (<filename>/boot</filename>) is present. If a "
+"boot partition is present, the <filename>/boot</filename> partition must be "
+"level 1 and the root (<filename>/</filename>) partition can be any of the "
+"available types. The <replaceable><partitions*></replaceable> (which "
+"denotes that multiple partitions can be listed) lists the RAID identifiers "
+"to add to the RAID array."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1788
+#, no-c-format
+msgid "<command>--level=</command> — RAID level to use (0, 1, or 5)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1794
+#, no-c-format
+msgid ""
+"<command>--device=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1800
+#, no-c-format
+msgid ""
+"<command>--bytes-per-inode=</command> — Specifies the size of inodes "
+"on the filesystem to be made on the RAID device. Not all filesystems support "
+"this option, so it is silently ignored for those cases."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1806
+#, no-c-format
+msgid ""
+"<command>--spares=</command> — Specifies the number of spare drives "
+"allocated for the RAID array. Spare drives are used to rebuild the array in "
+"case of drive failure."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1812
+#, no-c-format
+msgid ""
+"<command>--fstype=</command> — Sets the file system type for the RAID "
+"array. Valid values are <command>xfs</command>, <command>ext2</command>, "
+"<command>ext3</command>, <command>ext4</command>, <command>swap</command>, "
+"<command>vfat</command>, and <command>hfs</command>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1818
+#, no-c-format
+msgid ""
+"<command>--fsoptions=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1824
+#, no-c-format
+msgid ""
+"<command>--noformat</command> — Use an existing RAID device and do not "
+"format the RAID array."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1830
+#, no-c-format
+msgid ""
+"<command>--useexisting</command> — Use an existing RAID device and "
+"reformat it."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1836
+#, no-c-format
+msgid ""
+"<command>--encrypted</command> — Specifies that this RAID device "
+"should be encrypted."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1842
+#, no-c-format
+msgid ""
+"<command>--passphrase=</command> — Specifies the passphrase to use "
+"when encrypting this RAID device. Without the above <command>--encrypted</"
+"command> option, this option does nothing. If no passphrase is specified, "
+"the default system-wide one is used, or the installer will stop and prompt "
+"if there is no default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1847
+#, no-c-format
+msgid ""
+"The following example shows how to create a RAID level 1 partition for "
+"<filename>/</filename>, and a RAID level 5 for <filename>/usr</filename>, "
+"assuming there are three SCSI disks on the system. It also creates three "
+"swap partitions, one on each drive."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1851
+#, no-c-format
+msgid ""
+"part raid.01 --size=60 --ondisk=sda\n"
+"part raid.02 --size=60 --ondisk=sdb \n"
+"part raid.03 --size=60 --ondisk=sdc"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1852
+#, no-c-format
+msgid ""
+"part swap --size=128 --ondisk=sda  \n"
+"part swap --size=128 --ondisk=sdb  \n"
+"part swap --size=128 --ondisk=sdc"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1853
+#, no-c-format
+msgid ""
+"part raid.11 --size=1 --grow --ondisk=sda  \n"
+"part raid.12 --size=1 --grow --ondisk=sdb  \n"
+"part raid.13 --size=1 --grow --ondisk=sdc"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1854
+#, no-c-format
+msgid ""
+"raid / --level=1 --device=md0 raid.01 raid.02 raid.03  \n"
+"raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1855
+#, no-c-format
+msgid ""
+"For a detailed example of <command>raid</command> in action, refer to <xref "
+"linkend=\"s2-kickstart2-options-part-examples\"/>."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1866
+#, no-c-format
+msgid "<command>reboot</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1869
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1873
+#, no-c-format
+msgid ""
+"The <command>reboot</command> option is roughly equivalent to the "
+"<command>shutdown -r</command> command."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1880
+#, no-c-format
+msgid ""
+"Use of the <command>reboot</command> option <emphasis>may</emphasis> result "
+"in an endless installation loop, depending on the installation media and "
+"method."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1884
+#, no-c-format
+msgid ""
+"The <command>reboot</command> option is the default completion method if no "
+"other methods are explicitly specified in the kickstart file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1889
+#, no-c-format
+msgid ""
+"For other completion methods, refer to the <command>halt</command>, "
+"<command>poweroff</command>, and <command>shutdown</command> kickstart "
+"options."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1896
+#, no-c-format
+msgid "<command>repo</command> (optional)"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1903
+#, no-c-format
+msgid ""
+"Configures additional yum repositories that may be used as sources for "
+"package installation. Multiple repo lines may be specified."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1907
+#, no-c-format
+msgid ""
+"repo --name=<replaceable><repoid></replaceable> [--"
+"baseurl=<replaceable><url></replaceable>| --"
+"mirrorlist=<replaceable><url></replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1911
+#, no-c-format
+msgid ""
+"<command>--name=</command> — The repo id. This option is required."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1917
+#, no-c-format
+msgid ""
+"<command>--baseurl=</command> — 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."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1923
+#, no-c-format
+msgid ""
+"<command>--mirrorlist=</command> — 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."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1935
+#, no-c-format
+msgid "<command>rootpw</command> (required)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1940
+#, no-c-format
+msgid "rootpw"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1942
+#, no-c-format
+msgid ""
+"Sets the system's root password to the <replaceable><password></"
+"replaceable> argument."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1945
+#, no-c-format
+msgid "rootpw [--iscrypted] <replaceable><password></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1949
+#, no-c-format
+msgid ""
+"<command>--iscrypted</command> — If this is present, the password "
+"argument is assumed to already be encrypted."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:1959
+#, no-c-format
+msgid "<command>selinux</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:1964
+#, no-c-format
+msgid "selinux"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1966
+#, no-c-format
+msgid ""
+"Sets the state of SELinux on the installed system. SELinux defaults to "
+"enforcing in anaconda."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:1970
+#, no-c-format
+msgid "selinux [--disabled|--enforcing|--permissive]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1975
+#, no-c-format
+msgid ""
+"<command>--enforcing</command> — Enables SELinux with the default "
+"targeted policy being enforced."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1982
+#, no-c-format
+msgid ""
+"If the <command>selinux</command> option is not present in the kickstart "
+"file, SELinux is enabled and set to <command>--enforcing</command> by "
+"default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1989
+#, no-c-format
+msgid ""
+"<command>--permissive</command> — Outputs warnings based on the "
+"SELinux policy, but does not actually enforce the policy."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:1995
+#, no-c-format
+msgid ""
+"<command>--disabled</command> — Disables SELinux completely on the "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2001
+#, no-c-format
+msgid ""
+"For complete information regarding SELinux for Fedora, refer to the "
+"<citetitle>Fedora &PRODVER; Security-Enhanced Linux User Guide</citetitle>."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2008
+#, no-c-format
+msgid "<command>services</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2013
+#, no-c-format
+msgid "services"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2015
+#, no-c-format
+msgid ""
+"Modifies the default set of services that will run under the default "
+"runlevel. The services listed in the disabled list will be disabled before "
+"the services listed in the enabled list are enabled."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2023
+#, no-c-format
+msgid ""
+"<command>--disabled</command> — Disable the services given in the "
+"comma separated list."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2029
+#, no-c-format
+msgid ""
+"<command>--enabled</command> — Enable the services given in the comma "
+"separated list."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2037
+#, no-c-format
+msgid "Do not include spaces in the list of services"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2038
+#, no-c-format
+msgid ""
+"If you include spaces in the comma-separated list, kickstart will enable or "
+"disable only the services up to the first space. For example:"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2042
+#, no-c-format
+msgid "services --disabled auditd, cups,smartd, nfslock"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2044
+#, no-c-format
+msgid ""
+"will disable only the <application>auditd</application> service. To disable "
+"all four services, this entry should include no spaces between services:"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2048
+#, no-c-format
+msgid "services --disabled auditd,cups,smartd,nfslock"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2056
+#, no-c-format
+msgid "<command>shutdown</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2061
+#, no-c-format
+msgid "shutdown"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2063
+#, no-c-format
+msgid ""
+"Shut down the system after the installation has successfully completed. "
+"During a kickstart installation, if no completion method is specified, the "
+"<command>reboot</command> option is used as default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2067
+#, no-c-format
+msgid ""
+"The <command>shutdown</command> option is roughly equivalent to the "
+"<command>shutdown</command> command."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2071
+#, no-c-format
+msgid ""
+"For other completion methods, refer to the <command>halt</command>, "
+"<command>poweroff</command>, and <command>reboot</command> kickstart options."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2078
+#, no-c-format
+msgid "<command>skipx</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2083
+#, no-c-format
+msgid "skipx"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2085
+#, no-c-format
+msgid "If present, X is not configured on the installed system."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2092
+#, no-c-format
+msgid "<command>text</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2097 Kickstart2.xml:3411
+#, no-c-format
+msgid "text"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2099
+#, no-c-format
+msgid ""
+"Perform the kickstart installation in text mode. Kickstart installations are "
+"performed in graphical mode by default."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2108
+#, no-c-format
+msgid "<command>timezone</command> (required)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2113
+#, no-c-format
+msgid "timezone"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2115
+#, no-c-format
+msgid ""
+"Sets the system time zone to <replaceable><timezone></replaceable> "
+"which may be any of the time zones listed by <command>timeconfig</command>."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2118
+#, no-c-format
+msgid "timezone [--utc] <replaceable><timezone></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2122
+#, no-c-format
+msgid ""
+"<command>--utc</command> — If present, the system assumes the hardware "
+"clock is set to UTC (Greenwich Mean) time."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2132
+#, no-c-format
+msgid "<command>upgrade</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2137
+#, no-c-format
+msgid "upgrade"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2139
+#, no-c-format
+msgid ""
+"Tells the system to upgrade an existing system rather than install a fresh "
+"system. You must specify one of <command>cdrom</command>, "
+"<command>harddrive</command>, <command>nfs</command>, or <command>url</"
+"command> (for FTP and HTTP) as the location of the installation tree. Refer "
+"to <command>install</command> for details."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2148
+#, no-c-format
+msgid "<command>user</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2153
+#, no-c-format
+msgid "user"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2155
+#, no-c-format
+msgid "Creates a new user on the system."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2159
+#, no-c-format
+msgid ""
+"user --name=<replaceable><username></replaceable> [--"
+"groups=<replaceable><list></replaceable>] [--homedir=<replaceable><"
+"homedir></replaceable>] [--password=<replaceable><password></"
+"replaceable>] [--iscrypted] [--shell=<replaceable><shell></"
+"replaceable>] [--uid=<replaceable><uid></replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2165
+#, no-c-format
+msgid ""
+"<command>--name=</command> — Provides the name of the user. This "
+"option is required."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2171
+#, no-c-format
+msgid ""
+"<command>--groups=</command> — In addition to the default group, a "
+"comma separated list of group names the user should belong to."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2177
+#, no-c-format
+msgid ""
+"<command>--homedir=</command> — The home directory for the user. If "
+"not provided, this defaults to /home/<replaceable><username></"
+"replaceable>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2183
+#, no-c-format
+msgid ""
+"<command>--password=</command> — The new user's password. If not "
+"provided, the account will be locked by default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2189
+#, no-c-format
+msgid ""
+"<command>--iscrypted=</command> — Is the password provided by --"
+"password already encrypted or not?"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2195
+#, no-c-format
+msgid ""
+"<command>--shell=</command> — The user's login shell. If not provided, "
+"this defaults to the system default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2201
+#, no-c-format
+msgid ""
+"<command>--uid=</command> — The user's UID. If not provided, this "
+"defaults to the next available non-system UID."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2211
+#, no-c-format
+msgid "<command>vnc</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2216 Kickstart2.xml:3458
+#, no-c-format
+msgid "<command>vnc</command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2218
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2222
+#, no-c-format
+msgid ""
+"vnc [--host=<replaceable><hostname></replaceable>] [--"
+"port=<replaceable><port></replaceable>] [--password=<replaceable><"
+"password></replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2227
+#, no-c-format
+msgid ""
+"<command>--host=</command> — Instead of starting a VNC server on the "
+"install machine, connect to the VNC viewer process listening on the given "
+"hostname."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2233
+#, no-c-format
+msgid ""
+"<command>--port=</command> — Provide a port that the remote VNC viewer "
+"process is listening on. If not provided, anaconda will use the VNC default."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2239
+#, no-c-format
+msgid ""
+"<command>--password=</command> — Set a password which must be provided "
+"to connect to the VNC session. This is optional, but recommended."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2249
+#, no-c-format
+msgid "<command>volgroup</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2254
+#, no-c-format
+msgid "volgroup"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2256
+#, no-c-format
+msgid "Use to create a Logical Volume Management (LVM) group with the syntax:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2259
+#, no-c-format
+msgid ""
+"volgroup <replaceable><name></replaceable> <replaceable><"
+"partition></replaceable> <replaceable><options></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2267
+#, no-c-format
+msgid ""
+"<command>--noformat</command> — Use an existing volume group and do "
+"not format it."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2273
+#, no-c-format
+msgid ""
+"<command>--useexisting</command> — Use an existing volume group and "
+"reformat it."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2279
+#, no-c-format
+msgid ""
+"<command>--pesize=</command> — Set the size of the physical extents."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2289
+#, no-c-format
+msgid ""
+"part pv.01 --size 3000 \n"
+"volgroup myvg pv.01 \n"
+"logvol / --vgname=myvg --size=2000 --name=rootvol"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2290
+#, no-c-format
+msgid ""
+"For a detailed example of <command>volgroup</command> in action, refer to "
+"<xref linkend=\"s2-kickstart2-options-part-examples\"/>."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2297
+#, no-c-format
+msgid "<command>xconfig</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2302
+#, no-c-format
+msgid "xconfig"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2304
+#, no-c-format
+msgid ""
+"Configures the X Window System. If this option is not given, the user must "
+"configure X manually during the installation, if X was installed; this "
+"option should not be used if X is not installed on the final system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2311
+#, no-c-format
+msgid ""
+"<command>--driver</command> — Specify the X driver to use for the "
+"video hardware."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2317
+#, no-c-format
+msgid ""
+"<command>--videoram=</command> — Specifies the amount of video RAM the "
+"video card has."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2323
+#, no-c-format
+msgid ""
+"<command>--defaultdesktop=</command> — Specify either GNOME or KDE to "
+"set the default desktop (assumes that GNOME Desktop Environment and/or KDE "
+"Desktop Environment has been installed through <command>%packages</command>)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2329
+#, no-c-format
+msgid ""
+"<command>--startxonboot</command> — Use a graphical login on the "
+"installed system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2335
+#, no-c-format
+msgid ""
+"<command>--resolution=</command> — Specify the default resolution for "
+"the X Window System on the installed system. Valid values are 640x480, "
+"800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be sure to "
+"specify a resolution that is compatible with the video card and monitor."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2342
+#, no-c-format
+msgid ""
+"<command>--depth=</command> — Specify the default color depth for the "
+"X Window System on the installed system. Valid values are 8, 16, 24, and 32. "
+"Be sure to specify a color depth that is compatible with the video card and "
+"monitor."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2352
+#, no-c-format
+msgid "<command>zerombr</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2357
+#, no-c-format
+msgid "zerombr"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2359
+#, no-c-format
+msgid ""
+"If <command>zerombr</command> is specified any invalid partition tables "
+"found on disks are initialized. This destroys all of the contents of disks "
+"with invalid partition tables."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2364
+#, no-c-format
+msgid ""
+"Note that this command was previously specified as <command>zerombr yes</"
+"command>. This form is now deprecated; you should now simply specify "
+"<command>zerombr</command> in your kickstart file instead."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2369
+#, no-c-format
+msgid "<command>zfcp</command> (optional)"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2374
+#, no-c-format
+msgid "zfcp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2376
+#, no-c-format
+msgid "Define a Fiber channel device (IBM System z)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2380
+#, no-c-format
+msgid ""
+"zfcp [--devnum=<replaceable><devnum></replaceable>] [--"
+"fcplun=<replaceable><fcplun></replaceable>] [--scsiid=<replaceable><"
+"scsiid></replaceable>] [--scsilun=<replaceable><scsilun></"
+"replaceable>] [--wwpn=<replaceable><wwpn></replaceable>]"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2422
+#, no-c-format
+msgid "<command>%include</command> (optional)"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2427
+#, no-c-format
+msgid "include contents of another file"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2431
+#, no-c-format
+msgid "%include"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2433
+#, no-c-format
+msgid ""
+"Use the <command>%include <replaceable>/path/to/file</replaceable></command> "
+"command to include the contents of another file in the kickstart file as "
+"though the contents were at the location of the <command>%include</command> "
+"command in the kickstart file."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2441
+#, no-c-format
+msgid "Advanced Partitioning Example"
+msgstr ""
+
+#. Tag: tertiary
+#: Kickstart2.xml:2445
+#, no-c-format
+msgid "partitioning examples"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2447
+#, no-c-format
+msgid ""
+"The following is a single, integrated example showing the "
+"<command>clearpart</command>, <command>raid</command>, <command>part</"
+"command>, <command>volgroup</command>, and <command>logvol</command> "
+"kickstart options in action:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2451
+#, no-c-format
+msgid ""
+"clearpart --drives=hda,hdc --initlabel  \n"
+"# Raid 1 IDE config \n"
+"part raid.11    --size 1000     --asprimary     --ondrive=hda \n"
+"part raid.12    --size 1000     --asprimary     --ondrive=hda \n"
+"part raid.13    --size 2000     --asprimary     --ondrive=hda \n"
+"part raid.14    --size 8000                     --ondrive=hda \n"
+"part raid.15    --size 1 --grow                 --ondrive=hda             \n"
+"part raid.21    --size 1000     --asprimary     --ondrive=hdc \n"
+"part raid.22    --size 1000     --asprimary     --ondrive=hdc \n"
+"part raid.23    --size 2000     --asprimary     --ondrive=hdc \n"
+"part raid.24    --size 8000                     --ondrive=hdc \n"
+"part raid.25    --size 1 --grow                 --ondrive=hdc  \n"
+"\n"
+"# You can add --spares=x  \n"
+"raid /          --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21 \n"
+"raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22 \n"
+"raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23 \n"
+"raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24 \n"
+"raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25  \n"
+"\n"
+"# LVM configuration so that we can resize /var and /usr/local later \n"
+"volgroup sysvg pv.01     \n"
+"logvol /var             --vgname=sysvg  --size=8000     --name=var \n"
+"logvol /var/freespace   --vgname=sysvg  --size=8000     --"
+"name=freespacetouse \n"
+"logvol /usr/local       --vgname=sysvg  --size=1 --grow --name=usrlocal"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2452
+#, no-c-format
+msgid ""
+"This advanced example implements LVM over RAID, as well as the ability to "
+"resize various directories for future growth."
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2461
+#, no-c-format
+msgid "package selection specification"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2463
+#, no-c-format
+msgid ""
+"Use the <command>%packages</command> command to begin a kickstart file "
+"section that lists the packages you would like to install (this is for "
+"installations only, as package selection during upgrades is not supported)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2467
+#, no-c-format
+msgid ""
+"Packages can be specified by group or by individual package name, including "
+"with globs using the asterisk. The installation program defines several "
+"groups that contain related packages. Refer to the "
+"<filename><replaceable>variant</replaceable>/repodata/comps-*.xml</filename> "
+"file on the first Fedora CD-ROM for a list of groups. Each group has an id, "
+"user visibility value, name, description, and package list. In the package "
+"list, the packages marked as mandatory are always installed if the group is "
+"selected, the packages marked default are selected by default if the group "
+"is selected, and the packages marked optional must be specifically selected "
+"even if the group is selected to be installed."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2471
+#, no-c-format
+msgid ""
+"In most cases, it is only necessary to list the desired groups and not "
+"individual packages. Note that the <command>Core</command> and "
+"<command>Base</command> groups are always selected by default, so it is not "
+"necessary to specify them in the <command>%packages</command> section."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2475
+#, no-c-format
+msgid "Here is an example <command>%packages</command> selection:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2478
+#, no-c-format
+msgid ""
+"%packages \n"
+"@ X Window System \n"
+"@ GNOME Desktop Environment \n"
+"@ Graphical Internet \n"
+"@ Sound and Video dhcp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2479
+#, no-c-format
+msgid ""
+"As you can see, groups are specified, one to a line, starting with an "
+"<command>@</command> symbol, a space, and then the full group name as given "
+"in the <filename>comps.xml</filename> file. Groups can also be specified "
+"using the id for the group, such as <computeroutput>gnome-desktop</"
+"computeroutput>. Specify individual packages with no additional characters "
+"(the <filename>dhcp</filename> line in the example above is an individual "
+"package)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2485
+#, no-c-format
+msgid ""
+"You can also specify which packages not to install from the default package "
+"list:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2488
+#, no-c-format
+msgid "-autofs"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2489
+#, no-c-format
+msgid ""
+"The following options are available for the <command>%packages</command> "
+"option:"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2496
+#, no-c-format
+msgid "--nobase"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2498
+#, no-c-format
+msgid ""
+"Do not install the @Base group. Use this option if you are trying to create "
+"a very small system."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2505
+#, no-c-format
+msgid "--resolvedeps"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2507
+#, no-c-format
+msgid ""
+"The --resolvedeps option has been deprecated. Dependencies are resolved "
+"automatically every time now."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2514
+#, no-c-format
+msgid "--ignoredeps"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2516
+#, no-c-format
+msgid ""
+"The --ignoredeps option has been deprecated. Dependencies are resolved "
+"automatically every time now."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2523
+#, no-c-format
+msgid "--ignoremissing"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2525
+#, no-c-format
+msgid ""
+"Ignore the missing packages and groups instead of halting the installation "
+"to ask if the installation should be aborted or continued. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2528
+#, no-c-format
+msgid "%packages --ignoremissing"
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2534
+#, no-c-format
+msgid "Pre-installation Script"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2537
+#, no-c-format
+msgid "pre-installation configuration"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2541
+#, no-c-format
+msgid "%pre"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2543
+#, no-c-format
+msgid ""
+"You can add commands to run on the system immediately after the <filename>ks."
+"cfg</filename> has been parsed. This section must be at the end of the "
+"kickstart file (after the commands) and must start with the <command>%pre</"
+"command> command. You can access the network in the <command>%pre</command> "
+"section; however, <firstterm>name service</firstterm> has not been "
+"configured at this point, so only IP addresses work."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2551
+#, no-c-format
+msgid ""
+"Note that the pre-install script is not run in the change root environment."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2558 Kickstart2.xml:2638
+#, no-c-format
+msgid "--interpreter <replaceable>/usr/bin/python</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2560 Kickstart2.xml:2640
+#, no-c-format
+msgid ""
+"Allows you to specify a different scripting language, such as Python. "
+"Replace <replaceable>/usr/bin/python</replaceable> with the scripting "
+"language of your choice."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2568
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2570
+#, no-c-format
+msgid "Here is an example <command>%pre</command> section:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2573
+#, no-c-format
+msgid ""
+"%pre  \n"
+"#!/bin/sh  \n"
+"hds=\"\" \n"
+"mymedia=\"\"  \n"
+"for file in /proc/ide/h* do   \n"
+"        mymedia=`cat $file/media`   \n"
+"        if [ $mymedia == \"disk\" ] ; then       \n"
+"                hds=\"$hds `basename $file`\"   \n"
+"        fi \n"
+"done  \n"
+"set $hds \n"
+"numhd=`echo $#`  \n"
+"drive1=`echo $hds | cut -d' ' -f1` \n"
+"drive2=`echo $hds | cut -d' ' -f2`  \n"
+"#Write out partition scheme based on whether there are 1 or 2 hard drives  \n"
+"if [ $numhd == \"2\" ] ; then   \n"
+"        #2 drives   \n"
+"        echo \"#partitioning scheme generated in %pre for 2 drives\" > /"
+"tmp/part-include   \n"
+"        echo \"clearpart --all\" >> /tmp/part-include   \n"
+"        echo \"part /boot --fstype ext3 --size 75 --ondisk hda\" >> /"
+"tmp/part-include   \n"
+"        echo \"part / --fstype ext3 --size 1 --grow --ondisk hda\" >> /"
+"tmp/part-include   \n"
+"        echo \"part swap --recommended --ondisk $drive1\" >> /tmp/part-"
+"include   \n"
+"        echo \"part /home --fstype ext3 --size 1 --grow --ondisk hdb\" >"
+"> /tmp/part-include \n"
+"else   \n"
+"        #1 drive   \n"
+"        echo \"#partitioning scheme generated in %pre for 1 drive\" > /"
+"tmp/part-include   \n"
+"        echo \"clearpart --all\" >> /tmp/part-include   \n"
+"        echo \"part /boot --fstype ext3 --size 75\" >> /tmp/part-"
+"includ   \n"
+"        echo \"part swap --recommended\" >> /tmp/part-include   \n"
+"        echo \"part / --fstype ext3 --size 2048\" >> /tmp/part-"
+"include   \n"
+"        echo \"part /home --fstype ext3 --size 2048 --grow\" >> /tmp/"
+"part-include \n"
+"fi"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2574
+#, no-c-format
+msgid ""
+"This script determines the number of hard drives in the system and writes a "
+"text file with a different partitioning scheme depending on whether it has "
+"one or two drives. Instead of having a set of partitioning commands in the "
+"kickstart file, include the line:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2578
+#, no-c-format
+msgid "%include /tmp/part-include"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2579
+#, no-c-format
+msgid "The partitioning commands selected in the script are used."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2586
+#, no-c-format
+msgid ""
+"The pre-installation script section of kickstart <emphasis>cannot</emphasis> "
+"manage multiple install trees or source media. This information must be "
+"included for each created ks.cfg file, as the pre-installation script occurs "
+"during the second stage of the installation process."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2593
+#, no-c-format
+msgid "Post-installation Script"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2596
+#, no-c-format
+msgid "post-installation configuration"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2600
+#, no-c-format
+msgid "%post"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2602
+#, no-c-format
+msgid ""
+"You have the option of adding commands to run on the system once the "
+"installation is complete. This section must be at the end of the kickstart "
+"file and must start with the <command>%post</command> command. This section "
+"is useful for functions such as installing additional software and "
+"configuring an additional nameserver."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2609
+#, no-c-format
+msgid ""
+"If you configured the network with static IP information, including a "
+"nameserver, you can access the network and resolve IP addresses in the "
+"<command>%post</command> section. If you configured the network for DHCP, "
+"the <filename>/etc/resolv.conf</filename> file has not been completed when "
+"the installation executes the <command>%post</command> section. You can "
+"access the network, but you can not resolve IP addresses. Thus, if you are "
+"using DHCP, you must specify IP addresses in the <command>%post</command> "
+"section."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2617
+#, no-c-format
+msgid ""
+"The post-install script is run in a chroot environment; therefore, "
+"performing tasks such as copying scripts or RPMs from the installation media "
+"do not work."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2624
+#, no-c-format
+msgid "--nochroot"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2626
+#, no-c-format
+msgid ""
+"Allows you to specify commands that you would like to run outside of the "
+"chroot environment."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2630
+#, no-c-format
+msgid ""
+"The following example copies the file <filename>/etc/resolv.conf</filename> "
+"to the file system that was just installed."
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2633
+#, no-c-format
+msgid "%post --nochroot cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf"
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2648
+#, no-c-format
+msgid "Examples"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2650
+#, no-c-format
+msgid "Register the system to a Red Hat Network Satellite:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2653
+#, no-c-format
+msgid ""
+"%post\n"
+"( # Note that in this example we run the entire %post section as a subshell "
+"for logging.\n"
+"wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash\n"
+"/usr/sbin/rhnreg_ks --activationkey=<replaceable><activationkey></"
+"replaceable>\n"
+"# End the subshell and capture any output to a post-install log file.\n"
+") 1>/root/post_install.log 2>&1"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2654
+#, no-c-format
+msgid "Run a script named <filename>runme</filename> from an NFS share:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2657
+#, no-c-format
+msgid ""
+"mkdir /mnt/temp \n"
+"mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w -- \n"
+"/mnt/temp/runme \n"
+"umount /mnt/temp"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2661
+#, no-c-format
+msgid ""
+"NFS file locking is <emphasis>not</emphasis> supported while in kickstart "
+"mode, therefore <command>-o nolock</command> is required when mounting an "
+"NFS mount."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2669
+#, no-c-format
+msgid "Making the Kickstart File Available"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2672
+#, no-c-format
+msgid "file locations"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2674
+#, no-c-format
+msgid "A kickstart file must be placed in one of the following locations:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2680
+#, no-c-format
+msgid "On a boot diskette"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2686
+#, no-c-format
+msgid "On a boot CD-ROM"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2692
+#, no-c-format
+msgid "On a network"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2698
+#, no-c-format
+msgid ""
+"Normally a kickstart file is copied to the boot diskette, or made available "
+"on the network. The network-based approach is most commonly used, as most "
+"kickstart installations tend to be performed on networked computers."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2702
+#, no-c-format
+msgid ""
+"Let us take a more in-depth look at where the kickstart file may be placed."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2707
+#, no-c-format
+msgid "Creating Kickstart Boot Media"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2710 Kickstart2.xml:2714
+#, no-c-format
+msgid "diskette-based"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2716
+#, no-c-format
+msgid ""
+"Diskette-based booting is no longer supported in Fedora. Installations must "
+"use CD-ROM or flash memory products for booting. However, the kickstart file "
+"may still reside on a diskette's top-level directory, and must be named "
+"<filename>ks.cfg</filename>."
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2722 Kickstart2.xml:2726
+#, no-c-format
+msgid "CD-ROM-based"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2728
+#, no-c-format
+msgid ""
+"To perform a CD-ROM-based kickstart installation, the kickstart file must be "
+"named <filename>ks.cfg</filename> and must be located in the boot CD-ROM's "
+"top-level directory. Since a CD-ROM is read-only, the file must be added to "
+"the directory used to create the image that is written to the CD-ROM. Refer "
+"to <xref linkend=\"s2-steps-make-cd\"/> for instructions on creating boot "
+"media; however, before making the <filename>file.iso</filename> image file, "
+"copy the <filename>ks.cfg</filename> kickstart file to the "
+"<filename>isolinux/</filename> directory."
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2733 Kickstart2.xml:2737
+#, no-c-format
+msgid "flash-based"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2739
+#, no-c-format
+msgid ""
+"To perform a pen-based flash memory kickstart installation, the kickstart "
+"file must be named <filename>ks.cfg</filename> and must be located in the "
+"flash memory's top-level directory. Create the boot image first, and then "
+"copy the <filename>ks.cfg</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2744
+#, no-c-format
+msgid ""
+"For example, the following transfers a boot image to the pen drive "
+"(<filename>/dev/sda</filename>) using the <command>dd</command> command:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2747
+#, no-c-format
+msgid "dd if=diskboot.img of=/dev/sda bs=1M"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2751
+#, no-c-format
+msgid ""
+"Creation of USB flash memory pen drives for booting is possible, but is "
+"heavily dependent on system hardware BIOS settings. Refer to your hardware "
+"manufacturer to see if your system supports booting to alternate devices."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2758
+#, no-c-format
+msgid "Making the Kickstart File Available on the Network"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2761 Kickstart2.xml:2765 Kickstart2.xml:2819
+#: Kickstart2.xml:2823
+#, no-c-format
+msgid "network-based"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2767
+#, no-c-format
+msgid ""
+"Network installations using kickstart are quite common, because system "
+"administrators can easily automate the installation on many networked "
+"computers quickly and painlessly. In general, the approach most commonly "
+"used is for the administrator to have both a BOOTP/DHCP server and an NFS "
+"server on the local network. The BOOTP/DHCP server is used to give the "
+"client system its networking information, while the actual files used during "
+"the installation are served by the NFS server. Often, these two servers run "
+"on the same physical machine, but they are not required to."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2771
+#, no-c-format
+msgid ""
+"To perform a network-based kickstart installation, you must have a BOOTP/"
+"DHCP server on your network, and it must include configuration information "
+"for the machine on which you are attempting to install Fedora. The BOOTP/"
+"DHCP server provides the client with its networking information as well as "
+"the location of the kickstart file."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2775
+#, no-c-format
+msgid ""
+"If a kickstart file is specified by the BOOTP/DHCP server, the client system "
+"attempts an NFS mount of the file's path, and copies the specified file to "
+"the client, using it as the kickstart file. The exact settings required vary "
+"depending on the BOOTP/DHCP server you use."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2779
+#, no-c-format
+msgid ""
+"Here is an example of a line from the <filename>dhcpd.conf</filename> file "
+"for the DHCP server:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2782
+#, no-c-format
+msgid ""
+"<filename>filename</filename> <replaceable>\"/usr/new-machine/kickstart/\"</"
+"replaceable>; next-server <replaceable>blarg.redhat.com;</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2783
+#, no-c-format
+msgid ""
+"Note that you should replace the value after <computeroutput>filename</"
+"computeroutput> with the name of the kickstart file (or the directory in "
+"which the kickstart file resides) and the value after <computeroutput>next-"
+"server</computeroutput> with the NFS server name."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2787
+#, no-c-format
+msgid ""
+"If the file name returned by the BOOTP/DHCP server ends with a slash (\"/"
+"\"), then it is interpreted as a path only. In this case, the client system "
+"mounts that path using NFS, and searches for a particular file. The file "
+"name the client searches for is:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2790
+#, no-c-format
+msgid ""
+"<filename><replaceable><ip-addr></replaceable>-kickstart</filename>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2791
+#, no-c-format
+msgid ""
+"The <filename><replaceable><ip-addr></replaceable></filename> section "
+"of the file name should be replaced with the client's IP address in dotted "
+"decimal notation. For example, the file name for a computer with an IP "
+"address of 10.10.0.1 would be <filename>10.10.0.1-kickstart</filename>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2795
+#, no-c-format
+msgid ""
+"Note that if you do not specify a server name, then the client system "
+"attempts to use the server that answered the BOOTP/DHCP request as its NFS "
+"server. If you do not specify a path or file name, the client system tries "
+"to mount <filename>/kickstart</filename> from the BOOTP/DHCP server and "
+"tries to find the kickstart file using the same <filename><replaceable><"
+"ip-addr></replaceable>-kickstart</filename> file name as described above."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2801
+#, no-c-format
+msgid "Making the Installation Tree Available"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2804
+#, no-c-format
+msgid "installation tree"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2806
+#, no-c-format
+msgid ""
+"The kickstart installation must access an <firstterm>installation tree</"
+"firstterm>. An installation tree is a copy of the binary Fedora CD-ROMs with "
+"the same directory structure."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2810
+#, no-c-format
+msgid ""
+"If you are performing a CD-based installation, insert the Fedora CD-ROM #1 "
+"into the computer before starting the kickstart installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2814
+#, no-c-format
+msgid ""
+"If you are performing a hard drive installation, make sure the ISO images of "
+"the binary Fedora CD-ROMs are on a hard drive in the computer."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2825
+#, no-c-format
+msgid ""
+"If you are performing a network-based (NFS, FTP, or HTTP) installation, you "
+"must make the installation tree available over the network. Refer to <xref "
+"linkend=\"s1-steps-network-installs-x86\"/> for details."
+msgstr ""
+
+#. Tag: title
+#: Kickstart2.xml:2830
+#, no-c-format
+msgid "Starting a Kickstart Installation"
+msgstr ""
+
+#. Tag: primary
+#: Kickstart2.xml:2836
+#, no-c-format
+msgid "<primary>kickstart</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Kickstart2.xml:2837
+#, no-c-format
+msgid "how the file is found"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2839
+#, no-c-format
+msgid ""
+"To begin a kickstart installation, you must boot the system from boot media "
+"you have made or the Fedora CD-ROM #1, and enter a special boot command at "
+"the boot prompt. The installation program looks for a kickstart file if the "
+"<command>ks</command> command line argument is passed to the kernel."
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2845
+#, no-c-format
+msgid "CD-ROM #1 and Diskette"
+msgstr ""
+
+#. Tag: tertiary
+#: Kickstart2.xml:2851
+#, no-c-format
+msgid "from CD-ROM #1 with a diskette"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2852
+#, no-c-format
+msgid ""
+"The <userinput>linux ks=floppy</userinput> command also works if the "
+"<filename>ks.cfg</filename> file is located on a vfat or ext2 file system on "
+"a diskette and you boot from the Fedora CD-ROM #1."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2856
+#, no-c-format
+msgid ""
+"An alternate boot command is to boot off the Fedora CD-ROM #1 and have the "
+"kickstart file on a vfat or ext2 file system on a diskette. To do so, enter "
+"the following command at the <prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2859
+#, no-c-format
+msgid "linux ks=hd:fd0:/ks.cfg"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2866
+#, no-c-format
+msgid "With Driver Disk"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2868
+#, no-c-format
+msgid ""
+"If you need to use a driver disk with kickstart, specify the <userinput>dd</"
+"userinput> option as well. For example, to boot off a boot diskette and use "
+"a driver disk, enter the following command at the <prompt>boot:</prompt> "
+"prompt:"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2871
+#, no-c-format
+msgid "linux ks=floppy dd"
+msgstr ""
+
+#. Tag: term
+#: Kickstart2.xml:2876
+#, no-c-format
+msgid "Boot CD-ROM"
+msgstr ""
+
+#. Tag: tertiary
+#: Kickstart2.xml:2882
+#, no-c-format
+msgid "from a boot CD-ROM"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2883
+#, no-c-format
+msgid ""
+"If the kickstart file is on a boot CD-ROM as described in <xref linkend=\"s2-"
+"kickstart2-boot-media\"/>, insert the CD-ROM into the system, boot the "
+"system, and enter the following command at the <prompt>boot:</prompt> prompt "
+"(where <filename>ks.cfg</filename> is the name of the kickstart file):"
+msgstr ""
+
+#. Tag: screen
+#: Kickstart2.xml:2886
+#, no-c-format
+msgid "linux ks=cdrom:/ks.cfg"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2891
+#, no-c-format
+msgid "Other options to start a kickstart installation are as follows:"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2897
+#, no-c-format
+msgid "askmethod"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2899
+#, no-c-format
+msgid ""
+"Do not automatically use the CD-ROM as the install source if we detect a "
+"Fedora CD in your CD-ROM drive."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2908
+#, no-c-format
+msgid "Make kickstart non-interactive."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2915
+#, no-c-format
+msgid "debug"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2917
+#, no-c-format
+msgid "Start up pdb immediately."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2924
+#, no-c-format
+msgid "<command>dd</command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2926
+#, no-c-format
+msgid "Use a driver disk."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2933
+#, no-c-format
+msgid "dhcpclass=<replaceable><class></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2935
+#, no-c-format
+msgid ""
+"Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this "
+"value using \"option vendor-class-identifier\"."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2942
+#, no-c-format
+msgid "dns=<replaceable><dns></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2944
+#, no-c-format
+msgid "Comma separated list of nameservers to use for a network installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2953
+#, no-c-format
+msgid "Same as 'dd'."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2960
+#, no-c-format
+msgid "expert"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2962
+#, no-c-format
+msgid "Turns on special features:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2966
+#, no-c-format
+msgid "allows partitioning of removable media"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2972
+#, no-c-format
+msgid "prompts for a driver disk"
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:2982
+#, no-c-format
+msgid "gateway=<replaceable><gw></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2984
+#, no-c-format
+msgid "Gateway to use for a network installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:2993
+#, no-c-format
+msgid "Force graphical install. Required to have ftp/http use GUI."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3000
+#, no-c-format
+msgid "<command>isa</command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3002
+#, no-c-format
+msgid "Prompt user for ISA devices configuration."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3009
+#, no-c-format
+msgid "ip=<replaceable><ip></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3011
+#, no-c-format
+msgid "IP to use for a network installation, use 'dhcp' for DHCP."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3018
+#, no-c-format
+msgid "keymap=<replaceable><keymap></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3020
+#, no-c-format
+msgid ""
+"Keyboard layout to use. Valid values are those which can be used for the "
+"'keyboard' kickstart command."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3027
+#, no-c-format
+msgid ""
+"ks=nfs:<replaceable><server></replaceable>:/<replaceable><path></"
+"replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3029
+#, no-c-format
+msgid ""
+"The installation program looks for the kickstart file on the NFS server "
+"<replaceable><server></replaceable>, as file <replaceable><path>"
+"</replaceable>. The installation program uses DHCP to configure the Ethernet "
+"card. For example, if your NFS server is server.example.com and the "
+"kickstart file is in the NFS share <filename>/mydir/ks.cfg</filename>, the "
+"correct boot command would be <command>ks=nfs:server.example.com:/mydir/ks."
+"cfg</command>."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3036
+#, no-c-format
+msgid ""
+"ks=http://<replaceable><server></replaceable>/<replaceable><path>"
+"</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3038
+#, no-c-format
+msgid ""
+"The installation program looks for the kickstart file on the HTTP server "
+"<replaceable><server></replaceable>, as file <replaceable><path>"
+"</replaceable>. The installation program uses DHCP to configure the Ethernet "
+"card. For example, if your HTTP server is server.example.com and the "
+"kickstart file is in the HTTP directory <filename>/mydir/ks.cfg</filename>, "
+"the correct boot command would be <command>ks=http://server.example.com/"
+"mydir/ks.cfg</command>."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3045
+#, no-c-format
+msgid "ks=floppy"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3047
+#, no-c-format
+msgid ""
+"The installation program looks for the file <filename>ks.cfg</filename> on a "
+"vfat or ext2 file system on the diskette in <filename>/dev/fd0</filename>."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3054
+#, no-c-format
+msgid "ks=floppy:/<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3056
+#, no-c-format
+msgid ""
+"The installation program looks for the kickstart file on the diskette in "
+"<filename>/dev/fd0</filename>, as file <replaceable><path></"
+"replaceable>."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3063
+#, no-c-format
+msgid ""
+"ks=hd:<replaceable><device></replaceable>:/<replaceable><file></"
+"replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3065
+#, no-c-format
+msgid ""
+"The installation program mounts the file system on <replaceable><"
+"device></replaceable> (which must be vfat or ext2), and look for the "
+"kickstart configuration file as <replaceable><file></replaceable> in "
+"that file system (for example, <command>ks=hd:sda3:/mydir/ks.cfg</command>)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3072
+#, no-c-format
+msgid "ks=file:/<replaceable><file></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3074
+#, no-c-format
+msgid ""
+"The installation program tries to read the file <replaceable><file></"
+"replaceable> from the file system; no mounts are done. This is normally used "
+"if the kickstart file is already on the <filename>initrd</filename> image."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3081
+#, no-c-format
+msgid "ks=cdrom:/<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3083
+#, no-c-format
+msgid ""
+"The installation program looks for the kickstart file on CD-ROM, as file "
+"<replaceable><path></replaceable>."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3090
+#, no-c-format
+msgid "<command>ks</command>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3092
+#, no-c-format
+msgid ""
+"If <command>ks</command> is used alone, the installation program configures "
+"the Ethernet card to use DHCP. The kickstart file is read from the "
+"\"bootServer\" from the DHCP response as if it is an NFS server sharing the "
+"kickstart file. By default, the bootServer is the same as the DHCP server. "
+"The name of the kickstart file is one of the following:"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3098
+#, no-c-format
+msgid ""
+"If DHCP is specified and the boot file begins with a <filename>/</filename>, "
+"the boot file provided by DHCP is looked for on the NFS server."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3104
+#, no-c-format
+msgid ""
+"If DHCP is specified and the boot file begins with something other than a "
+"<computeroutput>/</computeroutput>, the boot file provided by DHCP is looked "
+"for in the <filename>/kickstart</filename> directory on the NFS server."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3110
+#, no-c-format
+msgid ""
+"If DHCP did not specify a boot file, then the installation program tries to "
+"read the file <filename>/kickstart/1.2.3.4-kickstart</filename>, where "
+"<replaceable>1.2.3.4</replaceable> is the numeric IP address of the machine "
+"being installed."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3119
+#, no-c-format
+msgid "ksdevice=<replaceable><device></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3121
+#, no-c-format
+msgid ""
+"The installation program uses this network device to connect to the network. "
+"For example, consider a system connected to an NFS server through the eth1 "
+"device. To perform a kickstart installation on this system using a kickstart "
+"file from the NFS server, you would use the command <command>ks=nfs:"
+"<replaceable><server></replaceable>:/<replaceable><path></"
+"replaceable> ksdevice=eth1</command> at the <prompt>boot:</prompt> prompt."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3128
+#, no-c-format
+msgid "kssendmac"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3130
+#, no-c-format
+msgid ""
+"Adds HTTP headers to ks=http:// request that can be helpful for provisioning "
+"systems. Includes MAC address of all nics in CGI environment variables of "
+"the form: \"X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab\"."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3137
+#, no-c-format
+msgid "lang=<replaceable><lang></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3139
+#, no-c-format
+msgid ""
+"Language to use for the installation. This should be a language which is "
+"valid to be used with the 'lang' kickstart command."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3146
+#, no-c-format
+msgid "loglevel=<replaceable><level></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3148
+#, no-c-format
+msgid ""
+"Set the minimum level required for messages to be logged. Values for <"
+"level> are debug, info, warning, error, and critical. The default value "
+"is info."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3155
+#, no-c-format
+msgid "lowres"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3157
+#, no-c-format
+msgid "Force GUI installer to run at 640x480."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3166
+#, no-c-format
+msgid ""
+"Activates loader code to give user option of testing integrity of install "
+"source (if an ISO-based method)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3173
+#, no-c-format
+msgid "method=cdrom"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3175
+#, no-c-format
+msgid "Do a CDROM based installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3182
+#, no-c-format
+msgid "method=ftp://<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3184
+#, no-c-format
+msgid "Use <path> for an FTP installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3191
+#, no-c-format
+msgid ""
+"method=hd:<replaceable><dev></replaceable>:<replaceable><path></"
+"replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3195
+#, no-c-format
+msgid "Use <path> on <dev> for a hard drive installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3202
+#, no-c-format
+msgid "method=http://<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3204
+#, no-c-format
+msgid "Use <path> for an HTTP installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3211
+#, no-c-format
+msgid "method=nfs:<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3213
+#, no-c-format
+msgid "Use <path> for an NFS installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3220
+#, no-c-format
+msgid "netmask=<replaceable><nm></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3222
+#, no-c-format
+msgid "Netmask to use for a network installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3229
+#, no-c-format
+msgid "nofallback"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3231
+#, no-c-format
+msgid "If GUI fails exit."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3238
+#, no-c-format
+msgid "nofb"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3240
+#, no-c-format
+msgid ""
+"Do not load the VGA16 framebuffer required for doing text-mode installation "
+"in some languages."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3250
+#, no-c-format
+msgid "Do not load support for firewire devices."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3257
+#, no-c-format
+msgid "noipv6"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3259
+#, no-c-format
+msgid "Disable IPv6 networking during installation."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3266
+#, no-c-format
+msgid "nokill"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3268
+#, no-c-format
+msgid ""
+"A debugging option that prevents anaconda from terminating all running "
+"programs when a fatal error occurs."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3275
+#, no-c-format
+msgid "nomount"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3277
+#, no-c-format
+msgid ""
+"Don't automatically mount any installed Linux partitions in rescue mode."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3286
+#, no-c-format
+msgid "Do not auto-probe network devices."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3295
+#, no-c-format
+msgid "Do not attempt to load support for parallel ports."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3304
+#, no-c-format
+msgid ""
+"Don't pass keyboard/mouse info to stage 2 installer, good for testing "
+"keyboard and mouse config screens in stage2 installer during network "
+"installs."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3313
+#, no-c-format
+msgid "Ignore PCMCIA controller in system."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3322
+#, no-c-format
+msgid "Do not attempt to detect hw, prompts user instead."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3331
+#, no-c-format
+msgid "Do not put a shell on tty2 during install."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3338
+#, no-c-format
+msgid "nostorage"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3340
+#, no-c-format
+msgid "Do not auto-probe storage devices (SCSI, IDE, RAID)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3349
+#, no-c-format
+msgid "Do not load USB support (helps if install hangs early sometimes)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3358
+#, no-c-format
+msgid ""
+"Do not load usbstorage module in loader. May help with device ordering on "
+"SCSI systems."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3366
+#, no-c-format
+msgid "rescue"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3368
+#, no-c-format
+msgid "Run rescue environment."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3375
+#, no-c-format
+msgid "resolution=<replaceable><mode></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3377
+#, no-c-format
+msgid "Run installer in mode specified, '1024x768' for example."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3384
+#, no-c-format
+msgid "serial"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3386
+#, no-c-format
+msgid "Turns on serial console support."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3393
+#, no-c-format
+msgid "skipddc"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3395
+#, no-c-format
+msgid "Skips DDC probe of monitor, may help if it's hanging system."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3402
+#, no-c-format
+msgid ""
+"syslog=<replaceable><host></replaceable>[:<replaceable><port></"
+"replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3404
+#, no-c-format
+msgid ""
+"Once installation is up and running, send log messages to the syslog process "
+"on <replaceable><host></replaceable>, and optionally, on port "
+"<replaceable><port></replaceable>. Requires the remote syslog process "
+"to accept connections (the -r option)."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3413
+#, no-c-format
+msgid "Force text mode install."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3422
+#, no-c-format
+msgid "updates"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3424
+#, no-c-format
+msgid "Prompt for floppy containing updates (bug fixes)."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3431
+#, no-c-format
+msgid "updates=ftp://<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3433
+#, no-c-format
+msgid "Image containing updates over FTP."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3440
+#, no-c-format
+msgid "updates=http://<replaceable><path></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3442
+#, no-c-format
+msgid "Image containing updates over HTTP."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3449
+#, no-c-format
+msgid "upgradeany"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3451
+#, no-c-format
+msgid ""
+"Don't require an /etc/redhat-release that matches the expected syntax to "
+"upgrade."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3460
+#, no-c-format
+msgid ""
+"Enable vnc-based installation. You will need to connect to the machine using "
+"a vnc client application."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3467
+#, no-c-format
+msgid ""
+"vncconnect=<replaceable><host></replaceable>[:<replaceable><port>"
+"</replaceable>]"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3469
+#, no-c-format
+msgid ""
+"Once installation is up and running, connect to the vnc client named "
+"<replaceable><host></replaceable>, and optionally use port "
+"<replaceable><port></replaceable>."
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3473 Kickstart2.xml:3486
+#, no-c-format
+msgid "Requires 'vnc' option to be specified as well."
+msgstr ""
+
+#. Tag: command
+#: Kickstart2.xml:3480
+#, no-c-format
+msgid "vncpassword=<replaceable><password></replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Kickstart2.xml:3482
+#, no-c-format
+msgid ""
+"Enable a password for the vnc connection. This will prevent someone from "
+"inadvertently connecting to the vnc-based installation."
+msgstr ""
+
+#. Tag: para
+#: Kickstart-note-1.xml:6
+#, no-c-format
+msgid ""
+"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 <application>anaconda</"
+"application> cannot prompt you for missing information. If you do not "
+"provide choices for these options, <application>anaconda</application> will "
+"stop the installation process."
+msgstr ""
+
+#. Tag: application
+#: Ksconfig.xml:5 Ksconfig.xml:7 Ksconfig.xml:13 Ksconfig.xml:24
+#: Ksconfig.xml:37 Ksconfig.xml:51 Ksconfig.xml:59 Ksconfig.xml:68
+#: Ksconfig.xml:76 Ksconfig.xml:81 Ksconfig.xml:94 Ksconfig.xml:102
+#: Ksconfig.xml:110 Ksconfig.xml:121 Ksconfig.xml:178 Ksconfig.xml:191
+#: Ksconfig.xml:230 Ksconfig.xml:315 Ksconfig.xml:405 Ksconfig.xml:433
+#: Ksconfig.xml:500 Ksconfig.xml:540 Ksconfig.xml:552 Ksconfig.xml:649
+#: Ksconfig.xml:677 Ksconfig.xml:735 Ksconfig.xml:798
+#, no-c-format
+msgid "<application>Kickstart Configurator</application>"
+msgstr ""
+
+#. Tag: command
+#: Ksconfig.xml:11
+#, no-c-format
+msgid "system-config-kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:17
+#, no-c-format
+msgid ""
+"<application>Kickstart Configurator</application> allows you to create or "
+"modify a kickstart file using a graphical user interface, so that you do not "
+"have to remember the correct syntax of the file."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:20
+#, no-c-format
+msgid ""
+"To use <application>Kickstart Configurator</application>, you must be "
+"running the X Window System. To start <application>Kickstart Configurator</"
+"application>, select <guimenu>Applications</guimenu> (the main menu on the "
+"panel) => <guimenu>System Tools</guimenu> => <guimenuitem>Kickstart</"
+"guimenuitem>, or type the command <command>/usr/sbin/system-config-"
+"kickstart</command>."
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:26
+#, no-c-format
+msgid "preview"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:28
+#, no-c-format
+msgid ""
+"As you are creating a kickstart file, you can select <guimenuitem>File</"
+"guimenuitem> => <guimenuitem>Preview</guimenuitem> at any time to review "
+"your current selections."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:31
+#, no-c-format
+msgid ""
+"To start with an existing kickstart file, select <guimenu>File</guimenu> "
+"=> <guimenuitem>Open</guimenuitem> and select the existing file."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:35 Ksconfig.xml:41
+#, no-c-format
+msgid "<title>Basic Configuration</title>"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:39
+#, no-c-format
+msgid "basic options"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:44
+#, no-c-format
+msgid "<para>Basic Configuration</para>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:55
+#, no-c-format
+msgid ""
+"Choose the language to use during the installation and as the default "
+"language to be used after installation from the <guimenu>Default Language</"
+"guimenu> menu."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:63
+#, no-c-format
+msgid ""
+"Select the system keyboard type from the <guimenu>Keyboard</guimenu> menu."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:72
+#, no-c-format
+msgid ""
+"From the <guimenu>Time Zone</guimenu> menu, choose the time zone to use for "
+"the system. To configure the system to use UTC, select <guilabel>Use UTC "
+"clock</guilabel>."
+msgstr ""
+
+#. Tag: tertiary
+#: Ksconfig.xml:84
+#, no-c-format
+msgid "encrypt"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:86
+#, no-c-format
+msgid ""
+"Enter the desired root password for the system in the <guilabel>Root "
+"Password</guilabel> text entry box. Type the same password in the "
+"<guilabel>Confirm Password</guilabel> text box. The second field is to make "
+"sure you do not mistype the password and then realize you do not know what "
+"it is after you have completed the installation. To save the password as an "
+"encrypted password in the file, select <guilabel>Encrypt root password</"
+"guilabel>. If the encryption option is selected, when the file is saved, the "
+"plain text password that you typed is encrypted and written to the kickstart "
+"file. Do not type an already encrypted password and select to encrypt it. "
+"Because a kickstart file is a plain text file that can be easily read, it is "
+"recommended that an encrypted password be used."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:90
+#, no-c-format
+msgid ""
+"Choosing <guilabel>Target Architecture</guilabel> specifies which specific "
+"hardware architecture distribution is used during installation."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:98
+#, no-c-format
+msgid ""
+"Choosing <guilabel>Reboot system after installation</guilabel> reboots your "
+"system automatically after the installation is finished."
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:104
+#, no-c-format
+msgid "text mode installation"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:106
+#, no-c-format
+msgid ""
+"Kickstart installations are performed in graphical mode by default. To "
+"override this default and use text mode instead, select the "
+"<guilabel>Perform installation in text mode</guilabel> option."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:114
+#, no-c-format
+msgid ""
+"You can perform a kickstart installation in interactive mode. This means "
+"that the installation program uses all the options pre-configured in the "
+"kickstart file, but it allows you to preview the options in each screen "
+"before continuing to the next screen. To continue to the next screen, click "
+"the <guibutton>Next</guibutton> button after you have approved the settings "
+"or change them before continuing the installation. To select this type of "
+"installation, select the <guilabel>Perform installation in interactive mode</"
+"guilabel> option."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:119 Ksconfig.xml:125
+#, no-c-format
+msgid "Installation Method"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:123
+#, no-c-format
+msgid "installation method selection"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:128
+#, no-c-format
+msgid "Kickstart Installation Method"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:134
+#, no-c-format
+msgid ""
+"The <guilabel>Installation Method</guilabel> screen allows you to choose "
+"whether to perform a new installation or an upgrade. If you choose upgrade, "
+"the <guilabel>Partition Information</guilabel> and <guilabel>Package "
+"Selection</guilabel> options are disabled. They are not supported for "
+"kickstart upgrades."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:138
+#, no-c-format
+msgid ""
+"Choose the type of kickstart installation or upgrade from the following "
+"options:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:144
+#, no-c-format
+msgid ""
+"<guilabel>CD-ROM</guilabel> — Choose this option to install or upgrade "
+"from the Fedora CD-ROMs."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:150
+#, no-c-format
+msgid ""
+"<guilabel>NFS</guilabel> — Choose this option to install or upgrade "
+"from an NFS shared directory. In the text field for the the NFS server, "
+"enter a fully-qualified domain name or IP address. For the NFS directory, "
+"enter the name of the NFS directory that contains the "
+"<filename><replaceable>variant</replaceable></filename> directory of the "
+"installation tree. For example, if the NFS server contains the directory "
+"<filename>/mirrors/redhat/i386/Server/</filename>, enter <filename>/mirrors/"
+"redhat/i386/</filename> for the NFS directory."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:156
+#, no-c-format
+msgid ""
+"<guilabel>FTP</guilabel> — Choose this option to install or upgrade "
+"from an FTP server. In the FTP server text field, enter a fully-qualified "
+"domain name or IP address. For the FTP directory, enter the name of the FTP "
+"directory that contains the <filename><replaceable>variant</replaceable></"
+"filename> directory. For example, if the FTP server contains the directory "
+"<filename>/mirrors/redhat/i386/Server/</filename>, enter <filename>/mirrors/"
+"redhat/i386/Server/</filename> for the FTP directory. If the FTP server "
+"requires a username and password, specify them as well."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:162
+#, no-c-format
+msgid ""
+"<guilabel>HTTP</guilabel> — Choose this option to install or upgrade "
+"from an HTTP server. In the text field for the HTTP server, enter the fully-"
+"qualified domain name or IP address. For the HTTP directory, enter the name "
+"of the HTTP directory that contains the <filename><replaceable>variant</"
+"replaceable></filename> directory. For example, if the HTTP server contains "
+"the directory <filename>/mirrors/redhat/i386/Server/</filename>, enter "
+"<filename>/mirrors/redhat/i386/Server/</filename> for the HTTP directory."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:168
+#, no-c-format
+msgid ""
+"<guilabel>Hard Drive</guilabel> — Choose this option to install or "
+"upgrade from a hard drive. Hard drive installations require the use of ISO "
+"(or CD-ROM) images. Be sure to verify that the ISO images are intact before "
+"you start the installation. To verify them, use an <command>md5sum</command> "
+"program as well as the <command>linux mediacheck</command> boot option as "
+"discussed in <xref linkend=\"sn-verifying-media\"/>. Enter the hard drive "
+"partition that contains the ISO images (for example, <filename>/dev/hda1</"
+"filename>) in the <guilabel>Hard Drive Partition</guilabel> text box. Enter "
+"the directory that contains the ISO images in the <guilabel>Hard Drive "
+"Directory</guilabel> text box."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:175 Ksconfig.xml:176
+#, no-c-format
+msgid "<title>Boot Loader Options</title>"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:180
+#, no-c-format
+msgid "boot loader options"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:184
+#, no-c-format
+msgid "<para>Boot Loader Options</para>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:195
+#, no-c-format
+msgid ""
+"Please note that this screen will be disabled if you have specified a target "
+"architecture other than x86 / x86_64."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:198
+#, no-c-format
+msgid ""
+"GRUB is the default boot loader for Fedora on x86 / x86_64 architectures. If "
+"you do not want to install a boot loader, select <guilabel>Do not install a "
+"boot loader</guilabel>. If you choose not to install a boot loader, make "
+"sure you create a boot diskette or have another way to boot your system, "
+"such as a third-party boot loader."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:202
+#, no-c-format
+msgid ""
+"You must choose where to install the boot loader (the Master Boot Record or "
+"the first sector of the <filename>/boot</filename> partition). Install the "
+"boot loader on the MBR if you plan to use it as your boot loader."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:206
+#, no-c-format
+msgid ""
+"To pass any special parameters to the kernel to be used when the system "
+"boots, enter them in the <guilabel>Kernel parameters</guilabel> text field. "
+"For example, if you have an IDE CD-ROM Writer, you can tell the kernel to "
+"use the SCSI emulation driver that must be loaded before using "
+"<command>cdrecord</command> by configuring <userinput>hdd=ide-scsi</"
+"userinput> as a kernel parameter (where <userinput>hdd</userinput> is the CD-"
+"ROM device)."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:211
+#, no-c-format
+msgid ""
+"You can password protect the GRUB boot loader by configuring a GRUB "
+"password. Select <guilabel>Use GRUB password</guilabel>, and enter a "
+"password in the <guilabel>Password</guilabel> field. Type the same password "
+"in the <guilabel>Confirm Password</guilabel> text field. To save the "
+"password as an encrypted password in the file, select <guilabel>Encrypt GRUB "
+"password</guilabel>. If the encryption option is selected, when the file is "
+"saved, the plain text password that you typed is encrypted and written to "
+"the kickstart file. If the password you typed was already encrypted, "
+"unselect the encryption option."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:215
+#, no-c-format
+msgid ""
+"If <guilabel>Upgrade an existing installation</guilabel> is selected on the "
+"<guilabel>Installation Method</guilabel> page, select <guilabel>Upgrade "
+"existing boot loader</guilabel> to upgrade the existing boot loader "
+"configuration, while preserving the old entries."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:228 Ksconfig.xml:234
+#, no-c-format
+msgid "Partition Information"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:237
+#, no-c-format
+msgid "Kickstart Partition Information"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:243
+#, no-c-format
+msgid ""
+"Select whether or not to clear the Master Boot Record (MBR). Choose to "
+"remove all existing partitions, remove all existing Linux partitions, or "
+"preserve existing partitions."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:247
+#, no-c-format
+msgid ""
+"To initialize the disk label to the default for the architecture of the "
+"system (for example, <command>msdos</command> for x86 and <command>gpt</"
+"command> for Itanium), select <guilabel>Initialize the disk label</guilabel> "
+"if you are installing on a brand new hard drive."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:252
+#, no-c-format
+msgid ""
+"Although <command>anaconda</command> and <command>kickstart</command> "
+"support Logical Volume Management (LVM), at present there is no mechanism "
+"for configuring this using the <application>Kickstart Configurator</"
+"application>."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:258 Ksconfig.xml:295
+#, no-c-format
+msgid "Creating Partitions"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:260
+#, no-c-format
+msgid ""
+"To create a partition, click the <guibutton>Add</guibutton> button. The "
+"<guilabel>Partition Options</guilabel> window shown in <xref linkend="
+"\"redhat-config-kickstart-add-part-fig\"/> appears. Choose the mount point, "
+"file system type, and partition size for the new partition. Optionally, you "
+"can also choose from the following:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:266
+#, no-c-format
+msgid ""
+"In the <guilabel>Additional Size Options</guilabel> section, choose to make "
+"the partition a fixed size, up to a chosen size, or fill the remaining space "
+"on the hard drive. If you selected swap as the file system type, you can "
+"select to have the installation program create the swap partition with the "
+"recommended size instead of specifying a size."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:272
+#, no-c-format
+msgid "Force the partition to be created as a primary partition."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:278
+#, no-c-format
+msgid ""
+"Create the partition on a specific hard drive. For example, to make the "
+"partition on the first IDE hard disk (<filename>/dev/hda</filename>), "
+"specify <userinput>hda</userinput> as the drive. Do not include <filename>/"
+"dev</filename> in the drive name."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:284
+#, no-c-format
+msgid ""
+"Use an existing partition. For example, to make the partition on the first "
+"partition on the first IDE hard disk (<filename>/dev/hda1</filename>), "
+"specify <userinput>hda1</userinput> as the partition. Do not include "
+"<filename>/dev</filename> in the partition name."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:290
+#, no-c-format
+msgid "Format the partition as the chosen file system type."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:298
+#, no-c-format
+msgid "Creating Partitions for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:304
+#, no-c-format
+msgid ""
+"To edit an existing partition, select the partition from the list and click "
+"the <guibutton>Edit</guibutton> button. The same <guilabel>Partition "
+"Options</guilabel> window appears as when you chose to add a partition as "
+"shown in <xref linkend=\"redhat-config-kickstart-add-part-fig\"/>, except it "
+"reflects the values for the selected partition. Modify the partition options "
+"and click <guibutton>OK</guibutton>."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:308
+#, no-c-format
+msgid ""
+"To delete an existing partition, select the partition from the list and "
+"click the <guibutton>Delete</guibutton> button."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:313
+#, no-c-format
+msgid "Creating Software RAID Partitions"
+msgstr ""
+
+#. Tag: tertiary
+#: Ksconfig.xml:318
+#, no-c-format
+msgid "software RAID"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:322
+#, no-c-format
+msgid "kickstart installations"
+msgstr ""
+
+#. Tag: tertiary
+#: Ksconfig.xml:323
+#, no-c-format
+msgid "<tertiary>Kickstart Configurator</tertiary>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:325
+#, no-c-format
+msgid "To create a software RAID partition, use the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:331 Ksconfig.xml:367
+#, no-c-format
+msgid "Click the <guibutton>RAID</guibutton> button."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:337
+#, no-c-format
+msgid "Select <guilabel>Create a software RAID partition</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:343
+#, no-c-format
+msgid ""
+"Configure the partitions as previously described, except select "
+"<guilabel>Software RAID</guilabel> as the file system type. Also, you must "
+"specify a hard drive on which to make the partition or specify an existing "
+"partition to use."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:348
+#, no-c-format
+msgid "Creating a Software RAID Partition"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:351
+#, no-c-format
+msgid "Software RAID Partition"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:357
+#, no-c-format
+msgid ""
+"Repeat these steps to create as many partitions as needed for your RAID "
+"setup. All of your partitions do not have to be RAID partitions."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:361
+#, no-c-format
+msgid ""
+"After creating all the partitions needed to form a RAID device, follow these "
+"steps:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:373
+#, no-c-format
+msgid "Select <guilabel>Create a RAID device</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:379
+#, no-c-format
+msgid ""
+"Select a mount point, file system type, RAID device name, RAID level, RAID "
+"members, number of spares for the software RAID device, and whether to "
+"format the RAID device."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:382
+#, no-c-format
+msgid "Creating a Software RAID Device"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:385
+#, no-c-format
+msgid "Software RAID Device"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:394
+#, no-c-format
+msgid "Click <guibutton>OK</guibutton> to add the device to the list."
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:407
+#, no-c-format
+msgid "network configuration"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:412
+#, no-c-format
+msgid "Network Configuration for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:418
+#, no-c-format
+msgid ""
+"If the system to be installed via kickstart does not have an Ethernet card, "
+"do not configure one on the <guilabel>Network Configuration</guilabel> page."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:422
+#, no-c-format
+msgid ""
+"Networking is only required if you choose a networking-based installation "
+"method (NFS, FTP, or HTTP). Networking can always be configured after "
+"installation with the <application>Network Administration Tool</application> "
+"(<command>system-config-network</command>). Refer to the Red Hat Enterprise "
+"Linux Deployment Guide for details."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:426
+#, no-c-format
+msgid ""
+"For each Ethernet card on the system, click <guibutton>Add Network Device</"
+"guibutton> and select the network device and network type for the device. "
+"Select <guilabel>eth0</guilabel> to configure the first Ethernet card, "
+"<guilabel>eth1</guilabel> for the second Ethernet card, and so on."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:431 Ksconfig.xml:437
+#, no-c-format
+msgid "Authentication"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:435
+#, no-c-format
+msgid "authentication options"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:440
+#, no-c-format
+msgid "Authentication for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:446
+#, no-c-format
+msgid ""
+"In the <guilabel>Authentication</guilabel> section, select whether to use "
+"shadow passwords and MD5 encryption for user passwords. These options are "
+"highly recommended and chosen by default."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:450
+#, no-c-format
+msgid ""
+"The <guilabel>Authentication Configuration</guilabel> options allow you to "
+"configure the following methods of authentication:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:456
+#, no-c-format
+msgid "<para>NIS</para>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:462
+#, no-c-format
+msgid "LDAP"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:468
+#, no-c-format
+msgid "Kerberos 5"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:474
+#, no-c-format
+msgid "Hesiod"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:480
+#, no-c-format
+msgid "<para>SMB</para>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:486
+#, no-c-format
+msgid "Name Switch Cache"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:492
+#, no-c-format
+msgid ""
+"These methods are not enabled by default. To enable one or more of these "
+"methods, click the appropriate tab, click the checkbox next to "
+"<guilabel>Enable</guilabel>, and enter the appropriate information for the "
+"authentication method. Refer to the Red Hat Enterprise Linux Deployment "
+"Guide for more information about the options."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:498 Ksconfig.xml:507
+#, no-c-format
+msgid "Firewall Configuration"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:502
+#, no-c-format
+msgid "firewall configuration"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:504
+#, no-c-format
+msgid ""
+"The <guilabel>Firewall Configuration</guilabel> window is similar to the "
+"screen in the installation program and the <application>Security Level "
+"Configuration Tool</application>."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:510
+#, no-c-format
+msgid "Firewall Configuration for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:516
+#, no-c-format
+msgid ""
+"If <guilabel>Disable firewall</guilabel> is selected, the system allows "
+"complete access to any active services and ports. No connections to the "
+"system are refused or denied."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:520
+#, no-c-format
+msgid ""
+"Selecting <guilabel>Enable firewall</guilabel> configures the system to "
+"reject incoming connections that are not in response to outbound requests, "
+"such as DNS replies or DHCP requests. If access to services running on this "
+"machine is required, you can choose to allow specific services through the "
+"firewall."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:524
+#, no-c-format
+msgid ""
+"Only devices configured in the <guilabel>Network Configuration</guilabel> "
+"section are listed as available <guilabel>Trusted devices</guilabel>. "
+"Connections from any devices selected in the list are accepted by the "
+"system. For example, if <guilabel>eth1</guilabel> only receives connections "
+"from internal system, you might want to allow connections from it."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:528
+#, no-c-format
+msgid ""
+"If a service is selected in the <guilabel>Trusted services</guilabel> list, "
+"connections for the service are accepted and processed by the system."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:532
+#, no-c-format
+msgid ""
+"In the <guilabel>Other ports</guilabel> text field, list any additional "
+"ports that should be opened for remote access. Use the following format: "
+"<userinput>port:protocol</userinput>. For example, to allow IMAP access "
+"through the firewall, specify <userinput>imap:tcp</userinput>. Numeric ports "
+"can also be specified explicitly; to allow UDP packets on port 1234 through "
+"the firewall, enter <userinput>1234:udp</userinput>. To specify multiple "
+"ports, separate them with commas."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:538
+#, no-c-format
+msgid "SELinux Configuration"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:542
+#, no-c-format
+msgid "SELinux configuration"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:544
+#, no-c-format
+msgid ""
+"Kickstart can set SELinux to <command>enforcing</command>, "
+"<command>permissive</command> or <command>disabled</command> mode. Finer "
+"grained configuration is not possible at this time."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:550
+#, no-c-format
+msgid "Display Configuration"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:554
+#, no-c-format
+msgid "Display configuration"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:556
+#, no-c-format
+msgid ""
+"If you are installing the X Window System, you can configure it during the "
+"kickstart installation by checking the <guilabel>Configure the X Window "
+"System</guilabel> option on the <guilabel>Display Configuration</guilabel> "
+"window as shown in <xref linkend=\"xconfig-fig\"/>. If this option is not "
+"chosen, the X configuration options are disabled and the <command>skipx</"
+"command> option is written to the kickstart file."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:559
+#, no-c-format
+msgid "X Configuration"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:562
+#, no-c-format
+msgid "X Configuration for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:568
+#, no-c-format
+msgid ""
+"Also select whether to start the <application>Setup Agent</application> the "
+"first time the system is rebooted. It is disabled by default, but the "
+"setting can be changed to enabled or enabled in reconfiguration mode. "
+"Reconfiguration mode enables the language, mouse, keyboard, root password, "
+"security level, time zone, and networking configuration options in addition "
+"to the default ones."
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:651
+#, no-c-format
+msgid "package selection"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:656
+#, no-c-format
+msgid "Package Selection for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:662
+#, no-c-format
+msgid ""
+"The <guilabel>Package Selection</guilabel> window allows you to choose which "
+"package groups to install."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:666
+#, no-c-format
+msgid "Package resolution is carried out automatically."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:670
+#, no-c-format
+msgid ""
+"Currently, <application>Kickstart Configurator </application> does not allow "
+"you to select individual packages. To install individual packages, modify "
+"the <command>%packages</command> section of the kickstart file after you "
+"save it. Refer to <xref linkend=\"s1-kickstart2-packageselection\"/> for "
+"details."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:675 Ksconfig.xml:681
+#, no-c-format
+msgid "Pre-Installation Script"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:679
+#, no-c-format
+msgid "%pre script"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:684
+#, no-c-format
+msgid "Pre-Installation Script for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:690
+#, no-c-format
+msgid ""
+"You can add commands to run on the system immediately after the kickstart "
+"file has been parsed and before the installation begins. If you have "
+"configured the network in the kickstart file, the network is enabled before "
+"this section is processed. To include a pre-installation script, type it in "
+"the text area."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:694
+#, no-c-format
+msgid ""
+"To specify a scripting language to use to execute the script, select the "
+"<guilabel>Use an interpreter</guilabel> option and enter the interpreter in "
+"the text box beside it. For example, <userinput>/usr/bin/python2.4</"
+"userinput> can be specified for a Python script. This option corresponds to "
+"using <command>%pre --interpreter <replaceable>/usr/bin/python2.4</"
+"replaceable></command> in your kickstart file."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:698
+#, no-c-format
+msgid ""
+"Many of the commands that are available in the pre-installation environment "
+"are provided by a version of <application>busybox</application> called "
+"<application>busybox-anaconda</application>. <application>Busybox</"
+"application>-supplied commands do not provide all features, but supply only "
+"the most commonly used features. The following list of available commands "
+"include commands provided by <application>busybox</application>:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:702
+#, no-c-format
+msgid ""
+"<command>addgroup</command>, <command>adduser</command>, <command>adjtimex</"
+"command>, <command>ar</command>, <command>arping</command>, <command>ash</"
+"command>, <command>awk</command>, <command>basename</command>, "
+"<command>bbconfig</command>, <command>bunzip2</command>, <command>busybox</"
+"command>, <command>bzcat</command>, <command>cal</command>, <command>cat</"
+"command>, <command>catv</command>, <command>chattr</command>, "
+"<command>chgrp</command>, <command>chmod</command>, <command>chown</"
+"command>, <command>chroot</command>, <command>chvt</command>, "
+"<command>cksum</command>, <command>clear</command>, <command>cmp</command>, "
+"<command>comm</command>, <command>cp</command>, <command>cpio</command>, "
+"<command>crond</command>, <command>crontab</command>, <command>cut</"
+"command>, <command>date</command>, <command>dc</command>, <command>dd</"
+"command>, <command>deallocvt</command>, <command>delgroup</command>, "
+"<command>deluser</command>, <command>devfsd</command>, <command>df</"
+"command>, <command>diff</command>, <command>dirname</command>, "
+"<command>dmesg</command>, <command>dnsd</command>, <command>dos2unix</"
+"command>, <command>dpkg</command>, <command>dpkg-deb</command>, <command>du</"
+"command>, <command>dumpkmap</command>, <command>dumpleases</command>, "
+"<command>e2fsck</command>, <command>e2label</command>, <command>echo</"
+"command>, <command>ed</command>, <command>egrep</command>, <command>eject</"
+"command>, <command>env</command>, <command>ether-wake</command>, "
+"<command>expr</command>, <command>fakeidentd</command>, <command>false</"
+"command>, <command>fbset</command>, <command>fdflush</command>, "
+"<command>fdformat</command>, <command>fdisk</command>, <command>fgrep</"
+"command>, <command>find</command>, <command>findfs</command>, <command>fold</"
+"command>, <command>free</command>, <command>freeramdisk</command>, "
+"<command>fsck</command>, <command>fsck.ext2</command>, <command>fsck.ext3</"
+"command>, <command>fsck.ext4</command>, <command>fsck.minix</command>, "
+"<command>ftpget</command>, <command>ftpput</command>, <command>fuser</"
+"command>, <command>getopt</command>, <command>getty</command>, "
+"<command>grep</command>, <command>gunzip</command>, <command>gzip</command>, "
+"<command>hdparm</command>, <command>head</command>, <command>hexdump</"
+"command>, <command>hostid</command>, <command>hostname</command>, "
+"<command>httpd</command>, <command>hush</command>, <command>hwclock</"
+"command>, <command>id</command>, <command>ifconfig</command>, "
+"<command>ifdown</command>, <command>ifup</command>, <command>inetd</"
+"command>, <command>insmod</command>, <command>install</command>, "
+"<command>ip</command>, <command>ipaddr</command>, <command>ipcalc</command>, "
+"<command>ipcrm</command>, <command>ipcs</command>, <command>iplink</"
+"command>, <command>iproute</command>, <command>iptunnel</command>, "
+"<command>kill</command>, <command>killall</command>, <command>lash</"
+"command>, <command>last</command>, <command>length</command>, <command>less</"
+"command>, <command>linux32</command>, <command>linux64</command>, "
+"<command>ln</command>, <command>load_policy</command>, <command>loadfont</"
+"command>, <command>loadkmap</command>, <command>login</command>, "
+"<command>logname</command>, <command>losetup</command>, <command>ls</"
+"command>, <command>lsattr</command>, <command>lsmod</command>, "
+"<command>lzmacat</command>, <command>makedevs</command>, <command>md5sum</"
+"command>, <command>mdev</command>, <command>mesg</command>, <command>mkdir</"
+"command>, <command>mke2fs</command>, <command>mkfifo</command>, "
+"<command>mkfs.ext2</command>, <command>mkfs.ext3</command>, <command>mkfs."
+"ext4</command>, <command>mkfs.minix</command>, <command>mknod</command>, "
+"<command>mkswap</command>, <command>mktemp</command>, <command>modprobe</"
+"command>, <command>more</command>, <command>mount</command>, "
+"<command>mountpoint</command>, <command>msh</command>, <command>mt</"
+"command>, <command>mv</command>, <command>nameif</command>, <command>nc</"
+"command>, <command>netstat</command>, <command>nice</command>, "
+"<command>nohup</command>, <command>nslookup</command>, <command>od</"
+"command>, <command>openvt</command>, <command>passwd</command>, "
+"<command>patch</command>, <command>pidof</command>, <command>ping</command>, "
+"<command>ping6</command>, <command>pipe_progress</command>, "
+"<command>pivot_root</command>, <command>printenv</command>, <command>printf</"
+"command>, <command>ps</command>, <command>pwd</command>, <command>rdate</"
+"command>, <command>readlink</command>, <command>readprofile</command>, "
+"<command>realpath</command>, <command>renice</command>, <command>reset</"
+"command>, <command>rm</command>, <command>rmdir</command>, <command>rmmod</"
+"command>, <command>route</command>, <command>rpm</command>, "
+"<command>rpm2cpio</command>, <command>run-parts</command>, "
+"<command>runlevel</command>, <command>rx</command>, <command>sed</command>, "
+"<command>seq</command>, <command>setarch</command>, <command>setconsole</"
+"command>, <command>setkeycodes</command>, <command>setlogcons</command>, "
+"<command>setsid</command>, <command>sh</command>, <command>sha1sum</"
+"command>, <command>sleep</command>, <command>sort</command>, <command>start-"
+"stop-daemon</command>, <command>stat</command>, <command>strings</command>, "
+"<command>stty</command>, <command>su</command>, <command>sulogin</command>, "
+"<command>sum</command>, <command>swapoff</command>, <command>swapon</"
+"command>, <command>switch_root</command>, <command>sync</command>, "
+"<command>sysctl</command>, <command>tail</command>, <command>tar</command>, "
+"<command>tee</command>, <command>telnet</command>, <command>telnetd</"
+"command>, <command>test</command>, <command>tftp</command>, <command>time</"
+"command>, <command>top</command>, <command>touch</command>, <command>tr</"
+"command>, <command>traceroute</command>, <command>true</command>, "
+"<command>tty</command>, <command>tune2fs</command>, <command>udhcpc</"
+"command>, <command>udhcpd</command>, <command>umount</command>, "
+"<command>uname</command>, <command>uncompress</command>, <command>uniq</"
+"command>, <command>unix2dos</command>, <command>unlzma</command>, "
+"<command>unzip</command>, <command>uptime</command>, <command>usleep</"
+"command>, <command>uudecode</command>, <command>uuencode</command>, "
+"<command>vconfig</command>, <command>vi</command>, <command>vlock</command>, "
+"<command>watch</command>, <command>watchdog</command>, <command>wc</"
+"command>, <command>wget</command>, <command>which</command>, <command>who</"
+"command>, <command>whoami</command>, <command>xargs</command>, <command>yes</"
+"command>, <command>zcat</command>, <command>zcip</command>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:704
+#, no-c-format
+msgid "For a description of any of these commands, run:"
+msgstr ""
+
+#. Tag: command
+#: Ksconfig.xml:706
+#, no-c-format
+msgid "busybox <replaceable>command</replaceable> --help"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:708
+#, no-c-format
+msgid ""
+"In addition to the aforementioned commands, the following commands are "
+"provided in their full featured versions:"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:716
+#, no-c-format
+msgid ""
+"<command>anaconda</command>, <command>bash</command>, <command>bzip2</"
+"command>, <command>jmacs</command>, <command>ftp</command>, <command>head</"
+"command>, <command>joe</command>, <command>kudzu-probe</command>, "
+"<command>list-harddrives</command>, <command>loadkeys</command>, "
+"<command>mtools</command>, <command>mbchk</command>, <command>mtools</"
+"command>, <command>mini-wm</command>, <command>mtools</command>, "
+"<command>jpico</command>, <command>pump</command>, <command>python</"
+"command>, <command>python2.4</command>, <command>raidstart</command>, "
+"<command>raidstop</command>, <command>rcp</command>, <command>rlogin</"
+"command>, <command>rsync</command>, <command>setxkbmap</command>, "
+"<command>sftp</command>, <command>shred</command>, <command>ssh</command>, "
+"<command>syslinux</command>, <command>syslogd</command>, <command>tac</"
+"command>, <command>termidx</command>, <command>vncconfig</command>, "
+"<command>vncpasswd</command>, <command>xkbcomp</command>, <command>Xorg</"
+"command>, <command>Xvnc</command>, <command>zcat</command>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:721
+#, no-c-format
+msgid ""
+"Do not include the <command>%pre</command> command. It is added for you."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:727
+#, no-c-format
+msgid ""
+"The pre-installation script is run after the source media is mounted and "
+"stage 2 of the bootloader has been loaded. For this reason it is not "
+"possible to change the source media in the pre-installation script."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:733 Ksconfig.xml:739
+#, no-c-format
+msgid "Post-Installation Script"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:737
+#, no-c-format
+msgid "%post script"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:742
+#, no-c-format
+msgid "Post-Installation Script for Kickstart"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:748
+#, no-c-format
+msgid ""
+"You can also add commands to execute on the system after the installation is "
+"completed. If the network is properly configured in the kickstart file, the "
+"network is enabled, and the script can include commands to access resources "
+"on the network. To include a post-installation script, type it in the text "
+"area."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:755
+#, no-c-format
+msgid ""
+"Do not include the <command>%post</command> command. It is added for you."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:760
+#, no-c-format
+msgid ""
+"For example, to change the message of the day for the newly installed "
+"system, add the following command to the <command>%post</command> section:"
+msgstr ""
+
+#. Tag: screen
+#: Ksconfig.xml:763
+#, no-c-format
+msgid "<command>echo \"Hackers will be punished!\" > /etc/motd</command>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:765
+#, no-c-format
+msgid ""
+"More examples can be found in <xref linkend=\"s2-kickstart2-post-examples\"/"
+">."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:770
+#, no-c-format
+msgid "Chroot Environment"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:772
+#, no-c-format
+msgid ""
+"To run the post-installation script outside of the chroot environment, click "
+"the checkbox next to this option on the top of the <guilabel>Post-"
+"Installation</guilabel> window. This is equivalent to using the <command>--"
+"nochroot</command> option in the <command>%post</command> section."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:776
+#, no-c-format
+msgid ""
+"To make changes to the newly installed file system, within the post-"
+"installation section, but outside of the chroot environment, you must "
+"prepend the directory name with <filename>/mnt/sysimage/</filename>."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:780
+#, no-c-format
+msgid ""
+"For example, if you select <guilabel>Run outside of the chroot environment</"
+"guilabel>, the previous example must be changed to the following:"
+msgstr ""
+
+#. Tag: screen
+#: Ksconfig.xml:783
+#, no-c-format
+msgid ""
+"<command>echo \"Hackers will be punished!\" > /mnt/sysimage/etc/motd</"
+"command>"
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:787
+#, no-c-format
+msgid "Use an Interpreter"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:789
+#, no-c-format
+msgid ""
+"To specify a scripting language to use to execute the script, select the "
+"<guilabel>Use an interpreter</guilabel> option and enter the interpreter in "
+"the text box beside it. For example, <userinput>/usr/bin/python2.2</"
+"userinput> can be specified for a Python script. This option corresponds to "
+"using <command>%post --interpreter <replaceable>/usr/bin/python2.2</"
+"replaceable></command> in your kickstart file."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:796
+#, no-c-format
+msgid "Saving the File"
+msgstr ""
+
+#. Tag: secondary
+#: Ksconfig.xml:800
+#, no-c-format
+msgid "saving"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:802
+#, no-c-format
+msgid ""
+"To review the contents of the kickstart file after you have finished "
+"choosing your kickstart options, select <guimenuitem>File</guimenuitem> "
+"=> <guimenuitem>Preview</guimenuitem> from the pull-down menu."
+msgstr ""
+
+#. Tag: title
+#: Ksconfig.xml:805
+#, no-c-format
+msgid "<title>Preview</title>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:808
+#, no-c-format
+msgid "<para>Preview</para>"
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:814
+#, no-c-format
+msgid ""
+"To save the kickstart file, click the <guibutton>Save to File</guibutton> "
+"button in the preview window. To save the file without previewing it, select "
+"<guimenuitem>File</guimenuitem> => <guimenuitem>Save File</guimenuitem> "
+"or press <keycombo><keycap>Ctrl</keycap><keycap>S</keycap> </keycombo> . A "
+"dialog box appears. Select where to save the file."
+msgstr ""
+
+#. Tag: para
+#: Ksconfig.xml:820
+#, no-c-format
+msgid ""
+"After saving the file, refer to <xref linkend=\"s1-kickstart2-startinginstall"
+"\"/> for information on how to start the kickstart installation."
+msgstr ""
+
+#. Tag: para
+#: Language_Selection_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"The language you select here will become the default language for the "
+"operating system once it is installed. Selecting the appropriate language "
+"also helps target your time zone configuration later in the installation. "
+"The installation program tries to define the appropriate time zone based on "
+"what you specify on this screen."
+msgstr ""
+
+#. Tag: para
+#: Language_Selection_common-para-2.xml:5
+#, no-c-format
+msgid ""
+"Once you select the appropriate language, click <guibutton>Next</guibutton> "
+"to continue."
+msgstr ""
+
+#. Tag: para
+#: Language_Selection_common-para-3.xml:5
+#, no-c-format
+msgid ""
+"To add support for additional languages, customize the installation at the "
+"package selection stage. For more information, refer to <xref linkend=\"sn-"
+"lang-packages\"/>."
+msgstr ""
+
+#. Tag: para
+#: Language_Selection-x86.xml:13
+#, no-c-format
+msgid ""
+"Using your mouse, select a language to use for the installation (refer to "
+"<xref linkend=\"fig-langselection-x86\"/>)."
+msgstr ""
+
+#. Tag: para
+#: Language_Selection-x86.xml:28
+#, no-c-format
+msgid "Language selection screen."
+msgstr ""
+
+#. Tag: para
+#: Loopbacktip-common.xml:6
+#, no-c-format
+msgid ""
+"You can save disk space by using the ISO images you have already copied to "
+"the server. To accomplish this, install Fedora using ISO images without "
+"copying them into a single tree by loopback mounting them. For each ISO "
+"image:"
+msgstr ""
+
+#. Tag: command
+#: Loopbacktip-common.xml:9
+#, no-c-format
+msgid "mkdir disc<replaceable>X</replaceable>"
+msgstr ""
+
+#. Tag: command
+#: Loopbacktip-common.xml:10
+#, no-c-format
+msgid ""
+"mount -o loop Fedora&PRODVER;-disc<replaceable>X</replaceable>.iso "
+"disc<replaceable>X</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Loopbacktip-common.xml:13
+#, no-c-format
+msgid "Replace <command>X</command> with the corresponding disc number."
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:7
+#, no-c-format
+msgid "Installing Without Media"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:8
+#, no-c-format
+msgid ""
+"This section discusses how to install Fedora to your system without making "
+"any additional physical media. Instead, you can use your existing "
+"<application>GRUB</application> boot loader to start the installation "
+"program."
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:13
+#, no-c-format
+msgid "Linux Required"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:14
+#, no-c-format
+msgid ""
+"This procedure assumes you are already using Fedora or another relatively "
+"modern Linux distribution, and the <application>GRUB</application> boot "
+"loader. It also assumes you are a somewhat experienced Linux user."
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:20
+#, no-c-format
+msgid "Retrieving Boot Files"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:21
+#, no-c-format
+msgid ""
+"To perform an installation without media or a PXE server, your system must "
+"have two files stored locally, a kernel and an initial RAM disk."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:26
+#, no-c-format
+msgid ""
+"Download a Live image or DVD distribution, or to locate an installation "
+"mirror, visit <ulink url=\"http://mirrors.fedoraproject.org/publiclist/"
+"Fedora/11/\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:30
+#, no-c-format
+msgid ""
+"Locate the <filename class=\"directory\">isolinux/</filename> folder using "
+"one of the following methods:"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:35
+#, no-c-format
+msgid ""
+"If you chose to download an image, open it with the appropriate desktop "
+"tool. If you are using Fedora, double-click the file to open it with the "
+"<application>Archive Manager</application>. Open the <filename class="
+"\"directory\">isolinux/</filename> folder."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:43
+#, no-c-format
+msgid ""
+"If you chose not to download a whole image because you wish to install via "
+"the network, locate the desired release. In general, once you find a "
+"suitable mirror, browse to the <filename>releases/11/Fedora/"
+"<replaceable>arch</replaceable>/os/isolinux/</filename> folder."
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:52
+#, no-c-format
+msgid "Installation Types Available"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:53
+#, no-c-format
+msgid ""
+"If you download an image, you may then choose a hard disk-based installation "
+"or a network installation. If you only download selected files from a "
+"mirror, you may only perform a network installation."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:60
+#, no-c-format
+msgid ""
+"Copy the <filename>vmlinuz</filename> and <filename>initrd.img</filename> "
+"files from the chosen source to the <filename class=\"directory\">/boot/</"
+"filename> directory, renaming them to <filename>vmlinuz-install</filename> "
+"and <filename>initrd.img-install</filename>You must have <systemitem class="
+"\"username\">root</systemitem> privileges to write files into the <filename "
+"class=\"directory\">/boot/</filename> directory."
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:73
+#, no-c-format
+msgid "Editing the <application>GRUB</application> Configuration"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:75
+#, no-c-format
+msgid ""
+"The <application>GRUB</application> boot loader uses the configuration file "
+"<filename>/boot/grub/grub.conf</filename>. To configure <application>GRUB</"
+"application> to boot from the new files, add a boot stanza to <filename>/"
+"boot/grub/grub.conf</filename>that refers to them."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:81
+#, no-c-format
+msgid "A minimal boot stanza looks like the following listing:"
+msgstr ""
+
+#. Tag: screen
+#: medialess.xml:82
+#, no-c-format
+msgid ""
+"<![CDATA[title Installation\n"
+"        root (hd0,0)\n"
+"        kernel /vmlinuz-install\n"
+"        initrd /initrd.img-install]]>"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:83
+#, no-c-format
+msgid ""
+"You may wish to add options to the end of the <option>kernel</option> line "
+"of the boot stanza. These options set preliminary options in "
+"<application>Anaconda</application> which the user normally sets "
+"interactively. For a list of available installer boot options, refer to "
+"<xref linkend=\"ap-admin-options\"/>."
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:89
+#, no-c-format
+msgid "The following options are generally useful for medialess installations:"
+msgstr ""
+
+#. Tag: option
+#: medialess.xml:93
+#, no-c-format
+msgid "<option>ip=</option>"
+msgstr ""
+
+#. Tag: option
+#: medialess.xml:96
+#, no-c-format
+msgid "method="
+msgstr ""
+
+#. Tag: option
+#: medialess.xml:99
+#, no-c-format
+msgid "lang="
+msgstr ""
+
+#. Tag: option
+#: medialess.xml:102
+#, no-c-format
+msgid "keymap="
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:105
+#, no-c-format
+msgid ""
+"<option>ksdevice=</option> (if installation requires an interface other than "
+"eth0)"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:109
+#, no-c-format
+msgid ""
+"<option>vnc</option> and <option>vncpassword=</option> for a remote "
+"installation"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:113
+#, no-c-format
+msgid ""
+"When you are finished, change the <option>default</option> option in "
+"<filename>/boot/grub/grub.conf</filename> to point to the new first stanza "
+"you added:"
+msgstr ""
+
+#. Tag: screen
+#: medialess.xml:116
+#, no-c-format
+msgid "<![CDATA[default 0]]>"
+msgstr ""
+
+#. Tag: title
+#: medialess.xml:119
+#, no-c-format
+msgid "Booting to Installation"
+msgstr ""
+
+#. Tag: para
+#: medialess.xml:120
+#, no-c-format
+msgid ""
+"Reboot the system. <application>GRUB</application> boots the installation "
+"kernel and RAM disk, including any options you set. You may now refer to the "
+"appropriate chapter in this guide for the next step. If you chose to install "
+"remotely using VNC, refer to <xref linkend=\"sn-remoteaccess-installation\"/"
+"> for assistance in connecting to the remote system."
+msgstr ""
+
+#. Tag: title
+#: Netboot_DHCP.xml:5
+#, no-c-format
+msgid "Configuring the DHCP Server"
+msgstr ""
+
+#. Tag: primary
+#: Netboot_DHCP.xml:7 Netboot_DHCP.xml:12
+#, no-c-format
+msgid "DHCP"
+msgstr ""
+
+#. Tag: secondary
+#: Netboot_DHCP.xml:8
+#, no-c-format
+msgid "<secondary>PXE installations</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: Netboot_DHCP.xml:13
+#, no-c-format
+msgid "<secondary>diskless environment</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: Netboot_DHCP.xml:17
+#, no-c-format
+msgid "<primary>PXE installations</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Netboot_DHCP.xml:18 Netboot_DHCP.xml:23
+#, no-c-format
+msgid "DHCP configuration"
+msgstr ""
+
+#. Tag: primary
+#: Netboot_DHCP.xml:22
+#, no-c-format
+msgid "<primary>diskless environment</primary>"
+msgstr ""
+
+#. Tag: para
+#: Netboot_DHCP.xml:26
+#, no-c-format
+msgid ""
+"If a DHCP server does not already exist on the network, configure one. Refer "
+"to the Red Hat Enterprise Linux Deployment Guide for details. Make sure the "
+"configuration file contains the following so that PXE booting is enabled for "
+"systems which support it:"
+msgstr ""
+
+#. Tag: computeroutput
+#: Netboot_DHCP.xml:31
+#, no-c-format
+msgid ""
+"allow booting; allow bootp; class \"pxeclients\" { match if substring(option "
+"vendor-class-identifier, 0, 9) = \"PXEClient\"; next-server <replaceable><"
+"server-ip></replaceable>; filename \"linux-install/pxelinux.0\"; }"
+msgstr ""
+
+#. Tag: para
+#: Netboot_DHCP.xml:34
+#, no-c-format
+msgid ""
+"where the next-server <replaceable><server-ip></replaceable> should be "
+"replaced with the IP address of the <command>tftp</command> server."
+msgstr ""
+
+#. Tag: title
+#: Netboot_TFTP.xml:5
+#, no-c-format
+msgid "Starting the <command>tftp</command> Server"
+msgstr ""
+
+#. Tag: command
+#: Netboot_TFTP.xml:7
+#, no-c-format
+msgid "tftp"
+msgstr ""
+
+#. Tag: para
+#: Netboot_TFTP.xml:11
+#, no-c-format
+msgid ""
+"On the DHCP server, verify that the <filename>tftp-server</filename> package "
+"is installed with the command <command>rpm -q tftp-server</command>."
+msgstr ""
+
+#. Tag: para
+#: Netboot_TFTP.xml:15
+#, no-c-format
+msgid ""
+"<command>tftp</command> is an xinetd-based service; start it with the "
+"following commands:"
+msgstr ""
+
+#. Tag: screen
+#: Netboot_TFTP.xml:19
+#, no-c-format
+msgid ""
+"<command>/sbin/chkconfig --level 345 xinetd on /sbin/chkconfig --level 345 "
+"tftp on</command>"
+msgstr ""
+
+#. Tag: para
+#: Netboot_TFTP.xml:21
+#, no-c-format
+msgid ""
+"These commands configure the <command>tftp</command> and <command>xinetd</"
+"command> services to immediately turn on and also configure them to start at "
+"boot time in runlevels 3, 4, and 5."
+msgstr ""
+
+#. Tag: primary
+#: networkconfig-fedora.xml:13
+#, no-c-format
+msgid "DHCP (Dynamic Host Configuration Protocol)"
+msgstr ""
+
+#. Tag: primary
+#: networkconfig-fedora.xml:16
+#, no-c-format
+msgid "IPv4"
+msgstr ""
+
+#. Tag: primary
+#: networkconfig-fedora.xml:19
+#, no-c-format
+msgid "hostname"
+msgstr ""
+
+#. Tag: primary
+#: networkconfig-fedora.xml:21
+#, no-c-format
+msgid "modem"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:25
+#, no-c-format
+msgid ""
+"Fedora contains support for both IPv4 and IPv6. However, by default, the "
+"installation program configures network interfaces on your computer for "
+"IPv4, and to use DHCP via <application>NetworkManager</application>. "
+"Currently <application>NetworkManager</application> does not support IPv6. "
+"If your network only supports IPv6 you should use <application>system-config-"
+"network</application> after installation to configure your network "
+"interfaces."
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:29
+#, no-c-format
+msgid ""
+"Setup prompts you to supply a host name and domain name for this computer, "
+"in the format <replaceable>hostname</replaceable>.<replaceable>domainname</"
+"replaceable>. Many networks have a DHCP (Dynamic Host Configuration "
+"Protocol) service that automatically supplies connected systems with a "
+"domain name, leaving the user to enter a hostname."
+msgstr ""
+
+#. Tag: title
+#: networkconfig-fedora.xml:33
+#, no-c-format
+msgid "<title>Setting the hostname</title>"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:36
+#, no-c-format
+msgid "<para>Setting the hostname</para>"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:43
+#, no-c-format
+msgid ""
+"To set up a network that is behind an Internet firewall or router, you may "
+"want to use <systemitem class=\"fqdomainname\"><replaceable>hostname</"
+"replaceable>.localdomain</systemitem> for your Fedora system. If you have "
+"more than one computer on this network, you should give each one a separate "
+"host name in this domain."
+msgstr ""
+
+#. Tag: title
+#: networkconfig-fedora.xml:47
+#, no-c-format
+msgid "Valid Hostnames"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:48
+#, no-c-format
+msgid ""
+"You may give your system any name provided that the full hostname is unique. "
+"The hostname may include letters, numbers and hyphens."
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:55
+#, no-c-format
+msgid ""
+"On some networks, the DHCP provider also provides the name of the computer, "
+"or hostname. The complete hostname includes both the name of the machine and "
+"the name of the domain of which it is a member, such as <systemitem class="
+"\"fqdomainname\"><replaceable>machine1.example.com</replaceable></"
+"systemitem>. The machine name (or \"short hostname\") is <systemitem class="
+"\"systemname\"><replaceable>machine1</replaceable></systemitem>, and the "
+"<indexterm> <primary>domain name</primary> </indexterm> domain name is "
+"<systemitem class=\"domainname\"><replaceable>example.com</replaceable></"
+"systemitem>."
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:59
+#, no-c-format
+msgid ""
+"If your Fedora system is connected <emphasis>directly</emphasis> to the "
+"Internet, you must pay attention to additional considerations to avoid "
+"service interruptions or risk action by your upstream service provider. A "
+"full discussion of these issues is beyond the scope of this document."
+msgstr ""
+
+#. Tag: title
+#: networkconfig-fedora.xml:68
+#, no-c-format
+msgid "Modem Configuration"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:69
+#, no-c-format
+msgid ""
+"The installation program does not configure modems. Configure these devices "
+"after installation with the <application>Network</application> utility. The "
+"settings for your modem are specific to your particular Internet Service "
+"Provider (ISP)."
+msgstr ""
+
+#. Tag: title
+#: networkconfig-fedora.xml:78
+#, no-c-format
+msgid "Manual configuration"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:79
+#, no-c-format
+msgid ""
+"Installations that require certain advanced configurations cannot succeed "
+"without network connectivity during the installation process, for example, "
+"installations on systems with ISCSI drives. In situations where successful "
+"installation depends upon correct network settings, the installation program "
+"will present you with a dialog that allows you to confirm these details."
+msgstr ""
+
+#. Tag: title
+#: networkconfig-fedora.xml:83
+#, no-c-format
+msgid "<title>Manual network configuration</title>"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:86
+#, no-c-format
+msgid "<para>Manual network configuration</para>"
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:93
+#, no-c-format
+msgid ""
+"If your network does not have DHCP enabled, or if you need to override the "
+"DHCP settings, select the network interface that you plan to use from the "
+"<guilabel>Interfaces</guilabel> menu. Clear the checkbox for <guilabel>Use "
+"dynamic IP configuration (DHCP)</guilabel>. You can now enter an IPv4 "
+"address and netmask for this system in the form <replaceable>address</"
+"replaceable> / <replaceable>netmask</replaceable>, along with the "
+"gateway address and nameserver address for your network."
+msgstr ""
+
+#. Tag: para
+#: networkconfig-fedora.xml:97
+#, no-c-format
+msgid "Click <guilabel>OK</guilabel> to accept these settings and continue."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:7
+#, no-c-format
+msgid "New Users"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:8
+#, no-c-format
+msgid ""
+"This chapter explains how to get the files you need to install and run "
+"Fedora on your computer. Concepts in this chapter may be new, especially if "
+"this is your first free and open source operating system. If you have any "
+"trouble with this chapter, find help by visiting the Fedora Forums at <ulink "
+"url=\"http://www.fedoraforum.org/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:16
+#, no-c-format
+msgid "Download Links"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:17
+#, no-c-format
+msgid ""
+"To follow a Web-based guide to downloading, visit <ulink url=\"http://get."
+"fedoraproject.org/\"></ulink>. For guidance on which architecture to "
+"download, refer to <xref linkend=\"sn-which-arch\"/>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:24
+#, no-c-format
+msgid "How Do I Download Installation Files?"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:25
+#, no-c-format
+msgid ""
+"The Fedora Project distributes Fedora in many ways, mostly free of cost and "
+"downloaded over the Internet. The most common distribution method is CD and "
+"DVD media. There are several types of CD and DVD media available, including:"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:31
+#, no-c-format
+msgid "A full set of the software on DVD media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:34
+#, no-c-format
+msgid ""
+"Live images you can use to try Fedora, and then install to your system if "
+"you so choose"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:38
+#, no-c-format
+msgid ""
+"Reduced-size bootable CD and USB flash disk images you can use to install "
+"over an Internet connection"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:42
+#, no-c-format
+msgid "Source code on DVD media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:45
+#, no-c-format
+msgid ""
+"Most users want the Fedora Live image or the full set of installable "
+"software on DVD or CDs. The reduced bootable images are suitable for use "
+"with a fast Internet connection and install Fedora on one computer. Source "
+"code discs are not used for installing Fedora, but are resources for "
+"experienced users and software developers."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:51
+#, no-c-format
+msgid "Downloading media"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:53 new-users.xml:445
+#, no-c-format
+msgid "CD/DVD media"
+msgstr ""
+
+#. Tag: seealso
+#: new-users.xml:55
+#, no-c-format
+msgid "<seealso>ISO images</seealso>"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:58
+#, no-c-format
+msgid "<primary>ISO images</primary>"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:62 new-users.xml:449
+#, no-c-format
+msgid "USB flash media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:65
+#, no-c-format
+msgid ""
+"Users with a broadband Internet connection can download <firstterm>ISO "
+"images</firstterm> of CD and DVD media or images of USB flash disks. An ISO "
+"image is a copy of an entire disc in a format suitable for writing directly "
+"to a CD or DVD. A USB flash disk image is a copy of an entire disk in a "
+"format suitable for writing directly to a USB flash disk."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:71
+#, no-c-format
+msgid ""
+"For more information on burning CDs and DVDs, refer to <xref linkend=\"sn-"
+"making-media\"/>."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:74
+#, no-c-format
+msgid ""
+"Fedora software is available for download at no cost in a variety of ways."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:77
+#, no-c-format
+msgid "From a Mirror"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:79
+#, no-c-format
+msgid "mirror"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:81
+#, no-c-format
+msgid ""
+"To find the freely downloadable distributions of Fedora, look for a "
+"<firstterm>mirror</firstterm>. A mirror is a computer server open to the "
+"public for free downloads of software, including Fedora. Mirrors offer both "
+"free open source software and closed source software. To locate a mirror, "
+"visit <ulink url=\"http://mirrors.fedoraproject.org/publiclist\"></ulink> "
+"using a Web browser, and choose a server from the list. The web page lists "
+"mirrors by geographic location. Mirrors geographically closer to you are "
+"ideal for faster downloading speeds."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:89
+#, no-c-format
+msgid ""
+"Mirrors publish Fedora software under a well-organized hierarchy of folders. "
+"For example, the Fedora &PRODVER; distribution normally appears in the "
+"directory <filename class=\"directory\">fedora/linux/releases/&PRODVER;/</"
+"filename>. This directory contains a folder for each architecture supported "
+"by that release of Fedora. CD and DVD media files appear inside that folder, "
+"in a folder called <filename>iso/</filename>. For example, you can find the "
+"file for the DVD distribution of Fedora &PRODVER; for x86_64 at "
+"<filename>fedora/linux/releases/&PRODVER;/Fedora/x86_64/iso/Fedora-&PRODVER;-"
+"x86_64-DVD.iso</filename>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:101
+#, no-c-format
+msgid "From BitTorrent"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:103 new-users.xml:106
+#, no-c-format
+msgid "BitTorrent"
+msgstr ""
+
+#. Tag: secondary
+#: new-users.xml:107
+#, no-c-format
+msgid "seeding"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:109
+#, no-c-format
+msgid ""
+"BitTorrent is a way to download information in cooperation with other "
+"computers. Each computer cooperating in the group downloads pieces of the "
+"information in a particular torrent from other peers in the group. Computers "
+"that have finished downloading all the data in a torrent remain in the swarm "
+"to <firstterm>seed</firstterm>, or provide data to other peers. If you "
+"download using BitTorrent, as a courtesy you should seed the torrent at "
+"least until you have uploaded the same amount of data you downloaded."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:118
+#, no-c-format
+msgid ""
+"If your computer does not have software installed for BitTorrent, visit the "
+"BitTorrent home page at <ulink url=\"http://www.bittorrent.com/download/\"></"
+"ulink> to download it. BitTorrent client software is available for Windows, "
+"Mac OS, Linux, and many other operating systems."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:122
+#, no-c-format
+msgid ""
+"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 <ulink url="
+"\"http://torrent.fedoraproject.org/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:127
+#, no-c-format
+msgid "Minimal Boot Images"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:128
+#, no-c-format
+msgid ""
+"Minimal boot CD and USB flash disk images are not available through "
+"BitTorrent."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:134
+#, no-c-format
+msgid "Which Architecture Is My Computer?"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:136 new-users.xml:144
+#, no-c-format
+msgid "architecture"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:138
+#, no-c-format
+msgid ""
+"Releases are separated by <firstterm>architecture</firstterm>, or type of "
+"computer processor. Use the following table to determine the architecture of "
+"your computer according to the type of processor. Consult your "
+"manufacturer's documentation for details on your processor, if necessary."
+msgstr ""
+
+#. Tag: secondary
+#: new-users.xml:145
+#, no-c-format
+msgid "determining"
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:148
+#, no-c-format
+msgid "Processor and architecture types"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:154
+#, no-c-format
+msgid "Processor manufacturer and model"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:155
+#, no-c-format
+msgid "Architecture type for Fedora"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:160
+#, no-c-format
+msgid ""
+"Intel (except Atom 230, Atom 330, Core 2 Duo, Centrino Core2 Duo, and recent "
+"vintage Xeon); AMD (except Athlon 64, Athlon x2, Sempron 64, and Opteron); "
+"VIA C3, C7"
+msgstr ""
+
+#. Tag: systemitem
+#: new-users.xml:162
+#, no-c-format
+msgid "i386"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:165
+#, no-c-format
+msgid ""
+"Intel Atom 230, Atom 330, Core 2 Duo, Centrino Core 2 Duo, and Xeon; AMD "
+"Athlon 64, Athlon x2, Sempron64, and Opteron; Apple MacBook, MacBook Pro, "
+"and MacBook Air"
+msgstr ""
+
+#. Tag: systemitem
+#: new-users.xml:167
+#, no-c-format
+msgid "x86_64"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:170
+#, no-c-format
+msgid "Apple Macintosh G3, G4, G5, PowerBook, and other non-Intel models"
+msgstr ""
+
+#. Tag: systemitem
+#: new-users.xml:172
+#, no-c-format
+msgid "<systemitem>ppc</systemitem>"
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:178
+#, no-c-format
+msgid ""
+"<systemitem>i386</systemitem> Works for Most Windows Compatible Computers"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:180
+#, no-c-format
+msgid ""
+"If you are unsure what type of processor your computer uses, choose "
+"<systemitem>i386</systemitem>."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:182
+#, no-c-format
+msgid ""
+"The exception is if your computer is a non-Intel based Apple Macintosh. "
+"Refer to <xref linkend=\"List-Processor_and_Architecture_Types\"/> for more "
+"information."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:187
+#, no-c-format
+msgid "Intel Atom Processor Architectures Vary"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:188
+#, no-c-format
+msgid ""
+"The N and Z Series Atom processors are based on the <systemitem>i386</"
+"systemitem> architecture. The 230 and 330 Series Atom processors are based "
+"on the<systemitem>x86_64</systemitem> architecture. Refer to <ulink url="
+"\"http://ark.intel.com/cpugroup.aspx?familyID=29035\"></ulink> for more "
+"details."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:195
+#, no-c-format
+msgid "Which Files Do I Download?"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:196
+#, no-c-format
+msgid ""
+"You have several options to download Fedora. Read the options below to "
+"decide the best one for you."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:198
+#, no-c-format
+msgid ""
+"Each file available for download in a Fedora distribution includes the "
+"architecture type in the file name. For example, the file for the DVD "
+"distribution of Fedora &PRODVER; for x86_64 is named <filename>Fedora-"
+"&PRODVER;-x86_64-DVD.iso</filename>. Refer to <xref linkend=\"sn-which-arch"
+"\"/> if you are unsure of your computer's architecture."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:208
+#, no-c-format
+msgid "Full Distribution on DVD"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:209
+#, no-c-format
+msgid ""
+"If you have plenty of time, a fast Internet connection, and wish a broader "
+"choice of software on the install media, download the full DVD version. Once "
+"burned to DVD, the media is bootable and includes an installation program. "
+"The DVD version contains a mode to perform rescue operations on your Fedora "
+"system in an emergency. You can download the DVD version directly from a "
+"mirror, or via BitTorrent."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:220
+#, no-c-format
+msgid "Live Image"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:221
+#, no-c-format
+msgid ""
+"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 <literal>Install to Hard Disk</"
+"literal> desktop shortcut. 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."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:241
+#, no-c-format
+msgid "Minimal Boot Media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:242
+#, no-c-format
+msgid ""
+"If you have a fast Internet connection but do not want to download the "
+"entire distribution, you can download a small boot image. Fedora offers "
+"images for a minimal boot environment on CD. Once you boot your system with "
+"the minimal media, you can install Fedora directly over the Internet. "
+"Although this method still involves downloading a significant amount of data "
+"over the Internet, it is almost always much less than the size of the full "
+"distribution media. Once you have finished installation, you can add or "
+"remove software to your system as desired."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:254
+#, no-c-format
+msgid "Download Size"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:255
+#, no-c-format
+msgid ""
+"Installing the default software for Fedora over the Internet requires more "
+"time than the Live image, but less time than the entire DVD distribution. "
+"Actual results depend on the software you select and network traffic "
+"conditions."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:263
+#, no-c-format
+msgid ""
+"The following table explains where to find the desired files on a mirror "
+"site. Replace <replaceable>arch</replaceable> with the architecture of the "
+"computer being installed."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:267
+#, no-c-format
+msgid "Locating files"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:273
+#, no-c-format
+msgid "Media type"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:274
+#, no-c-format
+msgid "File locations"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:279
+#, no-c-format
+msgid "Full distribution on DVD"
+msgstr ""
+
+#. Tag: filename
+#: new-users.xml:280
+#, no-c-format
+msgid ""
+"fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/iso/"
+"Fedora-&PRODVER;-<replaceable>arch</replaceable>-DVD.iso"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:283
+#, no-c-format
+msgid "Live image"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:284
+#, no-c-format
+msgid ""
+"<filename>fedora/linux/releases/&PRODVER;/Live/<replaceable>arch</"
+"replaceable>/iso/Fedora-&PRODVER;-<replaceable>arch</replaceable>-Live.iso</"
+"filename>, <filename>fedora/linux/releases/&PRODVER;/Live/<replaceable>arch</"
+"replaceable>/iso/Fedora-&PRODVER;-KDE-<replaceable>arch</replaceable>-Live."
+"iso</filename>"
+msgstr ""
+
+#. Tag: entry
+#: new-users.xml:288
+#, no-c-format
+msgid "Minimal CD boot media"
+msgstr ""
+
+#. Tag: filename
+#: new-users.xml:289
+#, no-c-format
+msgid ""
+"fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os/"
+"images/boot.iso"
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:296
+#, no-c-format
+msgid "How Do I Make Fedora Media?"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:297
+#, no-c-format
+msgid ""
+"A Fedora ISO file can be turned into either CD or DVD discs. You can turn "
+"Fedora Live ISO files into bootable USB media, as well as a CD or DVD."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:303
+#, no-c-format
+msgid "Making CD or DVD Discs"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:304
+#, no-c-format
+msgid ""
+"To learn how to turn ISO images into CD or DVD media, refer to <ulink url="
+"\"http://docs.fedoraproject.org/readme-burning-isos/\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:309
+#, no-c-format
+msgid "Making USB Media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:310
+#, no-c-format
+msgid ""
+"To make bootable USB media, use a Fedora Live image. Use either a Windows or "
+"Linux system to make the bootable USB media."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:315
+#, no-c-format
+msgid "USB Image Writing is Nondestructive"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:316
+#, no-c-format
+msgid ""
+"Writing the Live image to the USB media is <emphasis>nondestructive</"
+"emphasis>. Any existing data on the media is not harmed."
+msgstr ""
+
+#. Tag: emphasis
+#: new-users.xml:322
+#, no-c-format
+msgid ""
+"It is always a good idea to back up important data before performing "
+"sensitive disk operations."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:326
+#, no-c-format
+msgid ""
+"To begin, make sure there is sufficient free space available on the USB "
+"media. There is no need to repartition or reformat your media. <emphasis>It "
+"is always a good idea to back up important data before performing sensitive "
+"disk operations.</emphasis>"
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:334
+#, no-c-format
+msgid "USB Image Creation from Windows"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:337
+#, no-c-format
+msgid ""
+"Download a Live ISO file as explained in <xref linkend=\"sn-which-files\"/>."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:342
+#, no-c-format
+msgid ""
+"Download the Windows <application>liveusb-creator</application> program at "
+"<ulink url=\"http://fedorahosted.org/liveusb-creator\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:348
+#, no-c-format
+msgid ""
+"Follow the instructions given at the site and in the <application>liveusb-"
+"creator</application> program to create the bootable USB media."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:357
+#, no-c-format
+msgid "USB Image Creation in Linux"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:359
+#, no-c-format
+msgid ""
+"USB media often comes in the form of flash devices sometimes called "
+"<firstterm>pen drives</firstterm>, <firstterm>thumb disks</firstterm>, or "
+"<firstterm>keys</firstterm>; or as an externally connected hard disk device. "
+"Almost all media of this type is formatted as a vfat file system. You can "
+"create bootable USB media on media formatted as ext2, ext3, or vfat."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:369
+#, no-c-format
+msgid ""
+"The <application>GRUB</application> bootloader does not support the ext4 or "
+"Btrfs file systems. You cannot create bootable USB media on media formatted "
+"as ext4 or Btrfs."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:374
+#, no-c-format
+msgid "Unusual USB Media"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:375
+#, no-c-format
+msgid ""
+"In a few cases with oddly formatted or partitioned USB media, the image "
+"writing may fail."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:381
+#, no-c-format
+msgid ""
+"Download a Live ISO file as shown in <xref linkend=\"sn-which-files\"/>."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:387
+#, no-c-format
+msgid ""
+"Install the <package>livecd-tools</package> package on your system. For "
+"Fedora systems, use the following command:"
+msgstr ""
+
+#. Tag: screen
+#: new-users.xml:391
+#, no-c-format
+msgid "<![CDATA[su -c 'yum -y install livecd-tools']]>"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:394
+#, no-c-format
+msgid "Plug in your USB media."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:399
+#, no-c-format
+msgid ""
+"Find the device name for your USB media. If the media has a volume name, "
+"look up the name in <filename class=\"directory\">/dev/disk/by-label</"
+"filename>, or use the <command>findfs</command>:"
+msgstr ""
+
+#. Tag: screen
+#: new-users.xml:405
+#, no-c-format
+msgid ""
+"<![CDATA[su -c 'findfs LABEL=\"]]><replaceable>MyLabel</replaceable><![CDATA"
+"[\"']]>"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:406
+#, no-c-format
+msgid ""
+"If the media does not have a volume name, or you do not know it, consult the "
+"<filename>/var/log/messages</filename> log for details:"
+msgstr ""
+
+#. Tag: screen
+#: new-users.xml:411
+#, no-c-format
+msgid "<![CDATA[su -c 'less /var/log/messages']]>"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:414
+#, no-c-format
+msgid ""
+"Use the <command>livecd-iso-to-disk</command> command to write the ISO image "
+"to the media:"
+msgstr ""
+
+#. Tag: screen
+#: new-users.xml:418
+#, no-c-format
+msgid ""
+"<![CDATA[su -c 'livecd-iso-to-disk ]]><replaceable>the_image.iso</"
+"replaceable><![CDATA[ /dev/]]><replaceable>sdX1</replaceable><![CDATA[']]>"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:419
+#, no-c-format
+msgid ""
+"Replace <replaceable>sdX1</replaceable> with the device name for the "
+"partition on the USB media. Most flash drives and external hard disks use "
+"only one partition. If you have changed this behavior or have oddly "
+"partitioned media, you may need to consult other sources of help."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:432
+#, no-c-format
+msgid "What If I Cannot Download Fedora?"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:433
+#, no-c-format
+msgid ""
+"If you do not have a fast Internet connection, or if you have a problem "
+"creating boot media, downloading may not be an option. Fedora DVD and CD "
+"distribution media is available from a number of online sources around the "
+"world at a minimal cost. Use your favorite Web search engine to locate a "
+"vendor, or refer to <ulink url=\"http://fedoraproject.org/wiki/Distribution"
+"\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:440
+#, no-c-format
+msgid "How Do I Start the Installation Program?"
+msgstr ""
+
+#. Tag: primary
+#: new-users.xml:442
+#, no-c-format
+msgid "BIOS (Basic Input/Output System)"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:452
+#, no-c-format
+msgid ""
+"To start the installation program from minimal boot media, a Live image, or "
+"the distribution DVD, follow this procedure:"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:456
+#, no-c-format
+msgid "Power off your computer system."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:459
+#, no-c-format
+msgid ""
+"Disconnect any external FireWire or USB disks that you do not need for "
+"installation. Refer to <xref linkend=\"sn-partitioning-fw-usb\"/> for more "
+"information."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:465
+#, no-c-format
+msgid "Insert the media in your computer and turn it on."
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:468
+#, no-c-format
+msgid ""
+"You may need to press a specific key or combination of keys to boot from the "
+"media, or configure your system's <firstterm>Basic Input/Output System</"
+"firstterm>, or <acronym>BIOS</acronym>, to boot from the media. On most "
+"computers you must select the boot or BIOS option promptly after turning on "
+"the computer. Most Windows-compatible computer systems use a special key "
+"such as <keycap>F1</keycap>, <keycap>F2</keycap>, <keycap>F12</keycap>, or "
+"<keycap>Del</keycap> to start the BIOS configuration menu. On Apple "
+"computers, the <keycap>C</keycap> key boots the system from the DVD drive. "
+"On older Apple hardware you may need to press <keycap>Cmd</keycap> "
+"+<keycap>Opt</keycap>+<keycap>Shift</keycap>+<keycap>Del</keycap> to boot "
+"from DVD drive."
+msgstr ""
+
+#. Tag: title
+#: new-users.xml:481
+#, no-c-format
+msgid "Configuring the BIOS"
+msgstr ""
+
+#. Tag: para
+#: new-users.xml:482
+#, no-c-format
+msgid ""
+"If you are not sure what capabilities your computer has, or how to configure "
+"the BIOS, consult the documentation provided by the manufacturer. Detailed "
+"information on hardware specifications and configuration is beyond the scope "
+"of this document."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:10
+#, no-c-format
+msgid "Your Next Steps"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:11
+#, no-c-format
+msgid ""
+"Fedora provides you with a complete operating system with a vast range of "
+"capabilities, supported by a large community."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:16
+#, no-c-format
+msgid "Updating Your System"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:18
+#, no-c-format
+msgid ""
+"The Fedora Project releases updated software packages for Fedora throughout "
+"the support period of each version. Updated packages add new features, "
+"improve reliability, resolve bugs, or remove security vulnerabilities. To "
+"ensure the security of your system, update regularly, and as soon as "
+"possible after a security announcement is issued. Refer to <xref linkend="
+"\"sn-news-subscriptions\"/> for information on the Fedora announcements "
+"services."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:28
+#, no-c-format
+msgid ""
+"An update applet reminds you of updates when they are available. This applet "
+"is installed by default in Fedora. It checks for software updates from all "
+"configured repositories, and runs as a background service. It generates a "
+"notification message on the desktop if updates are found, and you can click "
+"the message to update your system's software."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:36
+#, no-c-format
+msgid ""
+"To update your system with the latest packages manually, use <indexterm> "
+"<primary>Update System</primary> </indexterm> <application>Update System</"
+"application>:"
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:43
+#, no-c-format
+msgid "Updating your system"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:46
+#, no-c-format
+msgid "Updating your system screen"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:55
+#, no-c-format
+msgid ""
+"Choose <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</"
+"guisubmenu> <guimenuitem>Update System</guimenuitem> </menuchoice>."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:64
+#, no-c-format
+msgid ""
+"To review the list of updated packages, select <guilabel>Review</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:70
+#, no-c-format
+msgid "Click <guibutton>Update System</guibutton> to begin the update process."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:76
+#, no-c-format
+msgid ""
+"If one or more updates require a system reboot, the update process displays "
+"a dialog with the option to <guibutton>Reboot Now</guibutton>. Either select "
+"this option to reboot the system immediately, or <guibutton>Cancel</"
+"guibutton> it and reboot the system at a more convenient time."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:85
+#, no-c-format
+msgid ""
+"If a reboot is not required the update will conclude with a dialog that "
+"indicates that the System Update Completed and all selected updates have "
+"been successfully installed as well as a button to <guibutton>Close</"
+"guibutton> <indexterm><primary>Update System</primary></indexterm> "
+"<application>Update System</application>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:95
+#, no-c-format
+msgid ""
+"To update packages from the command-line, use the <indexterm> <primary>yum</"
+"primary> </indexterm> <command>yum</command> utility. Type this command to "
+"begin a full update of your system with <command>yum</command>:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:103
+#, no-c-format
+msgid "<userinput>su -c 'yum update'</userinput>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:110
+#, no-c-format
+msgid ""
+"Refer to <ulink url=\"http://docs.fedoraproject.org/yum/\"></ulink> for more "
+"information on <command>yum</command>."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:116
+#, no-c-format
+msgid "Network Connection Required"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:118
+#, no-c-format
+msgid ""
+"Ensure that your system has an active network connection before you run the "
+"<application>Update Software</application> tool, or the <command>yum</"
+"command> utility. The update process downloads information and packages from "
+"a network of servers."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:125
+#, no-c-format
+msgid ""
+"If your Fedora system has a permanent network connection, you may choose to "
+"enable daily system updates. To enable automatic updates, follow the "
+"instructions on the webpage <ulink url=\"http://docs.fedoraproject.org/yum/"
+"sn-updating-your-system.html\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:132
+#, no-c-format
+msgid "Finishing an Upgrade"
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:134
+#, no-c-format
+msgid "System Updates Recommended"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:135
+#, no-c-format
+msgid ""
+"Once you have rebooted your system after performing an upgrade, you should "
+"also perform a manual system update. Consult <xref linkend=\"sn-system-"
+"updating\"/> for more information."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:140
+#, no-c-format
+msgid ""
+"If you chose to upgrade your system from a previous release rather than "
+"perform a fresh installation, you may want to examine the differences in the "
+"package set. <xref linkend=\"sn-upgrade-tree\"/> advised you to create a "
+"package listing for your original system. You can now use that listing to "
+"determine how to bring your new system close to the original system state."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:147
+#, no-c-format
+msgid ""
+"Most software repository configurations are stored in packages that end with "
+"the term <literal>release</literal>. Check the old package list for the "
+"repositories that were installed:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:150
+#, no-c-format
+msgid ""
+"<command><![CDATA[awk '{print $1}' ~/old-pkglist.txt | grep 'release$']]></"
+"command>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:151
+#, no-c-format
+msgid ""
+"If necessary, retrieve and install these software repository packages from "
+"their original sources on the Internet. Follow the instructions at the "
+"originating site to install the repository configuration packages for use by "
+"<command>yum</command> and other software management tools on your Fedora "
+"system."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:156
+#, no-c-format
+msgid ""
+"Then run the following commands to make a list of other missing software "
+"packages:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:159
+#, no-c-format
+msgid ""
+"<command>awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames."
+"txt</command>\n"
+"<command>rpm -qa --qf '%{NAME}\\n' | sort | uniq > ~/new-pkgnames.txt</"
+"command>\n"
+"<command>diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/"
+"^-//' > /tmp/pkgs-to-install.txt</command>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:161
+#, no-c-format
+msgid ""
+"Now use the file <filename>/tmp/pkgs-to-install.txt</filename> with the "
+"<command>yum</command> command to restore most or all of your old software:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:165
+#, no-c-format
+msgid ""
+"<command><![CDATA[su -c 'yum install `cat /tmp/pkgs-to-install.txt`']]></"
+"command>"
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:168
+#, no-c-format
+msgid "Missing Software"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:169
+#, no-c-format
+msgid ""
+"Due to changes in package complements between Fedora releases, it is "
+"possible this method may not restore all the software on your system. You "
+"can use the routines above to again compare the software on your system, and "
+"remedy any problems you find."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:177
+#, no-c-format
+msgid "Switching to a Graphical Login"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:178
+#, no-c-format
+msgid ""
+"If you installed using a text login and wish to switch to a graphical login, "
+"follow this procedure."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:184
+#, no-c-format
+msgid "Switch users to the <systemitem>root</systemitem> account:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:187
+#, no-c-format
+msgid "<![CDATA[su -]]>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:188
+#, no-c-format
+msgid "Provide the administrator password when prompted."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:193
+#, no-c-format
+msgid ""
+"If you have not already done so, install one of the graphical desktop "
+"environments. For instance, to install the GNOME desktop environment, use "
+"this command:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:198
+#, no-c-format
+msgid "<![CDATA[yum groupinstall \"GNOME Desktop Environment\"]]>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:199
+#, no-c-format
+msgid ""
+"This step may take some time as your Fedora system downloads and installs "
+"additional software. You may be asked to provide the installation media "
+"depending on your original installation source."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:207
+#, no-c-format
+msgid ""
+"Run the following command to edit the <filename>/etc/inittab</filename> file:"
+msgstr ""
+
+#. Tag: screen
+#: nextsteps.xml:211
+#, no-c-format
+msgid "<![CDATA[nano /etc/inittab]]>"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:214
+#, no-c-format
+msgid ""
+"Find the line that includes the text <literal>initdefault</literal>. Change "
+"the numeral <literal>3</literal> to <literal>5</literal>."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:219
+#, no-c-format
+msgid ""
+"Hit <keycombo><keycap>Ctrl</keycap><keycap>O</keycap></keycombo> to write "
+"the file to disk, and then hit <keycombo><keycap>Ctrl</keycap><keycap>X</"
+"keycap></keycombo> to exit the program."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:228
+#, no-c-format
+msgid "Type <command>exit</command> to logout of the administrator account."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:233
+#, no-c-format
+msgid ""
+"If desired, you can reboot the system using the <command>reboot</command> "
+"command. Your system will restart and present a graphical login."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:238
+#, no-c-format
+msgid ""
+"If you encounter any problems with the graphical login, consult one of the "
+"help sources listed in <xref linkend=\"sn-additional-help\"/>."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:245
+#, no-c-format
+msgid "Subscribing to Fedora Announcements and News"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:247
+#, no-c-format
+msgid ""
+"To receive information about package updates, subscribe to either the "
+"announcements mailing list, or the RSS feeds."
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:254
+#, no-c-format
+msgid "Fedora Project announcements mailing list"
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:265
+#, no-c-format
+msgid "Fedora Project RSS feeds"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:276
+#, no-c-format
+msgid ""
+"The announcements mailing list also provides you with news on the Fedora "
+"Project, and the Fedora community."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:282
+#, no-c-format
+msgid "Security Announcements"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:284
+#, no-c-format
+msgid ""
+"Announcements with the keyword <wordasword>[SECURITY]</wordasword> in the "
+"title identify package updates that resolve security vulnerabilities."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:292
+#, no-c-format
+msgid "Finding Documentation and Support"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:294
+#, no-c-format
+msgid ""
+"Members of the Fedora community provide support through mailing lists, Web "
+"forums and Linux User Groups (LUGs) across the world."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:299
+#, no-c-format
+msgid ""
+"The Web site for the formally endorsed forums is <ulink url=\"http://forums."
+"fedoraforum.org/\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:304
+#, no-c-format
+msgid "The following resources provide information on many aspects of Fedora:"
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:313
+#, no-c-format
+msgid "The FAQ on the Fedora Project website"
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:327
+#, no-c-format
+msgid "The documents available from the Fedora Documentation Project Web site"
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:341
+#, no-c-format
+msgid "The Linux Documentation Project (LDP)"
+msgstr ""
+
+#. Tag: term
+#: nextsteps.xml:355
+#, no-c-format
+msgid ""
+"The Red Hat Enterprise Linux documentation, much of which also applies to "
+"Fedora"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:369
+#, no-c-format
+msgid ""
+"Many other organizations and individuals also provide tutorials and HOWTOs "
+"for Fedora on their Web sites. You can locate information on any topic by "
+"using Google's Linux search site, located at <ulink url=\"http://www.google."
+"com/linux\"></ulink>."
+msgstr ""
+
+#. Tag: title
+#: nextsteps.xml:377
+#, no-c-format
+msgid "Joining the Fedora Community"
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:379
+#, no-c-format
+msgid ""
+"The Fedora Project is driven by the individuals that contribute to it. "
+"Community members provide support and documentation to other users, help to "
+"improve the software included in Fedora by testing, and develop new software "
+"alongside the programmers employed by Red Hat. The results of this work are "
+"available to all."
+msgstr ""
+
+#. Tag: para
+#: nextsteps.xml:387
+#, no-c-format
+msgid "To make a difference, start here:"
+msgstr ""
+
+#. Tag: title
+#: Other_Disk_Devices-x86.xml:7
+#, no-c-format
+msgid "RAID and Other Disk Devices"
+msgstr ""
+
+#. Tag: title
+#: Other_Disk_Devices-x86.xml:16
+#, no-c-format
+msgid "Hardware RAID"
+msgstr ""
+
+#. Tag: para
+#: Other_Disk_Devices-x86.xml:17
+#, no-c-format
+msgid ""
+"RAID, or Redundant Array of Independent Disks, allows a group, or array, of "
+"drives to act as a single device. Configure any RAID functions provided by "
+"the mainboard of your computer, or attached controller cards, before you "
+"begin the installation process. Each active RAID array appears as one drive "
+"within Fedora."
+msgstr ""
+
+#. Tag: para
+#: Other_Disk_Devices-x86.xml:25
+#, no-c-format
+msgid ""
+"On systems with more than one hard drive you may configure Fedora to operate "
+"several of the drives as a Linux RAID array without requiring any additional "
+"hardware."
+msgstr ""
+
+#. Tag: title
+#: Other_Disk_Devices-x86.xml:32
+#, no-c-format
+msgid "Software RAID"
+msgstr ""
+
+#. Tag: para
+#: Other_Disk_Devices-x86.xml:33
+#, no-c-format
+msgid ""
+"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 <xref "
+"linkend=\"s1-diskpartitioning-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Other_Disk_Devices-x86.xml:40
+#, no-c-format
+msgid "FireWire and USB Disks"
+msgstr ""
+
+#. Tag: para
+#: Other_Disk_Devices-x86.xml:41
+#, no-c-format
+msgid ""
+"Some FireWire and USB hard disks may not be recognized by the Fedora "
+"installation system. If configuration of these disks at installation time is "
+"not vital, disconnect them to avoid any confusion."
+msgstr ""
+
+#. Tag: title
+#: Other_Disk_Devices-x86.xml:46
+#, no-c-format
+msgid "Post-installation Usage"
+msgstr ""
+
+#. Tag: para
+#: Other_Disk_Devices-x86.xml:47
+#, no-c-format
+msgid ""
+"You can connect and configure external FireWire and USB hard disks after "
+"installation. Most such devices are recognized by the kernel and available "
+"for use at that time."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-imagecap-1.xml:8
+#, no-c-format
+msgid "Choose which package groups you want to install."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-imagecap-2.xml:5
+#, no-c-format
+msgid "Choose to add or remove optional packages from this package group."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-imagecap-3.xml:5
+#, no-c-format
+msgid "Enter the details of additional software repositories."
+msgstr ""
+
+#. Tag: primary
+#: Package_Selection_common-indexterm-4.xml:9
+#, no-c-format
+msgid "installing packages"
+msgstr ""
+
+#. Tag: term
+#: Package_Selection_common-list-1.xml:9
+#, no-c-format
+msgid "Office and Productivity"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-list-1.xml:11
+#, no-c-format
+msgid ""
+"This option provides the OpenOffice.org productivity suite, the Planner "
+"project management application, graphical tools such as the GIMP, and "
+"multimedia applications."
+msgstr ""
+
+#. Tag: term
+#: Package_Selection_common-list-1.xml:20
+#, no-c-format
+msgid "Software Development"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-list-1.xml:22
+#, no-c-format
+msgid ""
+"This option provides the necessary tools to compile software on your Fedora "
+"system."
+msgstr ""
+
+#. Tag: term
+#: Package_Selection_common-list-1.xml:30
+#, no-c-format
+msgid "Web server"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-list-1.xml:32
+#, no-c-format
+msgid "This option provides the Apache Web server."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-note-1.xml:9
+#, no-c-format
+msgid ""
+"If you install from a Fedora Live image, you cannot make package selections. "
+"This installation method transfers a copy of the Live image rather than "
+"installing packages from a repository. To change the package selection, "
+"complete the installation, then use the <application>Add/Remove Software</"
+"application> application to make desired changes."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-note-2.xml:9
+#, no-c-format
+msgid ""
+"If you install Fedora in text mode, you cannot make package selections. The "
+"installer automatically selects packages only from the base and core groups. "
+"These packages are sufficient to ensure that the system is operational at "
+"the end of the installation process, ready to install updates and new "
+"packages. To change the package selection, complete the installation, then "
+"use the <application>Add/Remove Software</application> application to make "
+"desired changes."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"Now that you have made most of the choices for your installation, you are "
+"ready to confirm the default package selection or customize packages for "
+"your system."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-para-2.xml:5
+#, no-c-format
+msgid ""
+"The <guilabel>Package Installation Defaults</guilabel> screen appears and "
+"details the default package set for your Fedora installation. This screen "
+"varies depending on the version of Fedora you are installing."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-para-3.xml:8
+#, no-c-format
+msgid ""
+"To customize your package set further, select the <guilabel>Customize now</"
+"guilabel> option on the screen. Clicking <guibutton>Next</guibutton> takes "
+"you to the <guilabel>Package Group Selection</guilabel> screen."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-para-4.xml:8
+#, no-c-format
+msgid ""
+"You can select package groups, which group components together according to "
+"function (for example, <guilabel>X Window System</guilabel> and "
+"<guilabel>Editors</guilabel>), individual packages, or a combination of the "
+"two."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_common-para-7.xml:7
+#, no-c-format
+msgid ""
+"By default, the Fedora installation process loads a selection of software "
+"that is suitable for a desktop system. To include or remove software for "
+"common tasks, select the relevant items from the list:"
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:8
+#, no-c-format
+msgid "Customizing the Software Selection"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:9
+#, no-c-format
+msgid ""
+"Select <guilabel>Customize now</guilabel> to specify the software packages "
+"for your final system in more detail. This option causes the installation "
+"process to display an additional customization screen when you select "
+"<guibutton>Next</guibutton>."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:16
+#, no-c-format
+msgid "Installing Support for Additional Languages"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:18
+#, no-c-format
+msgid ""
+"Select <guilabel>Customize now</guilabel> to install support for additional "
+"languages. Refer to <xref linkend=\"sn-lang-packages\"/> for more "
+"information on configuring language support."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:26
+#, no-c-format
+msgid "Package Group Details"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:37
+#, no-c-format
+msgid ""
+"Fedora divides the included software into <indexterm> <primary>package "
+"groups</primary> </indexterm> <firstterm>package groups</firstterm>. For "
+"ease of use, the package selection screen displays these groups as "
+"categories."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:49
+#, no-c-format
+msgid ""
+"To view the package groups for a category, select the category from the list "
+"on the left. The list on the right displays the package groups for the "
+"currently selected category."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:55
+#, no-c-format
+msgid ""
+"To specify a package group for installation, select the check box next to "
+"the group. The box at the bottom of the screen displays the details of the "
+"package group that is currently highlighted. <emphasis>None</emphasis> of "
+"the packages from a group will be installed unless the check box for that "
+"group is selected."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:63
+#, no-c-format
+msgid ""
+"If you select a package group, Fedora automatically installs the base and "
+"mandatory packages for that group. To change which optional packages within "
+"a selected group will be installed, select the <guibutton>Optional Packages</"
+"guibutton> button under the description of the group. Then use the check box "
+"next to an individual package name to change its selection."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:71
+#, no-c-format
+msgid ""
+"After you choose the desired packages, select <guilabel>Next</guilabel> to "
+"proceed. Fedora checks your selection, and automatically adds any extra "
+"packages required to use the software you select. When you have finished "
+"selecting packages, click <guilabel>Close</guilabel> to save your optional "
+"package selections and return to the main package selection screen."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:81
+#, no-c-format
+msgid "Changing Your Mind"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:82
+#, no-c-format
+msgid ""
+"The packages that you select are not permanent. After you boot your system, "
+"use the <application>Add/Remove Software</application> tool to either "
+"install new software or remove installed packages. To run this tool, from "
+"the main menu, select <menuchoice> <guimenu>System</guimenu> "
+"<guisubmenu>Administration</guisubmenu> <guimenuitem>Add/Remove Software</"
+"guimenuitem> </menuchoice>. The Fedora software management system downloads "
+"the latest packages from network servers, rather than using those on the "
+"installation discs."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:96
+#, no-c-format
+msgid "Additional Language Support"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:98
+#, no-c-format
+msgid ""
+"Your Fedora system automatically supports the language that you selected at "
+"the start of the installation process. To include support for additional "
+"languages, select the package group for those languages from the "
+"<guilabel>Languages</guilabel> category."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Customizing-x86.xml:108
+#, no-c-format
+msgid "Core Network Services"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:110
+#, no-c-format
+msgid "All Fedora installations include the following network services:"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:117
+#, no-c-format
+msgid "centralized logging through syslog"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:122
+#, no-c-format
+msgid "email through SMTP (Simple Mail Transfer Protocol)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:127
+#, no-c-format
+msgid "network file sharing through NFS (Network File System)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:132
+#, no-c-format
+msgid "remote access through SSH (Secure SHell)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:137
+#, no-c-format
+msgid "resource advertising through mDNS (multicast DNS)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:143
+#, no-c-format
+msgid "The default installation also provides:"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:149
+#, no-c-format
+msgid "network file transfer through HTTP (HyperText Transfer Protocol)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:155
+#, no-c-format
+msgid "printing through CUPS (Common UNIX Printing System)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:160
+#, no-c-format
+msgid "remote desktop access through VNC (Virtual Network Computing)"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:167
+#, no-c-format
+msgid ""
+"Some automated processes on your Fedora system use the email service to send "
+"reports and messages to the system administrator. By default, the email, "
+"logging, and printing services do not accept connections from other systems. "
+"Fedora installs the NFS sharing, HTTP, and VNC components without enabling "
+"those services."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Customizing-x86.xml:176
+#, no-c-format
+msgid ""
+"You may configure your Fedora system after installation to offer email, file "
+"sharing, logging, printing and remote desktop access services. The SSH "
+"service is enabled by default. You may use NFS to access files on other "
+"systems without enabling the NFS sharing service."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Repositories-x86.xml:8
+#, no-c-format
+msgid "Installing from Additional Repositories"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:9
+#, no-c-format
+msgid ""
+"You can define additional <firstterm>repositories</firstterm> to increase "
+"the software available to your system during installation. A repository is a "
+"network location that stores software packages along with "
+"<firstterm>metadata</firstterm> 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."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:20
+#, no-c-format
+msgid "The basic options are:"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:23
+#, no-c-format
+msgid ""
+"The <guilabel>Installation Repo</guilabel> repository is automatically "
+"selected for you. This represents the collection of software available on "
+"your installation CD or DVD."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:29
+#, no-c-format
+msgid ""
+"The <guilabel>Fedora &PRODVER; - i386</guilabel> repository contains the "
+"complete collection of software that was released as Fedora &PRODVER;, with "
+"the various pieces of software in their versions that were current at the "
+"time of release. If you are installing from the Fedora &PRODVER; DVD or "
+"<emphasis>set</emphasis> of CDs, this option does not offer you anything "
+"extra. However, if you are installing from a Fedora Live CD, this option "
+"provides access to far more software than is included on the disk. Note that "
+"the computer must have access to the internet to use this option."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:33
+#, no-c-format
+msgid ""
+"The <guilabel>Fedora &PRODVER; - i386 - Updates</guilabel> repository "
+"contains the complete collection of software that was released as Fedora "
+"&PRODVER;, with the various pieces of software in their most current stable "
+"versions. This option not only installs the software that you select, but "
+"makes sure that it is fully updated as well. Note that the computer must "
+"have access to the internet to use this option."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Repositories-x86.xml:39
+#, no-c-format
+msgid "Adding a software repository"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:50
+#, no-c-format
+msgid ""
+"To include software from <firstterm>repositories</firstterm> other than the "
+"Fedora package collection, select <guilabel>Add additional software "
+"repositories</guilabel>. You may provide the location of a repository of "
+"third-party software. Depending on the configuration of that repository, you "
+"may be able to select non-Fedora software during installation."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:58
+#, no-c-format
+msgid ""
+"To edit an existing software repository location, select the repository in "
+"the list and then select <guilabel>Modify repository</guilabel>."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Repositories-x86.xml:64
+#, no-c-format
+msgid "Network Access Required"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:65
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:71
+#, no-c-format
+msgid ""
+"If you select <guilabel>Add additional software repositories</guilabel>, the "
+"<guilabel>Edit repository</guilabel> dialog appears. Provide a "
+"<guilabel>Repository name</guilabel> and the <guilabel>Repository URL</"
+"guilabel> for its location."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Repositories-x86.xml:78
+#, no-c-format
+msgid "Fedora Software Mirrors"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:79
+#, no-c-format
+msgid ""
+"To find a Fedora software mirror near you, refer to <ulink url=\"http://"
+"fedoraproject.org/wiki/Mirrors\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:81
+#, no-c-format
+msgid ""
+"Once you have located a mirror, to determine the URL to use, find the "
+"directory on the mirror that <emphasis>contains</emphasis> a directory named "
+"<filename class=\"directory\">repodata</filename>. For instance, the "
+"\"Everything\" repository for Fedora is typically located in a directory "
+"tree <filename>releases/11/Everything/<replaceable>arch</replaceable>/os</"
+"filename>, where <replaceable>arch</replaceable> is a system architecture "
+"name."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:90
+#, no-c-format
+msgid ""
+"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. See <xref "
+"linkend=\"sn-package-selection\"/> for more information on selecting "
+"packages."
+msgstr ""
+
+#. Tag: title
+#: Package_Selection_Repositories-x86.xml:98
+#, no-c-format
+msgid "Backtracking Removes Repository Metadata"
+msgstr ""
+
+#. Tag: para
+#: Package_Selection_Repositories-x86.xml:99
+#, no-c-format
+msgid ""
+"If you choose <guilabel>Back</guilabel> from the package selection screen, "
+"any extra repository data you may have entered is lost. This allows you to "
+"effectively cancel extra repositories. Currently there is no way to cancel "
+"only a single repository once entered."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection-x86.xml:49
+#, no-c-format
+msgid ""
+"If you choose to accept the current package list, skip ahead to <xref "
+"linkend=\"s1-preparetoinstall-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Package_Selection-x86.xml:53
+#, no-c-format
+msgid ""
+"To select a component, click on the checkbox beside it (refer to <xref "
+"linkend=\"fig-pkgselection-group-x86\"/>)."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-caution-1.xml:11
+#, no-c-format
+msgid ""
+"If there was an operating system of some type installed on that partition, "
+"it needs to be reinstalled as well. Be aware that some computers sold with "
+"pre-installed operating systems may not include the CD-ROM media to "
+"reinstall the original operating system. The best time to notice if this "
+"applies to your system is <emphasis>before</emphasis> you destroy your "
+"original partition and its operating system installation."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-10.xml:8
+#, no-c-format
+msgid ""
+"Image of a disk drive being destructively repartitioned, where "
+"<wordasword>1</wordasword> represents before and <wordasword>2</wordasword> "
+"represents after."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-1.xml:7
+#, no-c-format
+msgid "Image of an unused disk drive."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-2.xml:7
+#, no-c-format
+msgid "Image of a formatted disk drive."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-3.xml:7
+#, no-c-format
+msgid "Image of a disk drive with a different file system."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-4.xml:7
+#, no-c-format
+msgid "Image of a disk drive with data written to it."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-5.xml:7
+#, no-c-format
+msgid "Image of an unused disk drive with a partition table."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-6.xml:7
+#, no-c-format
+msgid "Image of a disk drive with a single partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-7.xml:7
+#, no-c-format
+msgid "Image of a disk drive with an extended partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-8.xml:7
+#, no-c-format
+msgid ""
+"Image of a disk drive with unpartitioned free space, where <wordasword>1</"
+"wordasword> represents an undefined partition with unallocated space and "
+"<wordasword>2</wordasword> represents a defined partition with allocated "
+"space."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-imagecap-9.xml:7
+#, no-c-format
+msgid ""
+"Image of a disk drive with an unused partition, where <wordasword>1</"
+"wordasword> represents an unused partition and <wordasword>2</wordasword> "
+"represents reallocating an unused partition for Linux."
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-10.xml:10
+#, no-c-format
+msgid "partition types"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-11.xml:10
+#, no-c-format
+msgid "types of partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-14.xml:10
+#, no-c-format
+msgid "extended"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-16.xml:10
+#, no-c-format
+msgid "making room for partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-17.xml:10
+#, no-c-format
+msgid "using free space"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-18.xml:10
+#, no-c-format
+msgid "using unused partition"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-19.xml:10
+#, no-c-format
+msgid "using in-use partition"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-2.xml:10
+#, no-c-format
+msgid "partitioning of"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-4.xml:10
+#, no-c-format
+msgid "file system formats"
+msgstr ""
+
+#. Tag: primary
+#: Partitions_common-indexterm-5.xml:9
+#, no-c-format
+msgid "file system"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-5.xml:10
+#, no-c-format
+msgid "formats, overview of"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-6.xml:10
+#, no-c-format
+msgid "partition introduction"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-7.xml:10
+#, no-c-format
+msgid "introduction to"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-indexterm-9.xml:10
+#, no-c-format
+msgid "primary partitions"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-1.xml:10
+#, no-c-format
+msgid ""
+"A small percentage of the drive's available space is used to store file "
+"system-related data and can be considered as overhead."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-1.xml:16
+#, no-c-format
+msgid ""
+"A file system splits the remaining space into small, consistently-sized "
+"segments. For Linux, these segments are known as <firstterm>blocks</"
+"firstterm>."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-1.xml:18
+#, no-c-format
+msgid ""
+"Blocks really <emphasis>are</emphasis> consistently sized, unlike our "
+"illustrations. Keep in mind, also, that an average disk drive contains "
+"thousands of blocks. But for the purposes of this discussion, please ignore "
+"these minor discrepancies."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-2.xml:10
+#, no-c-format
+msgid "The points on the disk where the partition starts and ends"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-2.xml:16
+#, no-c-format
+msgid "Whether the partition is \"active\""
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-2.xml:22
+#, no-c-format
+msgid "The partition's type"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-3.xml:10
+#, no-c-format
+msgid "Unpartitioned free space is available"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-3.xml:16
+#, no-c-format
+msgid "An unused partition is available"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-itemizedlist-3.xml:22
+#, no-c-format
+msgid "Free space in an actively used partition is available"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-note-3.xml:8
+#, no-c-format
+msgid ""
+"Keep in mind that the following illustrations are simplified in the interest "
+"of clarity and do not reflect the exact partition layout that you encounter "
+"when actually installing Fedora."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-10.xml:8
+#, no-c-format
+msgid ""
+"Each partition table entry contains several important characteristics of the "
+"partition:"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-11.xml:8
+#, no-c-format
+msgid ""
+"Let us take a closer look at each of these characteristics. The starting and "
+"ending points actually define the partition's size and location on the disk. "
+"The \"active\" flag is used by some operating systems' boot loaders. In "
+"other words, the operating system in the partition that is marked \"active\" "
+"is booted."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-12.xml:8
+#, no-c-format
+msgid ""
+"The partition's type can be a bit confusing. The type is a number that "
+"identifies the partition's anticipated usage. If that statement sounds a bit "
+"vague, that is because the meaning of the partition type is a bit vague. "
+"Some operating systems use the partition type to denote a specific file "
+"system type, to flag the partition as being associated with a particular "
+"operating system, to indicate that the partition contains a bootable "
+"operating system, or some combination of the three."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-13.xml:8
+#, no-c-format
+msgid ""
+"In many cases, there is only a single partition spanning the entire disk, "
+"essentially duplicating the method used before partitions. The partition "
+"table has only one entry used, and it points to the start of the partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-14.xml:8
+#, no-c-format
+msgid ""
+"Of course, over time it became obvious that four partitions would not be "
+"enough. As disk drives continued to grow, it became more and more likely "
+"that a person could configure four reasonably-sized partitions and still "
+"have disk space left over. There needed to be some way of creating more "
+"partitions."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-15.xml:8
+#, no-c-format
+msgid ""
+"As this figure implies, there is a difference between primary and logical "
+"partitions — there can only be four primary partitions, but there is "
+"no fixed limit to the number of logical partitions that can exist. However, "
+"due to the way in which partitions are accessed in Linux, you should avoid "
+"defining more than 12 logical partitions on a single disk drive."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-16.xml:6
+#, no-c-format
+msgid ""
+"Now that we have discussed partitions in general, let us review how to use "
+"this knowledge to install Fedora."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-17.xml:8
+#, no-c-format
+msgid ""
+"The following list presents some possible scenarios you may face when "
+"attempting to repartition your hard disk:"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-18.xml:8
+#, no-c-format
+msgid "Let us look at each scenario in order."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-19.xml:8
+#, no-c-format
+msgid ""
+"If you think about it, an unused hard disk also falls into this category. "
+"The only difference is that <emphasis>all</emphasis> the space is not part "
+"of any defined partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-20.xml:8
+#, no-c-format
+msgid "Next, we will discuss a slightly more common situation."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-21.xml:8
+#, no-c-format
+msgid ""
+"If you find yourself in this situation, you can use the space allocated to "
+"the unused partition. You first must delete the partition and then create "
+"the appropriate Linux partition(s) in its place. You can delete the unused "
+"partition and manually create new partitions during the installation process."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-22.xml:8
+#, no-c-format
+msgid ""
+"This is the most common situation. It is also, unfortunately, the hardest to "
+"handle. The main problem is that, even if you have enough free space, it is "
+"presently allocated to a partition that is already in use. If you purchased "
+"a computer with pre-installed software, the hard disk most likely has one "
+"massive partition holding the operating system and data."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-23.xml:8
+#, no-c-format
+msgid ""
+"Aside from adding a new hard drive to your system, you have two choices:"
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-24.xml:8
+#, no-c-format
+msgid ""
+"Basically, you delete the single large partition and create several smaller "
+"ones. As you might imagine, any data you had in the original partition is "
+"destroyed. This means that making a complete backup is necessary. For your "
+"own sake, make two backups, use verification (if available in your backup "
+"software), and try to read data from your backup <emphasis>before</emphasis> "
+"you delete the partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-2.xml:8
+#, no-c-format
+msgid ""
+"Hard disks perform a very simple function — they store data and "
+"reliably retrieve it on command."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-3.xml:8
+#, no-c-format
+msgid ""
+"Not much to look at, is it? But if we are talking about disk drives on a "
+"basic level, it is adequate. Say that we would like to store some data on "
+"this drive. As things stand now, it will not work. There is something we "
+"need to do first."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-4.xml:8
+#, no-c-format
+msgid ""
+"Experienced computer users probably got this one on the first try. We need "
+"to <firstterm>format</firstterm> the drive. Formatting (usually known as "
+"\"making a <firstterm>file system</firstterm>\") writes information to the "
+"drive, creating order out of the empty space in an unformatted drive."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-5.xml:8
+#, no-c-format
+msgid ""
+"Given that file systems make things like directories and files possible, "
+"these trade-offs are usually seen as a small price to pay."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-6.xml:8
+#, no-c-format
+msgid ""
+"Of course, writing a file system to disk is only the beginning. The goal of "
+"this process is to actually <emphasis>store</emphasis> and "
+"<emphasis>retrieve</emphasis> data. Let us take a look at our drive after "
+"some files have been written to it."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-7.xml:8
+#, no-c-format
+msgid ""
+"As with most computer-related technologies, disk drives changed over time "
+"after their introduction. In particular, they got bigger. Not larger in "
+"physical size, but bigger in their capacity to store information. And, this "
+"additional capacity drove a fundamental change in the way disk drives were "
+"used."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-8.xml:8
+#, no-c-format
+msgid ""
+"As disk drive capacities soared, some people began to wonder if having all "
+"of that formatted space in one big chunk was such a great idea. This line of "
+"thinking was driven by several issues, some philosophical, some technical. "
+"On the philosophical side, above a certain size, it seemed that the "
+"additional space provided by a larger drive created more clutter. On the "
+"technical side, some file systems were never designed to support anything "
+"above a certain capacity. Or the file systems <emphasis>could</emphasis> "
+"support larger drives with a greater capacity, but the overhead imposed by "
+"the file system to track files became excessive."
+msgstr ""
+
+#. Tag: para
+#: Partitions_common-para-9.xml:8
+#, no-c-format
+msgid ""
+"The solution to this problem was to divide disks into <firstterm>partitions</"
+"firstterm>. Each partition can be accessed as if it was a separate disk. "
+"This is done through the addition of a <firstterm>partition table</"
+"firstterm>."
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-table-title-1.xml:8
+#, no-c-format
+msgid "Partition Types"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions_common-term-1.xml:10
+#, no-c-format
+msgid "destructive"
+msgstr ""
+
+#. Tag: emphasis
+#: Partitions_common-term-1.xml:12
+#, no-c-format
+msgid "Destructive Repartitioning"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-10.xml:8
+#, no-c-format
+msgid "Disk Drive Being Destructively Repartitioned"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-2.xml:8
+#, no-c-format
+msgid "Hard Disk Basic Concepts"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-3.xml:8
+#, no-c-format
+msgid "It is Not What You Write, it is How You Write It"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-4.xml:8
+#, no-c-format
+msgid "Partitions: Turning One Drive Into Many"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-5.xml:8
+#, no-c-format
+msgid "Partitions within Partitions — An Overview of Extended Partitions"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-6.xml:5
+#, no-c-format
+msgid "Making Room For Fedora"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-7.xml:8
+#, no-c-format
+msgid "Using Unpartitioned Free Space"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-8.xml:8
+#, no-c-format
+msgid "Using Space from an Unused Partition"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title-9.xml:8
+#, no-c-format
+msgid "Using Free Space from an Active Partition"
+msgstr ""
+
+#. Tag: title
+#: Partitions_common-title.xml:8
+#, no-c-format
+msgid "An Introduction to Disk Partitions"
+msgstr ""
+
+#. Tag: para
+#: Partitions_complete-note-1.xml:11
+#, no-c-format
+msgid ""
+"While the diagrams in this chapter show the partition table as being "
+"separate from the actual disk drive, this is not entirely accurate. In "
+"reality, the partition table is stored at the very start of the disk, before "
+"any file system or user data. But for clarity, they are separate in our "
+"diagrams."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:21
+#, no-c-format
+msgid ""
+"If you are reasonably comfortable with disk partitions, you could skip ahead "
+"to <xref linkend=\"s2-partitions-make-room-x86\"/>, for more information on "
+"the process of freeing up disk space to prepare for a Fedora installation. "
+"This section also discusses the partition naming scheme used by Linux "
+"systems, sharing disk space with other operating systems, and related topics."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:35
+#, no-c-format
+msgid ""
+"When discussing issues such as disk partitioning, it is important to know a "
+"bit about the underlying hardware. Unfortunately, it is easy to become "
+"bogged down in details. Therefore, this appendix uses a simplified diagram "
+"of a disk drive to help explain what is really happening when a disk drive "
+"is partitioned. <xref linkend=\"fig-partitions-unused-drive-x86\"/>, shows a "
+"brand-new, unused disk drive."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:38
+#, no-c-format
+msgid "An Unused Disk Drive"
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:64
+#, no-c-format
+msgid "Disk Drive with a File System"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:73
+#, no-c-format
+msgid ""
+"As <xref linkend=\"fig-partitions-formatted-drive-x86\"/>, implies, the "
+"order imposed by a file system involves some trade-offs:"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:83
+#, no-c-format
+msgid ""
+"It is also worth noting that there is no single, universal file system. As "
+"<xref linkend=\"fig-partitions-other-formatted-d-x86\"/>, shows, a disk "
+"drive may have one of many different file systems written on it. As you "
+"might guess, different file systems tend to be incompatible; that is, an "
+"operating system that supports one file system (or a handful of related file "
+"system types) may not support another. This last statement is not a hard-and-"
+"fast rule, however. For example, Fedora supports a wide variety of file "
+"systems (including many commonly used by other operating systems), making "
+"data interchange between different file systems easy."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:86
+#, no-c-format
+msgid "Disk Drive with a Different File System"
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:99
+#, no-c-format
+msgid "Disk Drive with Data Written to It"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:108
+#, no-c-format
+msgid ""
+"As <xref linkend=\"fig-partitions-used-formatted-dr-x86\"/>, shows, some of "
+"the previously-empty blocks are now holding data. However, by just looking "
+"at this picture, we cannot determine exactly how many files reside on this "
+"drive. There may only be one file or many, as all files use at least one "
+"block and some files use multiple blocks. Another important point to note is "
+"that the used blocks do not have to form a contiguous region; used and "
+"unused blocks may be interspersed. This is known as "
+"<firstterm>fragmentation</firstterm>. Fragmentation can play a part when "
+"attempting to resize an existing partition."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:137
+#, no-c-format
+msgid "Disk Drive with Partition Table"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:152
+#, no-c-format
+msgid ""
+"As <xref linkend=\"fig-partitions-unused-partitione-x86\"/> shows, the "
+"partition table is divided into four sections or four <firstterm>primary</"
+"firstterm> partitions. A primary partition is a partition on a hard drive "
+"that can contain only one logical drive (or section). Each section can hold "
+"the information necessary to define a single partition, meaning that the "
+"partition table can define no more than four partitions."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:169
+#, no-c-format
+msgid ""
+"By this point, you might be wondering how all this additional complexity is "
+"normally used. Refer to <xref linkend=\"fig-partitions-dos-single-part-x86\"/"
+">, for an example."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:172
+#, no-c-format
+msgid "Disk Drive With Single Partition"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:185
+#, no-c-format
+msgid ""
+"We have labeled this partition as being of the \"DOS\" type. Although it is "
+"only one of several possible partition types listed in <xref linkend=\"tb-"
+"partitions-types-x86\"/>, it is adequate for the purposes of this discussion."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:189
+#, no-c-format
+msgid ""
+", contains a listing of some popular (and obscure) partition types, along "
+"with their hexadecimal numeric values."
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:212 Partitions-x86.xml:220
+#, no-c-format
+msgid "Partition Type"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:216 Partitions-x86.xml:224
+#, no-c-format
+msgid "Value"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:231
+#, no-c-format
+msgid "Empty"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:235
+#, no-c-format
+msgid "<entry>00</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:239
+#, no-c-format
+msgid "Novell Netware 386"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:243
+#, no-c-format
+msgid "<entry>65</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:249
+#, no-c-format
+msgid "DOS 12-bit FAT"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:253
+#, no-c-format
+msgid "<entry>01</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:257
+#, no-c-format
+msgid "PIC/IX"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:261
+#, no-c-format
+msgid "<entry>75</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:267
+#, no-c-format
+msgid "XENIX root"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:271
+#, no-c-format
+msgid "<entry>02</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:275
+#, no-c-format
+msgid "Old MINIX"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:279
+#, no-c-format
+msgid "<entry>80</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:285
+#, no-c-format
+msgid "XENIX usr"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:289
+#, no-c-format
+msgid "<entry>03</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:293
+#, no-c-format
+msgid "Linux/MINUX"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:297
+#, no-c-format
+msgid "<entry>81</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:303
+#, no-c-format
+msgid "DOS 16-bit <=32M"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:307
+#, no-c-format
+msgid "<entry>04</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:311
+#, no-c-format
+msgid "Linux swap"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:315
+#, no-c-format
+msgid "<entry>82</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:321
+#, no-c-format
+msgid "Extended"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:325
+#, no-c-format
+msgid "<entry>05</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:329
+#, no-c-format
+msgid "Linux native"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:333
+#, no-c-format
+msgid "<entry>83</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:339
+#, no-c-format
+msgid "DOS 16-bit >=32"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:343
+#, no-c-format
+msgid "<entry>06</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:347
+#, no-c-format
+msgid "Linux extended"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:351
+#, no-c-format
+msgid "<entry>85</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:357
+#, no-c-format
+msgid "OS/2 HPFS"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:361
+#, no-c-format
+msgid "<entry>07</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:365
+#, no-c-format
+msgid "Amoeba"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:369
+#, no-c-format
+msgid "<entry>93</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:375
+#, no-c-format
+msgid "<entry>AIX</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:379
+#, no-c-format
+msgid "<entry>08</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:383
+#, no-c-format
+msgid "Amoeba BBT"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:387
+#, no-c-format
+msgid "<entry>94</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:393
+#, no-c-format
+msgid "AIX bootable"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:397
+#, no-c-format
+msgid "<entry>09</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:401
+#, no-c-format
+msgid "BSD/386"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:405
+#, no-c-format
+msgid "<entry>a5</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:411
+#, no-c-format
+msgid "OS/2 Boot Manager"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:415
+#, no-c-format
+msgid "<entry>0a</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:419
+#, no-c-format
+msgid "OpenBSD"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:423
+#, no-c-format
+msgid "<entry>a6</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:429
+#, no-c-format
+msgid "Win95 FAT32"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:433
+#, no-c-format
+msgid "<entry>0b</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:437
+#, no-c-format
+msgid "NEXTSTEP"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:441
+#, no-c-format
+msgid "<entry>a7</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:447
+#, no-c-format
+msgid "Win95 FAT32 (LBA)"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:451
+#, no-c-format
+msgid "<entry>0c</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:455
+#, no-c-format
+msgid "BSDI fs"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:459
+#, no-c-format
+msgid "<entry>b7</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:465
+#, no-c-format
+msgid "Win95 FAT16 (LBA)"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:469
+#, no-c-format
+msgid "<entry>0e</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:473
+#, no-c-format
+msgid "BSDI swap"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:477
+#, no-c-format
+msgid "<entry>b8</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:483
+#, no-c-format
+msgid "Win95 Extended (LBA)"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:487
+#, no-c-format
+msgid "<entry>0f</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:491
+#, no-c-format
+msgid "Syrinx"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:495
+#, no-c-format
+msgid "<entry>c7</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:501
+#, no-c-format
+msgid "Venix 80286"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:505
+#, no-c-format
+msgid "<entry>40</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:509
+#, no-c-format
+msgid "CP/M"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:513
+#, no-c-format
+msgid "<entry>db</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:519
+#, no-c-format
+msgid "Novell"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:523
+#, no-c-format
+msgid "<entry>51</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:527
+#, no-c-format
+msgid "DOS access"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:531
+#, no-c-format
+msgid "<entry>e1</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:537
+#, no-c-format
+msgid "PPC PReP Boot"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:541
+#, no-c-format
+msgid "<entry>41</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:545
+#, no-c-format
+msgid "DOS R/O"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:549
+#, no-c-format
+msgid "<entry>e3</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:555
+#, no-c-format
+msgid "GNU HURD"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:559
+#, no-c-format
+msgid "<entry>63</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:563
+#, no-c-format
+msgid "DOS secondary"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:567
+#, no-c-format
+msgid "<entry>f2</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:573
+#, no-c-format
+msgid "Novell Netware 286"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:577
+#, no-c-format
+msgid "<entry>64</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:581
+#, no-c-format
+msgid "<entry>BBT</entry>"
+msgstr ""
+
+#. Tag: entry
+#: Partitions-x86.xml:585
+#, no-c-format
+msgid "<entry>ff</entry>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:621
+#, no-c-format
+msgid ""
+"Enter the extended partition. As you may have noticed in <xref linkend=\"tb-"
+"partitions-types-x86\"/>, there is an \"Extended\" partition type. It is "
+"this partition type that is at the heart of extended partitions."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:625
+#, no-c-format
+msgid ""
+"When a partition is created and its type is set to \"Extended,\" an extended "
+"partition table is created. In essence, the extended partition is like a "
+"disk drive in its own right — it has a partition table that points to "
+"one or more partitions (now called <firstterm>logical partitions</"
+"firstterm>, as opposed to the four <firstterm>primary partitions</"
+"firstterm>) contained entirely within the extended partition itself. <xref "
+"linkend=\"fig-partitions-extended-part-x86\"/>, shows a disk drive with one "
+"primary partition and one extended partition containing two logical "
+"partitions (along with some unpartitioned free space)."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:630
+#, no-c-format
+msgid "Disk Drive With Extended Partition"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:671
+#, no-c-format
+msgid ""
+"In this situation, the partitions already defined do not span the entire "
+"hard disk, leaving unallocated space that is not part of any defined "
+"partition. <xref linkend=\"fig-partitions-unpart-space-x86\"/>, shows what "
+"this might look like."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:674
+#, no-c-format
+msgid "Disk Drive with Unpartitioned Free Space"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:683
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-unpart-space-x86\"/>, <wordasword>1</"
+"wordasword> represents an undefined partition with unallocated space and "
+"<wordasword>2</wordasword> represents a defined partition with allocated "
+"space."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:690
+#, no-c-format
+msgid ""
+"In any case, you can create the necessary partitions from the unused space. "
+"Unfortunately, this scenario, although very simple, is not very likely "
+"(unless you have just purchased a new disk just for Fedora). Most pre-"
+"installed operating systems are configured to take up all available space on "
+"a disk drive (refer to <xref linkend=\"s3-partitions-active-part-x86\"/>)."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:705
+#, no-c-format
+msgid ""
+"In this case, maybe you have one or more partitions that you do not use any "
+"longer. Perhaps you have dabbled with another operating system in the past, "
+"and the partition(s) you dedicated to it never seem to be used anymore. "
+"<xref linkend=\"fig-partitions-unused-partition-x86\"/>, illustrates such a "
+"situation."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:709
+#, no-c-format
+msgid "Disk Drive With an Unused Partition"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:718
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-unused-partition-x86\"/>, <wordasword>1</"
+"wordasword> represents an unused partition and <wordasword>2</wordasword> "
+"represents reallocating an unused partition for Linux."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:750
+#, no-c-format
+msgid ""
+"After creating a smaller partition for your existing operating system, you "
+"can reinstall any software, restore your data, and start your Fedora "
+"installation. <xref linkend=\"fig-partitions-dstrct-reprt-x86\"/> shows this "
+"being done."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:763
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-dstrct-reprt-x86\"/>, <wordasword>1</"
+"wordasword> represents before and <wordasword>2</wordasword> represents "
+"after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:770
+#, no-c-format
+msgid ""
+"As <xref linkend=\"fig-partitions-dstrct-reprt-x86\"/>, shows, any data "
+"present in the original partition is lost without proper backup!"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:780
+#, no-c-format
+msgid "non-destructive"
+msgstr ""
+
+#. Tag: emphasis
+#: Partitions-x86.xml:782
+#, no-c-format
+msgid "Non-Destructive Repartitioning"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:784
+#, no-c-format
+msgid ""
+"Here, you run a program that does the seemingly impossible: it makes a big "
+"partition smaller without losing any of the files stored in that partition. "
+"Many people have found this method to be reliable and trouble-free. What "
+"software should you use to perform this feat? There are several disk "
+"management software products on the market. Do some research to find the one "
+"that is best for your situation."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:789
+#, no-c-format
+msgid ""
+"While the process of non-destructive repartitioning is rather "
+"straightforward, there are a number of steps involved:"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:795
+#, no-c-format
+msgid "Compress and backup existing data"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:801
+#, no-c-format
+msgid "<para>Resize the existing partition</para>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:807
+#, no-c-format
+msgid "<para>Create new partition(s)</para>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:816
+#, no-c-format
+msgid "Next we will look at each step in a bit more detail."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:821
+#, no-c-format
+msgid "Compress existing data"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:823
+#, no-c-format
+msgid ""
+"As <xref linkend=\"fig-partitions-compression-x86\"/>, shows, the first step "
+"is to compress the data in your existing partition. The reason for doing "
+"this is to rearrange the data such that it maximizes the available free "
+"space at the \"end\" of the partition."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:827
+#, no-c-format
+msgid "Disk Drive Being Compressed"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:830
+#, no-c-format
+msgid ""
+"Image of a disk drive being compressed, where <wordasword>1</wordasword> "
+"represents before and <wordasword>2</wordasword> represents after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:836
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-compression-x86\"/>, <wordasword>1</"
+"wordasword> represents before and <wordasword>2</wordasword> represents "
+"after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:840
+#, no-c-format
+msgid ""
+"This step is crucial. Without it, the location of your data could prevent "
+"the partition from being resized to the extent desired. Note also that, for "
+"one reason or another, some data cannot be moved. If this is the case (and "
+"it severely restricts the size of your new partition(s)), you may be forced "
+"to destructively repartition your disk."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:847
+#, no-c-format
+msgid "<title>Resize the existing partition</title>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:849
+#, no-c-format
+msgid ""
+", shows the actual resizing process. While the actual result of the resizing "
+"operation varies depending on the software used, in most cases the newly "
+"freed space is used to create an unformatted partition of the same type as "
+"the original partition."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:853
+#, no-c-format
+msgid "Disk Drive with Partition Resized"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:856
+#, no-c-format
+msgid ""
+"Image of a disk drive with a resized partition, where <wordasword>1</"
+"wordasword> represents before and <wordasword>2</wordasword> represents "
+"after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:862
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-part-resize-x86\"/>, <wordasword>1</"
+"wordasword> represents before and <wordasword>2</wordasword> represents "
+"after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:866
+#, no-c-format
+msgid ""
+"It is important to understand what the resizing software you use does with "
+"the newly freed space, so that you can take the appropriate steps. In the "
+"case we have illustrated, it would be best to delete the new DOS partition "
+"and create the appropriate Linux partition(s)."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:873
+#, no-c-format
+msgid "<title>Create new partition(s)</title>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:875
+#, no-c-format
+msgid ""
+"As the previous step implied, it may or may not be necessary to create new "
+"partitions. However, unless your resizing software is Linux-aware, it is "
+"likely that you must delete the partition that was created during the "
+"resizing process. <xref linkend=\"fig-partitions-nondestruct-fin-x86\"/>, "
+"shows this being done."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:879
+#, no-c-format
+msgid "Disk Drive with Final Partition Configuration"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:882
+#, no-c-format
+msgid ""
+"Image of a disk drive with final partition configuration, where "
+"<wordasword>1</wordasword> represents before and <wordasword>2</wordasword> "
+"represents after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:888
+#, no-c-format
+msgid ""
+"In <xref linkend=\"fig-partitions-nondestruct-fin-x86\"/>, <wordasword>1</"
+"wordasword> represents before and <wordasword>2</wordasword> represents "
+"after."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:895
+#, no-c-format
+msgid "The following information is specific to x86-based computers only."
+msgstr ""
+
+#. Tag: primary
+#: Partitions-x86.xml:900
+#, no-c-format
+msgid "parted partitioning utility"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:902
+#, no-c-format
+msgid ""
+"As a convenience to our customers, we provide the <command>parted</command> "
+"utility. This is a freely available program that can resize partitions."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:906
+#, no-c-format
+msgid ""
+"If you decide to repartition your hard drive with <command>parted</command>, "
+"it is important that you be familiar with disk storage and that you perform "
+"a backup of your computer data. You should make two copies of all the "
+"important data on your computer. These copies should be to removable media "
+"(such as tape, CD-ROM, or diskettes), and you should make sure they are "
+"readable before proceeding."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:911
+#, no-c-format
+msgid ""
+"Should you decide to use <command>parted</command>, be aware that after "
+"<command>parted</command> runs you are left with <emphasis>two</emphasis> "
+"partitions: the one you resized, and the one <command>parted</command> "
+"created out of the newly freed space. If your goal is to use that space to "
+"install Fedora, you should delete the newly created partition, either by "
+"using the partitioning utility under your current operating system or while "
+"setting up partitions during installation."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:919
+#, no-c-format
+msgid "Partition Naming Scheme"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:922
+#, no-c-format
+msgid "numbering partitions"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:926
+#, no-c-format
+msgid "naming partitions"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:928
+#, no-c-format
+msgid ""
+"Linux refers to disk partitions using a combination of letters and numbers "
+"which may be confusing, particularly if you are used to the \"C drive\" way "
+"of referring to hard disks and their partitions. In the DOS/Windows world, "
+"partitions are named using the following method:"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:935
+#, no-c-format
+msgid ""
+"Each partition's type is checked to determine if it can be read by DOS/"
+"Windows."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:941
+#, no-c-format
+msgid ""
+"If the partition's type is compatible, it is assigned a \"drive letter.\" "
+"The drive letters start with a \"C\" and move on to the following letters, "
+"depending on the number of partitions to be labeled."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:947
+#, no-c-format
+msgid ""
+"The drive letter can then be used to refer to that partition as well as the "
+"file system contained on that partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:953
+#, no-c-format
+msgid ""
+"Fedora uses a naming scheme that is more flexible and conveys more "
+"information than the approach used by other operating systems. The naming "
+"scheme is file-based, with file names in the form of <filename>/dev/"
+"<replaceable>xxyN</replaceable></filename>."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:958
+#, no-c-format
+msgid "Here is how to decipher the partition naming scheme:"
+msgstr ""
+
+#. Tag: filename
+#: Partitions-x86.xml:964
+#, no-c-format
+msgid "/dev/"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:966
+#, no-c-format
+msgid ""
+"This is the name of the directory in which all device files reside. Since "
+"partitions reside on hard disks, and hard disks are devices, the files "
+"representing all possible partitions reside in <filename>/dev/</filename>."
+msgstr ""
+
+#. Tag: replaceable
+#: Partitions-x86.xml:973
+#, no-c-format
+msgid "<replaceable>xx</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:975
+#, no-c-format
+msgid ""
+"The first two letters of the partition name indicate the type of device on "
+"which the partition resides, usually either <filename>hd</filename> (for IDE "
+"disks) or <filename>sd</filename> (for SCSI disks)."
+msgstr ""
+
+#. Tag: replaceable
+#: Partitions-x86.xml:982
+#, no-c-format
+msgid "<replaceable>y</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:984
+#, no-c-format
+msgid ""
+"This letter indicates which device the partition is on. For example, "
+"<filename>/dev/hda</filename> (the first IDE hard disk) or <filename>/dev/"
+"sdb</filename> (the second SCSI disk)."
+msgstr ""
+
+#. Tag: replaceable
+#: Partitions-x86.xml:991
+#, no-c-format
+msgid "<replaceable>N</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:993
+#, no-c-format
+msgid ""
+"The final number denotes the partition. The first four (primary or extended) "
+"partitions are numbered <filename>1</filename> through <filename>4</"
+"filename>. Logical partitions start at <filename>5</filename>. So, for "
+"example, <filename>/dev/hda3</filename> is the third primary or extended "
+"partition on the first IDE hard disk, and <filename>/dev/sdb6</filename> is "
+"the second logical partition on the second SCSI hard disk."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1005
+#, no-c-format
+msgid ""
+"There is no part of this naming convention that is based on partition type; "
+"unlike DOS/Windows, <emphasis>all</emphasis> partitions can be identified "
+"under Fedora. Of course, this does not mean that Fedora can access data on "
+"every type of partition, but in many cases it is possible to access data on "
+"a partition dedicated to another operating system."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1010
+#, no-c-format
+msgid ""
+"Keep this information in mind; it makes things easier to understand when you "
+"are setting up the partitions Fedora requires."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:1016
+#, no-c-format
+msgid "Disk Partitions and Other Operating Systems"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:1019
+#, no-c-format
+msgid "other operating systems"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1021
+#, no-c-format
+msgid ""
+"If your Fedora partitions are sharing a hard disk with partitions used by "
+"other operating systems, most of the time you will have no problems. "
+"However, there are certain combinations of Linux and other operating systems "
+"that require extra care."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:1028
+#, no-c-format
+msgid "Disk Partitions and Mount Points"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:1031
+#, no-c-format
+msgid "mount points and"
+msgstr ""
+
+#. Tag: primary
+#: Partitions-x86.xml:1034
+#, no-c-format
+msgid "mount points"
+msgstr ""
+
+#. Tag: secondary
+#: Partitions-x86.xml:1035
+#, no-c-format
+msgid "partitions and"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1037
+#, no-c-format
+msgid ""
+"One area that many people new to Linux find confusing is the matter of how "
+"partitions are used and accessed by the Linux operating system. In DOS/"
+"Windows, it is relatively simple: Each partition gets a \"drive letter.\" "
+"You then use the correct drive letter to refer to files and directories on "
+"its corresponding partition."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1042
+#, no-c-format
+msgid ""
+"This is entirely different from how Linux deals with partitions and, for "
+"that matter, with disk storage in general. The main difference is that each "
+"partition is used to form part of the storage necessary to support a single "
+"set of files and directories. This is done by associating a partition with a "
+"directory through a process known as <firstterm>mounting</firstterm>. "
+"Mounting a partition makes its storage available starting at the specified "
+"directory (known as a <firstterm>mount point</firstterm>)."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1048
+#, no-c-format
+msgid ""
+"For example, if partition <filename>/dev/hda5</filename> is mounted on "
+"<filename>/usr/</filename>, that would mean that all files and directories "
+"under <filename>/usr/</filename> physically reside on <filename>/dev/hda5</"
+"filename>. So the file <filename>/usr/share/doc/FAQ/txt/Linux-FAQ</filename> "
+"would be stored on <filename>/dev/hda5</filename>, while the file <filename>/"
+"etc/gdm/custom.conf</filename> would not."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1054
+#, no-c-format
+msgid ""
+"Continuing our example, it is also possible that one or more directories "
+"below <filename>/usr/</filename> would be mount points for other partitions. "
+"For instance, a partition (say, <filename>/dev/hda7</filename>) could be "
+"mounted on <filename>/usr/local/</filename>, meaning that <filename>/usr/"
+"local/man/whatis</filename> would then reside on <filename>/dev/hda7</"
+"filename> rather than <filename>/dev/hda5</filename>."
+msgstr ""
+
+#. Tag: title
+#: Partitions-x86.xml:1062
+#, no-c-format
+msgid "How Many Partitions?"
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1067
+#, no-c-format
+msgid ""
+"At this point in the process of preparing to install Fedora, you must give "
+"some consideration to the number and size of the partitions to be used by "
+"your new operating system. The question of \"how many partitions\" continues "
+"to spark debate within the Linux community and, without any end to the "
+"debate in sight, it is safe to say that there are probably as many partition "
+"layouts as there are people debating the issue."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1071
+#, no-c-format
+msgid ""
+"Keeping this in mind, we recommend that, unless you have a reason for doing "
+"otherwise, you should at least create the following partitions: "
+"<filename>swap</filename>, <filename>/boot/</filename> (or a <filename>/boot/"
+"efi/</filename> partition for Itanium systems), a <filename>/var/</filename> "
+"partition for Itanium systems, and <filename>/</filename> (root)."
+msgstr ""
+
+#. Tag: para
+#: Partitions-x86.xml:1075
+#, no-c-format
+msgid ""
+"For more information, refer to <xref linkend=\"s2-diskpartrecommend-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Preface.xml:6
+#, no-c-format
+msgid "Preface"
+msgstr ""
+
+#. Tag: title
+#: Prepare_To_Install_common.xml:6
+#, no-c-format
+msgid "Prepare to Install"
+msgstr ""
+
+#. Tag: para
+#: Prepare_To_Install_common.xml:9
+#, no-c-format
+msgid "A screen preparing you for the installation of Fedora now appears."
+msgstr ""
+
+#. Tag: para
+#: Prepare_To_Install_common.xml:13
+#, no-c-format
+msgid ""
+"For your reference, a complete log of your installation can be found in "
+"<filename>/root/install.log</filename> once you reboot your system."
+msgstr ""
+
+#. Tag: primary
+#: Prepare_To_Install_common.xml:17
+#, no-c-format
+msgid "install log file"
+msgstr ""
+
+#. Tag: filename
+#: Prepare_To_Install_common.xml:18 Prepare_To_Install_common.xml:22
+#, no-c-format
+msgid "/root/install.log"
+msgstr ""
+
+#. Tag: secondary
+#: Prepare_To_Install_common.xml:24
+#, no-c-format
+msgid "install log file location"
+msgstr ""
+
+#. Tag: para
+#: Prepare_To_Install_common.xml:28
+#, no-c-format
+msgid ""
+"To cancel this installation process, press your computer's Reset button or "
+"use the <keycombo><keycap>Control</keycap><keycap>Alt</"
+"keycap><keycap>Delete</keycap></keycombo> key combination to restart your "
+"machine."
+msgstr ""
+
+#. Tag: title
+#: Prepare_To_Install_common-title-1.xml:8
+#, no-c-format
+msgid "Preparing to Install"
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:6
+#, no-c-format
+msgid "Manually configure a PXE server"
+msgstr ""
+
+#. Tag: primary
+#: pxe-server-manual.xml:8 pxe-server-manual.xml:54 pxe-server-manual.xml:64
+#: pxe-server-manual.xml:266 pxe-server-manual.xml:398
+#: pxe-server-manual.xml:408
+#, no-c-format
+msgid "PXE installations"
+msgstr ""
+
+#. Tag: secondary
+#: pxe-server-manual.xml:9
+#, no-c-format
+msgid "overview"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:11
+#, no-c-format
+msgid ""
+"The following steps must be performed to prepare for a PXE installation:"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:16
+#, no-c-format
+msgid ""
+"Configure the network (NFS, FTP, HTTP) server to export the installation "
+"tree."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:22
+#, no-c-format
+msgid ""
+"Configure the files on the <command>tftp</command> server necessary for PXE "
+"booting."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:28
+#, no-c-format
+msgid "Configure which hosts are allowed to boot from the PXE configuration."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:34
+#, no-c-format
+msgid "Start the <command>tftp</command> service."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:40
+#, no-c-format
+msgid "Configure DHCP."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:46
+#, no-c-format
+msgid "Boot the client, and start the installation."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:52
+#, no-c-format
+msgid "Setting up the Network Server"
+msgstr ""
+
+#. Tag: secondary
+#: pxe-server-manual.xml:55
+#, no-c-format
+msgid "setting up the network server"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:57
+#, no-c-format
+msgid ""
+"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 <xref linkend=\"s1-steps-network-installs-x86\"/> for detailed "
+"instructions."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:62
+#, no-c-format
+msgid "PXE Boot Configuration"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:67
+#, no-c-format
+msgid ""
+"The next step is to copy the files necessary to start the installation to "
+"the <command>tftp</command> server so they can be found when the client "
+"requests them. The <command>tftp</command> server is usually the same server "
+"as the network server exporting the installation tree."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:72
+#, no-c-format
+msgid ""
+"To copy these files, run the <application>Network Booting Tool</application> "
+"on the NFS, FTP, or HTTP server. A separate PXE server is not necessary."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:264
+#, no-c-format
+msgid "Adding PXE Hosts"
+msgstr ""
+
+#. Tag: secondary
+#: pxe-server-manual.xml:267
+#, no-c-format
+msgid "adding hosts"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:269
+#, no-c-format
+msgid ""
+"After configuring the network server, the interface as shown in <xref "
+"linkend=\"fig-netboot-add-hosts\"/> is displayed."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:272
+#, no-c-format
+msgid "<title>Add Hosts</title>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:275
+#, no-c-format
+msgid "<para>Add Hosts</para>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:281
+#, no-c-format
+msgid ""
+"The next step is to configure which hosts are allowed to connect to the PXE "
+"boot server."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:285
+#, no-c-format
+msgid "To add hosts, click the <guibutton>New</guibutton> button."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:288
+#, no-c-format
+msgid "<title>Add a Host</title>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:291
+#, no-c-format
+msgid "<para>Add a Host</para>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:297
+#, no-c-format
+msgid "Enter the following information:"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:303
+#, no-c-format
+msgid ""
+"<guilabel>Hostname or IP Address/Subnet</guilabel> — The IP address, "
+"fully qualified hostname, or a subnet of systems that should be allowed to "
+"connect to the PXE server for installations."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:309
+#, no-c-format
+msgid ""
+"<guilabel>Operating System</guilabel> — The operating system "
+"identifier to install on this client. The list is populated from the network "
+"install instances created from the <guilabel>Network Installation Dialog</"
+"guilabel>."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:316
+#, no-c-format
+msgid ""
+"<guilabel>Serial Console</guilabel> — This option allows use of a "
+"serial console."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:322
+#, no-c-format
+msgid ""
+"<guilabel>Kickstart File</guilabel> — The location of a kickstart file "
+"to use, such as <userinput>http://server.example.com/kickstart/ks.cfg</"
+"userinput>. This file can be created with the <application>Kickstart "
+"Configurator</application>. Refer to <xref linkend=\"ch-redhat-config-"
+"kickstart\"/> for details."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:329
+#, no-c-format
+msgid ""
+"Ignore the <guilabel>Snapshot name</guilabel> and <guilabel>Ethernet</"
+"guilabel> options. They are only used for diskless environments."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:391
+#, no-c-format
+msgid "TFTPD"
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:396
+#, no-c-format
+msgid "Adding a Custom Boot Message"
+msgstr ""
+
+#. Tag: secondary
+#: pxe-server-manual.xml:399
+#, no-c-format
+msgid "boot message, custom"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:401
+#, no-c-format
+msgid ""
+"Optionally, modify <filename>/tftpboot/linux-install/msgs/boot.msg</"
+"filename> to use a custom boot message."
+msgstr ""
+
+#. Tag: title
+#: pxe-server-manual.xml:406
+#, no-c-format
+msgid "Performing the PXE Installation"
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:411
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-manual.xml:415
+#, no-c-format
+msgid ""
+"After the system boots the installation program, refer to the <xref linkend="
+"\"ch-guimode-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-para-1.xml:5
+#, no-c-format
+msgid ""
+"Fedora allows for installation over a network using the NFS, FTP, or HTTP "
+"protocols. A network installation can be started from a boot CD-ROM, a "
+"bootable flash memory drive, or by using the <command>askmethod</command> "
+"boot option with the Fedora CD #1 or DVD. Alternatively, if the system to be "
+"installed contains a network interface card (NIC) with Pre-Execution "
+"Environment (PXE) support, it can be configured to boot from files on "
+"another networked system rather than local media such as a CD-ROM."
+msgstr ""
+
+#. Tag: para
+#: pxe-server-para-2.xml:5
+#, no-c-format
+msgid ""
+"For a PXE network installation, the client's NIC with PXE support sends out "
+"a broadcast request for DHCP information. The DHCP server provides the "
+"client with an IP address, other network information such as name server, "
+"the IP address or hostname of the <command>tftp</command> server (which "
+"provides the files necessary to start the installation program), and the "
+"location of the files on the <command>tftp</command> server. This is "
+"possible because of PXELINUX, which is part of the <filename>syslinux</"
+"filename> package."
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:7
+#, no-c-format
+msgid "Setting Up an Installation Server"
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:9
+#, no-c-format
+msgid "Experience Required"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:10
+#, no-c-format
+msgid ""
+"This appendix is intended for users with previous Linux experience. If you "
+"are a new user, you may want to install using minimal boot media or the "
+"distribution DVD instead."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:16
+#, no-c-format
+msgid ""
+"The instructions in this appendix configures an automated install server. "
+"The default configuration includes destruction of all existing data on all "
+"disks for hosts that install using this method. This is often different from "
+"other network install server configurations which may provide for an "
+"interactive installation experience."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:30
+#, no-c-format
+msgid ""
+"In the past, administrators needed to perform a great deal of manual "
+"configuration to produce an installation server. However, if you have a Red "
+"Hat Enterprise Linux, CentOS, or Fedora server on your local network, you "
+"can use <package>cobbler</package> to perform these tasks. To configure a "
+"PXE server manually, see <xref linkend=\"sn-pxe-server-manual\"/>."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:35
+#, no-c-format
+msgid ""
+"To perform the tasks in this section, switch to the <systemitem class="
+"\"username\">root</systemitem> account with the command <command>su -</"
+"command>. As an alternative, you can run a command with the <option>-c</"
+"option> option, using the form <command>su -c '<replaceable>command</"
+"replaceable>'</command>."
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:42
+#, no-c-format
+msgid "Setting Up <package>cobbler</package>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:43
+#, no-c-format
+msgid "To install <package>cobbler</package> use the following command:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:45
+#, no-c-format
+msgid "<command><![CDATA[yum -y install cobbler]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:46
+#, no-c-format
+msgid ""
+"The <command>cobbler</command> command can check its own settings for "
+"validity and report the results. Run the following command to check the "
+"settings:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:49
+#, no-c-format
+msgid "<command><![CDATA[cobbler check]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:50
+#, no-c-format
+msgid ""
+"Change the settings in the <filename>/var/lib/cobbler/settings</filename> "
+"file to reflect the IP address information for the server. You must change "
+"at least the <option>server</option> and <option>next_server</option> "
+"options, although these options may point to the same IP address."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:56
+#, no-c-format
+msgid ""
+"If you are not already running a DHCP server, you should also change the "
+"<option>manage_dhcp</option> option to <userinput>1</userinput>. If you are "
+"running a DHCP server, configure it according to the instructions found in "
+"the <package>syslinux</package> package documentation. For more information, "
+"refer to your local files <filename>/usr/share/doc/syslinux-"
+"<replaceable>version</replaceable>/syslinux.doc</filename> and <filename>/"
+"usr/share/doc/syslinux-<replaceable>version</replaceable>/pxelinux.doc</"
+"filename>."
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:67
+#, no-c-format
+msgid "Setting Up the Distribution"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:68
+#, no-c-format
+msgid ""
+"To set up a distribution from a full Fedora DVD or ISO image, use this "
+"procedure."
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:71
+#, no-c-format
+msgid "Network Locations"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:72
+#, no-c-format
+msgid ""
+"To create a local mirror from an existing network source, skip this section "
+"and refer instead to <xref linkend=\"sn-cobbler-mirror\"/>."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:78
+#, no-c-format
+msgid ""
+"If you are using a DVD disc or ISO image, Create a directory mount point:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:80
+#, no-c-format
+msgid "<command><![CDATA[mkdir /mnt/dvd]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:81
+#, no-c-format
+msgid "To mount a physical DVD disc, use the following command:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:83
+#, no-c-format
+msgid ""
+"<command><![CDATA[mount -o context=system_u:object_r:httpd_sys_content_t:s0 /"
+"dev/dvd /mnt/dvd]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:84
+#, no-c-format
+msgid "To mount a DVD ISO image, use the following command:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:86
+#, no-c-format
+msgid ""
+"<command><![CDATA[mount -ro loop,context=system_u:object_r:"
+"httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:89
+#, no-c-format
+msgid ""
+"To support NFS installation, create a file <filename>/etc/exports</filename> "
+"and add the following line to it:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:92
+#, no-c-format
+msgid "<![CDATA[/mnt/dvd *(ro,async)]]>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:93
+#, no-c-format
+msgid "Start the NFS server using the following commands:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:94
+#, no-c-format
+msgid ""
+"<command><![CDATA[/sbin/service rpcbind start\n"
+"/sbin/service nfs start]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:97
+#, no-c-format
+msgid ""
+"To support HTTP installation, use <command>yum</command> to install the "
+"Apache web server if it is not already installed:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:100
+#, no-c-format
+msgid "<command><![CDATA[yum -y install httpd]]></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:101
+#, no-c-format
+msgid "Make a link to the mounted disc in the Apache public content area:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:103
+#, no-c-format
+msgid ""
+"<command>ln -s /mnt/dvd /var/www/html/<replaceable>distro</replaceable></"
+"command>"
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:108
+#, no-c-format
+msgid "Mirroring a Network Location"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:109
+#, no-c-format
+msgid ""
+"If you do not have discs or ISO images for a distribution, you can use "
+"<command>cobbler</command> to create an installation server. The "
+"<command>cobbler</command> command can fetch the distribution over the "
+"network as part of the import process."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:114
+#, no-c-format
+msgid ""
+"Locate the distribution on the network. The location may be on the local "
+"network or reached at a remote site via FTP, HTTP, or rsync protocols. Note "
+"the URI, which will be in one of the following forms:"
+msgstr ""
+
+#. Tag: uri
+#: pxe-server.xml:120
+#, no-c-format
+msgid ""
+"http://mirror.example.com/pub/fedora/linux/releases/11/Fedora/"
+"<replaceable>arch</replaceable>/os"
+msgstr ""
+
+#. Tag: uri
+#: pxe-server.xml:123
+#, no-c-format
+msgid ""
+"ftp://mirror.example.com/pub/fedora/linux/releases/11/Fedora/"
+"<replaceable>arch</replaceable>/os"
+msgstr ""
+
+#. Tag: uri
+#: pxe-server.xml:126
+#, no-c-format
+msgid ""
+"rsync://mirror.example.com/fedora/linux/releases/11/Fedora/"
+"<replaceable>arch</replaceable>/os"
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:131
+#, no-c-format
+msgid "Importing the Distribution"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:132
+#, no-c-format
+msgid ""
+"To offer a distribution through more than one installation method, perform "
+"additional <command>cobbler import</command> tasks using a different name "
+"for each method. For best results, use the installation method as part of "
+"the name, so it appears in the client's boot menu."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:139
+#, no-c-format
+msgid ""
+"To import the DVD disc or ISO distribution into <command>cobbler</command>, "
+"run this command:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:141
+#, no-c-format
+msgid ""
+"<command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</"
+"replaceable></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:142
+#, no-c-format
+msgid ""
+"For <replaceable>distro_name</replaceable>, substitute a meaningful name for "
+"the distribution."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:144
+#, no-c-format
+msgid ""
+"To import a local or remote network distribution into <command>cobbler</"
+"command>, run this command. Replace <replaceable>network_URI</replaceable> "
+"with the URI you found in <xref linkend=\"sn-cobbler-mirror\"/>, and "
+"<replaceable>distro_name</replaceable> as above:"
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:149
+#, no-c-format
+msgid ""
+"<command>cobbler import --mirror=<replaceable>network_URI</replaceable> --"
+"name=<replaceable>distro_name</replaceable></command>"
+msgstr ""
+
+#. Tag: title
+#: pxe-server.xml:151
+#, no-c-format
+msgid "Importing a Source"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:152
+#, no-c-format
+msgid ""
+"When <command>cobbler</command> imports a distribution with the commands "
+"above, it copies all the files to the server's local storage, which may take "
+"some time."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:156
+#, no-c-format
+msgid ""
+"If you do not want to make local copies of the distribution because clients "
+"can already reach its location, use the <option>--available-as</option> "
+"option."
+msgstr ""
+
+#. Tag: screen
+#: pxe-server.xml:159
+#, no-c-format
+msgid ""
+"<command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</"
+"replaceable> --available-as=<replaceable>network_URI</replaceable></"
+"command>\n"
+"<command>cobbler import --mirror=<replaceable>network_URI</replaceable> --"
+"name=<replaceable>distro_name</replaceable> --available-"
+"as=<replaceable>network_URI</replaceable></command>"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:160
+#, no-c-format
+msgid ""
+"For <replaceable>nework_URI</replaceable>, 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 <command>cobbler</command> server reaches the mirror location at "
+"the same URI as the clients. If not, substitute an appropriate URI for the "
+"<option>--mirror</option> 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 <systemitem class=\"ipaddress\">192.168.1.1</"
+"systemitem>:"
+msgstr ""
+
+#. Tag: uri
+#: pxe-server.xml:173
+#, no-c-format
+msgid "nfs://<replaceable>192.168.1.1</replaceable>:/mnt/dvd"
+msgstr ""
+
+#. Tag: uri
+#: pxe-server.xml:176
+#, no-c-format
+msgid "http://<replaceable>192.168.1.1</replaceable>:/distro"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:179
+#, no-c-format
+msgid ""
+"If necessary, replace <replaceable>192.168.1.1</replaceable> with the IP "
+"address for your <command>cobbler</command> server."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:184
+#, no-c-format
+msgid ""
+"Run the command <command>cobbler sync</command> to apply the changes. To "
+"check that your <command>cobbler</command> server is listening on the "
+"correct ports, use the <command>netstat -lp</command> command."
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:190
+#, no-c-format
+msgid ""
+"Depending on your server's configuration, you may need to use the "
+"<command>system-config-securitylevel</command> command to permit access to "
+"some or all of these network services:"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:196
+#, no-c-format
+msgid "67 or bootps, for the DHCP/BOOTP server"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:199
+#, no-c-format
+msgid "69 or tftp, for providing the PXE loader"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:202
+#, no-c-format
+msgid ""
+"80 or http, if the <command>cobbler</command> server is to provide HTTP "
+"installation service"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:206
+#, no-c-format
+msgid ""
+"20 and 21 or ftp, if the <command>cobbler</command> server is to provide FTP "
+"installation service"
+msgstr ""
+
+#. Tag: para
+#: pxe-server.xml:210
+#, no-c-format
+msgid ""
+"111 or sunrpc, if the <command>cobbler</command> server is to provide NFS "
+"installation service"
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:5
+#, no-c-format
+msgid "Basic System Recovery"
+msgstr ""
+
+#. Tag: primary
+#: Rescue_Mode.xml:7 Rescue_Mode.xml:17 Rescue_Mode.xml:47 Rescue_Mode.xml:72
+#: Rescue_Mode.xml:85 Rescue_Mode.xml:260
+#, no-c-format
+msgid "system recovery"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:10
+#, no-c-format
+msgid ""
+"When things go wrong, there are ways to fix problems. However, these methods "
+"require that you understand the system well. This chapter describes how to "
+"boot into rescue mode, single-user mode, and emergency mode, where you can "
+"use your own knowledge to repair the system."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:15
+#, no-c-format
+msgid "Common Problems"
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:18 Rescue_Mode.xml:48 Rescue_Mode.xml:73 Rescue_Mode.xml:86
+#: Rescue_Mode.xml:261
+#, no-c-format
+msgid "common problems"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:20
+#, no-c-format
+msgid ""
+"You might need to boot into one of these recovery modes for any of the "
+"following reasons:"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:26
+#, no-c-format
+msgid "You are unable to boot normally into Fedora (runlevel 3 or 5)."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:32
+#, no-c-format
+msgid ""
+"You are having hardware or software problems, and you want to get a few "
+"important files off of your system's hard drive."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:38
+#, no-c-format
+msgid "You forgot the root password."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:45
+#, no-c-format
+msgid "Unable to Boot into Fedora"
+msgstr ""
+
+#. Tag: tertiary
+#: Rescue_Mode.xml:49
+#, no-c-format
+msgid "unable to boot into Fedora"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:54
+#, no-c-format
+msgid ""
+"This problem is often caused by the installation of another operating system "
+"after you have installed Fedora. Some other operating systems assume that "
+"you have no other operating system(s) on your computer. They overwrite the "
+"Master Boot Record (MBR) that originally contained the GRUB boot loader. If "
+"the boot loader is overwritten in this manner, you cannot boot Fedora unless "
+"you can get into rescue mode and reconfigure the boot loader."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:59
+#, no-c-format
+msgid ""
+"Another common problem occurs when using a partitioning tool to resize a "
+"partition or create a new partition from free space after installation, and "
+"it changes the order of your partitions. If the partition number of your "
+"<filename>/</filename> partition changes, the boot loader might not be able "
+"to find it to mount the partition. To fix this problem, boot in rescue mode "
+"and modify the <filename>/boot/grub/grub.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:64
+#, no-c-format
+msgid ""
+"For instructions on how to reinstall the GRUB boot loader from a rescue "
+"environment, refer to <xref linkend=\"s2-rescuemode-boot-reinstall-bootloader"
+"\"/>."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:70
+#, no-c-format
+msgid "Hardware/Software Problems"
+msgstr ""
+
+#. Tag: tertiary
+#: Rescue_Mode.xml:74
+#, no-c-format
+msgid "hardware/software problems"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:76
+#, no-c-format
+msgid ""
+"This category includes a wide variety of different situations. Two examples "
+"include failing hard drives and specifying an invalid root device or kernel "
+"in the boot loader configuration file. If either of these occur, you might "
+"not be able to reboot into Fedora. However, if you boot into one of the "
+"system recovery modes, you might be able to resolve the problem or at least "
+"get copies of your most important files."
+msgstr ""
+
+#. Tag: tertiary
+#: Rescue_Mode.xml:87
+#, no-c-format
+msgid "forgetting the root password"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:89
+#, no-c-format
+msgid ""
+"What can you do if you forget your root password? To reset it to a different "
+"password, boot into rescue mode or single-user mode, and use the "
+"<command>passwd</command> command to reset the root password."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:95
+#, no-c-format
+msgid "Booting into Rescue Mode"
+msgstr ""
+
+#. Tag: primary
+#: Rescue_Mode.xml:97 Rescue_Mode.xml:210
+#, no-c-format
+msgid "<primary>rescue mode</primary>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:100
+#, no-c-format
+msgid ""
+"Rescue mode provides the ability to boot a small Fedora environment entirely "
+"from CD-ROM, or some other boot method, instead of the system's hard drive."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:104
+#, no-c-format
+msgid ""
+"As the name implies, rescue mode is provided to rescue you from something. "
+"During normal operation, your Fedora system uses files located on your "
+"system's hard drive to do everything — run programs, store your files, "
+"and more."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:108
+#, no-c-format
+msgid ""
+"However, there may be times when you are unable to get Fedora running "
+"completely enough to access files on your system's hard drive. Using rescue "
+"mode, you can access the files stored on your system's hard drive, even if "
+"you cannot actually run Fedora from that hard drive."
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:114
+#, no-c-format
+msgid "<secondary>rescue mode</secondary>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:116
+#, no-c-format
+msgid ""
+"To boot into rescue mode, you must be able to boot the system using one of "
+"the following methods<footnote id=\"boot-media\"> <para> Refer to the "
+"earlier sections of this guide for more details. </para> </footnote>:"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:126
+#, no-c-format
+msgid "By booting the system from an installation boot CD-ROM or DVD."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:132
+#, no-c-format
+msgid ""
+"By booting the system from other installation boot media, such as USB flash "
+"devices."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:138
+#, no-c-format
+msgid "By booting the system from the Fedora CD-ROM #1 or DVD."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:144
+#, no-c-format
+msgid ""
+"Once you have booted using one of the described methods, add the keyword "
+"<userinput>rescue</userinput> as a kernel parameter. For example, for an x86 "
+"system, type the following command at the installation boot prompt:"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:147
+#, no-c-format
+msgid "<userinput>linux rescue</userinput>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:148
+#, no-c-format
+msgid ""
+"You are prompted to answer a few basic questions, including which language "
+"to use. It also prompts you to select where a valid rescue image is located. "
+"Select from <guilabel>Local CD-ROM</guilabel>, <guilabel>Hard Drive</"
+"guilabel>, <guilabel>NFS image</guilabel>, <guilabel>FTP</guilabel>, or "
+"<guilabel>HTTP</guilabel>. The location selected must contain a valid "
+"installation tree, and the installation tree must be for the same version of "
+"Fedora as the Fedora disk from which you booted. If you used a boot CD-ROM "
+"or other media to start rescue mode, the installation tree must be from the "
+"same tree from which the media was created. For more information about how "
+"to setup an installation tree on a hard drive, NFS server, FTP server, or "
+"HTTP server, refer to the earlier section of this guide."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:154
+#, no-c-format
+msgid ""
+"If you select a rescue image that does not require a network connection, you "
+"are asked whether or not you want to establish a network connection. A "
+"network connection is useful if you need to backup files to a different "
+"computer or install some RPM packages from a shared network location, for "
+"example."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:159
+#, no-c-format
+msgid "The following message is displayed:"
+msgstr ""
+
+#. Tag: computeroutput
+#: Rescue_Mode.xml:162
+#, no-c-format
+msgid ""
+"The rescue environment will now attempt to find your Linux installation and "
+"mount it under the directory /mnt/sysimage. You can then make any changes "
+"required to your system. If you want to proceed with this step choose "
+"'Continue'. You can also choose to mount your file systems read-only instead "
+"of read-write by choosing 'Read-only'. If for some reason this process fails "
+"you can choose 'Skip' and this step will be skipped and you will go directly "
+"to a command shell."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:164
+#, no-c-format
+msgid ""
+"If you select <guibutton>Continue</guibutton>, it attempts to mount your "
+"file system under the directory <filename>/mnt/sysimage/</filename>. If it "
+"fails to mount a partition, it notifies you. If you select <guibutton>Read-"
+"Only</guibutton>, it attempts to mount your file system under the directory "
+"<filename>/mnt/sysimage/</filename>, but in read-only mode. If you select "
+"<guibutton>Skip</guibutton>, your file system is not mounted. Choose "
+"<guibutton>Skip</guibutton> if you think your file system is corrupted."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:170
+#, no-c-format
+msgid ""
+"Once you have your system in rescue mode, a prompt appears on VC (virtual "
+"console) 1 and VC 2 (use the <keycap>Ctrl</keycap>-<keycap>Alt</keycap>-"
+"<keycap>F1</keycap> key combination to access VC 1 and <keycap>Ctrl</keycap>-"
+"<keycap>Alt</keycap>-<keycap>F2</keycap> to access VC 2):"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:174
+#, no-c-format
+msgid "<prompt>sh-3.00b#</prompt>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:175
+#, no-c-format
+msgid ""
+"If you selected <guibutton>Continue</guibutton> to mount your partitions "
+"automatically and they were mounted successfully, you are in single-user "
+"mode."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:179
+#, no-c-format
+msgid ""
+"Even if your file system is mounted, the default root partition while in "
+"rescue mode is a temporary root partition, not the root partition of the "
+"file system used during normal user mode (runlevel 3 or 5). If you selected "
+"to mount your file system and it mounted successfully, you can change the "
+"root partition of the rescue mode environment to the root partition of your "
+"file system by executing the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:183
+#, no-c-format
+msgid "<command>chroot /mnt/sysimage</command>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:184
+#, no-c-format
+msgid ""
+"This is useful if you need to run commands such as <command>rpm</command> "
+"that require your root partition to be mounted as <filename>/</filename>. To "
+"exit the <command>chroot</command> environment, type <command>exit</command> "
+"to return to the prompt."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:189
+#, no-c-format
+msgid ""
+"If you selected <guibutton>Skip</guibutton>, you can still try to mount a "
+"partition or LVM2 logical volume manually inside rescue mode by creating a "
+"directory such as <filename><replaceable>/foo</replaceable></filename>, and "
+"typing the following command:"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:193
+#, no-c-format
+msgid ""
+"<command>mount -t ext4 <replaceable>/dev/mapper/VolGroup00-LogVol02 /foo</"
+"replaceable></command>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:194
+#, no-c-format
+msgid ""
+"In the above command, <filename><replaceable>/foo</replaceable></filename> "
+"is a directory that you have created and <command><replaceable>/dev/mapper/"
+"VolGroup00-LogVol02</replaceable></command> is the LVM2 logical volume you "
+"want to mount. If the partition is of type <command>ext2</command> or "
+"<command>ext3</command> replace <command>ext4</command> with <command>ext2</"
+"command> or <command>ext3</command> respectively."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:199
+#, no-c-format
+msgid ""
+"If you do not know the names of all physical partitions, use the following "
+"command to list them:"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:202
+#, no-c-format
+msgid "<command>fdisk -l</command>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:203
+#, no-c-format
+msgid ""
+"If you do not know the names of all LVM2 physical volumes, volume groups, or "
+"logical volumes, use the following commands to list them:"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:206
+#, no-c-format
+msgid "<command>pvdisplay</command>"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:207
+#, no-c-format
+msgid "<command>vgdisplay</command>"
+msgstr ""
+
+#. Tag: screen
+#: Rescue_Mode.xml:208
+#, no-c-format
+msgid "<command>lvdisplay</command>"
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:211
+#, no-c-format
+msgid "utilities available"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:213
+#, no-c-format
+msgid "From the prompt, you can run many useful commands, such as:"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:219
+#, no-c-format
+msgid ""
+"<command>ssh</command>, <command>scp</command>, and <command>ping</command> "
+"if the network is started"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:225
+#, no-c-format
+msgid ""
+"<command>dump</command> and <command>restore</command> for users with tape "
+"drives"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:231
+#, no-c-format
+msgid ""
+"<command>parted</command> and <command>fdisk</command> for managing "
+"partitions"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:237
+#, no-c-format
+msgid "<command>rpm</command> for installing or upgrading software"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:243
+#, no-c-format
+msgid "<command>joe</command> for editing configuration files"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:250
+#, no-c-format
+msgid ""
+"If you try to start other popular editors such as <command>emacs</command>, "
+"<command>pico</command>, or <command>vi</command>, the <command>joe</"
+"command> editor is started."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:258
+#, no-c-format
+msgid "Reinstalling the Boot Loader"
+msgstr ""
+
+#. Tag: tertiary
+#: Rescue_Mode.xml:262
+#, no-c-format
+msgid "reinstalling the boot loader"
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:266
+#, no-c-format
+msgid "reinstalling"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:268
+#, no-c-format
+msgid ""
+"In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or "
+"replaced by other operating systems."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:272
+#, no-c-format
+msgid ""
+"The following steps detail the process on how GRUB is reinstalled on the "
+"master boot record:"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:278
+#, no-c-format
+msgid "Boot the system from an installation boot medium."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:284
+#, no-c-format
+msgid ""
+"Type <command>linux rescue</command> at the installation boot prompt to "
+"enter the rescue environment."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:290
+#, no-c-format
+msgid ""
+"Type <command>chroot /mnt/sysimage</command> to mount the root partition."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:296
+#, no-c-format
+msgid ""
+"Type <command>/sbin/grub-install /dev/hda</command> to reinstall the GRUB "
+"boot loader, where <command>/dev/hda</command> is the boot partition."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:302
+#, no-c-format
+msgid ""
+"Review the <filename>/boot/grub/grub.conf</filename> file, as additional "
+"entries may be needed for GRUB to control additional operating systems."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:308
+#, no-c-format
+msgid "Reboot the system."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:316
+#, no-c-format
+msgid "Booting into Single-User Mode"
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:319
+#, no-c-format
+msgid "<secondary>single-user mode</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: Rescue_Mode.xml:322
+#, no-c-format
+msgid "<primary>single-user mode</primary>"
+msgstr ""
+
+#. Tag: primary
+#: Rescue_Mode.xml:325
+#, no-c-format
+msgid "runlevel 1"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:327
+#, no-c-format
+msgid ""
+"One of the advantages of single-user mode is that you do not need a boot CD-"
+"ROM; however, it does not give you the option to mount the file systems as "
+"read-only or not mount them at all."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:331
+#, no-c-format
+msgid ""
+"If your system boots, but does not allow you to log in when it has completed "
+"booting, try single-user mode."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:335
+#, no-c-format
+msgid ""
+"In single-user mode, your computer boots to runlevel 1. Your local file "
+"systems are mounted, but your network is not activated. You have a usable "
+"system maintenance shell. Unlike rescue mode, single-user mode automatically "
+"tries to mount your file system. <emphasis>Do not use single-user mode if "
+"your file system cannot be mounted successfully.</emphasis> You cannot use "
+"single-user mode if the runlevel 1 configuration on your system is corrupted."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:340
+#, no-c-format
+msgid ""
+"On an x86 system using GRUB, use the following steps to boot into single-"
+"user mode:"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:346
+#, no-c-format
+msgid ""
+"At the GRUB splash screen at boot time, press any key to enter the GRUB "
+"interactive menu."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:352
+#, no-c-format
+msgid ""
+"Select <guilabel>Fedora</guilabel> with the version of the kernel that you "
+"wish to boot and type <command>a</command> to append the line."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:358
+#, no-c-format
+msgid ""
+"Go to the end of the line and type <userinput>single</userinput> as a "
+"separate word (press the <keycap>Spacebar</keycap> and then type "
+"<userinput>single</userinput>). Press <keycap>Enter</keycap> to exit edit "
+"mode."
+msgstr ""
+
+#. Tag: title
+#: Rescue_Mode.xml:366
+#, no-c-format
+msgid "Booting into Emergency Mode"
+msgstr ""
+
+#. Tag: secondary
+#: Rescue_Mode.xml:369
+#, no-c-format
+msgid "<secondary>emergency mode</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: Rescue_Mode.xml:372
+#, no-c-format
+msgid "<primary>emergency mode</primary>"
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:374
+#, no-c-format
+msgid ""
+"In emergency mode, you are booted into the most minimal environment "
+"possible. The root file system is mounted read-only and almost nothing is "
+"set up. The main advantage of emergency mode over single-user mode is that "
+"the <command>init</command> files are not loaded. If <command>init</command> "
+"is corrupted or not working, you can still mount file systems to recover "
+"data that could be lost during a re-installation."
+msgstr ""
+
+#. Tag: para
+#: Rescue_Mode.xml:379
+#, no-c-format
+msgid ""
+"To boot into emergency mode, use the same method as described for single-"
+"user mode in <xref linkend=\"s1-rescuemode-booting-single\"/> with one "
+"exception, replace the keyword <userinput>single</userinput> with the "
+"keyword <userinput>emergency</userinput>."
+msgstr ""
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:14
+#, no-c-format
+msgid ""
+"<firstname>Hans</firstname> <surname>De Goede</surname> "
+"<email>hdegoede at redhat.com</email>"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:19 Revision_History.xml:96 Revision_History.xml:111
+#: Revision_History.xml:126
+#, no-c-format
+msgid ""
+"<firstname>Paul</firstname> <othername>W.</othername> <surname>Frields</"
+"surname> <email>stickster at gmail.com</email>"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:25 Revision_History.xml:53
+#, no-c-format
+msgid ""
+"<firstname>Ruediger</firstname> <surname>Landmann</surname> <email>r."
+"landmann at redhat.com</email>"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:30
+#, no-c-format
+msgid ""
+"<firstname>David</firstname> <surname>Nalley</surname> <email>david."
+"nalley at fedoraproject.org</email>"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:35
+#, no-c-format
+msgid "<firstname>The anaconda</firstname> <surname>team</surname>"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:39
+#, no-c-format
+msgid ""
+"<firstname>Red Hat</firstname> <surname>Engineering Content Services</"
+"surname> <email>content-services-list at redhat.com</email>"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:46
+#, no-c-format
+msgid ""
+"Major update, incorporating material from the <citetitle>Red Hat Enterprise "
+"Linux Installation Guide</citetitle> and elsewhere, plus fixes for numerous "
+"bugs"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:60
+#, no-c-format
+msgid "Convert to build in Publican"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:67
+#, no-c-format
+msgid ""
+"<firstname>Karsten</firstname> <surname>Wade</surname> <email>kwade at redhat."
+"com</email>"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:74
+#, no-c-format
+msgid "Build and publish Fedora 10 version"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:81
+#, no-c-format
+msgid ""
+"<firstname>Jared</firstname> <othername>K.</othername> <surname>Smith</"
+"surname> <email>jaredsmith at jaredsmith.net</email>"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:89
+#, no-c-format
+msgid "Prepare for release of Fedora 10"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:104
+#, no-c-format
+msgid "Fix incorrect livecd-tools instructions"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:119
+#, no-c-format
+msgid "Lots of bug fixes"
+msgstr ""
+
+#. Tag: member
+#: Revision_History.xml:134
+#, no-c-format
+msgid "Add information on upgrading a distribution"
+msgstr ""
+
+#. Tag: title
+#: Steps_Cdrom-x86.xml:6
+#, no-c-format
+msgid "Can You Install Using the CD-ROM or DVD?"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:9
+#, no-c-format
+msgid "installing with CD-ROM or DVD"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:13
+#, no-c-format
+msgid "can you install with a CD-ROM or DVD"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:15
+#, no-c-format
+msgid "There are several methods that can be used to install Fedora."
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:21
+#, no-c-format
+msgid ""
+"Your BIOS may need to be changed to allow booting from your DVD/CD-ROM "
+"drive. For more information about changing your BIOS, refer to <xref linkend="
+"\"s2-x86-starting-booting\"/>."
+msgstr ""
+
+#. Tag: title
+#: Steps_Cdrom-x86.xml:26
+#, no-c-format
+msgid "Alternative Boot Methods"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Cdrom-x86.xml:28 Steps_Cdrom-x86.xml:54
+#, no-c-format
+msgid "<primary>boot methods</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:29
+#, no-c-format
+msgid "<secondary>boot CD-ROM</secondary>"
+msgstr ""
+
+#. Tag: term
+#: Steps_Cdrom-x86.xml:33
+#, no-c-format
+msgid "Boot DVD/CD-ROM"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Cdrom-x86.xml:37 Steps_Cdrom-x86.xml:79
+#, no-c-format
+msgid "<primary>boot CD-ROM</primary>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:37
+#, no-c-format
+msgid ""
+"If you can boot using the DVD/CD-ROM drive, you can create your own CD-ROM "
+"to boot the installation program. This may be useful, for example, if you "
+"are performing an installation over a network or from a hard drive. Refer to "
+"<xref linkend=\"s2-steps-make-cd\"/> for further instructions."
+msgstr ""
+
+#. Tag: term
+#: Steps_Cdrom-x86.xml:46
+#, no-c-format
+msgid "<term>USB pen drive</term>"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Cdrom-x86.xml:50
+#, no-c-format
+msgid "<primary>USB pen drive</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:51
+#, no-c-format
+msgid "<secondary>boot methods</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:55
+#, no-c-format
+msgid "<secondary>USB pen drive</secondary>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:56
+#, no-c-format
+msgid ""
+"If you cannot boot from the DVD/CD-ROM drive, but you can boot using a USB "
+"device, such as a USB pen drive, the following alternative boot method is "
+"available:"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:60
+#, no-c-format
+msgid ""
+"To boot using a USB pen drive, use the <command>dd</command> command to copy "
+"the <filename>diskboot.img</filename> image file from the <filename>/images/"
+"</filename> directory on the DVD or CD-ROM #1. For example:"
+msgstr ""
+
+#. Tag: screen
+#: Steps_Cdrom-x86.xml:63
+#, no-c-format
+msgid "dd if=diskboot.img of=/dev/sda"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:64
+#, no-c-format
+msgid ""
+"Your BIOS must support booting from a USB device in order for this boot "
+"method to work."
+msgstr ""
+
+#. Tag: title
+#: Steps_Cdrom-x86.xml:73
+#, no-c-format
+msgid "Making an Installation Boot CD-ROM"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Cdrom-x86.xml:76
+#, no-c-format
+msgid "boot CD-ROM, creating"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:86
+#, no-c-format
+msgid ""
+"The <filename>images/</filename> directory on the installation DVD contains "
+"the <filename>boot.iso</filename> file. This file is an image of a disc that "
+"you can burn to a CD and use to boot the installation program. To use this "
+"boot CD, your computer must be able to boot from its CD-ROM drive, and its "
+"BIOS settings must be configured to do so."
+msgstr ""
+
+#. Tag: title
+#: Steps_Cdrom-x86.xml:91
+#, no-c-format
+msgid "Choose an option to burn a CD from an image"
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom-x86.xml:92
+#, no-c-format
+msgid ""
+"When you burn the <filename>boot.iso</filename> image, make sure that you "
+"select the option to <literal>burn an image file to disc</literal> in your "
+"CD burning software. The exact wording of this option varies, depending on "
+"the software that you use, but should contain the word \"image\". Note that "
+"not all CD burning software includes this option. In particular, the CD "
+"burning software built into Microsoft Windows XP and Windows Vista does not "
+"offer this capability. There are many programs available that add this "
+"capability to Windows operating systems; <application>Infrarecorder</"
+"application> is a free and open-source example available from <ulink url="
+"\"http://www.infrarecorder.org/\">http://www.infrarecorder.org/</ulink>."
+msgstr ""
+
+#. Tag: para
+#: Steps_Cdrom_x86_ppc_preamble.xml:5
+#, no-c-format
+msgid ""
+"Installing from a CD-ROM or DVD requires that you have a Fedora &PRODVER; CD-"
+"ROM or DVD, and you have a DVD/CD-ROM drive on a system that supports "
+"booting from it."
+msgstr ""
+
+#. Tag: title
+#: Steps_Diskspace-x86.xml:6
+#, no-c-format
+msgid "Do You Have Enough Disk Space?"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Diskspace-x86.xml:9 Steps_Diskspace-x86.xml:16
+#, no-c-format
+msgid "<secondary>disk space</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Diskspace-x86.xml:12
+#, no-c-format
+msgid "<primary>disk space</primary>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace-x86.xml:19
+#, no-c-format
+msgid ""
+"Nearly every modern-day operating system (OS) uses <firstterm>disk "
+"partitions</firstterm>, and Fedora is no exception. When you install Fedora, "
+"you may have to work with disk partitions. If you have not worked with disk "
+"partitions before (or need a quick review of the basic concepts), refer to "
+"<xref linkend=\"ch-partitions-x86\"/> before proceeding."
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace-x86.xml:23
+#, no-c-format
+msgid ""
+"The disk space used by Fedora must be separate from the disk space used by "
+"other OSes you may have installed on your system, such as Windows, OS/2, or "
+"even a different version of Linux. For x86, AMD64, and <trademark class="
+"\"registered\">Intel</trademark> 64 systems, at least two partitions "
+"(<filename>/</filename> and <filename>swap</filename>) must be dedicated to "
+"Fedora."
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace-x86.xml:31
+#, no-c-format
+msgid ""
+"To gain a better sense of how much space you really need, refer to the "
+"recommended partitioning sizes discussed in <xref linkend=\"s2-"
+"diskpartrecommend-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace-x86.xml:35
+#, no-c-format
+msgid ""
+"If you are not sure that you meet these conditions, or if you want to know "
+"how to create free disk space for your Fedora installation, refer to <xref "
+"linkend=\"ch-partitions-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace_x86_ppc_Itemized_List.xml:9
+#, no-c-format
+msgid ""
+"have enough <emphasis>unpartitioned<footnote> <para> Unpartitioned disk "
+"space means that available disk space on the hard drive(s) you are "
+"installing to has not been divided into sections for data. When you "
+"partition a disk, each partition behaves like a separate disk drive. </para> "
+"</footnote></emphasis> disk space for the installation of Fedora, or"
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace_x86_ppc_Itemized_List.xml:19
+#, no-c-format
+msgid ""
+"have one or more partitions that may be deleted, thereby freeing up enough "
+"disk space to install Fedora."
+msgstr ""
+
+#. Tag: para
+#: Steps_Diskspace_x86_ppc_oneline_paragraph.xml:7
+#, no-c-format
+msgid "Before you start the installation process, you must"
+msgstr ""
+
+#. Tag: title
+#: Steps_Hardware-x86.xml:6
+#, no-c-format
+msgid "Is Your Hardware Compatible?"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Hardware-x86.xml:9
+#, no-c-format
+msgid "hardware compatibility"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Hardware-x86.xml:13
+#, no-c-format
+msgid "compatibility"
+msgstr ""
+
+#. Tag: para
+#: Steps_Hardware-x86.xml:15
+#, no-c-format
+msgid ""
+"Hardware compatibility is particularly important if you have an older system "
+"or a system that you built yourself. Fedora &PRODVER; should be compatible "
+"with most hardware in systems that were factory built within the last two "
+"years. However, hardware specifications change almost daily, so it is "
+"difficult to guarantee that your hardware is 100% compatible."
+msgstr ""
+
+#. Tag: para
+#: Steps_Hardware-x86.xml:20
+#, no-c-format
+msgid ""
+"The most recent list of supported hardware can be found in the Release Notes "
+"for Fedora &PRODVER;, available at <ulink url=\"http://docs.fedoraproject."
+"org/release-notes\">http://docs.fedoraproject.org/release-notes</ulink> ."
+msgstr ""
+
+#. Tag: title
+#: Steps_Hd_Install-x86.xml:6
+#, no-c-format
+msgid "Preparing for a Hard Drive Installation"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Hd_Install-x86.xml:39
+#, no-c-format
+msgid "installation media"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Hd_Install-x86.xml:40
+#, no-c-format
+msgid "testing"
+msgstr ""
+
+#. Tag: command
+#: Steps_Hd_Install-x86.xml:44
+#, no-c-format
+msgid "linux mediacheck"
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_note_para_1.xml:7
+#, no-c-format
+msgid ""
+"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 CDs). To use this test, type the following command at the "
+"<prompt>boot:</prompt> prompt:"
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_para_1.xml:5
+#, no-c-format
+msgid ""
+"Hard drive installations require the use of the ISO (or DVD/CD-ROM) images. "
+"An ISO image is a file containing an exact copy of a DVD/CD-ROM image. After "
+"placing the required ISO images (the binary Fedora DVD/CD-ROMs) in a "
+"directory, choose to install from the hard drive. You can then point the "
+"installation program at that directory to perform the installation."
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_s390_listitem_1.xml:8
+#, no-c-format
+msgid ""
+"Using a set of CD-ROMs, or a DVD — Create ISO image files from each "
+"installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), "
+"execute the following command on a Linux system:"
+msgstr ""
+
+#. Tag: screen
+#: Steps_Hd_Install_x86_ppc_s390_listitem_1.xml:10
+#, no-c-format
+msgid ""
+"<command>dd if=/dev/cdrom of=/tmp/<replaceable>file-name</replaceable>.iso</"
+"command>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml:8
+#, no-c-format
+msgid ""
+"Verifying that ISO images are intact before you attempt an installation, "
+"helps to avoid problems. To verify the ISO images are intact prior to "
+"performing an installation, use an <command>md5sum</command> program (many "
+"<command>md5sum</command> programs are available for various operating "
+"systems). An <command>md5sum</command> program should be available on the "
+"same Linux machine as the ISO images."
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_s390_listitem_2.xml:8
+#, no-c-format
+msgid ""
+"Using ISO images — transfer these images to the system to be installed."
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_s390_para_1.xml:8
+#, no-c-format
+msgid ""
+"To prepare your system for a hard drive installation, you must set the "
+"system up in one of the following ways:"
+msgstr ""
+
+#. Tag: para
+#: Steps_Hd_Install_x86_ppc_s390_para_2.xml:5
+#, no-c-format
+msgid ""
+"Additionally, if a file called <filename>updates.img</filename> exists in "
+"the location from which you install, it is used for updates to "
+"<filename>anaconda</filename>, the installation program. Refer to the file "
+"<filename>install-methods.txt</filename> in the <filename>anaconda</"
+"filename> RPM package for detailed information on the various ways to "
+"install Fedora, as well as how to apply the installation program updates."
+msgstr ""
+
+#. Tag: title
+#: Steps_Network_Install-x86.xml:6
+#, no-c-format
+msgid "Preparing for a Network Installation"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Network_Install-x86.xml:17
+#, no-c-format
+msgid "<secondary>FTP</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: Steps_Network_Install-x86.xml:25
+#, no-c-format
+msgid "<secondary>HTTP</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Network_Install-x86.xml:28
+#, no-c-format
+msgid "<primary>FTP</primary>"
+msgstr ""
+
+#. Tag: primary
+#: Steps_Network_Install-x86.xml:36
+#, no-c-format
+msgid "<primary>HTTP</primary>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_note.xml:11
+#, no-c-format
+msgid ""
+"Make sure an installation CD (or any other type of CD) is not in your "
+"system's CD/DVD drive if you are performing a network-based installation. "
+"Having a CD in the drive may cause unexpected errors."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml:8
+#, no-c-format
+msgid ""
+"Create an iso image from the installation disk(s) using the following "
+"command (for DVDs):"
+msgstr ""
+
+#. Tag: command
+#: Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml:15
+#, no-c-format
+msgid ""
+"dd if=/dev/<replaceable>dvd</replaceable> of=<replaceable>/location/of/disk/"
+"space/</replaceable>f&PRODVER;.iso"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml:20
+#, no-c-format
+msgid "where <replaceable>dvd</replaceable> refers to your DVD drive device."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml:24
+#, no-c-format
+msgid ""
+"For instructions on how to prepare a network installation using CD-ROMs, "
+"refer to the instructions on the <filename>README-en</filename> file in "
+"<filename>disk1</filename>."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_note_1.xml:8
+#, no-c-format
+msgid ""
+"In the following examples, the directory on the installation staging server "
+"that will contain the installation files will be specified as "
+"<filename><replaceable>/location/of/disk/space</replaceable></filename>. The "
+"directory that will be made publicly available via FTP, NFS, or HTTP will be "
+"specified as <replaceable>/publicly/available/directory</replaceable>. For "
+"example, <filename><replaceable>/location/of/disk/space</replaceable></"
+"filename> may be a directory you create called <filename>/var/isos</"
+"filename>. <filename><replaceable>/publicly/available/directory</"
+"replaceable></filename> might be <filename>/var/www/html/f&PRODVER;</"
+"filename>, for an HTTP install."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_para_1.xml:5
+#, no-c-format
+msgid ""
+"The Fedora installation media must be available for either a network "
+"installation (via NFS, FTP, or HTTP) or installation via local storage. Use "
+"the following steps if you are performing an NFS, FTP, or HTTP installation."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_para_2.xml:8
+#, no-c-format
+msgid ""
+"The NFS, FTP, or HTTP server to be used for installation over the network "
+"must be a separate machine which can provide the complete contents of the "
+"installation DVD-ROM or the installation CD-ROMs."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_para_3.xml:8
+#, no-c-format
+msgid ""
+"To copy the files from the installation DVD or CD-ROMs to a Linux machine "
+"which acts as an installation staging server, perform the following steps:"
+msgstr ""
+
+#. Tag: title
+#: Steps_Network_Install_x86_ppc_s390_section_1.xml:6
+#, no-c-format
+msgid "Preparing for FTP and HTTP installation"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_1.xml:8
+#, no-c-format
+msgid ""
+"Extract the files from the iso image of the installation DVD or the iso "
+"images of the installation CDs and place them in a directory that is shared "
+"over FTP or HTTP."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_1.xml:55
+#, no-c-format
+msgid ""
+"Next, make sure that the directory is shared via FTP or HTTP, and verify "
+"client access. You can check to see whether the directory is accessible from "
+"the server itself, and then from another machine on the same subnet that you "
+"will be installing to."
+msgstr ""
+
+#. Tag: title
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:6
+#, no-c-format
+msgid "Preparing for an NFS install"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:8
+#, no-c-format
+msgid ""
+"For NFS installation it is not necessary to mount the iso image. It is "
+"sufficient to make the iso image itself available via NFS. You can do this "
+"by moving the iso image or images to the NFS exported directory:"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:15
+#, no-c-format
+msgid "For DVD:"
+msgstr ""
+
+#. Tag: command
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:20
+#, no-c-format
+msgid ""
+"mv <replaceable>/location/of/disk/space/</replaceable>f&PRODVER;.iso "
+"<replaceable>/publicly/available/directory/</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:27
+#, no-c-format
+msgid "For CDROMs:"
+msgstr ""
+
+#. Tag: command
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:32
+#, no-c-format
+msgid ""
+"mv <replaceable>/location/of/disk/space/</replaceable>f&PRODVER;-disk*.iso "
+"<replaceable>/publicly/available/directory/</replaceable>"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:49
+#, no-c-format
+msgid ""
+"Ensure that the <filename><replaceable>/publicly/available/directory</"
+"replaceable></filename> directory is exported via NFS via an entry in "
+"<filename>/etc/exports</filename>."
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:53
+#, no-c-format
+msgid "To export to a specific system:"
+msgstr ""
+
+#. Tag: command
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:58
+#, no-c-format
+msgid ""
+"<replaceable>/publicly/available/directory</replaceable> <replaceable>client."
+"ip.address</replaceable>(ro,no_root_squash)"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:63
+#, no-c-format
+msgid "To export to all systems use an entry such as:"
+msgstr ""
+
+#. Tag: command
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:68
+#, no-c-format
+msgid ""
+"<replaceable>/publicly/available/directory</replaceable> *(ro,no_root_squash)"
+msgstr ""
+
+#. Tag: para
+#: Steps_Network_Install_x86_ppc_s390_section_2.xml:73
+#, no-c-format
+msgid ""
+"Start the NFS daemon (on a Fedora system, use <command>/sbin/service nfs "
+"start</command>). If NFS is already running, reload the configuration file "
+"(on a Fedora system use <command>/sbin/service nfs reload</command>)."
+msgstr ""
+
+#. Tag: title
+#: Steps_Upgrade-common.xml:6
+#, no-c-format
+msgid "Upgrade or Install?"
+msgstr ""
+
+#. Tag: para
+#: Steps_Upgrade-common.xml:8
+#, no-c-format
+msgid ""
+"For information to help you determine whether to perform an upgrade or an "
+"installation refer to <xref linkend=\"ch-upgrade-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Steps-x86.xml:6
+#, no-c-format
+msgid "Steps to Get You Started"
+msgstr ""
+
+#. Tag: title
+#: Swap_Partrecommend.xml:6
+#, no-c-format
+msgid "A swap partition (at least 256 MB)"
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:7
+#, no-c-format
+msgid ""
+"Swap partitions are used to support virtual memory. In other words, data is "
+"written to a swap partition when there is not enough RAM to store the data "
+"your system is processing. In addition, certain power management features "
+"store all of the memory for a suspended system in the available swap "
+"partitions."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:12
+#, no-c-format
+msgid ""
+"If you are unsure about what size swap partition to create, make it twice "
+"the amount of RAM on your machine. It must be of type swap."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:16
+#, no-c-format
+msgid ""
+"Creation of the proper amount of swap space varies depending on a number of "
+"factors including the following (in descending order of importance):"
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:22
+#, no-c-format
+msgid "The applications running on the machine."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:28
+#, no-c-format
+msgid "The amount of physical RAM installed on the machine."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:34
+#, no-c-format
+msgid "The version of the OS."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:40
+#, no-c-format
+msgid ""
+"Swap should equal 2x physical RAM for up to 2 GB of physical RAM, and then "
+"an additional 1x physical RAM for any amount above 2 GB, but never less than "
+"32 MB."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:44
+#, no-c-format
+msgid "So, if:"
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:48
+#, no-c-format
+msgid "M = Amount of RAM in GB, and S = Amount of swap in GB, then"
+msgstr ""
+
+#. Tag: screen
+#: Swap_Partrecommend.xml:52
+#, no-c-format
+msgid ""
+"If M < 2\n"
+"        S = M *2\n"
+"Else\n"
+"        S = M + 2"
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:55
+#, no-c-format
+msgid ""
+"Using this formula, a system with 2 GB of physical RAM would have 4 GB of "
+"swap, while one with 3 GB of physical RAM would have 5 GB of swap. Creating "
+"a large swap space partition can be especially helpful if you plan to "
+"upgrade your RAM at a later time."
+msgstr ""
+
+#. Tag: para
+#: Swap_Partrecommend.xml:59
+#, no-c-format
+msgid ""
+"For systems with really large amounts of RAM (more than 32 GB) you can "
+"likely get away with a smaller swap partition (around 1x, or less, of "
+"physical RAM)."
+msgstr ""
+
+#. Tag: title
+#: System_Requirements_Table.xml:6
+#, no-c-format
+msgid "System Specifications List"
+msgstr ""
+
+#. Tag: primary
+#: System_Requirements_Table.xml:10
+#, no-c-format
+msgid "<primary>hardware</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: System_Requirements_Table.xml:16
+#, no-c-format
+msgid "<secondary>hardware</secondary>"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:20
+#, no-c-format
+msgid ""
+"The installation program automatically detects and installs your computer's "
+"hardware. Although you should make sure that your hardware meets the minimum "
+"requirements to install Fedora (refer to <xref linkend=\"sn-"
+"Is_Your_Hardware_Compatible-x86\"/>) you do not usually need to supply the "
+"installation program with any specific details about your system."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:24
+#, no-c-format
+msgid ""
+"However, when performing certain types of installation, some specific "
+"details might be useful or even essential."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:30
+#, no-c-format
+msgid "If you plan to use a customized partition layout, record:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:35
+#, no-c-format
+msgid ""
+"The model numbers, sizes, types, and interfaces of the hard drives attached "
+"to the system. For example, Seagate ST3320613AS 320 GB on SATA0, Western "
+"Digital WD7500AAKS 750 GB on SATA1. This will allow you to identify specific "
+"hard drives during the partitioning process."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:43
+#, no-c-format
+msgid ""
+"If you are installing Fedora as an additional operating system on an "
+"existing system, record:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:48
+#, no-c-format
+msgid ""
+"The mount points of the existing partitions on the system. For example, "
+"<filename>/boot</filename> on <filename>sda1</filename>, <filename>/</"
+"filename> on <filename>sda2</filename>, and <filename>/home</filename> on "
+"<filename>sdb1</filename>. This will allow you to identify specific "
+"partitions during the partitioning process."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:56
+#, no-c-format
+msgid "If you plan to install from an image on a local hard drive:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:61
+#, no-c-format
+msgid ""
+"The hard drive and directory that holds the image – see <xref linkend="
+"\"table-Location_of_ISO_images\"/> for examples."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:69
+#, no-c-format
+msgid ""
+"If you plan to install from a network location, or install on an iSCSI "
+"target:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:74
+#, no-c-format
+msgid ""
+"The make and model numbers of the network adapters on your system. For "
+"example, Netgear GA311. This will allow you to identify adapters when "
+"manually configuring the network."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:79
+#, no-c-format
+msgid "IP, DHCP, and BOOTP addresses"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:85
+#, no-c-format
+msgid "Netmask"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:91
+#, no-c-format
+msgid "Gateway IP address"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:97
+#, no-c-format
+msgid "One or more name server IP addresses (DNS)"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:102
+#, no-c-format
+msgid ""
+"If any of these networking requirements or terms are unfamiliar to you, "
+"contact your network administrator for assistance."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:108
+#, no-c-format
+msgid "If you plan to install from a network location:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:113
+#, no-c-format
+msgid ""
+"The location of the image on an FTP server, HTTP (web) server, or NFS server "
+"– see <xref linkend=\"s1-begininstall-url-x86\"/> and <xref linkend="
+"\"s1-begininstall-nfs-x86\"/> for examples."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:121
+#, no-c-format
+msgid "If you plan to install on an iSCSI target:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:126
+#, no-c-format
+msgid ""
+"The location of the iSCSI target. Depending on your network, you might also "
+"need a CHAP username and password, and perhaps a reverse CHAP username and "
+"password – see <xref linkend=\"s1-advanced-storage-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:134
+#, no-c-format
+msgid "If your computer is part of a domain:"
+msgstr ""
+
+#. Tag: para
+#: System_Requirements_Table.xml:139
+#, no-c-format
+msgid ""
+"You should verify that the domain name will be supplied by the DHCP server. "
+"If not, you will need to input the domain name manually during installation."
+msgstr ""
+
+#. Tag: title
+#: techref.xml:10
+#, no-c-format
+msgid "Other Technical Documentation"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:11
+#, no-c-format
+msgid ""
+"This document provides a reference for using the Fedora installation "
+"software, known as <command>anaconda</command>. To learn more about "
+"<indexterm> <primary>Anaconda</primary> </indexterm> <command>anaconda</"
+"command>, visit the project Web page: <ulink url=\"http://www.fedoraproject."
+"org/wiki/Anaconda\"></ulink>."
+msgstr ""
+
+#. Tag: para
+#: techref.xml:20
+#, no-c-format
+msgid ""
+"Both <command>anaconda</command> and Fedora systems use a common set of "
+"software components. For detailed information on key technologies, refer to "
+"the Web sites listed below:"
+msgstr ""
+
+#. Tag: term
+#: techref.xml:27
+#, no-c-format
+msgid "Boot Loader"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:29
+#, no-c-format
+msgid ""
+"Fedora uses the <indexterm> <primary>GRUB</primary> "
+"<secondary>documentation</secondary> </indexterm> <command>GRUB</command> "
+"boot loader. Refer to <ulink url=\"http://www.gnu.org/software/grub/\"></"
+"ulink> for more information."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:43
+#, no-c-format
+msgid "Disk Partitioning"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:45
+#, no-c-format
+msgid ""
+"Fedora uses <command>parted</command> to partition disks. Refer to <ulink "
+"url=\"http://www.gnu.org/software/parted/\"></ulink> for more information."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:54
+#, no-c-format
+msgid "Storage Management"
+msgstr ""
+
+#. Tag: secondary
+#: techref.xml:59 techref.xml:169 techref.xml:220
+#, no-c-format
+msgid "documentation"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:60
+#, no-c-format
+msgid ""
+"Logical Volume Management (LVM) provides administrators with a range of "
+"facilities to manage storage. By default, the Fedora installation process "
+"formats drives as LVM volumes. Refer to <ulink url=\"http://www.tldp.org/"
+"HOWTO/LVM-HOWTO/\"></ulink> for more information."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:71
+#, no-c-format
+msgid "Audio Support"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:73
+#, no-c-format
+msgid ""
+"The Linux kernel used by Fedora incorporates <indexterm> "
+"<primary>PulseAudio</primary> </indexterm> PulseAudio audio server. For more "
+"information about PulseAudio, refer to the project documentation: <ulink url="
+"\"http://www.pulseaudio.org/wiki/Documentation\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:86
+#, no-c-format
+msgid "Graphics System"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:88
+#, no-c-format
+msgid ""
+"Both the installation system and Fedora use the <indexterm> <primary>Xorg</"
+"primary> </indexterm> <command>Xorg</command> suite to provide graphical "
+"capabilities. Components of <command>Xorg</command> manage the display, "
+"keyboard and mouse for the desktop environments that users interact with. "
+"Refer to <ulink url=\"http://www.x.org/\"></ulink> for more information."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:103
+#, no-c-format
+msgid "Remote Displays"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:105
+#, no-c-format
+msgid ""
+"Fedora and <command>anaconda</command> include <indexterm> <primary>VNC "
+"(Virtual Network Computing)</primary> <secondary>documentation</secondary> </"
+"indexterm> VNC (Virtual Network Computing) software to enable remote access "
+"to graphical displays. For more information about VNC, refer to the "
+"documentation on the RealVNC Web site: <ulink url=\"http://www.realvnc.com/"
+"documentation.html\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:120
+#, no-c-format
+msgid "Command-line Interface"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:122
+#, no-c-format
+msgid ""
+"By default, Fedora uses the GNU <command>bash</command> shell to provide a "
+"command-line interface. The GNU Core Utilities complete the command-line "
+"environment. Refer to <ulink url=\"http://www.gnu.org/software/bash/bash.html"
+"\"></ulink> for more information on <command>bash</command>. To learn more "
+"about the GNU Core Utilities, refer to <ulink url=\"http://www.gnu.org/"
+"software/coreutils/\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:135
+#, no-c-format
+msgid "Remote System Access"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:137
+#, no-c-format
+msgid ""
+"Fedora incorporates the <indexterm> <primary>OpenSSH</primary> <seealso>SSH</"
+"seealso> </indexterm> OpenSSH suite to provide remote access to the system. "
+"The SSH <indexterm> <primary>SSH (Secure SHell)</primary> "
+"<secondary>documentation</secondary> </indexterm> service enables a number "
+"of functions, which include access to the command-line from other systems, "
+"remote command execution, and network file transfers. During the "
+"installation process <command>anaconda</command> may use the <command>scp</"
+"command> <indexterm> <primary>scp</primary> <seealso>SSH</seealso> </"
+"indexterm> feature of OpenSSH to transfer crash reports to remote systems. "
+"Refer to the OpenSSH Web site for more information: <ulink url=\"http://www."
+"openssh.com/\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:164
+#, no-c-format
+msgid "Access Control"
+msgstr ""
+
+#. Tag: primary
+#: techref.xml:168
+#, no-c-format
+msgid "SELinux"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:170
+#, no-c-format
+msgid ""
+"SELinux provides Mandatory Access Control (MAC) capabilities that supplement "
+"the standard Linux security features. Refer to the SELinux Project Pages for "
+"more information: <ulink url=\"http://docs.fedoraproject.org/selinux-guide"
+"\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:180
+#, no-c-format
+msgid "Firewall"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:182
+#, no-c-format
+msgid ""
+"The Linux kernel used by Fedora incorporates the <command>netfilter</"
+"command> framework to provide <indexterm> <primary>firewall</primary> "
+"<secondary>documentation</secondary> </indexterm> firewall features. The "
+"Netfilter project website provides documentation for both "
+"<command>netfilter</command>, and the <command>iptables</command> "
+"administration facilities: <ulink url=\"http://netfilter.org/documentation/"
+"index.html\"></ulink>."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:198
+#, no-c-format
+msgid "Software Installation"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:200
+#, no-c-format
+msgid ""
+"Fedora uses <indexterm> <primary>yum</primary> <secondary>documentation</"
+"secondary> </indexterm> <command>yum</command> to manage the RPM packages "
+"that make up the system. Refer to <ulink url=\"http://docs.fedoraproject.org/"
+"yum/\"></ulink> for more information."
+msgstr ""
+
+#. Tag: term
+#: techref.xml:215
+#, no-c-format
+msgid "<term>Virtualization</term>"
+msgstr ""
+
+#. Tag: primary
+#: techref.xml:219
+#, no-c-format
+msgid "<primary>Virtualization</primary>"
+msgstr ""
+
+#. Tag: para
+#: techref.xml:221
+#, no-c-format
+msgid ""
+"Virtualization provides the capability to simultaneously run multiple "
+"operating systems on the same computer. Fedora also includes tools to "
+"install and manage the secondary systems on a Fedora host. You may select "
+"virtualization support during the installation process, or at any time "
+"thereafter. Refer to <ulink url=\"http://www.fedoraproject.org/wiki/Tools/"
+"Virtualization\"></ulink> for more information."
+msgstr ""
+
+#. Tag: title
+#: Time_Zone_common-figure-1.xml:5
+#, no-c-format
+msgid "Configuring the Time Zone"
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-figure-1.xml:8
+#, no-c-format
+msgid "Time zone configuration screen."
+msgstr ""
+
+#. Tag: secondary
+#: Time_Zone_common-indexterm-3.xml:10
+#, no-c-format
+msgid "time"
+msgstr ""
+
+#. Tag: primary
+#: Time_Zone_common-indexterm-7.xml:7
+#, no-c-format
+msgid "NTP (Network Time Protocol)"
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-itemizedlist-1.xml:10
+#, no-c-format
+msgid ""
+"Using your mouse, click on the interactive map to select a specific city "
+"(represented by a yellow dot). A red <guilabel>X</guilabel> appears "
+"indicating your selection."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-itemizedlist-1.xml:16
+#, no-c-format
+msgid ""
+"You can also scroll through the list at the bottom of the screen to select "
+"your time zone. Using your mouse, click on a location to highlight your "
+"selection."
+msgstr ""
+
+#. Tag: title
+#: Time_Zone_common-note-1.xml:7
+#, no-c-format
+msgid "Windows and the System Clock"
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-note-1.xml:9
+#, no-c-format
+msgid ""
+"Do not enable the <guilabel>System clock uses UTC</guilabel> option if your "
+"machine also runs Microsoft Windows. Microsoft operating systems change the "
+"BIOS clock to match local time rather than UTC. This may cause unexpected "
+"behavior under Fedora."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"Set your time zone by selecting the city closest to your computer's physical "
+"location. Click on the map to zoom in to a particular geographical region of "
+"the world."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-para-2.xml:8
+#, no-c-format
+msgid "From here there are two ways for you to select your time zone:"
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-para-4.xml:6
+#, no-c-format
+msgid ""
+"Specify a time zone even if you plan to use NTP (Network Time Protocol) to "
+"maintain the accuracy of the system clock."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-para-5.xml:6
+#, no-c-format
+msgid ""
+"If Fedora is the only operating system on your computer, select "
+"<guilabel>System clock uses UTC</guilabel>. The system clock is a piece of "
+"hardware on your computer system. Fedora uses the timezone setting to "
+"determine the offset between the local time and UTC on the system clock. "
+"This behavior is standard for UNIX-like operating systems."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-para-6.xml:6
+#, no-c-format
+msgid "Select <guibutton>Next</guibutton> to proceed."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-tip-1.xml:9
+#, no-c-format
+msgid ""
+"To change your time zone configuration after you have completed the "
+"installation, use the <application>Time and Date Properties Tool</"
+"application>."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-tip-1.xml:12
+#, no-c-format
+msgid ""
+"Type the <command>system-config-date</command> command in a shell prompt to "
+"launch the <application>Time and Date Properties Tool</application>. If you "
+"are not root, it prompts you for the root password to continue."
+msgstr ""
+
+#. Tag: para
+#: Time_Zone_common-tip-1.xml:15
+#, no-c-format
+msgid ""
+"To run the <application>Time and Date Properties Tool</application> as a "
+"text-based application, use the command <command>timeconfig</command>."
+msgstr ""
+
+#. Tag: title
+#: Time_Zone_common-title.xml:5
+#, no-c-format
+msgid "Time Zone Configuration"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_GUI-indexterm-1.xml:11
+#, no-c-format
+msgid "booting into a graphical environment"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_GUI-indexterm-2.xml:11
+#, no-c-format
+msgid "booting into the X Window System"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_GUI-indexterm-3.xml:11
+#, no-c-format
+msgid "booting into GNOME or KDE"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-10.xml:8
+#, no-c-format
+msgid ""
+"The next time you log in after rebooting your system, you are presented with "
+"a graphical login prompt."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-1.xml:5
+#, no-c-format
+msgid ""
+"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 <command moreinfo=\"none"
+"\">startx</command>."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-2.xml:8
+#, no-c-format
+msgid ""
+"Once you enter this command and press <keycap moreinfo=\"none\">Enter</"
+"keycap>, the graphical desktop environment is displayed."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-3.xml:8
+#, no-c-format
+msgid ""
+"Note, however, that this is just a one-time fix and does not change the log "
+"in process for future log ins."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-4.xml:8
+#, no-c-format
+msgid ""
+"To set up your system so that you can log in at a graphical login screen, "
+"you must edit one file, <filename moreinfo=\"none\">/etc/inittab</filename>, "
+"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."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-5.xml:8
+#, no-c-format
+msgid ""
+"Open a shell prompt. If you are in your user account, become root by typing "
+"the <command moreinfo=\"none\">su</command> command."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-6.xml:8
+#, no-c-format
+msgid ""
+"Now, type <command moreinfo=\"none\">gedit /etc/inittab</command> to edit "
+"the file with <application moreinfo=\"none\">gedit</application>. The file "
+"<filename moreinfo=\"none\">/etc/inittab</filename> opens. Within the first "
+"screen, a section of the file which looks like the following appears:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-7.xml:8
+#, no-c-format
+msgid ""
+"To change from a console to a graphical login, you should change the number "
+"in the line <computeroutput moreinfo=\"none\">id:3:initdefault:</"
+"computeroutput> from a <computeroutput moreinfo=\"none\">3</computeroutput> "
+"to a <computeroutput moreinfo=\"none\">5</computeroutput>."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-8.xml:8
+#, no-c-format
+msgid "Your changed line should look like the following:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-para-9.xml:8
+#, no-c-format
+msgid ""
+"When you are satisfied with your change, save and exit the file using the "
+"<keycombo moreinfo=\"none\"><keycap moreinfo=\"none\">Ctrl</keycap><keycap "
+"moreinfo=\"none\">Q</keycap> </keycombo> keys. A window appears and asks if "
+"you would like to save the changes. Click <guibutton moreinfo=\"none\">Save</"
+"guibutton>."
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_GUI-screen-1.xml:5
+#, no-c-format
+msgid ""
+"# Default runlevel. The runlevels used are: \n"
+"#   0 - halt (Do NOT set initdefault to this) \n"
+"#   1 - Single user mode \n"
+"#   2 - Multiuser, without NFS (The same as 3, if you do not have "
+"networking) \n"
+"#   3 - Full multiuser mode \n"
+"#   4 - unused \n"
+"#   5 - X11 \n"
+"#   6 - reboot (Do NOT set initdefault to this) \n"
+"#  id:3:initdefault:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_GUI-screen-2.xml:8
+#, no-c-format
+msgid ""
+"<computeroutput moreinfo=\"none\">        id:5:initdefault:       </"
+"computeroutput>"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_GUI-warning-1.xml:11
+#, no-c-format
+msgid ""
+"Change <emphasis>only</emphasis> the number of the default runlevel from "
+"<filename moreinfo=\"none\">3</filename> to <filename moreinfo=\"none\">5</"
+"filename>."
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_GUI_x86_ppc-title-1.xml:8
+#, no-c-format
+msgid "Booting into a Graphical Environment"
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_Problems-Apache.xml:9
+#, no-c-format
+msgid ""
+"Apache-based <command moreinfo=\"none\">httpd</command> service/Sendmail "
+"Hangs During Startup"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_Problems-Apache.xml:13
+#, no-c-format
+msgid ""
+"Apache-based <command moreinfo=\"none\">httpd</command> service hangs during "
+"startup"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_Problems-Apache.xml:18
+#, no-c-format
+msgid "Sendmail hangs during startup"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems-Apache.xml:20
+#, no-c-format
+msgid ""
+"If you are having trouble with the Apache-based <command moreinfo=\"none"
+"\">httpd</command> service or Sendmail hanging at startup, make sure the "
+"following line is in the <filename moreinfo=\"none\">/etc/hosts</filename> "
+"file:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_Problems-Apache.xml:23
+#, no-c-format
+msgid "127.0.0.1  localhost.localdomain  localhost"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_Problems_Login-indexterm-1.xml:11
+#, no-c-format
+msgid "logging in"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-10.xml:8
+#, no-c-format
+msgid ""
+"If you cannot remember your user account password, you must become root. To "
+"become root, type <command moreinfo=\"none\">su -</command> and enter your "
+"root password when prompted. Then, type <command moreinfo=\"none\">passwd "
+"<username></command>. This allows you to enter a new password for the "
+"specified user account."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-11.xml:5
+#, no-c-format
+msgid ""
+"If the graphical login screen does not appear, check your hardware for "
+"compatibility issues. Linuxquestions.org maintains a Hardware Compatibility "
+"List at:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-1.xml:5
+#, no-c-format
+msgid ""
+"If you did not create a user account in the <application>firstboot</"
+"application> screens, log in as root and use the password you assigned to "
+"root."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-2.xml:8
+#, no-c-format
+msgid ""
+"If you cannot remember your root password, boot your system as <command "
+"moreinfo=\"none\">linux single</command>."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-4.xml:8
+#, no-c-format
+msgid ""
+"If you are using an x86-based system and GRUB is your installed boot loader, "
+"type <command moreinfo=\"none\">e</command> 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."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-5.xml:8
+#, no-c-format
+msgid ""
+"Choose the line that starts with <filename moreinfo=\"none\">kernel</"
+"filename> and type <command moreinfo=\"none\">e</command> to edit this boot "
+"entry."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-6.xml:8
+#, no-c-format
+msgid ""
+"At the end of the <filename moreinfo=\"none\">kernel</filename> line, add:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems_Login-para-9.xml:8
+#, no-c-format
+msgid ""
+"Once you have booted into single user mode and have access to the <prompt "
+"moreinfo=\"none\">#</prompt> prompt, you must type <command moreinfo=\"none"
+"\">passwd root</command>, which allows you to enter a new password for root. "
+"At this point you can type <command moreinfo=\"none\">shutdown -r now</"
+"command> to reboot the system with the new root password."
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_Problems_Login-screen-1.xml:8
+#, no-c-format
+msgid "<userinput moreinfo=\"none\">single</userinput>"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_Problems_Login-screen-2.xml:5
+#, no-c-format
+msgid ""
+"<ulink url=\"http://www.linuxquestions.org/hcl/index.php\">http://www."
+"linuxquestions.org/hcl/index.php</ulink>"
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_Problems_Login-title-1.xml:8
+#, no-c-format
+msgid "Problems When You Try to Log In"
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_Problems-Printer.xml:9
+#, no-c-format
+msgid "Your Printer Does Not Work"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_Problems-Printer.xml:13
+#, no-c-format
+msgid "printers"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems-Printer.xml:15
+#, no-c-format
+msgid ""
+"If you are not sure how to set up your printer or are having trouble getting "
+"it to work properly, try using the <application moreinfo=\"none\">Printer "
+"Configuration Tool</application>."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_Problems-Printer.xml:19
+#, no-c-format
+msgid ""
+"Type the <command moreinfo=\"none\">system-config-printer</command> command "
+"at a shell prompt to launch the <application moreinfo=\"none\">Printer "
+"Configuration Tool</application>. If you are not root, it prompts you for "
+"the root password to continue."
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_X_Server_Non_Root.xml:9
+#, no-c-format
+msgid "Problems with the X Server Crashing and Non-Root Users"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_X_Server_Non_Root.xml:13
+#, no-c-format
+msgid "X server crashes"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Server_Non_Root.xml:15
+#, no-c-format
+msgid ""
+"If you are having trouble with the X server crashing when anyone other than "
+"root logs in, you may have a full file system (or, a lack of available hard "
+"drive space)."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Server_Non_Root.xml:19
+#, no-c-format
+msgid ""
+"To verify that this is the problem you are experiencing, run the following "
+"command:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Booting_X_Server_Non_Root.xml:22
+#, no-c-format
+msgid "df -h"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Server_Non_Root.xml:23
+#, no-c-format
+msgid ""
+"The <command moreinfo=\"none\">df</command> command should help you diagnose "
+"which partition is full. For additional information about <command moreinfo="
+"\"none\">df</command> and an explanation of the options available (such as "
+"the <option>-h</option> option used in this example), refer to the <command "
+"moreinfo=\"none\">df</command> man page by typing <command moreinfo=\"none"
+"\">man df</command> at a shell prompt."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Server_Non_Root.xml:28
+#, no-c-format
+msgid ""
+"A key indicator is 100% full or a percentage above 90% or 95% on a "
+"partition. The <filename moreinfo=\"none\">/home/</filename> and <filename "
+"moreinfo=\"none\">/tmp/</filename> 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."
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Booting_X_Windows.xml:6
+#, no-c-format
+msgid "Problems with the X Window System (GUI)"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Booting_X_Windows.xml:10
+#, no-c-format
+msgid "X (X Window System)"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Windows.xml:12
+#, no-c-format
+msgid ""
+"If you are having trouble getting X (the X Window System) to start, you may "
+"not have installed it during your installation."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Windows.xml:16
+#, no-c-format
+msgid ""
+"If you want X, you can either install the packages from the Fedora "
+"installation media or perform an upgrade."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Booting_X_Windows.xml:20
+#, no-c-format
+msgid ""
+"If you elect to upgrade, select the X Window System packages, and choose "
+"GNOME, KDE, or both, during the upgrade package selection process."
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_common-title-1.xml:8
+#, no-c-format
+msgid "Problems After Installation"
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Ram.xml:6
+#, no-c-format
+msgid "Is Your RAM Not Being Recognized?"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Ram.xml:10
+#, no-c-format
+msgid "RAM not recognized"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:12
+#, no-c-format
+msgid ""
+"Sometimes, the kernel does not recognize all of your memory (RAM). You can "
+"check this with the <command moreinfo=\"none\">cat /proc/meminfo</command> "
+"command."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:16
+#, no-c-format
+msgid ""
+"Verify that the displayed quantity is the same as the known amount of RAM in "
+"your system. If they are not equal, add the following line to the <filename "
+"moreinfo=\"none\">/boot/grub/grub.conf</filename>:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Ram.xml:19 Trouble_After_Ram.xml:46
+#, no-c-format
+msgid ""
+"<userinput moreinfo=\"none\">mem=<replaceable>xx</replaceable>M</userinput>"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:20
+#, no-c-format
+msgid ""
+"Replace <replaceable>xx</replaceable> with the amount of RAM you have in "
+"megabytes."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:24
+#, no-c-format
+msgid ""
+"In <filename moreinfo=\"none\">/boot/grub/grub.conf</filename>, the above "
+"example would look similar to the following:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_After_Ram.xml:29
+#, no-c-format
+msgid ""
+"# NOTICE: You have a /boot partition. This means that \n"
+"#  all kernel paths are relative to /boot/ \n"
+"default=0 \n"
+"timeout=30 \n"
+"splashimage=(hd0,0)/grub/splash.xpm.gz \n"
+" title Fedora (2.6.27.19-170.2.35.fc10.i686)\n"
+"root (hd0,1)\n"
+"kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-"
+"b207-002689545705 mem=1024M\n"
+"initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:31
+#, no-c-format
+msgid ""
+"Once you reboot, the changes made to <filename moreinfo=\"none\">grub.conf</"
+"filename> are reflected on your system."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:35
+#, no-c-format
+msgid ""
+"Once you have loaded the GRUB boot screen, type <command moreinfo=\"none"
+"\">e</command> for edit. You are presented with a list of items in the "
+"configuration file for the boot label you have selected."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:39
+#, no-c-format
+msgid ""
+"Choose the line that starts with <computeroutput moreinfo=\"none\">kernel</"
+"computeroutput> and type <command moreinfo=\"none\">e</command> to edit this "
+"boot entry."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:43
+#, no-c-format
+msgid ""
+"At the end of the <computeroutput moreinfo=\"none\">kernel</computeroutput> "
+"line, add"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:47
+#, no-c-format
+msgid ""
+"where <replaceable>xx</replaceable> equals the amount of RAM in your system."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:59
+#, no-c-format
+msgid ""
+"Itanium users must enter boot commands with <command moreinfo=\"none"
+"\">elilo</command> followed by the boot command."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Ram.xml:63
+#, no-c-format
+msgid ""
+"Remember to replace <replaceable>xx</replaceable> with the amount of RAM in "
+"your system. Press <keycap moreinfo=\"none\">Enter</keycap> to boot."
+msgstr ""
+
+#. Tag: title
+#: Trouble_After_Sound.xml:6
+#, no-c-format
+msgid "Problems with Sound Configuration"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_After_Sound.xml:10
+#, no-c-format
+msgid "sound configuration"
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Sound.xml:12
+#, no-c-format
+msgid ""
+"If, for some reason, you do not hear sound and know that you do have a sound "
+"card installed, you can run the <application moreinfo=\"none\">Sound Card "
+"Configuration Tool</application> (<command moreinfo=\"none\">system-config-"
+"soundcard</command>) utility."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Sound.xml:16
+#, no-c-format
+msgid ""
+"To use the <application moreinfo=\"none\">Sound Card Configuration Tool</"
+"application>, choose <guimenu moreinfo=\"none\">Main Menu</guimenu> => "
+"<guimenuitem moreinfo=\"none\">System </guimenuitem> => <guimenuitem "
+"moreinfo=\"none\">Administration </guimenuitem> => <guimenuitem moreinfo="
+"\"none\">Soundcard Detection</guimenuitem> in GNOME, or <guimenu moreinfo="
+"\"none\">Main Menu</guimenu> => <guimenuitem moreinfo=\"none\">Computer </"
+"guimenuitem> => <guimenuitem moreinfo=\"none\">System Settings</"
+"guimenuitem> => <guimenuitem moreinfo=\"none\">Multimedia</guimenuitem> "
+"in KDE. A small text box pops up prompting you for your root password."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Sound.xml:21
+#, no-c-format
+msgid ""
+"You can also type the <command moreinfo=\"none\">system-config-soundcard</"
+"command> command at a shell prompt to launch the <application moreinfo=\"none"
+"\">Sound Card Configuration Tool</application>. If you are not root, it "
+"prompts you for the root password to continue."
+msgstr ""
+
+#. Tag: para
+#: Trouble_After_Sound.xml:31
+#, no-c-format
+msgid ""
+"If the <application moreinfo=\"none\">Sound Card Configuration Tool</"
+"application> does not work (if the sample does not play and you still do not "
+"have audio sounds), it is likely that your sound card is not yet supported "
+"in Fedora."
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_Begin_GUI-indexterm-1.xml:11
+#, no-c-format
+msgid "GUI installation method unavailable"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_Begin_GUI-indexterm-2.xml:11
+#, no-c-format
+msgid "frame buffer, disabling"
+msgstr ""
+
+#. Tag: para
+#: Trouble_Begin_GUI-note-1.xml:11
+#, no-c-format
+msgid ""
+"To disable frame buffer support and allow the installation program to run in "
+"text mode, try using the <command moreinfo=\"none\">nofb</command> boot "
+"option. This command may be necessary for accessibility with some screen "
+"reading hardware."
+msgstr ""
+
+#. Tag: para
+#: Trouble_Begin_GUI-para-1.xml:8
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: Trouble_Begin_GUI-title.xml:8
+#, no-c-format
+msgid "Problems with Booting into the Graphical Installation"
+msgstr ""
+
+#. Tag: title
+#: Trouble_Begin_x86_ppc_title-1.xml:8
+#, no-c-format
+msgid "Trouble Beginning the Installation"
+msgstr ""
+
+#. Tag: para
+#: Trouble_common-para-1.xml:8
+#, no-c-format
+msgid ""
+"This appendix discusses some common installation problems and their "
+"solutions."
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_During_common-other-partitioning-indexterm-1.xml:11
+#, no-c-format
+msgid "completing partitions"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-other-partitioning-listitem-1.xml:9
+#, no-c-format
+msgid "A <filename moreinfo=\"none\">/</filename> (root) partition"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-other-partitioning-listitem-2.xml:9
+#, no-c-format
+msgid "A <swap> partition of type swap"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-other-partitioning-para-1.xml:5
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-other-partitioning-para-2.xml:8
+#, no-c-format
+msgid "You must have the following partitions as a bare minimum:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-other-partitioning-tip-1.xml:6
+#, no-c-format
+msgid ""
+"When defining a partition's type as swap, do not assign it a mount point. "
+"<application>Anaconda</application> automatically assigns the mount point "
+"for you."
+msgstr ""
+
+#. Tag: title
+#: Trouble_During_common-other-partitioning-title-1.xml:8
+#, no-c-format
+msgid "Other Partitioning Problems"
+msgstr ""
+
+#. Tag: guilabel
+#: Trouble_During_common-partitions-para-1.xml:9
+#, no-c-format
+msgid ""
+"The partition table on device hda was unreadable. To create new partitions "
+"it must be initialized, causing the loss of ALL DATA on this drive."
+msgstr ""
+
+#. Tag: title
+#: Trouble_During_common-python-errors.xml:6
+#, no-c-format
+msgid "Are You Seeing Python Errors?"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_During_common-python-errors.xml:10
+#, no-c-format
+msgid "Python errors"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-python-errors.xml:12
+#, no-c-format
+msgid ""
+"During some upgrades or installations of Fedora, the installation program "
+"(also known as <application moreinfo=\"none\">anaconda</application>) may "
+"fail with a Python or traceback error. This error may occur after the "
+"selection of individual packages or while trying to save the upgrade log in "
+"the <filename moreinfo=\"none\">/tmp/</filename>directory. The error may "
+"look similar to:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_During_common-python-errors.xml:15
+#, no-c-format
+msgid ""
+"<!--<computeroutput>-->Traceback (innermost last):\n"
+"File \"/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py\", line "
+"20, in run\n"
+"rc = self.todo.doInstall ()    \n"
+"File \"/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py\", line 1468, in "
+"doInstall \n"
+"self.fstab.savePartitions ()    \n"
+"File \"fstab.py\", line 221, in savePartitions      \n"
+"sys.exit(0)  \n"
+"SystemExit: 0   \n"
+"Local variables in innermost frame:  \n"
+"self: <fstab.GuiFstab instance at 8446fe0>  \n"
+"sys: <module 'sys' (built-in)>  \n"
+"ToDo object:  (itodo  ToDo  p1  (dp2  S'method'  p3  (iimage  "
+"CdromInstallMethod  \n"
+"p4  (dp5  S'progressWindow'  p6   <failed><!--</computeroutput>-->"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-python-errors.xml:16
+#, no-c-format
+msgid ""
+"This error occurs in some systems where links to <filename>/tmp/</filename> "
+"are symbolic to other locations or have been changed since creation. These "
+"symbolic or changed links are invalid during the installation process, so "
+"the installation program cannot write information and fails."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-python-errors.xml:21
+#, no-c-format
+msgid ""
+"If you experience such an error, first try to download any available updates "
+"for <application moreinfo=\"none\">anaconda</application>. Updates for "
+"<application>anaconda</application> and instructions for using them can be "
+"found at:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_During_common-python-errors.xml:24
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/Anaconda/Updates\">http://"
+"fedoraproject.org/wiki/Anaconda/Updates</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-python-errors.xml:30
+#, no-c-format
+msgid ""
+"The <application>anaconda</application> website may also be a useful "
+"reference and can be found online at:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_During_common-python-errors.xml:33
+#, no-c-format
+msgid ""
+"<ulink url=\"http://fedoraproject.org/wiki/Anaconda\">http://fedoraproject."
+"org/wiki/Anaconda</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_common-python-errors.xml:34
+#, no-c-format
+msgid ""
+"You can also search for bug reports related to this problem. To search Red "
+"Hat's bug tracking system, go to:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_During_common-python-errors.xml:37
+#, no-c-format
+msgid ""
+"<ulink url=\"http://bugzilla.redhat.com/bugzilla/\">http://bugzilla.redhat."
+"com/bugzilla/</ulink>"
+msgstr ""
+
+#. Tag: title
+#: Trouble_During_common-title-1.xml:6
+#, no-c-format
+msgid ""
+"<computeroutput moreinfo=\"none\">No devices found to install Fedora </"
+"computeroutput> Error Message"
+msgstr ""
+
+#. Tag: title
+#: Trouble_During-x86.xml:6
+#, no-c-format
+msgid "Trouble During the Installation"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_During-x86.xml:18
+#, no-c-format
+msgid ""
+"<computeroutput moreinfo=\"none\">No devices found to install Fedora</"
+"computeroutput> error message"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During-x86.xml:23
+#, no-c-format
+msgid ""
+"Check your hardware vendor's website to determine if a driver diskette image "
+"is available that fixes your problem. For more general information on driver "
+"diskettes, refer to <xref linkend=\"ch-driverdisk-x86\"/>."
+msgstr ""
+
+#. Tag: title
+#: Trouble_During-x86.xml:57
+#, no-c-format
+msgid "Trouble with Partition Tables"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During-x86.xml:63
+#, no-c-format
+msgid ""
+"If you receive an error after the <guilabel moreinfo=\"none\">Disk "
+"Partitioning Setup</guilabel> (<xref linkend=\"s1-diskpartsetup-x86\"/>) "
+"phase of the installation saying something similar to"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During-x86.xml:71
+#, no-c-format
+msgid ""
+"Users who have used programs such as <application moreinfo=\"none\">EZ-BIOS</"
+"application> 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."
+msgstr ""
+
+#. Tag: title
+#: Trouble_During-x86.xml:79
+#, no-c-format
+msgid "Using Remaining Space"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_During-x86.xml:83
+#, no-c-format
+msgid "using remaining hard drive space"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During-x86.xml:85
+#, no-c-format
+msgid ""
+"You have a <filename moreinfo=\"none\">swap</filename> and a <filename "
+"moreinfo=\"none\">/</filename> (root) partition created, and you have "
+"selected the root partition to use the remaining space, but it does not fill "
+"the hard drive."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During-x86.xml:89
+#, no-c-format
+msgid ""
+"If your hard drive is more than 1024 cylinders, you must create a <filename "
+"moreinfo=\"none\">/boot</filename> partition if you want the <filename "
+"moreinfo=\"none\">/</filename> (root) partition to use all of the remaining "
+"space on your hard drive."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_x86_ppc-para-1.xml:6
+#, no-c-format
+msgid ""
+"If you receive an error message stating <computeroutput moreinfo=\"none\">No "
+"devices found to install Fedora</computeroutput>, there is probably a SCSI "
+"controller that is not being recognized by the installation program."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_x86_ppc-para-3.xml:5
+#, no-c-format
+msgid ""
+"You can also refer to the LinuxQuestions.org Hardware Compatibility List, "
+"available online at:"
+msgstr ""
+
+#. Tag: ulink
+#: Trouble_During_x86_ppc-screen-1.xml:6
+#, no-c-format
+msgid "http://www.linuxquestions.org/hcl/index.php"
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_x86_ppc-section-2-para-1.xml:6
+#, no-c-format
+msgid ""
+"If you receive a traceback error message during installation, you can "
+"usually save it to removeable media, for example a USB flash drive or a "
+"floppy disk."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_x86_ppc-section-2-para-2.xml:5
+#, no-c-format
+msgid ""
+"If you do not have removeable media available on your system, you can "
+"<command moreinfo=\"none\">scp</command> the error message to a remote "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Trouble_During_x86_ppc-section-2-para-3.xml:8
+#, no-c-format
+msgid ""
+"When the traceback dialog appears, the traceback error message is "
+"automatically written to a file named <filename moreinfo=\"none\">/tmp/"
+"anacdump.txt</filename>. Once the dialog appears, switch over to a new tty "
+"(virtual console) by pressing the keys <command moreinfo=\"none\"> <keycombo "
+"moreinfo=\"none\"><keycap moreinfo=\"none\">Ctrl</keycap><keycap moreinfo="
+"\"none\">Alt</keycap><keycap moreinfo=\"none\">F2</keycap> </keycombo> </"
+"command> and <command moreinfo=\"none\">scp</command> the message written to "
+"<filename moreinfo=\"none\">/tmp/anacdump.txt</filename> to a known working "
+"remote system."
+msgstr ""
+
+#. Tag: title
+#: Trouble_During_x86_ppc-sectiontitle-2.xml:5
+#, no-c-format
+msgid "Saving traceback messages without removeable media"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble_No_Boot-Sig11-indexterm-1.xml:11
+#, no-c-format
+msgid "signal 11 error"
+msgstr ""
+
+#. Tag: para
+#: Trouble_No_Boot-Sig11-para-1.xml:8
+#, no-c-format
+msgid ""
+"A signal 11 error, commonly know as a <firstterm>segmentation fault</"
+"firstterm>, 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."
+msgstr ""
+
+#. Tag: para
+#: Trouble_No_Boot-Sig11-para-2.xml:5
+#, no-c-format
+msgid ""
+"If you receive a fatal signal 11 error during your installation, it is "
+"probably due to a hardware error in memory on your system's bus. Like other "
+"operating systems, Fedora places its own demands on your system's hardware. "
+"Some of this hardware may not be able to meet those demands, even if they "
+"work properly under another OS."
+msgstr ""
+
+#. Tag: para
+#: Trouble_No_Boot-Sig11-para-3.xml:5
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: Trouble_No_Boot-Sig11-para-7.xml:5
+#, no-c-format
+msgid ""
+"Another option is to perform a media check on your installation CD-ROMs. "
+"<application>Anaconda</application>, the 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. Red Hat "
+"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 CDs). To "
+"use this test, type the following command at the <prompt>boot:</prompt> "
+"prompt:"
+msgstr ""
+
+#. Tag: para
+#: Trouble_No_Boot-Sig11-para-8.xml:8
+#, no-c-format
+msgid "For more information concerning signal 11 errors, refer to:"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_No_Boot-Sig11-screen-2.xml:8
+#, no-c-format
+msgid "<userinput moreinfo=\"none\">linux mediacheck</userinput>"
+msgstr ""
+
+#. Tag: screen
+#: Trouble_No_Boot-Sig11-screen-3.xml:8
+#, no-c-format
+msgid ""
+"<ulink url=\"http://www.bitwizard.nl/sig11/\">http://www.bitwizard.nl/sig11/"
+"</ulink>"
+msgstr ""
+
+#. Tag: title
+#: Trouble_No_Boot-Sig11-title-1.xml:8
+#, no-c-format
+msgid "Is Your System Displaying Signal 11 Errors?"
+msgstr ""
+
+#. Tag: title
+#: Trouble_No_Boot-title-1.xml:5
+#, no-c-format
+msgid "You are unable to boot Fedora"
+msgstr ""
+
+#. Tag: title
+#: Trouble-x86.xml:7
+#, no-c-format
+msgid ""
+"Troubleshooting Installation on an <trademark class=\"registered\">Intel</"
+"trademark> or AMD System"
+msgstr ""
+
+#. Tag: title
+#: Trouble-x86.xml:25
+#, no-c-format
+msgid "Are You Unable to Boot With Your RAID Card?"
+msgstr ""
+
+#. Tag: tertiary
+#: Trouble-x86.xml:29
+#, no-c-format
+msgid "RAID cards"
+msgstr ""
+
+#. Tag: secondary
+#: Trouble-x86.xml:33
+#, no-c-format
+msgid "trouble booting from drive attached to RAID card"
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:35
+#, no-c-format
+msgid ""
+"If you have performed an installation and cannot boot your system properly, "
+"you may need to reinstall and create your partitions differently."
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:39
+#, no-c-format
+msgid ""
+"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, <prompt moreinfo=\"none\">GRUB:</prompt> ) and a flashing cursor "
+"may be all that appears. If this is the case, you must repartition your "
+"system."
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:45
+#, no-c-format
+msgid ""
+"Whether you choose automatic or manual partitioning, you must install your "
+"<filename moreinfo=\"none\">/boot</filename> 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."
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:50
+#, no-c-format
+msgid ""
+"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 <filename moreinfo=\"none\">/boot/</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:54
+#, no-c-format
+msgid ""
+"Once these changes have been made, you should be able to finish your "
+"installation and boot the system properly."
+msgstr ""
+
+#. Tag: para
+#: Trouble-x86.xml:115
+#, no-c-format
+msgid ""
+"One possible solution is to try using the <command moreinfo=\"none"
+"\">resolution=</command> boot option. This option may be most helpful for "
+"laptop users. Another solution to try is the <command>driver=</command> "
+"option to specify the driver that should be loaded for your video card. If "
+"this works, it should be reported as a bug as the installer has failed to "
+"autodetect your videocard. Refer to <xref linkend=\"ap-admin-options\"/> for "
+"more information on boot options."
+msgstr ""
+
+#. Tag: title
+#: Understanding_LVM.xml:7
+#, no-c-format
+msgid "Understanding LVM"
+msgstr ""
+
+#. Tag: secondary
+#: Understanding_LVM.xml:10
+#, no-c-format
+msgid "understanding"
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:12
+#, no-c-format
+msgid ""
+"LVM (Logical Volume Management) partitions provide a number of advantages "
+"over standard partitions. LVM partitions are formatted as <indexterm> "
+"<primary>LVM</primary> <secondary>physical volume</secondary> </indexterm> "
+"<firstterm>physical volumes</firstterm>. One or more physical volumes are "
+"combined to form a <indexterm> <primary>LVM</primary> <secondary>volume "
+"group</secondary> </indexterm> <firstterm>volume group</firstterm>. Each "
+"volume group's total storage is then divided into one or more <indexterm> "
+"<primary>LVM</primary> <secondary>logical volume</secondary> </indexterm> "
+"<firstterm>logical volumes</firstterm>. The logical volumes function much "
+"like standard partitions. They have a file system type, such as <systemitem "
+"class=\"filesystem\">ext4</systemitem>, and a mount point."
+msgstr ""
+
+#. Tag: title
+#: Understanding_LVM.xml:36
+#, no-c-format
+msgid "The <filename>/boot</filename> Partition and LVM"
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:37
+#, no-c-format
+msgid ""
+"The boot loader cannot read LVM volumes. You must make a standard, non-LVM "
+"disk partition for your <filename class=\"partition\">/boot</filename> "
+"partition."
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:44
+#, no-c-format
+msgid ""
+"To understand LVM better, imagine the physical volume as a pile of "
+"<firstterm>blocks</firstterm>. A block is simply a storage unit used to "
+"store data. Several piles of blocks can be combined to make a much larger "
+"pile, just as physical volumes are combined to make a volume group. The "
+"resulting pile can be subdivided into several smaller piles of arbitrary "
+"size, just as a volume group is allocated to several logical volumes."
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:52
+#, no-c-format
+msgid ""
+"An administrator may grow or shrink logical volumes without destroying data, "
+"unlike standard disk partitions. If the physical volumes in a volume group "
+"are on separate drives or RAID arrays then administrators may also spread a "
+"logical volume across the storage devices."
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:60
+#, no-c-format
+msgid ""
+"You may lose data if you shrink a logical volume to a smaller capacity than "
+"the data on the volume requires. To ensure maximum flexibility, create "
+"logical volumes to meet your current needs, and leave excess storage "
+"capacity unallocated. You may safely grow logical volumes to use unallocated "
+"space, as your needs dictate."
+msgstr ""
+
+#. Tag: title
+#: Understanding_LVM.xml:69
+#, no-c-format
+msgid "LVM and the Default Partition Layout"
+msgstr ""
+
+#. Tag: para
+#: Understanding_LVM.xml:71
+#, no-c-format
+msgid ""
+"By default, the installation process creates <filename class=\"partition\">/"
+"</filename> and swap partitions within LVM volumes, with a separate "
+"<filename>/boot</filename> partition."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-para-1.xml:5
+#, no-c-format
+msgid ""
+"This chapter explains the various methods available for upgrading your "
+"Fedora system."
+msgstr ""
+
+#. Tag: title
+#: Upgrade_common-section-1.xml:6
+#, no-c-format
+msgid "Determining Whether to Upgrade or Re-Install"
+msgstr ""
+
+#. Tag: primary
+#: Upgrade_common-section-1.xml:8 Upgrade_common-section-1.xml:103
+#, no-c-format
+msgid "<primary>upgrade</primary>"
+msgstr ""
+
+#. Tag: primary
+#: Upgrade_common-section-1.xml:11
+#, no-c-format
+msgid "re-installation"
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:13
+#, no-c-format
+msgid ""
+"While upgrading from Fedora 10 is supported, you are more likely to have a "
+"consistent experience by backing up your data and then installing this "
+"release of Fedora &PRODVER; over your previous Fedora installation."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:17
+#, no-c-format
+msgid ""
+"To upgrade from Fedora 10 you should bring your system up to date before "
+"performing the upgrade."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:22
+#, no-c-format
+msgid ""
+"It is not possible to upgrade directly from Fedora 9 to Fedora 11. To "
+"upgrade Fedora 9 to Fedora 11, upgrade to Fedora 10 first."
+msgstr ""
+
+#. Tag: emphasis
+#: Upgrade_common-section-1.xml:28
+#, no-c-format
+msgid ""
+"This recommended reinstallation method helps to ensure the best system "
+"stability possible."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:35
+#, no-c-format
+msgid ""
+"If you currently use Fedora 10, you can perform a traditional, installation "
+"program-based upgrade."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:39
+#, no-c-format
+msgid ""
+"However, before you chose to upgrade your system, there are a few things you "
+"should keep in mind:"
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:45
+#, no-c-format
+msgid ""
+"Individual package configuration files may or may not work after performing "
+"an upgrade due to changes in various configuration file formats or layouts."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:51
+#, no-c-format
+msgid ""
+"If you have one of Red Hat's layered products (such as the Cluster Suite) "
+"installed, it may need to be manually upgraded after the upgrade has been "
+"completed."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:57
+#, no-c-format
+msgid ""
+"Third party or ISV applications may not work correctly following the upgrade."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:63
+#, no-c-format
+msgid ""
+"Upgrading your system installs updated versions of the packages which are "
+"currently installed on your system."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:67
+#, no-c-format
+msgid ""
+"The upgrade process preserves existing configuration files by renaming them "
+"with an <filename>.rpmsave</filename> extension (for example, "
+"<filename>sendmail.cf.rpmsave</filename>). The upgrade process also creates "
+"a log of its actions in <filename>/root/upgrade.log</filename>."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:75
+#, no-c-format
+msgid ""
+"As software evolves, configuration file formats can change. It is very "
+"important to carefully compare your original configuration files to the new "
+"files before integrating your changes."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:83
+#, no-c-format
+msgid ""
+"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 hard drive(s). Mistakes do happen "
+"and can result in the loss of all of your data."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:89
+#, no-c-format
+msgid ""
+"Some upgraded packages may require the installation of other packages for "
+"proper operation. If you choose to customize your packages to upgrade, you "
+"may be required to resolve dependency problems. Otherwise, the upgrade "
+"procedure takes care of these dependencies, but it may need to install "
+"additional packages which are not on your system."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-1.xml:94
+#, no-c-format
+msgid ""
+"Depending on how you have partitioned your system, the upgrade program may "
+"prompt you to add an additional swap file. If the upgrade program does not "
+"detect a swap file that equals twice your RAM, it asks you if you would like "
+"to add a new swap file. If your system does not have a lot of RAM (less than "
+"256 MB), it is recommended that you add this swap file."
+msgstr ""
+
+#. Tag: primary
+#: Upgrade_common-section-1.xml:99
+#, no-c-format
+msgid "swap file"
+msgstr ""
+
+#. Tag: secondary
+#: Upgrade_common-section-1.xml:100
+#, no-c-format
+msgid "<secondary>upgrade</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: Upgrade_common-section-1.xml:104
+#, no-c-format
+msgid "adding a swap file"
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-2-note-1.xml:9
+#, no-c-format
+msgid ""
+"If the contents of your <filename>/etc/fedora-release</filename> file have "
+"been changed from the default, your Fedora installation may not be found "
+"when attempting an upgrade to Fedora &PRODVER;."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-2-note-1.xml:13
+#, no-c-format
+msgid ""
+"You can relax some of the checks against this file by booting with the "
+"following boot command:"
+msgstr ""
+
+#. Tag: screen
+#: Upgrade_common-section-2-note-1.xml:16
+#, no-c-format
+msgid "linux upgradeany"
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-2-note-1.xml:17
+#, no-c-format
+msgid ""
+"Use the <command>linux upgradeany</command> command if your Fedora "
+"installation was not given as an option to upgrade."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-2-para-1.xml:8
+#, no-c-format
+msgid ""
+"The <guilabel>Upgrade Examine</guilabel> screen appears if you have "
+"instructed the installation program to perform an upgrade."
+msgstr ""
+
+#. Tag: para
+#: Upgrade_common-section-2-para-2.xml:6
+#, no-c-format
+msgid ""
+"To perform an upgrade, select <guilabel>Perform an upgrade of an existing "
+"installation</guilabel>. Click <guibutton>Next</guibutton> when you are "
+"ready to begin your upgrade."
+msgstr ""
+
+#. Tag: title
+#: Upgrade_common-section-2-title.xml:8
+#, no-c-format
+msgid "Upgrading Your System"
+msgstr ""
+
+#. Tag: title
+#: Upgrade_common-title-1.xml:8
+#, no-c-format
+msgid "Upgrading Your Current System"
+msgstr ""
+
+#. Tag: para
+#: Upgrade-x86.xml:30
+#, no-c-format
+msgid ""
+"To re-install your system, select <guilabel>Perform a new Fedora "
+"installation</guilabel> and refer to <xref linkend=\"ch-guimode-x86\"/> for "
+"further instructions."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:9
+#, no-c-format
+msgid "Upgrading an Existing System"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:11
+#, no-c-format
+msgid ""
+"The installation system automatically detects any existing installation of "
+"Fedora. The upgrade process updates the existing system software with new "
+"versions, but does not remove any data from users' home directories. The "
+"existing partition structure on your hard drives does not change. Your "
+"system configuration changes only if a package upgrade demands it. Most "
+"package upgrades do not change system configuration, but rather install an "
+"additional configuration file for you to examine later."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:23
+#, no-c-format
+msgid "Upgrade Examine"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:25
+#, no-c-format
+msgid ""
+"If your system contains a Fedora or Red Hat Linux 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 <guibutton>Next</guibutton>."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:32
+#, no-c-format
+msgid "The upgrade screen"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:35
+#, no-c-format
+msgid "The upgrade screen."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:42
+#, no-c-format
+msgid "Manually Installed Software"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:43
+#, no-c-format
+msgid ""
+"Software you have installed manually on your existing Fedora or Red Hat "
+"Linux system may behave differently after an upgrade. You may need to "
+"manually reinstall or recompile this software after an upgrade to ensure it "
+"performs correctly on the updated system."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:53
+#, no-c-format
+msgid "Upgrading Using the Installer"
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:55
+#, no-c-format
+msgid "Installations are Recommended"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:56
+#, no-c-format
+msgid ""
+"In general, the Fedora Project recommends that you keep user data on a "
+"separate <filename class=\"partition\">/home</filename> partition and "
+"perform a fresh installation. For more information on partitions and how to "
+"set them up, refer to <xref linkend=\"s1-diskpartsetup-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:62
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: screen
+#: upgrading-fedora.xml:68
+#, no-c-format
+msgid ""
+"<command><![CDATA[rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\\n' > "
+"~/old-pkglist.txt]]></command>"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:70
+#, no-c-format
+msgid ""
+"After installation, consult this list to discover which packages you may "
+"need to rebuild or retrieve from non-Fedora software repositories."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:73
+#, no-c-format
+msgid "Next, make a backup of any system configuration data:"
+msgstr ""
+
+#. Tag: screen
+#: upgrading-fedora.xml:75
+#, no-c-format
+msgid ""
+"<command><![CDATA[su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc'\n"
+"su -c 'mv /tmp/etc-*.tar.gz /home']]></command>"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:77
+#, no-c-format
+msgid ""
+"Make a complete backup of any important data before performing an upgrade. "
+"Important data may include the contents of your entire <filename class="
+"\"directory\">/home</filename> 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."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:85
+#, no-c-format
+msgid "Storing Backups"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:86
+#, no-c-format
+msgid ""
+"Note that the above examples store backup materials in a <filename class="
+"\"directory\">/home</filename> directory. If your <filename class=\"directory"
+"\">/home</filename> directory is not a separate partition, <emphasis>you "
+"should not follow these examples verbatim!</emphasis> Store your backups on "
+"another device such as CD or DVD discs or an external hard disk."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:93
+#, no-c-format
+msgid ""
+"For more information on completing the upgrade process later, refer to <xref "
+"linkend=\"sn-finishing-upgrade\"/>."
+msgstr ""
+
+#. Tag: title
+#: upgrading-fedora.xml:98
+#, no-c-format
+msgid "Upgrading Boot Loader Configuration"
+msgstr ""
+
+#. Tag: secondary
+#: upgrading-fedora.xml:103
+#, no-c-format
+msgid "upgrading"
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:104
+#, no-c-format
+msgid ""
+"Your completed Fedora installation must be registered in the <indexterm> "
+"<primary>boot loader</primary> <seealso>GRUB</seealso> </indexterm> "
+"<firstterm>boot loader</firstterm> to boot properly. A boot loader is "
+"software on your machine that locates and starts the operating system. Refer "
+"to <xref linkend=\"s1-x86-bootloader\"/> for more information about boot "
+"loaders."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:113
+#, no-c-format
+msgid ""
+"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 <guilabel>Update boot loader "
+"configuration</guilabel>. This is the default behavior when you upgrade an "
+"existing Fedora or Red Hat Linux installation."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:121
+#, no-c-format
+msgid ""
+"<firstterm>GRUB</firstterm> is the standard boot loader for Fedora. If your "
+"machine uses another boot loader, such as <trademark>BootMagic</trademark>, "
+"<trademark>System Commander</trademark>, or the loader installed by "
+"Microsoft Windows, then the Fedora installation system cannot update it. In "
+"this case, select <guilabel>Skip boot loader updating</guilabel>. When the "
+"installation process completes, refer to the documentation for your product "
+"for assistance."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:132
+#, no-c-format
+msgid ""
+"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 "
+"<guilabel>Create new boot loader configuration</guilabel> to remove the "
+"existing boot loader and install GRUB."
+msgstr ""
+
+#. Tag: para
+#: upgrading-fedora.xml:142
+#, no-c-format
+msgid ""
+"After you make your selection, click <guibutton>Next</guibutton> to continue."
+msgstr ""
+
+#. Tag: title
+#: vnc_Installation_Chapter.xml:6
+#, no-c-format
+msgid "Installation Using VNC"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:7
+#, no-c-format
+msgid ""
+"Now that you have installed a VNC viewer application and selected a VNC mode "
+"for use in anaconda, you are ready to begin the installation."
+msgstr ""
+
+#. Tag: title
+#: vnc_Installation_Chapter.xml:14
+#, no-c-format
+msgid "Installation Example"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:15
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:26
+#, no-c-format
+msgid ""
+"Connect the laptop or other workstation to the target system using a "
+"crossover cable. If you are using regular patch cables, make sure you "
+"connect the two systems using a small hub or switch. Most recent Ethernet "
+"interfaces will automatically detect if they need to be crossover or not, so "
+"it may be possible to connect the two systems directly using a regular patch "
+"cable."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:42
+#, no-c-format
+msgid ""
+"Configure the VNC viewer system to use a RFC 1918 address with no gateway. "
+"This private network connection will only be used for the purpose of "
+"installation. Configure the VNC viewer system to be 192.168.100.1/24. If "
+"that address is in use, just pick something else in the RFC 1918 address "
+"space that is available to you."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:57
+#, no-c-format
+msgid "Start the installation on the target system."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:64
+#, no-c-format
+msgid "Booting the installation DVD or CD."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:70
+#, no-c-format
+msgid ""
+"If booting the installation media (CD or DVD), make sure <command>vnc</"
+"command> is passed as a boot parameter. To add the <command>vnc</command> "
+"parameter, you will need a console attached to the target system that allows "
+"you to interact with the boot process. Enter the following at the prompt:"
+msgstr ""
+
+#. Tag: screen
+#: vnc_Installation_Chapter.xml:91
+#, no-c-format
+msgid "boot: <userinput>linux vnc</userinput>"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:96
+#, no-c-format
+msgid "Boot over the network."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:101
+#, no-c-format
+msgid ""
+"If the target system is configured with a static IP address, add the "
+"<command>vnc</command> command to the kickstart file. If the target system "
+"is using DHCP, add <command>vncconnect=<replaceable>HOST</replaceable></"
+"command> to the boot arguments for the target system. HOST is the IP address "
+"or DNS host name of the VNC viewer system. Enter the following at the prompt:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:129
+#, no-c-format
+msgid ""
+"When prompted for the network configuration on the target system, assign it "
+"an available RFC 1918 address in the same network you used for the VNC "
+"viewer system. For example, 192.168.100.2/24."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:140
+#, no-c-format
+msgid ""
+"This IP address is only used during installation. You will have an "
+"opportunity to configure the final network settings, if any, later in the "
+"installer."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:152
+#, no-c-format
+msgid ""
+"Once the installer indicates it is starting anaconda, you will be instructed "
+"to connect to the system using the VNC viewer. Connect to the viewer and "
+"follow the graphical installation mode instructions found in the product "
+"documentation."
+msgstr ""
+
+#. Tag: title
+#: vnc_Installation_Chapter.xml:166
+#, no-c-format
+msgid "Kickstart Considerations"
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:167
+#, no-c-format
+msgid ""
+"If your target system will be booting over the network, VNC is still "
+"available. Just add the <command>vnc</command> 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."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:178
+#, no-c-format
+msgid ""
+"If you are using DHCP for the target system, the reverse "
+"<command>vncconnect</command> method may work better for you. Rather than "
+"adding the <command>vnc</command> boot parameter to the kickstart file, add "
+"the <command>vncconnect=<replaceable>HOST</replaceable></command> 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. See the next section for "
+"more details on using the vncconnect mode."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:194
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:205
+#, no-c-format
+msgid ""
+"In addition to passing the <command>vnc</command> boot parameter, you may "
+"also want to pass the <command>vncpassword</command> 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."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:220
+#, no-c-format
+msgid ""
+"Be sure to use a temporary password for the <command>vncpassword</command> "
+"option. It should not be a password you use on any systems, especially a "
+"real root password."
+msgstr ""
+
+#. Tag: para
+#: vnc_Installation_Chapter.xml:228
+#, no-c-format
+msgid ""
+"If you continue to have trouble, consider using the <command>vncconnect</"
+"command> parameter. In this mode of operation, you start the viewer on your "
+"system first telling it to listen for an incoming connection. Pass "
+"<command>vncconnect=<replaceable>HOST</replaceable></command> at the boot "
+"prompt and the installer will attempt to connect to the specified HOST "
+"(either a hostname or IP address)."
+msgstr ""
+
+#. Tag: title
+#: vnc_Modes_Chapter.xml:6
+#, no-c-format
+msgid "VNC Modes in Anaconda"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:7
+#, no-c-format
+msgid ""
+"Anaconda offers two modes for VNC installation. The mode you select will "
+"depend on the network configuration in your environment."
+msgstr ""
+
+#. Tag: title
+#: vnc_Modes_Chapter.xml:14
+#, no-c-format
+msgid "Direct Mode"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:15
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:25
+#, no-c-format
+msgid "Specify <command>vnc</command> as a boot argument."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:31
+#, no-c-format
+msgid ""
+"Specify the <command>vnc</command> command in the kickstart file used for "
+"installation."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:39
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: screen
+#: vnc_Modes_Chapter.xml:48
+#, no-c-format
+msgid ""
+"Running anaconda <replaceable>VERSION</replaceable>, the "
+"<replaceable>PRODUCT</replaceable> system installer - please wait..."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:51
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:60
+#, no-c-format
+msgid "There are some disadvantages to direct mode, including:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:67
+#, no-c-format
+msgid ""
+"Requires visual access to the system console to see the IP address and port "
+"to connect the VNC viewer to."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:74
+#, no-c-format
+msgid ""
+"Requires interactive access to the system console to complete the first "
+"stage of the installer."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:82
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: title
+#: vnc_Modes_Chapter.xml:91
+#, no-c-format
+msgid "Connect Mode"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:92
+#, no-c-format
+msgid ""
+"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."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:102
+#, no-c-format
+msgid ""
+"The VNC connect mode changes how VNC is started. Rather than anaconda "
+"starting up and waiting for you to connect, the VNC connect mode allows "
+"anaconda to automatically connect to your view. You won't need to know the "
+"IP address of the target system in this case."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:111
+#, no-c-format
+msgid ""
+"To activate the VNC connect mode, pass the <command>vncconnect</command> "
+"boot parameter:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:120
+#, no-c-format
+msgid ""
+"Replace HOST with your VNC viewer's IP address or DNS host name. Before "
+"starting the installation process on the target system, start up your VNC "
+"viewer and have it wait for an incoming connection."
+msgstr ""
+
+#. Tag: para
+#: vnc_Modes_Chapter.xml:128
+#, no-c-format
+msgid ""
+"Start the installation and when your VNC viewer displays the graphical "
+"installer, you are ready to go."
+msgstr ""
+
+#. Tag: title
+#: vnc_References_Chapter.xml:6
+#, no-c-format
+msgid "References"
+msgstr ""
+
+#. Tag: para
+#: vnc_References_Chapter.xml:10
+#, no-c-format
+msgid ""
+"VNC description at Wikipedia: <ulink url=\"http://en.wikipedia.org/wiki/Vnc"
+"\">http://en.wikipedia.org/wiki/Vnc</ulink>"
+msgstr ""
+
+#. Tag: para
+#: vnc_References_Chapter.xml:16
+#, no-c-format
+msgid ""
+"TightVNC: <ulink url=\"http://www.tightvnc.com/\">http://www.tightvnc.com/</"
+"ulink>"
+msgstr ""
+
+#. Tag: para
+#: vnc_References_Chapter.xml:22
+#, no-c-format
+msgid ""
+"RFC 1918 - Address Allocation for Private Networks: <ulink url=\"http://www."
+"ietf.org/rfc/rfc1918.txt\">http://www.ietf.org/rfc/rfc1918.txt</ulink>"
+msgstr ""
+
+#. Tag: para
+#: vnc_References_Chapter.xml:28
+#, no-c-format
+msgid ""
+"Anaconda boot options: <ulink url=\"http://fedoraproject.org/wiki/Anaconda/"
+"Options\">http://fedoraproject.org/wiki/Anaconda/Options</ulink>"
+msgstr ""
+
+#. Tag: para
+#: vnc_References_Chapter.xml:34
+#, no-c-format
+msgid ""
+"Kickstart documentation: <ulink url=\"http://fedoraproject.org/wiki/Anaconda/"
+"Kickstart\">http://fedoraproject.org/wiki/Anaconda/Kickstart</ulink>"
+msgstr ""
+
+#. Tag: title
+#: vnc_Viewer_Chapter.xml:6
+#, no-c-format
+msgid "VNC Viewer"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:7
+#, no-c-format
+msgid ""
+"Performing a VNC installation requires a VNC viewer running on your "
+"workstation or other terminal computer. Locations where you might want a VNC "
+"viewer installed:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:15
+#, no-c-format
+msgid "Your workstation"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:20
+#, no-c-format
+msgid "Laptop on a datacenter crash cart"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:26
+#, no-c-format
+msgid ""
+"VNC is open source software licensed under the GNU General Public License. "
+"Versions exist for Linux, Windows, and MacOS X. Here are some recommended "
+"VNC viewers:"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:34
+#, no-c-format
+msgid ""
+"<command>vncviewer</command> is available on <application>Red Hat Enterprise "
+"Linux</application> and <application>Fedora Linux</application> by "
+"installing the <filename>vnc</filename> package:"
+msgstr ""
+
+#. Tag: screen
+#: vnc_Viewer_Chapter.xml:43
+#, no-c-format
+msgid "# <userinput>yum install vnc</userinput>"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:47
+#, no-c-format
+msgid ""
+"TightVNC is available for Windows at <ulink url=\"http://www.tightvnc.com/"
+"\">http://www.tightvnc.com/</ulink>"
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:53
+#, no-c-format
+msgid ""
+"MacOS X includes built-in VNC support as of version 10.5. In the "
+"<application>Finder</application>, click the <guilabel>Go</guilabel> menu "
+"and choose <guilabel>Connect to Server</guilabel>. In the server address "
+"field, you can type <command>vnc://<replaceable>SERVER</replaceable>:"
+"<replaceable>DISPLAY</replaceable></command>, 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 <guilabel>Connect</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: vnc_Viewer_Chapter.xml:70
+#, no-c-format
+msgid ""
+"Once you have verified you have a VNC viewer available, it's time to start "
+"the installation."
+msgstr ""
+
+#. Tag: title
+#: vnc_VNC_Whitepaper.xml:6
+#, no-c-format
+msgid "Installing Through VNC"
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:9
+#, no-c-format
+msgid ""
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
+"environment and do not have a display, keyboard, or mouse. Additionally, a "
+"lot of these systems even lack the ability to connect a graphical display. "
+"Given that enterprise hardware rarely needs that ability at the physical "
+"system, this hardware configuration is acceptable."
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:26
+#, no-c-format
+msgid ""
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:42
+#, no-c-format
+msgid ""
+"Less screen real estate for creating user interfaces similar to those found "
+"in the graphical mode."
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:49
+#, no-c-format
+msgid "Difficult internationalization support."
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:54
+#, no-c-format
+msgid "Desire to maintain a single interactive installation code path."
+msgstr ""
+
+#. Tag: para
+#: vnc_VNC_Whitepaper.xml:61
+#, no-c-format
+msgid ""
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
+msgstr ""
+
+#. Tag: title
+#: Welcome-x86.xml:6
+#, no-c-format
+msgid "Welcome to Fedora"
+msgstr ""
+
+#. Tag: para
+#: Welcome-x86.xml:8
+#, no-c-format
+msgid ""
+"The <guilabel>Welcome</guilabel> screen does not prompt you for any input."
+msgstr ""
+
+#. Tag: para
+#: Welcome-x86.xml:14
+#, no-c-format
+msgid "Welcome to Fedora &PRODVER;"
+msgstr ""
+
+#. Tag: para
+#: Welcome-x86.xml:19
+#, no-c-format
+msgid "Click on the <guibutton>Next</guibutton> button to continue."
+msgstr ""
+
+#. Tag: para
+#: X86_Bios_Tip.xml:9
+#, no-c-format
+msgid ""
+"While partitioning your hard drive, keep in mind that the BIOS in some older "
+"systems cannot access more than the first 1024 cylinders on a hard drive. If "
+"this is the case, leave enough room for the <filename>/boot</filename> Linux "
+"partition on the first 1024 cylinders of your hard drive to boot Linux. The "
+"other Linux partitions can be after cylinder 1024."
+msgstr ""
+
+#. Tag: para
+#: X86_Bios_Tip.xml:13
+#, no-c-format
+msgid ""
+"In <command>parted</command>, 1024 cylinders equals 528MB. For more "
+"information, refer to:"
+msgstr ""
+
+#. Tag: screen
+#: X86_Bios_Tip.xml:16
+#, no-c-format
+msgid ""
+"<ulink url=\"http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html\">http://"
+"www.pcguide.com/ref/hdd/bios/sizeMB504-c.html</ulink>"
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:6
+#, no-c-format
+msgid ""
+"x86, AMD64, and <trademark class=\"registered\">Intel</trademark> 64 Boot "
+"Loader Configuration"
+msgstr ""
+
+#. Tag: primary
+#: X86_Bootloader.xml:8 X86_Bootloader.xml:11 X86_Bootloader.xml:26
+#: X86_Bootloader.xml:200 X86_Bootloader.xml:255 X86_Bootloader.xml:275
+#, no-c-format
+msgid "<primary>boot loader</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:12 X86_Bootloader.xml:19
+#, no-c-format
+msgid "<secondary>GRUB</secondary>"
+msgstr ""
+
+#. Tag: primary
+#: X86_Bootloader.xml:30
+#, no-c-format
+msgid "master boot record"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:32
+#, no-c-format
+msgid ""
+"To boot the system without boot media, you usually need to install a boot "
+"loader. A boot loader is the first software program that runs when a "
+"computer starts. It is responsible for loading and transferring control to "
+"the operating system kernel software. The kernel, in turn, initializes the "
+"rest of the operating system."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:39
+#, no-c-format
+msgid ""
+"If you install Fedora in text mode, the installer configures the bootloader "
+"automatically and you cannot customize bootloader settings during the "
+"installation process."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:42
+#, no-c-format
+msgid ""
+"GRUB (GRand Unified Bootloader), which is installed by default, is a very "
+"powerful boot loader. GRUB can load a variety of free operating systems, as "
+"well as proprietary operating systems with chain-loading (the mechanism for "
+"loading unsupported operating systems, such as DOS or Windows, by loading "
+"another boot loader)."
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:48
+#, no-c-format
+msgid "The GRUB boot menu"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:49
+#, no-c-format
+msgid ""
+"The GRUB menu defaults to being hidden, except on dual-boot systems. To show "
+"the GRUB menu during system boot, press and hold the <keycap>Shift</keycap> "
+"key before the kernel is loaded. (Any other key works as well but the "
+"<keycap>Shift</keycap> key is the safest to use.)"
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:57
+#, no-c-format
+msgid "Boot Loader Configuration"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:60
+#, no-c-format
+msgid "Configure how you would like to boot the system."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:74
+#, no-c-format
+msgid ""
+"If there are no other operating systems on your computer, or you are "
+"completely removing any other operating systems the installation program "
+"will install <application>GRUB</application> as your boot loader without any "
+"intervention. In that case you may continue on to <xref linkend=\"s1-"
+"pkgselection-x86\"/>."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:82
+#, no-c-format
+msgid ""
+"You may have a boot loader installed on your system already. An operating "
+"system may install its own preferred boot loader, or you may have installed "
+"a third-party boot loader.If your boot loader does not recognize Linux "
+"partitions, you may not be able to boot Fedora. Use <application>GRUB</"
+"application> as your boot loader to boot Linux and most other operating "
+"systems. Follow the directions in this chapter to install <application>GRUB</"
+"application>."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:96
+#, no-c-format
+msgid "If you install GRUB, it may overwrite your existing boot loader."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:101
+#, no-c-format
+msgid ""
+"By default, the installation program installs GRUB in the master boot record "
+"or <abbrev>MBR</abbrev>, of the device for the root file system. To decline "
+"installation of a new boot loader, unselect <guilabel>Install boot loader "
+"on /dev/sda</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:111
+#, no-c-format
+msgid ""
+"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!"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:120
+#, no-c-format
+msgid ""
+"If you have other operating systems already installed, Fedora attempts to "
+"automatically detect and configure <application>GRUB</application> to boot "
+"them. You may manually configure any additional operating systems if "
+"<application>GRUB</application> does not detect them."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:128
+#, no-c-format
+msgid ""
+"To add, remove, or change the detected operating system settings, use the "
+"options provided."
+msgstr ""
+
+#. Tag: guibutton
+#: X86_Bootloader.xml:133
+#, no-c-format
+msgid "<guibutton>Add</guibutton>"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:135
+#, no-c-format
+msgid ""
+"Select <guibutton>Add</guibutton> to include an additional operating system "
+"in GRUB."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:139
+#, no-c-format
+msgid ""
+"Select the disk partition which contains the bootable operating system from "
+"the drop-down list and give the entry a label. <application>GRUB</"
+"application> displays this label in its boot menu."
+msgstr ""
+
+#. Tag: guibutton
+#: X86_Bootloader.xml:149
+#, no-c-format
+msgid "Edit"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:151
+#, no-c-format
+msgid ""
+"To change an entry in the GRUB boot menu, select the entry and then select "
+"<guibutton>Edit</guibutton>."
+msgstr ""
+
+#. Tag: guibutton
+#: X86_Bootloader.xml:159
+#, no-c-format
+msgid "Delete"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:161
+#, no-c-format
+msgid ""
+"To remove an entry from the GRUB boot menu, select the entry and then select "
+"<guibutton>Delete</guibutton>."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:169
+#, no-c-format
+msgid ""
+"Select <guilabel>Default</guilabel> beside the preferred boot partition to "
+"choose your default bootable OS. You cannot move forward in the installation "
+"unless you choose a default boot image."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:176
+#, no-c-format
+msgid ""
+"The <guilabel>Label</guilabel> column lists what you must enter at the boot "
+"prompt, in non-graphical boot loaders, in order to boot the desired "
+"operating system."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:180
+#, no-c-format
+msgid ""
+"Once you have loaded the GRUB boot screen, use the arrow keys to choose a "
+"boot label or type <keycap>e</keycap> for edit. You are presented with a "
+"list of items in the configuration file for the boot label you have selected."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:185
+#, no-c-format
+msgid ""
+"Boot loader passwords provide a security mechanism in an environment where "
+"physical access to your server is available."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:189
+#, no-c-format
+msgid ""
+"If you are installing a boot loader, you should create a password to protect "
+"your system. Without a boot loader password, users with access to your "
+"system can pass options to the kernel which can compromise your system "
+"security. With a boot loader password in place, the password must first be "
+"entered before selecting any non-standard boot options. However, it is still "
+"possible for someone with physical access to the machine to boot from a "
+"diskette, CD-ROM, or USB media if the BIOS supports it. Security plans which "
+"include boot loader passwords should also address alternate boot methods."
+msgstr ""
+
+#. Tag: primary
+#: X86_Bootloader.xml:193
+#, no-c-format
+msgid "boot loader password"
+msgstr ""
+
+#. Tag: primary
+#: X86_Bootloader.xml:196
+#, no-c-format
+msgid "<primary>password</primary>"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:197
+#, no-c-format
+msgid "<secondary>boot loader</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:201
+#, no-c-format
+msgid "<secondary>password</secondary>"
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:205
+#, no-c-format
+msgid "GRUB Passwords Not Required"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:206
+#, no-c-format
+msgid ""
+"You may not require a <application>GRUB</application> password if your "
+"system only has trusted operators, or is physically secured with controlled "
+"console access. However, if an untrusted person can get physical access to "
+"your computer's keyboard and monitor, that person can reboot the system and "
+"access <application>GRUB</application>. A password is helpful in this case."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:218
+#, no-c-format
+msgid ""
+"If you choose to use a boot loader password to enhance your system security, "
+"be sure to select the checkbox labeled <guilabel>Use a boot loader password</"
+"guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:222
+#, no-c-format
+msgid "Once selected, enter a password and confirm it."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:226
+#, no-c-format
+msgid ""
+"<application>GRUB</application> stores the password in encrypted form, so it "
+"<emphasis>cannot</emphasis> be read or recovered. If you forget the boot "
+"password, boot the system normally and then change the password entry in the "
+"<filename>/boot/grub/grub.conf</filename> file. If you cannot boot, you may "
+"be able to use the \"rescue\" mode on the first Fedora installation disc to "
+"reset the GRUB password."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:236
+#, no-c-format
+msgid ""
+"If you do need to change the <application>GRUB</application> password, use "
+"the <command>grub-md5-crypt</command> utility. For information on using this "
+"utility, use the command <command>man grub-md5-crypt</command> in a terminal "
+"window to read the manual pages."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:244
+#, no-c-format
+msgid ""
+"To configure more advanced boot loader options, such as changing the drive "
+"order or passing options to the kernel, be sure <guilabel>Configure advanced "
+"boot loader options</guilabel> is selected before clicking <guibutton>Next</"
+"guibutton>."
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:249
+#, no-c-format
+msgid "Advanced Boot Loader Configuration"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:251
+#, no-c-format
+msgid ""
+"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:"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:256
+#, no-c-format
+msgid "<secondary>MBR</secondary>"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:260
+#, no-c-format
+msgid "installing boot loader on"
+msgstr ""
+
+#. Tag: primary
+#: X86_Bootloader.xml:263
+#, no-c-format
+msgid "OS/2 boot manager"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:267
+#, no-c-format
+msgid ""
+"The master boot record (MBR) — This is the recommended place to "
+"install a boot loader, unless the MBR already starts another operating "
+"system loader, such as System Commander. The MBR is a special area on your "
+"hard drive that is automatically loaded by your computer's BIOS, and is the "
+"earliest point at which the boot loader can take control of the boot "
+"process. If you install it in the MBR, when your machine boots, GRUB "
+"presents a boot prompt. You can then boot Fedora or any other operating "
+"system that you have configured the boot loader to boot."
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:276
+#, no-c-format
+msgid "installing on boot partition"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:277
+#, no-c-format
+msgid ""
+"The first sector of your boot partition — This is recommended if you "
+"are already using another boot loader on your system. In this case, your "
+"other boot loader takes control first. You can then configure that boot "
+"loader to start GRUB, which then boots Fedora."
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:282
+#, no-c-format
+msgid "GRUB as a Secondary Boot Loader"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:283
+#, no-c-format
+msgid ""
+"If you install GRUB as a secondary boot loader, you must reconfigure your "
+"primary boot loader whenever you install and boot from a new kernel. The "
+"kernel of an operating system such as Microsoft Windows does not boot in the "
+"same fashion. Most users therefore use GRUB as the primary boot loader on "
+"dual-boot systems."
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:296
+#, no-c-format
+msgid "Boot Loader Installation"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:299
+#, no-c-format
+msgid "Choose where to install a boot loader and how to configure it."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:306
+#, no-c-format
+msgid ""
+"If you have a RAID card, be aware that some BIOSes do not support booting "
+"from the RAID card. In cases such as these, the boot loader <emphasis>should "
+"not</emphasis> be installed on the MBR of the RAID array. Rather, the boot "
+"loader should be installed on the MBR of the same drive as the <filename>/"
+"boot/</filename> partition was created."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:310
+#, no-c-format
+msgid "If your system only uses Fedora, you should choose the MBR."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:314
+#, no-c-format
+msgid ""
+"Click the <guibutton>Change Drive Order</guibutton> 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."
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:332
+#, no-c-format
+msgid ""
+"Rescue mode provides the ability to boot a small Fedora environment entirely "
+"from boot media or some other boot method instead of the system's hard "
+"drive. There may be times when you are unable to get Fedora running "
+"completely enough to access files on your system's hard drive. Using rescue "
+"mode, you can access the files stored on your system's hard drive, even if "
+"you cannot actually run Fedora from that hard drive. If you need to use "
+"rescue mode, try the following method:"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:338
+#, no-c-format
+msgid ""
+"Using the CD-ROM to boot an x86, AMD64, or <trademark class=\"registered"
+"\">Intel</trademark> 64 system, type <userinput>linux rescue</userinput> at "
+"the installation boot prompt."
+msgstr ""
+
+#. Tag: title
+#: X86_Bootloader.xml:350
+#, no-c-format
+msgid "Alternative Boot Loaders"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Bootloader.xml:357
+#, no-c-format
+msgid "alternatives to"
+msgstr ""
+
+#. Tag: para
+#: X86_Bootloader.xml:360
+#, no-c-format
+msgid ""
+"<application>GRUB</application> is the default bootloader for Fedora, but is "
+"not the only choice. A variety of open-source and proprietary alternatives "
+"to <application>GRUB</application> are available to load Fedora, including "
+"<application>LILO</application>, <application>SYSLINUX</application>, "
+"<application>Acronis Disk Director Suite</application>, and "
+"<application>Apple Boot Camp</application>."
+msgstr ""
+
+#. Tag: title
+#: X86_Trouble_After_Grub.xml:9
+#, no-c-format
+msgid "Trouble With the Graphical GRUB Screen on an x86-based System?"
+msgstr ""
+
+#. Tag: tertiary
+#: X86_Trouble_After_Grub.xml:13
+#, no-c-format
+msgid "graphical GRUB screen"
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:15
+#, no-c-format
+msgid ""
+"If you are experiencing problems with GRUB, you may need to disable the "
+"graphical boot screen. To do this, become the root user and edit the "
+"<filename>/boot/grub/grub.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:19
+#, no-c-format
+msgid ""
+"Within the <filename>grub.conf</filename> file, comment out the line which "
+"begins with <computeroutput>splashimage</computeroutput> by inserting the "
+"<computeroutput>#</computeroutput> character at the beginning of the line."
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:24
+#, no-c-format
+msgid "Press <keycap>Enter</keycap> to exit the editing mode."
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:28
+#, no-c-format
+msgid ""
+"Once the boot loader screen has returned, type <command>b</command> to boot "
+"the system."
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:32
+#, no-c-format
+msgid ""
+"Once you reboot, the <filename>grub.conf</filename> file is reread and any "
+"changes you have made take effect."
+msgstr ""
+
+#. Tag: para
+#: X86_Trouble_After_Grub.xml:36
+#, no-c-format
+msgid ""
+"You may re-enable the graphical boot screen by uncommenting (or adding) the "
+"above line back into the <filename>grub.conf</filename> file."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-bootloader.xml:7
+#, no-c-format
+msgid "Remove Fedora entries from your bootloader"
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-bootloader.xml:9
+#, no-c-format
+msgid "Example only"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:12
+#, no-c-format
+msgid ""
+"These instructions assume that your system uses the <application>GRUB</"
+"application> bootloader. If you use a different bootloader (such as "
+"<application>LILO</application>) consult the documentation for that software "
+"to identify and remove Fedora entries from its list of boot targets and to "
+"ensure that your default operating system is correctly specified."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:17
+#, no-c-format
+msgid ""
+"At the command line, type <command>su -</command> and press "
+"<keycap>Enter</keycap>. When the system prompts you for the root password, "
+"type the password and press <keycap>Enter</keycap>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:22
+#, no-c-format
+msgid ""
+"Type <command>gedit /boot/grub/grub.conf</command> and press "
+"<keycap>Enter</keycap>. This opens the <filename>grub.conf</filename> file "
+"in the <application>gedit</application> text editor."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:27
+#, no-c-format
+msgid ""
+"A typical Fedora entry in the <filename>grub.conf</filename> file consists "
+"of four lines: <example> <title>Example Fedora entry in <filename>grub.conf</"
+"filename></title> <para> title Fedora (2.6.27.19-170.2.35.fc10.i686) </para> "
+"<para> root (hd0,1) </para> <para> kernel /vmlinuz-2.6.27.19-170.2.35.fc10."
+"i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet </para> "
+"<para> initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img </para> </example> "
+"Depending on the configuration of your system, there may be multiple Fedora "
+"entries in <filename>grub.conf</filename>, each corresponding to a different "
+"version of the Linux kernel. Delete each of the Fedora entries from the file."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:48
+#, no-c-format
+msgid ""
+"<filename>Grub.conf</filename> contains a line that specifies the default "
+"operating system to boot, in the format <literal>default=<replaceable>N</"
+"replaceable></literal> where <replaceable>N</replaceable> is a number equal "
+"to or greater than 0. If <replaceable>N</replaceable> is set to 0, "
+"<application>GRUB</application> will boot the first operating system in the "
+"list. If <replaceable>N</replaceable> is set to 1, it will boot the second "
+"operating system, and so forth."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:51
+#, no-c-format
+msgid ""
+"Identify the entry for the operating system that you want <application>GRUB</"
+"application> to boot by default and note its place in the order within the "
+"list."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:54
+#, no-c-format
+msgid ""
+"Make sure that the <literal>default=</literal> line contains the number "
+"<emphasis>one below</emphasis> the number of your chosen default operating "
+"system in the list."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-bootloader.xml:57
+#, no-c-format
+msgid ""
+"Save the updated <filename>grub.conf</filename> file and close "
+"<application>gedit</application>"
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand-lvm.xml:7
+#, no-c-format
+msgid "If you use LVM"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:9
+#, no-c-format
+msgid ""
+"Boot your computer from Linux live media and install <application>gparted</"
+"application> and <application>lvm2</application> if they are not already "
+"present."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand-lvm.xml:15
+#, no-c-format
+msgid "Create a new partition in the free space on the disk"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:22
+#, no-c-format
+msgid ""
+"<application>GParted</application> displays the partitions on your system "
+"both as a graph and as a table. The space freed by removing Fedora is "
+"labeled <literal>unallocated</literal>. Right-click on the unallocated space "
+"and select <guilabel>New</guilabel>. Accept the defaults and "
+"<application>GParted</application> will create a new partition that fills "
+"the space available on the drive."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:27
+#, no-c-format
+msgid ""
+"Click <guilabel>Apply</guilabel>. <application>GParted</application> writes "
+"the changes to your hard drive. Take note of the name of the partition that "
+"you just created, and the name of the device that holds the partition. For "
+"example, you may have created <filename>/dev/sda3</filename> on device "
+"<filename>/dev/sda</filename>."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand-lvm.xml:35
+#, no-c-format
+msgid "Change the partition type identifier"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:37
+#, no-c-format
+msgid ""
+"<application>Fdisk</application> is a partitioning tool capable of preparing "
+"partitions for LVM. At a command line, type <command>fdisk "
+"<replaceable>device</replaceable></command> and press <keycap>Enter</"
+"keycap>, where <replaceable>device</replaceable> is the name of the device "
+"on which you just created a partition. For example, <command>fdisk /dev/sda</"
+"command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:42
+#, no-c-format
+msgid ""
+"At the prompt <prompt>Command (m for help):</prompt>, press <keycap>T</"
+"keycap> and <keycap>Enter</keycap> to use <application>fdisk</application> "
+"to change a partition type."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:47
+#, no-c-format
+msgid ""
+"At the prompt <prompt>Partition number (1-4):</prompt>, type the number of "
+"the partition that you just created. For example, if you just created "
+"partition <filename>/dev/sda3</filename>, type the number <literal>3</"
+"literal> and press <keycap>Enter</keycap>. This identifies the partition "
+"whose type <application>fdisk</application> will change."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:52
+#, no-c-format
+msgid ""
+"At the prompt <prompt>Hex code (type L to list codes):</prompt>, type the "
+"code <literal>8e</literal> and press <keycap>Enter</keycap>. This is the "
+"code for a Linux LVM partition."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:57
+#, no-c-format
+msgid ""
+"At the prompt <prompt>Command (m for help):</prompt>, press <keycap>W</"
+"keycap> and <keycap>Enter</keycap>. <application>Fdisk</application> writes "
+"the new type code to the partition and exits."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand-lvm.xml:65
+#, no-c-format
+msgid "Expand the volume group"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:67
+#, no-c-format
+msgid ""
+"At the command prompt, type <command>lvm</command> and press <keycap>Enter</"
+"keycap> to start the <application>lvm2</application> tool."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:72
+#, no-c-format
+msgid ""
+"At the <prompt>lvm></prompt> prompt, type <command>pvcreate "
+"<replaceable>partition</replaceable></command> and press <keycap>Enter</"
+"keycap>, where <replaceable>partition</replaceable> is the partition that "
+"you recently created. For example, <command>pvcreate /dev/sda3</command>. "
+"This creates <filename>/dev/sda3</filename> as a physical volume in LVM."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:77
+#, no-c-format
+msgid ""
+"At the <prompt>lvm></prompt> prompt, type <command>vgextend "
+"<replaceable>VolumeGroup</replaceable> <replaceable>partition</replaceable></"
+"command> and press <keycap>Enter</keycap>, where <replaceable>VolumeGroup</"
+"replaceable> is the LVM volume group on which Linux is installed and "
+"<replaceable>partition</replaceable> is the partition that you recently "
+"created. For example, if Linux is installed on <filename>/dev/VolumeGroup00</"
+"filename>, you would type <command>vgextend /dev/VolumeGroup00 /dev/sda3</"
+"command> to extend that volume group to include the physical volume at "
+"<filename>/dev/sda3</filename>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:82
+#, no-c-format
+msgid ""
+"At the <prompt>lvm></prompt> prompt, type <command>lvextend -l +100%FREE "
+"<replaceable>LogVol</replaceable></command> and press <keycap>Enter</"
+"keycap>, where <replaceable>LogVol</replaceable> is the logical volume that "
+"contains your Linux filesystem. For example, to extend <filename>LogVol00</"
+"filename> to fill the newly-available space in its volume group, "
+"<filename>VolGroup00</filename>, type <command>lvextend -l +100%FREE /dev/"
+"VolGroup00/LogVol00</command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:87
+#, no-c-format
+msgid ""
+"At the <prompt>lvm></prompt> prompt, type <command>exit</command> and "
+"press <keycap>Enter</keycap> to exit <application>lvm2</application>"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:94
+#, no-c-format
+msgid ""
+"Type <command>e2fsck <replaceable>LogVol</replaceable></command> at the "
+"command line and press <keycap>Enter</keycap>, where <replaceable>LogVol</"
+"replaceable> is the logical volume that you just resized. For example, if "
+"you just resized <filename>/dev/VolumeGroup00/LogVol00</filename>, you would "
+"type <command>e2fsck /dev/VolumeGroup00/LogVol00</command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:97
+#, no-c-format
+msgid "Linux now checks the file system of the newly-resized logical volume."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:102
+#, no-c-format
+msgid ""
+"When the file system check finishes, type <command>resize2fs "
+"<replaceable>LogVol</replaceable></command> at a command line and press "
+"<keycap>Enter</keycap>, where <replaceable>LogVol</replaceable> is the "
+"partition that you just resized. For example, if you just resized <filename>/"
+"dev/VolumeGroup00/LogVol00</filename>, you would type "
+"<command>resize2fs /dev/VolumeGroup00/LogVol00</command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-lvm.xml:105
+#, no-c-format
+msgid ""
+"Linux now resizes your file system to fill the newly-resized logical volume."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand-nolvm.xml:7
+#, no-c-format
+msgid "If you do not use LVM"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:9
+#, no-c-format
+msgid ""
+"Boot your computer from Linux live media, and install <application>gparted</"
+"application> if it is not already present."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:19
+#, no-c-format
+msgid ""
+"<application>GParted</application> displays the partitions on your system "
+"both as a graph and as a table. Click on the partition that you want to "
+"extend to use the space freed by removing Fedora, and click the "
+"<guilabel>Resize/Move</guilabel> button."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:24
+#, no-c-format
+msgid ""
+"A new dialog opens, allowing you to specify a new size for the partition by "
+"entering it as numbers, or by dragging the sides of the graphical "
+"representation of the partition so that it fills the available space. Click "
+"the <guilabel>Resize/Move</guilabel> button in this dialog to confirm your "
+"choice."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:29
+#, no-c-format
+msgid ""
+"Back in the main <application>GParted</application> window, click "
+"<guilabel>Apply</guilabel>. Take note of the name of the partition that you "
+"just resized, for example, <filename>/dev/sda3</filename>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:34
+#, no-c-format
+msgid ""
+"When <application>GParted</application> finishes resizing the partition, "
+"type <command>e2fsck <replaceable>partition</replaceable></command> at a "
+"command line and press <keycap>Enter</keycap>, where <replaceable>partition</"
+"replaceable> is the partition that you just resized. For example, if you "
+"just resized <filename>/dev/sda3</filename>, you would type "
+"<command>e2fsck /dev/sda3</command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:37
+#, no-c-format
+msgid "Linux now checks the file system of the newly-resized partition."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:42
+#, no-c-format
+msgid ""
+"When the file system check finishes, type <command>resize2fs "
+"<replaceable>partition</replaceable></command> at a command line and press "
+"<keycap>Enter</keycap>, where <replaceable>partition</replaceable> is the "
+"partition that you just resized. For example, if you just resized <filename>/"
+"dev/sda3</filename>, you would type <command>resize2fs /dev/sda3</"
+"command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand-nolvm.xml:45
+#, no-c-format
+msgid "Linux now resizes your file system to fill the newly-resized partition."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-expand.xml:7
+#, no-c-format
+msgid "Make space available to your operating system"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand.xml:9
+#, no-c-format
+msgid ""
+"This step is not required to remove Fedora from your computer. However, if "
+"you skip this step, you will leave part of your hard drive's storage "
+"capacity unusable by your other Linux operating system. Depending on your "
+"configuration, this might be a a significant portion of the storage capacity "
+"of the drive."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand.xml:14
+#, no-c-format
+msgid ""
+"To carry out this step, you require live media for a Linux distribution, for "
+"example, the Fedora Live CD or the Knoppix DVD."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-expand.xml:18
+#, no-c-format
+msgid ""
+"The method to make the space freed by removing the Fedora partitions "
+"available to your other Linux operating system differs, depending on whether "
+"your chosen operating system is installed on disk partitions configured to "
+"use Logical Volume Management (LVM) or not."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux-partitions.xml:7
+#, no-c-format
+msgid "Remove Fedora partitions"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-partitions.xml:9
+#, no-c-format
+msgid "Boot the Linux version that you want to keep on your computer."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-partitions.xml:19
+#, no-c-format
+msgid ""
+"<application>GParted</application> displays the partitions that it detects "
+"on your computer, both as a graph and as a table."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux-partitions.xml:22
+#, no-c-format
+msgid ""
+"Right-click the Fedora partitions, then select <guilabel>Delete</guilabel>."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Linux.xml:7
+#, no-c-format
+msgid "Your computer dual-boots Fedora and a different Linux distribution"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Linux.xml:9
+#, no-c-format
+msgid ""
+"Because of the differences between the many different Linux distributions, "
+"these instructions are a general guide only. Specific details will vary "
+"according to your chosen distribution and the configuration of your "
+"particular computer. This example uses <application>GParted</application> as "
+"a partition editor and <application>gedit</application> as a text editor, "
+"but many other tools are available to perform these tasks. To follow these "
+"instructions exactly as written, install <application>GParted</application> "
+"and <application>gedit</application>."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Mac.xml:6
+#, no-c-format
+msgid "Your computer dual-boots Fedora and Mac OS X"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:7
+#, no-c-format
+msgid ""
+"The procedure to remove Fedora from a system that dual-boots Fedora and Mac "
+"OS X varies depending on whether you have installed <application>Boot Camp</"
+"application> on your computer:"
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Mac.xml:11
+#, no-c-format
+msgid "You are not using <application>Boot Camp</application> on your computer"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:13
+#, no-c-format
+msgid ""
+"Open the <application>Disk Utility</application> in <filename>/Applications/"
+"Utilities</filename>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:18
+#, no-c-format
+msgid "Select the entry on the left for the disk volume containing Fedora."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:23
+#, no-c-format
+msgid ""
+"Click the <guilabel>Partition</guilabel> tab on the right side of the dialog."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:28
+#, no-c-format
+msgid ""
+"Select the Fedora partitions and click the minus button below the partition "
+"layout diagram."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:33
+#, no-c-format
+msgid "Resize your OS X partition to include the newly freed space."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Mac.xml:40
+#, no-c-format
+msgid "You are using <application>Boot Camp</application> on your computer"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:42
+#, no-c-format
+msgid ""
+"Open the <application>Boot Camp Assistant</application> in <filename>/"
+"Applications/Utilities</filename>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:47
+#, no-c-format
+msgid ""
+"Select <guilabel>Create or remove a Windows partition</guilabel> and click "
+"<guilabel>Next</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:52
+#, no-c-format
+msgid ""
+"If your computer has a single internal disk, click <guilabel>Restore</"
+"guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Mac.xml:57
+#, no-c-format
+msgid ""
+"If your computer has multiple internal disks, select the Linux disk, and "
+"then select <guilabel>Restore to a single Mac OS partition</guilabel>. Click "
+"<guilabel>Continue</guilabel>."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-msdos.xml:6
+#, no-c-format
+msgid "Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:7
+#, no-c-format
+msgid ""
+"In DOS and Windows, use the Windows <command>fdisk</command> utility to "
+"create a new MBR with the <wordasword>undocumented</wordasword> flag "
+"<command>/mbr</command>. This <emphasis>ONLY</emphasis> rewrites the MBR to "
+"boot the primary DOS partition. The command should look like the following:"
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-msdos.xml:11
+#, no-c-format
+msgid "<command>fdisk /mbr</command>"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:12
+#, no-c-format
+msgid ""
+"If you need to remove Linux from a hard drive and have attempted to do this "
+"with the default DOS (Windows) <command>fdisk</command>, you will experience "
+"the <emphasis>Partitions exist but they do not exist</emphasis> problem. The "
+"best way to remove non-DOS partitions is with a tool that understands "
+"partitions other than DOS."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:16
+#, no-c-format
+msgid ""
+"To begin, insert the Fedora CD #1 and boot your system. Once you have booted "
+"off the CD, a boot prompt appears. At the boot prompt, type: "
+"<userinput>linux rescue</userinput>. This starts the rescue mode program."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:19
+#, no-c-format
+msgid ""
+"You are prompted for your keyboard and language requirements. Enter these "
+"values as you would during the installation of Fedora."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:22
+#, no-c-format
+msgid ""
+"Next, a screen appears telling you that the program attempts to find a "
+"Fedora install to rescue. Select <guibutton>Skip</guibutton> on this screen."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:25
+#, no-c-format
+msgid ""
+"After selecting <guibutton>Skip</guibutton>, you are given a command prompt "
+"where you can access the partitions you would like to remove."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:28
+#, no-c-format
+msgid ""
+"First, type the command <command>list-harddrives</command>. This command "
+"lists all hard drives on your system that are recognizable by the "
+"installation program, as well as their sizes in megabytes."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:34
+#, no-c-format
+msgid ""
+"Be careful to remove only the necessary Fedora partitions. Removing other "
+"partitions could result in data loss or a corrupted system environment."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:38
+#, no-c-format
+msgid ""
+"To remove partitions, use the partitioning utility <command>parted</"
+"command>. Start <command>parted</command>, where <replaceable>/dev/hda</"
+"replaceable> is the device on which to remove the partition:"
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-msdos.xml:41
+#, no-c-format
+msgid "parted /dev/hda"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:42
+#, no-c-format
+msgid ""
+"Using the <command>print</command> command, view the current partition table "
+"to determine the minor number of the partition to remove:"
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-msdos.xml:45
+#, no-c-format
+msgid "print"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:46
+#, no-c-format
+msgid ""
+"The <command>print</command> command also displays the partition's type "
+"(such as linux-swap, ext2, ext3, ext4 and so on). Knowing the type of the "
+"partition helps you in determining whether to remove the partition."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:49
+#, no-c-format
+msgid ""
+"Remove the partition with the command <command>rm</command>. For example, to "
+"remove the partition with minor number 3:"
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-msdos.xml:52
+#, no-c-format
+msgid "rm 3"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:56
+#, no-c-format
+msgid ""
+"The changes start taking place as soon as you press [Enter], so review the "
+"command before committing to it."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:60
+#, no-c-format
+msgid ""
+"After removing the partition, use the <command>print</command> command to "
+"confirm that it is removed from the partition table."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:63
+#, no-c-format
+msgid ""
+"Once you have removed the Linux partitions and made all of the changes you "
+"need to make, type <command>quit</command> to quit <command>parted</command>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-msdos.xml:66
+#, no-c-format
+msgid ""
+"After quitting <command>parted</command>, type <command>exit</command> at "
+"the boot prompt to exit rescue mode and reboot your system, instead of "
+"continuing with the installation. The system should reboot automatically. If "
+"it does not, you can reboot your computer using <keycombo><keycap>Control</"
+"keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo> ."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall.xml:5
+#, no-c-format
+msgid "Removing Fedora"
+msgstr ""
+
+#. Tag: primary
+#: X86_Uninstall.xml:9
+#, no-c-format
+msgid "uninstalling"
+msgstr ""
+
+#. Tag: primary
+#: X86_Uninstall.xml:12
+#, no-c-format
+msgid "removing"
+msgstr ""
+
+#. Tag: secondary
+#: X86_Uninstall.xml:13
+#, no-c-format
+msgid "Fedora"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:17
+#, no-c-format
+msgid ""
+"We respect your freedom to choose an operating system for your computer. "
+"This section explains how to uninstall Fedora."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall.xml:22
+#, no-c-format
+msgid "These instructions may destroy data!"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:25
+#, no-c-format
+msgid ""
+"If you have data from Fedora that you want to keep, back it up before you "
+"proceed. Write your data to CD, DVD, external hard disk, or other storage "
+"device."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:28
+#, no-c-format
+msgid ""
+"As a precaution, also back up data from any other operating systems that are "
+"installed on the same computer. Mistakes do happen and can result in the "
+"loss of all your data."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:31
+#, no-c-format
+msgid ""
+"If you back up data from Fedora to be used later in another operating "
+"system, make sure that the storage medium or device is readable by that "
+"other operating system. For example, without extra third-party software, "
+"Microsoft Windows cannot read an external hard drive that you have formatted "
+"with Fedora to use the ext2, ext3, or ext4 file system."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:36
+#, no-c-format
+msgid ""
+"To uninstall Fedora from your x86-based system, you must remove the Fedora "
+"boot loader information from your master boot record (MBR) and remove any "
+"partitions that contain the operating system. The method for removing Fedora "
+"from your computer varies, depending on whether Fedora is the only operating "
+"system installed on the computer, or whether the computer is configured to "
+"dual-boot Fedora and another operating system."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:40
+#, no-c-format
+msgid ""
+"These instructions cannot cover every possible computer configuration. If "
+"your computer is configured to boot three or more operating systems, or has "
+"a highly-customized partition scheme, use the following sections as a "
+"general guide to partition removal with the various tools described. In "
+"these situations, you will also need to learn to configure your chosen "
+"bootloader. See <xref linkend=\"ch-grub\"/> for a general introduction to "
+"the subject, but detailed instructions are beyond the scope of this document."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall.xml:45
+#, no-c-format
+msgid "Legacy versions of Microsoft operating systems"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:46
+#, no-c-format
+msgid ""
+"<application>Fdisk</application>, the disk partitioning tool provided with "
+"MS-DOS and Microsoft Windows, is unable to remove the file systems used by "
+"Fedora. MS-DOS and versions of Windows prior to Windows XP (except for "
+"Windows 2000) have no other means of removing or modifying partitions. Refer "
+"to <xref linkend=\"sn-x86-uninstall-legacy\"/> for alternative removal "
+"methods for use with MS-DOS and these versions of Windows."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall.xml:54
+#, no-c-format
+msgid "Your computer dual-boots Fedora and another operating system"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall.xml:55
+#, no-c-format
+msgid ""
+"If your computer is configured to dual-boot Fedora and another operating "
+"system, removing Fedora without removing the partitions containing the other "
+"operating system and its data is more complicated. Specific instructions for "
+"a number of operating systems are set out below. To keep neither Fedora nor "
+"the other operating system, follow the steps described for a computer with "
+"only Fedora installed:"
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall.xml:60
+#, no-c-format
+msgid ""
+"Your computer dual-boots Fedora and a Microsoft Windows operating system"
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-single.xml:6
+#, no-c-format
+msgid "Fedora is the only operating system on the computer"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:8
+#, no-c-format
+msgid ""
+"If Fedora is the only operating system on your computer, use the "
+"installation media for the replacement operating system to remove Fedora. "
+"Examples of installation media include the Windows XP installation CD, "
+"Windows Vista installation DVD, Mac OS X installation CDs or DVD, or the "
+"installation CD, CDs, or DVD of another Linux distribution."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:12
+#, no-c-format
+msgid ""
+"Note that some manufacturers of factory-built computers pre-installed with "
+"Microsoft Windows do not supply the Windows installation CD or DVD with the "
+"computer. The manufacturer may instead have supplied their own \"system "
+"restore disk\", or have included software with the computer that allowed you "
+"to create your own \"system restore disk\" when you first started the "
+"computer. In some cases, the system restore software is stored on a separate "
+"partition on the system's hard drive. If you cannot identify the "
+"installation media for an operating system that was pre-installed on your "
+"computer, consult the documentation supplied with the machine, or contact "
+"the manufacturer."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:16
+#, no-c-format
+msgid ""
+"When you have located the installation media for your chosen operating "
+"system:"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:22
+#, no-c-format
+msgid "Back up any data that you want to keep."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:27
+#, no-c-format
+msgid "Shut down the computer."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:32
+#, no-c-format
+msgid ""
+"Boot your computer with the installation disk for the replacement operating "
+"system."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:37
+#, no-c-format
+msgid ""
+"Follow the prompts presented during the installation process. Windows, OS X, "
+"and most Linux installation disks allow you to manually partition your hard "
+"drive during the installation process, or will offer you the option to "
+"remove all partitions and start with a fresh partition scheme. At this "
+"point, remove any existing partitions that the installation software detects "
+"or allow the installer to remove the partitions automatically. \"System "
+"restore\" media for computers pre-installed with Microsoft Windows might "
+"create a default partition layout automatically without input from you."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-single.xml:41
+#, no-c-format
+msgid ""
+"If your computer has system restore software stored on a partition on a hard "
+"drive, take care when removing partitions while installing an operating "
+"system from other media. Under these circumstances, you could destroy the "
+"partition holding the system restore software."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Windows-2000XP2003.xml:6
+#, no-c-format
+msgid "Windows 2000, Windows Server 2000, Windows XP, and Windows Server 2003"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:9
+#, no-c-format
+msgid ""
+"This procedure relies on the <application>Windows Recovery Console</"
+"application> that loads from the Windows installation disk, so you will not "
+"be able to complete the procedure without access to this disk. If you start "
+"this procedure and do not complete it, you could leave your computer in a "
+"condition where you cannot boot it. The \"system restore disk\" supplied "
+"with some factory-built computers that are sold with Windows pre-installed "
+"on them might not include the <application>Windows Recovery Console</"
+"application>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:12
+#, no-c-format
+msgid ""
+"During the process outlined in these instructions, the <application>Windows "
+"Recovery Console</application> will prompt you for the Administrator "
+"password for your Windows system. Do not follow these instructions unless "
+"you know the Administrator password for your system or are certain that an "
+"Administrator password has never been created, even by the computer "
+"manufacturer."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:25
+#, no-c-format
+msgid ""
+"Click <guilabel>Start</guilabel>><guilabel>Run...</guilabel>, type "
+"<command>diskmgmt.msc</command> and press <keycap>Enter</keycap>. The "
+"<application>Disk Management</application> tool opens."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:43
+#, no-c-format
+msgid ""
+"The <application>diskpart</application> tool used in this step is installed "
+"as part of the Windows XP and Windows 2003 operating systems. If you are "
+"performing this step on a computer running Windows 2000 or Windows Server "
+"2000, you can download a version of <application>diskpart</application> for "
+"your operating system from the Microsoft website."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:48
+#, no-c-format
+msgid ""
+"Click <guilabel>Start</guilabel>><guilabel>Run...</guilabel>, type "
+"<command>diskpart</command> and press <keycap>Enter</keycap>. A command "
+"window appears."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:53
+#, no-c-format
+msgid ""
+"Type <command>list volume</command> and press <keycap>Enter</keycap>. "
+"<application>Diskpart</application> displays a list of the partitions on "
+"your system with a volume number, its drive letter, volume label, filesystem "
+"type, and size. Identify the Windows partition that you would like to use to "
+"occupy the space vacated on your hard drive by Fedora and take note of its "
+"volume number (for example, your Windows <filename>C:</filename> drive might "
+"be \"Volume 0\")."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:58
+#, no-c-format
+msgid ""
+"Type <command>select volume <replaceable>N</replaceable></command> (where "
+"<replaceable>N</replaceable> is the volume number for the Windows partition "
+"that you want to extend) and press <keycap>Enter</keycap>. Now type "
+"<command>extend</command> and press <keycap>Enter</keycap>. "
+"<application>Diskpart</application> now extends your chosen partition to "
+"fill the remaining space on your hard drive. It will notify you when the "
+"operation is complete."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:66
+#, no-c-format
+msgid ""
+"In the the <literal>Disk Management</literal> window, right-click on disk "
+"space that Windows labels as <literal>unallocated</literal> and select "
+"<literal>New Partition</literal> from the menu. The <application>New "
+"Partition Wizard</application> starts."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:71
+#, no-c-format
+msgid ""
+"Follow the prompts presented by the <application>New Partition Wizard</"
+"application>. If you accept the default options, the tool will create a new "
+"partition that fills all available space on the hard drive, assigns it the "
+"next available drive letter, and formats it with the NTFS file system."
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-Windows-2000XP2003.xml:82
+#, no-c-format
+msgid "<prompt>Press any key to boot from CD</prompt>"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:86
+#, no-c-format
+msgid ""
+"When the <literal>Welcome to Setup</literal> screen appears, you can start "
+"the <application>Windows Recovery Console</application>. The procedure is "
+"slightly different on different versions of Windows:"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:91
+#, no-c-format
+msgid ""
+"On Windows 2000 and Windows Server 2000, press the <keycap>R</keycap> key, "
+"then the <keycap>C</keycap> key."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:96
+#, no-c-format
+msgid ""
+"On Windows XP and Windows Server 2003, press the <keycap>R</keycap> key."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:103
+#, no-c-format
+msgid ""
+"The <application>Windows Recovery Console</application> scans your hard "
+"drives for Windows installations, and assigns a number to each one. It "
+"displays a list of Windows installations and prompts you to select one. Type "
+"the number corresponding to the Windows installation that you want to "
+"restore."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:108
+#, no-c-format
+msgid ""
+"The <application>Windows Recovery Console</application> prompts you for the "
+"Administrator password for your Windows installation. Type the Administrator "
+"password and press the <keycap>Enter</keycap> key. If there is no "
+"administrator password for this system, press only the <keycap>Enter</"
+"keycap> key."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:113
+#, no-c-format
+msgid ""
+"At the prompt, type the command <command>fixmbr</command> and press the "
+"<keycap>Enter</keycap>. The <application>fixmbr</application> tool now "
+"restores the Master Boot Record for the system."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-2000XP2003.xml:118
+#, no-c-format
+msgid ""
+"When the prompt reappears, type <command>exit</command> and press the "
+"<keycap>Enter</keycap> key."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Windows-add-title-1.xml:5
+#, no-c-format
+msgid "Adding a new Windows partition"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-bootloader-para-1.xml:5
+#, no-c-format
+msgid "Restore the Windows bootloader"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-bootloader-para-2.xml:5
+#, no-c-format
+msgid ""
+"Insert the Windows installation disk and restart your computer. As your "
+"computer starts, the following message will appear on the screen for a few "
+"seconds:"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-bootloader-para-3.xml:5
+#, no-c-format
+msgid ""
+"Press any key while the message is still showing and the Windows "
+"installation software will load."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-bootloader-para-4.xml:5
+#, no-c-format
+msgid "Your computer will restart and boot your Windows operating system."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-extend-note-1.xml:6
+#, no-c-format
+msgid ""
+"This step is not required to remove Fedora from your computer. However, if "
+"you skip this step, you will leave part of your hard drive's storage "
+"capacity unusable by Windows. Depending on your configuration, this might be "
+"a a significant portion of the storage capacity of the drive."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-extend-para-1.xml:5
+#, no-c-format
+msgid ""
+"Enable Windows to use the space on your hard drive vacated by Fedora "
+"(optional)"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-extend-para-2.xml:5
+#, no-c-format
+msgid ""
+"Decide whether to extend an existing Windows partition to use the extra "
+"space, or create a new Windows partition in that space. If you create new a "
+"Windows partition, Windows will allocate a new drive letter to it and will "
+"interact with it as if it is a separate hard drive."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Windows-extend-title-1.xml:5
+#, no-c-format
+msgid "Extending an existing Windows partition"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-remove-para-1.xml:5
+#, no-c-format
+msgid "Remove the Fedora partitions"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-remove-para-2.xml:5
+#, no-c-format
+msgid "Boot your computer into your Microsoft Windows environment."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-remove-para-3.xml:5
+#, no-c-format
+msgid ""
+"The tool displays a graphical representation of your disk, with bars "
+"representing each partition. The first partition is usually labeled "
+"<literal>NTFS</literal> and corresponds to your <filename>C:</filename> "
+"drive. At least two Fedora partitions will be visible. Windows will not "
+"display a file system type for these partitions, but may allocate drive "
+"letters to some of them."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-remove-para-4.xml:5
+#, no-c-format
+msgid ""
+"Right-click on one of the Fedora partitions, then click <guilabel>Delete "
+"Partition</guilabel> and click <guilabel>Yes</guilabel> to confirm the "
+"deletion. Repeat this process for the other Fedora partitions on your "
+"system. As you delete partitions, Windows labels the space on the hard drive "
+"previously occupied by those partitions as <literal>unallocated</literal>."
+msgstr ""
+
+#. Tag: title
+#: X86_Uninstall-Windows-Vista2008.xml:6
+#, no-c-format
+msgid "Windows Vista and Windows Server 2008"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:9
+#, no-c-format
+msgid ""
+"This procedure relies on the <application>Windows Recovery Environment</"
+"application> that loads from the Windows installation disk and you will not "
+"be able to complete the procedure without access to this disk. If you start "
+"this procedure and do not complete it, you could leave your computer in a "
+"condition where you cannot boot it. The \"system restore disk\" supplied "
+"with some factory-built computers that are sold with Windows pre-installed "
+"on them might not include the <application>Windows Recovery Environment</"
+"application>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:22
+#, no-c-format
+msgid ""
+"Click <guilabel>Start</guilabel> then type <command>diskmgmt.msc</command> "
+"into the <guilabel>Start Search</guilabel> box and press <keycap>Enter</"
+"keycap>. The <application>Disk Management</application> tool opens."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:40
+#, no-c-format
+msgid ""
+"In the <application>Disk Management</application> window, right-click on the "
+"Windows partition that you want to extend and select <guilabel>Extend "
+"Volume</guilabel> from the menu. The <application>Extend Volume Wizard</"
+"application> opens."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:45
+#, no-c-format
+msgid ""
+"Follow the prompts presented by the <application>Extend Volume Wizard</"
+"application>. If you accept the defaults that it offers you, the tool will "
+"extend the selected volume to fill all available space on the hard drive."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:53
+#, no-c-format
+msgid ""
+"In the <literal>Disk Management</literal> window, right-click on disk space "
+"that Windows labels as <literal>unallocated</literal> and select "
+"<literal>New Simple Volume</literal> from the menu. The <application>New "
+"Simple Volume Wizard</application> starts."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:58
+#, no-c-format
+msgid ""
+"Follow the prompts presented by the <application>New Simple Volume Wizard</"
+"application>. If you accept the default options, the tool will create a new "
+"partition that fills all available space on the hard drive, assigns it the "
+"next available drive letter, and formats it with the NTFS file system."
+msgstr ""
+
+#. Tag: screen
+#: X86_Uninstall-Windows-Vista2008.xml:69
+#, no-c-format
+msgid "<prompt>Press any key to boot from CD or DVD</prompt>"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:73
+#, no-c-format
+msgid ""
+"In the <guilabel>Install Windows</guilabel> dialog, select a language, time "
+"and currency format, and keyboard type. Click <guilabel>Next</guilabel>"
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:78
+#, no-c-format
+msgid "Click <guilabel>Repair your computer</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:83
+#, no-c-format
+msgid ""
+"The <application>Windows Recovery Environment</application> (WRE) shows you "
+"the Windows installations that it can detect on your system. Select the "
+"installation that you want to restore, then click <guilabel>Next</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:88
+#, no-c-format
+msgid "Click <guilabel>Command prompt</guilabel>. A command window will open."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:93
+#, no-c-format
+msgid ""
+"Type <command>bootrec /fixmbr</command> and press <keycap>Enter</keycap>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-Vista2008.xml:98
+#, no-c-format
+msgid ""
+"When the prompt reappears, close the command window, then click "
+"<guilabel>Restart</guilabel>."
+msgstr ""
+
+#. Tag: para
+#: X86_Uninstall-Windows-warning-para-1.xml:5
+#, no-c-format
+msgid ""
+"Once you commence this process, your computer may be left in an unbootable "
+"state until you complete the entire set of instructions. Carefully read the "
+"steps below before beginning the removal process. Consider opening these "
+"instructions on another computer or printing them so that you have access to "
+"them at all times during the process."
+msgstr ""





More information about the Fedora-docs-commits mailing list