install-guide/en fedora-install-guide-adminoptions.xml, 1.7, 1.8 fedora-install-guide-diskpartitioning.xml, 1.8, 1.9 fedora-install-guide-intro.xml, 1.9, 1.10 fedora-install-guide-locale.xml, 1.7, 1.8 fedora-install-guide-nextsteps.xml, 1.6, 1.7 fedora-install-guide-other-instmethods.xml, 1.7, 1.8 fedora-install-guide-packageselection.xml, 1.7, 1.8 fedora-install-guide-techref.xml, 1.6, 1.7

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Fri Mar 3 02:43:48 UTC 2006


Author: elliss

Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15995/en

Modified Files:
	fedora-install-guide-adminoptions.xml 
	fedora-install-guide-diskpartitioning.xml 
	fedora-install-guide-intro.xml fedora-install-guide-locale.xml 
	fedora-install-guide-nextsteps.xml 
	fedora-install-guide-other-instmethods.xml 
	fedora-install-guide-packageselection.xml 
	fedora-install-guide-techref.xml 
Log Message:
- Removed Xen option from Task Selection.
- Broke out subsections in Boot Options.
- Added text to Disk Partitioning to address #170728.
- Added Storage section to Before You Begin. 




Index: fedora-install-guide-adminoptions.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-adminoptions.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-adminoptions.xml	2 Mar 2006 22:57:14 -0000	1.7
+++ fedora-install-guide-adminoptions.xml	3 Mar 2006 02:43:40 -0000	1.8
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -45,8 +46,10 @@
       Prompt</title>
 
     <para>
-      You can use the <prompt>boot:</prompt> prompt to specify a number
-      of settings for the installation system, including:
+      You can use the
+      <prompt>boot:</prompt>
+      prompt to specify a number of settings for the installation
+      system, including:
     </para>
 
     <itemizedlist>
@@ -278,9 +281,9 @@
       </note>
     </section>
   </section>
-  <section id="sn-remote-installation">
+  <section id="sn-remoteaccess-installation">
     <title>Enabling Remote Access to the Installation System</title>
-
+<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
     <para>
       You may access either graphical or text interfaces for the
       installation system from any other system. Access to a text mode
@@ -316,39 +319,42 @@
       running in <firstterm>listening mode</firstterm>.
     </para>
 
-    <para>
-      <indexterm>
-        <primary>VNC (Virtual Network Computing)</primary>
-        <secondary>enabling</secondary>
-      </indexterm>
-      To enable remote graphical access to the installation system,
-      enter two options at the prompt:
-    </para>
+    <section id="sn-remoteaccess-installation-vnc">
+      <title>Enabling Remote Access with VNC</title>
+
+      <para>
+        <indexterm>
+          <primary>VNC (Virtual Network Computing)</primary>
+          <secondary>enabling</secondary>
+        </indexterm>
+        To enable remote graphical access to the installation system,
+        enter two options at the prompt:
+      </para>
 <screen>
 <userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput>
 </screen>
-    <para>
-      The <option>vnc</option> option enables the VNC service. The
-      <option>vncpassword</option> option sets a password for remote
-      access. The example shown above sets the password as
-      <systemitem>qwerty</systemitem>.
-    </para>
+      <para>
+        The <option>vnc</option> option enables the VNC service. The
+        <option>vncpassword</option> option sets a password for remote
+        access. The example shown above sets the password as
+        <userinput>qwerty</userinput>.
+      </para>
 
-    <note>
-      <title>VNC Passwords</title>
+      <note>
+        <title>VNC Passwords</title>
+
+        <para>
+          The VNC password must be at least six characters long.
+        </para>
+      </note>
 
       <para>
-        The VNC password must be at least six characters long.
+        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>
-    </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.
@@ -356,105 +362,113 @@
 Starting graphical installation...
 Press <enter> for a shell]]></computeroutput>
 </screen>
-    <para>
-      You may then login to the installation system with a VNC client.
-      To run the <application>vncviewer</application> client on &FED;,
-      choose <menuchoice> <guimenu>Applications</guimenu>
-      <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC
-      Viewer</guimenuitem></menuchoice>, or type the command
-      <application>vncviewer</application> in a terminal window. Enter
-      the server and display number in the <guilabel>VNC
-      Server</guilabel> dialog. For the example above, the <guilabel>VNC
-      Server</guilabel> is
-      <systemitem>computer.mydomain.com:1</systemitem>.
-    </para>
+      <para>
+        You may then login to the installation system with a VNC client.
+        To run the <application>vncviewer</application> client on &FED;,
+        choose <menuchoice> <guimenu>Applications</guimenu>
+        <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC
+        Viewer</guimenuitem></menuchoice>, or type the command
+        <application>vncviewer</application> in a terminal window. Enter
+        the server and display number in the <guilabel>VNC
+        Server</guilabel> dialog. For the example above, the
+        <guilabel>VNC Server</guilabel> is
+        <userinput>computer.mydomain.com:1</userinput>.
+      </para>
+    </section>
 
-    <para>
-      To have the installation system automatically connect to a VNC
-      client, first start the client in
-      <indexterm>
-        <primary>VNC (Virtual Network Computing)</primary>
-        <secondary>listening mode</secondary>
-      </indexterm>
-      listening mode. On &FED; systems, use the <option>-listen</option>
-      option to run <application>vncviewer</application> as a listener.
-      In a terminal window, enter the command:
-    </para>
+    <section id="sn-remoteaccess-installation-vnclistener">
+      <title>Connecting the Installation System to a VNC Listener</title>
+
+      <para>
+        To have the installation system automatically connect to a VNC
+        client, first start the client in
+        <indexterm>
+          <primary>VNC (Virtual Network Computing)</primary>
+          <secondary>listening mode</secondary>
+        </indexterm>
+        listening mode. On &FED; systems, use the
+        <option>-listen</option> option to run
+        <application>vncviewer</application> as a listener. In a
+        terminal window, enter the command:
+      </para>
 <screen>
  <userinput>vncviewer -listen</userinput>
 </screen>
-    <note>
-      <title>Firewall Reconfiguration Required</title>
+      <note>
+        <title>Firewall Reconfiguration Required</title>
+
+        <para>
+          By default, the <application>vncviewer</application> utility
+          listens on TCP port 5500. To update the &FED; firewall
+          configuration to permit connections to this port from other
+          systems, choose <menuchoice> <guimenu>System</guimenu>
+          <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
+          Level and Firewall</guimenuitem> </menuchoice>, enter
+          <userinput>5500:tcp</userinput> in the <guilabel>Other
+          ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+        </para>
+      </note>
 
       <para>
-        By default, the <application>vncviewer</application> utility
-        listens on TCP port <systemitem>5500</systemitem>. To update the
-        &FED; firewall configuration to permit connections to this port
-        from other systems, choose <menuchoice>
-        <guimenu>System</guimenu>
-        <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
-        Level and Firewall</guimenuitem> </menuchoice>, enter
-        <userinput>5500:tcp</userinput> in the <guilabel>Other
-        ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+        Once the listening client is active, start the installation
+        system and set the VNC options at the
+        <prompt>boot:</prompt>
+        prompt. In addition to <option>vnc</option> and
+        <option>vncpassword</option> options, use the
+        <option>vncconnect</option> option to specify the name or IP
+        address of the system that has the listening client. To specify
+        the TCP port for the listener, add a colon and the port number
+        to the name of the system.
       </para>
-    </note>
 
-    <para>
-      Once the listening client is active, start the installation system
-      and set the VNC options at the
-      <prompt>boot:</prompt>
-      prompt. In addition to <option>vnc</option> and
-      <option>vncpassword</option> options, use the
-      <option>vncconnect</option> option to specify the name or IP
-      address of the system that has the listening client. To specify
-      the TCP port for the listener, add a colon and the port number to
-      the name of the system.
-    </para>
-
-    <para>
-      For example, to connect to a VNC client on the system
-      <systemitem
+      <para>
+        For example, to connect to a VNC client on the system
+        <systemitem
 	class="systemname">desktop.mydomain.com</systemitem>
-      on the port <systemitem>5500</systemitem>, enter the following at
-      the
-      <prompt>boot:</prompt>
-      prompt:
-    </para>
+        on the port 5500, enter the following at the
+        <prompt>boot:</prompt>
+        prompt:
+      </para>
 <screen>
 <userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
 </screen>
-    <para>
-      To enable remote access to a text mode installation, use the
-      <indexterm>
-        <primary>Telnet</primary>
-      </indexterm>
-      <option>telnet</option> option at the
-      <prompt>boot:</prompt>
-      prompt:
-    </para>
+    </section>
+
+    <section id="sn-telnet-installation">
+      <title>Enabling Remote Access with Telnet</title>
+
+      <para>
+        To enable remote access to a text mode installation, use the
+        <indexterm>
+          <primary>Telnet</primary>
+        </indexterm>
+        <option>telnet</option> option at the
+        <prompt>boot:</prompt>
+        prompt:
+      </para>
 <!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
 <screen>
 <userinput>linux text telnet</userinput>
 </screen>
-    <para>
-      You may then connect to the installation system with the
-      <command>telnet</command> utility. The <command>telnet</command>
-      command requires the name or IP address of the installation
-      system:
-    </para>
+      <para>
+        You may then connect to the installation system with the
+        <command>telnet</command> utility. The <command>telnet</command>
+        command requires the name or IP address of the installation
+        system:
+      </para>
 <screen>
 <userinput>telnet computer.mydomain.com</userinput>
 </screen>
-    <caution>
-      <title>Telnet Access Requires No Password</title>
+      <caution>
+        <title>Telnet Access Requires No Password</title>
 
-      <para>
-        To ensure the security of the installation process, only use the
-        <option>telnet</option> option to install systems on networks
-        with restricted access.
-      </para>
-    </caution>
-<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+        <para>
+          To ensure the security of the installation process, only use
+          the <option>telnet</option> option to install systems on
+          networks with restricted access.
+        </para>
+      </caution>
+    </section>
   </section>
   <section id="sn-remote-logging">
     <title>Logging to a Remote System During the Installation</title>
@@ -473,8 +487,7 @@
       To configure remote logging, add the <option>syslog</option>
       option. Specify the IP address of the logging system, and the UDP
       port number of the log service on that system. By default, syslog
-      services that accept remote messages listen on UDP port
-      <systemitem>514</systemitem>.
+      services that accept remote messages listen on UDP port 514.
     </para>
 
     <para>
@@ -488,64 +501,67 @@
 <screen>
 <userinput>linux syslog=<replaceable>192.168.1.20:514</replaceable></userinput>
 </screen>
-    <para>
-      &FED; uses <command>syslogd</command> to provide a syslog service.
-      The default configuration of <command>syslogd</command> rejects
-      messages from remote systems.
-    </para>
-
-    <caution>
-      <title>Only Enable Remote Syslog Access on Secured Networks</title>
+    <section id="sn-remote-logging-logserver">
+      <title>Configuring a Log Server</title>
 
       <para>
-        The <command>syslogd</command> service includes no security
-        measures. Crackers may slow or crash systems that permit access
-        to the logging service, by sending large quantities of false log
-        messages. In addition, hostile users may intercept or falsify
-        messages sent to the logging service over the network.
+        &FED; uses <command>syslogd</command> to provide a syslog
+        service. The default configuration of <command>syslogd</command>
+        rejects messages from remote systems.
       </para>
-    </caution>
 
-    <para>
-      To configure a &FED; system to accept log messages from other
-      systems on the network, edit the file
-      <filename>/etc/sysconfig/syslog</filename>.  You must use
-      <systemitem class="username">root</systemitem> privileges to edit
-      the file <filename>/etc/sysconfig/syslog</filename>.  Add the
-      option <option>-r</option> to the
-      <command>SYSLOGD_OPTIONS</command>:
-    </para>
+      <caution>
+        <title>Only Enable Remote Syslog Access on Secured Networks</title>
+
+        <para>
+          The <command>syslogd</command> service includes no security
+          measures. Crackers may slow or crash systems that permit
+          access to the logging service, by sending large quantities of
+          false log messages. In addition, hostile users may intercept
+          or falsify messages sent to the logging service over the
+          network.
+        </para>
+      </caution>
 
+      <para>
+        To configure a &FED; system to accept log messages from other
+        systems on the network, edit the file
+        <filename>/etc/sysconfig/syslog</filename>. You must use
+        <systemitem class="username">root</systemitem> privileges to
+        edit the file <filename>/etc/sysconfig/syslog</filename>. Add
+        the option <option>-r</option> to the
+        <command>SYSLOGD_OPTIONS</command>:
+      </para>
 <screen>
 <computeroutput>SYSLOGD_OPTIONS="-m 0 <userinput>-r</userinput>"</computeroutput>
 </screen>
-
-    <para>
-      Restart the <command>syslogd</command> service to apply the
-      change:
-    </para>
+      <para>
+        Restart the <command>syslogd</command> service to apply the
+        change:
+      </para>
 <screen>
 <userinput>su -c '/sbin/service syslog restart'</userinput>
 </screen>
-    <para>
-      Enter the <systemitem class="username">root</systemitem> password
-      when prompted.
-    </para>
-
-    <note>
-      <title>Firewall Reconfiguration Required</title>
-
       <para>
-        By default, the syslog service listens on UDP port
-        <systemitem>514</systemitem>. To update the &FED; firewall
-        configuration to permit connections to this port from other
-        systems, choose <menuchoice> <guimenu>System</guimenu>
-        <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
-        Level and Firewall</guimenuitem> </menuchoice>, enter
-        <userinput>514:udp</userinput> in the <guilabel>Other
-        ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+        Enter the <systemitem class="username">root</systemitem>
+        password when prompted.
       </para>
-    </note>
+
+      <note>
+        <title>Firewall Reconfiguration Required</title>
+
+        <para>
+          By default, the syslog service listens on UDP port 514. To
+          update the &FED; firewall configuration to permit connections
+          to this port from other systems, choose <menuchoice>
+          <guimenu>System</guimenu>
+          <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
+          Level and Firewall</guimenuitem> </menuchoice>, enter
+          <userinput>514:udp</userinput> in the <guilabel>Other
+          ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+        </para>
+      </note>
+    </section>
   </section>
   <section id="sn-automating-installation">
     <title>Automating the Installation with Kickstart</title>
@@ -557,8 +573,8 @@
       </indexterm>
       <firstterm>Kickstart</firstterm> file specifies settings for an
       installation. Once the installation system boots, it can read a
-      Kickstart file and carry out the installation process without
-      any further input from a user.
+      Kickstart file and carry out the installation process without any
+      further input from a user.
     </para>
     <tip>
       <title>Every Installation Produces a Kickstart File</title>
@@ -572,19 +588,18 @@
       </para>
     </tip>
     <para>
-      &FED; includes a graphical application to create
-      and modify Kickstart files by selecting the options you
-      require. Use the package
-      <filename>system-config-kickstart</filename> to install this
-      utility. To load the &FED; Kickstart editor, choose <menuchoice>
-      <guimenu>Applications</guimenu> <guisubmenu>System
+      &FED; includes a graphical application to create and modify
+      Kickstart files by selecting the options you require. Use the
+      package <filename>system-config-kickstart</filename> to install
+      this utility. To load the &FED; Kickstart editor, choose
+      <menuchoice> <guimenu>Applications</guimenu> <guisubmenu>System
       Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
     </para>
 
     <para>
       Kickstart files list installation settings in plain text, with one
-      option per line. This format lets you modify your Kickstart
-      files with any text editor, and write scripts or applications that
+      option per line. This format lets you modify your Kickstart files
+      with any text editor, and write scripts or applications that
       generate custom Kickstart files for your systems.
     </para>
 
@@ -1051,14 +1066,16 @@
           </tbody>
         </tgroup>
       </table>
+      <note>
+        <title>Additional Screen</title>
 
-<note>
-<title>Additional Screen</title>
-<para>
-  The <option>isa</option> option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer.
-</para>
-</note>
-
+        <para>
+          The <option>isa</option> option causes the system to display
+          an additional text screen at the beginning of the installation
+          process. Use this screen to configure the ISA devices on your
+          computer.
+        </para>
+      </note>
     </section>
   </section>
   <section id="sn-boot-modes">
@@ -1106,7 +1123,8 @@
         </indexterm>
         rescue disc or the first installation disc, without installing
         &FED; on the computer. This enables you to use the utilities and
-        functions of a running Linux system to modify or repair systems that are already installed on your computer.
+        functions of a running Linux system to modify or repair systems
+        that are already installed on your computer.
       </para>
 
       <para>


Index: fedora-install-guide-diskpartitioning.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-diskpartitioning.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-diskpartitioning.xml	2 Mar 2006 22:57:14 -0000	1.8
+++ fedora-install-guide-diskpartitioning.xml	3 Mar 2006 02:43:40 -0000	1.9
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -31,8 +32,9 @@
       </indexterm>
       <firstterm>RAID</firstterm> facilities enable a group, or array,
       of drives to act as a single device. Configure any RAID functions
-      provided by your mainboard, or attached controller cards, before
-      you install &FC;. Each active RAID array appears as one drive.
+      provided by the mainboard of your computer, or attached controller
+      cards, before you begin the installation process. Each active RAID
+      array appears as one drive within &FED;.
     </para>
   </important>
 <!-- SE: Note that this chapter uses the term "Linux software RAID" to differentiate RAID provided by the kernel from the functions of ATA RAID controllers, which are often also called "software RAID". Unfortunately. -->
@@ -168,7 +170,8 @@
     <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.
+      are not sure how best to configure the partitions for your
+      computer, accept the default partition layout.
     </para>
 
     <para>
@@ -249,7 +252,14 @@
       <link linkend="disk-druid-edit">Edit option</link>
       for more information.
     </para>
-
+    <tip>
+      <title>Leave Excess Capacity Unallocated</title>
+      <para>
+        Only assign storage capacity to partitions that you require
+        immediately. You may allocate free space at any time, to meet
+        needs as they arise.
+      </para>
+    </tip>
     <section id="sn-partitioning-types">
       <title>Partition Types</title>
 
@@ -330,6 +340,14 @@
         across the storage devices.
       </para>
 
+      <para>
+        You may lose data if you shrink a logical volume to a smaller
+        capacity than the data on the volume requires. For this reason,
+        create logical volumes to meet your current needs, and leave
+        excess storage capacity unallocated. You may safely grow logical
+        volumes to use unallocated space, as your needs dictate.
+      </para>
+
       <note>
         <title>LVM and the Default Partition Layout</title>
 
@@ -344,8 +362,8 @@
       <title>Creating a <filename>/home</filename> Partition</title>
 
       <para>
-        If you expect that you or other users will store data on
-        the system, create a separate partition for the
+        If you expect that you or other users will store data on the
+        system, create a separate partition for the
         <filename>/home</filename> directory within an LVM volume. With
         a separate <filename>/home</filename> partition, you may upgrade
         or reinstall &FC; without erasing user data files. LVM provides
@@ -723,9 +741,9 @@
           <para>
             You may not remove a physical volume from a volume group if
             doing so would leave insufficient space for that group's
-            logical volumes.  Take for example a volume group made up
-            of two 5 GB LVM physical volume partitions, which contains
-            an 8 GB logical volume. The installer would not allow you to
+            logical volumes. Take for example a volume group made up of
+            two 5 GB LVM physical volume partitions, which contains an 8
+            GB logical volume. The installer would not allow you to
             remove either of the component physical volumes, since that
             would leave only 5 GB in the group for an 8 GB logical
             volume. If you reduce the total size of any logical volumes


Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-intro.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-intro.xml	2 Mar 2006 22:57:14 -0000	1.9
+++ fedora-install-guide-intro.xml	3 Mar 2006 02:43:40 -0000	1.10
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -38,10 +39,6 @@
   <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;
@@ -51,17 +48,21 @@
 
     <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.
+      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>
@@ -165,18 +166,37 @@
       Release Notes are available at &FDPDOCS-URL;.
     </para>
 
+    <section id="sn-installing-storage-configurations">
+      <title>Storage</title>
+<!-- SE: There may also be additional considerations when installing on machines backed by a SAN. -->
+      <para>
+        A &FED; system requires a minimum of 700Mb storage for a
+        command-line system. Assign at least 3Gb for a desktop system
+        with the default applications. You may install multiple copies
+        of &FED; on the same computer.
+      </para>
+
+      <para>
+        Configure any RAID functions provided by the mainboard of your
+        computer, or attached controller cards, before you begin the
+        installation process. &FED; may automatically detect configured
+        RAID devices and use the storage that they provide.
+      </para>
+    </section>
+
     <section id="sn-installing-network-configurations">
       <title>Networking</title>
 
       <para>
         By default, &FC; systems attempt to discover correct connection
-        settings for the attached network using <indexterm>
-        <primary>DHCP (Dynamic Host Configuration Protocol)</primary>
-        </indexterm> <firstterm>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.
+        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>
@@ -199,34 +219,13 @@
         </para>
       </note>
     </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>
 
--->
     <section id="sn-installing-networkinstallation">
-      <title>Installing from a Server or Website</title>
+      <title>Installing from a Server or Web Site</title>
 
       <para>
         You may install &FC; using a <firstterm>mirror</firstterm>, a
-        website or network server that provide a copy of the necessary
+        Web site or network server that provide a copy of the necessary
         files. To use a mirror, you need to know:
       </para>
 
@@ -356,9 +355,10 @@
     </para>
 
     <para>
-      For instructions to download and prepare this CD or DVD installation media, refer
-      to <ulink url="http://fedora.redhat.com/download/"/>. If you
-      already have the full set of &FC; installation media, skip to
+      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>
@@ -367,18 +367,18 @@
       <title>Architecture-Specific Distributions</title>
 
       <para>
-        To install &FC;, you must use the boot and installation media that is
-        particular to your architecture.
+        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.
+      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>


Index: fedora-install-guide-locale.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-locale.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-locale.xml	2 Mar 2006 22:57:14 -0000	1.7
+++ fedora-install-guide-locale.xml	3 Mar 2006 02:43:40 -0000	1.8
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -11,25 +12,24 @@
 ]>
 
 <!-- $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
+    graphical interface. The text screens provide the same functions as
+    the standard screens. Later in the installation process you can
     manually specify your display hardware.
   </para>
-
   <important>
-   <title>Network Installations</title>
+    <title>Network Installations</title>
+
     <para>
       Network installations with HTTP and FTP always use text screens on
       systems with less than 128Mb of memory.
     </para>
   </important>
-
   <section id="sn-installer-language">
     <title>Language Selection</title>
 
@@ -37,41 +37,37 @@
       The installation program displays a list of languages supported by
       &FED;.
     </para>
-
     <figure id="fig-lang-selection">
       <title>Language Selection Screen</title>
       <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/langselection.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/langselection.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
+        <imageobject>
+          <imagedata align="center" fileref="./figs/langselection.eps" format="EPS"/>
+        </imageobject>
+        <imageobject>
+          <imagedata align="center" fileref="./figs/langselection.png" format="PNG"/>
+        </imageobject>
+        <textobject>
+          <phrase>
 	    Language selection screen.
 	  </phrase>
-	</textobject>
+        </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>
+      <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>.
+        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>
 
@@ -79,31 +75,27 @@
       The installation program display a list of the keyboard layouts
       supported by &FED;:
     </para>
-      
     <figure id="fig-keyb-conf">
       <title>Keyboard Configuration Screen</title>
       <mediaobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/keylayoutselection.eps" format="EPS"/>
-	</imageobject>
-	<imageobject>
-	  <imagedata align="center" fileref="./figs/keylayoutselection.png" format="PNG"/>
-	</imageobject>
-	<textobject>
-	  <phrase>
+        <imageobject>
+          <imagedata align="center" fileref="./figs/keylayoutselection.eps" format="EPS"/>
+        </imageobject>
+        <imageobject>
+          <imagedata align="center" fileref="./figs/keylayoutselection.png" format="PNG"/>
+        </imageobject>
+        <textobject>
+          <phrase>
 	    Keyboard configuration screen.
 	  </phrase>
-	</textobject>
+        </textobject>
       </mediaobject>
     </figure>
-
     <para>
       Highlight the correct layout on the list, and select
       <guibutton>Next</guibutton>.
     </para>
-
   </section>
-
 </chapter>
 
 <!--


Index: fedora-install-guide-nextsteps.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-nextsteps.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-nextsteps.xml	2 Mar 2006 22:57:14 -0000	1.6
+++ fedora-install-guide-nextsteps.xml	3 Mar 2006 02:43:40 -0000	1.7
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -160,11 +161,12 @@
 
     <para>
       Members of the &FED; community provides support through mailing
-      lists, web forums and Linux User Groups (LUGs) across the world.
+      lists, Web forums and Linux User Groups (LUGs) across the world.
     </para>
 
     <para>
-      The Website for the official forums is <ulink
+      The Web site for the official forums is
+      <ulink
 	url="http://forums.fedoraforum.org/"/>.
     </para>
 
@@ -175,70 +177,70 @@
 
     <itemizedlist>
       <listitem>
-	<variablelist>
-	  <varlistentry>
-	    <term>
+        <variablelist>
+          <varlistentry>
+            <term>
 	      The FAQ on the &FP; website
 	    </term>
-	    <listitem>
-	      <para>
-		<ulink url="http://fedoraproject.org/wiki/FAQ/"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+            <listitem>
+              <para>
+                <ulink url="http://fedoraproject.org/wiki/FAQ/"/>
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
       </listitem>
       <listitem>
-	<variablelist>
-	  <varlistentry>
-	    <term>
-	      The documents available from the &FDP; website 
+        <variablelist>
+          <varlistentry>
+            <term>
+	      The documents available from the &FDP; Web site 
 	    </term>
-	    <listitem>
-	      <para>
-		<ulink url="http://fedora.redhat.com/docs/"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+            <listitem>
+              <para>
+                <ulink url="http://fedora.redhat.com/docs/"/>
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
       </listitem>
       <listitem>
-	<variablelist>
-	  <varlistentry>
-	    <term>
+        <variablelist>
+          <varlistentry>
+            <term>
 	      The Linux Documentation Project (LDP)	   
 	    </term>
-	    <listitem>
-	      <para>
-		<ulink url="http://www.tldp.org/"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+            <listitem>
+              <para>
+                <ulink url="http://www.tldp.org/"/>
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
       </listitem>
       <listitem>
-	<variablelist>
-	  <varlistentry>
-	    <term>
+        <variablelist>
+          <varlistentry>
+            <term>
 	      The &RHEL; documentation, much of which also applies to
 	      &FED;
 	    </term>
-	    <listitem>
-	      <para>
-		<ulink
+            <listitem>
+              <para>
+                <ulink
 		  url="http://www.redhat.com/docs/manuals/enterprise/"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+              </para>
+            </listitem>
+          </varlistentry>
+        </variablelist>
       </listitem>
     </itemizedlist>
 
     <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's Linux search site, located at
-      <ulink url="http://www.google.com/linux/"/>.
+      and HOWTOs for &FED; on their Web sites. You can locate
+      information on any topic by using Google's Linux search site,
+      located at <ulink url="http://www.google.com/linux/"/>.
     </para>
   </section>
   <section id="sn-community">


Index: fedora-install-guide-other-instmethods.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-other-instmethods.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-other-instmethods.xml	2 Mar 2006 22:57:14 -0000	1.7
+++ fedora-install-guide-other-instmethods.xml	3 Mar 2006 02:43:40 -0000	1.8
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -69,9 +70,10 @@
     <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
+        <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>
@@ -159,15 +161,16 @@
           </textobject>
         </mediaobject>
       </figure>
+      <note>
+        <title>Large Download</title>
 
-  <note>
-    <title>Large Download</title>
-
-    <para>
-      Network installations download the main installation program from the server that you specify. The graphical installation program is over 60 Mb in size. Computers with a slow network connection may take several minutes to download this file. 
-    </para>
-  </note>
-
+        <para>
+          Network installations download the main installation program
+          from the server that you specify. The graphical installation
+          program is over 60 Mb in size. Computers with a slow network
+          connection may take several minutes to download this file.
+        </para>
+      </note>
     </section>
   </section>
   <section id="sn-installing-from-harddrive">
@@ -184,25 +187,34 @@
 
     <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;,
+      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


Index: fedora-install-guide-packageselection.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-packageselection.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-packageselection.xml	2 Mar 2006 22:57:14 -0000	1.7
+++ fedora-install-guide-packageselection.xml	3 Mar 2006 02:43:40 -0000	1.8
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -43,7 +44,9 @@
       <term>Office and Productivity</term>
       <listitem>
         <para>
-          This option provides the OpenOffice.org productivity suite.
+          This option provides the OpenOffice.org productivity suite,
+          the Planner project management application, graphical tools
+          such as the GIMP, and multimedia applications.
         </para>
       </listitem>
     </varlistentry>
@@ -66,16 +69,6 @@
         </para>
       </listitem>
     </varlistentry>
-
-    <varlistentry>
-      <term>Virtualization (Xen)</term>
-      <listitem>
-        <para>
-          This option provides the services and utilities to simultaneously run multiple operating systems on your computer.
-        </para>
-      </listitem>
-    </varlistentry>
-
   </variablelist>
   <para>
     Select <guilabel>Customize now</guilabel> to specify the software
@@ -148,11 +141,16 @@
       Some automated processes on your Fedora system use the email
       service to send reports and messages to the system administrator.
       By default, the email, logging, and printing services do not
-      accept connections from other systems. &FED; installs the NFS sharing and VNC components without enabling those services.
+      accept connections from other systems. &FED; installs the NFS
+      sharing and VNC components without enabling those services.
     </para>
 
-<para>
-  You may configure your Fedora system after installation to offer email, file sharing, logging, printing and remote desktop access services. The SSH service is enabled by default. You may use NFS to access files on other systems without enabling the NFS sharing service.
+    <para>
+      You may configure your Fedora system after installation to offer
+      email, file sharing, logging, printing and remote desktop access
+      services. The SSH service is enabled by default. You may use NFS
+      to access files on other systems without enabling the NFS sharing
+      service.
     </para>
   </section>
   <section id="sn-package-selection">


Index: fedora-install-guide-techref.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-techref.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-techref.xml	2 Mar 2006 22:57:14 -0000	1.6
+++ fedora-install-guide-techref.xml	3 Mar 2006 02:43:40 -0000	1.7
@@ -1,4 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
 
@@ -20,13 +21,13 @@
     <indexterm>
       <primary>Anaconda</primary>
     </indexterm>
-    <command>anaconda</command>, visit the project webpage:
+    <command>anaconda</command>, visit the project Web page:
     <ulink url="http://www.fedoraproject.org/wiki/Anaconda"/>.
   </para>
   <para>
     Both <command>anaconda</command> and &FC; systems use a common set
     of software components. For detailed information on key
-    technologies, refer to the websites listed below:
+    technologies, refer to the Web sites listed below:
   </para>
   <variablelist>
     <varlistentry>
@@ -64,8 +65,10 @@
             <primary>LVM</primary>
             <secondary>documentation</secondary>
           </indexterm>
-Logical Volume Management (LVM) provides administrators with a range of facilities to manage storage. By default, the &FED; installation process formats drives as LVM volumes. Refer
-          to <ulink url="http://www.tldp.org/HOWTO/LVM-HOWTO/"/> for more
+          Logical Volume Management (LVM) provides administrators with a
+          range of facilities to manage storage. By default, the &FED;
+          installation process formats drives as LVM volumes. Refer to
+          <ulink url="http://www.tldp.org/HOWTO/LVM-HOWTO/"/> for more
           information.
         </para>
       </listitem>
@@ -81,7 +84,7 @@
           Linux Sound Architecture)</primary>
           </indexterm>
           ALSA (Advanced Linux Sound Architecture). For more information
-          about ALSA, refer to the project website:
+          about ALSA, refer to the project Web site:
           <ulink url="http://www.alsa-project.org/"/>.
         </para>
       </listitem>
@@ -115,7 +118,7 @@
           </indexterm>
           VNC (Virtual Network Computing) software to enable remote
           access to graphical displays. For more information about VNC,
-          refer to the documentation on the RealVNC website:
+          refer to the documentation on the RealVNC Web site:
           <ulink url="http://www.realvnc.com/documentation/"/>.
         </para>
       </listitem>
@@ -125,8 +128,8 @@
       <term>Command-line Interface</term>
       <listitem>
         <para>
-          By default, &FC; uses the GNU <command>bash</command> shell
-          to provide a command-line interface. The GNU Core Utilities
+          By default, &FC; uses the GNU <command>bash</command> shell to
+          provide a command-line interface. The GNU Core Utilities
           complete the command-line environment. Refer to
           <ulink url="http://www.gnu.org/software/bash/bash.html"/> for
           more information on <command>bash</command>. To learn more
@@ -159,7 +162,7 @@
             <seealso>SSH</seealso>
           </indexterm>
           feature of OpenSSH to transfer crash reports to remote
-          systems. Refer to the OpenSSH website for more information:
+          systems. Refer to the OpenSSH Web site for more information:
           <ulink url="http://www.openssh.com/"/>.
         </para>
       </listitem>
@@ -224,9 +227,13 @@
             <primary>Xen</primary>
             <secondary>documentation</secondary>
           </indexterm>
-          Xen provides the capability to simultaneously run multiple operating systems on the same computer. &FC; also includes tools to install and manage the secondary systems on a &FED; host. You may select Xen support during the installation process, or at any time thereafter. Refer to
-          <ulink url="http://www.fedoraproject.org/wiki/Tools/Xen"/> for more
-          information.
+          Xen provides the capability to simultaneously run multiple
+          operating systems on the same computer. &FC; also includes
+          tools to install and manage the secondary systems on a &FED;
+          host. You may select Xen support during the installation
+          process, or at any time thereafter. Refer to
+          <ulink url="http://www.fedoraproject.org/wiki/Tools/Xen"/> for
+          more information.
         </para>
       </listitem>
     </varlistentry>




More information about the docs-commits mailing list