From 8ad79a7c4de406579cf38d938edf44a8b659d03a Mon Sep 17 00:00:00 2001 From: Richard Jones Date: Thu, 2 Sep 2010 22:25:47 +0100 Subject: [PATCH] Add full docs pot file. --- Makefile.am | 5 +- po-docs/ja.po | 25865 +++++++++++++++++++++++++++++++++++++++++- po-docs/ja/Makefile.am | 16 +- po-docs/libguestfs-docs.pot | 25428 ++++++++++++++++++++++++++++++++++++++++- 4 files changed, 51308 insertions(+), 6 deletions(-) diff --git a/Makefile.am b/Makefile.am index 085202b..ce2f940 100644 --- a/Makefile.am +++ b/Makefile.am @@ -20,7 +20,7 @@ include $(top_srcdir)/subdir-rules.mk ACLOCAL_AMFLAGS = -I m4 # Basic source for the library. -SUBDIRS = gnulib/lib images src examples po po-docs +SUBDIRS = gnulib/lib images src examples po if ENABLE_DAEMON SUBDIRS += daemon @@ -68,6 +68,9 @@ if HAVE_FUSE SUBDIRS += fuse endif +# po-docs must come after tools, inspector. +SUBDIRS += po-docs + EXTRA_DIST = \ $(generator_built) \ html/pod.css \ diff --git a/po-docs/ja.po b/po-docs/ja.po index 9b31391..95acacc 100644 --- a/po-docs/ja.po +++ b/po-docs/ja.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: libguestfs@redhat.com\n" -"POT-Creation-Date: 2010-09-02 14:43+0200\n" +"POT-Creation-Date: 2010-09-02 20:33+0200\n" "PO-Revision-Date: 2010-09-02 14:46+0100\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -15,6 +15,18 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +# type: =encoding +#: ../src/guestfs.pod:1 ../fish/guestfish.pod:1 +#: ../test-tool/libguestfs-test-tool.pod:1 ../fuse/guestmount.pod:1 +#: ../inspector/virt-inspector.pl:36 ../tools/virt-cat.pl:30 +#: ../tools/virt-df.pl:32 ../tools/virt-edit.pl:31 +#: ../tools/virt-list-filesystems.pl:28 ../tools/virt-list-partitions.pl:28 +#: ../tools/virt-ls.pl:31 ../tools/virt-make-fs.pl:33 +#: ../tools/virt-rescue.pl:29 ../tools/virt-resize.pl:38 +#: ../tools/virt-tar.pl:30 ../tools/virt-win-reg.pl:34 +msgid "utf8" +msgstr "" + # type: =head1 #: ../src/guestfs.pod:3 ../fish/guestfish.pod:3 #: ../test-tool/libguestfs-test-tool.pod:3 ../fuse/guestmount.pod:3 @@ -26,3 +38,25854 @@ msgstr "" #: ../tools/virt-tar.pl:32 ../tools/virt-win-reg.pl:36 msgid "NAME" msgstr "名前" + +# type: textblock +#: ../src/guestfs.pod:5 +msgid "guestfs - Library for accessing and modifying virtual machine images" +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:7 ../fish/guestfish.pod:7 +#: ../test-tool/libguestfs-test-tool.pod:7 ../fuse/guestmount.pod:7 +#: ../inspector/virt-inspector.pl:42 ../tools/virt-cat.pl:36 +#: ../tools/virt-df.pl:38 ../tools/virt-edit.pl:37 +#: ../tools/virt-list-filesystems.pl:34 ../tools/virt-list-partitions.pl:34 +#: ../tools/virt-ls.pl:37 ../tools/virt-make-fs.pl:39 +#: ../tools/virt-rescue.pl:35 ../tools/virt-resize.pl:44 +#: ../tools/virt-tar.pl:36 ../tools/virt-win-reg.pl:40 +msgid "SYNOPSIS" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:9 +#, no-wrap +msgid "" +" #include \n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:11 +#, no-wrap +msgid "" +" guestfs_h *g = guestfs_create ();\n" +" guestfs_add_drive (g, \"guest.img\");\n" +" guestfs_launch (g);\n" +" guestfs_mount (g, \"/dev/sda1\", \"/\");\n" +" guestfs_touch (g, \"/hello\");\n" +" guestfs_umount (g, \"/\");\n" +" guestfs_sync (g);\n" +" guestfs_close (g);\n" +"\n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:20 +#, no-wrap +msgid "" +" cc prog.c -o prog -lguestfs\n" +"or:\n" +" cc prog.c -o prog `pkg-config libguestfs --cflags --libs`\n" +"\n" +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:24 ../fish/guestfish.pod:115 +#: ../test-tool/libguestfs-test-tool.pod:11 ../fuse/guestmount.pod:16 +#: ../inspector/virt-inspector.pl:48 ../tools/virt-cat.pl:42 +#: ../tools/virt-df.pl:46 ../tools/virt-edit.pl:51 +#: ../tools/virt-list-filesystems.pl:40 ../tools/virt-list-partitions.pl:40 +#: ../tools/virt-ls.pl:43 ../tools/virt-make-fs.pl:47 +#: ../tools/virt-rescue.pl:51 ../tools/virt-resize.pl:50 +#: ../tools/virt-tar.pl:73 ../tools/virt-win-reg.pl:64 +msgid "DESCRIPTION" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:26 +msgid "" +"Libguestfs is a library for accessing and modifying guest disk images. " +"Amongst the things this is good for: making batch configuration changes to " +"guests, getting disk used/free statistics (see also: virt-df), migrating " +"between virtualization systems (see also: virt-p2v), performing partial " +"backups, performing partial guest clones, cloning guests and changing " +"registry/UUID/hostname info, and much else besides." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:34 +msgid "" +"Libguestfs uses Linux kernel and qemu code, and can access any type of guest " +"filesystem that Linux and qemu can, including but not limited to: ext2/3/4, " +"btrfs, FAT and NTFS, LVM, many different disk partition schemes, qcow, " +"qcow2, vmdk." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:39 +msgid "" +"Libguestfs provides ways to enumerate guest storage (eg. partitions, LVs, " +"what filesystem is in each LV, etc.). It can also run commands in the " +"context of the guest. Also you can access filesystems over FUSE." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:44 +msgid "" +"Libguestfs is a library that can be linked with C and C++ management " +"programs (or management programs written in OCaml, Perl, Python, Ruby, Java, " +"Haskell or C#). You can also use it from shell scripts or the command line." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:49 +msgid "" +"You don't need to be root to use libguestfs, although obviously you do need " +"enough permissions to access the disk images." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:52 +msgid "" +"Libguestfs is a large API because it can do many things. For a gentle " +"introduction, please read the L section next." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:55 +msgid "API OVERVIEW" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:57 +msgid "" +"This section provides a gentler overview of the libguestfs API. We also try " +"to group API calls together, where that may not be obvious from reading " +"about the individual calls in the main section of this manual." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:62 +msgid "HANDLES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:64 +msgid "" +"Before you can use libguestfs calls, you have to create a handle. Then you " +"must add at least one disk image to the handle, followed by launching the " +"handle, then performing whatever operations you want, and finally closing " +"the handle. By convention we use the single letter C for the name of the " +"handle variable, although of course you can use any name you want." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:71 +msgid "The general structure of all libguestfs-using programs looks like this:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:74 +#, no-wrap +msgid "" +" guestfs_h *g = guestfs_create ();\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:76 +#, no-wrap +msgid "" +" /* Call guestfs_add_drive additional times if there are\n" +" * multiple disk images.\n" +" */\n" +" guestfs_add_drive (g, \"guest.img\");\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:81 +#, no-wrap +msgid "" +" /* Most manipulation calls won't work until you've launched\n" +" * the handle 'g'. You have to do this _after_ adding drives\n" +" * and _before_ other commands.\n" +" */\n" +" guestfs_launch (g);\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:87 +#, no-wrap +msgid "" +" /* Now you can examine what partitions, LVs etc are available.\n" +" */\n" +" char **partitions = guestfs_list_partitions (g);\n" +" char **logvols = guestfs_lvs (g);\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:92 +#, no-wrap +msgid "" +" /* To access a filesystem in the image, you must mount it.\n" +" */\n" +" guestfs_mount (g, \"/dev/sda1\", \"/\");\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:96 +#, no-wrap +msgid "" +" /* Now you can perform filesystem actions on the guest\n" +" * disk image.\n" +" */\n" +" guestfs_touch (g, \"/hello\");\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:101 +#, no-wrap +msgid "" +" /* You only need to call guestfs_sync if you have made\n" +" * changes to the guest image. (But if you've made changes\n" +" * then you *must* sync). See also: guestfs_umount and\n" +" * guestfs_umount_all calls.\n" +" */\n" +" guestfs_sync (g);\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:108 +#, no-wrap +msgid "" +" /* Close the handle 'g'. */\n" +" guestfs_close (g);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:111 +msgid "" +"The code above doesn't include any error checking. In real code you should " +"check return values carefully for errors. In general all functions that " +"return integers return C<-1> on error, and all functions that return " +"pointers return C on error. See section L below for " +"how to handle errors, and consult the documentation for each function call " +"below to see precisely how they return error indications." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:119 +msgid "DISK IMAGES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:121 +msgid "" +"The image filename (C<\"guest.img\"> in the example above) could be a disk " +"image from a virtual machine, a L copy of a physical hard disk, an " +"actual block device, or simply an empty file of zeroes that you have created " +"through L. Libguestfs lets you do useful things to all " +"of these." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:127 +msgid "" +"You can add a disk read-only using L, in which case " +"libguestfs won't modify the file." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:130 +msgid "" +"Be extremely cautious if the disk image is in use, eg. if it is being used " +"by a virtual machine. Adding it read-write will almost certainly cause disk " +"corruption, but adding it read-only is safe." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:134 +msgid "" +"You must add at least one disk image, and you may add multiple disk images. " +"In the API, the disk images are usually referred to as C (for the " +"first one you added), C (for the second one you added), etc." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:139 +msgid "" +"Once L has been called you cannot add any more images. You " +"can call L to get a list of the device names, in the " +"order that you added them. See also L below." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:144 +msgid "MOUNTING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:146 +msgid "" +"Before you can read or write files, create directories and so on in a disk " +"image that contains filesystems, you have to mount those filesystems using " +"L. If you already know that a disk image contains (for " +"example) one partition with a filesystem on that partition, then you can " +"mount it directly:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:152 +#, no-wrap +msgid "" +" guestfs_mount (g, \"/dev/sda1\", \"/\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:154 +msgid "" +"where C means literally the first partition (C<1>) of the first " +"disk image that we added (C). If the disk contains Linux LVM2 " +"logical volumes you could refer to those instead (eg. C)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:158 +msgid "" +"If you are given a disk image and you don't know what it contains then you " +"have to find out. Libguestfs can do that too: use L and L to list possible partitions and " +"LVs, and either try mounting each to see what is mountable, or else examine " +"them with L or L. Libguestfs also has a " +"set of APIs for inspection of disk images (see L below). But " +"you might find it easier to look at higher level programs built on top of " +"libguestfs, in particular L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:168 +msgid "" +"To mount a disk image read-only, use L. There are " +"several other variations of the C call." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:171 +msgid "FILESYSTEM ACCESS AND MODIFICATION" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:173 +msgid "" +"The majority of the libguestfs API consists of fairly low-level calls for " +"accessing and modifying the files, directories, symlinks etc on mounted " +"filesystems. There are over a hundred such calls which you can find listed " +"in detail below in this man page, and we don't even pretend to cover them " +"all in this overview." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:179 +msgid "" +"Specify filenames as full paths, starting with C<\"/\"> and including the " +"mount point." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:182 +msgid "" +"For example, if you mounted a filesystem at C<\"/\"> and you want to read " +"the file called C<\"etc/passwd\"> then you could do:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:185 +#, no-wrap +msgid "" +" char *data = guestfs_cat (g, \"/etc/passwd\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:187 +msgid "" +"This would return C as a newly allocated buffer containing the full " +"content of that file (with some conditions: see also L below), " +"or C if there was an error." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:191 +msgid "" +"As another example, to create a top-level directory on that filesystem " +"called C<\"var\"> you would do:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:194 +#, no-wrap +msgid "" +" guestfs_mkdir (g, \"/var\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:196 +msgid "To create a symlink you could do:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:198 +#, no-wrap +msgid "" +" guestfs_ln_s (g, \"/etc/init.d/portmap\",\n" +" \"/etc/rc3.d/S30portmap\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:201 +msgid "" +"Libguestfs will reject attempts to use relative paths and there is no " +"concept of a current working directory." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:204 +msgid "" +"Libguestfs can return errors in many situations: for example if the " +"filesystem isn't writable, or if a file or directory that you requested " +"doesn't exist. If you are using the C API (documented here) you have to " +"check for those error conditions after each call. (Other language bindings " +"turn these errors into exceptions)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:210 +msgid "" +"File writes are affected by the per-handle umask, set by calling L and defaulting to 022. See L." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:213 +msgid "PARTITIONING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:215 +msgid "" +"Libguestfs contains API calls to read, create and modify partition tables on " +"disk images." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:218 +msgid "" +"In the common case where you want to create a single partition covering the " +"whole disk, you should use the L call:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:222 +#, no-wrap +msgid "" +" const char *parttype = \"mbr\";\n" +" if (disk_is_larger_than_2TB)\n" +" parttype = \"gpt\";\n" +" guestfs_part_disk (g, \"/dev/sda\", parttype);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:227 +msgid "" +"Obviously this effectively wipes anything that was on that disk image before." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:230 +msgid "LVM2" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:232 +msgid "" +"Libguestfs provides access to a large part of the LVM2 API, such as L and L. It won't make much sense unless " +"you familiarize yourself with the concepts of physical volumes, volume " +"groups and logical volumes." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:237 +msgid "" +"This author strongly recommends reading the LVM HOWTO, online at L." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:240 +msgid "DOWNLOADING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:242 +msgid "" +"Use L to download small, text only files. This call is " +"limited to files which are less than 2 MB and which cannot contain any ASCII " +"NUL (C<\\0>) characters. However it has a very simple to use API." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:247 +msgid "" +"L can be used to read files which contain arbitrary 8 " +"bit data, since it returns a (pointer, size) pair. However it is still " +"limited to \"small\" files, less than 2 MB." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:251 +msgid "" +"L can be used to download any file, with no limits on " +"content or size (even files larger than 4 GB)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:254 +msgid "" +"To download multiple files, see L and L." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:257 +msgid "UPLOADING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:259 +msgid "" +"It's often the case that you want to write a file or files to the disk image." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:262 +msgid "" +"To write a small file with fixed content, use L. To create " +"a file of all zeroes, use L (sparse) or L (with all disk blocks allocated). There are a variety " +"of other functions for creating test files, for example L and " +"L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:268 +msgid "" +"To upload a single file, use L. This call has no limits on " +"file content or size (even files larger than 4 GB)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:271 +msgid "" +"To upload multiple files, see L and L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:273 +msgid "" +"However the fastest way to upload I is to " +"turn them into a squashfs or CD ISO (see L and L), then attach this using L. If you add the drive " +"in a predictable way (eg. adding it last after all other drives) then you " +"can get the device name from L and mount it directly " +"using L. Note that squashfs images are sometimes non-" +"portable between kernel versions, and they don't support labels or UUIDs. " +"If you want to pre-build an image or you need to mount it using a label or " +"UUID, use an ISO image instead." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:284 +msgid "COPYING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:286 +msgid "" +"There are various different commands for copying between files and devices " +"and in and out of the guest filesystem. These are summarised in the table " +"below." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:292 +msgid "B to B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:294 +msgid "" +"Use L to copy a single file, or L to copy " +"directories recursively." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:297 +msgid "B to B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:299 +msgid "" +"Use L which efficiently uses L to copy between files and " +"devices in the guest." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:302 +msgid "Example: duplicate the contents of an LV:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:304 +#, no-wrap +msgid "" +" guestfs_dd (g, \"/dev/VG/Original\", \"/dev/VG/Copy\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:306 +msgid "" +"The destination (C) must be at least as large as the source " +"(C). To copy less than the whole source device, use L." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:310 +msgid "B to B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:312 +msgid "Use L. See L above." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:314 +msgid "B to B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:316 +msgid "Use L. See L above." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:320 +msgid "LISTING FILES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:322 +msgid "" +"L is just designed for humans to read (mainly when using the " +"L-equivalent command C)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:325 +msgid "" +"L is a quick way to get a list of files in a directory from " +"programs, as a flat list of strings." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:328 +msgid "" +"L is a programmatic way to get a list of files in a " +"directory, plus additional information about each one. It is more " +"equivalent to using the L call on a local filesystem." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:332 +msgid "" +"L and L can be used to recursively list files." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:335 +msgid "RUNNING COMMANDS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:337 +msgid "" +"Although libguestfs is a primarily an API for manipulating files inside " +"guest images, we also provide some limited facilities for running commands " +"inside guests." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:341 +msgid "There are many limitations to this:" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:345 ../src/guestfs.pod:350 ../src/guestfs.pod:355 +#: ../src/guestfs.pod:359 ../src/guestfs.pod:364 ../src/guestfs.pod:368 +#: ../src/guestfs.pod:373 ../src/guestfs.pod:1214 ../src/guestfs.pod:1219 +#: ../src/guestfs.pod:1223 ../src/guestfs.pod:1325 ../src/guestfs.pod:1329 +#: ../src/guestfs.pod:1333 ../src/guestfs.pod:1338 ../src/guestfs.pod:1346 +#: ../src/guestfs.pod:1365 ../src/guestfs.pod:1373 ../src/guestfs.pod:1587 +#: ../src/guestfs.pod:1593 ../src/guestfs.pod:1598 ../src/guestfs.pod:1604 +#: ../src/guestfs.pod:1711 ../src/guestfs.pod:1715 ../src/guestfs.pod:1719 +#: ../src/guestfs.pod:1723 ../src/guestfs-actions.pod:14 +#: ../src/guestfs-actions.pod:21 ../src/guestfs-actions.pod:372 +#: ../src/guestfs-actions.pod:380 ../src/guestfs-actions.pod:387 +#: ../src/guestfs-actions.pod:394 ../src/guestfs-actions.pod:1257 +#: ../src/guestfs-actions.pod:1261 ../src/guestfs-actions.pod:1265 +#: ../src/guestfs-actions.pod:1269 ../src/guestfs-actions.pod:1277 +#: ../src/guestfs-actions.pod:1281 ../src/guestfs-actions.pod:1285 +#: ../src/guestfs-actions.pod:1295 ../src/guestfs-actions.pod:1299 +#: ../src/guestfs-actions.pod:1303 ../src/guestfs-actions.pod:1426 +#: ../src/guestfs-actions.pod:1430 ../src/guestfs-actions.pod:1435 +#: ../src/guestfs-actions.pod:1440 ../src/guestfs-actions.pod:1492 +#: ../src/guestfs-actions.pod:1496 ../src/guestfs-actions.pod:1501 +#: ../fish/guestfish.pod:309 ../fish/guestfish.pod:313 +#: ../fish/guestfish.pod:317 ../fish/guestfish.pod:321 +#: ../fish/guestfish-actions.pod:13 ../fish/guestfish-actions.pod:20 +#: ../fish/guestfish-actions.pod:300 ../fish/guestfish-actions.pod:308 +#: ../fish/guestfish-actions.pod:315 ../fish/guestfish-actions.pod:322 +#: ../fish/guestfish-actions.pod:998 ../fish/guestfish-actions.pod:1002 +#: ../fish/guestfish-actions.pod:1006 ../fish/guestfish-actions.pod:1010 +#: ../fish/guestfish-actions.pod:1018 ../fish/guestfish-actions.pod:1022 +#: ../fish/guestfish-actions.pod:1026 ../fish/guestfish-actions.pod:1036 +#: ../fish/guestfish-actions.pod:1040 ../fish/guestfish-actions.pod:1044 +#: ../fish/guestfish-actions.pod:1134 ../fish/guestfish-actions.pod:1138 +#: ../fish/guestfish-actions.pod:1143 ../fish/guestfish-actions.pod:1148 +#: ../fish/guestfish-actions.pod:1190 ../fish/guestfish-actions.pod:1194 +#: ../fish/guestfish-actions.pod:1199 ../tools/virt-resize.pl:324 +#: ../tools/virt-resize.pl:329 ../tools/virt-resize.pl:339 +msgid "*" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:347 +msgid "" +"The kernel version that the command runs under will be different from what " +"it expects." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:352 +msgid "" +"If the command needs to communicate with daemons, then most likely they " +"won't be running." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:357 +msgid "The command will be running in limited memory." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:361 +msgid "" +"The network may not be available unless you enable it (see L)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:366 +msgid "Only supports Linux guests (not Windows, BSD, etc)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:370 +msgid "" +"Architecture limitations (eg. won't work for a PPC guest on an X86 host)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:375 +msgid "" +"For SELinux guests, you may need to enable SELinux and load policy first. " +"See L in this manpage." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:380 +msgid "" +"The two main API calls to run commands are L and L (there are also variations)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:383 +msgid "" +"The difference is that L runs commands using the shell, so any " +"shell globs, redirections, etc will work." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:386 +msgid "CONFIGURATION FILES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:388 +msgid "" +"To read and write configuration files in Linux guest filesystems, we " +"strongly recommend using Augeas. For example, Augeas understands how to " +"read and write, say, a Linux shadow password file or X.org configuration " +"file, and so avoids you having to write that code." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:393 +msgid "" +"The main Augeas calls are bound through the C APIs. We don't " +"document Augeas itself here because there is excellent documentation on the " +"L website." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:397 +msgid "" +"If you don't want to use Augeas (you fool!) then try calling L to get the file as a list of lines which you can iterate " +"over." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:401 +msgid "SELINUX" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:403 +msgid "" +"We support SELinux guests. To ensure that labeling happens correctly in " +"SELinux guests, you need to enable SELinux and load the guest's policy:" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:409 +msgid "1." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:411 +msgid "Before launching, do:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:413 +#, no-wrap +msgid "" +" guestfs_set_selinux (g, 1);\n" +"\n" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:415 +msgid "2." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:417 +msgid "" +"After mounting the guest's filesystem(s), load the policy. This is best " +"done by running the L command in the guest itself:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:421 +#, no-wrap +msgid "" +" guestfs_sh (g, \"/usr/sbin/load_policy\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:423 +msgid "" +"(Older versions of C require you to specify the name of the " +"policy file)." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:426 +msgid "3." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:428 +msgid "" +"Optionally, set the security context for the API. The correct security " +"context to use can only be known by inspecting the guest. As an example:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:432 +#, no-wrap +msgid "" +" guestfs_setcon (g, \"unconfined_u:unconfined_r:unconfined_t:s0\");\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:436 +msgid "This will work for running commands and editing existing files." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:438 +msgid "" +"When new files are created, you may need to label them explicitly, for " +"example by running the external command C." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:442 +msgid "UMASK" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:444 +msgid "" +"Certain calls are affected by the current file mode creation mask (the " +"\"umask\"). In particular ones which create files or directories, such as " +"L, L or L. This affects " +"either the default mode that the file is created with or modifies the mode " +"that you supply." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:450 +msgid "" +"The default umask is C<022>, so files are created with modes such as C<0644> " +"and directories with C<0755>." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:453 +msgid "" +"There are two ways to avoid being affected by umask. Either set umask to 0 " +"(call C early after launching). Or call L after creating each file or directory." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:457 +msgid "For more information about umask, see L." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:459 ../fish/guestfish.pod:559 +msgid "ENCRYPTED DISKS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:461 +msgid "" +"Libguestfs allows you to access Linux guests which have been encrypted using " +"whole disk encryption that conforms to the Linux Unified Key Setup (LUKS) " +"standard. This includes nearly all whole disk encryption systems used by " +"modern Linux guests." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:467 +msgid "" +"Use L to identify LUKS-encrypted block devices (it " +"returns the string C)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:470 +msgid "" +"Then open these devices by calling L. Obviously you " +"will require the passphrase!" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:473 +msgid "" +"Opening a LUKS device creates a new device mapper device called C (where C is the string you supply to L). Reads and writes to this mapper device are decrypted " +"from and encrypted to the underlying block device respectively." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:479 +msgid "" +"LVM volume groups on the device can be made visible by calling L followed by L. The logical volume" +"(s) can now be mounted in the usual way." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:483 +msgid "" +"Use the reverse process to close a LUKS device. Unmount any logical volumes " +"on it, deactivate the volume groups by caling C. Then close the mapper device by calling L on the C device (I the " +"underlying encrypted block device)." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:490 +msgid "INSPECTION" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:492 +msgid "" +"Libguestfs has APIs for inspecting an unknown disk image to find out if it " +"contains operating systems. (These APIs used to be in a separate Perl-only " +"library called L but since version 1.5.3 the most " +"frequently used part of this library has been rewritten in C and moved into " +"the core code)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:498 +msgid "" +"Add all disks belonging to the unknown virtual machine and call L in the usual way." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:501 +msgid "" +"Then call L. This function uses other libguestfs calls " +"and certain heuristics, and returns a list of operating systems that were " +"found. An empty list means none were found. A single element is the root " +"filesystem of the operating system. For dual- or multi-boot guests, " +"multiple roots can be returned, each one corresponding to a separate " +"operating system. (Multi-boot virtual machines are extremely rare in the " +"world of virtualization, but since this scenario can happen, we have built " +"libguestfs to deal with it.)" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:510 +msgid "" +"For each root, you can then call various C functions " +"to get additional details about that operating system. For example, call L to return the string C or C for " +"Windows and Linux-based operating systems respectively." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:516 +msgid "" +"Un*x-like and Linux-based operating systems usually consist of several " +"filesystems which are mounted at boot time (for example, a separate boot " +"partition mounted on C). The inspection rules are able to detect how " +"filesystems correspond to mount points. Call " +"C to get this mapping. It might return a " +"hash table like this example:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:523 +#, no-wrap +msgid "" +" /boot => /dev/sda1\n" +" / => /dev/vg_guest/lv_root\n" +" /usr => /dev/vg_guest/lv_usr\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:527 +msgid "" +"The caller can then make calls to L to mount the " +"filesystems as suggested." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:530 +msgid "" +"Be careful to mount filesystems in the right order (eg. C before C). Sorting the keys of the hash by length, shortest first, should work." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:534 +msgid "" +"Inspection currently only works for some common operating systems. " +"Contributors are welcome to send patches for other operating systems that we " +"currently cannot detect." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:538 +msgid "" +"Encrypted disks must be opened before inspection. See L " +"for more details. The L function just ignores any " +"encrypted devices." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:542 +msgid "" +"A note on the implementation: The call L performs " +"inspection and caches the results in the guest handle. Subsequent calls to " +"C return this cached information, but I re-" +"read the disks. If you change the content of the guest disks, you can redo " +"inspection by calling L again." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:549 +msgid "SPECIAL CONSIDERATIONS FOR WINDOWS GUESTS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:551 +msgid "" +"Libguestfs can mount NTFS partitions. It does this using the L driver." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:554 +msgid "" +"DOS and Windows still use drive letters, and the filesystems are always " +"treated as case insensitive by Windows itself, and therefore you might find " +"a Windows configuration file referring to a path like C. When the filesystem is mounted in libguestfs, that directory " +"might be referred to as C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:560 +msgid "" +"Drive letter mappings are outside the scope of libguestfs. You have to use " +"libguestfs to read the appropriate Windows Registry and configuration files, " +"to determine yourself how drives are mapped (see also L and L)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:565 +msgid "" +"Replacing backslash characters with forward slash characters is also outside " +"the scope of libguestfs, but something that you can easily do." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:568 +msgid "" +"Where we can help is in resolving the case insensitivity of paths. For " +"this, call L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:571 +msgid "" +"Libguestfs also provides some help for decoding Windows Registry \"hive\" " +"files, through the library C which is part of the libguestfs project " +"although ships as a separate tarball. You have to locate and download the " +"hive file(s) yourself, and then pass them to C functions. See also " +"the programs L, L, L and L for more help on this issue." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:579 +msgid "USING LIBGUESTFS WITH OTHER PROGRAMMING LANGUAGES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:581 +msgid "" +"Although we don't want to discourage you from using the C API, we will " +"mention here that the same API is also available in other languages." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:584 +msgid "" +"The API is broadly identical in all supported languages. This means that " +"the C call C is C<$g-Emount($path)> in Perl, C in Python, and C in OCaml. In other " +"words, a straightforward, predictable isomorphism between each language." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:590 +msgid "" +"Error messages are automatically transformed into exceptions if the language " +"supports it." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:593 +msgid "" +"We don't try to \"object orientify\" parts of the API in OO languages, " +"although contributors are welcome to write higher level APIs above what we " +"provide in their favourite languages if they wish." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:599 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:601 +msgid "" +"You can use the I header file from C++ programs. The C++ API is " +"identical to the C API. C++ classes and exceptions are not used." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:605 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:607 +msgid "" +"The C# bindings are highly experimental. Please read the warnings at the " +"top of C." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:610 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:612 +msgid "" +"This is the only language binding that is working but incomplete. Only " +"calls which return simple integers have been bound in Haskell, and we are " +"looking for help to complete this binding." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:616 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:618 +msgid "" +"Full documentation is contained in the Javadoc which is distributed with " +"libguestfs." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:621 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:623 +msgid "For documentation see the file C." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:625 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:627 +msgid "For documentation see L." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:629 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:631 +msgid "For documentation do:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:633 +#, no-wrap +msgid "" +" $ python\n" +" >>> import guestfs\n" +" >>> help (guestfs)\n" +"\n" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:637 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:639 +msgid "" +"Use the Guestfs module. There is no Ruby-specific documentation, but you " +"can find examples written in Ruby in the libguestfs source." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:642 +msgid "B" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:644 +msgid "For documentation see L." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:648 +msgid "LIBGUESTFS GOTCHAS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:650 +msgid "" +"L: \"A feature of a " +"system [...] that works in the way it is documented but is counterintuitive " +"and almost invites mistakes.\"" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:654 +msgid "" +"Since we developed libguestfs and the associated tools, there are several " +"things we would have designed differently, but are now stuck with for " +"backwards compatibility or other reasons. If there is ever a libguestfs 2.0 " +"release, you can expect these to change. Beware of them." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:662 +msgid "Autosync / forgetting to sync." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:664 +msgid "" +"When modifying a filesystem from C or another language, you B unmount " +"all filesystems and call L explicitly before you close the " +"libguestfs handle. You can also call:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:668 +#, no-wrap +msgid "" +" guestfs_set_autosync (g, 1);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:670 +msgid "" +"to have the unmount/sync done automatically for you when the handle 'g' is " +"closed. (This feature is called \"autosync\", L q.v.)" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:674 +msgid "" +"If you forget to do this, then it is entirely possible that your changes " +"won't be written out, or will be partially written, or (very rarely) that " +"you'll get disk corruption." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:678 +msgid "" +"Note that in L autosync is the default. So quick and dirty " +"guestfish scripts that forget to sync will work just fine, which can make " +"this very puzzling if you are trying to debug a problem." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:682 +msgid "Mount option C<-o sync> should not be the default." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:684 +msgid "" +"If you use L, then C<-o sync,noatime> are added implicitly. " +"However C<-o sync> does not add any reliability benefit, but does have a " +"very large performance impact." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:688 +msgid "" +"The work around is to use L and set the mount " +"options that you actually want to use." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:691 +msgid "Read-only should be the default." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:693 +msgid "" +"In L, I<--ro> should be the default, and you should have to " +"specify I<--rw> if you want to make changes to the image." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:696 +msgid "This would reduce the potential to corrupt live VM images." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:698 +msgid "" +"Note that many filesystems change the disk when you just mount and unmount, " +"even if you didn't perform any writes. You need to use L to guarantee that the disk is not changed." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:702 +msgid "guestfish command line is hard to use." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:704 +msgid "" +"C doesn't do what people expect (open C for " +"examination). It tries to run a guestfish command C which doesn't " +"exist, so it fails. In earlier versions of guestfish the error message was " +"also unintuitive, but we have corrected this since. Like the Bourne shell, " +"we should have used C to run commands." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:711 +msgid "guestfish megabyte modifiers don't work right on all commands" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:713 +msgid "" +"In recent guestfish you can use C<1M> to mean 1 megabyte (and similarly for " +"other modifiers). What guestfish actually does is to multiply the number " +"part by the modifier part and pass the result to the C API. However this " +"doesn't work for a few APIs which aren't expecting bytes, but are already " +"expecting some other unit (eg. megabytes)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:720 +msgid "The most common is L. The guestfish command:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:722 +#, no-wrap +msgid "" +" lvcreate LV VG 100M\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:724 +msgid "" +"does not do what you might expect. Instead because L is " +"already expecting megabytes, this tries to create a 100 I (100 " +"megabytes * megabytes) logical volume. The error message you get from this " +"is also a little obscure." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:729 +msgid "" +"This could be fixed in the generator by specially marking parameters and " +"return values which take bytes or other units." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:732 +msgid "Library should return errno with error messages." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:734 +msgid "" +"It would be a nice-to-have to be able to get the original value of 'errno' " +"from inside the appliance along error paths (where set). Currently " +"L goes through hoops to try to reverse the error message " +"string into an errno, see the function error() in fuse/guestmount.c." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:740 +msgid "" +"In libguestfs 1.5.4, the protocol was changed so that the Linux errno is " +"sent back from the daemon." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:745 +msgid "PROTOCOL LIMITS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:747 +msgid "" +"Internally libguestfs uses a message-based protocol to pass API calls and " +"their responses to and from a small \"appliance\" (see L for " +"plenty more detail about this). The maximum message size used by the " +"protocol is slightly less than 4 MB. For some API calls you may need to be " +"aware of this limit. The API calls which may be affected are individually " +"documented, with a link back to this section of the documentation." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:755 +msgid "" +"A simple call such as L returns its result (the file data) in " +"a simple string. Because this string is at some point internally encoded as " +"a message, the maximum size that it can return is slightly under 4 MB. If " +"the requested file is larger than this then you will get an error." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:761 +msgid "" +"In order to transfer large files into and out of the guest filesystem, you " +"need to use particular calls that support this. The sections L " +"and L document how to do this." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:765 +msgid "" +"You might also consider mounting the disk image using our FUSE filesystem " +"support (L)." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:768 +msgid "KEYS AND PASSPHRASES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:770 +msgid "" +"Certain libguestfs calls take a parameter that contains sensitive key " +"material, passed in as a C string." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:773 +msgid "" +"In the future we would hope to change the libguestfs implementation so that " +"keys are L-ed into physical RAM, and thus can never end up in " +"swap. However this is I done at the moment, because of the complexity " +"of such an implementation." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:778 +msgid "" +"Therefore you should be aware that any key parameter you pass to libguestfs " +"might end up being written out to the swap partition. If this is a concern, " +"scrub the swap partition or don't use libguestfs on encrypted devices." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:783 +msgid "CONNECTION MANAGEMENT" +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:785 +msgid "guestfs_h *" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:787 +msgid "" +"C is the opaque type representing a connection handle. Create a " +"handle by calling L. Call L to free the " +"handle and release all resources used." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:791 +msgid "" +"For information on using multiple handles and threads, see the section L below." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:794 +msgid "guestfs_create" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:796 +#, no-wrap +msgid "" +" guestfs_h *guestfs_create (void);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:798 +msgid "Create a connection handle." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:800 +msgid "You have to call L on the handle at least once." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:802 +msgid "" +"This function returns a non-NULL pointer to a handle on success or NULL on " +"error." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:805 +msgid "After configuring the handle, you have to call L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:807 +msgid "" +"You may also want to configure error handling for the handle. See L section below." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:810 +msgid "guestfs_close" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:812 +#, no-wrap +msgid "" +" void guestfs_close (guestfs_h *g);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:814 +msgid "This closes the connection handle and frees up all resources used." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:816 +msgid "ERROR HANDLING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:818 +msgid "" +"The convention in all functions that return C is that they return C<-1> " +"to indicate an error. You can get additional information on errors by " +"calling L and/or by setting up an error handler with L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:823 +msgid "The default error handler prints the information string to C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:825 +msgid "" +"Out of memory errors are handled differently. The default action is to call " +"L. If this is undesirable, then you can set a handler using L." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:829 +msgid "guestfs_last_error" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:831 +#, no-wrap +msgid "" +" const char *guestfs_last_error (guestfs_h *g);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:833 +msgid "" +"This returns the last error message that happened on C. If there has not " +"been an error since the handle was created, then this returns C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:837 +msgid "" +"The lifetime of the returned string is until the next error occurs, or L is called." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:840 +msgid "" +"The error string is not localized (ie. is always in English), because this " +"makes searching for error messages in search engines give the largest number " +"of results." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:844 +msgid "guestfs_set_error_handler" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:846 +#, no-wrap +msgid "" +" typedef void (*guestfs_error_handler_cb) (guestfs_h *g,\n" +" void *opaque,\n" +" const char *msg);\n" +" void guestfs_set_error_handler (guestfs_h *g,\n" +" guestfs_error_handler_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:853 +msgid "" +"The callback C will be called if there is an error. The parameters " +"passed to the callback are an opaque data pointer and the error message " +"string." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:857 +msgid "" +"Note that the message string C is freed as soon as the callback " +"function returns, so if you want to stash it somewhere you must make your " +"own copy." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:861 +msgid "The default handler prints messages on C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:863 +msgid "If you set C to C then I handler is called." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:865 +msgid "guestfs_get_error_handler" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:867 +#, no-wrap +msgid "" +" guestfs_error_handler_cb guestfs_get_error_handler (guestfs_h *g,\n" +" void **opaque_rtn);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:870 +msgid "Returns the current error handler callback." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:872 +msgid "guestfs_set_out_of_memory_handler" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:874 +#, no-wrap +msgid "" +" typedef void (*guestfs_abort_cb) (void);\n" +" int guestfs_set_out_of_memory_handler (guestfs_h *g,\n" +" guestfs_abort_cb);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:878 +msgid "" +"The callback C will be called if there is an out of memory situation. " +"I." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:881 +msgid "The default is to call L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:883 +msgid "" +"You cannot set C to C. You can't ignore out of memory situations." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:886 +msgid "guestfs_get_out_of_memory_handler" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:888 +#, no-wrap +msgid "" +" guestfs_abort_fn guestfs_get_out_of_memory_handler (guestfs_h *g);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:890 +msgid "This returns the current out of memory handler." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:892 +msgid "PATH" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:894 +msgid "" +"Libguestfs needs a kernel and initrd.img, which it finds by looking along an " +"internal path." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:897 +msgid "" +"By default it looks for these in the directory C<$libdir/guestfs> (eg. C or C)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:900 +msgid "" +"Use L or set the environment variable L " +"to change the directories that libguestfs will search in. The value is a " +"colon-separated list of paths. The current directory is I searched " +"unless the path contains an empty element or C<.>. For example " +"C would search the current directory and " +"then C." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:907 +msgid "HIGH-LEVEL API ACTIONS" +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:909 +msgid "ABI GUARANTEE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:911 +msgid "" +"We guarantee the libguestfs ABI (binary interface), for public, high-level " +"actions as outlined in this section. Although we will deprecate some " +"actions, for example if they get replaced by newer calls, we will keep the " +"old actions forever. This allows you the developer to program in confidence " +"against the libguestfs API." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:917 ../fish/guestfish.pod:898 +msgid "@ACTIONS@" +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:919 +msgid "STRUCTURES" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:921 +msgid "@STRUCTS@" +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:923 +msgid "AVAILABILITY" +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:925 +msgid "GROUPS OF FUNCTIONALITY IN THE APPLIANCE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:927 +msgid "" +"Using L you can test availability of the following " +"groups of functions. This test queries the appliance to see if the " +"appliance you are currently using supports the functionality." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:932 +msgid "@AVAILABILITY@" +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:934 +msgid "GUESTFISH supported COMMAND" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:936 +msgid "" +"In L there is a handy interactive command C which " +"prints out the available groups and whether they are supported by this build " +"of libguestfs. Note however that you have to do C first." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:941 +msgid "SINGLE CALLS AT COMPILE TIME" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:943 +msgid "" +"If you need to test whether a single libguestfs function is available at " +"compile time, we recommend using build tools such as autoconf or cmake. For " +"example in autotools you could use:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:948 +#, no-wrap +msgid "" +" AC_CHECK_LIB([guestfs],[guestfs_create])\n" +" AC_CHECK_FUNCS([guestfs_dd])\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:951 +msgid "" +"which would result in C being either defined or not defined " +"in your program." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:954 +msgid "SINGLE CALLS AT RUN TIME" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:956 +msgid "" +"Testing at compile time doesn't guarantee that a function really exists in " +"the library. The reason is that you might be dynamically linked against a " +"previous I (dynamic library) which doesn't have the call. " +"This situation unfortunately results in a segmentation fault, which is a " +"shortcoming of the C dynamic linking system itself." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:963 +msgid "" +"You can use L to test if a function is available at run time, as " +"in this example program (note that you still need the compile time check as " +"well):" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:967 +#, no-wrap +msgid "" +" #include \n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:969 +#, no-wrap +msgid "" +" #include \n" +" #include \n" +" #include \n" +" #include \n" +" #include \n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:975 +#, no-wrap +msgid "" +" main ()\n" +" {\n" +" #ifdef HAVE_GUESTFS_DD\n" +" void *dl;\n" +" int has_function;\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:981 +#, no-wrap +msgid "" +" /* Test if the function guestfs_dd is really available. */\n" +" dl = dlopen (NULL, RTLD_LAZY);\n" +" if (!dl) {\n" +" fprintf (stderr, \"dlopen: %s\\n\", dlerror ());\n" +" exit (EXIT_FAILURE);\n" +" }\n" +" has_function = dlsym (dl, \"guestfs_dd\") != NULL;\n" +" dlclose (dl);\n" +" \n" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:990 +#, no-wrap +msgid "" +" if (!has_function)\n" +" printf (\"this libguestfs.so does NOT have guestfs_dd function\\n\");\n" +" else {\n" +" printf (\"this libguestfs.so has guestfs_dd function\\n\");\n" +" /* Now it's safe to call\n" +" guestfs_dd (g, \"foo\", \"bar\");\n" +" */\n" +" }\n" +" #else\n" +" printf (\"guestfs_dd function was not found at compile time\\n\");\n" +" #endif\n" +" }\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1003 +msgid "" +"You may think the above is an awful lot of hassle, and it is. There are " +"other ways outside of the C linking system to ensure that this kind of " +"incompatibility never arises, such as using package versioning:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1008 +#, no-wrap +msgid "" +" Requires: libguestfs >= 1.0.80\n" +"\n" +msgstr "" + +# type: =end +#: ../src/guestfs.pod:1010 ../src/guestfs.pod:1015 +msgid "html" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1012 +msgid "" +" " +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1017 +msgid "ARCHITECTURE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1019 +msgid "" +"Internally, libguestfs is implemented by running an appliance (a special " +"type of small virtual machine) using L. Qemu runs as a child " +"process of the main program." +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1023 +#, no-wrap +msgid "" +" ___________________\n" +" / \\\n" +" | main program |\n" +" | |\n" +" | | child process / appliance\n" +" | | __________________________\n" +" | | / qemu \\\n" +" +-------------------+ RPC | +-----------------+ |\n" +" | libguestfs <--------------------> guestfsd | |\n" +" | | | +-----------------+ |\n" +" \\___________________/ | | Linux kernel | |\n" +" | +--^--------------+ |\n" +" \\_________|________________/\n" +" |\n" +" _______v______\n" +" / \\\n" +" | Device or |\n" +" | disk image |\n" +" \\______________/\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1043 +msgid "" +"The library, linked to the main program, creates the child process and hence " +"the appliance in the L function." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1046 +msgid "" +"Inside the appliance is a Linux kernel and a complete stack of userspace " +"tools (such as LVM and ext2 programs) and a small controlling daemon called " +"L. The library talks to L using remote procedure " +"calls (RPC). There is a mostly one-to-one correspondence between libguestfs " +"API calls and RPC calls to the daemon. Lastly the disk image(s) are " +"attached to the qemu process which translates device access by the " +"appliance's Linux kernel into accesses to the image." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1055 +msgid "" +"A common misunderstanding is that the appliance \"is\" the virtual machine. " +"Although the disk image you are attached to might also be used by some " +"virtual machine, libguestfs doesn't know or care about this. (But you will " +"care if both libguestfs's qemu process and your virtual machine are trying " +"to update the disk image at the same time, since these usually results in " +"massive disk corruption)." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1062 +msgid "STATE MACHINE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1064 +msgid "libguestfs uses a state machine to model the child process:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1066 +#, no-wrap +msgid "" +" |\n" +" guestfs_create\n" +" |\n" +" |\n" +" ____V_____\n" +" / \\\n" +" | CONFIG |\n" +" \\__________/\n" +" ^ ^ ^ \\\n" +" / | \\ \\ guestfs_launch\n" +" / | _\\__V______\n" +" / | / \\\n" +" / | | LAUNCHING |\n" +" / | \\___________/\n" +" / | /\n" +" / | guestfs_launch\n" +" / | /\n" +" ______ / __|____V\n" +" / \\ ------> / \\\n" +" | BUSY | | READY |\n" +" \\______/ <------ \\________/\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1088 +msgid "" +"The normal transitions are (1) CONFIG (when the handle is created, but there " +"is no child process), (2) LAUNCHING (when the child process is booting up), " +"(3) alternating between READY and BUSY as commands are issued to, and " +"carried out by, the child process." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1093 +msgid "" +"The guest may be killed by L, or may die " +"asynchronously at any time (eg. due to some internal error), and that causes " +"the state to transition back to CONFIG." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1097 +msgid "" +"Configuration commands for qemu such as L can only be " +"issued when in the CONFIG state." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1100 +msgid "" +"The high-level API offers two calls that go from CONFIG through LAUNCHING to " +"READY. L blocks until the child process is READY to accept " +"commands (or until some failure or timeout). L internally " +"moves the state from CONFIG to LAUNCHING while it is running." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1106 +msgid "" +"High-level API actions such as L can only be issued when in " +"the READY state. These high-level API calls block waiting for the command " +"to be carried out (ie. the state to transition to BUSY and then back to " +"READY). But using the low-level event API, you get non-blocking versions. " +"(But you can still only carry out one operation per handle at a time - that " +"is a limitation of the communications protocol we use)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1114 +msgid "" +"Finally, the child process sends asynchronous messages back to the main " +"program, such as kernel log messages. Mostly these are ignored by the high-" +"level API, but using the low-level event API you can register to receive " +"these messages." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1119 +msgid "SETTING CALLBACKS TO HANDLE EVENTS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1121 +msgid "" +"The child process generates events in some situations. Current events " +"include: receiving a log message, the child process exits." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1124 +msgid "" +"Use the C functions to set a callback for different " +"types of events." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1127 +msgid "" +"Only I can be registered for each handle. " +"Calling C again overwrites the previous callback of " +"that type. Cancel all callbacks of this type by calling this function with " +"C set to C." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1132 +msgid "guestfs_set_log_message_callback" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1134 +#, no-wrap +msgid "" +" typedef void (*guestfs_log_message_cb) (guestfs_h *g, void *opaque,\n" +" char *buf, int len);\n" +" void guestfs_set_log_message_callback (guestfs_h *g,\n" +" guestfs_log_message_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1140 +msgid "" +"The callback function C will be called whenever qemu or the guest writes " +"anything to the console." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1143 +msgid "Use this function to capture kernel messages and similar." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1145 +msgid "" +"Normally there is no log message handler, and log messages are just " +"discarded." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1148 +msgid "guestfs_set_subprocess_quit_callback" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1150 +#, no-wrap +msgid "" +" typedef void (*guestfs_subprocess_quit_cb) (guestfs_h *g, void *opaque);\n" +" void guestfs_set_subprocess_quit_callback (guestfs_h *g,\n" +" guestfs_subprocess_quit_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1155 +msgid "" +"The callback function C will be called when the child process quits, " +"either asynchronously or if killed by L. (This " +"corresponds to a transition from any state to the CONFIG state)." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1160 +msgid "guestfs_set_launch_done_callback" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1162 +#, no-wrap +msgid "" +" typedef void (*guestfs_launch_done_cb) (guestfs_h *g, void *opaque);\n" +" void guestfs_set_launch_done_callback (guestfs_h *g,\n" +" guestfs_launch_done_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1167 +msgid "" +"The callback function C will be called when the child process becomes " +"ready first time after it has been launched. (This corresponds to a " +"transition from LAUNCHING to the READY state)." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1171 +msgid "guestfs_set_close_callback" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1173 +#, no-wrap +msgid "" +" typedef void (*guestfs_close_cb) (guestfs_h *g, void *opaque);\n" +" void guestfs_set_close_callback (guestfs_h *g,\n" +" guestfs_close_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1178 +msgid "" +"The callback function C will be called while the handle is being closed " +"(synchronously from L)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1181 +msgid "" +"Note that libguestfs installs an L handler to try to clean up " +"handles that are open when the program exits. This means that this callback " +"might be called indirectly from L, which can cause unexpected " +"problems in higher-level languages (eg. if your HLL interpreter has already " +"been cleaned up by the time this is called, and if your callback then jumps " +"into some HLL function)." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1189 +msgid "guestfs_set_progress_callback" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1191 +#, no-wrap +msgid "" +" typedef void (*guestfs_progress_cb) (guestfs_h *g, void *opaque,\n" +" int proc_nr, int serial,\n" +" uint64_t position, uint64_t total);\n" +" void guestfs_set_progress_callback (guestfs_h *g,\n" +" guestfs_progress_cb cb,\n" +" void *opaque);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1198 +msgid "" +"Some long-running operations can generate progress messages. If this " +"callback is registered, then it will be called each time a progress message " +"is generated (usually two seconds after the operation started, and three " +"times per second thereafter until it completes, although the frequency may " +"change in future versions)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1204 +msgid "" +"The callback receives two numbers: C and C. The units of " +"C are not defined, although for some operations C may relate " +"in some way to the amount of data to be transferred (eg. in bytes or " +"megabytes), and C may be the portion which has been transferred." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1210 +msgid "The only defined and stable parts of the API are:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1216 +msgid "" +"The callback can display to the user some type of progress bar or indicator " +"which shows the ratio of C:C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1221 +msgid "0 E= C E= C" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1225 +msgid "" +"If any progress notification is sent during a call, then a final progress " +"notification is always sent when C = C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1228 +msgid "" +"This is to simplify caller code, so callers can easily set the progress " +"indicator to \"100%\" at the end of the operation, without requiring special " +"code to detect this case." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1234 +msgid "" +"The callback also receives the procedure number and serial number of the " +"call. These are only useful for debugging protocol issues, and the callback " +"can normally ignore them. The callback may want to print these numbers in " +"error messages or debugging messages." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1239 +msgid "PRIVATE DATA AREA" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1241 +msgid "" +"You can attach named pieces of private data to the libguestfs handle, and " +"fetch them by name for the lifetime of the handle. This is called the " +"private data area and is only available from the C API." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1245 +msgid "To attach a named piece of data, use the following call:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1247 +#, no-wrap +msgid "" +" void guestfs_set_private (guestfs_h *g, const char *key, void *data);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1249 +msgid "" +"C is the name to associate with this data, and C is an arbitrary " +"pointer (which can be C). Any previous item with the same name is " +"overwritten." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1253 +msgid "" +"You can use any C you want, but names beginning with an underscore " +"character are reserved for internal libguestfs purposes (for implementing " +"language bindings). It is recommended to prefix the name with some unique " +"string to avoid collisions with other users." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1258 +msgid "To retrieve the pointer, use:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1260 +#, no-wrap +msgid "" +" void *guestfs_get_private (guestfs_h *g, const char *key);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1262 +msgid "" +"This function returns C if either no data is found associated with " +"C, or if the user previously set the C's C pointer to " +"C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1266 +msgid "" +"Libguestfs does not try to look at or interpret the C pointer in any " +"way. As far as libguestfs is concerned, it need not be a valid pointer at " +"all. In particular, libguestfs does I try to free the data when the " +"handle is closed. If the data must be freed, then the caller must either " +"free it before calling L or must set up a close callback to " +"do it (see L, and note that only one callback " +"can be registered for a handle)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1274 +msgid "" +"The private data area is implemented using a hash table, and should be " +"reasonably efficient for moderate numbers of keys." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1277 +msgid "BLOCK DEVICE NAMING" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1279 +msgid "" +"In the kernel there is now quite a profusion of schemata for naming block " +"devices (in this context, by I I mean a physical or virtual " +"hard drive). The original Linux IDE driver used names starting with C. SCSI devices have historically used a different naming scheme, C. When the Linux kernel I driver became a popular replacement " +"for the old IDE driver (particularly for SATA devices) those devices also " +"used the C scheme. Additionally we now have virtual machines with " +"paravirtualized drivers. This has created several different naming systems, " +"such as C for virtio disks and C for Xen PV disks." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1291 +msgid "" +"As discussed above, libguestfs uses a qemu appliance running an embedded " +"Linux kernel to access block devices. We can run a variety of appliances " +"based on a variety of Linux kernels." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1295 +msgid "" +"This causes a problem for libguestfs because many API calls use device or " +"partition names. Working scripts and the recipe (example) scripts that we " +"make available over the internet could fail if the naming scheme changes." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1300 +msgid "" +"Therefore libguestfs defines C as the I. " +"Internally C names are translated, if necessary, to other names as " +"required. For example, under RHEL 5 which uses the C scheme, any " +"device parameter C is translated to C transparently." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1306 +msgid "" +"Note that this I applies to parameters. The L, " +"L and similar calls return the true names of the " +"devices and partitions as known to the appliance." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1311 +msgid "ALGORITHM FOR BLOCK DEVICE NAME TRANSLATION" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1313 +msgid "" +"Usually this translation is transparent. However in some (very rare) cases " +"you may need to know the exact algorithm. Such cases include where you use " +"L to add a mixture of virtio and IDE devices to the qemu-" +"based appliance, so have a mixture of C and C devices." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1319 +msgid "" +"The algorithm is applied only to I which are known to be either " +"device or partition names. Return values from functions such as L are never changed." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1327 +msgid "Is the string a parameter which is a device or partition name?" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1331 +msgid "Does the string begin with C?" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1335 +msgid "" +"Does the named device exist? If so, we use that device. However if I " +"then we continue with this algorithm." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1340 +msgid "Replace initial C string with C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1342 +msgid "For example, change C to C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1344 +msgid "If that named device exists, use it. If not, continue." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1348 +msgid "Replace initial C string with C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1350 +msgid "If that named device exists, use it. If not, return an error." +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1354 +msgid "PORTABILITY CONCERNS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1356 +msgid "" +"Although the standard naming scheme and automatic translation is useful for " +"simple programs and guestfish scripts, for larger programs it is best not to " +"rely on this mechanism." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1360 +msgid "" +"Where possible for maximum future portability programs using libguestfs " +"should use these future-proof techniques:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1367 +msgid "" +"Use L or L to list actual " +"device names, and then use those names directly." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1370 +msgid "" +"Since those device names exist by definition, they will never be translated." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1375 +msgid "" +"Use higher level ways to identify filesystems, such as LVM names, UUIDs and " +"filesystem labels." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1380 +msgid "INTERNALS" +msgstr "" + +# type: =head2 +#: ../src/guestfs.pod:1382 +msgid "COMMUNICATION PROTOCOL" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1384 +msgid "" +"Don't rely on using this protocol directly. This section documents how it " +"currently works, but it may change at any time." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1387 +msgid "" +"The protocol used to talk between the library and the daemon running inside " +"the qemu virtual machine is a simple RPC mechanism built on top of XDR (RFC " +"1014, RFC 1832, RFC 4506)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1391 +msgid "" +"The detailed format of structures is in C (note: " +"this file is automatically generated)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1394 +msgid "" +"There are two broad cases, ordinary functions that don't have any C " +"and C parameters, which are handled with very simple request/reply " +"messages. Then there are functions that have any C or C " +"parameters, which use the same request and reply messages, but they may also " +"be followed by files sent using a chunked encoding." +msgstr "" + +# type: =head3 +#: ../src/guestfs.pod:1401 +msgid "ORDINARY FUNCTIONS (NO FILEIN/FILEOUT PARAMS)" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1403 +msgid "For ordinary functions, the request message is:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1405 +#, no-wrap +msgid "" +" total length (header + arguments,\n" +" but not including the length word itself)\n" +" struct guestfs_message_header (encoded as XDR)\n" +" struct guestfs__args (encoded as XDR)\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1410 +msgid "" +"The total length field allows the daemon to allocate a fixed size buffer " +"into which it slurps the rest of the message. As a result, the total length " +"is limited to C bytes (currently 4MB), which means the " +"effective size of any request is limited to somewhere under this size." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1416 +msgid "" +"Note also that many functions don't take any arguments, in which case the " +"C_args> is completely omitted." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1419 +msgid "" +"The header contains the procedure number (C) which is how the " +"receiver knows what type of args structure to expect, or none at all." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1423 +msgid "The reply message for ordinary functions is:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1425 +#, no-wrap +msgid "" +" total length (header + ret,\n" +" but not including the length word itself)\n" +" struct guestfs_message_header (encoded as XDR)\n" +" struct guestfs__ret (encoded as XDR)\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1430 +msgid "" +"As above the C_ret> structure may be completely omitted for " +"functions that return no formal return values." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1433 +msgid "" +"As above the total length of the reply is limited to C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1436 +msgid "" +"In the case of an error, a flag is set in the header, and the reply message " +"is slightly changed:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1439 +#, no-wrap +msgid "" +" total length (header + error,\n" +" but not including the length word itself)\n" +" struct guestfs_message_header (encoded as XDR)\n" +" struct guestfs_message_error (encoded as XDR)\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1444 +msgid "" +"The C structure contains the error message as a " +"string." +msgstr "" + +# type: =head3 +#: ../src/guestfs.pod:1447 +msgid "FUNCTIONS THAT HAVE FILEIN PARAMETERS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1449 +msgid "" +"A C parameter indicates that we transfer a file I the guest. " +"The normal request message is sent (see above). However this is followed by " +"a sequence of file chunks." +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1453 +#, no-wrap +msgid "" +" total length (header + arguments,\n" +" but not including the length word itself,\n" +" and not including the chunks)\n" +" struct guestfs_message_header (encoded as XDR)\n" +" struct guestfs__args (encoded as XDR)\n" +" sequence of chunks for FileIn param #0\n" +" sequence of chunks for FileIn param #1 etc.\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1461 +msgid "The \"sequence of chunks\" is:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1463 +#, no-wrap +msgid "" +" length of chunk (not including length word itself)\n" +" struct guestfs_chunk (encoded as XDR)\n" +" length of chunk\n" +" struct guestfs_chunk (encoded as XDR)\n" +" ...\n" +" length of chunk\n" +" struct guestfs_chunk (with data.data_len == 0)\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1471 +msgid "" +"The final chunk has the C field set to zero. Additionally a flag " +"is set in the final chunk to indicate either successful completion or early " +"cancellation." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1475 +msgid "" +"At time of writing there are no functions that have more than one FileIn " +"parameter. However this is (theoretically) supported, by sending the " +"sequence of chunks for each FileIn parameter one after another (from left to " +"right)." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1480 +msgid "" +"Both the library (sender) I the daemon (receiver) may cancel the " +"transfer. The library does this by sending a chunk with a special flag set " +"to indicate cancellation. When the daemon sees this, it cancels the whole " +"RPC, does I send any reply, and goes back to reading the next request." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1486 +msgid "" +"The daemon may also cancel. It does this by writing a special word " +"C to the socket. The library listens for this during " +"the transfer, and if it gets it, it will cancel the transfer (it sends a " +"cancel chunk). The special word is chosen so that even if cancellation " +"happens right at the end of the transfer (after the library has finished " +"writing and has started listening for the reply), the \"spurious\" cancel " +"flag will not be confused with the reply message." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1495 +msgid "" +"This protocol allows the transfer of arbitrary sized files (no 32 bit " +"limit), and also files where the size is not known in advance (eg. from " +"pipes or sockets). However the chunks are rather small " +"(C), so that neither the library nor the daemon need " +"to keep much in memory." +msgstr "" + +# type: =head3 +#: ../src/guestfs.pod:1501 +msgid "FUNCTIONS THAT HAVE FILEOUT PARAMETERS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1503 +msgid "" +"The protocol for FileOut parameters is exactly the same as for FileIn " +"parameters, but with the roles of daemon and library reversed." +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1506 +#, no-wrap +msgid "" +" total length (header + ret,\n" +" but not including the length word itself,\n" +" and not including the chunks)\n" +" struct guestfs_message_header (encoded as XDR)\n" +" struct guestfs__ret (encoded as XDR)\n" +" sequence of chunks for FileOut param #0\n" +" sequence of chunks for FileOut param #1 etc.\n" +"\n" +msgstr "" + +# type: =head3 +#: ../src/guestfs.pod:1514 +msgid "INITIAL MESSAGE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1516 +msgid "" +"Because the underlying channel (QEmu -net channel) doesn't have any sort of " +"connection control, when the daemon launches it sends an initial word " +"(C) which indicates that the guest and daemon is " +"alive. This is what L waits for." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1521 +msgid "MULTIPLE HANDLES AND MULTIPLE THREADS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1523 +msgid "" +"All high-level libguestfs actions are synchronous. If you want to use " +"libguestfs asynchronously then you must create a thread." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1526 +msgid "" +"Only use the handle from a single thread. Either use the handle exclusively " +"from one thread, or provide your own mutex so that two threads cannot issue " +"calls on the same handle at the same time." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1530 +msgid "QEMU WRAPPERS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1532 +msgid "" +"If you want to compile your own qemu, run qemu from a non-standard location, " +"or pass extra arguments to qemu, then you can write a shell-script wrapper " +"around qemu." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1536 +msgid "" +"There is one important rule to remember: you I> as the " +"last command in the shell script (so that qemu replaces the shell and " +"becomes the direct child of the libguestfs-using program). If you don't do " +"this, then the qemu process won't be cleaned up correctly." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1541 +msgid "" +"Here is an example of a wrapper, where I have built my own copy of qemu from " +"source:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1544 +#, no-wrap +msgid "" +" #!/bin/sh -\n" +" qemudir=/home/rjones/d/qemu\n" +" exec $qemudir/x86_64-softmmu/qemu-system-x86_64 -L $qemudir/pc-bios \"$@\"\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1548 +msgid "" +"Save this script as C (or wherever), C, and " +"then use it by setting the LIBGUESTFS_QEMU environment variable. For " +"example:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1552 +#, no-wrap +msgid "" +" LIBGUESTFS_QEMU=/tmp/qemu.wrapper guestfish\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1554 +msgid "" +"Note that libguestfs also calls qemu with the -help and -version options in " +"order to determine features." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1557 +msgid "LIBGUESTFS VERSION NUMBERS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1559 +msgid "" +"Since April 2010, libguestfs has started to make separate development and " +"stable releases, along with corresponding branches in our git repository. " +"These separate releases can be identified by version number:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1564 +#, no-wrap +msgid "" +" even numbers for stable: 1.2.x, 1.4.x, ...\n" +" .-------- odd numbers for development: 1.3.x, 1.5.x, ...\n" +" |\n" +" v\n" +" 1 . 3 . 5\n" +" ^ ^\n" +" | |\n" +" | `-------- sub-version\n" +" |\n" +" `------ always '1' because we don't change the ABI\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1575 +msgid "Thus \"1.3.5\" is the 5th update to the development branch \"1.3\"." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1577 +msgid "" +"As time passes we cherry pick fixes from the development branch and backport " +"those into the stable branch, the effect being that the stable branch should " +"get more stable and less buggy over time. So the stable releases are ideal " +"for people who don't need new features but would just like the software to " +"work." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1583 +msgid "Our criteria for backporting changes are:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1589 +msgid "" +"Documentation changes which don't affect any code are backported unless the " +"documentation refers to a future feature which is not in stable." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1595 +msgid "" +"Bug fixes which are not controversial, fix obvious problems, and have been " +"well tested are backported." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1600 +msgid "" +"Simple rearrangements of code which shouldn't affect how it works get " +"backported. This is so that the code in the two branches doesn't get too " +"far out of step, allowing us to backport future fixes more easily." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1606 +msgid "" +"We I backport new features, new APIs, new tools etc, except in one " +"exceptional case: the new feature is required in order to implement an " +"important bug fix." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1612 +msgid "" +"A new stable branch starts when we think the new features in development are " +"substantial and compelling enough over the current stable branch to warrant " +"it. When that happens we create new stable and development versions 1.N.0 " +"and 1.(N+1).0 [N is even]. The new dot-oh release won't necessarily be so " +"stable at this point, but by backporting fixes from development, that branch " +"will stabilize over time." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1620 ../fish/guestfish.pod:905 +#: ../test-tool/libguestfs-test-tool.pod:104 ../tools/virt-edit.pl:312 +#: ../tools/virt-rescue.pl:226 +msgid "ENVIRONMENT VARIABLES" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1624 ../fish/guestfish.pod:925 +msgid "LIBGUESTFS_APPEND" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1626 ../fish/guestfish.pod:927 +msgid "Pass additional options to the guest kernel." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1628 ../fish/guestfish.pod:929 +msgid "LIBGUESTFS_DEBUG" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1630 +msgid "" +"Set C to enable verbose messages. This has the same " +"effect as calling C." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1633 ../fish/guestfish.pod:934 +msgid "LIBGUESTFS_MEMSIZE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1635 ../fish/guestfish.pod:936 +msgid "" +"Set the memory allocated to the qemu process, in megabytes. For example:" +msgstr "" + +# type: verbatim +#: ../src/guestfs.pod:1638 ../fish/guestfish.pod:939 +#, no-wrap +msgid "" +" LIBGUESTFS_MEMSIZE=700\n" +"\n" +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1640 ../fish/guestfish.pod:941 +msgid "LIBGUESTFS_PATH" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1642 +msgid "" +"Set the path that libguestfs uses to search for kernel and initrd.img. See " +"the discussion of paths in section PATH above." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1645 ../fish/guestfish.pod:946 +msgid "LIBGUESTFS_QEMU" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1647 ../fish/guestfish.pod:948 +msgid "" +"Set the default qemu binary that libguestfs uses. If not set, then the qemu " +"which was found at compile time by the configure script is used." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1651 +msgid "See also L above." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1653 ../fish/guestfish.pod:952 +msgid "LIBGUESTFS_TRACE" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1655 +msgid "" +"Set C to enable command traces. This has the same " +"effect as calling C." +msgstr "" + +# type: =item +#: ../src/guestfs.pod:1658 ../fish/guestfish.pod:961 +msgid "TMPDIR" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1660 ../fish/guestfish.pod:963 +msgid "Location of temporary directory, defaults to C." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1662 ../fish/guestfish.pod:965 +msgid "" +"If libguestfs was compiled to use the supermin appliance then each handle " +"will require rather a large amount of space in this directory for short " +"periods of time (~ 80 MB). You can use C<$TMPDIR> to configure another " +"directory to use in case C is not large enough." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1670 ../fish/guestfish.pod:1023 +#: ../test-tool/libguestfs-test-tool.pod:109 ../fuse/guestmount.pod:178 +#: ../inspector/virt-inspector.pl:846 ../tools/virt-cat.pl:163 +#: ../tools/virt-df.pl:482 ../tools/virt-edit.pl:325 +#: ../tools/virt-list-filesystems.pl:191 ../tools/virt-list-partitions.pl:229 +#: ../tools/virt-ls.pl:210 ../tools/virt-make-fs.pl:527 +#: ../tools/virt-rescue.pl:231 ../tools/virt-resize.pl:1390 +#: ../tools/virt-tar.pl:257 ../tools/virt-win-reg.pl:461 +msgid "SEE ALSO" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1672 +msgid "" +"L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, " +"L." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1690 +msgid "" +"Tools with a similar purpose: L, L, L, L, L." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1697 ../tools/virt-make-fs.pl:541 +#: ../tools/virt-win-reg.pl:476 +msgid "BUGS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1699 +msgid "To get a list of bugs against libguestfs use this link:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1701 +msgid "" +"L" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1703 +msgid "To report a new bug against libguestfs use this link:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1705 +msgid "" +"L" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1707 +msgid "When reporting a bug, please check:" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1713 +msgid "That the bug hasn't been reported already." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1717 +msgid "That you are testing a recent version." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1721 +msgid "Describe the bug accurately, and give a way to reproduce it." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1725 +msgid "" +"Run libguestfs-test-tool and paste the B output into the " +"bug report." +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1730 ../fish/guestfish.pod:1039 +#: ../test-tool/libguestfs-test-tool.pod:115 ../fuse/guestmount.pod:189 +#: ../inspector/virt-inspector.pl:855 +msgid "AUTHORS" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1732 ../fish/guestfish.pod:1041 +#: ../test-tool/libguestfs-test-tool.pod:117 ../fuse/guestmount.pod:191 +msgid "Richard W.M. Jones (C)" +msgstr "" + +# type: =head1 +#: ../src/guestfs.pod:1734 ../fish/guestfish.pod:1043 +#: ../test-tool/libguestfs-test-tool.pod:119 ../fuse/guestmount.pod:193 +#: ../inspector/virt-inspector.pl:861 ../tools/virt-cat.pl:177 +#: ../tools/virt-df.pl:495 ../tools/virt-edit.pl:341 +#: ../tools/virt-list-filesystems.pl:207 ../tools/virt-list-partitions.pl:244 +#: ../tools/virt-ls.pl:225 ../tools/virt-make-fs.pl:556 +#: ../tools/virt-rescue.pl:245 ../tools/virt-resize.pl:1411 +#: ../tools/virt-tar.pl:272 ../tools/virt-win-reg.pl:491 +msgid "COPYRIGHT" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1736 ../fish/guestfish.pod:1045 +msgid "Copyright (C) 2009-2010 Red Hat Inc. L" +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1739 +msgid "" +"This library is free software; you can redistribute it and/or modify it " +"under the terms of the GNU Lesser General Public License as published by the " +"Free Software Foundation; either version 2 of the License, or (at your " +"option) any later version." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1744 +msgid "" +"This library is distributed in the hope that it will be useful, but WITHOUT " +"ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or " +"FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License " +"for more details." +msgstr "" + +# type: textblock +#: ../src/guestfs.pod:1749 +msgid "" +"You should have received a copy of the GNU Lesser General Public License " +"along with this library; if not, write to the Free Software Foundation, " +"Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA" +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:1 +msgid "guestfs_add_cdrom" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:3 +#, no-wrap +msgid "" +" int guestfs_add_cdrom (guestfs_h *g,\n" +"\t\tconst char *filename);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:6 ../fish/guestfish-actions.pod:5 +msgid "This function adds a virtual CD-ROM disk image to the guest." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:8 ../fish/guestfish-actions.pod:7 +msgid "This is equivalent to the qemu parameter C<-cdrom filename>." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:10 ../src/guestfs-actions.pod:1488 +#: ../fish/guestfish-actions.pod:9 ../fish/guestfish-actions.pod:1186 +msgid "Notes:" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:16 +msgid "" +"This call checks for the existence of C. This stops you from " +"specifying other types of drive which are supported by qemu such as C " +"and C URLs. To specify those, use the general C call " +"instead." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:23 +msgid "" +"If you just want to add an ISO file (often you use this as an efficient way " +"to transfer large files into the guest), then you should probably use " +"C instead." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:29 ../src/guestfs-actions.pod:63 +#: ../src/guestfs-actions.pod:92 ../src/guestfs-actions.pod:103 +#: ../src/guestfs-actions.pod:114 ../src/guestfs-actions.pod:124 +#: ../src/guestfs-actions.pod:135 ../src/guestfs-actions.pod:238 +#: ../src/guestfs-actions.pod:255 ../src/guestfs-actions.pod:266 +#: ../src/guestfs-actions.pod:302 ../src/guestfs-actions.pod:324 +#: ../src/guestfs-actions.pod:339 ../src/guestfs-actions.pod:403 +#: ../src/guestfs-actions.pod:430 ../src/guestfs-actions.pod:441 +#: ../src/guestfs-actions.pod:453 ../src/guestfs-actions.pod:534 +#: ../src/guestfs-actions.pod:549 ../src/guestfs-actions.pod:560 +#: ../src/guestfs-actions.pod:571 ../src/guestfs-actions.pod:717 +#: ../src/guestfs-actions.pod:734 ../src/guestfs-actions.pod:749 +#: ../src/guestfs-actions.pod:824 ../src/guestfs-actions.pod:839 +#: ../src/guestfs-actions.pod:855 ../src/guestfs-actions.pod:866 +#: ../src/guestfs-actions.pod:883 ../src/guestfs-actions.pod:916 +#: ../src/guestfs-actions.pod:974 ../src/guestfs-actions.pod:996 +#: ../src/guestfs-actions.pod:1027 ../src/guestfs-actions.pod:1115 +#: ../src/guestfs-actions.pod:1146 ../src/guestfs-actions.pod:1346 +#: ../src/guestfs-actions.pod:1365 ../src/guestfs-actions.pod:1446 +#: ../src/guestfs-actions.pod:1794 ../src/guestfs-actions.pod:1917 +#: ../src/guestfs-actions.pod:1972 ../src/guestfs-actions.pod:2002 +#: ../src/guestfs-actions.pod:2349 ../src/guestfs-actions.pod:2361 +#: ../src/guestfs-actions.pod:2378 ../src/guestfs-actions.pod:2443 +#: ../src/guestfs-actions.pod:2454 ../src/guestfs-actions.pod:2464 +#: ../src/guestfs-actions.pod:2475 ../src/guestfs-actions.pod:2487 +#: ../src/guestfs-actions.pod:2517 ../src/guestfs-actions.pod:2581 +#: ../src/guestfs-actions.pod:2598 ../src/guestfs-actions.pod:2612 +#: ../src/guestfs-actions.pod:2632 ../src/guestfs-actions.pod:2652 +#: ../src/guestfs-actions.pod:2681 ../src/guestfs-actions.pod:2697 +#: ../src/guestfs-actions.pod:2713 ../src/guestfs-actions.pod:2725 +#: ../src/guestfs-actions.pod:2734 ../src/guestfs-actions.pod:2767 +#: ../src/guestfs-actions.pod:2780 ../src/guestfs-actions.pod:2790 +#: ../src/guestfs-actions.pod:2802 ../src/guestfs-actions.pod:2816 +#: ../src/guestfs-actions.pod:2896 ../src/guestfs-actions.pod:2913 +#: ../src/guestfs-actions.pod:2923 ../src/guestfs-actions.pod:2968 +#: ../src/guestfs-actions.pod:2983 ../src/guestfs-actions.pod:2998 +#: ../src/guestfs-actions.pod:3011 ../src/guestfs-actions.pod:3022 +#: ../src/guestfs-actions.pod:3033 ../src/guestfs-actions.pod:3047 +#: ../src/guestfs-actions.pod:3059 ../src/guestfs-actions.pod:3076 +#: ../src/guestfs-actions.pod:3107 ../src/guestfs-actions.pod:3135 +#: ../src/guestfs-actions.pod:3151 ../src/guestfs-actions.pod:3167 +#: ../src/guestfs-actions.pod:3176 ../src/guestfs-actions.pod:3190 +#: ../src/guestfs-actions.pod:3200 ../src/guestfs-actions.pod:3212 +#: ../src/guestfs-actions.pod:3224 ../src/guestfs-actions.pod:3256 +#: ../src/guestfs-actions.pod:3268 ../src/guestfs-actions.pod:3285 +#: ../src/guestfs-actions.pod:3296 ../src/guestfs-actions.pod:3310 +#: ../src/guestfs-actions.pod:3350 ../src/guestfs-actions.pod:3381 +#: ../src/guestfs-actions.pod:3392 ../src/guestfs-actions.pod:3417 +#: ../src/guestfs-actions.pod:3431 ../src/guestfs-actions.pod:3446 +#: ../src/guestfs-actions.pod:3568 ../src/guestfs-actions.pod:3620 +#: ../src/guestfs-actions.pod:3639 ../src/guestfs-actions.pod:3654 +#: ../src/guestfs-actions.pod:3665 ../src/guestfs-actions.pod:3699 +#: ../src/guestfs-actions.pod:3713 ../src/guestfs-actions.pod:3723 +#: ../src/guestfs-actions.pod:3734 ../src/guestfs-actions.pod:3966 +#: ../src/guestfs-actions.pod:3982 ../src/guestfs-actions.pod:3993 +#: ../src/guestfs-actions.pod:4002 ../src/guestfs-actions.pod:4013 +#: ../src/guestfs-actions.pod:4022 ../src/guestfs-actions.pod:4033 +#: ../src/guestfs-actions.pod:4046 ../src/guestfs-actions.pod:4064 +#: ../src/guestfs-actions.pod:4080 ../src/guestfs-actions.pod:4096 +#: ../src/guestfs-actions.pod:4111 ../src/guestfs-actions.pod:4131 +#: ../src/guestfs-actions.pod:4146 ../src/guestfs-actions.pod:4162 +#: ../src/guestfs-actions.pod:4180 ../src/guestfs-actions.pod:4196 +#: ../src/guestfs-actions.pod:4210 ../src/guestfs-actions.pod:4235 +#: ../src/guestfs-actions.pod:4256 ../src/guestfs-actions.pod:4272 +#: ../src/guestfs-actions.pod:4293 ../src/guestfs-actions.pod:4305 +#: ../src/guestfs-actions.pod:4317 ../src/guestfs-actions.pod:4333 +#: ../src/guestfs-actions.pod:4367 ../src/guestfs-actions.pod:4387 +#: ../src/guestfs-actions.pod:4410 ../src/guestfs-actions.pod:4500 +#: ../src/guestfs-actions.pod:4606 ../src/guestfs-actions.pod:4615 +#: ../src/guestfs-actions.pod:4625 ../src/guestfs-actions.pod:4635 +#: ../src/guestfs-actions.pod:4654 ../src/guestfs-actions.pod:4664 +#: ../src/guestfs-actions.pod:4674 ../src/guestfs-actions.pod:4684 +#: ../src/guestfs-actions.pod:4696 ../src/guestfs-actions.pod:4746 +#: ../src/guestfs-actions.pod:4760 ../src/guestfs-actions.pod:4773 +#: ../src/guestfs-actions.pod:4786 ../src/guestfs-actions.pod:4800 +#: ../src/guestfs-actions.pod:4810 ../src/guestfs-actions.pod:4827 +#: ../src/guestfs-actions.pod:4857 ../src/guestfs-actions.pod:4868 +#: ../src/guestfs-actions.pod:4903 ../src/guestfs-actions.pod:4913 +#: ../src/guestfs-actions.pod:4928 ../src/guestfs-actions.pod:4956 +#: ../src/guestfs-actions.pod:5060 ../src/guestfs-actions.pod:5075 +#: ../src/guestfs-actions.pod:5086 ../src/guestfs-actions.pod:5132 +#: ../src/guestfs-actions.pod:5142 ../src/guestfs-actions.pod:5179 +#: ../src/guestfs-actions.pod:5206 ../src/guestfs-actions.pod:5248 +#: ../src/guestfs-actions.pod:5271 ../src/guestfs-actions.pod:5328 +#: ../src/guestfs-actions.pod:5344 ../src/guestfs-actions.pod:5370 +msgid "This function returns 0 on success or -1 on error." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:31 +msgid "guestfs_add_drive" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:33 +#, no-wrap +msgid "" +" int guestfs_add_drive (guestfs_h *g,\n" +"\t\tconst char *filename);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:36 ../fish/guestfish-actions.pod:32 +msgid "" +"This function adds a virtual machine disk image C to the guest. " +"The first time you call this function, the disk appears as IDE disk 0 (C) in the guest, the second time as C, and so on." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:41 ../fish/guestfish-actions.pod:37 +msgid "" +"You don't necessarily need to be root when using libguestfs. However you " +"obviously do need sufficient permissions to access the filename for whatever " +"operations you want to perform (ie. read access if you just want to read the " +"image or write access if you want to modify the image)." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:47 ../fish/guestfish-actions.pod:43 +msgid "" +"This is equivalent to the qemu parameter C<-drive file=filename,cache=off," +"if=...>." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:50 ../fish/guestfish-actions.pod:46 +msgid "" +"C is omitted in cases where it is not supported by the underlying " +"filesystem." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:53 ../src/guestfs-actions.pod:82 +msgid "" +"C is set at compile time by the configuration option C<./configure --" +"with-drive-if=...>. In the rare case where you might need to change this at " +"run time, use C or " +"C." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:58 ../src/guestfs-actions.pod:87 +msgid "" +"Note that this call checks for the existence of C. This stops you " +"from specifying other types of drive which are supported by qemu such as " +"C and C URLs. To specify those, use the general " +"C call instead." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:65 +msgid "guestfs_add_drive_ro" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:67 +#, no-wrap +msgid "" +" int guestfs_add_drive_ro (guestfs_h *g,\n" +"\t\tconst char *filename);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:70 ../fish/guestfish-actions.pod:63 +msgid "This adds a drive in snapshot mode, making it effectively read-only." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:73 ../fish/guestfish-actions.pod:66 +msgid "" +"Note that writes to the device are allowed, and will be seen for the " +"duration of the guestfs handle, but they are written to a temporary file " +"which is discarded as soon as the guestfs handle is closed. We don't " +"currently have any method to enable changes to be committed, although qemu " +"can support this." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:79 ../fish/guestfish-actions.pod:72 +msgid "" +"This is equivalent to the qemu parameter C<-drive file=filename,snapshot=on," +"if=...>." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:94 +msgid "guestfs_add_drive_ro_with_if" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:96 +#, no-wrap +msgid "" +" int guestfs_add_drive_ro_with_if (guestfs_h *g,\n" +"\t\tconst char *filename,\n" +"\t\tconst char *iface);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:100 +msgid "" +"This is the same as C but it allows you to specify the " +"QEMU interface emulation to use at run time." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:105 +msgid "guestfs_add_drive_with_if" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:107 +#, no-wrap +msgid "" +" int guestfs_add_drive_with_if (guestfs_h *g,\n" +"\t\tconst char *filename,\n" +"\t\tconst char *iface);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:111 +msgid "" +"This is the same as C but it allows you to specify the " +"QEMU interface emulation to use at run time." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:116 +msgid "guestfs_aug_clear" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:118 +#, no-wrap +msgid "" +" int guestfs_aug_clear (guestfs_h *g,\n" +"\t\tconst char *augpath);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:121 ../fish/guestfish-actions.pod:103 +msgid "" +"Set the value associated with C to C. This is the same as the " +"L C command." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:126 +msgid "guestfs_aug_close" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:128 +#, no-wrap +msgid "" +" int guestfs_aug_close (guestfs_h *g);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:130 +msgid "" +"Close the current Augeas handle and free up any resources used by it. After " +"calling this, you have to call C again before you can use " +"any other Augeas functions." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:137 +msgid "guestfs_aug_defnode" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:139 +#, no-wrap +msgid "" +" struct guestfs_int_bool *guestfs_aug_defnode (guestfs_h *g,\n" +"\t\tconst char *name,\n" +"\t\tconst char *expr,\n" +"\t\tconst char *val);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:144 ../fish/guestfish-actions.pod:119 +msgid "" +"Defines a variable C whose value is the result of evaluating C." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:147 +msgid "" +"If C evaluates to an empty nodeset, a node is created, equivalent to " +"calling C C, C. C will be the nodeset " +"containing that single node." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:151 ../fish/guestfish-actions.pod:126 +msgid "" +"On success this returns a pair containing the number of nodes in the " +"nodeset, and a boolean flag if a node was created." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:155 +msgid "" +"This function returns a C, or NULL if there was " +"an error. I after use>." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:159 +msgid "guestfs_aug_defvar" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:161 +#, no-wrap +msgid "" +" int guestfs_aug_defvar (guestfs_h *g,\n" +"\t\tconst char *name,\n" +"\t\tconst char *expr);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:165 ../fish/guestfish-actions.pod:134 +msgid "" +"Defines an Augeas variable C whose value is the result of evaluating " +"C. If C is NULL, then C is undefined." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:169 ../fish/guestfish-actions.pod:138 +msgid "" +"On success this returns the number of nodes in C, or C<0> if C " +"evaluates to something which is not a nodeset." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:172 ../src/guestfs-actions.pod:313 +#: ../src/guestfs-actions.pod:467 ../src/guestfs-actions.pod:492 +#: ../src/guestfs-actions.pod:507 ../src/guestfs-actions.pod:523 +#: ../src/guestfs-actions.pod:1013 ../src/guestfs-actions.pod:1328 +#: ../src/guestfs-actions.pod:1510 ../src/guestfs-actions.pod:1591 +#: ../src/guestfs-actions.pod:1622 ../src/guestfs-actions.pod:1665 +#: ../src/guestfs-actions.pod:1682 ../src/guestfs-actions.pod:1907 +#: ../src/guestfs-actions.pod:2119 ../src/guestfs-actions.pod:2137 +#: ../src/guestfs-actions.pod:3370 ../src/guestfs-actions.pod:3477 +#: ../src/guestfs-actions.pod:3793 ../src/guestfs-actions.pod:4892 +#: ../src/guestfs-actions.pod:5216 ../src/guestfs-actions.pod:5226 +#: ../src/guestfs-actions.pod:5236 +msgid "On error this function returns -1." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:174 +msgid "guestfs_aug_get" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:176 +#, no-wrap +msgid "" +" char *guestfs_aug_get (guestfs_h *g,\n" +"\t\tconst char *augpath);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:179 ../fish/guestfish-actions.pod:145 +msgid "" +"Look up the value associated with C. If C matches exactly one " +"node, the C is returned." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:182 ../src/guestfs-actions.pod:610 +#: ../src/guestfs-actions.pod:625 ../src/guestfs-actions.pod:682 +#: ../src/guestfs-actions.pod:695 ../src/guestfs-actions.pod:786 +#: ../src/guestfs-actions.pod:899 ../src/guestfs-actions.pod:928 +#: ../src/guestfs-actions.pod:942 ../src/guestfs-actions.pod:958 +#: ../src/guestfs-actions.pod:1041 ../src/guestfs-actions.pod:1205 +#: ../src/guestfs-actions.pod:1314 ../src/guestfs-actions.pod:1459 +#: ../src/guestfs-actions.pod:1473 ../src/guestfs-actions.pod:1549 +#: ../src/guestfs-actions.pod:1567 ../src/guestfs-actions.pod:1701 +#: ../src/guestfs-actions.pod:1840 ../src/guestfs-actions.pod:2021 +#: ../src/guestfs-actions.pod:2071 ../src/guestfs-actions.pod:2187 +#: ../src/guestfs-actions.pod:2222 ../src/guestfs-actions.pod:2432 +#: ../src/guestfs-actions.pod:2853 ../src/guestfs-actions.pod:2949 +#: ../src/guestfs-actions.pod:3492 ../src/guestfs-actions.pod:3771 +#: ../src/guestfs-actions.pod:3909 ../src/guestfs-actions.pod:3952 +#: ../src/guestfs-actions.pod:4428 ../src/guestfs-actions.pod:4441 +#: ../src/guestfs-actions.pod:4455 ../src/guestfs-actions.pod:4476 +#: ../src/guestfs-actions.pod:5009 ../src/guestfs-actions.pod:5025 +#: ../src/guestfs-actions.pod:5040 ../src/guestfs-actions.pod:5188 +#: ../src/guestfs-actions.pod:5418 +msgid "" +"This function returns a string, or NULL on error. I." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:185 +msgid "guestfs_aug_init" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:187 +#, no-wrap +msgid "" +" int guestfs_aug_init (guestfs_h *g,\n" +"\t\tconst char *root,\n" +"\t\tint flags);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:191 ../fish/guestfish-actions.pod:152 +msgid "" +"Create a new Augeas handle for editing configuration files. If there was " +"any previous Augeas handle associated with this guestfs session, then it is " +"closed." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:195 +msgid "You must call this before using any other C commands." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:198 ../fish/guestfish-actions.pod:159 +msgid "" +"C is the filesystem root. C must not be NULL, use C instead." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:201 ../fish/guestfish-actions.pod:162 +msgid "" +"The flags are the same as the flags defined in Eaugeas.hE, the " +"logical I of the following integers:" +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:207 ../fish/guestfish-actions.pod:168 +msgid "C = 1" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:209 ../fish/guestfish-actions.pod:170 +msgid "Keep the original file with a C<.augsave> extension." +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:211 ../fish/guestfish-actions.pod:172 +msgid "C = 2" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:213 ../fish/guestfish-actions.pod:174 +msgid "" +"Save changes into a file with extension C<.augnew>, and do not overwrite " +"original. Overrides C." +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:216 ../fish/guestfish-actions.pod:177 +msgid "C = 4" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:218 ../fish/guestfish-actions.pod:179 +msgid "Typecheck lenses (can be expensive)." +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:220 ../fish/guestfish-actions.pod:181 +msgid "C = 8" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:222 ../fish/guestfish-actions.pod:183 +msgid "Do not use standard load path for modules." +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:224 ../fish/guestfish-actions.pod:185 +msgid "C = 16" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:226 ../fish/guestfish-actions.pod:187 +msgid "Make save a no-op, just record what would have been changed." +msgstr "" + +# type: =item +#: ../src/guestfs-actions.pod:228 ../fish/guestfish-actions.pod:189 +msgid "C = 32" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:230 +msgid "Do not load the tree in C." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:234 +msgid "To close the handle, you can call C." +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:236 ../fish/guestfish-actions.pod:197 +msgid "To find out more about Augeas, see L." +msgstr "" + +# type: =head2 +#: ../src/guestfs-actions.pod:240 +msgid "guestfs_aug_insert" +msgstr "" + +# type: verbatim +#: ../src/guestfs-actions.pod:242 +#, no-wrap +msgid "" +" int guestfs_aug_insert (guestfs_h *g,\n" +"\t\tconst char *augpath,\n" +"\t\tconst char *label,\n" +"\t\tint before);\n" +"\n" +msgstr "" + +# type: textblock +#: ../src/guestfs-actions.pod:247 ../fish/guestfish-actions.pod:203 +msgid "" +"Create a new sibling C