Author: pfrields
Update of /cvs/docs/install-guide/devel/en_US In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7976
Modified Files: diskpartitioning.xml Log Message: Add partitioning advice and rearrange for better workflow (#236264)
Index: diskpartitioning.xml =================================================================== RCS file: /cvs/docs/install-guide/devel/en_US/diskpartitioning.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- diskpartitioning.xml 11 May 2007 18:51:34 -0000 1.4 +++ diskpartitioning.xml 19 May 2007 02:54:48 -0000 1.5 @@ -77,9 +77,17 @@ create default layout</guilabel></term> <listitem> <para> - Avoid this option, unless you wish to erase all of the - existing operating systems and data on the selected drives. + If the selected hard disks are brand new, or if you want to + destroy all data currently on the selected drives, use this + option. This option removes all partitions on all selected + drives, even those used by non-Linux operating systems. </para> + <warning> + <title>This Option Destroys All Data</title> + <para>Once you have selected all installation options and + proceed, all data on the selected drives will be destroyed. + <emphasis>Use this option with caution.</emphasis></para> + </warning> </listitem> </varlistentry> <varlistentry> @@ -160,7 +168,7 @@ <xref linkend="ch-networkconfig"/>, unless you select an option to customize the partition layout. If you choose to either <guilabel>Create custom layout</guilabel>, or <guilabel>Review and - modify partitioning layout</guilabel>, proceed to + modify partitioning layout</guilabel>, proceed to <xref linkend="sn-partitioning-general"/>. </para> </note> @@ -174,17 +182,17 @@ <itemizedlist> <listitem> <para> - A data partition mounted at <filename>/boot</filename> + A <filename class="partition">/boot</filename> partition </para> </listitem> <listitem> <para> - A data partition mounted at <filename>/</filename> + A <filename class="partition">/</filename> partition </para> </listitem> <listitem> <para> - A swap partition + A <systemitem class="filesystem">swap</systemitem> partition </para> </listitem> </itemizedlist> @@ -192,9 +200,10 @@ <para> Many systems have more partitions than the minimum listed above. Choose partitions based on your particular system needs. For - example, consider creating a separate <filename>/home</filename> - partition on systems that store user data, for the reasons - explained in <xref linkend="sn-partitioning-home"/>. + example, consider creating a separate <filename + class="partition">/home</filename> partition on systems that + store user data. Refer to <xref + linkend="sn-partitioning-advice"/> for more information. </para>
<para> @@ -207,14 +216,14 @@ running systems. Linux systems use <indexterm> <primary>swap partitions</primary> - </indexterm> - <firstterm>swap</firstterm> partitions to expand this pool, by - automatically moving portions of memory between RAM and swap - partitions if insufficient RAM is available. In addition, certain - power management features store all of the memory for a suspended - system in the available swap partitions. If you manually specify - the partitions on your system, create one swap partition that has - more capacity than the computer RAM. + </indexterm> <firstterm><systemitem + class="filesystem">swap</systemitem> partitions</firstterm> to + expand this pool, by automatically moving portions of memory + between RAM and swap partitions if insufficient RAM is available. + In addition, certain power management features store all of the + memory for a suspended system in the available swap partitions. If + you manually specify the partitions on your system, create one + swap partition that has more capacity than the computer RAM. </para>
<para> @@ -222,36 +231,34 @@ a <indexterm> <primary>mount point</primary> - </indexterm> - <firstterm>mount point</firstterm>, to indicate the system - directory whose contents reside on that partition. A partition - with no mount point is not accessible by users. Data not located - on any other partition resides in the <filename>/</filename> (or + </indexterm> <firstterm>mount point</firstterm>, to indicate the + system directory whose contents reside on that partition. A + partition with no mount point is not accessible by users. Data not + located on any other partition resides in the <filename + class="partition">/</filename> (or <indexterm> <primary>partition</primary> <secondary>root</secondary> - </indexterm> - <firstterm>root</firstterm>) partition. + </indexterm> <firstterm>root</firstterm>) partition. </para>
<important> - <title>Root and <filename>/root</filename></title> + <title>Root and <filename + class="directory">/root</filename></title>
<para> - The <filename>/</filename> (or + The <filename class="partition">/</filename> (or <indexterm> <primary>partition</primary> <secondary>root</secondary> - </indexterm> - root) partition is the top of the directory structure. The + </indexterm> root) partition is the top of the directory + structure. The <indexterm> - <primary>partition</primary> - <secondary><filename>/root</filename> - </secondary> - </indexterm> - <filename>/root</filename> (sometimes pronounced "slash-root") - directory is the home directory of the user account for system - administration. + <primary><filename class="directory">/root</filename> + directory</primary> + </indexterm> <filename class="directory">/root</filename> + (sometimes pronounced "slash-root") directory is the home + directory of the user account for system administration. </para> </important>
@@ -262,46 +269,53 @@ <itemizedlist> <listitem> <para> - All data under the <filename>/boot/</filename> directory - resides on the <filename>/boot</filename> partition. For - example, the file <filename>/boot/grub/grub.conf</filename> - resides on the <filename>/boot</filename> partition. + All data under the <filename + class="directory">/boot/</filename> directory resides on the + <filename class="partition">/boot</filename> partition. For + example, the file <filename>/boot/grub/grub.conf</filename> + resides on the <filename class="partition">/boot</filename> + partition. </para> </listitem> <listitem> <para> - Any file outside of the <filename>/boot</filename> partition, - such as <filename>/etc/passwd</filename>, resides on the - <filename>/</filename> partition. + Any file outside of the <filename + class="partition">/boot</filename> partition, such as + <filename>/etc/passwd</filename>, resides on the <filename + class="partition">/</filename> partition. </para> </listitem> </itemizedlist>
<para> Subdirectories may be assigned to partitions as well. Some - administrators create both <filename>/usr</filename> and - <filename>/usr/local</filename> partitions. In that case, files - under <filename>/usr/local</filename>, such as - <filename>/usr/local/bin/foo</filename>, are on the - <filename>/usr/local</filename> partition. Any other files in - <filename>/usr/</filename>, such as - <filename>/usr/bin/foo</filename>, are in the - <filename>/usr</filename> partition. + administrators create both <filename + class="partition">/usr</filename> and <filename + class="partition">/usr/local</filename> partitions. In that + case, files under <filename + class="directory">/usr/local</filename>, such as + <filename>/usr/local/bin/foo</filename>, are on the <filename + class="partition">/usr/local</filename> partition. Any other + files in <filename class="directory">/usr/</filename>, such as + <filename>/usr/bin/foo</filename>, are in the <filename + class="partition">/usr</filename> partition. </para>
<para> - If you create many partitions instead of one large - <filename>/</filename> partition, upgrades become easier. Refer to - the description of <application>Disk Druid's</application> - <link linkend="disk-druid-edit">Edit option</link> - for more information. + If you create many partitions instead of one large <filename + class="partition">/</filename> partition, upgrades become + easier. Refer to the description of <application>Disk + Druid's</application> <link linkend="disk-druid-edit">Edit + option</link> for more information. </para> <tip> <title>Leave Excess Capacity Unallocated</title> <para> - Only assign storage capacity to partitions that you require - immediately. You may allocate free space at any time, to meet - needs as they arise. + Only assign storage capacity to those partitions you require + immediately. You may allocate free space at any time, to meet + needs as they occur. To learn about a more flexible method for + storage management, refer to <xref + linkend="sn-partitioning-lvm"/>. </para> </tip> <section id="sn-partitioning-types"> @@ -313,18 +327,15 @@ <primary>partition</primary> <secondary>type</secondary> <seealso>file system</seealso> - </indexterm> - <firstterm>partition type</firstterm>, to indicate the format of - the + </indexterm> <firstterm>partition type</firstterm>, to indicate + the format of the <indexterm> <primary>file system</primary> - </indexterm> - <firstterm>file system</firstterm> on that partition. The file - system enables Linux to organize, search, and retrieve files - stored on that partition. Use the + </indexterm> <firstterm>file system</firstterm> on that + partition. The file system enables Linux to organize, search, + and retrieve files stored on that partition. Use the <indexterm> - <primary><systemitem - class="filesystem">ext3</systemitem> + <primary><systemitem class="filesystem">ext3</systemitem> </primary> <see>file system</see> </indexterm> @@ -333,143 +344,261 @@ <secondary sortas="filesystem"><systemitem>ext3</systemitem> </secondary> - </indexterm> - <firstterm><systemitem - class="filesystem">ext3</systemitem></firstterm> - file system for data partitions that are not part of LVM, unless - you have specific needs that require another type of file - system. + </indexterm> <firstterm><systemitem + class="filesystem">ext3</systemitem></firstterm> file system + for data partitions that are not part of LVM, unless you have + specific needs that require another type of file system. </para> </section>
- <section id="sn-partitioning-lvm"> - <title>Understanding LVM</title> - <indexterm> - <primary>LVM</primary> - <secondary>understanding</secondary> - </indexterm> - <para> + <section id="sn-partitioning-minimums"> + <title>Minimum Partition Sizes</title> + <para>The following table summarizes minimum partition sizes for + the partitions containing the listed directories. You + <emphasis>do not</emphasis> have to make a separate partition + for each of these directories. For instance, if the partition + containing <filename class="directory">/foo</filename> must be + at least 500 MB, and you do not make a separate <filename + class="partition">/foo</filename> partition, then the + <filename class="partition">/</filename> (root) partition must + be at least 500 MB.</para> + <segmentedlist> + <segtitle>Directory</segtitle> + <segtitle>Minimum size</segtitle> + <seglistitem> + <seg><filename class="directory">/</filename></seg> + <seg>250 MB</seg> + </seglistitem> + <seglistitem> + <seg><filename class="directory">/usr</filename></seg> + <seg>250 MB</seg> + </seglistitem> + <seglistitem> + <seg><filename class="directory">/tmp</filename></seg> + <seg>50 MB</seg> + </seglistitem> + <seglistitem> + <seg><filename class="directory">/var</filename></seg> + <seg>384 MB</seg> + </seglistitem> + <seglistitem> + <seg><filename class="directory">/home</filename></seg> + <seg>100 MB</seg> + </seglistitem> + <seglistitem> + <seg><filename class="directory">/boot</filename></seg> + <seg>75 MB</seg> + </seglistitem> + </segmentedlist> + </section> + </section> + <section id="sn-partitioning-lvm"> + <title>Understanding LVM</title> + <indexterm> + <primary>LVM</primary> + <secondary>understanding</secondary> + </indexterm> + <para> LVM (Logical Volume Management) partitions provide a number of - advantages over standard partitions. LVM partitions are - formatted as + advantages over standard partitions. LVM partitions are formatted + as <indexterm> - <primary>LVM</primary> - <secondary>physical volume</secondary> - </indexterm> - <firstterm>physical volumes</firstterm>. One or more physical - volumes are combined to form a + <primary>LVM</primary> + <secondary>physical volume</secondary> + </indexterm> <firstterm>physical volumes</firstterm>. One or + more physical volumes are combined to form a <indexterm> - <primary>LVM</primary> - <secondary>volume group</secondary> - </indexterm> - <firstterm>volume group</firstterm>. Each volume group's total - storage is then divided into one or more + <primary>LVM</primary> + <secondary>volume group</secondary> + </indexterm> <firstterm>volume group</firstterm>. Each volume + group's total storage is then divided into one or more <indexterm> - <primary>LVM</primary> - <secondary>logical volume</secondary> - </indexterm> - <firstterm>logical volumes</firstterm>. The logical volumes - function much like standard partitions. They have a file system - type, such as - <systemitem - class="filesystem">ext3</systemitem>, and a mount - point. - </para> - - <note> - <title>The <filename>/boot</filename> Partition and LVM</title> - - <para> - Only an active Linux system may read or write to LVM volumes. - For this reason, the <filename>/boot</filename> partition that - initializes your system must be held outside of the LVM - physical volumes. - </para> - </note> - - <para> - An administrator may grow or shrink logical volumes without - destroying data, unlike standard disk partitions. If the - physical volumes in a volume group are on separate drives or - RAID arrays then administrators may also spread a logical volume - across the storage devices. - </para> + <primary>LVM</primary> + <secondary>logical volume</secondary> + </indexterm> <firstterm>logical volumes</firstterm>. The logical + volumes function much like standard partitions. They have a file + system type, such as <systemitem + class="filesystem">ext3</systemitem>, and a mount point. + </para>
+ <note> + <title>The <filename>/boot</filename> Partition and LVM</title> <para> - You may lose data if you shrink a logical volume to a smaller - capacity than the data on the volume requires. To ensure maximum - flexibility, create logical volumes to meet your current needs, - and leave excess storage capacity unallocated. You may safely - grow logical volumes to use unallocated space, as your needs - dictate. + The boot loader cannot read LVM volumes. You must make a + standard, non-LVM disk partition for your <filename + class="partition">/boot</filename> partition. </para> + </note>
- <note> - <title>LVM and the Default Partition Layout</title> + <para>To understand LVM better, imagine the physical volume as a + pile of <firstterm>blocks</firstterm>. A block is simply a + storage unit used to store data. Several piles of blocks can be + combined to make a much larger pile, just as physical volumes are + combined to make a volume group. The resulting pile can be + subdivided into several smaller piles of arbitrary size, just as a + volume group is allocated to several logical volumes.</para> + + <para> + An administrator may grow or shrink logical volumes without + destroying data, unlike standard disk partitions. If the physical + volumes in a volume group are on separate drives or RAID arrays + then administrators may also spread a logical volume across the + storage devices. + </para>
- <para> - By default, the installation process creates data and swap - partitions within LVM volumes, with a separate - <filename>/boot</filename> partition. - </para> - </note> - </section> + <para> + You may lose data if you shrink a logical volume to a smaller + capacity than the data on the volume requires. To ensure maximum + flexibility, create logical volumes to meet your current needs, + and leave excess storage capacity unallocated. You may safely grow + logical volumes to use unallocated space, as your needs dictate. + </para>
- <section id="sn-partitioning-home"> - <title>Creating a <filename>/home</filename> Partition</title> + <note> + <title>LVM and the Default Partition Layout</title>
<para> - If you expect that you or other users will store data on the - system, create a separate partition for the - <filename>/home</filename> directory within a volume group. With - a separate <filename>/home</filename> partition, you may upgrade - or reinstall &FC; without erasing user data files. LVM provides - you with the ability to add more storage capacity for the user - data at a later time. + By default, the installation process creates <filename + class="partition">/</filename> and swap partitions within LVM + volumes, with a separate <filename>/boot</filename> partition. </para> - </section> + </note> </section> -<!-- some notes follow: - - Sanity checks on partitions require: - /usr ge 250 MB - /tmp ge 50 - /var ge 384 - /home ge 100 - /boot ge 75 - / ge 250
- for ia64: - /boot/efi ge 50 MB + <section id="sn-partitioning-advice"> + <title>Advice on Partitions</title> + <para>Optimal partition setup depends on the usage for the Linux + system in question. The following tips may help you decide how to + allocate your disk space.</para>
- Cannot have these as separate partitions: - /bin /dev /sbin /etc /lib /root lost+found /proc - - Cannot make partitions for these symlinks: - /var/mail /usr/bin/X11 /usr/lib/X11 /usr/tmp + <itemizedlist> + <listitem> + <para> + If you expect that you or other users will store data on the + system, create a separate partition for the + <filename>/home</filename> directory within a volume group. + With a separate <filename>/home</filename> partition, you may + upgrade or reinstall &FC; without erasing user data files. + </para> + </listitem> + <listitem> + <para>Each kernel installed on your system requires + approximately 6 MB on the <filename + class="partition">/boot</filename> partition. Unless you + plan to install a great many kernels, the default partition + size of 100 MB for <filename + class="partition">/boot</filename> should suffice.</para> + </listitem> + <listitem> + <para>The <filename class="directory">/var</filename> directory + holds content for a number of applications, including the + <application>Apache</application> web server. It also is used + to store downloaded update packages on a temporary basis. + Ensure that the partition containing the <filename + class="directory">/var</filename> directory </para> + </listitem> + <listitem> + <para>The <filename class="directory">/usr</filename> directory + holds the majority of software content on a &DISTRO; system. + For an installation of the default set of software, allocate + at least 4 GB of space. If you are a software developer or + plan to use your &DISTRO; system to learn software development + skills, you may want to at least double this + allocation.</para> + </listitem> + <listitem> + <para>Consider leaving a portion of the space in an LVM volume + group unallocated. This unallocated space gives you + flexibility if your space requirements change but you do not + wish to remove data from other partitions to reallocate + storage.</para> + </listitem> + <listitem> + <para>If you separate subdirectories into partitions, you can + retain content in those subdirectories if you decide to + install a new version of &DISTRO; over your current system. + For instance, if you intend to run a + <application>MySQL</application> database in <filename + class="directory">/var/lib/mysql</filename>, make a separate + partition for that directory in case you need to reinstall + later.</para> + </listitem> + </itemizedlist> + <para>The following table is a possible partition setup for a system + with a single, new 80 GB hard disk and 1 GB of RAM. Note that + approximately 10 GB of the volume group is unallocated to allow + for future growth.</para> + <note> + <title>Example Usage</title> + <para>This setup is not optimal for all use cases.</para> + </note> + <example id="ex-partitioning-80g"> + <title>Example Partition Setup</title> + <segmentedlist> + <segtitle>Partition</segtitle> + <segtitle>Size and type</segtitle> + <seglistitem> + <seg><filename class="partition">/boot</filename></seg> + <seg>100 MB <systemitem class="filesystem">ext3</systemitem> + partition</seg> + </seglistitem> + <seglistitem> + <seg><filename class="partition">swap</filename></seg> + <seg>2 GB swap</seg> + </seglistitem> + <seglistitem> + <seg>LVM physical volume</seg> + <seg>Remaining space, as one LVM volume group</seg> + </seglistitem> + </segmentedlist> + <para>The physical volume is assigned to the default volume group + and divided into the following logical volumes:</para> + <segmentedlist> + <segtitle>Partition</segtitle> + <segtitle>Size and type</segtitle> + <seglistitem> + <seg><filename class="partition">/</filename></seg> + <seg>3 GB ext3</seg> + </seglistitem> + <seglistitem> + <seg><filename class="partition">/usr</filename></seg> + <seg>8 GB ext3</seg> + </seglistitem> + <seglistitem> + <seg><filename class="partition">/usr/local</filename></seg> + <seg>2 GB ext3</seg> + </seglistitem> + <seglistitem> + <seg><filename class="partition">/var</filename></seg> + <seg>4 GB ext3</seg> + </seglistitem> + <seglistitem> + <seg><filename class="partition">/home</filename></seg> + <seg>50 GB ext3</seg> + </seglistitem> + </segmentedlist> + </example> + <para></para> + </section>
---> <section id="sn-disk-druid"> <title>Disk Druid</title>
<para> <indexterm> <primary>Disk Druid</primary> - </indexterm> - <application><firstterm>Disk Druid</firstterm></application> is an - interactive program for editing disk partitions. Users run it only - within the &FC; installation system. Disk Druid enables you to - configure + </indexterm> <application><firstterm>Disk + Druid</firstterm></application> is an interactive program for + editing disk partitions. Users run it only within the &FC; + installation system. Disk Druid enables you to configure <indexterm> <primary>RAID</primary> <secondary>Linux software</secondary> - </indexterm> - Linux software RAID and + </indexterm> Linux software RAID and <indexterm> <primary>LVM</primary> - </indexterm> - <firstterm>LVM</firstterm> to provide more extensible and reliable - data storage. + </indexterm> <firstterm>LVM</firstterm> to provide more extensible + and reliable data storage. </para>
<note> @@ -477,10 +606,10 @@
<para> The default layout pools all of the available storage into a - single LVM physical volume, with one LVM logical volume for the - system. To make capacity available for additional partitions, - <guibutton>Edit</guibutton> the logical volume with the mount - point <filename>/</filename>, and reduce it's size as necessary. + single LVM physical volume, with one LVM logical volume for the + system. To make capacity available for additional partitions, + <guibutton>Edit</guibutton> the logical volume with the mount + point <filename>/</filename>, and reduce it's size as necessary. </para> </note> <figure id="fig-disk-setup"> @@ -511,12 +640,11 @@ <indexterm> <primary>partition</primary> <secondary>adding</secondary> - </indexterm> - or LVM physical volume to the disk. In the <guilabel>Add - partition</guilabel> dialog, choose a mount point and a - partition type. If you have more than one disk on the - system, choose which disks the partition may inhabit. - Indicate a size in megabytes for the partition. + </indexterm> or LVM physical volume to the disk. In the + <guilabel>Add partition</guilabel> dialog, choose a mount + point and a partition type. If you have more than one disk + on the system, choose which disks the partition may inhabit. + Indicate a size in megabytes for the partition. </para> <important> <title>Illegal Partitions</title> @@ -525,30 +653,28 @@ <indexterm> <primary>partition</primary> <secondary>illegal</secondary> - </indexterm> - The <filename>/bin/</filename>, - <filename>/dev/</filename>, <filename>/etc/</filename>, - <filename>/lib/</filename>, <filename>/proc/</filename>, - <filename>/root/</filename>, and - <filename>/sbin/</filename> directories may not be used - for separate partitions in <application>Disk - Druid</application>. These directories reside on the + </indexterm> The <filename>/bin/</filename>, + <filename>/dev/</filename>, <filename>/etc/</filename>, + <filename>/lib/</filename>, <filename>/proc/</filename>, + <filename>/root/</filename>, and + <filename>/sbin/</filename> directories may not be used + for separate partitions in <application>Disk + Druid</application>. These directories reside on the <indexterm> <primary>partition</primary> <secondary>root</secondary> - </indexterm> - <filename>/</filename> (root) partition. + </indexterm> <filename>/</filename> (root) partition. </para>
<para> The <filename>/boot</filename> partition may not reside on - an LVM volume group. Create the <filename>/boot</filename> - partition before configuring any volume groups. + an LVM volume group. Create the <filename>/boot</filename> + partition before configuring any volume groups. </para> </important> <para> You may also choose from three options for sizing your - partition: + partition: </para> <variablelist> <varlistentry> @@ -575,7 +701,7 @@ <listitem> <para> Grow the partition until it fills the remainder of the - selected disks. + selected disks. </para> </listitem> </varlistentry> @@ -585,13 +711,13 @@
<para> The actual partition on the disk may be slightly smaller - or larger than your choice. Disk geometry issues cause - this effect, not an error or bug. + or larger than your choice. Disk geometry issues cause + this effect, not an error or bug. </para> </note> <para> After you enter the details for your partition, select - <guibutton>OK</guibutton> to continue. + <guibutton>OK</guibutton> to continue. </para> </listitem> </varlistentry> @@ -604,22 +730,22 @@ <indexterm> <primary>partition</primary> <secondary>editing</secondary> - </indexterm> - LVM volume group, or an LVM physical volume that is not yet - part of a volume group. To change the size of a LVM physical - volume partition, first remove it from any volume groups. + </indexterm> LVM volume group, or an LVM physical volume + that is not yet part of a volume group. To change the size + of a LVM physical volume partition, first remove it from any + volume groups. </para> <warning> <title>Removing LVM Physical Volumes</title>
<para> If you remove an LVM physical volume from a volume group, - you erase any logical volumes it contains. + you erase any logical volumes it contains. </para> </warning> <para> Edit a partition to change its size, mount point, or file - system type. Use this function to: + system type. Use this function to: </para> <itemizedlist> <listitem> @@ -630,13 +756,13 @@ <listitem> <para> migrate Linux partitions if you are upgrading or - reinstalling &FC; + reinstalling &FC; </para> </listitem> <listitem> <para> provide a mount point for non-Linux partitions such as - those used on some Windows operating systems + those used on some Windows operating systems </para> </listitem> </itemizedlist> @@ -656,11 +782,9 @@ <secondary><systemitem class="filesystem">NTFS</systemitem> </secondary> - </indexterm> - <systemitem - class="filesystem">NTFS</systemitem> file - system with a mount point in the &FC; installer. You may - label + </indexterm> <systemitem + class="filesystem">NTFS</systemitem> file system with a + mount point in the &FC; installer. You may label <indexterm> <primary><systemitem class="filesystem">vfat</systemitem> @@ -672,35 +796,33 @@ <secondary><systemitem class="filesystem">vfat</systemitem> </secondary> - </indexterm> - <firstterm><systemitem - class="filesystem">vfat</systemitem></firstterm> - (<systemitem class="filesystem">FAT16</systemitem> or - <systemitem class="filesystem">FAT32</systemitem>) - partitions with a mount point. + </indexterm> <firstterm><systemitem + class="filesystem">vfat</systemitem></firstterm> + (<systemitem class="filesystem">FAT16</systemitem> or + <systemitem class="filesystem">FAT32</systemitem>) + partitions with a mount point. </para> </note> <para> If you need to make <emphasis>drastic</emphasis> changes to - your partition configuration, you may want to delete - partitions and start again. If your disk contains data that - you need to keep, back it up before you edit any partitions. - If you edit the size of a partition, you may lose all data - on it. + your partition configuration, you may want to delete + partitions and start again. If your disk contains data that + you need to keep, back it up before you edit any partitions. + If you edit the size of a partition, you may lose all data + on it. </para> <para> If your system contains many separate partitions for system - and user data, it is easier to upgrade your system. The - installation program allows you to erase or retain data on - specific partitions. If your user data is on a separate + and user data, it is easier to upgrade your system. The + installation program allows you to erase or retain data on + specific partitions. If your user data is on a separate <indexterm> <primary>partition</primary> <secondary><filename>/home</filename> </secondary> - </indexterm> - <filename>/home</filename> partition, you can retain that - data while erasing system partitions such as - <filename>/boot</filename>. + </indexterm> <filename>/home</filename> partition, you can + retain that data while erasing system partitions such as + <filename>/boot</filename>. </para> </listitem> </varlistentry> @@ -713,14 +835,13 @@ <indexterm> <primary>partition</primary> <secondary>deleting</secondary> - </indexterm> - or LVM physical volume. To delete an LVM physical volume, - first delete any volume groups of which that physical volume - is a member. + </indexterm> or LVM physical volume. To delete an LVM + physical volume, first delete any volume groups of which + that physical volume is a member. </para> <para> If you make a mistake, use the <guilabel>Reset</guilabel> - option to abandon all the changes you have made. + option to abandon all the changes you have made. </para> </listitem> </varlistentry> @@ -730,8 +851,8 @@ <listitem> <para> Select this option to force <application>Disk - Druid</application> to abandon all changes made to disk - partitions. + Druid</application> to abandon all changes made to disk + partitions. </para> </listitem> </varlistentry> @@ -743,8 +864,7 @@ Select this option to set up software RAID <indexterm> <primary>RAID</primary> - </indexterm> - on your &FED; system. + </indexterm> on your &FED; system. </para> <variablelist> <varlistentry> @@ -753,8 +873,8 @@ <listitem> <para> Choose this option to add a partition for software - RAID. This option is the only choice available if your - disk contains no software RAID partitions. + RAID. This option is the only choice available if your + disk contains no software RAID partitions. </para> </listitem> </varlistentry> @@ -764,9 +884,9 @@ <listitem> <para> Choose this option to construct a RAID device from two - or more existing software RAID partitions. This option - is available if two or more software RAID partitions - have been configured. + or more existing software RAID partitions. This option + is available if two or more software RAID partitions + have been configured. </para> </listitem> </varlistentry> @@ -777,9 +897,9 @@ <listitem> <para> Choose this option to set up a RAID - <firstterm>mirror</firstterm> of an existing disk. - This option is available if two or more disks are - attached to the system. + <firstterm>mirror</firstterm> of an existing disk. + This option is available if two or more disks are + attached to the system. </para> </listitem> </varlistentry> @@ -794,32 +914,31 @@ Select this option to set up LVM <indexterm> <primary>LVM</primary> - </indexterm> - on your &FED; system. First create at least one partition or - software RAID device as an LVM physical volume, using the - <application>New</application> dialog. + </indexterm> on your &FED; system. First create at least one + partition or software RAID device as an LVM physical volume, + using the <application>New</application> dialog. </para> <para> To assign one or more physical volumes to a volume group, - first name the volume group. Then select the physical - volumes to be used in the volume group. Finally, configure - logical volumes on any volume groups using the - <guilabel>Add</guilabel>, <guilabel>Edit</guilabel> and - <guilabel>Delete</guilabel> options. + first name the volume group. Then select the physical + volumes to be used in the volume group. Finally, configure + logical volumes on any volume groups using the + <guilabel>Add</guilabel>, <guilabel>Edit</guilabel> and + <guilabel>Delete</guilabel> options. </para> <para> You may not remove a physical volume from a volume group if - doing so would leave insufficient space for that group's - logical volumes. Take for example a volume group made up of - two 5 GB LVM physical volume partitions, which contains an 8 - GB logical volume. The installer would not allow you to - remove either of the component physical volumes, since that - would leave only 5 GB in the group for an 8 GB logical - volume. If you reduce the total size of any logical volumes - appropriately, you may then remove a physical volume from - the volume group. In the example, reducing the size of the - logical volume to 4 GB would allow you to remove one of the - 5 GB physical volumes. + doing so would leave insufficient space for that group's + logical volumes. Take for example a volume group made up of + two 5 GB LVM physical volume partitions, which contains an 8 + GB logical volume. The installer would not allow you to + remove either of the component physical volumes, since that + would leave only 5 GB in the group for an 8 GB logical + volume. If you reduce the total size of any logical volumes + appropriately, you may then remove a physical volume from + the volume group. In the example, reducing the size of the + logical volume to 4 GB would allow you to remove one of the + 5 GB physical volumes. </para> <important> <title>LVM Unavailable in Text Installs</title> @@ -830,7 +949,7 @@ <keycap function="alt">Alt</keycap> <keycap function="other" otherfunction="F2">F2</keycap> </keycombo> to use the terminal, and run the - <command>lvm</command> command. To return to the + <command>lvm</command> command. To return to the text-mode installation, hit <keycombo> <keycap function="alt">Alt</keycap> <keycap function="other" otherfunction="F1">F1</keycap>
docs-commits@lists.fedoraproject.org