Documentation Installer Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Fixed some typos)
Line 3: Line 3:
 
{{Admon/tip | To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/.| If you encounter a problem or have a question during installation that is not covered in these release notes, refer to http://www.fedoraproject.org/wiki/FAQ and http://www.fedoraproject.org/wiki/Bugs/Common.}}   
 
{{Admon/tip | To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/.| If you encounter a problem or have a question during installation that is not covered in these release notes, refer to http://www.fedoraproject.org/wiki/FAQ and http://www.fedoraproject.org/wiki/Bugs/Common.}}   
  
'''Anaconda''' is the name of the Fedora installer. This section outlines issues related to '''Anaconda''' and installing Fedora 11.
+
'''Anaconda''' is the name of the Fedora installer. This section outlines issues related to '''Anaconda''' and installing Fedora {{Template:DocsDict/BeatsVer}}.
  
 
=== Installation in text mode ===
 
=== Installation in text mode ===
  
  
{{Admon/tip | We recommend that you use the graphical installer to install Fedora on your computer wherever possible. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection (see "Chapter 12. Installing Through VNC" in the Fedora 11 Installation Guide).  If your system has a graphical display, but graphical installation fails, try booting with the  xdriver=vesa option (see "Chapter 9. Boot Options" in the Fedora 11 Installation Guide) or with the 'Install system with basic video driver' option when booting from the Fedora 11 DVD.}}
+
{{Admon/tip | We recommend that you use the graphical installer to install Fedora on your computer wherever possible. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection (see "Chapter 12. Installing Through VNC" in the Fedora {{Template:DocsDict/BeatsVer}} Installation Guide).  If your system has a graphical display, but graphical installation fails, try booting with the  xdriver=vesa option (see "Chapter 9. Boot Options" in the Fedora 11 Installation Guide) or with the 'Install system with basic video driver' option when booting from the Fedora {{Template:DocsDict/BeatsVer}} DVD.}}
  
The text-mode installation option in Fedora 11 is significantly more streamlined than it was in earlier versions. Text-mode installation now omits the more complicated steps that were previously part of the process, and provides users with an uncluttered and straightforward experience.
 
 
These steps are now automated in text mode:
 
* '''Package selection''': Anaconda now automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages.
 
* '''Advanced partitioning''': Anaconda still presents you with the initial screen from previous versions that allows them to specify where Anaconda should install Fedora on your system. You can choose to use a whole drive, to remove existing Linux partitions, or to use the free space on the drive. However, Anaconda now automatically sets the layout of the partitions and does not ask you to add or delete partitions or file systems from this basic layout. If you require customized layouts at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation. More advanced options yet, such as LVM, encrypted file systems, and resizable file systems continue to be available only in graphical mode and kickstart.
 
* '''Bootloader configuration''': Anaconda now performs bootloader configuration automatically.
 
  
 
==== Kickstart installations in text mode ====
 
==== Kickstart installations in text mode ====
Line 22: Line 16:
 
=== Upgrade Notes ===
 
=== Upgrade Notes ===
  
Upgrading from Fedora 9 directly to Fedora 11 using <code>yum</code> is not possible, you must upgrade to Fedora 10 first, then upgrade to Fedora 11.  See http://fedoraproject.org/wiki/YumUpgradeFaq for more information.  You can also use <code>preupgrade</code> to upgrade directly to Fedora 11 using Anaconda, minimizing the system downtime by downloading the packages in advance.  
+
Upgrading from Fedora 9 directly to Fedora {{Template:DocsDict/BeatsVer}} using <code>yum</code> is not possible, you must upgrade to Fedora 10 first, then upgrade to Fedora {{Template:DocsDict/BeatsVer}}.  See http://fedoraproject.org/wiki/YumUpgradeFaq for more information.  You can also use <code>preupgrade</code> to upgrade directly to Fedora 11 using Anaconda, minimizing the system downtime by downloading the packages in advance.  
  
 
Some modified configuration files will be replaced by their original versions during the upgrade.  Your modified versions of these configuration files will be saved as <code>*.rpmsave</code> files in that case.
 
Some modified configuration files will be replaced by their original versions during the upgrade.  Your modified versions of these configuration files will be saved as <code>*.rpmsave</code> files in that case.
Line 51: Line 45:
 
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.
 
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 11 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 <code>linux text</code> at the <code>boot:</code> prompt.
+
Fedora {{Template:DocsDict/BeatsVer}} 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 <code>linux text</code> at the <code>boot:</code> prompt.
  
 
=== Changes in Anaconda ===
 
=== Changes in Anaconda ===
  
* [http://www.fedoraproject.org/wiki/Anaconda/Features/NetConfigForNM NetConfig in NM] -- Anaconda is now using NetworkManager for configuring network interfaces during installation.  The previous backend tool was <code>libdhcp</code>, which was a replacement for <code>libpump</code>. Anaconda uses NetworkManager by communicating with it via D-Bus during installation. The move to NetworkManager in Anaconda is still ongoing, but the bulk of existing functionality has been retained. NetworkManager is enabled by default on newly installed systems, so moving to NetworkManager in Anaconda allows the installer to use the same network management tool that the final system uses. The move to NetworkManager brings some changes, most notably the removal of the network interface configuration screen in Anaconda. You are no longer asked to verify the network settings during installation. The screen now simply prompts for the hostname. The settings used during installation are written to the system.
 
 
* When using the <code>netinst.iso</code> to boot the installer, Anaconda defaults to using the Fedora mirrorlist URL as the installation source. The method selection screen no longer appears by default. If you do not wish to use the mirrorlist URL, either add <code>repo=&lt;your installation source&gt;</code> or <code>askmethod</code> to the installer boot parameters. The <code>askmethod</code> option causes the selection screen to appear as it did in previous releases. To add boot parameters, press the '''[Tab]''' key in the initial boot screen and append any new parameters to the existing list. For more information, see the <code>repo=</code> and <code>stage2=</code> descriptions at http://fedoraproject.org/wiki/Anaconda/Options
 
  
 
=== Installation Related Issues ===
 
=== Installation Related Issues ===
  
* When PXE booting and using a .iso file mounted via NFS for the installation media you are now required to add <code>method=nfsiso:server:/path</code> to the command line.
 
  
 
==== IDE device names ====
 
==== IDE device names ====

Revision as of 16:29, 25 July 2009

Contents

Installation Notes

Idea.png
To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/.
If you encounter a problem or have a question during installation that is not covered in these release notes, refer to http://www.fedoraproject.org/wiki/FAQ and http://www.fedoraproject.org/wiki/Bugs/Common.

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

Installation in text mode

Idea.png
We recommend that you use the graphical installer to install Fedora on your computer wherever possible. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection (see "Chapter 12. Installing Through VNC" in the Fedora 23 Installation Guide). If your system has a graphical display, but graphical installation fails, try booting with the xdriver=vesa option (see "Chapter 9. Boot Options" in the Fedora 11 Installation Guide) or with the 'Install system with basic video driver' option when booting from the Fedora 23 DVD.


Kickstart installations in text mode

Text-mode installations using kickstart are carried out in the same way that they were in previous versions. However, because package selection, advanced partitioning, and bootloader configuration are now automated in text mode, Anaconda cannot prompt users for information that it requires during these steps. Users must ensure that the kickstart file includes the packaging, partitioning, and bootloader configurations. If any of this information is missing, Anaconda will exit with an error message.

Upgrade Notes

Upgrading from Fedora 9 directly to Fedora 23 using yum is not possible, you must upgrade to Fedora 10 first, then upgrade to Fedora 23. See http://fedoraproject.org/wiki/YumUpgradeFaq for more information. You can also use preupgrade to upgrade directly to Fedora 11 using Anaconda, minimizing the system downtime by downloading the packages in advance.

Some modified configuration files will be replaced by their original versions during the upgrade. Your modified versions of these configuration files will be saved as *.rpmsave files in that case.

Boot menu

The boot menu for the Fedora DVD includes a new option: Install system with basic video driver. This option boots the system with the generic vesa driver (using the xdriver=vesa kernel option) and allows you to use Fedora's graphical installation mode even when Anaconda cannot load the correct driver for your video card.

boot.iso Now Works on Systems With UEFI

The fedora installation CDs and DVD provide you with an image file, boot.iso that you can burn to a CD and use to boot a system and start the installation process. Typically, you would do this prior to installing Fedora from a local hard drive or from a location on a network. You can now use the CD produced from the boot.iso image to start installation on a system that uses Unified Extensible Firmware Interface (UEFI). CDs produced from older versions of boot.iso only worked with systems that used Basic Input Output System (BIOS).