+#: ../tools/virt-rescue.pl:43
+msgid ""
+"You must I<not> use C<virt-rescue> on live virtual machines. Doing so will "
+"probably result in disk corruption in the VM. C<virt-rescue> tries to stop "
+"you from doing this, but doesn't catch all cases."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:47
+msgid ""
+"However if you use the I<--ro> (read only) option, then you can attach a "
+"shell to a live virtual machine. The results might be strange or "
+"inconsistent at times but you won't get disk corruption."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:53
+msgid ""
+"virt-rescue is like a Rescue CD, but for virtual machines, and without the "
+"need for a CD. virt-rescue gives you a rescue shell and some simple "
+"recovery tools which you can use to examine or rescue a virtual machine or "
+"disk image."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:58
+msgid ""
+"You can run virt-rescue on any virtual machine known to libvirt, or directly "
+"on disk image(s):"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-rescue.pl:61
+#, no-wrap
+msgid ""
+" virt-rescue GuestName\n"
+"\n"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-rescue.pl:63
+#, no-wrap
+msgid ""
+" virt-rescue --ro /path/to/disk.img\n"
+"\n"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-rescue.pl:65
+#, no-wrap
+msgid ""
+" virt-rescue /dev/sdc\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:67
+msgid "For live VMs you I<must> use the --ro option."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:69
+msgid ""
+"When you run virt-rescue on a virtual machine or disk image, you are placed "
+"in an interactive bash shell where you can use many ordinary Linux "
+"commands. What you see in C</> (C</bin>, C</lib> etc) is the rescue "
+"appliance. You must mount the virtual machine's filesystems by hand. There "
+"is an empty directory called C</sysroot> where you can mount filesystems."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:76
+msgid ""
+"In the example below, we list logical volumes, then choose one to mount "
+"under C</sysroot>:"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-rescue.pl:79
+#, no-wrap
+msgid ""
+" ><rescue> lvs\n"
+" LV VG Attr LSize Origin Snap% Move Log Copy% Convert\n"
+" lv_root vg_f11x64 -wi-a- 8.83G\n"
+" lv_swap vg_f11x64 -wi-a- 992.00M\n"
+" ><rescue> mount /dev/vg_f11x64/lv_root /sysroot\n"
+" ><rescue> ls /sysroot\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:86
+msgid ""
+"If you don't know what filesystems are available on the virtual machine then "
+"you can use commands such as L<parted(8)> and L<lvs(8)> to find out."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:92
+msgid ""
+"Virt-rescue can be used on I<any> disk image file or device, not just a "
+"virtual machine. For example you can use it on a blank file if you want to "
+"partition that file (although we would recommend using L<guestfish(1)> "
+"instead as it is more suitable for this purpose). You can even use "
+"virt-rescue on things like SD cards."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:98
+msgid ""
+"This tool is just designed for quick interactive hacking on a virtual "
+"machine. For more structured access to a virtual machine disk image, you "
+"should use L<guestfs(3)>. To get a structured shell that you can use to "
+"make scripted changes to guests, use L<guestfish(1)>."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-rescue.pl:127
+msgid "B<--append kernelopts>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:129
+msgid "Pass additional options to the rescue kernel."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-rescue.pl:147
+msgid "B<--memsize MB> | B<-m MB>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:149
+msgid ""
+"Change the amount of memory allocated to the rescue system. The default is "
+"set by libguestfs and is small but adequate for running system tools. The "
+"occasional program might need more memory. The parameter is specified in "
+"megabytes."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-rescue.pl:158
+msgid "B<--ro> | B<-r>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:160
+msgid "Open the image read-only."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:172
+msgid ""
+"Enable SELinux in the rescue appliance. You should read "
+"L<guestfs(3)/SELINUX> before using this option."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:228
+msgid ""
+"Several environment variables affect virt-rescue. See "
+"L<guestfs(3)/ENVIRONMENT VARIABLES> for the complete list."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-rescue.pl:233
+msgid ""
+"L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<Sys::Guestfs(3)>, "
+"L<Sys::Guestfs::Lib(3)>, L<Sys::Virt(3)>, L<http://libguestfs.org/>."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:37
+msgid "virt-make-fs - Make a filesystem from a tar archive or files"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:41
+#, no-wrap
+msgid ""
+" virt-make-fs [--options] input.tar output.img\n"
+"\n"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:43
+#, no-wrap
+msgid ""
+" virt-make-fs [--options] input.tar.gz output.img\n"
+"\n"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:45
+#, no-wrap
+msgid ""
+" virt-make-fs [--options] directory output.img\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:49
+msgid ""
+"Virt-make-fs is a command line tool for creating a filesystem from a tar "
+"archive or some files in a directory. It is similar to tools like "
+"L<mkisofs(1)>, L<genisoimage(1)> and L<mksquashfs(1)>. Unlike those tools, "
+"it can create common filesystem types like ext2/3 or NTFS, which can be "
+"useful if you want to attach these filesystems to existing virtual machines "
+"(eg. to import large amounts of read-only data to a VM)."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:57
+msgid "Basic usage is:"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:59
+#, no-wrap
+msgid ""
+" virt-make-fs input output\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:61
+msgid ""
+"where C<input> is either a directory containing files that you want to add, "
+"or a tar archive (either uncompressed tar or gzip-compressed tar); and "
+"C<output> is a disk image. The input type is detected automatically. The "
+"output disk image defaults to a raw ext2 image unless you specify extra "
+"flags (see L</OPTIONS> below)."
+msgstr ""
+
+# type: =head2
+#: ../tools/virt-make-fs.pl:67
+msgid "EXTRA SPACE"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:69
+msgid ""
+"Unlike formats such as tar and squashfs, a filesystem does not \"just fit\" "
+"the files that it contains, but might have extra space. Depending on how "
+"you are going to use the output, you might think this extra space is wasted "
+"and want to minimize it, or you might want to leave space so that more files "
+"can be added later. Virt-make-fs defaults to minimizing the extra space, "
+"but you can use the C<--size> flag to leave space in the filesystem if you "
+"want it."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:77
+msgid ""
+"An alternative way to leave extra space but not make the output image any "
+"bigger is to use an alternative disk image format (instead of the default "
+"\"raw\" format). Using C<--format=qcow2> will use the native QEmu/KVM qcow2 "
+"image format (check your hypervisor supports this before using it). This "
+"allows you to choose a large C<--size> but the extra space won't actually be "
+"allocated in the image until you try to store something in it."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:85
+msgid ""
+"Don't forget that you can also use local commands including L<resize2fs(8)> "
+"and L<virt-resize(1)> to resize existing filesystems, or rerun "
+"virt-make-resize to build another image from scratch."
+msgstr ""
+
+# type: =head3
+#: ../tools/virt-make-fs.pl:89 ../tools/virt-make-fs.pl:123 ../tools/virt-make-fs.pl:142
+msgid "EXAMPLE"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:91
+#, no-wrap
+msgid ""
+" virt-make-fs --format=qcow2 --size=+200M input output.img\n"
+"\n"
+msgstr ""
+
+# type: =head2
+#: ../tools/virt-make-fs.pl:93
+msgid "FILESYSTEM TYPE"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:95
+msgid ""
+"The default filesystem type is C<ext2>. Just about any filesystem type that "
+"libguestfs supports can be used (but I<not> read-only formats like "
+"ISO9660). Here are some of the more common choices:"
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:101
+msgid "I<ext3>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:103
+msgid ""
+"Note that ext3 filesystems contain a journal, typically 1-32 MB in size. If "
+"you are not going to use the filesystem in a way that requires the journal, "
+"then this is just wasted overhead."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:107
+msgid "I<ntfs> or I<vfat>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:109
+msgid "Useful if exporting data to a Windows guest."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:111
+msgid ""
+"I<Note for vfat>: The tar archive or local directory must only contain files "
+"which are owned by root (ie. UID:GID = 0:0). The reason is that the tar "
+"program running within libguestfs is unable to change the ownership of "
+"non-root files, since vfat itself does not support this."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:116
+msgid "I<minix>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:118
+msgid ""
+"Lower overhead than C<ext2>, but certain limitations on filename length and "
+"total filesystem size."
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:125
+#, no-wrap
+msgid ""
+" virt-make-fs --type=minix input minixfs.img\n"
+"\n"
+msgstr ""
+
+# type: =head2
+#: ../tools/virt-make-fs.pl:127
+msgid "TO PARTITION OR NOT TO PARTITION"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:129
+msgid "Optionally virt-make-fs can add a partition table to the output disk."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:131
+msgid ""
+"Adding a partition can make the disk image more compatible with certain "
+"virtualized operating systems which don't expect to see a filesystem "
+"directly located on a block device (Linux doesn't care and will happily "
+"handle both types)."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:136
+msgid ""
+"On the other hand, if you have a partition table then the output image is no "
+"longer a straight filesystem. For example you cannot run L<fsck(8)> "
+"directly on a partitioned disk image. (However libguestfs tools such as "
+"L<guestfish(1)> and L<virt-resize(1)> can still be used)."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:144
+msgid "Add an MBR partition:"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:146
+#, no-wrap
+msgid ""
+" virt-make-fs --partition -- input disk.img\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:148
+msgid ""
+"If the output disk image could be terabyte-sized or larger, it's better to "
+"use an EFI/GPT-compatible partition table:"
+msgstr ""
+
+# type: verbatim
+#: ../tools/virt-make-fs.pl:151
+#, no-wrap
+msgid ""
+" virt-make-fs --partition=gpt --size=+4T --format=qcow2 input disk.img\n"
+"\n"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:179
+msgid "Enable debugging information."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:185
+msgid "B<--size=E<lt>NE<gt>>"
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:187
+msgid "B<--size=+E<lt>NE<gt>>"
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:189
+msgid "B<-s E<lt>NE<gt>>"
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:191
+msgid "B<-s +E<lt>NE<gt>>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:193
+msgid "Use the C<--size> (or C<-s>) option to choose the size of the output image."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:196
+msgid ""
+"If this option is I<not> given, then the output image will be just large "
+"enough to contain all the files, with not much wasted space."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:199
+msgid ""
+"To choose a fixed size output disk, specify an absolute number followed by "
+"b/K/M/G/T/P/E to mean bytes, Kilobytes, Megabytes, Gigabytes, Terabytes, "
+"Petabytes or Exabytes. This must be large enough to contain all the input "
+"files, else you will get an error."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:204
+msgid ""
+"To leave extra space, specify C<+> (plus sign) and a number followed by "
+"b/K/M/G/T/P/E to mean bytes, Kilobytes, Megabytes, Gigabytes, Terabytes, "
+"Petabytes or Exabytes. For example: C<--size=+200M> means enough space for "
+"the input files, and (approximately) an extra 200 MB free space."
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:210
+msgid ""
+"Note that virt-make-fs estimates free space, and therefore will not produce "
+"filesystems containing precisely the free space requested. (It is much more "
+"expensive and time-consuming to produce a filesystem which has precisely the "
+"desired free space)."
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:219
+msgid "B<--format=E<lt>fmtE<gt>>"
+msgstr ""
+
+# type: =item
+#: ../tools/virt-make-fs.pl:221
+msgid "B<-F E<lt>fmtE<gt>>"
+msgstr ""
+
+# type: textblock
+#: ../tools/virt-make-fs.pl:223
+msgid "Choose the output disk image format."