Change libvirtd description from qemu only to various VM(i.e. Xen, LXC)

Fix typos and comments
This commit is contained in:
Atsushi SAKAI 2008-05-15 06:12:32 +00:00
parent 0857814dce
commit b87f3000aa
18 changed files with 31 additions and 22 deletions

View File

@ -1,3 +1,12 @@
Thu May 15 15:07:49 JST 2008 Atsushi SAKAI <sakaia@jp.fujitsu.com>
* qemud/libvirtd.init.in: change libvirtd description
which supports various guest not only Qemu
* docs/*: typo fixes
* include/libvirt/libvirt.h, include/libvirt/libvirt.h.in,
qemud/event.c, qemud/qemud.c, qemud/remote.c,
src/event.c, src/proxy_internal.c: typo fixes in comment
Wed May 14 23:17:55 CEST 2008 Jim Meyering <meyering@redhat.com>
exempt gnulib/ from "make syntax-check" strcmp prohibition

View File

@ -117,7 +117,7 @@
<dl><dt><a href="http://virt-manager.org/">virt-manager</a></dt><dd>
A general purpose desktop management tool, able to manage
virtual machines across both local and remotely accessed
hypervisors. It is targetted at home and small office usage
hypervisors. It is targeted at home and small office usage
upto managing 10-20 hosts and their VMs.
</dd><dt><a href="http://virt-manager.org/">virt-viewer</a></dt><dd>
A lightweight tool for accessing the graphical console

View File

@ -67,7 +67,7 @@
<dd>
A general purpose desktop management tool, able to manage
virtual machines across both local and remotely accessed
hypervisors. It is targetted at home and small office usage
hypervisors. It is targeted at home and small office usage
upto managing 10-20 hosts and their VMs.
</dd>
<dt><a href="http://virt-manager.org/">virt-viewer</a></dt>

View File

@ -130,7 +130,7 @@
</pre>
<h2>Built from CVS / GIT</h2>
<p>
When building from CVS it is neccessary to generate the autotools
When building from CVS it is necessary to generate the autotools
support files. This requires having <code>autoconf</code>,
<code>automake</code>, <code>libtool</code> and <code>intltool</code>
installed. The process can be automated with the <code>autogen.sh</code>

View File

@ -28,7 +28,7 @@
<h2>Built from CVS / GIT</h2>
<p>
When building from CVS it is neccessary to generate the autotools
When building from CVS it is necessary to generate the autotools
support files. This requires having <code>autoconf</code>,
<code>automake</code>, <code>libtool</code> and <code>intltool</code>
installed. The process can be automated with the <code>autogen.sh</code>

View File

@ -15,7 +15,7 @@
# mysqladmin -u root password new_password
# Create the new database libvir
# mysqladmin -p create libvir
# Create a database user 'veillard' and give him passord access
# Create a database user 'veillard' and give him password access
# change veillard and abcde with the right user name and passwd
# mysql -p
# password:
@ -55,7 +55,7 @@ def callback(ctx, str):
libxml2.registerErrorHandler(callback, None)
#
# The dictionnary of tables required and the SQL command needed
# The dictionary of tables required and the SQL command needed
# to create them
#
TABLES={
@ -449,7 +449,7 @@ def updateWordArchive(name, id, relevance):
#########################################################################
# #
# Word dictionnary and analysis routines #
# Word dictionary and analysis routines #
# #
#########################################################################

View File

@ -128,7 +128,7 @@ generic and stable layer to manage domains on a node.</p>
though Xen is the current default, which also means that some very
specific capabilities which are not generic enough may not be provided as
libvirt APIs</li><li>the API should allow to do efficiently and cleanly all the operations
needed to manage domains on a node</li><li>the API will not try to provide hight level multi-nodes management
needed to manage domains on a node</li><li>the API will not try to provide high level multi-nodes management
features like load balancing, though they could be implemented on top of
libvirt</li><li>stability of the API is a big concern, libvirt should isolate
applications from the frequent changes expected at the lower level of the

View File

@ -28,7 +28,7 @@ generic and stable layer to manage domains on a node.</p>
libvirt APIs</li>
<li>the API should allow to do efficiently and cleanly all the operations
needed to manage domains on a node</li>
<li>the API will not try to provide hight level multi-nodes management
<li>the API will not try to provide high level multi-nodes management
features like load balancing, though they could be implemented on top of
libvirt</li>
<li>stability of the API is a big concern, libvirt should isolate

View File

@ -75,7 +75,7 @@ some of the existing code ?
Pros:
- avoid the GPL Licence problem potentially more users
- allow do build a cleaner more stable layer
- the existing code is frigthening
- the existing code is frightening
Cons:
- awful lot of work debugging very hard
- will still require existing Xen code to be running
@ -93,7 +93,7 @@ some of the existing code ?
Potentially the API could be implemented as a layer on top of the existing
libxc C code library and then progressively migrating out the existing
dependance to Xen code as the interfaces stabilize.
dependence to Xen code as the interfaces stabilize.
Daniel Veillard <veillard@redhat.com>

View File

@ -531,7 +531,7 @@ L<xm(1)>, L<xmdomain.cfg(5)>, L<xentop(1)> , L<http://www.libvirt.org/>
=head1 BUGS
Bugs can be view on the RedHat buzilla page under the libvirt
Bugs can be view on the RedHat bugzilla page under the libvirt
L<https://bugzilla.redhat.com/>
L<https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora+Core&component=libvirt&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=MODIFIED&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr>

View File

@ -363,7 +363,7 @@ extern virConnectAuthPtr virConnectAuthPtrDefault;
#define VIR_UUID_STRING_BUFLEN (36+1)
/* library versionning */
/* library versioning */
/**
* LIBVIR_VERSION_NUMBER:

View File

@ -363,7 +363,7 @@ extern virConnectAuthPtr virConnectAuthPtrDefault;
#define VIR_UUID_STRING_BUFLEN (36+1)
/* library versionning */
/* library versioning */
/**
* LIBVIR_VERSION_NUMBER:

View File

@ -1,5 +1,5 @@
/*
* event.h: event loop for monitoring file handles
* event.c: event loop for monitoring file handles
*
* Copyright (C) 2007 Daniel P. Berrange
* Copyright (C) 2007 Red Hat, Inc.

View File

@ -8,17 +8,17 @@
# Should-Start: xend
# Default-Start: 3 4 5
# Short-Description: daemon for libvirt virtualization API
# Description: This is a daemon for managing QEMU guest instances
# Description: This is a daemon for managing guest instances
# and libvirt virtual networks
# See http://libvirt.org
### END INIT INFO
# the following is chkconfig init header
#
# libvirtd: QEMU and virtual network management daemon
# libvirtd: guest and virtual network management daemon
#
# chkconfig: 345 97 03
# description: This is a daemon for managing QEMU guest instances
# description: This is a daemon for managing guest instances
# and libvirt virtual networks
# See http://libvirt.org
#

View File

@ -1115,7 +1115,7 @@ static int qemudDispatchServer(struct qemud_server *server, struct qemud_socket
if (qemudGetSocketIdentity(client->fd, &uid, &pid) < 0)
goto cleanup;
/* Cient is running as root, so disable auth */
/* Client is running as root, so disable auth */
if (uid == 0) {
qemudLog(QEMUD_INFO, _("Turn off polkit auth for privileged client %d"), pid);
client->auth = REMOTE_AUTH_NONE;

View File

@ -2111,7 +2111,7 @@ static char *addrToString(struct qemud_client *client,
/*
* Initializes the SASL session in prepare for authentication
* and gives the client a list of allowed mechansims to choose
* and gives the client a list of allowed mechanisms to choose
*
* XXX callbacks for stuff like password verification ?
*/

View File

@ -1,5 +1,5 @@
/*
* event.h: event loop for monitoring file handles
* event.c: event loop for monitoring file handles
*
* Copyright (C) 2007 Daniel P. Berrange
* Copyright (C) 2007 Red Hat, Inc.

View File

@ -223,7 +223,7 @@ retry_wait:
/**
* virProxyOpenClientSocket:
* @path: the fileame for the socket
* @path: the filename for the socket
*
* try to connect to the socket open by libvirt_proxy
*