+Thu Dec 4 09:45:00 EST 2008 Cole Robinson <crobinso@redhat.com>
+
+ * docs/formatstorage.html.in docs/storage.html.in : Fix some
+ documentation copy and paste errors.
+ * src/virsh.c : Fix a typo
+
Thu Dec 4 09:42:00 EST 2008 Cole Robinson <crobinso@redhat.com>
* src/qemu_driver.c: Increase timeout for initial monitor poll
<dl>
<dt><code>path</code></dt>
- <dd>Provides the location at which the pool will be mapped into
- the local filesystem namespace. For a filesystem/directory based
- pool it will be the name of the directory in which volumes will
- be created. For device based pools it will be the name of the directory in which
- devices nodes exist. For the latter <code>/dev/</code> may seem
- like the logical choice, however, devices nodes there are not
- guaranteed stable across reboots, since they are allocated on
- demand. It is preferable to use a stable location such as one
- of the <code>/dev/disk/by-{path,id,uuid,label</code> locations.
- <span class="since">Since 0.4.1</span>
- </dd>
+ <dd>Provides the location at which the volume can be accessed on
+ the local filesystem, as an absolute path. This is a readonly
+ attribute, so shouldn't be specified when creating a volume.
+ <span class="since">Since 0.4.1</span></dd>
<dt><code>format</code></dt>
<dd>Provides information about the pool specific volume format.
For disk pools it will provide the partition type. For filesystem
<h3>Valid pool format types</h3>
<p>
- The logical volume pool does not use the pool format type element.
+ The iSCSI volume pool does not use the pool format type element.
</p>
<h3>Valid volume format types</h3>
<p>
- The logical volume pool does not use the volume format type element.
+ The iSCSI volume pool does not use the volume format type element.
</p>
</body>
</html>
return FALSE;
if (virStoragePoolBuild(pool, 0) == 0) {
- vshPrint(ctl, _("Pool %s builded\n"), name);
+ vshPrint(ctl, _("Pool %s built\n"), name);
} else {
vshError(ctl, FALSE, _("Failed to build pool %s"), name);
ret = FALSE;