install-guide fedora-install-guide-adminoptions-en.xml, 1.6, 1.7 fedora-install-guide-en.xml, 1.38, 1.39 fedora-install-guide-firstboot-en.xml, 1.16, 1.17 fedora-install-guide-nextsteps-en.xml, 1.10, 1.11 fedora-install-guide-techref-en.xml, 1.4, 1.5 fedora-install-guide-timezone-en.xml, 1.10, 1.11 rpm-info.xml, 1.3, 1.4

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Mon Jan 23 23:24:17 UTC 2006


Author: elliss

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

Modified Files:
	fedora-install-guide-adminoptions-en.xml 
	fedora-install-guide-en.xml 
	fedora-install-guide-firstboot-en.xml 
	fedora-install-guide-nextsteps-en.xml 
	fedora-install-guide-techref-en.xml 
	fedora-install-guide-timezone-en.xml rpm-info.xml 
Log Message:
- Amended Timezone section for new city selector map.
- Added text on soundcard options to First Boot section.
- Added SSH note and information on opening additional firewall ports to First Boot section.
- Revised notes on procedure for software update.
- Merged Documentation and Community support sections in Next Steps.  
- Restructured Management Options section.
- Added more to Technical Reference section.




Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-adminoptions-en.xml	16 Jan 2006 00:23:00 -0000	1.6
+++ fedora-install-guide-adminoptions-en.xml	23 Jan 2006 23:24:09 -0000	1.7
@@ -1,289 +1,254 @@
 <!-- $Id: -->
 
 <chapter id="ch-admin-options">
-  <title>Appendix: Management Options</title>
+  <title>Appendix: Boot Options</title>
   <para>
     The &FED; installation system includes a range of options and
-    functions for administrators.
+    functions for administrators. To use boot options, enter
+    <userinput>linux <replaceable>option</replaceable></userinput> at
+    the
+    <prompt>boot:</prompt>
+    prompt.
   </para>
-  <section id="sn-bootoptions">
-    <title>Boot Options</title>
+  <para>
+    If you specify more than one option, separate each of the options by
+    a single space. For example:
+  </para>
+<screen>
+<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput>
+</screen>
+  <section id="sn-bootoptions-installer">
+    <title>Configuring the Installation System</title>
 
     <para>
-      To use boot options, enter <userinput>linux
-      <replaceable>option</replaceable></userinput> at the
+      You may configure the installation system without affecting the
+      final &FED; system. The
       <prompt>boot:</prompt>
-      prompt.
+      prompt enables you to specify a number of settings for the
+      installation system. These include:
     </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>
+<!-- SE: May want to add the lang=language_code option to this section as well. -->
     <para>
-      If you specify more than one option, separate each of the options
-      by a single space. For example:
+      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 <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</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>
-
-      <para>
-        <remark role="FIXME">Add a note that the boot and rescue CDs also have this facility. 
-      </remark>
-      </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 specify a number of settings for the
-        installation system. These include:
-      </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>
-<!-- SE: May want to add the lang=language_code option to this section as well. -->
-      <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>
+    <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>
+      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>
+      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>
+      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>
+<entry>
                 <para>
                   <option>method=<replaceable>cdrom</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   Hard Drive
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>method=<replaceable>hd://device/</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   HTTP Server
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>method=<replaceable>http://server.example.com/directory/</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   FTP Server
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   NFS Server
                 </para>
               </entry>
-              <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 automatically
-        obtain the correct network settings. To manually configure the
-        network settings yourself, either enter them in the
-        <guilabel>Configure TCP/IP</guilabel> screen, or at the
-        <prompt>boot:</prompt>
-        prompt. You may specify the <option>ip</option> address,
-        <option>netmask</option>, <option>gateway</option>, and
-        <option>dns</option> server settings for the installation system
-        at the prompt. If you specify the network configuration at the
-        <prompt>boot:</prompt>
-        prompt, these settings are used for the installation process,
-        and the <guilabel>Configure TCP/IP</guilabel> screen does not
-        appear.
-      </para>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+    <para>
+      By default, the installation system uses DHCP to automatically
+      obtain the correct network settings. To manually configure the
+      network settings yourself, either enter them in the
+      <guilabel>Configure TCP/IP</guilabel> screen, or at the
+      <prompt>boot:</prompt>
+      prompt. You may specify the <option>ip</option> address,
+      <option>netmask</option>, <option>gateway</option>, and
+      <option>dns</option> server settings for the installation system
+      at the prompt. If you specify the network configuration at the
+      <prompt>boot:</prompt>
+      prompt, these settings are used for the installation process, and
+      the <guilabel>Configure TCP/IP</guilabel> screen does not appear.
+    </para>
 
-      <para>
-        This example configures the network settings for an installation
-        system that uses the IP address 192.168.1.10:
-      </para>
+    <para>
+      This example configures the network settings for an installation
+      system that uses the IP address
+      <systemitem class="ipaddress">192.168.1.10</systemitem>:
+    </para>
 <screen>
 <userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput>
 </screen>
-    </section>
-
-    <section id="sn-remote-installation">
-      <title>Enabling Remote Access to the Installation System</title>
+  </section>
+  <section id="sn-remote-installation">
+    <title>Enabling Remote Access to the Installation System</title>
 <!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+    <para>
+      You may access either graphical or text interfaces for the
+      installation system from any other system. Access to a text mode
+      display requires <command>telnet</command>, which is installed by
+      default on &FED; systems. To remotely access the graphical display
+      of an installation system, use client software that supports the
+      VNC (Virtual Network Computing) display protocol. A number of
+      providers offer VNC clients for Microsoft Windows and Mac OS, as
+      well as UNIX-based systems.
+    </para>
+    <tip>
+      <title>Installing a VNC Client on &FED;</title>
       <para>
-        You may access either graphical or text interfaces for the
-        installation system from any other system. Access to a text mode
-        display requires <command>telnet</command>, which is installed
-        by default on &FED; systems. To remotely access the graphical
-        display of an installation system, use client software that
-        supports the VNC (Virtual Network Computing) display protocol. A
-        number of providers offer VNC clients for Microsoft Windows and
-        Mac OS, as well as UNIX-based systems.
-      </para>
-      <tip>
-        <title>Installing a VNC Client on &FED;</title>
-        <para>
-          &FED; includes <application>vncviewer</application>, the
-          client provided by the developers of VNC. To obtain
-          <application>vncviewer</application>, install the
-          <filename>vnc</filename> package.
-        </para>
-      </tip>
-      <para>
-        The installation system supports two types of VNC connection.
-        You may either start the installation and manually login to the
-        graphical display with a VNC client on another system, or
-        configure the installation system to automatically connect to a
-        VNC client on the network that is running in
-        <emphasis>listening</emphasis> mode.
+        &FED; includes <application>vncviewer</application>, the client
+        provided by the developers of VNC. To obtain
+        <application>vncviewer</application>, install the
+        <filename>vnc</filename> package.
       </para>
+    </tip>
+    <para>
+      The installation system supports two types of VNC connection. You
+      may either start the installation and manually login to the
+      graphical display with a VNC client on another system, or
+      configure the installation system to automatically connect to a
+      VNC client on the network that is running in
+      <emphasis>listening</emphasis> mode.
+    </para>
 
-      <para>
-        To enable remote graphical access to the installation system,
-        enter two options at the prompt:
-      </para>
+    <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 <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 VNC password must be at least six characters long.
-        </para>
-      </note>
+    <note>
+      <title>VNC Passwords</title>
 
       <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:
+        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.
@@ -291,581 +256,646 @@
 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
+      <systemitem>computer.mydomain.com:1</systemitem>.
+    </para>
 
-      <para>
-        To have the installation system automatically connect to a VNC
-        client, first start the client in 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>
+    <para>
+      To have the installation system automatically connect to a VNC
+      client, first start the client in listening mode. On &FED;
+      systems, use the <option>-listen</option> option to run
+      <application>vncviewer</application> as a listener. In a terminal
+      window, enter the command:
+    </para>
 <screen>
  <userinput>vncviewer -listen</userinput>
 </screen>
-      <note>
-        <title>Firewall Reconfiguration Required</title>
-
-        <para>
-          By default, 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>.
-        </para>
-      </note>
+    <note>
+      <title>Firewall Reconfiguration Required</title>
 
       <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.
+        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>.
       </para>
+    </note>
 
-      <para>
-        For example, to connect to a VNC client on the system
-        <systemitem
+    <para>
+      Once the listening client is active, start the installation system
+      and set the VNC options at the
+      <prompt>boot:</prompt>
+      prompt. In addition to <option>vnc</option> and
+      <option>vncpassword</option> options, use the
+      <option>vncconnect</option> option to specify the name or IP
+      address of the system that has the listening client. To specify
+      the TCP port for the listener, add a colon and the port number to
+      the name of the system.
+    </para>
+
+    <para>
+      For example, to connect to a VNC client on the system
+      <systemitem
 	class="systemname">desktop.mydomain.com</systemitem>
-        on the port <systemitem>5500</systemitem>, enter the following
-        at the
-        <prompt>boot:</prompt>
-        prompt:
-      </para>
+      on the port <systemitem>5500</systemitem>, 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
-        <option>telnet</option> option at the
-        <prompt>boot:</prompt>
-        prompt:
-      </para>
+    <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>
+    <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 ? 
+    <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>
+  </section>
+  <section id="sn-automating-installation">
+    <title>Automating the Installation with Kickstart</title>
 
+    <para>
+      A <firstterm>Kickstart</firstterm> file specifies settings for an
+      installation. Once booted, the installation system may read a
+      Kickstart file and carry out the installation process without
+      requiring any further input from a user.
+    </para>
+    <tip>
+      <title>Every Installation Produces a Kickstart File</title>
       <para>
-        A <firstterm>Kickstart</firstterm> file specifies settings for
-        an installation. Once booted, the installation system may read a
-        Kickstart file and carry out the installation process without
-        requiring any further input from a user.
-      </para>
-      <tip>
-        <title>Every Installation Produces a Kickstart File</title>
-        <para>
-          The &FED; installation process automatically writes a
-          Kickstart file that contains the settings for the installed
-          system. This file is always saved as
-          <filename>/root/anaconda-ks.cfg</filename>. You may use this
-          file to repeat the installation with identical settings, or
-          modify copies to specify settings for other systems.
-        </para>
-      </tip>
-      <para>
-        &FED; includes a graphical application that enables you to
-        create and modify Kickstart files by selecting the options that
-        you require. Use the package
-        <filename>system-config-kickstart</filename> to install this
-        utility. To load the &FED; Kickstart editor, choose <menuchoice>
-        <guimenu>Applications</guimenu> <guisubmenu>System
-        Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
+        The &FED; installation process automatically writes a Kickstart
+        file that contains the settings for the installed system. This
+        file is always saved as
+        <filename>/root/anaconda-ks.cfg</filename>. You may use this
+        file to repeat the installation with identical settings, or
+        modify copies to specify settings for other systems.
       </para>
+    </tip>
+    <para>
+      &FED; includes a graphical application that enables you to create
+      and modify Kickstart files by selecting the options that you
+      require. Use the package
+      <filename>system-config-kickstart</filename> to install this
+      utility. To load the &FED; Kickstart editor, choose <menuchoice>
+      <guimenu>Applications</guimenu> <guisubmenu>System
+      Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
+    </para>
 
-      <para>
-        Kickstart files list installation settings in plain-text, with
-        one option per line. This format enables you to modify your
-        Kickstart files with any text editor, and write scripts or
-        applications that generate custom Kickstart files for your
-        systems.
-      </para>
+    <para>
+      Kickstart files list installation settings in plain-text, with one
+      option per line. This format enables you to modify your Kickstart
+      files with any text editor, and write scripts or applications that
+      generate custom Kickstart files for your systems.
+    </para>
 
-      <para>
-        To automate the installation process with a Kickstart file, use
-        the <option>ks</option> option to specify the name and location
-        of the file:
-      </para>
+    <para>
+      To automate the installation process with a Kickstart file, use
+      the <option>ks</option> option to specify the name and location of
+      the file:
+    </para>
 <screen>
  <userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
 </screen>
-      <para>
-        You may use Kickstart files that are held on either removable
-        storage, or a hard drive, or located 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>
+      You may use Kickstart files that are held on either removable
+      storage, or a hard drive, or located 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>
+<entry>
                 <para>
                   <option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   Hard Drive
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   Other Device
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   HTTP Server
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   FTP Server
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-            <row>
-              <entry>
+          </row>
+          <row>
+<entry>
                 <para>
                   NFS Server
                 </para>
               </entry>
-              <entry>
+<entry>
                 <para>
                   <option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option>
                 </para>
               </entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-      <para>
-        To obtain a Kickstart file from a script or application on a Web
-        server, specify the URL of the application with the
-        <option>ks=</option> option. If you add the option
-        <option>kssendmac</option>, the request also sends HTTP headers
-        to the Web application. Your application may use these headers
-        to identify the computer. This line sends a request with headers
-        to the application
-        <wordasword>http://server.example.com/kickstart.cgi</wordasword>:
-      </para>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+    <para>
+      To obtain a Kickstart file from a script or application on a Web
+      server, specify the URL of the application with the
+      <option>ks=</option> option. If you add the option
+      <option>kssendmac</option>, the request also sends HTTP headers to
+      the Web application. Your application may use these headers to
+      identify the computer. 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>
+  <section id="sn-bootoptions-hardware">
+    <title>Enhancing Hardware Support</title>
 
-    <section id="sn-bootoptions-hardware">
-      <title>Hardware Support</title>
+    <para>
+      By default, &FED; attempts to automatically detect and configure
+      support for all of the components of your computer. &FED; supports
+      the majority of hardware in common use with the software
+      <firstterm>drivers</firstterm> that are included with the
+      operating system. To enable a &FED; system to support more devices
+      you may supply additional drivers during the installation process,
+      or at a later time.
+    </para>
 
+    <section id="sn-bootoptions-driverdisks">
+      <title>Adding Hardware Support with Driver Disks</title>
+<!-- SE: This section is untested. -->
       <para>
-        By default, &FED; attempts to automatically detect and configure
-        support for all of the components of your computer. &FED;
-        supports the majority of hardware in common use with the
-        software <firstterm>drivers</firstterm> that are included with
-        the operating system. To enable a &FED; system to support more
-        devices you may supply additional drivers during the
-        installation process, or at a later time.
+        The installation system may load drivers from disks, pen drives,
+        or network servers to configure support for new devices. After
+        the installation is complete, remove any driver disks and store
+        them for later use.
       </para>
 
-      <section id="sn-bootoptions-driverdisks">
-        <title>Adding Hardware Support with Driver Disks</title>
-<!-- SE: This section is untested. -->
-        <para>
-          The installation system may load drivers from disks, pen
-          drives, or network servers to configure support for new
-          devices. After the installation is complete, remove any driver
-          disks and store them for later use.
-        </para>
-
-        <para>
-          Hardware manufacturers may supply driver disks for &FED; with
-          the device, or provide image files to prepare the disks. To
-          obtain the latest drivers, download the correct file from the
-          website of the manufacturer.
-        </para>
-
-        <note>
-          <title>Driver Disks Supplied as Zipped Files</title>
+      <para>
+        Hardware manufacturers may supply driver disks for &FED; with
+        the device, or provide image files to prepare the disks. To
+        obtain the latest drivers, download the correct file from the
+        website of the manufacturer.
+      </para>
 
-          <para>
-            Driver disk images may be distributed as compressed
-            archives, or zip files. For identification, the names of zip
-            files include the extensions <filename>.zip</filename>, or
-            <filename>.tar.gz</filename>. To extract the contents of a
-            zipped file with a &FED; system, choose <menuchoice>
-            <guimenu>Applications</guimenu> <guisubmenu>System
-            Tools</guisubmenu><guimenuitem>Archive
-            Manager</guimenuitem></menuchoice>.
-          </para>
-        </note>
+      <note>
+        <title>Driver Disks Supplied as Zipped Files</title>
 
         <para>
-          To format a disk or pen drive with an image file, use the
-          <command>dd</command> utility. For example, to prepare a
-          diskette with the image file <filename>drivers.img</filename>,
-          enter this command in a terminal window:
+          Driver disk images may be distributed as compressed archives,
+          or zip files. For identification, the names of zip files
+          include the extensions <filename>.zip</filename>, or
+          <filename>.tar.gz</filename>. To extract the contents of a
+          zipped file with a &FED; system, choose <menuchoice>
+          <guimenu>Applications</guimenu> <guisubmenu>System
+          Tools</guisubmenu><guimenuitem>Archive
+          Manager</guimenuitem></menuchoice>.
         </para>
+      </note>
+
+      <para>
+        To format a disk or pen drive with an image file, use the
+        <command>dd</command> utility. For example, to prepare a
+        diskette with the image file <filename>drivers.img</filename>,
+        enter this command in a terminal window:
+      </para>
 <screen>
  <userinput>dd if=drivers.img of=/dev/fd0</userinput>
 </screen>
-        <para>
-          To use a driver disk in the installation process, specify the
-          <option>dd</option> option at the
-          <prompt>boot:</prompt>
-          prompt:
-        </para>
+      <para>
+        To use a driver disk in the installation process, specify the
+        <option>dd</option> option at the
+        <prompt>boot:</prompt>
+        prompt:
+      </para>
 <screen>
  <userinput>linux dd</userinput>
 </screen>
-        <para>
-          When prompted, select <guibutton>Yes</guibutton> to provide a
-          driver disk. Choose the drive that holds the driver disk from
-          the list on the <guilabel>Driver Disk Source</guilabel> text
-          screen.
-        </para>
+      <para>
+        When prompted, select <guibutton>Yes</guibutton> to provide a
+        driver disk. Choose the drive that holds the driver disk from
+        the list on the <guilabel>Driver Disk Source</guilabel> text
+        screen.
+      </para>
 
-        <para>
-          The installation system may also read drivers from disk images
-          that are held on network servers. Refer to
-          <xref linkend="tb-driversources"/> for the supported sources
-          of driver image files.
-        </para>
-        <table id="tb-driversources">
-          <title>Driver Disk Image Sources</title>
-          <tgroup cols="2">
-            <colspec colnum="1" colname="Image Source"/>
-            <colspec colnum="2" colname="Option Format"/>
-            <thead>
-              <row>
-                <entry>Image Source</entry>
-                <entry>Option Format</entry>
-              </row>
-            </thead>
-            <tbody>
-              <row>
-                <entry>
+      <para>
+        The installation system may also read drivers from disk images
+        that are held on network servers. Refer to
+        <xref linkend="tb-driversources"/> for the supported sources of
+        driver image files.
+      </para>
+      <table id="tb-driversources">
+        <title>Driver Disk Image Sources</title>
+        <tgroup cols="2">
+          <colspec colnum="1" colname="Image Source"/>
+          <colspec colnum="2" colname="Option Format"/>
+          <thead>
+            <row>
+<entry>Image Source</entry>
+<entry>Option Format</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+<entry>
                   <para>
                     Select a drive or device
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>dd</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     HTTP Server
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>dd=<replaceable>http://server.mydomain.com/directory/drivers.img</replaceable></option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     FTP Server
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable></option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     NFS Server
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable></option>
                   </para>
                 </entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </table>
-      </section>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
 
-      <section id="sn-bootoptions-hwdetection">
-        <title>Overriding Automatic Hardware Detection</title>
+    <section id="sn-bootoptions-hwdetection">
+      <title>Overriding Automatic Hardware Detection</title>
 
+      <para>
+        For some models of device automatic hardware configuration may
+        fail, or cause instability. In these cases, you may need to
+        disable automatic configuration for that type of device, and
+        take additional steps to manually configure the device after the
+        installation process is complete.
+      </para>
+      <tip>
+        <title>Check the Release Notes</title>
         <para>
-          For some models of device automatic hardware configuration may
-          fail, or cause instability. In these cases, you may need to
-          disable automatic configuration for that type of device, and
-          take additional steps to manually configure the device after
-          the installation process is complete.
-        </para>
-        <tip>
-          <title>Check the Release Notes</title>
-          <para>
-            Refer to the Release Notes for information on known issues
-            with specific devices.
-          </para>
-        </tip>
-        <para>
-          To override the automatic hardware detection, use one or more
-          of the following options:
+          Refer to the Release Notes for information on known issues
+          with specific devices.
         </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>
+      </tip>
+      <para>
+        To override the automatic hardware detection, use one or more of
+        the following options:
+      </para>
+      <table id="tb-hwoptions">
+        <title>Hardware Options</title>
+        <tgroup cols="2">
+          <colspec colnum="1" colname="Compatibility Setting"/>
+          <colspec colnum="2" colname="Option"/>
+          <thead>
+            <row>
+<entry>Compatibility Setting</entry>
+<entry>Option</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+<entry>
                   <para>
                     Disable all hardware detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>noprobe</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable graphics, keyboard, and mouse detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>headless</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
+                  <para>
+                    Disable automatic monitor detection (DDC)
+                  </para>
+                </entry>
+<entry>
+                  <para>
+                    <option>skipddc</option>
+                  </para>
+                </entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable mainboard APIC
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>noapic</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable power management (ACPI)
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>acpi=off</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
-                    Disable automatic monitor detection (DDC)
+                    Disable Direct Memory Access (DMA) for storage
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
-                    <option>skipddc</option>
+                    <option>ide=nodma</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
+                  <para>
+                    Disable BIOS-assisted RAID
+                  </para>
+                </entry>
+<entry>
+                  <para>
+                    <option>nodmraid</option>
+                  </para>
+                </entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable Firewire device detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>nofirewire</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable parallel port detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>noparport</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable PC Card (PCMCIA) device detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>nopcmcia</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable USB storage device detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>nousbstorage</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Disable all USB device detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>nousb</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
-                  <para>
-                    Enable software RAID controller support
-                  </para>
-                </entry>
-                <entry>
-                  <para>
-                    <option>dmraid</option>
-                  </para>
-                </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Force Firewire device detection
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>firewire</option>
                   </para>
                 </entry>
-              </row>
-              <row>
-                <entry>
+            </row>
+            <row>
+<entry>
                   <para>
                     Prompt user for ISA device configuration
                   </para>
                 </entry>
-                <entry>
+<entry>
                   <para>
                     <option>isa</option>
                   </para>
                 </entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </table>
-      </section>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
+  </section>
+  <section id="sn-boot-modes">
+    <title>Using the Maintenance Boot Modes</title>
+
+    <section id="sn-memtest">
+      <title>Memory (RAM) Testing Mode</title>
+
+      <para>
+        Faults in memory modules may cause your system to freeze or
+        crash unpredictably. In some cases, memory faults may only cause
+        errors with particular combinations of software. For this
+        reason, you should test the memory of a computer before you
+        install &FED; for the first time, even if it has previously run
+        other operating systems.
+      </para>
+
+      <para>
+        To boot your computer in memory testing mode, enter
+        <userinput>memtest86</userinput> at the
+        <prompt>boot:</prompt>
+        prompt. The first test starts immediately. By default,
+        <command>memtest86</command> carries out a total of ten tests.
+      </para>
+
+      <para>
+        To halt the tests and reboot your computer, enter
+        <keycap>Esc</keycap> at any time.
+      </para>
+    </section>
+
+    <section id="sn-mode-rescue">
+      <title>Booting Your Computer with 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>
+
+      <para>
+        <remark role="FIXME">Add a note that the boot and rescue CDs also have this facility. 
+      </remark>
+      </para>
     </section>
 <!-- SE: To be useful, this needs an explanation of how it differs from providing driver disks.
 
@@ -887,127 +917,6 @@
     </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>
 
 <!--


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- fedora-install-guide-en.xml	16 Jan 2006 00:23:00 -0000	1.38
+++ fedora-install-guide-en.xml	23 Jan 2006 23:24:09 -0000	1.39
@@ -6,18 +6,14 @@
 
 <!ENTITY DOCNAME "fedora-install-guide">
 <!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.13">
-<!ENTITY DOCDATE "2006-01-16">
+<!ENTITY DOCVERSION "1.14">
+<!ENTITY DOCDATE "2006-01-23">
 <!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
 
-<!-- SE: Commented out, but does not stop duplicate Legal Notices in the HTML build. 
-<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
--->
-
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "129911">
 <!ENTITY FCLOCALVER "5">
-<!ENTITY DOCLOCALVER "1.13"> <!-- what's this for again? -->
+<!ENTITY DOCLOCALVER "1.14"> <!-- what's this for again? -->
 <!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" >
 
 <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">


Index: fedora-install-guide-firstboot-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-firstboot-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- fedora-install-guide-firstboot-en.xml	8 Dec 2005 00:27:16 -0000	1.16
+++ fedora-install-guide-firstboot-en.xml	23 Jan 2006 23:24:09 -0000	1.17
@@ -43,10 +43,12 @@
     <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
+      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>
@@ -75,20 +77,22 @@
     <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.
+      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.
+      permit only Secure SHell (SSH) connections from other systems. You
+      may make changes on this screen to allow access to specific
+      network services on your &FED; system.
     </para>
 
     <para>
@@ -97,20 +101,46 @@
     </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.
+      To enable access to the services listed on this screen, click the
+      check box next to the service name.
+    </para>
+
+    <important>
+      <title>SSH Remote Access</title>
+
+      <para>
+        All &FED; systems automatically run the SSH remote access
+        service. The default firewall configuration allows connections
+        to this service, to ensure that administrators have immediate
+        remote access to new systems.
+      </para>
+    </important>
+
+    <para>
+      To enable access to other services, enter the required ports in
+      the <guilabel>Other ports:</guilabel> field. For each port,
+      specify the port number followed by the connection type, in the
+      format
+      <userinput><replaceable>portnumber</replaceable>:<replaceable>type</replaceable></userinput>.
+      The majority of services use TCP ports.
+    </para>
+
+    <para>
+      For example, to allow other systems to access mail with the
+      <systemitem class="protocol">IMAP</systemitem> protocol, which may
+      use both TCP port 143 and TCP port 993, enter <userinput>143:tcp,
+      993:tcp</userinput>.
     </para>
 
     <para>
-      Avoid disabling the firewall. If you believe it is necessary to do
-      so, select <guilabel>No firewall</guilabel>.
+      Avoid disabling the firewall. If you believe that it is necessary
+      to do so, select <guilabel>No firewall</guilabel>.
     </para>
     <tip>
       <title>Changing the Firewall Settings</title>
       <para>
-        To change these settings later, choose
-        <menuchoice> <guimenu>System</guimenu>
+        To change these settings later, choose <menuchoice>
+        <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu><guimenuitem>Security
         Level and Firewall</guimenuitem></menuchoice>.
       </para>
@@ -125,15 +155,16 @@
     </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.
+      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>
@@ -147,7 +178,7 @@
 
     <variablelist>
       <varlistentry>
-        <term><guilabel>Active</guilabel></term>
+        <term><guilabel>Enforcing</guilabel></term>
         <listitem>
           <para>
             Select this mode to use the targeted &SEL; policy on your
@@ -176,8 +207,7 @@
           <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>
+            later, select <menuchoice> <guimenu>System</guimenu>
             <guisubmenu>Administration</guisubmenu>
             <guimenuitem>Security Level and Firewall</guimenuitem>
             </menuchoice>.
@@ -185,18 +215,21 @@
         </listitem>
       </varlistentry>
     </variablelist>
-
+<!-- SE: Note that items on this screen are labeled "SELinux...", so the text doesn't use the &SEL; entity in those cases. -->
     <para>
-      To adjust &SEL;, choose <guilabel>Modify SELinux Policy</guilabel>. To exempt a service from &SEL;, select the service from the list, and choose the <guilabel>Remove SELinux protection</guilabel> option. 
+      To adjust &SEL;, choose <guilabel>Modify SELinux
+      Policy</guilabel>. To exempt a key service from &SEL;
+      restrictions, select the service from the list, and choose the
+      <guilabel>Remove SELinux protection</guilabel> option. The
+      <guilabel>SELinux Service Protection</guilabel> item on the list
+      includes options for additional services.
     </para>
-
     <tip>
       <title>Changing the &SEL; policy</title>
       <para>
         &SEL; is unique in that it cannot be bypassed, even by the
         system administrators. To change the behavior of &SEL; after
-        installation, choose <menuchoice>
-        <guimenu>System</guimenu>
+        installation, choose <menuchoice> <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
         Level and Firewall</guimenuitem> </menuchoice>.
       </para>
@@ -208,10 +241,12 @@
     <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
+      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>
@@ -243,8 +278,8 @@
     <tip>
       <title>Setting the Clock</title>
       <para>
-        To change these settings later, choose
-        <menuchoice> <guimenu>System</guimenu>
+        To change these settings later, choose <menuchoice>
+        <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu> <guimenuitem>Date &
         Time</guimenuitem> </menuchoice>.
       </para>
@@ -365,8 +400,8 @@
     <tip>
       <title>Resetting the display</title>
       <para>
-        To reconfigure your system after the installation has completed, choose <menuchoice>
-        <guimenu>System</guimenu>
+        To reconfigure your system after the installation has completed,
+        choose <menuchoice> <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu>
         <guimenuitem>Display</guimenuitem> </menuchoice>.
       </para>
@@ -407,8 +442,8 @@
       <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>
+        installation is complete, choose <menuchoice>
+        <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu> <guimenuitem>Users &
         Groups</guimenuitem> </menuchoice>.
       </para>
@@ -417,9 +452,6 @@
       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>
@@ -452,14 +484,20 @@
     </figure>
     <para>
       Click <guibutton>Play Test Sound</guibutton> to check the sound
-      card configuration. If the configuration is correct, &FC; plays a
+      card configuration. If the configuration is correct, &FED; 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>
+      hear the sound, check your speakers and try again. In some cases,
+      you may need to alter the additional settings to obtain the best
+      sound quality.
+    </para>
+<!-- SE: This may not be quite correct: somebody with a stronger grasp of Linux audio could do better. -->
+    <para>
+      Sound cards may act as multiple audio devices. To change the
+      <guilabel>Default PCM device</guilabel>, select a new option from
+      the drop-down list. By default, audio applications connect to a
+      software mixer that manages the PCM devices. To enable
+      applications to bypass the software mixer, select the option to
+      <guilabel>Use only the hardware device</guilabel>.
     </para>
 
     <para>
@@ -470,10 +508,9 @@
     <tip>
       <title>Changing the Sound Card</title>
       <para>
-        &FC; will automatically attempt to detect a new sound card if
+        &FED; 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>
+        process manually, choose <menuchoice> <guimenu>System</guimenu>
         <guisubmenu>Administration</guisubmenu> <guimenuitem>Soundcard
         Detection</guimenuitem> </menuchoice>.
       </para>


Index: fedora-install-guide-nextsteps-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-nextsteps-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-nextsteps-en.xml	12 Dec 2005 02:21:54 -0000	1.10
+++ fedora-install-guide-nextsteps-en.xml	23 Jan 2006 23:24:09 -0000	1.11
@@ -3,11 +3,11 @@
 <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.
+    &FED; provides you with a complete operating system with a vast
+    range of capabilities, supported by a large community.
   </para>
   <section id="sn-system-updating">
-    <title>Updating Your &FED; System</title>
+    <title>Updating Your System</title>
 
     <para>
       The &FP; releases updated software packages for &FC; throughout
@@ -24,14 +24,15 @@
     <para>
       To update your system with the latest packages, use the
       <indexterm>
-      <primary>Package Updater</primary>
-      </indexterm> <application>Package Updater</application>:
+        <primary>Package Updater</primary>
+      </indexterm>
+      <application>Package Updater</application>:
     </para>
     <orderedlist>
       <listitem>
         <para>
-          Choose <menuchoice><guimenu>System</guimenu>
-          <guisubmenu>Administration</guisubmenu> <guimenuitem>Package
+          Choose <menuchoice><guimenu>Applications</guimenu>
+          <guisubmenu>System Tools</guisubmenu> <guimenuitem>Package
           Updater</guimenuitem> </menuchoice>.
         </para>
       </listitem>
@@ -43,10 +44,9 @@
       </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.
+          Review the list of updated packages. The package list displays
+          a double arrow next to any updates that require a system
+          reboot to take effect.
         </para>
       </listitem>
       <listitem>
@@ -57,22 +57,21 @@
       </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.
+          If one or more updates require a system reboot, the update
+          process displays a dialog with the option to <guibutton>Reboot
+          Now</guibutton>. Either select this option to reboot the
+          system immediately, or <guibutton>Cancel</guibutton> it and
+          reboot the system at a more convenient time.
         </para>
       </listitem>
     </orderedlist>
     <para>
-      <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>:
+      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>
@@ -140,41 +139,81 @@
       <para>
         Announcements with the keyword
         <wordasword>[SECURITY]</wordasword> in the title identify
-        package updates that remove security vulnerabilities.
+        package updates that resolve security vulnerabilities.
       </para>
     </important>
   </section>
   <section id="sn-web-help">
-    <title>Finding Documentation on the Web</title>
+    <title>Finding Documentation and Support</title>
 
     <para>
-      Documentation for &FC; is available from the &FP; Website:
-    </para>
-
-    <para>
-      <ulink
-	  url="http://fedora.redhat.com/docs/"/>
+      Members of the &FED; community provides support through mailing
+      lists, web forums and Linux User Groups (LUGs) across the world.
     </para>
 
     <para>
-      The Linux Documentation Project (LDP) produces books and
-      tutorials:
+      The Website for the official forums is:
     </para>
 
     <para>
       <ulink
-	  url="http://www.tldp.org/"/>
+	  url="http://forums.fedoraforum.org/"/>
     </para>
 
     <para>
-      For many parts of &FC;, you may find the &RHEL; documentation
-      useful:
+      The following resources provide information on many aspects of
+      &FED;:
     </para>
 
-    <para>
-      <ulink
+    <variablelist>
+      <varlistentry>
+        <term>
+	    The FAQ on the &FP; website
+	  </term>
+        <listitem>
+          <para>
+            <ulink
+	  url="http://fedoraproject.org/wiki/FAQ/"/>
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>
+	   The documents available from the &FDP; website 
+	  </term>
+        <listitem>
+          <para>
+            <ulink
+	  url="http://fedora.redhat.com/docs/"/>
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>
+         The Linux Documentation Project (LDP)	   
+	  </term>
+        <listitem>
+          <para>
+            <ulink
+	  url="http://www.tldp.org/"/>
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>
+         The &RHEL; documentation, much of which also applies to &FED;
+	  </term>
+        <listitem>
+          <para>
+            <ulink
 	url="http://www.redhat.com/docs/manuals/enterprise/"/>
-    </para>
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
 
     <para>
       Many other organizations and individuals also provide tutorials
@@ -187,23 +226,6 @@
 	  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>
 


Index: fedora-install-guide-techref-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-techref-en.xml	9 Jan 2006 23:56:29 -0000	1.4
+++ fedora-install-guide-techref-en.xml	23 Jan 2006 23:24:09 -0000	1.5
@@ -106,8 +106,7 @@
       <listitem>
         <para>
           &FED; uses the <command>netfilter</command> framework. The
-          Netfilter project website provides documentation for
-          <command>netfilter</command>, and the
+          Netfilter project website provides documentation for both <command>netfilter</command>, and the
           <command>iptables</command> administration facilities:
           <ulink url="http://netfilter.org/documentation/index.html"/>.
         </para>


Index: fedora-install-guide-timezone-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-timezone-en.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-timezone-en.xml	27 May 2005 22:15:15 -0000	1.10
+++ fedora-install-guide-timezone-en.xml	23 Jan 2006 23:24:09 -0000	1.11
@@ -2,16 +2,14 @@
 
 <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
+    location of your computer. Specify a time zone even if you plan to
     use <indexterm>
-      <primary>NTP (Network Time Protocol)</primary>
+    <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>
 
@@ -19,76 +17,72 @@
       &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>
+        <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>
+        </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.
+      To select a time zone using the map, first place your mouse
+      pointer over your region on the map. Click once to magnify that
+      region on the map. Next, select the yellow dot that represents the
+      city nearest to your location. Once you select a dot, it becomes a
+      red <guilabel>X</guilabel> to indicate your selection.
     </para>
 
     <para>
       To select a time zone using the list, select the name of the city
-      nearest to your location.  The cities are listed in alphabetical
+      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>
+      <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>
+      <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
+      <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
+      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;.
+        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>
 


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml	17 Jan 2006 23:04:15 -0000	1.3
+++ rpm-info.xml	23 Jan 2006 23:24:09 -0000	1.4
@@ -1,6 +1,6 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 
-<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd" >
+<!DOCTYPE rpm-info SYSTEM "../docs-common/packaging/rpm-info.dtd">
 
 <rpm-info>
   <colophon>
@@ -28,9 +28,14 @@
 <!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
   </titles>
   <changelog order="newest-first">
+    <revision date="2006-01-23" number="1.14" role="doc">
+      <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+      <details>Updated for FC5 test2.</details>
+    </revision>
     <revision date="Tue Jan 17 2006" number="0" role="rpm">
       <author worker="megacoder"/>
-      <details>Added initial empty RPM revision to test packaging.</details>
+      <details lang="en">Added initial empty RPM revision to test packaging.</details>
     </revision>
     <revision date="2006-01-16" number="1.13" role="doc">
       <author worker="StuartEllis"/>




More information about the Fedora-docs-commits mailing list