install-guide/en fdp-info.xml, NONE, 1.1.2.1 fedora-install-guide-abouttoinstall.xml, NONE, 1.1.2.1 fedora-install-guide-acknowledgements.xml, NONE, 1.1.2.1 fedora-install-guide-adminoptions.xml, NONE, 1.1.2.1 fedora-install-guide-beginninginstallation.xml, NONE, 1.1.2.1 fedora-install-guide-bootloader.xml, NONE, 1.1.2.1 fedora-install-guide-diskpartitioning.xml, NONE, 1.1.2.1 fedora-install-guide-firstboot.xml, NONE, 1.1.2.1 fedora-install-guide-installingpackages.xml, NONE, 1.1.2.1 fedora-install-guide-intro.xml, NONE, 1.1.2.1 fedora-install-guide-locale.xml, NONE, 1.1.2.1 fedora-install-guide-networkconfig.xml, NONE, 1.1.2.1 fedora-install-guide-nextsteps.xml, NONE, 1.1.2.1 fedora-install-guide-other-instmethods.xml, NONE, 1.1.2.1 fedora-install-guide-packageselection.xml, NONE, 1.1.2.1 fedora-install-guide-rootpassword.xml, NONE, 1.1.2.1 fedora-install-guide-techref.xml, NONE, 1.1.2.1 fedora-install-guide-timezone.xml, NONE, 1.1.2.1 fedora-install-guide-upgrading.xml, NONE, 1.1.2.1 fedora-install-gu! ide.xml,NONE,1.1.2.1
Scott Glaser (sonarguy)
fedora-docs-commits at redhat.com
Wed Feb 15 11:48:06 UTC 2006
- Previous message (by thread): docs-common/bin fdp-functions,1.10,1.11
- Next message (by thread): install-guide/figs about-to-install-ja_JP.png, 1.1, NONE bootloader-advanced-ja_JP.png, 1.1, NONE bootloader-change-ja_JP.png, 1.1, NONE bootloader-config-ja_JP.png, 1.1, NONE bootloader-others-ja_JP.png, 1.1, NONE bootloader-password-ja_JP.png, 1.1, NONE disk-setup-ja_JP.png, 1.1, NONE fboot-cds-ja_JP.png, 1.1, NONE fboot-display-ja_JP.png, 1.1, NONE fboot-display-monitor-ja_JP.png, 1.1, NONE fboot-finish-ja_JP.png, 1.1, NONE fboot-licence-ja_JP.png, 1.1, NONE fboot-sound-ja_JP.png, 1.1, NONE fboot-time-ja_JP.png, 1.1, NONE fboot-user-ja_JP.png, 1.1, NONE fboot-welcome-ja_JP.png, 1.1, NONE firewall-ja_JP.png, 1.1, NONE ftp-setup-further-ja_JP.png, 1.1, NONE ftp-setup-ja_JP.png, 1.1, NONE inst-ipsetup-ja_JP.png, 1.1, NONE install-method-ja_JP.png, 1.1, NONE install-types-ja_JP.png, 1.1, NONE installing-inprogress-ja_JP.png, 1.1, NONE keyb-conf-ja_JP.png, 1.1, NONE net-config-dhcp-ja_JP.png, 1.1, NONE package-default-ja_JP.png, 1.1, NONE package-selection-details-ja_JP.png, 1.1, NONE package-selection-ja_JP.png, 1.1, NONE! partitioning-automatic-ja_JP.png, 1.1, NONE partitioning-setup-ja_JP.png, 1.1, NONE root-passwd-ja_JP.png, 1.1, NONE timezone-ja_JP.png, 1.1, NONE upgrade-bootloader-ja_JP.png, 1.1, NONE upgrade-examine-ja_JP.png, 1.1, NONE
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: sonarguy
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29808/en
Added Files:
Tag: FC5_SAG
fdp-info.xml 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 fedora-install-guide.xml
Log Message:
Removed language specific directories per the latest changes
--- NEW FILE fdp-info.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<!--
Warning! Warning! Danger, Will Robinson!
This is a generated file, produced from information in
the "rpm-info.xml" file.
DO NOT EDIT THIS FILE DIRECTLY!
Edit "rpm-info.xml" to change this information.
-->
<bookinfo>
<title>Fedora Core 5 Installation Guide - BETA</title>
<copyright>
<year>2005</year>
<holder>Red Hat, Inc.</holder>
<holder>Stuart Ellis</holder>
<holder>Paul W. Frields</holder>
</copyright>
<authorgroup></authorgroup>
<revhistory></revhistory>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="/home/sglaser/fedora-cvs/docs/install-guide/../docs-common/common/legalnotice-en.xml"/>
</bookinfo>
--- NEW FILE fedora-install-guide-abouttoinstall.xml ---
<!-- $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/about-to-install.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/about-to-install.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
About to install screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
Click <guilabel>Next</guilabel> to begin the installation.
</para>
<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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-acknowledgements.xml ---
<!-- $Id: -->
<chapter id="ch-acknowledgements">
<title>Acknowledgements</title>
<para>
Many useful comments and suggestions were provided by Rahul
Sundaram and the Anaconda team.
</para>
</chapter>
<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-adminoptions.xml ---
<!-- $Id: -->
<chapter id="ch-admin-options">
<title>Appendix: Management Options</title>
<para>
The &FED; installation system includes a range of options and
functions for administrators.
</para>
<section id="sn-bootoptions">
<title>Boot Options</title>
<para>
<remark role="FIXME">Many of the options listed here have NOT yet been tested.
</remark>
</para>
<para>
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></userinput>
</screen>
<section id="sn-mode-rescue">
<title>Booting Your Computer with Rescue Mode</title>
<para>
You may use the first installation disc to boot a command-line
Linux system, without installing &FED; on the computer. This
rescue system may access the drives on your computer. Rescue
mode enables you to use the utilities and functions of a running
system to modify or repair an installed system.
</para>
<para>
To load the rescue mode, 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.
</para>
</section>
<section id="sn-bootoptions-installer">
<title>Configuring the Installation System</title>
<para>
You may configure the installation system without affecting the
final &FED; system. The
<prompt>boot:</prompt>
prompt enables you to configure the following:
</para>
<itemizedlist>
<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>
<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 <option>text</option> mode,
enter:
</para>
<screen>
<userinput>linux text</userinput>
</screen>
<para>
To enable support for a serial console, enter
<option>serial</option> as an additional option.
</para>
<para>
Use the <option>askmethod</option> option to display additional
menus that enable you to specify the installation method 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.example.com/directory/</replaceable></option>
</para>
</entry>
</row>
<row>
<entry>
<para>
FTP Server
</para>
</entry>
<entry>
<para>
<option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option>
</para>
</entry>
</row>
<row>
<entry>
<para>
NFS Server
</para>
</entry>
<entry>
<para>
<option>method=<replaceable>nfs:server.example.com:/directory/</replaceable></option>
</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
By default, the installation system uses DHCP to obtain the
correct network settings. To manually configure one or more
network settings, specify the setting at the
<prompt>boot:</prompt>
prompt. You may set the <option>ip</option> address,
<option>netmask</option>, <option>gateway</option>, and
<option>dns</option> servers for the installation system.
</para>
<para>
This example configures all of the network settings for an
installation system that uses the IP address 192.168.1.10:
</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>
</section>
<section id="sn-remote-installation">
<title>Enabling Remote Access to the Installation System</title>
<para>
You may access the interface 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, you must use client software that supports
the VNC (Virtual Network Computing) display protocol.
</para>
<tip>
<title>Installing a VNC Client</title>
<para>
To install the <application>vncviewer</application> VNC client
on &FED;, use the package <filename>vnc</filename>.
</para>
</tip>
<para>
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
<systemitem>qwerty</systemitem>.
</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>
To run the <application>vncviewer</application> client, 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
<systemitem>computer.mydomain.com:1</systemitem>.
</para>
<para>
Alternatively, you may automatically connect the interface for
the installation system to an active VNC client, with the
<option>vncconnect</option> option. This requires the VNC client
to run in <emphasis>listening</emphasis> mode. The client system
must also allow connections on a known TCP port. By default, the
<application>vncviewer</application> utility listens on TCP port
<systemitem>5500</systemitem>.
</para>
<para>
To connect to a VNC client on the system
<systemitem
class="systemname">desktop.mydomain.com</systemitem>
on the port <systemitem>5500</systemitem>, you would 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>
<para>
On &FED; systems, use the <option>-listen</option> option to
start the <application>vncviewer</application> VNC client in
listening mode. In a terminal window, enter the command:
</para>
<screen>
<userinput>vncviewer -listen</userinput>
</screen>
<para>
To enable remote access to a text mode installation, use the
<option>telnet</option> option at the
<prompt>boot:</prompt>
prompt:
</para>
<screen>
<userinput>linux 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>
<para>
<remark role="FIXME">No password option for telnet ?
</remark>
</para>
</section>
<section id="sn-automating-installation">
<title>Automating the Installation with Kickstart</title>
<para>
A <firstterm>Kickstart</firstterm> file specifies settings for
an installation. To automate the installation process, use the
<option>ks</option> option to provide the name and location of a
Kickstart file:
</para>
<screen>
<userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
</screen>
<para>
You may use Kickstart files that are located on either removable
storage, or a hard drive, or on 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>
<tip>
<title>Kickstart File is Automatically Created</title>
<para>
The Kickstart file <filename>/root/anaconda-ks.cfg</filename>
contains the settings for your system. The &FED; installation
process automatically creates this file.
</para>
</tip>
<para>
To install an application to create and edit Kickstart files,
use the package <filename>system-config-kickstart</filename>. To
load this Kickstart file editor, choose <menuchoice>
<guimenu>Applications</guimenu> <guisubmenu>System
Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
Alternatively, you may edit Kickstart files with a text editor.
</para>
<para>
You may also write Web applications to generate Kickstart files.
To use a Web application to provide a Kickstart file, 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
may use these headers to identify the computer. For example,
this line sends a request with headers to the application
<wordasword>http://server.example.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>Hardware Compatibility Options</title>
<para>
By default, &FED; detects and configures all of the components
of your computer. To override the automatic hardware detection,
use 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 power management (ACPI)
</para>
</entry>
<entry>
<para>
<option>acpi=off</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 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>
</section>
<section id="sn-mode-expert">
<title>Installing &FC; with Expert Mode</title>
<para>
The <option>expert</option> mode enables you to run the
installation process with additional options for hardware
configuration.
</para>
<para>
To run the installation process in expert mode, enter:
</para>
<screen>
<userinput>linux expert</userinput>
</screen>
<para>
<remark role="FIXME">May need an explanation of driver disks.
</remark>
</para>
</section>
</section>
<section id="sn-memtest">
<title>Performing a Memory (RAM) Test</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 load the <command>memtest86</command> memory test utility,
enter <userinput>memtest86</userinput> at the
<prompt>boot:</prompt>
prompt. The utility immediately starts the first test. By default,
<command>memtest86</command> carries out a total of ten tests.
</para>
<para>
To halt testing and reboot your computer, enter
<keycap>Esc</keycap> at any time.
</para>
</section>
<section id="sn-consoles-installation">
<title>Accessing the Consoles</title>
<para>
In addition to the main interface, or
<firstterm>console</firstterm>, the installation process provides
three other consoles. The shell console enables you to access the
command-line of the installation system. The two other consoles
display events as the installation proceeds. You may find these
consoles useful for diagnosing errors in the installation process.
</para>
<para>
To switch between the consoles of installation process, press the
key combinations shown below:
</para>
<table id="tb-consoles">
<title>Installation Consoles</title>
<tgroup cols="2">
<colspec colnum="1" colname="Console"/>
<colspec colnum="2" colname="Key Combination"/>
<thead>
<row>
<entry>Console</entry>
<entry>Key Combination</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<para>
Main Console
</para>
</entry>
<entry>
<para>
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F7</keycap>
</keycombo>
</para>
</entry>
</row>
<row>
<entry>
<para>
Shell Console
</para>
</entry>
<entry>
<para>
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap>
</keycombo>
</para>
</entry>
</row>
<row>
<entry>
<para>
Main Log Console
</para>
</entry>
<entry>
<para>
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F3</keycap>
</keycombo>
</para>
</entry>
</row>
<row>
<entry>
<para>
Boot Log Console
</para>
</entry>
<entry>
<para>
<keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F4</keycap>
</keycombo>
</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id="sn-aborting-installation">
<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>
</section>
</chapter>
<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-beginninginstallation.xml ---
<!-- $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>
<section id="sn-begin-non-network-installation">
<title>Beginning Non-Network Installation Methods</title>
<para>
Insert Text about Beginning Non-Network Installation Methods.
</para>
<section id="sn-begin-cd-installation">
<title>Beginning CD Installation Method</title>
<para>
Insert text about Beginning CD Installation Method.
</para>
</section>
<section id="sn-begin-dvd-installation">
<title>Beginning DVD Installation Method</title>
<para>
Insert text about Beginning DVD Installation Method.
</para>
</section>
<section id="sn-begin-usb-installation">
<title>Beginning USB Installation Method</title>
<para>
Insert text about Beginning USB Installation Method.
</para>
</section>
<section id="sn-begin-hard-drive-installation">
<title>Beginning Hard Drive Installation Method</title>
<para>
Insert text about Beginning Hard Drive Installation Method.
</para>
</section>
</section>
<section id="sn-begin-network-installation">
<title>Beginning Network Installation Methods</title>
<para>
Insert Text about Beginning Network Installation Methods.
</para>
<section id="sn-begin-http-installation">
<title>Beginning HTTP Installation Method</title>
<para>
Insert text about Beginning HTTP Installation Method.
</para>
</section>
<section id="sn-begin-ftp-installation">
<title>Beginning FTP Installation Method</title>
<para>
Insert text about Beginning FTP Installation Method.
</para>
</section>
<section id="sn-begin-nfs-installation">
<title>Beginning NFS Installation Method</title>
<para>
Insert text about Beginning NFS Installation Method.
</para>
</section>
</section>
<!--
<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/boot.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/boot.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 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/media-test.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/media-test.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/mediacheck-result.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/mediacheck-result.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/mediacheck-next.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/mediacheck-next.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.
-->
<!--
</section>
<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/pxe-instmethod.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/pxe-instmethod.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-bootloader.xml ---
<!-- $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
<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 section 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-config.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-config.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 change or decline installation of a new boot
loader, select the <guibutton>Change boot loader</guibutton>
button. The dialog shown in
<xref linkend="fig-bootloader-change"/> allows you to avoid
installing or changing your existing boot loader settings.
</para>
<figure id="fig-bootloader-change">
<title>Change Boot Loader</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-change.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-change.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>Change boot loader dialog</phrase>
</textobject>
</mediaobject>
</figure>
<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>
</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/bootloader-others.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-others.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.
</para>
<para>
However, if there is a chance someone can get physical access to
the keyboard and monitor of your computer, that person can
reboot the system and access <application>GRUB</application>.
This is where a password is helpful.
</para>
</tip>
<para>
To set a boot password, select the <guibutton>Use a boot loader
password</guibutton> checkbox. 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/bootloader-password.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-password.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>
Tto keep your current boot loader in the <abbrev>MBR</abbrev>, use
the advanced settings to place <application>GRUB</application> in
the first sector of the partition holding the Linux root file
system.
</para>
<para>
You may also need the advanced options if your
<abbrev>BIOS</abbrev> enumerates your disk devices differently
than &FC; expects. On a few systems, &FC; may not configure the
disk drive geometry for large disks correctly because of a broken
<abbrev>BIOS</abbrev>. To work around this problem, mark the
<guibutton>Force LBA32</guibutton> checkbox.
</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> checkbox. 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 checkbox
described above has been selected.
</para>
</note>
<figure id="fig-bootloader-advanced">
<title>Advanced Boot Options</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-advanced.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/bootloader-advanced.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-diskpartitioning.xml ---
<!-- $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. On systems with more
than one hard drive you may also configure &FC; to operate several
drives as a group, or array, with RAID. Partitions and RAID arrays
are explained in <xref linkend="sn-partitioning-general"/>, and
<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>
<remark role="FIXME">Needs screenshot.
</remark>
</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
checkbox 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>Use free space on selected drives and create default layout</guilabel></term>
<listitem>
<para>
If the selected drives have capacity that has not been
assigned to a partition, this option installs &FC; into the
free space. This 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>
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. If you
are not sure what to choose, accept the default partition layout.
</para>
<para>
Data partitions have a <indexterm>
<primary>mount point</primary>
</indexterm> <firstterm>mount point</firstterm>. The mount point
indicates the 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>, will be on the
<filename>/usr/local</filename> partition. Any other files in
<filename>/usr/</filename>, such as
<filename>/usr/bin/foo</filename>, will be 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>
<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>
<systemitem
class="filesystem"><firstterm>ext3</firstterm></systemitem>
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>
<primary>logical volume</primary>
</indexterm> <firstterm>logical volumes</firstterm>. The logical
volumes function much like standard data partitions. They have a
file system type, such as
<systemitem
class="filesystem">ext3</systemitem>, and a mount
point.
</para>
<para>
An administrator may grow or shrink logical volumes without
destroying data, unlike standard disk partitions. If the
physical volumes in a volume group are on separate drives then
administrators may also spread a logical volume across multiple
disks and RAID arrays.
</para>
<note>
<title>LVM and the Default Partition Layout</title>
<para>
By default, the installation process creates partitions within
LVM volumes.
</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 be storing data on
the system, create a separate partition for the
<filename>/home</filename> directory within an LVM volume. 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 supports <indexterm>
<primary>RAID</primary>
</indexterm> <firstterm>RAID</firstterm> and <indexterm>
<primary>LVM</primary>
</indexterm> <firstterm>LVM</firstterm> to provide more extensible
and reliable data storage.
</para>
<figure id="fig-disk-setup">
<title>Disk Setup Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="figs/disk-setup.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="figs/disk-setup.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 will 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>
<systemitem
class="filesystem"><firstterm>vfat</firstterm></systemitem>
(<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 may
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. For example, if a volume group is made up
of two 5 GB LVM physical volume partitions, then it 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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-firstboot.xml ---
<!-- $Id: -->
<chapter id="ch-firstboot">
<title>First Boot</title>
<para>
The <application>Setup Agent</application> launches the first time
that you start a new &FC; system. Use <application>Setup
Agent</application> to configure the system for use before you log
in.
</para>
<figure id="fig-fboot-welcome">
<title>Welcome Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-welcome.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-welcome.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Welcome screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
Select <guibutton>Next</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 none is available, configure these options manually
after you log in.
</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-licence">
<title>License Agreement Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-licence.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-licence.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>Next</guibutton>.
</para>
</section>
<section id="sn-firstboot-firewall">
<title>Firewall</title>
<para>
The <indexterm>
<primary>firewall</primary>
</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
block incoming connections from other systems. You may make
changes on this screen to allow access to specific network
services on your &FED; system.
</para>
<para>
<remark role="FIXME">Needs screenshot.
</remark>
</para>
<para>
To enable access to services listed on this screen, click the
check box next to the service name. After installation is
complete, you can enable access to other services as well.
</para>
<para>
Avoid disabling the firewall. If you believe 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>
<para>
<remark role="FIXME">Needs screenshot.
</remark>
</para>
<para>
The <indexterm>
<primary>&SEL;</primary>
</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>Active</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>Active</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>
<para>
To adjust &SEL;, choose <guilabel>Modify SELinux Policy</guilabel>. To exempt a service from &SEL;, select the service from the list, and choose the <guilabel>Remove SELinux protection</guilabel> option.
</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>
</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/fboot-time.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-time.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/fboot-time-ntp.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-time-ntp.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 will synchronize with another server.
</para>
<para>
To use an additional time server, either select it from the
<guilabel>Server</guilabel> drop-down box, or type the DNS name in
the box, and select <guilabel>Add</guilabel>. To remove a server
or server pool from the list, select the name and click
<guilabel>Delete</guilabel>. The drop-down box already has two
listings as examples, which are servers provided by &RH;.
</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>
<figure id="fig-fboot-display">
<title>Display Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-display.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-display.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/fboot-display-monitor.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-display-monitor.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>
<tip>
<title>Resetting the display</title>
<para>
To reconfigure your system after the installation has completed, choose <menuchoice>
<guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu>
<guimenuitem>Display</guimenuitem> </menuchoice>.
</para>
</tip>
</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/fboot-user.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-user.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>.
<!-- Network authentication is explained
in a separate tutorial. [Remove this comment when the
aforementioned tutorial exists. - PWF.] -->
</para>
<para>
After you configure login services, select
<guibutton>Next</guibutton> to proceed.
</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/fboot-sound.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-sound.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Sound card screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
Click <guibutton>Play Test Sound</guibutton> to check the sound
card configuration. If the configuration is correct, &FC; plays a
sound sequence. If your sound card is identified, but you do not
hear the sound, check your speakers and try again.
</para>
<para>
<remark role="FIXME">Explain the option to <guilabel>Use only the hardware device</guilabel>
</remark>
</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>
&FC; will automatically attempt 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>
Click <guilabel>Next</guilabel> to proceed to the final screen.
</para>
<figure id="fig-fboot-finish">
<title>Finish Setup Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-finish.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/fboot-finish.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Finish setup screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
Click <guilabel>Next</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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-installingpackages.xml ---
<!-- $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/installing-inprogress.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/installing-inprogress.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-intro.xml ---
<!-- $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; Life-cycle</title>
<para>
&FC; is a rapidly evolving system which follows the latest
technical developments. &FC; may not be appropriate for use in
critical applications in your organization.
</para>
</caution>
<para>
This manual helps you to 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.
<!-- Automating the installation process and
configuring network installation servers will be described in
separate tutorials. [These tutorials will be added later. Until
they exist, do not reference them. - PWF.] -->
</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
<ulink
url="http://fedora.redhat.com/">&FP-URL;</ulink>. Refer to
<ulink
url="http://www.opensource.org/">http://www.opensource.org/</ulink>
and
<ulink
url="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</ulink>
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 versions of &FC; for PCs, and also for a range
of other machines that are based on different technologies. Each
version of &FC; is built for computers that are based on a
specific <firstterm>architecture</firstterm>. All 32-bit PCs are
based on the <firstterm>i386</firstterm> architecture. You may
also install versions of &FC; on computers that are based on
<firstterm>x86_64</firstterm>, and <firstterm>ppc</firstterm>
technology. The architectures are explained 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, and Xeon; VIA C3/C3-m and Eden/Eden-N; and AMD
Athlon, AthlonXP, Duron, AthlonMP, and Sempron
</para>
</listitem>
</varlistentry>
<!-- Re-Ordered the List for Logical Progression from most common to least common SAG -->
<varlistentry>
<term>x86_64</term>
<listitem>
<para>
64-bit AMD processors such as Athlon64, Turion64, Opteron;
and Intel 64-bit processors such as EM64T
</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>
</variablelist>
</section>
<section id="sn-before-begin">
<title>Before You Begin</title>
<para>
Before installing &FC; you will need access to the following
things:
</para>
<itemizedlist>
<listitem>
<para>
Boot or installation media
</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 the
version of &FC; which you are about to install. 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 can always be found at &FDPDOCS-URL;.
</para>
<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>DHCP</firstterm> (Dynamic Host Control
Protocol). 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-network-installation" /> 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>
<!--
Is it just me, or is this section really out of place? [PWF]
The original text reminded the reader to get the hostname and IP settings for a server before installing. Other types of installation are usually better with the default DHCP. [SE]
<section id="sn-installing-asaserver">
<title>Installing &FC; as a Server</title>
<para>
&FC; includes software for a complete range of network services.
To install a system with the most common network services,
select the <guilabel>Server</guilabel> installation type during
the installation. Refer to <xref
linkend="ch-installtypes"/> for more information. You may
also select individual software packages during installation, or
install them later.
</para>
</section>
-->
<!-- This section Removed to follow New Flow Chart Design SAG
<section id="sn-installing-networkinstallation">
<title>Installing from a Server or Website</title>
<para>
You may install &FC; using a <firstterm>mirror</firstterm>, a
website or network server that provide a copy of the necessary
files. To use a mirror you will need to know the following:
</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:
<ulink url="http://fedora.redhat.com/download/mirrors.html"/>
</para>
<para>
To determine the complete the directory path for the
installation files, add
<filename>/&FCLOCALVER;/<replaceable>architecture</replaceable>/os/</filename>
to the path shown on the webpage.
</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 a &FED; disc, 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.]
-->
<!-- This section Removed to follow New Flow Chart Design SAG
<caution>
<title>Consult Network Administrators</title>
<para>
If you are installing outside of your home, always consult the
administrators before installing a &FC; system on an existing
network. They can provide correct network and authentication
settings, and guidance on specific organizational policies and
requirements.
</para>
</caution>
</section>
</section>
-->
<!-- Inserted the sections from the new Flow Chart -->
<section id="sn-underastanding-about">
<title>Understanding What You Are About To Do</title>
<para>
You are downloading an entire operating system, and in most cases,
you are then going to install the operating system on your computer.
If you are connected to the Internet via a slow connection, like a
modem, then downloading &FC; will be an extremely
time-consuming process. The time it takes to download the installation
files for &FC; depends greatly upon your connection speed to the Internet.
For example, if you are downloading the installation disk images (called ISOs),
then each image file will weigh in at just under 650 MB. This means that with a
56K modem connection it will take approximately 27 hours to complete the download of
just one disk, and most installations require more than one.
</para>
<para>
If you are connected to the Internet via a slow connection it is recommended
that you look at the option of using purchased media as referenced in <xref
linkend="sn-purchased-media" />. Another option that is available is to contact your
local Linux Users Group (LUG), typically these groups are more than willing to provide
copies of &FC; for free or at a nominal cost.
</para>
<para>
For those of you that are lucky enough to have a high-speed broadband Internet connection
there are numerous other options. First there is the option to download the ISO images
directly from the Internet as referenced in <xref
linkend="sn-downloaded-media" />. Other methods include downloading a boot image and
installing &FC; directly from the Internet, however those methods and others will be
referenced in <xref linkend="sn-determining-install-method" />.
</para>
</section>
<section id="sn-determining-install-method">
<title>Determining Your Installation Method</title>
<para>
The first thing that needs to be discussed is determining you method of installation.
Many things may factor into this decision such as the type of Internet connection you
may have or to which you may have access. Another determining factor will be can you
prepare the media once once obtained. Another factor is which method is most efficient
for you the user.
</para>
<para>
If your Internet Connection is slow, unreliable, or you would like to perform a standard
installation the best method for you is one of the ones discussed in
<xref linkend="sn-non-network-installation" />. This section also discusses some advanced
installation methods like Hard Drive installation and USB installation. The common thing
between all of these installation methods is that you are installing from media that is
in your machine. None of the installation media resides on a Network or the Internet. The
disadvantage to this method of installation is that for each installation you will need that
media. You will also have to in the case of a CD installation swap each CD as the installer
completes is use. In the case of a DVD this is not applicable, however if you have numerous
machines to load it can still be a time consuming process.
</para>
<para>
Now for those of you that have a High-Speed Broadband Internet connection that is reliable,
there are some other options. Rather than being constrained by using you CD/DVD you can boot
a boot image and pull all the information directly from a Network or the Internet. The
advantage to utilizing this method of installation, is the times savings. First you do are
not required to download and burn the media to discs. Secondly it only requires a boot image
or ISO, that is much smaller in size than the ISOs required for a disc installation. And lastly
there is no need to switch out the media during the install a great time saving advantage
when there are numerous machines to load with &FC;. The disadvantage however, is that in
the case of installing from the Internet there is no method of recovery. If the install
fails due to an Internet connectivity issue or if for some reason the server
which is the source source of the installation media goes offline, the install will have
to be started again from scratch. For those of you that would prefer this method of installation
the information can be found in <xref linkend="sn-network-installation" />.
</para>
</section>
<section id="sn-non-network-installation">
<title>Non-Network Installation Methods</title>
<para>
Non-Network Installation Methods are methods that do not require a network
interface in order to complete the installation. These installations are
geared toward people that do not want to install &FC; from a network or
the Internet. Each of method Non-Network Installation is discussed in
detail below.
</para>
<section id="sn-cd-installation">
<title>CD Installation Method</title>
<para>
The CD Installation Method is a method by which the user installs &FC; utilizing CD Media
for the installation. The number of discs may vary based on the architecture of your system.
For the installation there will be typically Five CDs required to complete the installation.
The number of CDs actually utilized in the installation vary based on the
packages selected for installation. If you would like to install &FC;
utilizing this method proceed to
<xref linkend="sn-getting-media" />.
</para>
</section>
<section id="sn-dvd-installation">
<title>DVD Installation Method</title>
<para>
The DVD Installation Method is very similar to the CD installation method, the only
real difference is that instead of utilizing several CDs you only require One DVD. This
means that during the installation there is no swapping disks. If you would like to install
&FC; utilizing this method proceed to <xref linkend="sn-getting-media" />.
</para>
</section>
<section id="sn-usb-installation">
<title>USB Installation Method</title>
<para>
The USB Installation method like the DVD installation method does not require switching
discs, that is because the entire installation image is on the USB media. This media
can be a USB Memory Stick or a USB Disk Drive, it does however have one limitation.
The machine you plan on conducting the installation from must support booting from USB
devices. Not all machines support this and as such the user must check the BIOS of
the machine to verify that this is an feasible option. If you would like to install
&FC; utilizing this method proceed to <xref linkend="sn-getting-media" />.
</para>
</section>
<section id="sn-hard-drive-installation">
<title>Hard Drive Installation Method</title>
<para>
The Hard Drive Installation Method is a specialized method of
installation where the installation media exists on the hard drive
of the machine to be installed. You may install from a hard drive that contains the ISO image files for the &FC; discs. The
hard drive may be internal to the computer or attached by USB. The partition on the
hard drive holding the ISO files must be formatted with the ext2, ext3 or vfat
file system. In Fedora, vfat includes a range of file systems, such as FAT-16 and
FAT-32, found on most removable media. External hard drives usually contain vfat
(FAT-32) file systems. Some Microsoft Windows systems also use vfat file systems on
internal hard disk partitions.
</para>
<note>
<title>FAT-16, FAT-32, and vfat</title>
<para>
Before you begin installation from a hard drive, check the partition type to
ensure that Fedora can read it. To check a partition's file system under
Windows, use the Disk Management tool. To check a partition's file system under
Linux, use the fdisk 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 would like to install &FC; utilizing this method proceed to
<xref linkend="sn-getting-media" />.
</para>
</section>
</section>
<section id="sn-network-installation">
<title>Network Installation Methods</title>
<para>
Network Installation Methods are installations that require a network
interface. These installations are geared toward people that do not wish
to use CD/DVD media as the core media to install &FC;. These methods
typically cover installations from either the Internet or from a local
intra-net. These installation methods can be kicked off from various types
of media including CD, DVD, or USB but complete the core of the installation
by downloading the files either from the Internet or intra-net. Each
Network Installation Method is discussed in detail below.
</para>
<section id="sn-http-installation">
<title>HTTP Installation Method</title>
<para>
The HTTP Installation Method is an installation method that utilizes
the HTTP Protocol to complete the installation. A boot image is required
to start the installation but once started all the files are transfered
from an HTTP server. This server may be a public server on the Internet
or a private server on an intra-net. If you would like to install
&FC; utilizing this method proceed to
<xref linkend="sn-getting-media" />.
</para>
</section>
<section id="sn-ftp-installation">
<title>FTP Installation Method</title>
<para>
The FTP Installation Method is an installation method that utilizes
the FTP Protocol to complete the installation. A boot image is required
to start the installation but once started all the files are transfered
from an FTP server. This server may be a public server on the Internet
or a private server on an intra-net. If you would like to install
&FC; utilizing this method proceed to
<xref linkend="sn-getting-media" />.
</para>
</section>
<section id="sn-nfs-installation">
<title>NFS Installation Method</title>
<para>
The NFS Installation Method is a method that occurs typically on an
intra-net. A Network File Server is required to conduct this method
of installation. A boot image is required to start the installation but
once started all the files are transfered from an NFS server. This
server is typically a private server on an intra-net. If you would
like to install &FC; utilizing this method proceed to
<xref linkend="sn-getting-media" />.
</para>
</section>
</section>
<section id="sn-getting-media">
<title>Getting the Installation Media</title>
<para>
To install &FC; you must obtain the media for installation. For the most
part there are only two options, Download the media, or Purchase the media.
As implied for Downloaded media you must take the time to download the media
then prepare it for installation.
</para>
<para>
Now for those of you that only have dial-up or slow broadband you could download
the media, but as discussed in previous sections of this guide it may take a very
long time so your best option would be to purchase the media. There are
numerous sources available on the Internet for purchasing the &FC; installation
media. If you a user that is new to Linux or &FC; it is recommended that
you choose an option that includes a well written &FC; book with the
installation media.
</para>
<section id="sn-downloaded-media">
<title>Downloaded Media</title>
<para>
Downloaded media my be utilized for any of the installation methods discussed
in the previous sections of this installation guide. Those methods are
listed below along with the steps required to obtain the media necessary
complete the installation:
</para>
<important>
<title>Architecture-Specific Distributions</title>
<para>
To install &FC;, you must download the installation media that is
particular to your architecture.
</para>
</important>
<note>
<title>Download Client Limitation</title>
<para>
If you are using HTTP or FTP to download, some download clients
cannot handle the DVD image because it is larger than 4 gigabytes.
Please refer to the documentation of your download client for
details.
</para>
</note>
<orderedlist>
<listitem>
<para>Non-Network Installation Media</para>
<orderedlist>
<listitem>
<para>
<emphasis>CD Installation Media: </emphasis>Below is a list of the images
required for CD installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download">http://fedora.redhat.com/download/</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-cd-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>The following images will need to be
to complete a CD installation:
FC5-i386-disc1.iso, FC5-i386-disc2.iso, FC5-i386-disc3.iso,
FC5-i386-disc4.iso, FC5-i386-disc5.iso, FC5-i386-rescuecd,
and SHA1SUM.
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>The following images will need to be
to complete a CD installation:
FC5-x86_64-disc1.iso, FC5-x86_64-disc2.iso, FC5-x86_64-disc3.iso,
FC5-x86_64-disc4.iso, FC5-x86_64-disc5.iso, FC5-x86_64-rescuecd,
and SHA1SUM.
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media - </emphasis>The following images will need to be
to complete a CD installation:
FC5-ppc-disc1.iso, FC5-ppc-disc2.iso, FC5-ppc-disc3.iso,
FC5-ppc-disc4.iso, FC5-ppc-disc5.iso, FC5-ppc-rescuecd,
and SHA1SUM.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>DVD Installation Media: </emphasis>Below is a list of the images
required for the DVD installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-dvd-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>The following images will needed to complete
a DVD installation: FC5-i386-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-i386.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>The following images will needed to complete
a DVD installation: FC5-x86_64-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-x86_64.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>The following images will needed to complete
a DVD installation: FC5-ppc-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-ppc.torrent.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>USB Installation Media: </emphasis>Below is a list of the images
required for the USB installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-usb-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>The following images will needed to complete
a USB installation: FC5-i386-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-i386.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>The following images will needed to complete
a USB installation: FC5-x86_64-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-x86_64.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>The following images will needed to complete
a USB installation: FC5-ppc-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-ppc.torrent.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>Hard Drive Installation Media: </emphasis>Below is a list of the images
required for the Hard Drive installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-hard-drive-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>The following images will needed to complete
a Hard Drive installation: FC5-i386-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-i386.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>The following images will needed to complete
a Hard Drive installation: FC5-x86_64-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-x86_64.torrent.
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>The following images will needed to complete
a Hard Drive installation: FC5-ppc-DVD.iso and SHA1SUM, of if you are utilizing
bittorrent the image would be FC5-binary-ppc.torrent.
</para>
</listitem>
</orderedlist>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Network Installation Media</para>
<orderedlist>
<listitem>
<para>
<emphasis>HTTP Installation Media: </emphasis>Below is a list of the images
required for the HTTP installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/">http://fedora.redhat.com/download/</ulink>
or <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-http-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>FTP Installation Media: </emphasis>Below is a list of the images
required for the FTP installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/">http://fedora.redhat.com/download/</ulink>
or <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-ftp-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>NFS Installation Media: </emphasis>Below is a list of the images
required for the NFS installation method based on architecture. The images are
available at <ulink url="http://fedora.redhat.com/download/">http://fedora.redhat.com/download/</ulink>
or <ulink url="http://fedora.redhat.com/download/mirrors.html">http://fedora.redhat.com/download/mirrors.html</ulink>.
Alternatively, you can <ulink url="http://torrent.fedoraproject.org/">Join the Torrent</ulink>.
Once you have downloaded the images specific to your architecture proceed to
<xref linkend="sn-prep-nfs-installation-media" />.
</para>
<orderedlist>
<listitem>
<para>
<emphasis>i386 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/i386/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>x86_64 Media - </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/x86_64/os/images/
</para>
</listitem>
<listitem>
<para>
<emphasis>ppc Media- </emphasis>Depending on the method with which you boot for
your installation you will either need the boot.iso for booting from a CD, or you
will need the diskboot.img if you plan on booting from a USB device. Both
images are located in the following location at both the Fedora Servers or
the Mirror Servers: /pub/fedora/linux/core/5/ppc/os/images/
</para>
</listitem>
</orderedlist>
</listitem>
</orderedlist>
</listitem>
</orderedlist>
</section>
<section id="sn-purchased-media">
<title>Purchased Media</title>
<para>
Just because we are discussing purchased media, does not mean one needs to purchase
the media. It is just a reference that covers purchase or prepared media that you
the user does not need to download. The purchased media can come from numerous
sources, one option is your local Linux Users Group or LUG as they are known in
the community. A quick search on <ulink url="http://google.com">Google</ulink>
will usually reveal a multitude of groups. These groups typically are more than
willing to provide a set of &FC; disks at little or no cost. Another option
would be your local Book Store, several publishers produce books about the latest
release of &FC; that are very informative and typically includes installation
media as part of the purchase. These books are are well written and include loads
of information about the &FC; operating system. The ultimate choice of
which media you go is up to you the user and what you wish to do to get the Fedora
Core operating system.
</para>
</section>
</section>
<!-- End inserted text to follow New Flow Chart -->
<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>
<section id="sn-prep-non-network-installation-media">Methods
<title>Preparing Non-Network Installation Media</title>
<para>
Insert Text about Preparing Non-Network Installation Media.
</para>
<section id="sn-prep-cd-installation-media">
<title>Preparing CD Installation Media</title>
<para>
Insert text about Preparing CD Installation Media.
</para>
</section>
<section id="sn-prep-dvd-installation-media">
<title>Preparing DVD Installation Media</title>
<para>
Insert text about Preparing DVD Installation Media.
</para>
</section>
<section id="sn-prep-usb-installation-media">
<title>Preparing USB Installation Media</title>
<para>
Insert text about Preparing USB Installation Media.
</para>
</section>
<section id="sn-prep-hard-drive-installation-media">
<title>Preparing Hard Drive Installation Media</title>
<para>
Insert text about Preparing Hard Drive Installation Media.
</para>
</section>
</section>
<section id="sn-prep-network-installation-media">
<title>Preparing Network Installation Media</title>
<para>
Insert Text about Preparing Network Installation Media.
</para>
<section id="sn-prep-http-installation-media">
<title>Preparing HTTP Installation Media</title>
<para>
Insert text about Preparing HTTP Installation Media.
</para>
</section>
<section id="sn-prep-ftp-installation-media">
<title>Preparing FTP Installation Media</title>
<para>
Insert text about Preparing FTP Installation Media.
</para>
</section>
<section id="sn-prep-nfs-installation-media">
<title>Preparing NFS Installation Media</title>
<para>
Insert text about Preparing NFS Installation Media.
</para>
</section>
</section>
</section>
<!-- Removed to match the New Flow Chart
<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.
</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.
These files can be converted 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>
To convert an ISO file into a physical CD, use the option in
your CD-writing program that burns a CD image file to a CD. If
you copy the file itself to a CD instead, the disc will not boot
or work correctly. Refer to your CD writing program
documentation for instructions. If you are using Linux, use the
following command to burn a CD image file to a blank recordable
CD:
</para>
</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. To write an
image file to boot media with <command>dd</command> on a current
version of &FC;:
</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>
</step>
</procedure>
</section>
</section>
-->
</preface>
<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "preface")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-locale.xml ---
<!-- $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>
<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/lang-selection.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/lang-selection.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/keyb-conf.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/keyb-conf.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-networkconfig.xml ---
<!-- $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/net-config-dhcp.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/net-config-dhcp.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> checkbox, 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> checkbox
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 either the <application>Internet Configuration
Wizard</application> or <application>Network
Cnfiguration</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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-nextsteps.xml ---
<!-- $Id: -->
<chapter id="ch-next-steps">
<title>Your Next Steps</title>
<para>
&FC; 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 &FED; 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>Package Updater</primary>
</indexterm> <application>Package Updater</application>:
</para>
<orderedlist>
<listitem>
<para>
Choose <menuchoice><guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu> <guimenuitem>Package
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. If your system uses a
slow network connection the <application>Package
Updater</application> may require several seconds to download
the information for all of the updated packages.
</para>
</listitem>
<listitem>
<para>
Click <guibutton>Apply Updates</guibutton> to begin the update
process.
</para>
</listitem>
<listitem>
<para>
Restart any active programs or network services listed in the
update window. If the updates include a
<filename>kernel</filename> package, restart your system as
soon as possible to load the new kernel.
</para>
</listitem>
</orderedlist>
<para>
<remark role="FIXME">Check this procedure on test2</remark>
</para>
<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>
<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 remove security vulnerabilities.
</para>
</important>
</section>
<section id="sn-web-help">
<title>Finding Documentation on the Web</title>
<para>
Documentation for &FC; is available from the &FP; Website:
</para>
<para>
<ulink
url="http://fedora.redhat.com/docs/"/>
</para>
<para>
The Linux Documentation Project (LDP) produces books and
tutorials:
</para>
<para>
<ulink
url="http://www.tldp.org/"/>
</para>
<para>
For many parts of &FC;, you may find the &RHEL; documentation
useful:
</para>
<para>
<ulink
url="http://www.redhat.com/docs/manuals/enterprise/"/>
</para>
<para>
Many other organizations and individuals also provide tutorials
and HOWTOs for &FED; on their Websites. You can locate information
on any topic by using Google:
</para>
<para>
<ulink
url="http://www.google.com/linux/"/>
</para>
</section>
<section id="sn-community-help">
<title>Getting Community 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 Website for the official forums is:
</para>
<para>
<ulink
url="http://forums.fedoraforum.org/"/>
</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://fedora.redhat.com/participate/"/>
</para>
</section>
</chapter>
<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-other-instmethods.xml ---
<!-- $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/install-method.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/install-method.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 checkbox 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/inst-ipsetup.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/inst-ipsetup.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/ftp-setup.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/ftp-setup.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/ftp-setup-further.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/ftp-setup-further.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Non-anonymous FTP account dialog.
</phrase>
</textobject>
</mediaobject>
</figure>
</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/hdd-instmethod.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/hdd-instmethod.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-packageselection.xml ---
<!-- $Id: -->
<chapter id="ch-packageselection">
<title>Package Selection</title>
<warning>
<title>Obsolete</title>
<para>
&FC; &FCLOCALVER; will have a new package selection interface. This
has not been completed for test1. The content in this section will
be replaced after test2.
</para>
</warning>
<para>
&FED; uses the installation type to select a set of software
packages for your system. Refer to
<xref linkend="ch-installtypes"
/> for more information. You can
accept this default set of packages, or customize it to fit your
preferences. If you choose the <guilabel>Custom</guilabel>
installation type, &FED; displays the screen for <guilabel>Package
Group Selection</guilabel> automatically.
</para>
<tip>
<title>Changing Your Mind</title>
<para>
The installation type and packages that you select are not
permanent. After you boot your system, use the
<application>Package Management</application> tool to make
different software selections for your system. To run this tool,
from the main menu, select <menuchoice> <guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu> <guimenuitem>Add/Remove
Applications</guimenuitem> </menuchoice>.
</para>
</tip>
<section id="sn-defaultpackages">
<title>Package Installation Defaults</title>
<para>
A summary of the default package selection is displayed.
</para>
<figure id="fig-package-default">
<title>Package Installation Defaults Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-default.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-default.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Package installation defaults screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
To accept the default package selection, select <guilabel>Install
the default software packages</guilabel>. Select
<guilabel>Next</guilabel> to continue, and proceed to
<xref
linkend="ch-abouttoinstall" />.
</para>
<para>
To view or change the packages, select <guilabel>Customize
software packages to be installed</guilabel>. Select
<guilabel>Next</guilabel> to continue, and proceed to
<xref
linkend="sn-packagegroups" />.
</para>
</section>
<section id="sn-packagegroups">
<title>Package Group Selection</title>
<para>
&FC; divides included software into <indexterm>
<primary>package groups</primary>
</indexterm> <firstterm>package groups</firstterm> that make
software selection easier.
</para>
<figure id="fig-package-selection">
<title>Package Group Selection Screen</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-selection.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-selection.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Package group selection screen.
</phrase>
</textobject>
</mediaobject>
</figure>
<para>
The default groups for the chosen installation type are already
selected. Select or remove any group of packages as desired.
<emphasis>None</emphasis> of the packages from a group will be
installed unless the checkbox next to the group is selected.
</para>
<para>
To change which packages within a selected group will be
installed, select the <guilabel>Details</guilabel> link next to
the name of the group. &FC; automatically installs <guilabel>Base
Packages</guilabel> of a group if the group is selected. Change
the selection of <guilabel>Optional Packages</guilabel> by using
the checkbox next to the name of the individual package.
</para>
<para>
&FC; lists with each group the number of packages currently
selected for installation, and the total number of packages within
that group.
</para>
<figure id="fig-package-selection-details">
<title>Package Group Details Dialog</title>
<mediaobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-selection-details.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/package-selection-details.png" format="PNG"/>
</imageobject>
<textobject>
<phrase>
Package group details dialog.
</phrase>
</textobject>
</mediaobject>
</figure>
</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 packages for those
languages from the <guilabel>Language Support</guilabel> package
group.
</para>
<warning>
<title>Language Selection</title>
<para>
Select <emphasis>every</emphasis> language that you need for
your system. Adding support for a language after installation is
difficult, and not recommended.
</para>
</warning>
</section>
<!-- Removed due to everything install not being applicable to FC5 SAG
<section id="sn-extreme-packagegroups">
<title><guilabel>Everything</guilabel> or <guilabel>Minimal</guilabel>
Installations</title>
<para>
Two of the groups under the heading of
<guilabel>Miscellaneous</guilabel> are incompatible with the
others. If you select either of these groups, your other group
selections become invalid.
</para>
<para>
If you select <guilabel>Everything</guilabel>, &FC; installs
<emphasis>all</emphasis> of the packages provided. Although &FC;
installs many additional network services in this package group,
some are not enabled after installation. This option may be useful
for some testing and development purposes.
</para>
<caution>
<title>Storage Requirements</title>
<para>
The <guilabel>Everything</guilabel> installation fills
approximately 6.9Gb of free disk space, and temporarily requires
an additional 175Mb of disk space during the installation
process. Refer to the Release Notes for more information about
storage requirements.
</para>
</caution>
<para>
The <guilabel>Minimal</guilabel> package group provides only the
essential packages to create a bootable system. This package group
provides no graphical interface.
</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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-rootpassword.xml ---
<!-- $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 every Linux system is only limited by &SEL;. It is not
subject to any other normal account restrictions. As the system
owner or administrator, you may sometimes require unrestricted
access 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/root-passwd.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/root-passwd.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-techref.xml ---
<!-- $Id: -->
<chapter id="ch-techref">
<title>Appendix: Technical References</title>
<para>
This document provides a reference for using the &FED; installation
software, known as <command>anaconda</command>. To learn more about
<command>anaconda</command>, visit the project webpage:
<ulink url="http://www.fedoraproject.org/wiki/Anaconda"/>.
</para>
<para>
Both <command>anaconda</command> and &FED; systems use a common set
of software components. For detailed information on key
technologies, refer to the websites listed below:
</para>
<variablelist>
<varlistentry>
<term>Boot Loader</term>
<listitem>
<para>
By default, &FED; uses the <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>
&FED; 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>Graphics System</term>
<listitem>
<para>
Both the installation system and &FED; itself use the
<command>Xorg</command> suite to provide graphical displays.
Refer to <ulink url="http://www.x.org/"/> for more
information.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Remote Display</term>
<listitem>
<para>
&FC; and <command>anaconda</command> include VNC to provide
remote display capabilities. For more information about VNC,
refer to the documentation on the RealVNC website: <ulink url="http://www.realvnc.com/documentation/"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Firewall</term>
<listitem>
<para>
&FED; uses the <command>netfilter</command> framework. The
Netfilter project website provides documentation for
<command>netfilter</command>, and the
<command>iptables</command> administration facilities:
<ulink url="http://netfilter.org/documentation/index.html"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Access Control</term>
<listitem>
<para>
&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>Software Installation</term>
<listitem>
<para>
&FED; uses <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>
</variablelist>
</chapter>
<!--
Local variables:
mode: xml
sgml-parent-document:("fedora-install-guide-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-timezone.xml ---
<!-- $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, select the yellow dot that
represents the city nearest to your location. When you place the
arrow on a dot, &FED; displays the name of the city below the map.
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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide-upgrading.xml ---
<!-- $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-examine.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/upgrade-examine.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/upgrade-bootloader.eps" format="EPS"/>
</imageobject>
<imageobject>
<imagedata align="center" fileref="./figs/upgrade-bootloader.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-en.xml" "book" "chapter")
fill-column: 72
End:
-->
--- NEW FILE fedora-install-guide.xml ---
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM
"../../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY DOCNAME "fedora-install-guide">
<!ENTITY DOCLANG "en">
<!ENTITY DOCVERSION "1.1.1">
<!ENTITY DOCDATE "2006-01-04">
<!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "129911">
<!ENTITY FCLOCALVER "5">
<!ENTITY DOCLOCALVER "1.1"> <!-- what's this for again? -->
<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro.xml">
<!ENTITY BEGINNINGINSTALLATION SYSTEM "fedora-install-guide-beginninginstallation.xml">
<!-- Removed to follow New Flow Chart SAG
<!ENTITY OTHERINSTALLMETHODS SYSTEM "fedora-install-guide-other-instmethods.xml">
-->
<!ENTITY LOCALE SYSTEM "fedora-install-guide-locale.xml">
<!ENTITY UPGRADING SYSTEM "fedora-install-guide-upgrading.xml">
<!ENTITY DISKPARTITIONING SYSTEM "fedora-install-guide-diskpartitioning.xml">
<!ENTITY BOOTLOADER SYSTEM "fedora-install-guide-bootloader.xml">
<!ENTITY NETWORKCONFIG SYSTEM "fedora-install-guide-networkconfig.xml">
<!ENTITY TIMEZONE SYSTEM "fedora-install-guide-timezone.xml">
<!ENTITY ROOTPASSWORD SYSTEM "fedora-install-guide-rootpassword.xml">
<!ENTITY PACKAGESELECTION SYSTEM "fedora-install-guide-packageselection.xml">
<!ENTITY ABOUTTOINSTALL SYSTEM "fedora-install-guide-abouttoinstall.xml">
<!ENTITY INSTALLINGPACKAGES SYSTEM "fedora-install-guide-installingpackages.xml">
<!ENTITY FIRSTBOOT SYSTEM "fedora-install-guide-firstboot.xml">
<!ENTITY NEXTSTEPS SYSTEM "fedora-install-guide-nextsteps.xml">
<!ENTITY ADMINOPTIONS SYSTEM "fedora-install-guide-adminoptions.xml">
<!ENTITY TECHREF SYSTEM "fedora-install-guide-techref.xml">
<!ENTITY ACKNOWLEDGEMENTS SYSTEM "fedora-install-guide-acknowledgements.xml">
]>
<book id="book" lang="en">
<bookinfo>
<title>&FC; &FCLOCALVER; &IG; - BETA</title>
<!-- Remove DOCLOCALVER for release -->
<copyright>
<year>2005</year>
<holder>&FORMAL-RHI;</holder>
<holder>Stuart Ellis</holder>
<holder>Paul W. Frields</holder>
</copyright>
<authorgroup>
<author>
<surname>Ellis</surname>
<firstname>Stuart</firstname>
</author>
<author>
<surname>Frields</surname>
<firstname>Paul</firstname>
<othername role="mi">W.</othername>
</author>
</authorgroup>
<!-- &LEGALNOTICE;-->
<revhistory>
<revision>
<revnumber>0.6.2</revnumber>
<date>2005-04-30</date>
<authorinitials>StuartEllis</authorinitials>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
First commission to CVS, plus very minor parent file edits
</para>
</revdescription>
</revision>
<revision>
<revnumber>0.6.3</revnumber>
<date>2005-05-10</date>
<authorinitials>PaulWFrields</authorinitials>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Style editing, removed "nextsteps" from build
</para>
</revdescription>
</revision>
<revision>
<revnumber>0.7</revnumber>
<date>2005-05-15</date>
<authorinitials>StuartEllis</authorinitials>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
Additional style editing and indexing
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0rc1</revnumber>
<date>2005-06-08</date>
<authorinitials>KarstenWade</authorinitials>
<revdescription>
<para>
Publication edit and declaration of release candidate
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>2005-06-10</date>
<authorinitials>KarstenWade</authorinitials>
<revdescription>
<para>
Release version
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.1rc1</revnumber>
<date>2005-11-20</date>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
Reorganization of introductory material
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.2</revnumber>
<date>2005-11-25</date>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
Additional reorganization for clarity; information on
<filename>/home</filename> partition
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.3</revnumber>
<date>2005-12-04</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Reorganized to match anaconda screens.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.4</revnumber>
<date>2005-12-06</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Added material on updating the new installation.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.5</revnumber>
<date>2005-12-08</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Updated partitioning section.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.6</revnumber>
<date>2005-12-10</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Updated sections on installation methods.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.7</revnumber>
<date>2005-12-12</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Added Management Options section.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.8</revnumber>
<date>2005-12-14</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Added Technical References section.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.0.9</revnumber>
<date>2005-12-22</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Updated Management Options section.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.1</revnumber>
<date>2005-12-22</date>
<authorinitials>StuartEllis</authorinitials>
<revdescription>
<para>
Amended Management Options section.
</para>
</revdescription>
</revision>
<revision>
<revnumber>1.1.1</revnumber>
<date>2006-01-04</date>
<authorinitials>ScottGlaser</authorinitials>
<revdescription>
<para>
Edited Install Guide per RFE 173735 to include new flow.
</para>
</revdescription>
</revision>
</revhistory>
</bookinfo>
&INTRODUCTION;
&BEGINNINGINSTALLATION;
<!-- Removed to follow New Flow Chart SAG
&OTHERINSTALLMETHODS;
-->
&LOCALE;
&UPGRADING;
&DISKPARTITIONING;
&BOOTLOADER;
&NETWORKCONFIG;
&TIMEZONE;
&ROOTPASSWORD;
&PACKAGESELECTION;
&ABOUTTOINSTALL;
&INSTALLINGPACKAGES;
&FIRSTBOOT;
&NEXTSTEPS;
&ADMINOPTIONS;
&TECHREF;
&ACKNOWLEDGEMENTS;
<index id="generated-index">
</index>
</book>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
- Previous message (by thread): docs-common/bin fdp-functions,1.10,1.11
- Next message (by thread): install-guide/figs about-to-install-ja_JP.png, 1.1, NONE bootloader-advanced-ja_JP.png, 1.1, NONE bootloader-change-ja_JP.png, 1.1, NONE bootloader-config-ja_JP.png, 1.1, NONE bootloader-others-ja_JP.png, 1.1, NONE bootloader-password-ja_JP.png, 1.1, NONE disk-setup-ja_JP.png, 1.1, NONE fboot-cds-ja_JP.png, 1.1, NONE fboot-display-ja_JP.png, 1.1, NONE fboot-display-monitor-ja_JP.png, 1.1, NONE fboot-finish-ja_JP.png, 1.1, NONE fboot-licence-ja_JP.png, 1.1, NONE fboot-sound-ja_JP.png, 1.1, NONE fboot-time-ja_JP.png, 1.1, NONE fboot-user-ja_JP.png, 1.1, NONE fboot-welcome-ja_JP.png, 1.1, NONE firewall-ja_JP.png, 1.1, NONE ftp-setup-further-ja_JP.png, 1.1, NONE ftp-setup-ja_JP.png, 1.1, NONE inst-ipsetup-ja_JP.png, 1.1, NONE install-method-ja_JP.png, 1.1, NONE install-types-ja_JP.png, 1.1, NONE installing-inprogress-ja_JP.png, 1.1, NONE keyb-conf-ja_JP.png, 1.1, NONE net-config-dhcp-ja_JP.png, 1.1, NONE package-default-ja_JP.png, 1.1, NONE package-selection-details-ja_JP.png, 1.1, NONE package-selection-ja_JP.png, 1.1, NONE! partitioning-automatic-ja_JP.png, 1.1, NONE partitioning-setup-ja_JP.png, 1.1, NONE root-passwd-ja_JP.png, 1.1, NONE timezone-ja_JP.png, 1.1, NONE upgrade-bootloader-ja_JP.png, 1.1, NONE upgrade-examine-ja_JP.png, 1.1, NONE
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list