en-US/adminoptions.xml en-US/Advice_on_Partitions.xml en-US/Disk_Partitioning_Setup_common-warning-1.xml en-US/Disk_Partitioning_X86_Partitions.xml en-US/Driver_Disk_x86_ppc-para-1.xml en-US/Driver_Disk_x86_ppc-section-2.xml en-US/Driver_Disk-x86.xml en-US/Installation_Guide.xml en-US/pxe-server-manual.xml en-US/Steps_Cdrom-x86.xml en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml en-US/X86_Bootloader.xml
Rüdiger Landmann
rlandmann at fedoraproject.org
Wed Apr 15 01:04:55 UTC 2009
en-US/Advice_on_Partitions.xml | 16 ++---
en-US/Disk_Partitioning_Setup_common-warning-1.xml | 2
en-US/Disk_Partitioning_X86_Partitions.xml | 2
en-US/Driver_Disk-x86.xml | 15 +++--
en-US/Driver_Disk_x86_ppc-para-1.xml | 2
en-US/Driver_Disk_x86_ppc-section-2.xml | 2
en-US/Installation_Guide.xml | 2
en-US/Steps_Cdrom-x86.xml | 48 +++--------------
en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml | 8 +-
en-US/X86_Bootloader.xml | 17 +++---
en-US/adminoptions.xml | 25 --------
en-US/pxe-server-manual.xml | 32 +++++------
12 files changed, 63 insertions(+), 108 deletions(-)
New commits:
commit 63bde6d9bddff558e5e3e7efa7a6da6fdb0fde6a
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Wed Apr 15 11:04:42 2009 +1000
Corrections and updates per feedback from anaconda team
diff --git a/en-US/Advice_on_Partitions.xml b/en-US/Advice_on_Partitions.xml
index 36d4f33..564fc6e 100644
--- a/en-US/Advice_on_Partitions.xml
+++ b/en-US/Advice_on_Partitions.xml
@@ -21,7 +21,7 @@
</listitem>
<listitem>
<para>Each kernel installed on your system requires
- approximately 6 MB on the <filename
+ approximately 10 MB on the <filename
class="partition">/boot</filename> partition. Unless you
plan to install a great many kernels, the default partition
size of 100 MB for <filename
@@ -60,6 +60,10 @@
plan to use your Fedora system to learn software development
skills, you may want to at least double this
allocation.</para>
+ <important>
+ <title>Do not place <filename class="directory">/usr</filename> on a separate partition</title>
+ <para>If <filename class="directory">/usr</filename> is on a separate partition from <filename class="directory">/</filename>, the boot process becomes much more complex, and in some situations (like installations on iSCSI drives), might not work at all. </para>
+ </important>
</listitem>
<listitem>
<para>Consider leaving a portion of the space in an LVM volume
@@ -129,15 +133,7 @@
<tbody>
<row>
<entry><filename class="partition">/</filename></entry>
- <entry>3 GB ext4</entry>
- </row>
- <row>
- <entry><filename class="partition">/usr</filename></entry>
- <entry>8 GB ext4</entry>
- </row>
- <row>
- <entry><filename class="partition">/usr/local</filename></entry>
- <entry>2 GB ext4</entry>
+ <entry>13 GB ext4</entry>
</row>
<row>
<entry><filename class="partition">/var</filename></entry>
diff --git a/en-US/Disk_Partitioning_Setup_common-warning-1.xml b/en-US/Disk_Partitioning_Setup_common-warning-1.xml
index 524884c..ace5575 100644
--- a/en-US/Disk_Partitioning_Setup_common-warning-1.xml
+++ b/en-US/Disk_Partitioning_Setup_common-warning-1.xml
@@ -6,6 +6,6 @@
<title>Warning</title>
<para>
- The <!-- (RHEL) <application>Red Hat Update Agent</application> --> <application>yum</application> update software downloads updated packages to <filename>/var/cache/yum/</filename> by default. If you partition the system manually, and create a separate <filename>/var/</filename> partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
+ The <!-- (RHEL) <application>Red Hat Update Agent</application> --> <application>PackageKit</application> update software downloads updated packages to <filename>/var/cache/yum/</filename> by default. If you partition the system manually, and create a separate <filename>/var/</filename> partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.
</para>
</warning>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_X86_Partitions.xml b/en-US/Disk_Partitioning_X86_Partitions.xml
index 0f35b05..8f8942f 100644
--- a/en-US/Disk_Partitioning_X86_Partitions.xml
+++ b/en-US/Disk_Partitioning_X86_Partitions.xml
@@ -107,7 +107,7 @@
</row>
<row>
<entry><filename class="directory">/usr</filename></entry>
- <entry>250 MB</entry>
+ <entry>250 MB, but avoid placing this on a separate partition</entry>
</row>
<row>
<entry><filename class="directory">/tmp</filename></entry>
diff --git a/en-US/Driver_Disk-x86.xml b/en-US/Driver_Disk-x86.xml
index a6941fc..f825089 100644
--- a/en-US/Driver_Disk-x86.xml
+++ b/en-US/Driver_Disk-x86.xml
@@ -25,19 +25,24 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-para-1.xml"/>
- <itemizedlist>
+ <itemizedlist>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-2.xml"/>
+ <!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-2.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-3.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-3.xml"/> -->
<listitem>
<para>
- If you run the installation program by entering <userinput>linux dd</userinput> at the installation boot prompt <!-- (RHEL) (Itanium users should enter <userinput>elilo linux dd</userinput>) -->
+ There is no driver available for a piece of hardware that is necessary for installation to proceed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you run the installation program by entering <userinput>linux dd</userinput> at the installation boot prompt. <!-- (RHEL) (Itanium users should enter <userinput>elilo linux dd</userinput>) -->
</para>
</listitem>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-4.xml"/>
+ <!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Driver_Disk_x86_ppc-listitem-4.xml"/>-->
</itemizedlist>
</section>
diff --git a/en-US/Driver_Disk_x86_ppc-para-1.xml b/en-US/Driver_Disk_x86_ppc-para-1.xml
index 243ad33..1c48c1b 100644
--- a/en-US/Driver_Disk_x86_ppc-para-1.xml
+++ b/en-US/Driver_Disk_x86_ppc-para-1.xml
@@ -3,5 +3,5 @@
]>
<para>
- While the Fedora installation program is loading, a screen may appear asking you for driver media. The driver media screen is most often seen in the following scenarios:
+ While the Fedora installation program is loading, a screen may appear asking you for driver media. The driver media screen is most often seen in the following scenarios:
</para>
\ No newline at end of file
diff --git a/en-US/Driver_Disk_x86_ppc-section-2.xml b/en-US/Driver_Disk_x86_ppc-section-2.xml
index 45ba2b2..e946a5c 100644
--- a/en-US/Driver_Disk_x86_ppc-section-2.xml
+++ b/en-US/Driver_Disk_x86_ppc-section-2.xml
@@ -10,7 +10,7 @@
</para>
<para>
- Driver media is used if you need access to a particular device to install Fedora. Drivers can be used for network (NFS) installations, installations using a PCMCIA or block device, non-standard or very new optical drives, SCSI adapters, NICs, and other uncommon devices.
+ Driver media is used if you need access to a particular device to install Fedora. Drivers can be used for <!--network (NFS) installations, installations using a PCMCIA or block device,--> non-standard, <!--or--> very new, <!--optical drives, SCSI adapters, NICs, and other--> or uncommon devices.
</para>
<note>
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
index a652e1c..33d90dc 100644
--- a/en-US/Installation_Guide.xml
+++ b/en-US/Installation_Guide.xml
@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<book status="draft">
+<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
diff --git a/en-US/Steps_Cdrom-x86.xml b/en-US/Steps_Cdrom-x86.xml
index 5b33861..9bc6ebf 100644
--- a/en-US/Steps_Cdrom-x86.xml
+++ b/en-US/Steps_Cdrom-x86.xml
@@ -79,46 +79,20 @@
<primary>boot CD-ROM</primary>
<secondary>creating</secondary>
</indexterm>
+ <indexterm significance="normal">
+ <primary><filename>boot.iso</filename></primary>
+ </indexterm>
+
<para>
- <command>isolinux</command> <!-- (RHEL) (not available for Itanium systems) is used for booting the Fedora installation CD.-->To create your own CD-ROM to boot the installation program, use the following instructions:
- </para>
-
- <para>
- Copy the <filename>isolinux/</filename> directory from the Fedora DVD or CD #1 into a temporary directory (referred to here as <filename><<replaceable>path-to-workspace</replaceable>></filename>) using
- the following command:
- </para>
-<screen>
-<command>cp -r <filename><<replaceable>path-to-cd</replaceable>>/isolinux/</filename> <filename><<replaceable>path-to-workspace</replaceable>></filename></command>
-</screen>
- <para>
- Change directories to the <filename><<replaceable>path-to-workspace</replaceable>></filename> directory you have created:
- </para>
-<screen>
-<command>cd <filename><<replaceable>path-to-workspace</replaceable>></filename></command>
-</screen>
- <para>
- Make sure the files you have copied have appropriate permissions:
- </para>
-<screen>
-<command>chmod u+w isolinux/*</command>
-</screen>
- <para>
- Finally, issue the following command to create the ISO image file:
+ The <filename>images/</filename> directory on the installation DVD contains the <filename>boot.iso</filename> file. This file is an image of a disc that you can burn to a CD and use to boot the installation program. To use this boot CD, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so.
</para>
-<screen>
-mkisofs -o file.iso -b isolinux.bin -c boot.cat -no-emul-boot \
--boot-load-size 4 -boot-info-table -R -J -v -T isolinux/
-</screen>
- <note>
- <title>Note</title>
-
+
+ <important>
+ <title>Choose an option to burn a CD from an image</title>
<para>
- The above command was split into two lines for printing purposes only. When you execute this command, be sure to type it as a single command, all on the same line.
+ When you burn the <filename>boot.iso</filename> image, make sure that you select the option to <literal>burn an image file to disc</literal> in your CD burning software. The exact wording of this option varies, depending on the software that you use, but should contain the word "image". Note that not all CD burning software includes this option. In particular, the CD burning software built into Microsoft Windows XP and Windows Vista does not offer this capability. There are many programs available that add this capability to Windows operating systems; <application>Infrarecorder</application> is a free and open-source example available from <ulink url="http://www.infrarecorder.org/">http://www.infrarecorder.org/</ulink>.
</para>
- </note>
-
- <para>
- Burn the resulting ISO image (named <filename>file.iso</filename> and located in <filename><<replaceable>path-to-workspace</replaceable>></filename>) to a CD-ROM as you normally would.
- </para>
+ </important>
+
</section>
</section>
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml b/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml
index d34b6f2..640b498 100644
--- a/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml
+++ b/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml
@@ -6,9 +6,9 @@
<title>Preparing for FTP and HTTP installation</title>
<para>
- For FTP and HTTP installation, the iso image or images should be mounted via loopback in the publicly available directory, in the following manner:
+ Extract the files from the iso image of the installation DVD or the iso images of the installation CDs and place them in a directory that is shared over FTP or HTTP.
</para>
-
+ <!--
<itemizedlist>
<listitem>
<para>
@@ -50,9 +50,9 @@
</para>
</example>
</listitem>
- </itemizedlist>
+ </itemizedlist> -->
<para>
- Next make sure that the <filename><replaceable>/publicly/available/directory</replaceable></filename> directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
+ Next, make sure that the <!--<filename><replaceable>/publicly/available/directory</replaceable></filename>--> directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
</para>
</section>
\ No newline at end of file
diff --git a/en-US/X86_Bootloader.xml b/en-US/X86_Bootloader.xml
index 04a0971..cd92ec6 100644
--- a/en-US/X86_Bootloader.xml
+++ b/en-US/X86_Bootloader.xml
@@ -336,7 +336,7 @@
<itemizedlist>
<listitem>
<para>
- Using the CD-ROM to boot an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system, type <userinput>linux rescue</userinput> at the installation boot prompt. Itanium users should type <userinput>elilo linux rescue</userinput> to enter rescue mode.
+ Using the CD-ROM to boot an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system, type <userinput>linux rescue</userinput> at the installation boot prompt. <!-- (RHEL) Itanium users should type <userinput>elilo linux rescue</userinput> to enter rescue mode. -->
</para>
</listitem>
</itemizedlist>
@@ -348,17 +348,22 @@
<section id="s2-x86-bootloader-alt">
<title>Alternative Boot Loaders</title>
- <indexterm significance="normal">
+ <!-- <indexterm significance="normal">
<primary>boot loader</primary>
<secondary>alternatives to</secondary>
- </indexterm>
+ </indexterm> -->
<indexterm significance="normal">
<primary>GRUB</primary>
<secondary>alternatives to</secondary>
</indexterm>
+
<para>
- If you do not wish to use a boot loader, you have several alternatives:
+ <application>GRUB</application> is the default bootloader for Fedora, but is not the only choice. A variety of open-source and proprietary alternatives to <application>GRUB</application> are available to load Fedora, including <application>LILO</application>, <application>SYSLINUX</application>, <application>Acronis Disk Director Suite</application>, and <application>Apple Boot Camp</application>.
</para>
+
+ <!-- <para>
+ If you do not wish to use a boot loader, you have several alternatives:
+ </para>
<variablelist>
<varlistentry>
@@ -421,7 +426,7 @@ LOADLIN </term> <listitem>
<primary>boot loader</primary>
<secondary>alternatives to</secondary>
<tertiary>commercial products</tertiary>
- </indexterm>
+ </indexterm>
<indexterm significance="normal">
<primary>GRUB</primary>
<secondary>alternatives to</secondary>
@@ -441,7 +446,7 @@ Commercial boot loaders </term> <listitem>
</varlistentry>
</variablelist>
- <!-- (RHEL) <note>
+ (RHEL) <note>
<title>Note</title>
<para>
diff --git a/en-US/adminoptions.xml b/en-US/adminoptions.xml
index 7f595d6..a657584 100644
--- a/en-US/adminoptions.xml
+++ b/en-US/adminoptions.xml
@@ -814,10 +814,6 @@ Press <enter> for a shell</screen>
<entry><option>nopass</option></entry>
</row>
<row>
- <entry>Disable automatic monitor detection (DDC)</entry>
- <entry><option>skipddc</option></entry>
- </row>
- <row>
<entry>Use basic VESA driver for video</entry>
<entry><option>xdriver=vesa</option></entry>
</row>
@@ -826,14 +822,6 @@ Press <enter> for a shell</screen>
<entry><option>noshell</option></entry>
</row>
<row>
- <entry>Enable advanced programmable interrupt controller (APIC) support on Intel symmetic multi-processor (SMP) motherboards with this feature (for example, thos with the 440GX chipset)</entry>
- <entry><option>apic</option></entry>
- </row>
- <row>
- <entry>Disable mainboard APIC</entry>
- <entry><option>noapic</option></entry>
- </row>
- <row>
<entry>Disable advanced configuration and power interface (ACPI)</entry>
<entry><option>acpi=off</option></entry>
</row>
@@ -846,11 +834,6 @@ Press <enter> for a shell</screen>
<entry><option>numa-off</option></entry>
</row>
<row>
- <entry>Disable Direct Memory Access (DMA) for IDE, SATA, and
- ATAPI drives</entry>
- <entry><option>libata.dma=0</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>
@@ -863,10 +846,6 @@ Press <enter> for a shell</screen>
<entry><option>nodmraid</option></entry>
</row>
<row>
- <entry>Force Firewire device detection</entry>
- <entry><option>firewire</option></entry>
- </row>
- <row>
<entry>Disable Firewire device detection</entry>
<entry><option>nofirewire</option></entry>
</row>
@@ -890,10 +869,6 @@ Press <enter> for a shell</screen>
<entry>Disable all probing of network hardware</entry>
<entry><option>nonet</option></entry>
</row>
- <row>
- <entry>Prompt user for ISA device configuration</entry>
- <entry><option>isa</option></entry>
- </row>
</tbody>
</tgroup>
</table>
diff --git a/en-US/pxe-server-manual.xml b/en-US/pxe-server-manual.xml
index a838906..9b8deec 100644
--- a/en-US/pxe-server-manual.xml
+++ b/en-US/pxe-server-manual.xml
@@ -74,7 +74,7 @@
</para>
<!-- This next section has been commented out because system-config-netboot has been left out of the distro.
- We'll uncomment it when the component is reincluded. Be aware that there are four more sentences commented out in the section below for the same reason. -->
+ We'll uncomment it when the component is reincluded. -->
<!--
<para>
@@ -166,7 +166,7 @@
<filename>images/pxeboot/</filename> in the provided installation tree to <filename>/tftpboot/linux-install/<replaceable><os-identifier></replaceable>/</filename> on the <command>tftp</command>
server (the one you are running the <application>Network Booting Tool</application> on).
</para>
- -->
+
<section id="s2-netboot-pxeos">
<title>Command Line Configuration</title>
@@ -200,15 +200,15 @@
<listitem>
<para>
- <option>-i</option> "<replaceable><description></replaceable>" — Replace "<replaceable><description></replaceable>" with a description of the OS instance. <!-- This corresponds to the <guilabel>Description</guilabel>
- field in <xref linkend="fig-network-install-setup"/>. -->
+ <option>-i</option> "<replaceable><description></replaceable>" — Replace "<replaceable><description></replaceable>" with a description of the OS instance. This corresponds to the <guilabel>Description</guilabel>
+ field in <xref linkend="fig-network-install-setup"/>.
</para>
</listitem>
<listitem>
<para>
- <option>-p</option> <NFS|HTTP|FTP> — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified. <!-- This corresponds to the <guilabel>Select protocol for installation</guilabel>
- menu in <xref linkend="fig-network-install-setup"/>. -->
+ <option>-p</option> <NFS|HTTP|FTP> — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified. This corresponds to the <guilabel>Select protocol for installation</guilabel>
+ menu in <xref linkend="fig-network-install-setup"/>.
</para>
</listitem>
@@ -221,15 +221,15 @@
<listitem>
<para>
- <option>-s</option> <replaceable>client.example.com</replaceable> — Provide the name of the NFS, FTP, or HTTP server after the <option>-s</option> option. <!-- This corresponds to the <guilabel>Server</guilabel> field in
- <xref linkend="fig-network-install-setup"/>. -->
+ <option>-s</option> <replaceable>client.example.com</replaceable> — Provide the name of the NFS, FTP, or HTTP server after the <option>-s</option> option. This corresponds to the <guilabel>Server</guilabel> field in
+ <xref linkend="fig-network-install-setup"/>.
</para>
</listitem>
<listitem>
<para>
- <option>-L</option> <replaceable><net-location></replaceable> — Provide the location of the installation tree on that server after the <option>-L</option> option. <!-- This corresponds to the <guilabel>Location</guilabel>
- field in <xref linkend="fig-network-install-setup"/>. -->
+ <option>-L</option> <replaceable><net-location></replaceable> — Provide the location of the installation tree on that server after the <option>-L</option> option. This corresponds to the <guilabel>Location</guilabel>
+ field in <xref linkend="fig-network-install-setup"/>.
</para>
</listitem>
@@ -247,8 +247,8 @@
<listitem>
<para>
- <replaceable><os-identifer></replaceable> — Specify the OS identifier, which is used as the directory name in the <filename>/tftpboot/linux-install/</filename> directory. <!-- This corresponds to the
- <guilabel>Operating system identifier</guilabel> field in <xref linkend="fig-network-install-setup"/>. -->
+ <replaceable><os-identifer></replaceable> — Specify the OS identifier, which is used as the directory name in the <filename>/tftpboot/linux-install/</filename> directory. This corresponds to the
+ <guilabel>Operating system identifier</guilabel> field in <xref linkend="fig-network-install-setup"/>.
</para>
</listitem>
</itemizedlist>
@@ -262,7 +262,7 @@
<para>
For more information on command line options available for the <command>pxeos</command> command, refer to the <command>pxeos</command> man page.
</para>
- </section>
+ </section> -->
</section>
<section id="s1-netboot-add-hosts">
<title>Adding PXE Hosts</title>
@@ -283,7 +283,7 @@
</mediaobject>
</figure>
<para>
- The next step is to configure which hosts are allowed to connect to the PXE boot server. For the command line version of this step, refer to <xref linkend="s2-netboot-pxeboot"/>.
+ The next step is to configure which hosts are allowed to connect to the PXE boot server. <!-- For the command line version of this step, refer to <xref linkend="s2-netboot-pxeboot"/>. -->
</para>
<para>
@@ -334,7 +334,7 @@
Ignore the <guilabel>Snapshot name</guilabel> and <guilabel>Ethernet</guilabel> options. They are only used for diskless environments.
</para>
- <section id="s2-netboot-pxeboot">
+ <!-- <section id="s2-netboot-pxeboot">
<title>Command Line Configuration</title>
<indexterm significance="normal">
<primary><application>Network Booting Tool</application>
@@ -391,7 +391,7 @@ pxeboot -a -K <replaceable><kickstart></replaceable> -O <replaceable><o
<para>
For more information on command line options available for the <command>pxeboot</command> command, refer to the <command>pxeboot</command> man page.
</para>
- </section>
+ </section> -->
</section>
<section id="s1-netboot-tftp">
<title>TFTPD</title>
More information about the Fedora-docs-commits
mailing list