install-guide fedora-install-guide-diskpartitioning-en.xml,1.8,1.9

[Stuart Ellis (elliss)]

Author: elliss

Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28691

Modified Files:
	fedora-install-guide-diskpartitioning-en.xml 
Log Message:

- Moved the large LVM admonition to a separate subsection under General.
- Added admonition that /boot cannot be part of LVM.
- Moved filesystem paragraph to a separate subsection under General.
- Moved / vs /root admonition to General section.
- Altered "General Information" to be "General Information on Partitioning"
- Removed some quotes, per Documentation Guide.
- Also added trailing slash to names of directories, per Documentation Guide.
Note: Didn't add trailing slashes to partition names.  Documentation Guide doesn't specify how to handle these, and just IMO it looks better.  



Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-diskpartitioning-en.xml	28 May 2005 11:23:18 -0000	1.8
+++ fedora-install-guide-diskpartitioning-en.xml	28 May 2005 17:25:46 -0000	1.9
@@ -144,11 +144,12 @@
   </section>
     
   <section id="sn-partitioning-general">
-    <title>General Information</title>
+    <title>General Information on Partitions</title>
 
     <para>
       A &FC; system has at least three partitions:
     </para>
+
     <itemizedlist>
       <listitem>
 	<para>
@@ -166,39 +167,16 @@
 	</para>
       </listitem>
     </itemizedlist>
+
     <para>
-      Most systems have more partitions than the minimum listed above.
+      Many systems have more partitions than the minimum listed above.
       Choose partitions based on your particular system needs.  If you
-      are not sure what to choose, use the "Automatic partitioning"
+      are not sure what to choose, use the Automatic Partitioning
       method shown in <xref linkend="sn-choosing-partition-method"/>.
     </para>
+
     <para>
-      Every partition has a <indexterm>
-	<primary>partition</primary>
-	<secondary>type</secondary>
-	<seealso>file system</seealso>
-      </indexterm> <firstterm>partition type</firstterm>.  The partition
-      type indicates the <indexterm>
-	<primary>file system</primary>
-      </indexterm> <firstterm>file system</firstterm> expected on that
-      partition.  A file system allows a Linux system to more
-      effectively organize, search, and retrieve files.  The most common
-      partition type for &FED; is <indexterm>
-	<primary><systemitem
-	    class="filesystem">ext3</systemitem></primary>
-	<see>file system</see>
-      </indexterm><indexterm>
-	<primary>file system</primary>
-	<secondary
-	  sortas="filesystem"><systemitem>ext3</systemitem></secondary>
-      </indexterm> <systemitem
-	class="filesystem"><firstterm>ext3</firstterm></systemitem>.
-      The <systemitem class="filesystem">ext3</systemitem> file system
-      provides more robust features for preventing data loss.  Most
-      &FED; administrators choose this type for data partitions.
-    </para>
-    <para>
-      Most partitions have a <indexterm>
+      Data partitions have a <indexterm>
 	<primary>mount point</primary>
       </indexterm> <firstterm>mount point</firstterm>.  The mount point
       indicates the directory whose contents reside on that partition.
@@ -207,13 +185,29 @@
       <filename>/</filename> (or <indexterm>
 	<primary>partition</primary>
 	<secondary>root</secondary>
-      </indexterm> <firstterm>"root"</firstterm>) partition.  In the
-      minimum configuration shown above:
+      </indexterm> <firstterm>root</firstterm>) partition.  
+     </para>
+
+    <important>
+     <title>Root and <filename>/root</filename></title>
+      <para>
+       The <filename>/</filename> (or
+	      <indexterm><primary>partition</primary><secondary>root</secondary></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.
+	    </para>
+     </important>
+
+    <para>
+    In the minimum configuration shown above:
     </para>
     <itemizedlist>
       <listitem>
 	<para>
-	  All data under the <filename>/boot</filename> directory
+	  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.
@@ -234,7 +228,7 @@
       under <filename>/usr/local</filename>, such as
       <filename>/usr/local/bin/foo</filename>, will be on the
       <filename>/usr/local</filename> partition.  Any other files in
-      <filename>/usr</filename>, such as
+      <filename>/usr/</filename>, such as
       <filename>/usr/bin/foo</filename>, will be in the
       <filename>/usr</filename> partition.
     </para>
@@ -246,6 +240,80 @@
       information.
     </para>
 
+
+     <section id="sn-partitioning-types">
+      <title>Partition Types</title>
+
+      <para>
+      Every partition has a <indexterm>
+	<primary>partition</primary>
+	<secondary>type</secondary>
+	<seealso>file system</seealso>
+      </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>
+	<primary><systemitem
+	    class="filesystem">ext3</systemitem></primary>
+	<see>file system</see>
+      </indexterm><indexterm>
+	<primary>file system</primary>
+	<secondary
+	  sortas="filesystem"><systemitem>ext3</systemitem></secondary>
+      </indexterm> <systemitem
+	class="filesystem"><firstterm>ext3</firstterm></systemitem> file
+	    system for data partitions, 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, understanding</primary>
+      </indexterm>
+
+      <para>
+	Formatting the disks on your computer with LVM (Logical Volume
+	Management) partitions provides a number of advantages over
+	standard partitions.
+      </para>
+
+       <para>
+	With LVM, partitions are formatted as <indexterm>
+	<primary>physical volumes</primary></indexterm>
+	<firstterm>physical volumes</firstterm>.  One or more physical
+	volumes are combined to form a <indexterm><primary>volume groups</primary>
+      </indexterm> <firstterm>volume group</firstterm>.  Each volume
+	group's total storage is then divided into one or more <indexterm>
+	<primary>logical volumes</primary></indexterm> 
+	<firstterm>logical volumes</firstterm>.  The logical volumes
+	function much like standard data partitions.  They have a file
+	system type, such as ext3, and a mount point. 
+      </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 then
+	administrators may also spread a logical volume across multiple
+	disks and RAID arrays. 
+      </para>
+
+      <note>
+	<title>Automatic Partitioning and LVM</title>
+         <para>
+	  The Automatic Partitioning option creates partitions as LVM volumes.
+         </para>
+      </note>
+
+   </section>
+
+
   </section>
 
 <!-- some notes follow:
@@ -278,14 +346,12 @@
       </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 supports advanced technologies
-      such as
-       <indexterm>
+      installation system.  Disk Druid supports <indexterm>
 	<primary>RAID</primary>
       </indexterm> <firstterm>RAID</firstterm> and
       <indexterm>
 	<primary>LVM</primary>
-      </indexterm> <firstterm>LVM</firstterm>, which provide more
+      </indexterm> <firstterm>LVM</firstterm> to provide more
       extensible and reliable data storage.
     </para>
 
@@ -330,10 +396,10 @@
 	      <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>
+	      </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
@@ -343,21 +409,13 @@
 	      </indexterm> <filename>/</filename> (root) partition.
 	    </para>
 	  </note>
-	  <important>
-	    <title>Root and <filename>/root</filename></title>
-	    <para>
-	      The <filename>/</filename> (or <indexterm>
-		<primary>partition</primary>
-		<secondary>root</secondary>
-	      </indexterm> "root") partition is the top of the file
-	      system.  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 administrator.
-	    </para>
-	  </important>
+          <important>
+           <title><filename>/boot</filename> may not be on an LVM volume</title>
+           <para>
+	       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:
@@ -482,7 +540,7 @@
 	  <para>
 	    If you need to make <emphasis>drastic</emphasis> changes to
 	    your partition configuration, you may want to delete
-	    partitions and start over.  If your disk contains data that
+	    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.
@@ -583,30 +641,13 @@
 	      <primary>LVM</primary>
 	    </indexterm> on your &FED; system. First create at least one
 	    partition or software RAID device as a LVM physical volume,
-	    using the <guilabel>Add</guilabel> option in the main
-	    <application>Disk Druid</application> dialog.
+	    using the <application>New</application> dialog.
 	  </para>
-	  <important>
-	    <title>Understanding LVM Components</title>
-	    <para>
-	      In LVM, <indexterm>
-		<primary>LVM</primary>
-		<secondary>understanding</secondary>
-	      </indexterm> one or more physical volumes are combined to
-	      form a volume group.  Each volume group's total storage
-	      may be apportioned for one or more logical volumes.
-	      Logical volumes function much like standard data
-	      partitions.  They have a file system type, such as ext3,
-	      and a mount point. An administrator can grow or shrink
-	      logical volumes without destroying data, unlike standard
-	      disk partitions.
-	    </para>
-	  </important>
 	  <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, create
-	    and/or edit logical volumes on any volume groups using the
+	    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>