install-guide rpm-info.xml, NONE, 1.1 fedora-install-guide-adminoptions-en.xml, 1.5, 1.6 fedora-install-guide-en.xml, 1.37, 1.38
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Mon Jan 16 00:23:08 UTC 2006
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30321
Modified Files:
fedora-install-guide-adminoptions-en.xml
fedora-install-guide-en.xml
Added Files:
rpm-info.xml
Log Message:
- Updated to support new build requirements.
- Reworked Remote Acces and Kickstart text.
- Added material on Driver Disks.
--- NEW FILE rpm-info.xml ---
<rpm-info>
<colophon>
<worker surname="Ellis" firstname="Stuart" othername="" id="StuartEllis" email="stuart at elsn.org" wholename="Stuart Ellis" initials="StuartEllis"/>
<worker surname="Frields" firstname="Paul" othername="W." id="PaulFrields" email="stickster at gmail.com" wholename="Paul W. Frields" initials="PaulFrields"/>
</colophon>
<license>
<rights>GNU FDL</rights>
<version>1.0</version>
</license>
<copyright>
<year>2006</year>
<holder>Red Hat, Inc.</holder>
<holder>Stuart Ellis</holder>
<holder>Paul W. Frields</holder>
</copyright>
<titles>
<translation lang="en">
<title>Fedora Core 5 Installation Guide - BETA</title>
<desc>Provides documentation for the installation process.</desc>
</translation>
<!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
</titles>
<changelog order="newest-first">
<revision date="2006-01-16" number="1.13" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Added information on driver disks.</details>
</revision>
<revision date="2006-01-11" number="1.12" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Minor fixes to Boot Options.</details>
</revision>
<revision date="2006-01-09" number="1.11" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Expanded Technical References section.</details>
</revision>
<revision date="2005-12-22" number="1.1" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Amended Management Options section.</details>
</revision>
<revision date="2005-12-22" number="1.0.9" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Updated Management Options section.</details>
</revision>
<revision date="2005-12-14" number="1.0.8" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Added Technical References section.</details>
</revision>
<revision date="2005-12-12" number="1.0.7" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Added Management Options section.</details>
</revision>
<revision date="2005-12-10" number="1.0.6" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Updated sections on installation methods.</details>
</revision>
<revision date="2005-12-08" number="1.0.5" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Updated partitioning section.</details>
</revision>
<revision date="2005-12-06" number="1.0.4" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Added material on updating the new installation.</details>
</revision>
<revision date="2005-12-04" number="1.0.3" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Reorganized to match anaconda screens.</details>
</revision>
<revision date="2005-11-25" number="1.0.2" role="doc">
<author worker="PaulWFrields"/>
<details lang="en">Additional reorganization for clarity; information on /home partition</details>
</revision>
<revision date="2005-11-20" number="1.0.1rc1" role="doc">
<author worker="PaulWFrields"/>
<details lang="en">Reorganization of introductory material</details>
</revision>
<revision date="2005-06-10" number="1.0" role="doc">
<author worker="KarstenWade"/>
<details lang="en">Release version</details>
</revision>
<revision date="2005-06-08" number="1.0rc1" role="doc">
<author worker="KarstenWade"/>
<details lang="en">Publication edit and declaration of release candidate</details>
</revision>
<revision date="2005-05-15" number="0.7" role="doc">
<author worker="StuartEllis"/>
<details lang="en">Additional style editing and indexing</details>
</revision>
<revision date="2005-05-10" number="0.6.3" role="doc">
<author worker="PaulWFrields"/>
<details lang="en">Style editing, removed "nextsteps" from build</details>
</revision>
<revision date="2005-04-30" number="0.6.2" role="doc">
<author worker="StuartEllis"/>
<details lang="en">First commission to CVS, plus very minor parent file edits</details>
</revision>
</changelog>
</rpm-info>
Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-adminoptions-en.xml 11 Jan 2006 22:40:26 -0000 1.5
+++ fedora-install-guide-adminoptions-en.xml 16 Jan 2006 00:23:00 -0000 1.6
@@ -44,6 +44,11 @@
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">
@@ -53,7 +58,8 @@
You may configure the installation system without affecting the
final &FED; system. The
<prompt>boot:</prompt>
- prompt enables you to configure the following:
+ prompt enables you to specify a number of settings for the
+ installation system. These include:
</para>
<itemizedlist>
@@ -78,7 +84,7 @@
</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>
@@ -194,14 +200,19 @@
</tgroup>
</table>
<para>
- By default, the installation system uses DHCP to obtain the
- correct network settings. To override DHCP, specify the settings
- at the
+ 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 configure the <option>ip</option> address,
+ 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.
+ <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>
@@ -215,23 +226,36 @@
<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 the interface for the installation system from
- any other system. Access to a text mode display requires
- <command>telnet</command>, which is installed by default on
- &FED; systems. To remotely access the graphical display of an
- installation system, you must use client software that supports
- the VNC (Virtual Network Computing) display protocol.
+ 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</title>
+ <title>Installing a VNC Client on &FED;</title>
<para>
- To install the <application>vncviewer</application> VNC client
- on &FED;, use the package <filename>vnc</filename>.
+ &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>
@@ -268,8 +292,9 @@
Press <enter> for a shell]]></computeroutput>
</screen>
<para>
- To run the <application>vncviewer</application> client, choose
- <menuchoice> <guimenu>Applications</guimenu>
+ 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
@@ -280,21 +305,49 @@
</para>
<para>
- Alternatively, you may automatically connect the interface for
- the installation system to an active VNC client, with the
- <option>vncconnect</option> option. This requires the VNC client
- to run in <emphasis>listening</emphasis> mode. The client system
- must also allow connections on a known TCP port. By default, the
- <application>vncviewer</application> utility listens on TCP port
- <systemitem>5500</systemitem>.
+ 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>
+
+ <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>
- To connect to a VNC client on the system
+ For example, 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
+ on the port <systemitem>5500</systemitem>, enter the following
+ at the
<prompt>boot:</prompt>
prompt:
</para>
@@ -302,14 +355,6 @@
<userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
</screen>
<para>
- On &FED; systems, use the <option>-listen</option> option to
- start the <application>vncviewer</application> VNC client in
- listening mode. In a terminal window, enter the command:
- </para>
-<screen>
- <userinput>vncviewer -listen</userinput>
-</screen>
- <para>
To enable remote access to a text mode installation, use the
<option>telnet</option> option at the
<prompt>boot:</prompt>
@@ -338,17 +383,51 @@
<para>
A <firstterm>Kickstart</firstterm> file specifies settings for
- an installation. To automate the installation process, use the
- <option>ks</option> option to provide the name and location of a
- Kickstart file:
+ 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>.
+ </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>
<screen>
<userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
</screen>
<para>
- You may use Kickstart files that are located on either removable
- storage, or a hard drive, or on a network server. Refer to
- <xref linkend="tb-kssources"/> for the supported Kickstart
+ 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">
@@ -438,31 +517,14 @@
</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
+ 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>
@@ -471,173 +533,341 @@
</section>
<section id="sn-bootoptions-hardware">
- <title>Hardware Compatibility Options</title>
+ <title>Hardware Support</title>
<para>
- By default, &FED; detects and configures all of the components
- of your computer. To override the automatic hardware detection,
- use the following options:
+ 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>
- <table id="tb-hwoptions">
- <title>Hardware Options</title>
- <tgroup cols="2">
- <colspec colnum="1" colname="Compatibility Setting"/>
- <colspec colnum="2" colname="Option"/>
- <thead>
- <row>
- <entry>Compatibility Setting</entry>
- <entry>Option</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <para>
- Disable all hardware detection
- </para>
- </entry>
- <entry>
- <para>
- <option>noprobe</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable graphics, keyboard, and mouse detection
- </para>
- </entry>
- <entry>
- <para>
- <option>headless</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable mainboard APIC
- </para>
- </entry>
- <entry>
- <para>
- <option>noapic</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable power management (ACPI)
- </para>
- </entry>
- <entry>
- <para>
- <option>acpi=off</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable automatic monitor detection (DDC)
- </para>
- </entry>
- <entry>
- <para>
- <option>skipddc</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable Firewire device detection
- </para>
- </entry>
- <entry>
- <para>
- <option>nofirewire</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable parallel port detection
- </para>
- </entry>
- <entry>
- <para>
- <option>noparport</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable PC Card (PCMCIA) device detection
- </para>
- </entry>
- <entry>
- <para>
- <option>nopcmcia</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable USB storage device detection
- </para>
- </entry>
- <entry>
- <para>
- <option>nousbstorage</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Disable all USB device detection
- </para>
- </entry>
- <entry>
- <para>
- <option>nousb</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Force Firewire device detection
- </para>
- </entry>
- <entry>
- <para>
- <option>firewire</option>
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Prompt user for ISA device configuration
- </para>
- </entry>
- <entry>
- <para>
- <option>isa</option>
- </para>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
+
+ <section 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>
+ 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>
+<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>
+ 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>
+ <para>
+ <option>dd</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ HTTP Server
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>dd=<replaceable>http://server.mydomain.com/directory/drivers.img</replaceable></option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ FTP Server
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>dd=<replaceable>ftp://server.mydomain.com/directory/drivers.img</replaceable></option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ NFS Server
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>dd=<replaceable>nfs:server.mydomain.com:/directory/drivers.img</replaceable></option>
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <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>
+ 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:
+ </para>
+ <table id="tb-hwoptions">
+ <title>Hardware Options</title>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="Compatibility Setting"/>
+ <colspec colnum="2" colname="Option"/>
+ <thead>
+ <row>
+ <entry>Compatibility Setting</entry>
+ <entry>Option</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>
+ Disable all hardware detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>noprobe</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable graphics, keyboard, and mouse detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>headless</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable mainboard APIC
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>noapic</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable power management (ACPI)
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>acpi=off</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable automatic monitor detection (DDC)
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>skipddc</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable Firewire device detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>nofirewire</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable parallel port detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>noparport</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable PC Card (PCMCIA) device detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>nopcmcia</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable USB storage device detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>nousbstorage</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Disable all USB device detection
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>nousb</option>
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>
+ Enable software RAID controller support
+ </para>
+ </entry>
+ <entry>
+ <para>
+ <option>dmraid</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>
+<!-- SE: To be useful, this needs an explanation of how it differs from providing driver disks.
<section id="sn-mode-expert">
<title>Installing &FC; with Expert Mode</title>
@@ -654,11 +884,8 @@
<screen>
<userinput>linux expert</userinput>
</screen>
- <para>
- <remark role="FIXME">May need an explanation of driver disks.
- </remark>
- </para>
</section>
+-->
</section>
<section id="sn-memtest">
<title>Performing a Memory (RAM) Test</title>
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- fedora-install-guide-en.xml 11 Jan 2006 22:40:26 -0000 1.37
+++ fedora-install-guide-en.xml 16 Jan 2006 00:23:00 -0000 1.38
@@ -6,17 +6,19 @@
<!ENTITY DOCNAME "fedora-install-guide">
<!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.11">
-<!ENTITY DOCDATE "2006-01-11">
+<!ENTITY DOCVERSION "1.13">
+<!ENTITY DOCDATE "2006-01-16">
<!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.12"> <!-- what's this for again? -->
-
+<!ENTITY DOCLOCALVER "1.13"> <!-- what's this for again? -->
+<!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" >
<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">
<!ENTITY BEGINNINGINSTALLATION SYSTEM "fedora-install-guide-beginninginstallation-en.xml">
@@ -40,204 +42,8 @@
]>
<book id="book" lang="en">
- <bookinfo>
- <title>&FC; &FCLOCALVER; &IG; - BETA</title>
- <!-- Remove DOCLOCALVER for release -->
- <copyright>
- <year>2006</year>
- <holder>&FORMAL-RHI;</holder>
- <holder>Stuart Ellis</holder>
- <holder>Paul W. Frields</holder>
- </copyright>
- <authorgroup>
- <author>
- <surname>Ellis</surname>
- <firstname>Stuart</firstname>
- </author>
- <author>
- <surname>Frields</surname>
- <firstname>Paul</firstname>
- <othername role="mi">W.</othername>
- </author>
- </authorgroup>
- &LEGALNOTICE;
- <revhistory>
- <revision>
- <revnumber>0.6.2</revnumber>
- <date>2005-04-30</date>
- <authorinitials>StuartEllis</authorinitials>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- First commission to CVS, plus very minor parent file edits
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>0.6.3</revnumber>
- <date>2005-05-10</date>
- <authorinitials>PaulWFrields</authorinitials>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Style editing, removed "nextsteps" from build
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>0.7</revnumber>
- <date>2005-05-15</date>
- <authorinitials>StuartEllis</authorinitials>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- Additional style editing and indexing
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0rc1</revnumber>
- <date>2005-06-08</date>
- <authorinitials>KarstenWade</authorinitials>
- <revdescription>
- <para>
- Publication edit and declaration of release candidate
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0</revnumber>
- <date>2005-06-10</date>
- <authorinitials>KarstenWade</authorinitials>
- <revdescription>
- <para>
- Release version
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.1rc1</revnumber>
- <date>2005-11-20</date>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- Reorganization of introductory material
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.2</revnumber>
- <date>2005-11-25</date>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- Additional reorganization for clarity; information on
- <filename>/home</filename> partition
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.3</revnumber>
- <date>2005-12-04</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Reorganized to match anaconda screens.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.4</revnumber>
- <date>2005-12-06</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Added material on updating the new installation.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.5</revnumber>
- <date>2005-12-08</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Updated partitioning section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.6</revnumber>
- <date>2005-12-10</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Updated sections on installation methods.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.7</revnumber>
- <date>2005-12-12</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Added Management Options section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.8</revnumber>
- <date>2005-12-14</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Added Technical References section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.0.9</revnumber>
- <date>2005-12-22</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Updated Management Options section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.1</revnumber>
- <date>2005-12-22</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Amended Management Options section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.11</revnumber>
- <date>2006-01-09</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Expanded Technical References section.
- </para>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1.12</revnumber>
- <date>2006-01-11</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Minor fixes to Boot Options.
- </para>
- </revdescription>
- </revision>
- </revhistory>
- </bookinfo>
+
+ &FDP-INFO;
&INTRODUCTION;
More information about the Fedora-docs-commits
mailing list