<?
include("site.inc");
$template = new Page;
$template->initCommon();
$template->displayHeader();
?>
<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5. Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-Feedback.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-ArchSpecific.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="sn-Installer">5. Installation Notes</h2></div></div></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Latest Release Notes on the Web"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Latest Release Notes on the Web</th></tr><tr><td align="left" valign="top"><p>
These release notes may be updated. Visit <a class="ulink" href="http://docs.fedoraproject.org/release-notes/" target="_top">http://docs.fedoraproject.org/release-notes/</a>
to view the latest release notes for Fedora.</p></td></tr></table></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Fedora Installation Guide"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">Fedora Installation Guide</th></tr><tr><td align="left" valign="top"><p>
To learn how to install Fedora, refer to <a class="ulink" href="http://docs.fedoraproject.org/install-guide/" target="_top">http://docs.fedoraproject.org/install-guide/</a>.
</p></td></tr></table></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Installation issues not covered in these release notes"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Installation issues not covered in these release notes</th></tr><tr><td align="left" valign="top"><p>
If you encounter a problem or have a question during installation that is
not covered in these relese notes, refer to <a class="ulink" href="http://fedoraproject.org/wiki/FAQ" target="_top">http://fedoraproject.org/wiki/FAQ</a>
and <a class="ulink" href="http://fedoraproject.org/wiki/Bugs/Common" target="_top">http://fedoraproject.org/wiki/Bugs/Common</a>.
</p></td></tr></table></div><p>
<span class="application"><strong>Anaconda</strong></span> is the name of the
Fedora installer. This section outlines issues related to
<span class="application"><strong>Anaconda</strong></span> and installing Fedora 8.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Downloading Large Files"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Downloading Large Files</th></tr><tr><td align="left" valign="top"><p>
If you intend to download the Fedora DVD ISO image, keep in mind that not
all file downloading tools can accommodate files larger than 2 GiB in
size. Tools without this limitation include <code class="command">wget</code>
1.9.1-16 and above, <code class="command">curl</code>, and
<code class="command">ncftpget</code>. <span class="application"><strong>BitTorrent</strong></span> is
another method for downloading large files. For information about
obtaining and using the torrent file, refer to <a class="ulink" href="http://torrent.fedoraproject.org/" target="_top">http://torrent.fedoraproject.org/</a>.
</p></td></tr></table></div><p>
<span class="application"><strong>Anaconda</strong></span> tests the integrity of
installation media by default. This function works with the CD, DVD,
hard drive ISO, and NFS ISO installation methods. The Fedora Project
recommends that you test all installation media before starting the
installation process and before reporting any installation-related
bugs. Many of the bugs reported are actually due to
improperly-burned CDs or DVDs.
</p><p>
The <code class="command">mediacheck</code> function is highly sensitive, and
may report some usable discs as faulty. This result is often caused
by disc writing software that does not include padding when creating
discs from ISO files. To use this test, at boot time hit any key to
enter the menu. Then press the <span class="keycap"><strong>Tab</strong></span> key, add the
option <code class="option">mediacheck</code> to the parameter list, and press
<span class="keycap"><strong>Enter</strong></span>.
</p><p>
After you complete the <code class="command">mediacheck</code> function
successfully, reboot to return DMA mode to its normal state. On many
systems, this results in a faster installation process from the
disc. You may skip the <code class="option">mediacheck</code> option when
rebooting.
</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: BitTorrent Automatically Verifies File Integrity"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">BitTorrent Automatically Verifies File Integrity</th></tr><tr><td align="left" valign="top"><p>
If you use
<span class="application"><strong>BitTorrent</strong></span>, any
files you download are automatically validated. If your file
completes downloading, you do not need to check it. Once you burn
your CD or DVD, however, you should still use
<code class="command">mediacheck</code> to test the integrity of the media.
</p></td></tr></table></div><p>
To perform memory testing before you install Fedora, press any key
to enter the boot menu, then select <span class="guimenuitem"><strong>Memory
Test</strong></span>. This option runs the
<span class="application"><strong>Memtest86</strong></span> stand alone memory testing
software in place of <span class="application"><strong>Anaconda</strong></span>.
<span class="application"><strong>Memtest86</strong></span> memory testing continues until
you press the <span class="keycap"><strong>Esc</strong></span> key.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Memtest86 Availability"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Memtest86 Availability</th></tr><tr><td align="left" valign="top"><p>
You must boot from Installation Disc 1, the DVD, or a rescue CD in
order to use this feature.
</p></td></tr></table></div><p>
Fedora 8 supports graphical FTP and HTTP installations. However, the
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 fall back to
using the text-based installer automatically. If you prefer to use
the text-based installer, type <code class="command">linux text</code> at the
<code class="prompt">boot:</code> prompt.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title" id="sn-Changes-in-Anaconda">5.1. Changes in Anaconda</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Improved Live images support</p></li><li><p>Ability to install from Live image running from RAM or USB
stick</p></li><li><p>Improved IEEE-1394 (Firewire) support</p></li><li><p>Use of <code class="filename">/dev/hdX</code> is
deprecated on i386 and x86_64 for IDE drives, and has
changed to <code class="filename">/dev/sdX</code>
except on PPC. See note about the importance of labeling
devices for upgrades from FC6, and partition
limitations.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title" id="sn-Installation-Related-Issues">5.2. Installation Related Issues</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-IDE-RAID">5.2.1. IDE RAID</h4></div></div></div><p>
Not all IDE RAID controllers are supported. If your RAID
controller is not yet supported by <span class="package">dmraid</span>, you may
combine drives into RAID arrays by configuring Linux software
RAID. For supported controllers, configure the RAID functions in
the computer BIOS.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-Multiple-NICs-and-PXE-Installation">5.2.2. Multiple NICs and PXE Installation</h4></div></div></div><p>
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 <code class="filename">pxelinux.cfg/*</code> config files:
</p><pre class="screen">IPAPPEND 2
APPEND ksdevice=bootif
</pre><p>
The configuration options above causes the installer to use the
same network interface as BIOS and PXE use. You can also use the
following option:
</p><pre class="screen">ksdevice=link
</pre><p>
This option causes the installer to use the first network device
it finds that is linked to a network switch.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-ProLiant-DL360-with-Smart-Array">5.2.3. HP ProLiant DL360 with Smart Array</h4></div></div></div><p>
If you have difficulties with this installation not detecting
the Smart Array card, try entering <code class="command">linux isa</code> on the
installer prompt. This lets you manually select the card.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-drivers-requiring-firmware">5.2.4. Drivers Requiring Firmware</h4></div></div></div><p>Currently, <span class="application"><strong>Anaconda</strong></span> is not able
to load userland firmware. This means that any devices with a
driver that relies on loaded firmware will not be supported at
install time. This includes all QLogic storage
controllers.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title" id="Upgrade-Related-Issues">5.3. Upgrade Related Issues</h3></div></div></div><p>
Refer to
<a class="ulink" href="http://fedoraproject.org/wiki/DistributionUpgrades" target="_top">http://fedoraproject.org/wiki/DistributionUpgrades</a>
for detailed recommended procedures for upgrading Fedora.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-scsi-partition-limit">5.3.1. SCSI driver partition limits</h4></div></div></div><p>Whereas older IDE drivers supported up to 63 partitions per
device, SCSI devices are limited to 15 partitions per device.
<span class="application"><strong>Anaconda</strong></span> uses the new <code class="systemitem">libata</code> driver in the same fashion
as the rest of Fedora, so it is unable to detect more than 15
partitions on an IDE disk during the installation or upgrade
process.</p><p>If you are upgrading a system with more than 15 partitions,
you may need to migrate the disk to Logical Volume Management
(LVM). This restriction may cause conflicts with other installed
systems if they do not support LVM. Most modern Linux
distributions support LVM, and drivers are available for other
operating systems as well.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="sn-label-disk-partitions">5.3.2. Disk partitions must be labeled</h4></div></div></div><p>A change in the way that the linux kernel handles storage
devices means that device names like <code class="filename">/dev/hdX</code> or <code class="filename">/dev/sdX</code> may
differ from the values used in earlier releases. Anaconda solves
this problem by relying on partition labels. If these labels are
not present, then Anaconda presents a warning indicating that
partitions need to be labelled and that the upgrade can not
proceed. Systems that use Logical Volume Management (LVM) and
the device mapper usually do not require relabeling.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title" id="check-disk-partition-labels">5.3.2.1. To check disk partition labels</h5></div></div></div><p>To view partition labels, boot the existing Fedora
installation, and enter the following at a terminal
prompt:</p><pre class="screen">/sbin/blkid</pre><p>Confirm that each volume line in the list has a
<code class="option">LABEL=</code> value, as shown below:</p><pre class="screen">/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3"</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title" id="update-fs-mount-entries">5.3.2.2. Update the file system mount entries</h5></div></div></div><p>If any filesystem labels were added or modified, then the
device entries in <code class="filename">/etc/fstab</code> must be
adjusted to match:</p><pre class="screen">su -c 'cp /etc/fstab /etc/fstab.orig'
su -c 'gedit /etc/fstab'</pre><p>An example of a mount by label entry is:</p><pre class="screen">LABEL=f7-slash / ext3 defaults 1 1</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title" id="update-grub.conf">5.3.2.3. Update the <code class="filename">grub.conf</code> kernel root
entry</h5></div></div></div><p>If the label for the <code class="filename">/</code> (root) filesystem was
modified, the kernel boot parameter in the grub configuration
file must also be modified:</p><pre class="screen">su -c 'gedit /boot/grub/grub.conf'</pre><p>A matching example kernel grub line is:</p><pre class="screen">kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=LABEL=f7-slash rhgb quiet</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title" id="test-changed-labels">5.3.2.4. Test changes made to labels</h5></div></div></div><p>If partition labels were adjusted, or the
<code class="filename">/etc/fstab</code> file modified, then boot the
existing Fedora installation to confirm that all partitions
still mount normally and login is successful. When complete,
reboot with the installation media to start the installer and
begin the upgrade.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title" id="Upgrades-versus-Installs">5.3.3. Upgrades versus fresh installations</h4></div></div></div><p>
In general, fresh installations are recommended over upgrades,
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
information may be helpful:
</p><div class="itemizedlist"><ul type="disc"><li><p>
Before you upgrade, back up the system completely. In
particular, preserve <code class="filename">/etc</code>, <code class="filename">/home</code>,
and possibly <code class="filename">/opt</code> and <code class="filename">/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, create
alternate boot media, such as a GRUB boot floppy.
</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: System Configuration Backups"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">System Configuration Backups</th></tr><tr><td align="left" valign="top"><p>
Backups of configurations in <code class="filename">/etc</code> are also
useful in reconstructing system settings after a fresh installation.
</p></td></tr></table></div></li><li><p> After you complete the upgrade, run the following
command:</p></li><li><pre class="screen">rpm -qa --last > RPMS_by_Install_Time.txt
</pre><p>Inspect the end of the output for packages that pre-date
the upgrade. Remove or upgrade those packages from
third-party repositories, or otherwise deal with them as
necessary. Some previously installed packages may no longer
be available in any configured repository. To list all
these packages, use the following command:</p><pre class="screen">su -c 'yum list extras'</pre></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-Feedback.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-ArchSpecific.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4. Feedback </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 6. Architecture Specific Notes</td></tr></table></div>
<?
$template->displayFooter('$Date: 2007/11/08 03:46:57 $');
?>