Update section on partitioning using LVM to reflect recent changes

5 files changed, 108 insertions, 61 deletions

diff --git a/build/templates/docstruct.ent b/build/templates/docstruct.ent
index 583ed4689..925bc2fa4 100644
--- a/build/templates/docstruct.ent
+++ b/build/templates/docstruct.ent
@@ -115,7 +115,7 @@
   <!ENTITY module-autopartkit.xml        SYSTEM "##SRCPATH##/using-d-i/modules/autopartkit.xml">
   <!ENTITY module-partitioner.xml        SYSTEM "##SRCPATH##/using-d-i/modules/partitioner.xml">
   <!ENTITY module-partconf.xml           SYSTEM "##SRCPATH##/using-d-i/modules/partconf.xml">
-  <!ENTITY module-lvmcfg.xml             SYSTEM "##SRCPATH##/using-d-i/modules/lvmcfg.xml">
+  <!ENTITY module-partman-lvm.xml        SYSTEM "##SRCPATH##/using-d-i/modules/partman-lvm.xml">
   <!ENTITY module-mdcfg.xml              SYSTEM "##SRCPATH##/using-d-i/modules/mdcfg.xml">
   <!ENTITY module-partman-crypto.xml     SYSTEM "##SRCPATH##/using-d-i/modules/partman-crypto.xml">
   <!ENTITY module-finish-install.xml     SYSTEM "##SRCPATH##/using-d-i/modules/finish-install.xml">
diff --git a/debian/changelog b/debian/changelog
index 59cd5568f..6d2ad42ca 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,8 +9,9 @@ installation-guide (2006xxxx) UNRELEASED; urgency=low
   * Update instructions on how to set module parameters for PLIP installation.
   * Update chroot install instructions to use aptitude instead of apt-get.
   * Add /srv in overview of directory tree in partitioning appendix.
+  * Update section on partitioning using LVM to reflect recent changes.
 
- -- Frans Pop <fjp@debian.org>  Sun, 30 Jul 2006 17:01:38 +0200
+ -- Frans Pop <fjp@debian.org>  Wed,  2 Aug 2006 20:48:17 +0200
 
 installation-guide (20060726) unstable; urgency=low
 
diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml
index 453bb9388..0d0570fd2 100644
--- a/en/using-d-i/components.xml
+++ b/en/using-d-i/components.xml
@@ -72,8 +72,8 @@ like LVM or RAID devices.
 &module-autopartkit.xml;
 &module-partitioner.xml;
 &module-partconf.xml;
-&module-lvmcfg.xml;
 &module-mdcfg.xml;
+&module-partman-lvm.xml;
 &module-partman-crypto.xml;
   </sect2>
   
diff --git a/en/using-d-i/modules/lvmcfg.xml b/en/using-d-i/modules/lvmcfg.xml
deleted file mode 100644
index 6d7fae931..000000000
--- a/en/using-d-i/modules/lvmcfg.xml
+++ /dev/null
@@ -1,58 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-   <sect3 id="lvmcfg">
-   <title>Configuring Logical Volume Manager (LVM)</title>
-<para>
-
-If you are working with computers at the level of system administrator
-or <quote>advanced</quote> user, you have surely seen the situation
-where some disk partition (usually the most important one) was short on
-space, while some other partition was grossly underused and you had to
-manage this situation with moving stuff around, symlinking, etc.
-
-</para><para>
-
-To avoid the described situation you can use Logical Volume Manager
-(LVM). Simply said, with LVM you can combine your partitions
-(<firstterm>physical volumes</firstterm> in LVM lingo) to form
-a virtual disc (so called <firstterm>volume group</firstterm>), which
-can then be divided into virtual partitions (<firstterm>logical
-volumes</firstterm>). The point is that logical volumes (and of course
-underlying volume groups) can span across several physical discs.
-
-</para><para>
-
-Now when you realize you need more space for your old 160GB
-<filename>/home</filename> partition, you can simply add a new 300GB
-disc to the computer, join it with your existing volume group and then
-resize the logical volume which holds your <filename>/home</filename>
-filesystem and voila &mdash; your users have some room again on their
-renewed 460GB partition.  This example is of course a bit
-oversimplified. If you haven't read it yet, you should consult the
-<ulink url="&url-lvm-howto;">LVM HOWTO</ulink>.
-
-</para><para>
-
-LVM setup in &d-i; is quite simple. At first, you have to mark your
-partitions to be used as physical volumes for LVM. (This is done in
-<command>partman</command> in the <guimenu>Partition
-settings</guimenu> menu where you should select <menuchoice>
-<guimenu>Use as:</guimenu> <guimenuitem>physical volume for
-LVM</guimenuitem> </menuchoice>.) Then start the
-<command>lvmcfg</command> module (either directly from
-<command>partman</command> or from the &d-i;'s main menu) and combine
-physical volumes to volume group(s) under the <guimenuitem>Modify
-volume groups (VG)</guimenuitem> menu. After that, you should create
-logical volumes on the top of volume groups from the menu
-<guimenuitem>Modify logical volumes (LV)</guimenuitem>.
-
-</para><para>
-
-After returning from <command>lvmcfg</command> back to
-<command>partman</command>, you will see any created logical volumes
-in the same way as ordinary partitions (and you should treat them like
-that).
-
-</para>
-   </sect3>
diff --git a/en/using-d-i/modules/partman-lvm.xml b/en/using-d-i/modules/partman-lvm.xml
new file mode 100644
index 000000000..4feadedc1
--- /dev/null
+++ b/en/using-d-i/modules/partman-lvm.xml
@@ -0,0 +1,104 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- $Id$ -->
+
+   <sect3 id="partman-lvm">
+   <title>Configuring the Logical Volume Manager (LVM)</title>
+<para>
+
+If you are working with computers at the level of system administrator
+or <quote>advanced</quote> user, you have surely seen the situation
+where some disk partition (usually the most important one) was short on
+space, while some other partition was grossly underused and you had to
+manage this situation with moving stuff around, symlinking, etc.
+
+</para><para>
+
+To avoid the described situation you can use Logical Volume Manager
+(LVM). Simply said, with LVM you can combine your partitions
+(<firstterm>physical volumes</firstterm> in LVM lingo) to form
+a virtual disk (so called <firstterm>volume group</firstterm>), which
+can then be divided into virtual partitions (<firstterm>logical
+volumes</firstterm>). The point is that logical volumes (and of course
+underlying volume groups) can span across several physical disks.
+
+</para><para>
+
+Now when you realize you need more space for your old 160GB
+<filename>/home</filename> partition, you can simply add a new 300GB
+disk to the computer, join it with your existing volume group and then
+resize the logical volume which holds your <filename>/home</filename>
+filesystem and voila &mdash; your users have some room again on their
+renewed 460GB partition.  This example is of course a bit
+oversimplified. If you haven't read it yet, you should consult the
+<ulink url="&url-lvm-howto;">LVM HOWTO</ulink>.
+
+</para><para>
+
+LVM setup in &d-i; is quite simple and completely supported inside
+<command>partman</command>. First, you have to mark the partition(s)
+to be used as physical volumes for LVM. This is done in the
+<guimenu>Partition settings</guimenu> menu where you should select
+<menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume
+for LVM</guimenuitem> </menuchoice>.
+
+</para><para>
+
+When you return to the main <command>partman</command> screen, you will see
+a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>.
+When you select that, you will first be asked to confirm pending changes to
+the partition table (if any) and after that the LVM configuration menu will
+be shown. Above the menu a summary of the LVM configuration is shown. The
+menu itself is context sensitive and only shows valid actions. The possible
+actions are:
+
+<itemizedlist>
+  <listitem><para>
+    <guimenuitem>Display configuration details</guimenuitem>:
+    shows LVM device structure, names and sizes of logical volumes and more
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Create volume group</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Create logical volume</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Delete volume group</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Delete logical volume</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Extend volume group</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Reduce volume group</guimenuitem>
+  </para></listitem>
+  <listitem><para>
+    <guimenuitem>Finish</guimenuitem>:
+    return to the main <command>partman</command> screen
+  </para></listitem>
+</itemizedlist>
+
+</para><para>
+
+Use the options in that menu to first create a volume group and then create
+your logical volumes inside it.
+
+</para>
+<note><para>
+
+You can also use this menu to delete an existing LVM configuration from
+your hard disk before choosing <quote>Guided partitioning using LVM</quote>.
+Guided partitioning using LVM is not possible if there already are volume
+groups defined, but by removing them you can get a clean start.
+
+</para></note>
+<para>
+
+After you return to the main <command>partman</command> screen, any created
+logical volumes will be displayed in the same way as ordinary partitions
+(and you should treat them as such).
+
+</para>
+   </sect3>