Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20809
Modified Files: Installer.xml Log Message: Resync with wiki and editorial changes
Index: Installer.xml =================================================================== RCS file: /cvs/docs/release-notes/devel/en_US/Installer.xml,v retrieving revision 1.35 retrieving revision 1.36 diff -u -r1.35 -r1.36 --- Installer.xml 7 Apr 2008 05:39:37 -0000 1.35 +++ Installer.xml 8 Apr 2008 16:39:35 -0000 1.36 @@ -136,13 +136,14 @@ <itemizedlist> <listitem> <para> - Built-in features for resizing ext2, ext3, and ntfs + Built-in support for resizing ext2, ext3, and ntfs partitions. </para> </listitem> <listitem> <para> - Encrypted partition support. + Support for installation to encrypted block devices, including + the root filesystem. </para> </listitem> <listitem> @@ -161,18 +162,9 @@ </listitem> <listitem> <para> - Experimental support for installing to - <systemitem - class="filesystem">ext4</systemitem> - partitions, with the <option>iamanext4developer</option> boot - option. - </para> - </listitem> - <listitem> - <para> - Native installation to <systemitem>x86_64</systemitem> - machines using EFI and booting via - <systemitem>grub</systemitem>. + Native installation to <systemitem>x86</systemitem> and + <systemitem>x86_64</systemitem> machines using EFI and + booting via <systemitem>grub</systemitem>. </para> </listitem> <listitem> @@ -281,17 +273,18 @@
<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 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. + 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. <application>Anaconda</application> solves this + problem by relying on partition labels or UUIDs for finding + devices. If these are not present, then + <application>Anaconda</application> 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"> @@ -411,10 +404,15 @@ </section>
<section id="Kickstart-HTTP-Issue"> - <title>Kickstart HTTP Issue</title> - <para> - When delivering a Kickstart configuration file via HTTP, the retrieval of the file may fail, saying that the file could not be retrieved. Clicking the <guilabel>OK</guilabel> button several times without making modifications will result in the file being used. As a workaround, use one of the other supported methods to retrieve Kickstart configurations. - </para> + <title>Kickstart HTTP Issue</title> + <para> + 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 <guilabel>OK</guilabel> 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. + </para> </section>
</section>