release-notes/devel/en_US Installer.xml,1.9,1.10
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon Sep 25 08:30:35 UTC 2006
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31082
Modified Files:
Installer.xml
Log Message:
Good for FC6
Index: Installer.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Installer.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Installer.xml 24 Sep 2006 20:41:49 -0000 1.9
+++ Installer.xml 25 Sep 2006 08:30:32 -0000 1.10
@@ -20,14 +20,14 @@
<note>
<title>Downloading Large Files</title>
<para>
- If you intend to download the Fedora Core 6 DVD ISO image, keep
- in mind that not all file downloading tools can accommodate
- files larger than 2 GiB in size. {{{wget}}} 1.9.1-16 and above,
- {{{curl}}} and {{{ncftpget}}} do not have this limitation, and
- can successfully download files larger than 2 GiB.
- '''BitTorrent''' is another method for downloading large files.
- For information about obtaining and using the torrent file,
- refer to http://torrent.fedoraproject.org/.
+ If you intend to download the Fedora Core 6 DVD ISO image, keep in mind
+ that not all file downloading tools can accommodate files larger than 2
+ GiB in size. <command>wget</command> 1.9.1-16 and above,
+ <command>curl</command> and <command>ncftpget</command> do not have this
+ limitation, and can successfully download files larger than 2 GiB.
+ BitTorrent is another method for downloading large files. For
+ information about obtaining and using the torrent file, refer to
+ http://torrent.fedoraproject.org/.
</para>
</note>
</para>
@@ -40,7 +40,8 @@
installation process, and before reporting any installation-related
bugs. Many of the bugs reported are actually due to
improperly-burned CDs. To use this test, type <code>linux
- mediacheck</code> at the <code>boot:</code> prompt.
+ mediacheck</code> at the <prompt>boot:</prompt> prompt presented at the
+ start of installation.
</para>
<para>
@@ -69,12 +70,12 @@
<para>
<important>
- <title>Bit``Torrent Automatically Verifies File Integrity</title>
+ <title>BitTorrent Automatically Verifies File Integrity</title>
<para>
- If you use '''Bit``Torrent''', any files you download are
+ If you use '''BitTorrent''', any files you download are
automatically validated. If your file completes downloading, you
do not need to check it. Once you burn your CD, however, you
- should still use {{{mediacheck}}}.
+ should still use <command>mediacheck</command>.
</para>
</important>
</para>
@@ -91,7 +92,7 @@
<para>
<note>
- <title>{{{Memtest86}}} Availability</title>
+ <title>Memtest86 Availability</title>
<para>
You must boot from Installation Disc 1 or a rescue CD in order
to use this feature.
@@ -106,7 +107,7 @@
installer image must either fit in RAM or appear on local storage
such as Installation Disc 1. Therefore, only systems with more than
192MiB of RAM, or which boot from Installation Disc 1, can use the
- graphical installer. Systems with 192MiB RAM or less will fall back
+ graphical installer. Systems with 192MiB RAM or less fall back
to using the text-based installer automatically. If you prefer to
use the text-based installer, type <code>linux text</code> at the
<code>boot:</code> prompt.
@@ -224,7 +225,7 @@
</para>
<para>
<code>services</code> modifies the default set of services that
- will be started in the default runlevel. <code>enabled</code> and
+ are started in the default runlevel. <code>enabled</code> and
<code>disabled</code> take comma-separated lists, with
<code>enabled</code> services taking priority.
</para>
@@ -278,10 +279,10 @@
<title>Multiple NICs and PXE Installation</title>
<para>
Some servers with multiple network interfaces may not assign
- eth0 to the first network interface as BIOS knows it, which can
- cause the installer to try using a different network interface
- than was used by PXE. To change this behavior, use the following
- in pxelinux.cfg/* config files:
+ <computeroutput>eth0</computeroutput> to the first network interface as
+ BIOS knows it, which can cause the installer to try using a different
+ network interface than was used by PXE. To change this behavior, use the
+ following in pxelinux.cfg/* config files:
</para>
<screen><![CDATA[IPAPPEND 2
APPEND ksdevice=bootif
@@ -309,7 +310,7 @@
</para>
<para>
In general, fresh installations are recommended over upgrades,
- particularly for systems which include software from third-party
+ particularly for systems that include software from third-party
repositories. Third-party packages remaining from a previous
installation may not work as expected on an upgraded Fedora
system. If you decide to perform an upgrade anyway, the following
@@ -318,13 +319,13 @@
<itemizedlist>
<listitem>
<para>
- Before you upgrade, back up the system completely. In
- particular, preserve <code>/etc</code>, <code>/home</code>,
- and possibly <code>/opt</code> and <code>/usr/local</code> if
- customized packages are installed there. You may wish to use a
- multi-boot approach with a "clone" of the old installation on
- alternate partition(s) as a fallback. In that case, creating
- alternate boot media such as GRUB boot floppy.
+ Before you upgrade, back up the system completely. In particular,
+ preserve <code>/etc</code>, <code>/home</code>, and possibly
+ <code>/opt</code> and <code>/usr/local</code> if customized packages
+ are installed there. You may wish to use a multi-boot approach with a
+ <firstterm>clone</firstterm> of the old installation on alternate
+ partition(s) as a fallback. In that case, create alternate boot
+ media such as a GRUB boot floppy.
</para>
</listitem>
</itemizedlist>
@@ -332,8 +333,8 @@
<important>
<title>System Configuration Backups</title>
<para>
- Backups of configurations in `/etc` are also useful in
- reconstructing system settings after a fresh installation.
+ Backups of configurations in <filename>/etc</filename> are also useful
+ in reconstructing system settings after a fresh installation.
</para>
</important>
</para>
More information about the docs-commits
mailing list