Branch 'f14' - en-US/adminoptions.xml en-US/adminoptions.xml~
Rüdiger Landmann
rlandmann at fedoraproject.org
Fri Oct 8 04:58:15 UTC 2010
en-US/adminoptions.xml | 39 --
en-US/adminoptions.xml~ | 878 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 880 insertions(+), 37 deletions(-)
New commits:
commit 72cf6c3e42caf79d73a7ab9cf00eff089eaf27f7
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Fri Oct 8 14:58:48 2010 +1000
rm telnet references BZ#640309
diff --git a/en-US/adminoptions.xml b/en-US/adminoptions.xml
index 7d3d53e..fcaee3d 100644
--- a/en-US/adminoptions.xml
+++ b/en-US/adminoptions.xml
@@ -273,13 +273,13 @@
<indexterm>
<primary>VNC (Virtual Network Computing)</primary>
</indexterm>
- <para>
+<!-- <para>
You may access either graphical or text interfaces for the
installation system from any other system. Access to a text mode
display requires <application>telnet</application>, which is installed by default on Fedora systems. To remotely access the graphical display
of an installation system, use client software that supports the
VNC (Virtual Network Computing) display protocol.
- </para>
+ </para> -->
<note>
<title>Installing a VNC Client on Fedora</title>
<para>
@@ -417,42 +417,7 @@ Press <enter> for a shell</screen>
</screen>
</section>
- <section id="sn-telnet-installation">
- <title>Enabling Remote Access with Telnet</title>
- <para>
- To enable remote access to a text mode installation, use the
- <indexterm>
- <primary>Telnet</primary>
- </indexterm>
- <option>telnet</option> option at the
- <prompt>boot:</prompt>
- prompt:
- </para>
-<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
-<screen>
-<userinput>linux text telnet</userinput>
-</screen>
- <para>
- You may then connect to the installation system with the
- <command>telnet</command> utility. The <command>telnet</command>
- command requires the name or IP address of the installation
- system:
- </para>
-<screen>
-<userinput>telnet computer.mydomain.com</userinput>
-</screen>
- <warning>
- <title>Telnet Access Requires No Password</title>
-
- <para>
- To ensure the security of the installation process, only use
- the <option>telnet</option> option to install systems on
- networks with restricted access.
- </para>
- </warning>
- </section>
- </section>
<section id="sn-remote-logging">
<title>Logging to a Remote System During the Installation</title>
diff --git a/en-US/adminoptions.xml~ b/en-US/adminoptions.xml~
new file mode 100644
index 0000000..19978de
--- /dev/null
+++ b/en-US/adminoptions.xml~
@@ -0,0 +1,878 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+
+<!-- $Id: -->
+
+<chapter id="ap-admin-options">
+ <title>Boot Options</title>
+ <para>
+ The Fedora installation system includes a range of functions and
+ options for administrators. To use boot options, enter
+ <userinput>linux <replaceable>option</replaceable></userinput> at
+ the
+ <prompt>boot:</prompt>
+ prompt.
+ </para>
+ <para>
+ If you specify more than one option, separate each of the options by
+ a single space. For example:
+ </para>
+<screen>
+<userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput>
+</screen>
+ <note>
+ <title>Anaconda Boot Options</title>
+
+ <para>
+ The anaconda installer has many boot options, most are listed on
+ the wiki <ulink url="http://fedoraproject.org/wiki/Anaconda/Options"/>.
+ </para>
+ </note>
+ <note>
+ <title>Kernel Boot Options</title>
+
+ <para>
+ The <ulink url="http://fedoraproject.org/wiki/KernelCommonProblems"/> page lists many common kernel boot options.
+ The full list of kernel options is in the file
+ /usr/share/doc/kernel-doc-<replaceable>version</replaceable>/Documentation/kernel-parameters.txt,
+ which is installed with the kernel-doc package.
+ </para>
+ </note>
+ <note>
+ <title>Rescue Mode</title>
+
+ <para>
+ The Fedora installation and <firstterm>rescue discs</firstterm> may
+ either boot with <firstterm>rescue mode</firstterm>, or load the
+ installation system. For more information on rescue discs and
+ rescue mode, refer to <xref linkend="sn-mode-rescue"/>.
+ </para>
+ </note>
+ <section id="sn-bootoptions-installer">
+ <title>Configuring the Installation System at the Boot Menu</title>
+
+ <para>
+ You can use the boot menu to specify a number of settings for the
+ installation system, including:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ language
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ display resolution
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ interface type
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installation method
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network settings
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <section id="sn-boot-options-language">
+ <title>Specifying the Language</title>
+
+ <para>
+ To set the language for both the installation process and the
+ final system, specify the ISO code for that language with the
+ <option>lang</option> option. Use the <option>keymap</option>
+ option to configure the correct keyboard layout.
+ </para>
+
+ <para>
+ For example, the ISO codes <userinput>el_GR</userinput> and
+ <userinput>gr</userinput> identify the Greek language and the
+ Greek keyboard layout:
+ </para>
+<screen>
+<userinput>linux lang=<replaceable>el_GR</replaceable> keymap=<replaceable>gr</replaceable></userinput>
+</screen>
+ </section>
+
+ <section id="sn-boot-options-interface">
+ <title>Configuring the Interface</title>
+
+ <para>
+ 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
+ 1024×768, enter:
+ </para>
+<screen>
+<userinput>linux resolution=<replaceable>1024x768</replaceable></userinput>
+</screen>
+ <para>
+ To run the installation process in
+ <indexterm>
+ <primary>text interface</primary>
+ </indexterm>
+ <option>text</option> mode, enter:
+ </para>
+<screen>
+<userinput>linux text</userinput>
+</screen>
+ <para>
+ To enable support for a
+ <indexterm>
+ <primary>serial console</primary>
+ </indexterm>
+ serial console, enter <option>serial</option> as an additional
+ option.
+ </para>
+
+ <para>
+ Use <option>display=<replaceable>ip</replaceable>:0</option> to allow remote display forwarding. In this command, <replaceable>ip</replaceable> should be replaced with the IP address of the system on which you want the display to appear.
+ </para>
+
+ <para>
+ On the system you want the display to appear on, you must execute the command <command>xhost +<replaceable>remotehostname</replaceable></command>, where <replaceable>remotehostname</replaceable> is the name of the host from which you are running the original display. Using the command <command>xhost +<replaceable>remotehostname</replaceable></command> limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
+ </para>
+
+ </section>
+
+ <section id="sn-boot-options-update">
+ <title>Updating anaconda</title>
+ <para>
+ You can install Fedora with a newer version of the <application>anaconda</application> installation program than the one supplied on your installation media.
+ </para>
+ <para>
+ The boot option
+ </para>
+<screen>
+ <userinput>linux updates</userinput>
+</screen>
+ <para>
+ presents you with a prompt that asks you for a disk image containing <application>anaconda</application> updates. You do not need to specify this option if you are performing a network installation and have already placed the updates image contents in <filename>rhupdates/</filename> on the server.
+ </para>
+ <para>
+ To load the <application>anaconda</application> updates from a network location instead, use:
+ </para>
+<screen>
+ <userinput>linux updates=</userinput>
+</screen>
+ <para>
+ followed by the URL for the location where the updates are stored.
+ </para>
+ </section>
+
+ <section id="sn-boot-options-installmethod">
+ <title>Specifying the Installation Method</title>
+
+ <para>
+ Use the <option>askmethod</option> option to display additional
+ menus that enable you to specify the installation method and
+ network settings. You may also configure the installation method
+ and network settings at the
+ <prompt>boot:</prompt>
+ prompt itself.
+ </para>
+
+ <para>
+ To specify the installation method from the
+ <prompt>boot:</prompt>
+ prompt, use the <option>repo</option> option. Refer to
+ <xref linkend="tb-installmethods"/> for the supported
+ installation methods.
+ </para>
+ <table id="tb-installmethods" frame='all'><title>Installation methods</title>
+ <tgroup cols='2' align='left' colsep='1' rowsep='1'>
+ <colspec colnum="1" colwidth="1*"/>
+ <colspec colnum="2" colwidth="3*"/>
+ <thead>
+ <row>
+ <entry>Installation method</entry>
+ <entry>Option format</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>DVD drive</entry>
+ <entry><option>repo=cdrom:<replaceable>device</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>Hard Drive</entry>
+ <entry><option>repo=hd:<replaceable>device</replaceable>/<replaceable>path</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>HTTP Server</entry>
+ <entry><option>repo=http://<replaceable>host</replaceable>/<replaceable>path</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>FTP Server</entry>
+ <entry><option>repo=ftp://<replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>host</replaceable>/<replaceable>path</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>NFS Server</entry>
+ <entry><option>repo=nfs:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>ISO images on an NFS Server</entry>
+ <entry><option>repo=nfsiso:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section id="sn-boot-options-network">
+ <title>Manually Configuring the Network Settings</title>
+ <para>
+ By default, the installation system uses DHCP to automatically
+ obtain the correct network settings. To manually configure the
+ network settings yourself, either enter them in the
+ <guilabel>Configure TCP/IP</guilabel> screen, or at the
+ <prompt>boot:</prompt>
+ prompt. You may specify the <option>ip</option> address,
+ <option>netmask</option>, <option>gateway</option>, and
+ <option>dns</option> server settings for the installation system
+ at the prompt. If you specify the network configuration at the
+ <prompt>boot:</prompt>
+ prompt, these settings are used for the installation process,
+ and the <guilabel>Configure TCP/IP</guilabel> screen does not
+ appear.
+ </para>
+
+ <para>
+ This example configures the network settings for an installation
+ system that uses the IP address
+ <systemitem class="ipaddress">192.168.1.10</systemitem>:
+ </para>
+<screen>
+<userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput>
+</screen>
+ <!-- <note>
+ <title>Configuring the Installed System</title>
+
+ <para>
+ Use the Network Configuration screen to specify the network
+ settings for the new system. Refer to
+ <xref linkend="sn-networkconfig-fedora_manual-configuration"/> for more information on
+ configuring the network settings for the installed system.
+ </para>
+ </note> -->
+ </section>
+ </section>
+ <section id="sn-remoteaccess-installation">
+ <title>Enabling Remote Access to the Installation System</title>
+<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ </indexterm>
+ <para>
+ You may access either graphical or text interfaces for the
+ installation system from any other system. Access to a text mode
+ display requires <application>telnet</application>, which is installed by default on Fedora systems. To remotely access the graphical display
+ of an installation system, use client software that supports the
+ VNC (Virtual Network Computing) display protocol.
+ </para>
+ <note>
+ <title>Installing a VNC Client on Fedora</title>
+ <para>
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ <secondary>installing client</secondary>
+ </indexterm>
+ Fedora includes the VNC client <application>vncviewer</application>. To obtain
+ <application>vncviewer</application>, install the
+ <package>tigervnc</package> package.
+ </para>
+ </note>
+ <para>
+ The installation system supports two methods of establishing a VNC
+ connection. You may start the installation, and manually login to
+ the graphical display with a VNC client on another system.
+ Alternatively, you may configure the installation system to
+ automatically connect to a VNC client on the network that is
+ running in <firstterm>listening mode</firstterm>.
+ </para>
+
+ <section id="sn-remoteaccess-installation-vnc">
+ <title>Enabling Remote Access with VNC</title>
+
+ <para>
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ <secondary>enabling</secondary>
+ </indexterm>
+ To enable remote graphical access to the installation system,
+ enter two options at the prompt:
+ </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput>
+</screen>
+ <para>
+ The <option>vnc</option> option enables the VNC service. The
+ <option>vncpassword</option> option sets a password for remote
+ access. The example shown above sets the password as
+ <userinput>qwerty</userinput>.
+ </para>
+
+ <note>
+ <title>VNC Passwords</title>
+
+ <para>
+ The VNC password must be at least six characters long.
+ </para>
+ </note>
+
+ <para>
+ Specify the language, keyboard layout and network settings for
+ the installation system with the screens that follow. You may
+ then access the graphical interface through a VNC client. The
+ installation system displays the correct connection setting for
+ the VNC client:
+ </para>
+<screen>Starting VNC...
+The VNC server is now running.
+Please connect to computer.mydomain.com:1 to begin the install...
+Starting graphical installation...
+Press <enter> for a shell</screen>
+ <para>
+ You may then login to the installation system with a VNC client.
+ To run the <application>vncviewer</application> client on Fedora,
+ choose <menuchoice> <guimenu>Applications</guimenu>
+ <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC
+ Viewer</guimenuitem></menuchoice>, or type the command
+ <application>vncviewer</application> in a terminal window. Enter
+ the server and display number in the <guilabel>VNC
+ Server</guilabel> dialog. For the example above, the
+ <guilabel>VNC Server</guilabel> is
+ <userinput>computer.mydomain.com:1</userinput>.
+ </para>
+ </section>
+
+ <section id="sn-remoteaccess-installation-vnclistener">
+ <title>Connecting the Installation System to a VNC Listener</title>
+
+ <para>
+ To have the installation system automatically connect to a VNC
+ client, first start the client in
+ <indexterm>
+ <primary>VNC (Virtual Network Computing)</primary>
+ <secondary>listening mode</secondary>
+ </indexterm>
+ listening mode. On Fedora systems, use the
+ <option>-listen</option> option to run
+ <application>vncviewer</application> as a listener. In a
+ terminal window, enter the command:
+ </para>
+<screen>
+ <userinput>vncviewer -listen</userinput>
+</screen>
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ By default, <application>vncviewer</application> uses TCP port
+ 5500 when in listening mode. To permit connections to this
+ port from other systems, choose <menuchoice>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>
+ Firewall</guimenuitem> </menuchoice>. Select
+ <guilabel>Other ports</guilabel>, and
+ <guibutton>Add</guibutton>. Enter <userinput>5500</userinput>
+ in the <guilabel>Port(s)</guilabel> field, and specify
+ <userinput>tcp</userinput> as the
+ <guilabel>Protocol</guilabel>.
+ </para>
+ </note>
+
+ <para>
+ Once the listening client is active, start the installation
+ system and set the VNC options at the
+ <prompt>boot:</prompt>
+ prompt. In addition to <option>vnc</option> and
+ <option>vncpassword</option> options, use the
+ <option>vncconnect</option> option to specify the name or IP
+ address of the system that has the listening client. To specify
+ the TCP port for the listener, add a colon and the port number
+ to the name of the system.
+ </para>
+
+ <para>
+ For example, to connect to a VNC client on the system
+ <systemitem
+ class="systemname">desktop.mydomain.com</systemitem>
+ on the port 5500, enter the following at the
+ <prompt>boot:</prompt>
+ prompt:
+ </para>
+<screen>
+<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
+</screen>
+ </section>
+
+
+ <section id="sn-remote-logging">
+ <title>Logging to a Remote System During the Installation</title>
+
+ <para>
+ By default, the installation process sends log messages to the
+ console as they are generated. You may specify that these messages
+ go to a remote system that runs a
+ <indexterm>
+ <primary>syslog</primary>
+ </indexterm>
+ <firstterm>syslog</firstterm> service.
+ </para>
+
+ <para>
+ To configure remote logging, add the <option>syslog</option>
+ option. Specify the IP address of the logging system, and the UDP
+ port number of the log service on that system. By default, syslog
+ services that accept remote messages listen on UDP port 514.
+ </para>
+
+ <para>
+ For example, to connect to a syslog service on the system
+ <systemitem
+ class="ipaddress">192.168.1.20</systemitem>, enter
+ the following at the
+ <prompt>boot:</prompt>
+ prompt:
+ </para>
+<screen>
+<userinput>linux syslog=<replaceable>192.168.1.20:514</replaceable></userinput>
+</screen>
+ <section id="sn-remote-logging-logserver">
+ <title>Configuring a Log Server</title>
+
+ <para>
+ Fedora uses <command>rsyslog</command> to provide a syslog
+ service. The default configuration of <command>rsyslog</command>
+ rejects messages from remote systems.
+ </para>
+
+ <warning>
+ <title>Only Enable Remote Syslog Access on Secured Networks</title>
+
+ <para>
+ The <command>rsyslog</command> configuration detailed below
+ does not make use of any of the security measures available
+ in <command>rsyslog</command> Crackers may slow or crash systems
+ that permit access to the logging service, by sending large
+ quantities of false log messages. In addition, hostile users may
+ intercept or falsify messages sent to the logging service over the
+ network.
+ </para>
+ </warning>
+
+ <para>
+ To configure a Fedora system to accept log messages from other
+ systems on the network, edit the file
+ <filename>/etc/rsyslog.conf</filename>. You must use
+ <systemitem class="username">root</systemitem> privileges to
+ edit the file <filename>/etc/rsyslog.conf</filename>. Uncomment the
+ following lines by removing the hash preceding them:</para>
+<screen><computeroutput>$ModLoad imudp.so</computeroutput>
+ <computeroutput>$UDPServerRun 514</computeroutput></screen>
+ <para>
+ Restart the <command>rsyslog</command> service to apply the
+ change:
+ </para>
+<screen>
+<userinput>su -c '/sbin/service rsyslog restart'</userinput>
+</screen>
+ <para>
+ Enter the <systemitem class="username">root</systemitem>
+ password when prompted.
+ </para>
+
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ By default, the syslog service listens on UDP port 514. To
+ permit connections to this port from other systems, choose
+ <menuchoice> <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>
+ Firewall</guimenuitem> </menuchoice>. Select
+ <guilabel>Other ports</guilabel>, and
+ <guibutton>Add</guibutton>. Enter <userinput>514</userinput>
+ in the <guilabel>Port(s)</guilabel> field, and specify
+ <userinput>udp</userinput> as the
+ <guilabel>Protocol</guilabel>.
+ </para>
+ </note>
+ </section>
+ </section>
+ <section id="sn-automating-installation">
+ <xi:include href="Automating_installation-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- Automating the Installation with Kickstart -->
+
+ <xi:include href="Automating_installation-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- A Kickstart file specifies settings for an installation -->
+
+ <note>
+ <xi:include href="Automating_installation-title-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- Every installation produces a Kickstart file -->
+
+ <xi:include href="Automating_installation-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- The Fedora installation system automatically writes -->
+
+ </note>
+ <xi:include href="Important-Kickstart_and_Firstboot.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <para>
+ Fedora includes a graphical application to create and modify
+ Kickstart files by selecting the options that you require. Use the
+ package <filename>system-config-kickstart</filename> to install
+ this utility. To load the Fedora Kickstart editor, choose
+ <menuchoice> <guimenu>Applications</guimenu> <guisubmenu>System
+ Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
+ </para>
+
+ <para>
+ Kickstart files list installation settings in plain text, with one
+ option per line. This format lets you modify your Kickstart files
+ with any text editor, and write scripts or applications that
+ generate custom Kickstart files for your systems.
+ </para>
+
+ <para>
+ To automate the installation process with a Kickstart file, use
+ the <option>ks</option> option to specify the name and location of
+ the file:
+ </para>
+<screen>
+ <userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
+</screen>
+ <para>
+ You may use Kickstart files that are held on either removable
+ storage, a hard drive, or a network server. Refer to
+ <xref linkend="tb-kssources"/> for the supported Kickstart
+ sources.
+ </para>
+
+ <table id="tb-kssources" frame='all'><title>Kickstart sources</title>
+ <tgroup cols='2' align='left' colsep='1' rowsep='1'>
+ <colspec colnum="1" colwidth="1*"/>
+ <colspec colnum="2" colwidth="3*"/>
+ <thead>
+ <row>
+ <entry>Kickstart source</entry>
+ <entry>Option format</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>DVD drive</entry>
+ <entry><option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>Hard Drive</entry>
+ <entry><option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>Other Device</entry>
+ <entry><option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>HTTP Server</entry>
+ <entry><option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>FTP Server</entry>
+ <entry><option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ <row>
+ <entry>NFS Server</entry>
+ <entry><option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ To obtain a Kickstart file from a script or application on a Web
+ server, specify the URL of the application with the
+ <option>ks=</option> option. If you add the option
+ <option>kssendmac</option>, the request also sends HTTP headers to
+ the Web application. Your application can use these headers to
+ identify the computer. This line sends a request with headers to
+ the application
+ <wordasword>http://server.mydomain.com/kickstart.cgi</wordasword>:
+ </para>
+<screen>
+<userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput>
+</screen>
+ </section>
+ <section id="sn-bootoptions-hardware">
+ <title>Enhancing Hardware Support</title>
+
+ <para>
+ By default, Fedora attempts to automatically detect and configure
+ support for all of the components of your computer. Fedora supports
+ the majority of hardware in common use with the software
+ <firstterm>drivers</firstterm> that are included with the
+ operating system. To support other devices you may supply
+ additional drivers during the installation process, or at a later
+ time.
+ </para>
+
+ <section id="sn-bootoptions-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>
+ <note>
+ <title>Check the Release Notes</title>
+ <para>
+ Refer to the Release Notes for information on known issues
+ with specific devices.
+ </para>
+ </note>
+ <para>
+ To override the automatic hardware detection, use one or more of
+ the following options:
+ </para>
+
+ <table id="tb-hardwareoptions" frame='all'><title>Hardware Options</title>
+ <tgroup cols='2' align='left' colsep='1' rowsep='1'>
+ <colspec colnum="1" colwidth="3*"/>
+ <colspec colnum="2" colwidth="2*"/>
+ <thead>
+ <row>
+ <entry>Compatibility</entry>
+ <entry>Option</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Disable all hardware detection</entry>
+ <entry><option>noprobe</option></entry>
+ </row>
+ <row>
+ <entry>Disable graphics, keyboard, and mouse detection</entry>
+ <entry><option>headless</option></entry>
+ </row>
+ <row>
+ <entry>Disable probing for SCSI and RAID storage hardware</entry>
+ <entry><option>nostorage</option></entry>
+ </row>
+ <row>
+ <entry>Disable passing keyboard and mouse information to stage 2 of the installation program</entry>
+ <entry><option>nopass</option></entry>
+ </row>
+ <row>
+ <entry>Use basic VESA driver for video</entry>
+ <entry><option>xdriver=vesa</option></entry>
+ </row>
+ <row>
+ <entry>Disable shell access on virtual console 2 during installation</entry>
+ <entry><option>noshell</option></entry>
+ </row>
+ <row>
+ <entry>Disable advanced configuration and power interface (ACPI)</entry>
+ <entry><option>acpi=off</option></entry>
+ </row>
+ <row>
+ <entry>Disable machine check exception (MCE) CPU self-diagnosis.</entry>
+ <entry><option>nomce</option></entry>
+ </row>
+ <row>
+ <entry>Disable non-uniform menory access on the AMD64 architecture</entry>
+ <entry><option>numa-off</option></entry>
+ </row>
+ <row>
+ <entry>Force kernel to detect a specific amount of memory, where <replaceable>xxx</replaceable> is a value in megabytes</entry>
+ <entry><option>mem=<replaceable>xxx</replaceable>m</option></entry>
+ </row>
+ <row>
+ <entry>Enable DMA only for IDE and SATA drives</entry>
+ <entry><option>libata.dma=1</option></entry>
+ </row>
+ <row>
+ <entry>Disable BIOS-assisted RAID</entry>
+ <entry><option>nodmraid</option></entry>
+ </row>
+ <row>
+ <entry>Disable Firewire device detection</entry>
+ <entry><option>nofirewire</option></entry>
+ </row>
+ <row>
+ <entry>Disable parallel port detection</entry>
+ <entry><option>noparport</option></entry>
+ </row>
+ <row>
+ <entry>Disable PC Card (PCMCIA) device detection</entry>
+ <entry><option>nopcmcia</option></entry>
+ </row>
+ <row>
+ <entry>Disable USB storage device detection</entry>
+ <entry><option>nousbstorage</option></entry>
+ </row>
+ <row>
+ <entry>Disable all USB device detection</entry>
+ <entry><option>nousb</option></entry>
+ </row>
+ <row>
+ <entry>Disable all probing of network hardware</entry>
+ <entry><option>nonet</option></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note>
+ <title>Additional Screen</title>
+
+ <para>
+ The <option>isa</option> option causes the system to display
+ an additional text screen at the beginning of the installation
+ process. Use this screen to configure the ISA devices on your
+ computer.
+ </para>
+ </note>
+
+ <important>
+ <para>
+ Other kernel boot options have no particular meaning for <application>anaconda</application> and do not affect the installation process. However, if you use these options to boot the installation system, <application>anaconda</application> will preserve them in the bootloader configuration.
+ </para>
+ </important>
+
+ </section>
+ </section>
+
+ <section id="sn-boot-modes">
+ <title>Using the Maintenance Boot Modes</title>
+
+
+ <section id="sn-memtest">
+ <title>Loading the Memory (RAM) Testing Mode</title>
+
+ <para>
+ Faults in memory modules may cause your system to freeze or
+ crash unpredictably. In some cases, memory faults may only cause
+ errors with particular combinations of software. For this
+ reason, you should test the memory of a computer before you
+ install Fedora for the first time, even if it has previously run
+ other operating systems.
+ </para>
+
+ <para>
+ Fedora includes the <application>Memtest86+</application>
+ memory testing application. To boot your computer in
+ <indexterm>
+ <primary>memory testing mode</primary>
+ </indexterm> memory testing mode, choose <guimenuitem>Memory
+ test</guimenuitem> at the boot menu. The first test starts
+ immediately. By default, <application>Memtest86+</application>
+ carries out a total of ten tests.
+ </para>
+
+ <para>
+ In most cases, a single successful pass with <application>Memtest86+</application> is sufficient to verify that your RAM is in good condition. In some rare circumstances, however, errors that went undetected on the first pass might appear on subsequent passes. To perform a thorough test of the RAM on an important system, leave <application>Memtest86+</application> running overnight or for a few days.
+ </para>
+ <para>
+ For more information on using <application>Memtest86+</application>, refer to the <citetitle>Memtest86+ FAQ</citetitle> available at <ulink url="http://forum.canardpc.com/showthread.php?t=28864"></ulink>.
+ </para>
+ <para>
+ To halt the tests and reboot your computer, enter
+ <keycap>Esc</keycap> at any time.
+ </para>
+ </section>
+
+ <section id="sn-boot-mediacheck">
+ <title>Verifying boot media</title>
+ <para>
+ You can test the integrity of an ISO-based installation source before using it to install Fedora. These sources include DVD, and ISO images stored on a hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation.
+ </para>
+ <para>
+ Fedora offers you two ways to test installation ISOs:
+ </para>
+ <itemizedlist>
+<!-- FIG <listitem>
+ <para>
+ select the <guilabel>Verify and Boot</guilabel> option on the Fedora Live CD. To access the Live CD boot menu, press any key within ten seconds of the splash screen appearing.
+ </para>
+ </listitem> -->
+ <listitem>
+ <para>
+ select <guilabel>OK</guilabel> at the prompt to test the media before installation when booting from the Fedora DVD
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ boot Fedora with the option <option>mediacheck</option> option.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sn-mode-rescue">
+ <title>Booting Your Computer with the Rescue Mode</title>
+ <indexterm>
+ <primary>rescue mode</primary>
+ </indexterm>
+ <para>
+ You may boot a command-line Linux system from either a
+ <indexterm>
+ <primary>rescue discs</primary>
+ </indexterm>
+ rescue disc or an installation disc, without installing
+ Fedora on the computer. This enables you to use the utilities and
+ functions of a running Linux system to modify or repair systems
+ that are already installed on your computer.
+ </para>
+
+ <para>
+ The rescue disc starts the rescue mode system by default. To
+ load the rescue system with the installation disc, choose
+ <guimenuitem>Rescue installed system</guimenuitem> from the boot
+ menu.
+ </para>
+ <para>
+ Specify the language, keyboard layout and network settings for
+ the rescue system with the screens that follow. The final setup
+ screen configures access to the existing system on your
+ computer.
+ </para>
+
+ <para>
+ By default, rescue mode attaches an existing operating system to
+ the rescue system under the directory
+ <filename>/mnt/sysimage/</filename>.
+ </para>
+ </section>
+
+ <section id="sn-mode-upgradeany">
+ <title>Upgrading your computer</title>
+
+ <para>
+ A previous boot option, <option>upgrade</option>, has been superceded by a stage in the installation process where the installation program prompts you to upgrade or reinstall earlier versions of Fedora that it detects on your system.
+ </para>
+
+ <para>
+ However, the installation program may not correctly detect a previous version of Fedora if the contents of the <filename>/etc/redhat-release</filename> file have changed. The boot option <option>upgradeany</option> relaxes the test that the installation program performs and allows you to upgrade a Fedora installation that the installation program has not correctly identified.
+ </para>
+
+ </section>
+ </section>
+
+</chapter>
+
+<!--
+Local variables:
+mode: xml
+fill-column: 72
+End:
+-->
+
More information about the docs-commits
mailing list