Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by KarstenWade: http://fedoraproject.org/wiki/Docs/Beats/Installer?action=diff&rev2=98&rev1=97 The comment on the change is: formatting, some other minor fixes ------------------------------------------------------------------------------ - = Installation Notes = + {{{#!html + <h2>Installation Notes</h2>}}} [[Admonition("important", "Fedora Installation Guide", "To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/.";)]] [[Admonition("tip", "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 [[GetVal(DocsDict,BeatsVer)]]. + '''Anaconda''' is the name of the Fedora installer. This section outlines issues related to '''Anaconda''' and installing Fedora [[GetVal(DocsDict,BeatsVer)]]. - [[Admonition("note", "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. {{{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/.";)]] + [[Admonition("note", "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. {{{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''' 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. To use this test, type {{{linux mediacheck}}} at the `boot:` prompt. 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. For best results with {{{mediacheck}}}, boot with the following option: - {{{linux ide=nodma + {{{linux ide=nodma mediacheck }}} After you complete the {{{mediacheck}}} 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 {{{mediacheck}}} option when rebooting. @@ -25, +26 @@ [[Admonition("note", "{{{Memtest86}}} Availability", "You must boot from Installation Disc 1 or a rescue CD in order to use this feature.")]] - Fedora [[GetVal(DocsDict,BeatsVer)]] 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 will 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. + Fedora [[GetVal(DocsDict,BeatsVer)]] 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. - == Changes in Anaconda == + === Changes in Anaconda === - * New artwork for the installer. (F[[GetVal(DocsDict,BeatsVer)]]) + + * New artwork for the installer. * '''Anaconda''' now features the ability to install packages from any `yum`-compatible software repository. [[Admonition("note","Yum Repository Support","Only HTTP and FTP repositories are supported; repositories on CDs or NFS are not currently supported.")]] * '''Anaconda''' uses SquashFS to compress and store packages on images. @@ -41, +43 @@ * Vera fonts are retired and replaced by DejaVu as default for the installer. * The installer is now translated in Greek, Kannada, Malayalam, Marathi and Oriya. - == Kickstart Changes == + === Kickstart Changes === Three new {{{kickstart}}} keywords have been added. {{{repo --name=<repoid> [--baseurl=<url>|--mirrorlist=<url>] }}} - `repo` specifies additional package repositories to use for installation. - `baseurl` specifies the URL for the repository, while `mirrorlist` specifies a list of mirrors. One and only one of these options may be specified per repository definition. + The keyword `repo` specifies additional package repositories to use for installation. The parameter `baseurl` specifies the URL for the repository, while `mirrorlist` specifies a list of mirrors. One and only one of these options may be specified per repository definition. {{{services [--disabled=<list>] [--enabled=<list>] }}} - `services` modifies the default set of services that will be started in the default runlevel. `enabled` and `disabled` take comma-separated lists, with `enabled` services taking priority. + The keyword `services` modifies the default set of services that are started in the default runlevel. The parameters `enabled` and `disabled` take comma-separated lists, with `enabled` services taking priority. {{{user --name=<username> [--groups=<list>] [--homedir=<homedir>] [--password=<password>] [--iscrypted] [--shell=<shell>] [--uid=<uid>] }}} - `user` creates a new user with the specified parameters. `name` is required; all other parameters are optional. + The keyword `user` creates a new user with the specified parameters. The parameter `name` is required; all other parameters are optional. More documentation on {{{kickstart}}} is available in the `anaconda` package. To install it, run the command {{{su -c 'yum install anaconda'}}} and read the `/usr/share/doc/anaconda*/kickstart-docs.txt` file for more information. - == Installation Related Issues == + === Installation Related Issues === - === Sony VAIO Notebooks === + ==== Sony VAIO Notebooks ==== Some Sony VAIO notebook systems may experience problems installing Fedora from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line: @@ -71, +72 @@ Installation should proceed normally, and any devices not detected are configured the first time Fedora is booted. - === IDE RAID === + ==== 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. - === Multiple NICs and PXE Installation === + ==== 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: @@ -83, +84 @@ APPEND ksdevice=bootif }}} - The configuration options above cause the installer to use the same network interface as BIOS and PXE use. You can also use the following option: + 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. - === Compaq DL360 with Smart Array === + ==== Compaq 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. - == Upgrade Related Issues == + === Upgrade Related Issues === Refer to http://fedoraproject.org/wiki/DistributionUpgrades for detailed recommended procedures for upgrading Fedora. - In general, fresh installations are recommended over upgrades, particularly for systems which 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: + 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 GRUB boot floppy. + * 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. [[Admonition("important", "System Configuration Backups", "Backups of configurations in `/etc` are also useful in reconstructing system settings after a fresh installation.")]] -- Fedora-relnotes-content mailing list Fedora-relnotes-content@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-relnotes-content
