libguestfs/virt-v2v-docs-master — Tajik @ Fedora Weblate: AUTHORS

Zen

	English	Tajik	Actions
	Specify a libvirt connection URI
	B<-ip> file
	Instead of asking for password(s) interactively, pass the password through a file. Note the file should contain the whole password, B<without any trailing newline>, and for security the file should have mode C<0600> so that others cannot read it.
	Currently this option does not have any effect on xen+ssh transfers, but that is a bug.
	B<-q>
	B<--quiet>
	This disables progress bars and other unnecessary output.
	B<-v>
	B<--verbose>
	Enable verbose messages for debugging.
	B<-V>
	B<--version>
	Display version number and exit.
	SEE ALSO
	L<virt-v2v(1)>, L<virsh(1)>, L<http://libguestfs.org/>, L<https://libvirt.org/uri.html>, L<https://libvirt.org/remote.html>.
	AUTHORS	МУАЛЛИФ
	Richard W.M. Jones L<http://people.redhat.com/~rjones/>
	COPYRIGHT
	Copyright (C) 2009-2020 Red Hat Inc.
	virt-v2v-hacking -
	First a little history. Virt-v2v has been through at least two complete rewrites, so this is probably about the third version (but we don't intend to rewrite it again). The previous version was written in Perl and can be found here: L<https://git.fedorahosted.org/git/virt-v2v.git>
	The current version started out as almost a line-for-line rewrite of the Perl code in OCaml + C, and it still has a fairly similar structure. Therefore if there are details of this code that you don't understand (especially in the details of guest conversion), checking the Perl code may help.
	The files to start with when reading this code are:
	F<types.mli>
	F<v2v.ml>
	F<types.mli> defines all the structures used and passed around when communicating between different bits of the program. F<v2v.ml> controls how the program runs in stages.
	After studying those files, you may want to branch out into the input modules (F<input_>), the output modules (F<output_>) or the conversion modules (F<convert_*>). The input and output modules define I<-i> and I<-o> options (see the manual). The conversion modules define what guest types we can handle and the detailed steps involved in converting them.
	Every other file in this directory is a support module / library of some sort. Some code is written in C, especially where we want to use an external C library such as libxml2.
	L<virt-p2v(1)>, L<virt-v2v(1)>.
	Richard W.M. Jones
	virt-v2v-input-vmware - Using virt-v2v to convert guests from VMware

Loading…

No matching activity found.

Browse all string changes

Things to check

Reused translation

Other source string: “AUTHOR”

Reset

Glossary

English	Tajik
No related strings found in the glossary.

String information

Source string description

type: =head1

Source string location

docs/virt-v2v-copy-to-local.pod:120 • docs/virt-v2v-hacking.pod:53 • docs/virt-v2v-release-notes-1.42.pod:218 • docs/virt-v2v.pod:1684 • test-harness/virt-v2v-test-harness.pod:273

String age

3 years ago

Last updated

a year ago

Source string age

3 years ago

Translation file

po-docs/tg.po, string 192