External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-07 17:28:15 +00:00
Code

Fix documentation cut and paste errors, and a virsh typo.

Browse Source
This commit is contained in:
Cole Robinson 2008-12-04 14:51:57 +00:00
parent b9b9c8b020
commit 76944e8137
4 changed files with 13 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
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> Thu Dec 4 09:42:00 EST 2008 Cole Robinson <crobinso@redhat.com>
* src/qemu_driver.c: Increase timeout for initial monitor poll * src/qemu_driver.c: Increase timeout for initial monitor poll

15
docs/formatstorage.html.in
View File

@ -245,17 +245,10 @@
<dl> <dl>
<dt><code>path</code></dt> <dt><code>path</code></dt>
<dd>Provides the location at which the pool will be mapped into <dd>Provides the location at which the volume can be accessed on
the local filesystem namespace. For a filesystem/directory based the local filesystem, as an absolute path. This is a readonly
pool it will be the name of the directory in which volumes will attribute, so shouldn't be specified when creating a volume.
be created. For device based pools it will be the name of the directory in which <span class="since">Since 0.4.1</span></dd>
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>
<dt><code>format</code></dt> <dt><code>format</code></dt>
<dd>Provides information about the pool specific volume format. <dd>Provides information about the pool specific volume format.
For disk pools it will provide the partition type. For filesystem For disk pools it will provide the partition type. For filesystem

4
docs/storage.html.in
View File

@ -343,12 +343,12 @@ libvirt.
<h3>Valid pool format types</h3> <h3>Valid pool format types</h3>
<p> <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> </p>
<h3>Valid volume format types</h3> <h3>Valid volume format types</h3>
<p> <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> </p>
</body> </body>
</html> </html>

2
src/virsh.c
View File

@ -3168,7 +3168,7 @@ cmdPoolBuild(vshControl *ctl, const vshCmd *cmd)
return FALSE; return FALSE;
if (virStoragePoolBuild(pool, 0) == 0) { if (virStoragePoolBuild(pool, 0) == 0) {
vshPrint(ctl, _("Pool %s builded\n"), name); vshPrint(ctl, _("Pool %s built\n"), name);
} else { } else {
vshError(ctl, FALSE, _("Failed to build pool %s"), name); vshError(ctl, FALSE, _("Failed to build pool %s"), name);
ret = FALSE; ret = FALSE;