diff --git a/ChangeLog b/ChangeLog index 2d79dfaacfb267ae96bfa2066e30e3f1e0c01ee3..39e21fb72da97d32eb0aa6710d2e4fc3ebc10909 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Fri Mar 7 12:11:53 CET 2008 Daniel Veillard + + * docs/libvir.html docs/storage.html: apply documentation fixes + and typos cleanup from Atsushi Sakai + Fri Mar 7 10:22:00 CET 2008 Daniel Veillard * src/xend_internal.c: applied patch from Cole Robinson to not diff --git a/docs/libvir.html b/docs/libvir.html index a0be08451278d630547f8903107c1d31254c9733..d4c229ca344f85a0e7fff230fcf482b839623207 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -4069,7 +4069,7 @@ full capacity for storage volumes. This value is in bytes. This is not applicable when creating a pool.
available
-
Providing the free space available for allocating new volums +
Providing the free space available for allocating new volumes in the pool. Due to underlying device constraints it may not be possible to allocate the entire free space to a single volume. This value is in bytes. This is not applicable when creating a @@ -4119,11 +4119,11 @@ value for this, so it is optional.
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 tbe directory in which +be created. For device based pools it will be the name of the directory in which devices nodes exist. For the latter /dev/ may seem like the logical choice, however, devices nodes there are not -guarenteed stable across reboots, since they are allocated on -demand. It is preferrable to use a stable location such as one +guaranteed stable across reboots, since they are allocated on +demand. It is preferable to use a stable location such as one of the /dev/disk/by-{path,id,uuid,label locations.
permissions
@@ -4145,7 +4145,7 @@ contains the MAC (eg SELinux) label string. If a storage pool exposes information about its underlying placement / allocation scheme, the device element within the source element may contain information -about its avilable extents. Some pools have a constraint that +about its available extents. Some pools have a constraint that a volume must be allocated entirely within a single constraint (eg disk partition pools). Thus the extent information allows an application to determine the maximum possible size for a new @@ -4209,10 +4209,10 @@ on the local host.
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 tbe directory in which +be created. For device based pools it will be the name of the directory in which devices nodes exist. For the latter /dev/ may seem like the logical choice, however, devices nodes there are not -guarenteed stable across reboots, since they are allocated on +guaranteed stable across reboots, since they are allocated on demand. It is preferrable to use a stable location such as one of the /dev/disk/by-{path,id,uuid,label locations.
@@ -4297,10 +4297,10 @@ One of the following options:

When listing existing volumes all these formats are supported natively. When creating new volumes, only a subset may be -available. The raw type is guarenteed always +available. The raw type is guaranteed always available. The qcow2 type can be created if either qemu-img or qcow-create tools -are present. The others are dependant on support of the +are present. The others are dependent on support of the qemu-img tool.

Filesystem pool

@@ -4332,7 +4332,7 @@ required.
Valid pool format types

-The fileystem pool supports the following formats: +The filesystem pool supports the following formats: