[relnotes] [Fedora Project Wiki] Update of "Docs/Beats/Installer" by JeremyKatz

[fedorawiki-noreply at fedoraproject.org]

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 JeremyKatz:
http://fedoraproject.org/wiki/Docs/Beats/Installer?action=diff&rev2=143&rev1=142

The comment on the change is:
some updates

------------------------------------------------------------------------------
  
  This option causes the installer to use the first network device it finds that is linked to a network switch.
  
- ==== HP ProLiant DL360 with SmartArray ====
- 
- If you have difficulties with this installation not detecting the SmartArray card, try entering {{{linux isa}}} on the installer prompt.  This lets you manually select the card.
- 
- ==== 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.
- 
  === Upgrade Related Issues ===
  
  Refer to http://fedoraproject.org/wiki/DistributionUpgrades for detailed recommended procedures for upgrading Fedora.
  
  ==== 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.
+ Whereas older IDE drivers supported up to 63 partitions per device, SCSI devices are limited to 15 partitions per device.  '''Anaconda''' uses the `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.
  
  ==== Disk partitions must be labelled ====
  
- 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.
+ 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 or UUIDs for finding devices. If these 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.
  
  ===== To check disk partition labels =====