Branch 'f10' - en-US/abouttoinstall.xml en-US/acknowledgements.xml en-US/adminoptions.xml en-US/Author_Group.xml en-US/before-begin.xml en-US/beginninginstallation.xml en-US/Book_Info.xml en-US/bootloader.xml en-US/colophon.xml en-US/diskpartitioning.xml en-US/expert-quickstart.xml en-US/firstboot.xml en-US/Installation_Guide.ent en-US/Installation_Guide.xml en-US/installingpackages.xml en-US/intro.xml en-US/locale.xml en-US/medialess.xml en-US/networkconfig.xml en-US/new-users.xml en-US/nextsteps.xml en-US/old-intro.xml en-US/other-instmethods.xml en-US/packageselection.xml en-US/Preface.xml en-US/preparing-media.xml en-US/pxe-server.xml en-US/Revision_History.xml en-US/rootpassword.xml en-US/rpm-info.xml en-US/techref.xml en-US/timezone.xml en-US/upgrading.xml en-US/welcome.xml publican.cfg
Rüdiger Landmann
rlandmann at fedoraproject.org
Tue May 11 10:42:21 UTC 2010
en-US/Author_Group.xml | 11
en-US/Book_Info.xml | 27 +
en-US/Installation_Guide.ent | 23
en-US/Installation_Guide.xml | 54 ++
en-US/Preface.xml | 11
en-US/Revision_History.xml | 25
en-US/abouttoinstall.xml | 57 ++
en-US/acknowledgements.xml | 30 +
en-US/adminoptions.xml | 901 +++++++++++++++++++++++++++++++++
en-US/before-begin.xml | 231 ++++++++
en-US/beginninginstallation.xml | 327 ++++++++++++
en-US/bootloader.xml | 309 +++++++++++
en-US/colophon.xml | 87 +++
en-US/diskpartitioning.xml | 1077 ++++++++++++++++++++++++++++++++++++++++
en-US/expert-quickstart.xml | 140 +++++
en-US/firstboot.xml | 197 +++++++
en-US/installingpackages.xml | 45 +
en-US/intro.xml | 100 +++
en-US/locale.xml | 60 ++
en-US/medialess.xml | 138 +++++
en-US/networkconfig.xml | 138 +++++
en-US/new-users.xml | 489 ++++++++++++++++++
en-US/nextsteps.xml | 405 +++++++++++++++
en-US/old-intro.xml | 67 ++
en-US/other-instmethods.xml | 316 +++++++++++
en-US/packageselection.xml | 311 +++++++++++
en-US/preparing-media.xml | 368 +++++++++++++
en-US/pxe-server.xml | 211 +++++++
en-US/rootpassword.xml | 109 ++++
en-US/rpm-info.xml | 50 +
en-US/techref.xml | 247 +++++++++
en-US/timezone.xml | 86 +++
en-US/upgrading.xml | 156 +++++
en-US/welcome.xml | 52 +
publican.cfg | 7
35 files changed, 6862 insertions(+)
New commits:
commit ecd097ab9e86292f578d4aa7955c524892b08b4e
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Tue May 11 20:41:40 2010 +1000
Add files for Publican build
diff --git a/en-US/Author_Group.xml b/en-US/Author_Group.xml
new file mode 100644
index 0000000..09463e0
--- /dev/null
+++ b/en-US/Author_Group.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup>
+ <author>
+ <firstname>Fedora</firstname>
+ <surname>Documentation Project</surname>
+ <email>docs at lists.fedoraproject.org</email>
+ </author>
+</authorgroup>
+
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
new file mode 100644
index 0000000..843d1f2
--- /dev/null
+++ b/en-US/Book_Info.xml
@@ -0,0 +1,27 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo id="book-Installation_Guide-Installation_Guide">
+ <title>Installation Guide</title>
+ <subtitle> </subtitle>
+ <productname>Fedora</productname>
+ <productnumber>10</productnumber>
+ <edition>2.0</edition>
+ <pubsnumber>0</pubsnumber>
+ <abstract>
+ <para>
+
+ </para>
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" />
+ </imageobject>
+ <textobject><phrase>Fedora Documentation Project</phrase></textobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
+
diff --git a/en-US/Installation_Guide.ent b/en-US/Installation_Guide.ent
new file mode 100644
index 0000000..7aa628c
--- /dev/null
+++ b/en-US/Installation_Guide.ent
@@ -0,0 +1,23 @@
+<!ENTITY PRODUCT "Fedora_Installation Guide">
+<!ENTITY BOOKID "install-guide">
+<!ENTITY YEAR "2008,2009">
+<!ENTITY HOLDER "Red Hat, Inc. and Others">
+<!ENTITY FED "Fedora">
+<!ENTITY FC "Fedora">
+<!ENTITY SEL "SELinux">
+<!ENTITY DISTRO "Fedora">
+<!ENTITY DISTROVER "10">
+<!ENTITY FEDLC "fedora">
+<!ENTITY RHEL "Red Hat Enterprise Linux">
+<!ENTITY RH "Red Hat">
+<!ENTITY FP "Fedora Project">
+<!ENTITY FDP "Fedora Documentation Project">
+<!ENTITY PROJECT "Fedora Project">
+<!ENTITY FCVER "10">
+<!ENTITY RHL "Red Hat Linux">
+<!ENTITY FCLOCALVER "10">
+<!ENTITY FCX "F">
+<!ENTITY FDPX "Docs Project">
+<!ENTITY BZ "Bugzilla">
+<!ENTITY BZ-PROD "install-guide">
+
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
new file mode 100644
index 0000000..35e786d
--- /dev/null
+++ b/en-US/Installation_Guide.xml
@@ -0,0 +1,54 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="intro.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="expert-quickstart.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="new-users.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="beginninginstallation.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="locale.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="other-instmethods.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="welcome.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="upgrading.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="networkconfig.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="timezone.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="rootpassword.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="diskpartitioning.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="bootloader.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="packageselection.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="installingpackages.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="firstboot.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="nextsteps.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="adminoptions.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="medialess.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="pxe-server.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="techref.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="colophon.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <!-- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <index />
+</book>
+
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
new file mode 100644
index 0000000..bd60302
--- /dev/null
+++ b/en-US/Preface.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface id="pref-Installation_Guide-Preface">
+ <title>Preface</title>
+ <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </xi:fallback>
+ </xi:include>
+</preface>
+
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
new file mode 100644
index 0000000..7c4100c
--- /dev/null
+++ b/en-US/Revision_History.xml
@@ -0,0 +1,25 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix id="appe-Installation_Guide-Revision_History">
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>2.0</revnumber>
+ <date>Tue May 11 2010</date>
+ <author>
+ <firstname>Rüdiger</firstname>
+ <surname>Ladmann</surname>
+ <email>r.landmann at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Convert to build in Publican</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+</appendix>
+
diff --git a/en-US/abouttoinstall.xml b/en-US/abouttoinstall.xml
new file mode 100644
index 0000000..326cd85
--- /dev/null
+++ b/en-US/abouttoinstall.xml
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-abouttoinstall">
+ <title>About to Install</title>
+
+ <para>
+ No changes are made to your computer until you click the
+ <guilabel>Next</guilabel> button. If you abort the installation
+ process after that point, the &FC; system will be incomplete and
+ unusable. To return to previous screens to make different choices,
+ select <guilabel>Back</guilabel>. To abort the installation, turn
+ off the computer.
+ </para>
+
+ <important>
+ <title>Aborting Installation</title>
+ <para>
+ In certain situations, you may be unable to return to previous
+ screens. &FC; notifies you of this restriction and allows you to
+ abort the installation program. You may reboot with the
+ installation media to start over.
+ </para>
+ </important>
+ <para>
+ Click <guilabel>Next</guilabel> to begin the installation.
+ </para>
+
+<!-- SE: Check this - it doesn't seem to happen on FC5 test2.
+ <para>
+ If your installation requires more than one disc, &FC; displays a
+ list of all discs required to complete the process. If you do not
+ have all of the necessary discs, select
+ <guibutton>Reboot</guibutton> to abort the installation. Otherwise,
+ choose <guibutton>Continue</guibutton> to proceed with installation.
+ </para>
+-->
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/acknowledgements.xml b/en-US/acknowledgements.xml
new file mode 100644
index 0000000..8cac2ed
--- /dev/null
+++ b/en-US/acknowledgements.xml
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<section id="sn-acknowledgements">
+ <title>Acknowledgements</title>
+ <para>
+ Many useful comments and suggestions were provided by Rahul Sundaram
+ and the Anaconda team. David Neimi and Debra Deutsch contributed
+ additional information on boot loader and RAID configurations. The
+ sections on LVM benefited from the contributions of Bob McKay.
+ </para>
+</section>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/adminoptions.xml b/en-US/adminoptions.xml
new file mode 100644
index 0000000..dc4cd27
--- /dev/null
+++ b/en-US/adminoptions.xml
@@ -0,0 +1,901 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<appendix id="ap-admin-options">
+ <title>Boot Options</title>
+ <para>
+ The &FED; 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.
+ </para>
+ <para>
+ If you specify more than one option, separate each of the options by
+ a single space. For example:
+ </para>
+<screen>
+<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput>
+</screen>
+ <tip>
+ <title>Anaconda Boot Options</title>
+
+ <para>
+ The anaconda installer has many boot options, most are listed on
+ the wiki <ulink url="http://fedoraproject.org/wiki/Anaconda/Options"/>.
+ </para>
+ </tip>
+ <tip>
+ <title>Kernel Boot Options</title>
+
+ <para>
+ The <ulink url="http://fedoraproject.org/wiki/KernelCommonProblems"/> 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.
+ </para>
+ </tip>
+ <note>
+ <title>Rescue Mode</title>
+
+ <para>
+ The &FED; 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"/>.
+ </para>
+ </note>
+ <section id="sn-bootoptions-installer">
+ <title>Configuring the Installation System at the Boot Menu</title>
+
+ <para>
+ You can use the boot menu to specify a number of settings for the
+ installation system, including:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ language
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ display resolution
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ interface type
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installation method
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network settings
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <section id="sn-boot-options-language">
+ <title>Specifying the Language</title>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ For example, the ISO codes <userinput>el_GR</userinput> and
+ <userinput>gr</userinput> identify the Greek language and the
+ Greek keyboard layout:
+ </para>
+<screen>
+<userinput>linux lang=<replaceable>el_GR</replaceable> keymap=<replaceable>gr</replaceable></userinput>
+</screen>
+ </section>
+
+ <section id="sn-boot-options-interface">
+ <title>Configuring the Interface</title>
+
+ <para>
+ 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:
+ </para>
+<screen>
+<userinput>linux resolution=<replaceable>1024x768</replaceable></userinput>
+</screen>
+ <para>
+ To run the installation process in
+ <indexterm>
+ <primary>text interface</primary>
+ </indexterm>
+ <option>text</option> mode, enter:
+ </para>
+<screen>
+ <userinput>linux text</userinput>
+</screen>
+ <para>
+ To enable support for a
+ <indexterm>
+ <primary>serial console</primary>
+ </indexterm>
+ serial console, enter <option>serial</option> as an additional
+ option.
+ </para>
+
+ </section>
+
+ <section id="sn-boot-options-installmethod">
+ <title>Specifying the Installation Method</title>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ <segmentedlist id="tb-installmethods">
+ <title>Installation Methods</title>
+ <segtitle>Installation Method</segtitle>
+ <segtitle>Option Format</segtitle>
+ <seglistitem>
+ <seg>CD or DVD drive</seg>
+ <seg><option>method=<replaceable>cdrom</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Hard Drive</seg>
+ <seg><option>method=<replaceable>hd://device/</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>HTTP Server</seg>
+ <seg><option>method=<replaceable>http://server.mydomain.com/directory/</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>FTP Server</seg>
+ <seg><option>method=<replaceable>ftp://server.mydomain.com/directory/</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>NFS Server</seg>
+ <seg><option>method=<replaceable>nfs:server.mydomain.com:/directory/</replaceable></option></seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+
+ <section id="sn-boot-options-network">
+ <title>Manually Configuring the Network Settings</title>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ This example configures the network settings for an installation
+ system that uses the IP address
+ <systemitem class="ipaddress">192.168.1.10</systemitem>:
+ </para>
+<screen>
+<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>
+</screen>
+ <note>
+ <title>Configuring the Installed System</title>
+
+ <para>
+ Use the Network Configuration screen to specify the network
+ settings for the new system. Refer to
+ <xref linkend="ch-networkconfig"/> for more information on
+ configuring the network settings for the installed system.
+ </para>
+ </note>
+ </section>
+ </section>
+ <section id="sn-remoteaccess-installation">
+ <title>Enabling Remote Access to the Installation System</title>
+<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+ <para>
+ You may access either graphical or text interfaces for the
+ installation system from any other system. Access to a text mode
+ display requires <command>telnet</command>, which is installed by
+ default on &FED; 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.
+ </para>
+ <tip>
+ <title>Installing a VNC Client on &FED;</title>
+ <para>
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ <secondary>installing client</secondary>
+ </indexterm>
+ &FED; includes <application>vncviewer</application>, the client
+ provided by the developers of VNC. To obtain
+ <application>vncviewer</application>, install the
+ <filename>vnc</filename> package.
+ </para>
+ </tip>
+ <para>
+ 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>.
+ </para>
+
+ <section id="sn-remoteaccess-installation-vnc">
+ <title>Enabling Remote Access with VNC</title>
+
+ <para>
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ <secondary>enabling</secondary>
+ </indexterm>
+ To enable remote graphical access to the installation system,
+ enter two options at the prompt:
+ </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput>
+</screen>
+ <para>
+ 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>.
+ </para>
+
+ <note>
+ <title>VNC Passwords</title>
+
+ <para>
+ The VNC password must be at least six characters long.
+ </para>
+ </note>
+
+ <para>
+ 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:
+ </para>
+<screen>
+<computeroutput>Starting VNC...</computeroutput>
+<computeroutput>The VNC server is now running.</computeroutput>
+<computeroutput>Please connect to computer.mydomain.com:1 to begin the install...</computeroutput>
+<computeroutput>Starting graphical installation...</computeroutput>
+<computeroutput>Press <enter> for a shell</computeroutput>
+</screen>
+ <para>
+ You may then login to the installation system with a VNC client.
+ To run the <application>vncviewer</application> client on &FED;,
+ 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>.
+ </para>
+ </section>
+
+ <section id="sn-remoteaccess-installation-vnclistener">
+ <title>Connecting the Installation System to a VNC Listener</title>
+
+ <para>
+ 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 &FED; systems, use the
+ <option>-listen</option> option to run
+ <application>vncviewer</application> as a listener. In a
+ terminal window, enter the command:
+ </para>
+<screen>
+ <userinput>vncviewer -listen</userinput>
+</screen>
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ 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>.
+ </para>
+ </note>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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:
+ </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
+</screen>
+ </section>
+
+ <section id="sn-telnet-installation">
+ <title>Enabling Remote Access with Telnet</title>
+
+ <para>
+ 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:
+ </para>
+<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
+<screen>
+<userinput>linux text telnet</userinput>
+</screen>
+ <para>
+ 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:
+ </para>
+<screen>
+<userinput>telnet computer.mydomain.com</userinput>
+</screen>
+ <caution>
+ <title>Telnet Access Requires No Password</title>
+
+ <para>
+ To ensure the security of the installation process, only use
+ the <option>telnet</option> option to install systems on
+ networks with restricted access.
+ </para>
+ </caution>
+ </section>
+ </section>
+ <section id="sn-remote-logging">
+ <title>Logging to a Remote System During the Installation</title>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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:
+ </para>
+<screen>
+<userinput>linux syslog=<replaceable>192.168.1.20:514</replaceable></userinput>
+</screen>
+ <section id="sn-remote-logging-logserver">
+ <title>Configuring a Log Server</title>
+
+ <para>
+ &FED; uses <command>syslogd</command> to provide a syslog
+ service. The default configuration of <command>syslogd</command>
+ rejects messages from remote systems.
+ </para>
+
+ <caution>
+ <title>Only Enable Remote Syslog Access on Secured Networks</title>
+
+ <para>
+ The <command>syslogd</command> service includes no security
+ measures. 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.
+ </para>
+ </caution>
+
+ <para>
+ To configure a &FED; system to accept log messages from other
+ systems on the network, edit the file
+ <filename>/etc/sysconfig/syslog</filename>. You must use
+ <systemitem class="username">root</systemitem> privileges to
+ edit the file <filename>/etc/sysconfig/syslog</filename>. Add
+ the option <option>-r</option> to the
+ <command>SYSLOGD_OPTIONS</command>:
+ </para>
+<screen>
+<computeroutput>SYSLOGD_OPTIONS="-m 0 <userinput>-r</userinput>"</computeroutput>
+</screen>
+ <para>
+ Restart the <command>syslogd</command> service to apply the
+ change:
+ </para>
+<screen>
+<userinput>su -c '/sbin/service syslog restart'</userinput>
+</screen>
+ <para>
+ Enter the <systemitem class="username">root</systemitem>
+ password when prompted.
+ </para>
+
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ 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>.
+ </para>
+ </note>
+ </section>
+ </section>
+ <section id="sn-automating-installation">
+ <title>Automating the Installation with Kickstart</title>
+
+ <para>
+ 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.
+ </para>
+ <tip>
+ <title>Every Installation Produces a Kickstart File</title>
+ <para>
+ The &FED; 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.
+ </para>
+ </tip>
+ <para>
+ &FED; 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 &FED; Kickstart editor, choose
+ <menuchoice> <guimenu>Applications</guimenu> <guisubmenu>System
+ Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ To automate the installation process with a Kickstart file, use
+ the <option>ks</option> option to specify the name and location of
+ the file:
+ </para>
+<screen>
+ <userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
+</screen>
+ <para>
+ 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.
+ </para>
+ <segmentedlist id="tb-kssources">
+ <title>Kickstart Sources</title>
+ <segtitle>Kickstart Source</segtitle>
+ <segtitle>Option Format</segtitle>
+ <seglistitem>
+ <seg>CD or DVD drive</seg>
+ <seg><option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Hard Drive</seg>
+ <seg><option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Other Device</seg>
+ <seg><option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>HTTP Server</seg>
+ <seg><option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>FTP Server</seg>
+ <seg><option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>NFS Server</seg>
+ <seg><option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option></seg>
+ </seglistitem>
+ </segmentedlist>
+ <para>
+ 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>:
+ </para>
+<screen>
+<userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput>
+</screen>
+ </section>
+ <section id="sn-bootoptions-hardware">
+ <title>Enhancing Hardware Support</title>
+
+ <para>
+ By default, &FED; attempts to automatically detect and configure
+ support for all of the components of your computer. &FED; 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.
+ </para>
+
+ <section id="sn-bootoptions-driverdisks">
+ <title>Adding Hardware Support with Driver Disks</title>
+<!-- SE: This section is untested - there seem to be very few driver disks for Fedora. -->
+ <para>
+ 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.
+ </para>
+
+ <para>
+ Hardware manufacturers may supply
+ <indexterm>
+ <primary>driver disks</primary>
+ </indexterm>
+ driver disks for &FED; 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.
+ </para>
+
+ <note>
+ <title>Driver Disks Supplied as Zipped Files</title>
+
+ <para>
+ 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 &FED; system, choose <menuchoice>
+ <guimenu>Applications</guimenu> <guisubmenu>Accessories</guisubmenu><guimenuitem>Archive
+ Manager</guimenuitem></menuchoice>.
+ </para>
+ </note>
+
+ <para>
+ 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:
+ </para>
+<screen>
+ <userinput>dd if=drivers.img of=/dev/fd0</userinput>
+</screen>
+ <para>
+ To use a driver disk in the installation process, specify the
+ <option>dd</option> option at the
+ <prompt>boot:</prompt>
+ prompt:
+ </para>
+<screen>
+ <userinput>linux dd</userinput>
+</screen>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ <segmentedlist id="tb-driversources">
+ <title>Driver Disk Image Sources</title>
+ <segtitle>Image Source</segtitle>
+ <segtitle>Option Format</segtitle>
+ <seglistitem>
+ <seg>Select a drive or device</seg>
+ <seg><option>dd</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>HTTP Server</seg>
+ <seg><option>dd=<replaceable>http://server.mydomain.com/directory/drivers.img</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>FTP Server</seg>
+ <seg><option>dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable></option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>NFS Server</seg>
+ <seg><option>dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable></option></seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+
+ <section id="sn-bootoptions-hwdetection">
+ <title>Overriding Automatic Hardware Detection</title>
+
+ <para>
+ 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.
+ </para>
+ <tip>
+ <title>Check the Release Notes</title>
+ <para>
+ Refer to the Release Notes for information on known issues
+ with specific devices.
+ </para>
+ </tip>
+ <para>
+ To override the automatic hardware detection, use one or more of
+ the following options:
+ </para>
+ <segmentedlist>
+ <title>Hardware Options</title>
+ <segtitle>Compatibility Setting</segtitle>
+ <segtitle>Option</segtitle>
+ <seglistitem>
+ <seg>Disable all hardware detection</seg>
+ <seg><option>noprobe</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable graphics, keyboard, and mouse detection</seg>
+ <seg><option>headless</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable automatic monitor detection (DDC)</seg>
+ <seg><option>skipddc</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Use basic VESA driver for video</seg>
+ <seg><option>xdriver=vesa</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable mainboard APIC</seg>
+ <seg><option>noapic</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable power management (ACPI)</seg>
+ <seg><option>acpi=off</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable Direct Memory Access (DMA) for IDE, SATA, and
+ ATAPI drives</seg>
+ <seg><option>libata.dma=0</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Enable DMA only for IDE and SATA drives</seg>
+ <seg><option>libata.dma=1</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable BIOS-assisted RAID</seg>
+ <seg><option>nodmraid</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable Firewire device detection</seg>
+ <seg><option>nofirewire</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable parallel port detection</seg>
+ <seg><option>noparport</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable PC Card (PCMCIA) device detection</seg>
+ <seg><option>nopcmcia</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable USB storage device detection</seg>
+ <seg><option>nousbstorage</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Disable all USB device detection</seg>
+ <seg><option>nousb</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Force Firewire device detection</seg>
+ <seg><option>firewire</option></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Prompt user for ISA device configuration</seg>
+ <seg><option>isa</option></seg>
+ </seglistitem>
+ </segmentedlist>
+ <note>
+ <title>Additional Screen</title>
+
+ <para>
+ 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.
+ </para>
+ </note>
+ </section>
+ </section>
+
+ <section id="sn-boot-modes">
+ <title>Using the Maintenance Boot Modes</title>
+
+ <section id="sn-memtest">
+ <title>Loading the Memory (RAM) Testing Mode</title>
+
+ <para>
+ 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 &DISTRO; for the first time, even if it has previously run
+ other operating systems.
+ </para>
+
+ <para>
+ &DISTRO; 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.
+ </para>
+
+ <para>
+ To halt the tests and reboot your computer, enter
+ <keycap>Esc</keycap> at any time.
+ </para>
+ </section>
+
+ <section id="sn-mode-rescue">
+ <title>Booting Your Computer with the Rescue Mode</title>
+ <indexterm>
+ <primary>rescue mode</primary>
+ </indexterm>
+ <para>
+ 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
+ &FED; 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ By default, rescue mode attaches an existing operating system to
+ the rescue system under the directory
+ <filename>/mnt/sysimage/</filename>.
+ </para>
+ </section>
+ </section>
+
+</appendix>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/before-begin.xml b/en-US/before-begin.xml
new file mode 100644
index 0000000..c5276b1
--- /dev/null
+++ b/en-US/before-begin.xml
@@ -0,0 +1,231 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-before-begin">
+ <title>Before You Begin</title>
+
+ <para>
+ Before you install &FC;, you need access to:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ boot or installation media (refer to
+ <xref
+ linkend="ch-preparing-media"/> for more information)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ information about your network configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ a copy of this &IG; and the Release Notes for this version of &FC;
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The Release Notes specify the hardware requirements for &FC; &FCLOCALVER;.
+ They also provide advice on any known problems with particular hardware and
+ software configurations.
+ </para>
+
+ <para>
+ The Release Notes are available on the first disc in HTML and plain text
+ format. The latest versions of this &IG; and the Release Notes are available
+ at &FDPDOCS-URL;.
+ </para>
+
+ <section id="sn-installing-storage-configurations">
+ <title>Storage</title>
+<!-- SE: There may also be additional considerations when installing on machines backed by a SAN. -->
+ <para>
+ A &FED; system requires a minimum of 700 MB storage for a command-line
+ system. A desktop system with the default applications requires at least 3
+ GB of storage. You may install multiple copies of &FED; on the same
+ computer.
+ </para>
+
+ <para>
+ Configure any RAID functions provided by the mainboard of your computer,
+ or attached controller cards, before you begin the installation process.
+ &FED; can automatically detect many RAID devices and use any storage they
+ provide.
+ </para>
+ </section>
+
+ <section id="sn-installing-network-configurations">
+ <title>Networking</title>
+
+ <para>
+ By default, &FC; systems attempt to discover correct connection settings
+ for the attached network using
+ <indexterm>
+ <primary>DHCP (Dynamic Host Configuration Protocol)</primary>
+ </indexterm> <firstterm>Dynamic Host Configuration Protocol</firstterm>, or
+ <firstterm><acronym>DHCP</acronym></firstterm>. Your network may include a
+ DHCP provider which delivers settings to other systems on demand. The DHCP
+ provider may be a router or wireless access point for the network, or a
+ server.
+ </para>
+
+ <para>
+ In some circumstances you may need to provide information about your
+ network during the installation process. Refer to
+ <xref
+ linkend="sn-installing-networkinstallation" /> and
+ <xref
+ linkend="sn-installing-managed-network" /> for more information.
+ </para>
+
+ <note>
+ <title>Modem Configuration</title>
+
+ <para>
+ The installation system for &FC; does not configure modems. If your
+ computer has a modem, configure the dialing settings after you complete
+ the installation and reboot.
+ </para>
+ </note>
+ </section>
+
+ <section id="sn-installing-networkinstallation">
+ <title>Installing from a Server or Web Site</title>
+
+ <para>
+ You may install &FC; using a <firstterm>mirror</firstterm>, a Web site or
+ network server that provide a copy of the necessary files. To use a
+ mirror, you need to know:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ the name of the server
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the network protocol used for installation (FTP, HTTP, or NFS)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the path to the installation files on the server
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ You may install &FC; 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.
+ </para>
+
+ <para>
+ The &FP; maintains a list of HTTP and FTP public mirrors, sorted by
+ region, at <ulink url="http://mirrors.fedoraproject.org/publiclist"/>.
+ To determine the complete directory path for the installation files, add
+ <filename>/&FCLOCALVER;/<replaceable>architecture</replaceable>/os/</filename>
+ to the path shown on the web page. If your computer uses the
+ <systemitem>ppc</systemitem> architecture, for instance, add <filename
+ class="directory">/&FCLOCALVER;/ppc/os/</filename> to the path shown.
+ </para>
+ <tip>
+ <title>Building Your Own Mirror</title>
+ <para>
+ Refer to <ulink url="http://docs.fedoraproject.org/mirror/"/> for
+ information on how to create your own &FED; mirror for either public or
+ private use.
+ </para>
+ </tip>
+ <para>
+ To use a mirror, boot your computer with &FED; boot media, and follow
+ the instructions in
+ <xref linkend="ch-other-install-methods"/>. Refer to
+ <xref
+ linkend="ch-preparing-media"/> for more information on creating the boot
+ media.
+ </para>
+
+ <note>
+ <title>Using the Installation Discs</title>
+
+ <para>
+ If you boot your computer with an installation DVD, the first
+ installation CD, or another bootable &FED; CD, enter
+ <userinput>linux askmethod</userinput> at the
+ <prompt>boot:</prompt> prompt to access the server installation
+ options.
+ </para>
+ </note>
+
+ <para>
+ If your network includes a server, you may also use
+ <firstterm>PXE</firstterm> (Pre-boot eXecution Environment) to boot your
+ computer. PXE (also referred to as <firstterm>netboot</firstterm>) is a
+ standard that enables PCs to use files on a server as a boot device. &FC;
+ includes utilities that allow it to function as a PXE server for other
+ computers. You can use this option to install &FC; on a PXE-enabled
+ computer entirely over the network connection, using no physical media at
+ all.
+ </para>
+ </section>
+
+ <section id="sn-installing-managed-network">
+ <title>Installing &FC; on a Managed Network</title>
+
+ <para>
+ Some corporate networks include a <firstterm>directory service</firstterm>
+ that manages user accounts for the organization. &FC; systems can join a
+ Kerberos, NIS, Hesiod, or <trademark
+ class="registered">Microsoft</trademark> <trademark
+ class="registered">Windows</trademark> domain as part of the
+ installation process. &FC; can also use LDAP directories.
+ </para>
+
+<!--
+
+ <para>
+ The process of configuring your &FC; system to use network
+ authentication services is explained in a separate tutorial.
+ </para>
+
+ [When this tutorial exists, remove these comments.]
+
+-->
+
+ <caution>
+ <title>Consult Network Administrators</title>
+
+ <para>
+ Always consult the administrators before you install a &FC; system on an
+ existing network owned by someone besides yourself. They can provide
+ correct network and authentication settings, and guidance on specific
+ organizational policies and requirements.
+ </para>
+ </caution>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/beginninginstallation.xml b/en-US/beginninginstallation.xml
new file mode 100644
index 0000000..9ef55df
--- /dev/null
+++ b/en-US/beginninginstallation.xml
@@ -0,0 +1,327 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+<chapter id="ch-beginninginstallation">
+ <title>Beginning the Installation</title>
+
+ <note>
+ <title>Aborting the Installation</title>
+ <para>
+ 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.
+ </para>
+ </note>
+ <section id="sn-boot-menu">
+ <title>The Boot Menu</title>
+ <para>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.</para>
+ <tip>
+ <title>Using Boot Options</title>
+ <para>For a listing and explanation of common boot options, refer
+ to <xref linkend="ap-admin-options"/>.</para>
+ </tip>
+ <para>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:</para>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Boot</title>
+ <para>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.</para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Verify and Boot</title>
+ <para>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.</para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Memory Test</title>
+ <para>
+ This option runs an exhaustive test on the memory on your
+ system. For more information, refer to <xref
+ linkend="sn-memtest"/>.
+ </para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Boot from local drive</title>
+ <para>
+ 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.
+ </para>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ <para>If you boot the DVD, rescue CD, or minimal boot media, the
+ boot menu options include:</para>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Install or upgrade an existing system</title>
+ <para>This option is the default. Choose this option to
+ install &DISTRO; onto your computer system using the
+ graphical installation program.</para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Install or upgrade an existing system (text mode)</title>
+ <para>Choose this option to install &DISTRO; onto your
+ computer system using the text-based installation program.
+ If your computer system has problems using the graphical
+ installation program, you can install the system with this
+ option. Installing with this option does
+ <emphasis role="strong">not</emphasis> prevent you from using a graphical
+ interface on the system once it is installed.</para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Rescue installed system</title>
+ <para>Choose this option to repair a problem with your
+ installed &DISTRO; system that prevents you from booting
+ normally. Although &DISTRO; 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.</para>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-install-diff-source">
+ <title>Installing from a Different Source</title>
+ <para>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.</para>
+ <para>You can install &DISTRO; 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.</para>
+ <para>The following table summarizes the different boot methods and
+ recommended installation methods to use with each:</para>
+ <segmentedlist>
+ <segtitle>Boot Method</segtitle>
+ <segtitle>Installation Method</segtitle>
+ <seglistitem>
+ <seg>DVD</seg>
+ <seg>DVD, network, or hard disk</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Minimal boot CD or USB, rescue CD</seg>
+ <seg>Network or hard disk</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Live CD or USB</seg>
+ <seg><application>Install to Hard Disk</application>
+ application</seg>
+ </seglistitem>
+ </segmentedlist>
+ <para><xref
+ linkend="ch-other-install-methods"/> contains detailed
+ information about installing from alternate locations.
+ </para>
+ </section>
+ <section id="sn-verifying-media">
+ <title>Verifying Media</title>
+ <para>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.</para>
+<!-- <tip>
+ <title>BitTorrent Automatically Verifies File Integrity</title>
+ <para>If you use BitTorrent, any files you download are automatically
+ validated. If your file completes downloading you do not need to
+ check it. Once you burn your CD or DVD, however, during the installation
+ you should still use mediacheck to verify the integrity of the media.</para>
+ </tip> -->
+ <section id="sn-verifying-livecd">
+ <title>Verifying the Live CD</title>
+ <para>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.</para>
+ </section>
+ <section id="sn-verifying-dvd">
+ <title>Verifying the DVD</title>
+ <para>If you boot from the &DISTRO; distribution DVD, the option
+ to verify the media appears after you choose to install
+ &DISTRO;. If the verification succeeds, the installation
+ process proceeds normally. If the process fails, create a new
+ DVD using the ISO image you downloaded earlier.</para>
+ </section>
+ </section>
+
+ <section id="sn-booting-from-pxe">
+ <title>Booting from the Network using PXE</title>
+
+ <para>
+ 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"/>.
+ </para>
+
+ <para>
+ 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 &FED;
+ installation system without any other media.
+ </para>
+
+ <para>
+ To boot a computer from a PXE server:
+ </para>
+
+ <procedure>
+ <step>
+ <para>
+ 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.
+ </para>
+ </step>
+ <step>
+ <para>
+ Switch on the computer.
+ </para>
+ </step>
+ <step>
+ <para>
+ A menu screen appears. Press the number key that corresponds
+ to the desired option.
+ </para>
+ </step>
+ </procedure>
+
+ <note>
+ <title>PXE Troubleshooting</title>
+ <para>
+ 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.
+ </para>
+ </note>
+<note>
+ <title>Multiple NICs and PXE installation </title>
+ <para>
+ 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: </para>
+ <para><option>IPAPPEND 2</option>
+ </para>
+ <para><option>APPEND ksdevice=bootif</option>
+ </para>
+ <para>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:
+ </para>
+ <para><option>ksdevice=link</option>
+ </para>
+ <para>This option causes the installer to use the first network device
+ it finds that is linked to a network switch.
+ </para>
+ </note>
+ </section>
+ <section id="sn-graphics-problem">
+ <title>Graphical and Text Interfaces</title>
+ <para>Fedora 10 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 192MB of RAM or that boot from the
+ installation DVD or Live Media can use the graphical installer. Systems
+ with 192MB RAM or less automatically scale back to using the text-based
+ installer. If you prefer to use the text-based installer, type <option>linux text</option> at the
+ <prompt>boot:</prompt> prompt.</para>
+ <para>If one of the following situations occurs, the installation
+ program uses a text mode:</para>
+ <itemizedlist>
+ <listitem>
+ <para>The installation system fails to identify the display
+ hardware on your computer</para>
+ </listitem>
+ <listitem>
+ <para>Your computer has less than 192 MB of RAM</para>
+ </listitem>
+ <listitem>
+ <para>You choose the text mode installation from the boot
+ menu</para>
+ </listitem>
+ </itemizedlist>
+ <para>The text screens provide the same functions as the standard
+ screens. You can configure your system for graphical interface
+ use after installation.</para>
+ <important>
+ <title>Graphical Interface Usage</title>
+ <para>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"/>.</para>
+ </important>
+ </section>
+</chapter>
+
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+<!--
+vim: softtabstop=2:shiftwidth=2:expandtab:textwidth=72
+-->
diff --git a/en-US/bootloader.xml b/en-US/bootloader.xml
new file mode 100644
index 0000000..cf4a1a8
--- /dev/null
+++ b/en-US/bootloader.xml
@@ -0,0 +1,309 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-bootloader">
+ <title>Boot Loader</title>
+ <para>
+ A <firstterm>boot loader</firstterm> is a small program that reads
+ and launches the operating system. &FC; uses the
+ <indexterm>
+ <primary>GRUB</primary>
+ <secondary>configuring</secondary>
+ <seealso>boot loader</seealso>
+ </indexterm>
+ <application>GRUB</application> boot loader by default. If you have
+ multiple operating systems, the boot loader allows you to choose
+ which operating system to boot.
+ </para>
+ <note>
+ <title>The GRUB boot menu</title>
+ <para>Please note that beginning in &FED; version 10, 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.)
+ </para>
+ </note>
+ <para>
+ 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="ch-packageselection"/>.
+ </para>
+ <para>
+ 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
+ &FC;. 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>.
+ </para>
+ <warning>
+ <title>Installing GRUB</title>
+
+ <para>
+ If you install GRUB, it may overwrite your existing boot loader.
+ </para>
+ </warning>
+ <section id="sn-bootloader-config-change">
+ <title>Keeping Your Existing Boot Loader Settings</title>
+
+ <para>
+ By default, the installation program installs GRUB in the
+ <firstterm>master boot record</firstterm>,
+ <indexterm>
+ <primary>master boot record</primary>
+ </indexterm> 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>.
+ </para>
+ <important>
+ <title>Boot Loader Required</title>
+
+ <para>
+ Your computer must have <application>GRUB</application> or
+ another boot loader installed in order to start, unless you
+ create a separate startup disk to boot from. <!-- FIXME: Add
+ reference to startup disk elsewhere in the IG. PWF. -->
+ </para>
+ </important>
+<!--
+ <para>
+ You may need to customize the GRUB installation to correctly
+ support some hardware or system configurations. To specify
+ compatibility settings, select <guilabel>Configure advanced boot
+ loader options</guilabel>. This causes a second screen of options
+ to appear when you choose <guibutton>Next</guibutton>.
+ <xref linkend="sn-bootloader-advanced"/> explains the features of
+ the additional screen.
+ </para>
+This section was removed because this isn't possible in current anaconda
+-->
+ </section>
+ <section id="sn-bootloader-others">
+ <title>Booting Additional Operating Systems</title>
+
+ <para>
+ If you have other operating systems already installed, &FC;
+ 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.</para>
+ <!--
+ <important>
+ <title>GRUB and Microsoft Vista</title>
+ <para>Due to architectural changes made by Microsoft, the
+ <application>GRUB</application> boot loader cannot load
+ Microsoft Vista operating systems.</para>
+ </important>
+ FIXME: Need to find out if this is correct before adding it.
+ -->
+ <para>To add, remove, or change the detected operating system
+ settings, use the options provided.</para>
+
+ <variablelist>
+ <varlistentry>
+ <term><guibutton>Add</guibutton></term>
+ <listitem>
+ <para>
+ Select <guibutton>Add</guibutton> to include an additional
+ operating system in GRUB.
+ </para>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guibutton>Edit</guibutton></term>
+ <listitem>
+ <para>
+ To change an entry in the GRUB boot menu, select the entry
+ and then select <guibutton>Edit</guibutton>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guibutton>Delete</guibutton></term>
+ <listitem>
+ <para>
+ To remove an entry from the GRUB boot menu, select the entry
+ and then select <guibutton>Delete</guibutton>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section id="sn-bootloader-password">
+ <title>Setting a Boot Loader Password</title>
+
+ <para>
+ <application>GRUB</application> reads many file systems without
+ the help of an operating system. An operator can interrupt the
+ booting sequence to choose a different operating system to boot,
+ change boot options, or recover from a system error. However,
+ these functions may introduce serious security risks in some
+ environments. You can add a password to
+ <application>GRUB</application> so that the operator must enter
+ the password to interrupt the normal boot sequence.
+ </para>
+ <tip>
+ <title>GRUB Passwords Not Required</title>
+ <para>
+ 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.
+ </para>
+ </tip>
+ <para>
+ To set a boot password, select the <guibutton>Use a boot loader
+ password</guibutton> check box. The Enter Boot Loader Password
+ entry dialog is diplayed. Type the desired password and then
+ confirm it by typing it again in the spaces provided and selecting
+ <guibutton>Ok</guibutton>.
+ </para>
+ <tip>
+ <title>Choose a Good Password</title>
+ <para>
+ Choose a password that is easy for you to remember but hard for
+ others to guess.
+ </para>
+ </tip>
+ <section id="sn-forgotten-grub-pass">
+ <title>Forgotten <application>GRUB</application> Passwords</title>
+
+ <para>
+ <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 &FC;
+ installation disc to reset the GRUB password.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </section>
+ </section>
+ <section id="sn-bootloader-advanced">
+ <title>Advanced Boot Loader Options</title>
+ <para>
+ The default boot options are adequate for most situations. The
+ installation program writes the <application>GRUB</application>
+ boot loader in the
+ <indexterm>
+ <primary>master boot record</primary>
+ </indexterm>
+ master boot record (<abbrev>MBR</abbrev>), overwriting any
+ existing boot loader.
+ </para>
+
+ <para>
+ You may keep your current boot loader in the <abbrev>MBR</abbrev>
+ and install GRUB as a secondary boot loader. If you choose this
+ option, the installer program will write GRUB to the first sector
+ of the Linux <filename>/boot</filename> partition.
+ </para>
+
+ <note>
+ <title>GRUB as a Secondary Boot Loader</title>
+ <para>
+ 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.
+ </para>
+ </note>
+
+ <para>
+ You may also need the advanced options if your
+ <abbrev>BIOS</abbrev> enumerates your drives or RAID arrays
+ differently than &FC; expects. If necessary, select the
+ <guibutton>Change Device</guibutton> button and expand the
+ <guibutton>BIOS Drive Order</guibutton> selection within
+ the Boot loader device dialog to set the order of the
+ devices in &FC; to match your BIOS.
+ </para>
+<!--
+ <para>
+ On a few systems, &FC; may not configure the disk drive geometry
+ for large disks correctly because of limitations within the
+ <abbrev>BIOS</abbrev>. To work around this problem, mark the
+ <guibutton>Force LBA32</guibutton> check box.
+ </para>
+-->
+<!--
+ <para>
+ The Linux kernel usually auto-detects its environment correctly,
+ and no additional kernel parameters are needed. However, you may
+ provide any needed kernel parameter using the advanced boot loader
+ options.
+ </para>
+
+ <note>
+ <title>Kernel Parameters</title>
+
+ <para>
+ For a partial list of the kernel command line parameters, type
+ the following command in a terminal window: <userinput>man
+ bootparam</userinput>. For a comprehensive and authoritative
+ list, refer to the documentation provided in the kernel sources.
+ </para>
+ </note>
+
+ <para>
+ To alter any of these settings, mark the <guibutton>Configure
+ advanced boot loader options</guibutton> check box. Select
+ <guibutton>Next</guibutton> and the advanced boot options menu
+ appears.
+ </para>
+
+ <note>
+ <title>Optional Menu</title>
+
+ <para>
+ &FC; displays the advanced boot options menu
+ <emphasis>only</emphasis> if the advanced configuration check
+ box described above has been selected.
+ </para>
+ </note>
+-->
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/colophon.xml b/en-US/colophon.xml
new file mode 100644
index 0000000..43eee90
--- /dev/null
+++ b/en-US/colophon.xml
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+
+]>
+<!-- $Id: -->
+
+<chapter id="ch-colophon">
+ <title>Colophon</title>
+ <para>As we use the term, a <emphasis>colophon</emphasis>:
+ </para><itemizedlist>
+ <listitem>
+ <para> recognizes contributors and provides accountability,
+ and</para>
+ </listitem><listitem>
+ <para> explains tools and production methods.</para>
+ </listitem>
+ </itemizedlist>
+ <section id="sn-Contributors">
+ <title>Contributors</title>
+ <note>
+ <title>Out of date content.</title>
+ <para>
+ This content is out of date, it does not include translators.</para>
+ </note>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://fedoraproject.org/wiki/User:Pfrields"> Paul W. Frields</ulink> (writer, editor) </para> </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://fedoraproject.org/wiki/StuartEllis"> Stuart Ellis</ulink> (writer, editor) </para></listitem>
+ <listitem>
+ <para>
+ <ulink url="https://fedoraproject.org/wiki/User:Jsmith"> Jared Smith</ulink> (writer, editor) </para></listitem>
+ <listitem>
+ <para>
+ Elizabeth Ann West (editor) </para></listitem>
+ <listitem>
+ <para>
+ <ulink url="https://fedoraproject.org/wiki/TommyReynolds"> Tommy Reynolds </ulink> (writer) </para></listitem>
+ <listitem>
+ <para>
+ Jeremy Mooney (writer) </para></listitem>
+ <listitem>
+ <para>
+ John Nguyen (writer) </para></listitem>
+ <listitem>
+ <para>
+ Chris Johnson (writer) </para></listitem>
+ <listitem>
+ <para>
+ Erick Lemon (writer) </para></listitem>
+ <listitem>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/KarstenWade"> Karsten Wade</ulink> (writer, editor, publisher)</para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://fedoraproject.org/wiki/User:ke4qqq"> David Nalley</ulink> (writer, editor)</para></listitem>
+
+ </itemizedlist>
+ <para>
+ <ulink
+ url="http://docs.fedoraproject.org/install-guide/">http://docs.fedoraproject.org/install-guide/</ulink>
+ </para>
+ </section><section id="sn-Production_methods">
+ <title>Production methods</title>
+ <para>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.</para>
+ </section>
+</chapter>
diff --git a/en-US/diskpartitioning.xml b/en-US/diskpartitioning.xml
new file mode 100644
index 0000000..15a177a
--- /dev/null
+++ b/en-US/diskpartitioning.xml
@@ -0,0 +1,1077 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-disk-partitioning">
+ <title>Disk Partitioning</title>
+ <para>
+ &DISTRO; creates and uses several <firstterm>partitions</firstterm> on
+ the available hard drives. You may customize both the partitions,
+ and how the drives on your system are managed.
+ <xref linkend="sn-partitioning-general"/> explains drive partitions
+ in more detail.
+ </para>
+ <section id="sn-partitioning-raid">
+ <title>RAID and Other Disk Devices</title>
+ <section id="sn-partitioning-raid-hw">
+ <title>Hardware RAID</title>
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>hardware</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>array</primary>
+ <see>RAID</see>
+ </indexterm>
+ <para>
+ <firstterm>RAID</firstterm>, or Redundant Array of Independent
+ Disks, allows a group, or <firstterm>array</firstterm>, 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 &FED;.
+ </para>
+ <para>
+ On systems with more than one hard drive you may configure &DISTRO;
+ to operate several of the drives as a Linux RAID array without
+ requiring any additional hardware.
+ </para>
+ </section>
+ <section id="sn-partitioning-raid-sw">
+ <title>Software RAID</title>
+ <para>You can use the &DISTRO; 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="sn-disk-druid"/>.</para>
+ </section>
+ <section id="sn-partitioning-fw-usb">
+ <title>FireWire and USB Disks</title>
+ <para>Some FireWire and USB hard disks may not be recognized by
+ the &DISTRO; installation system. If configuration of these
+ disks at installation time is not vital, disconnect them to
+ avoid any confusion.</para>
+ <tip>
+ <title>Post-installation Usage</title>
+ <para>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.</para>
+ </tip>
+ </section>
+ </section>
+ <section id="sn-partitioning-general">
+ <title>General Information on Partitions</title>
+
+ <para>
+ A &DISTRO; system has at least three partitions:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ A <filename class="partition">/boot</filename> partition
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A <filename class="partition">/</filename> partition
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A <systemitem class="filesystem">swap</systemitem> partition
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ If you are not sure how best to configure the partitions for your
+ computer, accept the default partition layout.
+ </para>
+
+ <para>
+ The RAM installed in your computer provides a pool of memory for
+ running systems. Linux systems use
+ <indexterm>
+ <primary>swap partitions</primary>
+ </indexterm> <firstterm>swap partitions</firstterm> to
+ expand this pool, by automatically moving portions of memory
+ between RAM and swap partitions if insufficient RAM is available.
+ In addition, certain power management features store all of the
+ memory for a suspended system in the available swap partitions. If
+ you manually specify the partitions on your system, create one
+ swap partition that has more capacity than the computer RAM.
+ </para>
+
+ <para>
+ Data partitions provide storage for files. Each data partition has
+ a
+ <indexterm>
+ <primary>mount point</primary>
+ </indexterm> <firstterm>mount point</firstterm>, to indicate the
+ system directory whose contents reside on that partition. A
+ partition with no mount point is not accessible by users. Data not
+ located on any other partition resides in the <filename
+ class="partition">/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm> <firstterm>root</firstterm>) partition.
+ </para>
+
+ <important>
+ <title>Root and <filename
+ class="directory">/root</filename></title>
+
+ <para>
+ The <filename class="partition">/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm> root) partition is the top of the directory
+ structure. The
+ <indexterm>
+ <primary><filename class="directory">/root</filename>
+ directory</primary>
+ </indexterm> <filename class="directory">/root</filename>
+ (sometimes pronounced "slash-root") directory is the home
+ directory of the user account for system administration.
+ </para>
+ </important>
+
+ <para>
+ In the minimum configuration shown above:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ All data under the <filename
+ class="directory">/boot/</filename> directory resides on the
+ <filename class="partition">/boot</filename> partition. For
+ example, the file <filename>/boot/grub/grub.conf</filename>
+ resides on the <filename class="partition">/boot</filename>
+ partition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any file outside of the <filename
+ class="partition">/boot</filename> partition, such as
+ <filename>/etc/passwd</filename>, resides on the <filename
+ class="partition">/</filename> partition.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Subdirectories may be assigned to partitions as well. Some
+ administrators create both <filename
+ class="partition">/usr</filename> and <filename
+ class="partition">/usr/local</filename> partitions. In that
+ case, files under <filename
+ class="directory">/usr/local</filename>, such as
+ <filename>/usr/local/bin/foo</filename>, are on the <filename
+ class="partition">/usr/local</filename> partition. Any other
+ files in <filename class="directory">/usr/</filename>, such as
+ <filename>/usr/bin/foo</filename>, are in the <filename
+ class="partition">/usr</filename> partition.
+ </para>
+
+ <para>
+ If you create many partitions instead of one large <filename
+ class="partition">/</filename> partition, upgrades become
+ easier. Refer to the description of <application>Disk
+ Druid's</application> <link linkend="disk-druid-edit">Edit
+ option</link> for more information.
+ </para>
+ <tip>
+ <title>Leave Excess Capacity Unallocated</title>
+ <para>
+ 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"/>.
+ </para>
+ </tip>
+ <section id="sn-partitioning-types">
+ <title>Partition Types</title>
+
+ <para>
+ Every partition has a
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>type</secondary>
+ <seealso>file system</seealso>
+ </indexterm> <firstterm>partition type</firstterm>, to indicate
+ the format of the
+ <indexterm>
+ <primary>file system</primary>
+ </indexterm> <firstterm>file system</firstterm> on that
+ partition. The file system enables Linux to organize, search,
+ and retrieve files stored on that partition. Use the
+ <indexterm>
+ <primary><systemitem class="filesystem">ext3</systemitem>
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary
+ sortas="filesystem"><systemitem>ext3</systemitem>
+ </secondary>
+ </indexterm> <firstterm><systemitem
+ class="filesystem">ext3</systemitem></firstterm> file system
+ for data partitions that are not part of LVM, unless you have
+ specific needs that require another type of file system.
+ </para>
+ </section>
+
+ <section id="sn-partitioning-minimums">
+ <title>Minimum Partition Sizes</title>
+ <para>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.</para>
+ <segmentedlist>
+ <segtitle>Directory</segtitle>
+ <segtitle>Minimum size</segtitle>
+ <seglistitem>
+ <seg><filename class="directory">/</filename></seg>
+ <seg>250 MB</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="directory">/usr</filename></seg>
+ <seg>250 MB</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="directory">/tmp</filename></seg>
+ <seg>50 MB</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="directory">/var</filename></seg>
+ <seg>384 MB</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="directory">/home</filename></seg>
+ <seg>100 MB</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="directory">/boot</filename></seg>
+ <seg>75 MB</seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+ </section>
+ <section id="sn-partitioning-lvm">
+ <title>Understanding LVM</title>
+ <indexterm>
+ <primary>LVM</primary>
+ <secondary>understanding</secondary>
+ </indexterm>
+ <para>
+ 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">ext3</systemitem>, and a mount point.
+ </para>
+
+ <note>
+ <title>The <filename>/boot</filename> Partition and LVM</title>
+ <para>
+ The boot loader cannot read LVM volumes. You must make a
+ standard, non-LVM disk partition for your <filename
+ class="partition">/boot</filename> partition.
+ </para>
+ </note>
+
+ <para>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.</para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <note>
+ <title>LVM and the Default Partition Layout</title>
+
+ <para>
+ By default, the installation process creates <filename
+ class="partition">/</filename> and swap partitions within LVM
+ volumes, with a separate <filename>/boot</filename> partition.
+ </para>
+ </note>
+ </section>
+
+ <section id="sn-understanding-encryption">
+ <title>Understanding Encryption</title>
+ <para>
+ &DISTRO; includes functions to encrypt your storage. You may find
+ this function useful if you have a laptop or if you worry about
+ your disk storage falling out of your control. This disk
+ encryption requires you to provide an additional passphrase at
+ boot time or whenever you first access the disk storage.
+ </para>
+ <para>
+ You may choose to encrypt either all partitions, or only selected
+ ones. A typical use case includes encrypting partitions
+ containing <filename class="directory">/home</filename>, <filename
+ class="directory">/var</filename>, and <filename
+ class="directory">/tmp</filename>, along with the swap partition.
+ There is usually no need to encrypt <filename
+ class="directory">/usr</filename>, since this directory usually
+ contains only system executables and libraries that have no
+ intrinsic privacy value. The <filename
+ class="partition">/boot</filename> partition is never encrypted
+ and should not be used for sensitive data.
+ </para>
+ <note>
+ <title>Encrypted Storage Performance</title>
+ <para>
+ Storage encryption creates a slight performance decrease. You
+ may wish to weigh this drawback against the benefits of security
+ and privacy that encryption provides.
+ </para>
+ </note>
+ <para>
+ To make the encryption effective, choose a good passphrase.
+ Note the use of the term "passphrase", as opposed to the term
+ "password." This is intentional. Utilizing a phrase containing
+ multiple words increases the security of your data.
+ </para>
+ <para>
+ The encryption provided uses the Linux Unified Key System
+ (<acronym>LUKS</acronym>) for encryption. For more information on
+ LUKS, refer to <ulink url="http://luks.endorphin.org/"/>.
+ </para>
+ </section>
+
+ <section id="sn-partitioning-advice">
+ <title>Advice on Partitions</title>
+ <para>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.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ 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 &DISTRO; without erasing user data files.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Each kernel installed on your system requires
+ approximately 6 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.</para>
+ </listitem>
+ <listitem>
+ <para>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.</para>
+ <important>
+ <title>Pending Updates</title>
+ <para>Because &DISTRO; 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.
+ </para>
+ </important>
+ </listitem>
+ <listitem>
+ <para>The <filename class="directory">/usr</filename> directory
+ holds the majority of software content on a &DISTRO; 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 &DISTRO; system to learn software development
+ skills, you may want to at least double this
+ allocation.</para>
+ </listitem>
+ <listitem>
+ <para>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.</para>
+ </listitem>
+ <listitem>
+ <para>If you separate subdirectories into partitions, you can
+ retain content in those subdirectories if you decide to
+ install a new version of &DISTRO; 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.</para>
+ </listitem>
+ </itemizedlist>
+ <para>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.</para>
+ <note>
+ <title>Example Usage</title>
+ <para>This setup is not optimal for all use cases.</para>
+ </note>
+ <example id="ex-partitioning-80g">
+ <title>Example Partition Setup</title>
+ <segmentedlist>
+ <segtitle>Partition</segtitle>
+ <segtitle>Size and type</segtitle>
+ <seglistitem>
+ <seg><filename class="partition">/boot</filename></seg>
+ <seg>100 MB <systemitem class="filesystem">ext3</systemitem>
+ partition</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="partition">swap</filename></seg>
+ <seg>2 GB swap</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>LVM physical volume</seg>
+ <seg>Remaining space, as one LVM volume group</seg>
+ </seglistitem>
+ </segmentedlist>
+ <para>The physical volume is assigned to the default volume group
+ and divided into the following logical volumes:</para>
+ <segmentedlist>
+ <segtitle>Partition</segtitle>
+ <segtitle>Size and type</segtitle>
+ <seglistitem>
+ <seg><filename class="partition">/</filename></seg>
+ <seg>3 GB ext3</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="partition">/usr</filename></seg>
+ <seg>8 GB ext3</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="partition">/usr/local</filename></seg>
+ <seg>2 GB ext3</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="partition">/var</filename></seg>
+ <seg>4 GB ext3</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg><filename class="partition">/home</filename></seg>
+ <seg>50 GB ext3</seg>
+ </seglistitem>
+ </segmentedlist>
+ </example>
+ <para></para>
+ </section>
+
+ <section id="sn-general-disk-setup">
+ <title>General Disk Setup</title>
+ <para>
+ The on-screen dialog lists the available drives. By default, the
+ installation process may affect all of the drives on your
+ computer. To prevent the installation program from repartitioning
+ specific drives, clear the check box next to those drives on this
+ list.
+ </para>
+ <para>
+ By default, the installation process erases any existing Linux
+ partitions on the selected drives, and replaces them with the
+ default set of partitions for &DISTRO;. All other types of
+ partitions remain unchanged. For example, partitions used by
+ Microsoft Windows, and system recovery partitions created by the
+ computer manufacturer, are both left intact. You may choose an
+ alternative from the drop-down list:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><guilabel>Remove all partitions on selected drives and
+ create default layout</guilabel></term>
+ <listitem>
+ <para>
+ If the selected hard disks are brand new, or if you want to
+ destroy all data currently on the selected drives, use this
+ option. This option removes all partitions on all selected
+ drives, even those used by non-Linux operating systems.
+ </para>
+ <warning>
+ <title>This Option Destroys All Data</title>
+ <para>Once you have selected all installation options and
+ proceed, all data on the selected drives will be destroyed.
+ <emphasis>Use this option with caution.</emphasis></para>
+ </warning>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><guilabel>Remove linux partitions on selected drives and
+ create default layout</guilabel></term>
+ <listitem>
+ <para>
+ If the selected drives have any Linux partitions, this
+ option removes them and installs &DISTRO; into the resulting
+ free space. This option does not modify partitions assigned
+ to other non-Linux operating systems. It does not
+ discriminate, however, between partitions assigned to
+ different Linux distributions, and will remove all of them.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><guilabel>Use free space on selected drives and create
+ default layout</guilabel></term>
+ <listitem>
+ <para>
+ If the selected drives have free space that has not been
+ assigned to a partition, this option installs &DISTRO; into
+ the free space. This option ensures that no existing
+ partition is modified by the installation process.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><guilabel>Create custom layout</guilabel></term>
+ <listitem>
+ <para>
+ You manually specify the partitioning on the selected
+ drives. The next screen enables you to configure the drives
+ and partitions for your computer. If you choose this option,
+ &DISTRO; creates no partitions by default.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Select <guilabel>Encrypt system</guilabel> to encrypt all
+ partitions except the <filename class="partition">/boot</filename>
+ partition.
+ </para>
+ <para>
+ Select <guilabel>Review and modify partitioning layout</guilabel>
+ to customize the set of partitions that &DISTRO; creates, to
+ configure your system to use drives in RAID arrays, or to modify
+ the boot options for your computer. If you choose one of the
+ alternative partitioning options, this is automatically selected.
+ </para>
+ <para>
+ Use the <guilabel>Advanced storage options</guilabel> option if:
+ <itemizedlist>
+ <listitem>
+ <para>
+ You want to install &DISTRO; 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>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>You want to disable a <firstterm>dmraid</firstterm>
+ device that was detected at boot time. <!-- Need more here,
+ but how? PWF. --></para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Choose a partitioning option, and select
+ <guibutton>Next</guibutton> to proceed.
+ </para>
+ <para>
+ If you do not select an option to customize the partition layout,
+ proceed to <xref linkend="sn-disk-changes"/>. If you choose
+ <guilabel>Create custom layout</guilabel> or <guilabel>Review and
+ modify partitioning layout</guilabel>, proceed to <xref
+ linkend="sn-disk-druid"/>.
+ </para>
+
+ </section>
+ <section id="sn-disk-druid">
+ <title>Disk Druid</title>
+
+ <para>
+ <indexterm>
+ <primary>Disk Druid</primary>
+ </indexterm> <application><firstterm>Disk
+ Druid</firstterm></application> is an interactive program for
+ editing disk partitions. Users run it only within the &DISTRO;
+ installation system. Disk Druid enables you to configure
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>Linux software</secondary>
+ </indexterm> Linux software RAID and
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm> <firstterm>LVM</firstterm> to provide more extensible
+ and reliable data storage.
+ </para>
+
+ <note>
+ <title>Modifying the Default LVM Layout</title>
+
+ <para>
+ The default layout pools all of the available storage into a
+ single LVM physical volume, with one LVM logical volume for the
+ system. To make capacity available for additional partitions,
+ <guibutton>Edit</guibutton> the logical volume with the mount
+ point <filename>/</filename>, and reduce its size as necessary.
+ </para>
+ </note>
+ <para>
+ <application>Disk Druid</application> displays the following
+ actions in the installation program:
+ </para>
+
+ <variablelist>
+ <varlistentry id="vle-disk-druid-new">
+ <term><guilabel>New</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to add a partition
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>adding</secondary> </indexterm> 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.
+ </para>
+ <important>
+ <title>Illegal Partitions</title>
+
+ <para>
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>illegal</secondary>
+ </indexterm> The <filename>/bin/</filename>,
+ <filename>/dev/</filename>, <filename>/etc/</filename>,
+ <filename>/lib/</filename>, <filename>/proc/</filename>,
+ <filename>/root/</filename>, and
+ <filename>/sbin/</filename> directories may not be used
+ for separate partitions in <application>Disk
+ Druid</application>. These directories reside on the
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm> <filename>/</filename> (root) partition.
+ </para>
+
+ <para>
+ The <filename>/boot</filename> partition may not reside on
+ an LVM volume group. Create the <filename>/boot</filename>
+ partition before configuring any volume groups.
+ </para>
+ </important>
+ <para>
+ You may also choose from three options for sizing your
+ partition:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><guilabel>Fixed size</guilabel></term>
+ <listitem>
+ <para>
+ Use a fixed size as close to your entry as possible.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Fill all space up to</guilabel></term>
+ <listitem>
+ <para>
+ Grow the partition to a maximum size of your choice.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Fill to maximum allowable
+ size</guilabel></term>
+ <listitem>
+ <para>
+ Grow the partition until it fills the remainder of the
+ selected disks.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <note>
+ <title>Partition Sizes</title>
+
+ <para>
+ 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.
+ </para>
+ </note>
+ <para>
+ Select the <guilabel>Encrypt partition</guilabel> option to
+ encrypt all information on the disk partition.
+ </para>
+ <para>
+ 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="ch-rootpassword"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry id="disk-druid-edit">
+ <term><guilabel>Edit</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to edit an existing partition,
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>editing</secondary>
+ </indexterm> LVM volume group, or an LVM physical volume
+ that is not yet part of a volume group. To change the size
+ of a LVM physical volume partition, first remove it from any
+ volume groups.
+ </para>
+ <warning>
+ <title>Removing LVM Physical Volumes</title>
+
+ <para>
+ If you remove an LVM physical volume from a volume group,
+ you erase any logical volumes it contains.
+ </para>
+ </warning>
+ <para>
+ Edit a partition to change its size, mount point, or file
+ system type. Use this function to:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ correct a mistake in setting up your partitions
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ migrate Linux partitions if you are upgrading or
+ reinstalling &DISTRO;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ provide a mount point for non-Linux partitions such as
+ those used on some Windows operating systems
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ resize an existing <systemitem
+ class="filesystem">NTFS</systemitem>, <systemitem
+ class="filesystem">ext2</systemitem>, or <systemitem
+ class="filesystem">ext3</systemitem> partition
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>Windows Partitions</title>
+ <para>
+ You may not label Windows partitions that use the
+ <indexterm>
+ <primary><systemitem
+ class="filesystem">NTFS</systemitem>
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
+ class="filesystem">NTFS</systemitem>
+ </secondary>
+ </indexterm> <systemitem
+ class="filesystem">NTFS</systemitem> file system with a
+ mount point in the &DISTRO; installer. You may label
+ <indexterm>
+ <primary><systemitem
+ class="filesystem">vfat</systemitem>
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
+ class="filesystem">vfat</systemitem>
+ </secondary>
+ </indexterm> <firstterm><systemitem
+ class="filesystem">vfat</systemitem></firstterm>
+ (<systemitem class="filesystem">FAT16</systemitem> or
+ <systemitem class="filesystem">FAT32</systemitem>)
+ partitions with a mount point.
+ </para>
+ </note>
+ <para>
+ If you need to make <emphasis>drastic</emphasis> changes to
+ your partition configuration, you may want to delete
+ partitions and start again. If your disk contains data that
+ you need to keep, back it up before you edit any partitions.
+ If you edit the size of a partition, you may lose all data
+ on it.
+ </para>
+ <para>
+ If your system contains many separate partitions for system
+ and user data, it is easier to upgrade your system. The
+ installation program allows you to erase or retain data on
+ specific partitions. If your user data is on a separate
+ <indexterm>
+ <primary>partition</primary>
+ <secondary><filename>/home</filename>
+ </secondary>
+ </indexterm> <filename>/home</filename> partition, you can
+ retain that data while erasing system partitions such as
+ <filename>/boot</filename>.
+ </para>
+ <para>
+ To change the partition's mount point, enter the new mount
+ point in the space provided. To resize the partition,
+ select <guilabel>Resize</guilabel> and enter a new size, or
+ click and hold the arrow controls to dial the size up or
+ down as needed. To encrypt the partition, select
+ <guilabel>Encrypt</guilabel> and provide a passphrase by
+ typing it twice at the prompt. Refer to <xref
+ linkend="ch-rootpassword"/> for information on using good
+ passphrases.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Delete</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to erase an existing partition
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>deleting</secondary>
+ </indexterm> or LVM physical volume. To delete an LVM
+ physical volume, first delete any volume groups of which
+ that physical volume is a member.
+ </para>
+ <para>
+ If you make a mistake, use the <guilabel>Reset</guilabel>
+ option to abandon all the changes you have made.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Reset</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to force <application>Disk
+ Druid</application> to abandon all changes made to disk
+ partitions.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>RAID</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to set up software RAID
+ <indexterm>
+ <primary>RAID</primary>
+ </indexterm> on your &FED; system.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><guilabel>Create a software RAID
+ partition</guilabel></term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Create a RAID device</guilabel></term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>Clone a drive to create a RAID
+ device</guilabel></term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><guilabel>LVM</guilabel></term>
+ <listitem>
+ <para>
+ Select this option to set up LVM
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm> on your &FED; system. First create at least one
+ partition or software RAID device as an LVM physical volume,
+ using the <application>New</application> dialog. For more
+ information on LVM, refer to <xref
+ linkend="sn-partitioning-lvm"/>.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ <important>
+ <title>LVM Unavailable in Text Installs</title>
+ <para>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>.</para>
+ </important>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ After you finish setting up and reviewing your partition
+ configuration, select <guilabel>Next</guilabel> to continue the
+ installation process.
+ </para>
+ </section>
+
+ <section id="sn-disk-changes">
+ <title>Making Disk Changes</title>
+ <para>
+ To proceed, the installer makes important changes to the disk
+ configuration. This is the last point at which you can quit the
+ installer and still retain your original system configuration. If
+ you have chosen to resize existing Windows NTFS partitions without
+ erasing or formatting them, the data in those partitions is
+ retained.
+ </para>
+ <para>
+ Select <guilabel>Write changes to disk</guilabel> to proceed.
+ </para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/expert-quickstart.xml b/en-US/expert-quickstart.xml
new file mode 100644
index 0000000..220ea6b
--- /dev/null
+++ b/en-US/expert-quickstart.xml
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
+%FDP-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-experts-quickstart">
+ <title>Quick Start for Experts</title>
+ <para>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.</para>
+ <warning>
+ <title>Experts Only</title>
+ <para>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.</para>
+ </warning>
+ <section id="sn-expert-overview">
+ <title>Overview</title>
+ <para>The installation procedure is fairly simple, and consists of
+ only a few steps:</para>
+ <orderedlist>
+ <listitem>
+ <para>Download files to make media or another bootable
+ configuration.</para>
+ </listitem>
+ <listitem>
+ <para>Prepare system for installation.</para>
+ </listitem>
+ <listitem>
+ <para>Boot the computer and run the installation process.</para>
+ </listitem>
+ <listitem>
+ <para>Reboot and perform post-installation configuration.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="sn-expert-download">
+ <title>Download Files</title>
+ <para>Do any one of the following:</para>
+ <tip>
+ <title>Verify your downloads</title>
+ <para>Downloads may fail for any number of reasons. Always verify
+ the sha1sum of the downloaded files.</para>
+ </tip>
+ <orderedlist>
+ <listitem>
+ <indexterm>
+ <primary>ISO images</primary>
+ <secondary>downloading</secondary>
+ </indexterm>
+ <para>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.</para>
+ </listitem>
+ <listitem>
+ <para>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.</para>
+ </listitem>
+ <listitem>
+ <para>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.</para>
+ </listitem>
+ <listitem>
+ <para>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.</para>
+ </listitem>
+ <listitem>
+ <para>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"/>.</para>
+ <para>For information on setting up a network boot server from
+ which you can install &DISTRO;, refer to <xref
+ linkend="ap-install-server"/>.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section id="sn-expert-prepare">
+ <title>Prepare for Installation</title>
+ <indexterm>
+ <primary>NTFS partitions</primary>
+ <secondary>resizing</secondary>
+ </indexterm>
+ <para>Back up any user data you need to preserve.</para>
+ <tip>
+ <title>Resizing Partitions</title>
+ <para>The installation program provides functions for resizing
+ ext2, ext3, ext4, and NTFS formatted partitions. Refer to <xref
+ linkend="ch-disk-partitioning" /> for more information.</para>
+ </tip>
+ </section>
+ <section id="sn-expert-install">
+ <title>Install &DISTRO;</title>
+ <para>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.</para>
+ <para>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.</para>
+ </section>
+ <section id="sn-expert-post-install">
+ <title>Perform Post-installation Steps</title>
+ <para>After the system reboots, it displays additional configuration
+ options. Make appropriate changes to your system and proceed to
+ the login prompt.</para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/firstboot.xml b/en-US/firstboot.xml
new file mode 100644
index 0000000..5ae6f90
--- /dev/null
+++ b/en-US/firstboot.xml
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-firstboot">
+ <title>First Boot</title>
+ <indexterm>
+ <primary>Setup Agent</primary>
+ </indexterm>
+ <para>
+ The <application>Setup Agent</application> launches the first time
+ that you start a new &FC; system. Use <application>Setup
+ Agent</application> to configure the system for use before you log
+ in.
+ </para>
+ <para>
+ Select <guibutton>Forward</guibutton> to start the
+ <application>Setup Agent</application>.
+ </para>
+ <note>
+ <title>Graphical Interface Required</title>
+
+ <para>
+ <application>Setup Agent</application> requires a graphical
+ interface. If you did not install one, or if &FED; has trouble
+ starting it, you may see a slightly different setup screen.
+ </para>
+ </note>
+ <section id="sn-firstboot-license">
+ <title>License Agreement</title>
+
+ <para>
+ This screen displays the overall licensing terms for
+ &DISTRO;. Each software package in &DISTRO; is covered by its own
+ license. All licensing guidelines for &DISTRO; are located at
+ <ulink url='http://fedoraproject.org/wiki/Legal/Licenses'/>.
+ </para>
+ <para>
+ To proceed, select <guilabel>Understood, please proceed</guilabel>
+ and then select <guibutton>Forward</guibutton>.
+ </para>
+ </section>
+ <section id="sn-firstboot-systemuser">
+ <title>System User</title>
+
+ <para>
+ Create a user account for yourself with this screen. Always use
+ this account to log in to your &FC; system, rather than using the
+ <systemitem class="username">root</systemitem> account.
+ </para>
+ <para>
+ 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="ch-rootpassword" /> for guidelines on selecting a
+ secure password.
+ </para>
+ <tip>
+ <title>Creating Extra User Accounts</title>
+ <para>
+ 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>.
+ </para>
+ </tip>
+ <para>
+ To configure &FC; to use network services for authentication or
+ user information, select <guibutton>Use Network
+ Login...</guibutton>.
+ </para>
+ </section>
+
+<section id="sn-firstboot-datetime">
+ <title>Date and Time</title>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ The initial display enables you to set the date and time of your
+ system manually.
+ </para>
+ <para>
+ Select the <guilabel>Network Time Protocol</guilabel> tab to
+ configure your system to use NTP servers instead.
+ </para>
+ <tip>
+ <title>Setting the Clock</title>
+ <para>
+ To change these settings later, choose <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>Date &
+ Time</guimenuitem> </menuchoice>.
+ </para>
+ </tip>
+ <para>
+ 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.
+ </para>
+ <para>
+ By default, &FC; 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.
+ </para>
+
+ <para>
+ 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>.
+ </para>
+ <para>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.</para>
+ <important>
+ <title>Laptops and NTP</title>
+ <para>Do not use this option with laptop computers that sometimes
+ use wireless networks.</para>
+ </important>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ If you enable the <guilabel>Enable NTP Broadcast</guilabel>
+ advanced option, &FC; attempts to automatically locate time
+ servers on the network.
+ </para>
+ </section>
+ <section id="sn-smolt">
+ <title>Hardware Profile</title>
+ <para>
+ The <application>Setup Agent</application> displays a screen that
+ allows you to anonymously submit your hardware information to the
+ &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/"/>.
+ </para>
+ <para>
+ 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>Next</guilabel> to
+ continue to the login screen.
+ </para>
+ <important>
+ <title>Update Your System</title>
+
+ <para>
+ 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
+ &FED; system.
+ </para>
+ </important>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/installingpackages.xml b/en-US/installingpackages.xml
new file mode 100644
index 0000000..36bbf9a
--- /dev/null
+++ b/en-US/installingpackages.xml
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-installing-packages">
+ <title>Installing Packages</title>
+
+ <para>
+ &FC; 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, &FC;
+ prompts you to change discs periodically. After you insert a disc,
+ select <guibutton>OK</guibutton> to resume the installation.
+ </para>
+
+ <para>
+ After installation completes, select <guibutton>Reboot</guibutton>
+ to restart your computer. &FC; ejects any loaded discs before the
+ computer reboots.
+ </para>
+ <note>
+ <title>Installing from a Live Image</title>
+ <para>If you install from a &DISTRO; 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
+ &DISTRO; system.</para>
+ </note>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/intro.xml b/en-US/intro.xml
new file mode 100644
index 0000000..ce52926
--- /dev/null
+++ b/en-US/intro.xml
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
+%FDP-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-introduction">
+ <title>Introduction</title>
+ <para>This guide covers installation of &DISTRO;, a Linux distribution
+ built on free and open source software. This manual helps you
+ install &DISTRO; 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, &DISTRO; provides a complete desktop operating system,
+ including productivity applications, Internet utilities, and desktop
+ tools.</para>
+ <para>This document does not detail all of the features of the
+ installation system.</para>
+ <section id="sn-background">
+ <title>Background</title>
+ <section id="sn-about-fedora">
+ <title>About &DISTRO;</title>
+ <para>To find out more about &DISTRO;, refer to <ulink
+ url="http://fedoraproject.org/"/>. To read other documentation
+ on &DISTRO; related topics, refer to <ulink
+ url="http://docs.fedoraproject.org/"/>.</para>
+ </section>
+ <section id="sn-additional-help">
+ <title>Getting Additional Help</title>
+ <para>For information on additional help resources for &DISTRO;,
+ visit <ulink
+ url="http://fedoraproject.org/wiki/Communicate"/>.</para>
+ </section>
+ </section>
+ <section id="sn-about-document">
+ <title>About This Document</title>
+ <section id="sn-goals">
+ <title>Goals</title>
+ <para>This guide helps a reader:</para>
+ <orderedlist>
+ <listitem>
+ <para>Understand how to locate the &DISTRO; distribution
+ online</para>
+ </listitem>
+ <listitem>
+ <para>Create configuration data that allows a computer to boot
+ &DISTRO;</para>
+ </listitem>
+ <listitem>
+ <para>Understand and interact with the &DISTRO; installation
+ program</para>
+ </listitem>
+ <listitem>
+ <para>Complete basic post-installation configuration of a
+ &DISTRO; system</para>
+ </listitem>
+ </orderedlist>
+ <tip>
+ <title>Other Sources of Documentation</title>
+ <para>This guide does not cover use of &DISTRO;. To learn how to
+ use an installed &DISTRO; system, refer to <ulink
+ url="http://docs.fedoraproject.org/"/> for other
+ documentation.</para>
+ </tip>
+ </section>
+ <section id="sn-audience">
+ <title>Audience</title>
+ <para>This guide is intended for new and intermediate &DISTRO;
+ users. Advanced &DISTRO; 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/"/>.</para>
+ </section>
+ </section>
+ <section id="sn-feedback">
+ <title>Feedback</title>
+ <indexterm>
+ <primary>&FDPX;</primary>
+ <see>&FDP;</see>
+ </indexterm>
+ <indexterm>
+ <primary>&FDP;</primary>
+ </indexterm>
+ <para>The &FDP; (&FDPX;) is a group of volunteer writers, editors,
+ translators, and other contributors who create content for free
+ and open source software. The &FDPX; maintains this document and is
+ always interested in reader feedback.</para>
+ <para>To send feedback regarding this document, file a bug
+ in &BZ;. To file a bug, fill in "&BZ-PROD;" as the Product, choose
+ the name of this document from the Component list, and choose
+ "devel" as the version. &FDPX; volunteers receive your feedback, and
+ may contact you for additional information, if necessary.</para>
+ </section>
+</chapter>
diff --git a/en-US/locale.xml b/en-US/locale.xml
new file mode 100644
index 0000000..cc06b0f
--- /dev/null
+++ b/en-US/locale.xml
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-installer-locale">
+ <title>Identifying Your Locale</title>
+ <section id="sn-installer-language">
+ <title>Language Selection</title>
+
+ <para>
+ The installation program displays a list of languages supported by
+ &DISTRO;. Highlight the correct language on the list and select
+ <guibutton>Next</guibutton>.
+ </para>
+
+ <para>
+ To select support for additional languages, customize the
+ installation at the package selection stage. For more information,
+ refer to <xref linkend="sn-lang-packages"></xref>.
+ </para>
+ <note>
+ <title>Installing from &DISTRO; Live Media</title>
+ <para>If you install from &DISTRO; Live Media, you may not see a
+ locale selection screen. For additional locale support, use the
+ <application>Add/Remove Software</application> application after
+ you boot your newly installed &DISTRO; system, following
+ installation.</para>
+ </note>
+ </section>
+ <section id="sn-installer-keyboard">
+ <title>Keyboard Configuration</title>
+
+ <para>
+ The installation program displays a list of the keyboard layouts
+ supported by &DISTRO;. Highlight the correct layout on the list, and
+ select <guibutton>Next</guibutton>.
+ </para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+<!--
+vim: softtabstop=2:shiftwidth=2:expandtab:textwidth=72
+-->
diff --git a/en-US/medialess.xml b/en-US/medialess.xml
new file mode 100644
index 0000000..2d6ecf4
--- /dev/null
+++ b/en-US/medialess.xml
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
+%FDP-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<appendix id='ap-medialess-install'>
+ <title>Installing Without Media</title>
+ <para>This section discusses how to install &DISTRO; 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.</para>
+ <important>
+ <title>Linux Required</title>
+ <para>This procedure assumes you are already using &DISTRO; or
+ another relatively modern Linux distribution, and the
+ <application>GRUB</application> boot loader. It also assumes you
+ are a somewhat experienced Linux user.</para>
+ </important>
+ <section id="sn-medialess-getting-files">
+ <title>Retrieving Boot Files</title>
+ <para>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.</para>
+ <procedure>
+ <step>
+ <para>Download a Live image or DVD distribution, or to locate an
+ installation mirror, visit <ulink
+ url="http://mirrors.fedoraproject.org/publiclist/Fedora/&DISTROVER;/"/>.</para>
+ </step>
+ <step>
+ <para>Locate the <filename
+ class="directory">isolinux/</filename> folder using one of
+ the following methods:</para>
+ <itemizedlist>
+ <listitem>
+ <para>If you chose to download an image, open it with the
+ appropriate desktop tool. If you are using &DISTRO;,
+ double-click the file to open it with the
+ <application>Archive Manager</application>. Open the
+ <filename class="directory">isolinux/</filename>
+ folder.</para>
+ </listitem>
+ <listitem>
+ <para>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/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os/isolinux/</filename>
+ folder.</para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>Installation Types Available</title>
+ <para>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.</para>
+ </note>
+ </step>
+ <step>
+ <para>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.</para>
+ </step>
+ </procedure>
+ </section>
+ <section id="sn-medialess-editing-grub-conf">
+ <title>Editing the <application>GRUB</application>
+ Configuration</title>
+ <para>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.</para>
+ <para>A minimal boot stanza looks like the following listing:</para>
+ <screen><![CDATA[title Installation
+ root (hd0,0)
+ kernel /vmlinuz-install
+ initrd /initrd.img-install]]></screen>
+ <para>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"/>.</para>
+ <para>The following options are generally useful for medialess
+ installations:</para>
+ <itemizedlist>
+ <listitem>
+ <para><option>ip=</option></para>
+ </listitem>
+ <listitem>
+ <para><option>method=</option></para>
+ </listitem>
+ <listitem>
+ <para><option>lang=</option></para>
+ </listitem>
+ <listitem>
+ <para><option>keymap=</option></para>
+ </listitem>
+ <listitem>
+ <para><option>ksdevice=</option> (if installation requires an
+ interface other than eth0)</para>
+ </listitem>
+ <listitem>
+ <para><option>vnc</option> and <option>vncpassword=</option> for
+ a remote installation</para>
+ </listitem>
+ </itemizedlist>
+ <para>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:</para>
+ <screen><![CDATA[default 0]]></screen>
+ </section>
+ <section id="sn-medialess-booting">
+ <title>Booting to Installation</title>
+ <para>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.</para>
+ </section>
+</appendix>
diff --git a/en-US/networkconfig.xml b/en-US/networkconfig.xml
new file mode 100644
index 0000000..5fad0db
--- /dev/null
+++ b/en-US/networkconfig.xml
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-networkconfig">
+ <title>Network Configuration</title>
+
+ <para>Setup simply prompts for the hostname and the settings used
+ during installation are written to the system. Many networks have a <indexterm>
+ <primary>DHCP (Dynamic Host Configuration Protocol)</primary>
+ </indexterm> <firstterm>DHCP</firstterm> (Dynamic Host Configuration
+ Protocol) service that automatically supplies connected systems with
+ domain name, leaving the user to enter a host name. By default, &FC; activates all network
+ interfaces on your computer and configures them to use DHCP.
+ </para>
+ <indexterm>
+ <primary>IPv4</primary>
+ </indexterm>
+ <para>&DISTRO; contains support for both
+ <firstterm>IPv4</firstterm> and <firstterm>IPv6</firstterm>. However, by
+ default, &DISTRO; 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. </para>
+
+ <note>
+ <title>Modem Configuration</title>
+ <para>
+ The installation program does not configure
+ <indexterm> <primary>modem</primary>
+ </indexterm> 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).
+ </para>
+ </note>
+
+ <section id="sn-hostname">
+ <title>Hostname</title>
+
+ <para>
+ On some networks, the DHCP provider also provides the name of the
+ computer, or <indexterm>
+ <primary>hostname</primary>
+ </indexterm> <firstterm>hostname</firstterm>. 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>.
+ </para>
+ <para>To set up a home network that is behind an Internet firewall
+ or router, you may want to use <systemitem
+ class="fqdomainname"><replaceable>hostname</replaceable>.localdomain</systemitem>
+ for your &DISTRO; system. If you have more than one computer on
+ this network, you should give each one a separate host name in
+ this domain.</para>
+ <tip>
+ <title>Valid Hostnames</title>
+ <para>
+ You may give your system any name provided that the full
+ hostname is unique. The hostname may include letters, numbers
+ and hyphens.
+ </para>
+ </tip>
+ <para>If your &DISTRO; 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.</para>
+ </section>
+<!--
+ <section id="sn-network-misc-settings">
+ <title>Miscellaneous Settings</title>
+ <para>
+ To manually configure a network interface, you may also provide
+ other network settings for your computer. All of these settings
+ are the IP addresses of other systems on the network.
+ </para>
+
+ <para>
+ A <firstterm>gateway</firstterm> <indexterm>
+ <primary>gateway</primary>
+ </indexterm> is the device that provides access to other networks.
+ Gateways are also referred to as <indexterm>
+ <primary>router</primary>
+ <see>gateway</see>
+ </indexterm> <firstterm>routers</firstterm>. If your system
+ connects to other networks through a gateway, enter its IP address
+ in the <guilabel>Gateway</guilabel> box.
+ </para>
+
+ <para>
+ Most software relies on the <indexterm>
+ <primary>DNS (Domain Name Service)</primary>
+ </indexterm> <firstterm>DNS</firstterm> (Domain Name Service)
+ provider to locate machines and services on the network. DNS
+ converts hostnames to IP addresses and vice versa. A &FC; system
+ may use more than one DNS server. If the primary DNS server does
+ not respond, the computer sends any query to the secondary DNS
+ server, and so on. To assign DNS servers, type their IP addresses
+ into the <guilabel>Primary DNS</guilabel> or <guilabel>Secondary
+ DNS</guilabel> boxes.
+ </para>
+
+ <para>
+ Select <guibutton>Next</guibutton> once you are satisfied with the
+ network settings for your system.
+ </para>
+
+ </section>
+Commented out this section since network configuration is really transparent now. DJN
+-->
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/new-users.xml b/en-US/new-users.xml
new file mode 100644
index 0000000..9f6e633
--- /dev/null
+++ b/en-US/new-users.xml
@@ -0,0 +1,489 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
+%FDP-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-new-users">
+ <title>New Users</title>
+ <para>
+ This chapter explains how to get the files you need to install and
+ run &DISTRO; 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/"/>.
+ </para>
+ <tip>
+ <title>Download Links</title>
+ <para>
+ To follow a Web-based guide to downloading, visit <ulink
+ url="http://get.fedoraproject.org/"/>. For guidance on which
+ architecture to download, refer to <xref
+ linkend="sn-which-arch"/>.
+ </para>
+ </tip>
+ <section id="sn-howto-download">
+ <title>How Do I Download Installation Files?</title>
+ <para>The &FP; distributes &DISTRO; 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:</para>
+ <itemizedlist>
+ <listitem>
+ <para>A full set of the software on DVD media</para>
+ </listitem>
+ <listitem>
+ <para>Live images you can use to try &DISTRO;, and then install
+ to your system if you so choose</para>
+ </listitem>
+ <listitem>
+ <para>Reduced-size bootable CD and USB flash disk images you can
+ use to install over an Internet connection</para>
+ </listitem>
+ <listitem>
+ <para>Source code on DVD media</para>
+ </listitem>
+ </itemizedlist>
+ <para>Most users want the &DISTRO; 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 &DISTRO;
+ on one computer. Source code discs are not used for installing &DISTRO;,
+ but are resources for experienced users and software developers.</para>
+ <tip>
+ <title>Downloading media</title>
+ <indexterm>
+ <primary>CD/DVD media</primary>
+ <secondary>downloading</secondary>
+ <seealso>ISO images</seealso>
+ </indexterm>
+ <indexterm>
+ <primary>ISO images</primary>
+ <secondary>downloading</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>USB flash media</primary>
+ <secondary>downloading</secondary>
+ </indexterm>
+ <para>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.</para>
+ <para>For more information on burning CDs and DVDs, refer to
+ <xref linkend="sn-making-media"/>.</para>
+ </tip>
+ <para>&DISTRO; software is available for download at no cost in a
+ variety of ways. </para>
+ <section id="sn-which-download-mirror">
+ <title>From a Mirror</title>
+ <indexterm>
+ <primary>mirror</primary>
+ </indexterm>
+ <para>To find the freely downloadable distributions of &DISTRO;,
+ look for a <firstterm>mirror</firstterm>. A mirror is a computer
+ server open to the public for free downloads of
+ software, including &DISTRO;. Mirrors offer both free open
+ source software and closed source software. To locate a mirror, visit <ulink
+ url="http://mirrors.fedoraproject.org/publiclist"/> 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.</para>
+ <para>Mirrors publish &DISTRO; software under a well-organized
+ hierarchy of folders. For example, the &DISTRO; &DISTROVER;
+ distribution normally appears in the directory <filename
+ class="directory">&FEDLC;/linux/releases/&DISTROVER;/</filename>.
+ This directory contains a folder for each architecture supported
+ by that release of &DISTRO;. 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 &DISTRO; &DISTROVER; for x86_64 at
+ <filename>&FEDLC;/linux/releases/&DISTROVER;/x86_64/iso/&FCX;-&DISTROVER;-x86_64-DVD.iso</filename>.</para>
+ </section>
+ <section id="sn-which-download-bt">
+ <title>From BitTorrent</title>
+ <indexterm>
+ <primary>BitTorrent</primary>
+ </indexterm>
+ <indexterm>
+ <primary>BitTorrent</primary>
+ <secondary>seeding</secondary>
+ </indexterm>
+ <para>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.</para>
+ <para>If your computer does not have software installed for
+ BitTorrent, visit the BitTorrent home page at <ulink
+ url="http://www.bittorrent.com/download/"/> to download it.
+ BitTorrent client software is available for Windows, Mac OS,
+ Linux, and many other operating systems.</para>
+ <para>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 &DISTRO;
+ BitTorrent files, visit <ulink
+ url="http://torrent.fedoraproject.org/"/>.</para>
+ <tip>
+ <title>Minimal Boot Images</title>
+ <para>Minimal boot CD and USB flash disk images are not
+ available through BitTorrent.</para>
+ </tip>
+ </section>
+ </section>
+ <section id="sn-which-arch">
+ <title>Which Architecture Is My Computer?</title>
+ <indexterm>
+ <primary>architecture</primary>
+ </indexterm>
+ <para>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.</para>
+ <indexterm>
+ <primary>architecture</primary>
+ <secondary>determining</secondary>
+ </indexterm>
+ <segmentedlist id="List-Processor_and_Architecture_Types">
+ <title>Processor and Architecture Types</title>
+ <segtitle>Processor Manufacturer and Model</segtitle>
+ <segtitle>Architecture Type for &DISTRO;</segtitle>
+ <seglistitem>
+ <seg>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; Apple MacBook
+ Pro</seg>
+ <seg><systemitem>i386</systemitem></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Intel Atom 230, Atom 330, Core 2 Duo, Centrino Core 2 Duo, and Xeon; AMD
+ Athlon 64, Athlon x2, Sempron64, and Opteron</seg>
+ <seg><systemitem>x86_64</systemitem></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Apple Macintosh G3, G4, G5, PowerBook, and other non-Intel
+ models</seg>
+ <seg><systemitem>ppc</systemitem></seg>
+ </seglistitem>
+ </segmentedlist>
+ <tip>
+ <title><systemitem>i386</systemitem> Works for Most Windows
+ Compatible Computers</title>
+ <para>If you are unsure what type of processor your computer uses, choose
+ <systemitem>i386</systemitem>.</para>
+ <para>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.</para>
+ </tip>
+ <tip>
+ <title>Intel Atom Processor Architectures Vary</title>
+ <para>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"/> for more details. </para>
+ </tip>
+ </section>
+ <section id="sn-which-files">
+ <title>Which Files Do I Download?</title>
+ <para>You have several options to download &DISTRO;. Read the
+ options below to decide the best one for you.</para>
+ <para>Each file available for download in a &DISTRO; distribution
+ includes the architecture type in the file name. For example, the file for
+ the DVD distribution of &DISTRO; &DISTROVER; for x86_64 is named
+ <filename>&DISTRO;-&DISTROVER;-x86_64-DVD.iso</filename>. Refer to
+ <xref
+ linkend="sn-which-arch"/> if you are unsure of your computer's
+ architecture.</para>
+ <orderedlist>
+ <listitem>
+ <formalpara>
+ <title>Full Distribution on DVD</title>
+ <para>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
+ &DISTRO; system in an emergency. You can download the DVD
+ version directly from a mirror, or via BitTorrent.</para>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Live Image</title>
+ <para>If you want to try &DISTRO; 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 <guiicon>Install to
+ Hard Disk</guiicon> desktop shortcut. If you decide you
+ like what you see, and want to install it, simply activate
+ the selection to copy &DISTRO; to your hard disk. You can
+ download the Live image directly from a mirror, or using
+ BitTorrent.</para>
+ </formalpara>
+ <!-- <note>
+ <title>No Live Images for <systemitem>ppc</systemitem></title>
+ <para>&DISTRO; does not offer Live images available for the
+ <systemitem>ppc</systemitem> architecture due to resource
+ constraints.</para>
+ </note> -->
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Minimal Boot Media</title>
+ <para>If you have a fast Internet connection but do not want
+ to download the entire distribution, you can download a
+ small boot image. &DISTRO; offers images for a minimal boot
+ environment on CD. Once you boot your system with the minimal
+ media, you can install &DISTRO; 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.</para>
+ </formalpara>
+ <tip>
+ <title>Download Size</title>
+ <para>Installing the default software for &DISTRO; 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.</para>
+ </tip>
+ </listitem>
+ </orderedlist>
+ <para>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.</para>
+ <segmentedlist>
+ <title>Locating Files</title>
+ <segtitle>Media Type</segtitle>
+ <segtitle>File Locations</segtitle>
+ <seglistitem>
+ <seg>Full distribution on DVD</seg>
+ <seg><filename>&FEDLC;/linux/releases/&DISTROVER;/&FED;/<replaceable>arch</replaceable>/iso/&FCX;-&DISTROVER;-<replaceable>arch</replaceable>-DVD.iso</filename></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Live image</seg>
+ <seg><filename>&FEDLC;/linux/releases/&DISTROVER;/Live/<replaceable>arch</replaceable>/iso/&FCX;-&DISTROVER;-<replaceable>arch</replaceable>-Live.iso</filename>,
+ <filename>&FEDLC;/linux/releases/&DISTROVER;/Live/<replaceable>arch</replaceable>/iso/&FCX;-&DISTROVER;-KDE-<replaceable>arch</replaceable>-Live.iso</filename></seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>Minimal CD boot media</seg>
+ <seg><filename>&FEDLC;/linux/releases/&DISTROVER;/&FED;/<replaceable>arch</replaceable>/os/images/boot.iso</filename></seg>
+ </seglistitem>
+ </segmentedlist>
+ </section>
+ <section id="sn-making-media">
+ <title>How Do I Make &DISTRO; Media?</title>
+ <para>
+ A &DISTRO; ISO file can be turned into either CD or DVD discs.
+ Turn &DISTRO; Live ISO files into bootable USB media, as well as
+ a CD or DVD.
+ </para>
+ <section id="sn-making-disc-media">
+ <title>Making CD or DVD Discs</title>
+ <para>
+ To learn how to turn ISO images into CD or DVD media, refer to
+ <ulink
+ url="http://docs.fedoraproject.org/readme-burning-isos/"/>.</para>
+ </section>
+ <section>
+ <title>Making USB Media</title>
+ <para>
+ To make bootable USB media, use a &DISTRO; Live image. Use
+ either a Windows or Linux system to make the bootable USB media.
+ </para>
+ <note>
+ <title>USB Image Writing is Nondestructive</title>
+ <para>
+ Writing the Live image to the USB media is
+ <emphasis>nondestructive</emphasis>. Any existing data on the
+ media is not harmed.
+ </para>
+ <para>
+ <emphasis>It is always a good idea to back up important data
+ before performing sensitive disk operations.</emphasis>
+ </para>
+ </note>
+ <para>
+ 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>
+ </para>
+ <section>
+ <title>USB Image Creation from Windows</title>
+ <procedure>
+ <step>
+ <para>
+ Download a Live ISO file as explained in <xref linkend="sn-which-files"/>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Download the Windows
+ <application>liveusb-creator</application> program at <ulink
+ url="http://fedorahosted.org/liveusb-creator"/>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Follow the instructions given at the site and in the
+ <application>liveusb-creator</application> program to create
+ the bootable USB media.
+ </para>
+ </step>
+ </procedure>
+ </section>
+ <section>
+ <title>USB Image Creation in Linux</title>
+ <procedure>
+ <para>
+ 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.
+ </para>
+ <important>
+ <title>Unusual USB Media</title>
+ <para>
+ In a few cases with oddly formatted or partitioned USB
+ media, the image writing may fail.
+ </para>
+ </important>
+ <step>
+ <para>
+ Download a Live ISO file as shown in <xref
+ linkend="sn-which-files"/>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Install the <package>livecd-tools</package> package on your
+ system. For &FED; systems, use the following command:
+ </para>
+ <screen><![CDATA[su -c 'yum -y install livecd-tools']]></screen>
+ </step>
+ <step>
+ <para>
+ Plug in your USB media.
+ </para>
+ </step>
+ <step>
+ <para>
+ 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>:
+ </para>
+ <screen><![CDATA[su -c 'findfs LABEL="]]><replaceable>MyLabel</replaceable><![CDATA["']]></screen>
+ <para>
+ 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:
+ </para>
+ <screen><![CDATA[su -c 'less /var/log/messages']]></screen>
+ </step>
+ <step>
+ <para>
+ Use the <command>livecd-iso-to-disk</command> command to
+ write the ISO image to the media:
+ </para>
+ <screen><![CDATA[su -c 'livecd-iso-to-disk ]]><replaceable>the_image.iso</replaceable><![CDATA[ /dev/]]><replaceable>sdX1</replaceable><![CDATA[']]></screen>
+ <para>
+ 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.
+ </para>
+ </step>
+ </procedure>
+ </section>
+ </section>
+ </section>
+ <section id="sn-cannot-download">
+ <title>What If I Cannot Download &DISTRO;?</title>
+ <para>If you do not have a fast Internet connection, or if you have
+ a problem creating boot media, downloading may not be an option.
+ &DISTRO; 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"/>.</para>
+ </section>
+ <section id="sn-start-installation">
+ <title>How Do I Start the Installation Program?</title>
+ <indexterm>
+ <primary>BIOS (Basic Input/Output System)</primary>
+ </indexterm>
+ <indexterm>
+ <primary>CD/DVD media</primary>
+ <secondary>booting</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>USB flash media</primary>
+ <secondary>booting</secondary>
+ </indexterm>
+ <para>To start the installation program from minimal boot media, a
+ Live image, or the distribution DVD, follow this procedure:</para>
+ <procedure>
+ <step>
+ <para>Power off your computer system.</para>
+ </step>
+ <step>
+ <para>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.</para>
+ </step>
+ <step>
+ <para>Insert the media in your computer and turn it on.</para>
+ </step>
+ </procedure>
+ <para>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.</para>
+ <tip>
+ <title>Configuring the BIOS</title>
+ <para>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.</para>
+ </tip>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+<!--
+vim: softtabstop=2:shiftwidth=2:expandtab:textwidth=72
+-->
diff --git a/en-US/nextsteps.xml b/en-US/nextsteps.xml
new file mode 100644
index 0000000..aa73ad9
--- /dev/null
+++ b/en-US/nextsteps.xml
@@ -0,0 +1,405 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-next-steps">
+ <title>Your Next Steps</title>
+ <para>
+ &FED; provides you with a complete operating system with a vast
+ range of capabilities, supported by a large community.
+ </para>
+ <section id="sn-system-updating">
+ <title>Updating Your System</title>
+
+ <para>
+ The &PROJECT; releases updated software packages for &DISTRO;
+ 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 &DISTRO;
+ announcements services.
+ </para>
+ <para>
+ An update applet reminds you of updates when they are available.
+ This applet is installed by default in &DISTRO;. 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.
+ </para>
+ <para>
+ To update your system with the latest packages manually, use the
+ <indexterm>
+ <primary>Update System</primary>
+ </indexterm> <application>Update System</application>:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Choose <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu>
+ <guimenuitem>Update System</guimenuitem>
+ </menuchoice>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To review the list of updated packages, select
+ <guilabel>Review</guilabel>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Click <guibutton>Update System</guibutton> to begin the update
+ process.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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>
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ 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>:
+ </para>
+<screen>
+<userinput>su -c 'yum update'</userinput>
+</screen>
+ <para>
+ Enter the <systemitem
+ class="username">root</systemitem> password
+ when prompted.
+ </para>
+
+ <para>
+ Refer to <ulink url="http://docs.fedoraproject.org/yum/"/> for
+ more information on <command>yum</command>.
+ </para>
+
+ <note>
+ <title>Network Connection Required</title>
+
+ <para>
+ 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.
+ </para>
+ </note>
+ <para>
+ If your &FED; 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"/>.
+ </para>
+ </section>
+ <section id="sn-finishing-upgrade">
+ <title>Finishing an Upgrade</title>
+ <important>
+ <title>System Updates Recommended</title>
+ <para>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.</para>
+ </important>
+ <para>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.</para>
+ <para>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:</para>
+ <screen><command><![CDATA[awk '{print $1}' ~/old-pkglist.txt | grep 'release$']]></command></screen>
+ <para>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 &DISTRO; system.</para>
+ <para>Then run the following commands to make a list of other
+ missing software packages:</para>
+
+<screen><command>awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt</command>
+<command>rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt</command>
+<command>diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt</command> </screen>
+
+ <para>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:</para>
+
+ <screen><command><![CDATA[su -c 'yum install `cat /tmp/pkgs-to-install.txt`']]></command></screen>
+
+ <important>
+ <title>Missing Software</title>
+ <para>Due to changes in package complements between &DISTRO;
+ 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.</para>
+ </important>
+ </section>
+ <section id="sn-switching-to-gui-login">
+ <title>Switching to a Graphical Login</title>
+ <para>
+ If you installed using a text login and wish to switch to a
+ graphical login, follow this procedure.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Switch users to the <systemitem>root</systemitem> account:
+ </para>
+ <screen><![CDATA[su -]]></screen>
+ <para>
+ Provide the administrator password when prompted.
+ </para>
+ </step>
+ <step>
+ <para>
+ 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:
+ </para>
+ <screen><![CDATA[yum groupinstall "GNOME Desktop Environment"]]></screen>
+ <para>
+ This step may take some time as your &DISTRO; system downloads
+ and installs additional software. You may be asked to provide
+ the installation media depending on your original installation
+ source.
+ </para>
+ </step>
+ <step>
+ <para>
+ Run the following command to edit the
+ <filename>/etc/inittab</filename> file:
+ </para>
+ <screen><![CDATA[nano /etc/inittab]]></screen>
+ </step>
+ <step>
+ <para>
+ Find the line that includes the text <literal>initdefault</literal>. Change the numeral <literal>3</literal> to <literal>5</literal>.
+ </para>
+ </step>
+ <step>
+ <para>
+ 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.
+ </para>
+ </step>
+ <step>
+ <para>
+ Type <command>exit</command> to logout of the administrator account.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ If desired, you can reboot the system using the
+ <command>reboot</command> command. Your system will restart and
+ present a graphical login.
+ </para>
+ <para>
+ If you encounter any problems with the graphical login, consult
+ one of the help sources listed in <xref
+ linkend="sn-additional-help"/>.
+ </para>
+ </section>
+ <section id="sn-news-subscriptions">
+ <title>Subscribing to &FED; Announcements and News</title>
+
+ <para>
+ To receive information about package updates, subscribe to either
+ the announcements mailing list, or the RSS feeds.
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>
+ &FP; announcements mailing list
+ </term>
+ <listitem>
+ <para>
+ <ulink url="https://www.redhat.com/mailman/listinfo/fedora-announce-list"/>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ &FP; RSS feeds
+ </term>
+ <listitem>
+ <para>
+ <ulink url="http://fedoraproject.org/infofeed/"/>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <para>
+ The announcements mailing list also provides you with news on the
+ &FP;, and the &FED; community.
+ </para>
+
+ <important>
+ <title>Security Announcements</title>
+
+ <para>
+ Announcements with the keyword
+ <wordasword>[SECURITY]</wordasword> in the title identify
+ package updates that resolve security vulnerabilities.
+ </para>
+ </important>
+ </section>
+ <section id="sn-web-help">
+ <title>Finding Documentation and Support</title>
+
+ <para>
+ Members of the &FED; community provide support through mailing
+ lists, Web forums and Linux User Groups (LUGs) across the world.
+ </para>
+
+ <para>
+ The Web site for the formally endorsed forums is
+ <ulink
+ url="http://forums.fedoraforum.org/"/>.
+ </para>
+
+ <para>
+ The following resources provide information on many aspects of
+ &FED;:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <variablelist>
+ <varlistentry>
+ <term>
+ The FAQ on the &FP; website
+ </term>
+ <listitem>
+ <para>
+ <ulink url="http://fedoraproject.org/wiki/FAQ/"/>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ <listitem>
+ <variablelist>
+ <varlistentry>
+ <term>
+ The documents available from the &FDP; Web site
+ </term>
+ <listitem>
+ <para>
+ <ulink url="http://docs.fedoraproject.org/"/>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ <listitem>
+ <variablelist>
+ <varlistentry>
+ <term>
+ The Linux Documentation Project (LDP)
+ </term>
+ <listitem>
+ <para>
+ <ulink url="http://www.tldp.org/"/>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ <listitem>
+ <variablelist>
+ <varlistentry>
+ <term>
+ The &RHEL; documentation, much of which also applies to
+ &FED;
+ </term>
+ <listitem>
+ <para>
+ <ulink
+ url="http://www.redhat.com/docs/manuals/enterprise/"/>
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Many other organizations and individuals also provide tutorials
+ and HOWTOs for &FED; 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"/>.
+ </para>
+ </section>
+ <section id="sn-community">
+ <title>Joining the &FED; Community</title>
+
+ <para>
+ The &FP; 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 &FC; by testing,
+ and develop new software alongside the programmers employed by
+ &RH;. The results of this work are available to all.
+ </para>
+
+ <para>
+ To make a difference, start here:
+ </para>
+
+ <para>
+ <ulink url="http://join.fedoraproject.org/"/>
+ </para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/old-intro.xml b/en-US/old-intro.xml
new file mode 100644
index 0000000..8c077bc
--- /dev/null
+++ b/en-US/old-intro.xml
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<preface id="ch-intro">
+ <title>Introduction</title>
+ <section>
+ <title>About &FC;</title>
+ <para>
+ &FC; is a complete desktop and server operating system created
+ entirely with open source software.
+ </para>
+ <caution>
+ <title>&FC; Lifecycle</title>
+
+ <para>
+ &FC; is a rapidly evolving system which follows the latest
+ technical developments. &FC; may not be appropriate for use in
+ business-critical applications in your organization.
+ </para>
+ </caution>
+ <para>
+ For complete access to information about &FC;, refer to the
+ official project wiki at <ulink url="http://fedoraproject.org/"/>
+ and <xref linkend="ch-next-steps"/>.
+ </para>
+ </section>
+ <section>
+ <title>About this Manual</title>
+ <para>
+ This manual helps you install &FC; on desktops, laptops and
+ servers. The installation system is flexible enough to use even if
+ you have no previous knowledge of Linux or computer networks. If
+ you select default options, &FC; provides a complete desktop
+ operating system, including productivity applications, Internet
+ utilities, and desktop tools.
+ </para>
+ <para>
+ This document does not detail all of the features of the
+ installation system.
+ </para>
+
+ &BUG-REPORTING;
+
+ </section>
+ <xi:include href="./acknowledgements.xml" xpointer="element(sn-acknowledgements)"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+</preface>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/other-instmethods.xml b/en-US/other-instmethods.xml
new file mode 100644
index 0000000..3e3fdde
--- /dev/null
+++ b/en-US/other-instmethods.xml
@@ -0,0 +1,316 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-other-install-methods">
+ <title>Installation Methods</title>
+ <itemizedlist>
+ <listitem>
+ <para>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="ch-welcome"/>.</para>
+ </listitem>
+ <listitem>
+ <para>If you used the <option>askmethod</option> option or booted
+ from minimal boot media or a PXE server, proceed to <xref
+ linkend="sn-alt-install-method"/>.</para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>CD/DVD Activity</title>
+ <para>
+ If you boot any &DISTRO; 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.
+ </para>
+ </note>
+ <section id="sn-alt-install-method">
+ <title>Alternative Installation Methods</title>
+ <para>
+ Even if you booted from alternative media, you can still install
+ &FC; from CD or DVD media. Alternately, install from ISO
+ images stored on your computer's hard disk, or from a network
+ server.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ To install from CD or DVD media, insert a &FC; DVD or the
+ first installation CD, select <guilabel>Local
+ CD/DVD</guilabel>, and proceed to <xref
+ linkend="ch-welcome"/>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To install from ISO images on a hard disk, select <guilabel>Hard
+ drive</guilabel> and proceed to <xref
+ linkend="sn-installing-from-harddrive"/>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To install from a NFS server or other network location, such
+ as a Web or FTP server, proceed to <xref
+ linkend="sn-install-tcpip-config"/>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-installing-from-harddrive">
+ <title>Installation from a Hard Drive</title>
+
+ <para>
+ Once you have booted your computer, you may use ISO image files of
+ the &FED; discs to continue the installation process. 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 &FC; on computers
+ that are without a network connection or CD/DVD drives.
+ </para>
+ <para>
+ To extract the <filename>install.img</filename> from the iso
+ follow the procedure:
+ </para>
+ <screen>
+ <command><![CDATA[mount -t iso9660 /path/to/Fedora10.iso /mnt/point -o loop]]></command>
+ <command><![CDATA[cp -a /mnt/point/images /path/images/]]></command>
+ <command><![CDATA[umount /mnt/point]]></command>
+ </screen>
+
+ <para>
+ The partition on the hard drive holding the ISO files must be
+ formatted with the
+ <indexterm>
+ <primary>ext2</primary>
+ <see>file systems</see>
+ </indexterm>
+ <indexterm>
+ <primary>file systems</primary>
+ <secondary>ext2</secondary>
+ </indexterm> <firstterm>ext2</firstterm>,
+ <indexterm>
+ <primary>ext3</primary>
+ <see>file systems</see>
+ </indexterm>
+ <indexterm>
+ <primary>file systems</primary>
+ <secondary>ext3</secondary>
+ </indexterm> <firstterm>ext3</firstterm> or
+ <indexterm>
+ <primary>vfat</primary>
+ <see>file systems</see>
+ </indexterm>
+ <indexterm>
+ <primary>file systems</primary>
+ <secondary>vfat</secondary>
+ </indexterm> <firstterm>vfat</firstterm> file system. In &FED;,
+ <systemitem class="filesystem">vfat</systemitem> includes a range
+ of file systems, such as FAT-16 and FAT-32, found on most
+ removable media. External hard drives usually contain <systemitem
+ class="filesystem">vfat</systemitem> (FAT-32) file systems. Some
+ Microsoft Windows systems also use <systemitem
+ class="filesystem">vfat</systemitem> file systems on internal
+ hard disk partitions.
+ </para>
+
+ <para>
+ Before you begin installation from a hard drive, check the
+ partition type to ensure that &FED; 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.
+ </para>
+ <important>
+ <title>Cannot Install from LVM Partitions</title>
+ <para>
+ You cannot use ISO files on partitions controlled by LVM
+ (Logical Volume Management).
+ </para>
+ </important>
+
+ <para>
+ 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>.
+ </para>
+
+ <para>
+ 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:
+ </para>
+ <segmentedlist>
+ <segtitle>Partition type</segtitle>
+ <segtitle>Volume</segtitle>
+ <segtitle>Original path to files</segtitle>
+ <segtitle>Directory to use</segtitle>
+ <seglistitem>
+ <seg>VFAT, NTFS</seg>
+ <seg>D:\</seg>
+ <seg>D:\Downloads\&FCX;&FCVER;</seg>
+ <seg>/Downloads/&FCX;&FCVER;</seg>
+ </seglistitem>
+ <seglistitem>
+ <seg>ext2, ext3</seg>
+ <seg>/home</seg>
+ <seg>/home/user1/&FCX;&FCVER;</seg>
+ <seg>/user1/&FCX;&FCVER;</seg>
+ </seglistitem>
+ </segmentedlist>
+ <tip>
+ <title>Use a leading slash</title>
+ <para>
+ Use a leading slash character (/) to start the directory path.
+ An entry without a leading slash may cause the installation to
+ fail.
+ </para>
+ </tip>
+ <para>
+ Select <guibutton>OK</guibutton> to continue. Proceed with <xref
+ linkend="ch-welcome"/>.
+ </para>
+ </section>
+ <section id="sn-install-tcpip-config">
+ <title>Installation TCP/IP Configuration</title>
+
+ <para>
+ The installation program is network-aware and can use network
+ settings for a number of functions. For instance, you can install
+ &FC; from a network server using FTP, HTTP, or
+ <indexterm>
+ <primary>NFS (Network File System)</primary>
+ <secondary>install from</secondary>
+ </indexterm> NFS protocols. You can also instruct the
+ installation program to consult additional software repositories
+ later in the process.
+ </para>
+
+ <para>
+ 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. In a business
+ environment, consult with your network administrators for
+ appropriate settings. If your network has no DHCP server, clear
+ the check box labeled <guilabel>Use dynamic IP configuration
+ (DHCP)</guilabel>.
+ </para>
+ <para>
+ The installation program supports only the IPv4 protocol.
+ Refer also to <xref linkend="ch-networkconfig"/> for more
+ information on configuring your network.
+ </para>
+ <note>
+ <title>DHCP Responses Take Time</title>
+ <para>
+ If you select options for a protocol not used on your network,
+ or vice versa, it may take additional time to receive network
+ settings from the DHCP server.
+ </para>
+ </note>
+ <para>
+ These settings apply only during the installation process. The
+ installation program allows you to configure the final network
+ configuration later.
+ </para>
+
+ <para>
+ 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 &DISTRO; 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.
+ </para>
+
+ <para>
+ The &FP; maintains a list of Web and FTP public mirrors, sorted
+ by region, at <ulink
+ url="http://fedoraproject.org/wiki/Mirrors"/>. To determine the
+ complete directory path for the installation files, add
+ <filename>/&FCLOCALVER;/&DISTRO;/<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/&FCLOCALVER;/&DISTRO;/i386/os</literal>.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If you are installing via NFS, proceed to <xref
+ linkend="sn-nfs-install-settings"/>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you are installing via Web or FTP, proceed to <xref
+ linkend="sn-url-install-settings"/>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sn-nfs-install-settings">
+ <title>NFS Installation Setup</title>
+ <para>
+ To install from an NFS server, select <guilabel>NFS</guilabel> from
+ the <guilabel>Installation Method</guilabel> menu and select
+ <guilabel>OK</guilabel>. Enter the name or IP address of the NFS
+ server and the directory where the installation files reside.
+ </para>
+ <note>
+ <title>NFS Mirror Availability</title>
+ <para>
+ Public NFS mirrors are rare due to security concerns with NFS
+ that do not necessarily apply to FTP or HTTP servers. The &FP;
+ does not maintain a list of public NFS mirrors for &FC;.
+ </para>
+ </note>
+ <para>
+ Select <guilabel>OK</guilabel> to continue. Proceed with <xref
+ linkend="ch-welcome"/>.
+ </para>
+
+ </section>
+
+ <section id="sn-url-install-settings">
+ <title>Web and FTP Installation Setup</title>
+
+ <para>
+ Enter the name or IP address of the network server and the
+ directory where the installation files reside. Select
+ <guibutton>OK</guibutton> to continue. Proceed with <xref
+ linkend="ch-welcome"/>.
+ </para>
+ </section>
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/packageselection.xml b/en-US/packageselection.xml
new file mode 100644
index 0000000..9f56505
--- /dev/null
+++ b/en-US/packageselection.xml
@@ -0,0 +1,311 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-packageselection">
+ <title>Software Selection</title>
+ <important>
+ <title>Installing from a Live Image</title>
+ <para>If you install from a &DISTRO; 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.</para>
+ </important>
+ <para>
+ By default, the &FED; 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:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Office and Productivity</term>
+ <listitem>
+ <para>
+ This option provides the OpenOffice.org productivity suite,
+ the Planner project management application, graphical tools
+ such as the GIMP, and multimedia applications.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Software Development</term>
+ <listitem>
+ <para>
+ This option provides the necessary tools to compile software
+ on your &FED; system.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Web server</term>
+ <listitem>
+ <para>
+ This option provides the Apache Web server.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <section id="sn-additional-repos">
+ <title>Installing from Additional Repositories</title>
+ <para>
+ 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 &FED;
+ 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.
+ </para>
+ <para>
+ The &DISTRO; software repository is automatically selected for
+ you. The <guilabel>Additional &DISTRO; Software</guilabel>
+ repository contains software beyond the selection found on the
+ default installation source. All software in &DISTRO; is entirely
+ free and open source.
+ </para>
+ <para>
+ To include software from <firstterm>repositories</firstterm> other
+ than the &FED; 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.
+ </para>
+ <para>
+ To edit an existing software repository location, select the
+ repository in the list and then select <guilabel>Modify
+ repository</guilabel>.
+ </para>
+ <note>
+ <title>Network Access Required</title>
+ <para>
+ If you change the repository information during a non-network
+ installation, such as from a &DISTRO; DVD, the installer prompts
+ you for network configuration information.
+ </para>
+ </note>
+ <para>
+ 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.
+ </para>
+ <tip>
+ <title>&DISTRO; Software Mirrors</title>
+ <para>To find a &DISTRO; software mirror near you, refer to <ulink
+ url="http://fedoraproject.org/wiki/Mirrors"/>.</para>
+ </tip>
+ <para>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 &DISTRO; is typically located in a
+ directory tree
+ <filename>releases/&FCVER;/Everything/<replaceable>arch</replaceable>/os</filename>,
+ where <replaceable>arch</replaceable> is a system architecture
+ name.</para>
+ <para>
+ 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.
+ </para>
+ <note>
+ <title>Backtracking Removes Repository Metadata</title>
+ <para>
+ 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.
+ </para>
+ </note>
+ </section>
+ <section id="sn-package-selection">
+ <title>Customizing the Software Selection</title>
+ <para>
+ 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>.
+ </para>
+ <note>
+ <title>Installing Support for Additional Languages</title>
+
+ <para>
+ 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.
+ </para>
+ </note>
+
+ <para>
+ &FED; 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.
+ </para>
+ <para>
+ 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ If you select a package group, &FED; 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.
+ </para>
+ <para>
+ After you choose the desired packages, select
+ <guilabel>Next</guilabel> to proceed. &FC; 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.
+ </para>
+ <section id="sn-changing-selection">
+ <title>Changing Your Mind</title>
+ <para>
+ 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 &FED; software management system downloads
+ the latest packages from network servers, rather than using
+ those on the installation discs.
+ </para>
+ </section>
+ <section id="sn-lang-packages">
+ <title>Additional Language Support</title>
+
+ <para>
+ Your &FC; 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.
+ </para>
+
+ </section>
+ <section id="sn-mandatory-services">
+ <title>Core Network Services</title>
+
+ <para>
+ All &DISTRO; installations include the following network
+ services:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ centralized logging through syslog
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ email through SMTP (Simple Mail Transfer Protocol)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network file sharing through NFS (Network File System)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ remote access through SSH (Secure SHell)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ resource advertising through mDNS (multicast DNS)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The default installation also provides:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ network file transfer through HTTP (HyperText Transfer
+ Protocol)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ printing through CUPS (Common UNIX Printing System)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ remote desktop access through VNC (Virtual Network
+ Computing)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ 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. &FED;
+ installs the NFS sharing, HTTP, and VNC components without
+ enabling those services.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </section>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/preparing-media.xml b/en-US/preparing-media.xml
new file mode 100644
index 0000000..dead145
--- /dev/null
+++ b/en-US/preparing-media.xml
@@ -0,0 +1,368 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-preparing-media">
+ <title>Preparing Media</title>
+ <indexterm>
+ <primary>discs</primary>
+ </indexterm>
+ <indexterm>
+ <primary>media</primary>
+ <secondary>installation</secondary>
+ </indexterm>
+ <para>
+ To install &FC; from discs, you need any one of the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>a set of installation CDs or DVDs of the &FED;
+ distribution</para>
+ <tip>
+ <title>Set Size May Vary</title>
+ <para>In some cases, there may be only one disc in a set.</para>
+ </tip>
+ </listitem>
+ <listitem>
+ <para>A &FED; rescue CD</para>
+ </listitem>
+ <listitem>
+ <para>A &FED; boot-only CD</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ For instructions to download and prepare this CD or DVD installation
+ media, refer to <ulink url="http://fedoraproject.org/wiki/Distribution/Download"/>. If you
+ already have the full set of &FC; installation media, skip to
+ <xref
+ linkend="sn-booting-from-disc"/>.
+ </para>
+
+ <para>
+ There are separate discs and sets for each supported architecture.
+ </para>
+ <important>
+ <title>Architecture-Specific Distributions</title>
+
+ <para>
+ To install &FC;, you must use the boot and installation media that is
+ particular to your architecture. Refer to <xref
+ linkend="sn-which-arch"/> for information on hardware architectures
+ and how to determine the right one for your computer.
+ </para>
+ </important>
+
+ <para>
+ You may use the first CD or DVD installation disc from the complete &FC;
+ distribution to boot your computer. The &FC; distribution also includes
+ <firstterm>image files</firstterm> for boot-only CD or DVD media and USB
+ media. You can convert these files into bootable media using standard Linux
+ utilities or third-party programs on other operating systems.
+ </para>
+
+ <para>
+ You may boot your computer with boot-only media, and load the installation
+ system from another source to continue the process. The types of
+ installation source for &FED; include:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ CD or DVD media installation discs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ hard drive, either attached by USB, or internal to the computer
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network installation server, using either HTTP, FTP, or NFS
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ You can use this facility to install &FC; on machines without using
+ installation discs. For example, you may install &FC; on a laptop with no CD
+ or DVD drive by booting the machine with a USB pen drive, and then using a
+ hard drive as an installation source.
+ </para>
+
+ <para>
+ The supported boot media for &FED; include:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ CD or DVD media (either installation disc #1 or a special boot-only
+ disc)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ USB media
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network interface (via PXE)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Installation from Diskettes</title>
+
+ <para>
+ There is no option to either boot or install &FC; from diskettes.
+ </para>
+ </note>
+
+ <section id="sn-preparing-cd-or-dvd-media">
+ <title>Preparing CD or DVD Media</title>
+
+ <para>
+ The <filename>images/boot.iso</filename> file on the first &FC;
+ installation disc is a boot image designed for CD and DVD media. This file
+ also appears on FTP and Web sites providing &FC;. You can also find this
+ file on mirror sites in the &FC; distribution directory for your
+ particular architecture.
+ </para>
+
+ <para>
+ The &FC; distribution is also downloadable as a set of CD-sized ISO image
+ files or a single DVD-sized ISO image file. You can record these files to
+ CD or DVD using a CD or DVD burning program on your current operating
+ system:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term>Windows operating systems</term>
+ <listitem>
+ <para>
+ Burn an ISO image to disc using your installed CD or DVD burning
+ software. Most software has an option labeled <guilabel>Burn image
+ file to disc</guilabel> or <guilabel>Make disc from ISO
+ image</guilabel>. If your software offers a choice of image
+ formats, choose "ISO image" as the file type. If several ISO formats
+ are offered, choose the closest match to "Mode 1, 2048-byte blocks."
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Apple Mac OS X</term>
+ <listitem>
+ <para>
+ Open the <guilabel>Disk Utility</guilabel> application,
+ found in the <filename>/Applications/Utilities</filename>
+ folder. Select
+ <menuchoice>
+ <guimenu>File</guimenu>
+ <guimenuitem>Open Disk Image</guimenuitem>
+ </menuchoice> and select the ISO image. From the list of
+ volumes, select the item representing the ISO image. Select
+ <guibutton>Burn</guibutton> and follow the instructions.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Linux operating systems</term>
+ <listitem>
+ <para>
+ If you are using a recent version of the GNOME desktop
+ environment, right-click the ISO image file and choose
+ <guilabel>Write to disc</guilabel>. If you are using a recent
+ version of the KDE desktop environment, use
+ <application>K3B</application> and select <menuchoice>
+ <guimenu>Tools</guimenu> <guimenuitem>Burn CD Image</guimenuitem>
+ </menuchoice>, or <menuchoice>
+ <guimenu>Tools</guimenu> <guimenuitem>Burn DVD ISO
+ Image</guimenuitem> </menuchoice> if appropriate. The following
+ command line works for many other environments:
+ </para>
+
+<screen>
+<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
+</screen>
+
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <note>
+ <title>System-Specific Instructions</title>
+
+ <para>
+ Unfortunately this guide cannot offer specific instructions for every
+ possible combination of hardware and software. You can find more
+ information at <ulink
+ url="http://fedoraproject.org/wiki/Docs/Drafts/BurningDiscs"/>.
+ Consult your operating system's documentation and online support
+ services, and <xref linkend="sn-web-help"/> for additional help if
+ needed.
+ </para>
+ </note>
+ </section>
+
+ <section id="sn-preparing-usb-media">
+ <title>Preparing USB Boot Media</title>
+
+ <warning>
+ <title>Data Loss</title>
+
+ <para>
+ <emphasis>This procedure destroys data on the media.</emphasis> Back up
+ any important information before you begin. Some models of USB media use
+ additional partitions or software to provide functions such as
+ encryption. This procedure may make it difficult or impossible to access
+ these special areas on your boot media.
+ </para>
+ </warning>
+
+ <para>
+ The <filename>images/diskboot.img</filename> file on the first &FC;
+ installation disc is a boot image designed for USB media. This file also
+ appears on FTP and Web sites providing &FC;.
+ </para>
+
+ <para>
+ Several software utilities are available for Windows and Linux that can
+ write image files to a device. Linux includes the <command>dd</command>
+ command for this purpose.
+ </para>
+
+ <para>
+ The <command>dd</command> utility requires you to specify the
+ device file that corresponds to the physical media. The name of
+ the device file matches the name assigned to the device by your
+ system. All device files appear in the directory
+ <filename>/dev/</filename>. For example,
+ <filename>/dev/sda</filename> denotes the first USB, SATA, or SCSI
+ device that is attached to the system.
+ </para>
+
+ <para>
+ To learn the name that your system assigns to the media:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Open a terminal window. On a &FED; system, choose
+ <menuchoice><guimenu>Applications</guimenu>
+ <guisubmenu>Accessories</guisubmenu>
+ <guimenuitem>Terminal</guimenuitem> </menuchoice> to start a
+ terminal.
+ </para>
+ </step>
+ <step>
+ <para>
+ Attach or insert the media.
+ </para>
+ </step>
+ <step>
+ <para>
+ In the terminal window, type the following command:
+ </para>
+ <screen><userinput>dmesg</userinput></screen>
+ <para>
+ Look for the items in the <command>dmesg</command> output that relate
+ to the detection of a new SCSI device. Linux systems treat USB media
+ as SCSI devices.
+ </para>
+ <tip>
+ <title>Using the Device Mapper</title>
+ <para>
+ On &FC; 5 and later systems, it may be easier to find the
+ right device name by examining the <filename
+ class="directory">/dev/disk/</filename> directory. Use the
+ command <command>ls -l /dev/disk/by-id/</command> to see the
+ disk devices collated by model and device name.
+ </para>
+ </tip>
+ </step>
+ <step>
+ <para>
+ Unmount the media. On a &FED; system, right-click the icon that
+ corresponds to the media, and select <guimenuitem>Unmount
+ Volume</guimenuitem>. Alternatively, enter this command in a
+ terminal window:
+ </para>
+
+<screen>
+<userinput>umount /dev/<replaceable><device></replaceable></userinput>
+</screen>
+
+ <para>
+ Replace <replaceable><device></replaceable> with the
+ name of the correct device file for the media.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ To write an image file to boot media with <command>dd</command> on a
+ current version of &FC;, carry out the following steps:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Locate the image file.
+ </para>
+ </step>
+ <step>
+ <para>
+ Attach or insert the media.
+ </para>
+ </step>
+ <step>
+ <para>
+ Your system may automatically detect and open the media. If that
+ happens, close or unmount the media before continuing.
+ </para>
+ </step>
+ <step>
+ <para>
+ Open a terminal window.
+ </para>
+ </step>
+ <step>
+ <para>
+ In the terminal window, type the following command:
+ </para>
+
+<screen>
+<userinput>dd if=diskboot.img of=/dev/<replaceable><device></replaceable></userinput>
+</screen>
+
+ <para>
+ Replace <replaceable><device></replaceable> with the
+ name of the correct device file for the media.
+ </para>
+ </step>
+ </procedure>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/pxe-server.xml b/en-US/pxe-server.xml
new file mode 100644
index 0000000..19a7784
--- /dev/null
+++ b/en-US/pxe-server.xml
@@ -0,0 +1,211 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.docbook.org/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
+%FDP-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<appendix id="ap-install-server">
+ <title>Setting Up an Installation Server</title>
+ <note>
+ <title>Experience Required</title>
+ <para>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.</para>
+ </note>
+ <para>In the past, administrators needed to perform a great deal of
+ manual configuration to produce an installation server. However, if
+ you have a &RHEL;, CentOS, or Fedora server on your local network,
+ you can use <package>cobbler</package> to perform these
+ tasks.</para>
+ <para>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>.</para>
+ <section id="sn-install-cobbler">
+ <title>Setting Up <package>cobbler</package></title>
+ <para>To install <package>cobbler</package> use the following
+ command:</para>
+ <screen><command><![CDATA[yum -y install cobbler]]></command></screen>
+ <para>The <command>cobbler</command> command can check its own
+ settings for validity and report the results. Run the following
+ command to check the settings:</para>
+ <screen><command><![CDATA[cobbler check]]></command></screen>
+ <para>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.</para>
+ <para>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>.</para>
+ </section>
+ <section id="sn-cobbler-setup-distro">
+ <title>Setting Up the Distribution</title>
+ <para>To set up a distribution from a full &DISTRO; DVD or ISO
+ image, use this procedure.</para>
+ <note>
+ <title>Network Locations</title>
+ <para>To create a local mirror from an existing network source,
+ skip this section and refer instead to <xref
+ linkend="sn-cobbler-mirror"/>.</para>
+ </note>
+ <procedure>
+ <step>
+ <para>If you are using a DVD disc or ISO image, Create a
+ directory mount point:</para>
+ <screen><command><![CDATA[mkdir /mnt/dvd]]></command></screen>
+ <para>To mount a physical DVD disc, use the following
+ command:</para>
+ <screen><command><![CDATA[mount -o context=system_u:object_r:httpd_sys_content_t:s0 /dev/dvd /mnt/dvd]]></command></screen>
+ <para>To mount a DVD ISO image, use the following
+ command:</para>
+ <screen><command><![CDATA[mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd]]></command></screen>
+ </step>
+ <step>
+ <para>To support NFS installation, create a file
+ <filename>/etc/exports</filename> and add the following line
+ to it:</para>
+ <screen><![CDATA[/mnt/dvd *(ro,async)]]></screen>
+ <para>Start the NFS server using the following commands:</para>
+ <screen><command><![CDATA[/sbin/service rpcbind start
+/sbin/service nfs start]]></command></screen>
+ </step>
+ <step>
+ <para>To support HTTP installation, use <command>yum</command>
+ to install the Apache web server if it is not already
+ installed:</para>
+ <screen><command><![CDATA[yum -y install httpd]]></command></screen>
+ <para>Make a link to the mounted disc in the Apache public
+ content area:</para>
+ <screen><command>ln -s /mnt/dvd /var/www/html/<replaceable>distro</replaceable></command></screen>
+ </step>
+ </procedure>
+ </section>
+ <section id="sn-cobbler-mirror">
+ <title>Mirroring a Network Location</title>
+ <para>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.</para>
+ <para>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:</para>
+ <itemizedlist>
+ <listitem>
+ <para><uri>http://mirror.example.com/pub/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+ </listitem>
+ <listitem>
+ <para><uri>ftp://mirror.example.com/pub/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+ </listitem>
+ <listitem>
+ <para><uri>rsync://mirror.example.com/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section id="sn-cobbler-import">
+ <title>Importing the Distribution</title>
+ <para>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.</para>
+ <procedure>
+ <step>
+ <para>To import the DVD disc or ISO distribution into
+ <command>cobbler</command>, run this command:</para>
+ <screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable></command></screen>
+ <para>For <replaceable>distro_name</replaceable>, substitute a
+ meaningful name for the distribution.</para>
+ <para>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:</para>
+ <screen><command>cobbler import --mirror=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable></command></screen>
+ <important>
+ <title>Importing a Source</title>
+ <para>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.</para>
+ </important>
+ <para>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.</para>
+ <screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
+<command>cobbler import --mirror=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
+</screen>
+ <para>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>:</para>
+ <itemizedlist>
+ <listitem>
+ <para><uri>nfs://<replaceable>192.168.1.1</replaceable>:/mnt/dvd</uri></para>
+ </listitem>
+ <listitem>
+ <para><uri>http://<replaceable>192.168.1.1</replaceable>:/distro</uri></para>
+ </listitem>
+ </itemizedlist>
+ <para>If necessary, replace
+ <replaceable>192.168.1.1</replaceable> with the IP address for
+ your <command>cobbler</command> server.</para>
+ </step>
+ <step>
+ <para>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.</para>
+ <important>
+ <title>Firewall Considerations</title>
+ <para>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:</para>
+ <itemizedlist>
+ <listitem>
+ <para>67 or bootps, for the DHCP/BOOTP server</para>
+ </listitem>
+ <listitem>
+ <para>69 or tftp, for providing the PXE loader</para>
+ </listitem>
+ <listitem>
+ <para>80 or http, if the <command>cobbler</command> server
+ is to provide HTTP installation service</para>
+ </listitem>
+ <listitem>
+ <para>20 and 21 or ftp, if the <command>cobbler</command>
+ server is to provide FTP installation service</para>
+ </listitem>
+ <listitem>
+ <para>111 or sunrpc, if the <command>cobbler</command>
+ server is to provide NFS installation service</para>
+ </listitem>
+ </itemizedlist>
+ </important>
+ </step>
+ </procedure>
+ </section>
+</appendix>
diff --git a/en-US/rootpassword.xml b/en-US/rootpassword.xml
new file mode 100644
index 0000000..ef40a8f
--- /dev/null
+++ b/en-US/rootpassword.xml
@@ -0,0 +1,109 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-rootpassword">
+ <title>Set the Root Password</title>
+
+ <para>
+ &FED; uses a special account named <indexterm>
+ <primary>root account</primary>
+ </indexterm> <firstterm><systemitem
+ class="username">root</systemitem></firstterm> for system
+ administration. The <systemitem class="username">root</systemitem>
+ account on a Linux system is not subject to most normal account
+ restrictions. As the system owner or administrator, you may
+ sometimes require special privileges to configure or modify the
+ system. In those cases, use the <systemitem
+ class="username">root</systemitem> account.
+ </para>
+
+ <important>
+ <title>Using the <systemitem class="username">root</systemitem>
+ Account</title>
+ <para>
+ Avoid logging in to &FC; as <systemitem
+ class="username">root</systemitem> when possible. Any
+ administration tools which require <systemitem
+ class="username">root</systemitem> privileges will prompt you
+ for the password.
+ </para>
+ </important>
+
+ <para>
+ The &FED; installation program requires the <systemitem
+ class="username">root</systemitem> password to be at least six characters
+ long. Because the <systemitem class="username">root</systemitem>
+ account may potentially control any part of the system, use the
+ following guidelines to create a good password:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use a combination of uppercase letters, lowercase letters,
+ numbers, punctuation and other characters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use a word or name. Obscuring the word or name with
+ substitute characters is not effective.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Do not use the same password for more than one system.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The following are examples of good passwords:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <systemitem>f9*@1Ls99A</systemitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>HL8$391%%rb</systemitem>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <systemitem>Iwtb,10^th</systemitem>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Enter the <systemitem class="username">root</systemitem> password
+ into the <guilabel>Root Password</guilabel> field. &FED; 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.
+ </para>
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/rpm-info.xml b/en-US/rpm-info.xml
new file mode 100644
index 0000000..d7cd85c
--- /dev/null
+++ b/en-US/rpm-info.xml
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE rpm-info PUBLIC "-//Fedora//DTD Docs RPM-INFO V1.0//EN" "http://docs.fedoraproject.org/dtds/rpm-info.dtd">
+<rpm-info>
+ <colophon>
+ <worker surname="Ellis" firstname="Stuart" othername="" id="StuartEllis" email="stuart at elsn.org" wholename="Stuart Ellis" initials="SE"/>
+ <worker surname="Frields" firstname="Paul" othername="W." id="PaulWFrields" email="stickster at gmail.com" wholename="Paul W. Frields" initials="PWF"/>
+ <worker email="Tommy.Reynolds at MegaCoder.com" firstname="Tommy" id="megacoder" initials="JTR" surname="Reynolds" wholename="Tommy Reynolds"/>
+ <worker email="kwade at redhat.com" firstname="Karsten" id="quaid" initials="KW" surname="Wade" wholename="Karsten Wade"/>
+ <worker email="jaredsmith at jaredsmith.net" firstname="Jared" id="jsmith" initials="JKS" surname="Smith" wholename="Jared K. Smith"/>
+ <worker email="david at gnsa.us" firstname="David" id="ke4qqq" initials="DJN" surname="Nalley" wholename="David Nalley" />
+ <worker email="soulspecter117 at yahoo.com" firstname="Jeremy" id="soulspecter" initials="JWM" surname="Mooney" wholename="Jeremy W. Mooney" />
+ <worker email="nguyenjs at gmail.com" firstname="John" id="nguyenj" initials="JSN" surname="Nguyen" wholename="John Nguyen" />
+ <worker email="chrisjohnsona4 at gmail.com" firstname="Chris" id="chr1sjohnson" initials="CLJ" surname="Johnson" wholename="Chris Johnson" />
+ <worker email="elizabeth at eawestwriting.com" firstname="Elizabeth" id="eawest" initials="EAW" surname="West" wholename="Elizabeth Ann West" />
+ <worker email="fedora-docs-list at redhat.com" firstname="Fedora" id="DocsProject" initials="FDP" surname="Documentation Project" wholename="Fedora Documentation Project" />
+ </colophon>
+ <author worker="DocsProject"/>
+ <license>
+ <rights>OPL</rights>
+ <version>1.0</version>
+ </license>
+ <copyright>
+ <year>2008</year>
+ <holder>Red Hat, Inc. and others </holder>
+ </copyright>
+ <title>Fedora 10 Installation Guide</title>
+ <desc>Provides documentation for the installation process.</desc>
+ <changelog order="newest-first">
+ <revision date="2008-11-24" number="10.0.0">
+ <author worker="KarstenWade"/>
+ <details>Build and publish Fedora 10 version</details>
+ </revision>
+ <revision date="2008-10-18" number="9.92">
+ <author worker="jsmith"/>
+ <details>Prepare for release of Fedora 10</details>
+ </revision>
+ <revision date="2008-07-25" number="9.0.2">
+ <author worker="PaulWFrields"/>
+ <details>Fix incorrect livecd-tools instructions</details>
+ </revision>
+ <revision date="2008-06-28" number="9.0.1">
+ <author worker="PaulWFrields"/>
+ <details>Lots of bug fixes</details>
+ </revision>
+ <revision date="2008-05-13" number="9.0.0">
+ <author worker="PaulWFrields"/>
+ <details>Add information on upgrading a distribution</details>
+ </revision>
+ </changelog>
+</rpm-info>
diff --git a/en-US/techref.xml b/en-US/techref.xml
new file mode 100644
index 0000000..bf74673
--- /dev/null
+++ b/en-US/techref.xml
@@ -0,0 +1,247 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<appendix id="ap-techref">
+ <title>Other Technical Documentation</title>
+ <para>
+ This document provides a reference for using the &FC; 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"/>.
+ </para>
+ <para>
+ Both <command>anaconda</command> and &FC; systems use a common set
+ of software components. For detailed information on key
+ technologies, refer to the Web sites listed below:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Boot Loader</term>
+ <listitem>
+ <para>
+ &FC; 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/"/> for more
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Disk Partitioning</term>
+ <listitem>
+ <para>
+ &FC; uses <command>parted</command> to partition disks. Refer
+ to <ulink url="http://www.gnu.org/software/parted/"/> for more
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Storage Management</term>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary>LVM</primary>
+ <secondary>documentation</secondary>
+ </indexterm>
+ Logical Volume Management (LVM) provides administrators with a
+ range of facilities to manage storage. By default, the &FED;
+ installation process formats drives as LVM volumes. Refer to
+ <ulink url="http://www.tldp.org/HOWTO/LVM-HOWTO/"/> for more
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Audio Support</term>
+ <listitem>
+ <para>
+ The Linux kernel used by &FC; 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"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Graphics System</term>
+ <listitem>
+ <para>
+ Both the installation system and &FC; 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/"/>
+ for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Remote Displays</term>
+ <listitem>
+ <para>
+ &FC; 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"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Command-line Interface</term>
+ <listitem>
+ <para>
+ By default, &FC; 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"/> 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/"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Remote System Access</term>
+ <listitem>
+ <para>
+ &FC; 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/"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Access Control</term>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary>&SEL;</primary>
+ <secondary>documentation</secondary>
+ </indexterm>
+ &SEL; provides Mandatory Access Control (MAC) capabilities
+ that supplement the standard Linux security features. Refer to
+ the &SEL; Project Pages for more information:
+ <ulink url="http://docs.fedoraproject.org/selinux-guide"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Firewall</term>
+ <listitem>
+ <para>
+ The Linux kernel used by &FC; 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"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Software Installation</term>
+ <listitem>
+ <para>
+ &FC; 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/"/> for more
+ information.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Virtualization</term>
+ <listitem>
+ <para>
+ <indexterm>
+ <primary>Virtualization</primary>
+ <secondary>documentation</secondary>
+ </indexterm> Virtualization provides the capability to
+ simultaneously run multiple operating systems on the same
+ computer. &FC; also includes tools to install and manage the
+ secondary systems on a &FED; 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"/>
+ for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+</appendix>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/timezone.xml b/en-US/timezone.xml
new file mode 100644
index 0000000..8010845
--- /dev/null
+++ b/en-US/timezone.xml
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-timezone">
+ <title>Time Zone Selection</title>
+ <para>
+ This screen allows you to specify the correct time zone for the
+ location of your computer. Specify a time zone even if you plan to
+ use <indexterm>
+ <primary>NTP (Network Time Protocol)</primary>
+ </indexterm> NTP (Network Time Protocol) to maintain the accuracy of
+ the system clock.
+ </para>
+ <section id="sn-selecting-timezone">
+ <title>Selecting a Time Zone</title>
+
+ <para>
+ &FED; displays on the screen two methods for selecting the time
+ zone. To select a time zone using the map, first place your mouse
+ pointer over your region on the map. Click once to magnify that
+ region on the map. Next, select the yellow dot that represents the
+ city nearest to your location. Once you select a dot, it becomes a
+ red <guilabel>X</guilabel> to indicate your selection.
+ </para>
+
+ <para>
+ To select a time zone using the list, select the name of the city
+ nearest to your location. The cities are listed in alphabetical
+ order.
+ </para>
+ </section>
+ <section id="sn-utc">
+ <title>Universal Co-ordinated Time (UTC)</title>
+ <indexterm>
+ <primary>UTC (Universal Co-ordinated time)</primary>
+ </indexterm>
+ <indexterm>
+ <primary>GMT (Greenwich Mean Time)</primary>
+ <see>UTC</see>
+ </indexterm>
+ <para>For purposes of addressing time zones, Universal Co-ordinated
+ Time is also known as Greenwich Mean Time (GMT).</para>
+
+ <para>
+ If &FC; 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. &FC; 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.
+ </para>
+
+ <caution>
+ <title>Windows and the System Clock</title>
+
+ <para>
+ 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 &FC;.
+ </para>
+ </caution>
+
+ <para>
+ Select <guibutton>Next</guibutton> to proceed.
+ </para>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/upgrading.xml b/en-US/upgrading.xml
new file mode 100644
index 0000000..1e0ae4e
--- /dev/null
+++ b/en-US/upgrading.xml
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<!-- $Id: -->
+
+<chapter id="ch-upgrading-system">
+ <title>Upgrading an Existing System</title>
+
+ <para>
+ The installation system automatically detects any existing
+ installation of &FC;. 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.
+ </para>
+
+ <section id="sn-upgrade-examine">
+ <title>Upgrade Examine</title>
+
+ <para>
+ If your system contains a &FC; or &RHL; 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>.
+ </para>
+
+ <note>
+ <title>Manually Installed Software</title>
+ <para>
+ Software you have installed manually on your existing &FC; or
+ &RHL; 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.
+ </para>
+ </note>
+ </section>
+
+ <section id="sn-upgrade-tree">
+ <title>Upgrading Using the Installer</title>
+ <tip>
+ <title>Installations are Recommended</title>
+ <para>In general, the &FP; 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="ch-disk-partitioning"/>.</para>
+ </tip>
+ <para>If you choose to upgrade your system using the installation
+ program, any software not provided by &DISTRO; that conflicts with
+ &DISTRO; software is overwritten. Before you begin an upgrade
+ this way, make a list of your system's current packages for later
+ reference:</para>
+
+ <screen><command><![CDATA[rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' > ~/old-pkglist.txt]]></command></screen>
+
+ <para>After installation, consult this list to discover which
+ packages you may need to rebuild or retrieve from non-&DISTRO;
+ software repositories.</para>
+ <para>Next, make a backup of any system configuration data:</para>
+
+ <screen><command><![CDATA[su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc'
+su -c 'mv /tmp/etc-*.tar.gz /home']]></command></screen>
+
+ <para>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.</para>
+ <warning>
+ <title>Storing Backups</title>
+ <para>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.</para>
+ </warning>
+ <para>For more information on completing the upgrade process later,
+ refer to <xref linkend="sn-finishing-upgrade"/>.</para>
+ </section>
+
+ <section id="sn-upgrading-bootloader">
+ <title>Upgrading Boot Loader Configuration</title>
+
+ <para>
+ <indexterm>
+ <primary>boot loader</primary>
+ <secondary>upgrading</secondary>
+ </indexterm> Your completed &FC; 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="ch-bootloader" />
+ for more information about boot loaders.
+ </para>
+ <para>
+ If the existing boot loader was installed by a Linux distribution,
+ the installation system can modify it to load the new &FC; 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 &FC; or &RHL; installation.
+ </para>
+
+ <para>
+ <firstterm>GRUB</firstterm> is the standard boot loader for &FED;.
+ 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 &FED; 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ After you make your selection, click <guibutton>Next</guibutton>
+ to continue.
+ </para>
+
+ </section>
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
diff --git a/en-US/welcome.xml b/en-US/welcome.xml
new file mode 100644
index 0000000..a533007
--- /dev/null
+++ b/en-US/welcome.xml
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!ENTITY % FEDORA-ENTITIES SYSTEM "fdp-entities.ent">
+%FEDORA-ENTITIES;
+
+<!ENTITY % DOC-ENTITIES SYSTEM "entities.ent">
+%DOC-ENTITIES;
+
+]>
+
+<chapter id="ch-welcome">
+ <title>Welcome Dialog</title>
+
+ <para>
+ After the installation program loads its next stage, a welcome
+ dialog appears. Select <guilabel>Next</guilabel> to continue.
+ </para>
+ <section id="sn-initialize-hdd">
+ <title>Initializing the Hard Disk</title>
+ <para>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>.</para>
+ </section>
+ <section id="sn-raid-config">
+ <title>RAID or Other Nonstandard Configurations</title>
+ <para>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.</para>
+ <warning>
+ <title>Detach Unneeded Disks</title>
+ <para>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.</para>
+ </warning>
+ </section>
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+
diff --git a/publican.cfg b/publican.cfg
new file mode 100644
index 0000000..41937cd
--- /dev/null
+++ b/publican.cfg
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Tue May 11 16:33:52 2010
+
+xml_lang: en-US
+type: Book
+brand: fedora
+
More information about the docs-commits
mailing list