From d631eec412a1557226c418cee463b00698115b75 Mon Sep 17 00:00:00 2001
From: "A. Wilcox" <AWilcox@Wilcox-Tech.com>
Date: Tue, 17 Sep 2019 15:09:41 -0500
Subject: script: 2: lvm_vg key without 1:1 lvm_pv mapping

`lvm_vg` may be used on systems with existing physical volumes.  Let's
allow that by removing the required 1:1 mapping with lvm_pv.
---
 devel/script/2_keys.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'devel')

diff --git a/devel/script/2_keys.xml b/devel/script/2_keys.xml
index 605df2d..c26b334 100644
--- a/devel/script/2_keys.xml
+++ b/devel/script/2_keys.xml
@@ -860,7 +860,7 @@ lvm_pv /dev/sda2
             </formalpara>
             <formalpara id="lvm_vg.format">
                 <title>Format</title>
-                <para>The <literal>lvm_vg</literal> key is a space-separated tuple of exactly two string values: a path to a valid block device containing an LVM physical volume, and a valid LVM volume group name.  A volume group will be created on the specified LVM physical volume with the specified name.  <literal>lvm_vg</literal> must appear exactly once per <literal>lvm_pv</literal> key.  It is invalid to specify a block device that does not contain an LVM physical volume.</para>
+                <para>The <literal>lvm_vg</literal> key is a space-separated tuple of exactly two string values: a path to a valid block device containing an LVM physical volume, and a valid LVM volume group name.  A volume group will be created on the specified LVM physical volume with the specified name.  It is invalid to specify a block device that does not contain an LVM physical volume.</para>
             </formalpara>
             <formalpara id="lvm_vg.default">
                 <title>Default</title>
-- 
cgit v1.2.3-70-g09d2