+" 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"