install-guide/devel/en_US abouttoinstall.xml, NONE, 1.1 acknowledgements.xml, NONE, 1.1 adminoptions.xml, NONE, 1.1 beginninginstallation.xml, NONE, 1.1 bootloader.xml, NONE, 1.1 diskpartitioning.xml, NONE, 1.1 firstboot.xml, NONE, 1.1 installingpackages.xml, NONE, 1.1 intro.xml, NONE, 1.1 locale.xml, NONE, 1.1 networkconfig.xml, NONE, 1.1 nextsteps.xml, NONE, 1.1 other-instmethods.xml, NONE, 1.1 packageselection.xml, NONE, 1.1 rootpassword.xml, NONE, 1.1 techref.xml, NONE, 1.1 timezone.xml, NONE, 1.1 upgrading.xml, NONE, 1.1 fedora-install-guide.xml, 1.1, 1.2 fedora-install-guide-abouttoinstall.xml, 1.1, NONE fedora-install-guide-acknowledgements.xml, 1.1, NONE fedora-install-guide-adminoptions.xml, 1.1, NONE fedora-install-guide-beginninginstallation.xml, 1.1, NONE fedora-install-guide-bootloader.xml, 1.2, NONE fedora-install-guide-diskpartitioning.xml, 1.2, NONE fedora-install-guide-firstboot.xml, 1.1, NONE fedora-install-guide-installingpackages.xml, 1.1, NONE fedora-install-guide-intro.xml, 1.4, NONE fedora-install-! guide-locale.xml, 1.1, NONE fedora-install-guide-networkconfig.xml, 1.1, NONE fedora-install-guide-nextsteps.xml, 1.2, NONE fedora-install-guide-other-instmethods.xml, 1.1, NONE fedora-install-guide-packageselection.xml, 1.2, NONE fedora-install-guide-rootpassword.xml, 1.1, NONE fedora-install-guide-techref.xml, 1.1, NONE fedora-install-guide-timezone.xml, 1.1, NONE fedora-install-guide-upgrading.xml, 1.1, NONE

Paul W. Frields (pfrields) fedora-docs-commits at redhat.com
Mon Aug 21 12:05:33 UTC 2006


Author: pfrields

Update of /cvs/docs/install-guide/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17980/en_US

Modified Files:
	fedora-install-guide.xml 
Added Files:
	abouttoinstall.xml acknowledgements.xml adminoptions.xml 
	beginninginstallation.xml bootloader.xml diskpartitioning.xml 
	firstboot.xml installingpackages.xml intro.xml locale.xml 
	networkconfig.xml nextsteps.xml other-instmethods.xml 
	packageselection.xml rootpassword.xml techref.xml timezone.xml 
	upgrading.xml 
Removed Files:
	fedora-install-guide-abouttoinstall.xml 
	fedora-install-guide-acknowledgements.xml 
	fedora-install-guide-adminoptions.xml 
	fedora-install-guide-beginninginstallation.xml 
	fedora-install-guide-bootloader.xml 
	fedora-install-guide-diskpartitioning.xml 
	fedora-install-guide-firstboot.xml 
	fedora-install-guide-installingpackages.xml 
	fedora-install-guide-intro.xml fedora-install-guide-locale.xml 
	fedora-install-guide-networkconfig.xml 
	fedora-install-guide-nextsteps.xml 
	fedora-install-guide-other-instmethods.xml 
	fedora-install-guide-packageselection.xml 
	fedora-install-guide-rootpassword.xml 
	fedora-install-guide-techref.xml 
	fedora-install-guide-timezone.xml 
	fedora-install-guide-upgrading.xml 
Log Message:
Get rid of unnecessary namespace, more fixes, still tinkering...


--- NEW FILE abouttoinstall.xml ---
<?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>

  <figure id="fig-about-to-install">
    <title>About to Install Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/abouttoinstall.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/abouttoinstall.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  About to install screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <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
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE acknowledgements.xml ---
<?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-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>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE adminoptions.xml ---
<?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>
  <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
      <prompt>boot:</prompt>
      Prompt</title>

    <para>
      You can use the
      <prompt>boot:</prompt>
      prompt 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>

      <note>
        <title>Configuring the Installed System</title>

        <para>
          The installed system runs the Setup Agent the first time that
          it boots. Use the Setup Agent to configure the display
          settings for the new system. Refer to
          <xref linkend="sn-firstboot-display"/> for more information on
          configuring the display with the Setup Agent.
        </para>
      </note>
    </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>
      <table id="tb-installmethods">
        <title>Installation Methods</title>
        <tgroup cols="2">
          <colspec colnum="1" colname="Installation Method"/>
          <colspec colnum="2" colname="Option Format"/>
          <thead>
            <row>
<entry>Installation Method</entry>
<entry>Option Format</entry>
            </row>
          </thead>
          <tbody>
            <row>
<entry>
                <para>
                  CD or DVD drive
                </para>
              </entry>
<entry>
                <para>
                  <option>method=<replaceable>cdrom</replaceable></option>
                </para>
              </entry>
            </row>
            <row>
<entry>
                <para>
                  Hard Drive
                </para>
              </entry>
<entry>
                <para>
                  <option>method=<replaceable>hd://device/</replaceable></option>
                </para>
              </entry>
            </row>
            <row>
<entry>
                <para>
                  HTTP Server
                </para>
              </entry>
<entry>
                <para>
                  <option>method=<replaceable>http://server.mydomain.com/directory/</replaceable></option>
                </para>
              </entry>
            </row>
            <row>
<entry>
                <para>
                  FTP Server
                </para>
              </entry>
<entry>
                <para>
                  <option>method=<replaceable>ftp://server.mydomain.com/directory/</replaceable></option>
                </para>
              </entry>
            </row>
            <row>
<entry>
                <para>
                  NFS Server
                </para>
              </entry>
<entry>
                <para>
                  <option>method=<replaceable>nfs:server.mydomain.com:/directory/</replaceable></option>
                </para>
              </entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </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><![CDATA[Starting VNC...
The VNC server is now running.
Please connect to computer.mydomain.com:1 to begin the install...
Starting graphical installation...
Press <enter> for a shell]]></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>Security
          Level and 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>Security
          Level and 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>
    <table id="tb-kssources">
      <title>Kickstart Sources</title>
      <tgroup cols="2">
        <colspec colnum="1" colname="Kickstart Source"/>
        <colspec colnum="2" colname="Option Format"/>
        <thead>
          <row>
<entry>Kickstart Source</entry>
<entry>Option Format</entry>
          </row>
        </thead>
        <tbody>
          <row>
<entry>
                <para>
                  CD or DVD drive
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
          <row>
<entry>
                <para>
                  Hard Drive
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
          <row>
<entry>
                <para>
                  Other Device
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
          <row>
<entry>
                <para>
                  HTTP Server
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
          <row>
<entry>
                <para>
                  FTP Server
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
          <row>
<entry>
                <para>
                  NFS Server
                </para>
              </entry>
<entry>
                <para>
                  <option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option>
                </para>
              </entry>
          </row>
        </tbody>
      </tgroup>
    </table>
    <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>
      <table id="tb-driversources">
        <title>Driver Disk Image Sources</title>
        <tgroup cols="2">
          <colspec colnum="1" colname="Image Source"/>
          <colspec colnum="2" colname="Option Format"/>
          <thead>
            <row>
<entry>Image Source</entry>
<entry>Option Format</entry>
            </row>
          </thead>
          <tbody>
            <row>
<entry>
                  <para>
                    Select a drive or device
                  </para>
                </entry>
<entry>
                  <para>
                    <option>dd</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    HTTP Server
                  </para>
                </entry>
<entry>
                  <para>
                    <option>dd=<replaceable>http://server.mydomain.com/directory/drivers.img</replaceable></option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    FTP Server
                  </para>
                </entry>
<entry>
                  <para>
                    <option>dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable></option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    NFS Server
                  </para>
                </entry>
<entry>
                  <para>
                    <option>dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable></option>
                  </para>
                </entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </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>
      <table id="tb-hwoptions">
        <title>Hardware Options</title>
        <tgroup cols="2">
          <colspec colnum="1" colname="Compatibility Setting"/>
          <colspec colnum="2" colname="Option"/>
          <thead>
            <row>
<entry>Compatibility Setting</entry>
<entry>Option</entry>
            </row>
          </thead>
          <tbody>
            <row>
<entry>
                  <para>
                    Disable all hardware detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>noprobe</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable graphics, keyboard, and mouse detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>headless</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable automatic monitor detection (DDC)
                  </para>
                </entry>
<entry>
                  <para>
                    <option>skipddc</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable mainboard APIC
                  </para>
                </entry>
<entry>
                  <para>
                    <option>noapic</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable power management (ACPI)
                  </para>
                </entry>
<entry>
                  <para>
                    <option>acpi=off</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable Direct Memory Access (DMA) for IDE drives
                  </para>
                </entry>
<entry>
                  <para>
                    <option>ide=nodma</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable BIOS-assisted RAID
                  </para>
                </entry>
<entry>
                  <para>
                    <option>nodmraid</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable Firewire device detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>nofirewire</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable parallel port detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>noparport</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable PC Card (PCMCIA) device detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>nopcmcia</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable USB storage device detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>nousbstorage</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Disable all USB device detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>nousb</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Force Firewire device detection
                  </para>
                </entry>
<entry>
                  <para>
                    <option>firewire</option>
                  </para>
                </entry>
            </row>
            <row>
<entry>
                  <para>
                    Prompt user for ISA device configuration
                  </para>
                </entry>
<entry>
                  <para>
                    <option>isa</option>
                  </para>
                </entry>
            </row>
          </tbody>
        </tgroup>
      </table>
      <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 &FED; for the first time, even if it has previously run
        other operating systems.
      </para>

      <para>
        To boot your computer in
        <indexterm>
          <primary>memory testing mode</primary>
        </indexterm>
        memory testing mode, enter <userinput>memtest86</userinput> at
        the
        <prompt>boot:</prompt>
        prompt. The first test starts immediately. By default,
        <command>memtest86</command> 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 the first 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 first installation disc, enter:
      </para>
<screen>
 <userinput>linux rescue</userinput>
</screen>
      <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
sgml-parent-document:("fedora-install-guide.xml" "book" "appendix")
fill-column: 72
End:
-->


--- NEW FILE beginninginstallation.xml ---
<?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>

  <para>
    To begin installation of &FC;, boot the computer from the bootable
    media.  The bootable media provides the necessary programs and files
    to start the installation program.  Once you start the installation
    program, you may be able to install from a completely different
    piece of media.
  </para>

  <para>
    If you boot from the first installation disc of the &FC;
    distribution, you may choose a different source for installation.
    The default source is the CDs themselves.  To change this behavior,
    enter <userinput>linux askmethod</userinput> at the
    <computeroutput>boot:</computeroutput> prompt.  If you boot from
    other media, the installation program <emphasis>always</emphasis>
    asks you to choose the installation source.
  </para>
  
  <para>
    The <indexterm>
      <primary>BIOS (Basic Input/Output System)</primary>
    </indexterm> <firstterm>BIOS</firstterm> (Basic Input/Output System)
    on your computer must support the type of boot media you select. The
    BIOS controls access to some hardware devices during boot time. Any
    computer that meets the minimum recommended specification for &FC;
    can boot from a CD or DVD drive with the first disc.  USB drives and
    flash media are newer technologies, but many computers can use them
    as boot media. Some network cards and chipsets include support for
    network booting with
    <indexterm>
      <primary>PXE (Pre-boot eXecution Environment)</primary>
    </indexterm> <firstterm>PXE</firstterm>.  PXE (pronounced "pixie")
    allows a computer to load boot files from a network server instead
    of directly-connected hardware.
  </para>

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

  <note>
    <title>Aborting the Installation</title>
    <para>
      To abort the installation process at any time before the
      <guilabel>Installing Packages</guilabel> screen, either press
      <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo> 
      or power off the computer with the power switch.  &FED; makes no
      changes to your computer until package installation begins.
    </para>
  </note>


  <section id="sn-booting-from-disc">
    <title>Booting from CD, DVD, or USB Media</title>

    <para>
      To boot your computer:
    </para>

    <procedure>
      <step>
	<para>Switch on the computer.</para>
      </step>
      <step>
	<para>Insert the first disc into the CD or DVD drive, or attach
	  the USB media.</para>
      </step>
      <step>
	<para>A boot screen appears, with a <prompt>boot:</prompt>
	  prompt at the bottom.</para>
      </step>
    </procedure>

    <note>
      <title>BIOS Boot Order</title>
      <para>
	The BIOS contains settings that control the order of boot
	devices.  If your PC boots from a device other than the &FC;
	boot media, check the BIOS boot configuration.
      </para>
    </note>

    <figure id="fig-boot">
      <title>Boot Screen</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/bootprompt.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/bootprompt.png" format="PNG"/>
	</imageobject>
	<textobject id="tx-boot">
	  <phrase>
	    &FC; boot screen.
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      If you hit <keycap>Enter</keycap>, the installation runs in
      default mode.  In the default mode, the installation uses a
      graphical interface if possible.  If the installation program runs
      from the &FC; installation CD or DVD media, in default mode it
      uses these media as the installation source.  To change the
      installation mode, at the <prompt>boot:</prompt> prompt, type
      <userinput>linux</userinput> followed by one or more of the
      following options:
    </para>
    <itemizedlist>
      <listitem>
	<para>
	  To install from a hard drive or network server, add the
	  directive <userinput>askmethod</userinput>.
	</para>
      </listitem>
      <listitem>
	<para>
	  To use a text interface, add the directive
	  <userinput>text</userinput>.
	</para>
      </listitem>
      <listitem>
	<para>
	  To retry installation because the installation aborted at an
	  early stage, add the directive
	  <userinput>acpi=off</userinput>.  ACPI is responsible for many
	  kinds of installation errors.  If you turn ACPI off, you may
	  be able to overcome some of these errors.
	</para>
      </listitem>
    </itemizedlist>

    <para>
      Refer to the Release Notes for additional options that may help if
      you encounter problems with the installation program.  A current
      copy of the Release Notes is always available at &FDPDOCS-URL;.
    </para>

    <para>
      When you issue a command at the <prompt>boot:</prompt> prompt, the
      first stage of the installation program starts.
    </para>

	</section>
    <section id="sn-media-testing">
      <title>Testing CD and DVD Media</title>

      <figure id="fig-media-test">
	<title>Media Test Screen</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediacheck.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediacheck.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      Media test screen.
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

      <para>
	Select <guibutton>OK</guibutton> to test the disc, or select
	<guibutton>Skip</guibutton> to proceed with the installation
	without testing the disc.
      </para>

      <caution>
	<title>Testing Discs</title>
	<para>
	  Test any discs which you have not previously tested.  A disc
	  error during the installation process may force you to restart
	  the entire procedure.
	</para>
      </caution>

      <para>
	After you test the first disc, another screen appears and shows
	the result:
      </para>

      <figure id="fig-mediacheck-result">
	<title>Media Check Result</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediacheckresult.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediacheckresult.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      Media check result.
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

      <para>
	Select <guibutton>OK</guibutton>.  The following screen appears:
      </para>

      <figure id="fig-mediacheck-next">
	<title>Next Disc Screen</title>
	<mediaobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediachecknext.eps" format="EPS"/>
	  </imageobject>
	  <imageobject>
	    <imagedata align="center" fileref="./figs/mediachecknext.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>
	      Next disc or continue.
	    </phrase>
	  </textobject>
	</mediaobject>
      </figure>

      <para>
	Select <guibutton>Test</guibutton> to test the next disc in the
	set, or <guibutton>Continue</guibutton> to proceed with the
	installation.
      </para>

<!--

    <note>
      <title>The <guilabel>Media Check</guilabel> may fail usable
	discs</title>
      <para>
	Discs that are valid and usable may still fail to pass the
	<guilabel>Media Check</guilabel>.
      </para>
    </note>

    Let's hash this out before we print this in the guide.  The media
    check performs a MD5 checksum over the entire data area of a CD,
    save for a small reserved area at the top, which is not used for any
    installation data.  It is possible for a disc to fail this sum and
    still install, because the error may occur in, for example, a RPM
    package that the user has not selected.  However, the user may
    encounter this error later when he tries to install that package.
    Or he may pass the disc(s) on to another person, who may make
    different choices and thus induce the media error.

    It's best to have discs that pass this check; although the user
    *may* not have a problem, we don't want to encourage people to try
    installing from bad discs on that chance. - PWF.

-->
    <para>
      After you test your discs and select
      <guibutton>Continue</guibutton>, or if you choose to skip testing,
      the main graphical installation program loads.
    </para>

    <note>
      <title>BIOS Boot Order</title>
      <para>
	The BIOS contains settings that control the order of boot
	devices.  If your PC boots from a device other than the &FC;
	boot media, check the BIOS boot configuration.
      </para>
    </note>

  </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. <!-- Refer
      to <ulink url="SOME-URL">SOME-URL</ulink> for information on how
      to configure a PXE server.  [When this tutorial exists, uncomment
      this. - PWF.] -->
    </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>

    <figure id="fig-pxe-instmethod">
      <title>Welcome to Red Hat Network Installer</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/pxeinstmethod.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/pxeinstmethod.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    Red Hat Network Installer screen.
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      Choose a network installation option to continue.
    </para>

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

  </section>
</chapter>


<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE bootloader.xml ---
<?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 determines which one to
    boot, usually by offering a menu.
  </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>
  <para>
    The following screen displays boot loader configuration options.
  </para>
  <figure id="fig-bootloader-config">
    <title>Boot Loader Configuration Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="figs/bootloader.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>Boot loader configuration screen</phrase>
      </textobject>
    </mediaobject>
  </figure>
  <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, select
      <guilabel>No boot loader will be installed</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>
  </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. To add,
      remove, or change the detected operating system settings, use the
      options provided.
    </para>

    <variablelist>
      <varlistentry>
        <term><guibutton>Add</guibutton></term>
        <listitem>
          <para>
            Press the <guibutton>Add</guibutton> button to include an
            additional operating system in GRUB. &FC; displays the
            dialog shown in
            <xref
	      linkend="fig-bootloader-others-popup"/>.
          </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>
    <figure id="fig-bootloader-others-popup">
      <title>Adding Operating Systems to the Boot Menu</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloaderothers.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloaderothers.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>Adding entries to the GRUB boot menu.</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </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 <guibutton>Change
      password</guibutton> button will become active. Select
      <guibutton>Change password</guibutton> to display the dialog
      below. Type the desired password, and then confirm it by typing it
      again in the spaces provided.
    </para>
    <figure id="fig-bootloader-password">
      <title>Entering A Boot Password</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloaderpassword.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootloaderpassword.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>Entering and confirming a boot password</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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>
    <warning>
      <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>
    </warning>

    <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 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, use the
      <guibutton>Change Drive Order</guibutton> 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 menu shown in
      <xref
	linkend="fig-bootloader-advanced"/> appears.
    </para>

    <note>
      <title>Optional Menu</title>

      <para>
        &FC; displays the following advanced boot options menu
        <emphasis>only</emphasis> if the advanced configuration check box
        described above has been selected.
      </para>
    </note>
    <figure id="fig-bootloader-advanced">
      <title>Advanced Boot Options</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootadvanced.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/bootadvanced.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>Advanced boot settings menu</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE diskpartitioning.xml ---
<?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>
    &FC; 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>
  <important>
    <title>Configuring RAID Devices</title>

    <para>
      <indexterm>
        <primary>RAID</primary>
        <secondary>hardware</secondary>
      </indexterm>
      <firstterm>RAID</firstterm> facilities enable a group, or array,
      of drives to act as a single device. Configure any RAID functions
      provided by the mainboard of your computer, or attached controller
      cards, before you begin the installation process. Each active RAID
      array appears as one drive within &FED;.
    </para>
  </important>
<!-- SE: Note that this chapter uses the term "Linux software RAID" to differentiate RAID provided by the kernel from the functions of ATA RAID controllers, which are often also called "software RAID". Unfortunately. -->
  <para>
    On systems with more than one hard drive you may configure &FC; to
    operate several of the drives as a Linux RAID array without
    requiring any additional hardware. Linux software RAID arrays are
    explained in <xref linkend="sn-disk-druid"/>.
  </para>
  <note>
    <title>Changing Your Mind</title>

    <para>
      The installation process makes no changes to your system until
      package installation begins. You may use
      <guibutton>Back</guibutton> to return to previous screens and
      change your selections at any time.
    </para>
  </note>
  <para>
    <figure id="fig-partitioning-options">
      <title>Partitioning Options Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/partitionoption.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/partitionoption.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>partitioning options screen</phrase>
        </textobject>
      </mediaobject>
    </figure>
  </para>
  <para>
    The box on the screen lists the available drives. By default, the
    installation process may affect all of the drives on your computer.
    To ensure that specific drives are not repartitioned, clear the
    check box next to those drives on this list.
  </para>
  <para>
    The installation process erases any existing Linux partitions on the
    selected drives, and replaces them with the default set of
    partitions for &FC;. 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>
          Avoid this option, unless you wish to erase all of the
	  existing operating systems and data on the selected drives.
        </para>
      </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 &FC; 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 &FC; 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, &FC;
	  creates no partitions by default.
	</para>
      </listitem>
    </varlistentry>
  </variablelist>
  <para>
    Select <guilabel>Review and modify partitioning layout</guilabel> to
    customize the set of partitions that &FC; 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 &FC; 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>
  <note>
    <title>The Next Screen</title>

    <para>
      The next screen is <guilabel>Network Devices</guilabel>, explained
      <xref linkend="ch-networkconfig"/>, unless you select an option to
      customize the partition layout. If you choose to either
      <guilabel>Create custom layout</guilabel>, or <guilabel>Review and
      modify partitioning layout</guilabel>, proceed to
      <xref linkend="sn-partitioning-general"/>.
    </para>
  </note>
  <section id="sn-partitioning-general">
    <title>General Information on Partitions</title>

    <para>
      A &FC; system has at least three partitions:
    </para>

    <itemizedlist>
      <listitem>
        <para>
          A data partition mounted at <filename>/boot</filename>
        </para>
      </listitem>
      <listitem>
        <para>
          A data partition mounted at <filename>/</filename>
        </para>
      </listitem>
      <listitem>
        <para>
          A swap 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>/home</filename>
      partition on systems that store user data, for the reasons
      explained in <xref linkend="sn-partitioning-home"/>.
    </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</firstterm> partitions 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>/</filename> (or
      <indexterm>
        <primary>partition</primary>
        <secondary>root</secondary>
      </indexterm>
      <firstterm>root</firstterm>) partition.
    </para>

    <important>
      <title>Root and <filename>/root</filename></title>

      <para>
        The <filename>/</filename> (or
        <indexterm>
          <primary>partition</primary>
          <secondary>root</secondary>
        </indexterm>
        root) partition is the top of the directory structure. The
        <indexterm>
          <primary>partition</primary>
          <secondary><filename>/root</filename>
          </secondary>
        </indexterm>
        <filename>/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>/boot/</filename> directory
          resides on the <filename>/boot</filename> partition. For
          example, the file <filename>/boot/grub/grub.conf</filename>
          resides on the <filename>/boot</filename> partition.
        </para>
      </listitem>
      <listitem>
        <para>
          Any file outside of the <filename>/boot</filename> partition,
          such as <filename>/etc/passwd</filename>, resides on the
          <filename>/</filename> partition.
        </para>
      </listitem>
    </itemizedlist>

    <para>
      Subdirectories may be assigned to partitions as well. Some
      administrators create both <filename>/usr</filename> and
      <filename>/usr/local</filename> partitions. In that case, files
      under <filename>/usr/local</filename>, such as
      <filename>/usr/local/bin/foo</filename>, are on the
      <filename>/usr/local</filename> partition. Any other files in
      <filename>/usr/</filename>, such as
      <filename>/usr/bin/foo</filename>, are in the
      <filename>/usr</filename> partition.
    </para>

    <para>
      If you create many partitions instead of one large
      <filename>/</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 partitions that you require
        immediately. You may allocate free space at any time, to meet
        needs as they arise.
      </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-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>
          Only an active Linux system may read or write to LVM volumes.
          For this reason, the <filename>/boot</filename> partition that
          initializes your system must be held outside of the LVM
          physical volumes.
        </para>
      </note>

      <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 data and swap
          partitions within LVM volumes, with a separate
          <filename>/boot</filename> partition.
        </para>
      </note>
    </section>

    <section id="sn-partitioning-home">
      <title>Creating a <filename>/home</filename> Partition</title>

      <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 &FC; without erasing user data files. LVM provides
        you with the ability to add more storage capacity for the user
        data at a later time.
      </para>
    </section>
  </section>
<!-- some notes follow:

    Sanity checks on partitions require:
    /usr  ge 250 MB
    /tmp  ge  50
    /var  ge 384
    /home ge 100
    /boot ge  75
    /     ge 250

    for ia64:
    /boot/efi ge 50 MB

    Cannot have these as separate partitions:
    /bin /dev /sbin /etc /lib /root lost+found /proc

    Cannot make partitions for these symlinks:
    /var/mail /usr/bin/X11 /usr/lib/X11 /usr/tmp

-->
  <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 &FC; 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 it's size as necessary.
      </para>
    </note>
    <figure id="fig-disk-setup">
      <title>Disk Setup Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="figs/disksetup.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="figs/disksetup.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>disk setup screen</phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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.
          </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>
            After you enter the details for your partition, select
            <guibutton>OK</guibutton> to continue.
          </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 &FC;
              </para>
            </listitem>
            <listitem>
              <para>
                provide a mount point for non-Linux partitions such as
                those used on some Windows operating systems
              </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 &FC; 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>
        </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 button 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 button 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.
          </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>
        </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>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE firstboot.xml ---
<?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>
  <para>
    The
    <indexterm>
      <primary>Setup Agent</primary>
    </indexterm>
    <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>
  <figure id="fig-fboot-welcome">
    <title>Welcome Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fbootwelcome.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/fbootwelcome.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Welcome screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>
  <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 &FC;. Each
      software package in &FC; is covered by its own license which has
      been approved by the
      <indexterm>
        <primary>OSI (Open Source Initiative)</primary>
      </indexterm>
      Open Source Initiative (OSI). For more information about the OSI,
      refer to
      <ulink
	url="http://www.opensource.org/">http://www.opensource.org/</ulink>.
    </para>
    <figure id="fig-fboot-license">
      <title>License Agreement Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootlicense.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootlicense.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    License agreement screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      To proceed, select <guilabel>Yes, I agree to the License
      Agreement</guilabel> and then select
      <guibutton>Forward</guibutton>.
    </para>
  </section>
  <section id="sn-firstboot-firewall">
    <title>Firewall</title>

    <para>
      The
      <indexterm>
        <primary>firewall</primary>
        <secondary>configuring</secondary>
      </indexterm>
      <firstterm>firewall</firstterm> built into &FC; checks every
      incoming and outgoing network connection on your machine against a
      set of rules. These rules specify which types of connections are
      permitted and which are denied.
    </para>

    <para>
      By default the firewall is enabled, with a simple set of rules
      that allow connections to be made from your system to others, but
      permit only network browsing and
      <indexterm>
        <primary>SSH (Secure SHell)</primary>
        <secondary>firewall configuration</secondary>
      </indexterm>
      SSH (Secure SHell) connections from other systems. You may make
      changes on this screen to allow access to specific network
      services on your &FED; system.
    </para>
    <figure id="fig-fboot-firewall">
      <title>Firewall Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootfirewall.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootfirewall.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Firewall screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      To enable access to the services listed on this screen, click the
      check box next to the service name.
    </para>

    <important>
      <title>SSH Provides Immediate Remote Access</title>

      <para>
        All &FED; systems automatically run the SSH remote access
        service. The default firewall configuration allows connections
        to this service, to ensure that administrators have immediate
        remote access to new systems through the user and
        <systemitem class="username">root</systemitem> accounts.
      </para>
    </important>

    <para>
      To enable access to other services, select <guilabel>Other
      ports</guilabel>, and <guibutton>Add</guibutton> the details. Use
      the <guilabel>Port(s)</guilabel> field to specify either the port
      number, or the registered name of the service. Select the relevant
      <guilabel>Protocol</guilabel> from the drop-down. The majority of
      services use the TCP protocol.
    </para>
    <tip>
      <title>The Services List</title>
      <para>
        The <filename>services</filename> file on every system lists the
        port numbers and names of services that are registered with the
        Internet Assigned Names Authority (IANA). &FED; systems hold
        this file in the directory <filename>/etc</filename>.
      </para>
    </tip>
    <para>
      If a service uses more than one port number, enter each port. For
      example, an IMAP service enables users to access their e-mail from
      another system with either a standard connection to TCP port 143,
      or with an encrypted connection to TCP port 993. To permit IMAP
      connections to your system, add <userinput>imap</userinput> or
      port number <userinput>143</userinput>, and
      <userinput>imaps</userinput>, or port number
      <userinput>993</userinput>, for IMAP with SSL encryption.
    </para>

    <para>
      Avoid disabling the firewall. If you believe that it is necessary
      to do so, select <guilabel>No firewall</guilabel>.
    </para>
    <tip>
      <title>Changing the Firewall Settings</title>
      <para>
        To change these settings later, choose <menuchoice>
        <guimenu>System</guimenu>
        <guisubmenu>Administration</guisubmenu><guimenuitem>Security
        Level and Firewall</guimenuitem></menuchoice>.
      </para>
    </tip>
  </section>
  <section id="sn-firstboot-selinux">
    <title>&SEL;</title>
    <figure id="fig-fboot-selinux">
      <title>&SEL; Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootselinux.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootselinux.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    &SEL; screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      The
      <indexterm>
        <primary>&SEL;</primary>
        <secondary>configuring</secondary>
      </indexterm>
      <firstterm>&SEL;</firstterm> (Security Enhanced Linux) framework
      is part of &FC;. &SEL; limits the actions of both users and
      programs by enforcing security policies throughout the operating
      system. Without &SEL;, software bugs or configuration changes may
      render a system more vulnerable. The restrictions imposed by &SEL;
      policies provide extra security against unauthorized access.
    </para>

    <para>
      Inflexible &SEL; policies might inhibit many normal activities on
      a &FED; system. For this reason, &FC; uses targeted policies,
      which only affect specific network services. These services cannot
      perform actions that are not part of their normal functions. The
      targeted policies reduce or eliminate any inconvenience &SEL;
      might cause users. Set the &SEL; mode to one of the following:
    </para>

    <variablelist>
      <varlistentry>
        <term><guilabel>Enforcing</guilabel></term>
        <listitem>
          <para>
            Select this mode to use the targeted &SEL; policy on your
            &FED; system. This is the default mode for &FED;
            installations.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><guilabel>Permissive</guilabel></term>
        <listitem>
          <para>
            In this mode, the system is configured with &SEL;, but a
            breach of security policies only causes an error message to
            appear. No activities are actually prohibited when &SEL; is
            installed in this mode. You may change the &SEL; mode to
            <guilabel>Enforcing</guilabel> at any time after booting.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><guilabel>Disabled</guilabel></term>
        <listitem>
          <para>
            If you choose this mode for &SEL;, &FED; does not configure
            the access control system at all. To make &SEL; active
            later, select <menuchoice> <guimenu>System</guimenu>
            <guisubmenu>Administration</guisubmenu>
            <guimenuitem>Security Level and Firewall</guimenuitem>
            </menuchoice>.
          </para>
        </listitem>
      </varlistentry>
    </variablelist>
<!-- SE: Note that items on this screen are labeled "SELinux...", so the text doesn't use the &SEL; entity in those cases. -->
    <para>
      To adjust &SEL;, choose <guilabel>Modify SELinux
      Policy</guilabel>. To exempt a key service from &SEL;
      restrictions, select the service from the list, and choose the
      <guilabel>Disable SELinux protection</guilabel> option. The
      <guilabel>SELinux Service Protection</guilabel> item on the list
      includes options to disable &SEL; restrictions on additional
      services.
    </para>
    <tip>
      <title>Changing the &SEL; policy</title>
      <para>
        &SEL; is unique in that it cannot be bypassed, even by the
        system administrators. To change the behavior of &SEL; after
        installation, choose <menuchoice> <guimenu>System</guimenu>
        <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
        Level and Firewall</guimenuitem> </menuchoice>.
      </para>
    </tip>
    <para>
      For more information about &SEL;, refer to the &SEL; FAQ at
      <ulink
      url="http://fedora.redhat.com/docs/selinux-faq/"/>.
    </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>
    <figure id="fig-fboot-time">
      <title>Date and Time Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdatetime.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdatetime.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Date and time screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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>
    <figure id="fig-fboot-time-ntp">
      <title>Date and Time Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdatetimentp.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdatetimentp.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Date and time screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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 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-firstboot-display">
    <title>Display</title>

    <para>
      The <application>Setup Agent</application> automatically attempts
      to identify the graphics card and monitor for your computer. It
      uses this information to calculate the correct
      <guilabel>Resolution</guilabel> and <guilabel>Color
      Depth</guilabel> settings.
    </para>

<!-- This screen has been removed in FC6.

    <figure id="fig-fboot-display">
      <title>Display Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdisplay.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdisplay.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Display screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      If you need to change the monitor, select
      <guilabel>Configure</guilabel> to display a list of manufacturers.
      Select the manufacturer of your monitor on the list, and hit the
      <keycap>+</keycap> key or select the triangle next to the name to
      view supported models. Choose the correct model from the list and
      select <guibutton>OK</guibutton>. If none of the listed models
      match your monitor, select the closest match from either the
      <guilabel>Generic CRT Display</guilabel> list or the
      <guilabel>Generic LCD Display</guilabel> list.
    </para>
    <figure id="fig-fboot-display-monitor">
      <title>Monitor Dialog</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdisplaymonitor.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootdisplaymonitor.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Monitor dialog.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      To change a display setting, select
      <guilabel>Resolution</guilabel> or <guilabel>Color
      Depth</guilabel>, and select a new value from the drop-down list.
      The <application>Setup Agent</application> only shows the settings
      that are valid for your hardware.
    </para>

-->

    <para>
      To reconfigure your system after the installation has completed,
      choose <menuchoice> <guimenu>System</guimenu>
        <guisubmenu>Administration</guisubmenu>
        <guimenuitem>Display</guimenuitem> </menuchoice>.
    </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>
    <figure id="fig-fboot-user">
      <title>System User Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootsystemuser.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootsystemuser.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    System user screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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-soundcard">
    <title>Sound Card</title>

    <para>
      The <application>Setup Agent</application> automatically attempts
      to identify the sound card in your computer.
    </para>
    <figure id="fig-fboot-sound">
      <title>Sound Card Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootsoundcard.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/fbootsoundcard.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
           Sound card screen.
         </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      Click the play button to check the sound card configuration. If
      the configuration is correct, &FED; plays a sound sequence. You
      may adjust the volume with the slidebar. The
      <guilabel>Repeat</guilabel> option causes the sound to play until
      the option is unselected, to assist you in tuning your system.
    </para>

    <para>
      If your sound card is identified, but you do not hear the sound,
      check your speakers and try again. In some cases, you may need to
      alter the additional settings to obtain the best sound quality.
    </para>

    <para>
      A sound card may provide multiple audio input and output devices.
      To change the <guilabel>Default PCM device</guilabel>, select a
      new option from the drop-down list. By default, audio applications
      connect to a software mixer that manages the PCM devices. To
      enable applications to bypass the software mixer, select the
      option to <guilabel>Disable software mixing</guilabel>.
    </para>

    <para>
      You may manually configure a &FC; system to use unsupported sound
      cards after the installation process is complete. Manual sound
      hardware configuration is beyond the scope of this document.
    </para>
    <tip>
      <title>Changing the Sound Card</title>
      <para>
        &FED; automatically attempts to detect a new sound card if you
        add one to your system. If you need to launch the detection
        process manually, choose <menuchoice> <guimenu>System</guimenu>
        <guisubmenu>Administration</guisubmenu> <guimenuitem>Soundcard
        Detection</guimenuitem> </menuchoice>.
      </para>
    </tip>
    <para>
      After you configure the sound card, select
      <guilabel>Finish</guilabel> to proceed to the login screen. Your
      &FC; system is now ready for use.
    </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
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE installingpackages.xml ---
<?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>

  <figure id="fig-installing-inprogress">
    <title>Installing Packages Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installingpackages.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/installingpackages.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Installing packages screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>
    
  <para>
    After installation completes, select <guibutton>Reboot</guibutton>
    to restart your computer.  &FC; ejects any loaded discs before the
    computer reboots.
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE intro.xml ---
<?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>
  <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>
    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 id="sn-background">
    <title>Background</title>

    <para>
      The &FP;, which produces and maintains &FC;, is a collaboration
      between &FORMAL-RHI; and the
      <indexterm>
        <primary>free software</primary>
        <see>FOSS</see>
      </indexterm>
      <indexterm>
        <primary>open source</primary>
        <see>FOSS</see>
      </indexterm>
      <indexterm>
        <primary>FOSS (free and open source software)</primary>
      </indexterm>
      <firstterm>free and open source software</firstterm> (FOSS)
      community. The &FP; also provides &FEX;, additional software
      packaged for installation on a &FC; system.
    </para>

    <para>
      For more information about the &FP;, please visit &FP-URL;. Refer
      to <ulink url="http://www.opensource.org/"/> and <ulink
	url="http://www.gnu.org/philosophy/free-sw.html"/> for more
      information about open source software.
    </para>
  </section>
  <section id="sn-hwarchitecture">
    <title>Understanding i386 and Other Computer Architectures</title>

    <para>
      The &FP; provides distributions of &FC; for several different
      types of computer systems.  Each distribution of &FC; is built for
      computers based on a specific <firstterm>architecture</firstterm>.
      The architecture describes the processor on which the computer is
      built.  Most computers come with identifying marks and literature
      describing the processor inside the computer.  Refer to your
      computer's marks or literature and find its architecture in the
      list below:
    </para>

    <variablelist>
      <varlistentry>
        <term>i386</term>
        <listitem>
          <para>
            Intel x86-compatible processors, including Intel Pentium and
	    Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron,
	    Pentium 4, Xeon, Core Duo, and Centrino/Centrino Duo; VIA
	    C3/C3-m and Eden/Eden-N; and AMD Athlon, AthlonXP, Duron,
	    AthlonMP, Sempron, and Turion
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>ppc</term>
        <listitem>
          <para>
            PowerPC processors, such as those found in Apple Power
            Macintosh, G3, G4, and G5, and IBM pSeries systems
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term>x86_64</term>
        <listitem>
          <para>
            64-bit AMD processors such as Athlon64/FX/X2, Turion64,
	    Opteron; and Intel 64-bit processors such as EM64T
          </para>
        </listitem>
      </varlistentry>
    </variablelist>
  </section>
  <section id="sn-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="sn-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 Control
	  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://fedora.redhat.com/download/mirrors.html"/>. 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://fedora.redhat.com/docs/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="sn-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 either an installation DVD, or
          the first installation 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>
  </section>
  <section id="sn-preparing-media">
    <title>Preparing Media</title>

    <para>
      To install &FC; from discs, you need five installation CDs, or the
      installation DVD. There are separate disc sets for each supported
      architecture.
    </para>

    <para>
      For instructions to download and prepare this CD or DVD
      installation media, refer to
      <ulink url="http://fedora.redhat.com/download/"/>. If you already
      have the full set of &FC; installation media, skip to
      <xref
      linkend="sn-booting-from-disc"/>.
    </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-hwarchitecture"/> 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 MacOS X</term>
          <listitem>
            <para>
              Open the <guilabel>Disk Copy</guilabel> application, found
              in the <filename>/Applications/Utilities</filename>
              folder. From the menu, select <menuchoice>
              <guimenu>Image</guimenu> <guimenuitem>Burn
              Image...</guimenuitem> </menuchoice>. Select the CD image
              to burn, check that the burn options are correct, and
              select the <guilabel>Burn</guilabel> button.
            </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 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 forms of SCSI device.
          </para>
        </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 <replaceable>/dev/sda</replaceable></userinput>
</screen>
          <para>
            Replace <filename>/dev/sda</filename> 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=<replaceable>/dev/sda</replaceable></userinput>
</screen>
          <para>
            Replace <filename>/dev/sda</filename> with the name of the
            correct device file for the media.
          </para>
        </step>
      </procedure>
    </section>
  </section>
</preface>

<!--
Local variables:
mode: xml
fill-column: 72
End:
-->


--- NEW FILE locale.xml ---
<?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>
  <para>
    If the installation system fails to identify the display hardware on
    your computer, it displays text screens rather than the default
    graphical interface. The text screens provide the same functions as
    the standard screens. Later in the installation process you can
    manually specify your display hardware.
  </para>
  <important>
    <title>Network Installations</title>

    <para>
      Network installations with HTTP and FTP always use text screens on
      systems with less than 128Mb of memory.
    </para>
  </important>
  <section id="sn-installer-language">
    <title>Language Selection</title>

    <para>
      The installation program displays a list of languages supported by
      &FED;.
    </para>
    <figure id="fig-lang-selection">
      <title>Language Selection Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/langselection.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/langselection.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Language selection screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      Highlight the correct language on the list and select
      <guibutton>Next</guibutton>.
    </para>

    <note>
      <title>Installing Support For Additional Languages</title>

      <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>
  </section>
  <section id="sn-installer-keyboard">
    <title>Keyboard Configuration</title>

    <para>
      The installation program display a list of the keyboard layouts
      supported by &FED;:
    </para>
    <figure id="fig-keyb-conf">
      <title>Keyboard Configuration Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/keylayoutselection.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/keylayoutselection.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Keyboard configuration screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      Highlight the correct layout on the list, and select
      <guibutton>Next</guibutton>.
    </para>
  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE networkconfig.xml ---
<?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>
    Use this screen to customize the network settings of your &FED;
    system.
  </para>

  <para>
    Manual network configuration of a &FED; system is often not
    required.  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
    configuration data.  By default, &FC; activates all network
    interfaces on your computer and configures them to use DHCP. 
  </para>

  <figure id="fig-net-config-dhcp">
    <title>Network Configuration Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/networkconfig.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/networkconfig.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Network configuration screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>


  <section id="sn-network-devices">
    <title>Network Devices</title>

    <para>
      &FED; displays a list of network interfaces detected on your
      computer.  Each interface must have a unique <firstterm>IP
	address</firstterm> <indexterm>
	<primary>IP address</primary>
      </indexterm> on the network to which it is attached. The interface
      may receive this address from the network <indexterm>
	<primary>DHCP (Dynamic Host Configuration Protocol)</primary>
      </indexterm> DHCP service.
    </para>

    <para>
      To manually assign an IP address, highlight the interface on the
      <guilabel>Network Device</guilabel> list and select
      <guibutton>Edit</guibutton>.  &FED; then displays a network
      configuration dialog. <emphasis>Deselect</emphasis> the
      <guilabel>Configure using DHCP</guilabel> check box, so that it is
      empty.  Enter the <guilabel>IP Address</guilabel> and the
      appropriate <guilabel>Netmask</guilabel> for the interface.  Then
      select <guibutton>OK</guibutton>.
    </para>

    <para>
      If your computer will be a server, do not use DHCP.  Manually
      configure networking instead.  Manual network configuration allows
      your server to join the local network even if the DHCP provider is
      down.
    </para>
      
    <para>
      Specify whether an interface should be automatically activated at
      boot time with the <guilabel>Active on Boot</guilabel> check box
      for that device. You may manually activate a network interface at
      any time after the system has booted.
    </para>

    <note>
      <title>Modem Configuration</title>
      <para>
	The <guilabel>Network Configuration</guilabel> screen does not
	list <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>


  <section id="sn-computer-hostname">
    <title>Computer 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>.  To specify the
      hostname, select <guilabel>Manual</guilabel> and type the complete
      name in the box. The complete hostname includes both the name of
      the machine and the name of the domain of which it is a member,
      such as <replaceable>machine1.example.com</replaceable>.  The
      machine name (or "short hostname") is
      <replaceable>machine1</replaceable>, and the <indexterm>
	<primary>domain name</primary>
      </indexterm> domain name is
      <replaceable>example.com</replaceable>.
    </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>

  </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</guilabel>,
      <guilabel>Secondary</guilabel>, or <guilabel>Tertiary DNS
	Server</guilabel> boxes.
    </para>

    <para>
      Click <guibutton>Next</guibutton> once you are satisfied with the
      network settings for your system.
    </para>

  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE nextsteps.xml ---
<?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 &FP; releases updated software packages for &FC; 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, carry out
      an update when the installation process completes. You should then
      update regularly, and as soon as possible after a security
      announcement is issued. Refer to
      <xref linkend="sn-news-subscriptions"/> for information on the
      &FED; announcements services.
    </para>

    <para>
      To update your system with the latest packages, use the
      <indexterm>
        <primary>Software Updater</primary>
      </indexterm>
      <application>Software Updater</application>:
    </para>
    <orderedlist>
      <listitem>
        <para>
          Choose <menuchoice><guimenu>Applications</guimenu>
          <guisubmenu>System Tools</guisubmenu> <guimenuitem>Software
          Updater</guimenuitem> </menuchoice>.
        </para>
      </listitem>
      <listitem>
        <para>
          When prompted, enter the
          <systemitem class="username">root</systemitem> password.
        </para>
      </listitem>
      <listitem>
        <para>
          Review the list of updated packages. The package list displays
          a double arrow next to any updates that require a system
          reboot to take effect.
        </para>
      </listitem>
      <listitem>
        <para>
          Click <guibutton>Apply Updates</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>
    </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://fedora.redhat.com/docs/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>Software Updater</application>, or the
        <command>yum</command> utility. The update process downloads
        information and packages from a network of servers.
      </para>
    </note>
    <tip>
      <title>Automating Updates</title>
      <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://fedora.redhat.com/docs/yum/sn-updating-your-system.html"/>.
      </para>
    </tip>
  </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 provides support through mailing
      lists, Web forums and Linux User Groups (LUGs) across the world.
    </para>

    <para>
      The Web site for the official 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://fedora.redhat.com/docs/"/>
              </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://fedoraproject.org/wiki/HelpWanted"/>
    </para>
  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE other-instmethods.xml ---
<?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>Alternative Installation Methods</title>
  <para>
    The installation method screen below appears if one of the following
    is true:
  </para>
  <orderedlist>
    <listitem>
      <para>
        You booted with PXE, USB media, or boot-only CD or DVD media.
      </para>
    </listitem>
    <listitem>
      <para>
        You entered the <option>askmethod</option> option at the
        <prompt>boot:</prompt>
        prompt.
      </para>
    </listitem>
  </orderedlist>
  <figure id="fig-install-method">
    <title>Installation Method Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/askinstallmethod.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/askinstallmethod.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Installation method screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>
    Highlight the appropriate installation method on the list, and
    select <guibutton>OK</guibutton>.
  </para>
  <note>
    <title>CD/DVD Activity</title>

    <para>
      If the first &FC; distribution installation disc is in your
      computer's CD or DVD drive, the installation program loads its
      next stage from that disc. The installation program still
      downloads <emphasis>package data</emphasis> from the source you
      choose.
    </para>
  </note>
  <section id="sn-install-method-server">
    <title>Installation from a Network Server</title>

    <para>
      You may install &FC; from a network server using FTP, HTTP, or
      <indexterm>
        <primary>NFS (Network File System)</primary>
        <secondary>install from</secondary>
      </indexterm>
      NFS protocols. Refer to
      <xref linkend="sn-installing-networkinstallation"/> for
      information on installation servers.
    </para>

    <section id="sn-installer-tcpip">
      <title>TCP/IP Configuration</title>

      <para>
        By default, the installation program uses DHCP to automatically
        provide the network settings. If your network has no DHCP
        server, clear the check box labeled <guibutton>Use dynamic IP
        configuration</guibutton> and enter the settings manually.
        Select <guibutton>OK</guibutton> to continue.
      </para>
      <figure id="fig-inst-ipsetup">
        <title>Configure TCP/IP Dialog</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/anaipsetup.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/anaipsetup.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>
	      TCP/IP configuration dialog.
	    </phrase>
          </textobject>
        </mediaobject>
      </figure>
      <para>
        These settings apply only during the installation process. The
        installation program allows you to configure the final network
        configuration later.
      </para>
    </section>

    <section id="sn-installer-service-settings">
      <title>Network Service Setup</title>

      <para>
        The FTP, HTTP, and NFS service setup dialogs are very similar.
        Each requires the name or IP address of the server, and a
        directory where the installation files reside. To use a public
        server, or mirror website, refer to
        <xref linkend="sn-installing-networkinstallation"/> for
        information on valid server names and directory paths.
      </para>
      <figure id="fig-ftp-setup">
        <title>FTP Setup Dialog</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftpsetup.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftpsetup.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>
	      FTP setup dialog.
	    </phrase>
          </textobject>
        </mediaobject>
      </figure>
      <para>
        The FTP service setup dialog also has an option for
        <guilabel>non-anonymous FTP</guilabel>. If your FTP server does
        not provide anonymous access, select this check box, and provide
        an account name and password in the following dialog. Select
        <guibutton>OK</guibutton> to continue.
      </para>
      <figure id="fig-ftp-setup-further">
        <title>Non-anonymous FTP Account Dialog</title>
        <mediaobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftpsetupfurther.eps" format="EPS"/>
          </imageobject>
          <imageobject>
            <imagedata align="center" fileref="./figs/ftpsetupfurther.png" format="PNG"/>
          </imageobject>
          <textobject>
            <phrase>
	      Non-anonymous FTP account dialog.
	    </phrase>
          </textobject>
        </mediaobject>
      </figure>
      <note>
        <title>Large Download</title>

        <para>
          Network installations download the main installation program
          from the server that you specify. The graphical installation
          program is over 60 Mb in size. Computers with a slow network
          connection may take several minutes to download this file.
        </para>
      </note>
    </section>
  </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. You can use this
      option to install &FC; on computers that have neither a network
      connection nor CD or DVD drives.
    </para>

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

    <note>
      <title>FAT-16, FAT-32, and <systemitem
	  class="filesystem">vfat</systemitem></title>

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

    <para>
      You cannot use ISO files on partitions controlled by LVM (Logical
      Volume Management). Refer to
      <xref
	linkend="sn-partitioning-general" /> for more information
      about file systems.
    </para>

    <para>
      If you choose this option, the following screen appears:
    </para>
    <figure id="fig-hdd-instmethod">
      <title>Select Partition Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/hddinstmethod.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/hddinstmethod.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Select partition screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      Select the partition containing the ISO files from the list of
      available partitions. Internal IDE drive device names begin with
      <filename>/dev/hd</filename>. SCSI or USB drive device names begin
      with <filename>/dev/sd</filename>. Each individual drive has its
      own letter, for example <filename>/dev/hda</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.
    </para>

    <para>
      Select <guibutton>OK</guibutton> to continue.
    </para>
  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE packageselection.xml ---
<?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>
  <para>
    By default, the &FED; installation process loads a selection of
    software that is suitable for a desktop system.
  </para>
  <figure id="fig-task-selection">
    <title>Task Selection Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/taskselection.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/taskselection.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	    Task selection screen.
	  </phrase>
      </textobject>
    </mediaobject>
  </figure>
  <para>
    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>
  <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>
  <section id="sn-additional-repos">
    <title>Installing from Additional Repositories</title>
    <para>
      To include software from <firstterm>repositories</firstterm> other
      than Fedora Core, select <guilabel>Add additional software
	repositories</guilabel>.  A repository is a network location
      that stores software packages along with
      <firstterm>metadata</firstterm> that describes them.  The
      following list includes examples of ways you can use this option.
    </para>
    <itemizedlist>
      <listitem>
	<formalpara>
	  <title>Get the Latest Fedora Software</title>
	  <para>
	    If you provide the location of a repository of updates for
	    Fedora Core, your system will have the most recent versions
	    of Core software.  You will not need to peform a system
	    update immediately after installation to get these updates.
	    This usage is ideal if you are installing over the Internet
	    or any network where bandwidth is a concern.
	  </para>
	</formalpara>
      </listitem>
      <listitem>
	<formalpara>
	  <title>Install Fedora Extras Software</title>
	  <para>If you provide the location of a repository of Fedora
	    Extras software, you can include many additional packages on
	    your system during installation.  For more information about
	    Fedora Extras, refer to the Release Notes or <ulink
	      url="http://fedoraproject.org/wiki/Extras"/>.</para>
	</formalpara>
      </listitem>
      <listitem>
	<formalpara>
	  <title>Install Third-party Software</title>
	  <para>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>
	</formalpara>
      </listitem>
    </itemizedlist>
    <para>
      If you select <guilabel>Add additional software
	repositories</guilabel>, the following dialog appears:
    </para>
    <figure id="fig-additional-repos">
      <title>Add Repository Screen</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/additionalrepo.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/additionalrepo.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    Add repository screen.
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>
    <para>
      Provide a name for the repository and the URL for its location.
      Here are some URLs for listings of specific Fedora software
      repository mirrors.
    </para>
    <itemizedlist>
      <listitem>
	<para>Fedora Core Updates -
	  http://fedora.redhat.com/download/mirrors/updates-released-fc&FCLOCALVER;</para>
      </listitem>
      <listitem>
	<para>Fedora Extras - http://fedora.redhat.com/download/mirrors/fedora-extras-&FCLOCALVER;</para>
      </listitem>
    </itemizedlist>
    <important>
      <title>These URLs are Mirror Lists</title>
      <para>
	The URLs above provide a list of actual mirrors.  You cannot use
	them verbatim in the <guilabel>Add repository</guilabel>
	dialog.  Visit the URL for a list of actual repository
	locations.  If you see the text <literal>$ARCH</literal> in the
	URL, substitute your system's architecture.  See <xref
	  linkend="sn-hwarchitecture"/> for more information on
	architectures.
      </para>
    </important>
    <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 Erases Added Repository Data</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-mandatory-services">
    <title>Core Network Services</title>

    <para>
      All Fedora Core 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 id="sn-package-selection">
    <title>Customizing the Software Selection</title>

    <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 six categories:
    </para>
    <figure id="fig-package-selection">
      <title>Package Group Selection Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/packagegroups.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/packagegroups.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Package group selection screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <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>
    <figure id="fig-package-selection-details">
      <title>Package Group Details Dialog</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/packagegroupdetail.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/packagegroupdetail.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Package group details dialog.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <tip>
      <title>Changing Your Mind</title>
      <para>
        The packages that you select are not permanent. After you boot
        your system, use the <application>pirut</application> tool to
        either install new software, or remove installed packages. To
        run this tool, from the main menu, select <menuchoice>
        <guimenu>Applications</guimenu> <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>
    </tip>
  </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>

    <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.
    </para>
  </section>
</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE rootpassword.xml ---
<?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.
  </para>

  <figure id="fig-set-rootpw">
    <title>Set Root Password Screen</title>
    <mediaobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/rootpassword.eps" format="EPS"/>
      </imageobject>
      <imageobject>
        <imagedata align="center" fileref="./figs/rootpassword.png" format="PNG"/>
      </imageobject>
      <textobject>
        <phrase>
	  Set root password screen.
        </phrase>
      </textobject>
    </mediaobject>
  </figure>

  <para>
    After you set the root password, select <guibutton>Next</guibutton>
    to proceed.
  </para>

</chapter>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE techref.xml ---
<?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>ALSA (Advanced
          Linux Sound Architecture)</primary>
          </indexterm>
          ALSA (Advanced Linux Sound Architecture). For more information
          about ALSA, refer to the project Web site:
          <ulink url="http://www.alsa-project.org/"/>.
        </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/"/>.
        </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; FAQ for more information:
          <ulink url="http://fedora.redhat.com/docs/selinux-faq/"/>.
        </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://fedora.redhat.com/docs/yum/"/> for more
          information.
        </para>
      </listitem>
    </varlistentry>

    <varlistentry>
      <term>Virtualization</term>
      <listitem>
        <para>
          <indexterm>
            <primary>Xen</primary>
            <secondary>documentation</secondary>
          </indexterm>
          Xen 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 Xen support during the installation
          process, or at any time thereafter. Refer to
          <ulink url="http://www.fedoraproject.org/wiki/Tools/Xen"/> for
          more information.
        </para>
      </listitem>
    </varlistentry>
  </variablelist>
</appendix>

<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide.xml" "book" "appendix")
fill-column: 72
End:
-->


--- NEW FILE timezone.xml ---
<?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.
    </para>
    <figure id="fig-timezone">
      <title>Time Zone Selection Screen</title>
      <mediaobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/timezone.eps" format="EPS"/>
        </imageobject>
        <imageobject>
          <imagedata align="center" fileref="./figs/timezone.png" format="PNG"/>
        </imageobject>
        <textobject>
          <phrase>
	    Time zone selection screen.
	  </phrase>
        </textobject>
      </mediaobject>
    </figure>
    <para>
      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>

    <para>
      <indexterm>
      <primary>UTC (Universal Co-ordinated time)</primary>
      </indexterm> Universal Co-ordinated Time is also known as
      <indexterm>
      <primary>GMT (Greenwich Mean Time)</primary>
      <see>UTC</see>
      </indexterm> 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
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


--- NEW FILE upgrading.xml ---
<?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, the
      following screen appears:
    </para>

    <figure id="fig-upgrade-examine">
      <title>Upgrade Examine Screen</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgrade.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    Upgrade examine screen.
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <para>
      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 which you have installed manually on your existing &FC;
	or &RHL; system may behave differently after an upgrade.  You
	may need to manually recompile this software after an upgrade to
	ensure it performs correctly on the updated system.
      </para>
    </note>

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


    <figure id="fig-upgrade-bootloader">
      <title>Upgrade Bootloader Screen</title>
      <mediaobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgradebootloader.eps" format="EPS"/>
	</imageobject>
	<imageobject>
	  <imagedata align="center" fileref="./figs/upgradebootloader.png" format="PNG"/>
	</imageobject>
	<textobject>
	  <phrase>
	    Upgrade bootloader screen.
	  </phrase>
	</textobject>
      </mediaobject>
    </figure>

    <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
sgml-parent-document:("fedora-install-guide.xml" "book" "chapter")
fill-column: 72
End:
-->


Index: fedora-install-guide.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/fedora-install-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide.xml	19 Aug 2006 23:41:06 -0000	1.1
+++ fedora-install-guide.xml	21 Aug 2006 12:05:30 -0000	1.2
@@ -14,41 +14,41 @@
 <book id="book" lang="en_US">
   <xi:include href="./fdp-info.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-intro.xml" xpointer="element(ch-intro)"
+  <xi:include href="./intro.xml" xpointer="element(ch-intro)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-beginninginstallation.xml" xpointer="element(ch-beginninginstallation)"
+  <xi:include href="./beginninginstallation.xml" xpointer="element(ch-beginninginstallation)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-other-instmethods.xml" xpointer="element(ch-other-install-methods)"
+  <xi:include href="./other-instmethods.xml" xpointer="element(ch-other-install-methods)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-locale.xml" xpointer="element(ch-installer-locale)"
+  <xi:include href="./locale.xml" xpointer="element(ch-installer-locale)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-upgrading.xml" xpointer="element(ch-upgrading-system)"
+  <xi:include href="./upgrading.xml" xpointer="element(ch-upgrading-system)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-diskpartitioning.xml" xpointer="element(ch-disk-partitioning)"
+  <xi:include href="./diskpartitioning.xml" xpointer="element(ch-disk-partitioning)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-bootloader.xml" xpointer="element(ch-bootloader)"
+  <xi:include href="./bootloader.xml" xpointer="element(ch-bootloader)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-networkconfig.xml" xpointer="element(ch-networkconfig)"
+  <xi:include href="./networkconfig.xml" xpointer="element(ch-networkconfig)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-timezone.xml" xpointer="element(ch-timezone)"
+  <xi:include href="./timezone.xml" xpointer="element(ch-timezone)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-rootpassword.xml" xpointer="element(ch-rootpassword)"
+  <xi:include href="./rootpassword.xml" xpointer="element(ch-rootpassword)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-packageselection.xml" xpointer="element(ch-packageselection)"
+  <xi:include href="./packageselection.xml" xpointer="element(ch-packageselection)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-abouttoinstall.xml" xpointer="element(ch-abouttoinstall)"
+  <xi:include href="./abouttoinstall.xml" xpointer="element(ch-abouttoinstall)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-installingpackages.xml" xpointer="element(ch-installing-packages)"
+  <xi:include href="./installingpackages.xml" xpointer="element(ch-installing-packages)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-firstboot.xml" xpointer="element(ch-firstboot)"
+  <xi:include href="./firstboot.xml" xpointer="element(ch-firstboot)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-nextsteps.xml" xpointer="element(ch-next-steps)"
+  <xi:include href="./nextsteps.xml" xpointer="element(ch-next-steps)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-adminoptions.xml" xpointer="element(ap-admin-options)"
+  <xi:include href="./adminoptions.xml" xpointer="element(ap-admin-options)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-techref.xml" xpointer="element(ap-techref)"
+  <xi:include href="./techref.xml" xpointer="element(ap-techref)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <xi:include href="./fedora-install-guide-acknowledgements.xml" xpointer="element(ch-acknowledgements)"
+  <xi:include href="./acknowledgements.xml" xpointer="element(ch-acknowledgements)"
   xmlns:xi="http://www.w3.org/2001/XInclude"/>
   <index id="generated-index">
   </index>


--- fedora-install-guide-abouttoinstall.xml DELETED ---


--- fedora-install-guide-acknowledgements.xml DELETED ---


--- fedora-install-guide-adminoptions.xml DELETED ---


--- fedora-install-guide-beginninginstallation.xml DELETED ---


--- fedora-install-guide-bootloader.xml DELETED ---


--- fedora-install-guide-diskpartitioning.xml DELETED ---


--- fedora-install-guide-firstboot.xml DELETED ---


--- fedora-install-guide-installingpackages.xml DELETED ---


--- fedora-install-guide-intro.xml DELETED ---


--- fedora-install-guide-locale.xml DELETED ---


--- fedora-install-guide-networkconfig.xml DELETED ---


--- fedora-install-guide-nextsteps.xml DELETED ---


--- fedora-install-guide-other-instmethods.xml DELETED ---


--- fedora-install-guide-packageselection.xml DELETED ---


--- fedora-install-guide-rootpassword.xml DELETED ---


--- fedora-install-guide-techref.xml DELETED ---


--- fedora-install-guide-timezone.xml DELETED ---


--- fedora-install-guide-upgrading.xml DELETED ---




More information about the Fedora-docs-commits mailing list