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.
	The programs 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/.

Anaconda asks if it should verify the installation medium when Install or upgrade an existing system is selected during boot from an installation-only media.

For Fedora Live media, press any key during the initial boot countdown, bringing up a boot option menu. Select Verify and boot to perform the media test. The pure installation medium can be used to verify a Fedora Live medium. Anaconda asks during the mediacheck if you want to check any other disc than the one Anaconda is running from. To test another media, select eject to eject the inserted medium, then replace it with the medium you want to test instead.

Perform this test everytime after you create or receive a new installation or live medium.

The Fedora Project strongly recommends that you perform this test before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CD or DVDs.

In rare cases, the testing procedure 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.

	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.

Another reason for a failure during installation is faulty memory. 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 standalone memory testing software in place of Anaconda. Memtest86 memory testing continues until you press the Esc key.

Fedora 10 supports graphical FTP and HTTP installations. However, the installer image must either fit in RAM or appear on local storage, such as the installation DVD or Live Media. Therefore, only systems with more than 192MiB of RAM or that boot from the installation DVD or Live Media 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.

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

	  /sbin/blkid
	

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

	  su -c 'e2label /dev/example f7-slash'
	

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

	  LABEL=f7-slash  /  ext3  defaults  1
	    1
	

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

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

3.1.4.3. Upgrades versus fresh installations

In general, fresh installations are recommended over upgrades. This is particularly true 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 want 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.

	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'
      

When using a Kickstart configuration file via HTTP, kickstart file retrieval may fail with an error that indicates the file could not be retrieved. Click the OK button several times without making modifications to override this error successfully. As a workaround, use one of the other supported methods to retrieve Kickstart configurations.

The Firstboot application requires the creation of a non-root user for the system. This is to support gdm no longer allowing the root user to log in to the graphical desktop.

If a network authentication mechanism is chosen during installation Firstboot does not require creating a that does not use local user.

For a complete list of current spins available, and instructions for using them, refer to:

http://fedoraproject.org/wiki/CustomSpins

To boot from the Fedora Live image, insert it into your computer and restart. To log in and use the desktop environment, enter the username fedora. There is no password on this account. The GNOME-based Fedora Live images automatically login after one minute, so users have time to select a preferred language. After logging in, if you wish to install the contents of the live image to your hard drive, click on the Install to Hard Drive icon on the desktop.

You can do a text mode installation of the Fedora Live images using the liveinst command in the console.

Another way to use these Fedora Live images is to put them on a USB stick. To do this, use the liveusb-creator graphical interface. Use Add/Remove Software, search for, then install liveusb-creator. To install using yum:

      su -c 'yum install liveusb-creator'
    

Instead of the graphical tool, you can use the command line interface from the livecd-tools package. Then, run the livecd-iso-to-disk script:

      /usr/bin/livecd-iso-to-disk /path/to/live.iso
	/dev/sdb1
    

Replace /dev/sdb1 with the partition where you want to put the image.

This is not a destructive process; any data you currently have on your USB stick is preserved.

Support for keeping a persistent /home with the rest of the system stateless has been added for Fedora 10. This includes support for encrypting /home to protect your system in the case where your USB stick is lost or stolen. To use this, download the live image and run the following command:

      livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso
	/dev/sdb1
    

Replace /dev/sdb1 with the partition where you want to put the image.

Replace 512 with the desired size in megabytes of the persistent /home. The livecd-iso-to-disk shell script is stored in the LiveOS directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the /home, plus any other data to be stored on the media. By default, this encrypts your data and prompts for a passphrase to use. If you want to have an unencrypted /home, then you can specify --unencrypted-home.

Note that later runs of livecd-iso-to-disk preserve the /home that is created on the USB stick, continuing to use it even if you change your live image.

Support for persistent changes with a Fedora Live image exists for Fedora 9 and later. The primary use case is booting from a Fedora Live image on a USB flash drive and storing changes to that same device. To do this, download the Fedora Live image and then run the following command:

      livecd-iso-to-disk --overlay-size-mb 512
	/path/to/live.iso /dev/sdb1
    

Replace /dev/sdb1 with the partition where you want to put the image.

Replace 512 with the desired size in megabytes of the persistent data, or overlay. The livecd-iso-to-disk shell script is stored in the LiveOS directory at the top level of the CD image. The USB media must have sufficient free space for the Fedora Live image, plus the overlay, plus any other data to be stored on the media.

Fedora 10 includes support for putting the live image onto a USB image and then booting it on Intel processor-based Apple hardware. Unlike for most x86 machines, this unfortunately requires reformatting the USB stick that you are using. To set up a stick for this, you can run:

      /usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso
	/dev/sdb1
    

Replace /dev/sdb1 with the partition where you want to put the image.

Note that all of the other arguments for the livecd-iso-to-disk tool as described above can be used here as well.

The following items are different from a normal Fedora install with the Fedora Live images.

From http://fedoraproject.org/wiki/ForbiddenItems:

RPM supports parallel installation of multiple architectures of the same package. A default package listing such as rpm -qa might appear to include duplicate packages, since the architecture is not displayed. Instead, use the repoquery command, part of the yum-utils package, which displays architecture by default. To install yum-utils, run the following command:

      su -c 'yum install yum-utils'
    

To list all packages with their architecture using rpm, run the following command:

      rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
    

This setting changes the default query to list the architecture. Add it to /etc/rpm/macros (for a system wide setting) or ~/.rpmmacros (for a per-user setting).

      %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
    

This section covers specific information about Fedora and the x86 hardware platform.

This section covers specific information about Fedora and the x86_64 hardware platform.

This section covers specific information about Fedora and the PPC (Power PC) hardware platform.

Fedora 10 uses the

evdev

input driver as standard mouse and keyboard driver for the X server. This driver works with HAL to provide a persistent per-device configuration that allows devices to be added or removed at runtime.

Refer to the Xorg third-party drivers page for detailed guidelines on using third-party video drivers.

http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers

http://who-t.blogspot.com/2008/07/input-configuration-in-nutshell.html -- Evdev configuration.

Plymouth is the graphical boot up system debuting with Fedora 10.

Fedora 10 gets a faster boot from improvements in process start-up.

Kernel modesetting (KMS) can default to either enabled or disabled in the DRM driver and it can be enabled or disabled at boot-time.