"attach method" is from now on known as "backend".

This large, but mainly mechanical commit, renames "attach method"
everywhere to "backend".

Backwards compatibility of the API (guestfs_{set,get}_attach_method)
and environment (LIBGUESTFS_ATTACH_METHOD) is maintained, but in new
code use guestfs_{set,get}_backend and LIBGUESTFS_BACKEND instead.

The default backend (launching qemu directly) is now called 'direct'
instead of 'appliance', although you can still use 'appliance' as a
synonym.
This commit is contained in:
Richard W.M. Jones
2013-03-31 21:58:46 +01:00
parent f2b1a01e76
commit 68990840b6
32 changed files with 431 additions and 341 deletions

View File

@@ -1253,8 +1253,12 @@ Pass additional options to the guest kernel.
=item LIBGUESTFS_ATTACH_METHOD
This is the old way to set C<LIBGUESTFS_BACKEND>.
=item LIBGUESTFS_BACKEND
Choose the default way to create the appliance. See
L<guestfs(3)/guestfs_set_attach_method>.
L<guestfs(3)/guestfs_set_backend>.
=item LIBGUESTFS_CACHEDIR
@@ -1313,7 +1317,7 @@ set, it uses C<more>.
Libguestfs and guestfish may run some external programs, and rely on
C<$PATH> being set to a reasonable value. If using the libvirt
attach-method, libvirt will not work at all unless C<$PATH> contains
backend, libvirt will not work at all unless C<$PATH> contains
the path of qemu/KVM.
=item SUPERMIN_KERNEL