5. Installation Notes

5. Installation Notes
Előző		Következő

	A legújabb kiadási jegyzék a hálózaton
These release notes may be updated. To view the latest release notes for Fedora, visit: http://docs.fedoraproject.org/release-notes/

A legújabb kiadási jegyzék a hálózaton

These release notes may be updated. To view the latest release notes for Fedora, visit:

http://docs.fedoraproject.org/release-notes/

	Fedora Installation Guide
	To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/.

	Installation issues not covered in these release notes
	If you encounter a problem or have a question during installation that is not covered in these relese notes, refer to http://fedoraproject.org/wiki/FAQ and http://fedoraproject.org/wiki/Bugs/Common.

Anaconda is the name of the Fedora installer. This section outlines issues related to Anaconda and installing Fedora 9.

Downloading Large Files

	Downloading Large Files
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 `wget` 1.9.1-16 and above, `curl`, and `ncftpget`. 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 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 wget 1.9.1-16 and above, curl, and ncftpget. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/.

Anaconda 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.

The mediacheck 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 Tab key, add the option mediacheck to the parameter list, and press Enter.

After you complete the mediacheck function successfully, reboot to return the system to its normal state. On many systems, this results in a faster installation process from the disc. You may skip the mediacheck option when rebooting.

	BitTorrent Automatically Verifies File Integrity
	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 or DVD, however, you should still use `mediacheck` to test the integrity of the media.

To perform memory testing before you install Fedora, press any key to enter the boot menu, then select Memory Test. This option runs the Memtest86 stand alone memory testing software in place of Anaconda. Memtest86 memory testing continues until you press the Esc key.

	Memtest86 Availability
	You must boot from Installation Disc 1, the DVD, or a rescue CD in order to use this feature.

Fedora 9 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 linux text at the boot: prompt.

5.1. Changes in Anaconda

Built-in features for resizing ext2, ext3, and ntfs partitions.
Encrypted partition support.
Consolidated network booting ISO image, replacing old boot.iso, diskboot.img, and rescuecd.iso.
Second stage installer location now independent of software package location.
Experimental support for installing to ext4 partitions, with the iamanext4developer boot option.
Native installation to x86_64 machines using EFI and booting via grub.
Hardware probing and detection now based on HAL and udev.
Support for persistence in Live images on USB flash media.

5.2.1. IDE Device Names

Use of /dev/hdX on i386 and x86_64 for IDE drives has changed to /dev/sdX. See notes about the importance of labeling devices for upgrades from releases before Fedora 7, and partition limitations.

5.2.2. IDE RAID

Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by dmraid , you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS.

5.2.3. Multiple NICs and PXE Installation

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:

IPAPPEND 2 
APPEND ksdevice=bootif

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:

ksdevice=link

This option causes the installer to use the first network device it finds that is linked to a network switch.

5.2.4. HP ProLiant DL360 with Smart Array

If you have difficulties with this installation not detecting the Smart Array card, try entering linux isa on the installer prompt. This lets you manually select the card.

5.2.5. Drivers Requiring Firmware

Currently, Anaconda 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.

Refer to http://fedoraproject.org/wiki/DistributionUpgrades for detailed recommended procedures for upgrading Fedora.

5.3.1. SCSI driver partition limits

Whereas older IDE drivers supported up to 63 partitions per device, SCSI devices are limited to 15 partitions per device. Anaconda uses the new libata 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.

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.

5.3.2. Disk partitions must be labeled

A change in the way that the linux kernel handles storage devices means that device names like /dev/hdX or /dev/sdX 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.

5.3.2.1. To check disk partition labels

To view partition labels, boot the existing Fedora installation, and enter the following at a terminal prompt:

/sbin/blkid

Confirm that each volume line in the list has a LABEL= value, as shown below:

/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3"

5.3.2.2. Update the file system mount entries

If any filesystem labels were added or modified, then the device entries in /etc/fstab must be adjusted to match:

su -c "cp /etc/fstab /etc/fstab.orig"
su -c "gedit /etc/fstab"

An example of a mount by label entry is:

LABEL=f7-slash  /  ext3  defaults  1 1

5.3.2.3. Update the `grub.conf` kernel root entry

If the label for the / (root) filesystem was modified, the kernel boot parameter in the grub configuration file must also be modified:

su -c "gedit /boot/grub/grub.conf"

A matching example kernel grub line is:

kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=LABEL=f7-slash rhgb quiet

5.3.2.4. Test changes made to labels

If partition labels were adjusted, or the /etc/fstab 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.

5.3.3. Upgrades versus fresh installations

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:

Before you upgrade, back up the system completely. In particular, preserve /etc, /home, and possibly /opt and /usr/local 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.

	System Configuration Backups
	Backups of configurations in `/etc` are also useful in reconstructing system settings after a fresh installation.

After you complete the upgrade, run the following command:
```
rpm -qa --last > RPMS_by_Install_Time.txt 
```
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:
```
su -c "yum list extras"
```

Előző		Következő
4. Feedback	Tartalom	6. Architecture Specific Notes