install-guide fedora-install-guide-adminoptions-en.xml, 1.2, 1.3 fedora-install-guide-en.xml, 1.32, 1.33 fedora-install-guide-techref-en.xml, 1.1, 1.2

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Thu Dec 22 01:47:44 UTC 2005


Author: elliss

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

Modified Files:
	fedora-install-guide-adminoptions-en.xml 
	fedora-install-guide-en.xml 
	fedora-install-guide-techref-en.xml 
Log Message:
- Filled out Management Option section: needs indexing and testing to complete.
- Fixed small typo in Technical References section.




Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-adminoptions-en.xml	14 Dec 2005 22:59:52 -0000	1.2
+++ fedora-install-guide-adminoptions-en.xml	22 Dec 2005 01:47:35 -0000	1.3
@@ -10,6 +10,11 @@
     <title>Boot Options</title>
 
     <para>
+      <remark role="FIXME">Almost all of the options listed here have NOT yet been tested. 
+      </remark>
+    </para>
+
+    <para>
       To use boot options, enter <userinput>linux
       <replaceable>option</replaceable></userinput> at the
       <prompt>boot:</prompt>
@@ -27,10 +32,10 @@
       <title>Booting Your Computer with Rescue Mode</title>
 
       <para>
-        You may use installation disc #1 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
+        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>
 
@@ -38,7 +43,7 @@
         To load the rescue mode, enter:
       </para>
 <screen>
-  <userinput>linux rescue</userinput>
+ <userinput>linux rescue</userinput>
 </screen>
       <para>
         Specify the language, keyboard layout and network settings for
@@ -46,54 +51,550 @@
       </para>
     </section>
 
-    <section id="sn-automating-installation">
-      <title>Automating the Installation with Kickstart</title>
+    <section id="sn-bootoptions-installer">
+      <title>Configuring the Installation System</title>
 
       <para>
-        <remark role="FIXME">Kickstart.
-      </remark>
+        You may configure the installation system without affecting the
+        final &FED; system.
+      </para>
+
+      <para>
+        You may force the installation system to use the lowest possible
+        screen resolution (640x480) with the <option>lowres</option>
+        option. To use a specific display resolution, enter
+        <option>resolution=<replaceable>setting</replaceable></option>
+        as a boot option. For example, to set the display resolution to
+        1024x768, enter:
+      </para>
+<screen>
+<userinput>linux resolution=<replaceable>1024x768</replaceable></userinput>
+</screen>
+      <para>
+        To run the installation process in <option>text</option> mode,
+        enter:
+      </para>
+<screen>
+  <userinput>linux text</userinput>
+</screen>
+      <para>
+        To enable support for a serial console, enter
+        <option>serial</option> as an additional option.
       </para>
+
+      <para>
+        You may also configure the installation method and network
+        settings at the
+        <prompt>boot:</prompt>
+        prompt itself, without using <option>askmethod</option> to
+        display menus. To specify the installation method from the
+        <prompt>boot:</prompt>
+        prompt, use the <option>method</option> option.
+      </para>
+      <table id="tb-installmethods">
+        <title>Installation Methods</title>
+        <tgroup cols="2">
+          <colspec colnum="1" colname="Method"/>
+          <colspec colnum="2" colname="Format"/>
+          <thead>
+            <row>
+              <entry>Method</entry>
+              <entry>Format</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>
+                <para>
+                  CD or DVD drive
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>method=<replaceable>cdrom</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Hard Drive
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>method=<replaceable>hd://device/</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  HTTP Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>method=<replaceable>http://server.example.com/directory/</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  FTP Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  NFS Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>method=<replaceable>nfs:server.example.com:/directory/</replaceable></option>
+                </para>
+              </entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <para>
+        By default, the installation system uses DHCP to obtain the
+        correct network settings. To manually configure one or more
+        network settings, specify the setting at the
+        <prompt>boot:</prompt>
+        prompt. You may set the <option>ip</option> address,
+        <option>netmask</option>, <option>gateway</option>, and
+        <option>dns</option> servers for the installation system.
+      </para>
+
+      <para>
+        This example configures all of the network settings for an
+        installation syste that uses the IP address 192.168.1.10:
+      </para>
+<screen>
+<userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput>
+</screen>
     </section>
 
-    <section id="sn-bootoptions-networking">
-      <title>Networking Options</title>
+    <section id="sn-remote-installation">
+      <title>Enabling Remote Access to the Installation System</title>
 
       <para>
-        <remark role="FIXME">VNC, remote syslog, and options for network settings.
-      </remark>
+        You may access the interface for the installation system from
+        any other system. Access to a text mode display requires
+        <command>telnet</command>, which is installed by default on
+        &FED; systems. To remotely access a graphical display for the
+        installation system, you must install client software that
+        supports the VNC (Virtual Network Computing) display protocol.
       </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>
+<screen>
+<userinput>telnet computer.mydomain.com</userinput>
+</screen>
+      <para>
+        To enable remote graphical access to the installation system,
+        enter two options at the prompt:
+      </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput>
+</screen>
+      <para>
+        The <option>vnc</option> option enables the VNC service. The
+        <option>vncpassword</option> option sets a password for remote
+        access. The example shown above sets the password as
+        <systemitem>qwerty</systemitem>.
+      </para>
+
+      <note>
+        <title>VNC Passwords</title>
+
+        <para>
+          The VNC password must be at least six characters long.
+        </para>
+      </note>
+
+      <para>
+        Specify the language, keyboard layout and network settings for
+        the installation system with the screens that follow. You may
+        then access the graphical interface through a VNC client. The
+        installation system displays the correct connection setting for
+        the VNC client:
+      </para>
+<screen>
+<computeroutput><![CDATA[Starting VNC...
+The VNC server is now running.
+Please connect to server.example.com:1 to begin the install...
+Starting graphical installation...
+Press <enter> for a shell]]></computeroutput>
+</screen>
+      <tip>
+        <title>Installing a VNC Client</title>
+        <para>
+          To install a VNC client on &FED;, use the package
+          <filename>vnc</filename>. To run the
+          <application>vncviewer</application> client, choose
+          <menuchoice> <guimenu>Applications</guimenu>
+          <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC
+          Viewer</guimenuitem></menuchoice>.
+        </para>
+      </tip>
+      <para>
+        Alternatively, you may automatically connect the interface for
+        the installation system to an active VNC client, with the
+        <option>vncconnect</option> option. This requires the VNC client
+        to run in <emphasis>listening</emphasis> mode. The client system
+        must also allow connections on a known TCP port. By default, the
+        <application>vncviewer</application> utility listens on TCP port
+        <systemitem>5500</systemitem>.
+      </para>
+
+      <para>
+        To connect to a VNC client on the system
+        <systemitem
+	class="systemname">desktop.mydomain.com</systemitem>
+        on the port <systemitem>5500</systemitem>, you would enter the
+        following at the
+        <prompt>boot:</prompt>
+        prompt:
+      </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
+</screen>
+      <para>
+        On &FED; systems, use the <option>-listen</option> option to
+        start the <application>vncviewer</application> VNC client in
+        listening mode:
+      </para>
+<screen>
+ <userinput>vncviewer -listen</userinput>
+</screen>
     </section>
 
-    <section id="sn-bootoptions-interface">
-      <title>Configuring the Installation Interface</title>
+    <section id="sn-automating-installation">
+      <title>Automating the Installation with Kickstart</title>
 
       <para>
-        To run the installation process in text mode, enter:
+        A <firstterm>Kickstart</firstterm> file specifies settings for
+        an installation. To automate the installation process, use the
+        <option>ks</option> option to provide the name and location of a
+        Kickstart file:
       </para>
 <screen>
-  <userinput>linux text</userinput>
+ <userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
 </screen>
       <para>
-        <remark role="FIXME"> Add information on enabling serial console.
-      </remark>
+        You may use Kickstart files that are located on either removable
+        storage, a hard drive, or a network server. Refer to
+        <xref linkend="tb-kssources"/> for the supported Kickstart
+        sources.
+      </para>
+      <table id="tb-kssources">
+        <title>Kickstart Sources</title>
+        <tgroup cols="2">
+          <colspec colnum="1" colname="Source"/>
+          <colspec colnum="2" colname="Format"/>
+          <thead>
+            <row>
+              <entry>Source</entry>
+              <entry>Format</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>
+                <para>
+                  CD or DVD drive
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Hard Drive
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Other Device
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  HTTP Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  FTP Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  NFS Server
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option>
+                </para>
+              </entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <tip>
+        <title>Kickstart File is Automatically Created</title>
+        <para>
+          The Kickstart file <filename>/root/anaconda-ks.cfg</filename>
+          contains the settings for your system. The &FED; installation
+          process automatically creates this file.
+        </para>
+      </tip>
+      <para>
+        To install an application to create and edit Kickstart files,
+        use the package <filename>system-config-kickstart</filename>. To
+        load this Kickstart file editor, choose <menuchoice>
+        <guimenu>Applications</guimenu> <guisubmenu>System
+        Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
+        Alternatively, you may edit Kickstart files with a text editor.
+      </para>
+
+      <para>
+        You may also write Web applications to generate Kickstart files.
+        To use a Web application to provide a Kickstart file, specify
+        the URL of the application with the <option>ks=</option> option.
+        If you add the option <option>kssendmac</option>, the request
+        also sends HTTP headers to the Web application. Your application
+        may use these headers to identify the computer. For example,
+        this line sends a request with headers to the application
+        <wordasword>http://server.example.com/kickstart.cgi</wordasword>:
       </para>
+<screen>
+<userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput>
+</screen>
     </section>
 
     <section id="sn-bootoptions-hardware">
       <title>Hardware Compatibility Options</title>
 
       <para>
-        <remark role="FIXME">Most of these options turn off configuring or using certain systems. Consider a table to summarise them.
-      </remark>
-      </para>
+        By default, &FED; detects and configures all of the components
+        of your computer. To override the automatic hardware detection,
+        use the following options:
+      </para>
+      <table id="tb-hwoptions">
+        <title>Hardware Options</title>
+        <tgroup cols="2">
+          <colspec colnum="1" colname="Option"/>
+          <colspec colnum="2" colname="Keyword"/>
+          <thead>
+            <row>
+              <entry>Option</entry>
+              <entry>Keyword</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>
+                <para>
+                  Disable all hardware detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>noprobe</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable graphics, keyboard, and mouse detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>headless</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable power management (ACPI)
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>acpi=off</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable monitor detection (DDC)
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>skipddc</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable Firewire device detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>nofirewire</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable parallel port detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>noparport</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable PC Card (PCMCIA) device detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>nopcmcia</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable USB storage device detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>nousbstorage</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Disable all USB device detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>nousb</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Force Firewire device detection
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>firewire</option>
+                </para>
+              </entry>
+            </row>
+            <row>
+              <entry>
+                <para>
+                  Prompt user for ISA device configuration
+                </para>
+              </entry>
+              <entry>
+                <para>
+                  <option>isa</option>
+                </para>
+              </entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
     </section>
 
     <section id="sn-mode-expert">
       <title>Installing &FC; with Expert Mode</title>
 
       <para>
-        The expert mode enables you to run the installation process with
-        additional options for hardware configuration.
+        The <option>expert</option> mode enables you to run the
+        installation process with additional options for hardware
+        configuration.
       </para>
 
       <para>
@@ -102,10 +603,6 @@
 <screen>
   <userinput>linux expert</userinput>
 </screen>
-      <para>
-        <remark role="FIXME">This is untested.
-      </remark>
-      </para>
     </section>
   </section>
   <section id="sn-memtest">


Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- fedora-install-guide-en.xml	14 Dec 2005 22:59:52 -0000	1.32
+++ fedora-install-guide-en.xml	22 Dec 2005 01:47:35 -0000	1.33
@@ -6,8 +6,8 @@
 
 <!ENTITY DOCNAME "fedora-install-guide">
 <!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.0.8">
-<!ENTITY DOCDATE "2005-12-14">
+<!ENTITY DOCVERSION "1.0.9">
+<!ENTITY DOCDATE "2005-12-22">
 <!ENTITY BOOKID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
 
 <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
@@ -15,7 +15,7 @@
 <!-- Bugzilla bug number for the draft notice -->
 <!ENTITY BUG-NUM "129911">
 <!ENTITY FCLOCALVER "5">
-<!ENTITY DOCLOCALVER "1.0.8"> <!-- what's this for again? -->
+<!ENTITY DOCLOCALVER "1.0.9"> <!-- what's this for again? -->
 
 
 <!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">
@@ -196,6 +196,16 @@
           </para>
         </revdescription>
       </revision>
+      <revision>
+        <revnumber>1.0.9</revnumber>
+        <date>2005-12-22</date>
+        <authorinitials>StuartEllis</authorinitials>
+        <revdescription>
+          <para>
+            Updated Management Options section.
+          </para>
+        </revdescription>
+      </revision>
     </revhistory>
   </bookinfo>
 


Index: fedora-install-guide-techref-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-techref-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-techref-en.xml	14 Dec 2005 22:59:52 -0000	1.1
+++ fedora-install-guide-techref-en.xml	22 Dec 2005 01:47:35 -0000	1.2
@@ -55,8 +55,7 @@
         <para>
           &FC; and <command>anaconda</command> include VNC to provide
           remote display capabilities. For more information about VNC,
-          refer to the documentation on the RealVNC website
-          <ulink url="http://www.realvnc.com/documentation/"/>.
+          refer to the documentation on the RealVNC website: <ulink url="http://www.realvnc.com/documentation/"/>.
         </para>
       </listitem>
     </varlistentry>
@@ -79,7 +78,7 @@
       <listitem>
         <para>
           &SEL; provides Mandatory Access Control (MAC) capabilities
-          that supplement the standard Linux security systems. Refer to
+          that supplement the standard Linux security features. Refer to
           the &SEL; FAQ for more information:
           <ulink url="http://fedora.redhat.com/docs/selinux-faq/"/>.
         </para>




More information about the Fedora-docs-commits mailing list