Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19962
Modified Files: Installer.xml Log Message: Incorporate latest wiki changes for 0-day release
Index: Installer.xml =================================================================== RCS file: /cvs/docs/release-notes/devel/en_US/Installer.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- Installer.xml 18 May 2007 00:40:19 -0000 1.18 +++ Installer.xml 31 May 2007 01:43:58 -0000 1.19 @@ -54,7 +54,7 @@ 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 <command>linux + improperly-burned CDs or DVDs. To use this test, type <command>linux mediacheck</command> at the <prompt>boot:</prompt> prompt. </para>
@@ -82,23 +82,24 @@ <application>BitTorrent</application>, any files you download are automatically validated. If your file completes downloading, you do not need to check it. Once you burn - your CD, however, you should still use <command>mediacheck</command>. + your CD or DVD, however, you should still use + <command>mediacheck</command> to test the integrity of the media. </para> </important> <para> - You may perform memory testing before you install Fedora by entering - <option>memtest86</option> at the <prompt>boot:</prompt> prompt. This option - runs the <application>Memtest86</application> stand alone - memory testing software in place of - <application>Anaconda</application>. - <application>Memtest86</application> memory testing - continues until the <keycap>Esc</keycap> key is pressed. + You may perform memory testing before you install Fedora by pressing + <keycap>Esc</keycap> twice, then entering <option>memtest86</option> + at the <prompt>boot:</prompt> prompt. This option runs the + <application>Memtest86</application> stand alone memory testing + software in place of <application>Anaconda</application>. + <application>Memtest86</application> memory testing continues until + the <keycap>Esc</keycap> key is pressed. </para> <note> <title>Memtest86 Availability</title> <para> - You must boot from Installation Disc 1 or a rescue CD in order to use this - feature. + You must boot from Installation Disc 1, the DVD, or a rescue CD in + order to use this feature. </para> </note> <para> @@ -133,7 +134,7 @@ </itemizedlist> </listitem> <listitem> - <para>Improved LiveCD support</para> + <para>Improved Live images support</para> </listitem> <listitem> <para>Ability to install from Live image running from RAM or USB @@ -151,6 +152,13 @@ <listitem> <para>Improved kickstart installation</para> </listitem> + <listitem> + <para>Use of <filename class="devicefile">/dev/hdX</filename> is + deprecated on i386 and and x86_64 for IDE drives, and has + changed to <filename class="devicefile">/dev/sdX</filename> + except on PPC. See note about the importance of labeling + devices for upgrades from FC6.</para> + </listitem> </itemizedlist> </section>
@@ -205,8 +213,8 @@ it finds that is linked to a network switch. </para> </section> - <section id="sn-Compaq-DL360-with-Smart-Array"> - <title>Compaq DL360 with Smart Array</title> + <section id="sn-ProLiant-DL360-with-Smart-Array"> + <title>HP ProLiant DL360 with Smart Array</title> <para> If you have difficulties with this installation not detecting the Smart Array card, try entering <command>linux isa</command> on the @@ -222,6 +230,61 @@ <ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink> for detailed recommended procedures for upgrading Fedora. </para> + <section> + <title>Disk partitions must be labeled</title> + <para>A change in the way that the linux kernel handles storage + devices means that device names like <filename + class="devicefile">/dev/hdX</filename> or <filename + class="devicefile">/dev/sdX</filename> 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.</para> + <section id="check-disk-partition-labels"> + <title>To check disk partition labels</title> + <para>To view partition labels, boot the existing Fedora + installation, and enter the following at a terminal + prompt:</para> + <screen><![CDATA[/sbin/blkid]]></screen> + <para>Confirm that each volume line in the list has a + <option>LABEL=</option> value, as shown below:</para> + <screen><![CDATA[/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3"]]></screen> + </section> + <section id="update-fs-mount-entries"> + <title>Update the file system mount entries</title> + <para>If any filesystem labels were added or modified, then the + device entries in <filename>/etc/fstab</filename> must be + adjusted to match:</para> + <screen><![CDATA[su -c 'cp /etc/fstab /etc/fstab.orig' +su -c 'gedit /etc/fstab']]></screen> + <para>An example of a mount by label entry is:</para> + <screen><![CDATA[LABEL=f7-slash / ext3 defaults 1 1]]></screen> + </section> + <section id="update-grub.conf"> + <title>Update the <filename>grub.conf</filename> kernel root + entry</title> + <para>If the label for the <filename + class="partition">/</filename> (root) filesystem was + modified, the kernel boot parameter in the grub configuration + file must also be modified:</para> + <screen><![CDATA[su -c 'gedit /boot/grub/grub.conf']]></screen> + <para>A matching example kernel grub line is:</para> + <screen><![CDATA[kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=f7-slash rhgb quiet]]></screen> + </section> + <section id="test-changed-labels"> + <title>Test changes made to labels</title> + <para>If partition labels were adjusted, or the + <filename>/etc/fstab</filename> 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.</para> + </section> + </section> + <section id="Upgrades-versus-Installs"> + <title>Upgrades versus fresh installations</title> <para> In general, fresh installations are recommended over upgrades, particularly for systems that include software from third-party @@ -261,5 +324,6 @@ or otherwise deal with them as necessary.</para> </listitem> </itemizedlist> + </section> </section> </section>
docs-commits@lists.fedoraproject.org