/test-data/phony-guests/debian.img
/test-data/phony-guests/fedora.img
/test-data/phony-guests/fedora-btrfs.img
-/test-data/phony-guests/fedora-luks.img
+/test-data/phony-guests/fedora-luks-on-lvm.img
+/test-data/phony-guests/fedora-lvm-on-luks.img
/test-data/phony-guests/fedora-md1.img
/test-data/phony-guests/fedora-md2.img
/test-data/phony-guests/fedora.db
/test-data/phony-guests/windows-software
/test-data/phony-guests/windows-system
/website/*.html
+/win-reg/virt-win-reg
--- /dev/null
+To learn how to compile guestfs-tools from sources:
+
+ guestfs-building(1) or http://libguestfs.org/guestfs-building.1.html
+
+To learn how to extend guestfs-tools:
+
+ guestfs-hacking(1) http://libguestfs.org/guestfs-hacking.1.html
+
+Although the above documentation applies specifically to libguestfs,
+this project was split from that repo, and similar steps and principles
+apply.
+
+For example, replace libguestfs with guestfs-tools in commands like:
+
+ dnf builddep guestfs-tools
# Perl tools.
SUBDIRS += win-reg
+# Miscellaneous documentation.
+SUBDIRS += docs
+
# After all source files were used we can generate the translation strings
SUBDIRS += po
if HAVE_PO4A
endif
EXTRA_DIST = \
+ HACKING \
README \
.gitignore \
+ bugs-in-changelog.sh \
check-mli.sh \
common/.gitignore \
common/README \
build-test-guests:
$(MAKE) -C test-data/phony-guests check
+check-valgrind: build-test-guests
+ @errors=0; \
+ for f in `grep -l '^$@:' $(SUBDIRS:%=%/Makefile.am)`; do \
+ echo $(MAKE) -C `dirname $$f` $@; \
+ $(MAKE) -C `dirname $$f` $@ || (( errors++ )); \
+ done; \
+ exit $$(( $$errors ? 1 : 0 ))
+
check-slow: build-test-guests
@errors=0; \
for f in `grep -l '^$@:' $(SUBDIRS:%=%/Makefile.am)`; do \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
-CSCOPE = cscope
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
TEST_SUITE_LOG = test-suite.log
TEST_EXTENSIONS = @EXEEXT@ .test
common/mlvisit common/mlxml common/mltools common/mlcustomize \
test-data align cat diff df edit format inspector make-fs \
customize builder builder/templates get-kernel resize sparsify \
- sysprep dib bash win-reg po po-docs
+ sysprep dib bash win-reg docs po po-docs
am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/config.h.in \
$(srcdir)/config.sh.in $(srcdir)/ocaml-dep.sh.in \
$(srcdir)/ocaml-link.sh.in $(srcdir)/podwrapper.pl.in \
$(top_srcdir)/builder/test-website/virt-builder/repos.d/libguestfs.conf.in \
$(top_srcdir)/common-rules.mk COPYING COPYING.LIB README \
build-aux/compile build-aux/config.guess \
- build-aux/config.rpath build-aux/config.sub \
- build-aux/install-sh build-aux/ltmain.sh build-aux/missing
+ build-aux/config.rpath build-aux/config.sub build-aux/depcomp \
+ build-aux/install-sh build-aux/ltmain.sh build-aux/missing \
+ build-aux/ylwrap
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
distdir = $(PACKAGE)-$(VERSION)
top_distdir = $(distdir)
DIST_ARCHIVES = $(distdir).tar.gz
GZIP_ENV = --best
DIST_TARGETS = dist-gzip
+# Exists only to be overridden by the user if desired.
+AM_DISTCHECK_DVI_TARGET = dvi
distuninstallcheck_listfiles = find . -type f -print
am__distuninstallcheck_listfiles = $(distuninstallcheck_listfiles) \
| sed 's|^\./|$(prefix)/|' | grep -v '$(infodir)/dir$$'
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
# Perl tools.
+# Miscellaneous documentation.
+
# After all source files were used we can generate the translation strings
SUBDIRS = gnulib/lib common/utils common/structs common/mlstdutils \
common/mlutils common/mlpcre common/edit common/options \
common/mltools common/mlcustomize test-data align cat diff df \
edit format inspector make-fs customize builder \
builder/templates get-kernel resize sparsify sysprep dib bash \
- win-reg po $(am__append_1)
+ win-reg docs po $(am__append_1)
EXTRA_DIST = \
+ HACKING \
README \
.gitignore \
+ bugs-in-changelog.sh \
check-mli.sh \
common/.gitignore \
common/README \
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
$(DISTCHECK_CONFIGURE_FLAGS) \
--srcdir=../.. --prefix="$$dc_install_base" \
&& $(MAKE) $(AM_MAKEFLAGS) \
- && $(MAKE) $(AM_MAKEFLAGS) dvi \
+ && $(MAKE) $(AM_MAKEFLAGS) $(AM_DISTCHECK_DVI_TARGET) \
&& $(MAKE) $(AM_MAKEFLAGS) check \
&& $(MAKE) $(AM_MAKEFLAGS) install \
&& $(MAKE) $(AM_MAKEFLAGS) installcheck \
build-test-guests:
$(MAKE) -C test-data/phony-guests check
+check-valgrind: build-test-guests
+ @errors=0; \
+ for f in `grep -l '^$@:' $(SUBDIRS:%=%/Makefile.am)`; do \
+ echo $(MAKE) -C `dirname $$f` $@; \
+ $(MAKE) -C `dirname $$f` $@ || (( errors++ )); \
+ done; \
+ exit $$(( $$errors ? 1 : 0 ))
+
check-slow: build-test-guests
@errors=0; \
for f in `grep -l '^$@:' $(SUBDIRS:%=%/Makefile.am)`; do \
-# generated automatically by aclocal 1.16.2 -*- Autoconf -*-
+# generated automatically by aclocal 1.16.5 -*- Autoconf -*-
-# Copyright (C) 1996-2020 Free Software Foundation, Inc.
+# Copyright (C) 1996-2021 Free Software Foundation, Inc.
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
AC_SUBST([$1])dnl
])
-# Copyright (C) 2002-2020 Free Software Foundation, Inc.
+# Copyright (C) 2002-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
[am__api_version='1.16'
dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way to
dnl require some minimum version. Point them to the right macro.
-m4_if([$1], [1.16.2], [],
+m4_if([$1], [1.16.5], [],
[AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl
])
# Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.
# This function is AC_REQUIREd by AM_INIT_AUTOMAKE.
AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
-[AM_AUTOMAKE_VERSION([1.16.2])dnl
+[AM_AUTOMAKE_VERSION([1.16.5])dnl
m4_ifndef([AC_AUTOCONF_VERSION],
[m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl
_AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))])
# AM_AUX_DIR_EXPAND -*- Autoconf -*-
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# AM_CONDITIONAL -*- Autoconf -*-
-# Copyright (C) 1997-2020 Free Software Foundation, Inc.
+# Copyright (C) 1997-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
Usually this means the macro was only invoked conditionally.]])
fi])])
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Generate code to set up dependency tracking. -*- Autoconf -*-
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Do all the work for Automake. -*- Autoconf -*-
-# Copyright (C) 1996-2020 Free Software Foundation, Inc.
+# Copyright (C) 1996-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# release and drop the old call support.
AC_DEFUN([AM_INIT_AUTOMAKE],
[AC_PREREQ([2.65])dnl
+m4_ifdef([_$0_ALREADY_INIT],
+ [m4_fatal([$0 expanded multiple times
+]m4_defn([_$0_ALREADY_INIT]))],
+ [m4_define([_$0_ALREADY_INIT], m4_expansion_stack)])dnl
dnl Autoconf wants to disallow AM_ names. We explicitly allow
dnl the ones we care about.
m4_pattern_allow([^AM_[A-Z]+FLAGS$])dnl
[_AM_SET_OPTIONS([$1])dnl
dnl Diagnose old-style AC_INIT with new-style AM_AUTOMAKE_INIT.
m4_if(
- m4_ifdef([AC_PACKAGE_NAME], [ok]):m4_ifdef([AC_PACKAGE_VERSION], [ok]),
+ m4_ifset([AC_PACKAGE_NAME], [ok]):m4_ifset([AC_PACKAGE_VERSION], [ok]),
[ok:ok],,
[m4_fatal([AC_INIT should be called with package and version arguments])])dnl
AC_SUBST([PACKAGE], ['AC_PACKAGE_TARNAME'])dnl
[m4_define([AC_PROG_OBJCXX],
m4_defn([AC_PROG_OBJCXX])[_AM_DEPENDENCIES([OBJCXX])])])dnl
])
+# Variables for tags utilities; see am/tags.am
+if test -z "$CTAGS"; then
+ CTAGS=ctags
+fi
+AC_SUBST([CTAGS])
+if test -z "$ETAGS"; then
+ ETAGS=etags
+fi
+AC_SUBST([ETAGS])
+if test -z "$CSCOPE"; then
+ CSCOPE=cscope
+fi
+AC_SUBST([CSCOPE])
+
AC_REQUIRE([AM_SILENT_RULES])dnl
dnl The testsuite driver may need to know about EXEEXT, so add the
dnl 'am__EXEEXT' conditional if _AM_COMPILER_EXEEXT was seen. This
done
echo "timestamp for $_am_arg" >`AS_DIRNAME(["$_am_arg"])`/stamp-h[]$_am_stamp_count])
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
fi
AC_SUBST([install_sh])])
-# Copyright (C) 2003-2020 Free Software Foundation, Inc.
+# Copyright (C) 2003-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Check to see how 'make' treats includes. -*- Autoconf -*-
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Fake the existence of programs that GNU maintainers use. -*- Autoconf -*-
-# Copyright (C) 1997-2020 Free Software Foundation, Inc.
+# Copyright (C) 1997-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
AC_REQUIRE_AUX_FILE([missing])dnl
if test x"${MISSING+set}" != xset; then
- case $am_aux_dir in
- *\ * | *\ *)
- MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;;
- *)
- MISSING="\${SHELL} $am_aux_dir/missing" ;;
- esac
+ MISSING="\${SHELL} '$am_aux_dir/missing'"
fi
# Use eval to expand $SHELL
if eval "$MISSING --is-lightweight"; then
# Helper functions for option handling. -*- Autoconf -*-
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
AC_DEFUN([_AM_IF_OPTION],
[m4_ifset(_AM_MANGLE_OPTION([$1]), [$2], [$3])])
-# Copyright (C) 1999-2020 Free Software Foundation, Inc.
+# Copyright (C) 1999-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# For backward compatibility.
AC_DEFUN_ONCE([AM_PROG_CC_C_O], [AC_REQUIRE([AC_PROG_CC])])
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Check to make sure that the build environment is sane. -*- Autoconf -*-
-# Copyright (C) 1996-2020 Free Software Foundation, Inc.
+# Copyright (C) 1996-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
rm -f conftest.file
])
-# Copyright (C) 2009-2020 Free Software Foundation, Inc.
+# Copyright (C) 2009-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
_AM_SUBST_NOTMAKE([AM_BACKSLASH])dnl
])
-# Copyright (C) 2001-2020 Free Software Foundation, Inc.
+# Copyright (C) 2001-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s"
AC_SUBST([INSTALL_STRIP_PROGRAM])])
-# Copyright (C) 2006-2020 Free Software Foundation, Inc.
+# Copyright (C) 2006-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# Check how to create a tarball. -*- Autoconf -*-
-# Copyright (C) 2004-2020 Free Software Foundation, Inc.
+# Copyright (C) 2004-2021 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 0);
- assert (live == 0);
/* Must be no extra arguments on the command line. */
if (optind != argc)
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to rebuild."
-@HAVE_BASH_COMPLETION_FALSE@install-data-local:
@HAVE_BASH_COMPLETION_FALSE@clean-local:
+@HAVE_BASH_COMPLETION_FALSE@install-data-local:
clean: clean-am
clean-am: clean-generic clean-libtool clean-local mostlyclean-am
# virt-tools bash completion script -*- shell-script -*-
-# Copyright (C) 2010-2020 Red Hat Inc.
+# Copyright (C) 2010-2021 Red Hat Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
COMPREPLY=( $( compgen -W "short long json" -- "$cur") )
return ;;
--password-crypto)
- COMPREPLY=( $( compgen -W "md5 sha256 sha512" -- "$cur") )
+ COMPREPLY=( $( compgen -W "md5 sha256 sha512 yescrypt" -- "$cur") )
return ;;
--unknown-filesystems)
COMPREPLY=( $( compgen -W "ignore warn error" -- "$cur") )
--- /dev/null
+#!/bin/bash -
+# bugs-in-changelog.sh
+# Copyright (C) 2009-2020 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# Used when preparing the release notes. This script looks at the
+# bugs noted in the git changelog since the last stable release (or
+# any release). To use it, the only parameter should be the git
+# commit range, eg:
+#
+# ./bugs-in-changelog.sh "1.0.89.."
+
+if [ -z "$1" ]; then
+ echo "$0 git-commit-range"
+ exit 1
+fi
+
+# Comma-separated list of Bugzilla IDs.
+bugids=$(
+ git log "$1" |
+ egrep -io 'RHBZ#[0-9]+|https?://bugzilla.redhat.com/[a-z\.\?/_=]*[0-9]+' |
+ sed 's/^[^0-9]*//' |
+ sort -u |
+ tr '\n' ',' |
+ sed 's/,$//'
+)
+
+#echo bugids "$bugids"
+
+# Filter out any bugs which may still be in NEW or ASSIGNED.
+#
+# Ensure user is logged in, otherwise bugzilla will silently truncate
+# the number of responses. To log in, see "API KEYS" in bugzilla(1).
+bugzilla \
+ --ensure-logged-in \
+ query \
+ -b "$bugids" \
+ -s MODIFIED,POST,ON_QA,PASSES_QA,VERIFIED,RELEASE_PENDING,CLOSED \
+ --outputformat='%{bug_id} %{short_desc}' |
+ sort -n -r |
+ perl -pe '
+ s{([0-9]+)\s+(.*)}{
+ sprintf ("=item L<https://bugzilla.redhat.com/%s>\n\n%s\n",
+ $1, $2)
+ }xe'
-pthread \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
-Wno-unused-macros \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBLZMA_CFLAGS) \
$(LIBTINFO_CFLAGS) \
$(LIBXML2_CFLAGS)
-lutils \
$(LIBTINFO_LIBS) \
$(LIBCRYPT_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBLZMA_LIBS) \
$(LIBXML2_LIBS) \
$(JANSSON_LIBS) \
-I$(top_srcdir)/include
virt_index_validate_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
- -Wno-unused-macros
+ -Wno-unused-macros \
+ $(LIBGUESTFS_CFLAGS)
virt_index_validate_LDADD = \
$(LTLIBINTL) \
../gnulib/lib/libgnu.la
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@ -pthread \
@HAVE_OCAML_TRUE@ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
@HAVE_OCAML_TRUE@ -Wno-unused-macros \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBLZMA_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBTINFO_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_CFLAGS)
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBTINFO_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBCRYPT_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBLZMA_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
@HAVE_OCAML_TRUE@ $(JANSSON_LIBS) \
virt_index_validate_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
- -Wno-unused-macros
+ -Wno-unused-macros \
+ $(LIBGUESTFS_CFLAGS)
virt_index_validate_LDADD = \
$(LTLIBINTL) \
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
done
install: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) install-am
-install-exec: install-exec-am
+install-exec: $(BUILT_SOURCES)
+ $(MAKE) $(AM_MAKEFLAGS) install-exec-am
install-data: install-data-am
uninstall: uninstall-am
uninstall-man: uninstall-man1
-.MAKE: all check check-am install install-am install-strip
+.MAKE: all check check-am install install-am install-exec \
+ install-strip
.PHONY: CTAGS GTAGS TAGS all all-am am--depfiles check check-TESTS \
check-am clean clean-binPROGRAMS clean-checkPROGRAMS \
* create.
*)
let tmpdir = Mkdtemp.temp_dir "virt-builder." in
- rmdir_on_exit tmpdir;
+ On_exit.rmdir tmpdir;
(* Download the sources. *)
let downloader = Downloader.create ~curl:cmdline.curl ~cache ~tmpdir in
let progress_bar = not (quiet ()) in
Downloader.download downloader ~template ~progress_bar ~proxy
file_uri in
- if delete_on_exit then unlink_on_exit template;
+ if delete_on_exit then On_exit.unlink template;
template in
(* Check the signature of the file. *)
| { Index.signature_uri = Some signature_uri } ->
let sigfile, delete_on_exit =
Downloader.download downloader signature_uri in
- if delete_on_exit then unlink_on_exit sigfile;
+ if delete_on_exit then On_exit.unlink sigfile;
Some sigfile in
Sigchecker.verify_detached sigchecker template sigfile in
* to choose unique tempfiles per transition, so this is OK:
*)
let tempfile = Filename.temp_file ~temp_dir:cache_dir "vb" ".img" in
- unlink_on_exit tempfile;
+ On_exit.unlink tempfile;
(* Always possible to copy from one place to another. The only
* thing a copy does is to remove the template tag (since it's always
* atomically rename it to the final filename.
*)
let filename_new = filename ^ "." ^ String.random8 () in
- unlink_on_exit filename_new;
+ On_exit.unlink filename_new;
(match parseduri.URI.protocol with
(* Download (ie. copy) from a local file. *)
let tmpdir =
let tmpdir = Mkdtemp.temp_dir "guestfs-tests." in
- rmdir_on_exit tmpdir;
+ On_exit.rmdir tmpdir;
tmpdir
let dummy_sigchecker = Sigchecker.create ~gpg:"gpg"
*)
external pxzcat : string -> string -> unit = "virt_builder_pxzcat"
-external using_parallel_xzcat : unit -> bool = "virt_builder_using_parallel_xzcat" "noalloc"
+external using_parallel_xzcat : unit -> bool = "virt_builder_using_parallel_xzcat" [@@noalloc]
(* Create a temporary folder to work in *)
let tmpdir = Mkdtemp.temp_dir ~base_dir:cmdline.repo
"virt-builder-repository." in
- rmdir_on_exit tmpdir;
+ On_exit.rmdir tmpdir;
let tmprepo = tmpdir // "repo" in
mkdir_p tmprepo 0o700;
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
--- /dev/null
+[alma-8.5]
+name=AlmaLinux 8.5
+osinfo=almalinux8
+arch=x86_64
+file=alma-8.5.xz
+checksum[sha512]=f5e50e4eeb56e0fe17436210bc1218a72999f581fff787e748b161646a38661722818455bdee3c1ffed81df3302d913b78de562f2095e1b9dd0539e6990a861d
+format=raw
+size=6442450944
+compressed_size=496571356
+expand=/dev/sda4
+notes=AlmaLinux 8.5
+
+ This AlmaLinux image contains only unmodified @Core group packages.
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# Kickstart file for alma-8.5
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+install
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'alma-8.5'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-pev56f7p' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=almalinux8' \
+ '--initrd-inject=alma-8.5.ks' \
+ '--extra-args=inst.ks=file:/alma-8.5.ks inst.repo=http://repo.almalinux.org/almalinux/8/BaseOS/x86_64/os/ console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-pev56f7p.img,size=6,format=raw' \
+ '--location=http://mirror.cov.ukservers.com/almalinux/8.5/BaseOS/x86_64/kickstart/' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+[centosstream-8]
+name=CentOS Stream 8
+osinfo=centosstream8
+arch=x86_64
+file=centosstream-8.xz
+checksum[sha512]=73668d92f2b028820ed7ec01367f16cff12c4a62c2b9dcd3c56d7ea3aefa25f45f03d859a0f047dd264db3bfc69e8bc95aa48e6bd350b41e2353a97e5d95fdb1
+format=raw
+size=6442450944
+compressed_size=471938880
+expand=/dev/sda4
+notes=CentOS Stream 8
+
+ This CentOS Stream image contains only unmodified @Core group packages.
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# Kickstart file for centosstream-8
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+install
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'centosstream-8'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-parkabak' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=rhel8.0' \
+ '--initrd-inject=centosstream-8.ks' \
+ '--extra-args=ks=file:/centosstream-8.ks console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/data/src/guestfs-tools/builder/templates/tmp-parkabak.img,size=6,format=raw' \
+ '--location=http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+[debian-11]
+name=Debian 11 (bullseye)
+osinfo=debian11
+arch=x86_64
+file=debian-11.xz
+checksum[sha512]=c44a82bde9d7d5478ca9ed6ddbfd199237216f2c90896cb2cf07d3b9439f4bfcdc0b370d5e848d347bbd6f73b3f860f3c015901843b9756937a72d0505e0804a
+format=raw
+size=6442450944
+compressed_size=233468380
+expand=/dev/sda1
+notes=Debian 11 (bullseye)
+
+ This is a minimal Debian install.
+
+ This image is so very minimal that it only includes an ssh server
+ This image does not contain SSH host keys. To regenerate them use:
+
+ --firstboot-command "dpkg-reconfigure openssh-server"
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'debian-11'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-cndg6a6p' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=debian8' \
+ '--initrd-inject=/tmp/fltk7gd4.tmp/preseed.cfg' \
+ '--extra-args=auto mirror/http/proxy= console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-cndg6a6p.img,size=6,format=raw' \
+ '--location=http://deb.debian.org/debian/dists/bullseye/main/installer-amd64' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+[fedora-34]
+name=Fedora® 34 Server (armv7l)
+osinfo=fedora34
+arch=armv7l
+file=fedora-34-armv7l.xz
+revision=2
+checksum[sha512]=99ea2c9c987d0bf78ceaceb729883969e49f3785e6508cee10259fa472721d2fa23bdcc98ec64d57a032b021292470061fd0d4652970a561562d89a8977eda81
+format=raw
+size=6442450944
+compressed_size=396629488
+expand=/dev/sda3
+notes=Fedora® 34 Server (armv7l)
+
+ This Fedora image contains only unmodified @Core group packages.
+
+ Fedora and the Infinity design logo are trademarks of Red Hat, Inc.
+ Source and further information is available from http://fedoraproject.org/
+
+ You will need to use the associated UEFI NVRAM variables file:
+ http://libguestfs.org/download/builder/fedora-34-armv7l-nvram.xz
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# Kickstart file for fedora-34-armv7l
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyAMA0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+%post
+# Ensure the installation is up-to-date.
+# This makes Fedora >= 33 unbootable, see:
+# https://bugzilla.redhat.com/show_bug.cgi?id=1911177
+#dnf -y --best upgrade
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'fedora-34-armv7l'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-wm0yz2f0' \
+ '--ram=4096' \
+ '--arch=armv7l' \
+ '--machine=virt-2.11' \
+ '--vcpus=1' \
+ '--os-variant=fedora34' \
+ '--boot' 'loader=/usr/share/edk2/arm/QEMU_EFI-pflash.raw,loader_ro=yes,loader_type=pflash,nvram=/home/rjones/d/guestfs-tools/builder/templates/tmp-wm0yz2f0.vars' \
+ '--initrd-inject=fedora-34-armv7l.ks' \
+ '--extra-args=inst.ks=file:/fedora-34-armv7l.ks console=tty0 console=ttyAMA0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-wm0yz2f0.img,size=6,format=raw' \
+ '--location=https://mirror.bytemark.co.uk/fedora/linux/releases/34/Server/armhfp/os/' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+[fedora-35]
+name=Fedora® 35 Server (aarch64)
+osinfo=fedora35
+arch=aarch64
+file=fedora-35-aarch64.xz
+checksum[sha512]=4315b72c67a00b7d3efb606145fcf648baf2a991228f47d57e64e17885ff93567b2510751e78ca749842b22d33ff704db545ba28b42b03f3683c042dceceb4bd
+format=raw
+size=6442450944
+compressed_size=473245720
+expand=/dev/sda3
+notes=Fedora® 35 Server (aarch64)
+
+ This Fedora image contains only unmodified @Core group packages.
+
+ Fedora and the Infinity design logo are trademarks of Red Hat, Inc.
+ Source and further information is available from http://fedoraproject.org/
+
+ You will need to use the associated UEFI NVRAM variables file:
+ http://libguestfs.org/download/builder/fedora-35-aarch64-nvram.xz
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# Kickstart file for fedora-35-aarch64
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=ttyAMA0 earlyprintk=pl011,0x9000000 ignore_loglevel no_timer_check printk.time=1 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+%post
+# Ensure the installation is up-to-date.
+# This makes Fedora >= 33 unbootable, see:
+# https://bugzilla.redhat.com/show_bug.cgi?id=1911177
+#dnf -y --best upgrade
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'fedora-35-aarch64'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-fd1rfc4g' \
+ '--ram=4096' \
+ '--arch=aarch64' \
+ '--vcpus=1' \
+ '--os-variant=fedora34' \
+ '--boot' 'loader=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,loader_ro=yes,loader_type=pflash,nvram=/home/rjones/d/guestfs-tools/builder/templates/tmp-fd1rfc4g.vars' \
+ '--initrd-inject=fedora-35-aarch64.ks' \
+ '--extra-args=inst.ks=file:/fedora-35-aarch64.ks console=ttyAMA0 earlyprintk=pl011,0x9000000 ignore_loglevel no_timer_check printk.time=1 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-fd1rfc4g.img,size=6,format=raw' \
+ '--location=https://mirror.bytemark.co.uk/fedora/linux/releases/35/Server/aarch64/os/' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+[fedora-35]
+name=Fedora® 35 Server
+osinfo=fedora35
+arch=x86_64
+file=fedora-35.xz
+checksum[sha512]=bd5d6c1311463b7bee3c3743ab14ad05dfbfedc135933c519015e62ebd127d904be7222391fb73c4631044e44b5f70038a28d87b5a6be1508bca752517929415
+format=raw
+size=6442450944
+compressed_size=474387772
+expand=/dev/sda3
+notes=Fedora® 35 Server
+
+ This Fedora image contains only unmodified @Core group packages.
+
+ Fedora and the Infinity design logo are trademarks of Red Hat, Inc.
+ Source and further information is available from http://fedoraproject.org/
+
+ This template was generated by a script in the libguestfs source tree:
+ builder/templates/make-template.ml
+ Associated files used to prepare this template can be found in the
+ same directory.
+
--- /dev/null
+# Kickstart file for fedora-35
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+%post
+# Ensure the installation is up-to-date.
+# This makes Fedora >= 33 unbootable, see:
+# https://bugzilla.redhat.com/show_bug.cgi?id=1911177
+#dnf -y --best upgrade
+# Enable Xen domU support.
+pushd /etc/dracut.conf.d
+echo 'add_drivers+=" xen:vbd xen:vif "' > virt-builder-xen-drivers.conf
+popd
+# To make dracut config changes permanent, we need to rerun dracut.
+# Rerun dracut for the installed kernel (not the running kernel).
+# See commit 0fa52e4e45d80874bc5ea5f112f74be1d3f3472f and
+# https://www.redhat.com/archives/libguestfs/2014-June/thread.html#00045
+KERNEL_VERSION="$(rpm -q kernel --qf '%{version}-%{release}.%{arch}\n' | sort -V | tail -1)"
+dracut -f /boot/initramfs-$KERNEL_VERSION.img $KERNEL_VERSION
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'fedora-35'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-4qrk2p3m' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=fedora34' \
+ '--initrd-inject=fedora-35.ks' \
+ '--extra-args=inst.ks=file:/fedora-35.ks console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-4qrk2p3m.img,size=6,format=raw' \
+ '--location=https://mirror.bytemark.co.uk/fedora/linux/releases/35/Server/x86_64/os/' \
+ '--serial=pty' \
+ '--nographics'
+
#!/usr/bin/env ocaml
(* libguestfs
- * Copyright (C) 2016-2020 Red Hat Inc.
+ * Copyright (C) 2016-2022 Red Hat Inc.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
;;
type os =
+ | Alma of int * int (* major, minor *)
| CentOS of int * int (* major, minor *)
+ | CentOSStream of int (* major *)
| RHEL of int * int
| Debian of int * string (* version, dist name like "wheezy" *)
| Ubuntu of string * string
| Aarch64 ->
"/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw",
"/usr/share/edk2/aarch64/vars-template-pflash.raw"
+ | Armv7 ->
+ "/usr/share/edk2/arm/QEMU_EFI-pflash.raw",
+ "/usr/share/edk2/arm/vars-template-pflash.raw"
| _ -> assert false in
let vars_out = Sys.getcwd () // sprintf "%s.vars" tmpname in
and os_of_string os ver =
match os, ver with
+ | "alma", ver -> let maj, min = parse_major_minor ver in Alma (maj, min)
| "centos", ver -> let maj, min = parse_major_minor ver in CentOS (maj, min)
+ | "centosstream", ver -> CentOSStream(int_of_string ver)
| "rhel", ver -> let maj, min = parse_major_minor ver in RHEL (maj, min)
| "debian", "6" -> Debian (6, "squeeze")
| "debian", "7" -> Debian (7, "wheezy")
| "debian", "8" -> Debian (8, "jessie")
| "debian", "9" -> Debian (9, "stretch")
| "debian", "10" -> Debian (10, "buster")
+ | "debian", "11" -> Debian (11, "bullseye")
| "ubuntu", "10.04" -> Ubuntu (ver, "lucid")
| "ubuntu", "12.04" -> Ubuntu (ver, "precise")
| "ubuntu", "14.04" -> Ubuntu (ver, "trusty")
| Fedora ver ->
if arch = X86_64 then sprintf "fedora-%d%s" ver ext
else sprintf "fedora-%d-%s%s" ver (string_of_arch arch) ext
+ | Alma (major, minor) ->
+ if arch = X86_64 then sprintf "alma-%d.%d%s" major minor ext
+ else sprintf "alma-%d.%d-%s%s" major minor (string_of_arch arch) ext
| CentOS (major, minor) ->
if arch = X86_64 then sprintf "centos-%d.%d%s" major minor ext
else sprintf "centos-%d.%d-%s%s" major minor (string_of_arch arch) ext
+ | CentOSStream ver ->
+ if arch = X86_64 then sprintf "centosstream-%d%s" ver ext
+ else sprintf "centosstream-%d-%s%s" ver (string_of_arch arch) ext
| RHEL (major, minor) ->
if arch = X86_64 then sprintf "rhel-%d.%d%s" major minor ext
else sprintf "rhel-%d.%d-%s%s" major minor (string_of_arch arch) ext
(* This is what virt-builder called "os-version". *)
and string_of_os_noarch = function
| Fedora ver -> sprintf "fedora-%d" ver
+ | Alma (major, minor) -> sprintf "alma-%d.%d" major minor
| CentOS (major, minor) -> sprintf "centos-%d.%d" major minor
+ | CentOSStream ver -> sprintf "centosstream-%d" ver
| RHEL (major, minor) -> sprintf "rhel-%d.%d" major minor
| Debian (ver, _) -> sprintf "debian-%d" ver
| Ubuntu (ver, _) -> sprintf "ubuntu-%s" ver
(* Does virt-sysprep know how to sysprep this OS? *)
and can_sysprep_os = function
- | RHEL _ | CentOS _ | Fedora _ | Debian _ | Ubuntu _ -> true
+ | RHEL _ | Alma _ | CentOS _ | CentOSStream _ | Fedora _
+ | Debian _ | Ubuntu _ -> true
| FreeBSD _ | Windows _ -> false
and is_selinux_os = function
- | RHEL _ | CentOS _ | Fedora _ -> true
+ | RHEL _ | Alma _ | CentOS _ | CentOSStream _ | Fedora _ -> true
| Debian _ | Ubuntu _
| FreeBSD _ | Windows _ -> false
and needs_uefi os arch =
match os, arch with
+ | Fedora _, Armv7
| Fedora _, Aarch64
| RHEL _, Aarch64 -> true
- | RHEL _, _ | CentOS _, _ | Fedora _, _
+ | RHEL _, _ | Alma _, _ | CentOS _, _ | CentOSStream _, _ | Fedora _, _
| Debian _, _ | Ubuntu _, _
| FreeBSD _, _ | Windows _, _ -> false
and get_virtual_size_gb os arch =
match os with
- | RHEL _ | CentOS _ | Fedora _
+ | RHEL _ | Alma _ | CentOS _ | CentOSStream _ | Fedora _
| Debian _ | Ubuntu _
| FreeBSD _ -> 6
| Windows (10, _, _) -> 40 (* Windows 10 *)
and make_kickstart os arch =
match os with
(* Kickstart. *)
- | Fedora _ | CentOS _ | RHEL _ ->
+ | Fedora _ | Alma _ | CentOS _ | CentOSStream _ | RHEL _ ->
let ks_filename = filename_of_os os arch ".ks" in
Some (make_kickstart_common ks_filename os arch)
(* Fedora 34+ removes the "install" keyword. *)
(match os with
| Fedora n when n >= 34 -> ()
- | RHEL (n, _) | CentOS (n, _) when n >= 9 -> ()
+ | RHEL (n, _)
+ | Alma (n, _) | CentOS (n, _) | CentOSStream n when n >= 9 -> ()
| _ -> bpf "install\n";
);
*)
(match os with
| CentOS (8, _) ->
- bpf "url --url=\"http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os\"\n"
+ bpf "url --url=\"https://vault.centos.org/8.5.2111/BaseOS/x86_64/os/\"\n"
| _ -> ()
);
bpf "\n";
part swap --size=1024 --asprimary
part / --fstype=%s --size=1024 --grow --asprimary
" bootfs rootfs;
- | CentOS _ | RHEL _ | Fedora _ ->
+ | Alma _ | CentOS _ | CentOSStream _ | RHEL _ | Fedora _ ->
bpf "\
zerombr
clearpart --all --initlabel --disklabel=gpt
and make_boot_media os arch =
match os, arch with
+ | Alma (major, minor), X86_64 ->
+ (* UK mirror *)
+ Location (sprintf "http://mirror.cov.ukservers.com/almalinux/%d.%d/BaseOS/x86_64/kickstart/"
+ major minor)
+
| CentOS (major, _), Aarch64 ->
(* XXX This always points to the latest CentOS, so
* effectively the minor number is always ignored.
Location "http://mirror.centos.org/centos-7/7/os/x86_64/"
| CentOS (8, _), X86_64 ->
- Location "http://mirror.centos.org/centos-8/8/BaseOS/x86_64/kickstart"
+ (* This is probably the last CentOS 8 release. *)
+ Location "https://vault.centos.org/8.5.2111/BaseOS/x86_64/kickstart/"
+
+ | CentOSStream ver, X86_64 ->
+ Location (sprintf "http://mirror.centos.org/centos/%d-stream/BaseOS/x86_64/os" ver)
| Debian (_, dist), arch ->
Location (sprintf "http://deb.debian.org/debian/dists/%s/main/installer-%s"
(* If the install is not automated and we need a graphical console. *)
and needs_graphics = function
- | CentOS _ | RHEL _ | Debian _ | Ubuntu _ | Fedora _ -> false
+ | Alma _ | CentOS _ | CentOSStream _ | RHEL _
+ | Debian _ | Ubuntu _ | Fedora _ -> false
| FreeBSD _ | Windows _ -> true
(* NB: Arguments do not need to be quoted, because we pass them
add "--machine=pseries";
add "--cpu=power8";
add "--vcpus=1"
+ | Armv7 ->
+ add "--arch=armv7l";
+ add "--machine=virt-2.11"; (* RHBZ#1633328, RHBZ#2003706 *)
+ add "--vcpus=1"
| arch ->
add (sprintf "--arch=%s" (string_of_arch arch));
add "--vcpus=1"
(* --initrd-inject and --extra-args flags for Linux only. *)
(match os with
| Debian _ | Ubuntu _
- | Fedora _ | RHEL _ | CentOS _ ->
+ | Fedora _ | RHEL _ | Alma _ | CentOS _ | CentOSStream _ ->
let ks =
match ks with None -> assert false | Some ks -> ks in
add (sprintf "--initrd-inject=%s" ks);
| Debian _ | Ubuntu _ -> "auto"
| Fedora n when n >= 34 ->
sprintf "inst.ks=file:/%s" (Filename.basename ks)
- | RHEL (n, _) | CentOS (n, _) when n >= 9 ->
+ | Alma (major, _) ->
+ (* This is only required because of missing osinfo-db data.
+ * https://bugs.almalinux.org/view.php?id=127
+ * Once this is fixed, do the same as CentOS below.
+ *)
+ sprintf "inst.ks=file:/%s inst.repo=http://repo.almalinux.org/almalinux/%d/BaseOS/x86_64/os/" (Filename.basename ks) major
+ | RHEL (n, _) | CentOS (n, _) | CentOSStream n when n >= 9 ->
sprintf "inst.ks=file:/%s" (Filename.basename ks)
- | Fedora _ | RHEL _ | CentOS _ ->
+ | Fedora _ | RHEL _ | CentOS _ | CentOSStream _ ->
sprintf "ks=file:/%s" (Filename.basename ks)
| FreeBSD _ | Windows _ -> assert false in
let proxy =
match p with
| None ->
(match os with
- | Fedora _ | RHEL _ | CentOS _ | Ubuntu _ -> ""
+ | Fedora _ | RHEL _ | Alma _ | CentOS _ | CentOSStream _
+ | Ubuntu _ -> ""
| Debian _ -> "mirror/http/proxy="
| FreeBSD _ | Windows _ -> assert false
)
| Some p ->
match os with
| Fedora n when n >= 34 -> sprintf "inst.proxy=" ^ p
- | RHEL (n, _) | CentOS (n, _) when n >= 9 -> "inst.proxy=" ^ p
- | Fedora _ | RHEL _ | CentOS _ -> "proxy=" ^ p
+ | RHEL (n, _)
+ | Alma (n, _) | CentOS (n, _) | CentOSStream n when n >= 9 ->
+ "inst.proxy=" ^ p
+ | Fedora _ | RHEL _ | Alma _ | CentOS _ | CentOSStream _ ->
+ "proxy=" ^ p
| Debian _ | Ubuntu _ -> "mirror/http/proxy=" ^ p
| FreeBSD _ | Windows _ -> assert false in
if not for_fedora then (
match os with
| Fedora ver -> sprintf "fedora%d" ver
+ | Alma (major, _) -> sprintf "almalinux%d" major
| CentOS (major, minor) -> sprintf "centos%d.%d" major minor
+ | CentOSStream ver -> sprintf "centosstream%d" ver
| RHEL (major, minor) -> sprintf "rhel%d.%d" major minor
| Debian (ver, _) -> sprintf "debian%d" ver
| Ubuntu (ver, _) -> sprintf "ubuntu%s" ver
| Fedora _, (PPC64|PPC64le) -> "fedora22"
| Fedora ver, _ when ver <= 23 ->
sprintf "fedora%d" ver
- | Fedora _, _ -> "fedora26" (* max version known in Fedora 28 *)
+ | Fedora _, _ -> "fedora34" (* max version known in Fedora 34 *)
+
+ | Alma (major, _), _ -> sprintf "almalinux%d" major
| CentOS (8, _), _ -> "rhel8.0" (* temporary until osinfo updated *)
| CentOS (major, minor), _ when (major, minor) <= (7,0) ->
sprintf "centos%d.%d" major minor
| CentOS _, _ -> "centos7.0" (* max version known in Fedora 31 *)
+ | CentOSStream 8, _ -> "rhel8.0" (* temporary until osinfo updated *)
+ | CentOSStream _, _ -> "rhel8.0" (* min known version is 8 *)
+
| RHEL (6, minor), _ when minor <= 8 ->
sprintf "rhel6.%d" minor
| RHEL (6, _), _ -> "rhel6.9" (* max version known in Fedora 29 *)
"console=tty0 console=ttyAMA0,115200 rd_NO_PLYMOUTH"
| (Debian _|Fedora _|Ubuntu _), (PPC64|PPC64le) ->
"console=tty0 console=hvc0 rd_NO_PLYMOUTH"
- | (RHEL _|CentOS _), PPC64
- | (RHEL _|CentOS _), PPC64le ->
+ | (RHEL _ | Alma _ | CentOS _ | CentOSStream _), PPC64
+ | (RHEL _ | Alma _ | CentOS _ | CentOSStream _), PPC64le ->
"console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
| FreeBSD _, _ | Windows _, _ -> assert false
g#write "/etc/yum.repos.d/download.devel.redhat.com.repo" yum_conf
)
- | RHEL _ | Fedora _ | CentOS _ | FreeBSD _ | Windows _ -> None
+ | RHEL _ | Fedora _ | Alma _ | CentOS _ | CentOSStream _
+ | FreeBSD _ | Windows _ -> None
and make_rhel_yum_conf major minor arch =
let buf = Buffer.create 4096 in
and long_name_of_os os arch =
match os, arch with
+ | Alma (major, minor), X86_64 ->
+ sprintf "AlmaLinux %d.%d" major minor
+ | Alma (major, minor), arch ->
+ sprintf "AlmaLinux %d.%d (%s)" major minor (string_of_arch arch)
| CentOS (major, minor), X86_64 ->
sprintf "CentOS %d.%d" major minor
| CentOS (major, minor), arch ->
sprintf "CentOS %d.%d (%s)" major minor (string_of_arch arch)
+ | CentOSStream ver, X86_64 ->
+ sprintf "CentOS Stream %d" ver
+ | CentOSStream ver, arch ->
+ sprintf "CentOS Stream %d (%s)" ver (string_of_arch arch)
| Debian (ver, dist), X86_64 ->
sprintf "Debian %d (%s)" ver dist
| Debian (ver, dist), arch ->
add "";
(match os with
+ | Alma _ ->
+ add "This AlmaLinux image contains only unmodified @Core group packages."
| CentOS _ ->
add "This CentOS image contains only unmodified @Core group packages."
+ | CentOSStream _ ->
+ add "This CentOS Stream image contains only unmodified @Core group packages."
| Debian _ ->
add "This is a minimal Debian install."
| Fedora _ ->
--- /dev/null
+# Kickstart file for rhel-8.3
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+install
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'rhel-8.3'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-n24u28xe' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=rhel8.0' \
+ '--initrd-inject=rhel-8.3.ks' \
+ '--extra-args=ks=file:/rhel-8.3.ks console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-n24u28xe.img,size=6,format=raw' \
+ '--location=http://download.eng.bos.redhat.com/released/rhel-6-7-8/rhel-8/RHEL-8/8.3.0/BaseOS/x86_64/os' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+# Kickstart file for rhel-8.4
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+install
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'rhel-8.4'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-n44ma315' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=rhel8.0' \
+ '--initrd-inject=rhel-8.4.ks' \
+ '--extra-args=ks=file:/rhel-8.4.ks console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-n44ma315.img,size=6,format=raw' \
+ '--location=http://download.eng.bos.redhat.com/released/rhel-6-7-8/rhel-8/RHEL-8/8.4.0/BaseOS/x86_64/os' \
+ '--serial=pty' \
+ '--nographics'
+
--- /dev/null
+# Kickstart file for rhel-8.5
+# Generated by libguestfs.git/builder/templates/make-template.ml
+
+install
+text
+reboot
+lang en_US.UTF-8
+keyboard us
+network --bootproto dhcp
+rootpw builder
+firewall --enabled --ssh
+timezone --utc America/New_York
+selinux --enforcing
+
+bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
+
+
+zerombr
+clearpart --all --initlabel --disklabel=gpt
+autopart --type=plain
+
+# Halt the system once configuration has finished.
+poweroff
+
+%packages
+@core
+%end
+
+# EOF
--- /dev/null
+# This is the virt-install command which was used to create
+# the virt-builder template 'rhel-8.5'
+# NB: This file is generated for documentation purposes ONLY!
+# This script was never run, and is not intended to be run.
+
+'virt-install' \
+ '--transient' \
+ '--name=tmp-ntvwrorc' \
+ '--ram=4096' \
+ '--arch=x86_64' \
+ '--cpu=host' \
+ '--vcpus=4' \
+ '--os-variant=rhel8.0' \
+ '--initrd-inject=rhel-8.5.ks' \
+ '--extra-args=ks=file:/rhel-8.5.ks console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH' \
+ '--disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-ntvwrorc.img,size=6,format=raw' \
+ '--location=http://download.eng.bos.redhat.com/released/rhel-6-7-8/rhel-8/RHEL-8/8.5.0/BaseOS/x86_64/os' \
+ '--serial=pty' \
+ '--nographics'
+
$TEST_FUNCTIONS
slow_test
skip_if_skipped
-skip_if_backend uml
export XDG_CONFIG_HOME=
export VIRT_BUILDER_DIRS="$abs_builddir/test-config"
output=phony-fedora.img
-format=qcow2
-if [ "$(guestfish get-backend)" = "uml" ]; then
- format=raw
-
- # XXX We specifically want virt-builder to work with the UML
- # backend. However currently it fails with:
- # error: uml backend does not support networking
- # We should be able to make uml have a network backend, but in
- # the meantime add this:
- no_network=--no-network
-fi
-
rm -f $output
# Test as many options as we can!
# on the multi-line parameters. (RHBZ#1420301)
virt-builder phony-fedora \
-v --no-cache --no-check-signature $no_network \
- -o $output --size 2G --format $format \
+ -o $output --size 2G --format qcow2 \
--arch x86_64 \
--hostname test.example.com \
--timezone Europe/London \
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
xzcat) if liblzma was found at build time. If liblzma was not found
at build time, regular C<xzcat> is used which is single-threaded.
-=head3 User-Mode Linux
-
-You can use virt-builder with the User-Mode Linux (UML) backend. This
-may be faster when running virt-builder inside a virtual machine
-(eg. in the cloud).
-
-To enable the UML backend, read the instructions in
-L<guestfs(3)/USER-MODE LINUX BACKEND>.
-
-Currently you have to use the I<--no-network> option. This should be
-fixed in a future version.
-
-The qcow2 output format is not supported by UML. You can only create
-raw-format guests.
-
=head2 SELINUX
Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux)
virt_ls_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
$(LIBXML2_CFLAGS) \
- $(LIBGUESTFS_LIBS)
+ $(LIBGUESTFS_CFLAGS)
virt_ls_LDADD = \
$(top_builddir)/common/options/liboptions.la \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
virt_ls_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
$(LIBXML2_CFLAGS) \
- $(LIBGUESTFS_LIBS)
+ $(LIBGUESTFS_CFLAGS)
virt_ls_LDADD = \
$(top_builddir)/common/options/liboptions.la \
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1 || mps != NULL);
- assert (live == 0);
/* User must specify at least one filename on the command line. */
if (optind >= argc || argc - optind < 1)
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 0);
- assert (live == 0);
/* Must be no extra arguments on the command line. */
if (optind != argc) {
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1);
- assert (live == 0);
/* User must not specify more arguments on the command line. */
if (optind != argc) {
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1 || mps != NULL);
- assert (live == 0);
CHECK_OPTION_format_consumed;
CHECK_OPTION_blocksize_consumed;
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1 || mps != NULL);
- assert (live == 0);
/* User must specify at least one filename on the command line. */
if (optind >= argc || argc - optind < 1) {
-I$(top_srcdir)/lib -I$(top_builddir)/lib \
$(INCLUDE_DIRECTORY)
libedit_la_CFLAGS = \
- $(WARN_CFLAGS) $(WERROR_CFLAGS)
+ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS)
libedit_la_LIBADD = \
$(top_builddir)/common/utils/libutils.la
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
$(INCLUDE_DIRECTORY)
libedit_la_CFLAGS = \
- $(WARN_CFLAGS) $(WERROR_CFLAGS)
+ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS)
libedit_la_LIBADD = \
$(top_builddir)/common/utils/libutils.la
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
CAMLreturn (barv);
}
-/* NB: "noalloc" function. */
+/* NB: [@@noalloc] function. */
value
guestfs_int_mllib_progress_bar_reset (value barv)
{
return Val_unit;
}
-/* NB: "noalloc" function. */
+/* NB: [@@noalloc] function. */
value
guestfs_int_mllib_progress_bar_set (value barv,
value positionv, value totalv)
external progress_bar_init : machine_readable:bool -> progress_bar
= "guestfs_int_mllib_progress_bar_init"
external progress_bar_reset : progress_bar -> unit
- = "guestfs_int_mllib_progress_bar_reset" "noalloc"
+ = "guestfs_int_mllib_progress_bar_reset" [@@noalloc]
external progress_bar_set : progress_bar -> int64 -> int64 -> unit
- = "guestfs_int_mllib_progress_bar_set" "noalloc"
+ = "guestfs_int_mllib_progress_bar_set" [@@noalloc]
let set_up_progress_bar ?(machine_readable = false) (g : Guestfs.guestfs) =
(* Only display progress bars if the machine_readable flag is set or
CONFIGURE_GENERATED_ML = \
guestfs_config.ml
-SOURCES_MLI =
-
-if HAVE_BYTES_COMPAT_ML
-SOURCES_MLI += bytes.mli
-endif
-
-SOURCES_MLI += \
+SOURCES_MLI = \
guestfs_config.mli \
std_utils.mli \
stringMap.mli \
stringSet.mli
-SOURCES_ML =
-
-if HAVE_BYTES_COMPAT_ML
-SOURCES_ML += bytes.ml
-endif
-
-SOURCES_ML += \
+SOURCES_ML = \
$(CONFIGURE_GENERATED_ML) \
stringMap.ml \
stringSet.ml \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
POST_UNINSTALL = :
build_triplet = @build@
host_triplet = @host@
-@HAVE_BYTES_COMPAT_ML_TRUE@am__append_1 = bytes.mli
-@HAVE_BYTES_COMPAT_ML_TRUE@am__append_2 = bytes.ml
-@HAVE_OCAMLOPT_TRUE@am__append_3 = mlstdutils.cmxa
-@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_4 = -package ounit2
+@HAVE_OCAMLOPT_TRUE@am__append_1 = mlstdutils.cmxa
+@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_2 = -package ounit2
TESTS = $(am__EXEEXT_1)
check_PROGRAMS = $(am__EXEEXT_1)
-@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_5 = std_utils_tests
-@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_6 = std_utils_tests
+@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_3 = std_utils_tests
+@HAVE_OCAML_PKG_OUNIT_TRUE@am__append_4 = std_utils_tests
subdir = common/mlstdutils
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
CONFIGURE_GENERATED_ML = \
guestfs_config.ml
-SOURCES_MLI = $(am__append_1) guestfs_config.mli std_utils.mli \
- stringMap.mli stringSet.mli
-SOURCES_ML = $(am__append_2) $(CONFIGURE_GENERATED_ML) stringMap.ml \
- stringSet.ml std_utils.ml
+SOURCES_MLI = \
+ guestfs_config.mli \
+ std_utils.mli \
+ stringMap.mli \
+ stringSet.mli
+
+SOURCES_ML = \
+ $(CONFIGURE_GENERATED_ML) \
+ stringMap.ml \
+ stringSet.ml \
+ std_utils.ml
+
# We pretend that we're building a C library. automake handles the
# compilation of the C sources for us. At the end we take the C
# Just for this library, we need to build both bytecode and native
# code because the generator always requires the bytecode version.
-noinst_DATA = mlstdutils.cma $(am__append_3)
+noinst_DATA = mlstdutils.cma $(am__append_1)
libmlstdutils_a_SOURCES = dummy.c
libmlstdutils_a_CPPFLAGS = \
-I. \
-package str,unix \
-I $(builddir)
-OCAMLPACKAGES_TESTS = $(MLSTDUTILS_CMA) $(am__append_4)
+OCAMLPACKAGES_TESTS = $(MLSTDUTILS_CMA) $(am__append_2)
OCAMLFLAGS = $(OCAML_FLAGS) $(OCAML_WARN_ERROR) -ccopt '$(CFLAGS)'
@HAVE_OCAMLOPT_FALSE@OBJECTS = $(BOBJECTS)
@HAVE_OCAMLOPT_TRUE@OBJECTS = $(XOBJECTS)
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
in
List.rev (loop [] xs)
- (* This is present in OCaml 4.04, so we can remove it when
- * we depend on OCaml >= 4.04.
- *)
- let sort_uniq ?(cmp = Pervasives.compare) xs =
- let xs = List.sort cmp xs in
- let xs = uniq ~cmp xs in
- xs
-
let remove_duplicates xs =
let h = Hashtbl.create (List.length xs) in
let rec loop = function
Bytes.unsafe_set b 7 (Char.unsafe_chr (Int64.to_int c0));
Bytes.to_string b
-type wrap_break_t = WrapEOS | WrapSpace | WrapNL
-
-let rec wrap ?(chan = stdout) ?(indent = 0) str =
- let len = String.length str in
- _wrap chan indent 0 0 len str
-
-and _wrap chan indent column i len str =
- if i < len then (
- let (j, break) = _wrap_find_next_break i len str in
- let next_column =
- if column + (j-i) >= 76 then (
- output_char chan '\n';
- output_spaces chan indent;
- indent + (j-i) + 1
- )
- else column + (j-i) + 1 in
- output chan (Bytes.of_string str) i (j-i);
- match break with
- | WrapEOS -> ()
- | WrapSpace ->
- output_char chan ' ';
- _wrap chan indent next_column (j+1) len str
- | WrapNL ->
- output_char chan '\n';
- output_spaces chan indent;
- _wrap chan indent indent (j+1) len str
- )
-
-and _wrap_find_next_break i len str =
- if i >= len then (len, WrapEOS)
- else if String.unsafe_get str i = ' ' then (i, WrapSpace)
- else if String.unsafe_get str i = '\n' then (i, WrapNL)
- else _wrap_find_next_break (i+1) len str
-
-and output_spaces chan n = for i = 0 to n-1 do output_char chan ' ' done
+let output_spaces chan n = for i = 0 to n-1 do output_char chan ' ' done
let unique = let i = ref 0 in fun () -> incr i; !i
finally ();
match r with Either ret -> ret | Or exn -> raise exn
-type 'a return = { return: 'b. 'a -> 'b } (* OCaml >= 4.03: [@@unboxed] *)
-(* This requires features in OCaml >= 4.04:
+type 'a return = { return: 'b. 'a -> 'b } [@@unboxed]
let with_return (type a) f =
let exception Return of a in
try f {return = fun ret -> raise (Return ret)} with Return ret -> ret
-*)
-
-(* This should work for any version of OCaml, but it doesn't work
- * properly for nested with_return statements. When we can assume
- * OCaml >= 4.04 we should use the above definition instead.
- *)
-let with_return f =
- let ret = ref None in
- try f {return = fun r -> ret := Some r; raise Exit}
- with Exit -> match !ret with None -> assert false | Some r -> r
let failwithf fs = ksprintf failwith fs
(* Program name. *)
let prog = Filename.basename Sys.executable_name
-(* Stores the colours (--colours), quiet (--quiet), trace (-x) and
- * verbose (-v) flags in a global variable.
+(* Stores the colours (--colours), quiet (--quiet), trace (-x), verbose (-v)
+ * and wrap (--wrap) flags in a global variable.
*)
let colours = ref false
let set_colours () = colours := true
let set_verbose () = verbose := true
let verbose () = !verbose
+let wrap = ref false
+let set_wrap () = wrap := true
+let wrap () = !wrap
+
let with_open_in filename f =
let chan = open_in filename in
protect ~f:(fun () -> f chan) ~finally:(fun () -> close_in chan)
| [] -> ""
| app :: xs -> app ^ quote_args xs
-(* Unlink a temporary file on exit. *)
-let unlink_on_exit =
- let files = ref [] in
- let registered_handlers = ref false in
-
- let rec unlink_files () =
- List.iter (
- fun file -> try Unix.unlink file with _ -> ()
- ) !files
- and register_handlers () =
- (* Unlink on exit. *)
- at_exit unlink_files
- in
-
- fun file ->
- files := file :: !files;
- if not !registered_handlers then (
- register_handlers ();
- registered_handlers := true
- )
-
let is_block_device file =
try (Unix.stat file).Unix.st_kind = Unix.S_BLK
with Unix.Unix_error _ -> false
val concat : string -> string list -> string
val contains : string -> char -> bool
val contains_from : string -> int -> char -> bool
- val copy : string -> string
val escaped : string -> string
val get : string -> int -> char
val index : string -> char -> int
val sort : ('a -> 'a -> int) -> 'a list -> 'a list
val stable_sort : ('a -> 'a -> int) -> 'a list -> 'a list
val fast_sort : ('a -> 'a -> int) -> 'a list -> 'a list
+ val sort_uniq : ('a -> 'a -> int) -> 'a list -> 'a list
val merge : ('a -> 'a -> int) -> 'a list -> 'a list -> 'a list
val dropwhile : ('a -> bool) -> 'a list -> 'a list
val uniq : ?cmp:('a -> 'a -> int) -> 'a list -> 'a list
(** Uniquify a list (the list must be sorted first). *)
- val sort_uniq : ?cmp:('a -> 'a -> int) -> 'a list -> 'a list
- (** Sort and uniquify a list. *)
-
val remove_duplicates : 'a list -> 'a list
(** Remove duplicates from an unsorted list; useful when the order
of the elements matter.
On the OCaml side, 64 bit integers are always used so that you
can use the [.^] operators on them for bit manipulation. *)
-val wrap : ?chan:out_channel -> ?indent:int -> string -> unit
-(** Wrap text. *)
-
val output_spaces : out_channel -> int -> unit
(** Write [n] spaces to [out_channel]. *)
case, but requires a lot more work by the caller. Perhaps we
will change this in future.) *)
-type 'a return = { return: 'b. 'a -> 'b } (* OCaml >= 4.03: [@@unboxed] *)
+type 'a return = { return: 'b. 'a -> 'b } [@@unboxed]
val with_return : ('a return -> 'a) -> 'a
(** {v
with_return (fun {return} ->
val trace : unit -> bool
val set_verbose : unit -> unit
val verbose : unit -> bool
-(** Stores the colours ([--colours]), quiet ([--quiet]), trace ([-x]) and
- verbose ([-v]) flags in global variables. *)
+val set_wrap : unit -> unit
+val wrap : unit -> bool
+(** Stores the colours ([--colours]), quiet ([--quiet]), trace ([-x]), verbose
+ ([-v]) and wrap ([--wrap]) flags in global variables. *)
val with_open_in : string -> (in_channel -> 'a) -> 'a
(** [with_open_in filename f] calls function [f] with [filename]
(** Create a "pretty-print" representation of a program invocation
(i.e. executable and its arguments). *)
-val unlink_on_exit : string -> unit
-(** Unlink a temporary file on exit. *)
-
val is_block_device : string -> bool
val is_char_device : string -> bool
val is_directory : string -> bool
| JSON.String s -> s
| _ -> error (f_"the value for the key ‘%s’ is not a string") key
+let object_get_bool key yv =
+ match object_find key yv with
+ | JSON.Bool b -> b
+ | _ -> error (f_"the value for the key ‘%s’ is not a bool") key
+
let object_find_object key yv =
match object_find key yv with
| JSON.Dict _ as o -> o
(** [object_get_string key yv] gets the value of the [key] field as a string
in the [yv] structure *)
+val object_get_bool : string -> JSON.json_t -> bool
+(** [object_get_bool key yv] gets the value of the [key] field as a bool
+ in the [yv] structure *)
+
val object_find_object : string -> JSON.json_t -> JSON.json_t
(** [object_get_object key yv] gets the value of the [key] field as a JSON
value in the [yv] structure.
getopt.mli \
JSON.mli \
JSON_parser.mli \
+ on_exit.mli \
planner.mli \
regedit.mli \
registry.mli \
getopt.ml \
JSON.ml \
tools_utils.ml \
+ on_exit.ml \
URI.ml \
planner.ml \
registry.ml \
../mlpcre/mlpcre.$(MLARCHIVE) \
$(MLTOOLS_CMA) \
$(top_srcdir)/ocaml-link.sh
+tools_utils_tests_OCAMLCLIBS = \
+ -pthread -lpthread \
+ -lutils \
+ $(LIBXML2_LIBS) \
+ -lgnu \
+ $(LIBGUESTFS_LIBS)
tools_utils_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread -lutils $(LIBXML2_LIBS) -lgnu' -- \
+ -cclib '$(tools_utils_tests_OCAMLCLIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(tools_utils_tests_THEOBJECTS) -o $@
../mlpcre/mlpcre.$(MLARCHIVE) \
$(MLTOOLS_CMA) \
$(top_srcdir)/ocaml-link.sh
+getopt_tests_OCAMLCLIBS = \
+ -pthread -lpthread \
+ -lutils \
+ $(LIBXML2_LIBS) \
+ -lgnu \
+ $(LIBGUESTFS_LIBS)
getopt_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread -lutils $(LIBXML2_LIBS) -lgnu' -- \
+ -cclib '$(getopt_tests_OCAMLCLIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(getopt_tests_THEOBJECTS) -o $@
$(top_srcdir)/ocaml-link.sh
JSON_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread' -- \
+ -cclib '-pthread -lpthread $(LIBGUESTFS_LIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(JSON_tests_THEOBJECTS) -o $@
$(top_srcdir)/ocaml-link.sh
JSON_parser_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread $(OCAMLCLIBS)' -- \
+ -cclib '-pthread -lpthread $(OCAMLCLIBS) $(LIBGUESTFS_LIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(JSON_parser_tests_THEOBJECTS) -o $@
$(top_srcdir)/ocaml-link.sh
machine_readable_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread -lutils -lgnu' -- \
+ -cclib '-pthread -lpthread -lutils -lgnu $(LIBGUESTFS_LIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(machine_readable_tests_THEOBJECTS) -o $@
$(top_srcdir)/ocaml-link.sh
tools_messages_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread -lutils -lgnu' -- \
+ -cclib '-pthread -lpthread -lutils -lgnu $(LIBGUESTFS_LIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(tools_messages_tests_THEOBJECTS) -o $@
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
getopt.mli \
JSON.mli \
JSON_parser.mli \
+ on_exit.mli \
planner.mli \
regedit.mli \
registry.mli \
getopt.ml \
JSON.ml \
tools_utils.ml \
+ on_exit.ml \
URI.ml \
planner.ml \
registry.ml \
@HAVE_OCAML_TRUE@ $(MLTOOLS_CMA) \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh
+@HAVE_OCAML_TRUE@tools_utils_tests_OCAMLCLIBS = \
+@HAVE_OCAML_TRUE@ -pthread -lpthread \
+@HAVE_OCAML_TRUE@ -lutils \
+@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ -lgnu \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS)
+
@HAVE_OCAML_TRUE@tools_utils_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils $(LIBXML2_LIBS) -lgnu' -- \
+@HAVE_OCAML_TRUE@ -cclib '$(tools_utils_tests_OCAMLCLIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(tools_utils_tests_THEOBJECTS) -o $@
@HAVE_OCAML_TRUE@ $(MLTOOLS_CMA) \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh
+@HAVE_OCAML_TRUE@getopt_tests_OCAMLCLIBS = \
+@HAVE_OCAML_TRUE@ -pthread -lpthread \
+@HAVE_OCAML_TRUE@ -lutils \
+@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ -lgnu \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS)
+
@HAVE_OCAML_TRUE@getopt_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils $(LIBXML2_LIBS) -lgnu' -- \
+@HAVE_OCAML_TRUE@ -cclib '$(getopt_tests_OCAMLCLIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(getopt_tests_THEOBJECTS) -o $@
@HAVE_OCAML_TRUE@JSON_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread' -- \
+@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread $(LIBGUESTFS_LIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(JSON_tests_THEOBJECTS) -o $@
@HAVE_OCAML_TRUE@JSON_parser_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread $(OCAMLCLIBS)' -- \
+@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread $(OCAMLCLIBS) $(LIBGUESTFS_LIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(JSON_parser_tests_THEOBJECTS) -o $@
@HAVE_OCAML_TRUE@machine_readable_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils -lgnu' -- \
+@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils -lgnu $(LIBGUESTFS_LIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(machine_readable_tests_THEOBJECTS) -o $@
@HAVE_OCAML_TRUE@tools_messages_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils -lgnu' -- \
+@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lutils -lgnu $(LIBGUESTFS_LIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(tools_messages_tests_THEOBJECTS) -o $@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
--- /dev/null
+(* Common way to handle actions on exit.
+ * Copyright (C) 2010-2019 Red Hat Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program 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 General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License along
+ * with this program; if not, write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ *)
+
+open Std_utils
+open Tools_utils
+open Common_gettext.Gettext
+
+open Unix
+open Printf
+
+(* List of files to unlink. *)
+let files = ref []
+
+(* List of directories to remove. *)
+let rmdirs = ref []
+
+(* List of PIDs to kill. *)
+let kills = ref []
+
+(* List of functions to call. *)
+let fns = ref []
+
+(* Perform a single exit action, printing any exception but
+ * otherwise ignoring failures.
+ *)
+let do_action f arg =
+ try f arg with exn -> debug "%s" (Printexc.to_string exn)
+
+(* Make sure the actions are performed only once. *)
+let done_actions = ref false
+
+(* Perform the exit actions. *)
+let do_actions () =
+ if not !done_actions then (
+ List.iter (do_action (fun f -> f ())) !fns;
+ List.iter (do_action (fun (signal, pid) -> kill pid signal)) !kills;
+ List.iter (do_action (fun file -> Unix.unlink file)) !files;
+ List.iter (do_action (
+ fun dir ->
+ let cmd = sprintf "rm -rf %s" (Filename.quote dir) in
+ ignore (Tools_utils.shell_command cmd)
+ )
+ ) !rmdirs;
+ );
+ done_actions := true
+
+(* False until at least one function is called. Avoids registering
+ * the signal and at_exit handlers unnnecessarily.
+ *)
+let registered = ref false
+
+(* Register signal and at_exit handlers. *)
+let register () =
+ if not !registered then (
+ List.iter (
+ fun (signal, name) ->
+ let handler _ =
+ (* Try to get a final message out. This is helpful
+ * when debugging so we can tell if a program was killed
+ * or segfaulted.
+ *)
+ eprintf (f_"%s: Exiting on signal %s\n%!") prog name;
+ (* Do the cleanup actions. *)
+ do_actions ();
+ (* Call _exit instead of exit because the OCaml exit calls
+ * C exit which is probably not safe from a signal handler
+ * especially if we forked.
+ *)
+ Unix_utils.Exit._exit 1
+ in
+ ignore (Sys.signal signal (Sys.Signal_handle handler))
+ ) [ Sys.sigint, "SIGINT";
+ Sys.sigquit, "SIGQUIT";
+ Sys.sigterm, "SIGTERM";
+ Sys.sighup, "SIGHUP" ];
+
+ (* Register the at_exit handler. *)
+ at_exit do_actions
+ );
+ registered := true
+
+let f fn =
+ register ();
+ List.push_front fn fns
+
+let unlink filename =
+ register ();
+ List.push_front filename files
+
+let rmdir dir =
+ register ();
+ List.push_front dir rmdirs
+
+let kill ?(signal = Sys.sigterm) pid =
+ register ();
+ List.push_front (signal, pid) kills
--- /dev/null
+(* Common way to handle actions on exit.
+ * Copyright (C) 2010-2021 Red Hat Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program 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 General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License along
+ * with this program; if not, write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ *)
+
+(** This module allows you to register actions which
+ are mostly guaranteed to happen when the process
+ exits, even if it exits with a signal. Note that
+ segfaults, kill -9, etc. will not run these actions.
+
+ The main problem with the {!Stdlib.at_exit} function
+ is that it is not called if the program exits with
+ a signal. A lesser problem is that it's hard to
+ use for common cases such as deleting a temp file or
+ killing another process, so we provide simple
+ wrappers for those common actions here.
+
+ Note this module registers signal handlers for
+ SIGINT, SIGQUIT, SIGTERM and SIGHUP. This means
+ that any program that links with mltools.cmxa
+ will automatically have signal handlers pointing
+ to an internal function within this module. To
+ register your own signal handler function to be
+ called instead, you have to call {!register}
+ before using the ordinary {!Sys.signal} functions.
+ Your cleanup action might no longer run unless the
+ program calls {!Stdlib.exit}. *)
+
+val f : (unit -> unit) -> unit
+(** Register a function [f] which runs when the program exits.
+ Similar to [Stdlib.at_exit] but also runs if the program is
+ killed with a signal that we can catch. *)
+
+val unlink : string -> unit
+(** Unlink a single temporary file on exit. *)
+
+val rmdir : string -> unit
+(** Recursively remove a temporary directory on exit (using [rm -rf]). *)
+
+val kill : ?signal:int -> int -> unit
+(** Kill [PID] on exit. The signal sent defaults to [Sys.sigterm].
+
+ Use this with care since you can end up unintentionally killing
+ another process if [PID] goes away or doesn't exist before the
+ program exits. *)
+
+val register : unit -> unit
+(** Force this module to register its at_exit function and signal
+ handlers now. You do {!i not} normally need to call this.
+ Calling the functions above implicitly calls register. However
+ you might need to call it if you want to register your own
+ signal handler. See above description for why and use with care.
+ Note that this is safe if at_exit and signal handlers have
+ already been registered - it does nothing in that case. *)
$t --help | grep -F -- '-o, --optstr[=string]'
# --version
-$t --version | grep '^getopt_tests 1\.'
+$t --version | grep '^getopt_tests [12]\.'
# --short-options
$t --short-options | grep '^-a'
$t --long-options | grep '^--is'
$t --long-options | grep '^--version'
$t --long-options | grep '^--verbose'
+$t --long-options | grep '^--wrap'
# -a/--add parameter.
$t | grep '^adds = \[\]'
CAMLreturn (Val_unit);
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_set_echo_keys (value unitv)
{
return Val_unit;
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_set_keys_from_stdin (value unitv)
{
open Common_gettext.Gettext
open Getopt.OptionName
+(* For this file only, create a reference to prog so that the
+ * --program-name option can change the program name in error
+ * messages.
+ *)
+let prog = ref prog
+
type key_store = {
keys : (string, key_store_key) Hashtbl.t;
}
| KeyFileName of string
external c_inspect_decrypt : Guestfs.t -> int64 -> (string * key_store_key) list -> unit = "guestfs_int_mllib_inspect_decrypt"
-external c_set_echo_keys : unit -> unit = "guestfs_int_mllib_set_echo_keys" "noalloc"
-external c_set_keys_from_stdin : unit -> unit = "guestfs_int_mllib_set_keys_from_stdin" "noalloc"
+external c_set_echo_keys : unit -> unit = "guestfs_int_mllib_set_echo_keys" [@@noalloc]
+external c_set_keys_from_stdin : unit -> unit = "guestfs_int_mllib_set_keys_from_stdin" [@@noalloc]
external c_rfc3339_date_time_string : unit -> string = "guestfs_int_mllib_rfc3339_date_time_string"
type machine_readable_fn = {
in
ksprintf display fs
+(* Wrap text. *)
+type wrap_break_t = WrapEOS | WrapSpace | WrapNL
+
+let rec wrap ?(chan = stdout) ?(indent = 0) str =
+ if Std_utils.wrap () || istty chan then
+ let len = String.length str in
+ _wrap chan indent 0 0 len str
+ else (
+ output_spaces chan indent;
+ output_string chan str
+ )
+
+and _wrap chan indent column i len str =
+ if i < len then (
+ let (j, break) = _wrap_find_next_break i len str in
+ let next_column =
+ if column + (j-i) >= 76 then (
+ output_char chan '\n';
+ output_spaces chan indent;
+ indent + (j-i) + 1
+ )
+ else column + (j-i) + 1 in
+ output chan (Bytes.of_string str) i (j-i);
+ match break with
+ | WrapEOS -> ()
+ | WrapSpace ->
+ output_char chan ' ';
+ _wrap chan indent next_column (j+1) len str
+ | WrapNL ->
+ output_char chan '\n';
+ output_spaces chan indent;
+ _wrap chan indent indent (j+1) len str
+ )
+
+and _wrap_find_next_break i len str =
+ if i >= len then (len, WrapEOS)
+ else if String.unsafe_get str i = ' ' then (i, WrapSpace)
+ else if String.unsafe_get str i = '\n' then (i, WrapNL)
+ else _wrap_find_next_break (i+1) len str
+
(* Error messages etc. *)
let error ?(exit_code = 1) fs =
let display str =
log_as_json "error" str;
let chan = stderr in
ansi_red ~chan ();
- wrap ~chan (sprintf (f_"%s: error: %s") prog str);
+ wrap ~chan (sprintf (f_"%s: error: %s") !prog str);
if not (verbose () && trace ()) then (
prerr_newline ();
prerr_newline ();
wrap ~chan
(sprintf (f_"If reporting bugs, run %s with debugging enabled and include the complete output:\n\n %s -v -x [...]")
- prog prog);
+ !prog !prog);
);
ansi_restore ~chan ();
prerr_newline ();
log_as_json "warning" str;
let chan = stdout in
ansi_blue ~chan ();
- wrap ~chan (sprintf (f_"%s: warning: %s") prog str);
+ wrap ~chan (sprintf (f_"%s: warning: %s") !prog str);
ansi_restore ~chan ();
print_newline ();
in
log_as_json "info" str;
let chan = stdout in
ansi_magenta ~chan ();
- wrap ~chan (sprintf (f_"%s: %s") prog str);
+ wrap ~chan (sprintf (f_"%s: %s") !prog str);
ansi_restore ~chan ();
print_newline ();
in
* (e.g. debug, tracing) already set.
*)
let open_guestfs ?identifier () =
- let g = new Guestfs.guestfs () in
+ let g = new Guestfs.guestfs ~environment:false () in
+ g#parse_environment ();
if trace () then g#set_trace true;
if verbose () then g#set_verbose true;
Option.may g#set_identifier identifier;
* the OCaml tools.
*)
let print_version_and_exit () =
- printf "%s %s\n%!" prog Guestfs_config.package_version_full;
+ printf "%s %s\n%!" !prog Guestfs_config.package_version_full;
exit 0
let generated_by =
- sprintf (f_"generated by %s %s") prog Guestfs_config.package_version_full
+ sprintf (f_"generated by %s %s") !prog Guestfs_config.package_version_full
let virt_tools_data_dir =
let dir = lazy (
type cmdline_options = {
getopt : Getopt.t;
ks : key_store;
+ debug_gc : bool ref;
}
-let create_standard_options argspec ?anon_fun ?(key_opts = false) ?(machine_readable = false) usage_msg =
- (** Install an exit hook to check gc consistency for --debug-gc *)
- let set_debug_gc () =
- at_exit (fun () -> Gc.compact()) in
+let create_standard_options argspec ?anon_fun ?(key_opts = false)
+ ?(machine_readable = false) ?(program_name = false) usage_msg =
+ (* Install an exit hook to check gc consistency for --debug-gc *)
+ let debug_gc = ref false in
+ let set_debug_gc () = at_exit Gc.compact; debug_gc := true in
+
let parse_machine_readable = function
| None ->
machine_readable_output := Channel stdout
let ks = {
keys = Hashtbl.create 13;
} in
- let argspec = [
- [ S 'V'; L"version" ], Getopt.Unit print_version_and_exit, s_"Display version and exit";
- [ S 'v'; L"verbose" ], Getopt.Unit set_verbose, s_"Enable libguestfs debugging messages";
- [ S 'x' ], Getopt.Unit set_trace, s_"Enable tracing of libguestfs calls";
- [ L"debug-gc" ], Getopt.Unit set_debug_gc, Getopt.hidden_option_description;
- [ S 'q'; L"quiet" ], Getopt.Unit set_quiet, s_"Don’t print progress messages";
- [ L"color"; L"colors";
- L"colour"; L"colours" ], Getopt.Unit set_colours, s_"Use ANSI colour sequences even if not tty";
- ] @ argspec in
- let argspec =
- argspec @
- (if key_opts then
- let parse_key_selector arg =
- let parts = String.nsplit ~max:3 ":" arg in
- match parts with
- | [ device; "key"; key ] ->
- Hashtbl.replace ks.keys device (KeyString key)
- | [ device; "file"; file ] ->
- Hashtbl.replace ks.keys device (KeyFileName file)
- | _ ->
- error (f_"invalid selector string for --key: %s") arg
- in
- [
- [ L"echo-keys" ], Getopt.Unit c_set_echo_keys, s_"Don’t turn off echo for passphrases";
- [ L"keys-from-stdin" ], Getopt.Unit c_set_keys_from_stdin, s_"Read passphrases from stdin";
- [ L"key" ], Getopt.String (s_"SELECTOR", parse_key_selector), s_"Specify a LUKS key";
- ]
- else []) @
- (if machine_readable then
- [
- [ L"machine-readable" ], Getopt.OptString ("format", parse_machine_readable), s_"Make output machine readable";
- ]
- else []) in
+ let argspec = ref argspec in
+ let add_argspec = List.push_back argspec in
+
+ add_argspec ([ S 'V'; L"version" ], Getopt.Unit print_version_and_exit, s_"Display version and exit");
+ add_argspec ([ S 'v'; L"verbose" ], Getopt.Unit set_verbose, s_"Enable libguestfs debugging messages");
+ add_argspec ([ S 'x' ], Getopt.Unit set_trace, s_"Enable tracing of libguestfs calls");
+ add_argspec ([ L"debug-gc" ], Getopt.Unit set_debug_gc, Getopt.hidden_option_description);
+ add_argspec ([ S 'q'; L"quiet" ], Getopt.Unit set_quiet, s_"Don’t print progress messages");
+ add_argspec ([ L"color"; L"colors";
+ L"colour"; L"colours" ], Getopt.Unit set_colours, s_"Use ANSI colour sequences even if not tty");
+ add_argspec ([ L"wrap" ], Getopt.Unit set_wrap, s_"Wrap log messages even if not tty");
+
+ if key_opts then (
+ let parse_key_selector arg =
+ let parts = String.nsplit ~max:3 ":" arg in
+ match parts with
+ | [ device; "key"; key ] ->
+ Hashtbl.replace ks.keys device (KeyString key)
+ | [ device; "file"; file ] ->
+ Hashtbl.replace ks.keys device (KeyFileName file)
+ | _ ->
+ error (f_"invalid selector string for --key: %s") arg
+ in
+
+ add_argspec ([ L"echo-keys" ], Getopt.Unit c_set_echo_keys, s_"Don’t turn off echo for passphrases");
+ add_argspec ([ L"keys-from-stdin" ], Getopt.Unit c_set_keys_from_stdin, s_"Read passphrases from stdin");
+ add_argspec ([ L"key" ], Getopt.String (s_"SELECTOR", parse_key_selector), s_"Specify a LUKS key");
+ );
+
+ if machine_readable then (
+ add_argspec ([ L"machine-readable" ], Getopt.OptString ("format", parse_machine_readable), s_"Make output machine readable");
+ );
+
+ if program_name then (
+ add_argspec ([ L"program-name" ], Getopt.Set_string ("prog", prog), s_"Set program name");
+ );
+
+ let argspec = !argspec in
+
let getopt = Getopt.create argspec ?anon_fun usage_msg in
- {
- getopt; ks;
- }
+ { getopt; ks; debug_gc }
+
+let key_store_to_cli { keys } =
+ Hashtbl.fold (
+ fun k v acc ->
+ let arg =
+ match v with
+ | KeyString s -> sprintf "%s:key:%s" k s
+ | KeyFileName f -> sprintf "%s:file:%s" k f in
+ "--key" :: arg :: acc
+ ) keys []
(* Run an external command, slurp up the output as a list of lines. *)
let external_command ?(echo_cmd = true) cmd =
if String.length uuid < 10 then assert false; (* sanity check on uuidgen *)
uuid
-(* Remove a temporary directory on exit. *)
-let rmdir_on_exit =
- let dirs = ref [] in
- let registered_handlers = ref false in
-
- let rec rmdirs () =
- List.iter (
- fun dir ->
- let cmd = sprintf "rm -rf %s" (Filename.quote dir) in
- ignore (shell_command cmd)
- ) !dirs
- and register_handlers () =
- (* Remove on exit. *)
- at_exit rmdirs
- in
-
- fun dir ->
- dirs := dir :: !dirs;
- if not !registered_handlers then (
- register_handlers ();
- registered_handlers := true
- )
-
(* Using the libguestfs API, recursively remove only files from the
* given directory. Useful for cleaning /var/cache etc in sysprep
* without removing the actual directory structure. Also if 'dir' is
flush stderr
with
- Guestfs.Error msg -> eprintf "%s: augeas: %s (ignored)\n" prog msg
+ Guestfs.Error msg -> eprintf "%s: augeas: %s (ignored)\n" !prog msg
)
(* Detect type of a file. *)
type cmdline_options = {
getopt : Getopt.t; (** The actual {!Getopt} handle. *)
ks : key_store; (** Container for keys read via [--key]. *)
+ debug_gc : bool ref; (** True if [--debug-gc] was used. *)
}
(** Structure representing all the data needed for handling command
line options. *)
-val create_standard_options : Getopt.speclist -> ?anon_fun:Getopt.anon_fun -> ?key_opts:bool -> ?machine_readable:bool -> Getopt.usage_msg -> cmdline_options
+val create_standard_options : Getopt.speclist -> ?anon_fun:Getopt.anon_fun -> ?key_opts:bool -> ?machine_readable:bool -> ?program_name:bool -> Getopt.usage_msg -> cmdline_options
(** Adds the standard libguestfs command line options to the specified ones,
sorting them, and setting [long_options] to them.
[machine_readable] specifies whether add the [--machine-readable]
option.
+ [program_name] specifies whether to add the [--program-name] option
+ which allows another tool to run this tool and change the program
+ name used in error messages.
+
Returns a new {!cmdline_options} structure. *)
+val key_store_to_cli : key_store -> string list
+(** Convert a {!key_store} object back to a list of command line
+ options, essentially undoing the effect of Getopt parsing.
+ This is used in virt-v2v to pass the keystore to helpers.
+ It is not particularly secure, especially if you use the
+ [:key:] selector, although not any less secure than passing
+ them via the command line in the first place. *)
+
val external_command : ?echo_cmd:bool -> string -> string list
(** Run an external command, slurp up the output as a list of lines.
val uuidgen : unit -> string
(** Run uuidgen to return a random UUID. *)
-val rmdir_on_exit : string -> unit
-(** Remove a temporary directory on exit (using [rm -rf]). *)
-
val rm_rf_only_files : Guestfs.guestfs -> ?filter:(string -> bool) -> string -> unit
(** Using the libguestfs API, recursively remove only files from the
given directory. Useful for cleaning [/var/cache] etc in sysprep
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
external shell_unquote : string -> string = "guestfs_int_mlutils_shell_unquote"
-external is_reg : int64 -> bool = "guestfs_int_mlutils_is_reg" "noalloc"
-external is_dir : int64 -> bool = "guestfs_int_mlutils_is_dir" "noalloc"
-external is_chr : int64 -> bool = "guestfs_int_mlutils_is_chr" "noalloc"
-external is_blk : int64 -> bool = "guestfs_int_mlutils_is_blk" "noalloc"
-external is_fifo : int64 -> bool = "guestfs_int_mlutils_is_fifo" "noalloc"
-external is_lnk : int64 -> bool = "guestfs_int_mlutils_is_lnk" "noalloc"
-external is_sock : int64 -> bool = "guestfs_int_mlutils_is_sock" "noalloc"
+external is_reg : int64 -> bool = "guestfs_int_mlutils_is_reg" [@@noalloc]
+external is_dir : int64 -> bool = "guestfs_int_mlutils_is_dir" [@@noalloc]
+external is_chr : int64 -> bool = "guestfs_int_mlutils_is_chr" [@@noalloc]
+external is_blk : int64 -> bool = "guestfs_int_mlutils_is_blk" [@@noalloc]
+external is_fifo : int64 -> bool = "guestfs_int_mlutils_is_fifo" [@@noalloc]
+external is_lnk : int64 -> bool = "guestfs_int_mlutils_is_lnk" [@@noalloc]
+external is_sock : int64 -> bool = "guestfs_int_mlutils_is_sock" [@@noalloc]
external full_path : string -> string option -> string = "guestfs_int_mlutils_full_path"
extern value guestfs_int_mllib_statvfs_is_network_filesystem (value pathv);
extern value guestfs_int_mllib_sysconf_nr_processors_online (value unitv);
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_dev_t_makedev (value majv, value minv)
{
return Val_int (makedev (Int_val (majv), Int_val (minv)));
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_dev_t_major (value devv)
{
return Val_int (major (Int_val (devv)));
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_dev_t_minor (value devv)
{
return Val_int (minor (Int_val (devv)));
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_unsetenv (value strv)
{
return Val_unit;
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
int
guestfs_int_mllib_exit (value rv)
{
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_sync (value unitv)
{
CAMLreturn (rv);
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_statvfs_is_network_filesystem (value pathv)
{
#endif
}
-/* NB: This is a "noalloc" call. */
+/* NB: This is a [@@noalloc] call. */
value
guestfs_int_mllib_sysconf_nr_processors_online (value unitv)
{
open Std_utils
module Dev_t = struct
- external makedev : int -> int -> int = "guestfs_int_mllib_dev_t_makedev" "noalloc"
- external major : int -> int = "guestfs_int_mllib_dev_t_major" "noalloc"
- external minor : int -> int = "guestfs_int_mllib_dev_t_minor" "noalloc"
+ external makedev : int -> int -> int = "guestfs_int_mllib_dev_t_makedev" [@@noalloc]
+ external major : int -> int = "guestfs_int_mllib_dev_t_major" [@@noalloc]
+ external minor : int -> int = "guestfs_int_mllib_dev_t_minor" [@@noalloc]
end
module Env = struct
- external unsetenv : string -> unit = "guestfs_int_mllib_unsetenv" "noalloc"
+ external unsetenv : string -> unit = "guestfs_int_mllib_unsetenv" [@@noalloc]
end
module Exit = struct
- external _exit : int -> 'a = "guestfs_int_mllib_exit" "noalloc"
+ external _exit : int -> 'a = "guestfs_int_mllib_exit" [@@noalloc]
end
module Fnmatch = struct
end
module Fsync = struct
- external sync : unit -> unit = "guestfs_int_mllib_sync" "noalloc"
+ external sync : unit -> unit = "guestfs_int_mllib_sync" [@@noalloc]
external file : string -> unit = "guestfs_int_mllib_fsync_file"
end
let free_space { f_bsize = bsize; f_bavail = bavail } = bsize *^ bavail
external is_network_filesystem : string -> bool =
- "guestfs_int_mllib_statvfs_is_network_filesystem" "noalloc"
+ "guestfs_int_mllib_statvfs_is_network_filesystem" [@@noalloc]
end
module Sysconf = struct
external nr_processors_online : unit -> int =
- "guestfs_int_mllib_sysconf_nr_processors_online" "noalloc"
+ "guestfs_int_mllib_sysconf_nr_processors_online" [@@noalloc]
end
-I$(top_srcdir)/common/visit
libmlvisit_a_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBVIRT_CFLAGS) $(LIBXML2_CFLAGS) \
-fPIC
../mlutils/mlcutils.$(MLARCHIVE) \
$(MLVISIT_CMA) \
$(top_srcdir)/ocaml-link.sh
+visit_tests_OCAMLCLIBS = \
+ -pthread -lpthread \
+ -lvisit \
+ -lstructs \
+ -lutils \
+ $(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS)
visit_tests_LINK = \
$(top_srcdir)/ocaml-link.sh \
- -cclib '-pthread -lpthread -lvisit -lstructs -lutils $(LIBXML2_LIBS)' -- \
+ -cclib '$(visit_tests_OCAMLCLIBS)' -- \
$(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
$(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
$(visit_tests_THEOBJECTS) -o $@
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@libmlvisit_a_CFLAGS = \
@HAVE_OCAML_TRUE@ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBVIRT_CFLAGS) $(LIBXML2_CFLAGS) \
@HAVE_OCAML_TRUE@ -fPIC
@HAVE_OCAML_TRUE@ $(MLVISIT_CMA) \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh
+@HAVE_OCAML_TRUE@visit_tests_OCAMLCLIBS = \
+@HAVE_OCAML_TRUE@ -pthread -lpthread \
+@HAVE_OCAML_TRUE@ -lvisit \
+@HAVE_OCAML_TRUE@ -lstructs \
+@HAVE_OCAML_TRUE@ -lutils \
+@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS)
+
@HAVE_OCAML_TRUE@visit_tests_LINK = \
@HAVE_OCAML_TRUE@ $(top_srcdir)/ocaml-link.sh \
-@HAVE_OCAML_TRUE@ -cclib '-pthread -lpthread -lvisit -lstructs -lutils $(LIBXML2_LIBS)' -- \
+@HAVE_OCAML_TRUE@ -cclib '$(visit_tests_OCAMLCLIBS)' -- \
@HAVE_OCAML_TRUE@ $(OCAMLFIND) $(BEST) $(OCAMLFLAGS) $(OCAMLLINKFLAGS) \
@HAVE_OCAML_TRUE@ $(OCAMLPACKAGES) $(OCAMLPACKAGES_TESTS) \
@HAVE_OCAML_TRUE@ $(visit_tests_THEOBJECTS) -o $@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
#include <libintl.h>
#include <error.h>
#include <assert.h>
+#include <errno.h>
#include "c-ctype.h"
#include "options.h"
+static void
+append_char (size_t *idx, char *buffer, char c)
+{
+ /* bail out if the size of the string (including the terminating NUL, if any
+ * cannot be expressed as a size_t
+ */
+ if (*idx == (size_t)-1)
+ error (EXIT_FAILURE, 0, _("string size overflow"));
+
+ /* if we're not just counting, then actually write the character */
+ if (buffer != NULL)
+ buffer[*idx] = c;
+
+ /* advance */
+ ++*idx;
+}
+
/**
- * Make a LUKS map name from the partition name,
- * eg. C<"/dev/vda2" =E<gt> "cryptvda2">
+ * Make a LUKS map name from the partition or logical volume name, eg.
+ * C<"/dev/vda2" =E<gt> "cryptvda2">, or C<"/dev/vg-ssd/lv-root7" =E<gt>
+ * "cryptvgssdlvroot7">. Note that, in logical volume device names,
+ * c_isalnum() eliminates the "/" separator from between the VG and the LV, so
+ * this mapping is not unique; but for our purposes, it will do.
*/
-static void
-make_mapname (const char *device, char *mapname, size_t len)
+static char *
+make_mapname (const char *device)
{
- size_t i = 0;
+ bool strip_iprefix;
+ static const char iprefix[] = "/dev/";
+ char *mapname;
+ enum { COUNT, WRITE, DONE } mode;
+
+ strip_iprefix = STRPREFIX (device, iprefix);
+
+ /* set to NULL in COUNT mode, flipped to non-NULL for WRITE mode */
+ mapname = NULL;
+
+ for (mode = COUNT; mode < DONE; ++mode) {
+ size_t ipos;
+ static const size_t iprefixlen = sizeof iprefix - 1;
+ size_t opos;
+ static const char oprefix[] = "crypt";
+ static const size_t oprefixlen = sizeof oprefix - 1;
+ char ichar;
+
+ /* skip the input prefix, if any */
+ ipos = strip_iprefix ? iprefixlen : 0;
+ /* start producing characters after the output prefix */
+ opos = oprefixlen;
+
+ /* filter & copy */
+ while ((ichar = device[ipos]) != '\0') {
+ if (c_isalnum (ichar))
+ append_char (&opos, mapname, ichar);
+ ++ipos;
+ }
+
+ /* terminate */
+ append_char (&opos, mapname, '\0');
- if (len < 6)
- abort ();
- strcpy (mapname, "crypt");
- mapname += 5;
- len -= 5;
+ /* allocate the output buffer when flipping from COUNT to WRITE mode */
+ if (mode == COUNT) {
+ assert (opos >= sizeof oprefix);
+ mapname = malloc (opos);
+ if (mapname == NULL)
+ error (EXIT_FAILURE, errno, "malloc");
- if (STRPREFIX (device, "/dev/"))
- i = 5;
+ /* populate the output prefix -- note: not NUL-terminated yet */
+ memcpy (mapname, oprefix, oprefixlen);
+ }
+ }
+
+ return mapname;
+}
- for (; device[i] != '\0' && len >= 1; ++i) {
- if (c_isalnum (device[i])) {
- *mapname++ = device[i];
- len--;
+static bool
+decrypt_mountables (guestfs_h *g, const char * const *mountables,
+ struct key_store *ks, bool name_decrypted_by_uuid)
+{
+ bool decrypted_some = false;
+ const char * const *mnt_scan = mountables;
+ const char *mountable;
+
+ while ((mountable = *mnt_scan++) != NULL) {
+ CLEANUP_FREE char *type = NULL;
+ CLEANUP_FREE char *uuid = NULL;
+ CLEANUP_FREE_STRING_LIST char **keys = NULL;
+ CLEANUP_FREE char *mapname = NULL;
+ const char * const *key_scan;
+ const char *key;
+
+ type = guestfs_vfs_type (g, mountable);
+ if (type == NULL)
+ continue;
+
+ /* "cryptsetup luksUUID" cannot read a UUID on Windows BitLocker disks
+ * (unclear if this is a limitation of the format or cryptsetup).
+ */
+ if (STREQ (type, "crypto_LUKS")) {
+ uuid = guestfs_luks_uuid (g, mountable);
+ } else if (STRNEQ (type, "BitLocker"))
+ continue;
+
+ /* Grab the keys that we should try with this device, based on device name,
+ * or UUID (if any).
+ */
+ keys = get_keys (ks, mountable, uuid);
+ assert (keys[0] != NULL);
+
+ /* Generate a node name for the plaintext (decrypted) device node. */
+ if (!name_decrypted_by_uuid || uuid == NULL ||
+ asprintf (&mapname, "luks-%s", uuid) == -1)
+ mapname = make_mapname (mountable);
+
+ /* Try each key in turn. */
+ key_scan = (const char * const *)keys;
+ while ((key = *key_scan++) != NULL) {
+ int r;
+
+ guestfs_push_error_handler (g, NULL, NULL);
+ r = guestfs_cryptsetup_open (g, mountable, key, mapname, -1);
+ guestfs_pop_error_handler (g);
+
+ if (r == 0)
+ break;
}
+
+ if (key == NULL)
+ error (EXIT_FAILURE, 0,
+ _("could not find key to open LUKS encrypted %s.\n\n"
+ "Try using --key on the command line.\n\n"
+ "Original error: %s (%d)"),
+ mountable, guestfs_last_error (g), guestfs_last_errno (g));
+
+ decrypted_some = true;
}
- *mapname = '\0';
+ return decrypted_some;
}
/**
inspect_do_decrypt (guestfs_h *g, struct key_store *ks)
{
CLEANUP_FREE_STRING_LIST char **partitions = guestfs_list_partitions (g);
+ CLEANUP_FREE_STRING_LIST char **lvs = NULL;
+ bool need_rescan;
+
if (partitions == NULL)
exit (EXIT_FAILURE);
- int need_rescan = 0, r;
- size_t i, j;
-
- for (i = 0; partitions[i] != NULL; ++i) {
- CLEANUP_FREE char *type = guestfs_vfs_type (g, partitions[i]);
- if (type &&
- (STREQ (type, "crypto_LUKS") || STREQ (type, "BitLocker"))) {
- bool is_bitlocker = STREQ (type, "BitLocker");
- char mapname[32];
- make_mapname (partitions[i], mapname, sizeof mapname);
-
-#ifdef GUESTFS_HAVE_LUKS_UUID
- CLEANUP_FREE char *uuid = NULL;
-
- /* This fails for Windows BitLocker disks because cryptsetup
- * luksUUID cannot read a UUID (unclear if this is a limitation
- * of the format or cryptsetup).
- */
- if (!is_bitlocker)
- uuid = guestfs_luks_uuid (g, partitions[i]);
-#else
- const char *uuid = NULL;
-#endif
-
- CLEANUP_FREE_STRING_LIST char **keys = get_keys (ks, partitions[i], uuid);
- assert (guestfs_int_count_strings (keys) > 0);
-
- /* Try each key in turn. */
- for (j = 0; keys[j] != NULL; ++j) {
- /* XXX Should we set GUESTFS_CRYPTSETUP_OPEN_READONLY if readonly
- * is set? This might break 'mount_ro'.
- */
- guestfs_push_error_handler (g, NULL, NULL);
-#ifdef GUESTFS_HAVE_CRYPTSETUP_OPEN
- r = guestfs_cryptsetup_open (g, partitions[i], keys[j], mapname, -1);
-#else
- r = guestfs_luks_open (g, partitions[i], keys[j], mapname);
-#endif
- guestfs_pop_error_handler (g);
- if (r == 0)
- goto opened;
- }
- error (EXIT_FAILURE, 0,
- _("could not find key to open LUKS encrypted %s.\n\n"
- "Try using --key on the command line.\n\n"
- "Original error: %s (%d)"),
- partitions[i], guestfs_last_error (g),
- guestfs_last_errno (g));
-
- opened:
- need_rescan = 1;
- }
- }
+ need_rescan = decrypt_mountables (g, (const char * const *)partitions, ks,
+ false);
if (need_rescan) {
if (guestfs_lvm_scan (g, 1) == -1)
exit (EXIT_FAILURE);
}
+
+ lvs = guestfs_lvs (g);
+ if (lvs == NULL)
+ exit (EXIT_FAILURE);
+ decrypt_mountables (g, (const char * const *)lvs, ks, true);
}
optargs.bitmask |= GUESTFS_ADD_DOMAIN_READONLY_BITMASK;
optargs.readonly = 1;
}
- if (live) {
- optargs.bitmask |= GUESTFS_ADD_DOMAIN_LIVE_BITMASK;
- optargs.live = 1;
- }
optargs.bitmask |= GUESTFS_ADD_DOMAIN_ALLOWUUID_BITMASK;
optargs.allowuuid = 1;
void
inspect_mount_handle (guestfs_h *g, struct key_store *ks)
{
- if (live)
- error (EXIT_FAILURE, 0, _("don’t use --live and -i options together"));
-
inspect_do_decrypt (g, ks);
char **roots = guestfs_inspect_os (g);
/* Provided by guestfish or guestmount. */
extern guestfs_h *g;
extern int read_only;
-extern int live;
extern int verbose;
extern int inspector;
extern int keys_from_stdin;
libparallel_la_CFLAGS = \
-pthread \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBXML2_CFLAGS) \
$(LIBVIRT_CFLAGS)
libparallel_la_LIBADD = \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
libparallel_la_CFLAGS = \
-pthread \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBXML2_CFLAGS) \
$(LIBVIRT_CFLAGS)
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
$(INCLUDE_DIRECTORY)
libprogress_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBTINFO_CFLAGS)
libprogress_la_LIBADD = \
$(top_builddir)/common/utils/libutils.la \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
libprogress_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBTINFO_CFLAGS)
libprogress_la_LIBADD = \
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
$(INCLUDE_DIRECTORY)
libstructs_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(GCC_VISIBILITY_HIDDEN)
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
libstructs_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(GCC_VISIBILITY_HIDDEN)
all: $(BUILT_SOURCES)
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
installdirs:
install: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) install-am
-install-exec: install-exec-am
+install-exec: $(BUILT_SOURCES)
+ $(MAKE) $(AM_MAKEFLAGS) install-exec-am
install-data: install-data-am
uninstall: uninstall-am
uninstall-am:
-.MAKE: all check install install-am install-strip
+.MAKE: all check install install-am install-exec install-strip
.PHONY: CTAGS GTAGS TAGS all all-am am--depfiles check check-am clean \
clean-generic clean-libtool clean-noinstLTLIBRARIES \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
extern int guestfs_int_is_sock (int64_t mode);
extern char *guestfs_int_full_path (const char *dir, const char *name);
extern void guestfs_int_hexdump (const void *data, size_t len, FILE *fp);
+extern const char *guestfs_int_strerror (int errnum, char *buf, size_t buflen);
/* Not all language bindings know how to deal with Pointer arguments.
* Those that don't will use this macro which complains noisily and
fprintf (fp, "|\n");
}
}
+
+/**
+ * Thread-safe strerror_r.
+ *
+ * This is a wrapper around the two variants of L<strerror_r(3)>
+ * in glibc since it is hard to use correctly (RHBZ#2030396).
+ *
+ * The buffer passed in should be large enough to store the
+ * error message (256 chars at least) and should be non-static.
+ * Note that the buffer might not be used, use the return value.
+ */
+const char *
+guestfs_int_strerror (int errnum, char *buf, size_t buflen)
+{
+#ifdef _GNU_SOURCE
+ /* GNU strerror_r */
+ return strerror_r (errnum, buf, buflen);
+#else
+ /* XSI-compliant strerror_r */
+ int err = strerror_r (errnum, buf, buflen);
+ if (err > 0)
+ snprintf (buf, buflen, "error number %d", errnum);
+ return buf;
+#endif
+}
-I$(top_srcdir)/common/structs -I$(top_builddir)/common/structs
libvisit_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(GCC_VISIBILITY_HIDDEN)
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
libvisit_la_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(GCC_VISIBILITY_HIDDEN)
all: all-am
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-I$(top_srcdir)/lib -I$(top_builddir)/lib \
$(INCLUDE_DIRECTORY)
libwindows_la_CFLAGS = \
- $(WARN_CFLAGS) $(WERROR_CFLAGS)
+ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS)
libwindows_la_LIBADD = \
$(top_builddir)/common/utils/libutils.la \
$(LTLIBINTL)
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
$(INCLUDE_DIRECTORY)
libwindows_la_CFLAGS = \
- $(WARN_CFLAGS) $(WERROR_CFLAGS)
+ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS)
libwindows_la_LIBADD = \
$(top_builddir)/common/utils/libutils.la \
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.71 for guestfs-tools 1.46.1.
+# Generated by GNU Autoconf 2.71 for guestfs-tools 1.48.0.
#
#
# Copyright (C) 1992-1996, 1998-2017, 2020-2021 Free Software Foundation,
# Identity of this package.
PACKAGE_NAME='guestfs-tools'
PACKAGE_TARNAME='guestfs-tools'
-PACKAGE_VERSION='1.46.1'
-PACKAGE_STRING='guestfs-tools 1.46.1'
+PACKAGE_VERSION='1.48.0'
+PACKAGE_STRING='guestfs-tools 1.48.0'
PACKAGE_BUGREPORT=''
PACKAGE_URL=''
AM_DEFAULT_VERBOSITY
AM_DEFAULT_V
AM_V
+CSCOPE
+ETAGS
+CTAGS
am__fastdepCC_FALSE
am__fastdepCC_TRUE
CCDEPMODE
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures guestfs-tools 1.46.1 to adapt to many kinds of systems.
+\`configure' configures guestfs-tools 1.48.0 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of guestfs-tools 1.46.1:";;
+ short | recursive ) echo "Configuration of guestfs-tools 1.48.0:";;
esac
cat <<\_ACEOF
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-guestfs-tools configure 1.46.1
+guestfs-tools configure 1.48.0
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by guestfs-tools $as_me 1.46.1, which was
+It was created by guestfs-tools $as_me 1.48.0, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
if test x"${MISSING+set}" != xset; then
- case $am_aux_dir in
- *\ * | *\ *)
- MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;;
- *)
- MISSING="\${SHELL} $am_aux_dir/missing" ;;
- esac
+ MISSING="\${SHELL} '$am_aux_dir/missing'"
fi
# Use eval to expand $SHELL
if eval "$MISSING --is-lightweight"; then
# Define the identity of the package.
PACKAGE='guestfs-tools'
- VERSION='1.46.1'
+ VERSION='1.48.0'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
fi
+# Variables for tags utilities; see am/tags.am
+if test -z "$CTAGS"; then
+ CTAGS=ctags
+fi
+
+if test -z "$ETAGS"; then
+ ETAGS=etags
+fi
+
+if test -z "$CSCOPE"; then
+ CSCOPE=cscope
+fi
+
+
# POSIX will say in a future version that running "rm -f" with no argument
# is OK; and we want to be able to make that assumption in our Makefile
fi
-ocaml_ver_str=4.02
+ocaml_ver_str=4.04
ocaml_min_major=4
-ocaml_min_minor=2
+ocaml_min_minor=4
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking if OCaml version >= $ocaml_ver_str" >&5
printf %s "checking if OCaml version >= $ocaml_ver_str... " >&6; }
ocaml_major="`echo $OCAMLVERSION | $AWK -F. '{print $1}'`"
OCAML_PKG_gettext=no
OCAML_PKG_ounit2=no
ounit_is_v2=no
-have_Bytes_module=no
if test "x$OCAMLC" != "xno"
then :
fi
- # Check if we have the 'Bytes' module. If not (OCaml < 4.02) then
- # we need to create a compatibility module.
- # AC_CHECK_OCAML_MODULE is a bit broken, so open code this test.
- { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking for OCaml module Bytes" >&5
-printf %s "checking for OCaml module Bytes... " >&6; }
- rm -f conftest.ml
- echo 'let s = Bytes.empty' > conftest.ml
- if $OCAMLC -c conftest.ml >&5 2>&5 ; then
- { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
-printf "%s\n" "yes" >&6; }
- have_Bytes_module=yes
- else
- { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: not found" >&5
-printf "%s\n" "not found" >&6; }
- have_Bytes_module=no
- fi
-
fi
if test "x$OCAML_PKG_gettext" != "xno"; then
HAVE_OCAML_PKG_GETTEXT_TRUE=
fi
-OCAML_WARN_ERROR="-warn-error CDEFLMPSUVYZX+52-3"
+OCAML_WARN_ERROR="-warn-error +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3-6 -w -6"
OCAML_FLAGS="-g -annot $safe_string_option"
ac_config_files="$ac_config_files run"
+ac_config_files="$ac_config_files win-reg/virt-win-reg"
+
-ac_config_files="$ac_config_files Makefile align/Makefile bash/Makefile builder/Makefile builder/libguestfs.conf builder/opensuse.conf builder/templates/Makefile builder/test-config/virt-builder/repos.d/test-index.conf builder/test-simplestreams/virt-builder/repos.d/cirros.conf builder/test-website/virt-builder/repos.d/libguestfs.conf cat/Makefile common/edit/Makefile common/mlcustomize/Makefile common/mlgettext/Makefile common/mlpcre/Makefile common/mlprogress/Makefile common/mlstdutils/Makefile common/mlstdutils/guestfs_config.ml common/mltools/Makefile common/mlutils/Makefile common/mlvisit/Makefile common/mlxml/Makefile common/options/Makefile common/parallel/Makefile common/progress/Makefile common/structs/Makefile common/utils/Makefile common/visit/Makefile common/windows/Makefile config.sh customize/Makefile df/Makefile dib/Makefile diff/Makefile edit/Makefile format/Makefile get-kernel/Makefile gnulib/lib/Makefile inspector/Makefile make-fs/Makefile po-docs/Makefile po-docs/ja/Makefile po-docs/uk/Makefile po/Makefile resize/Makefile sparsify/Makefile sysprep/Makefile test-data/Makefile test-data/binaries/Makefile test-data/blank-disks/Makefile test-data/files/Makefile test-data/phony-guests/Makefile test-data/phony-guests/guests.xml win-reg/Makefile"
+ac_config_files="$ac_config_files Makefile align/Makefile bash/Makefile builder/Makefile builder/libguestfs.conf builder/opensuse.conf builder/templates/Makefile builder/test-config/virt-builder/repos.d/test-index.conf builder/test-simplestreams/virt-builder/repos.d/cirros.conf builder/test-website/virt-builder/repos.d/libguestfs.conf cat/Makefile common/edit/Makefile common/mlcustomize/Makefile common/mlgettext/Makefile common/mlpcre/Makefile common/mlprogress/Makefile common/mlstdutils/Makefile common/mlstdutils/guestfs_config.ml common/mltools/Makefile common/mlutils/Makefile common/mlvisit/Makefile common/mlxml/Makefile common/options/Makefile common/parallel/Makefile common/progress/Makefile common/structs/Makefile common/utils/Makefile common/visit/Makefile common/windows/Makefile config.sh customize/Makefile docs/Makefile df/Makefile dib/Makefile diff/Makefile edit/Makefile format/Makefile get-kernel/Makefile gnulib/lib/Makefile inspector/Makefile make-fs/Makefile po-docs/Makefile po-docs/ja/Makefile po-docs/uk/Makefile po/Makefile resize/Makefile sparsify/Makefile sysprep/Makefile test-data/Makefile test-data/binaries/Makefile test-data/blank-disks/Makefile test-data/files/Makefile test-data/phony-guests/Makefile test-data/phony-guests/guests.xml win-reg/Makefile"
cat >confcache <<\_ACEOF
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by guestfs-tools $as_me 1.46.1, which was
+This file was extended by guestfs-tools $as_me 1.48.0, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
-guestfs-tools config.status 1.46.1
+guestfs-tools config.status 1.48.0
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"
"ocaml-link.sh") CONFIG_FILES="$CONFIG_FILES ocaml-link.sh" ;;
"podwrapper.pl") CONFIG_FILES="$CONFIG_FILES podwrapper.pl" ;;
"run") CONFIG_FILES="$CONFIG_FILES run" ;;
+ "win-reg/virt-win-reg") CONFIG_FILES="$CONFIG_FILES win-reg/virt-win-reg" ;;
"Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
"align/Makefile") CONFIG_FILES="$CONFIG_FILES align/Makefile" ;;
"bash/Makefile") CONFIG_FILES="$CONFIG_FILES bash/Makefile" ;;
"common/windows/Makefile") CONFIG_FILES="$CONFIG_FILES common/windows/Makefile" ;;
"config.sh") CONFIG_FILES="$CONFIG_FILES config.sh" ;;
"customize/Makefile") CONFIG_FILES="$CONFIG_FILES customize/Makefile" ;;
+ "docs/Makefile") CONFIG_FILES="$CONFIG_FILES docs/Makefile" ;;
"df/Makefile") CONFIG_FILES="$CONFIG_FILES df/Makefile" ;;
"dib/Makefile") CONFIG_FILES="$CONFIG_FILES dib/Makefile" ;;
"diff/Makefile") CONFIG_FILES="$CONFIG_FILES diff/Makefile" ;;
"ocaml-link.sh":F) chmod +x,-w ocaml-link.sh ;;
"podwrapper.pl":F) chmod +x,-w podwrapper.pl ;;
"run":F) chmod +x,-w run ;;
+ "win-reg/virt-win-reg":F) chmod +x,-w win-reg/virt-win-reg ;;
esac
done # for ac_tag
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-AC_INIT([guestfs-tools], [1.46.1])
+AC_INIT([guestfs-tools], [1.48.0])
dnl The common/ subdirectory assumes this. In libguestfs it contains
dnl the --with-extra parameter. Here we just define it to the version.
[chmod +x,-w podwrapper.pl])
AC_CONFIG_FILES([run],
[chmod +x,-w run])
+AC_CONFIG_FILES([win-reg/virt-win-reg],
+ [chmod +x,-w win-reg/virt-win-reg])
AC_CONFIG_FILES([Makefile
align/Makefile
common/windows/Makefile
config.sh
customize/Makefile
+ docs/Makefile
df/Makefile
dib/Makefile
diff/Makefile
-I$(top_srcdir)/common/edit
libcustomize_a_CFLAGS = \
$(WARN_CFLAGS) $(WERROR_CFLAGS) \
+ $(LIBGUESTFS_CFLAGS) \
$(LIBCRYPT_CFLAGS) \
$(LIBVIRT_CFLAGS) \
$(LIBXML2_CFLAGS) \
-pthread -lpthread \
-lutils \
$(LIBTINFO_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBCRYPT_LIBS) \
$(LIBVIRT_LIBS) \
$(LIBXML2_LIBS) \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@libcustomize_a_CFLAGS = \
@HAVE_OCAML_TRUE@ $(WARN_CFLAGS) $(WERROR_CFLAGS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBCRYPT_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBVIRT_CFLAGS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_CFLAGS) \
@HAVE_OCAML_TRUE@ -pthread -lpthread \
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBTINFO_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBCRYPT_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBVIRT_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
done
install: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) install-am
-install-exec: install-exec-am
+install-exec: $(BUILT_SOURCES)
+ $(MAKE) $(AM_MAKEFLAGS) install-exec-am
install-data: install-data-am
uninstall: uninstall-am
uninstall-man: uninstall-man1
-.MAKE: all check check-am install install-am install-strip
+.MAKE: all check check-am install install-am install-exec \
+ install-strip
.PHONY: CTAGS GTAGS TAGS all all-am am--depfiles check check-TESTS \
check-am clean clean-binPROGRAMS clean-generic clean-libtool \
(* virt-sysprep
- * Copyright (C) 2012-2020 Red Hat Inc.
+ * Copyright (C) 2012-2021 Red Hat Inc.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
open Printf
-type password_crypto = [`MD5 | `SHA256 | `SHA512 ]
+type password_crypto = [ `MD5 | `SHA256 | `SHA512 | `YESCRYPT ]
type password_selector = {
pw_password : password;
| "md5" -> `MD5
| "sha256" -> `SHA256
| "sha512" -> `SHA512
+ | "yescrypt" -> `YESCRYPT
| arg ->
- error (f_"password-crypto: unknown algorithm %s, use \"md5\", \"sha256\" or \"sha512\"") arg
+ error (f_"password-crypto: unknown algorithm %s, use \"md5\", \"sha256\", \"sha512\" or \"yescrypt\"") arg
let rec parse_selector arg =
parse_selector_list arg (String.nsplit ":" arg)
* https://rwmj.wordpress.com/2013/07/09/setting-the-root-or-other-passwords-in-a-linux-guest/
*)
and encrypt password crypto =
- (* Get random characters from the set [A-Za-z0-9./] *)
- let salt = Urandom.urandom_uniform 16 chars in
+ (* Get random characters from the set [A-Za-z0-9./]
+ *
+ * 24 characters gives a 144 bits (18 bytes) salt. Unlike the more
+ * traditional 128 bits (16 bytes) salt, this 144 bits salt is always
+ * represented by the same number of base64 characters without any
+ * padding issues, where 128 bits can be represented by 22 or 23
+ * (depending on padding) base64-encoded characters, even with a
+ * non-standard base64 encoding scheme.
+ *
+ * We need it this way, because the yescrypt hashing methods requires
+ * at least 128 bits of salt to work properly.
+ *)
+ let salt = Urandom.urandom_uniform 24 chars in
let salt =
(match crypto with
| `MD5 -> "$1$"
| `SHA256 -> "$5$"
- | `SHA512 -> "$6$") ^ salt ^ "$" in
+ | `SHA512 -> "$6$"
+ | `YESCRYPT -> "$y$j9T$") ^ salt ^ "$" in
let r = Crypt.crypt password salt in
(*printf "password: encrypt %s with salt %s -> %s\n" password salt r;*)
r
(* glibc 2.7 was released in Oct 2007. Approximately, all guests that
* precede this date only support md5, whereas all guests after this
* date can support sha512.
+ *
+ * Most distros released in 2020 or later ship with libxcrypt >= 4.3,
+ * and are able to handle yescrypt hashes.
*)
and default_crypto g root =
let distro = g#inspect_get_distro root in
let major = g#inspect_get_major_version root in
match distro, major with
+ | ("rhel"|"centos"|"scientificlinux"|"oraclelinux"|"redhat-based"), v when v >= 9 ->
+ `YESCRYPT
| ("rhel"|"centos"|"scientificlinux"|"oraclelinux"|"redhat-based"), v when v >= 6 ->
`SHA512
| ("rhel"|"centos"|"scientificlinux"|"oraclelinux"|"redhat-based"), _ ->
`MD5 (* RHEL 5 does not appear to support SHA512, according to crypt(3) *)
+ | "fedora", v when v >= 30 -> `YESCRYPT
| "fedora", v when v >= 9 -> `SHA512
| "fedora", _ -> `MD5
+ | "debian", v when v >= 11 -> `YESCRYPT
| "debian", v when v >= 5 -> `SHA512
| "debian", _ -> `MD5
- (* Very likely earlier versions of Ubuntu than 10.04 had new crypt,
- * but Ubuntu 10.04 is the earliest version I have checked.
- *)
+ | "ubuntu", v when v >= 20 -> `YESCRYPT
| "ubuntu", v when v >= 10 -> `SHA512
| "ubuntu", _ -> `MD5
+ | ("opensuse"|"sles"), v when v >= 15 -> `YESCRYPT
| ("opensuse"|"sles"), v when v >= 11 -> `SHA512
| ("opensuse"|"sles"), _ -> `MD5
(* Rolling distributions, which hopefully should be updated enough. *)
- | ("archlinux"|"voidlinux"|"kalilinux"), _ -> `SHA512
+ | ("archlinux"|"kalilinux"), _ -> `YESCRYPT
+ | ("voidlinux"), _ -> `SHA512
| _, _ ->
let minor = g#inspect_get_minor_version root in
(* virt-sysprep
- * Copyright (C) 2012-2020 Red Hat Inc.
+ * Copyright (C) 2012-2021 Red Hat Inc.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
*)
-type password_crypto = [ `MD5 | `SHA256 | `SHA512 ]
+type password_crypto = [ `MD5 | `SHA256 | `SHA512 | `YESCRYPT ]
val password_crypto_of_string : string -> password_crypto
(** Parse --password-crypto parameter on command line. *)
rm -f $fq $out
qemu-img create -f qcow2 -b $f -F raw $fq
-# Add --no-network so UML works.
-$VG virt-customize --format qcow2 -a $fq --no-network \
+$VG virt-customize --format qcow2 -a $fq \
--write /etc/motd:MOTD \
--write /etc/motd2:MOTD2 \
--write /etc/motd3:MOTD3 \
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 0);
- assert (live == 0);
/* Must be no extra arguments on the command line. */
if (optind != argc)
-pthread -lpthread \
-lutils \
$(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBINTL) \
-lgnu
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@ -pthread -lpthread \
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBINTL) \
@HAVE_OCAML_TRUE@ -lgnu
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
let image_basename_d = image_basename ^ ".d" in
let tmpdir = Mkdtemp.temp_dir "dib." in
- rmdir_on_exit tmpdir;
+ On_exit.rmdir tmpdir;
let auxtmpdir = tmpdir // "in_target.aux" in
do_mkdir auxtmpdir;
let hookstmpdir = auxtmpdir // "hooks" in
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g, *g2;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1);
- assert (live == 0);
CHECK_OPTION_format_consumed;
CHECK_OPTION_blocksize_consumed;
$TEST_FUNCTIONS
skip_if_skipped
-skip_if_backend uml
skip_unless_phony_guest fedora.img
rm -f fedora.qcow2
--- /dev/null
+# guestfs-tools documentation
+# Copyright (C) 2010-2022 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+include $(top_srcdir)/subdir-rules.mk
+
+EXTRA_DIST = \
+ guestfs-tools-release-notes-1.48.pod
+
+man_MANS = \
+ guestfs-tools-release-notes-1.48.1
+noinst_DATA = \
+ $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html
+
+guestfs-tools-release-notes-1.48.1 guestfs-tools-release-notes-1.48.txt $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html: stamp-guestfs-tools-release-notes-1.48.pod
+
+stamp-guestfs-tools-release-notes-1.48.pod: guestfs-tools-release-notes-1.48.pod
+ $(PODWRAPPER) \
+ --section 1 \
+ --man guestfs-tools-release-notes-1.48.1 \
+ --html $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html \
+ --license GPLv2+ \
+ $<
+ touch $@
--- /dev/null
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
+# @configure_input@
+
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
+
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+
+# guestfs-tools documentation
+# Copyright (C) 2010-2022 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# libguestfs
+# Copyright (C) 2009-2020 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# subdir-rules.mk should be included in every *subdirectory* Makefile.am.
+
+# libguestfs
+# Copyright (C) 2013 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# 'common-rules.mk' should be included in every Makefile.am.
+# cf. 'subdir-rules.mk'
+
+VPATH = @srcdir@
+am__is_gnu_make = { \
+ if test -z '$(MAKELEVEL)'; then \
+ false; \
+ elif test -n '$(MAKE_HOST)'; then \
+ true; \
+ elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
+ true; \
+ else \
+ false; \
+ fi; \
+}
+am__make_running_with_option = \
+ case $${target_option-} in \
+ ?) ;; \
+ *) echo "am__make_running_with_option: internal error: invalid" \
+ "target option '$${target_option-}' specified" >&2; \
+ exit 1;; \
+ esac; \
+ has_opt=no; \
+ sane_makeflags=$$MAKEFLAGS; \
+ if $(am__is_gnu_make); then \
+ sane_makeflags=$$MFLAGS; \
+ else \
+ case $$MAKEFLAGS in \
+ *\\[\ \ ]*) \
+ bs=\\; \
+ sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \
+ | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \
+ esac; \
+ fi; \
+ skip_next=no; \
+ strip_trailopt () \
+ { \
+ flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \
+ }; \
+ for flg in $$sane_makeflags; do \
+ test $$skip_next = yes && { skip_next=no; continue; }; \
+ case $$flg in \
+ *=*|--*) continue;; \
+ -*I) strip_trailopt 'I'; skip_next=yes;; \
+ -*I?*) strip_trailopt 'I';; \
+ -*O) strip_trailopt 'O'; skip_next=yes;; \
+ -*O?*) strip_trailopt 'O';; \
+ -*l) strip_trailopt 'l'; skip_next=yes;; \
+ -*l?*) strip_trailopt 'l';; \
+ -[dEDm]) skip_next=yes;; \
+ -[JT]) skip_next=yes;; \
+ esac; \
+ case $$flg in \
+ *$$target_option*) has_opt=yes; break;; \
+ esac; \
+ done; \
+ test $$has_opt = yes
+am__make_dryrun = (target_option=n; $(am__make_running_with_option))
+am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
+pkgdatadir = $(datadir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkglibexecdir = $(libexecdir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
+subdir = docs
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
+ $(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
+ $(top_srcdir)/m4/ltversion.m4 $(top_srcdir)/m4/lt~obsolete.m4 \
+ $(top_srcdir)/m4/ocaml.m4 $(top_srcdir)/m4/guestfs-progs.m4 \
+ $(top_srcdir)/m4/guestfs-c.m4 \
+ $(top_srcdir)/m4/guestfs-libraries.m4 \
+ $(top_srcdir)/m4/guestfs-ocaml-gettext.m4 \
+ $(top_srcdir)/m4/guestfs-ocaml.m4 \
+ $(top_srcdir)/m4/guestfs-perl.m4 \
+ $(top_srcdir)/m4/guestfs-misc-libraries.m4 \
+ $(top_srcdir)/m4/guestfs-bash-completion.m4 \
+ $(top_srcdir)/configure.ac
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+ $(ACLOCAL_M4)
+DIST_COMMON = $(srcdir)/Makefile.am $(am__DIST_COMMON)
+mkinstalldirs = $(install_sh) -d
+CONFIG_HEADER = $(top_builddir)/config.h
+CONFIG_CLEAN_FILES =
+CONFIG_CLEAN_VPATH_FILES =
+AM_V_P = $(am__v_P_@AM_V@)
+am__v_P_ = $(am__v_P_@AM_DEFAULT_V@)
+am__v_P_0 = false
+am__v_P_1 = :
+AM_V_GEN = $(am__v_GEN_@AM_V@)
+am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@)
+am__v_GEN_0 = @echo " GEN " $@;
+am__v_GEN_1 =
+AM_V_at = $(am__v_at_@AM_V@)
+am__v_at_ = $(am__v_at_@AM_DEFAULT_V@)
+am__v_at_0 = @
+am__v_at_1 =
+SOURCES =
+DIST_SOURCES =
+am__can_run_installinfo = \
+ case $$AM_UPDATE_INFO_DIR in \
+ n|no|NO) false;; \
+ *) (install-info --version) >/dev/null 2>&1;; \
+ esac
+am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
+am__vpath_adj = case $$p in \
+ $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
+ *) f=$$p;; \
+ esac;
+am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
+am__install_max = 40
+am__nobase_strip_setup = \
+ srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
+am__nobase_strip = \
+ for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
+am__nobase_list = $(am__nobase_strip_setup); \
+ for p in $$list; do echo "$$p $$p"; done | \
+ sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
+ $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
+ if (++n[$$2] == $(am__install_max)) \
+ { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
+ END { for (dir in files) print dir, files[dir] }'
+am__base_list = \
+ sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
+ sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
+am__uninstall_files_from_dir = { \
+ test -z "$$files" \
+ || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
+ || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
+ $(am__cd) "$$dir" && rm -f $$files; }; \
+ }
+man1dir = $(mandir)/man1
+am__installdirs = "$(DESTDIR)$(man1dir)"
+NROFF = nroff
+MANS = $(man_MANS)
+DATA = $(noinst_DATA)
+am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP)
+am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/common-rules.mk \
+ $(top_srcdir)/subdir-rules.mk
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
+AR = @AR@
+AUTOCONF = @AUTOCONF@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+BASH_COMPLETIONS_DIR = @BASH_COMPLETIONS_DIR@
+BASH_COMPLETION_CFLAGS = @BASH_COMPLETION_CFLAGS@
+BASH_COMPLETION_LIBS = @BASH_COMPLETION_LIBS@
+CC = @CC@
+CCDEPMODE = @CCDEPMODE@
+CFLAGS = @CFLAGS@
+CPP = @CPP@
+CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
+CYGPATH_W = @CYGPATH_W@
+DEFS = @DEFS@
+DEPDIR = @DEPDIR@
+DLLTOOL = @DLLTOOL@
+DSYMUTIL = @DSYMUTIL@
+DUMPBIN = @DUMPBIN@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+EGREP = @EGREP@
+ETAGS = @ETAGS@
+EXEEXT = @EXEEXT@
+FGREP = @FGREP@
+GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
+GETTEXT_MACRO_VERSION = @GETTEXT_MACRO_VERSION@
+GMSGFMT = @GMSGFMT@
+GMSGFMT_015 = @GMSGFMT_015@
+GREP = @GREP@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+INTLLIBS = @INTLLIBS@
+INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@
+JANSSON_CFLAGS = @JANSSON_CFLAGS@
+JANSSON_LIBS = @JANSSON_LIBS@
+LD = @LD@
+LDFLAGS = @LDFLAGS@
+LEX = @LEX@
+LEXLIB = @LEXLIB@
+LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@
+LIBCRYPT_CFLAGS = @LIBCRYPT_CFLAGS@
+LIBCRYPT_LIBS = @LIBCRYPT_LIBS@
+LIBGUESTFS_CFLAGS = @LIBGUESTFS_CFLAGS@
+LIBGUESTFS_LIBS = @LIBGUESTFS_LIBS@
+LIBICONV = @LIBICONV@
+LIBINTL = @LIBINTL@
+LIBLZMA_CFLAGS = @LIBLZMA_CFLAGS@
+LIBLZMA_LIBS = @LIBLZMA_LIBS@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LIBTINFO_CFLAGS = @LIBTINFO_CFLAGS@
+LIBTINFO_LIBS = @LIBTINFO_LIBS@
+LIBTOOL = @LIBTOOL@
+LIBVIRT_CFLAGS = @LIBVIRT_CFLAGS@
+LIBVIRT_LIBS = @LIBVIRT_LIBS@
+LIBXML2_CFLAGS = @LIBXML2_CFLAGS@
+LIBXML2_LIBS = @LIBXML2_LIBS@
+LIPO = @LIPO@
+LN_S = @LN_S@
+LTLIBICONV = @LTLIBICONV@
+LTLIBINTL = @LTLIBINTL@
+LTLIBOBJS = @LTLIBOBJS@
+LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@
+MAKEINFO = @MAKEINFO@
+MANIFEST_TOOL = @MANIFEST_TOOL@
+MKDIR_P = @MKDIR_P@
+MKISOFS = @MKISOFS@
+MSGCAT = @MSGCAT@
+MSGFMT = @MSGFMT@
+MSGMERGE = @MSGMERGE@
+MSGMERGE_FOR_MSGFMT_OPTION = @MSGMERGE_FOR_MSGFMT_OPTION@
+NCURSES_CONFIG = @NCURSES_CONFIG@
+NM = @NM@
+NMEDIT = @NMEDIT@
+OBJDUMP = @OBJDUMP@
+OBJEXT = @OBJEXT@
+OCAMLBEST = @OCAMLBEST@
+OCAMLBUILD = @OCAMLBUILD@
+OCAMLC = @OCAMLC@
+OCAMLCDOTOPT = @OCAMLCDOTOPT@
+OCAMLDEP = @OCAMLDEP@
+OCAMLDEP_ALL = @OCAMLDEP_ALL@
+OCAMLDEP_ONE_LINE = @OCAMLDEP_ONE_LINE@
+OCAMLDOC = @OCAMLDOC@
+OCAMLFIND = @OCAMLFIND@
+OCAMLLIB = @OCAMLLIB@
+OCAMLMKLIB = @OCAMLMKLIB@
+OCAMLMKTOP = @OCAMLMKTOP@
+OCAMLOPT = @OCAMLOPT@
+OCAMLOPTDOTOPT = @OCAMLOPTDOTOPT@
+OCAMLVERSION = @OCAMLVERSION@
+OCAML_FLAGS = @OCAML_FLAGS@
+OCAML_GETTEXT = @OCAML_GETTEXT@
+OCAML_PKG_gettext = @OCAML_PKG_gettext@
+OCAML_PKG_guestfs = @OCAML_PKG_guestfs@
+OCAML_PKG_ounit2 = @OCAML_PKG_ounit2@
+OCAML_RUNTIME_VARIANT_PIC_OPTION = @OCAML_RUNTIME_VARIANT_PIC_OPTION@
+OCAML_WARN_ERROR = @OCAML_WARN_ERROR@
+OTOOL = @OTOOL@
+OTOOL64 = @OTOOL64@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_URL = @PACKAGE_URL@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PACKAGE_VERSION_FULL = @PACKAGE_VERSION_FULL@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+PCRE2_CFLAGS = @PCRE2_CFLAGS@
+PCRE2_CONFIG = @PCRE2_CONFIG@
+PCRE2_LIBS = @PCRE2_LIBS@
+PERL = @PERL@
+PKG_CONFIG = @PKG_CONFIG@
+PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
+PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
+PO4A_GETTEXTIZE = @PO4A_GETTEXTIZE@
+PO4A_TRANSLATE = @PO4A_TRANSLATE@
+PODWRAPPER = @PODWRAPPER@
+POSUB = @POSUB@
+RANLIB = @RANLIB@
+SED = @SED@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+SQLITE3 = @SQLITE3@
+STRIP = @STRIP@
+SYSCONFDIR = @SYSCONFDIR@
+USE_NLS = @USE_NLS@
+VALGRIND = @VALGRIND@
+VERSION = @VERSION@
+VERSION_SCRIPT_FLAGS = @VERSION_SCRIPT_FLAGS@
+XGETTEXT = @XGETTEXT@
+XGETTEXT_015 = @XGETTEXT_015@
+XGETTEXT_EXTRA_OPTIONS = @XGETTEXT_EXTRA_OPTIONS@
+XMLLINT = @XMLLINT@
+XZCAT = @XZCAT@
+YACC = @YACC@
+YFLAGS = @YFLAGS@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+ac_ct_AR = @ac_ct_AR@
+ac_ct_CC = @ac_ct_CC@
+ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
+am__include = @am__include@
+am__leading_dot = @am__leading_dot@
+am__quote = @am__quote@
+am__tar = @am__tar@
+am__untar = @am__untar@
+bindir = @bindir@
+build = @build@
+build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
+builddir = @builddir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+host = @host@
+host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
+htmldir = @htmldir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+libdir = @libdir@
+libexecdir = @libexecdir@
+libvirt_ro_uri = @libvirt_ro_uri@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+oldincludedir = @oldincludedir@
+ounit_is_v2 = @ounit_is_v2@
+pdfdir = @pdfdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+runstatedir = @runstatedir@
+sbindir = @sbindir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target_alias = @target_alias@
+top_build_prefix = @top_build_prefix@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+
+# Files that should universally be removed by 'make clean'. Note if
+# there is any case in any subdirectory where a file should not be
+# removed by 'make clean', it should not be listed here!
+
+# Editor backup files
+
+# Patch original and reject files.
+
+# OCaml intermediate and generated files.
+
+# OCaml -annot files (used for displaying types in some IDEs).
+
+# OCaml oUnit generated files.
+
+# Manual pages - these are all generated from *.pod, so the
+# pages themselves should all be removed by 'make clean'.
+
+# Stamp files used when generating man pages.
+
+# Bindtests temporary files used in many language bindings.
+CLEANFILES = *~ *.bak *.orig *.rej *.cmi *.cmo *.cma *.cmx *.cmxa \
+ dll*.so *.a *.annot oUnit-*.cache oUnit-*.log *.1 *.3 *.5 *.8 \
+ stamp-*.pod bindtests.tmp
+
+# Files that should be universally removed by 'make distclean'.
+DISTCLEANFILES = .depend stamp-*
+
+# Special suffixes used by OCaml.
+
+# Special suffixes used by PO files.
+SUFFIXES = .cmo .cmi .cmx .ml .mli .mll .mly .po .gmo
+LOG_DRIVER = env $(SHELL) $(top_srcdir)/build-aux/guestfs-test-driver
+
+# Rules for building OCaml objects.
+# See also:
+# guestfs-hacking(1) section "HOW OCAML PROGRAMS ARE COMPILED AND LINKED"
+@HAVE_OCAMLOPT_FALSE@MLARCHIVE = cma
+@HAVE_OCAMLOPT_TRUE@MLARCHIVE = cmxa
+@HAVE_OCAMLOPT_FALSE@LINK_CUSTOM_OCAMLC_ONLY = -custom
+@HAVE_OCAMLOPT_FALSE@BEST = c
+@HAVE_OCAMLOPT_TRUE@BEST = opt
+
+# custom silent rules
+guestfs_am_v_ocamlc = $(guestfs_am_v_ocamlc_@AM_V@)
+guestfs_am_v_ocamlc_ = $(guestfs_am_v_ocamlc_@AM_DEFAULT_V@)
+guestfs_am_v_ocamlc_0 = @echo " OCAMLC " $@;
+guestfs_am_v_ocamlcmi = $(guestfs_am_v_ocamlcmi_@AM_V@)
+guestfs_am_v_ocamlcmi_ = $(guestfs_am_v_ocamlcmi_@AM_DEFAULT_V@)
+guestfs_am_v_ocamlcmi_0 = @echo " OCAMLCMI" $@;
+guestfs_am_v_ocamlopt = $(guestfs_am_v_ocamlopt_@AM_V@)
+guestfs_am_v_ocamlopt_ = $(guestfs_am_v_ocamlopt_@AM_DEFAULT_V@)
+guestfs_am_v_ocamlopt_0 = @echo " OCAMLOPT" $@;
+guestfs_am_v_javac = $(guestfs_am_v_javac_@AM_V@)
+guestfs_am_v_javac_ = $(guestfs_am_v_javac_@AM_DEFAULT_V@)
+guestfs_am_v_javac_0 = @echo " JAVAC " $@;
+guestfs_am_v_erlc = $(guestfs_am_v_erlc_@AM_V@)
+guestfs_am_v_erlc_ = $(guestfs_am_v_erlc_@AM_DEFAULT_V@)
+guestfs_am_v_erlc_0 = @echo " ERLC " $@;
+guestfs_am_v_podwrapper = $(guestfs_am_v_podwrapper_@AM_V@)
+guestfs_am_v_podwrapper_ = $(guestfs_am_v_podwrapper_@AM_DEFAULT_V@)
+guestfs_am_v_podwrapper_0 = @echo " POD " $@;
+guestfs_am_v_jar = $(guestfs_am_v_jar_@AM_V@)
+guestfs_am_v_jar_ = $(guestfs_am_v_jar_@AM_DEFAULT_V@)
+guestfs_am_v_jar_0 = @echo " JAR " $@;
+guestfs_am_v_po4a_translate = $(guestfs_am_v_po4a_translate_@AM_V@)
+guestfs_am_v_po4a_translate_ = $(guestfs_am_v_po4a_translate_@AM_DEFAULT_V@)
+guestfs_am_v_po4a_translate_0 = @echo " PO4A-T " $@;
+EXTRA_DIST = \
+ guestfs-tools-release-notes-1.48.pod
+
+man_MANS = \
+ guestfs-tools-release-notes-1.48.1
+
+noinst_DATA = \
+ $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html
+
+all: all-am
+
+.SUFFIXES:
+.SUFFIXES: .cmo .cmi .cmx .ml .mli .mll .mly .po .gmo
+$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(top_srcdir)/subdir-rules.mk $(top_srcdir)/common-rules.mk $(am__configure_deps)
+ @for dep in $?; do \
+ case '$(am__configure_deps)' in \
+ *$$dep*) \
+ ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
+ && { if test -f $@; then exit 0; else break; fi; }; \
+ exit 1;; \
+ esac; \
+ done; \
+ echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign docs/Makefile'; \
+ $(am__cd) $(top_srcdir) && \
+ $(AUTOMAKE) --foreign docs/Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+ @case '$?' in \
+ *config.status*) \
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+ *) \
+ echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles)'; \
+ cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__maybe_remake_depfiles);; \
+ esac;
+$(top_srcdir)/subdir-rules.mk $(top_srcdir)/common-rules.mk $(am__empty):
+
+$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure: $(am__configure_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4): $(am__aclocal_m4_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(am__aclocal_m4_deps):
+
+mostlyclean-libtool:
+ -rm -f *.lo
+
+clean-libtool:
+ -rm -rf .libs _libs
+install-man1: $(man_MANS)
+ @$(NORMAL_INSTALL)
+ @list1=''; \
+ list2='$(man_MANS)'; \
+ test -n "$(man1dir)" \
+ && test -n "`echo $$list1$$list2`" \
+ || exit 0; \
+ echo " $(MKDIR_P) '$(DESTDIR)$(man1dir)'"; \
+ $(MKDIR_P) "$(DESTDIR)$(man1dir)" || exit 1; \
+ { for i in $$list1; do echo "$$i"; done; \
+ if test -n "$$list2"; then \
+ for i in $$list2; do echo "$$i"; done \
+ | sed -n '/\.1[a-z]*$$/p'; \
+ fi; \
+ } | while read p; do \
+ if test -f $$p; then d=; else d="$(srcdir)/"; fi; \
+ echo "$$d$$p"; echo "$$p"; \
+ done | \
+ sed -e 'n;s,.*/,,;p;h;s,.*\.,,;s,^[^1][0-9a-z]*$$,1,;x' \
+ -e 's,\.[0-9a-z]*$$,,;$(transform);G;s,\n,.,' | \
+ sed 'N;N;s,\n, ,g' | { \
+ list=; while read file base inst; do \
+ if test "$$base" = "$$inst"; then list="$$list $$file"; else \
+ echo " $(INSTALL_DATA) '$$file' '$(DESTDIR)$(man1dir)/$$inst'"; \
+ $(INSTALL_DATA) "$$file" "$(DESTDIR)$(man1dir)/$$inst" || exit $$?; \
+ fi; \
+ done; \
+ for i in $$list; do echo "$$i"; done | $(am__base_list) | \
+ while read files; do \
+ test -z "$$files" || { \
+ echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(man1dir)'"; \
+ $(INSTALL_DATA) $$files "$(DESTDIR)$(man1dir)" || exit $$?; }; \
+ done; }
+
+uninstall-man1:
+ @$(NORMAL_UNINSTALL)
+ @list=''; test -n "$(man1dir)" || exit 0; \
+ files=`{ for i in $$list; do echo "$$i"; done; \
+ l2='$(man_MANS)'; for i in $$l2; do echo "$$i"; done | \
+ sed -n '/\.1[a-z]*$$/p'; \
+ } | sed -e 's,.*/,,;h;s,.*\.,,;s,^[^1][0-9a-z]*$$,1,;x' \
+ -e 's,\.[0-9a-z]*$$,,;$(transform);G;s,\n,.,'`; \
+ dir='$(DESTDIR)$(man1dir)'; $(am__uninstall_files_from_dir)
+tags TAGS:
+
+ctags CTAGS:
+
+cscope cscopelist:
+
+distdir: $(BUILT_SOURCES)
+ $(MAKE) $(AM_MAKEFLAGS) distdir-am
+
+distdir-am: $(DISTFILES)
+ @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ list='$(DISTFILES)'; \
+ dist_files=`for file in $$list; do echo $$file; done | \
+ sed -e "s|^$$srcdirstrip/||;t" \
+ -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+ case $$dist_files in \
+ */*) $(MKDIR_P) `echo "$$dist_files" | \
+ sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+ sort -u` ;; \
+ esac; \
+ for file in $$dist_files; do \
+ if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+ if test -d $$d/$$file; then \
+ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+ if test -d "$(distdir)/$$file"; then \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
+ fi; \
+ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+ cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
+ fi; \
+ cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
+ else \
+ test -f "$(distdir)/$$file" \
+ || cp -p $$d/$$file "$(distdir)/$$file" \
+ || exit 1; \
+ fi; \
+ done
+check-am: all-am
+check: check-am
+all-am: Makefile $(MANS) $(DATA)
+installdirs:
+ for dir in "$(DESTDIR)$(man1dir)"; do \
+ test -z "$$dir" || $(MKDIR_P) "$$dir"; \
+ done
+install: install-am
+install-exec: install-exec-am
+install-data: install-data-am
+uninstall: uninstall-am
+
+install-am: all-am
+ @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-am
+install-strip:
+ if test -z '$(STRIP)'; then \
+ $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+ install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+ install; \
+ else \
+ $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+ install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+ "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
+ fi
+mostlyclean-generic:
+
+clean-generic:
+ -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
+
+distclean-generic:
+ -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+ -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
+ -test -z "$(DISTCLEANFILES)" || rm -f $(DISTCLEANFILES)
+
+maintainer-clean-generic:
+ @echo "This command is intended for maintainers to use"
+ @echo "it deletes files that may require special tools to rebuild."
+clean: clean-am
+
+clean-am: clean-generic clean-libtool mostlyclean-am
+
+distclean: distclean-am
+ -rm -f Makefile
+distclean-am: clean-am distclean-generic
+
+dvi: dvi-am
+
+dvi-am:
+
+html: html-am
+
+html-am:
+
+info: info-am
+
+info-am:
+
+install-data-am: install-man
+
+install-dvi: install-dvi-am
+
+install-dvi-am:
+
+install-exec-am:
+
+install-html: install-html-am
+
+install-html-am:
+
+install-info: install-info-am
+
+install-info-am:
+
+install-man: install-man1
+
+install-pdf: install-pdf-am
+
+install-pdf-am:
+
+install-ps: install-ps-am
+
+install-ps-am:
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-am
+ -rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-am
+
+mostlyclean-am: mostlyclean-generic mostlyclean-libtool
+
+pdf: pdf-am
+
+pdf-am:
+
+ps: ps-am
+
+ps-am:
+
+uninstall-am: uninstall-man
+
+uninstall-man: uninstall-man1
+
+.MAKE: install-am install-strip
+
+.PHONY: all all-am check check-am clean clean-generic clean-libtool \
+ cscopelist-am ctags-am distclean distclean-generic \
+ distclean-libtool distdir dvi dvi-am html html-am info info-am \
+ install install-am install-data install-data-am install-dvi \
+ install-dvi-am install-exec install-exec-am install-html \
+ install-html-am install-info install-info-am install-man \
+ install-man1 install-pdf install-pdf-am install-ps \
+ install-ps-am install-strip installcheck installcheck-am \
+ installdirs maintainer-clean maintainer-clean-generic \
+ mostlyclean mostlyclean-generic mostlyclean-libtool pdf pdf-am \
+ ps ps-am tags-am uninstall uninstall-am uninstall-man \
+ uninstall-man1
+
+.PRECIOUS: Makefile
+
+
+-include $(top_builddir)/localenv
+
+# Individual Makefile.am's should define generator_built if that
+# subdirectory contains any files which are built by the generator.
+# Set generator_built to the list of those files.
+
+$(generator_built): $(top_builddir)/generator/stamp-generator
+
+$(top_builddir)/generator/stamp-generator: $(top_builddir)/generator/generator
+ @if test -f $(top_builddir)/generator/Makefile; then \
+ $(MAKE) -C $(top_builddir)/generator stamp-generator; \
+ else \
+ echo "warning: Run 'make' at the top level to build $(generator_built)"; \
+ fi
+
+# If this file doesn't exist, just print a warning and continue.
+# During 'make distclean' we can end up deleting this file.
+$(top_builddir)/generator/generator:
+ @if test -f $(top_builddir)/generator/Makefile; then \
+ $(MAKE) -C $(top_builddir)/generator generator; \
+ else \
+ echo "warning: Run 'make' at the top level to build $@"; \
+ fi
+
+%.cmi: %.mli
+ $(guestfs_am_v_ocamlcmi)$(OCAMLFIND) ocamlc $(OCAMLFLAGS) $(OCAMLPACKAGES) -c $< -o $@
+%.cmo: %.ml
+ $(guestfs_am_v_ocamlc)$(OCAMLFIND) ocamlc $(OCAMLFLAGS) $(OCAMLPACKAGES) -c $< -o $@
+@HAVE_OCAMLOPT_TRUE@%.cmx: %.ml
+@HAVE_OCAMLOPT_TRUE@ $(guestfs_am_v_ocamlopt)$(OCAMLFIND) ocamlopt $(OCAMLFLAGS) $(OCAMLPACKAGES) -c $< -o $@
+
+# Test shell scripts should use '$TEST_FUNCTIONS' to get a predefined
+# set of helper functions for running tests (see test-functions.sh).
+#
+# Notes:
+#
+# (1) This is in fact a single command all on one line. The variables
+# are evaluated in test-functions.sh.
+#
+# (2) We use absolute paths here and in test-functions.sh so that the
+# test can change directory freely. But we also include the
+# non-absolute values so they can be used by the test script itself.
+export TEST_FUNCTIONS := \
+ source $(abs_top_srcdir)/test-functions.sh \
+ abs_srcdir="$(abs_srcdir)" \
+ abs_builddir="$(abs_builddir)" \
+ top_srcdir="$(top_srcdir)" \
+ top_builddir="$(top_builddir)" \
+ abs_top_srcdir="$(abs_top_srcdir)" \
+ abs_top_builddir="$(abs_top_builddir)"
+
+guestfs-tools-release-notes-1.48.1 guestfs-tools-release-notes-1.48.txt $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html: stamp-guestfs-tools-release-notes-1.48.pod
+
+stamp-guestfs-tools-release-notes-1.48.pod: guestfs-tools-release-notes-1.48.pod
+ $(PODWRAPPER) \
+ --section 1 \
+ --man guestfs-tools-release-notes-1.48.1 \
+ --html $(top_builddir)/website/guestfs-tools-release-notes-1.48.1.html \
+ --license GPLv2+ \
+ $<
+ touch $@
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:
--- /dev/null
+=head1 NAME
+
+guestfs-tools-release-notes - guestfs tools release Notes
+
+=head1 RELEASE NOTES FOR GUESTFS TOOLS 1.48
+
+These are the release notes for guestfs tools stable release 1.48.
+This describes the major changes since 1.46.
+
+Guestfs tools 1.48.0 was released on B<14 March 2022>.
+
+=head2 virt-builder
+
+New templates: C<alma-8.5>, C<centosstream-8>, C<debian-11>,
+C<fedora-34>, C<fedora-34> (armv7l), C<fedora-35> C<fedora-35>
+(aarch64)
+(Lars Kaiser, Stef Walter).
+
+New fedora-34 (armv7l) template is built to use UEFI.
+
+=head2 virt-customize
+
+The yescrypt password hashing method is now supported
+(Björn Esser).
+
+=head2 virt-inspector
+
+Recognise C<kalilinux>, C<kylin> and C<msdos> operating systems /
+Linux distros (Laszlo Ersek).
+
+Inspection of LUKS encrypted filesystems placed directly on logical
+volumes is now supported, but you will need libguestfs E<ge> 1.48
+(Laszlo Ersek).
+
+=head2 virt-sysprep
+
+Add a new default operation called C<net-nmconn> which removes
+NetworkManager connection profiles (Laszlo Ersek).
+
+=head2 virt-win-reg
+
+C<virt-win-reg --version> now prints both the version of guestfs tools
+and the libguestfs library that it is linked with.
+
+=head2 Common changes
+
+All OCaml tools now suppress line wrapping when output is redirected
+to a file (to make it easier to parse logs with external programs).
+There is a new I<--wrap> option which can be used to reenable line
+wrapping to files if needed (Laszlo Ersek).
+
+=head2 Build changes
+
+Multiple fixes to make it easier to build against either the system
+installed libguestfs or a locally built libguestfs (Laszlo Ersek).
+
+Fix multiple OCaml warnings. Remove some deprecated OCaml features.
+We now require OCaml E<ge> 4.04.
+
+Multiple fixes to valgrind support for glibc 2.35, OCaml 4.13 and
+libvirt 7.7. C<make check-valgrind> should now work.
+
+=head2 Internals
+
+New OCaml C<On_exit> module (from libguestfs-common) is used instead
+of custom on-exit and signal handling.
+
+=head2 Bugs fixed
+
+=over 4
+
+=item L<https://bugzilla.redhat.com/2003706>
+
+virt-install armv7 guest on aarch64 host doesn't work, no LPAE support and no PCI devices
+
+=item L<https://bugzilla.redhat.com/1995391>
+
+RFE: virt-inspector fails to detect the distro and applications on Kylin-Desktop-V10 image
+
+=item L<https://bugzilla.redhat.com/1980922>
+
+virt-sysprep doesn't cleanup NetworkManager connection files
+
+=item L<https://bugzilla.redhat.com/1961160>
+
+The version is incorrect when running 'virt-win-reg --version'
+
+=item L<https://bugzilla.redhat.com/1820221>
+
+Log lines wrapping make log parsing difficult
+
+=item L<https://bugzilla.redhat.com/1658126>
+
+Virt-v2v can't convert guest using LUKS-on-LV
+
+=item L<https://bugzilla.redhat.com/1633328>
+
+Armv7 guest fails to boot with qemu-3.0.0-1
+
+=back
+
+=head1 SEE ALSO
+
+L<http://libguestfs.org/>
+
+=head1 AUTHORS
+
+=begin comment
+
+git shortlog -s v1.46.0..
+
+=end comment
+
+=over 4
+
+=item Björn Esser
+
+=item Lars Kaiser
+
+=item Laszlo Ersek
+
+=item Richard W.M. Jones
+
+=item Stef Walter
+
+=back
+
+=head1 COPYRIGHT
+
+Copyright (C) 2009-2022 Red Hat Inc.
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
int read_only = 0;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 0);
assert (inspector == 1 || mps != NULL);
- assert (live == 0);
/* User must specify at least one filename on the command line. */
if (optind >= argc || argc - optind < 1)
$TEST_FUNCTIONS
skip_if_skipped
-# UML backend does not support qcow2.
-skip_if_backend uml
rm -f test.qcow2
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
int read_only = 0;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 0);
assert (inspector == 0);
- assert (live == 0);
/* Must be no extra arguments on the command line. */
if (optind != argc) {
-pthread -lpthread \
-lutils \
$(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBINTL) \
-lgnu
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@ -pthread -lpthread \
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBINTL) \
@HAVE_OCAML_TRUE@ -lgnu
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__DIST_COMMON = $(srcdir)/Makefile.in \
$(top_srcdir)/build-aux/depcomp $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
EXTRA_DIST = \
expected-debian.img.xml \
expected-fedora.img.xml \
- expected-fedora-luks.img.xml \
+ expected-fedora-luks-on-lvm.img.xml \
+ expected-fedora-lvm-on-luks.img.xml \
expected-ubuntu.img.xml \
expected-archlinux.img.xml \
expected-coreos.img.xml \
expected-windows.img.xml \
test-virt-inspector.sh \
- test-virt-inspector-luks.sh \
+ test-virt-inspector-luks-on-lvm.sh \
+ test-virt-inspector-lvm-on-luks.sh \
test-virt-inspector-docs.sh \
test-xmllint.sh \
virt-inspector.pod
TESTS = \
test-virt-inspector-docs.sh \
test-virt-inspector.sh \
- test-virt-inspector-luks.sh
+ test-virt-inspector-luks-on-lvm.sh \
+ test-virt-inspector-lvm-on-luks.sh
if HAVE_XMLLINT
TESTS += test-xmllint.sh
endif
check-valgrind:
- $(MAKE) TESTS="test-virt-inspector.sh test-virt-inspector-luks.sh" VG="@VG@" check
+ $(MAKE) TESTS="test-virt-inspector.sh test-virt-inspector-luks-on-lvm.sh test-virt-inspector-lvm-on-luks.sh" VG="@VG@" check
check-valgrind-local-guests:
for g in $(GUESTS); do \
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
EXTRA_DIST = \
expected-debian.img.xml \
expected-fedora.img.xml \
- expected-fedora-luks.img.xml \
+ expected-fedora-luks-on-lvm.img.xml \
+ expected-fedora-lvm-on-luks.img.xml \
expected-ubuntu.img.xml \
expected-archlinux.img.xml \
expected-coreos.img.xml \
expected-windows.img.xml \
test-virt-inspector.sh \
- test-virt-inspector-luks.sh \
+ test-virt-inspector-luks-on-lvm.sh \
+ test-virt-inspector-lvm-on-luks.sh \
test-virt-inspector-docs.sh \
test-xmllint.sh \
virt-inspector.pod
noinst_DATA = $(top_builddir)/website/virt-inspector.1.html
TESTS_ENVIRONMENT = $(top_builddir)/run --test
TESTS = test-virt-inspector-docs.sh test-virt-inspector.sh \
- test-virt-inspector-luks.sh $(am__append_1)
+ test-virt-inspector-luks-on-lvm.sh \
+ test-virt-inspector-lvm-on-luks.sh $(am__append_1)
all: all-am
.SUFFIXES:
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
--log-file $$b.log --trs-file $$b.trs \
$(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \
"$$tst" $(AM_TESTS_FD_REDIRECT)
-test-virt-inspector-luks.sh.log: test-virt-inspector-luks.sh
- @p='test-virt-inspector-luks.sh'; \
- b='test-virt-inspector-luks.sh'; \
+test-virt-inspector-luks-on-lvm.sh.log: test-virt-inspector-luks-on-lvm.sh
+ @p='test-virt-inspector-luks-on-lvm.sh'; \
+ b='test-virt-inspector-luks-on-lvm.sh'; \
+ $(am__check_pre) $(LOG_DRIVER) --test-name "$$f" \
+ --log-file $$b.log --trs-file $$b.trs \
+ $(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \
+ "$$tst" $(AM_TESTS_FD_REDIRECT)
+test-virt-inspector-lvm-on-luks.sh.log: test-virt-inspector-lvm-on-luks.sh
+ @p='test-virt-inspector-lvm-on-luks.sh'; \
+ b='test-virt-inspector-lvm-on-luks.sh'; \
$(am__check_pre) $(LOG_DRIVER) --test-name "$$f" \
--log-file $$b.log --trs-file $$b.trs \
$(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
touch $@
check-valgrind:
- $(MAKE) TESTS="test-virt-inspector.sh test-virt-inspector-luks.sh" VG="@VG@" check
+ $(MAKE) TESTS="test-virt-inspector.sh test-virt-inspector-luks-on-lvm.sh test-virt-inspector-lvm-on-luks.sh" VG="@VG@" check
check-valgrind-local-guests:
for g in $(GUESTS); do \
--- /dev/null
+<?xml version="1.0"?>
+<operatingsystems>
+ <operatingsystem>
+ <root>/dev/mapper/luks-ROOTUUID</root>
+ <name>linux</name>
+ <arch>x86_64</arch>
+ <distro>fedora</distro>
+ <product_name>Fedora release 14 (Phony)</product_name>
+ <major_version>14</major_version>
+ <minor_version>0</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <hostname>fedora.invalid</hostname>
+ <osinfo>fedora14</osinfo>
+ <mountpoints>
+ <mountpoint dev="/dev/mapper/luks-ROOTUUID">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ </mountpoints>
+ <filesystems>
+ <filesystem dev="/dev/mapper/luks-ROOTUUID">
+ <type>ext2</type>
+ <label>ROOT</label>
+ <uuid>01234567-0123-0123-0123-012345678902</uuid>
+ </filesystem>
+ <filesystem dev="/dev/sda1">
+ <type>ext2</type>
+ <label>BOOT</label>
+ <uuid>01234567-0123-0123-0123-012345678901</uuid>
+ </filesystem>
+ </filesystems>
+ <applications>
+ <application>
+ <name>basesystem</name>
+ <version>11</version>
+ <release>10.fc33</release>
+ <arch>noarch</arch>
+ <url>(none)</url>
+ <summary>The skeleton package which defines a simple Fedora system</summary>
+ <description>Basesystem defines the components of a basic Fedora system
+(for example, the package installation order to use during bootstrapping).
+Basesystem should be in every installation of a system, and it
+should never be removed.</description>
+ </application>
+ <application>
+ <name>bash</name>
+ <version>5.0.17</version>
+ <release>2.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://www.gnu.org/software/bash</url>
+ <summary>The GNU Bourne Again shell</summary>
+ <description>The GNU Bourne Again shell (Bash) is a shell or command language
+interpreter that is compatible with the Bourne shell (sh). Bash
+incorporates useful features from the Korn shell (ksh) and the C shell
+(csh). Most sh scripts can be run by bash without modification.</description>
+ </application>
+ <application>
+ <name>fedora-gpg-keys</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora RPM keys</summary>
+ <description>This package provides the RPM signature keys.</description>
+ </application>
+ <application>
+ <name>fedora-release</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora release files</summary>
+ <description>Fedora release files such as various /etc/ files that define the release
+and systemd preset files that determine which services are enabled by default.</description>
+ </application>
+ <application>
+ <name>fedora-release-common</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora release files</summary>
+ <description>Release files common to all Editions and Spins of Fedora</description>
+ </application>
+ <application>
+ <name>fedora-release-identity-basic</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Package providing the basic Fedora identity</summary>
+ <description>Provides the necessary files for a Fedora installation that is not identifying
+itself as a particular Edition or Spin.</description>
+ </application>
+ <application>
+ <name>fedora-repos</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora package repositories</summary>
+ <description>Fedora package repository files for yum and dnf along with gpg public keys.</description>
+ </application>
+ <application>
+ <name>filesystem</name>
+ <version>3.14</version>
+ <release>3.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://pagure.io/filesystem</url>
+ <summary>The basic directory layout for a Linux system</summary>
+ <description>The filesystem package is one of the basic packages that is installed
+on a Linux system. Filesystem contains the basic directory layout
+for a Linux operating system, including the correct permissions for
+the directories.</description>
+ </application>
+ <application>
+ <name>glibc</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>The GNU libc libraries</summary>
+ <description>The glibc package contains standard libraries which are used by
+multiple programs on the system. In order to save disk space and
+memory, as well as to make upgrading easier, common system code is
+kept in one place and shared between programs. This particular package
+contains the most important sets of shared libraries: the standard C
+library and the standard math library. Without these two libraries, a
+Linux system will not function.</description>
+ </application>
+ <application>
+ <name>glibc-all-langpacks</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>All language packs for glibc.</summary>
+ </application>
+ <application>
+ <name>glibc-common</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>Common binaries and locale data for glibc</summary>
+ <description>The glibc-common package includes common binaries for the GNU libc
+libraries, as well as national language (locale) support.</description>
+ </application>
+ <application>
+ <name>gpg-pubkey</name>
+ <version>9570ff31</version>
+ <release>5e3006fb</release>
+ <arch>(none)</arch>
+ <url>(none)</url>
+ <summary>Fedora (33) <fedora-33-primary@fedoraproject.org> public key</summary>
+ <description>-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: rpm-4.16.1.2 (NSS-3)
+
+mQINBF4wBvsBEADQmcGbVUbDRUoXADReRmOOEMeydHghtKC9uRs9YNpGYZIB+bie
+bGYZmflQayfh/wEpO2W/IZfGpHPL42V7SbyvqMjwNls/fnXsCtf4LRofNK8Qd9fN
+kYargc9R7BEz/mwXKMiRQVx+DzkmqGWy2gq4iD0/mCyf5FdJCE40fOWoIGJXaOI1
+Tz1vWqKwLS5T0dfmi9U4Tp/XsKOZGvN8oi5h0KmqFk7LEZr1MXarhi2Va86sgxsF
+QcZEKfu5tgD0r00vXzikoSjn3qA5JW5FW07F1pGP4bF5f9J3CZbQyOjTSWMmmfTm
+2d2BURWzaDiJN9twY2yjzkoOMuPdXXvovg7KxLcQerKT+FbKbq8DySJX2rnOA77k
+UG4c9BGf/L1uBkAT8dpHLk6Uf5BfmypxUkydSWT1xfTDnw1MqxO0MsLlAHOR3J7c
+oW9kLcOLuCQn1hBEwfZv7VSWBkGXSmKfp0LLIxAFgRtv+Dh+rcMMRdJgKr1V3FU+
+rZ1+ZAfYiBpQJFPjv70vx+rGEgS801D3PJxBZUEy4Ic4ZYaKNhK9x9PRQuWcIBuW
+6eTe/6lKWZeyxCumLLdiS75mF2oTcBaWeoc3QxrPRV15eDKeYJMbhnUai/7lSrhs
+EWCkKR1RivgF4slYmtNE5ZPGZ/d61zjwn2xi4xNJVs8q9WRPMpHp0vCyMwARAQAB
+tDFGZWRvcmEgKDMzKSA8ZmVkb3JhLTMzLXByaW1hcnlAZmVkb3JhcHJvamVjdC5v
+cmc+iQI4BBMBAgAiBQJeMAb7AhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK
+CRBJ/XdJlXD/MZm2D/9kriL43vd3+0DNMeA82n2v9mSR2PQqKny39xNlYPyy/1yZ
+P/KXoa4NYSCA971LSd7lv4n/h5bEKgGHxZfttfOzOnWMVSSTfjRyM/df/NNzTUEV
+7ORA5GW18g8PEtS7uRxVBf3cLvWu5q+8jmqES5HqTAdGVcuIFQeBXFN8Gy1Jinuz
+AH8rJSdkUeZ0cehWbERq80BWM9dhad5dW+/+Gv0foFBvP15viwhWqajr8V0B8es+
+2/tHI0k86FAujV5i0rrXl5UOoLilO57QQNDZH/qW9GsHwVI+2yecLstpUNLq+EZC
+GqTZCYoxYRpl0gAMbDLztSL/8Bc0tJrCRG3tavJotFYlgUK60XnXlQzRkh9rgsfT
+EXbQifWdQMMogzjCJr0hzJ+V1d0iozdUxB2ZEgTjukOvatkB77DY1FPZRkSFIQs+
+fdcjazDIBLIxwJu5QwvTNW8lOLnJ46g4sf1WJoUdNTbR0BaC7HHj1inVWi0p7IuN
+66EPGzJOSjLK+vW+J0ncPDEgLCV74RF/0nR5fVTdrmiopPrzFuguHf9S9gYI3Zun
+Yl8FJUu4kRO6JPPTicUXWX+8XZmE94aK14RCJL23nOSi8T1eW8JLW43dCBRO8QUE
+Aso1t2pypm/1zZexJdOV8yGME3g5l2W6PLgpz58DBECgqc/kda+VWgEAp7rO2A==
+=EPL3
+-----END PGP PUBLIC KEY BLOCK-----
+</description>
+ </application>
+ <application>
+ <name>libgcc</name>
+ <version>10.2.1</version>
+ <release>9.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://gcc.gnu.org</url>
+ <summary>GCC version 10 shared support library</summary>
+ <description>This package contains GCC shared support library which is needed
+e.g. for exception handling support.</description>
+ </application>
+ <application>
+ <name>ncurses-base</name>
+ <version>6.2</version>
+ <release>3.20200222.fc33</release>
+ <arch>noarch</arch>
+ <url>https://invisible-island.net/ncurses/ncurses.html</url>
+ <summary>Descriptions of common terminals</summary>
+ <description>This package contains descriptions of common terminals. Other terminal
+descriptions are included in the ncurses-term package.</description>
+ </application>
+ <application>
+ <name>ncurses-libs</name>
+ <version>6.2</version>
+ <release>3.20200222.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://invisible-island.net/ncurses/ncurses.html</url>
+ <summary>Ncurses libraries</summary>
+ <description>The curses library routines are a terminal-independent method of
+updating character screens with reasonable optimization. The ncurses
+(new curses) library is a freely distributable replacement for the
+discontinued 4.4 BSD classic curses library.
+
+This package contains the ncurses libraries.</description>
+ </application>
+ <application>
+ <name>setup</name>
+ <version>2.13.7</version>
+ <release>2.fc33</release>
+ <arch>noarch</arch>
+ <url>https://pagure.io/setup/</url>
+ <summary>A set of system configuration and setup files</summary>
+ <description>The setup package contains a set of important system configuration and
+setup files, such as passwd, group, and profile.</description>
+ </application>
+ <application>
+ <name>tzdata</name>
+ <version>2021a</version>
+ <release>1.fc33</release>
+ <arch>noarch</arch>
+ <url>https://www.iana.org/time-zones</url>
+ <summary>Timezone data</summary>
+ <description>This package contains data files with rules for various timezones around
+the world.</description>
+ </application>
+ </applications>
+ </operatingsystem>
+</operatingsystems>
+++ /dev/null
-<?xml version="1.0"?>
-<operatingsystems>
- <operatingsystem>
- <root>/dev/VG/Root</root>
- <name>linux</name>
- <arch>x86_64</arch>
- <distro>fedora</distro>
- <product_name>Fedora release 14 (Phony)</product_name>
- <major_version>14</major_version>
- <minor_version>0</minor_version>
- <package_format>rpm</package_format>
- <package_management>yum</package_management>
- <hostname>fedora.invalid</hostname>
- <osinfo>fedora14</osinfo>
- <mountpoints>
- <mountpoint dev="/dev/VG/Root">/</mountpoint>
- <mountpoint dev="/dev/sda1">/boot</mountpoint>
- </mountpoints>
- <filesystems>
- <filesystem dev="/dev/VG/Root">
- <type>ext2</type>
- <label>ROOT</label>
- <uuid>01234567-0123-0123-0123-012345678902</uuid>
- </filesystem>
- <filesystem dev="/dev/sda1">
- <type>ext2</type>
- <label>BOOT</label>
- <uuid>01234567-0123-0123-0123-012345678901</uuid>
- </filesystem>
- </filesystems>
- <applications>
- <application>
- <name>basesystem</name>
- <version>11</version>
- <release>10.fc33</release>
- <arch>noarch</arch>
- <url>(none)</url>
- <summary>The skeleton package which defines a simple Fedora system</summary>
- <description>Basesystem defines the components of a basic Fedora system
-(for example, the package installation order to use during bootstrapping).
-Basesystem should be in every installation of a system, and it
-should never be removed.</description>
- </application>
- <application>
- <name>bash</name>
- <version>5.0.17</version>
- <release>2.fc33</release>
- <arch>x86_64</arch>
- <url>https://www.gnu.org/software/bash</url>
- <summary>The GNU Bourne Again shell</summary>
- <description>The GNU Bourne Again shell (Bash) is a shell or command language
-interpreter that is compatible with the Bourne shell (sh). Bash
-incorporates useful features from the Korn shell (ksh) and the C shell
-(csh). Most sh scripts can be run by bash without modification.</description>
- </application>
- <application>
- <name>fedora-gpg-keys</name>
- <version>33</version>
- <release>3</release>
- <arch>noarch</arch>
- <url>https://fedoraproject.org/</url>
- <summary>Fedora RPM keys</summary>
- <description>This package provides the RPM signature keys.</description>
- </application>
- <application>
- <name>fedora-release</name>
- <version>33</version>
- <release>3</release>
- <arch>noarch</arch>
- <url>https://fedoraproject.org/</url>
- <summary>Fedora release files</summary>
- <description>Fedora release files such as various /etc/ files that define the release
-and systemd preset files that determine which services are enabled by default.</description>
- </application>
- <application>
- <name>fedora-release-common</name>
- <version>33</version>
- <release>3</release>
- <arch>noarch</arch>
- <url>https://fedoraproject.org/</url>
- <summary>Fedora release files</summary>
- <description>Release files common to all Editions and Spins of Fedora</description>
- </application>
- <application>
- <name>fedora-release-identity-basic</name>
- <version>33</version>
- <release>3</release>
- <arch>noarch</arch>
- <url>https://fedoraproject.org/</url>
- <summary>Package providing the basic Fedora identity</summary>
- <description>Provides the necessary files for a Fedora installation that is not identifying
-itself as a particular Edition or Spin.</description>
- </application>
- <application>
- <name>fedora-repos</name>
- <version>33</version>
- <release>3</release>
- <arch>noarch</arch>
- <url>https://fedoraproject.org/</url>
- <summary>Fedora package repositories</summary>
- <description>Fedora package repository files for yum and dnf along with gpg public keys.</description>
- </application>
- <application>
- <name>filesystem</name>
- <version>3.14</version>
- <release>3.fc33</release>
- <arch>x86_64</arch>
- <url>https://pagure.io/filesystem</url>
- <summary>The basic directory layout for a Linux system</summary>
- <description>The filesystem package is one of the basic packages that is installed
-on a Linux system. Filesystem contains the basic directory layout
-for a Linux operating system, including the correct permissions for
-the directories.</description>
- </application>
- <application>
- <name>glibc</name>
- <version>2.32</version>
- <release>4.fc33</release>
- <arch>x86_64</arch>
- <url>http://www.gnu.org/software/glibc/</url>
- <summary>The GNU libc libraries</summary>
- <description>The glibc package contains standard libraries which are used by
-multiple programs on the system. In order to save disk space and
-memory, as well as to make upgrading easier, common system code is
-kept in one place and shared between programs. This particular package
-contains the most important sets of shared libraries: the standard C
-library and the standard math library. Without these two libraries, a
-Linux system will not function.</description>
- </application>
- <application>
- <name>glibc-all-langpacks</name>
- <version>2.32</version>
- <release>4.fc33</release>
- <arch>x86_64</arch>
- <url>http://www.gnu.org/software/glibc/</url>
- <summary>All language packs for glibc.</summary>
- </application>
- <application>
- <name>glibc-common</name>
- <version>2.32</version>
- <release>4.fc33</release>
- <arch>x86_64</arch>
- <url>http://www.gnu.org/software/glibc/</url>
- <summary>Common binaries and locale data for glibc</summary>
- <description>The glibc-common package includes common binaries for the GNU libc
-libraries, as well as national language (locale) support.</description>
- </application>
- <application>
- <name>gpg-pubkey</name>
- <version>9570ff31</version>
- <release>5e3006fb</release>
- <arch>(none)</arch>
- <url>(none)</url>
- <summary>Fedora (33) <fedora-33-primary@fedoraproject.org> public key</summary>
- <description>-----BEGIN PGP PUBLIC KEY BLOCK-----
-Version: rpm-4.16.1.2 (NSS-3)
-
-mQINBF4wBvsBEADQmcGbVUbDRUoXADReRmOOEMeydHghtKC9uRs9YNpGYZIB+bie
-bGYZmflQayfh/wEpO2W/IZfGpHPL42V7SbyvqMjwNls/fnXsCtf4LRofNK8Qd9fN
-kYargc9R7BEz/mwXKMiRQVx+DzkmqGWy2gq4iD0/mCyf5FdJCE40fOWoIGJXaOI1
-Tz1vWqKwLS5T0dfmi9U4Tp/XsKOZGvN8oi5h0KmqFk7LEZr1MXarhi2Va86sgxsF
-QcZEKfu5tgD0r00vXzikoSjn3qA5JW5FW07F1pGP4bF5f9J3CZbQyOjTSWMmmfTm
-2d2BURWzaDiJN9twY2yjzkoOMuPdXXvovg7KxLcQerKT+FbKbq8DySJX2rnOA77k
-UG4c9BGf/L1uBkAT8dpHLk6Uf5BfmypxUkydSWT1xfTDnw1MqxO0MsLlAHOR3J7c
-oW9kLcOLuCQn1hBEwfZv7VSWBkGXSmKfp0LLIxAFgRtv+Dh+rcMMRdJgKr1V3FU+
-rZ1+ZAfYiBpQJFPjv70vx+rGEgS801D3PJxBZUEy4Ic4ZYaKNhK9x9PRQuWcIBuW
-6eTe/6lKWZeyxCumLLdiS75mF2oTcBaWeoc3QxrPRV15eDKeYJMbhnUai/7lSrhs
-EWCkKR1RivgF4slYmtNE5ZPGZ/d61zjwn2xi4xNJVs8q9WRPMpHp0vCyMwARAQAB
-tDFGZWRvcmEgKDMzKSA8ZmVkb3JhLTMzLXByaW1hcnlAZmVkb3JhcHJvamVjdC5v
-cmc+iQI4BBMBAgAiBQJeMAb7AhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK
-CRBJ/XdJlXD/MZm2D/9kriL43vd3+0DNMeA82n2v9mSR2PQqKny39xNlYPyy/1yZ
-P/KXoa4NYSCA971LSd7lv4n/h5bEKgGHxZfttfOzOnWMVSSTfjRyM/df/NNzTUEV
-7ORA5GW18g8PEtS7uRxVBf3cLvWu5q+8jmqES5HqTAdGVcuIFQeBXFN8Gy1Jinuz
-AH8rJSdkUeZ0cehWbERq80BWM9dhad5dW+/+Gv0foFBvP15viwhWqajr8V0B8es+
-2/tHI0k86FAujV5i0rrXl5UOoLilO57QQNDZH/qW9GsHwVI+2yecLstpUNLq+EZC
-GqTZCYoxYRpl0gAMbDLztSL/8Bc0tJrCRG3tavJotFYlgUK60XnXlQzRkh9rgsfT
-EXbQifWdQMMogzjCJr0hzJ+V1d0iozdUxB2ZEgTjukOvatkB77DY1FPZRkSFIQs+
-fdcjazDIBLIxwJu5QwvTNW8lOLnJ46g4sf1WJoUdNTbR0BaC7HHj1inVWi0p7IuN
-66EPGzJOSjLK+vW+J0ncPDEgLCV74RF/0nR5fVTdrmiopPrzFuguHf9S9gYI3Zun
-Yl8FJUu4kRO6JPPTicUXWX+8XZmE94aK14RCJL23nOSi8T1eW8JLW43dCBRO8QUE
-Aso1t2pypm/1zZexJdOV8yGME3g5l2W6PLgpz58DBECgqc/kda+VWgEAp7rO2A==
-=EPL3
------END PGP PUBLIC KEY BLOCK-----
-</description>
- </application>
- <application>
- <name>libgcc</name>
- <version>10.2.1</version>
- <release>9.fc33</release>
- <arch>x86_64</arch>
- <url>http://gcc.gnu.org</url>
- <summary>GCC version 10 shared support library</summary>
- <description>This package contains GCC shared support library which is needed
-e.g. for exception handling support.</description>
- </application>
- <application>
- <name>ncurses-base</name>
- <version>6.2</version>
- <release>3.20200222.fc33</release>
- <arch>noarch</arch>
- <url>https://invisible-island.net/ncurses/ncurses.html</url>
- <summary>Descriptions of common terminals</summary>
- <description>This package contains descriptions of common terminals. Other terminal
-descriptions are included in the ncurses-term package.</description>
- </application>
- <application>
- <name>ncurses-libs</name>
- <version>6.2</version>
- <release>3.20200222.fc33</release>
- <arch>x86_64</arch>
- <url>https://invisible-island.net/ncurses/ncurses.html</url>
- <summary>Ncurses libraries</summary>
- <description>The curses library routines are a terminal-independent method of
-updating character screens with reasonable optimization. The ncurses
-(new curses) library is a freely distributable replacement for the
-discontinued 4.4 BSD classic curses library.
-
-This package contains the ncurses libraries.</description>
- </application>
- <application>
- <name>setup</name>
- <version>2.13.7</version>
- <release>2.fc33</release>
- <arch>noarch</arch>
- <url>https://pagure.io/setup/</url>
- <summary>A set of system configuration and setup files</summary>
- <description>The setup package contains a set of important system configuration and
-setup files, such as passwd, group, and profile.</description>
- </application>
- <application>
- <name>tzdata</name>
- <version>2021a</version>
- <release>1.fc33</release>
- <arch>noarch</arch>
- <url>https://www.iana.org/time-zones</url>
- <summary>Timezone data</summary>
- <description>This package contains data files with rules for various timezones around
-the world.</description>
- </application>
- </applications>
- </operatingsystem>
-</operatingsystems>
--- /dev/null
+<?xml version="1.0"?>
+<operatingsystems>
+ <operatingsystem>
+ <root>/dev/VG/Root</root>
+ <name>linux</name>
+ <arch>x86_64</arch>
+ <distro>fedora</distro>
+ <product_name>Fedora release 14 (Phony)</product_name>
+ <major_version>14</major_version>
+ <minor_version>0</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <hostname>fedora.invalid</hostname>
+ <osinfo>fedora14</osinfo>
+ <mountpoints>
+ <mountpoint dev="/dev/VG/Root">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ </mountpoints>
+ <filesystems>
+ <filesystem dev="/dev/VG/Root">
+ <type>ext2</type>
+ <label>ROOT</label>
+ <uuid>01234567-0123-0123-0123-012345678902</uuid>
+ </filesystem>
+ <filesystem dev="/dev/sda1">
+ <type>ext2</type>
+ <label>BOOT</label>
+ <uuid>01234567-0123-0123-0123-012345678901</uuid>
+ </filesystem>
+ </filesystems>
+ <applications>
+ <application>
+ <name>basesystem</name>
+ <version>11</version>
+ <release>10.fc33</release>
+ <arch>noarch</arch>
+ <url>(none)</url>
+ <summary>The skeleton package which defines a simple Fedora system</summary>
+ <description>Basesystem defines the components of a basic Fedora system
+(for example, the package installation order to use during bootstrapping).
+Basesystem should be in every installation of a system, and it
+should never be removed.</description>
+ </application>
+ <application>
+ <name>bash</name>
+ <version>5.0.17</version>
+ <release>2.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://www.gnu.org/software/bash</url>
+ <summary>The GNU Bourne Again shell</summary>
+ <description>The GNU Bourne Again shell (Bash) is a shell or command language
+interpreter that is compatible with the Bourne shell (sh). Bash
+incorporates useful features from the Korn shell (ksh) and the C shell
+(csh). Most sh scripts can be run by bash without modification.</description>
+ </application>
+ <application>
+ <name>fedora-gpg-keys</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora RPM keys</summary>
+ <description>This package provides the RPM signature keys.</description>
+ </application>
+ <application>
+ <name>fedora-release</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora release files</summary>
+ <description>Fedora release files such as various /etc/ files that define the release
+and systemd preset files that determine which services are enabled by default.</description>
+ </application>
+ <application>
+ <name>fedora-release-common</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora release files</summary>
+ <description>Release files common to all Editions and Spins of Fedora</description>
+ </application>
+ <application>
+ <name>fedora-release-identity-basic</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Package providing the basic Fedora identity</summary>
+ <description>Provides the necessary files for a Fedora installation that is not identifying
+itself as a particular Edition or Spin.</description>
+ </application>
+ <application>
+ <name>fedora-repos</name>
+ <version>33</version>
+ <release>3</release>
+ <arch>noarch</arch>
+ <url>https://fedoraproject.org/</url>
+ <summary>Fedora package repositories</summary>
+ <description>Fedora package repository files for yum and dnf along with gpg public keys.</description>
+ </application>
+ <application>
+ <name>filesystem</name>
+ <version>3.14</version>
+ <release>3.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://pagure.io/filesystem</url>
+ <summary>The basic directory layout for a Linux system</summary>
+ <description>The filesystem package is one of the basic packages that is installed
+on a Linux system. Filesystem contains the basic directory layout
+for a Linux operating system, including the correct permissions for
+the directories.</description>
+ </application>
+ <application>
+ <name>glibc</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>The GNU libc libraries</summary>
+ <description>The glibc package contains standard libraries which are used by
+multiple programs on the system. In order to save disk space and
+memory, as well as to make upgrading easier, common system code is
+kept in one place and shared between programs. This particular package
+contains the most important sets of shared libraries: the standard C
+library and the standard math library. Without these two libraries, a
+Linux system will not function.</description>
+ </application>
+ <application>
+ <name>glibc-all-langpacks</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>All language packs for glibc.</summary>
+ </application>
+ <application>
+ <name>glibc-common</name>
+ <version>2.32</version>
+ <release>4.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://www.gnu.org/software/glibc/</url>
+ <summary>Common binaries and locale data for glibc</summary>
+ <description>The glibc-common package includes common binaries for the GNU libc
+libraries, as well as national language (locale) support.</description>
+ </application>
+ <application>
+ <name>gpg-pubkey</name>
+ <version>9570ff31</version>
+ <release>5e3006fb</release>
+ <arch>(none)</arch>
+ <url>(none)</url>
+ <summary>Fedora (33) <fedora-33-primary@fedoraproject.org> public key</summary>
+ <description>-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: rpm-4.16.1.2 (NSS-3)
+
+mQINBF4wBvsBEADQmcGbVUbDRUoXADReRmOOEMeydHghtKC9uRs9YNpGYZIB+bie
+bGYZmflQayfh/wEpO2W/IZfGpHPL42V7SbyvqMjwNls/fnXsCtf4LRofNK8Qd9fN
+kYargc9R7BEz/mwXKMiRQVx+DzkmqGWy2gq4iD0/mCyf5FdJCE40fOWoIGJXaOI1
+Tz1vWqKwLS5T0dfmi9U4Tp/XsKOZGvN8oi5h0KmqFk7LEZr1MXarhi2Va86sgxsF
+QcZEKfu5tgD0r00vXzikoSjn3qA5JW5FW07F1pGP4bF5f9J3CZbQyOjTSWMmmfTm
+2d2BURWzaDiJN9twY2yjzkoOMuPdXXvovg7KxLcQerKT+FbKbq8DySJX2rnOA77k
+UG4c9BGf/L1uBkAT8dpHLk6Uf5BfmypxUkydSWT1xfTDnw1MqxO0MsLlAHOR3J7c
+oW9kLcOLuCQn1hBEwfZv7VSWBkGXSmKfp0LLIxAFgRtv+Dh+rcMMRdJgKr1V3FU+
+rZ1+ZAfYiBpQJFPjv70vx+rGEgS801D3PJxBZUEy4Ic4ZYaKNhK9x9PRQuWcIBuW
+6eTe/6lKWZeyxCumLLdiS75mF2oTcBaWeoc3QxrPRV15eDKeYJMbhnUai/7lSrhs
+EWCkKR1RivgF4slYmtNE5ZPGZ/d61zjwn2xi4xNJVs8q9WRPMpHp0vCyMwARAQAB
+tDFGZWRvcmEgKDMzKSA8ZmVkb3JhLTMzLXByaW1hcnlAZmVkb3JhcHJvamVjdC5v
+cmc+iQI4BBMBAgAiBQJeMAb7AhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK
+CRBJ/XdJlXD/MZm2D/9kriL43vd3+0DNMeA82n2v9mSR2PQqKny39xNlYPyy/1yZ
+P/KXoa4NYSCA971LSd7lv4n/h5bEKgGHxZfttfOzOnWMVSSTfjRyM/df/NNzTUEV
+7ORA5GW18g8PEtS7uRxVBf3cLvWu5q+8jmqES5HqTAdGVcuIFQeBXFN8Gy1Jinuz
+AH8rJSdkUeZ0cehWbERq80BWM9dhad5dW+/+Gv0foFBvP15viwhWqajr8V0B8es+
+2/tHI0k86FAujV5i0rrXl5UOoLilO57QQNDZH/qW9GsHwVI+2yecLstpUNLq+EZC
+GqTZCYoxYRpl0gAMbDLztSL/8Bc0tJrCRG3tavJotFYlgUK60XnXlQzRkh9rgsfT
+EXbQifWdQMMogzjCJr0hzJ+V1d0iozdUxB2ZEgTjukOvatkB77DY1FPZRkSFIQs+
+fdcjazDIBLIxwJu5QwvTNW8lOLnJ46g4sf1WJoUdNTbR0BaC7HHj1inVWi0p7IuN
+66EPGzJOSjLK+vW+J0ncPDEgLCV74RF/0nR5fVTdrmiopPrzFuguHf9S9gYI3Zun
+Yl8FJUu4kRO6JPPTicUXWX+8XZmE94aK14RCJL23nOSi8T1eW8JLW43dCBRO8QUE
+Aso1t2pypm/1zZexJdOV8yGME3g5l2W6PLgpz58DBECgqc/kda+VWgEAp7rO2A==
+=EPL3
+-----END PGP PUBLIC KEY BLOCK-----
+</description>
+ </application>
+ <application>
+ <name>libgcc</name>
+ <version>10.2.1</version>
+ <release>9.fc33</release>
+ <arch>x86_64</arch>
+ <url>http://gcc.gnu.org</url>
+ <summary>GCC version 10 shared support library</summary>
+ <description>This package contains GCC shared support library which is needed
+e.g. for exception handling support.</description>
+ </application>
+ <application>
+ <name>ncurses-base</name>
+ <version>6.2</version>
+ <release>3.20200222.fc33</release>
+ <arch>noarch</arch>
+ <url>https://invisible-island.net/ncurses/ncurses.html</url>
+ <summary>Descriptions of common terminals</summary>
+ <description>This package contains descriptions of common terminals. Other terminal
+descriptions are included in the ncurses-term package.</description>
+ </application>
+ <application>
+ <name>ncurses-libs</name>
+ <version>6.2</version>
+ <release>3.20200222.fc33</release>
+ <arch>x86_64</arch>
+ <url>https://invisible-island.net/ncurses/ncurses.html</url>
+ <summary>Ncurses libraries</summary>
+ <description>The curses library routines are a terminal-independent method of
+updating character screens with reasonable optimization. The ncurses
+(new curses) library is a freely distributable replacement for the
+discontinued 4.4 BSD classic curses library.
+
+This package contains the ncurses libraries.</description>
+ </application>
+ <application>
+ <name>setup</name>
+ <version>2.13.7</version>
+ <release>2.fc33</release>
+ <arch>noarch</arch>
+ <url>https://pagure.io/setup/</url>
+ <summary>A set of system configuration and setup files</summary>
+ <description>The setup package contains a set of important system configuration and
+setup files, such as passwd, group, and profile.</description>
+ </application>
+ <application>
+ <name>tzdata</name>
+ <version>2021a</version>
+ <release>1.fc33</release>
+ <arch>noarch</arch>
+ <url>https://www.iana.org/time-zones</url>
+ <summary>Timezone data</summary>
+ <description>This package contains data files with rules for various timezones around
+the world.</description>
+ </application>
+ </applications>
+ </operatingsystem>
+</operatingsystems>
guestfs_h *g;
int read_only = 1;
-int live = 0;
int verbose = 0;
int keys_from_stdin = 0;
int echo_keys = 0;
*/
assert (read_only == 1);
assert (inspector == 1);
- assert (live == 0);
/* Must be no extra arguments on the command line. */
if (optind != argc) {
--- /dev/null
+#!/bin/bash -
+# libguestfs virt-inspector test script
+# Copyright (C) 2012-2020 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# Test that virt-inspector can work on encrypted images when the
+# right password is supplied.
+#
+# Regression test for https://bugzilla.redhat.com/show_bug.cgi?id=1658126
+
+set -e
+set -x
+
+$TEST_FUNCTIONS
+skip_if_skipped
+
+# This test requires libguestfs >= 1.47.3. Just check the minor
+# number because this is a development branch so we can expect
+# everyone to be at the latest version.
+if [ "$(guestfish version | grep minor | awk '{print $2}')" -lt 47 ]; then
+ echo "$0: test skipped because this requires libguestfs >= 1.47.3"
+ exit 77
+fi
+
+f=../test-data/phony-guests/fedora-luks-on-lvm.img
+keys=(--key /dev/VG/Root:key:FEDORA-Root
+ --key /dev/VG/LV1:key:FEDORA-LV1
+ --key /dev/VG/LV2:key:FEDORA-LV2
+ --key /dev/VG/LV3:key:FEDORA-LV3)
+
+# Ignore zero-sized file.
+if [ -s "$f" ]; then
+ uuid_root=$(guestfish --ro -i -a "$f" "${keys[@]}" luks-uuid /dev/VG/Root)
+ b=$(basename "$f")
+ $VG virt-inspector "${keys[@]}" --format=raw -a "$f" > "actual-$b.xml"
+ # Check the generated output validate the schema.
+ $XMLLINT --noout --relaxng "$srcdir/virt-inspector.rng" "actual-$b.xml"
+ # This 'diff' command will fail (because of -e option) if there
+ # are any differences.
+ sed -e "s/ROOTUUID/$uuid_root/" < "$srcdir/expected-$b.xml" \
+ | diff -u - "actual-$b.xml"
+fi
+++ /dev/null
-#!/bin/bash -
-# libguestfs virt-inspector test script
-# Copyright (C) 2012-2020 Red Hat Inc.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program 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 General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-# Test that virt-inspector can work on encrypted images when the
-# right password is supplied.
-#
-# Regression test for https://bugzilla.redhat.com/show_bug.cgi?id=1602353
-
-set -e
-set -x
-
-$TEST_FUNCTIONS
-skip_if_skipped
-
-f=../test-data/phony-guests/fedora-luks.img
-
-# Ignore zero-sized file.
-if [ -s "$f" ]; then
- b=$(basename "$f")
- echo FEDORA |
- $VG virt-inspector --keys-from-stdin --format=raw -a "$f" > "actual-$b.xml"
- # Check the generated output validate the schema.
- $XMLLINT --noout --relaxng "$srcdir/virt-inspector.rng" "actual-$b.xml"
- # This 'diff' command will fail (because of -e option) if there
- # are any differences.
- diff -ur $diff_ignore "$srcdir/expected-$b.xml" "actual-$b.xml"
-fi
--- /dev/null
+#!/bin/bash -
+# libguestfs virt-inspector test script
+# Copyright (C) 2012-2020 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+# Test that virt-inspector can work on encrypted images when the
+# right password is supplied.
+#
+# Regression test for https://bugzilla.redhat.com/show_bug.cgi?id=1602353
+
+set -e
+set -x
+
+$TEST_FUNCTIONS
+skip_if_skipped
+
+f=../test-data/phony-guests/fedora-lvm-on-luks.img
+
+# Ignore zero-sized file.
+if [ -s "$f" ]; then
+ b=$(basename "$f")
+ echo FEDORA |
+ $VG virt-inspector --keys-from-stdin --format=raw -a "$f" > "actual-$b.xml"
+ # Check the generated output validate the schema.
+ $XMLLINT --noout --relaxng "$srcdir/virt-inspector.rng" "actual-$b.xml"
+ # This 'diff' command will fail (because of -e option) if there
+ # are any differences.
+ diff -ur $diff_ignore "$srcdir/expected-$b.xml" "actual-$b.xml"
+fi
<value>freedos</value>
<value>frugalware</value>
<value>gentoo</value>
+ <value>kalilinux</value>
+ <value>kylin</value>
<value>linuxmint</value>
<value>mageia</value>
<value>mandriva</value>
<value>meego</value>
+ <value>msdos</value>
<value>neokylin</value>
<value>netbsd</value>
<value>openbsd</value>
[],
[enable_ocaml=yes])
-dnl OCaml >= 4.02 is required.
-ocaml_ver_str=4.02
+dnl OCaml >= 4.04 is required.
+ocaml_ver_str=4.04
ocaml_min_major=4
-ocaml_min_minor=2
+ocaml_min_minor=4
AC_MSG_CHECKING([if OCaml version >= $ocaml_ver_str])
ocaml_major="`echo $OCAMLVERSION | $AWK -F. '{print $1}'`"
ocaml_minor="`echo $OCAMLVERSION | $AWK -F. '{print $2}' | sed 's/^0//'`"
OCAML_PKG_gettext=no
OCAML_PKG_ounit2=no
ounit_is_v2=no
-have_Bytes_module=no
AS_IF([test "x$OCAMLC" != "xno"],[
# Create common/mlgettext/common_gettext.ml gettext functions or stubs.
if test "x$OCAML_PKG_ounit2" != "xno"; then
AC_CHECK_OCAML_MODULE(ounit_is_v2,[OUnit.OUnit2],OUnit2,[+ounit2])
fi
-
- # Check if we have the 'Bytes' module. If not (OCaml < 4.02) then
- # we need to create a compatibility module.
- # AC_CHECK_OCAML_MODULE is a bit broken, so open code this test.
- AC_MSG_CHECKING([for OCaml module Bytes])
- rm -f conftest.ml
- echo 'let s = Bytes.empty' > conftest.ml
- if $OCAMLC -c conftest.ml >&5 2>&5 ; then
- AC_MSG_RESULT([yes])
- have_Bytes_module=yes
- else
- AC_MSG_RESULT([not found])
- have_Bytes_module=no
- fi
])
AM_CONDITIONAL([HAVE_OCAML_PKG_GETTEXT],
[test "x$OCAML_PKG_gettext" != "xno"])
])
dnl Flags we want to pass to every OCaml compiler call.
-OCAML_WARN_ERROR="-warn-error CDEFLMPSUVYZX+52-3"
+OCAML_WARN_ERROR="-warn-error +C+D+E+F+L+M+P+S+U+V+Y+Z+X+52-3-6 -w -6"
AC_SUBST([OCAML_WARN_ERROR])
OCAML_FLAGS="-g -annot $safe_string_option"
AC_SUBST([OCAML_FLAGS])
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
guestfs_h *g;
const char *libvirt_uri;
-int live;
int read_only;
int verbose;
int in_guestfish = 0;
btrfs_available=
fi
-# UML backend doesn't support qcow2.
-if [ "$(guestfish get-backend)" != "uml" ]; then
- qcow2_supported=yes
-fi
-
declare -a choices
# Return a random element from the array 'choices'.
fi
type=`random_choice`
-if [ "$qcow2_supported" = "yes" ]; then
- choices=("" --format=raw --format=qcow2)
- format=`random_choice`
-else
- format="--format=raw"
-fi
+choices=("" --format=raw --format=qcow2)
+format=`random_choice`
choices=(--partition --partition=gpt --partition=mbr)
partition=`random_choice`
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
DIST_SUBDIRS = $(SUBDIRS)
am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
=item B<--blocksize>
-This parameter sets the sector size of the disk image. It affects all
-explicitly added subsequent disks after this parameter. Using
-I<--blocksize> with no argument switches the disk sector size to the default
-value which is usually 512 bytes. See also
-L<guestfs(3)/guestfs_add_drive_opts>.
+This parameter sets the sector size of the disk image. It affects all explicitly added subsequent disks after this parameter. Using I<--blocksize> with no argument switches the disk sector size to the default value which is usually 512 bytes. See also L<guestfs(3)/guestfs_add_drive_opts>.
=item B<--append-line> FILE:LINE
-Append a single line of text to the C<FILE>. If the file does not already
-end with a newline, then one is added before the appended line. Also a
-newline is added to the end of the C<LINE> string automatically.
+Append a single line of text to the C<FILE>. If the file does not already end with a newline, then one is added before the appended line. Also a newline is added to the end of the C<LINE> string automatically.
For example (assuming ordinary shell quoting) this command:
--append-line '/etc/hosts:10.0.0.1 foo'
-will add either C<10.0.0.1 foo⏎> or C<⏎10.0.0.1 foo⏎> to the file, the
-latter only if the existing file does not already end with a newline.
+will add either C<10.0.0.1 foo⏎> or C<⏎10.0.0.1 foo⏎> to the file, the latter only if the existing file does not already end with a newline.
-C<⏎> represents a newline character, which is guessed by looking at the
-existing content of the file, so this command does the right thing for files
-using Unix or Windows line endings. It also works for empty or non-existent
-files.
+C<⏎> represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. It also works for empty or non-existent files.
To insert several lines, use the same option several times:
Change the permissions of C<FILE> to C<PERMISSIONS>.
-I<Note>: C<PERMISSIONS> by default would be decimal, unless you prefix it
-with C<0> to get octal, ie. use C<0700> not C<700>.
+I<Note>: C<PERMISSIONS> by default would be decimal, unless you prefix it with C<0> to get octal, ie. use C<0700> not C<700>.
=item B<--commands-from-file> FILENAME
Read the customize commands from a file, one (and its arguments) each line.
-Each line contains a single customization command and its arguments, for
-example:
+Each line contains a single customization command and its arguments, for example:
delete /some/file
install some-package
password some-user:password:its-new-password
-Empty lines are ignored, and lines starting with C<#> are comments and are
-ignored as well. Furthermore, arguments can be spread across multiple
-lines, by adding a C<\> (continuation character) at the of a line, for
-example
+Empty lines are ignored, and lines starting with C<#> are comments and are ignored as well. Furthermore, arguments can be spread across multiple lines, by adding a C<\> (continuation character) at the of a line, for example
edit /some/file:\
s/^OPT=.*/OPT=ok/
-The commands are handled in the same order as they are in the file, as if
-they were specified as I<--delete /some/file> on the command line.
+The commands are handled in the same order as they are in the file, as if they were specified as I<--delete /some/file> on the command line.
=item B<--copy> SOURCE:DEST
=item B<--copy-in> LOCALPATH:REMOTEDIR
-Copy local files or directories recursively into the disk image, placing
-them in the directory C<REMOTEDIR> (which must exist).
+Copy local files or directories recursively into the disk image, placing them in the directory C<REMOTEDIR> (which must exist).
Wildcards cannot be used.
=item B<--delete> PATH
-Delete a file from the guest. Or delete a directory (and all its contents,
-recursively).
+Delete a file from the guest. Or delete a directory (and all its contents, recursively).
-You can use shell glob characters in the specified path. Be careful to
-escape glob characters from the host shell, if that is required. For
-example:
+You can use shell glob characters in the specified path. Be careful to escape glob characters from the host shell, if that is required. For example:
virt-customize --delete '/var/log/*.log'.
=item B<--firstboot> SCRIPT
-Install C<SCRIPT> inside the guest, so that when the guest first boots up,
-the script runs (as root, late in the boot process).
+Install C<SCRIPT> inside the guest, so that when the guest first boots up, the script runs (as root, late in the boot process).
The script is automatically chmod +x after installation in the guest.
-The alternative version I<--firstboot-command> is the same, but it
-conveniently wraps the command up in a single line script for you.
+The alternative version I<--firstboot-command> is the same, but it conveniently wraps the command up in a single line script for you.
-You can have multiple I<--firstboot> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--firstboot> options. They run in the same order that they appear on the command line.
-Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more
-information and caveats about the first boot scripts.
+Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more information and caveats about the first boot scripts.
See also I<--run>.
=item B<--firstboot-command> 'CMD+ARGS'
-Run command (and arguments) inside the guest when the guest first boots up
-(as root, late in the boot process).
+Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process).
-You can have multiple I<--firstboot> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--firstboot> options. They run in the same order that they appear on the command line.
-Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more
-information and caveats about the first boot scripts.
+Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more information and caveats about the first boot scripts.
See also I<--run>.
=item B<--firstboot-install> PKG,PKG..
-Install the named packages (a comma-separated list). These are installed
-when the guest first boots using the guest’s package manager (eg. apt, yum,
-etc.) and the guest’s network connection.
+Install the named packages (a comma-separated list). These are installed when the guest first boots using the guest’s package manager (eg. apt, yum, etc.) and the guest’s network connection.
-For an overview on the different ways to install packages, see
-L<virt-builder(1)/INSTALLING PACKAGES>.
+For an overview on the different ways to install packages, see L<virt-builder(1)/INSTALLING PACKAGES>.
=item B<--hostname> HOSTNAME
-Set the hostname of the guest to C<HOSTNAME>. You can use a dotted
-hostname.domainname (FQDN) if you want.
+Set the hostname of the guest to C<HOSTNAME>. You can use a dotted hostname.domainname (FQDN) if you want.
=item B<--install> PKG,PKG..
-Install the named packages (a comma-separated list). These are installed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.) and the host’s network connection.
+Install the named packages (a comma-separated list). These are installed during the image build using the guest’s package manager (eg. apt, yum, etc.) and the host’s network connection.
-For an overview on the different ways to install packages, see
-L<virt-builder(1)/INSTALLING PACKAGES>.
+For an overview on the different ways to install packages, see L<virt-builder(1)/INSTALLING PACKAGES>.
See also I<--update>, I<--uninstall>.
=item B<--link> TARGET:LINK[:LINK..]
-Create symbolic link(s) in the guest, starting at C<LINK> and pointing at
-C<TARGET>.
+Create symbolic link(s) in the guest, starting at C<LINK> and pointing at C<TARGET>.
=item B<--mkdir> DIR
Create a directory in the guest.
-This uses S<C<mkdir -p>> so any intermediate directories are created, and it
-also works if the directory already exists.
+This uses S<C<mkdir -p>> so any intermediate directories are created, and it also works if the directory already exists.
=item B<--move> SOURCE:DEST
=item B<--no-logfile>
-Scrub C<builder.log> (log file from build commands) from the image after
-building is complete. If you don't want to reveal precisely how the image
-was built, use this option.
+Scrub C<builder.log> (log file from build commands) from the image after building is complete. If you don't want to reveal precisely how the image was built, use this option.
See also: L</LOG FILE>.
=item B<--password> USER:SELECTOR
-Set the password for C<USER>. (Note this option does I<not> create the user
-account).
+Set the password for C<USER>. (Note this option does I<not> create the user account).
-See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR>
-field, and also how to set up user accounts.
+See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR> field, and also how to set up user accounts.
=item B<--password-crypto> md5|sha256|sha512
-When the virt tools change or set a password in the guest, this option sets
-the password encryption of that password to C<md5>, C<sha256> or C<sha512>.
+When the virt tools change or set a password in the guest, this option sets the password encryption of that password to C<md5>, C<sha256> or C<sha512>.
-C<sha256> and C<sha512> require glibc E<ge> 2.7 (check crypt(3) inside the
-guest).
+C<sha256> and C<sha512> require glibc E<ge> 2.7 (check crypt(3) inside the guest).
-C<md5> will work with relatively old Linux guests (eg. RHEL 3), but is not
-secure against modern attacks.
+C<md5> will work with relatively old Linux guests (eg. RHEL 3), but is not secure against modern attacks.
-The default is C<sha512> unless libguestfs detects an old guest that didn't
-have support for SHA-512, in which case it will use C<md5>. You can
-override libguestfs by specifying this option.
+The default is C<sha512> unless libguestfs detects an old guest that didn't have support for SHA-512, in which case it will use C<md5>. You can override libguestfs by specifying this option.
-Note this does not change the default password encryption used by the guest
-when you create new user accounts inside the guest. If you want to do that,
-then you should use the I<--edit> option to modify
-C</etc/sysconfig/authconfig> (Fedora, RHEL) or C</etc/pam.d/common-password>
-(Debian, Ubuntu).
+Note this does not change the default password encryption used by the guest when you create new user accounts inside the guest. If you want to do that, then you should use the I<--edit> option to modify C</etc/sysconfig/authconfig> (Fedora, RHEL) or C</etc/pam.d/common-password> (Debian, Ubuntu).
=item B<--root-password> SELECTOR
Set the root password.
-See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR>
-field, and also how to set up user accounts.
+See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR> field, and also how to set up user accounts.
-Note: In virt-builder, if you I<don't> set I<--root-password> then the guest
-is given a I<random> root password.
+Note: In virt-builder, if you I<don't> set I<--root-password> then the guest is given a I<random> root password.
=item B<--run> SCRIPT
-Run the shell script (or any program) called C<SCRIPT> on the disk image.
-The script runs virtualized inside a small appliance, chrooted into the
-guest filesystem.
+Run the shell script (or any program) called C<SCRIPT> on the disk image. The script runs virtualized inside a small appliance, chrooted into the guest filesystem.
The script is automatically chmod +x.
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. ISO files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (I<--attach>). You can also
-upload data files (I<--upload>).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. ISO files) as another way to provide data (eg. software packages) to the script without needing a network connection (I<--attach>). You can also upload data files (I<--upload>).
-You can have multiple I<--run> options. They run in the same order that
-they appear on the command line.
+You can have multiple I<--run> options. They run in the same order that they appear on the command line.
See also: I<--firstboot>, I<--attach>, I<--upload>.
=item B<--run-command> 'CMD+ARGS'
-Run the command and arguments on the disk image. The command runs
-virtualized inside a small appliance, chrooted into the guest filesystem.
+Run the command and arguments on the disk image. The command runs virtualized inside a small appliance, chrooted into the guest filesystem.
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. ISO files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (I<--attach>). You can also
-upload data files (I<--upload>).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. ISO files) as another way to provide data (eg. software packages) to the script without needing a network connection (I<--attach>). You can also upload data files (I<--upload>).
-You can have multiple I<--run-command> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--run-command> options. They run in the same order that they appear on the command line.
See also: I<--firstboot>, I<--attach>, I<--upload>.
Relabel files in the guest so that they have the correct SELinux label.
-This will attempt to relabel files immediately, but if the operation fails
-this will instead touch F</.autorelabel> on the image to schedule a relabel
-operation for the next time the image boots.
+This will attempt to relabel files immediately, but if the operation fails this will instead touch F</.autorelabel> on the image to schedule a relabel operation for the next time the image boots.
You should only use this option for guests which support SELinux.
Attach to a pool using C<subscription-manager>.
-See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the
-C<SELECTOR> field.
+See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the C<SELECTOR> field.
=item B<--sm-credentials> SELECTOR
Set the credentials for C<subscription-manager>.
-See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the
-C<SELECTOR> field.
+See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the C<SELECTOR> field.
=item B<--sm-register>
=item B<--ssh-inject> USER[:SELECTOR]
-Inject an ssh key so the given C<USER> will be able to log in over ssh
-without supplying a password. The C<USER> must exist already in the guest.
+Inject an ssh key so the given C<USER> will be able to log in over ssh without supplying a password. The C<USER> must exist already in the guest.
See L<virt-builder(1)/SSH KEYS> for the format of the C<SELECTOR> field.
-You can have multiple I<--ssh-inject> options, for different users and also
-for more keys for each user.
+You can have multiple I<--ssh-inject> options, for different users and also for more keys for each user.
=item B<--timezone> TIMEZONE
-Set the default timezone of the guest to C<TIMEZONE>. Use a location string
-like C<Europe/London>
+Set the default timezone of the guest to C<TIMEZONE>. Use a location string like C<Europe/London>
=item B<--touch> FILE
=item B<--truncate> FILE
-This command truncates C<FILE> to a zero-length file. The file must exist
-already.
+This command truncates C<FILE> to a zero-length file. The file must exist already.
=item B<--truncate-recursive> PATH
=item B<--uninstall> PKG,PKG..
-Uninstall the named packages (a comma-separated list). These are removed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.). Dependent packages may also need to be uninstalled to satisfy the
-request.
+Uninstall the named packages (a comma-separated list). These are removed during the image build using the guest’s package manager (eg. apt, yum, etc.). Dependent packages may also need to be uninstalled to satisfy the request.
See also I<--install>, I<--update>.
=item B<--update>
-Do the equivalent of C<yum update>, C<apt-get upgrade>, or whatever command
-is required to update the packages already installed in the template to
-their latest versions.
+Do the equivalent of C<yum update>, C<apt-get upgrade>, or whatever command is required to update the packages already installed in the template to their latest versions.
See also I<--install>, I<--uninstall>.
=item B<--upload> FILE:DEST
-Upload local file C<FILE> to destination C<DEST> in the disk image. File
-owner and permissions from the original are preserved, so you should set
-them to what you want them to be in the disk image.
+Upload local file C<FILE> to destination C<DEST> in the disk image. File owner and permissions from the original are preserved, so you should set them to what you want them to be in the disk image.
-C<DEST> could be the final filename. This can be used to rename the file on
-upload.
+C<DEST> could be the final filename. This can be used to rename the file on upload.
-If C<DEST> is a directory name (which must already exist in the guest) then
-the file is uploaded into that directory, and it keeps the same name as on
-the local filesystem.
+If C<DEST> is a directory name (which must already exist in the guest) then the file is uploaded into that directory, and it keeps the same name as on the local filesystem.
See also: I<--mkdir>, I<--delete>, I<--scrub>.
--- /dev/null
+
+=head1 名前
+
+guestfs-tools-release-notes - guestfs tools release Notes
+
+=head1 RELEASE NOTES FOR GUESTFS TOOLS 1.48
+
+These are the release notes for guestfs tools stable release 1.48. This describes the major changes since 1.46.
+
+Guestfs tools 1.48.0 was released on B<14 March 2022>.
+
+=head2 virt-builder
+
+New templates: C<alma-8.5>, C<centosstream-8>, C<debian-11>, C<fedora-34>, C<fedora-34> (armv7l), C<fedora-35> C<fedora-35> (aarch64) (Lars Kaiser, Stef Walter).
+
+New fedora-34 (armv7l) template is built to use UEFI.
+
+=head2 virt-customize
+
+The yescrypt password hashing method is now supported (Björn Esser).
+
+=head2 virt-inspector
+
+Recognise C<kalilinux>, C<kylin> and C<msdos> operating systems / Linux distros (Laszlo Ersek).
+
+Inspection of LUKS encrypted filesystems placed directly on logical volumes is now supported, but you will need libguestfs E<ge> 1.48 (Laszlo Ersek).
+
+=head2 virt-sysprep
+
+Add a new default operation called C<net-nmconn> which removes NetworkManager connection profiles (Laszlo Ersek).
+
+=head2 virt-win-reg
+
+C<virt-win-reg --version> now prints both the version of guestfs tools and the libguestfs library that it is linked with.
+
+=head2 Common changes
+
+All OCaml tools now suppress line wrapping when output is redirected to a file (to make it easier to parse logs with external programs). There is a new I<--wrap> option which can be used to reenable line wrapping to files if needed (Laszlo Ersek).
+
+=head2 Build changes
+
+Multiple fixes to make it easier to build against either the system installed libguestfs or a locally built libguestfs (Laszlo Ersek).
+
+Fix multiple OCaml warnings. Remove some deprecated OCaml features. We now require OCaml E<ge> 4.04.
+
+Multiple fixes to valgrind support for glibc 2.35, OCaml 4.13 and libvirt 7.7. C<make check-valgrind> should now work.
+
+=head2 内部
+
+New OCaml C<On_exit> module (from libguestfs-common) is used instead of custom on-exit and signal handling.
+
+=head2 バグ修正
+
+=over 4
+
+=item L<https://bugzilla.redhat.com/2003706>
+
+virt-install armv7 guest on aarch64 host doesn't work, no LPAE support and no PCI devices
+
+=item L<https://bugzilla.redhat.com/1995391>
+
+RFE: virt-inspector fails to detect the distro and applications on Kylin-Desktop-V10 image
+
+=item L<https://bugzilla.redhat.com/1980922>
+
+virt-sysprep doesn't cleanup NetworkManager connection files
+
+=item L<https://bugzilla.redhat.com/1961160>
+
+The version is incorrect when running 'virt-win-reg --version'
+
+=item L<https://bugzilla.redhat.com/1820221>
+
+Log lines wrapping make log parsing difficult
+
+=item L<https://bugzilla.redhat.com/1658126>
+
+Virt-v2v can't convert guest using LUKS-on-LV
+
+=item L<https://bugzilla.redhat.com/1633328>
+
+Armv7 guest fails to boot with qemu-3.0.0-1
+
+=back
+
+=head1 関連項目
+
+L<http://libguestfs.org/>
+
+=head1 著者
+
+=begin コメント
+
+git shortlog -s v1.46.0..
+
+=end コメント
+
+=over 4
+
+=item Björn Esser
+
+=item Lars Kaiser
+
+=item Laszlo Ersek
+
+=item Richard W.M. Jones
+
+=item Stef Walter
+
+=back
+
+=head1 COPYRIGHT
+
+Copyright (C) 2009-2022 Red Hat Inc.
+
=item B<--key> SELECTOR
-Specify a key for LUKS, to automatically open a LUKS device when using the
-inspection. C<ID> can be either the libguestfs device name, or the UUID of
-the LUKS device.
+Specify a key for LUKS, to automatically open a LUKS device when using the inspection. C<ID> can be either the libguestfs device name, or the UUID of the LUKS device.
=over 4
=item B<--keys-from-stdin>
-Read key or passphrase parameters from stdin. The default is to try to read
-passphrases from the user by opening F</dev/tty>.
+Read key or passphrase parameters from stdin. The default is to try to read passphrases from the user by opening F</dev/tty>.
-If there are multiple encrypted devices then you may need to supply multiple
-keys on stdin, one per line.
+If there are multiple encrypted devices then you may need to supply multiple keys on stdin, one per line.
=item B<--append-line> FILE:LINE (see C<customize> below)
-Append a single line of text to the C<FILE>. If the file does not already
-end with a newline, then one is added before the appended line. Also a
-newline is added to the end of the C<LINE> string automatically.
+Append a single line of text to the C<FILE>. If the file does not already end with a newline, then one is added before the appended line. Also a newline is added to the end of the C<LINE> string automatically.
For example (assuming ordinary shell quoting) this command:
--append-line '/etc/hosts:10.0.0.1 foo'
-will add either C<10.0.0.1 foo⏎> or C<⏎10.0.0.1 foo⏎> to the file, the
-latter only if the existing file does not already end with a newline.
+will add either C<10.0.0.1 foo⏎> or C<⏎10.0.0.1 foo⏎> to the file, the latter only if the existing file does not already end with a newline.
-C<⏎> represents a newline character, which is guessed by looking at the
-existing content of the file, so this command does the right thing for files
-using Unix or Windows line endings. It also works for empty or non-existent
-files.
+C<⏎> represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. It also works for empty or non-existent files.
To insert several lines, use the same option several times:
Change the permissions of C<FILE> to C<PERMISSIONS>.
-I<Note>: C<PERMISSIONS> by default would be decimal, unless you prefix it
-with C<0> to get octal, ie. use C<0700> not C<700>.
+I<Note>: C<PERMISSIONS> by default would be decimal, unless you prefix it with C<0> to get octal, ie. use C<0700> not C<700>.
=item B<--commands-from-file> FILENAME (see C<customize> below)
Read the customize commands from a file, one (and its arguments) each line.
-Each line contains a single customization command and its arguments, for
-example:
+Each line contains a single customization command and its arguments, for example:
delete /some/file
install some-package
password some-user:password:its-new-password
-Empty lines are ignored, and lines starting with C<#> are comments and are
-ignored as well. Furthermore, arguments can be spread across multiple
-lines, by adding a C<\> (continuation character) at the of a line, for
-example
+Empty lines are ignored, and lines starting with C<#> are comments and are ignored as well. Furthermore, arguments can be spread across multiple lines, by adding a C<\> (continuation character) at the of a line, for example
edit /some/file:\
s/^OPT=.*/OPT=ok/
-The commands are handled in the same order as they are in the file, as if
-they were specified as I<--delete /some/file> on the command line.
+The commands are handled in the same order as they are in the file, as if they were specified as I<--delete /some/file> on the command line.
=item B<--copy> SOURCE:DEST (see C<customize> below)
=item B<--copy-in> LOCALPATH:REMOTEDIR (see C<customize> below)
-Copy local files or directories recursively into the disk image, placing
-them in the directory C<REMOTEDIR> (which must exist).
+Copy local files or directories recursively into the disk image, placing them in the directory C<REMOTEDIR> (which must exist).
Wildcards cannot be used.
=item B<--delete> PATH (see C<customize> below)
-Delete a file from the guest. Or delete a directory (and all its contents,
-recursively).
+Delete a file from the guest. Or delete a directory (and all its contents, recursively).
-You can use shell glob characters in the specified path. Be careful to
-escape glob characters from the host shell, if that is required. For
-example:
+You can use shell glob characters in the specified path. Be careful to escape glob characters from the host shell, if that is required. For example:
virt-customize --delete '/var/log/*.log'.
=item B<--firstboot> SCRIPT (see C<customize> below)
-Install C<SCRIPT> inside the guest, so that when the guest first boots up,
-the script runs (as root, late in the boot process).
+Install C<SCRIPT> inside the guest, so that when the guest first boots up, the script runs (as root, late in the boot process).
The script is automatically chmod +x after installation in the guest.
-The alternative version I<--firstboot-command> is the same, but it
-conveniently wraps the command up in a single line script for you.
+The alternative version I<--firstboot-command> is the same, but it conveniently wraps the command up in a single line script for you.
-You can have multiple I<--firstboot> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--firstboot> options. They run in the same order that they appear on the command line.
-Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more
-information and caveats about the first boot scripts.
+Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more information and caveats about the first boot scripts.
See also I<--run>.
=item B<--firstboot-command> 'CMD+ARGS' (see C<customize> below)
-Run command (and arguments) inside the guest when the guest first boots up
-(as root, late in the boot process).
+Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process).
-You can have multiple I<--firstboot> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--firstboot> options. They run in the same order that they appear on the command line.
-Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more
-information and caveats about the first boot scripts.
+Please take a look at L<virt-builder(1)/FIRST BOOT SCRIPTS> for more information and caveats about the first boot scripts.
See also I<--run>.
=item B<--firstboot-install> PKG,PKG.. (see C<customize> below)
-Install the named packages (a comma-separated list). These are installed
-when the guest first boots using the guest’s package manager (eg. apt, yum,
-etc.) and the guest’s network connection.
+Install the named packages (a comma-separated list). These are installed when the guest first boots using the guest’s package manager (eg. apt, yum, etc.) and the guest’s network connection.
-For an overview on the different ways to install packages, see
-L<virt-builder(1)/INSTALLING PACKAGES>.
+For an overview on the different ways to install packages, see L<virt-builder(1)/INSTALLING PACKAGES>.
=item B<--hostname> HOSTNAME (see C<customize> below)
-Set the hostname of the guest to C<HOSTNAME>. You can use a dotted
-hostname.domainname (FQDN) if you want.
+Set the hostname of the guest to C<HOSTNAME>. You can use a dotted hostname.domainname (FQDN) if you want.
=item B<--install> PKG,PKG.. (see C<customize> below)
-Install the named packages (a comma-separated list). These are installed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.) and the host’s network connection.
+Install the named packages (a comma-separated list). These are installed during the image build using the guest’s package manager (eg. apt, yum, etc.) and the host’s network connection.
-For an overview on the different ways to install packages, see
-L<virt-builder(1)/INSTALLING PACKAGES>.
+For an overview on the different ways to install packages, see L<virt-builder(1)/INSTALLING PACKAGES>.
See also I<--update>, I<--uninstall>.
=item B<--keep-user-accounts> USERS (see C<user-account> below)
-The user accounts to be kept in the guest. The value of this option is a
-list of user names separated by comma, where specifying an user means it is
-going to be kept. For example:
+The user accounts to be kept in the guest. The value of this option is a list of user names separated by comma, where specifying an user means it is going to be kept. For example:
--keep-user-accounts mary
=item B<--link> TARGET:LINK[:LINK..] (see C<customize> below)
-Create symbolic link(s) in the guest, starting at C<LINK> and pointing at
-C<TARGET>.
+Create symbolic link(s) in the guest, starting at C<LINK> and pointing at C<TARGET>.
=item B<--mkdir> DIR (see C<customize> below)
Create a directory in the guest.
-This uses S<C<mkdir -p>> so any intermediate directories are created, and it
-also works if the directory already exists.
+This uses S<C<mkdir -p>> so any intermediate directories are created, and it also works if the directory already exists.
=item B<--move> SOURCE:DEST (see C<customize> below)
=item B<--no-logfile> (see C<customize> below)
-Scrub C<builder.log> (log file from build commands) from the image after
-building is complete. If you don't want to reveal precisely how the image
-was built, use this option.
+Scrub C<builder.log> (log file from build commands) from the image after building is complete. If you don't want to reveal precisely how the image was built, use this option.
See also: L</LOG FILE>.
=item B<--password> USER:SELECTOR (see C<customize> below)
-Set the password for C<USER>. (Note this option does I<not> create the user
-account).
+Set the password for C<USER>. (Note this option does I<not> create the user account).
-See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR>
-field, and also how to set up user accounts.
+See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR> field, and also how to set up user accounts.
=item B<--password-crypto> md5|sha256|sha512 (see C<customize> below)
-When the virt tools change or set a password in the guest, this option sets
-the password encryption of that password to C<md5>, C<sha256> or C<sha512>.
+When the virt tools change or set a password in the guest, this option sets the password encryption of that password to C<md5>, C<sha256> or C<sha512>.
-C<sha256> and C<sha512> require glibc E<ge> 2.7 (check crypt(3) inside the
-guest).
+C<sha256> and C<sha512> require glibc E<ge> 2.7 (check crypt(3) inside the guest).
-C<md5> will work with relatively old Linux guests (eg. RHEL 3), but is not
-secure against modern attacks.
+C<md5> will work with relatively old Linux guests (eg. RHEL 3), but is not secure against modern attacks.
-The default is C<sha512> unless libguestfs detects an old guest that didn't
-have support for SHA-512, in which case it will use C<md5>. You can
-override libguestfs by specifying this option.
+The default is C<sha512> unless libguestfs detects an old guest that didn't have support for SHA-512, in which case it will use C<md5>. You can override libguestfs by specifying this option.
-Note this does not change the default password encryption used by the guest
-when you create new user accounts inside the guest. If you want to do that,
-then you should use the I<--edit> option to modify
-C</etc/sysconfig/authconfig> (Fedora, RHEL) or C</etc/pam.d/common-password>
-(Debian, Ubuntu).
+Note this does not change the default password encryption used by the guest when you create new user accounts inside the guest. If you want to do that, then you should use the I<--edit> option to modify C</etc/sysconfig/authconfig> (Fedora, RHEL) or C</etc/pam.d/common-password> (Debian, Ubuntu).
=item B<--remove-user-accounts> USERS (see C<user-account> below)
-The user accounts to be removed from the guest. The value of this option is
-a list of user names separated by comma, where specifying an user means it
-is going to be removed. For example:
+The user accounts to be removed from the guest. The value of this option is a list of user names separated by comma, where specifying an user means it is going to be removed. For example:
--remove-user-accounts bob,eve
Set the root password.
-See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR>
-field, and also how to set up user accounts.
+See L<virt-builder(1)/USERS AND PASSWORDS> for the format of the C<SELECTOR> field, and also how to set up user accounts.
-Note: In virt-builder, if you I<don't> set I<--root-password> then the guest
-is given a I<random> root password.
+Note: In virt-builder, if you I<don't> set I<--root-password> then the guest is given a I<random> root password.
=item B<--run> SCRIPT (see C<customize> below)
-Run the shell script (or any program) called C<SCRIPT> on the disk image.
-The script runs virtualized inside a small appliance, chrooted into the
-guest filesystem.
+Run the shell script (or any program) called C<SCRIPT> on the disk image. The script runs virtualized inside a small appliance, chrooted into the guest filesystem.
The script is automatically chmod +x.
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. ISO files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (I<--attach>). You can also
-upload data files (I<--upload>).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. ISO files) as another way to provide data (eg. software packages) to the script without needing a network connection (I<--attach>). You can also upload data files (I<--upload>).
-You can have multiple I<--run> options. They run in the same order that
-they appear on the command line.
+You can have multiple I<--run> options. They run in the same order that they appear on the command line.
See also: I<--firstboot>, I<--attach>, I<--upload>.
=item B<--run-command> 'CMD+ARGS' (see C<customize> below)
-Run the command and arguments on the disk image. The command runs
-virtualized inside a small appliance, chrooted into the guest filesystem.
+Run the command and arguments on the disk image. The command runs virtualized inside a small appliance, chrooted into the guest filesystem.
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. ISO files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (I<--attach>). You can also
-upload data files (I<--upload>).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. ISO files) as another way to provide data (eg. software packages) to the script without needing a network connection (I<--attach>). You can also upload data files (I<--upload>).
-You can have multiple I<--run-command> options. They run in the same order
-that they appear on the command line.
+You can have multiple I<--run-command> options. They run in the same order that they appear on the command line.
See also: I<--firstboot>, I<--attach>, I<--upload>.
=item B<--script> SCRIPT (see C<script> below)
-Run the named C<SCRIPT> (a shell script or program) against the guest. The
-script can be any program on the host. The script’s current directory will
-be the guest’s root directory.
+Run the named C<SCRIPT> (a shell script or program) against the guest. The script can be any program on the host. The script’s current directory will be the guest’s root directory.
-B<Note:> If the script is not on the $PATH, then you must give the full
-absolute path to the script.
+B<Note:> If the script is not on the $PATH, then you must give the full absolute path to the script.
=item B<--scriptdir> SCRIPTDIR (see C<script> below)
-The mount point (an empty directory on the host) used when the C<script>
-operation is enabled and one or more scripts are specified using I<--script>
-parameter(s).
+The mount point (an empty directory on the host) used when the C<script> operation is enabled and one or more scripts are specified using I<--script> parameter(s).
B<Note:> C<SCRIPTDIR> B<must> be an absolute path.
-If I<--scriptdir> is not specified then a temporary mountpoint will be
-created.
+If I<--scriptdir> is not specified then a temporary mountpoint will be created.
=item B<--scrub> FILE (see C<customize> below)
Relabel files in the guest so that they have the correct SELinux label.
-This will attempt to relabel files immediately, but if the operation fails
-this will instead touch F</.autorelabel> on the image to schedule a relabel
-operation for the next time the image boots.
+This will attempt to relabel files immediately, but if the operation fails this will instead touch F</.autorelabel> on the image to schedule a relabel operation for the next time the image boots.
You should only use this option for guests which support SELinux.
Attach to a pool using C<subscription-manager>.
-See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the
-C<SELECTOR> field.
+See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the C<SELECTOR> field.
=item B<--sm-credentials> SELECTOR (see C<customize> below)
Set the credentials for C<subscription-manager>.
-See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the
-C<SELECTOR> field.
+See L<virt-builder(1)/SUBSCRIPTION-MANAGER> for the format of the C<SELECTOR> field.
=item B<--sm-register> (see C<customize> below)
=item B<--ssh-inject> USER[:SELECTOR] (see C<customize> below)
-Inject an ssh key so the given C<USER> will be able to log in over ssh
-without supplying a password. The C<USER> must exist already in the guest.
+Inject an ssh key so the given C<USER> will be able to log in over ssh without supplying a password. The C<USER> must exist already in the guest.
See L<virt-builder(1)/SSH KEYS> for the format of the C<SELECTOR> field.
-You can have multiple I<--ssh-inject> options, for different users and also
-for more keys for each user.
+You can have multiple I<--ssh-inject> options, for different users and also for more keys for each user.
=item B<--timezone> TIMEZONE (see C<customize> below)
-Set the default timezone of the guest to C<TIMEZONE>. Use a location string
-like C<Europe/London>
+Set the default timezone of the guest to C<TIMEZONE>. Use a location string like C<Europe/London>
=item B<--touch> FILE (see C<customize> below)
=item B<--truncate> FILE (see C<customize> below)
-This command truncates C<FILE> to a zero-length file. The file must exist
-already.
+This command truncates C<FILE> to a zero-length file. The file must exist already.
=item B<--truncate-recursive> PATH (see C<customize> below)
=item B<--uninstall> PKG,PKG.. (see C<customize> below)
-Uninstall the named packages (a comma-separated list). These are removed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.). Dependent packages may also need to be uninstalled to satisfy the
-request.
+Uninstall the named packages (a comma-separated list). These are removed during the image build using the guest’s package manager (eg. apt, yum, etc.). Dependent packages may also need to be uninstalled to satisfy the request.
See also I<--install>, I<--update>.
=item B<--update> (see C<customize> below)
-Do the equivalent of C<yum update>, C<apt-get upgrade>, or whatever command
-is required to update the packages already installed in the template to
-their latest versions.
+Do the equivalent of C<yum update>, C<apt-get upgrade>, or whatever command is required to update the packages already installed in the template to their latest versions.
See also I<--install>, I<--uninstall>.
=item B<--upload> FILE:DEST (see C<customize> below)
-Upload local file C<FILE> to destination C<DEST> in the disk image. File
-owner and permissions from the original are preserved, so you should set
-them to what you want them to be in the disk image.
+Upload local file C<FILE> to destination C<DEST> in the disk image. File owner and permissions from the original are preserved, so you should set them to what you want them to be in the disk image.
-C<DEST> could be the final filename. This can be used to rename the file on
-upload.
+C<DEST> could be the final filename. This can be used to rename the file on upload.
-If C<DEST> is a directory name (which must already exist in the guest) then
-the file is uploaded into that directory, and it keeps the same name as on
-the local filesystem.
+If C<DEST> is a directory name (which must already exist in the guest) then the file is uploaded into that directory, and it keeps the same name as on the local filesystem.
See also: I<--mkdir>, I<--delete>, I<--scrub>.
=back
-On Linux and Unix operating systems, only the following filesystems will be
-examined:
+On Linux and Unix operating systems, only the following filesystems will be examined:
=over 4
仮想マシンにおいて bash 履歴を削除します。
-ユーザー "root" および他のあらゆるユーザーのホームディレクトリーに C<.bash_history> ファイルを持つユーザーの bash
-履歴を削除します。
+ユーザー "root" および他のあらゆるユーザーのホームディレクトリーに C<.bash_history> ファイルを持つユーザーの bash 履歴を削除します。
=head3 Notes on bash-history
-Currently this only looks in C</root> and C</home/*> for home directories,
-so users with home directories in other locations won't have the bash
-history removed.
+Currently this only looks in C</root> and C</home/*> for home directories, so users with home directories in other locations won't have the bash history removed.
=head2 B<blkid-tab> *
Customize the guest.
-Customize the guest by providing L<virt-customize(1)> options for installing
-packages, editing files and so on.
+Customize the guest by providing L<virt-customize(1)> options for installing packages, editing files and so on.
=head2 B<dhcp-client-state> *
ファイアウォールルールを削除します。
-This removes custom firewall rules by removing C</etc/sysconfig/iptables> or
-custom firewalld configuration in C</etc/firewalld/*/*>.
+This removes custom firewall rules by removing C</etc/sysconfig/iptables> or custom firewalld configuration in C</etc/firewalld/*/*>.
-Note this is I<not> enabled by default since it may expose guests to
-exploits. Use with care.
+Note this is I<not> enabled by default since it may expose guests to exploits. Use with care.
=head2 B<flag-reconfiguration>
Flag the system for reconfiguration.
-For Linux guests, this touches C</.unconfigured>, which causes the first
-boot to interactively query the user for settings such as the root password
-and timezone.
+For Linux guests, this touches C</.unconfigured>, which causes the first boot to interactively query the user for settings such as the root password and timezone.
=head2 B<fs-uuids>
Change filesystem UUIDs.
-On guests and filesystem types where this is supported, new random UUIDs are
-generated and assigned to filesystems.
+On guests and filesystem types where this is supported, new random UUIDs are generated and assigned to filesystems.
=head3 Notes on fs-uuids
-The fs-uuids operation is disabled by default because it does not yet find
-and update all the places in the guest that use the UUIDs. For example
-C</etc/fstab> or the bootloader. Enabling this operation is more likely
-than not to make your guest unbootable.
+The fs-uuids operation is disabled by default because it does not yet find and update all the places in the guest that use the UUIDs. For example C</etc/fstab> or the bootloader. Enabling this operation is more likely than not to make your guest unbootable.
参照: L<https://bugzilla.redhat.com/show_bug.cgi?id=991641>
Remove the IPA files.
-Remove all the files related to an IPA (Identity, Policy, Audit) system.
-This effectively unenrolls the guest from an IPA server without interacting
-with it.
+Remove all the files related to an IPA (Identity, Policy, Audit) system. This effectively unenrolls the guest from an IPA server without interacting with it.
This operation does not run C<ipa-client>.
LVM2 の PV および VG の UUID を変更します。
-LVM2 物理ボリューム (PV) またはボリュームグループ (VG) を持つ Linux 仮想マシンにおいて、新しいランダムな UUID
-が生成され、これらの PV や VG に割り当てられます。
+LVM2 物理ボリューム (PV) またはボリュームグループ (VG) を持つ Linux 仮想マシンにおいて、新しいランダムな UUID が生成され、これらの PV や VG に割り当てられます。
=head2 B<machine-id> *
ローカルマシン ID を削除します。
-The machine ID is usually generated from a random source during system
-installation and stays constant for all subsequent boots. Optionally, for
-stateless systems it is generated during runtime at boot if it is found to
-be empty.
+The machine ID is usually generated from a random source during system installation and stays constant for all subsequent boots. Optionally, for stateless systems it is generated during runtime at boot if it is found to be empty.
=head2 B<mail-spool> *
Fedora および Red Hat Enterprise Linux に対して、これは C<ifcfg-*> ファイルから削除されます。
+=head2 B<net-nmconn> *
+
+Remove system-local NetworkManager connection profiles (keyfiles).
+
+On Fedora and Red Hat Enterprise Linux, remove the C</etc/NetworkManager/system-connections/*.nmconnection> files.
+
=head2 B<pacct-log> *
プロセス・アカウンティングのログファイルを削除します。
Remove host-specific RPM database files.
-Remove host-specific RPM database files and locks. RPM will recreate these
-files automatically if needed.
+Remove host-specific RPM database files and locks. RPM will recreate these files automatically if needed.
=head2 B<samba-db-log> *
仮想マシンに対して任意のスクリプトを実行します。
-The C<script> module lets you run arbitrary shell scripts or programs
-against the guest.
+The C<script> module lets you run arbitrary shell scripts or programs against the guest.
-Note this feature requires FUSE support. You may have to enable this in
-your host, for example by adding the current user to the C<fuse> group, or
-by loading a kernel module.
+Note this feature requires FUSE support. You may have to enable this in your host, for example by adding the current user to the C<fuse> group, or by loading a kernel module.
-Use one or more I<--script> parameters to specify scripts or programs that
-will be run against the guest.
+Use one or more I<--script> parameters to specify scripts or programs that will be run against the guest.
-The script or program is run with its current directory being the guest’s
-root directory, so relative paths should be used. For example: C<rm
-etc/resolv.conf> in the script would remove a Linux guest’s DNS
-configuration file, but C<rm /etc/resolv.conf> would (try to) remove the
-host’s file.
+The script or program is run with its current directory being the guest’s root directory, so relative paths should be used. For example: C<rm etc/resolv.conf> in the script would remove a Linux guest’s DNS configuration file, but C<rm /etc/resolv.conf> would (try to) remove the host’s file.
-Normally a temporary mount point for the guest is used, but you can choose a
-specific one by using the I<--scriptdir> parameter.
+Normally a temporary mount point for the guest is used, but you can choose a specific one by using the I<--scriptdir> parameter.
-B<Note:> This is different from I<--firstboot> scripts (which run in the
-context of the guest when it is booting first time). I<--script> scripts
-run on the host, not in the guest.
+B<Note:> This is different from I<--firstboot> scripts (which run in the context of the guest when it is booting first time). I<--script> scripts run on the host, not in the guest.
=head2 B<smolt-uuid> *
仮想マシンにある ".ssh" ディレクトリーを削除します。
-ユーザー "root" 、およびホームディレクトリーに C<.ssh> ディレクトリーがある他のすべてのユーザーの、C<.ssh>
-ディレクトリーを削除します。
+ユーザー "root" 、およびホームディレクトリーに C<.ssh> ディレクトリーがある他のすべてのユーザーの、C<.ssh> ディレクトリーを削除します。
=head3 Notes on ssh-userdir
-Currently this only looks in C</root> and C</home/*> for home directories,
-so users with home directories in other locations won't have the ssh files
-removed.
+Currently this only looks in C</root> and C</home/*> for home directories, so users with home directories in other locations won't have the ssh files removed.
=head2 B<sssd-db-log> *
udev persistent net ルールを削除します。
-Remove udev persistent net rules which map the guest’s existing MAC address
-to a fixed ethernet device (eg. eth0).
+Remove udev persistent net rules which map the guest’s existing MAC address to a fixed ethernet device (eg. eth0).
-仮想マシンをクローンした後、通常 MAC アドレスは変わります。古い MAC アドレスは古い名前（たとえば eth0）を占有するため、このことは新しい
-MAC アドレスが新しい名前（たとえば eth1）に割り当てられることを意味します。それは、一般的に好ましくありません。 udev の永続的な net
-ルールを削除することにより、これを避けます。
+仮想マシンをクローンした後、通常 MAC アドレスは変わります。古い MAC アドレスは古い名前（たとえば eth0）を占有するため、このことは新しい MAC アドレスが新しい名前（たとえば eth1）に割り当てられることを意味します。それは、一般的に好ましくありません。 udev の永続的な net ルールを削除することにより、これを避けます。
=head2 B<user-account>
仮想マシンにあるユーザーアカウントを削除します。
-By default remove all the user accounts and their home directories. The
-"root" account is not removed.
+By default remove all the user accounts and their home directories. The "root" account is not removed.
-See the I<--remove-user-accounts> parameter for a way to specify how to
-remove only some users, or to not remove some others.
+See the I<--remove-user-accounts> parameter for a way to specify how to remove only some users, or to not remove some others.
=head2 B<utmp> *
utmp ファイルを削除します。
-This file records who is currently logged in on a machine. In modern Linux
-distros it is stored in a ramdisk and hence not part of the virtual
-machine’s disk, but it was stored on disk in older distros.
+This file records who is currently logged in on a machine. In modern Linux distros it is stored in a ramdisk and hence not part of the virtual machine’s disk, but it was stored on disk in older distros.
=head2 B<yum-uuid> *
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-alignment-scan 1"
-.TH virt-alignment-scan 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-alignment-scan 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-古いオペレーティングシステムが自身をインストールするとき、パーティションツールが基礎となるストレージと一致しないセクターにパーティションを配置します
-(一般的に最初のパーティションはセクター \f(CW63\fR から始まります)。一致しないパーティションにより、必要以上に I/O
-を発生させるというオペレーティングシステムの問題を引き起こします。
+古いオペレーティングシステムが自身をインストールするとき、パーティションツールが基礎となるストレージと一致しないセクターにパーティションを配置します (一般的に最初のパーティションはセクター \f(CW63\fR から始まります)。一致しないパーティションにより、必要以上に I/O を発生させるというオペレーティングシステムの問題を引き起こします。
.PP
virt-alignment-scan ツールは、仮想マシンおよびディスクイメージにあるパーティションの配置を確認します。配置に問題があれば警告します。
.PP
-現在、配置の問題を修正するための仮想化ツールはありません。ゲストオペレーティングシステムを再インストールすることだけができます。以下の NetApp
-のドキュメントが、問題と取り得る解決策をまとめています:
-http://media.netapp.com/documents/tr\-3747.pdf
+現在、配置の問題を修正するための仮想化ツールはありません。ゲストオペレーティングシステムを再インストールすることだけができます。以下の NetApp のドキュメントが、問題と取り得る解決策をまとめています: http://media.netapp.com/documents/tr\-3747.pdf
.SH "出力"
.IX Header "出力"
このツールをディスクイメージにおいて直接実行するには、\fI\-a\fR オプションを使用します:
\& /dev/sdb1 65536 64K ok
.Ve
.PP
-すべての libvirt 仮想マシンをスキャンするには \fI\-a\fR や \fI\-d\fR オプションをつけずに virt-alignment-scan
-を実行します。
+すべての libvirt 仮想マシンをスキャンするには \fI\-a\fR や \fI\-d\fR オプションをつけずに virt-alignment-scan を実行します。
.PP
.Vb 4
\& # virt\-alignment\-scan
\& F16x64:/dev/sda3 526385152 2048K ok
.Ve
.PP
-出力は 4 つまたはそれより多い、空白区切りの項目から構成されます。プログラムからこれを構文解析する場合、最初の 4
-列のみが重要です。各項目は次のとおりです:
+出力は 4 つまたはそれより多い、空白区切りの項目から構成されます。プログラムからこれを構文解析する場合、最初の 4 列のみが重要です。各項目は次のとおりです:
.IP "1 列目" 4
.IX Item "1 列目"
-The device and partition name (eg. \fI/dev/sda1\fR meaning the first partition
-on the first block device).
+The device and partition name (eg. \fI/dev/sda1\fR meaning the first partition on the first block device).
.Sp
-すべての libvirt 仮想マシンを一覧表示するとき (\fI\-a\fR や \fI\-d\fR オプションなし)、この列は libvirt 名または \s-1UUID\s0
-が先頭につきます (\fI\-\-uuid\fR が指定されていると)。例: \f(CW\*(C`WinXP:/dev/sda1\*(C'\fR
+すべての libvirt 仮想マシンを一覧表示するとき (\fI\-a\fR や \fI\-d\fR オプションなし)、この列は libvirt 名または \s-1UUID\s0 が先頭につきます (\fI\-\-uuid\fR が指定されていると)。例: \f(CW\*(C`WinXP:/dev/sda1\*(C'\fR
.IP "2 列目" 4
.IX Item "2 列目"
パーティションの開始位置（バイト単位）
.IX Item "5 列目以降"
オプションの自由なテキスト説明。
.PP
-プログラムからの終了コードは、不適切に配置されたパーティションが見つかったかどうかに依存して変わります。以下の \*(L"終了ステータス\*(R"
-を参照してください。
+プログラムからの終了コードは、不適切に配置されたパーティションが見つかったかどうかに依存して変わります。以下の \*(L"終了ステータス\*(R" を参照してください。
.PP
出力なしで終了コードを欲しいならば、\fI\-q\fR オプションを使用してください。
.SH "オプション"
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-alignment\-scan \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-P\fR nr_threads" 4
.IX Item "-P nr_threads"
-Since libguestfs 1.22, virt-alignment-scan is multithreaded and examines
-guests in parallel. By default the number of threads to use is chosen based
-on the amount of free memory available at the time that virt-alignment-scan
-is started. You can force virt-alignment-scan to use at most \f(CW\*(C`nr_threads\*(C'\fR
-by using the \fI\-P\fR option.
+Since libguestfs 1.22, virt-alignment-scan is multithreaded and examines guests in parallel. By default the number of threads to use is chosen based on the amount of free memory available at the time that virt-alignment-scan is started. You can force virt-alignment-scan to use at most \f(CW\*(C`nr_threads\*(C'\fR by using the \fI\-P\fR option.
.Sp
-Note that \fI\-P 0\fR means to autodetect, and \fI\-P 1\fR means to use a single
-thread.
+Note that \fI\-P 0\fR means to autodetect, and \fI\-P 1\fR means to use a single thread.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
.IP "\fB\-\-quiet\fR" 4
.IX Item "--quiet"
.PD
-Don’t produce any output. Just set the exit code (see \*(L"\s-1EXIT STATUS\*(R"\s0
-below).
+Don’t produce any output. Just set the exit code (see \*(L"\s-1EXIT STATUS\*(R"\s0 below).
.IP "\fB\-\-uuid\fR" 4
.IX Item "--uuid"
-名前の代わりに \s-1UUID\s0 を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2
-つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
+名前の代わりに \s-1UUID\s0 を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2 つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
.Sp
-すべての libvirt 仮想マシンを一覧表示するとき (\fI\-a\fR や \fI\-d\fR オプションが指定されていないとき)、
-このオプションのみが適用されます。
+すべての libvirt 仮想マシンを一覧表示するとき (\fI\-a\fR や \fI\-d\fR オプションが指定されていないとき)、 このオプションのみが適用されます。
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.SH "推奨されるアライメント"
.IX Header "推奨されるアライメント"
-Windows 2008 および ca.2010 以前のLinux よりも古いオペレーティングシステムは、512 バイトのセクター容量でセクター 63
-に、第 1 パーティションの第1セクターを配置しなければいけません。これは古くからの障害によるものです。ドライブは \s-1BIOS\s0
-にシリンダー/ヘッド/セクター (\s-1CHS\s0) の配置を通知する必要があります。配置は最近のドライブにおいては意味がありませんが、必ずトラックあたり 63
-セクターを持つことをときどき通知します。そのため、オペレーティングシステムはセクター 63 にある、第 2 \*(L"トラック\*(R" の先頭にある第 1
-パーティションに置かれます。
+Windows 2008 および ca.2010 以前のLinux よりも古いオペレーティングシステムは、512 バイトのセクター容量でセクター 63 に、第 1 パーティションの第1セクターを配置しなければいけません。これは古くからの障害によるものです。ドライブは \s-1BIOS\s0 にシリンダー/ヘッド/セクター (\s-1CHS\s0) の配置を通知する必要があります。配置は最近のドライブにおいては意味がありませんが、必ずトラックあたり 63 セクターを持つことをときどき通知します。そのため、オペレーティングシステムはセクター 63 にある、第 2 \*(L"トラック\*(R" の先頭にある第 1 パーティションに置かれます。
.PP
ゲスト \s-1OS\s0 が仮想化されているとき、ホストオペレーティングシステムおよびハイパーバイザーは以下のどれかにアライメントされていることが好ましいでしょう。
.IP "\(bu" 4
.IP "\(bu" 4
4 K バイト
.Sp
-4K バイトの物理セクターを持つ新規ハードディスクにおけるローカルストレージ向け。 4K
-バイトのブロック容量を持つファイルシステムにおけるファイル形式のストレージ向け。もしくは、何種類かのネットワークストレージ（NAS）向け。
+4K バイトの物理セクターを持つ新規ハードディスクにおけるローカルストレージ向け。 4K バイトのブロック容量を持つファイルシステムにおけるファイル形式のストレージ向け。もしくは、何種類かのネットワークストレージ（NAS）向け。
.IP "\(bu" 4
64 K バイト
.Sp
\& ─ ┴─────────────────────────┴─────────────────────────┴ ─ ─
.Ve
.PP
-この例では、4K ブロックが読み込まれるたびに、ホストにある 2 つのブロックにアクセスする必要があります（そのため I/O が 2
-倍になります）。仮想マシンの 4K ブロックが書き込まれるとき、まず 2 つのホストブロックを読み込む必要があり、古いデータと新しいデータが結合され、2
-つのブロックが書き込まれます（4 倍の I/O）。
+この例では、4K ブロックが読み込まれるたびに、ホストにある 2 つのブロックにアクセスする必要があります（そのため I/O が 2 倍になります）。仮想マシンの 4K ブロックが書き込まれるとき、まず 2 つのホストブロックを読み込む必要があり、古いデータと新しいデータが結合され、2 つのブロックが書き込まれます（4 倍の I/O）。
.SS "Linux ホストブロック"
.IX Subsection "Linux ホストブロック"
新しいバージョンの Linux カーネルは、物理ブロック容量、論理ブロック容量および最小かつ推奨の I/O サイズを明らかにします。
\& 65536
.Ve
.PP
-NetApp は、最小の 4K I/O サイズより好ましい 512 バイトアクセスが可能です（しかし、非常に効率が悪いです）、しかし最適な I/O
-サイズは 64K です。
+NetApp は、最小の 4K I/O サイズより好ましい 512 バイトアクセスが可能です（しかし、非常に効率が悪いです）、しかし最適な I/O サイズは 64K です。
.PP
-これらの数字の意味に関する詳細は
-http://docs.redhat.com/docs/en\-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage\-iolimits.html
-を参照してください。
+これらの数字の意味に関する詳細は http://docs.redhat.com/docs/en\-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage\-iolimits.html を参照してください。
.PP
-[4K ドライブデータを提供してくれた Matt Booth に感謝します。NetApp のデータと追加情報を提供してくれた Mike Snitzer
-に感謝します。]
+[4K ドライブデータを提供してくれた Matt Booth に感謝します。NetApp のデータと追加情報を提供してくれた Mike Snitzer に感謝します。]
.SS "1 \s-1MB\s0 パーティションアライメント"
.IX Subsection "1 MB パーティションアライメント"
-Microsoft は Windows Server 2008 以降、すべてのパーティションに対してデフォルトのアライメントとして 1 \s-1MB\s0
-を選択しました。 Linux はこれに従ってきました。
+Microsoft は Windows Server 2008 以降、すべてのパーティションに対してデフォルトのアライメントとして 1 \s-1MB\s0 を選択しました。 Linux はこれに従ってきました。
.PP
-仮想マシンにおいて 512 バイトのセクターと仮定すると、セクター 2048
-に開始されている最初のパーティションを参照してください。また、（もしあれば）後続のパーティションは 2048 セクターの倍数から始まります。
+仮想マシンにおいて 512 バイトのセクターと仮定すると、セクター 2048 に開始されている最初のパーティションを参照してください。また、（もしあれば）後続のパーティションは 2048 セクターの倍数から始まります。
.PP
-1 \s-1MB\s0 アライメントはすべての現行アライメント要求 (4K, 64K)
-と互換性があります。また、物理ブロック容量における将来的な拡張の余地を残します。
+1 \s-1MB\s0 アライメントはすべての現行アライメント要求 (4K, 64K) と互換性があります。また、物理ブロック容量における将来的な拡張の余地を残します。
.SS "アライメントの設定法"
.IX Subsection "アライメントの設定法"
-\&\fBvirt\-resize\fR\|(1) can change the alignment of the partitions of some
-guests. Currently it can fully align all the partitions of all Windows
-guests, and it will fix the bootloader where necessary. For Linux guests,
-it can align the second and subsequent partitions, so the majority of \s-1OS\s0
-accesses except at boot will be aligned.
+\&\fBvirt\-resize\fR\|(1) can change the alignment of the partitions of some guests. Currently it can fully align all the partitions of all Windows guests, and it will fix the bootloader where necessary. For Linux guests, it can align the second and subsequent partitions, so the majority of \s-1OS\s0 accesses except at boot will be aligned.
.PP
-Another way to correct partition alignment problems is to reinstall your
-guest operating systems. If you install operating systems from templates,
-ensure these have correct partition alignment too.
+Another way to correct partition alignment problems is to reinstall your guest operating systems. If you install operating systems from templates, ensure these have correct partition alignment too.
.PP
-古いバージョンの Windows は、次の NetApp ドキュメントに有用な情報があります:
-http://media.netapp.com/documents/tr\-3747.pdf
+古いバージョンの Windows は、次の NetApp ドキュメントに有用な情報があります: http://media.netapp.com/documents/tr\-3747.pdf
.PP
-For Red Hat Enterprise Linux ≤ 5, use a Kickstart script that contains
-an explicit \f(CW%pre\fR section that creates aligned partitions using
-\&\fBparted\fR\|(8). Do not use the Kickstart \f(CW\*(C`part\*(C'\fR command. The NetApp
-document above contains an example.
+For Red Hat Enterprise Linux ≤ 5, use a Kickstart script that contains an explicit \f(CW%pre\fR section that creates aligned partitions using \fBparted\fR\|(8). Do not use the Kickstart \f(CW\*(C`part\*(C'\fR command. The NetApp document above contains an example.
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは以下を返します:
正常終了、いくつかのパーティションが多くのハイパーバイザーにおいてパフォーマンスの悪い < 4K のアライメントを持ちます
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBvirt\-resize\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-古いオペレーティングシステムが自身をインストールするとき、パーティションツールが基礎となるストレージと一致しないセクターにパーティションを配置します
-(一般的に最初のパーティションはセクター C<63> から始まります)。一致しないパーティションにより、必要以上に I/O
-を発生させるというオペレーティングシステムの問題を引き起こします。
+古いオペレーティングシステムが自身をインストールするとき、パーティションツールが基礎となるストレージと一致しないセクターにパーティションを配置します (一般的に最初のパーティションはセクター C<63> から始まります)。一致しないパーティションにより、必要以上に I/O を発生させるというオペレーティングシステムの問題を引き起こします。
virt-alignment-scan ツールは、仮想マシンおよびディスクイメージにあるパーティションの配置を確認します。配置に問題があれば警告します。
-現在、配置の問題を修正するための仮想化ツールはありません。ゲストオペレーティングシステムを再インストールすることだけができます。以下の NetApp
-のドキュメントが、問題と取り得る解決策をまとめています:
-L<http://media.netapp.com/documents/tr-3747.pdf>
+現在、配置の問題を修正するための仮想化ツールはありません。ゲストオペレーティングシステムを再インストールすることだけができます。以下の NetApp のドキュメントが、問題と取り得る解決策をまとめています: L<http://media.netapp.com/documents/tr-3747.pdf>
=head1 出力
/dev/sda2 105906176 1024K ok
/dev/sdb1 65536 64K ok
-すべての libvirt 仮想マシンをスキャンするには I<-a> や I<-d> オプションをつけずに virt-alignment-scan
-を実行します。
+すべての libvirt 仮想マシンをスキャンするには I<-a> や I<-d> オプションをつけずに virt-alignment-scan を実行します。
# virt-alignment-scan
F16x64:/dev/sda1 1048576 1024K ok
F16x64:/dev/sda2 2097152 2048K ok
F16x64:/dev/sda3 526385152 2048K ok
-出力は 4 つまたはそれより多い、空白区切りの項目から構成されます。プログラムからこれを構文解析する場合、最初の 4
-列のみが重要です。各項目は次のとおりです:
+出力は 4 つまたはそれより多い、空白区切りの項目から構成されます。プログラムからこれを構文解析する場合、最初の 4 列のみが重要です。各項目は次のとおりです:
=over 4
=item 1 列目
-The device and partition name (eg. F</dev/sda1> meaning the first partition
-on the first block device).
+The device and partition name (eg. F</dev/sda1> meaning the first partition on the first block device).
-すべての libvirt 仮想マシンを一覧表示するとき (I<-a> や I<-d> オプションなし)、この列は libvirt 名または UUID
-が先頭につきます (I<--uuid> が指定されていると)。例: C<WinXP:/dev/sda1>
+すべての libvirt 仮想マシンを一覧表示するとき (I<-a> や I<-d> オプションなし)、この列は libvirt 名または UUID が先頭につきます (I<--uuid> が指定されていると)。例: C<WinXP:/dev/sda1>
=item 2 列目
=back
-プログラムからの終了コードは、不適切に配置されたパーティションが見つかったかどうかに依存して変わります。以下の L</終了ステータス>
-を参照してください。
+プログラムからの終了コードは、不適切に配置されたパーティションが見つかったかどうかに依存して変わります。以下の L</終了ステータス> を参照してください。
出力なしで終了コードを欲しいならば、I<-q> オプションを使用してください。
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-alignment-scan --format=raw -a disk.img --format -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<-P> nr_threads
-Since libguestfs 1.22, virt-alignment-scan is multithreaded and examines
-guests in parallel. By default the number of threads to use is chosen based
-on the amount of free memory available at the time that virt-alignment-scan
-is started. You can force virt-alignment-scan to use at most C<nr_threads>
-by using the I<-P> option.
+Since libguestfs 1.22, virt-alignment-scan is multithreaded and examines guests in parallel. By default the number of threads to use is chosen based on the amount of free memory available at the time that virt-alignment-scan is started. You can force virt-alignment-scan to use at most C<nr_threads> by using the I<-P> option.
-Note that I<-P 0> means to autodetect, and I<-P 1> means to use a single
-thread.
+Note that I<-P 0> means to autodetect, and I<-P 1> means to use a single thread.
=item B<-q>
=item B<--quiet>
-Don’t produce any output. Just set the exit code (see L</EXIT STATUS>
-below).
+Don’t produce any output. Just set the exit code (see L</EXIT STATUS> below).
=item B<--uuid>
-名前の代わりに UUID を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2
-つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
+名前の代わりに UUID を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2 つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
-すべての libvirt 仮想マシンを一覧表示するとき (I<-a> や I<-d> オプションが指定されていないとき)、
-このオプションのみが適用されます。
+すべての libvirt 仮想マシンを一覧表示するとき (I<-a> や I<-d> オプションが指定されていないとき)、 このオプションのみが適用されます。
=item B<-v>
=head1 推奨されるアライメント
-Windows 2008 および ca.2010 以前のLinux よりも古いオペレーティングシステムは、512 バイトのセクター容量でセクター 63
-に、第 1 パーティションの第1セクターを配置しなければいけません。これは古くからの障害によるものです。ドライブは BIOS
-にシリンダー/ヘッド/セクター (CHS) の配置を通知する必要があります。配置は最近のドライブにおいては意味がありませんが、必ずトラックあたり 63
-セクターを持つことをときどき通知します。そのため、オペレーティングシステムはセクター 63 にある、第 2 "トラック" の先頭にある第 1
-パーティションに置かれます。
+Windows 2008 および ca.2010 以前のLinux よりも古いオペレーティングシステムは、512 バイトのセクター容量でセクター 63 に、第 1 パーティションの第1セクターを配置しなければいけません。これは古くからの障害によるものです。ドライブは BIOS にシリンダー/ヘッド/セクター (CHS) の配置を通知する必要があります。配置は最近のドライブにおいては意味がありませんが、必ずトラックあたり 63 セクターを持つことをときどき通知します。そのため、オペレーティングシステムはセクター 63 にある、第 2 "トラック" の先頭にある第 1 パーティションに置かれます。
ゲスト OS が仮想化されているとき、ホストオペレーティングシステムおよびハイパーバイザーは以下のどれかにアライメントされていることが好ましいでしょう。
=item * 4 K バイト
-4K バイトの物理セクターを持つ新規ハードディスクにおけるローカルストレージ向け。 4K
-バイトのブロック容量を持つファイルシステムにおけるファイル形式のストレージ向け。もしくは、何種類かのネットワークストレージ（NAS）向け。
+4K バイトの物理セクターを持つ新規ハードディスクにおけるローカルストレージ向け。 4K バイトのブロック容量を持つファイルシステムにおけるファイル形式のストレージ向け。もしくは、何種類かのネットワークストレージ（NAS）向け。
=item * 64 K バイト
│ │ │
─ ┴─────────────────────────┴─────────────────────────┴ ─ ─
-この例では、4K ブロックが読み込まれるたびに、ホストにある 2 つのブロックにアクセスする必要があります（そのため I/O が 2
-倍になります）。仮想マシンの 4K ブロックが書き込まれるとき、まず 2 つのホストブロックを読み込む必要があり、古いデータと新しいデータが結合され、2
-つのブロックが書き込まれます（4 倍の I/O）。
+この例では、4K ブロックが読み込まれるたびに、ホストにある 2 つのブロックにアクセスする必要があります（そのため I/O が 2 倍になります）。仮想マシンの 4K ブロックが書き込まれるとき、まず 2 つのホストブロックを読み込む必要があり、古いデータと新しいデータが結合され、2 つのブロックが書き込まれます（4 倍の I/O）。
=head2 Linux ホストブロック
$ cat /sys/block/sdc/queue/optimal_io_size
65536
-NetApp は、最小の 4K I/O サイズより好ましい 512 バイトアクセスが可能です（しかし、非常に効率が悪いです）、しかし最適な I/O
-サイズは 64K です。
+NetApp は、最小の 4K I/O サイズより好ましい 512 バイトアクセスが可能です（しかし、非常に効率が悪いです）、しかし最適な I/O サイズは 64K です。
-これらの数字の意味に関する詳細は
-L<http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage-iolimits.html>
-を参照してください。
+これらの数字の意味に関する詳細は L<http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage-iolimits.html> を参照してください。
-[4K ドライブデータを提供してくれた Matt Booth に感謝します。NetApp のデータと追加情報を提供してくれた Mike Snitzer
-に感謝します。]
+[4K ドライブデータを提供してくれた Matt Booth に感謝します。NetApp のデータと追加情報を提供してくれた Mike Snitzer に感謝します。]
=head2 1 MB パーティションアライメント
-Microsoft は Windows Server 2008 以降、すべてのパーティションに対してデフォルトのアライメントとして 1 MB
-を選択しました。 Linux はこれに従ってきました。
+Microsoft は Windows Server 2008 以降、すべてのパーティションに対してデフォルトのアライメントとして 1 MB を選択しました。 Linux はこれに従ってきました。
-仮想マシンにおいて 512 バイトのセクターと仮定すると、セクター 2048
-に開始されている最初のパーティションを参照してください。また、（もしあれば）後続のパーティションは 2048 セクターの倍数から始まります。
+仮想マシンにおいて 512 バイトのセクターと仮定すると、セクター 2048 に開始されている最初のパーティションを参照してください。また、（もしあれば）後続のパーティションは 2048 セクターの倍数から始まります。
-1 MB アライメントはすべての現行アライメント要求 (4K, 64K)
-と互換性があります。また、物理ブロック容量における将来的な拡張の余地を残します。
+1 MB アライメントはすべての現行アライメント要求 (4K, 64K) と互換性があります。また、物理ブロック容量における将来的な拡張の余地を残します。
=head2 アライメントの設定法
-L<virt-resize(1)> can change the alignment of the partitions of some
-guests. Currently it can fully align all the partitions of all Windows
-guests, and it will fix the bootloader where necessary. For Linux guests,
-it can align the second and subsequent partitions, so the majority of OS
-accesses except at boot will be aligned.
+L<virt-resize(1)> can change the alignment of the partitions of some guests. Currently it can fully align all the partitions of all Windows guests, and it will fix the bootloader where necessary. For Linux guests, it can align the second and subsequent partitions, so the majority of OS accesses except at boot will be aligned.
-Another way to correct partition alignment problems is to reinstall your
-guest operating systems. If you install operating systems from templates,
-ensure these have correct partition alignment too.
+Another way to correct partition alignment problems is to reinstall your guest operating systems. If you install operating systems from templates, ensure these have correct partition alignment too.
-古いバージョンの Windows は、次の NetApp ドキュメントに有用な情報があります:
-L<http://media.netapp.com/documents/tr-3747.pdf>
+古いバージョンの Windows は、次の NetApp ドキュメントに有用な情報があります: L<http://media.netapp.com/documents/tr-3747.pdf>
-For Red Hat Enterprise Linux E<le> 5, use a Kickstart script that contains
-an explicit C<%pre> section that creates aligned partitions using
-L<parted(8)>. Do not use the Kickstart C<part> command. The NetApp
-document above contains an example.
+For Red Hat Enterprise Linux E<le> 5, use a Kickstart script that contains an explicit C<%pre> section that creates aligned partitions using L<parted(8)>. Do not use the Kickstart C<part> command. The NetApp document above contains an example.
=head1 終了ステータス
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-rescue(1)>,
-L<virt-resize(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 著者
=head1 説明
-Virt-builder is a tool for quickly building new virtual machines. It can be
-configured to use template repositories. However creating and maintaining a
-repository involves many tasks which can be automated.
-virt-builder-repository is a tool helping to manage these repositories.
+Virt-builder is a tool for quickly building new virtual machines. It can be configured to use template repositories. However creating and maintaining a repository involves many tasks which can be automated. virt-builder-repository is a tool helping to manage these repositories.
-Virt-builder-repository loops over the files in the directory specified as
-argument, compresses the files with a name ending by C<qcow2>, C<raw>,
-C<img> or without extension, extracts data from them and creates or updates
-the C<index> file.
+Virt-builder-repository loops over the files in the directory specified as argument, compresses the files with a name ending by C<qcow2>, C<raw>, C<img> or without extension, extracts data from them and creates or updates the C<index> file.
-Some of the image-related data needed for the index file can’t be computed
-from the image file. virt-builder-repository first tries to find them in the
-existing index file. If data are still missing after this, they are prompted
-in interactive mode, otherwise an error will be triggered.
+Some of the image-related data needed for the index file can’t be computed from the image file. virt-builder-repository first tries to find them in the existing index file. If data are still missing after this, they are prompted in interactive mode, otherwise an error will be triggered.
-If a C<KEYID> is provided, the generated index file will be signed with this
-GPG key.
+If a C<KEYID> is provided, the generated index file will be signed with this GPG key.
=head1 例
=head2 Create the initial repository
-Create a folder and copy the disk image template files in it. Then run a
-command like the following one:
+Create a folder and copy the disk image template files in it. Then run a command like the following one:
virt-builder-repository --gpg-key "joe@hacker.org" -i /path/to/folder
-Note that this example command runs in interactive mode. To run in automated
-mode, a minimal index file needs to be created before running the command
-containing sections like this one:
+Note that this example command runs in interactive mode. To run in automated mode, a minimal index file needs to be created before running the command containing sections like this one:
[template_id]
file=template_filename.qcow.xz
-The file value needs to match the image name extended with the C<.xz> suffix
-if the I<--no-compression> parameter is not provided or the image name if no
-compression is involved. Other optional data can be prefilled. Default
-values are computed by inspecting the disk image. For more informations,
-see L<virt-builder(1)/Creating and signing the index file>.
+The file value needs to match the image name extended with the C<.xz> suffix if the I<--no-compression> parameter is not provided or the image name if no compression is involved. Other optional data can be prefilled. Default values are computed by inspecting the disk image. For more informations, see L<virt-builder(1)/Creating and signing the index file>.
=head2 Update images in an existing repository
-In this use case, a new image or a new revision of an existing image needs
-to be added to the repository. Place the corresponding image template files
-in the repository folder.
+In this use case, a new image or a new revision of an existing image needs to be added to the repository. Place the corresponding image template files in the repository folder.
-To update the revision of an image, the file needs to have the same name
-than the existing one (without the C<xz> extension).
+To update the revision of an image, the file needs to have the same name than the existing one (without the C<xz> extension).
-As in the repository creation use case, a minimal fragment can be added to
-the index file for the automated mode. This can be done on the signed index
-even if it may sound a strange idea: the index will be signed again by the
-tool.
+As in the repository creation use case, a minimal fragment can be added to the index file for the automated mode. This can be done on the signed index even if it may sound a strange idea: the index will be signed again by the tool.
-To remove an image from the repository, just remove the corresponding image
-file before running virt-builder-repository.
+To remove an image from the repository, just remove the corresponding image file before running virt-builder-repository.
Then running the following command will complete and update the index file:
virt-builder-repository --gpg-key "joe@hacker.org" -i /path/to/folder
-virt-builder-repository works in a temporary folder inside the repository
-one. If anything wrong happens when running the tool, the repository is left
-untouched.
+virt-builder-repository works in a temporary folder inside the repository one. If anything wrong happens when running the tool, the repository is left untouched.
=head1 オプション
=item B<--gpg> GPG
-Specify an alternate L<gpg(1)> (GNU Privacy Guard) binary. You can also use
-this to add gpg parameters, for example to specify an alternate home
-directory:
+Specify an alternate L<gpg(1)> (GNU Privacy Guard) binary. You can also use this to add gpg parameters, for example to specify an alternate home directory:
virt-builder-repository --gpg "gpg --homedir /tmp" [...]
=item B<--gpg-key> KEYID
-Specify the GPG key to be used to sign the repository index file. If not
-provided, the index will left unsigned. C<KEYID> is used to identify the GPG
-key to use. This value is passed to gpg’s I<--default-key> option and can
-thus be an email address or a fingerprint.
+Specify the GPG key to be used to sign the repository index file. If not provided, the index will left unsigned. C<KEYID> is used to identify the GPG key to use. This value is passed to gpg’s I<--default-key> option and can thus be an email address or a fingerprint.
-B<NOTE>: by default, virt-builder-repository searches for the key in the
-user’s GPG keyring.
+B<NOTE>: by default, virt-builder-repository searches for the key in the user’s GPG keyring.
=item B<-i>
Prompt for missing data. Default values are computed from the disk image.
-When prompted for data, inputting C<-> corresponds to leaving the value
-empty. This can be used to avoid setting the default computed value.
+When prompted for data, inputting C<-> corresponds to leaving the value empty. This can be used to avoid setting the default computed value.
=item B<--no-compression>
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<-q>
Enable debug messages and/or produce verbose output.
-When reporting bugs, use this option and attach the complete output to your
-bug report.
+When reporting bugs, use this option and attach the complete output to your bug report.
=item B<-V>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 マシン可読な出力
-The I<--machine-readable> option can be used to make the output more machine
-friendly, which is useful when calling virt-builder-repository from other
-programs, GUIs etc.
+The I<--machine-readable> option can be used to make the output more machine friendly, which is useful when calling virt-builder-repository from other programs, GUIs etc.
-Use the option on its own to query the capabilities of the
-virt-builder-repository binary. Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-builder-repository binary. Typical output looks like this:
$ virt-builder-repository --machine-readable
virt-builder-repository
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 終了ステータス
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-builder 1"
-.TH virt-builder 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-builder 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-builder is a tool for quickly building new virtual machines. You can
-build a variety of VMs for local or cloud use, usually within a few minutes
-or less. Virt-builder also has many ways to customize these VMs.
-Everything is run from the command line and nothing requires root
-privileges, so automation and scripting is simple.
-.PP
-Note that virt-builder does not install guests from scratch. It takes
-cleanly prepared, digitally signed \s-1OS\s0 templates and customizes them. This
-approach is used because it is much faster, but if you need to do fresh
-installs you may want to look at \fBvirt\-install\fR\|(1) and \fBoz\-install\fR\|(1).
-.PP
-The easiest way to get started is by looking at the examples in the next
-section.
+Virt-builder is a tool for quickly building new virtual machines. You can build a variety of VMs for local or cloud use, usually within a few minutes or less. Virt-builder also has many ways to customize these VMs. Everything is run from the command line and nothing requires root privileges, so automation and scripting is simple.
+.PP
+Note that virt-builder does not install guests from scratch. It takes cleanly prepared, digitally signed \s-1OS\s0 templates and customizes them. This approach is used because it is much faster, but if you need to do fresh installs you may want to look at \fBvirt\-install\fR\|(1) and \fBoz\-install\fR\|(1).
+.PP
+The easiest way to get started is by looking at the examples in the next section.
.SH "例"
.IX Header "例"
.SS "List the virtual machines available"
\& virt\-builder \-\-list
.Ve
.PP
-will list out the operating systems available to install. A selection of
-freely redistributable OSes is available as standard. You can add your own
-too (see below).
+will list out the operating systems available to install. A selection of freely redistributable OSes is available as standard. You can add your own too (see below).
.PP
-After choosing a guest from the list, you may want to see if there are any
-installation notes:
+After choosing a guest from the list, you may want to see if there are any installation notes:
.PP
.Vb 1
\& virt\-builder \-\-notes fedora\-27
\& virt\-builder fedora\-27
.Ve
.PP
-will build a Fedora 25 image for the same architecture as virt-builder (so
-running it from an i686 installation will try to build an i686 image, if
-available). This will have all default configuration (minimal size, no user
-accounts, random root password, only the bare minimum installed software,
-etc.).
+will build a Fedora 25 image for the same architecture as virt-builder (so running it from an i686 installation will try to build an i686 image, if available). This will have all default configuration (minimal size, no user accounts, random root password, only the bare minimum installed software, etc.).
.PP
You \fIdo not\fR need to run this command as root.
.PP
-The first time this runs it has to download the template over the network,
-but this gets cached (see \*(L"\s-1CACHING\*(R"\s0).
+The first time this runs it has to download the template over the network, but this gets cached (see \*(L"\s-1CACHING\*(R"\s0).
.PP
-The name of the output file is derived from the template name, so above it
-will be \fIfedora\-27.img\fR. You can change the output filename using the
-\&\fI\-o\fR option:
+The name of the output file is derived from the template name, so above it will be \fIfedora\-27.img\fR. You can change the output filename using the \fI\-o\fR option:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-o mydisk.img
.Ve
.PP
-You can also use the \fI\-o\fR option to write to existing devices or logical
-volumes.
+You can also use the \fI\-o\fR option to write to existing devices or logical volumes.
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-format qcow2
\& virt\-builder fedora\-27 \-\-size 20G
.Ve
.PP
-As above, but the output size will be 20 \s-1GB.\s0 The guest \s-1OS\s0 is resized as it
-is copied to the output (automatically, using \fBvirt\-resize\fR\|(1)).
+As above, but the output size will be 20 \s-1GB.\s0 The guest \s-1OS\s0 is resized as it is copied to the output (automatically, using \fBvirt\-resize\fR\|(1)).
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-arch i686
\& virt\-builder fedora\-27 \-\-root\-password file:/tmp/rootpw
.Ve
.PP
-Create a Fedora 25 image. The root password is taken from the file
-\&\fI/tmp/rootpw\fR.
+Create a Fedora 25 image. The root password is taken from the file \fI/tmp/rootpw\fR.
.PP
-Note if you \fIdon’t\fR set \fI\-\-root\-password\fR then the guest is given a
-\&\fIrandom\fR root password which is printed on stdout.
+Note if you \fIdon’t\fR set \fI\-\-root\-password\fR then the guest is given a \fIrandom\fR root password which is printed on stdout.
.PP
You can also create user accounts. See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 below.
.SS "Set the hostname"
Set the hostname to \f(CW\*(C`virt.example.com\*(C'\fR.
.SS "Installing software"
.IX Subsection "Installing software"
-To install packages from the ordinary (guest) software repository (eg. dnf
-or apt):
+To install packages from the ordinary (guest) software repository (eg. dnf or apt):
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-install "inkscape,@Xfce Desktop"
.Ve
.PP
-(In Fedora, \f(CW\*(C`@\*(C'\fR is used to install groups of packages. On Debian you would
-install a meta-package instead.)
+(In Fedora, \f(CW\*(C`@\*(C'\fR is used to install groups of packages. On Debian you would install a meta-package instead.)
.PP
To update the installed packages to the latest version:
.PP
\& virt\-builder debian\-7 \-\-update
.Ve
.PP
-For guests which use SELinux, like Fedora and Red Hat Enterprise Linux, you
-may need to do SELinux relabelling after installing or updating packages
-(see \*(L"\s-1SELINUX\*(R"\s0 below):
+For guests which use SELinux, like Fedora and Red Hat Enterprise Linux, you may need to do SELinux relabelling after installing or updating packages (see \*(L"\s-1SELINUX\*(R"\s0 below):
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-update \-\-selinux\-relabel
.Ve
.SS "Customizing the installation"
.IX Subsection "Customizing the installation"
-There are many options that let you customize the installation. These
-include: \fI\-\-run\fR/\fI\-\-run\-command\fR, which run a shell script or command
-while the disk image is being generated and lets you add or edit files that
-go into the disk image. \fI\-\-firstboot\fR/\fI\-\-firstboot\-command\fR, which let
-you add scripts/commands that are run the first time the guest boots.
-\&\fI\-\-edit\fR to edit files. \fI\-\-upload\fR to upload files.
+There are many options that let you customize the installation. These include: \fI\-\-run\fR/\fI\-\-run\-command\fR, which run a shell script or command while the disk image is being generated and lets you add or edit files that go into the disk image. \fI\-\-firstboot\fR/\fI\-\-firstboot\-command\fR, which let you add scripts/commands that are run the first time the guest boots. \fI\-\-edit\fR to edit files. \fI\-\-upload\fR to upload files.
.PP
例:
.PP
\& virt\-builder fedora\-27 \-\-firstboot\-command \*(Aqdnf \-y \-\-best update\*(Aq
.Ve
.PP
-which makes the \fBdnf\fR\|(8) \f(CW\*(C`update\*(C'\fR command run once the first time the
-guest boots.
+which makes the \fBdnf\fR\|(8) \f(CW\*(C`update\*(C'\fR command run once the first time the guest boots.
.PP
Or:
.PP
\& s/gpgcheck=1/gpgcheck=0/\*(Aq
.Ve
.PP
-which edits \fI/etc/dnf/dnf.conf\fR inside the disk image (during disk image
-creation, long before boot).
+which edits \fI/etc/dnf/dnf.conf\fR inside the disk image (during disk image creation, long before boot).
.PP
You can combine these options, and have multiple options of all types.
.SH "オプション"
ヘルプを表示します。
.IP "\fB\-\-arch\fR \s-1ARCHITECTURE\s0" 4
.IX Item "--arch ARCHITECTURE"
-Use the specified architecture for the output image. This means there must
-be sources providing the requested template for the requested architecture.
+Use the specified architecture for the output image. This means there must be sources providing the requested template for the requested architecture.
.Sp
See also \*(L"\s-1ARCHITECTURE\*(R"\s0.
.IP "\fB\-\-attach\fR \s-1ISOFILE\s0" 4
.IX Item "--attach ISOFILE"
-During the customization phase, the given disk is attached to the libguestfs
-appliance. This is used to provide extra software repositories or other
-data for customization.
+During the customization phase, the given disk is attached to the libguestfs appliance. This is used to provide extra software repositories or other data for customization.
.Sp
-You probably want to ensure the volume(s) or filesystems in the attached
-disks are labelled (or use an \s-1ISO\s0 volume name) so that you can mount them by
-label in your run-scripts:
+You probably want to ensure the volume(s) or filesystems in the attached disks are labelled (or use an \s-1ISO\s0 volume name) so that you can mount them by label in your run-scripts:
.Sp
.Vb 2
\& mkdir /tmp/mount
\& mount LABEL=EXTRA /tmp/mount
.Ve
.Sp
-You can have multiple \fI\-\-attach\fR options, and the format can be any disk
-format (not just an \s-1ISO\s0).
+You can have multiple \fI\-\-attach\fR options, and the format can be any disk format (not just an \s-1ISO\s0).
.Sp
-See also: \fI\-\-run\fR, \*(L"Installing packages at build time from a side
-repository\*(R", \fBgenisoimage\fR\|(1), \fBvirt\-make\-fs\fR\|(1).
+See also: \fI\-\-run\fR, \*(L"Installing packages at build time from a side repository\*(R", \fBgenisoimage\fR\|(1), \fBvirt\-make\-fs\fR\|(1).
.IP "\fB\-\-attach\-format\fR \s-1FORMAT\s0" 4
.IX Item "--attach-format FORMAT"
-Specify the disk format for the next \fI\-\-attach\fR option. The \f(CW\*(C`FORMAT\*(C'\fR is
-usually \f(CW\*(C`raw\*(C'\fR or \f(CW\*(C`qcow2\*(C'\fR. Use \f(CW\*(C`raw\*(C'\fR for ISOs.
+Specify the disk format for the next \fI\-\-attach\fR option. The \f(CW\*(C`FORMAT\*(C'\fR is usually \f(CW\*(C`raw\*(C'\fR or \f(CW\*(C`qcow2\*(C'\fR. Use \f(CW\*(C`raw\*(C'\fR for ISOs.
.IP "\fB\-\-cache\fR \s-1DIR\s0" 4
.IX Item "--cache DIR"
.PD 0
.IP "\fB\-\-no\-cache\fR" 4
.IX Item "--no-cache"
.PD
-\&\fI\-\-cache\fR \s-1DIR\s0 sets the directory to use/check for cached template files.
-If not set, defaults to either \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR or
-\&\fI\f(CI$HOME\fI/.cache/virt\-builder/\fR.
+\&\fI\-\-cache\fR \s-1DIR\s0 sets the directory to use/check for cached template files. If not set, defaults to either \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR or \fI\f(CI$HOME\fI/.cache/virt\-builder/\fR.
.Sp
\&\fI\-\-no\-cache\fR disables template caching.
.IP "\fB\-\-cache\-all\-templates\fR" 4
.IX Item "--cache-all-templates"
Download all templates to the cache and then exit. See \*(L"\s-1CACHING\*(R"\s0.
.Sp
-Note this doesn't cache everything. More templates might be uploaded. Also
-this doesn't cache packages (the \fI\-\-install\fR, \fI\-\-update\fR options).
+Note this doesn't cache everything. More templates might be uploaded. Also this doesn't cache packages (the \fI\-\-install\fR, \fI\-\-update\fR options).
.IP "\fB\-\-check\-signature\fR" 4
.IX Item "--check-signature"
.PD 0
.IP "\fB\-\-no\-check\-signature\fR" 4
.IX Item "--no-check-signature"
.PD
-Check/don’t check the digital signature of the \s-1OS\s0 template. The default is
-to check the signature and exit if it is not correct. Using
-\&\fI\-\-no\-check\-signature\fR bypasses this check.
+Check/don’t check the digital signature of the \s-1OS\s0 template. The default is to check the signature and exit if it is not correct. Using \fI\-\-no\-check\-signature\fR bypasses this check.
.Sp
See also \fI\-\-fingerprint\fR.
.IP "\fB\-\-colors\fR" 4
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-\-curl\fR \s-1CURL\s0" 4
.IX Item "--curl CURL"
-Specify an alternate \fBcurl\fR\|(1) binary. You can also use this to add curl
-parameters, for example to disable https certificate checks:
+Specify an alternate \fBcurl\fR\|(1) binary. You can also use this to add curl parameters, for example to disable https certificate checks:
.Sp
.Vb 1
\& virt\-builder \-\-curl "curl \-\-insecure" [...]
Delete the template cache. See \*(L"\s-1CACHING\*(R"\s0.
.IP "\fB\-\-no\-delete\-on\-failure\fR" 4
.IX Item "--no-delete-on-failure"
-Don’t delete the output file on failure to build. You can use this to debug
-failures to run scripts. See \*(L"\s-1DEBUGGING BUILDS\*(R"\s0 for ways to debug images.
+Don’t delete the output file on failure to build. You can use this to debug failures to run scripts. See \*(L"\s-1DEBUGGING BUILDS\*(R"\s0 for ways to debug images.
.Sp
-The default is to delete the output file if virt-builder fails (or, for
-example, some script that it runs fails).
+The default is to delete the output file if virt-builder fails (or, for example, some script that it runs fails).
.IP "\fB\-\-fingerprint\fR '\s-1AAAA BBBB ...\s0'" 4
.IX Item "--fingerprint 'AAAA BBBB ...'"
-Check that the index and templates are signed by the key with the given
-fingerprint. (The fingerprint is a long string, usually written as 10
-groups of 4 hexadecimal digits).
-.Sp
-You can give this option multiple times. If you have multiple source URLs,
-then you can have either no fingerprint, one fingerprint or multiple
-fingerprints. If you have multiple, then each must correspond 1\-1 with a
-source \s-1URL.\s0
+Check that the index and templates are signed by the key with the given fingerprint. (The fingerprint is a long string, usually written as 10 groups of 4 hexadecimal digits).
+.Sp
+You can give this option multiple times. If you have multiple source URLs, then you can have either no fingerprint, one fingerprint or multiple fingerprints. If you have multiple, then each must correspond 1\-1 with a source \s-1URL.\s0
.IP "\fB\-\-format\fR qcow2" 4
.IX Item "--format qcow2"
.PD 0
.Sp
With \fI\-\-get\-kernel\fR this specifies the input format.
.Sp
-To create an old-style qcow2 file (for compatibility with \s-1RHEL 6\s0 or very old
-qemu < 1.1), after running virt-builder, use this command:
+To create an old-style qcow2 file (for compatibility with \s-1RHEL 6\s0 or very old qemu < 1.1), after running virt-builder, use this command:
.Sp
.Vb 1
\& qemu\-img amend \-f qcow2 \-o compat=0.10 output.qcow2
.Ve
.IP "\fB\-\-get\-kernel\fR \s-1IMAGE\s0" 4
.IX Item "--get-kernel IMAGE"
-This option extracts the kernel and initramfs from a previously built disk
-image called \f(CW\*(C`IMAGE\*(C'\fR (in fact it works for any \s-1VM\s0 disk image, not just ones
-built using virt-builder).
+This option extracts the kernel and initramfs from a previously built disk image called \f(CW\*(C`IMAGE\*(C'\fR (in fact it works for any \s-1VM\s0 disk image, not just ones built using virt-builder).
.Sp
-Note this method is \fBdeprecated\fR: there is a separate tool for this,
-\&\fBvirt\-get\-kernel\fR\|(1), which has more options for the file extraction.
+Note this method is \fBdeprecated\fR: there is a separate tool for this, \fBvirt\-get\-kernel\fR\|(1), which has more options for the file extraction.
.Sp
-The kernel and initramfs are written to the current directory, unless you
-also specify the \fI\-\-output\fR \f(CW\*(C`outputdir\*(C'\fR \fBdirectory\fR name.
+The kernel and initramfs are written to the current directory, unless you also specify the \fI\-\-output\fR \f(CW\*(C`outputdir\*(C'\fR \fBdirectory\fR name.
.Sp
-The format of the disk image is automatically detected unless you specify it
-by using the \fI\-\-format\fR option.
+The format of the disk image is automatically detected unless you specify it by using the \fI\-\-format\fR option.
.Sp
-In the case where the guest contains multiple kernels, the one with the
-highest version number is chosen. To extract arbitrary kernels from the
-disk image, see \fBguestfish\fR\|(1). To extract the entire \fI/boot\fR directory
-of a guest, see \fBvirt\-copy\-out\fR\|(1).
+In the case where the guest contains multiple kernels, the one with the highest version number is chosen. To extract arbitrary kernels from the disk image, see \fBguestfish\fR\|(1). To extract the entire \fI/boot\fR directory of a guest, see \fBvirt\-copy\-out\fR\|(1).
.IP "\fB\-\-gpg\fR \s-1GPG\s0" 4
.IX Item "--gpg GPG"
-Specify an alternate \fBgpg\fR\|(1) (\s-1GNU\s0 Privacy Guard) binary. By default
-virt-builder looks for either \f(CW\*(C`gpg2\*(C'\fR or \f(CW\*(C`gpg\*(C'\fR in the \f(CW$PATH\fR.
+Specify an alternate \fBgpg\fR\|(1) (\s-1GNU\s0 Privacy Guard) binary. By default virt-builder looks for either \f(CW\*(C`gpg2\*(C'\fR or \f(CW\*(C`gpg\*(C'\fR in the \f(CW$PATH\fR.
.Sp
-You can also use this to add gpg parameters, for example to specify an
-alternate home directory:
+You can also use this to add gpg parameters, for example to specify an alternate home directory:
.Sp
.Vb 1
\& virt\-builder \-\-gpg "gpg \-\-homedir /tmp" [...]
.IP "\fB\-\-list\fR \fB\-\-long\fR [os\-version]" 4
.IX Item "--list --long [os-version]"
.PD
-List all the available templates if no guest is specified, or only for the
-specified one.
+List all the available templates if no guest is specified, or only for the specified one.
.Sp
-It is possible to choose with \fI\-\-list\-format\fR the output format for the
-list templates:
+It is possible to choose with \fI\-\-list\-format\fR the output format for the list templates:
.RS 4
.IP "\fBshort\fR" 4
.IX Item "short"
-The default format, prints only the template identifier and, next to it, its
-short description.
+The default format, prints only the template identifier and, next to it, its short description.
.IP "\fBlong\fR" 4
.IX Item "long"
-Prints a textual list with the details of the available sources, followed by
-the details of the available templates.
+Prints a textual list with the details of the available sources, followed by the details of the available templates.
.IP "\fBjson\fR" 4
.IX Item "json"
-Prints a \s-1JSON\s0 object with the details of the available sources and the
-details of the available templates.
+Prints a \s-1JSON\s0 object with the details of the available sources and the details of the available templates.
.Sp
-The \f(CW\*(C`version\*(C'\fR key in the main object represents the \*(L"compatibility
-version\*(R", and it is bumped every time the resulting \s-1JSON\s0 output is
-incompatible with the previous versions (for example the structure has
-changed, or non-optional keys are no more present).
+The \f(CW\*(C`version\*(C'\fR key in the main object represents the \*(L"compatibility version\*(R", and it is bumped every time the resulting \s-1JSON\s0 output is incompatible with the previous versions (for example the structure has changed, or non-optional keys are no more present).
.RE
.RS 4
.Sp
.IP "\fB\-\-memsize\fR \s-1MB\s0" 4
.IX Item "--memsize MB"
.PD
-Change the amount of memory allocated to \fI\-\-run\fR scripts. Increase this if
-you find that \fI\-\-run\fR scripts or the \fI\-\-install\fR option are running out of
-memory.
+Change the amount of memory allocated to \fI\-\-run\fR scripts. Increase this if you find that \fI\-\-run\fR scripts or the \fI\-\-install\fR option are running out of memory.
.Sp
The default can be found with this command:
.Sp
.Sp
Enabled is the default. Use \fI\-\-no\-network\fR to disable access.
.Sp
-The network only allows outgoing connections and has other minor
-limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
+The network only allows outgoing connections and has other minor limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
.Sp
-If you use \fI\-\-no\-network\fR then certain other options such as \fI\-\-install\fR
-will not work.
+If you use \fI\-\-no\-network\fR then certain other options such as \fI\-\-install\fR will not work.
.Sp
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-builder.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-builder.
.Sp
-Generally speaking you should \fInot\fR use \fI\-\-no\-network\fR. But here are some
-reasons why you might want to:
+Generally speaking you should \fInot\fR use \fI\-\-no\-network\fR. But here are some reasons why you might want to:
.RS 4
.IP "1." 4
-Because the libguestfs backend that you are using doesn't support the
-network. (See: \*(L"\s-1BACKEND\*(R"\s0 in \fBguestfs\fR\|(3)).
+Because the libguestfs backend that you are using doesn't support the network. (See: \*(L"\s-1BACKEND\*(R"\s0 in \fBguestfs\fR\|(3)).
.IP "2." 4
-Any software you need to install comes from an attached \s-1ISO,\s0 so you don't
-need the network.
+Any software you need to install comes from an attached \s-1ISO,\s0 so you don't need the network.
.IP "3." 4
-You don’t want untrusted guest code trying to access your host network when
-running virt-builder. This is particularly an issue when you don't trust
-the source of the operating system templates. (See \*(L"\s-1SECURITY\*(R"\s0 below).
+You don’t want untrusted guest code trying to access your host network when running virt-builder. This is particularly an issue when you don't trust the source of the operating system templates. (See \*(L"\s-1SECURITY\*(R"\s0 below).
.IP "4." 4
You don’t have a host network (eg. in secure/restricted environments).
.RE
.Sp
Virt-builder \f(CW\*(C`fsync\*(C'\fRs the output file or disk image when it exits.
.Sp
-The reason is that qemu/KVM’s default caching mode is \f(CW\*(C`none\*(C'\fR or
-\&\f(CW\*(C`directsync\*(C'\fR, both of which bypass the host page cache. Therefore these
-would not work correctly if you immediately started the guest after running
-virt-builder \- they would not see the complete output file. (Note that you
-should not use these caching modes \- they are fundamentally broken for this
-and other reasons.)
+The reason is that qemu/KVM’s default caching mode is \f(CW\*(C`none\*(C'\fR or \f(CW\*(C`directsync\*(C'\fR, both of which bypass the host page cache. Therefore these would not work correctly if you immediately started the guest after running virt-builder \- they would not see the complete output file. (Note that you should not use these caching modes \- they are fundamentally broken for this and other reasons.)
.Sp
-If you are not using these broken caching modes, you can use \fI\-\-no\-sync\fR to
-avoid this unnecessary sync and gain considerable extra performance.
+If you are not using these broken caching modes, you can use \fI\-\-no\-sync\fR to avoid this unnecessary sync and gain considerable extra performance.
.IP "\fB\-\-notes\fR os-version" 4
.IX Item "--notes os-version"
-List any notes associated with this guest, then exit (this does not do the
-install).
+List any notes associated with this guest, then exit (this does not do the install).
.IP "\fB\-o\fR filename" 4
.IX Item "-o filename"
.PD 0
.IP "\fB\-\-output\fR filename" 4
.IX Item "--output filename"
.PD
-Write the output to \fIfilename\fR. If you don’t specify this option, then the
-output filename is generated by taking the \f(CW\*(C`os\-version\*(C'\fR string and adding
-\&\f(CW\*(C`.img\*(C'\fR (for raw format) or \f(CW\*(C`.qcow2\*(C'\fR (for qcow2 format).
+Write the output to \fIfilename\fR. If you don’t specify this option, then the output filename is generated by taking the \f(CW\*(C`os\-version\*(C'\fR string and adding \f(CW\*(C`.img\*(C'\fR (for raw format) or \f(CW\*(C`.qcow2\*(C'\fR (for qcow2 format).
.Sp
-Note that the output filename could be a device, partition or logical
-volume.
+Note that the output filename could be a device, partition or logical volume.
.Sp
When used with \fI\-\-get\-kernel\fR, this option specifies the output directory.
.IP "\fB\-\-print\-cache\fR" 4
Don’t print ordinary progress messages.
.IP "\fB\-\-size\fR \s-1SIZE\s0" 4
.IX Item "--size SIZE"
-Select the size of the output disk, where the size can be specified using
-common names such as \f(CW\*(C`32G\*(C'\fR (32 gigabytes) etc.
+Select the size of the output disk, where the size can be specified using common names such as \f(CW\*(C`32G\*(C'\fR (32 gigabytes) etc.
.Sp
Virt-builder will resize filesystems inside the disk image automatically.
.Sp
-If the size is not specified, then one of two things happens. If the output
-is a file, then the size is the same as the template. If the output is a
-device, partition, etc then the size of that device is used.
+If the size is not specified, then one of two things happens. If the output is a file, then the size is the same as the template. If the output is a device, partition, etc then the size of that device is used.
.Sp
-To specify size in bytes, the number must be followed by the lowercase
-letter \fIb\fR, eg: \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
+To specify size in bytes, the number must be followed by the lowercase letter \fIb\fR, eg: \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
.IP "\fB\-\-smp\fR N" 4
.IX Item "--smp N"
Enable N ≥ 2 virtual CPUs for \fI\-\-run\fR scripts to use.
.Sp
See also \*(L"\s-1SOURCES OF TEMPLATES\*(R"\s0 below.
.Sp
-Note that you should not point \fI\-\-source\fR to sources that you don’t trust
-(unless the source is signed by someone you do trust). See also the
-\&\fI\-\-no\-network\fR option.
+Note that you should not point \fI\-\-source\fR to sources that you don’t trust (unless the source is signed by someone you do trust). See also the \fI\-\-no\-network\fR option.
.IP "\fB\-\-no\-warn\-if\-partition\fR" 4
.IX Item "--no-warn-if-partition"
-Do not emit a warning if the output device is a partition. This warning
-avoids a common user error when writing to a \s-1USB\s0 key or external drive, when
-you should normally write to the whole device (\fI\-\-output /dev/sdX\fR), not
-to a partition on the device (\fI\-\-output /dev/sdX1\fR). Use this option to
-\&\fIsuppress\fR this warning.
+Do not emit a warning if the output device is a partition. This warning avoids a common user error when writing to a \s-1USB\s0 key or external drive, when you should normally write to the whole device (\fI\-\-output /dev/sdX\fR), not to a partition on the device (\fI\-\-output /dev/sdX1\fR). Use this option to \fIsuppress\fR this warning.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.PD
Enable debug messages and/or produce verbose output.
.Sp
-When reporting bugs, use this option and attach the complete output to your
-bug report.
+When reporting bugs, use this option and attach the complete output to your bug report.
.IP "\fB\-V\fR" 4
.IX Item "-V"
.PD 0
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.IX Subsection "Customization options"
.IP "\fB\-\-append\-line\fR \s-1FILE:LINE\s0" 4
.IX Item "--append-line FILE:LINE"
-Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already
-end with a newline, then one is added before the appended line. Also a
-newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
+Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already end with a newline, then one is added before the appended line. Also a newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
.Sp
For example (assuming ordinary shell quoting) this command:
.Sp
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the
-latter only if the existing file does not already end with a newline.
+will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the latter only if the existing file does not already end with a newline.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the
-existing content of the file, so this command does the right thing for files
-using Unix or Windows line endings. It also works for empty or non-existent
-files.
+\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. It also works for empty or non-existent files.
.Sp
To insert several lines, use the same option several times:
.Sp
.IX Item "--chmod PERMISSIONS:FILE"
Change the permissions of \f(CW\*(C`FILE\*(C'\fR to \f(CW\*(C`PERMISSIONS\*(C'\fR.
.Sp
-\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it
-with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
+\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
.IP "\fB\-\-commands\-from\-file\fR \s-1FILENAME\s0" 4
.IX Item "--commands-from-file FILENAME"
Read the customize commands from a file, one (and its arguments) each line.
.Sp
-Each line contains a single customization command and its arguments, for
-example:
+Each line contains a single customization command and its arguments, for example:
.Sp
.Vb 3
\& delete /some/file
\& password some\-user:password:its\-new\-password
.Ve
.Sp
-Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are
-ignored as well. Furthermore, arguments can be spread across multiple
-lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for
-example
+Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are ignored as well. Furthermore, arguments can be spread across multiple lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for example
.Sp
.Vb 2
\& edit /some/file:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-The commands are handled in the same order as they are in the file, as if
-they were specified as \fI\-\-delete /some/file\fR on the command line.
+The commands are handled in the same order as they are in the file, as if they were specified as \fI\-\-delete /some/file\fR on the command line.
.IP "\fB\-\-copy\fR \s-1SOURCE:DEST\s0" 4
.IX Item "--copy SOURCE:DEST"
Copy files or directories recursively inside the guest.
Wildcards cannot be used.
.IP "\fB\-\-copy\-in\fR \s-1LOCALPATH:REMOTEDIR\s0" 4
.IX Item "--copy-in LOCALPATH:REMOTEDIR"
-Copy local files or directories recursively into the disk image, placing
-them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
+Copy local files or directories recursively into the disk image, placing them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
.Sp
Wildcards cannot be used.
.IP "\fB\-\-delete\fR \s-1PATH\s0" 4
.IX Item "--delete PATH"
-Delete a file from the guest. Or delete a directory (and all its contents,
-recursively).
+Delete a file from the guest. Or delete a directory (and all its contents, recursively).
.Sp
-You can use shell glob characters in the specified path. Be careful to
-escape glob characters from the host shell, if that is required. For
-example:
+You can use shell glob characters in the specified path. Be careful to escape glob characters from the host shell, if that is required. For example:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
See \*(L"NON-INTERACTIVE \s-1EDITING\*(R"\s0 in \fBvirt\-edit\fR\|(1).
.IP "\fB\-\-firstboot\fR \s-1SCRIPT\s0" 4
.IX Item "--firstboot SCRIPT"
-Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up,
-the script runs (as root, late in the boot process).
+Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up, the script runs (as root, late in the boot process).
.Sp
The script is automatically chmod +x after installation in the guest.
.Sp
-The alternative version \fI\-\-firstboot\-command\fR is the same, but it
-conveniently wraps the command up in a single line script for you.
+The alternative version \fI\-\-firstboot\-command\fR is the same, but it conveniently wraps the command up in a single line script for you.
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-command\fR '\s-1CMD+ARGS\s0'" 4
.IX Item "--firstboot-command 'CMD+ARGS'"
-Run command (and arguments) inside the guest when the guest first boots up
-(as root, late in the boot process).
+Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process).
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-install\fR \s-1PKG,PKG..\s0" 4
.IX Item "--firstboot-install PKG,PKG.."
-Install the named packages (a comma-separated list). These are installed
-when the guest first boots using the guest’s package manager (eg. apt, yum,
-etc.) and the guest’s network connection.
+Install the named packages (a comma-separated list). These are installed when the guest first boots using the guest’s package manager (eg. apt, yum, etc.) and the guest’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0.
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0.
.IP "\fB\-\-hostname\fR \s-1HOSTNAME\s0" 4
.IX Item "--hostname HOSTNAME"
-Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted
-hostname.domainname (\s-1FQDN\s0) if you want.
+Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted hostname.domainname (\s-1FQDN\s0) if you want.
.IP "\fB\-\-install\fR \s-1PKG,PKG..\s0" 4
.IX Item "--install PKG,PKG.."
-Install the named packages (a comma-separated list). These are installed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.) and the host’s network connection.
+Install the named packages (a comma-separated list). These are installed during the image build using the guest’s package manager (eg. apt, yum, etc.) and the host’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0.
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0.
.Sp
See also \fI\-\-update\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-link\fR TARGET:LINK[:LINK..]" 4
.IX Item "--link TARGET:LINK[:LINK..]"
-Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at
-\&\f(CW\*(C`TARGET\*(C'\fR.
+Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at \f(CW\*(C`TARGET\*(C'\fR.
.IP "\fB\-\-mkdir\fR \s-1DIR\s0" 4
.IX Item "--mkdir DIR"
Create a directory in the guest.
.Sp
-This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it
-also works if the directory already exists.
+This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it also works if the directory already exists.
.IP "\fB\-\-move\fR \s-1SOURCE:DEST\s0" 4
.IX Item "--move SOURCE:DEST"
Move files or directories inside the guest.
Wildcards cannot be used.
.IP "\fB\-\-no\-logfile\fR" 4
.IX Item "--no-logfile"
-Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after
-building is complete. If you don't want to reveal precisely how the image
-was built, use this option.
+Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after building is complete. If you don't want to reveal precisely how the image was built, use this option.
.Sp
See also: \*(L"\s-1LOG FILE\*(R"\s0.
.IP "\fB\-\-password\fR \s-1USER:SELECTOR\s0" 4
.IX Item "--password USER:SELECTOR"
-Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user
-account).
+Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user account).
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.IP "\fB\-\-password\-crypto\fR md5|sha256|sha512" 4
.IX Item "--password-crypto md5|sha256|sha512"
-When the virt tools change or set a password in the guest, this option sets
-the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
+When the virt tools change or set a password in the guest, this option sets the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
.Sp
-\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the
-guest).
+\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the guest).
.Sp
-\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not
-secure against modern attacks.
+\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not secure against modern attacks.
.Sp
-The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't
-have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can
-override libguestfs by specifying this option.
+The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can override libguestfs by specifying this option.
.Sp
-Note this does not change the default password encryption used by the guest
-when you create new user accounts inside the guest. If you want to do that,
-then you should use the \fI\-\-edit\fR option to modify
-\&\f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR
-(Debian, Ubuntu).
+Note this does not change the default password encryption used by the guest when you create new user accounts inside the guest. If you want to do that, then you should use the \fI\-\-edit\fR option to modify \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.IP "\fB\-\-root\-password\fR \s-1SELECTOR\s0" 4
.IX Item "--root-password SELECTOR"
Set the root password.
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.Sp
-Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest
-is given a \fIrandom\fR root password.
+Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest is given a \fIrandom\fR root password.
.IP "\fB\-\-run\fR \s-1SCRIPT\s0" 4
.IX Item "--run SCRIPT"
-Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image.
-The script runs virtualized inside a small appliance, chrooted into the
-guest filesystem.
+Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image. The script runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
The script is automatically chmod +x.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\fR options. They run in the same order that
-they appear on the command line.
+You can have multiple \fI\-\-run\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-run\-command\fR '\s-1CMD+ARGS\s0'" 4
.IX Item "--run-command 'CMD+ARGS'"
-Run the command and arguments on the disk image. The command runs
-virtualized inside a small appliance, chrooted into the guest filesystem.
+Run the command and arguments on the disk image. The command runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\-command\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-run\-command\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-scrub\fR \s-1FILE\s0" 4
.IX Item "--selinux-relabel"
Relabel files in the guest so that they have the correct SELinux label.
.Sp
-This will attempt to relabel files immediately, but if the operation fails
-this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel
-operation for the next time the image boots.
+This will attempt to relabel files immediately, but if the operation fails this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel operation for the next time the image boots.
.Sp
You should only use this option for guests which support SELinux.
.IP "\fB\-\-sm\-attach\fR \s-1SELECTOR\s0" 4
.IX Item "--sm-attach SELECTOR"
Attach to a pool using \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.IP "\fB\-\-sm\-credentials\fR \s-1SELECTOR\s0" 4
.IX Item "--sm-credentials SELECTOR"
Set the credentials for \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.IP "\fB\-\-sm\-register\fR" 4
.IX Item "--sm-register"
Register the guest using \f(CW\*(C`subscription\-manager\*(C'\fR.
Unregister the guest using \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-ssh\-inject\fR USER[:SELECTOR]" 4
.IX Item "--ssh-inject USER[:SELECTOR]"
-Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh
-without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
+Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
.Sp
See \*(L"\s-1SSH KEYS\*(R"\s0 for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.Sp
-You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also
-for more keys for each user.
+You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also for more keys for each user.
.IP "\fB\-\-timezone\fR \s-1TIMEZONE\s0" 4
.IX Item "--timezone TIMEZONE"
-Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string
-like \f(CW\*(C`Europe/London\*(C'\fR
+Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string like \f(CW\*(C`Europe/London\*(C'\fR
.IP "\fB\-\-touch\fR \s-1FILE\s0" 4
.IX Item "--touch FILE"
This command performs a \fBtouch\fR\|(1)\-like operation on \f(CW\*(C`FILE\*(C'\fR.
.IP "\fB\-\-truncate\fR \s-1FILE\s0" 4
.IX Item "--truncate FILE"
-This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist
-already.
+This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist already.
.IP "\fB\-\-truncate\-recursive\fR \s-1PATH\s0" 4
.IX Item "--truncate-recursive PATH"
This command recursively truncates all files under \f(CW\*(C`PATH\*(C'\fR to zero-length.
.IP "\fB\-\-uninstall\fR \s-1PKG,PKG..\s0" 4
.IX Item "--uninstall PKG,PKG.."
-Uninstall the named packages (a comma-separated list). These are removed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.). Dependent packages may also need to be uninstalled to satisfy the
-request.
+Uninstall the named packages (a comma-separated list). These are removed during the image build using the guest’s package manager (eg. apt, yum, etc.). Dependent packages may also need to be uninstalled to satisfy the request.
.Sp
See also \fI\-\-install\fR, \fI\-\-update\fR.
.IP "\fB\-\-update\fR" 4
.IX Item "--update"
-Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command
-is required to update the packages already installed in the template to
-their latest versions.
+Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command is required to update the packages already installed in the template to their latest versions.
.Sp
See also \fI\-\-install\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-upload\fR \s-1FILE:DEST\s0" 4
.IX Item "--upload FILE:DEST"
-Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File
-owner and permissions from the original are preserved, so you should set
-them to what you want them to be in the disk image.
+Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File owner and permissions from the original are preserved, so you should set them to what you want them to be in the disk image.
.Sp
-\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on
-upload.
+\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on upload.
.Sp
-If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then
-the file is uploaded into that directory, and it keeps the same name as on
-the local filesystem.
+If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then the file is uploaded into that directory, and it keeps the same name as on the local filesystem.
.Sp
See also: \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.IP "\fB\-\-write\fR \s-1FILE:CONTENT\s0" 4
.IX Header "REFERENCE"
.SS "\s-1INSTALLING PACKAGES\s0"
.IX Subsection "INSTALLING PACKAGES"
-There are several approaches to installing packages or applications in the
-guest which have different trade-offs.
+There are several approaches to installing packages or applications in the guest which have different trade-offs.
.PP
\fIInstalling packages at build time\fR
.IX Subsection "Installing packages at build time"
.PP
-If the guest \s-1OS\s0 you are installing is similar to the host \s-1OS\s0 (eg. both are
-Linux), and if libguestfs supports network connections, then you can use
-\&\fI\-\-install\fR to install packages like this:
+If the guest \s-1OS\s0 you are installing is similar to the host \s-1OS\s0 (eg. both are Linux), and if libguestfs supports network connections, then you can use \fI\-\-install\fR to install packages like this:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-install inkscape
\& virt\-builder fedora\-27 \-\-update
.Ve
.PP
-Most of the templates that ship with virt-builder come with a very minimal
-selection of packages (known as a \*(L"\s-1JEOS\*(R"\s0 or \*(L"Just Enough Operating System\*(R"),
-which are up to date at the time the template is created, but could be out
-of date by the time you come to install an \s-1OS\s0 from the template. This
-option updates those template packages.
+Most of the templates that ship with virt-builder come with a very minimal selection of packages (known as a \*(L"\s-1JEOS\*(R"\s0 or \*(L"Just Enough Operating System\*(R"), which are up to date at the time the template is created, but could be out of date by the time you come to install an \s-1OS\s0 from the template. This option updates those template packages.
.PP
\fIInstalling packages at first boot\fR
.IX Subsection "Installing packages at first boot"
.PP
This uses the guest’s package manager and the guest’s network connection.
.PP
-The downsides are that it will take the guest a lot longer to boot first
-time, and there’s nothing much you can do if package installation fails
-(eg. if a network problem means the guest can't reach the package
-repositories).
+The downsides are that it will take the guest a lot longer to boot first time, and there’s nothing much you can do if package installation fails (eg. if a network problem means the guest can't reach the package repositories).
.PP
\fIInstalling packages at build time from a side repository\fR
.IX Subsection "Installing packages at build time from a side repository"
.PP
-If the software you want to install is not available in the main package
-repository of the guest, then you can add a side repository. Usually this
-is presented as an \s-1ISO\s0 (\s-1CD\s0 disk image) file containing extra packages.
+If the software you want to install is not available in the main package repository of the guest, then you can add a side repository. Usually this is presented as an \s-1ISO\s0 (\s-1CD\s0 disk image) file containing extra packages.
.PP
-You can create the disk image using either \fBgenisoimage\fR\|(1) or
-\&\fBvirt\-make\-fs\fR\|(1). For genisoimage, use a command like this:
+You can create the disk image using either \fBgenisoimage\fR\|(1) or \fBvirt\-make\-fs\fR\|(1). For genisoimage, use a command like this:
.PP
.Vb 1
\& genisoimage \-o extra\-packages.iso \-R \-J \-V EXTRA cdcontents/
.Ve
.PP
-Create a script that mounts the \s-1ISO\s0 and sets up the repository. For dnf,
-create /tmp/install.sh containing:
+Create a script that mounts the \s-1ISO\s0 and sets up the repository. For dnf, create /tmp/install.sh containing:
.PP
.Vb 2
\& mkdir /tmp/mount
\& apt\-get \-y install famousdatabase
.Ve
.PP
-Use the \fI\-\-attach\fR option to attach the \s-1CD /\s0 disk image and the \fI\-\-run\fR
-option to run the script:
+Use the \fI\-\-attach\fR option to attach the \s-1CD /\s0 disk image and the \fI\-\-run\fR option to run the script:
.PP
.Vb 3
\& virt\-builder fedora\-27 \e
.Ve
.SS "\s-1USERS AND PASSWORDS\s0"
.IX Subsection "USERS AND PASSWORDS"
-The \fI\-\-root\-password\fR option is used to change the root password (otherwise
-a random password is used). This option takes a password \f(CW\*(C`SELECTOR\*(C'\fR in one
-of the following formats:
+The \fI\-\-root\-password\fR option is used to change the root password (otherwise a random password is used). This option takes a password \f(CW\*(C`SELECTOR\*(C'\fR in one of the following formats:
.IP "\fB\-\-root\-password\fR file:FILENAME" 4
.IX Item "--root-password file:FILENAME"
-Read the root password from \f(CW\*(C`FILENAME\*(C'\fR. The whole first line of this file
-is the replacement password. Any other lines are ignored. You should
-create the file with mode 0600 to ensure no one else can read it.
+Read the root password from \f(CW\*(C`FILENAME\*(C'\fR. The whole first line of this file is the replacement password. Any other lines are ignored. You should create the file with mode 0600 to ensure no one else can read it.
.IP "\fB\-\-root\-password\fR password:PASSWORD" 4
.IX Item "--root-password password:PASSWORD"
Set the root password to the literal string \f(CW\*(C`PASSWORD\*(C'\fR.
.Sp
-\&\fBNote: this is not secure\fR since any user on the same machine can see the
-cleartext password using \fBps\fR\|(1).
+\&\fBNote: this is not secure\fR since any user on the same machine can see the cleartext password using \fBps\fR\|(1).
.IP "\fB\-\-root\-password\fR random" 4
.IX Item "--root-password random"
-Choose a random password, which is printed on stdout. The password has
-approximately 120 bits of randomness.
+Choose a random password, which is printed on stdout. The password has approximately 120 bits of randomness.
.Sp
これがデフォルトです。
.IP "\fB\-\-root\-password\fR disabled" 4
.IX Item "--root-password disabled"
-The root account password is disabled. This is like putting \f(CW\*(C`*\*(C'\fR in the
-password field.
+The root account password is disabled. This is like putting \f(CW\*(C`*\*(C'\fR in the password field.
.IP "\fB\-\-root\-password\fR locked:file:FILENAME" 4
.IX Item "--root-password locked:file:FILENAME"
.PD 0
.IP "\fB\-\-root\-password\fR locked:random" 4
.IX Item "--root-password locked:random"
.PD
-The root account is locked, but a password is placed on the account. If
-first unlocked (using \f(CW\*(C`passwd \-u\*(C'\fR) then logins will use the given password.
+The root account is locked, but a password is placed on the account. If first unlocked (using \f(CW\*(C`passwd \-u\*(C'\fR) then logins will use the given password.
.IP "\fB\-\-root\-password\fR locked" 4
.IX Item "--root-password locked"
.PD 0
\fICreating user accounts\fR
.IX Subsection "Creating user accounts"
.PP
-To create user accounts, use the \fBuseradd\fR\|(8) command with
-\&\-\-firstboot\-command like this:
+To create user accounts, use the \fBuseradd\fR\|(8) command with \-\-firstboot\-command like this:
.PP
.Vb 2
\& virt\-builder \-\-firstboot\-command \e
\& \*(Aquseradd \-m \-p "" rjones ; chage \-d 0 rjones\*(Aq
.Ve
.PP
-The above command will create an \f(CW\*(C`rjones\*(C'\fR account with no password, and
-force the user to set a password when they first log in. There are other
-ways to manage passwords, see \fBuseradd\fR\|(8) for details.
+The above command will create an \f(CW\*(C`rjones\*(C'\fR account with no password, and force the user to set a password when they first log in. There are other ways to manage passwords, see \fBuseradd\fR\|(8) for details.
.SS "\s-1KEYBOARD LAYOUT\s0"
.IX Subsection "KEYBOARD LAYOUT"
-Because there are so many different ways to set the keyboard layout in Linux
-distributions, virt-builder does not yet attempt to have a simple command
-line option. This section describes how to set the keyboard for some common
-Linux distributions.
+Because there are so many different ways to set the keyboard layout in Linux distributions, virt-builder does not yet attempt to have a simple command line option. This section describes how to set the keyboard for some common Linux distributions.
.PP
\fIKeyboard layout with systemd\fR
.IX Subsection "Keyboard layout with systemd"
\& \-\-firstboot\-command \*(Aqlocalectl set\-keymap uk\*(Aq
.Ve
.PP
-See \fBlocalectl\fR\|(1) and
-https://www.happyassassin.net/2013/11/23/keyboard\-layouts\-in\-fedora\-20\-and\-previously/
-for more details.
+See \fBlocalectl\fR\|(1) and https://www.happyassassin.net/2013/11/23/keyboard\-layouts\-in\-fedora\-20\-and\-previously/ for more details.
.PP
\fIKeyboard layout using \fI/etc/sysconfig/keyboard\fI\fR
.IX Subsection "Keyboard layout using /etc/sysconfig/keyboard"
.PP
-For \s-1RHEL\s0 ≤ 6, Fedora ≤ 18 and similar, upload or modify the keyboard
-configuration file using the \fI\-\-upload\fR, \fI\-\-write\fR or \fI\-\-edit\fR options.
-For example:
+For \s-1RHEL\s0 ≤ 6, Fedora ≤ 18 and similar, upload or modify the keyboard configuration file using the \fI\-\-upload\fR, \fI\-\-write\fR or \fI\-\-edit\fR options. For example:
.PP
.Vb 2
\& virt\-builder centos\-6 \e
\fIKeyboard layout with Debian-derived distros\fR
.IX Subsection "Keyboard layout with Debian-derived distros"
.PP
-For Debian-derived distros using \fI/etc/default/keyboard\fR, upload or modify
-the keyboard file using the \fI\-\-upload\fR, \fI\-\-write\fR or \fI\-\-edit\fR options.
-For example:
+For Debian-derived distros using \fI/etc/default/keyboard\fR, upload or modify the keyboard file using the \fI\-\-upload\fR, \fI\-\-write\fR or \fI\-\-edit\fR options. For example:
.PP
.Vb 2
\& virt\-builder debian\-8 \e
See https://wiki.debian.org/Keyboard.
.SS "\s-1LANGUAGE\s0"
.IX Subsection "LANGUAGE"
-Most Linux distributions support multiple locale settings so that you can
-have guest messages printed in another language such as Russian.
+Most Linux distributions support multiple locale settings so that you can have guest messages printed in another language such as Russian.
.PP
-However there is no single setting which controls this, since extra packages
-may need to be installed to support console and X fonts, and keyboard input
-methods. The packages required, and their configuration is highly
-distro-specific, and it is outside the scope of virt-builder to do this.
+However there is no single setting which controls this, since extra packages may need to be installed to support console and X fonts, and keyboard input methods. The packages required, and their configuration is highly distro-specific, and it is outside the scope of virt-builder to do this.
.PP
This section contains examples for some common Linux distributions.
.PP
\fISetting Japanese in Debian 8 (Jessie)\fR
.IX Subsection "Setting Japanese in Debian 8 (Jessie)"
.PP
-Note that although this enables Japanese in the text console too, it is
-unlikely that you will see properly rendered Japanese there. However
-Japanese is properly rendered in X applications and terminals.
+Note that although this enables Japanese in the text console too, it is unlikely that you will see properly rendered Japanese there. However Japanese is properly rendered in X applications and terminals.
.PP
.Vb 6
\& pkgs=locales,xfce4,\e
.Ve
.SS "\s-1LOG FILE\s0"
.IX Subsection "LOG FILE"
-Scripts and package installation that runs at build time (\fI\-\-run\fR,
-\&\fI\-\-run\-command\fR, \fI\-\-install\fR, \fI\-\-update\fR, but \fInot\fR firstboot) is logged
-in one of the following locations:
+Scripts and package installation that runs at build time (\fI\-\-run\fR, \fI\-\-run\-command\fR, \fI\-\-install\fR, \fI\-\-update\fR, but \fInot\fR firstboot) is logged in one of the following locations:
.IP "\fI/tmp/builder.log\fR" 4
.IX Item "/tmp/builder.log"
On Linux, \s-1BSD,\s0 and other non-Windows guests.
.IX Item "/builder.log"
If \fI/tmp\fR or \fIC:\eTemp\fR is missing.
.PP
-If you don’t want the log file to appear in the final image, then use the
-\&\fI\-\-no\-logfile\fR command line option.
+If you don’t want the log file to appear in the final image, then use the \fI\-\-no\-logfile\fR command line option.
.SS "\s-1SSH KEYS\s0"
.IX Subsection "SSH KEYS"
-The \fI\-\-ssh\-inject\fR option is used to inject ssh keys for users in the
-guest, so they can login without supplying a password.
+The \fI\-\-ssh\-inject\fR option is used to inject ssh keys for users in the guest, so they can login without supplying a password.
.PP
-The \f(CW\*(C`SELECTOR\*(C'\fR part of the option value is optional; in this case,
-\&\fI\-\-ssh\-inject\fR \f(CW\*(C`USER\*(C'\fR means that we look in the \fIcurrent\fR user’s
-\&\fI~/.ssh\fR directory to find the default public \s-1ID\s0 file. That key is
-uploaded. \*(L"default public \s-1ID\*(R"\s0 is the \fIdefault_ID_file\fR file described in
-\&\fBssh\-copy\-id\fR\|(1).
+The \f(CW\*(C`SELECTOR\*(C'\fR part of the option value is optional; in this case, \fI\-\-ssh\-inject\fR \f(CW\*(C`USER\*(C'\fR means that we look in the \fIcurrent\fR user’s \fI~/.ssh\fR directory to find the default public \s-1ID\s0 file. That key is uploaded. \*(L"default public \s-1ID\*(R"\s0 is the \fIdefault_ID_file\fR file described in \fBssh\-copy\-id\fR\|(1).
.PP
If specified, the \f(CW\*(C`SELECTOR\*(C'\fR can be in one of the following formats:
.IP "\fB\-\-ssh\-inject\fR USER:file:FILENAME" 4
Read the ssh key from \fI\s-1FILENAME\s0\fR. \fI\s-1FILENAME\s0\fR is usually a \fI.pub\fR file.
.IP "\fB\-\-ssh\-inject\fR USER:string:KEY_STRING" 4
.IX Item "--ssh-inject USER:string:KEY_STRING"
-Use the specified \f(CW\*(C`KEY_STRING\*(C'\fR. \f(CW\*(C`KEY_STRING\*(C'\fR is usually a public string
-like \fIssh-rsa \s-1AAAA....\s0 user@localhost\fR.
+Use the specified \f(CW\*(C`KEY_STRING\*(C'\fR. \f(CW\*(C`KEY_STRING\*(C'\fR is usually a public string like \fIssh-rsa \s-1AAAA....\s0 user@localhost\fR.
.PP
-In any case, the \fI~USER/.ssh\fR directory and the
-\&\fI~USER/.ssh/authorized_keys\fR file will be created if not existing already.
+In any case, the \fI~USER/.ssh\fR directory and the \fI~USER/.ssh/authorized_keys\fR file will be created if not existing already.
.SS "\s-1FIRST BOOT SCRIPTS\s0"
.IX Subsection "FIRST BOOT SCRIPTS"
-The \fI\-\-firstboot\fR and \fI\-\-firstboot\-command\fR options allow you to execute
-commands at the first boot of the guest. To do so, an init script for the
-guest init system is installed, which takes care of running all the added
-scripts and commands.
+The \fI\-\-firstboot\fR and \fI\-\-firstboot\-command\fR options allow you to execute commands at the first boot of the guest. To do so, an init script for the guest init system is installed, which takes care of running all the added scripts and commands.
.PP
Supported operating systems are:
.IP "Linux" 4
.IX Item "Linux"
-Init systems supported are: systemd, System-V init (known also as sysvinit),
-and Upstart (using the System-V scripts).
+Init systems supported are: systemd, System-V init (known also as sysvinit), and Upstart (using the System-V scripts).
.Sp
-Note that usually init scripts run as root, but with a more limited
-environment than what could be available from a normal shell: for example,
-\&\f(CW$HOME\fR may be unset or empty.
+Note that usually init scripts run as root, but with a more limited environment than what could be available from a normal shell: for example, \f(CW$HOME\fR may be unset or empty.
.Sp
-The output of the first boot scripts is available in the guest as
-\&\fI~root/virt\-sysprep\-firstboot.log\fR.
+The output of the first boot scripts is available in the guest as \fI~root/virt\-sysprep\-firstboot.log\fR.
.IP "Windows" 4
.IX Item "Windows"
-\&\fIrhsrvany.exe\fR, available from sources at
-https://github.com/rwmjones/rhsrvany, or \fIpvvxsvc.exe\fR, available with
-\&\s-1SUSE VMDP\s0 is installed to run the first boot scripts. It is required, and
-the setup of first boot scripts will fail if it is not present.
+\&\fIrhsrvany.exe\fR, available from sources at https://github.com/rwmjones/rhsrvany, or \fIpvvxsvc.exe\fR, available with \s-1SUSE VMDP\s0 is installed to run the first boot scripts. It is required, and the setup of first boot scripts will fail if it is not present.
.Sp
-\&\fIrhsrvany.exe\fR or \fIpvvxsvc.exe\fR is copied from the location pointed to by
-the \f(CW\*(C`VIRT_TOOLS_DATA_DIR\*(C'\fR environment variable; if not set, a compiled-in
-default will be used (something like \fI/usr/share/virt\-tools\fR).
+\&\fIrhsrvany.exe\fR or \fIpvvxsvc.exe\fR is copied from the location pointed to by the \f(CW\*(C`VIRT_TOOLS_DATA_DIR\*(C'\fR environment variable; if not set, a compiled-in default will be used (something like \fI/usr/share/virt\-tools\fR).
.Sp
-The output of the first boot scripts is available in the guest as
-\&\fIC:\eProgram Files\eGuestfs\eFirstboot\elog.txt\fR.
+The output of the first boot scripts is available in the guest as \fIC:\eProgram Files\eGuestfs\eFirstboot\elog.txt\fR.
.SS "SUBSCRIPTION-MANAGER"
.IX Subsection "SUBSCRIPTION-MANAGER"
-It is possible to automate the registration and attaching of the system
-using \f(CW\*(C`subscription\-manager\*(C'\fR. This is typical on Red Hat Enterprise Linux
-guests. There are few options which ease this process, avoid executing
-commands manually and exposing passwords on command line.
-.PP
-\&\fI\-\-sm\-register\fR starts the registration process, and requires
-\&\fI\-\-sm\-credentials\fR to be specified; the format of the \f(CW\*(C`SELECTOR\*(C'\fR of
-\&\fI\-\-sm\-credentials\fR is one of the following formats:
+It is possible to automate the registration and attaching of the system using \f(CW\*(C`subscription\-manager\*(C'\fR. This is typical on Red Hat Enterprise Linux guests. There are few options which ease this process, avoid executing commands manually and exposing passwords on command line.
+.PP
+\&\fI\-\-sm\-register\fR starts the registration process, and requires \fI\-\-sm\-credentials\fR to be specified; the format of the \f(CW\*(C`SELECTOR\*(C'\fR of \fI\-\-sm\-credentials\fR is one of the following formats:
.IP "\fB\-\-sm\-credentials\fR USER:file:FILENAME" 4
.IX Item "--sm-credentials USER:file:FILENAME"
Read the password for the specified \f(CW\*(C`USER\*(C'\fR from \fI\s-1FILENAME\s0\fR.
.IX Item "--sm-credentials USER:password:PASSWORD"
Use the literal string \f(CW\*(C`PASSWORD\*(C'\fR for the specified \f(CW\*(C`USER\*(C'\fR.
.PP
-\&\fI\-\-sm\-attach\fR attaches the system to subscriptions; the format of its
-\&\f(CW\*(C`SELECTOR\*(C'\fR is one of the following:
+\&\fI\-\-sm\-attach\fR attaches the system to subscriptions; the format of its \f(CW\*(C`SELECTOR\*(C'\fR is one of the following:
.IP "\fB\-\-sm\-attach\fR auto" 4
.IX Item "--sm-attach auto"
-\&\f(CW\*(C`subscription\-manager\*(C'\fR attaches to the best-fitting subscriptions for the
-system.
+\&\f(CW\*(C`subscription\-manager\*(C'\fR attaches to the best-fitting subscriptions for the system.
.IP "\fB\-\-sm\-attach\fR file:FILENAME" 4
.IX Item "--sm-attach file:FILENAME"
Read the pool \s-1ID\s0 from \fI\s-1FILENAME\s0\fR.
.IX Item "--sm-attach pool:POOL"
Use the literal string \f(CW\*(C`POOL\*(C'\fR as pool \s-1ID.\s0
.PP
-\&\fI\-\-sm\-remove\fR removes all the subscriptions from the guest, while
-\&\fI\-\-sm\-unregister\fR completely unregister the system.
+\&\fI\-\-sm\-remove\fR removes all the subscriptions from the guest, while \fI\-\-sm\-unregister\fR completely unregister the system.
.SS "\s-1INSTALLATION PROCESS\s0"
.IX Subsection "INSTALLATION PROCESS"
When you invoke virt-builder, installation proceeds as follows:
.IP "\(bu" 4
The template image is downloaded.
.Sp
-If the template image is present in the cache, the cached version is used
-instead. (See \*(L"\s-1CACHING\*(R"\s0).
+If the template image is present in the cache, the cached version is used instead. (See \*(L"\s-1CACHING\*(R"\s0).
.IP "\(bu" 4
The template signature is checked.
.IP "\(bu" 4
.IP "\(bu" 4
A new random seed is generated for the guest.
.IP "\(bu" 4
-Guest customization is performed, in the order specified on the command
-line.
+Guest customization is performed, in the order specified on the command line.
.IP "\(bu" 4
SELinux relabelling is done (\fI\-\-selinux\-relabel\fR).
.SS "\s-1IMPORTING THE DISK IMAGE\s0"
\fIImporting into libvirt\fR
.IX Subsection "Importing into libvirt"
.PP
-Import the disk image into libvirt using \fBvirt\-install\fR\|(1) \fI\-\-import\fR
-option.
+Import the disk image into libvirt using \fBvirt\-install\fR\|(1) \fI\-\-import\fR option.
.PP
.Vb 3
\& virt\-install \-\-import \e
.PP
注:
.IP "1." 4
-You \fImust\fR specify the correct format. The format is \f(CW\*(C`raw\*(C'\fR unless you
-used virt\-builder’s \fI\-\-format\fR option.
+You \fImust\fR specify the correct format. The format is \f(CW\*(C`raw\*(C'\fR unless you used virt\-builder’s \fI\-\-format\fR option.
.IP "2." 4
-\&\fI\-\-os\-variant\fR is highly recommended, because it will present optimum
-devices to enable the guest to run most efficiently. To get a list of all
-variants, do:
+\&\fI\-\-os\-variant\fR is highly recommended, because it will present optimum devices to enable the guest to run most efficiently. To get a list of all variants, do:
.Sp
.Vb 1
\& osinfo\-query os
.Sp
The above tool is provided by libosinfo package.
.IP "3." 4
-You can run virt-install as root or non-root. Each works slightly
-differently because libvirt manages a different set of virtual machines for
-each user. In particular virt-manager normally shows the root-owned VMs,
-whereas Boxes shows the user-owned VMs, and other tools probably work
-differently as well.
+You can run virt-install as root or non-root. Each works slightly differently because libvirt manages a different set of virtual machines for each user. In particular virt-manager normally shows the root-owned VMs, whereas Boxes shows the user-owned VMs, and other tools probably work differently as well.
.PP
\fIImporting into OpenStack\fR
.IX Subsection "Importing into OpenStack"
\& \-\-is\-public True
.Ve
.PP
-The \fI\-\-file\fR parameter is the virt-builder-generated disk image. It should
-match virt\-builder’s \fI\-\-output\fR option. The \fI\-\-disk\-format\fR parameter
-should match virt\-builder’s \fI\-\-format\fR option (or \f(CW\*(C`raw\*(C'\fR if you didn't use
-that option). The \fI\-\-container\-format\fR should always be \f(CW\*(C`bare\*(C'\fR since
-virt-builder doesn't put images into containers.
+The \fI\-\-file\fR parameter is the virt-builder-generated disk image. It should match virt\-builder’s \fI\-\-output\fR option. The \fI\-\-disk\-format\fR parameter should match virt\-builder’s \fI\-\-format\fR option (or \f(CW\*(C`raw\*(C'\fR if you didn't use that option). The \fI\-\-container\-format\fR should always be \f(CW\*(C`bare\*(C'\fR since virt-builder doesn't put images into containers.
.PP
-You can use the \f(CW\*(C`glance image\-show \f(CIfedora\-27\-image\f(CW\*(C'\fR command to
-display the properties of the image.
+You can use the \f(CW\*(C`glance image\-show \f(CIfedora\-27\-image\f(CW\*(C'\fR command to display the properties of the image.
.PP
To boot up an instance of your image on a Nova compute node, do:
.PP
\fIBooting directly using qemu or \s-1KVM\s0\fR
.IX Subsection "Booting directly using qemu or KVM"
.PP
-The qemu command line is not very stable or easy to use, hence libvirt
-should be used if possible. However a command line similar to the following
-could be used to boot the virtual machine:
+The qemu command line is not very stable or easy to use, hence libvirt should be used if possible. However a command line similar to the following could be used to boot the virtual machine:
.PP
.Vb 5
\& qemu\-system\-x86_64 \e
\& \-drive file=disk.img,format=raw,if=virtio
.Ve
.PP
-As with libvirt, it is very important that the correct format is chosen. It
-will be \f(CW\*(C`raw\*(C'\fR unless the \fI\-\-format\fR option was used.
+As with libvirt, it is very important that the correct format is chosen. It will be \f(CW\*(C`raw\*(C'\fR unless the \fI\-\-format\fR option was used.
.SS "\s-1CONFIGURATION MANAGEMENT\s0"
.IX Subsection "CONFIGURATION MANAGEMENT"
\fIPuppet\fR
.IX Subsection "Puppet"
.PP
-To enable the Puppet agent in a guest, install the package, point the
-configuration at your Puppetmaster, and ensure the agent runs at boot.
+To enable the Puppet agent in a guest, install the package, point the configuration at your Puppetmaster, and ensure the agent runs at boot.
.PP
A typical virt-builder command would be:
.PP
\& \-\-selinux\-relabel
.Ve
.PP
-The precise instructions vary according to the Linux distro. For further
-information see: https://docs.puppet.com/puppet/latest/install_pre.html
+The precise instructions vary according to the Linux distro. For further information see: https://docs.puppet.com/puppet/latest/install_pre.html
.SS "\s-1DEBUGGING BUILDS\s0"
.IX Subsection "DEBUGGING BUILDS"
-If virt-builder itself fails, then enable debugging (\fI\-v\fR) and report a bug
-(see \*(L"\s-1BUGS\*(R"\s0 below).
+If virt-builder itself fails, then enable debugging (\fI\-v\fR) and report a bug (see \*(L"\s-1BUGS\*(R"\s0 below).
.PP
-If virt-builder fails because some script or package it is installing fails,
-try using \fI\-\-no\-delete\-on\-failure\fR to preserve the output file, and
-continue reading this section.
+If virt-builder fails because some script or package it is installing fails, try using \fI\-\-no\-delete\-on\-failure\fR to preserve the output file, and continue reading this section.
.PP
-If virt-builder is successful but the image doesn't work, here are some
-things to try:
+If virt-builder is successful but the image doesn't work, here are some things to try:
.IP "Use virt-rescue" 4
.IX Item "Use virt-rescue"
Run \fBvirt\-rescue\fR\|(1) on the disk image:
\& virt\-rescue \-a disk.img
.Ve
.Sp
-This gives you a rescue shell. You can mount the filesystems from the disk
-image on \fI/sysroot\fR and examine them using ordinary Linux commands. You
-can also chroot into the guest to reinstall the bootloader. The virt-rescue
-man page has a lot more information and examples.
+This gives you a rescue shell. You can mount the filesystems from the disk image on \fI/sysroot\fR and examine them using ordinary Linux commands. You can also chroot into the guest to reinstall the bootloader. The virt-rescue man page has a lot more information and examples.
.IP "Use guestfish" 4
.IX Item "Use guestfish"
Run \fBguestfish\fR\|(1) on the disk image:
\& guestfish \-a disk.img \-i
.Ve
.Sp
-Use guestfish commands like \f(CW\*(C`ll /directory\*(C'\fR and \f(CW\*(C`cat /file\*(C'\fR to examine
-directories and files.
+Use guestfish commands like \f(CW\*(C`ll /directory\*(C'\fR and \f(CW\*(C`cat /file\*(C'\fR to examine directories and files.
.IP "Use guestmount" 4
.IX Item "Use guestmount"
Mount the disk image safely on the host using \s-1FUSE\s0 and \fBguestmount\fR\|(1):
.Ve
.IP "Add a serial console" 4
.IX Item "Add a serial console"
-If the guest hangs during boot, it can be helpful to add a serial console to
-the guest, and direct kernel messages to the serial console. Adding the
-serial console will involve looking at the documentation for your
-hypervisor. To direct kernel messages to the serial console, add the
-following on the kernel command line:
+If the guest hangs during boot, it can be helpful to add a serial console to the guest, and direct kernel messages to the serial console. Adding the serial console will involve looking at the documentation for your hypervisor. To direct kernel messages to the serial console, add the following on the kernel command line:
.Sp
.Vb 1
\& console=tty0 console=ttyS0,115200
.Ve
.SS "\s-1SOURCES OF TEMPLATES\s0"
.IX Subsection "SOURCES OF TEMPLATES"
-virt-builder reads the available sources from configuration files, with the
-\&\fI.conf\fR extension and located in the following paths:
+virt-builder reads the available sources from configuration files, with the \fI.conf\fR extension and located in the following paths:
.IP "\(bu" 4
-\&\f(CW$XDG_CONFIG_HOME\fR/virt\-builder/repos.d/ (\f(CW$XDG_CONFIG_HOME\fR is
-\&\fI\f(CI$HOME\fI/.config\fR if not set).
+\&\f(CW$XDG_CONFIG_HOME\fR/virt\-builder/repos.d/ (\f(CW$XDG_CONFIG_HOME\fR is \fI\f(CI$HOME\fI/.config\fR if not set).
.IP "\(bu" 4
-\&\f(CW$VIRT_BUILDER_DIRS\fR/virt\-builder/repos.d/ (where \f(CW$VIRT_BUILDER_DIRS\fR means
-any of the directories in that environment variable, or just \fI/etc\fR if not
-set).
+\&\f(CW$VIRT_BUILDER_DIRS\fR/virt\-builder/repos.d/ (where \f(CW$VIRT_BUILDER_DIRS\fR means any of the directories in that environment variable, or just \fI/etc\fR if not set).
.PP
-Each \fI.conf\fR file in those paths has a simple text format like the
-following:
+Each \fI.conf\fR file in those paths has a simple text format like the following:
.PP
.Vb 3
\& [libguestfs.org]
\& gpgkey=file:///etc/xdg/virt\-builder/repos.d/libguestfs.gpg
.Ve
.PP
-The part in square brackets is the repository identifier, which is used as
-unique identifier.
+The part in square brackets is the repository identifier, which is used as unique identifier.
.PP
The following fields can appear:
.ie n .IP """uri=URI""" 4
.ie n .IP """gpgkey=URI""" 4
.el .IP "\f(CWgpgkey=URI\fR" 4
.IX Item "gpgkey=URI"
-This optional field represents the \s-1URI\s0 (although only \fIfile://\fR URIs are
-accepted) of the key used to sign the index file. If not present, the index
-file referred by \fIuri=..\fR is not signed.
+This optional field represents the \s-1URI\s0 (although only \fIfile://\fR URIs are accepted) of the key used to sign the index file. If not present, the index file referred by \fIuri=..\fR is not signed.
.ie n .IP """proxy=MODE""" 4
.el .IP "\f(CWproxy=MODE\fR" 4
.IX Item "proxy=MODE"
-This optional field specifies the proxy mode, to be used when downloading
-the index file of this repository. The possible values are:
+This optional field specifies the proxy mode, to be used when downloading the index file of this repository. The possible values are:
.RS 4
.IP "\fBno\fR, \fBoff\fR" 4
.IX Item "no, off"
The proxy used is the system one.
.IP "\fIanything else\fR" 4
.IX Item "anything else"
-Specifies the actual proxy configuration to be used, overriding the system
-configuration.
+Specifies the actual proxy configuration to be used, overriding the system configuration.
.RE
.RS 4
.Sp
-If not present, the assumed value is to respect the proxy settings of the
-system (i.e. as if \fBsystem\fR would be specified).
+If not present, the assumed value is to respect the proxy settings of the system (i.e. as if \fBsystem\fR would be specified).
.RE
.ie n .IP """format=FORMAT""" 4
.el .IP "\f(CWformat=FORMAT\fR" 4
.IX Item "format=FORMAT"
-This optional field specifies the format of the repository. The possible
-values are:
+This optional field specifies the format of the repository. The possible values are:
.RS 4
.IP "\fBnative\fR" 4
.IX Item "native"
-The native format of the \f(CW\*(C`virt\-builder\*(C'\fR repository. See also \*(L"Creating
-and signing the index file\*(R" below.
+The native format of the \f(CW\*(C`virt\-builder\*(C'\fR repository. See also \*(L"Creating and signing the index file\*(R" below.
.IP "\fBsimplestreams\fR" 4
.IX Item "simplestreams"
The \s-1URI\s0 represents the root of a Simple Streams v1.0 tree of metadata.
.Sp
-For more information about Simple Streams, see also
-https://launchpad.net/simplestreams.
+For more information about Simple Streams, see also https://launchpad.net/simplestreams.
.RE
.RS 4
.Sp
If not present, the assumed value is \f(CW\*(C`native\*(C'\fR.
.RE
.PP
-For serious virt-builder use, you may want to create your own repository of
-templates.
+For serious virt-builder use, you may want to create your own repository of templates.
.PP
\fILibguestfs.org repository\fR
.IX Subsection "Libguestfs.org repository"
.PP
-Out of the box, virt-builder downloads the file
-http://libguestfs.org/download/builder/index.asc which is an index of
-available templates plus some information about each one, wrapped up in a
-digital signature. The command \f(CW\*(C`virt\-builder \-\-list\*(C'\fR lists out the
-information in this index file.
+Out of the box, virt-builder downloads the file http://libguestfs.org/download/builder/index.asc which is an index of available templates plus some information about each one, wrapped up in a digital signature. The command \f(CW\*(C`virt\-builder \-\-list\*(C'\fR lists out the information in this index file.
.PP
-The templates hosted on libguestfs.org were created using shell scripts,
-kickstart files and preseed files which can be found in the libguestfs
-source tree, in \f(CW\*(C`builder/templates\*(C'\fR.
+The templates hosted on libguestfs.org were created using shell scripts, kickstart files and preseed files which can be found in the libguestfs source tree, in \f(CW\*(C`builder/templates\*(C'\fR.
.PP
\fISetting up the repository\fR
.IX Subsection "Setting up the repository"
.PP
-You can set up your own site containing an index file and some templates,
-and then point virt-builder at the site by creating a \fI.conf\fR file pointing
-to it.
+You can set up your own site containing an index file and some templates, and then point virt-builder at the site by creating a \fI.conf\fR file pointing to it.
.PP
-Note that if your index is signed, you will need to properly fill
-\&\fIgpgkey=..\fR in your \fI.conf\fR file, making sure to deploy also the \s-1GPG\s0 key
-file.
+Note that if your index is signed, you will need to properly fill \fIgpgkey=..\fR in your \fI.conf\fR file, making sure to deploy also the \s-1GPG\s0 key file.
.PP
.Vb 3
\& virt\-builder \-\-source https://example.com/builder/index.asc \e
\& \-\-list
.Ve
.PP
-You can host this on any web or \s-1FTP\s0 server, or a local or network
-filesystem.
+You can host this on any web or \s-1FTP\s0 server, or a local or network filesystem.
.PP
\fISetting up a \s-1GPG\s0 key\fR
.IX Subsection "Setting up a GPG key"
.PP
-If you don’t have a GnuPG key, you will need to set one up. (Strictly
-speaking this is optional, but if your index and template files are not
-signed then virt-builder users will have to use the \fI\-\-no\-check\-signature\fR
-flag every time they use virt-builder.)
+If you don’t have a GnuPG key, you will need to set one up. (Strictly speaking this is optional, but if your index and template files are not signed then virt-builder users will have to use the \fI\-\-no\-check\-signature\fR flag every time they use virt-builder.)
.PP
-To create a key, see the \s-1GPG\s0 manual
-http://www.gnupg.org/gph/en/manual.html.
+To create a key, see the \s-1GPG\s0 manual http://www.gnupg.org/gph/en/manual.html.
.PP
Export your \s-1GPG\s0 public key:
.PP
\fICreate the templates\fR
.IX Subsection "Create the templates"
.PP
-There are many ways to create the templates. For example you could clone
-existing guests (see \fBvirt\-sysprep\fR\|(1)), or you could install a guest by
-hand (\fBvirt\-install\fR\|(1)). To see how the templates were created for
-virt-builder, look at the scripts in \f(CW\*(C`builder/templates\*(C'\fR
+There are many ways to create the templates. For example you could clone existing guests (see \fBvirt\-sysprep\fR\|(1)), or you could install a guest by hand (\fBvirt\-install\fR\|(1)). To see how the templates were created for virt-builder, look at the scripts in \f(CW\*(C`builder/templates\*(C'\fR
.PP
-Virt-builder supports any image format (e.g. raw, qcow2, etc) as template,
-both as-is, and compressed as \s-1XZ.\s0 This way, existing images (e.g. cleaned
-using \fBvirt\-sysprep\fR\|(1)) can be used as templates.
+Virt-builder supports any image format (e.g. raw, qcow2, etc) as template, both as-is, and compressed as \s-1XZ.\s0 This way, existing images (e.g. cleaned using \fBvirt\-sysprep\fR\|(1)) can be used as templates.
.PP
-For best results when compressing the templates, use the following xz
-options (see \fBnbdkit\-xz\-plugin\fR\|(1) for further explanation):
+For best results when compressing the templates, use the following xz options (see \fBnbdkit\-xz\-plugin\fR\|(1) for further explanation):
.PP
.Vb 1
\& xz \-\-best \-\-block\-size=16777216 disk
\fICreating and signing the index file\fR
.IX Subsection "Creating and signing the index file"
.PP
-The index file has a simple text format (shown here without the digital
-signature):
+The index file has a simple text format (shown here without the digital signature):
.PP
.Vb 10
\& [fedora\-18]
\& expand=/dev/sda3
.Ve
.PP
-The part in square brackets is the \f(CW\*(C`os\-version\*(C'\fR, which is the same string
-that is used on the virt-builder command line to build that \s-1OS.\s0
+The part in square brackets is the \f(CW\*(C`os\-version\*(C'\fR, which is the same string that is used on the virt-builder command line to build that \s-1OS.\s0
.PP
-The index file creation and signature can be eased with the
-\&\fBvirt\-builder\-repository\fR\|(1) tool.
+The index file creation and signature can be eased with the \fBvirt\-builder\-repository\fR\|(1) tool.
.PP
-After preparing the \f(CW\*(C`index\*(C'\fR file in the correct format, clearsign it using
-the following command:
+After preparing the \f(CW\*(C`index\*(C'\fR file in the correct format, clearsign it using the following command:
.PP
.Vb 1
\& gpg \-\-clearsign \-\-armor index
.Ve
.PP
-This will create the final file called \fIindex.asc\fR which can be uploaded to
-the server (and is the \fIuri=..\fR \s-1URL\s0). As noted above, signing the index
-file is optional, but recommended.
+This will create the final file called \fIindex.asc\fR which can be uploaded to the server (and is the \fIuri=..\fR \s-1URL\s0). As noted above, signing the index file is optional, but recommended.
.PP
The following fields can appear:
.ie n .IP """name=NAME""" 4
.el .IP "\f(CWname=NAME\fR" 4
.IX Item "name=NAME"
-The user-friendly name of this template. This is displayed in the \fI\-\-list\fR
-output but is otherwise not significant.
+The user-friendly name of this template. This is displayed in the \fI\-\-list\fR output but is otherwise not significant.
.ie n .IP """osinfo=ID""" 4
.el .IP "\f(CWosinfo=ID\fR" 4
.IX Item "osinfo=ID"
-This optional field maps the operating system to the associated libosinfo
-\&\s-1ID.\s0 Virt-builder does not use it (yet).
+This optional field maps the operating system to the associated libosinfo \s-1ID.\s0 Virt-builder does not use it (yet).
.ie n .IP """arch=ARCH""" 4
.el .IP "\f(CWarch=ARCH\fR" 4
.IX Item "arch=ARCH"
-The architecture of the operating system installed within the template. This
-field is required.
+The architecture of the operating system installed within the template. This field is required.
.ie n .IP """file=PATH""" 4
.el .IP "\f(CWfile=PATH\fR" 4
.IX Item "file=PATH"
The path (relative to the index) of the xz-compressed template.
.Sp
-Note that absolute paths or URIs are \fBnot\fR permitted here. This is because
-virt-builder has a \*(L"same origin\*(R" policy for templates so they cannot come
-from other servers.
+Note that absolute paths or URIs are \fBnot\fR permitted here. This is because virt-builder has a \*(L"same origin\*(R" policy for templates so they cannot come from other servers.
.ie n .IP """sig=PATH""" 4
.el .IP "\f(CWsig=PATH\fR" 4
.IX Item "sig=PATH"
\&\fBThis option is deprecated\fR. Use the checksum field instead.
.Sp
-The path (relative to the index) of the \s-1GPG\s0 detached signature of the xz
-file.
+The path (relative to the index) of the \s-1GPG\s0 detached signature of the xz file.
.Sp
-Note that absolute paths or URIs are \fBnot\fR permitted here. This is because
-virt-builder has a \*(L"same origin\*(R" policy for templates so they cannot come
-from other servers.
+Note that absolute paths or URIs are \fBnot\fR permitted here. This is because virt-builder has a \*(L"same origin\*(R" policy for templates so they cannot come from other servers.
.Sp
The file can be created as follows:
.Sp
.ie n .IP """checksum[sha512]=7b882fe9b82eb0fef...""" 4
.el .IP "\f(CWchecksum[sha512]=7b882fe9b82eb0fef...\fR" 4
.IX Item "checksum[sha512]=7b882fe9b82eb0fef..."
-The \s-1SHA\-512\s0 checksum of the file specified in \fIfile=..\fR is checked after it
-is downloaded. To work out the signature, do:
+The \s-1SHA\-512\s0 checksum of the file specified in \fIfile=..\fR is checked after it is downloaded. To work out the signature, do:
.Sp
.Vb 1
\& sha512sum disk.xz
.Ve
.Sp
-Note if you use this, you don’t need to sign the file, ie. don’t use
-\&\f(CW\*(C`sig\*(C'\fR. This option overrides \f(CW\*(C`sig\*(C'\fR.
+Note if you use this, you don’t need to sign the file, ie. don’t use \f(CW\*(C`sig\*(C'\fR. This option overrides \f(CW\*(C`sig\*(C'\fR.
.ie n .IP """checksum=7b882fe9b82eb0fef...""" 4
.el .IP "\f(CWchecksum=7b882fe9b82eb0fef...\fR" 4
.IX Item "checksum=7b882fe9b82eb0fef..."
\&\f(CW\*(C`checksum\*(C'\fR is an alias for \f(CW\*(C`checksum[sha512]\*(C'\fR.
.Sp
-If you need to interoperate with virt-builder = 1.24.0 then you have to use
-\&\f(CW\*(C`checksum\*(C'\fR because that version would give a parse error with square
-brackets and numbers in the key of a field. This is fixed in virt-builder
-≥ 1.24.1.
+If you need to interoperate with virt-builder = 1.24.0 then you have to use \f(CW\*(C`checksum\*(C'\fR because that version would give a parse error with square brackets and numbers in the key of a field. This is fixed in virt-builder ≥ 1.24.1.
.ie n .IP """revision=N""" 4
.el .IP "\f(CWrevision=N\fR" 4
.IX Item "revision=N"
-The revision is an integer which is used to control the template cache.
-Increasing the revision number causes clients to download the template again
-even if they have a copy in the cache.
+The revision is an integer which is used to control the template cache. Increasing the revision number causes clients to download the template again even if they have a copy in the cache.
.Sp
The revision number is optional. If omitted it defaults to \f(CW1\fR.
.ie n .IP """format=raw""" 4
.el .IP "\f(CWformat=qcow2\fR" 4
.IX Item "format=qcow2"
.PD
-Specify the format of the disk image; in case it is compressed, that is the
-format before the compression. If not given, the format is autodetected,
-but generally it is better to be explicit about the intended format.
+Specify the format of the disk image; in case it is compressed, that is the format before the compression. If not given, the format is autodetected, but generally it is better to be explicit about the intended format.
.Sp
-Note this is the source format, which is different from the \fI\-\-format\fR
-option (requested output format). Virt-builder does on-the-fly conversion
-from the source format to the requested output format.
+Note this is the source format, which is different from the \fI\-\-format\fR option (requested output format). Virt-builder does on-the-fly conversion from the source format to the requested output format.
.ie n .IP """size=NNN""" 4
.el .IP "\f(CWsize=NNN\fR" 4
.IX Item "size=NNN"
-The virtual size of the image in bytes. This is the size of the image when
-uncompressed. If using a non-raw format such as qcow2 then it means the
-virtual disk size, not the size of the qcow2 file.
+The virtual size of the image in bytes. This is the size of the image when uncompressed. If using a non-raw format such as qcow2 then it means the virtual disk size, not the size of the qcow2 file.
.Sp
This field is required.
.Sp
-Virt-builder also uses this as the minimum size that users can request via
-the \fI\-\-size\fR option, or as the default size if there is no \fI\-\-size\fR
-option.
+Virt-builder also uses this as the minimum size that users can request via the \fI\-\-size\fR option, or as the default size if there is no \fI\-\-size\fR option.
.ie n .IP """compressed_size=NNN""" 4
.el .IP "\f(CWcompressed_size=NNN\fR" 4
.IX Item "compressed_size=NNN"
-The actual size of the disk image in bytes, i.e. what was specified in
-\&\fIfile=..\fR. This is just used for information (when using \f(CW\*(C`long\*(C'\fR, and
-\&\f(CW\*(C`json\*(C'\fR formats of \fI\-\-list\fR).
+The actual size of the disk image in bytes, i.e. what was specified in \fIfile=..\fR. This is just used for information (when using \f(CW\*(C`long\*(C'\fR, and \f(CW\*(C`json\*(C'\fR formats of \fI\-\-list\fR).
.ie n .IP """expand=/dev/sdaX""" 4
.el .IP "\f(CWexpand=/dev/sdaX\fR" 4
.IX Item "expand=/dev/sdaX"
-When expanding the image to its final size, instruct \fBvirt\-resize\fR\|(1) to
-expand the named partition in the guest image to fill up all available
-space. This works like the virt-resize \fI\-\-expand\fR option.
+When expanding the image to its final size, instruct \fBvirt\-resize\fR\|(1) to expand the named partition in the guest image to fill up all available space. This works like the virt-resize \fI\-\-expand\fR option.
.Sp
You should usually put the device name of the guest’s root filesystem here.
.Sp
-It’s a good idea to use this, but not required. If the field is omitted
-then virt-resize will create an extra partition at the end of the disk to
-cover the free space, which is much less user-friendly.
+It’s a good idea to use this, but not required. If the field is omitted then virt-resize will create an extra partition at the end of the disk to cover the free space, which is much less user-friendly.
.ie n .IP """lvexpand=/dev/VolGroup/LogVol""" 4
.el .IP "\f(CWlvexpand=/dev/VolGroup/LogVol\fR" 4
.IX Item "lvexpand=/dev/VolGroup/LogVol"
-When expanding the image to its final size, instruct \fBvirt\-resize\fR\|(1) to
-expand the named logical volume in the guest image to fill up all available
-space. This works like the virt-resize \fI\-\-lv\-expand\fR option.
+When expanding the image to its final size, instruct \fBvirt\-resize\fR\|(1) to expand the named logical volume in the guest image to fill up all available space. This works like the virt-resize \fI\-\-lv\-expand\fR option.
.Sp
-If the guest uses \s-1LVM2\s0 you should usually put the \s-1LV\s0 of the guest’s root
-filesystem here. If the guest does not use \s-1LVM2\s0 or its root filesystem is
-not on an \s-1LV,\s0 don't use this option.
+If the guest uses \s-1LVM2\s0 you should usually put the \s-1LV\s0 of the guest’s root filesystem here. If the guest does not use \s-1LVM2\s0 or its root filesystem is not on an \s-1LV,\s0 don't use this option.
.ie n .IP """notes=NOTES""" 4
.el .IP "\f(CWnotes=NOTES\fR" 4
.IX Item "notes=NOTES"
-Any notes that go with this image, especially notes describing what packages
-are in the image, how the image was prepared, and licensing information.
+Any notes that go with this image, especially notes describing what packages are in the image, how the image was prepared, and licensing information.
.Sp
This information is shown in the \fI\-\-notes\fR and \fI\-\-list\fR \fI\-\-long\fR modes.
.Sp
-You can use multi-line notes here by indenting each new line with at least
-one character of whitespace (even on blank lines):
+You can use multi-line notes here by indenting each new line with at least one character of whitespace (even on blank lines):
.Sp
.Vb 5
\& notes=This image was prepared using
.ie n .IP """hidden=true""" 4
.el .IP "\f(CWhidden=true\fR" 4
.IX Item "hidden=true"
-Using the hidden flag prevents the template from being listed by the
-\&\fI\-\-list\fR option (but it is still installable). This is used for test
-images.
+Using the hidden flag prevents the template from being listed by the \fI\-\-list\fR option (but it is still installable). This is used for test images.
.ie n .IP """aliases=ALIAS1 ALIAS2 ...""" 4
.el .IP "\f(CWaliases=ALIAS1 ALIAS2 ...\fR" 4
.IX Item "aliases=ALIAS1 ALIAS2 ..."
-This optional field specifies a list of aliases, separated by spaces, for
-the image. For example, an alias could be used to always point to the
-latest version of a certain image, leaving the old versions available in the
-index instead of updating the same image (see the \f(CW\*(C`revision\*(C'\fR field).
+This optional field specifies a list of aliases, separated by spaces, for the image. For example, an alias could be used to always point to the latest version of a certain image, leaving the old versions available in the index instead of updating the same image (see the \f(CW\*(C`revision\*(C'\fR field).
.PP
\fIRunning virt-builder against multiple sources\fR
.IX Subsection "Running virt-builder against multiple sources"
.PP
-It is possible to use multiple sources with virt-builder. The recommended
-way is to deploy \fI.conf\fR files pointing to the index files. Another way is
-to specify the sources using multiple \fI\-\-source\fR and/or \fI\-\-fingerprint\fR
-options:
+It is possible to use multiple sources with virt-builder. The recommended way is to deploy \fI.conf\fR files pointing to the index files. Another way is to specify the sources using multiple \fI\-\-source\fR and/or \fI\-\-fingerprint\fR options:
.PP
.Vb 3
\& virt\-builder \e
\& \-\-source http://example.com/s2/index.asc
.Ve
.PP
-You can provide N or 1 fingerprints. In the case where you provide N
-fingerprints, N = number of sources and there is a 1\-1 correspondence
-between each source and each fingerprint:
+You can provide N or 1 fingerprints. In the case where you provide N fingerprints, N = number of sources and there is a 1\-1 correspondence between each source and each fingerprint:
.PP
.Vb 3
\& virt\-builder \e
\& \-\-source http://example.com/s2/index.asc \-\-fingerprint \*(Aq9876 ...\*(Aq
.Ve
.PP
-In the case where you provide 1 fingerprint, the same fingerprint is used
-for all sources.
+In the case where you provide 1 fingerprint, the same fingerprint is used for all sources.
.PP
You \f(CW\*(C`must\*(C'\fR provide at least 1 fingerprint.
.PP
\fILicensing of templates\fR
.IX Subsection "Licensing of templates"
.PP
-You should be aware of the licensing of images that you distribute. For
-open source guests, provide a link to the source code in the \f(CW\*(C`notes\*(C'\fR field
-and comply with other requirements (eg. around trademarks).
+You should be aware of the licensing of images that you distribute. For open source guests, provide a link to the source code in the \f(CW\*(C`notes\*(C'\fR field and comply with other requirements (eg. around trademarks).
.PP
\fIFormal specification of the index file\fR
.IX Subsection "Formal specification of the index file"
.PP
-The index file format has a formal specification defined by the flex scanner
-and bison parser used to parse the file. This can be found in the following
-files in the libguestfs source tree:
+The index file format has a formal specification defined by the flex scanner and bison parser used to parse the file. This can be found in the following files in the libguestfs source tree:
.PP
.Vb 2
\& builder/index\-scan.l
\& builder/index\-parse.y
.Ve
.PP
-A tool called \fBvirt\-index\-validate\fR\|(1) is available to validate the index
-file to ensure it is correct.
+A tool called \fBvirt\-index\-validate\fR\|(1) is available to validate the index file to ensure it is correct.
.PP
-Note that the parser and tool can work on either the signed or unsigned
-index file (ie. \fIindex\fR or \fIindex.asc\fR).
+Note that the parser and tool can work on either the signed or unsigned index file (ie. \fIindex\fR or \fIindex.asc\fR).
.PP
The index is always encoded in \s-1UTF\-8.\s0
.SS "\s-1CACHING\s0"
\fICaching templates\fR
.IX Subsection "Caching templates"
.PP
-Since the templates are usually very large, downloaded templates are cached
-in the user’s home directory.
+Since the templates are usually very large, downloaded templates are cached in the user’s home directory.
.PP
-The location of the cache is \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR or
-\&\fI\f(CI$HOME\fI/.cache/virt\-builder\fR.
+The location of the cache is \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR or \fI\f(CI$HOME\fI/.cache/virt\-builder\fR.
.PP
-You can print out information about the cache directory, including which
-guests are currently cached, by doing:
+You can print out information about the cache directory, including which guests are currently cached, by doing:
.PP
.Vb 1
\& virt\-builder \-\-print\-cache
.PP
To disable the template cache, use \fI\-\-no\-cache\fR.
.PP
-Only templates are cached. The index and detached digital signatures are
-not cached.
+Only templates are cached. The index and detached digital signatures are not cached.
.PP
\fICaching packages\fR
.IX Subsection "Caching packages"
.PP
-Virt-builder uses \fBcurl\fR\|(1) to download files and it also uses the current
-\&\f(CW\*(C`http_proxy\*(C'\fR (etc) settings when installing packages (\fI\-\-install\fR,
-\&\fI\-\-update\fR).
+Virt-builder uses \fBcurl\fR\|(1) to download files and it also uses the current \f(CW\*(C`http_proxy\*(C'\fR (etc) settings when installing packages (\fI\-\-install\fR, \fI\-\-update\fR).
.PP
-You may therefore want to set those environment variables in order to
-maximize the amount of local caching that happens. See \*(L"\s-1ENVIRONMENT
-VARIABLES\*(R"\s0 and \fBcurl\fR\|(1).
+You may therefore want to set those environment variables in order to maximize the amount of local caching that happens. See \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 and \fBcurl\fR\|(1).
.PP
\fILocal mirrors\fR
.IX Subsection "Local mirrors"
.PP
-To increase both speed and reliability of installing packages, you can set
-up a local mirror of the target distribution, and point the guest package
-manager at that.
+To increase both speed and reliability of installing packages, you can set up a local mirror of the target distribution, and point the guest package manager at that.
.PP
Using a local mirror with Fedora
.IX Subsection "Using a local mirror with Fedora"
Using a local mirror with Debian
.IX Subsection "Using a local mirror with Debian"
.PP
-Assuming that you are using \f(CW\*(C`apt\-proxy\*(C'\fR to mirror the repository, you
-should create a new \fIsources.list\fR file to point to your proxy (see
-https://help.ubuntu.com/community/AptProxy) and then do:
+Assuming that you are using \f(CW\*(C`apt\-proxy\*(C'\fR to mirror the repository, you should create a new \fIsources.list\fR file to point to your proxy (see https://help.ubuntu.com/community/AptProxy) and then do:
.PP
.Vb 4
\& virt\-builder debian\-8 \e
.Ve
.SS "\s-1DIGITAL SIGNATURES\s0"
.IX Subsection "DIGITAL SIGNATURES"
-Virt-builder uses \s-1GNU\s0 Privacy Guard (GnuPG or gpg) to verify that the index
-and templates have not been tampered with.
+Virt-builder uses \s-1GNU\s0 Privacy Guard (GnuPG or gpg) to verify that the index and templates have not been tampered with.
.PP
The source points to an index file, which is optionally signed.
.PP
-Virt-builder downloads the index and checks that the signature is valid and
-the signer’s fingerprint matches the specified fingerprint (ie. the one
-specified in \fIgpgkey=..\fR in the \fI.conf\fR, or with \fI\-\-fingerprint\fR, in that
-order).
+Virt-builder downloads the index and checks that the signature is valid and the signer’s fingerprint matches the specified fingerprint (ie. the one specified in \fIgpgkey=..\fR in the \fI.conf\fR, or with \fI\-\-fingerprint\fR, in that order).
.PP
-For checking against the built-in public key/fingerprint, this requires
-importing the public key into the user’s local gpg keyring (that’s just the
-way that gpg works).
+For checking against the built-in public key/fingerprint, this requires importing the public key into the user’s local gpg keyring (that’s just the way that gpg works).
.PP
When a template is downloaded, its signature is checked in the same way.
.PP
-Although the signatures are optional, if you don’t have them then
-virt-builder users will have to use \fI\-\-no\-check\-signature\fR on the command
-line. This prevents an attacker from replacing the signed index file with
-an unsigned index file and having virt-builder silently work without
-checking the signature. In any case it is highly recommended that you
-always create signed index and templates.
+Although the signatures are optional, if you don’t have them then virt-builder users will have to use \fI\-\-no\-check\-signature\fR on the command line. This prevents an attacker from replacing the signed index file with an unsigned index file and having virt-builder silently work without checking the signature. In any case it is highly recommended that you always create signed index and templates.
.SS "アーキテクチャー"
.IX Subsection "アーキテクチャー"
-Virt-builder can build a guest for any architecture no matter what the host
-architecture is. For example an x86\-64 guest on an \s-1ARM\s0 host.
+Virt-builder can build a guest for any architecture no matter what the host architecture is. For example an x86\-64 guest on an \s-1ARM\s0 host.
.PP
-However certain options may not work, specifically options that require
-running commands in the guest during the build process: \fI\-\-install\fR,
-\&\fI\-\-update\fR, \fI\-\-run\fR, \fI\-\-run\-command\fR. You may need to replace these with
-their firstboot-equivalents.
+However certain options may not work, specifically options that require running commands in the guest during the build process: \fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR, \fI\-\-run\-command\fR. You may need to replace these with their firstboot-equivalents.
.PP
-An x86\-64 host building 32 bit i686 guests should work without any special
-steps.
+An x86\-64 host building 32 bit i686 guests should work without any special steps.
.SS "セキュリティ"
.IX Subsection "セキュリティ"
-Virt-builder does not need to run as root (in fact, should not be run as
-root), and doesn't use setuid, \f(CW\*(C`sudo\*(C'\fR or any similar mechanism.
+Virt-builder does not need to run as root (in fact, should not be run as root), and doesn't use setuid, \f(CW\*(C`sudo\*(C'\fR or any similar mechanism.
.PP
-\&\fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR and \fI\-\-run\-command\fR are implemented
-using an appliance (a small virtual machine) so these commands do not run on
-the host. If you are using the libguestfs libvirt backend and have SELinux
-enabled then the virtual machine is additionally encapsulated in an SELinux
-container (sVirt).
+\&\fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR and \fI\-\-run\-command\fR are implemented using an appliance (a small virtual machine) so these commands do not run on the host. If you are using the libguestfs libvirt backend and have SELinux enabled then the virtual machine is additionally encapsulated in an SELinux container (sVirt).
.PP
-However these options will have access to the host’s network and since the
-template may contain untrusted code, the code might try to access host
-network resources which it should not. You can use \fI\-\-no\-network\fR to
-prevent this.
+However these options will have access to the host’s network and since the template may contain untrusted code, the code might try to access host network resources which it should not. You can use \fI\-\-no\-network\fR to prevent this.
.PP
-Firstboot commands run in the context of the guest when it is booted, and so
-the security of your hypervisor / cloud should be considered.
+Firstboot commands run in the context of the guest when it is booted, and so the security of your hypervisor / cloud should be considered.
.PP
-Virt-builder injects a random seed into every guest which it builds. This
-helps to ensure that \s-1TCP\s0 sequence numbers, UUIDs, ssh host keys etc are
-truly random when the guest boots.
+Virt-builder injects a random seed into every guest which it builds. This helps to ensure that \s-1TCP\s0 sequence numbers, UUIDs, ssh host keys etc are truly random when the guest boots.
.PP
You should check digital signatures and not ignore any signing errors.
.SS "\s-1CLONES\s0"
.IX Subsection "CLONES"
-If you wish to create many new guests of the same type, it is tempting to
-run virt-builder once and then copy the output file. You should \fBnot\fR do
-this. You should run virt-builder once for each new guest you need.
+If you wish to create many new guests of the same type, it is tempting to run virt-builder once and then copy the output file. You should \fBnot\fR do this. You should run virt-builder once for each new guest you need.
.PP
-The reason is that each clone needs to have (at least) a separate random
-seed, and possibly other unique features (such as filesystem UUIDs) in
-future versions of virt-builder.
+The reason is that each clone needs to have (at least) a separate random seed, and possibly other unique features (such as filesystem UUIDs) in future versions of virt-builder.
.PP
-Another thing you should \fInot\fR do is to boot the guest, then clone the
-booted disk image. The reason is that some guests create unique machine
-IDs, \s-1SSH\s0 host keys and so on at first boot, and you would not want clones to
-have duplicate identities.
+Another thing you should \fInot\fR do is to boot the guest, then clone the booted disk image. The reason is that some guests create unique machine IDs, \s-1SSH\s0 host keys and so on at first boot, and you would not want clones to have duplicate identities.
.PP
See also: \fBvirt\-sysprep\fR\|(1).
.SS "\s-1PERFORMANCE\s0"
.IX Subsection "PERFORMANCE"
-The most important aspect of getting good performance is caching. Templates
-gets downloaded into the cache the first time they are used, or if you use
-the \fI\-\-cache\-all\-templates\fR option. See \*(L"\s-1CACHING\*(R"\s0 above for further
-information.
-.PP
-Packages required for the \fI\-\-install\fR and \fI\-\-update\fR options are
-downloaded using the host network connection. Setting the \f(CW\*(C`http_proxy\*(C'\fR,
-\&\f(CW\*(C`https_proxy\*(C'\fR and \f(CW\*(C`ftp_proxy\*(C'\fR environment variables to point to a local
-web cache may ensure they only need to be downloaded once. You can also try
-using a local package repository, although this can be complex to set up and
-varies according to which Linux distro you are trying to install.
+The most important aspect of getting good performance is caching. Templates gets downloaded into the cache the first time they are used, or if you use the \fI\-\-cache\-all\-templates\fR option. See \*(L"\s-1CACHING\*(R"\s0 above for further information.
+.PP
+Packages required for the \fI\-\-install\fR and \fI\-\-update\fR options are downloaded using the host network connection. Setting the \f(CW\*(C`http_proxy\*(C'\fR, \f(CW\*(C`https_proxy\*(C'\fR and \f(CW\*(C`ftp_proxy\*(C'\fR environment variables to point to a local web cache may ensure they only need to be downloaded once. You can also try using a local package repository, although this can be complex to set up and varies according to which Linux distro you are trying to install.
.PP
\fIUsing \fI\-\-no\-sync\fI\fR
.IX Subsection "Using --no-sync"
.PP
-Use \fI\-\-no\-sync\fR. However read the caveats in the \*(L"\s-1OPTIONS\*(R"\s0 section
-above, since this can cause disk corruption if not used correctly.
+Use \fI\-\-no\-sync\fR. However read the caveats in the \*(L"\s-1OPTIONS\*(R"\s0 section above, since this can cause disk corruption if not used correctly.
.PP
\fISkipping virt-resize\fR
.IX Subsection "Skipping virt-resize"
.PP
-Virt-builder can skip the virt-resize step under certain conditions. This
-makes virt-builder much faster. The conditions are:
+Virt-builder can skip the virt-resize step under certain conditions. This makes virt-builder much faster. The conditions are:
.IP "\(bu" 4
the output must be a regular file (not a block device), \fBand\fR
.IP "\(bu" 4
\fIpxzcat\fR
.IX Subsection "pxzcat"
.PP
-Virt-builder uses an internal implementation of pxzcat (parallel xzcat) if
-liblzma was found at build time. If liblzma was not found at build time,
-regular \f(CW\*(C`xzcat\*(C'\fR is used which is single-threaded.
-.PP
-\fIUser-Mode Linux\fR
-.IX Subsection "User-Mode Linux"
-.PP
-You can use virt-builder with the User-Mode Linux (\s-1UML\s0) backend. This may
-be faster when running virt-builder inside a virtual machine (eg. in the
-cloud).
-.PP
-To enable the \s-1UML\s0 backend, read the instructions in \*(L"USER-MODE
-\&\s-1LINUX BACKEND\*(R"\s0 in \fBguestfs\fR\|(3).
-.PP
-Currently you have to use the \fI\-\-no\-network\fR option. This should be fixed
-in a future version.
-.PP
-The qcow2 output format is not supported by \s-1UML.\s0 You can only create
-raw-format guests.
+Virt-builder uses an internal implementation of pxzcat (parallel xzcat) if liblzma was found at build time. If liblzma was not found at build time, regular \f(CW\*(C`xzcat\*(C'\fR is used which is single-threaded.
.SS "SELinux"
.IX Subsection "SELinux"
-Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux)
-require that each file has a correct SELinux label.
+Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux) require that each file has a correct SELinux label.
.PP
-Virt-builder does not know how to give new files a label, so there are two
-possible strategies it can use to ensure correct labelling:
+Virt-builder does not know how to give new files a label, so there are two possible strategies it can use to ensure correct labelling:
.IP "Using \fI\-\-selinux\-relabel\fR" 4
.IX Item "Using --selinux-relabel"
-This runs \fBsetfiles\fR\|(8) just before finalizing the guest, which sets
-SELinux labels correctly in the disk image.
+This runs \fBsetfiles\fR\|(8) just before finalizing the guest, which sets SELinux labels correctly in the disk image.
.Sp
This is the recommended method.
.IP "\fI\-\-touch\fR \fI/.autorelabel\fR" 4
.IX Item "--touch /.autorelabel"
-Guest templates may already contain a file called \fI/.autorelabel\fR or you
-may touch it.
+Guest templates may already contain a file called \fI/.autorelabel\fR or you may touch it.
.Sp
-For guests that use SELinux, this causes \fBrestorecon\fR\|(8) to run at first
-boot. Guests will reboot themselves once the first time you use them, which
-is normal and harmless.
+For guests that use SELinux, this causes \fBrestorecon\fR\|(8) to run at first boot. Guests will reboot themselves once the first time you use them, which is normal and harmless.
.PP
-Please note that if your guest uses SELinux, and you are doing operations on
-it which might create new files or change existing ones, you are recommended
-to use \fI\-\-selinux\-relabel\fR. This will help in making sure that files have
-the right SELinux labels.
+Please note that if your guest uses SELinux, and you are doing operations on it which might create new files or change existing ones, you are recommended to use \fI\-\-selinux\-relabel\fR. This will help in making sure that files have the right SELinux labels.
.SH "マシン可読な出力"
.IX Header "マシン可読な出力"
-The \fI\-\-machine\-readable\fR option can be used to make the output more machine
-friendly, which is useful when calling virt-builder from other programs,
-GUIs etc.
+The \fI\-\-machine\-readable\fR option can be used to make the output more machine friendly, which is useful when calling virt-builder from other programs, GUIs etc.
.PP
-Use the option on its own to query the capabilities of the virt-builder
-binary. Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-builder binary. Typical output looks like this:
.PP
.Vb 7
\& $ virt\-builder \-\-machine\-readable
\& pxzcat
.Ve
.PP
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
.PP
-It is possible to specify a format string for controlling the output; see
-\&\*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
+It is possible to specify a format string for controlling the output; see \*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "環境変数"
.IX Header "環境変数"
-For other environment variables which affect all libguestfs programs, see
-\&\*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+For other environment variables which affect all libguestfs programs, see \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.ie n .IP """http_proxy""" 4
.el .IP "\f(CWhttp_proxy\fR" 4
.IX Item "http_proxy"
.el .IP "\f(CWno_proxy\fR" 4
.IX Item "no_proxy"
.PD
-Set the proxy for downloads. These environment variables (and more) are
-actually interpreted by \fBcurl\fR\|(1), not virt-builder.
+Set the proxy for downloads. These environment variables (and more) are actually interpreted by \fBcurl\fR\|(1), not virt-builder.
.ie n .IP """HOME""" 4
.el .IP "\f(CWHOME\fR" 4
.IX Item "HOME"
-Used to determine the location of the template cache, and the location of
-the user' sources. See \*(L"\s-1CACHING\*(R"\s0 and \*(L"\s-1SOURCES OF TEMPLATES\*(R"\s0.
+Used to determine the location of the template cache, and the location of the user' sources. See \*(L"\s-1CACHING\*(R"\s0 and \*(L"\s-1SOURCES OF TEMPLATES\*(R"\s0.
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
.Sp
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like \fI/usr/share/virt\-tools\fR).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like \fI/usr/share/virt\-tools\fR).
.Sp
This directory may contain the following files:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in
-Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or
-\&\fI\-\-firstboot\-command\fR options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.Sp
See also: \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a
-\&\*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use
-the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
+This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.RE
.RS 4
.RE
.ie n .IP """XDG_CONFIG_HOME""" 4
.el .IP "\f(CWXDG_CONFIG_HOME\fR" 4
.IX Item "XDG_CONFIG_HOME"
-Used to determine the location of the user' sources. See \*(L"\s-1SOURCES OF
-TEMPLATES\*(R"\s0.
+Used to determine the location of the user' sources. See \*(L"\s-1SOURCES OF TEMPLATES\*(R"\s0.
.ie n .IP """VIRT_BUILDER_DIRS""" 4
.el .IP "\f(CWVIRT_BUILDER_DIRS\fR" 4
.IX Item "VIRT_BUILDER_DIRS"
-Used to determine the location of the system sources. See \*(L"\s-1SOURCES OF
-TEMPLATES\*(R"\s0.
+Used to determine the location of the system sources. See \*(L"\s-1SOURCES OF TEMPLATES\*(R"\s0.
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1),
-\&\fBvirt\-builder\-repository\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-customize\fR\|(1),
-\&\fBvirt\-get\-kernel\fR\|(1), \fBvirt\-install\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBvirt\-resize\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBoz\-install\fR\|(1), \fBgpg\fR\|(1),
-\&\fBgpg2\fR\|(1), \fBcurl\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBgenisoimage\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-builder\-repository\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-customize\fR\|(1), \fBvirt\-get\-kernel\fR\|(1), \fBvirt\-install\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBoz\-install\fR\|(1), \fBgpg\fR\|(1), \fBgpg2\fR\|(1), \fBcurl\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBgenisoimage\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-builder is a tool for quickly building new virtual machines. You can
-build a variety of VMs for local or cloud use, usually within a few minutes
-or less. Virt-builder also has many ways to customize these VMs.
-Everything is run from the command line and nothing requires root
-privileges, so automation and scripting is simple.
+Virt-builder is a tool for quickly building new virtual machines. You can build a variety of VMs for local or cloud use, usually within a few minutes or less. Virt-builder also has many ways to customize these VMs. Everything is run from the command line and nothing requires root privileges, so automation and scripting is simple.
-Note that virt-builder does not install guests from scratch. It takes
-cleanly prepared, digitally signed OS templates and customizes them. This
-approach is used because it is much faster, but if you need to do fresh
-installs you may want to look at L<virt-install(1)> and L<oz-install(1)>.
+Note that virt-builder does not install guests from scratch. It takes cleanly prepared, digitally signed OS templates and customizes them. This approach is used because it is much faster, but if you need to do fresh installs you may want to look at L<virt-install(1)> and L<oz-install(1)>.
-The easiest way to get started is by looking at the examples in the next
-section.
+The easiest way to get started is by looking at the examples in the next section.
=head1 例
virt-builder --list
-will list out the operating systems available to install. A selection of
-freely redistributable OSes is available as standard. You can add your own
-too (see below).
+will list out the operating systems available to install. A selection of freely redistributable OSes is available as standard. You can add your own too (see below).
-After choosing a guest from the list, you may want to see if there are any
-installation notes:
+After choosing a guest from the list, you may want to see if there are any installation notes:
virt-builder --notes fedora-27
virt-builder fedora-27
-will build a Fedora 25 image for the same architecture as virt-builder (so
-running it from an i686 installation will try to build an i686 image, if
-available). This will have all default configuration (minimal size, no user
-accounts, random root password, only the bare minimum installed software,
-etc.).
+will build a Fedora 25 image for the same architecture as virt-builder (so running it from an i686 installation will try to build an i686 image, if available). This will have all default configuration (minimal size, no user accounts, random root password, only the bare minimum installed software, etc.).
You I<do not> need to run this command as root.
-The first time this runs it has to download the template over the network,
-but this gets cached (see L</CACHING>).
+The first time this runs it has to download the template over the network, but this gets cached (see L</CACHING>).
-The name of the output file is derived from the template name, so above it
-will be F<fedora-27.img>. You can change the output filename using the
-I<-o> option:
+The name of the output file is derived from the template name, so above it will be F<fedora-27.img>. You can change the output filename using the I<-o> option:
virt-builder fedora-27 -o mydisk.img
-You can also use the I<-o> option to write to existing devices or logical
-volumes.
+You can also use the I<-o> option to write to existing devices or logical volumes.
virt-builder fedora-27 --format qcow2
virt-builder fedora-27 --size 20G
-As above, but the output size will be 20 GB. The guest OS is resized as it
-is copied to the output (automatically, using L<virt-resize(1)>).
+As above, but the output size will be 20 GB. The guest OS is resized as it is copied to the output (automatically, using L<virt-resize(1)>).
virt-builder fedora-27 --arch i686
virt-builder fedora-27 --root-password file:/tmp/rootpw
-Create a Fedora 25 image. The root password is taken from the file
-F</tmp/rootpw>.
+Create a Fedora 25 image. The root password is taken from the file F</tmp/rootpw>.
-Note if you I<don’t> set I<--root-password> then the guest is given a
-I<random> root password which is printed on stdout.
+Note if you I<don’t> set I<--root-password> then the guest is given a I<random> root password which is printed on stdout.
You can also create user accounts. See L</USERS AND PASSWORDS> below.
=head2 Installing software
-To install packages from the ordinary (guest) software repository (eg. dnf
-or apt):
+To install packages from the ordinary (guest) software repository (eg. dnf or apt):
virt-builder fedora-27 --install "inkscape,@Xfce Desktop"
-(In Fedora, C<@> is used to install groups of packages. On Debian you would
-install a meta-package instead.)
+(In Fedora, C<@> is used to install groups of packages. On Debian you would install a meta-package instead.)
To update the installed packages to the latest version:
virt-builder debian-7 --update
-For guests which use SELinux, like Fedora and Red Hat Enterprise Linux, you
-may need to do SELinux relabelling after installing or updating packages
-(see L</SELINUX> below):
+For guests which use SELinux, like Fedora and Red Hat Enterprise Linux, you may need to do SELinux relabelling after installing or updating packages (see L</SELINUX> below):
virt-builder fedora-27 --update --selinux-relabel
=head2 Customizing the installation
-There are many options that let you customize the installation. These
-include: I<--run>/I<--run-command>, which run a shell script or command
-while the disk image is being generated and lets you add or edit files that
-go into the disk image. I<--firstboot>/I<--firstboot-command>, which let
-you add scripts/commands that are run the first time the guest boots.
-I<--edit> to edit files. I<--upload> to upload files.
+There are many options that let you customize the installation. These include: I<--run>/I<--run-command>, which run a shell script or command while the disk image is being generated and lets you add or edit files that go into the disk image. I<--firstboot>/I<--firstboot-command>, which let you add scripts/commands that are run the first time the guest boots. I<--edit> to edit files. I<--upload> to upload files.
例:
virt-builder fedora-27 --firstboot-command 'dnf -y --best update'
-which makes the L<dnf(8)> C<update> command run once the first time the
-guest boots.
+which makes the L<dnf(8)> C<update> command run once the first time the guest boots.
Or:
--edit '/etc/dnf/dnf.conf:
s/gpgcheck=1/gpgcheck=0/'
-which edits F</etc/dnf/dnf.conf> inside the disk image (during disk image
-creation, long before boot).
+which edits F</etc/dnf/dnf.conf> inside the disk image (during disk image creation, long before boot).
You can combine these options, and have multiple options of all types.
=item B<--arch> ARCHITECTURE
-Use the specified architecture for the output image. This means there must
-be sources providing the requested template for the requested architecture.
+Use the specified architecture for the output image. This means there must be sources providing the requested template for the requested architecture.
See also L</ARCHITECTURE>.
=item B<--attach> ISOFILE
-During the customization phase, the given disk is attached to the libguestfs
-appliance. This is used to provide extra software repositories or other
-data for customization.
+During the customization phase, the given disk is attached to the libguestfs appliance. This is used to provide extra software repositories or other data for customization.
-You probably want to ensure the volume(s) or filesystems in the attached
-disks are labelled (or use an ISO volume name) so that you can mount them by
-label in your run-scripts:
+You probably want to ensure the volume(s) or filesystems in the attached disks are labelled (or use an ISO volume name) so that you can mount them by label in your run-scripts:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
-You can have multiple I<--attach> options, and the format can be any disk
-format (not just an ISO).
+You can have multiple I<--attach> options, and the format can be any disk format (not just an ISO).
-See also: I<--run>, L</Installing packages at build time from a side
-repository>, L<genisoimage(1)>, L<virt-make-fs(1)>.
+See also: I<--run>, L</Installing packages at build time from a side repository>, L<genisoimage(1)>, L<virt-make-fs(1)>.
=item B<--attach-format> FORMAT
-Specify the disk format for the next I<--attach> option. The C<FORMAT> is
-usually C<raw> or C<qcow2>. Use C<raw> for ISOs.
+Specify the disk format for the next I<--attach> option. The C<FORMAT> is usually C<raw> or C<qcow2>. Use C<raw> for ISOs.
=item B<--cache> DIR
=item B<--no-cache>
-I<--cache> DIR sets the directory to use/check for cached template files.
-If not set, defaults to either F<$XDG_CACHE_HOME/virt-builder/> or
-F<$HOME/.cache/virt-builder/>.
+I<--cache> DIR sets the directory to use/check for cached template files. If not set, defaults to either F<$XDG_CACHE_HOME/virt-builder/> or F<$HOME/.cache/virt-builder/>.
I<--no-cache> disables template caching.
Download all templates to the cache and then exit. See L</CACHING>.
-Note this doesn't cache everything. More templates might be uploaded. Also
-this doesn't cache packages (the I<--install>, I<--update> options).
+Note this doesn't cache everything. More templates might be uploaded. Also this doesn't cache packages (the I<--install>, I<--update> options).
=item B<--check-signature>
=item B<--no-check-signature>
-Check/don’t check the digital signature of the OS template. The default is
-to check the signature and exit if it is not correct. Using
-I<--no-check-signature> bypasses this check.
+Check/don’t check the digital signature of the OS template. The default is to check the signature and exit if it is not correct. Using I<--no-check-signature> bypasses this check.
See also I<--fingerprint>.
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<--curl> CURL
-Specify an alternate L<curl(1)> binary. You can also use this to add curl
-parameters, for example to disable https certificate checks:
+Specify an alternate L<curl(1)> binary. You can also use this to add curl parameters, for example to disable https certificate checks:
virt-builder --curl "curl --insecure" [...]
=item B<--no-delete-on-failure>
-Don’t delete the output file on failure to build. You can use this to debug
-failures to run scripts. See L</DEBUGGING BUILDS> for ways to debug images.
+Don’t delete the output file on failure to build. You can use this to debug failures to run scripts. See L</DEBUGGING BUILDS> for ways to debug images.
-The default is to delete the output file if virt-builder fails (or, for
-example, some script that it runs fails).
+The default is to delete the output file if virt-builder fails (or, for example, some script that it runs fails).
=item B<--fingerprint> 'AAAA BBBB ...'
-Check that the index and templates are signed by the key with the given
-fingerprint. (The fingerprint is a long string, usually written as 10
-groups of 4 hexadecimal digits).
+Check that the index and templates are signed by the key with the given fingerprint. (The fingerprint is a long string, usually written as 10 groups of 4 hexadecimal digits).
-You can give this option multiple times. If you have multiple source URLs,
-then you can have either no fingerprint, one fingerprint or multiple
-fingerprints. If you have multiple, then each must correspond 1-1 with a
-source URL.
+You can give this option multiple times. If you have multiple source URLs, then you can have either no fingerprint, one fingerprint or multiple fingerprints. If you have multiple, then each must correspond 1-1 with a source URL.
=item B<--format> qcow2
With I<--get-kernel> this specifies the input format.
-To create an old-style qcow2 file (for compatibility with RHEL 6 or very old
-qemu E<lt> 1.1), after running virt-builder, use this command:
+To create an old-style qcow2 file (for compatibility with RHEL 6 or very old qemu E<lt> 1.1), after running virt-builder, use this command:
qemu-img amend -f qcow2 -o compat=0.10 output.qcow2
=item B<--get-kernel> IMAGE
-This option extracts the kernel and initramfs from a previously built disk
-image called C<IMAGE> (in fact it works for any VM disk image, not just ones
-built using virt-builder).
+This option extracts the kernel and initramfs from a previously built disk image called C<IMAGE> (in fact it works for any VM disk image, not just ones built using virt-builder).
-Note this method is B<deprecated>: there is a separate tool for this,
-L<virt-get-kernel(1)>, which has more options for the file extraction.
+Note this method is B<deprecated>: there is a separate tool for this, L<virt-get-kernel(1)>, which has more options for the file extraction.
-The kernel and initramfs are written to the current directory, unless you
-also specify the I<--output> C<outputdir> B<directory> name.
+The kernel and initramfs are written to the current directory, unless you also specify the I<--output> C<outputdir> B<directory> name.
-The format of the disk image is automatically detected unless you specify it
-by using the I<--format> option.
+The format of the disk image is automatically detected unless you specify it by using the I<--format> option.
-In the case where the guest contains multiple kernels, the one with the
-highest version number is chosen. To extract arbitrary kernels from the
-disk image, see L<guestfish(1)>. To extract the entire F</boot> directory
-of a guest, see L<virt-copy-out(1)>.
+In the case where the guest contains multiple kernels, the one with the highest version number is chosen. To extract arbitrary kernels from the disk image, see L<guestfish(1)>. To extract the entire F</boot> directory of a guest, see L<virt-copy-out(1)>.
=item B<--gpg> GPG
-Specify an alternate L<gpg(1)> (GNU Privacy Guard) binary. By default
-virt-builder looks for either C<gpg2> or C<gpg> in the C<$PATH>.
+Specify an alternate L<gpg(1)> (GNU Privacy Guard) binary. By default virt-builder looks for either C<gpg2> or C<gpg> in the C<$PATH>.
-You can also use this to add gpg parameters, for example to specify an
-alternate home directory:
+You can also use this to add gpg parameters, for example to specify an alternate home directory:
virt-builder --gpg "gpg --homedir /tmp" [...]
=item B<--list> B<--long> [os-version]
-List all the available templates if no guest is specified, or only for the
-specified one.
+List all the available templates if no guest is specified, or only for the specified one.
-It is possible to choose with I<--list-format> the output format for the
-list templates:
+It is possible to choose with I<--list-format> the output format for the list templates:
=over 4
=item B<short>
-The default format, prints only the template identifier and, next to it, its
-short description.
+The default format, prints only the template identifier and, next to it, its short description.
=item B<long>
-Prints a textual list with the details of the available sources, followed by
-the details of the available templates.
+Prints a textual list with the details of the available sources, followed by the details of the available templates.
=item B<json>
-Prints a JSON object with the details of the available sources and the
-details of the available templates.
+Prints a JSON object with the details of the available sources and the details of the available templates.
-The C<version> key in the main object represents the "compatibility
-version", and it is bumped every time the resulting JSON output is
-incompatible with the previous versions (for example the structure has
-changed, or non-optional keys are no more present).
+The C<version> key in the main object represents the "compatibility version", and it is bumped every time the resulting JSON output is incompatible with the previous versions (for example the structure has changed, or non-optional keys are no more present).
=back
=item B<--memsize> MB
-Change the amount of memory allocated to I<--run> scripts. Increase this if
-you find that I<--run> scripts or the I<--install> option are running out of
-memory.
+Change the amount of memory allocated to I<--run> scripts. Increase this if you find that I<--run> scripts or the I<--install> option are running out of memory.
The default can be found with this command:
Enabled is the default. Use I<--no-network> to disable access.
-The network only allows outgoing connections and has other minor
-limitations. See L<virt-rescue(1)/NETWORK>.
+The network only allows outgoing connections and has other minor limitations. See L<virt-rescue(1)/NETWORK>.
-If you use I<--no-network> then certain other options such as I<--install>
-will not work.
+If you use I<--no-network> then certain other options such as I<--install> will not work.
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-builder.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-builder.
-Generally speaking you should I<not> use I<--no-network>. But here are some
-reasons why you might want to:
+Generally speaking you should I<not> use I<--no-network>. But here are some reasons why you might want to:
=over 4
=item 1.
-Because the libguestfs backend that you are using doesn't support the
-network. (See: L<guestfs(3)/BACKEND>).
+Because the libguestfs backend that you are using doesn't support the network. (See: L<guestfs(3)/BACKEND>).
=item 2.
-Any software you need to install comes from an attached ISO, so you don't
-need the network.
+Any software you need to install comes from an attached ISO, so you don't need the network.
=item 3.
-You don’t want untrusted guest code trying to access your host network when
-running virt-builder. This is particularly an issue when you don't trust
-the source of the operating system templates. (See L</SECURITY> below).
+You don’t want untrusted guest code trying to access your host network when running virt-builder. This is particularly an issue when you don't trust the source of the operating system templates. (See L</SECURITY> below).
=item 4.
Virt-builder C<fsync>s the output file or disk image when it exits.
-The reason is that qemu/KVM’s default caching mode is C<none> or
-C<directsync>, both of which bypass the host page cache. Therefore these
-would not work correctly if you immediately started the guest after running
-virt-builder - they would not see the complete output file. (Note that you
-should not use these caching modes - they are fundamentally broken for this
-and other reasons.)
+The reason is that qemu/KVM’s default caching mode is C<none> or C<directsync>, both of which bypass the host page cache. Therefore these would not work correctly if you immediately started the guest after running virt-builder - they would not see the complete output file. (Note that you should not use these caching modes - they are fundamentally broken for this and other reasons.)
-If you are not using these broken caching modes, you can use I<--no-sync> to
-avoid this unnecessary sync and gain considerable extra performance.
+If you are not using these broken caching modes, you can use I<--no-sync> to avoid this unnecessary sync and gain considerable extra performance.
=item B<--notes> os-version
-List any notes associated with this guest, then exit (this does not do the
-install).
+List any notes associated with this guest, then exit (this does not do the install).
=item B<-o> filename
=item B<--output> filename
-Write the output to F<filename>. If you don’t specify this option, then the
-output filename is generated by taking the C<os-version> string and adding
-C<.img> (for raw format) or C<.qcow2> (for qcow2 format).
+Write the output to F<filename>. If you don’t specify this option, then the output filename is generated by taking the C<os-version> string and adding C<.img> (for raw format) or C<.qcow2> (for qcow2 format).
-Note that the output filename could be a device, partition or logical
-volume.
+Note that the output filename could be a device, partition or logical volume.
When used with I<--get-kernel>, this option specifies the output directory.
=item B<--size> SIZE
-Select the size of the output disk, where the size can be specified using
-common names such as C<32G> (32 gigabytes) etc.
+Select the size of the output disk, where the size can be specified using common names such as C<32G> (32 gigabytes) etc.
Virt-builder will resize filesystems inside the disk image automatically.
-If the size is not specified, then one of two things happens. If the output
-is a file, then the size is the same as the template. If the output is a
-device, partition, etc then the size of that device is used.
+If the size is not specified, then one of two things happens. If the output is a file, then the size is the same as the template. If the output is a device, partition, etc then the size of that device is used.
-To specify size in bytes, the number must be followed by the lowercase
-letter I<b>, eg: S<C<--size 10737418240b>>.
+To specify size in bytes, the number must be followed by the lowercase letter I<b>, eg: S<C<--size 10737418240b>>.
=item B<--smp> N
See also L</SOURCES OF TEMPLATES> below.
-Note that you should not point I<--source> to sources that you don’t trust
-(unless the source is signed by someone you do trust). See also the
-I<--no-network> option.
+Note that you should not point I<--source> to sources that you don’t trust (unless the source is signed by someone you do trust). See also the I<--no-network> option.
=item B<--no-warn-if-partition>
-Do not emit a warning if the output device is a partition. This warning
-avoids a common user error when writing to a USB key or external drive, when
-you should normally write to the whole device (S<I<--output /dev/sdX>>), not
-to a partition on the device (S<I<--output /dev/sdX1>>). Use this option to
-I<suppress> this warning.
+Do not emit a warning if the output device is a partition. This warning avoids a common user error when writing to a USB key or external drive, when you should normally write to the whole device (S<I<--output /dev/sdX>>), not to a partition on the device (S<I<--output /dev/sdX1>>). Use this option to I<suppress> this warning.
=item B<-v>
Enable debug messages and/or produce verbose output.
-When reporting bugs, use this option and attach the complete output to your
-bug report.
+When reporting bugs, use this option and attach the complete output to your bug report.
=item B<-V>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head2 INSTALLING PACKAGES
-There are several approaches to installing packages or applications in the
-guest which have different trade-offs.
+There are several approaches to installing packages or applications in the guest which have different trade-offs.
=head3 Installing packages at build time
-If the guest OS you are installing is similar to the host OS (eg. both are
-Linux), and if libguestfs supports network connections, then you can use
-I<--install> to install packages like this:
+If the guest OS you are installing is similar to the host OS (eg. both are Linux), and if libguestfs supports network connections, then you can use I<--install> to install packages like this:
virt-builder fedora-27 --install inkscape
virt-builder fedora-27 --update
-Most of the templates that ship with virt-builder come with a very minimal
-selection of packages (known as a "JEOS" or "Just Enough Operating System"),
-which are up to date at the time the template is created, but could be out
-of date by the time you come to install an OS from the template. This
-option updates those template packages.
+Most of the templates that ship with virt-builder come with a very minimal selection of packages (known as a "JEOS" or "Just Enough Operating System"), which are up to date at the time the template is created, but could be out of date by the time you come to install an OS from the template. This option updates those template packages.
=head3 Installing packages at first boot
This uses the guest’s package manager and the guest’s network connection.
-The downsides are that it will take the guest a lot longer to boot first
-time, and there’s nothing much you can do if package installation fails
-(eg. if a network problem means the guest can't reach the package
-repositories).
+The downsides are that it will take the guest a lot longer to boot first time, and there’s nothing much you can do if package installation fails (eg. if a network problem means the guest can't reach the package repositories).
=head3 Installing packages at build time from a side repository
-If the software you want to install is not available in the main package
-repository of the guest, then you can add a side repository. Usually this
-is presented as an ISO (CD disk image) file containing extra packages.
+If the software you want to install is not available in the main package repository of the guest, then you can add a side repository. Usually this is presented as an ISO (CD disk image) file containing extra packages.
-You can create the disk image using either L<genisoimage(1)> or
-L<virt-make-fs(1)>. For genisoimage, use a command like this:
+You can create the disk image using either L<genisoimage(1)> or L<virt-make-fs(1)>. For genisoimage, use a command like this:
genisoimage -o extra-packages.iso -R -J -V EXTRA cdcontents/
-Create a script that mounts the ISO and sets up the repository. For dnf,
-create /tmp/install.sh containing:
+Create a script that mounts the ISO and sets up the repository. For dnf, create /tmp/install.sh containing:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
apt-cdrom -d=/tmp/mount add
apt-get -y install famousdatabase
-Use the I<--attach> option to attach the CD / disk image and the I<--run>
-option to run the script:
+Use the I<--attach> option to attach the CD / disk image and the I<--run> option to run the script:
virt-builder fedora-27 \
--attach extra-packages.iso \
=head2 USERS AND PASSWORDS
-The I<--root-password> option is used to change the root password (otherwise
-a random password is used). This option takes a password C<SELECTOR> in one
-of the following formats:
+The I<--root-password> option is used to change the root password (otherwise a random password is used). This option takes a password C<SELECTOR> in one of the following formats:
=over 4
=item B<--root-password> file:FILENAME
-Read the root password from C<FILENAME>. The whole first line of this file
-is the replacement password. Any other lines are ignored. You should
-create the file with mode 0600 to ensure no one else can read it.
+Read the root password from C<FILENAME>. The whole first line of this file is the replacement password. Any other lines are ignored. You should create the file with mode 0600 to ensure no one else can read it.
=item B<--root-password> password:PASSWORD
Set the root password to the literal string C<PASSWORD>.
-B<Note: this is not secure> since any user on the same machine can see the
-cleartext password using L<ps(1)>.
+B<Note: this is not secure> since any user on the same machine can see the cleartext password using L<ps(1)>.
=item B<--root-password> random
-Choose a random password, which is printed on stdout. The password has
-approximately 120 bits of randomness.
+Choose a random password, which is printed on stdout. The password has approximately 120 bits of randomness.
これがデフォルトです。
=item B<--root-password> disabled
-The root account password is disabled. This is like putting C<*> in the
-password field.
+The root account password is disabled. This is like putting C<*> in the password field.
=item B<--root-password> locked:file:FILENAME
=item B<--root-password> locked:random
-The root account is locked, but a password is placed on the account. If
-first unlocked (using C<passwd -u>) then logins will use the given password.
+The root account is locked, but a password is placed on the account. If first unlocked (using C<passwd -u>) then logins will use the given password.
=item B<--root-password> locked
=head3 Creating user accounts
-To create user accounts, use the L<useradd(8)> command with
-L<--firstboot-command> like this:
+To create user accounts, use the L<useradd(8)> command with L<--firstboot-command> like this:
virt-builder --firstboot-command \
'useradd -m -p "" rjones ; chage -d 0 rjones'
-The above command will create an C<rjones> account with no password, and
-force the user to set a password when they first log in. There are other
-ways to manage passwords, see L<useradd(8)> for details.
+The above command will create an C<rjones> account with no password, and force the user to set a password when they first log in. There are other ways to manage passwords, see L<useradd(8)> for details.
=head2 KEYBOARD LAYOUT
-Because there are so many different ways to set the keyboard layout in Linux
-distributions, virt-builder does not yet attempt to have a simple command
-line option. This section describes how to set the keyboard for some common
-Linux distributions.
+Because there are so many different ways to set the keyboard layout in Linux distributions, virt-builder does not yet attempt to have a simple command line option. This section describes how to set the keyboard for some common Linux distributions.
=head3 Keyboard layout with systemd
virt-builder fedora-27 \
--firstboot-command 'localectl set-keymap uk'
-See L<localectl(1)> and
-L<https://www.happyassassin.net/2013/11/23/keyboard-layouts-in-fedora-20-and-previously/>
-for more details.
+See L<localectl(1)> and L<https://www.happyassassin.net/2013/11/23/keyboard-layouts-in-fedora-20-and-previously/> for more details.
=head3 Keyboard layout using F</etc/sysconfig/keyboard>
-For RHEL E<le> 6, Fedora E<le> 18 and similar, upload or modify the keyboard
-configuration file using the I<--upload>, I<--write> or I<--edit> options.
-For example:
+For RHEL E<le> 6, Fedora E<le> 18 and similar, upload or modify the keyboard configuration file using the I<--upload>, I<--write> or I<--edit> options. For example:
virt-builder centos-6 \
--edit '/etc/sysconfig/keyboard: s/^KEYTABLE=.*/KEYTABLE="uk"/'
=head3 Keyboard layout with Debian-derived distros
-For Debian-derived distros using F</etc/default/keyboard>, upload or modify
-the keyboard file using the I<--upload>, I<--write> or I<--edit> options.
-For example:
+For Debian-derived distros using F</etc/default/keyboard>, upload or modify the keyboard file using the I<--upload>, I<--write> or I<--edit> options. For example:
virt-builder debian-8 \
--edit '/etc/default/keyboard: s/^XKBLAYOUT=.*/XKBLAYOUT="gb"/'
=head2 LANGUAGE
-Most Linux distributions support multiple locale settings so that you can
-have guest messages printed in another language such as Russian.
+Most Linux distributions support multiple locale settings so that you can have guest messages printed in another language such as Russian.
-However there is no single setting which controls this, since extra packages
-may need to be installed to support console and X fonts, and keyboard input
-methods. The packages required, and their configuration is highly
-distro-specific, and it is outside the scope of virt-builder to do this.
+However there is no single setting which controls this, since extra packages may need to be installed to support console and X fonts, and keyboard input methods. The packages required, and their configuration is highly distro-specific, and it is outside the scope of virt-builder to do this.
This section contains examples for some common Linux distributions.
=head3 Setting Japanese in Debian 8 (Jessie)
-Note that although this enables Japanese in the text console too, it is
-unlikely that you will see properly rendered Japanese there. However
-Japanese is properly rendered in X applications and terminals.
+Note that although this enables Japanese in the text console too, it is unlikely that you will see properly rendered Japanese there. However Japanese is properly rendered in X applications and terminals.
pkgs=locales,xfce4,\
ibus,ibus-anthy,\
=head2 LOG FILE
-Scripts and package installation that runs at build time (I<--run>,
-I<--run-command>, I<--install>, I<--update>, but I<not> firstboot) is logged
-in one of the following locations:
+Scripts and package installation that runs at build time (I<--run>, I<--run-command>, I<--install>, I<--update>, but I<not> firstboot) is logged in one of the following locations:
=over 4
=back
-If you don’t want the log file to appear in the final image, then use the
-I<--no-logfile> command line option.
+If you don’t want the log file to appear in the final image, then use the I<--no-logfile> command line option.
=head2 SSH KEYS
-The I<--ssh-inject> option is used to inject ssh keys for users in the
-guest, so they can login without supplying a password.
+The I<--ssh-inject> option is used to inject ssh keys for users in the guest, so they can login without supplying a password.
-The C<SELECTOR> part of the option value is optional; in this case,
-I<--ssh-inject> C<USER> means that we look in the I<current> user’s
-F<~/.ssh> directory to find the default public ID file. That key is
-uploaded. "default public ID" is the I<default_ID_file> file described in
-L<ssh-copy-id(1)>.
+The C<SELECTOR> part of the option value is optional; in this case, I<--ssh-inject> C<USER> means that we look in the I<current> user’s F<~/.ssh> directory to find the default public ID file. That key is uploaded. "default public ID" is the I<default_ID_file> file described in L<ssh-copy-id(1)>.
If specified, the C<SELECTOR> can be in one of the following formats:
=item B<--ssh-inject> USER:string:KEY_STRING
-Use the specified C<KEY_STRING>. C<KEY_STRING> is usually a public string
-like I<ssh-rsa AAAA.... user@localhost>.
+Use the specified C<KEY_STRING>. C<KEY_STRING> is usually a public string like I<ssh-rsa AAAA.... user@localhost>.
=back
-In any case, the F<~USER/.ssh> directory and the
-F<~USER/.ssh/authorized_keys> file will be created if not existing already.
+In any case, the F<~USER/.ssh> directory and the F<~USER/.ssh/authorized_keys> file will be created if not existing already.
=head2 FIRST BOOT SCRIPTS
-The I<--firstboot> and I<--firstboot-command> options allow you to execute
-commands at the first boot of the guest. To do so, an init script for the
-guest init system is installed, which takes care of running all the added
-scripts and commands.
+The I<--firstboot> and I<--firstboot-command> options allow you to execute commands at the first boot of the guest. To do so, an init script for the guest init system is installed, which takes care of running all the added scripts and commands.
Supported operating systems are:
=item Linux
-Init systems supported are: systemd, System-V init (known also as sysvinit),
-and Upstart (using the System-V scripts).
+Init systems supported are: systemd, System-V init (known also as sysvinit), and Upstart (using the System-V scripts).
-Note that usually init scripts run as root, but with a more limited
-environment than what could be available from a normal shell: for example,
-C<$HOME> may be unset or empty.
+Note that usually init scripts run as root, but with a more limited environment than what could be available from a normal shell: for example, C<$HOME> may be unset or empty.
-The output of the first boot scripts is available in the guest as
-F<~root/virt-sysprep-firstboot.log>.
+The output of the first boot scripts is available in the guest as F<~root/virt-sysprep-firstboot.log>.
=item Windows
-F<rhsrvany.exe>, available from sources at
-L<https://github.com/rwmjones/rhsrvany>, or F<pvvxsvc.exe>, available with
-SUSE VMDP is installed to run the first boot scripts. It is required, and
-the setup of first boot scripts will fail if it is not present.
+F<rhsrvany.exe>, available from sources at L<https://github.com/rwmjones/rhsrvany>, or F<pvvxsvc.exe>, available with SUSE VMDP is installed to run the first boot scripts. It is required, and the setup of first boot scripts will fail if it is not present.
-F<rhsrvany.exe> or F<pvvxsvc.exe> is copied from the location pointed to by
-the C<VIRT_TOOLS_DATA_DIR> environment variable; if not set, a compiled-in
-default will be used (something like F</usr/share/virt-tools>).
+F<rhsrvany.exe> or F<pvvxsvc.exe> is copied from the location pointed to by the C<VIRT_TOOLS_DATA_DIR> environment variable; if not set, a compiled-in default will be used (something like F</usr/share/virt-tools>).
-The output of the first boot scripts is available in the guest as
-F<C:\Program Files\Guestfs\Firstboot\log.txt>.
+The output of the first boot scripts is available in the guest as F<C:\Program Files\Guestfs\Firstboot\log.txt>.
=back
=head2 SUBSCRIPTION-MANAGER
-It is possible to automate the registration and attaching of the system
-using C<subscription-manager>. This is typical on Red Hat Enterprise Linux
-guests. There are few options which ease this process, avoid executing
-commands manually and exposing passwords on command line.
+It is possible to automate the registration and attaching of the system using C<subscription-manager>. This is typical on Red Hat Enterprise Linux guests. There are few options which ease this process, avoid executing commands manually and exposing passwords on command line.
-I<--sm-register> starts the registration process, and requires
-I<--sm-credentials> to be specified; the format of the C<SELECTOR> of
-I<--sm-credentials> is one of the following formats:
+I<--sm-register> starts the registration process, and requires I<--sm-credentials> to be specified; the format of the C<SELECTOR> of I<--sm-credentials> is one of the following formats:
=over 4
=back
-I<--sm-attach> attaches the system to subscriptions; the format of its
-C<SELECTOR> is one of the following:
+I<--sm-attach> attaches the system to subscriptions; the format of its C<SELECTOR> is one of the following:
=over 4
=item B<--sm-attach> auto
-C<subscription-manager> attaches to the best-fitting subscriptions for the
-system.
+C<subscription-manager> attaches to the best-fitting subscriptions for the system.
=item B<--sm-attach> file:FILENAME
=back
-I<--sm-remove> removes all the subscriptions from the guest, while
-I<--sm-unregister> completely unregister the system.
+I<--sm-remove> removes all the subscriptions from the guest, while I<--sm-unregister> completely unregister the system.
=head2 INSTALLATION PROCESS
The template image is downloaded.
-If the template image is present in the cache, the cached version is used
-instead. (See L</CACHING>).
+If the template image is present in the cache, the cached version is used instead. (See L</CACHING>).
=item *
=item *
-Guest customization is performed, in the order specified on the command
-line.
+Guest customization is performed, in the order specified on the command line.
=item *
=head3 Importing into libvirt
-Import the disk image into libvirt using L<virt-install(1)> I<--import>
-option.
+Import the disk image into libvirt using L<virt-install(1)> I<--import> option.
virt-install --import \
--name guest --ram 2048 \
=item 1.
-You I<must> specify the correct format. The format is C<raw> unless you
-used virt-builder’s I<--format> option.
+You I<must> specify the correct format. The format is C<raw> unless you used virt-builder’s I<--format> option.
=item 2.
-I<--os-variant> is highly recommended, because it will present optimum
-devices to enable the guest to run most efficiently. To get a list of all
-variants, do:
+I<--os-variant> is highly recommended, because it will present optimum devices to enable the guest to run most efficiently. To get a list of all variants, do:
osinfo-query os
=item 3.
-You can run virt-install as root or non-root. Each works slightly
-differently because libvirt manages a different set of virtual machines for
-each user. In particular virt-manager normally shows the root-owned VMs,
-whereas Boxes shows the user-owned VMs, and other tools probably work
-differently as well.
+You can run virt-install as root or non-root. Each works slightly differently because libvirt manages a different set of virtual machines for each user. In particular virt-manager normally shows the root-owned VMs, whereas Boxes shows the user-owned VMs, and other tools probably work differently as well.
=back
--disk-format raw --container-format bare \
--is-public True
-The I<--file> parameter is the virt-builder-generated disk image. It should
-match virt-builder’s I<--output> option. The I<--disk-format> parameter
-should match virt-builder’s I<--format> option (or C<raw> if you didn't use
-that option). The I<--container-format> should always be C<bare> since
-virt-builder doesn't put images into containers.
+The I<--file> parameter is the virt-builder-generated disk image. It should match virt-builder’s I<--output> option. The I<--disk-format> parameter should match virt-builder’s I<--format> option (or C<raw> if you didn't use that option). The I<--container-format> should always be C<bare> since virt-builder doesn't put images into containers.
-You can use the S<C<glance image-show I<fedora-27-image>>> command to
-display the properties of the image.
+You can use the S<C<glance image-show I<fedora-27-image>>> command to display the properties of the image.
To boot up an instance of your image on a Nova compute node, do:
nova boot fedora-27-server --image fedora-27-image \
--flavor m1.medium
-Use S<C<nova flavor-list>> to list possible machine flavors. Use S<C<nova
-list>> to list running instances.
+Use S<C<nova flavor-list>> to list possible machine flavors. Use S<C<nova list>> to list running instances.
=head3 Booting directly using qemu or KVM
-The qemu command line is not very stable or easy to use, hence libvirt
-should be used if possible. However a command line similar to the following
-could be used to boot the virtual machine:
+The qemu command line is not very stable or easy to use, hence libvirt should be used if possible. However a command line similar to the following could be used to boot the virtual machine:
qemu-system-x86_64 \
-machine accel=kvm:tcg \
-m 2048 \
-drive file=disk.img,format=raw,if=virtio
-As with libvirt, it is very important that the correct format is chosen. It
-will be C<raw> unless the I<--format> option was used.
+As with libvirt, it is very important that the correct format is chosen. It will be C<raw> unless the I<--format> option was used.
=head2 CONFIGURATION MANAGEMENT
=head3 Puppet
-To enable the Puppet agent in a guest, install the package, point the
-configuration at your Puppetmaster, and ensure the agent runs at boot.
+To enable the Puppet agent in a guest, install the package, point the configuration at your Puppetmaster, and ensure the agent runs at boot.
A typical virt-builder command would be:
--run-command 'systemctl enable puppet' \
--selinux-relabel
-The precise instructions vary according to the Linux distro. For further
-information see: L<https://docs.puppet.com/puppet/latest/install_pre.html>
+The precise instructions vary according to the Linux distro. For further information see: L<https://docs.puppet.com/puppet/latest/install_pre.html>
=head2 DEBUGGING BUILDS
-If virt-builder itself fails, then enable debugging (I<-v>) and report a bug
-(see L</BUGS> below).
+If virt-builder itself fails, then enable debugging (I<-v>) and report a bug (see L</BUGS> below).
-If virt-builder fails because some script or package it is installing fails,
-try using I<--no-delete-on-failure> to preserve the output file, and
-continue reading this section.
+If virt-builder fails because some script or package it is installing fails, try using I<--no-delete-on-failure> to preserve the output file, and continue reading this section.
-If virt-builder is successful but the image doesn't work, here are some
-things to try:
+If virt-builder is successful but the image doesn't work, here are some things to try:
=over 4
virt-rescue -a disk.img
-This gives you a rescue shell. You can mount the filesystems from the disk
-image on F</sysroot> and examine them using ordinary Linux commands. You
-can also chroot into the guest to reinstall the bootloader. The virt-rescue
-man page has a lot more information and examples.
+This gives you a rescue shell. You can mount the filesystems from the disk image on F</sysroot> and examine them using ordinary Linux commands. You can also chroot into the guest to reinstall the bootloader. The virt-rescue man page has a lot more information and examples.
=item Use guestfish
guestfish -a disk.img -i
-Use guestfish commands like C<ll /directory> and C<cat /file> to examine
-directories and files.
+Use guestfish commands like C<ll /directory> and C<cat /file> to examine directories and files.
=item Use guestmount
=item Add a serial console
-If the guest hangs during boot, it can be helpful to add a serial console to
-the guest, and direct kernel messages to the serial console. Adding the
-serial console will involve looking at the documentation for your
-hypervisor. To direct kernel messages to the serial console, add the
-following on the kernel command line:
+If the guest hangs during boot, it can be helpful to add a serial console to the guest, and direct kernel messages to the serial console. Adding the serial console will involve looking at the documentation for your hypervisor. To direct kernel messages to the serial console, add the following on the kernel command line:
console=tty0 console=ttyS0,115200
=head2 SOURCES OF TEMPLATES
-virt-builder reads the available sources from configuration files, with the
-I<.conf> extension and located in the following paths:
+virt-builder reads the available sources from configuration files, with the I<.conf> extension and located in the following paths:
=over 4
=item *
-$XDG_CONFIG_HOME/virt-builder/repos.d/ (C<$XDG_CONFIG_HOME> is
-F<$HOME/.config> if not set).
+$XDG_CONFIG_HOME/virt-builder/repos.d/ (C<$XDG_CONFIG_HOME> is F<$HOME/.config> if not set).
=item *
-$VIRT_BUILDER_DIRS/virt-builder/repos.d/ (where C<$VIRT_BUILDER_DIRS> means
-any of the directories in that environment variable, or just F</etc> if not
-set).
+$VIRT_BUILDER_DIRS/virt-builder/repos.d/ (where C<$VIRT_BUILDER_DIRS> means any of the directories in that environment variable, or just F</etc> if not set).
=back
-Each I<.conf> file in those paths has a simple text format like the
-following:
+Each I<.conf> file in those paths has a simple text format like the following:
[libguestfs.org]
uri=http://libguestfs.org/download/builder/index.asc
gpgkey=file:///etc/xdg/virt-builder/repos.d/libguestfs.gpg
-The part in square brackets is the repository identifier, which is used as
-unique identifier.
+The part in square brackets is the repository identifier, which is used as unique identifier.
The following fields can appear:
=item C<gpgkey=URI>
-This optional field represents the URI (although only I<file://> URIs are
-accepted) of the key used to sign the index file. If not present, the index
-file referred by I<uri=..> is not signed.
+This optional field represents the URI (although only I<file://> URIs are accepted) of the key used to sign the index file. If not present, the index file referred by I<uri=..> is not signed.
=item C<proxy=MODE>
-This optional field specifies the proxy mode, to be used when downloading
-the index file of this repository. The possible values are:
+This optional field specifies the proxy mode, to be used when downloading the index file of this repository. The possible values are:
=over 4
=item I<anything else>
-Specifies the actual proxy configuration to be used, overriding the system
-configuration.
+Specifies the actual proxy configuration to be used, overriding the system configuration.
=back
-If not present, the assumed value is to respect the proxy settings of the
-system (i.e. as if B<system> would be specified).
+If not present, the assumed value is to respect the proxy settings of the system (i.e. as if B<system> would be specified).
=item C<format=FORMAT>
-This optional field specifies the format of the repository. The possible
-values are:
+This optional field specifies the format of the repository. The possible values are:
=over 4
=item B<native>
-The native format of the C<virt-builder> repository. See also L</Creating
-and signing the index file> below.
+The native format of the C<virt-builder> repository. See also L</Creating and signing the index file> below.
=item B<simplestreams>
The URI represents the root of a Simple Streams v1.0 tree of metadata.
-For more information about Simple Streams, see also
-L<https://launchpad.net/simplestreams>.
+For more information about Simple Streams, see also L<https://launchpad.net/simplestreams>.
=back
=back
-For serious virt-builder use, you may want to create your own repository of
-templates.
+For serious virt-builder use, you may want to create your own repository of templates.
=head3 Libguestfs.org repository
-Out of the box, virt-builder downloads the file
-L<http://libguestfs.org/download/builder/index.asc> which is an index of
-available templates plus some information about each one, wrapped up in a
-digital signature. The command C<virt-builder --list> lists out the
-information in this index file.
+Out of the box, virt-builder downloads the file L<http://libguestfs.org/download/builder/index.asc> which is an index of available templates plus some information about each one, wrapped up in a digital signature. The command C<virt-builder --list> lists out the information in this index file.
-The templates hosted on libguestfs.org were created using shell scripts,
-kickstart files and preseed files which can be found in the libguestfs
-source tree, in C<builder/templates>.
+The templates hosted on libguestfs.org were created using shell scripts, kickstart files and preseed files which can be found in the libguestfs source tree, in C<builder/templates>.
=head3 Setting up the repository
-You can set up your own site containing an index file and some templates,
-and then point virt-builder at the site by creating a I<.conf> file pointing
-to it.
+You can set up your own site containing an index file and some templates, and then point virt-builder at the site by creating a I<.conf> file pointing to it.
-Note that if your index is signed, you will need to properly fill
-I<gpgkey=..> in your I<.conf> file, making sure to deploy also the GPG key
-file.
+Note that if your index is signed, you will need to properly fill I<gpgkey=..> in your I<.conf> file, making sure to deploy also the GPG key file.
virt-builder --source https://example.com/builder/index.asc \
--fingerprint 'AAAA BBBB ...' \
--list
-You can host this on any web or FTP server, or a local or network
-filesystem.
+You can host this on any web or FTP server, or a local or network filesystem.
=head3 Setting up a GPG key
-If you don’t have a GnuPG key, you will need to set one up. (Strictly
-speaking this is optional, but if your index and template files are not
-signed then virt-builder users will have to use the I<--no-check-signature>
-flag every time they use virt-builder.)
+If you don’t have a GnuPG key, you will need to set one up. (Strictly speaking this is optional, but if your index and template files are not signed then virt-builder users will have to use the I<--no-check-signature> flag every time they use virt-builder.)
-To create a key, see the GPG manual
-L<http://www.gnupg.org/gph/en/manual.html>.
+To create a key, see the GPG manual L<http://www.gnupg.org/gph/en/manual.html>.
Export your GPG public key:
=head3 Create the templates
-There are many ways to create the templates. For example you could clone
-existing guests (see L<virt-sysprep(1)>), or you could install a guest by
-hand (L<virt-install(1)>). To see how the templates were created for
-virt-builder, look at the scripts in C<builder/templates>
+There are many ways to create the templates. For example you could clone existing guests (see L<virt-sysprep(1)>), or you could install a guest by hand (L<virt-install(1)>). To see how the templates were created for virt-builder, look at the scripts in C<builder/templates>
-Virt-builder supports any image format (e.g. raw, qcow2, etc) as template,
-both as-is, and compressed as XZ. This way, existing images (e.g. cleaned
-using L<virt-sysprep(1)>) can be used as templates.
+Virt-builder supports any image format (e.g. raw, qcow2, etc) as template, both as-is, and compressed as XZ. This way, existing images (e.g. cleaned using L<virt-sysprep(1)>) can be used as templates.
-For best results when compressing the templates, use the following xz
-options (see L<nbdkit-xz-plugin(1)> for further explanation):
+For best results when compressing the templates, use the following xz options (see L<nbdkit-xz-plugin(1)> for further explanation):
xz --best --block-size=16777216 disk
=head3 Creating and signing the index file
-The index file has a simple text format (shown here without the digital
-signature):
+The index file has a simple text format (shown here without the digital signature):
[fedora-18]
name=Fedora® 18
compressed_size=172190964
expand=/dev/sda3
-The part in square brackets is the C<os-version>, which is the same string
-that is used on the virt-builder command line to build that OS.
+The part in square brackets is the C<os-version>, which is the same string that is used on the virt-builder command line to build that OS.
-The index file creation and signature can be eased with the
-L<virt-builder-repository(1)> tool.
+The index file creation and signature can be eased with the L<virt-builder-repository(1)> tool.
-After preparing the C<index> file in the correct format, clearsign it using
-the following command:
+After preparing the C<index> file in the correct format, clearsign it using the following command:
gpg --clearsign --armor index
-This will create the final file called F<index.asc> which can be uploaded to
-the server (and is the I<uri=..> URL). As noted above, signing the index
-file is optional, but recommended.
+This will create the final file called F<index.asc> which can be uploaded to the server (and is the I<uri=..> URL). As noted above, signing the index file is optional, but recommended.
The following fields can appear:
=item C<name=NAME>
-The user-friendly name of this template. This is displayed in the I<--list>
-output but is otherwise not significant.
+The user-friendly name of this template. This is displayed in the I<--list> output but is otherwise not significant.
=item C<osinfo=ID>
-This optional field maps the operating system to the associated libosinfo
-ID. Virt-builder does not use it (yet).
+This optional field maps the operating system to the associated libosinfo ID. Virt-builder does not use it (yet).
=item C<arch=ARCH>
-The architecture of the operating system installed within the template. This
-field is required.
+The architecture of the operating system installed within the template. This field is required.
=item C<file=PATH>
The path (relative to the index) of the xz-compressed template.
-Note that absolute paths or URIs are B<not> permitted here. This is because
-virt-builder has a "same origin" policy for templates so they cannot come
-from other servers.
+Note that absolute paths or URIs are B<not> permitted here. This is because virt-builder has a "same origin" policy for templates so they cannot come from other servers.
=item C<sig=PATH>
B<This option is deprecated>. Use the checksum field instead.
-The path (relative to the index) of the GPG detached signature of the xz
-file.
+The path (relative to the index) of the GPG detached signature of the xz file.
-Note that absolute paths or URIs are B<not> permitted here. This is because
-virt-builder has a "same origin" policy for templates so they cannot come
-from other servers.
+Note that absolute paths or URIs are B<not> permitted here. This is because virt-builder has a "same origin" policy for templates so they cannot come from other servers.
The file can be created as follows:
=item C<checksum[sha512]=7b882fe9b82eb0fef...>
-The SHA-512 checksum of the file specified in I<file=..> is checked after it
-is downloaded. To work out the signature, do:
+The SHA-512 checksum of the file specified in I<file=..> is checked after it is downloaded. To work out the signature, do:
sha512sum disk.xz
-Note if you use this, you don’t need to sign the file, ie. don’t use
-C<sig>. This option overrides C<sig>.
+Note if you use this, you don’t need to sign the file, ie. don’t use C<sig>. This option overrides C<sig>.
=item C<checksum=7b882fe9b82eb0fef...>
C<checksum> is an alias for C<checksum[sha512]>.
-If you need to interoperate with virt-builder = 1.24.0 then you have to use
-C<checksum> because that version would give a parse error with square
-brackets and numbers in the key of a field. This is fixed in virt-builder
-E<ge> 1.24.1.
+If you need to interoperate with virt-builder = 1.24.0 then you have to use C<checksum> because that version would give a parse error with square brackets and numbers in the key of a field. This is fixed in virt-builder E<ge> 1.24.1.
=item C<revision=N>
-The revision is an integer which is used to control the template cache.
-Increasing the revision number causes clients to download the template again
-even if they have a copy in the cache.
+The revision is an integer which is used to control the template cache. Increasing the revision number causes clients to download the template again even if they have a copy in the cache.
The revision number is optional. If omitted it defaults to C<1>.
=item C<format=qcow2>
-Specify the format of the disk image; in case it is compressed, that is the
-format before the compression. If not given, the format is autodetected,
-but generally it is better to be explicit about the intended format.
+Specify the format of the disk image; in case it is compressed, that is the format before the compression. If not given, the format is autodetected, but generally it is better to be explicit about the intended format.
-Note this is the source format, which is different from the I<--format>
-option (requested output format). Virt-builder does on-the-fly conversion
-from the source format to the requested output format.
+Note this is the source format, which is different from the I<--format> option (requested output format). Virt-builder does on-the-fly conversion from the source format to the requested output format.
=item C<size=NNN>
-The virtual size of the image in bytes. This is the size of the image when
-uncompressed. If using a non-raw format such as qcow2 then it means the
-virtual disk size, not the size of the qcow2 file.
+The virtual size of the image in bytes. This is the size of the image when uncompressed. If using a non-raw format such as qcow2 then it means the virtual disk size, not the size of the qcow2 file.
This field is required.
-Virt-builder also uses this as the minimum size that users can request via
-the I<--size> option, or as the default size if there is no I<--size>
-option.
+Virt-builder also uses this as the minimum size that users can request via the I<--size> option, or as the default size if there is no I<--size> option.
=item C<compressed_size=NNN>
-The actual size of the disk image in bytes, i.e. what was specified in
-I<file=..>. This is just used for information (when using C<long>, and
-C<json> formats of I<--list>).
+The actual size of the disk image in bytes, i.e. what was specified in I<file=..>. This is just used for information (when using C<long>, and C<json> formats of I<--list>).
=item C<expand=/dev/sdaX>
-When expanding the image to its final size, instruct L<virt-resize(1)> to
-expand the named partition in the guest image to fill up all available
-space. This works like the virt-resize I<--expand> option.
+When expanding the image to its final size, instruct L<virt-resize(1)> to expand the named partition in the guest image to fill up all available space. This works like the virt-resize I<--expand> option.
You should usually put the device name of the guest’s root filesystem here.
-It’s a good idea to use this, but not required. If the field is omitted
-then virt-resize will create an extra partition at the end of the disk to
-cover the free space, which is much less user-friendly.
+It’s a good idea to use this, but not required. If the field is omitted then virt-resize will create an extra partition at the end of the disk to cover the free space, which is much less user-friendly.
=item C<lvexpand=/dev/VolGroup/LogVol>
-When expanding the image to its final size, instruct L<virt-resize(1)> to
-expand the named logical volume in the guest image to fill up all available
-space. This works like the virt-resize I<--lv-expand> option.
+When expanding the image to its final size, instruct L<virt-resize(1)> to expand the named logical volume in the guest image to fill up all available space. This works like the virt-resize I<--lv-expand> option.
-If the guest uses LVM2 you should usually put the LV of the guest’s root
-filesystem here. If the guest does not use LVM2 or its root filesystem is
-not on an LV, don't use this option.
+If the guest uses LVM2 you should usually put the LV of the guest’s root filesystem here. If the guest does not use LVM2 or its root filesystem is not on an LV, don't use this option.
=item C<notes=NOTES>
-Any notes that go with this image, especially notes describing what packages
-are in the image, how the image was prepared, and licensing information.
+Any notes that go with this image, especially notes describing what packages are in the image, how the image was prepared, and licensing information.
This information is shown in the I<--notes> and I<--list> I<--long> modes.
-You can use multi-line notes here by indenting each new line with at least
-one character of whitespace (even on blank lines):
+You can use multi-line notes here by indenting each new line with at least one character of whitespace (even on blank lines):
notes=This image was prepared using
the following kickstart script:
=item C<hidden=true>
-Using the hidden flag prevents the template from being listed by the
-I<--list> option (but it is still installable). This is used for test
-images.
+Using the hidden flag prevents the template from being listed by the I<--list> option (but it is still installable). This is used for test images.
=item C<aliases=ALIAS1 ALIAS2 ...>
-This optional field specifies a list of aliases, separated by spaces, for
-the image. For example, an alias could be used to always point to the
-latest version of a certain image, leaving the old versions available in the
-index instead of updating the same image (see the C<revision> field).
+This optional field specifies a list of aliases, separated by spaces, for the image. For example, an alias could be used to always point to the latest version of a certain image, leaving the old versions available in the index instead of updating the same image (see the C<revision> field).
=back
=head3 Running virt-builder against multiple sources
-It is possible to use multiple sources with virt-builder. The recommended
-way is to deploy I<.conf> files pointing to the index files. Another way is
-to specify the sources using multiple I<--source> and/or I<--fingerprint>
-options:
+It is possible to use multiple sources with virt-builder. The recommended way is to deploy I<.conf> files pointing to the index files. Another way is to specify the sources using multiple I<--source> and/or I<--fingerprint> options:
virt-builder \
--source http://example.com/s1/index.asc \
--source http://example.com/s2/index.asc
-You can provide N or 1 fingerprints. In the case where you provide N
-fingerprints, N = number of sources and there is a 1-1 correspondence
-between each source and each fingerprint:
+You can provide N or 1 fingerprints. In the case where you provide N fingerprints, N = number of sources and there is a 1-1 correspondence between each source and each fingerprint:
virt-builder \
--source http://example.com/s1/index.asc --fingerprint '0123 ...' \
--source http://example.com/s2/index.asc --fingerprint '9876 ...'
-In the case where you provide 1 fingerprint, the same fingerprint is used
-for all sources.
+In the case where you provide 1 fingerprint, the same fingerprint is used for all sources.
You C<must> provide at least 1 fingerprint.
=head3 Licensing of templates
-You should be aware of the licensing of images that you distribute. For
-open source guests, provide a link to the source code in the C<notes> field
-and comply with other requirements (eg. around trademarks).
+You should be aware of the licensing of images that you distribute. For open source guests, provide a link to the source code in the C<notes> field and comply with other requirements (eg. around trademarks).
=head3 Formal specification of the index file
-The index file format has a formal specification defined by the flex scanner
-and bison parser used to parse the file. This can be found in the following
-files in the libguestfs source tree:
+The index file format has a formal specification defined by the flex scanner and bison parser used to parse the file. This can be found in the following files in the libguestfs source tree:
builder/index-scan.l
builder/index-parse.y
-A tool called L<virt-index-validate(1)> is available to validate the index
-file to ensure it is correct.
+A tool called L<virt-index-validate(1)> is available to validate the index file to ensure it is correct.
-Note that the parser and tool can work on either the signed or unsigned
-index file (ie. F<index> or F<index.asc>).
+Note that the parser and tool can work on either the signed or unsigned index file (ie. F<index> or F<index.asc>).
The index is always encoded in UTF-8.
=head3 Caching templates
-Since the templates are usually very large, downloaded templates are cached
-in the user’s home directory.
+Since the templates are usually very large, downloaded templates are cached in the user’s home directory.
-The location of the cache is F<$XDG_CACHE_HOME/virt-builder/> or
-F<$HOME/.cache/virt-builder>.
+The location of the cache is F<$XDG_CACHE_HOME/virt-builder/> or F<$HOME/.cache/virt-builder>.
-You can print out information about the cache directory, including which
-guests are currently cached, by doing:
+You can print out information about the cache directory, including which guests are currently cached, by doing:
virt-builder --print-cache
To disable the template cache, use I<--no-cache>.
-Only templates are cached. The index and detached digital signatures are
-not cached.
+Only templates are cached. The index and detached digital signatures are not cached.
=head3 Caching packages
-Virt-builder uses L<curl(1)> to download files and it also uses the current
-C<http_proxy> (etc) settings when installing packages (I<--install>,
-I<--update>).
+Virt-builder uses L<curl(1)> to download files and it also uses the current C<http_proxy> (etc) settings when installing packages (I<--install>, I<--update>).
-You may therefore want to set those environment variables in order to
-maximize the amount of local caching that happens. See L</ENVIRONMENT
-VARIABLES> and L<curl(1)>.
+You may therefore want to set those environment variables in order to maximize the amount of local caching that happens. See L</ENVIRONMENT VARIABLES> and L<curl(1)>.
=head3 Local mirrors
-To increase both speed and reliability of installing packages, you can set
-up a local mirror of the target distribution, and point the guest package
-manager at that.
+To increase both speed and reliability of installing packages, you can set up a local mirror of the target distribution, and point the guest package manager at that.
=head4 Using a local mirror with Fedora
=head4 Using a local mirror with Debian
-Assuming that you are using C<apt-proxy> to mirror the repository, you
-should create a new F<sources.list> file to point to your proxy (see
-L<https://help.ubuntu.com/community/AptProxy>) and then do:
+Assuming that you are using C<apt-proxy> to mirror the repository, you should create a new F<sources.list> file to point to your proxy (see L<https://help.ubuntu.com/community/AptProxy>) and then do:
virt-builder debian-8 \
--upload sources.list:/etc/apt/sources.list \
=head2 DIGITAL SIGNATURES
-Virt-builder uses GNU Privacy Guard (GnuPG or gpg) to verify that the index
-and templates have not been tampered with.
+Virt-builder uses GNU Privacy Guard (GnuPG or gpg) to verify that the index and templates have not been tampered with.
The source points to an index file, which is optionally signed.
-Virt-builder downloads the index and checks that the signature is valid and
-the signer’s fingerprint matches the specified fingerprint (ie. the one
-specified in I<gpgkey=..> in the I<.conf>, or with I<--fingerprint>, in that
-order).
+Virt-builder downloads the index and checks that the signature is valid and the signer’s fingerprint matches the specified fingerprint (ie. the one specified in I<gpgkey=..> in the I<.conf>, or with I<--fingerprint>, in that order).
-For checking against the built-in public key/fingerprint, this requires
-importing the public key into the user’s local gpg keyring (that’s just the
-way that gpg works).
+For checking against the built-in public key/fingerprint, this requires importing the public key into the user’s local gpg keyring (that’s just the way that gpg works).
When a template is downloaded, its signature is checked in the same way.
-Although the signatures are optional, if you don’t have them then
-virt-builder users will have to use I<--no-check-signature> on the command
-line. This prevents an attacker from replacing the signed index file with
-an unsigned index file and having virt-builder silently work without
-checking the signature. In any case it is highly recommended that you
-always create signed index and templates.
+Although the signatures are optional, if you don’t have them then virt-builder users will have to use I<--no-check-signature> on the command line. This prevents an attacker from replacing the signed index file with an unsigned index file and having virt-builder silently work without checking the signature. In any case it is highly recommended that you always create signed index and templates.
=head2 アーキテクチャー
-Virt-builder can build a guest for any architecture no matter what the host
-architecture is. For example an x86-64 guest on an ARM host.
+Virt-builder can build a guest for any architecture no matter what the host architecture is. For example an x86-64 guest on an ARM host.
-However certain options may not work, specifically options that require
-running commands in the guest during the build process: I<--install>,
-I<--update>, I<--run>, I<--run-command>. You may need to replace these with
-their firstboot-equivalents.
+However certain options may not work, specifically options that require running commands in the guest during the build process: I<--install>, I<--update>, I<--run>, I<--run-command>. You may need to replace these with their firstboot-equivalents.
-An x86-64 host building 32 bit i686 guests should work without any special
-steps.
+An x86-64 host building 32 bit i686 guests should work without any special steps.
=head2 セキュリティ
-Virt-builder does not need to run as root (in fact, should not be run as
-root), and doesn't use setuid, C<sudo> or any similar mechanism.
+Virt-builder does not need to run as root (in fact, should not be run as root), and doesn't use setuid, C<sudo> or any similar mechanism.
-I<--install>, I<--update>, I<--run> and I<--run-command> are implemented
-using an appliance (a small virtual machine) so these commands do not run on
-the host. If you are using the libguestfs libvirt backend and have SELinux
-enabled then the virtual machine is additionally encapsulated in an SELinux
-container (sVirt).
+I<--install>, I<--update>, I<--run> and I<--run-command> are implemented using an appliance (a small virtual machine) so these commands do not run on the host. If you are using the libguestfs libvirt backend and have SELinux enabled then the virtual machine is additionally encapsulated in an SELinux container (sVirt).
-However these options will have access to the host’s network and since the
-template may contain untrusted code, the code might try to access host
-network resources which it should not. You can use I<--no-network> to
-prevent this.
+However these options will have access to the host’s network and since the template may contain untrusted code, the code might try to access host network resources which it should not. You can use I<--no-network> to prevent this.
-Firstboot commands run in the context of the guest when it is booted, and so
-the security of your hypervisor / cloud should be considered.
+Firstboot commands run in the context of the guest when it is booted, and so the security of your hypervisor / cloud should be considered.
-Virt-builder injects a random seed into every guest which it builds. This
-helps to ensure that TCP sequence numbers, UUIDs, ssh host keys etc are
-truly random when the guest boots.
+Virt-builder injects a random seed into every guest which it builds. This helps to ensure that TCP sequence numbers, UUIDs, ssh host keys etc are truly random when the guest boots.
You should check digital signatures and not ignore any signing errors.
=head2 CLONES
-If you wish to create many new guests of the same type, it is tempting to
-run virt-builder once and then copy the output file. You should B<not> do
-this. You should run virt-builder once for each new guest you need.
+If you wish to create many new guests of the same type, it is tempting to run virt-builder once and then copy the output file. You should B<not> do this. You should run virt-builder once for each new guest you need.
-The reason is that each clone needs to have (at least) a separate random
-seed, and possibly other unique features (such as filesystem UUIDs) in
-future versions of virt-builder.
+The reason is that each clone needs to have (at least) a separate random seed, and possibly other unique features (such as filesystem UUIDs) in future versions of virt-builder.
-Another thing you should I<not> do is to boot the guest, then clone the
-booted disk image. The reason is that some guests create unique machine
-IDs, SSH host keys and so on at first boot, and you would not want clones to
-have duplicate identities.
+Another thing you should I<not> do is to boot the guest, then clone the booted disk image. The reason is that some guests create unique machine IDs, SSH host keys and so on at first boot, and you would not want clones to have duplicate identities.
See also: L<virt-sysprep(1)>.
=head2 PERFORMANCE
-The most important aspect of getting good performance is caching. Templates
-gets downloaded into the cache the first time they are used, or if you use
-the I<--cache-all-templates> option. See L</CACHING> above for further
-information.
+The most important aspect of getting good performance is caching. Templates gets downloaded into the cache the first time they are used, or if you use the I<--cache-all-templates> option. See L</CACHING> above for further information.
-Packages required for the I<--install> and I<--update> options are
-downloaded using the host network connection. Setting the C<http_proxy>,
-C<https_proxy> and C<ftp_proxy> environment variables to point to a local
-web cache may ensure they only need to be downloaded once. You can also try
-using a local package repository, although this can be complex to set up and
-varies according to which Linux distro you are trying to install.
+Packages required for the I<--install> and I<--update> options are downloaded using the host network connection. Setting the C<http_proxy>, C<https_proxy> and C<ftp_proxy> environment variables to point to a local web cache may ensure they only need to be downloaded once. You can also try using a local package repository, although this can be complex to set up and varies according to which Linux distro you are trying to install.
=head3 Using I<--no-sync>
-Use I<--no-sync>. However read the caveats in the L</OPTIONS> section
-above, since this can cause disk corruption if not used correctly.
+Use I<--no-sync>. However read the caveats in the L</OPTIONS> section above, since this can cause disk corruption if not used correctly.
=head3 Skipping virt-resize
-Virt-builder can skip the virt-resize step under certain conditions. This
-makes virt-builder much faster. The conditions are:
+Virt-builder can skip the virt-resize step under certain conditions. This makes virt-builder much faster. The conditions are:
=over 4
=head3 pxzcat
-Virt-builder uses an internal implementation of pxzcat (parallel xzcat) if
-liblzma was found at build time. If liblzma was not found at build time,
-regular C<xzcat> is used which is single-threaded.
-
-=head3 User-Mode Linux
-
-You can use virt-builder with the User-Mode Linux (UML) backend. This may
-be faster when running virt-builder inside a virtual machine (eg. in the
-cloud).
-
-To enable the UML backend, read the instructions in L<guestfs(3)/USER-MODE
-LINUX BACKEND>.
-
-Currently you have to use the I<--no-network> option. This should be fixed
-in a future version.
-
-The qcow2 output format is not supported by UML. You can only create
-raw-format guests.
+Virt-builder uses an internal implementation of pxzcat (parallel xzcat) if liblzma was found at build time. If liblzma was not found at build time, regular C<xzcat> is used which is single-threaded.
=head2 SELinux
-Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux)
-require that each file has a correct SELinux label.
+Guests which use SELinux (such as Fedora and Red Hat Enterprise Linux) require that each file has a correct SELinux label.
-Virt-builder does not know how to give new files a label, so there are two
-possible strategies it can use to ensure correct labelling:
+Virt-builder does not know how to give new files a label, so there are two possible strategies it can use to ensure correct labelling:
=over 4
=item Using I<--selinux-relabel>
-This runs L<setfiles(8)> just before finalizing the guest, which sets
-SELinux labels correctly in the disk image.
+This runs L<setfiles(8)> just before finalizing the guest, which sets SELinux labels correctly in the disk image.
This is the recommended method.
=item I<--touch> F</.autorelabel>
-Guest templates may already contain a file called F</.autorelabel> or you
-may touch it.
+Guest templates may already contain a file called F</.autorelabel> or you may touch it.
-For guests that use SELinux, this causes L<restorecon(8)> to run at first
-boot. Guests will reboot themselves once the first time you use them, which
-is normal and harmless.
+For guests that use SELinux, this causes L<restorecon(8)> to run at first boot. Guests will reboot themselves once the first time you use them, which is normal and harmless.
=back
-Please note that if your guest uses SELinux, and you are doing operations on
-it which might create new files or change existing ones, you are recommended
-to use I<--selinux-relabel>. This will help in making sure that files have
-the right SELinux labels.
+Please note that if your guest uses SELinux, and you are doing operations on it which might create new files or change existing ones, you are recommended to use I<--selinux-relabel>. This will help in making sure that files have the right SELinux labels.
=head1 マシン可読な出力
-The I<--machine-readable> option can be used to make the output more machine
-friendly, which is useful when calling virt-builder from other programs,
-GUIs etc.
+The I<--machine-readable> option can be used to make the output more machine friendly, which is useful when calling virt-builder from other programs, GUIs etc.
-Use the option on its own to query the capabilities of the virt-builder
-binary. Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-builder binary. Typical output looks like this:
$ virt-builder --machine-readable
virt-builder
json-list
pxzcat
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 環境変数
-For other environment variables which affect all libguestfs programs, see
-L<guestfs(3)/ENVIRONMENT VARIABLES>.
+For other environment variables which affect all libguestfs programs, see L<guestfs(3)/ENVIRONMENT VARIABLES>.
=over 4
=item C<no_proxy>
-Set the proxy for downloads. These environment variables (and more) are
-actually interpreted by L<curl(1)>, not virt-builder.
+Set the proxy for downloads. These environment variables (and more) are actually interpreted by L<curl(1)>, not virt-builder.
=item C<HOME>
-Used to determine the location of the template cache, and the location of
-the user' sources. See L</CACHING> and L</SOURCES OF TEMPLATES>.
+Used to determine the location of the template cache, and the location of the user' sources. See L</CACHING> and L</SOURCES OF TEMPLATES>.
=item C<VIRT_TOOLS_DATA_DIR>
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like F</usr/share/virt-tools>).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like F</usr/share/virt-tools>).
This directory may contain the following files:
=item F<rhsrvany.exe>
-This is the RHSrvAny Windows binary, used to install a "firstboot" script in
-Windows guests. It is required if you intend to use the I<--firstboot> or
-I<--firstboot-command> options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
See also: C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-This is a Windows binary shipped with SUSE VMDP, used to install a
-"firstboot" script in Windows guests. It is required if you intend to use
-the I<--firstboot> or I<--firstboot-command> options with Windows guests.
+This is a Windows binary shipped with SUSE VMDP, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
=back
=item C<XDG_CONFIG_HOME>
-Used to determine the location of the user' sources. See L</SOURCES OF
-TEMPLATES>.
+Used to determine the location of the user' sources. See L</SOURCES OF TEMPLATES>.
=item C<VIRT_BUILDER_DIRS>
-Used to determine the location of the system sources. See L</SOURCES OF
-TEMPLATES>.
+Used to determine the location of the system sources. See L</SOURCES OF TEMPLATES>.
=back
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>,
-L<virt-builder-repository(1)>, L<virt-copy-out(1)>, L<virt-customize(1)>,
-L<virt-get-kernel(1)>, L<virt-install(1)>, L<virt-rescue(1)>,
-L<virt-resize(1)>, L<virt-sysprep(1)>, L<oz-install(1)>, L<gpg(1)>,
-L<gpg2(1)>, L<curl(1)>, L<virt-make-fs(1)>, L<genisoimage(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-builder-repository(1)>, L<virt-copy-out(1)>, L<virt-customize(1)>, L<virt-get-kernel(1)>, L<virt-install(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sysprep(1)>, L<oz-install(1)>, L<gpg(1)>, L<gpg2(1)>, L<curl(1)>, L<virt-make-fs(1)>, L<genisoimage(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-cat 1"
-.TH virt-cat 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-cat 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\f(CW\*(C`virt\-cat\*(C'\fR は \f(CW\*(C`file\*(C'\fR の内容を表示するためにコマンドラインツールです。ここで \f(CW\*(C`file\*(C'\fR は仮想マシン
-(またはディスクイメージ) の中に存在します。
+\&\f(CW\*(C`virt\-cat\*(C'\fR は \f(CW\*(C`file\*(C'\fR の内容を表示するためにコマンドラインツールです。ここで \f(CW\*(C`file\*(C'\fR は仮想マシン (またはディスクイメージ) の中に存在します。
.PP
-Multiple filenames can be given, in which case they are concatenated
-together. Each filename must be a full path, starting at the root directory
-(starting with '/').
+Multiple filenames can be given, in which case they are concatenated together. Each filename must be a full path, starting at the root directory (starting with '/').
.PP
-\&\f(CW\*(C`virt\-cat\*(C'\fR can be used to quickly view a file. To edit a file, use
-\&\f(CW\*(C`virt\-edit\*(C'\fR. For more complex cases you should look at the \fBguestfish\fR\|(1)
-tool (see \*(L"\s-1USING GUESTFISH\*(R"\s0 below).
+\&\f(CW\*(C`virt\-cat\*(C'\fR can be used to quickly view a file. To edit a file, use \f(CW\*(C`virt\-edit\*(C'\fR. For more complex cases you should look at the \fBguestfish\fR\|(1) tool (see \*(L"\s-1USING GUESTFISH\*(R"\s0 below).
.SH "例"
.IX Header "例"
Display \fI/etc/fstab\fR file from inside the libvirt \s-1VM\s0 called \f(CW\*(C`mydomain\*(C'\fR:
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a \s-1URI\s0\fR" 4
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-キーやパスフレーズを入力するとき、通常 virt-cat はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-cat はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-cat \-\-format=raw \-a disk.img \-\-format \-a another.img file
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.Sp
If the mountpoint is omitted, it defaults to \fI/\fR.
.Sp
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
.Sp
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R"
-commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R" commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
.Sp
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR フラグが使用されている場合) になります。
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Sp
このフラグを使用することは、 \f(CW\*(C`mount\-options\*(C'\fR コマンドを使用することと同等です。
.Sp
-パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
\& virt\-cat guestname file
.Ve
.PP
-whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid the confusing case where a disk image might have the same name as a guest.
.PP
互換性のため古い形式がまだサポートされています。
.SH "LOG FILES"
.IX Header "LOG FILES"
-To list out the log files from guests, see the related tool \fBvirt\-log\fR\|(1).
-It understands binary log formats such as the systemd journal.
+To list out the log files from guests, see the related tool \fBvirt\-log\fR\|(1). It understands binary log formats such as the systemd journal.
.PP
To follow (tail) text log files, use \fBvirt\-tail\fR\|(1).
.SH "Windows のパス"
.IX Header "Windows のパス"
-\&\f(CW\*(C`virt\-cat\*(C'\fR has a limited ability to understand Windows drive letters and
-paths (eg. \fIE:\efoo\ebar.txt\fR).
+\&\f(CW\*(C`virt\-cat\*(C'\fR has a limited ability to understand Windows drive letters and paths (eg. \fIE:\efoo\ebar.txt\fR).
.PP
仮想マシンが Windows を実行している場合に限り:
.IP "\(bu" 4
-Drive letter prefixes like \f(CW\*(C`C:\*(C'\fR are resolved against the Windows Registry
-to the correct filesystem.
+Drive letter prefixes like \f(CW\*(C`C:\*(C'\fR are resolved against the Windows Registry to the correct filesystem.
.IP "\(bu" 4
-Any backslash (\f(CW\*(C`\e\*(C'\fR) characters in the path are replaced with forward
-slashes so that libguestfs can process it.
+Any backslash (\f(CW\*(C`\e\*(C'\fR) characters in the path are replaced with forward slashes so that libguestfs can process it.
.IP "\(bu" 4
-The path is resolved case insensitively to locate the file that should be
-displayed.
+The path is resolved case insensitively to locate the file that should be displayed.
.PP
There are some known shortcomings:
.IP "\(bu" 4
\& guestfish \-\-ro \-i \-d domname download file \-
.Ve
.PP
-ここで \f(CW\*(C`domname\*(C'\fR は libvirt 仮想マシンの名前です。また、\f(CW\*(C`file\*(C'\fR はファイルの完全パスです。最後の \f(CW\*(C`\-\*(C'\fR
-(\*(L"標準出力に出力\*(R" を意味します) に注意してください。
+ここで \f(CW\*(C`domname\*(C'\fR は libvirt 仮想マシンの名前です。また、\f(CW\*(C`file\*(C'\fR はファイルの完全パスです。最後の \f(CW\*(C`\-\*(C'\fR (\*(L"標準出力に出力\*(R" を意味します) に注意してください。
.PP
-The command above uses libguestfs’s guest inspection feature and so does not
-work on guests that libguestfs cannot inspect, or on things like arbitrary
-disk images that don't contain guests. To display a file from a disk image
-directly, use:
+The command above uses libguestfs’s guest inspection feature and so does not work on guests that libguestfs cannot inspect, or on things like arbitrary disk images that don't contain guests. To display a file from a disk image directly, use:
.PP
.Vb 1
\& guestfish \-\-ro \-a disk.img \-m /dev/sda1 download file \-
.Ve
.PP
-where \fIdisk.img\fR is the disk image, \fI/dev/sda1\fR is the filesystem within
-the disk image, and \f(CW\*(C`file\*(C'\fR is the full path to the file.
+where \fIdisk.img\fR is the disk image, \fI/dev/sda1\fR is the filesystem within the disk image, and \f(CW\*(C`file\*(C'\fR is the full path to the file.
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-edit\fR\|(1),
-\&\fBvirt\-log\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-edit\fR\|(1), \fBvirt\-log\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-C<virt-cat> は C<file> の内容を表示するためにコマンドラインツールです。ここで C<file> は仮想マシン
-(またはディスクイメージ) の中に存在します。
+C<virt-cat> は C<file> の内容を表示するためにコマンドラインツールです。ここで C<file> は仮想マシン (またはディスクイメージ) の中に存在します。
-Multiple filenames can be given, in which case they are concatenated
-together. Each filename must be a full path, starting at the root directory
-(starting with '/').
+Multiple filenames can be given, in which case they are concatenated together. Each filename must be a full path, starting at the root directory (starting with '/').
-C<virt-cat> can be used to quickly view a file. To edit a file, use
-C<virt-edit>. For more complex cases you should look at the L<guestfish(1)>
-tool (see L</USING GUESTFISH> below).
+C<virt-cat> can be used to quickly view a file. To edit a file, use C<virt-edit>. For more complex cases you should look at the L<guestfish(1)> tool (see L</USING GUESTFISH> below).
=head1 例
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--echo-keys>
-キーやパスフレーズを入力するとき、通常 virt-cat はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-cat はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
=item B<--format=raw|qcow2|..>
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-cat --format=raw -a disk.img --format -a another.img file
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
If the mountpoint is omitted, it defaults to F</>.
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see L</list-partitions>, L</list-filesystems> and L</lvs>
-commands), or you can use the L<virt-filesystems(1)> program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see L</list-partitions>, L</list-filesystems> and L</lvs> commands), or you can use the L<virt-filesystems(1)> program.
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro>
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro> フラグが使用されている場合) になります。
-m /dev/sda1:/:acl,user_xattr
このフラグを使用することは、 C<mount-options> コマンドを使用することと同等です。
-パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
=item B<-v>
virt-cat guestname file
-whereas in this version you should use I<-a> or I<-d> respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use I<-a> or I<-d> respectively to avoid the confusing case where a disk image might have the same name as a guest.
互換性のため古い形式がまだサポートされています。
=head1 LOG FILES
-To list out the log files from guests, see the related tool L<virt-log(1)>.
-It understands binary log formats such as the systemd journal.
+To list out the log files from guests, see the related tool L<virt-log(1)>. It understands binary log formats such as the systemd journal.
To follow (tail) text log files, use L<virt-tail(1)>.
=head1 Windows のパス
-C<virt-cat> has a limited ability to understand Windows drive letters and
-paths (eg. F<E:\foo\bar.txt>).
+C<virt-cat> has a limited ability to understand Windows drive letters and paths (eg. F<E:\foo\bar.txt>).
仮想マシンが Windows を実行している場合に限り:
=item *
-Drive letter prefixes like C<C:> are resolved against the Windows Registry
-to the correct filesystem.
+Drive letter prefixes like C<C:> are resolved against the Windows Registry to the correct filesystem.
=item *
-Any backslash (C<\>) characters in the path are replaced with forward
-slashes so that libguestfs can process it.
+Any backslash (C<\>) characters in the path are replaced with forward slashes so that libguestfs can process it.
=item *
-The path is resolved case insensitively to locate the file that should be
-displayed.
+The path is resolved case insensitively to locate the file that should be displayed.
=back
guestfish --ro -i -d domname download file -
-ここで C<domname> は libvirt 仮想マシンの名前です。また、C<file> はファイルの完全パスです。最後の C<->
-("標準出力に出力" を意味します) に注意してください。
+ここで C<domname> は libvirt 仮想マシンの名前です。また、C<file> はファイルの完全パスです。最後の C<-> ("標準出力に出力" を意味します) に注意してください。
-The command above uses libguestfs’s guest inspection feature and so does not
-work on guests that libguestfs cannot inspect, or on things like arbitrary
-disk images that don't contain guests. To display a file from a disk image
-directly, use:
+The command above uses libguestfs’s guest inspection feature and so does not work on guests that libguestfs cannot inspect, or on things like arbitrary disk images that don't contain guests. To display a file from a disk image directly, use:
guestfish --ro -a disk.img -m /dev/sda1 download file -
-where F<disk.img> is the disk image, F</dev/sda1> is the filesystem within
-the disk image, and C<file> is the full path to the file.
+where F<disk.img> is the disk image, F</dev/sda1> is the filesystem within the disk image, and C<file> is the full path to the file.
=head1 終了ステータス
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-edit(1)>,
-L<virt-log(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-edit(1)>, L<virt-log(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-customize 1"
-.TH virt-customize 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-customize 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-customize can customize a virtual machine (disk image) by installing
-packages, editing configuration files, and so on.
+Virt-customize can customize a virtual machine (disk image) by installing packages, editing configuration files, and so on.
.PP
-Virt-customize modifies the guest or disk image \fIin place\fR. The guest must
-be shut down. If you want to preserve the existing contents of the guest,
-\&\fIyou must snapshot, copy or clone the disk first\fR.
+Virt-customize modifies the guest or disk image \fIin place\fR. The guest must be shut down. If you want to preserve the existing contents of the guest, \fIyou must snapshot, copy or clone the disk first\fR.
.PP
-You do \fInot\fR need to run virt-customize as root. In fact we'd generally
-recommend that you don't.
+You do \fInot\fR need to run virt-customize as root. In fact we'd generally recommend that you don't.
.PP
Related tools include: \fBvirt\-sysprep\fR\|(1) and \fBvirt\-builder\fR\|(1).
.SH "オプション"
.IP "\fB\-\-add\fR \s-1URI\s0" 4
.IX Item "--add URI"
.PD
-Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See
-\&\*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
+Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See \*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
.IP "\fB\-\-attach\fR \s-1ISOFILE\s0" 4
.IX Item "--attach ISOFILE"
-The given disk is attached to the libguestfs appliance. This is used to
-provide extra software repositories or other data for customization.
+The given disk is attached to the libguestfs appliance. This is used to provide extra software repositories or other data for customization.
.Sp
-You probably want to ensure the volume(s) or filesystems in the attached
-disks are labelled (or use an \s-1ISO\s0 volume name) so that you can mount them by
-label in your run-scripts:
+You probably want to ensure the volume(s) or filesystems in the attached disks are labelled (or use an \s-1ISO\s0 volume name) so that you can mount them by label in your run-scripts:
.Sp
.Vb 2
\& mkdir /tmp/mount
\& mount LABEL=EXTRA /tmp/mount
.Ve
.Sp
-You can have multiple \fI\-\-attach\fR options, and the format can be any disk
-format (not just an \s-1ISO\s0).
+You can have multiple \fI\-\-attach\fR options, and the format can be any disk format (not just an \s-1ISO\s0).
.IP "\fB\-\-attach\-format\fR \s-1FORMAT\s0" 4
.IX Item "--attach-format FORMAT"
-Specify the disk format for the next \fI\-\-attach\fR option. The \f(CW\*(C`FORMAT\*(C'\fR is
-usually \f(CW\*(C`raw\*(C'\fR or \f(CW\*(C`qcow2\*(C'\fR. Use \f(CW\*(C`raw\*(C'\fR for ISOs.
+Specify the disk format for the next \fI\-\-attach\fR option. The \f(CW\*(C`FORMAT\*(C'\fR is usually \f(CW\*(C`raw\*(C'\fR or \f(CW\*(C`qcow2\*(C'\fR. Use \f(CW\*(C`raw\*(C'\fR for ISOs.
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-c\fR \s-1URI\s0" 4
.IX Item "-c URI"
.PD 0
.IP "\fB\-\-dry\-run\fR" 4
.IX Item "--dry-run"
.PD
-Perform a read-only \*(L"dry run\*(R" on the guest. This runs the sysprep
-operation, but throws away any changes to the disk at the end.
+Perform a read-only \*(L"dry run\*(R" on the guest. This runs the sysprep operation, but throws away any changes to the disk at the end.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-customize normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-customize normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-The default for the \fI\-a\fR option is to auto-detect the format of the disk
-image. Using this forces the disk format for \fI\-a\fR options which follow on
-the command line. Using \fI\-\-format auto\fR switches back to auto-detection
-for subsequent \fI\-a\fR options.
+The default for the \fI\-a\fR option is to auto-detect the format of the disk image. Using this forces the disk format for \fI\-a\fR options which follow on the command line. Using \fI\-\-format auto\fR switches back to auto-detection for subsequent \fI\-a\fR options.
.Sp
例:
.Sp
\& virt\-customize \-\-format raw \-a disk.img \-\-format auto \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IP "\fB\-\-memsize\fR \s-1MB\s0" 4
.IX Item "--memsize MB"
.PD
-Change the amount of memory allocated to \fI\-\-run\fR scripts. Increase this if
-you find that \fI\-\-run\fR scripts or the \fI\-\-install\fR option are running out of
-memory.
+Change the amount of memory allocated to \fI\-\-run\fR scripts. Increase this if you find that \fI\-\-run\fR scripts or the \fI\-\-install\fR option are running out of memory.
.Sp
The default can be found with this command:
.Sp
.Sp
Enabled is the default. Use \fI\-\-no\-network\fR to disable access.
.Sp
-The network only allows outgoing connections and has other minor
-limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
+The network only allows outgoing connections and has other minor limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
.Sp
-If you use \fI\-\-no\-network\fR then certain other options such as \fI\-\-install\fR
-will not work.
+If you use \fI\-\-no\-network\fR then certain other options such as \fI\-\-install\fR will not work.
.Sp
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-customize.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-customize.
.Sp
-Generally speaking you should \fInot\fR use \fI\-\-no\-network\fR. But here are some
-reasons why you might want to:
+Generally speaking you should \fInot\fR use \fI\-\-no\-network\fR. But here are some reasons why you might want to:
.RS 4
.IP "1." 4
-Because the libguestfs backend that you are using doesn't support the
-network. (See: \*(L"\s-1BACKEND\*(R"\s0 in \fBguestfs\fR\|(3)).
+Because the libguestfs backend that you are using doesn't support the network. (See: \*(L"\s-1BACKEND\*(R"\s0 in \fBguestfs\fR\|(3)).
.IP "2." 4
-Any software you need to install comes from an attached \s-1ISO,\s0 so you don't
-need the network.
+Any software you need to install comes from an attached \s-1ISO,\s0 so you don't need the network.
.IP "3." 4
-You don’t want untrusted guest code trying to access your host network when
-running virt-customize. This is particularly an issue when you don't trust
-the source of the operating system templates. (See \*(L"\s-1SECURITY\*(R"\s0 below).
+You don’t want untrusted guest code trying to access your host network when running virt-customize. This is particularly an issue when you don't trust the source of the operating system templates. (See \*(L"\s-1SECURITY\*(R"\s0 below).
.IP "4." 4
You don’t have a host network (eg. in secure/restricted environments).
.RE
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.IX Subsection "Customization options"
.IP "\fB\-\-append\-line\fR \s-1FILE:LINE\s0" 4
.IX Item "--append-line FILE:LINE"
-Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already
-end with a newline, then one is added before the appended line. Also a
-newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
+Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already end with a newline, then one is added before the appended line. Also a newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
.Sp
For example (assuming ordinary shell quoting) this command:
.Sp
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the
-latter only if the existing file does not already end with a newline.
+will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the latter only if the existing file does not already end with a newline.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the
-existing content of the file, so this command does the right thing for files
-using Unix or Windows line endings. It also works for empty or non-existent
-files.
+\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. It also works for empty or non-existent files.
.Sp
To insert several lines, use the same option several times:
.Sp
.IX Item "--chmod PERMISSIONS:FILE"
Change the permissions of \f(CW\*(C`FILE\*(C'\fR to \f(CW\*(C`PERMISSIONS\*(C'\fR.
.Sp
-\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it
-with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
+\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
.IP "\fB\-\-commands\-from\-file\fR \s-1FILENAME\s0" 4
.IX Item "--commands-from-file FILENAME"
Read the customize commands from a file, one (and its arguments) each line.
.Sp
-Each line contains a single customization command and its arguments, for
-example:
+Each line contains a single customization command and its arguments, for example:
.Sp
.Vb 3
\& delete /some/file
\& password some\-user:password:its\-new\-password
.Ve
.Sp
-Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are
-ignored as well. Furthermore, arguments can be spread across multiple
-lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for
-example
+Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are ignored as well. Furthermore, arguments can be spread across multiple lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for example
.Sp
.Vb 2
\& edit /some/file:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-The commands are handled in the same order as they are in the file, as if
-they were specified as \fI\-\-delete /some/file\fR on the command line.
+The commands are handled in the same order as they are in the file, as if they were specified as \fI\-\-delete /some/file\fR on the command line.
.IP "\fB\-\-copy\fR \s-1SOURCE:DEST\s0" 4
.IX Item "--copy SOURCE:DEST"
Copy files or directories recursively inside the guest.
Wildcards cannot be used.
.IP "\fB\-\-copy\-in\fR \s-1LOCALPATH:REMOTEDIR\s0" 4
.IX Item "--copy-in LOCALPATH:REMOTEDIR"
-Copy local files or directories recursively into the disk image, placing
-them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
+Copy local files or directories recursively into the disk image, placing them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
.Sp
Wildcards cannot be used.
.IP "\fB\-\-delete\fR \s-1PATH\s0" 4
.IX Item "--delete PATH"
-Delete a file from the guest. Or delete a directory (and all its contents,
-recursively).
+Delete a file from the guest. Or delete a directory (and all its contents, recursively).
.Sp
-You can use shell glob characters in the specified path. Be careful to
-escape glob characters from the host shell, if that is required. For
-example:
+You can use shell glob characters in the specified path. Be careful to escape glob characters from the host shell, if that is required. For example:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
See \*(L"NON-INTERACTIVE \s-1EDITING\*(R"\s0 in \fBvirt\-edit\fR\|(1).
.IP "\fB\-\-firstboot\fR \s-1SCRIPT\s0" 4
.IX Item "--firstboot SCRIPT"
-Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up,
-the script runs (as root, late in the boot process).
+Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up, the script runs (as root, late in the boot process).
.Sp
The script is automatically chmod +x after installation in the guest.
.Sp
-The alternative version \fI\-\-firstboot\-command\fR is the same, but it
-conveniently wraps the command up in a single line script for you.
+The alternative version \fI\-\-firstboot\-command\fR is the same, but it conveniently wraps the command up in a single line script for you.
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-command\fR '\s-1CMD+ARGS\s0'" 4
.IX Item "--firstboot-command 'CMD+ARGS'"
-Run command (and arguments) inside the guest when the guest first boots up
-(as root, late in the boot process).
+Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process).
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-install\fR \s-1PKG,PKG..\s0" 4
.IX Item "--firstboot-install PKG,PKG.."
-Install the named packages (a comma-separated list). These are installed
-when the guest first boots using the guest’s package manager (eg. apt, yum,
-etc.) and the guest’s network connection.
+Install the named packages (a comma-separated list). These are installed when the guest first boots using the guest’s package manager (eg. apt, yum, etc.) and the guest’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.IP "\fB\-\-hostname\fR \s-1HOSTNAME\s0" 4
.IX Item "--hostname HOSTNAME"
-Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted
-hostname.domainname (\s-1FQDN\s0) if you want.
+Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted hostname.domainname (\s-1FQDN\s0) if you want.
.IP "\fB\-\-install\fR \s-1PKG,PKG..\s0" 4
.IX Item "--install PKG,PKG.."
-Install the named packages (a comma-separated list). These are installed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.) and the host’s network connection.
+Install the named packages (a comma-separated list). These are installed during the image build using the guest’s package manager (eg. apt, yum, etc.) and the host’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.Sp
See also \fI\-\-update\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-link\fR TARGET:LINK[:LINK..]" 4
.IX Item "--link TARGET:LINK[:LINK..]"
-Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at
-\&\f(CW\*(C`TARGET\*(C'\fR.
+Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at \f(CW\*(C`TARGET\*(C'\fR.
.IP "\fB\-\-mkdir\fR \s-1DIR\s0" 4
.IX Item "--mkdir DIR"
Create a directory in the guest.
.Sp
-This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it
-also works if the directory already exists.
+This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it also works if the directory already exists.
.IP "\fB\-\-move\fR \s-1SOURCE:DEST\s0" 4
.IX Item "--move SOURCE:DEST"
Move files or directories inside the guest.
Wildcards cannot be used.
.IP "\fB\-\-no\-logfile\fR" 4
.IX Item "--no-logfile"
-Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after
-building is complete. If you don't want to reveal precisely how the image
-was built, use this option.
+Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after building is complete. If you don't want to reveal precisely how the image was built, use this option.
.Sp
See also: \*(L"\s-1LOG FILE\*(R"\s0.
.IP "\fB\-\-password\fR \s-1USER:SELECTOR\s0" 4
.IX Item "--password USER:SELECTOR"
-Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user
-account).
+Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user account).
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.IP "\fB\-\-password\-crypto\fR md5|sha256|sha512" 4
.IX Item "--password-crypto md5|sha256|sha512"
-When the virt tools change or set a password in the guest, this option sets
-the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
+When the virt tools change or set a password in the guest, this option sets the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
.Sp
-\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the
-guest).
+\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the guest).
.Sp
-\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not
-secure against modern attacks.
+\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not secure against modern attacks.
.Sp
-The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't
-have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can
-override libguestfs by specifying this option.
+The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can override libguestfs by specifying this option.
.Sp
-Note this does not change the default password encryption used by the guest
-when you create new user accounts inside the guest. If you want to do that,
-then you should use the \fI\-\-edit\fR option to modify
-\&\f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR
-(Debian, Ubuntu).
+Note this does not change the default password encryption used by the guest when you create new user accounts inside the guest. If you want to do that, then you should use the \fI\-\-edit\fR option to modify \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.IP "\fB\-\-root\-password\fR \s-1SELECTOR\s0" 4
.IX Item "--root-password SELECTOR"
Set the root password.
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.Sp
-Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest
-is given a \fIrandom\fR root password.
+Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest is given a \fIrandom\fR root password.
.IP "\fB\-\-run\fR \s-1SCRIPT\s0" 4
.IX Item "--run SCRIPT"
-Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image.
-The script runs virtualized inside a small appliance, chrooted into the
-guest filesystem.
+Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image. The script runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
The script is automatically chmod +x.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\fR options. They run in the same order that
-they appear on the command line.
+You can have multiple \fI\-\-run\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-run\-command\fR '\s-1CMD+ARGS\s0'" 4
.IX Item "--run-command 'CMD+ARGS'"
-Run the command and arguments on the disk image. The command runs
-virtualized inside a small appliance, chrooted into the guest filesystem.
+Run the command and arguments on the disk image. The command runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\-command\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-run\-command\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-scrub\fR \s-1FILE\s0" 4
.IX Item "--selinux-relabel"
Relabel files in the guest so that they have the correct SELinux label.
.Sp
-This will attempt to relabel files immediately, but if the operation fails
-this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel
-operation for the next time the image boots.
+This will attempt to relabel files immediately, but if the operation fails this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel operation for the next time the image boots.
.Sp
You should only use this option for guests which support SELinux.
.IP "\fB\-\-sm\-attach\fR \s-1SELECTOR\s0" 4
.IX Item "--sm-attach SELECTOR"
Attach to a pool using \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.IP "\fB\-\-sm\-credentials\fR \s-1SELECTOR\s0" 4
.IX Item "--sm-credentials SELECTOR"
Set the credentials for \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.IP "\fB\-\-sm\-register\fR" 4
.IX Item "--sm-register"
Register the guest using \f(CW\*(C`subscription\-manager\*(C'\fR.
Unregister the guest using \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-ssh\-inject\fR USER[:SELECTOR]" 4
.IX Item "--ssh-inject USER[:SELECTOR]"
-Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh
-without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
+Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
.Sp
See \*(L"\s-1SSH KEYS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.Sp
-You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also
-for more keys for each user.
+You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also for more keys for each user.
.IP "\fB\-\-timezone\fR \s-1TIMEZONE\s0" 4
.IX Item "--timezone TIMEZONE"
-Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string
-like \f(CW\*(C`Europe/London\*(C'\fR
+Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string like \f(CW\*(C`Europe/London\*(C'\fR
.IP "\fB\-\-touch\fR \s-1FILE\s0" 4
.IX Item "--touch FILE"
This command performs a \fBtouch\fR\|(1)\-like operation on \f(CW\*(C`FILE\*(C'\fR.
.IP "\fB\-\-truncate\fR \s-1FILE\s0" 4
.IX Item "--truncate FILE"
-This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist
-already.
+This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist already.
.IP "\fB\-\-truncate\-recursive\fR \s-1PATH\s0" 4
.IX Item "--truncate-recursive PATH"
This command recursively truncates all files under \f(CW\*(C`PATH\*(C'\fR to zero-length.
.IP "\fB\-\-uninstall\fR \s-1PKG,PKG..\s0" 4
.IX Item "--uninstall PKG,PKG.."
-Uninstall the named packages (a comma-separated list). These are removed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.). Dependent packages may also need to be uninstalled to satisfy the
-request.
+Uninstall the named packages (a comma-separated list). These are removed during the image build using the guest’s package manager (eg. apt, yum, etc.). Dependent packages may also need to be uninstalled to satisfy the request.
.Sp
See also \fI\-\-install\fR, \fI\-\-update\fR.
.IP "\fB\-\-update\fR" 4
.IX Item "--update"
-Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command
-is required to update the packages already installed in the template to
-their latest versions.
+Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command is required to update the packages already installed in the template to their latest versions.
.Sp
See also \fI\-\-install\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-upload\fR \s-1FILE:DEST\s0" 4
.IX Item "--upload FILE:DEST"
-Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File
-owner and permissions from the original are preserved, so you should set
-them to what you want them to be in the disk image.
+Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File owner and permissions from the original are preserved, so you should set them to what you want them to be in the disk image.
.Sp
-\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on
-upload.
+\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on upload.
.Sp
-If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then
-the file is uploaded into that directory, and it keeps the same name as on
-the local filesystem.
+If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then the file is uploaded into that directory, and it keeps the same name as on the local filesystem.
.Sp
See also: \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.IP "\fB\-\-write\fR \s-1FILE:CONTENT\s0" 4
Write \f(CW\*(C`CONTENT\*(C'\fR to \f(CW\*(C`FILE\*(C'\fR.
.SH "SELinux"
.IX Header "SELinux"
-For guests which make use of SELinux, special handling for them might be
-needed when using operations which create new files or alter existing ones.
+For guests which make use of SELinux, special handling for them might be needed when using operations which create new files or alter existing ones.
.PP
For further details, see \*(L"\s-1SELINUX\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.SH "終了ステータス"
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
.Sp
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like \fI/usr/share/virt\-tools\fR).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like \fI/usr/share/virt\-tools\fR).
.Sp
This directory may contain the following files:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in
-Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or
-\&\fI\-\-firstboot\-command\fR options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.Sp
See also: \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a
-\&\*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use
-the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
+This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.RE
.RS 4
.RE
他の環境変数は \*(L"環境変数\*(R" in \fBguestfs\fR\|(3) を参照してください。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1),
-\&\fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1),
-\&\fBvirt\-sysprep\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1),
-\&\fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1), \fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-customize can customize a virtual machine (disk image) by installing
-packages, editing configuration files, and so on.
+Virt-customize can customize a virtual machine (disk image) by installing packages, editing configuration files, and so on.
-Virt-customize modifies the guest or disk image I<in place>. The guest must
-be shut down. If you want to preserve the existing contents of the guest,
-I<you must snapshot, copy or clone the disk first>.
+Virt-customize modifies the guest or disk image I<in place>. The guest must be shut down. If you want to preserve the existing contents of the guest, I<you must snapshot, copy or clone the disk first>.
-You do I<not> need to run virt-customize as root. In fact we'd generally
-recommend that you don't.
+You do I<not> need to run virt-customize as root. In fact we'd generally recommend that you don't.
Related tools include: L<virt-sysprep(1)> and L<virt-builder(1)>.
=item B<--add> URI
-Add a remote disk. The URI format is compatible with guestfish. See
-L<guestfish(1)/ADDING REMOTE STORAGE>.
+Add a remote disk. The URI format is compatible with guestfish. See L<guestfish(1)/ADDING REMOTE STORAGE>.
=item B<--attach> ISOFILE
-The given disk is attached to the libguestfs appliance. This is used to
-provide extra software repositories or other data for customization.
+The given disk is attached to the libguestfs appliance. This is used to provide extra software repositories or other data for customization.
-You probably want to ensure the volume(s) or filesystems in the attached
-disks are labelled (or use an ISO volume name) so that you can mount them by
-label in your run-scripts:
+You probably want to ensure the volume(s) or filesystems in the attached disks are labelled (or use an ISO volume name) so that you can mount them by label in your run-scripts:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
-You can have multiple I<--attach> options, and the format can be any disk
-format (not just an ISO).
+You can have multiple I<--attach> options, and the format can be any disk format (not just an ISO).
=item B<--attach-format> FORMAT
-Specify the disk format for the next I<--attach> option. The C<FORMAT> is
-usually C<raw> or C<qcow2>. Use C<raw> for ISOs.
+Specify the disk format for the next I<--attach> option. The C<FORMAT> is usually C<raw> or C<qcow2>. Use C<raw> for ISOs.
=item B<--colors>
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<-c> URI
=item B<--dry-run>
-Perform a read-only "dry run" on the guest. This runs the sysprep
-operation, but throws away any changes to the disk at the end.
+Perform a read-only "dry run" on the guest. This runs the sysprep operation, but throws away any changes to the disk at the end.
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-customize normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-customize normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-The default for the I<-a> option is to auto-detect the format of the disk
-image. Using this forces the disk format for I<-a> options which follow on
-the command line. Using I<--format auto> switches back to auto-detection
-for subsequent I<-a> options.
+The default for the I<-a> option is to auto-detect the format of the disk image. Using this forces the disk format for I<-a> options which follow on the command line. Using I<--format auto> switches back to auto-detection for subsequent I<-a> options.
例:
virt-customize --format raw -a disk.img --format auto -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
=item B<--memsize> MB
-Change the amount of memory allocated to I<--run> scripts. Increase this if
-you find that I<--run> scripts or the I<--install> option are running out of
-memory.
+Change the amount of memory allocated to I<--run> scripts. Increase this if you find that I<--run> scripts or the I<--install> option are running out of memory.
The default can be found with this command:
Enabled is the default. Use I<--no-network> to disable access.
-The network only allows outgoing connections and has other minor
-limitations. See L<virt-rescue(1)/NETWORK>.
+The network only allows outgoing connections and has other minor limitations. See L<virt-rescue(1)/NETWORK>.
-If you use I<--no-network> then certain other options such as I<--install>
-will not work.
+If you use I<--no-network> then certain other options such as I<--install> will not work.
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-customize.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-customize.
-Generally speaking you should I<not> use I<--no-network>. But here are some
-reasons why you might want to:
+Generally speaking you should I<not> use I<--no-network>. But here are some reasons why you might want to:
=over 4
=item 1.
-Because the libguestfs backend that you are using doesn't support the
-network. (See: L<guestfs(3)/BACKEND>).
+Because the libguestfs backend that you are using doesn't support the network. (See: L<guestfs(3)/BACKEND>).
=item 2.
-Any software you need to install comes from an attached ISO, so you don't
-need the network.
+Any software you need to install comes from an attached ISO, so you don't need the network.
=item 3.
-You don’t want untrusted guest code trying to access your host network when
-running virt-customize. This is particularly an issue when you don't trust
-the source of the operating system templates. (See L</SECURITY> below).
+You don’t want untrusted guest code trying to access your host network when running virt-customize. This is particularly an issue when you don't trust the source of the operating system templates. (See L</SECURITY> below).
=item 4.
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 SELinux
-For guests which make use of SELinux, special handling for them might be
-needed when using operations which create new files or alter existing ones.
+For guests which make use of SELinux, special handling for them might be needed when using operations which create new files or alter existing ones.
For further details, see L<virt-builder(1)/SELINUX>.
=item C<VIRT_TOOLS_DATA_DIR>
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like F</usr/share/virt-tools>).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like F</usr/share/virt-tools>).
This directory may contain the following files:
=item F<rhsrvany.exe>
-This is the RHSrvAny Windows binary, used to install a "firstboot" script in
-Windows guests. It is required if you intend to use the I<--firstboot> or
-I<--firstboot-command> options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
See also: C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-This is a Windows binary shipped with SUSE VMDP, used to install a
-"firstboot" script in Windows guests. It is required if you intend to use
-the I<--firstboot> or I<--firstboot-command> options with Windows guests.
+This is a Windows binary shipped with SUSE VMDP, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
=back
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>,
-L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>,
-L<virt-sysprep(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>,
-L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>, L<virt-sysprep(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>, L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-df 1"
-.TH virt-df 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-df 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\f(CW\*(C`virt\-df\*(C'\fR is a command line tool to display free space on virtual machine
-filesystems. Unlike other tools, it doesn't just display the size of disk
-allocated to a virtual machine, but can look inside disk images to see how
-much space is really being used.
+\&\f(CW\*(C`virt\-df\*(C'\fR is a command line tool to display free space on virtual machine filesystems. Unlike other tools, it doesn't just display the size of disk allocated to a virtual machine, but can look inside disk images to see how much space is really being used.
.PP
-If used without any \fI\-a\fR or \fI\-d\fR arguments, \f(CW\*(C`virt\-df\*(C'\fR checks with libvirt
-to get a list of all active and inactive guests, and performs a \f(CW\*(C`df\*(C'\fR\-type
-operation on each one in turn, printing out the results.
+If used without any \fI\-a\fR or \fI\-d\fR arguments, \f(CW\*(C`virt\-df\*(C'\fR checks with libvirt to get a list of all active and inactive guests, and performs a \f(CW\*(C`df\*(C'\fR\-type operation on each one in turn, printing out the results.
.PP
-If any \fI\-a\fR or \fI\-d\fR arguments are specified, \f(CW\*(C`virt\-df\*(C'\fR performs a
-\&\f(CW\*(C`df\*(C'\fR\-type operation on either the single named libvirt domain, or on the
-disk image(s) listed on the command line (which must all belong to a single
-\&\s-1VM\s0). \fBIn this mode (with arguments), \f(CB\*(C`virt\-df\*(C'\fB will only work for a
-single guest\fR. If you want to run on multiple guests, then you have to
-invoke \f(CW\*(C`virt\-df\*(C'\fR multiple times.
+If any \fI\-a\fR or \fI\-d\fR arguments are specified, \f(CW\*(C`virt\-df\*(C'\fR performs a \f(CW\*(C`df\*(C'\fR\-type operation on either the single named libvirt domain, or on the disk image(s) listed on the command line (which must all belong to a single \s-1VM\s0). \fBIn this mode (with arguments), \f(CB\*(C`virt\-df\*(C'\fB will only work for a single guest\fR. If you want to run on multiple guests, then you have to invoke \f(CW\*(C`virt\-df\*(C'\fR multiple times.
.PP
-Use the \fI\-\-csv\fR option to get a format which can be easily parsed by other
-programs. Other options are similar to the standard \fBdf\fR\|(1) command.
+Use the \fI\-\-csv\fR option to get a format which can be easily parsed by other programs. Other options are similar to the standard \fBdf\fR\|(1) command.
.SH "例"
.IX Header "例"
-Show disk usage for a single libvirt guest called \f(CW\*(C`F14x64\*(C'\fR. Make the
-output human-readable:
+Show disk usage for a single libvirt guest called \f(CW\*(C`F14x64\*(C'\fR. Make the output human-readable:
.PP
.Vb 4
\& # virt\-df \-d F14x64 \-h
\& test1.img:/dev/sda1 99099 1551 92432 2%
.Ve
.PP
-If a single guest has multiple disks, use the \fI\-a\fR option repeatedly. A
-plus sign (\f(CW\*(C`+\*(C'\fR) is displayed for each additional disk. \fBNote: Do not do
-this with unrelated guest disks.\fR
+If a single guest has multiple disks, use the \fI\-a\fR option repeatedly. A plus sign (\f(CW\*(C`+\*(C'\fR) is displayed for each additional disk. \fBNote: Do not do this with unrelated guest disks.\fR
.PP
.Vb 5
\& $ virt\-df \-a Win7x32TwoDisks\-a \-a Win7x32TwoDisks\-b
.IP "\fB\-\-add\fR \s-1FILE\s0" 4
.IX Item "--add FILE"
.PD
-Add \f(CW\*(C`FILE\*(C'\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \f(CW\*(C`FILE\*(C'\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a\fR \s-1URI\s0" 4
ゲストのブロックデバイスを直接指定していると（(\fI\-a\fR)）、libvirt は何も使用されません。
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Write out the results in \s-1CSV\s0 format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE
-ABOUT CSV FORMAT\*(R"\s0 below.
+Write out the results in \s-1CSV\s0 format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE ABOUT CSV FORMAT\*(R"\s0 below.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-df \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
ブロックの代わりに inode を表示します。
.IP "\fB\-\-one\-per\-guest\fR" 4
.IX Item "--one-per-guest"
-Since libguestfs 1.22, this is the default. This option does nothing and is
-left here for backwards compatibility with older scripts.
+Since libguestfs 1.22, this is the default. This option does nothing and is left here for backwards compatibility with older scripts.
.IP "\fB\-P\fR nr_threads" 4
.IX Item "-P nr_threads"
-Since libguestfs 1.22, virt-df is multithreaded and examines guests in
-parallel. By default the number of threads to use is chosen based on the
-amount of free memory available at the time that virt-df is started. You
-can force virt-df to use at most \f(CW\*(C`nr_threads\*(C'\fR by using the \fI\-P\fR option.
+Since libguestfs 1.22, virt-df is multithreaded and examines guests in parallel. By default the number of threads to use is chosen based on the amount of free memory available at the time that virt-df is started. You can force virt-df to use at most \f(CW\*(C`nr_threads\*(C'\fR by using the \fI\-P\fR option.
.Sp
-Note that \fI\-P 0\fR means to autodetect, and \fI\-P 1\fR means to use a single
-thread.
+Note that \fI\-P 0\fR means to autodetect, and \fI\-P 1\fR means to use a single thread.
.IP "\fB\-\-uuid\fR" 4
.IX Item "--uuid"
-名前の代わりに \s-1UUID\s0 を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2
-つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
+名前の代わりに \s-1UUID\s0 を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2 つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
.Sp
-Note that only domains that we fetch from libvirt come with UUIDs. For disk
-images, we still print the disk image name even when this option is
-specified.
+Note that only domains that we fetch from libvirt come with UUIDs. For disk images, we still print the disk image name even when this option is specified.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.SH "STATVFS NUMBERS"
.IX Header "STATVFS NUMBERS"
-\&\f(CW\*(C`virt\-df\*(C'\fR (and \fBdf\fR\|(1)) get information by issuing a \fBstatvfs\fR\|(3) system
-call. You can get the same information directly, either from the host
-(using libguestfs) or inside the guest:
+\&\f(CW\*(C`virt\-df\*(C'\fR (and \fBdf\fR\|(1)) get information by issuing a \fBstatvfs\fR\|(3) system call. You can get the same information directly, either from the host (using libguestfs) or inside the guest:
.IP "ホストから" 4
.IX Item "ホストから"
このコマンドを実行してください:
(change \fI/\fR to see stats for other filesystems).
.SH "CSV 形式に関する注意"
.IX Header "CSV 形式に関する注意"
-Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it should be easy to parse, but it is definitely not easy to parse.
.PP
神話: ただコンマで項目を区切る。 真実: これは正しく動き \fIません\fR。この例は 2 つの列があります:
.PP
\& bar",baz
.Ve
.PP
-For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv
-also packaged in major Linux distributions).
+For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv also packaged in major Linux distributions).
.PP
-For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl
-or Python’s built-in csv library).
+For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl or Python’s built-in csv library).
.PP
Most spreadsheets and databases can import \s-1CSV\s0 directly.
.SH "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBdf\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1),
-http://libguestfs.org/.
+\&\fBdf\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-C<virt-df> is a command line tool to display free space on virtual machine
-filesystems. Unlike other tools, it doesn't just display the size of disk
-allocated to a virtual machine, but can look inside disk images to see how
-much space is really being used.
+C<virt-df> is a command line tool to display free space on virtual machine filesystems. Unlike other tools, it doesn't just display the size of disk allocated to a virtual machine, but can look inside disk images to see how much space is really being used.
-If used without any I<-a> or I<-d> arguments, C<virt-df> checks with libvirt
-to get a list of all active and inactive guests, and performs a C<df>-type
-operation on each one in turn, printing out the results.
+If used without any I<-a> or I<-d> arguments, C<virt-df> checks with libvirt to get a list of all active and inactive guests, and performs a C<df>-type operation on each one in turn, printing out the results.
-If any I<-a> or I<-d> arguments are specified, C<virt-df> performs a
-C<df>-type operation on either the single named libvirt domain, or on the
-disk image(s) listed on the command line (which must all belong to a single
-VM). B<In this mode (with arguments), C<virt-df> will only work for a
-single guest>. If you want to run on multiple guests, then you have to
-invoke C<virt-df> multiple times.
+If any I<-a> or I<-d> arguments are specified, C<virt-df> performs a C<df>-type operation on either the single named libvirt domain, or on the disk image(s) listed on the command line (which must all belong to a single VM). B<In this mode (with arguments), C<virt-df> will only work for a single guest>. If you want to run on multiple guests, then you have to invoke C<virt-df> multiple times.
-Use the I<--csv> option to get a format which can be easily parsed by other
-programs. Other options are similar to the standard L<df(1)> command.
+Use the I<--csv> option to get a format which can be easily parsed by other programs. Other options are similar to the standard L<df(1)> command.
=head1 例
-Show disk usage for a single libvirt guest called C<F14x64>. Make the
-output human-readable:
+Show disk usage for a single libvirt guest called C<F14x64>. Make the output human-readable:
# virt-df -d F14x64 -h
Filesystem Size Used Available Use%
Filesystem 1K-blocks Used Available Use%
test1.img:/dev/sda1 99099 1551 92432 2%
-If a single guest has multiple disks, use the I<-a> option repeatedly. A
-plus sign (C<+>) is displayed for each additional disk. B<Note: Do not do
-this with unrelated guest disks.>
+If a single guest has multiple disks, use the I<-a> option repeatedly. A plus sign (C<+>) is displayed for each additional disk. B<Note: Do not do this with unrelated guest disks.>
$ virt-df -a Win7x32TwoDisks-a -a Win7x32TwoDisks-b
Filesystem 1K-blocks Used Available Use%
=item B<--add> FILE
-Add C<FILE> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add C<FILE> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--csv>
-Write out the results in CSV format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read L</NOTE
-ABOUT CSV FORMAT> below.
+Write out the results in CSV format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read L</NOTE ABOUT CSV FORMAT> below.
=item B<-d> guest
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-df --format=raw -a disk.img --format -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<-h>
=item B<--one-per-guest>
-Since libguestfs 1.22, this is the default. This option does nothing and is
-left here for backwards compatibility with older scripts.
+Since libguestfs 1.22, this is the default. This option does nothing and is left here for backwards compatibility with older scripts.
=item B<-P> nr_threads
-Since libguestfs 1.22, virt-df is multithreaded and examines guests in
-parallel. By default the number of threads to use is chosen based on the
-amount of free memory available at the time that virt-df is started. You
-can force virt-df to use at most C<nr_threads> by using the I<-P> option.
+Since libguestfs 1.22, virt-df is multithreaded and examines guests in parallel. By default the number of threads to use is chosen based on the amount of free memory available at the time that virt-df is started. You can force virt-df to use at most C<nr_threads> by using the I<-P> option.
-Note that I<-P 0> means to autodetect, and I<-P 1> means to use a single
-thread.
+Note that I<-P 0> means to autodetect, and I<-P 1> means to use a single thread.
=item B<--uuid>
-名前の代わりに UUID を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2
-つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
+名前の代わりに UUID を表示します。仮想マシンがマイグレーションまたは名前変更されたとき、または偶然 2 つの仮想マシンが同じ名前を持つとき、仮想マシンに使用させるために有用です。
-Note that only domains that we fetch from libvirt come with UUIDs. For disk
-images, we still print the disk image name even when this option is
-specified.
+Note that only domains that we fetch from libvirt come with UUIDs. For disk images, we still print the disk image name even when this option is specified.
=item B<-v>
=head1 STATVFS NUMBERS
-C<virt-df> (and L<df(1)>) get information by issuing a L<statvfs(3)> system
-call. You can get the same information directly, either from the host
-(using libguestfs) or inside the guest:
+C<virt-df> (and L<df(1)>) get information by issuing a L<statvfs(3)> system call. You can get the same information directly, either from the host (using libguestfs) or inside the guest:
=over 4
=head1 CSV 形式に関する注意
-Comma-separated values (CSV) is a deceptive format. It I<seems> like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (CSV) is a deceptive format. It I<seems> like it should be easy to parse, but it is definitely not easy to parse.
神話: ただコンマで項目を区切る。 真実: これは正しく動き I<ません>。この例は 2 つの列があります:
"foo
bar",baz
-For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv>
-also packaged in major Linux distributions).
+For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv> also packaged in major Linux distributions).
-For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl
-or Python’s built-in csv library).
+For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl or Python’s built-in csv library).
Most spreadsheets and databases can import CSV directly.
=head1 関連項目
-L<df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>,
-L<http://libguestfs.org/>.
+L<df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-dib 1"
-.TH virt-dib 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-dib 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-dib is a tool for using the elements of \f(CW\*(C`diskimage\-builder\*(C'\fR to build a
-new disk image, generate new ramdisks, etc.
+Virt-dib is a tool for using the elements of \f(CW\*(C`diskimage\-builder\*(C'\fR to build a new disk image, generate new ramdisks, etc.
.PP
-Virt-dib is intended as safe replacement for \f(CW\*(C`diskimage\-builder\*(C'\fR and its
-\&\f(CW\*(C`ramdisk\-image\-create\*(C'\fR mode, see \*(L"\s-1COMPARISON WITH\s0 DISKIMAGE-BUILDER\*(R" for
-a quick comparison with usage of \f(CW\*(C`diskimage\-builder\*(C'\fR.
+Virt-dib is intended as safe replacement for \f(CW\*(C`diskimage\-builder\*(C'\fR and its \f(CW\*(C`ramdisk\-image\-create\*(C'\fR mode, see \*(L"\s-1COMPARISON WITH\s0 DISKIMAGE-BUILDER\*(R" for a quick comparison with usage of \f(CW\*(C`diskimage\-builder\*(C'\fR.
.PP
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR is part of the TripleO OpenStack project:
-https://wiki.openstack.org/wiki/TripleO.
+\&\f(CW\*(C`diskimage\-builder\*(C'\fR is part of the TripleO OpenStack project: https://wiki.openstack.org/wiki/TripleO.
.SH "例"
.IX Header "例"
.SS "Build simple images of distributions"
\& debian vm
.Ve
.PP
-This builds a Debian Jessie (8.x) disk image, suitable for running as
-virtual machine, saved as \fIdebian\-jessie.qcow2\fR.
+This builds a Debian Jessie (8.x) disk image, suitable for running as virtual machine, saved as \fIdebian\-jessie.qcow2\fR.
.SS "Build ramdisks"
.IX Subsection "Build ramdisks"
.Vb 6
\& ubuntu deploy\-ironic
.Ve
.PP
-This builds a ramdisk for the Ironic OpenStack component based on the Ubuntu
-distribution.
+This builds a ramdisk for the Ironic OpenStack component based on the Ubuntu distribution.
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
ヘルプを表示します。
.IP "\fB\-B\fR \s-1PATH\s0" 4
.IX Item "-B PATH"
-Set the path to the library directory of \f(CW\*(C`diskimage\-builder\*(C'\fR. This is
-usually the \fIlib\fR subdirectory in the sources and when installed, and
-\&\fI/usr/share/diskimage\-builder/lib\fR when installed in \fI/usr\fR.
+Set the path to the library directory of \f(CW\*(C`diskimage\-builder\*(C'\fR. This is usually the \fIlib\fR subdirectory in the sources and when installed, and \fI/usr/share/diskimage\-builder/lib\fR when installed in \fI/usr\fR.
.Sp
-This parameter is \fBmandatory\fR, as virt-dib needs to provide it for the
-elements (as some of them might use scripts in it). Virt-dib itself does
-not make use of the library directory.
+This parameter is \fBmandatory\fR, as virt-dib needs to provide it for the elements (as some of them might use scripts in it). Virt-dib itself does not make use of the library directory.
.IP "\fB\-\-arch\fR \s-1ARCHITECTURE\s0" 4
.IX Item "--arch ARCHITECTURE"
-Use the specified architecture for the output image. The default value is
-the same as the host running virt-dib.
+Use the specified architecture for the output image. The default value is the same as the host running virt-dib.
.Sp
-Right now this option does nothing more than setting the \f(CW\*(C`ARCH\*(C'\fR environment
-variable for the elements, and it’s up to them to produce an image for the
-requested architecture.
+Right now this option does nothing more than setting the \f(CW\*(C`ARCH\*(C'\fR environment variable for the elements, and it’s up to them to produce an image for the requested architecture.
.IP "\fB\-\-checksum\fR" 4
.IX Item "--checksum"
-Generate checksum files for the generated image. The supported checksums
-are \s-1MD5,\s0 and \s-1SHA256.\s0
+Generate checksum files for the generated image. The supported checksums are \s-1MD5,\s0 and \s-1SHA256.\s0
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-\-debug\fR \s-1LEVEL\s0" 4
.IX Item "--debug LEVEL"
-Set the debug level to \f(CW\*(C`LEVEL\*(C'\fR, which is a non-negative integer number.
-The default is \f(CW0\fR.
+Set the debug level to \f(CW\*(C`LEVEL\*(C'\fR, which is a non-negative integer number. The default is \f(CW0\fR.
.Sp
-This debug level is different than what \fI\-x\fR and \fI\-v\fR set, and it
-increases the debugging information printed out. Specifically, this sets
-the \f(CW\*(C`DIB_DEBUG_TRACE\*(C'\fR, and any value > \f(CW0\fR enables tracing in the
-scripts executed.
+This debug level is different than what \fI\-x\fR and \fI\-v\fR set, and it increases the debugging information printed out. Specifically, this sets the \f(CW\*(C`DIB_DEBUG_TRACE\*(C'\fR, and any value > \f(CW0\fR enables tracing in the scripts executed.
.IP "\fB\-\-docker\-target\fR \s-1TARGET\s0" 4
.IX Item "--docker-target TARGET"
Set the repository and tag for docker.
.Sp
-This is used only when the formats include \f(CW\*(C`docker\*(C'\fR, and it is required in
-that case.
+This is used only when the formats include \f(CW\*(C`docker\*(C'\fR, and it is required in that case.
.IP "\fB\-\-drive\fR \s-1DISK\s0" 4
.IX Item "--drive DISK"
-Add the specified disk to be used as helper drive where to cache files of
-the elements, like disk images, distribution packages, etc.
+Add the specified disk to be used as helper drive where to cache files of the elements, like disk images, distribution packages, etc.
.Sp
See \*(L"\s-1HELPER DRIVE\*(R"\s0.
.IP "\fB\-\-drive\-format\fR raw" 4
.IP "\fB\-\-drive\-format\fR qcow2" 4
.IX Item "--drive-format qcow2"
.PD
-Specify the format of the helper drive. If this flag is not given then it
-is auto-detected from the drive itself.
+Specify the format of the helper drive. If this flag is not given then it is auto-detected from the drive itself.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.Sp
This option is used only if \fI\-\-drive\fR is specified.
.Sp
.IP "\fB\-\-element\-path\fR \s-1PATH\s0" 4
.IX Item "--element-path PATH"
.PD
-Add a new path with elements. Paths are used in the same order as the \fI\-p\fR
-parameters appear, so a path specified first is looked first, and so on.
+Add a new path with elements. Paths are used in the same order as the \fI\-p\fR parameters appear, so a path specified first is looked first, and so on.
.Sp
-Obviously, it is recommended to add the path to the own elements of
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR, as most of the other elements will rely on them.
+Obviously, it is recommended to add the path to the own elements of \f(CW\*(C`diskimage\-builder\*(C'\fR, as most of the other elements will rely on them.
.IP "\fB\-\-extra\-packages\fR \s-1PACKAGE,...\s0" 4
.IX Item "--extra-packages PACKAGE,..."
Install additional packages in the image being built.
.Sp
-This relies on the \f(CW\*(C`install\-packages\*(C'\fR binary provided by the package
-management elements.
+This relies on the \f(CW\*(C`install\-packages\*(C'\fR binary provided by the package management elements.
.Sp
-This option can be specified multiple times, each time with multiple
-packages separated by comma.
+This option can be specified multiple times, each time with multiple packages separated by comma.
.IP "\fB\-\-envvar\fR \s-1VARIABLE\s0" 4
.IX Item "--envvar VARIABLE"
.PD 0
.PD
Carry or set an environment variable for the elements.
.Sp
-See \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 below for more information on the interaction
-and usage of environment variables.
+See \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 below for more information on the interaction and usage of environment variables.
.Sp
This option can be used in two ways:
.RS 4
.IP "\fB\-\-envvar\fR \s-1VARIABLE\s0" 4
.IX Item "--envvar VARIABLE"
-Carry the environment variable \f(CW\*(C`VARIABLE\*(C'\fR. If it is not set, nothing is
-exported to the elements.
+Carry the environment variable \f(CW\*(C`VARIABLE\*(C'\fR. If it is not set, nothing is exported to the elements.
.IP "\fB\-\-envvar\fR VARIABLE=VALUE" 4
.IX Item "--envvar VARIABLE=VALUE"
-Set the environment variable \f(CW\*(C`VARIABLE\*(C'\fR with value \f(CW\*(C`VALUE\*(C'\fR for the
-elements, regardless whether an environment variable with the same name
-exists.
+Set the environment variable \f(CW\*(C`VARIABLE\*(C'\fR with value \f(CW\*(C`VALUE\*(C'\fR for the elements, regardless whether an environment variable with the same name exists.
.Sp
-This can be useful to pass environment variable without exporting them in
-the environment where virt-dib runs.
+This can be useful to pass environment variable without exporting them in the environment where virt-dib runs.
.RE
.RS 4
.RE
.IX Item "--exclude-script SCRIPT"
Ignore any element script named \f(CW\*(C`SCRIPT\*(C'\fR, whichever element it is in.
.Sp
-This can be useful in case some script does not run well with virt-dib, for
-example when they really need \f(CW\*(C`diskimage\-builder\*(C'\fR's environment.
+This can be useful in case some script does not run well with virt-dib, for example when they really need \f(CW\*(C`diskimage\-builder\*(C'\fR's environment.
.IP "\fB\-\-formats\fR \s-1FORMAT,...\s0" 4
.IX Item "--formats FORMAT,..."
Set the list of output formats, separating them with comma.
.ie n .IP """docker""" 4
.el .IP "\f(CWdocker\fR" 4
.IX Item "docker"
-Import the image to docker, running \fBdocker import\fR. The target for the
-image \fBmust\fR be specified using \fI\-\-docker\-target\fR.
+Import the image to docker, running \fBdocker import\fR. The target for the image \fBmust\fR be specified using \fI\-\-docker\-target\fR.
.Sp
-Please note this operation usually requires the docker service to be
-enabled, otherwise it will fail. Furthermore, \fBdocker\fR is run using
-\&\fBsudo\fR\|(8), so make sure the user has the permissions to run at least
-\&\fBdocker\fR.
+Please note this operation usually requires the docker service to be enabled, otherwise it will fail. Furthermore, \fBdocker\fR is run using \fBsudo\fR\|(8), so make sure the user has the permissions to run at least \fBdocker\fR.
.ie n .IP """qcow2"" (enabled by default)" 4
.el .IP "\f(CWqcow2\fR (enabled by default)" 4
.IX Item "qcow2 (enabled by default)"
.ie n .IP """squashfs""" 4
.el .IP "\f(CWsquashfs\fR" 4
.IX Item "squashfs"
-An squashfs filesystem, compressed with \s-1XZ.\s0 This output format requires the
-\&\f(CW\*(C`squashfs\*(C'\fR feature; see also \*(L"\s-1AVAILABILITY\*(R"\s0 in \fBguestfs\fR\|(3).
+An squashfs filesystem, compressed with \s-1XZ.\s0 This output format requires the \f(CW\*(C`squashfs\*(C'\fR feature; see also \*(L"\s-1AVAILABILITY\*(R"\s0 in \fBguestfs\fR\|(3).
.ie n .IP """tar""" 4
.el .IP "\f(CWtar\fR" 4
.IX Item "tar"
.ie n .IP """vhd""" 4
.el .IP "\f(CWvhd\fR" 4
.IX Item "vhd"
-\&\f(CW\*(C`Virtual Hard Disk\*(C'\fR disk image. This output format requires the
-\&\f(CW\*(C`vhd\-util\*(C'\fR tool.
+\&\f(CW\*(C`Virtual Hard Disk\*(C'\fR disk image. This output format requires the \f(CW\*(C`vhd\-util\*(C'\fR tool.
.Sp
-Please note that the version of \f(CW\*(C`vhd\-util\*(C'\fR tool needs to be patched to
-support the \f(CW\*(C`convert\*(C'\fR subcommand, and to be bootable. The patch is
-available here:
-https://github.com/emonty/vhd\-util/blob/master/debian/patches/citrix.
+Please note that the version of \f(CW\*(C`vhd\-util\*(C'\fR tool needs to be patched to support the \f(CW\*(C`convert\*(C'\fR subcommand, and to be bootable. The patch is available here: https://github.com/emonty/vhd\-util/blob/master/debian/patches/citrix.
.RE
.RS 4
.RE
.IP "\fB\-\-fs\-type\fR \s-1FILESYSTEM\s0" 4
.IX Item "--fs-type FILESYSTEM"
-Set the filesystem type to use for the root filesystem. The default is
-\&\f(CW\*(C`ext4\*(C'\fR.
+Set the filesystem type to use for the root filesystem. The default is \f(CW\*(C`ext4\*(C'\fR.
.Sp
See also \*(L"guestfs_filesystem_available\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-image\-cache\fR \s-1DIRECTORY\s0" 4
.IX Item "--image-cache DIRECTORY"
-Set the path in the host where cache the resources used by the elements of
-the \f(CW\*(C`extra\-data.d\*(C'\fR phase. The default is \fI~/.cache/image\-create\fR.
+Set the path in the host where cache the resources used by the elements of the \f(CW\*(C`extra\-data.d\*(C'\fR phase. The default is \fI~/.cache/image\-create\fR.
.Sp
-Please note that most of the resources fetched in phases other than
-\&\f(CW\*(C`extra\-data.d\*(C'\fR will be cached in the helper drive specified with
-\&\fI\-\-drive\fR; see also \*(L"\s-1HELPER DRIVE\*(R"\s0.
+Please note that most of the resources fetched in phases other than \f(CW\*(C`extra\-data.d\*(C'\fR will be cached in the helper drive specified with \fI\-\-drive\fR; see also \*(L"\s-1HELPER DRIVE\*(R"\s0.
.IP "\fB\-\-install\-type\fR \s-1TYPE\s0" 4
.IX Item "--install-type TYPE"
Specify the default installation type. Defaults to \f(CW\*(C`source\*(C'\fR.
.IP "\fB\-\-memsize\fR \s-1MB\s0" 4
.IX Item "--memsize MB"
.PD
-Change the amount of memory allocated to the appliance. Increase this if you
-find that the virt-dib execution runs out of memory.
+Change the amount of memory allocated to the appliance. Increase this if you find that the virt-dib execution runs out of memory.
.Sp
The default can be found with this command:
.Sp
.ie n .IP "\fB\-\-mkfs\-options\fR ""OPTION STRING""" 4
.el .IP "\fB\-\-mkfs\-options\fR \f(CWOPTION STRING\fR" 4
.IX Item "--mkfs-options OPTION STRING"
-Add the specified options to \fBmkfs\fR\|(1), to be able to fine-tune the root
-filesystem creation; the options are passed to the driver of \fBmfks\fR\|(1), and
-not to \fBmfks\fR\|(1) itself. Note that \fI\-\-fs\-type\fR is used to change the
-filesystem type.
+Add the specified options to \fBmkfs\fR\|(1), to be able to fine-tune the root filesystem creation; the options are passed to the driver of \fBmfks\fR\|(1), and not to \fBmfks\fR\|(1) itself. Note that \fI\-\-fs\-type\fR is used to change the filesystem type.
.Sp
-You should use \fI\-\-mkfs\-options\fR at most once. To pass multiple options,
-separate them with space, eg:
+You should use \fI\-\-mkfs\-options\fR at most once. To pass multiple options, separate them with space, eg:
.Sp
.Vb 1
\& virt\-dib ... \-\-mkfs\-options \*(Aq\-O someopt \-I foo\*(Aq
.Sp
Enabled is the default. Use \fI\-\-no\-network\fR to disable access.
.Sp
-The network only allows outgoing connections and has other minor
-limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
+The network only allows outgoing connections and has other minor limitations. See \*(L"\s-1NETWORK\*(R"\s0 in \fBvirt\-rescue\fR\|(1).
.Sp
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-dib.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-dib.
.Sp
-If you use \fI\-\-no\-network\fR, then the environment variable \f(CW\*(C`DIB_OFFLINE\*(C'\fR is
-set to \f(CW1\fR, signaling the elements that they should use only cached
-resources when available. Note also that, unlike with \f(CW\*(C`diskimage\-builder\*(C'\fR
-where elements may still be able to access to the network even with
-\&\f(CW\*(C`DIB_OFFLINE=\*(C'\fR, under virt-dib network will not be accessible at all.
+If you use \fI\-\-no\-network\fR, then the environment variable \f(CW\*(C`DIB_OFFLINE\*(C'\fR is set to \f(CW1\fR, signaling the elements that they should use only cached resources when available. Note also that, unlike with \f(CW\*(C`diskimage\-builder\*(C'\fR where elements may still be able to access to the network even with \f(CW\*(C`DIB_OFFLINE=\*(C'\fR, under virt-dib network will not be accessible at all.
.IP "\fB\-\-name\fR \s-1NAME\s0" 4
.IX Item "--name NAME"
Set the name of the output image file. The default is \f(CW\*(C`image\*(C'\fR.
.Sp
-According to the chosen name, there will be the following in the current
-directory:
+According to the chosen name, there will be the following in the current directory:
.RS 4
.IP "\fI\f(CI$NAME\fI.ext\fR" 4
.IX Item "$NAME.ext"
-For each output format, a file named after the output image with the
-extension depending on the format; for example: \fI\f(CI$NAME\fI.qcow2\fR,
-\&\fI\f(CI$NAME\fI.raw\fR, etc.
+For each output format, a file named after the output image with the extension depending on the format; for example: \fI\f(CI$NAME\fI.qcow2\fR, \fI\f(CI$NAME\fI.raw\fR, etc.
.Sp
Not applicable in ramdisk mode, see \*(L"\s-1RAMDISK BUILDING\*(R"\s0.
.IP "\fI\f(CI$NAME\fI.d\fR" 4
.IX Item "$NAME.d"
-A directory containing any files created by the elements, for example
-\&\fIdib-manifests\fR directory (created by the \f(CW\*(C`manifests\*(C'\fR element), ramdisks
-and kernels in ramdisk mode, and so on.
+A directory containing any files created by the elements, for example \fIdib-manifests\fR directory (created by the \f(CW\*(C`manifests\*(C'\fR element), ramdisks and kernels in ramdisk mode, and so on.
.IP "\fI\f(CI$NAME\fI.ext.checksum\fR" 4
.IX Item "$NAME.ext.checksum"
-When \fI\-\-checksum\fR is specified, there will be files for each supported
-checksum type; for example: \fI\f(CI$NAME\fI.ext.md5\fR, \fI\f(CI$NAME\fI.ext.sha256\fR, etc.
+When \fI\-\-checksum\fR is specified, there will be files for each supported checksum type; for example: \fI\f(CI$NAME\fI.ext.md5\fR, \fI\f(CI$NAME\fI.ext.sha256\fR, etc.
.Sp
Not applicable in ramdisk mode, see \*(L"\s-1RAMDISK BUILDING\*(R"\s0.
.RE
.RE
.IP "\fB\-\-no\-delete\-on\-failure\fR" 4
.IX Item "--no-delete-on-failure"
-Don’t delete the output files on failure to build. You can use this to
-debug failures to run scripts.
+Don’t delete the output files on failure to build. You can use this to debug failures to run scripts.
.Sp
-The default is to delete the output files if virt-dib fails (or, for
-example, some script that it runs fails).
+The default is to delete the output files if virt-dib fails (or, for example, some script that it runs fails).
.IP "\fB\-\-python\fR \s-1PYTHON\s0" 4
.IX Item "--python PYTHON"
-Specify a different Python interpreter to use. Parts of
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR are implemented in Python, and thus an interpreter is
-needed.
+Specify a different Python interpreter to use. Parts of \f(CW\*(C`diskimage\-builder\*(C'\fR are implemented in Python, and thus an interpreter is needed.
.Sp
-\&\f(CW\*(C`PYTHON\*(C'\fR can either be an executable filename (e.g. \fIpython2\fR, which is
-then searched in \f(CW$PATH\fR), or a full path (e.g. \fI/usr/bin/python2\fR). If
-not specified, the default value is \fIpython\fR.
+\&\f(CW\*(C`PYTHON\*(C'\fR can either be an executable filename (e.g. \fIpython2\fR, which is then searched in \f(CW$PATH\fR), or a full path (e.g. \fI/usr/bin/python2\fR). If not specified, the default value is \fIpython\fR.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
Don’t print ordinary progress messages.
.IP "\fB\-\-qemu\-img\-options\fR option[,option,...]" 4
.IX Item "--qemu-img-options option[,option,...]"
-Pass \fI\-\-qemu\-img\-options\fR option(s) to the \fBqemu\-img\fR\|(1) command to
-fine-tune the output format. Options available depend on the output format
-(see \fI\-\-formats\fR) and the installed version of the qemu-img program.
+Pass \fI\-\-qemu\-img\-options\fR option(s) to the \fBqemu\-img\fR\|(1) command to fine-tune the output format. Options available depend on the output format (see \fI\-\-formats\fR) and the installed version of the qemu-img program.
.Sp
-You should use \fI\-\-qemu\-img\-options\fR at most once. To pass multiple
-options, separate them with commas, eg:
+You should use \fI\-\-qemu\-img\-options\fR at most once. To pass multiple options, separate them with commas, eg:
.Sp
.Vb 1
\& virt\-dib ... \-\-qemu\-img\-options cluster_size=512,preallocation=metadata ...
See \*(L"\s-1RAMDISK BUILDING\*(R"\s0.
.IP "\fB\-\-ramdisk\-element\fR \s-1NAME\s0" 4
.IX Item "--ramdisk-element NAME"
-Set the name for the additional element added in ramdisk building mode. The
-default is \f(CW\*(C`ramdisk\*(C'\fR.
+Set the name for the additional element added in ramdisk building mode. The default is \f(CW\*(C`ramdisk\*(C'\fR.
.Sp
See \*(L"\s-1RAMDISK BUILDING\*(R"\s0.
.IP "\fB\-\-root\-label\fR \s-1LABEL\s0" 4
.IX Item "--root-label LABEL"
Set the label for the root filesystem in the created image.
.Sp
-Please note that some filesystems have different restrictions on the length
-of their labels; for example, on \f(CW\*(C`ext2/3/4\*(C'\fR filesystems labels cannot be
-longer than 16 characters, while on \f(CW\*(C`xfs\*(C'\fR they have at most 12 characters.
+Please note that some filesystems have different restrictions on the length of their labels; for example, on \f(CW\*(C`ext2/3/4\*(C'\fR filesystems labels cannot be longer than 16 characters, while on \f(CW\*(C`xfs\*(C'\fR they have at most 12 characters.
.Sp
-The default depends on the actual filesystem for the root partition (see
-\&\fI\-\-fs\-type\fR): on \f(CW\*(C`xfs\*(C'\fR is \f(CW\*(C`img\-rootfs\*(C'\fR, while \f(CW\*(C`cloudimg\-rootfs\*(C'\fR on any
-other filesystem.
+The default depends on the actual filesystem for the root partition (see \fI\-\-fs\-type\fR): on \f(CW\*(C`xfs\*(C'\fR is \f(CW\*(C`img\-rootfs\*(C'\fR, while \f(CW\*(C`cloudimg\-rootfs\*(C'\fR on any other filesystem.
.IP "\fB\-\-size\fR \s-1SIZE\s0" 4
.IX Item "--size SIZE"
-Select the size of the output disk, where the size can be specified using
-common names such as \f(CW\*(C`32G\*(C'\fR (32 gigabytes) etc. The default size is \f(CW\*(C`5G\*(C'\fR.
+Select the size of the output disk, where the size can be specified using common names such as \f(CW\*(C`32G\*(C'\fR (32 gigabytes) etc. The default size is \f(CW\*(C`5G\*(C'\fR.
.Sp
-To specify size in bytes, the number must be followed by the lowercase
-letter \fIb\fR, eg: \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
+To specify size in bytes, the number must be followed by the lowercase letter \fIb\fR, eg: \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
.Sp
-See also \fBvirt\-resize\fR\|(1) for resizing partitions of an existing disk
-image.
+See also \fBvirt\-resize\fR\|(1) for resizing partitions of an existing disk image.
.IP "\fB\-\-skip\-base\fR" 4
.IX Item "--skip-base"
Skip the inclusion of the \f(CW\*(C`base\*(C'\fR element.
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.SH "環境変数"
.IX Header "環境変数"
-Unlike with \f(CW\*(C`diskimage\-builder\*(C'\fR, the environment of the host is \fBnot\fR
-inherited in the appliance when running most of the elements (i.e. all
-except the ones in the \f(CW\*(C`extra\-data.d\*(C'\fR phase).
+Unlike with \f(CW\*(C`diskimage\-builder\*(C'\fR, the environment of the host is \fBnot\fR inherited in the appliance when running most of the elements (i.e. all except the ones in the \f(CW\*(C`extra\-data.d\*(C'\fR phase).
.PP
-To set environment for the elements being run, it is necessary to tell
-virt-dib to use them, with the option \fI\-\-envvar\fR. Such option allows to
-selectively export environment variables when running the elements, and it
-is the preferred way to pass environment variables to the elements.
+To set environment for the elements being run, it is necessary to tell virt-dib to use them, with the option \fI\-\-envvar\fR. Such option allows to selectively export environment variables when running the elements, and it is the preferred way to pass environment variables to the elements.
.PP
-To recap: if you want the environment variable \f(CW\*(C`MYVAR\*(C'\fR (and its content) to
-be available to the elements, you can do either
+To recap: if you want the environment variable \f(CW\*(C`MYVAR\*(C'\fR (and its content) to be available to the elements, you can do either
.PP
.Vb 2
\& export MYVAR # whichever is its value
.Ve
.SH "HELPER DRIVE"
.IX Header "HELPER DRIVE"
-Virt-dib runs most of the element in its own appliance, and thus not on the
-host. Because of this, there is no possibility for elements to cache
-resources directly on the host.
+Virt-dib runs most of the element in its own appliance, and thus not on the host. Because of this, there is no possibility for elements to cache resources directly on the host.
.PP
-To solve this issue, virt-dib allows the usage of an helper drive where to
-store cached resources, like disk images, distribution packages, etc. While
-this means that there is a smaller space available for caching, at least it
-allows to limit the space on the host for caches, without assuming that
-elements will do that by themselves.
+To solve this issue, virt-dib allows the usage of an helper drive where to store cached resources, like disk images, distribution packages, etc. While this means that there is a smaller space available for caching, at least it allows to limit the space on the host for caches, without assuming that elements will do that by themselves.
.PP
-Currently this disk is either required to have a single partition on it, or
-the first partition on it will be used. A disk with the latter
-configuration can be easily created with \fBguestfish\fR\|(1) like the following:
+Currently this disk is either required to have a single partition on it, or the first partition on it will be used. A disk with the latter configuration can be easily created with \fBguestfish\fR\|(1) like the following:
.PP
.Vb 1
\& guestfish \-N filename.img=fs:ext4:10G exit
.Ve
.PP
-The above will create a disk image called \fIfilename.img\fR, 10G big, with a
-single partition of type ext4; see \*(L"\s-1PREPARED DISK IMAGES\*(R"\s0 in \fBguestfish\fR\|(1).
+The above will create a disk image called \fIfilename.img\fR, 10G big, with a single partition of type ext4; see \*(L"\s-1PREPARED DISK IMAGES\*(R"\s0 in \fBguestfish\fR\|(1).
.PP
-It is recommended for it to be ≥ 10G or even more, as elements will
-cache disk images, distribution packages, etc. As with any disk image, the
-helper disk can be easily resized using \fBvirt\-resize\fR\|(1) if more space in
-it is needed.
+It is recommended for it to be ≥ 10G or even more, as elements will cache disk images, distribution packages, etc. As with any disk image, the helper disk can be easily resized using \fBvirt\-resize\fR\|(1) if more space in it is needed.
.PP
-The drive can be accessed like any other disk image, for example using other
-tools of libguestfs such as \fBguestfish\fR\|(1):
+The drive can be accessed like any other disk image, for example using other tools of libguestfs such as \fBguestfish\fR\|(1):
.PP
.Vb 1
\& guestfish \-a filename.img \-m /dev/sda1
.Ve
.PP
-If no helper drive is specified with \fI\-\-drive\fR, all the resources cached
-during a virt-dib run will be discarded.
+If no helper drive is specified with \fI\-\-drive\fR, all the resources cached during a virt-dib run will be discarded.
.SS "\s-1RESOURCES INSIDE THE DRIVE\s0"
.IX Subsection "RESOURCES INSIDE THE DRIVE"
Inside the helper drive, it is possible to find the following resources:
.IP "\fI/home\fR" 4
.IX Item "/home"
-This directory is set as \f(CW\*(C`HOME\*(C'\fR environment variable during the build. It
-contains mostly the image cache (saved as \fI/home/.cache/image\-create\fR), and
-whichever other resource is cached in the home directory of the user running
-the various tools.
+This directory is set as \f(CW\*(C`HOME\*(C'\fR environment variable during the build. It contains mostly the image cache (saved as \fI/home/.cache/image\-create\fR), and whichever other resource is cached in the home directory of the user running the various tools.
.IP "\fI/virt\-dib\-*.log\fR" 4
.IX Item "/virt-dib-*.log"
-These are the logs of the elements being run within the libguestfs
-appliance, which means all the phases except \f(CW\*(C`extra\-data.d\*(C'\fR.
+These are the logs of the elements being run within the libguestfs appliance, which means all the phases except \f(CW\*(C`extra\-data.d\*(C'\fR.
.SH "RAMDISK BUILDING"
.IX Header "RAMDISK BUILDING"
-Virt-dib can emulate also \f(CW\*(C`ramdisk\-image\-create\*(C'\fR, which is a secondary
-operation mode of \f(CW\*(C`diskimage\-builder\*(C'\fR. Instead of being a different tool
-name, virt-dib provides easy access to this mode using the \fI\-\-ramdisk\fR
-switch.
+Virt-dib can emulate also \f(CW\*(C`ramdisk\-image\-create\*(C'\fR, which is a secondary operation mode of \f(CW\*(C`diskimage\-builder\*(C'\fR. Instead of being a different tool name, virt-dib provides easy access to this mode using the \fI\-\-ramdisk\fR switch.
.PP
In this mode:
.IP "\(bu" 4
\&\fI\f(CI$NAME\fI.d\fR (see \fI\-\-name\fR) will contain initrd, kernel, etc
.SH "TEMPORARY DIRECTORY"
.IX Header "TEMPORARY DIRECTORY"
-Virt-dib uses the standard temporary directory used by libguestfs, see
-\&\*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+Virt-dib uses the standard temporary directory used by libguestfs, see \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.PP
-By default this location is \fI/tmp\fR (default value for \f(CW\*(C`TMPDIR\*(C'\fR), which on
-some systems may be on a tmpfs filesystem, and thus defaulting to a maximum
-size of \fIhalf\fR of physical \s-1RAM.\s0 If virt-dib exceeds this, it may hang or
-exit early with an error. The solution is to point \f(CW\*(C`TMPDIR\*(C'\fR to a permanent
-location used as temporary location, for example:
+By default this location is \fI/tmp\fR (default value for \f(CW\*(C`TMPDIR\*(C'\fR), which on some systems may be on a tmpfs filesystem, and thus defaulting to a maximum size of \fIhalf\fR of physical \s-1RAM.\s0 If virt-dib exceeds this, it may hang or exit early with an error. The solution is to point \f(CW\*(C`TMPDIR\*(C'\fR to a permanent location used as temporary location, for example:
.PP
.Vb 3
\& mkdir local\-tmp
.Ve
.SH "EXTRA DEPENDENCIES"
.IX Header "EXTRA DEPENDENCIES"
-Because of virt-dib runs most of the elements in its own appliance, all the
-tools and libraries used by elements running outside the guest (typically
-\&\f(CW\*(C`root.d\*(C'\fR, \f(CW\*(C`block\-device.d\*(C'\fR, and \f(CW\*(C`cleanup.d\*(C'\fR) need to be present in the
-appliance as well. In case they are not, scripts will fail typically with a
-\&\f(CW\*(C`command not found\*(C'\fR error.
+Because of virt-dib runs most of the elements in its own appliance, all the tools and libraries used by elements running outside the guest (typically \f(CW\*(C`root.d\*(C'\fR, \f(CW\*(C`block\-device.d\*(C'\fR, and \f(CW\*(C`cleanup.d\*(C'\fR) need to be present in the appliance as well. In case they are not, scripts will fail typically with a \f(CW\*(C`command not found\*(C'\fR error.
.PP
-For tools and libraries packaged by the distribution, the easy solution is
-to tell libguestfs to include additional packages in the appliance. This is
-doable by e.g. creating a new file with the additional packages:
+For tools and libraries packaged by the distribution, the easy solution is to tell libguestfs to include additional packages in the appliance. This is doable by e.g. creating a new file with the additional packages:
.PP
.Vb 1
\& # echo wget > /usr/lib64/guestfs/supermin.d/dib\-my\-extra
.Ve
.PP
-The actual path to the \fIsupermin.d\fR directory depends on the distribution;
-additional files can list more packages, each in its own line. For more
-details, see \fBsupermin\fR\|(1).
+The actual path to the \fIsupermin.d\fR directory depends on the distribution; additional files can list more packages, each in its own line. For more details, see \fBsupermin\fR\|(1).
.SH "COMPARISON WITH DISKIMAGE-BUILDER"
.IX Header "COMPARISON WITH DISKIMAGE-BUILDER"
-Virt-dib is intended as safe replacement for \f(CW\*(C`diskimage\-builder\*(C'\fR and its
-\&\f(CW\*(C`ramdisk\-image\-create\*(C'\fR mode; the user-notable differences consist in:
+Virt-dib is intended as safe replacement for \f(CW\*(C`diskimage\-builder\*(C'\fR and its \f(CW\*(C`ramdisk\-image\-create\*(C'\fR mode; the user-notable differences consist in:
.IP "\(bu" 4
-the command line arguments; some of the arguments are the same as available
-in \f(CW\*(C`diskimage\-builder\*(C'\fR, while some have different names:
+the command line arguments; some of the arguments are the same as available in \f(CW\*(C`diskimage\-builder\*(C'\fR, while some have different names:
.Sp
.Vb 12
\& disk\-image\-create virt\-dib
.IP "\(bu" 4
the location of non-image output files (like ramdisks and kernels)
.IP "\(bu" 4
-the way some of the cached resources are saved: using an helper drive, not
-directly on the disk where virt-dib is run
+the way some of the cached resources are saved: using an helper drive, not directly on the disk where virt-dib is run
.IP "\(bu" 4
-the need to specify a target size for the output disk, as opposed to
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR calculating an optimal one
+the need to specify a target size for the output disk, as opposed to \f(CW\*(C`diskimage\-builder\*(C'\fR calculating an optimal one
.IP "\(bu" 4
the handling of environment variables, see \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0.
.Sp
-Furthermore, other than the libguestfs own environment variables (see
-\&\*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3)), virt-dib does not read any other
-environment variable: this means that all the options and behaviour changes
-are specified solely using command line arguments
+Furthermore, other than the libguestfs own environment variables (see \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3)), virt-dib does not read any other environment variable: this means that all the options and behaviour changes are specified solely using command line arguments
.IP "\(bu" 4
-extra tools needed on some out-of-chroot phases need to be available in the
-appliance, see \*(L"\s-1EXTRA DEPENDENCIES\*(R"\s0.
+extra tools needed on some out-of-chroot phases need to be available in the appliance, see \*(L"\s-1EXTRA DEPENDENCIES\*(R"\s0.
.PP
-Elements themselves should notice no difference in they way they are run;
-behaviour differences may due to wrong assumptions in elements, or not
-correct virt-dib emulation.
+Elements themselves should notice no difference in they way they are run; behaviour differences may due to wrong assumptions in elements, or not correct virt-dib emulation.
.PP
Known issues at the moment:
.IP "\(bu" 4
(none)
.SH "マシン可読な出力"
.IX Header "マシン可読な出力"
-The \fI\-\-machine\-readable\fR option can be used to make the output more machine
-friendly, which is useful when calling virt-dib from other programs, GUIs
-etc.
+The \fI\-\-machine\-readable\fR option can be used to make the output more machine friendly, which is useful when calling virt-dib from other programs, GUIs etc.
.PP
-Use the option on its own to query the capabilities of the virt-dib binary.
-Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-dib binary. Typical output looks like this:
.PP
.Vb 6
\& $ virt\-dib \-\-machine\-readable
\& output:vhd
.Ve
.PP
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
.PP
-The \f(CW\*(C`output:\*(C'\fR features refer to the output formats (\fI\-\-formats\fR command
-line option) supported by this binary.
+The \f(CW\*(C`output:\*(C'\fR features refer to the output formats (\fI\-\-formats\fR command line option) supported by this binary.
.PP
-It is possible to specify a format string for controlling the output; see
-\&\*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
+It is possible to specify a format string for controlling the output; see \*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "TESTING"
.IX Header "TESTING"
-Virt-dib has been tested with \f(CW\*(C`diskimage\-builder\*(C'\fR (and its elements) ≥
-0.1.43; from time to time also with \f(CW\*(C`tripleo\-image\-elements\*(C'\fR and
-\&\f(CW\*(C`sahara\-image\-elements\*(C'\fR.
+Virt-dib has been tested with \f(CW\*(C`diskimage\-builder\*(C'\fR (and its elements) ≥ 0.1.43; from time to time also with \f(CW\*(C`tripleo\-image\-elements\*(C'\fR and \f(CW\*(C`sahara\-image\-elements\*(C'\fR.
.PP
Previous versions may work, but it is not guaranteed.
.SH "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-resize\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Pino Toscano (\f(CW\*(C`ptoscano at redhat dot com\*(C'\fR)
=head1 説明
-Virt-dib is a tool for using the elements of C<diskimage-builder> to build a
-new disk image, generate new ramdisks, etc.
+Virt-dib is a tool for using the elements of C<diskimage-builder> to build a new disk image, generate new ramdisks, etc.
-Virt-dib is intended as safe replacement for C<diskimage-builder> and its
-C<ramdisk-image-create> mode, see L</COMPARISON WITH DISKIMAGE-BUILDER> for
-a quick comparison with usage of C<diskimage-builder>.
+Virt-dib is intended as safe replacement for C<diskimage-builder> and its C<ramdisk-image-create> mode, see L</COMPARISON WITH DISKIMAGE-BUILDER> for a quick comparison with usage of C<diskimage-builder>.
-C<diskimage-builder> is part of the TripleO OpenStack project:
-L<https://wiki.openstack.org/wiki/TripleO>.
+C<diskimage-builder> is part of the TripleO OpenStack project: L<https://wiki.openstack.org/wiki/TripleO>.
=head1 例
--name debian-jessie \
debian vm
-This builds a Debian Jessie (8.x) disk image, suitable for running as
-virtual machine, saved as F<debian-jessie.qcow2>.
+This builds a Debian Jessie (8.x) disk image, suitable for running as virtual machine, saved as F<debian-jessie.qcow2>.
=head2 Build ramdisks
--name ramdisk \
ubuntu deploy-ironic
-This builds a ramdisk for the Ironic OpenStack component based on the Ubuntu
-distribution.
+This builds a ramdisk for the Ironic OpenStack component based on the Ubuntu distribution.
=head1 オプション
=item B<-B> PATH
-Set the path to the library directory of C<diskimage-builder>. This is
-usually the F<lib> subdirectory in the sources and when installed, and
-F</usr/share/diskimage-builder/lib> when installed in F</usr>.
+Set the path to the library directory of C<diskimage-builder>. This is usually the F<lib> subdirectory in the sources and when installed, and F</usr/share/diskimage-builder/lib> when installed in F</usr>.
-This parameter is B<mandatory>, as virt-dib needs to provide it for the
-elements (as some of them might use scripts in it). Virt-dib itself does
-not make use of the library directory.
+This parameter is B<mandatory>, as virt-dib needs to provide it for the elements (as some of them might use scripts in it). Virt-dib itself does not make use of the library directory.
=item B<--arch> ARCHITECTURE
-Use the specified architecture for the output image. The default value is
-the same as the host running virt-dib.
+Use the specified architecture for the output image. The default value is the same as the host running virt-dib.
-Right now this option does nothing more than setting the C<ARCH> environment
-variable for the elements, and it’s up to them to produce an image for the
-requested architecture.
+Right now this option does nothing more than setting the C<ARCH> environment variable for the elements, and it’s up to them to produce an image for the requested architecture.
=item B<--checksum>
-Generate checksum files for the generated image. The supported checksums
-are MD5, and SHA256.
+Generate checksum files for the generated image. The supported checksums are MD5, and SHA256.
=item B<--colors>
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<--debug> LEVEL
-Set the debug level to C<LEVEL>, which is a non-negative integer number.
-The default is C<0>.
+Set the debug level to C<LEVEL>, which is a non-negative integer number. The default is C<0>.
-This debug level is different than what I<-x> and I<-v> set, and it
-increases the debugging information printed out. Specifically, this sets
-the C<DIB_DEBUG_TRACE>, and any value E<gt> C<0> enables tracing in the
-scripts executed.
+This debug level is different than what I<-x> and I<-v> set, and it increases the debugging information printed out. Specifically, this sets the C<DIB_DEBUG_TRACE>, and any value E<gt> C<0> enables tracing in the scripts executed.
=item B<--docker-target> TARGET
Set the repository and tag for docker.
-This is used only when the formats include C<docker>, and it is required in
-that case.
+This is used only when the formats include C<docker>, and it is required in that case.
=item B<--drive> DISK
-Add the specified disk to be used as helper drive where to cache files of
-the elements, like disk images, distribution packages, etc.
+Add the specified disk to be used as helper drive where to cache files of the elements, like disk images, distribution packages, etc.
See L</HELPER DRIVE>.
=item B<--drive-format> qcow2
-Specify the format of the helper drive. If this flag is not given then it
-is auto-detected from the drive itself.
+Specify the format of the helper drive. If this flag is not given then it is auto-detected from the drive itself.
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
This option is used only if I<--drive> is specified.
=item B<--element-path> PATH
-Add a new path with elements. Paths are used in the same order as the I<-p>
-parameters appear, so a path specified first is looked first, and so on.
+Add a new path with elements. Paths are used in the same order as the I<-p> parameters appear, so a path specified first is looked first, and so on.
-Obviously, it is recommended to add the path to the own elements of
-C<diskimage-builder>, as most of the other elements will rely on them.
+Obviously, it is recommended to add the path to the own elements of C<diskimage-builder>, as most of the other elements will rely on them.
=item B<--extra-packages> PACKAGE,...
Install additional packages in the image being built.
-This relies on the C<install-packages> binary provided by the package
-management elements.
+This relies on the C<install-packages> binary provided by the package management elements.
-This option can be specified multiple times, each time with multiple
-packages separated by comma.
+This option can be specified multiple times, each time with multiple packages separated by comma.
=item B<--envvar> VARIABLE
Carry or set an environment variable for the elements.
-See L</ENVIRONMENT VARIABLES> below for more information on the interaction
-and usage of environment variables.
+See L</ENVIRONMENT VARIABLES> below for more information on the interaction and usage of environment variables.
This option can be used in two ways:
=item B<--envvar> VARIABLE
-Carry the environment variable C<VARIABLE>. If it is not set, nothing is
-exported to the elements.
+Carry the environment variable C<VARIABLE>. If it is not set, nothing is exported to the elements.
=item B<--envvar> VARIABLE=VALUE
-Set the environment variable C<VARIABLE> with value C<VALUE> for the
-elements, regardless whether an environment variable with the same name
-exists.
+Set the environment variable C<VARIABLE> with value C<VALUE> for the elements, regardless whether an environment variable with the same name exists.
-This can be useful to pass environment variable without exporting them in
-the environment where virt-dib runs.
+This can be useful to pass environment variable without exporting them in the environment where virt-dib runs.
=back
Ignore any element script named C<SCRIPT>, whichever element it is in.
-This can be useful in case some script does not run well with virt-dib, for
-example when they really need C<diskimage-builder>'s environment.
+This can be useful in case some script does not run well with virt-dib, for example when they really need C<diskimage-builder>'s environment.
=item B<--formats> FORMAT,...
=item C<docker>
-Import the image to docker, running B<docker import>. The target for the
-image B<must> be specified using I<--docker-target>.
+Import the image to docker, running B<docker import>. The target for the image B<must> be specified using I<--docker-target>.
-Please note this operation usually requires the docker service to be
-enabled, otherwise it will fail. Furthermore, B<docker> is run using
-L<sudo(8)>, so make sure the user has the permissions to run at least
-B<docker>.
+Please note this operation usually requires the docker service to be enabled, otherwise it will fail. Furthermore, B<docker> is run using L<sudo(8)>, so make sure the user has the permissions to run at least B<docker>.
=item C<qcow2> (enabled by default)
=item C<squashfs>
-An squashfs filesystem, compressed with XZ. This output format requires the
-C<squashfs> feature; see also L<guestfs(3)/AVAILABILITY>.
+An squashfs filesystem, compressed with XZ. This output format requires the C<squashfs> feature; see also L<guestfs(3)/AVAILABILITY>.
=item C<tar>
=item C<vhd>
-C<Virtual Hard Disk> disk image. This output format requires the
-C<vhd-util> tool.
+C<Virtual Hard Disk> disk image. This output format requires the C<vhd-util> tool.
-Please note that the version of C<vhd-util> tool needs to be patched to
-support the C<convert> subcommand, and to be bootable. The patch is
-available here:
-L<https://github.com/emonty/vhd-util/blob/master/debian/patches/citrix>.
+Please note that the version of C<vhd-util> tool needs to be patched to support the C<convert> subcommand, and to be bootable. The patch is available here: L<https://github.com/emonty/vhd-util/blob/master/debian/patches/citrix>.
=back
=item B<--fs-type> FILESYSTEM
-Set the filesystem type to use for the root filesystem. The default is
-C<ext4>.
+Set the filesystem type to use for the root filesystem. The default is C<ext4>.
See also L<guestfs(3)/guestfs_filesystem_available>.
=item B<--image-cache> DIRECTORY
-Set the path in the host where cache the resources used by the elements of
-the C<extra-data.d> phase. The default is F<~/.cache/image-create>.
+Set the path in the host where cache the resources used by the elements of the C<extra-data.d> phase. The default is F<~/.cache/image-create>.
-Please note that most of the resources fetched in phases other than
-C<extra-data.d> will be cached in the helper drive specified with
-I<--drive>; see also L</HELPER DRIVE>.
+Please note that most of the resources fetched in phases other than C<extra-data.d> will be cached in the helper drive specified with I<--drive>; see also L</HELPER DRIVE>.
=item B<--install-type> TYPE
=item B<--memsize> MB
-Change the amount of memory allocated to the appliance. Increase this if you
-find that the virt-dib execution runs out of memory.
+Change the amount of memory allocated to the appliance. Increase this if you find that the virt-dib execution runs out of memory.
The default can be found with this command:
=item B<--mkfs-options> C<OPTION STRING>
-Add the specified options to L<mkfs(1)>, to be able to fine-tune the root
-filesystem creation; the options are passed to the driver of L<mfks(1)>, and
-not to L<mfks(1)> itself. Note that I<--fs-type> is used to change the
-filesystem type.
+Add the specified options to L<mkfs(1)>, to be able to fine-tune the root filesystem creation; the options are passed to the driver of L<mfks(1)>, and not to L<mfks(1)> itself. Note that I<--fs-type> is used to change the filesystem type.
-You should use I<--mkfs-options> at most once. To pass multiple options,
-separate them with space, eg:
+You should use I<--mkfs-options> at most once. To pass multiple options, separate them with space, eg:
virt-dib ... --mkfs-options '-O someopt -I foo'
Enabled is the default. Use I<--no-network> to disable access.
-The network only allows outgoing connections and has other minor
-limitations. See L<virt-rescue(1)/NETWORK>.
+The network only allows outgoing connections and has other minor limitations. See L<virt-rescue(1)/NETWORK>.
-This does not affect whether the guest can access the network once it has
-been booted, because that is controlled by your hypervisor or cloud
-environment and has nothing to do with virt-dib.
+This does not affect whether the guest can access the network once it has been booted, because that is controlled by your hypervisor or cloud environment and has nothing to do with virt-dib.
-If you use I<--no-network>, then the environment variable C<DIB_OFFLINE> is
-set to C<1>, signaling the elements that they should use only cached
-resources when available. Note also that, unlike with C<diskimage-builder>
-where elements may still be able to access to the network even with
-C<DIB_OFFLINE=>, under virt-dib network will not be accessible at all.
+If you use I<--no-network>, then the environment variable C<DIB_OFFLINE> is set to C<1>, signaling the elements that they should use only cached resources when available. Note also that, unlike with C<diskimage-builder> where elements may still be able to access to the network even with C<DIB_OFFLINE=>, under virt-dib network will not be accessible at all.
=item B<--name> NAME
Set the name of the output image file. The default is C<image>.
-According to the chosen name, there will be the following in the current
-directory:
+According to the chosen name, there will be the following in the current directory:
=over 4
=item F<$NAME.ext>
-For each output format, a file named after the output image with the
-extension depending on the format; for example: F<$NAME.qcow2>,
-F<$NAME.raw>, etc.
+For each output format, a file named after the output image with the extension depending on the format; for example: F<$NAME.qcow2>, F<$NAME.raw>, etc.
Not applicable in ramdisk mode, see L</RAMDISK BUILDING>.
=item F<$NAME.d>
-A directory containing any files created by the elements, for example
-F<dib-manifests> directory (created by the C<manifests> element), ramdisks
-and kernels in ramdisk mode, and so on.
+A directory containing any files created by the elements, for example F<dib-manifests> directory (created by the C<manifests> element), ramdisks and kernels in ramdisk mode, and so on.
=item F<$NAME.ext.checksum>
-When I<--checksum> is specified, there will be files for each supported
-checksum type; for example: F<$NAME.ext.md5>, F<$NAME.ext.sha256>, etc.
+When I<--checksum> is specified, there will be files for each supported checksum type; for example: F<$NAME.ext.md5>, F<$NAME.ext.sha256>, etc.
Not applicable in ramdisk mode, see L</RAMDISK BUILDING>.
=item B<--no-delete-on-failure>
-Don’t delete the output files on failure to build. You can use this to
-debug failures to run scripts.
+Don’t delete the output files on failure to build. You can use this to debug failures to run scripts.
-The default is to delete the output files if virt-dib fails (or, for
-example, some script that it runs fails).
+The default is to delete the output files if virt-dib fails (or, for example, some script that it runs fails).
=item B<--python> PYTHON
-Specify a different Python interpreter to use. Parts of
-C<diskimage-builder> are implemented in Python, and thus an interpreter is
-needed.
+Specify a different Python interpreter to use. Parts of C<diskimage-builder> are implemented in Python, and thus an interpreter is needed.
-C<PYTHON> can either be an executable filename (e.g. F<python2>, which is
-then searched in C<$PATH>), or a full path (e.g. F</usr/bin/python2>). If
-not specified, the default value is F<python>.
+C<PYTHON> can either be an executable filename (e.g. F<python2>, which is then searched in C<$PATH>), or a full path (e.g. F</usr/bin/python2>). If not specified, the default value is F<python>.
=item B<-q>
=item B<--qemu-img-options> option[,option,...]
-Pass I<--qemu-img-options> option(s) to the L<qemu-img(1)> command to
-fine-tune the output format. Options available depend on the output format
-(see I<--formats>) and the installed version of the qemu-img program.
+Pass I<--qemu-img-options> option(s) to the L<qemu-img(1)> command to fine-tune the output format. Options available depend on the output format (see I<--formats>) and the installed version of the qemu-img program.
-You should use I<--qemu-img-options> at most once. To pass multiple
-options, separate them with commas, eg:
+You should use I<--qemu-img-options> at most once. To pass multiple options, separate them with commas, eg:
virt-dib ... --qemu-img-options cluster_size=512,preallocation=metadata ...
=item B<--ramdisk-element> NAME
-Set the name for the additional element added in ramdisk building mode. The
-default is C<ramdisk>.
+Set the name for the additional element added in ramdisk building mode. The default is C<ramdisk>.
See L</RAMDISK BUILDING>.
Set the label for the root filesystem in the created image.
-Please note that some filesystems have different restrictions on the length
-of their labels; for example, on C<ext2/3/4> filesystems labels cannot be
-longer than 16 characters, while on C<xfs> they have at most 12 characters.
+Please note that some filesystems have different restrictions on the length of their labels; for example, on C<ext2/3/4> filesystems labels cannot be longer than 16 characters, while on C<xfs> they have at most 12 characters.
-The default depends on the actual filesystem for the root partition (see
-I<--fs-type>): on C<xfs> is C<img-rootfs>, while C<cloudimg-rootfs> on any
-other filesystem.
+The default depends on the actual filesystem for the root partition (see I<--fs-type>): on C<xfs> is C<img-rootfs>, while C<cloudimg-rootfs> on any other filesystem.
=item B<--size> SIZE
-Select the size of the output disk, where the size can be specified using
-common names such as C<32G> (32 gigabytes) etc. The default size is C<5G>.
+Select the size of the output disk, where the size can be specified using common names such as C<32G> (32 gigabytes) etc. The default size is C<5G>.
-To specify size in bytes, the number must be followed by the lowercase
-letter I<b>, eg: S<C<--size 10737418240b>>.
+To specify size in bytes, the number must be followed by the lowercase letter I<b>, eg: S<C<--size 10737418240b>>.
-See also L<virt-resize(1)> for resizing partitions of an existing disk
-image.
+See also L<virt-resize(1)> for resizing partitions of an existing disk image.
=item B<--skip-base>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 環境変数
-Unlike with C<diskimage-builder>, the environment of the host is B<not>
-inherited in the appliance when running most of the elements (i.e. all
-except the ones in the C<extra-data.d> phase).
+Unlike with C<diskimage-builder>, the environment of the host is B<not> inherited in the appliance when running most of the elements (i.e. all except the ones in the C<extra-data.d> phase).
-To set environment for the elements being run, it is necessary to tell
-virt-dib to use them, with the option I<--envvar>. Such option allows to
-selectively export environment variables when running the elements, and it
-is the preferred way to pass environment variables to the elements.
+To set environment for the elements being run, it is necessary to tell virt-dib to use them, with the option I<--envvar>. Such option allows to selectively export environment variables when running the elements, and it is the preferred way to pass environment variables to the elements.
-To recap: if you want the environment variable C<MYVAR> (and its content) to
-be available to the elements, you can do either
+To recap: if you want the environment variable C<MYVAR> (and its content) to be available to the elements, you can do either
export MYVAR # whichever is its value
virt-dib ... --envvar MYVAR ...
=head1 HELPER DRIVE
-Virt-dib runs most of the element in its own appliance, and thus not on the
-host. Because of this, there is no possibility for elements to cache
-resources directly on the host.
+Virt-dib runs most of the element in its own appliance, and thus not on the host. Because of this, there is no possibility for elements to cache resources directly on the host.
-To solve this issue, virt-dib allows the usage of an helper drive where to
-store cached resources, like disk images, distribution packages, etc. While
-this means that there is a smaller space available for caching, at least it
-allows to limit the space on the host for caches, without assuming that
-elements will do that by themselves.
+To solve this issue, virt-dib allows the usage of an helper drive where to store cached resources, like disk images, distribution packages, etc. While this means that there is a smaller space available for caching, at least it allows to limit the space on the host for caches, without assuming that elements will do that by themselves.
-Currently this disk is either required to have a single partition on it, or
-the first partition on it will be used. A disk with the latter
-configuration can be easily created with L<guestfish(1)> like the following:
+Currently this disk is either required to have a single partition on it, or the first partition on it will be used. A disk with the latter configuration can be easily created with L<guestfish(1)> like the following:
guestfish -N filename.img=fs:ext4:10G exit
-The above will create a disk image called F<filename.img>, 10G big, with a
-single partition of type ext4; see L<guestfish(1)/PREPARED DISK IMAGES>.
+The above will create a disk image called F<filename.img>, 10G big, with a single partition of type ext4; see L<guestfish(1)/PREPARED DISK IMAGES>.
-It is recommended for it to be E<ge> 10G or even more, as elements will
-cache disk images, distribution packages, etc. As with any disk image, the
-helper disk can be easily resized using L<virt-resize(1)> if more space in
-it is needed.
+It is recommended for it to be E<ge> 10G or even more, as elements will cache disk images, distribution packages, etc. As with any disk image, the helper disk can be easily resized using L<virt-resize(1)> if more space in it is needed.
-The drive can be accessed like any other disk image, for example using other
-tools of libguestfs such as L<guestfish(1)>:
+The drive can be accessed like any other disk image, for example using other tools of libguestfs such as L<guestfish(1)>:
guestfish -a filename.img -m /dev/sda1
-If no helper drive is specified with I<--drive>, all the resources cached
-during a virt-dib run will be discarded.
+If no helper drive is specified with I<--drive>, all the resources cached during a virt-dib run will be discarded.
=head2 RESOURCES INSIDE THE DRIVE
=item F</home>
-This directory is set as C<HOME> environment variable during the build. It
-contains mostly the image cache (saved as F</home/.cache/image-create>), and
-whichever other resource is cached in the home directory of the user running
-the various tools.
+This directory is set as C<HOME> environment variable during the build. It contains mostly the image cache (saved as F</home/.cache/image-create>), and whichever other resource is cached in the home directory of the user running the various tools.
=item F</virt-dib-*.log>
-These are the logs of the elements being run within the libguestfs
-appliance, which means all the phases except C<extra-data.d>.
+These are the logs of the elements being run within the libguestfs appliance, which means all the phases except C<extra-data.d>.
=back
=head1 RAMDISK BUILDING
-Virt-dib can emulate also C<ramdisk-image-create>, which is a secondary
-operation mode of C<diskimage-builder>. Instead of being a different tool
-name, virt-dib provides easy access to this mode using the I<--ramdisk>
-switch.
+Virt-dib can emulate also C<ramdisk-image-create>, which is a secondary operation mode of C<diskimage-builder>. Instead of being a different tool name, virt-dib provides easy access to this mode using the I<--ramdisk> switch.
In this mode:
=head1 TEMPORARY DIRECTORY
-Virt-dib uses the standard temporary directory used by libguestfs, see
-L<guestfs(3)/ENVIRONMENT VARIABLES>.
+Virt-dib uses the standard temporary directory used by libguestfs, see L<guestfs(3)/ENVIRONMENT VARIABLES>.
-By default this location is F</tmp> (default value for C<TMPDIR>), which on
-some systems may be on a tmpfs filesystem, and thus defaulting to a maximum
-size of I<half> of physical RAM. If virt-dib exceeds this, it may hang or
-exit early with an error. The solution is to point C<TMPDIR> to a permanent
-location used as temporary location, for example:
+By default this location is F</tmp> (default value for C<TMPDIR>), which on some systems may be on a tmpfs filesystem, and thus defaulting to a maximum size of I<half> of physical RAM. If virt-dib exceeds this, it may hang or exit early with an error. The solution is to point C<TMPDIR> to a permanent location used as temporary location, for example:
mkdir local-tmp
env TMPDIR=$PWD/local-tmp virt-dib ...
=head1 EXTRA DEPENDENCIES
-Because of virt-dib runs most of the elements in its own appliance, all the
-tools and libraries used by elements running outside the guest (typically
-C<root.d>, C<block-device.d>, and C<cleanup.d>) need to be present in the
-appliance as well. In case they are not, scripts will fail typically with a
-C<command not found> error.
+Because of virt-dib runs most of the elements in its own appliance, all the tools and libraries used by elements running outside the guest (typically C<root.d>, C<block-device.d>, and C<cleanup.d>) need to be present in the appliance as well. In case they are not, scripts will fail typically with a C<command not found> error.
-For tools and libraries packaged by the distribution, the easy solution is
-to tell libguestfs to include additional packages in the appliance. This is
-doable by e.g. creating a new file with the additional packages:
+For tools and libraries packaged by the distribution, the easy solution is to tell libguestfs to include additional packages in the appliance. This is doable by e.g. creating a new file with the additional packages:
# echo wget > /usr/lib64/guestfs/supermin.d/dib-my-extra
-The actual path to the F<supermin.d> directory depends on the distribution;
-additional files can list more packages, each in its own line. For more
-details, see L<supermin(1)>.
+The actual path to the F<supermin.d> directory depends on the distribution; additional files can list more packages, each in its own line. For more details, see L<supermin(1)>.
=head1 COMPARISON WITH DISKIMAGE-BUILDER
-Virt-dib is intended as safe replacement for C<diskimage-builder> and its
-C<ramdisk-image-create> mode; the user-notable differences consist in:
+Virt-dib is intended as safe replacement for C<diskimage-builder> and its C<ramdisk-image-create> mode; the user-notable differences consist in:
=over 4
=item
-the command line arguments; some of the arguments are the same as available
-in C<diskimage-builder>, while some have different names:
+the command line arguments; some of the arguments are the same as available in C<diskimage-builder>, while some have different names:
disk-image-create virt-dib
----------------- --------
=item
-the way some of the cached resources are saved: using an helper drive, not
-directly on the disk where virt-dib is run
+the way some of the cached resources are saved: using an helper drive, not directly on the disk where virt-dib is run
=item
-the need to specify a target size for the output disk, as opposed to
-C<diskimage-builder> calculating an optimal one
+the need to specify a target size for the output disk, as opposed to C<diskimage-builder> calculating an optimal one
=item
the handling of environment variables, see L</ENVIRONMENT VARIABLES>.
-Furthermore, other than the libguestfs own environment variables (see
-L<guestfs(3)/ENVIRONMENT VARIABLES>), virt-dib does not read any other
-environment variable: this means that all the options and behaviour changes
-are specified solely using command line arguments
+Furthermore, other than the libguestfs own environment variables (see L<guestfs(3)/ENVIRONMENT VARIABLES>), virt-dib does not read any other environment variable: this means that all the options and behaviour changes are specified solely using command line arguments
=item
-extra tools needed on some out-of-chroot phases need to be available in the
-appliance, see L</EXTRA DEPENDENCIES>.
+extra tools needed on some out-of-chroot phases need to be available in the appliance, see L</EXTRA DEPENDENCIES>.
=back
-Elements themselves should notice no difference in they way they are run;
-behaviour differences may due to wrong assumptions in elements, or not
-correct virt-dib emulation.
+Elements themselves should notice no difference in they way they are run; behaviour differences may due to wrong assumptions in elements, or not correct virt-dib emulation.
Known issues at the moment:
=head1 マシン可読な出力
-The I<--machine-readable> option can be used to make the output more machine
-friendly, which is useful when calling virt-dib from other programs, GUIs
-etc.
+The I<--machine-readable> option can be used to make the output more machine friendly, which is useful when calling virt-dib from other programs, GUIs etc.
-Use the option on its own to query the capabilities of the virt-dib binary.
-Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-dib binary. Typical output looks like this:
$ virt-dib --machine-readable
virt-dib
output:raw
output:vhd
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-The C<output:> features refer to the output formats (I<--formats> command
-line option) supported by this binary.
+The C<output:> features refer to the output formats (I<--formats> command line option) supported by this binary.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 TESTING
-Virt-dib has been tested with C<diskimage-builder> (and its elements) E<ge>
-0.1.43; from time to time also with C<tripleo-image-elements> and
-C<sahara-image-elements>.
+Virt-dib has been tested with C<diskimage-builder> (and its elements) E<ge> 0.1.43; from time to time also with C<tripleo-image-elements> and C<sahara-image-elements>.
Previous versions may work, but it is not guaranteed.
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-resize(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-diff 1"
-.TH virt-diff 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-diff 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\f(CW\*(C`virt\-diff\*(C'\fR lists the differences between files in two virtual machines or
-disk images. The usual use case is to show the changes in a \s-1VM\s0 after it has
-been running for a while, by taking a snapshot, running the \s-1VM,\s0 and then
-using this tool to show what changed between the new \s-1VM\s0 state and the old
-snapshot.
+\&\f(CW\*(C`virt\-diff\*(C'\fR lists the differences between files in two virtual machines or disk images. The usual use case is to show the changes in a \s-1VM\s0 after it has been running for a while, by taking a snapshot, running the \s-1VM,\s0 and then using this tool to show what changed between the new \s-1VM\s0 state and the old snapshot.
.PP
-This tool will find differences in filenames, file sizes, checksums,
-extended attributes, file content and more from a virtual machine or disk
-image. However it \fBdoes not\fR look at the boot loader, unused space between
-partitions or within filesystems, \*(L"hidden\*(R" sectors and so on. In other
-words, it is not a security or forensics tool.
+This tool will find differences in filenames, file sizes, checksums, extended attributes, file content and more from a virtual machine or disk image. However it \fBdoes not\fR look at the boot loader, unused space between partitions or within filesystems, \*(L"hidden\*(R" sectors and so on. In other words, it is not a security or forensics tool.
.PP
-To specify two guests, you have to use the \fI\-a\fR or \fI\-d\fR option(s) for the
-first guest, and the \fI\-A\fR or \fI\-D\fR option(s) for the second guest. The
-common case is:
+To specify two guests, you have to use the \fI\-a\fR or \fI\-d\fR option(s) for the first guest, and the \fI\-A\fR or \fI\-D\fR option(s) for the second guest. The common case is:
.PP
.Vb 1
\& virt\-diff \-a old.img \-A new.img
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from the first virtual machine. If
-the virtual machine has multiple block devices, you must supply all of them
-with separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from the first virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a\fR \s-1URI\s0" 4
Same as \fI\-\-extra\-stats\fR \fI\-\-times\fR \fI\-\-uids\fR \fI\-\-xattrs\fR.
.IP "\fB\-\-atime\fR" 4
.IX Item "--atime"
-The default is to ignore changes in file access times, since those are
-unlikely to be interesting. Using this flag shows atime differences as
-well.
+The default is to ignore changes in file access times, since those are unlikely to be interesting. Using this flag shows atime differences as well.
.IP "\fB\-A\fR file" 4
.IX Item "-A file"
.PD 0
.IP "\fB\-\-checksum=crc|md5|sha1|sha224|sha256|sha384|sha512\fR" 4
.IX Item "--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512"
.PD
-Use a checksum over file contents to detect when regular files have changed
-content.
+Use a checksum over file contents to detect when regular files have changed content.
.Sp
-With no argument, this defaults to using \fImd5\fR. Using an argument, you can
-select the checksum type to use. If the flag is omitted then file times and
-size are used to determine if a file has changed.
+With no argument, this defaults to using \fImd5\fR. Using an argument, you can select the checksum type to use. If the flag is omitted then file times and size are used to determine if a file has changed.
.IP "\fB\-c\fR \s-1URI\s0" 4
.IX Item "-c URI"
.PD 0
ゲストのブロックデバイスを直接指定していると（(\fI\-a\fR)）、libvirt は何も使用されません。
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Write out the results in \s-1CSV\s0 format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE
-ABOUT CSV FORMAT\*(R"\s0 below.
+Write out the results in \s-1CSV\s0 format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE ABOUT CSV FORMAT\*(R"\s0 below.
.IP "\fB\-\-dir\-links\fR" 4
.IX Item "--dir-links"
-The default is to ignore changes in the number of links in directory
-entries, since those are unlikely to be interesting. Using this flag shows
-changes to the nlink field of directories.
+The default is to ignore changes in the number of links in directory entries, since those are unlikely to be interesting. Using this flag shows changes to the nlink field of directories.
.IP "\fB\-\-dir\-times\fR" 4
.IX Item "--dir-times"
-The default is to ignore changed times on directory entries, since those are
-unlikely to be interesting. Using this flag shows changes to the time
-fields of directories.
+The default is to ignore changed times on directory entries, since those are unlikely to be interesting. Using this flag shows changes to the time fields of directories.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
.IP "\fB\-\-domain\fR guest" 4
.IX Item "--domain guest"
.PD
-Add all the disks from the named libvirt guest, as the first guest. Domain
-UUIDs can be used instead of names.
+Add all the disks from the named libvirt guest, as the first guest. Domain UUIDs can be used instead of names.
.IP "\fB\-D\fR guest" 4
.IX Item "-D guest"
-Add all the disks from the named libvirt guest, as the second guest. Domain
-UUIDs can be used instead of names.
+Add all the disks from the named libvirt guest, as the second guest. Domain UUIDs can be used instead of names.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-diff normally turns echoing
-off so you cannot see what you are typing. If you are not worried about
-Tempest attacks and there is no one else in the room you can specify this
-flag to see what you are typing.
+When prompting for keys and passphrases, virt-diff normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-extra\-stats\fR" 4
.IX Item "--extra-stats"
Display extra stats.
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-The default for the \fI\-a\fR/\fI\-A\fR option is to auto-detect the format of the
-disk image. Using this forces the disk format for \fI\-a\fR/\fI\-A\fR options which
-follow on the command line. Using \fI\-\-format\fR with no argument switches
-back to auto-detection for subsequent \fI\-a\fR/\fI\-A\fR options.
+The default for the \fI\-a\fR/\fI\-A\fR option is to auto-detect the format of the disk image. Using this forces the disk format for \fI\-a\fR/\fI\-A\fR options which follow on the command line. Using \fI\-\-format\fR with no argument switches back to auto-detection for subsequent \fI\-a\fR/\fI\-A\fR options.
.Sp
例:
.Sp
\& virt\-diff \-\-format=raw \-a disk.img \-\-format \-a another.img [...]
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
.IX Item "--time-days"
Display time fields as days before now (negative if in the future).
.Sp
-Note that \f(CW0\fR in output means \*(L"up to 1 day before now\*(R", or that the age of
-the file is between 0 and 86399 seconds.
+Note that \f(CW0\fR in output means \*(L"up to 1 day before now\*(R", or that the age of the file is between 0 and 86399 seconds.
.IP "\fB\-\-time\-relative\fR" 4
.IX Item "--time-relative"
Display time fields as seconds before now (negative if in the future).
Display extended attributes.
.SH "CSV 形式に関する注意"
.IX Header "CSV 形式に関する注意"
-Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it should be easy to parse, but it is definitely not easy to parse.
.PP
神話: ただコンマで項目を区切る。 真実: これは正しく動き \fIません\fR。この例は 2 つの列があります:
.PP
\& bar",baz
.Ve
.PP
-For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv
-also packaged in major Linux distributions).
+For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv also packaged in major Linux distributions).
.PP
-For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl
-or Python’s built-in csv library).
+For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl or Python’s built-in csv library).
.PP
Most spreadsheets and databases can import \s-1CSV\s0 directly.
.SH "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-ls\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-ls\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-C<virt-diff> lists the differences between files in two virtual machines or
-disk images. The usual use case is to show the changes in a VM after it has
-been running for a while, by taking a snapshot, running the VM, and then
-using this tool to show what changed between the new VM state and the old
-snapshot.
-
-This tool will find differences in filenames, file sizes, checksums,
-extended attributes, file content and more from a virtual machine or disk
-image. However it B<does not> look at the boot loader, unused space between
-partitions or within filesystems, "hidden" sectors and so on. In other
-words, it is not a security or forensics tool.
-
-To specify two guests, you have to use the I<-a> or I<-d> option(s) for the
-first guest, and the I<-A> or I<-D> option(s) for the second guest. The
-common case is:
+C<virt-diff> lists the differences between files in two virtual machines or disk images. The usual use case is to show the changes in a VM after it has been running for a while, by taking a snapshot, running the VM, and then using this tool to show what changed between the new VM state and the old snapshot.
+
+This tool will find differences in filenames, file sizes, checksums, extended attributes, file content and more from a virtual machine or disk image. However it B<does not> look at the boot loader, unused space between partitions or within filesystems, "hidden" sectors and so on. In other words, it is not a security or forensics tool.
+
+To specify two guests, you have to use the I<-a> or I<-d> option(s) for the first guest, and the I<-A> or I<-D> option(s) for the second guest. The common case is:
virt-diff -a old.img -A new.img
=item B<--add> file
-Add I<file> which should be a disk image from the first virtual machine. If
-the virtual machine has multiple block devices, you must supply all of them
-with separate I<-a> options.
+Add I<file> which should be a disk image from the first virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--atime>
-The default is to ignore changes in file access times, since those are
-unlikely to be interesting. Using this flag shows atime differences as
-well.
+The default is to ignore changes in file access times, since those are unlikely to be interesting. Using this flag shows atime differences as well.
=item B<-A> file
=item B<--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512>
-Use a checksum over file contents to detect when regular files have changed
-content.
+Use a checksum over file contents to detect when regular files have changed content.
-With no argument, this defaults to using I<md5>. Using an argument, you can
-select the checksum type to use. If the flag is omitted then file times and
-size are used to determine if a file has changed.
+With no argument, this defaults to using I<md5>. Using an argument, you can select the checksum type to use. If the flag is omitted then file times and size are used to determine if a file has changed.
=item B<-c> URI
=item B<--csv>
-Write out the results in CSV format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read L</NOTE
-ABOUT CSV FORMAT> below.
+Write out the results in CSV format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read L</NOTE ABOUT CSV FORMAT> below.
=item B<--dir-links>
-The default is to ignore changes in the number of links in directory
-entries, since those are unlikely to be interesting. Using this flag shows
-changes to the nlink field of directories.
+The default is to ignore changes in the number of links in directory entries, since those are unlikely to be interesting. Using this flag shows changes to the nlink field of directories.
=item B<--dir-times>
-The default is to ignore changed times on directory entries, since those are
-unlikely to be interesting. Using this flag shows changes to the time
-fields of directories.
+The default is to ignore changed times on directory entries, since those are unlikely to be interesting. Using this flag shows changes to the time fields of directories.
=item B<-d> guest
=item B<--domain> guest
-Add all the disks from the named libvirt guest, as the first guest. Domain
-UUIDs can be used instead of names.
+Add all the disks from the named libvirt guest, as the first guest. Domain UUIDs can be used instead of names.
=item B<-D> guest
-Add all the disks from the named libvirt guest, as the second guest. Domain
-UUIDs can be used instead of names.
+Add all the disks from the named libvirt guest, as the second guest. Domain UUIDs can be used instead of names.
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-diff normally turns echoing
-off so you cannot see what you are typing. If you are not worried about
-Tempest attacks and there is no one else in the room you can specify this
-flag to see what you are typing.
+When prompting for keys and passphrases, virt-diff normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--extra-stats>
=item B<--format>
-The default for the I<-a>/I<-A> option is to auto-detect the format of the
-disk image. Using this forces the disk format for I<-a>/I<-A> options which
-follow on the command line. Using I<--format> with no argument switches
-back to auto-detection for subsequent I<-a>/I<-A> options.
+The default for the I<-a>/I<-A> option is to auto-detect the format of the disk image. Using this forces the disk format for I<-a>/I<-A> options which follow on the command line. Using I<--format> with no argument switches back to auto-detection for subsequent I<-a>/I<-A> options.
例:
virt-diff --format=raw -a disk.img --format -a another.img [...]
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<-h>
Display time fields as days before now (negative if in the future).
-Note that C<0> in output means "up to 1 day before now", or that the age of
-the file is between 0 and 86399 seconds.
+Note that C<0> in output means "up to 1 day before now", or that the age of the file is between 0 and 86399 seconds.
=item B<--time-relative>
=head1 CSV 形式に関する注意
-Comma-separated values (CSV) is a deceptive format. It I<seems> like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (CSV) is a deceptive format. It I<seems> like it should be easy to parse, but it is definitely not easy to parse.
神話: ただコンマで項目を区切る。 真実: これは正しく動き I<ません>。この例は 2 つの列があります:
"foo
bar",baz
-For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv>
-also packaged in major Linux distributions).
+For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv> also packaged in major Linux distributions).
-For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl
-or Python’s built-in csv library).
+For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl or Python’s built-in csv library).
Most spreadsheets and databases can import CSV directly.
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-ls(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-ls(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-edit 1"
-.TH virt-edit 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-edit 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.IX Header "説明"
\&\f(CW\*(C`virt\-edit\*(C'\fR は名前付きの仮想マシン（またはディスクイメージ）にある、それぞれの \f(CW\*(C`ファイル\*(C'\fR を編集するためのコマンドラインツールです。
.PP
-複数のファイル名を指定できます。その場合、それぞれ順番に編集されます。各ファイル名はルートディレクトリーから始まる（つまり '/'
-から始まる）完全パスである必要があります。
+複数のファイル名を指定できます。その場合、それぞれ順番に編集されます。各ファイル名はルートディレクトリーから始まる（つまり '/' から始まる）完全パスである必要があります。
.PP
単にファイルを表示したいだけならば、 \fBvirt\-cat\fR\|(1) を使用してください。
.PP
\& virt\-edit \-d mywindomain \*(Aqc:\eautoexec.bat\*(Aq
.Ve
.PP
-Perl がインストールされていると、非対話的にファイルを編集することもできます（以下の \*(L"非対話的な編集方法\*(R" 参照）。 init
-の初期ランベルを 5 に変更するには:
+Perl がインストールされていると、非対話的にファイルを編集することもできます（以下の \*(L"非対話的な編集方法\*(R" 参照）。 init の初期ランベルを 5 に変更するには:
.PP
.Vb 1
\& virt\-edit \-d mydomain /etc/inittab \-e \*(Aqs/^id:.*/id:5:initdefault:/\*(Aq
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a\fR \s-1URI\s0" 4
.IP "\fB\-\-backup\fR \s-1EXTENSION\s0" 4
.IX Item "--backup EXTENSION"
.PD
-\&\fI仮想マシンのディスクイメージにある\fR 元のファイルのバックアップを作成します。バックアップは元のファイル名に \f(CW\*(C`extension\*(C'\fR
-を加えたものになります。
+\&\fI仮想マシンのディスクイメージにある\fR 元のファイルのバックアップを作成します。バックアップは元のファイル名に \f(CW\*(C`extension\*(C'\fR を加えたものになります。
.Sp
一般的に \f(CW\*(C`extension\*(C'\fR の最初の文字はドット \f(CW\*(C`.\*(C'\fR です。そのため次のように書きます:
.Sp
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-キーやパスフレーズを入力するとき、通常 virt-edit はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-edit はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
.IP "\fB\-e\fR \s-1EXPR\s0" 4
.IX Item "-e EXPR"
.PD 0
.IP "\fB\-\-expr\fR \s-1EXPR\s0" 4
.IX Item "--expr EXPR"
.PD
-外部エディターを起動する代わりに、ファイルにある各行に対して非対話的に Perl 表現 \f(CW\*(C`EXPR\*(C'\fR を適用します。以下の \*(L"非対話的な編集方法\*(R"
-を参照してください。
+外部エディターを起動する代わりに、ファイルにある各行に対して非対話的に Perl 表現 \f(CW\*(C`EXPR\*(C'\fR を適用します。以下の \*(L"非対話的な編集方法\*(R" を参照してください。
.Sp
表現がシェルにより変更されるのを防ぐために、適切に引用符でくくるよう注意してください。
.Sp
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-edit \-\-format=raw \-a disk.img \-\-format \-a another.img file
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.Sp
If the mountpoint is omitted, it defaults to \fI/\fR.
.Sp
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
.Sp
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R"
-commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R" commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
.Sp
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR フラグが使用されている場合) になります。
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Sp
このフラグを使用することは、 \f(CW\*(C`mount\-options\*(C'\fR コマンドを使用することと同等です。
.Sp
-パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
\& virt\-edit guestname file
.Ve
.PP
-whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid the confusing case where a disk image might have the same name as a guest.
.PP
互換性のため古い形式がまだサポートされています。
.SH "非対話的な編集方法"
.IX Header "非対話的な編集方法"
-\&\f(CW\*(C`virt\-edit\*(C'\fR normally calls out to \f(CW$EDITOR\fR (or vi) so the system
-administrator can interactively edit the file.
+\&\f(CW\*(C`virt\-edit\*(C'\fR normally calls out to \f(CW$EDITOR\fR (or vi) so the system administrator can interactively edit the file.
.PP
-There are two ways also to use \f(CW\*(C`virt\-edit\*(C'\fR from scripts in order to make
-automated edits to files. (Note that although you \fIcan\fR use \f(CW\*(C`virt\-edit\*(C'\fR
-like this, it’s less error-prone to write scripts directly using the
-libguestfs \s-1API\s0 and Augeas for configuration file editing.)
+There are two ways also to use \f(CW\*(C`virt\-edit\*(C'\fR from scripts in order to make automated edits to files. (Note that although you \fIcan\fR use \f(CW\*(C`virt\-edit\*(C'\fR like this, it’s less error-prone to write scripts directly using the libguestfs \s-1API\s0 and Augeas for configuration file editing.)
.PP
-The first method is to temporarily set \f(CW$EDITOR\fR to any script or program
-you want to run. The script is invoked as \f(CW\*(C`$EDITOR tmpfile\*(C'\fR and it should
-update \f(CW\*(C`tmpfile\*(C'\fR in place however it likes.
+The first method is to temporarily set \f(CW$EDITOR\fR to any script or program you want to run. The script is invoked as \f(CW\*(C`$EDITOR tmpfile\*(C'\fR and it should update \f(CW\*(C`tmpfile\*(C'\fR in place however it likes.
.PP
-The second method is to use the \fI\-e\fR parameter of \f(CW\*(C`virt\-edit\*(C'\fR to run a
-short Perl snippet in the style of \fBsed\fR\|(1). For example to replace all
-instances of \f(CW\*(C`foo\*(C'\fR with \f(CW\*(C`bar\*(C'\fR in a file:
+The second method is to use the \fI\-e\fR parameter of \f(CW\*(C`virt\-edit\*(C'\fR to run a short Perl snippet in the style of \fBsed\fR\|(1). For example to replace all instances of \f(CW\*(C`foo\*(C'\fR with \f(CW\*(C`bar\*(C'\fR in a file:
.PP
.Vb 1
\& virt\-edit \-d domname filename \-e \*(Aqs/foo/bar/\*(Aq
.Ve
.PP
-The full power of Perl regular expressions can be used (see \fBperlre\fR\|(1)).
-For example to delete root’s password you could do:
+The full power of Perl regular expressions can be used (see \fBperlre\fR\|(1)). For example to delete root’s password you could do:
.PP
.Vb 1
\& virt\-edit \-d domname /etc/passwd \-e \*(Aqs/^root:.*?:/root::/\*(Aq
.Ve
.PP
-What really happens is that the snippet is evaluated as a Perl expression
-for each line of the file. The line, including the final \f(CW\*(C`\en\*(C'\fR, is passed
-in \f(CW$_\fR and the expression should update \f(CW$_\fR or leave it unchanged.
+What really happens is that the snippet is evaluated as a Perl expression for each line of the file. The line, including the final \f(CW\*(C`\en\*(C'\fR, is passed in \f(CW$_\fR and the expression should update \f(CW$_\fR or leave it unchanged.
.PP
-To delete a line, set \f(CW$_\fR to the empty string. For example, to delete the
-\&\f(CW\*(C`apache\*(C'\fR user account from the password file you can do:
+To delete a line, set \f(CW$_\fR to the empty string. For example, to delete the \f(CW\*(C`apache\*(C'\fR user account from the password file you can do:
.PP
.Vb 1
\& virt\-edit \-d mydomain /etc/passwd \-e \*(Aq$_ = "" if /^apache:/\*(Aq
.Ve
.PP
-To insert a line, prepend or append it to \f(CW$_\fR. However appending lines to
-the end of the file is rather difficult this way since there is no concept
-of \*(L"last line of the file\*(R" \- your expression just doesn't get called again.
-You might want to use the first method (setting \f(CW$EDITOR\fR) if you want to
-do this.
+To insert a line, prepend or append it to \f(CW$_\fR. However appending lines to the end of the file is rather difficult this way since there is no concept of \*(L"last line of the file\*(R" \- your expression just doesn't get called again. You might want to use the first method (setting \f(CW$EDITOR\fR) if you want to do this.
.PP
-The variable \f(CW$lineno\fR contains the current line number. As is
-traditional, the first line in the file is number \f(CW1\fR.
+The variable \f(CW$lineno\fR contains the current line number. As is traditional, the first line in the file is number \f(CW1\fR.
.PP
-The return value from the expression is ignored, but the expression may call
-\&\f(CW\*(C`die\*(C'\fR in order to abort the whole program, leaving the original file
-untouched.
+The return value from the expression is ignored, but the expression may call \f(CW\*(C`die\*(C'\fR in order to abort the whole program, leaving the original file untouched.
.PP
-Remember when matching the end of a line that \f(CW$_\fR may contain the final
-\&\f(CW\*(C`\en\*(C'\fR, or (for \s-1DOS\s0 files) \f(CW\*(C`\er\en\*(C'\fR, or if the file does not end with a
-newline then neither of these. Thus to match or substitute some text at the
-end of a line, use this regular expression:
+Remember when matching the end of a line that \f(CW$_\fR may contain the final \f(CW\*(C`\en\*(C'\fR, or (for \s-1DOS\s0 files) \f(CW\*(C`\er\en\*(C'\fR, or if the file does not end with a newline then neither of these. Thus to match or substitute some text at the end of a line, use this regular expression:
.PP
.Vb 1
\& /some text(\er?\en)?$/
.Ve
.PP
-Alternately, use the perl \f(CW\*(C`chomp\*(C'\fR function, being careful not to chomp
-\&\f(CW$_\fR itself (since that would remove all newlines from the file):
+Alternately, use the perl \f(CW\*(C`chomp\*(C'\fR function, being careful not to chomp \f(CW$_\fR itself (since that would remove all newlines from the file):
.PP
.Vb 1
\& my $m = $_; chomp $m; $m =~ /some text$/
.Ve
.SH "Windows のパス"
.IX Header "Windows のパス"
-\&\f(CW\*(C`virt\-edit\*(C'\fR has a limited ability to understand Windows drive letters and
-paths (eg. \fIE:\efoo\ebar.txt\fR).
+\&\f(CW\*(C`virt\-edit\*(C'\fR has a limited ability to understand Windows drive letters and paths (eg. \fIE:\efoo\ebar.txt\fR).
.PP
仮想マシンが Windows を実行している場合に限り:
.IP "\(bu" 4
-Drive letter prefixes like \f(CW\*(C`C:\*(C'\fR are resolved against the Windows Registry
-to the correct filesystem.
+Drive letter prefixes like \f(CW\*(C`C:\*(C'\fR are resolved against the Windows Registry to the correct filesystem.
.IP "\(bu" 4
-Any backslash (\f(CW\*(C`\e\*(C'\fR) characters in the path are replaced with forward
-slashes so that libguestfs can process it.
+Any backslash (\f(CW\*(C`\e\*(C'\fR) characters in the path are replaced with forward slashes so that libguestfs can process it.
.IP "\(bu" 4
-The path is resolved case insensitively to locate the file that should be
-edited.
+The path is resolved case insensitively to locate the file that should be edited.
.PP
There are some known shortcomings:
.IP "\(bu" 4
\&\s-1NTFS\s0 junction points that cross filesystems are not followed.
.SH "guestfish の使用法"
.IX Header "guestfish の使用法"
-\&\fBguestfish\fR\|(1) is a more powerful, lower level tool which you can use when
-\&\f(CW\*(C`virt\-edit\*(C'\fR doesn't work.
+\&\fBguestfish\fR\|(1) is a more powerful, lower level tool which you can use when \f(CW\*(C`virt\-edit\*(C'\fR doesn't work.
.PP
Using \f(CW\*(C`virt\-edit\*(C'\fR is approximately equivalent to doing:
.PP
\& guestfish \-\-rw \-i \-d domname edit /file
.Ve
.PP
-where \f(CW\*(C`domname\*(C'\fR is the name of the libvirt guest, and \fI/file\fR is the full
-path to the file.
+where \f(CW\*(C`domname\*(C'\fR is the name of the libvirt guest, and \fI/file\fR is the full path to the file.
.PP
-The command above uses libguestfs’s guest inspection feature and so does not
-work on guests that libguestfs cannot inspect, or on things like arbitrary
-disk images that don't contain guests. To edit a file on a disk image
-directly, use:
+The command above uses libguestfs’s guest inspection feature and so does not work on guests that libguestfs cannot inspect, or on things like arbitrary disk images that don't contain guests. To edit a file on a disk image directly, use:
.PP
.Vb 1
\& guestfish \-\-rw \-a disk.img \-m /dev/sda1 edit /file
.Ve
.PP
-where \fIdisk.img\fR is the disk image, \fI/dev/sda1\fR is the filesystem within
-the disk image to edit, and \fI/file\fR is the full path to the file.
+where \fIdisk.img\fR is the disk image, \fI/dev/sda1\fR is the filesystem within the disk image to edit, and \fI/file\fR is the full path to the file.
.PP
-\&\f(CW\*(C`virt\-edit\*(C'\fR は新しいファイルを作成できません。代わりに guestfish コマンド \f(CW\*(C`touch\*(C'\fR, \f(CW\*(C`write\*(C'\fR または
-\&\f(CW\*(C`upload\*(C'\fR を使用してください:
+\&\f(CW\*(C`virt\-edit\*(C'\fR は新しいファイルを作成できません。代わりに guestfish コマンド \f(CW\*(C`touch\*(C'\fR, \f(CW\*(C`write\*(C'\fR または \f(CW\*(C`upload\*(C'\fR を使用してください:
.PP
.Vb 1
\& guestfish \-\-rw \-i \-d domname touch /newfile
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-in\fR\|(1),
-\&\fBvirt\-tar\-in\fR\|(1), http://libguestfs.org/, \fBperl\fR\|(1), \fBperlre\fR\|(1).
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-in\fR\|(1), \fBvirt\-tar\-in\fR\|(1), http://libguestfs.org/, \fBperl\fR\|(1), \fBperlre\fR\|(1).
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
C<virt-edit> は名前付きの仮想マシン（またはディスクイメージ）にある、それぞれの C<ファイル> を編集するためのコマンドラインツールです。
-複数のファイル名を指定できます。その場合、それぞれ順番に編集されます。各ファイル名はルートディレクトリーから始まる（つまり '/'
-から始まる）完全パスである必要があります。
+複数のファイル名を指定できます。その場合、それぞれ順番に編集されます。各ファイル名はルートディレクトリーから始まる（つまり '/' から始まる）完全パスである必要があります。
単にファイルを表示したいだけならば、 L<virt-cat(1)> を使用してください。
virt-edit -d mywindomain 'c:\autoexec.bat'
-Perl がインストールされていると、非対話的にファイルを編集することもできます（以下の L</非対話的な編集方法> 参照）。 init
-の初期ランベルを 5 に変更するには:
+Perl がインストールされていると、非対話的にファイルを編集することもできます（以下の L</非対話的な編集方法> 参照）。 init の初期ランベルを 5 に変更するには:
virt-edit -d mydomain /etc/inittab -e 's/^id:.*/id:5:initdefault:/'
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--backup> EXTENSION
-I<仮想マシンのディスクイメージにある> 元のファイルのバックアップを作成します。バックアップは元のファイル名に C<extension>
-を加えたものになります。
+I<仮想マシンのディスクイメージにある> 元のファイルのバックアップを作成します。バックアップは元のファイル名に C<extension> を加えたものになります。
一般的に C<extension> の最初の文字はドット C<.> です。そのため次のように書きます:
=item B<--echo-keys>
-キーやパスフレーズを入力するとき、通常 virt-edit はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-edit はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
=item B<-e> EXPR
=item B<--expr> EXPR
-外部エディターを起動する代わりに、ファイルにある各行に対して非対話的に Perl 表現 C<EXPR> を適用します。以下の L</非対話的な編集方法>
-を参照してください。
+外部エディターを起動する代わりに、ファイルにある各行に対して非対話的に Perl 表現 C<EXPR> を適用します。以下の L</非対話的な編集方法> を参照してください。
表現がシェルにより変更されるのを防ぐために、適切に引用符でくくるよう注意してください。
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-edit --format=raw -a disk.img --format -a another.img file
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
If the mountpoint is omitted, it defaults to F</>.
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see L</list-partitions>, L</list-filesystems> and L</lvs>
-commands), or you can use the L<virt-filesystems(1)> program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see L</list-partitions>, L</list-filesystems> and L</lvs> commands), or you can use the L<virt-filesystems(1)> program.
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro>
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro> フラグが使用されている場合) になります。
-m /dev/sda1:/:acl,user_xattr
このフラグを使用することは、 C<mount-options> コマンドを使用することと同等です。
-パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
=item B<-v>
virt-edit guestname file
-whereas in this version you should use I<-a> or I<-d> respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use I<-a> or I<-d> respectively to avoid the confusing case where a disk image might have the same name as a guest.
互換性のため古い形式がまだサポートされています。
=head1 非対話的な編集方法
-C<virt-edit> normally calls out to C<$EDITOR> (or vi) so the system
-administrator can interactively edit the file.
+C<virt-edit> normally calls out to C<$EDITOR> (or vi) so the system administrator can interactively edit the file.
-There are two ways also to use C<virt-edit> from scripts in order to make
-automated edits to files. (Note that although you I<can> use C<virt-edit>
-like this, it’s less error-prone to write scripts directly using the
-libguestfs API and Augeas for configuration file editing.)
+There are two ways also to use C<virt-edit> from scripts in order to make automated edits to files. (Note that although you I<can> use C<virt-edit> like this, it’s less error-prone to write scripts directly using the libguestfs API and Augeas for configuration file editing.)
-The first method is to temporarily set C<$EDITOR> to any script or program
-you want to run. The script is invoked as C<$EDITOR tmpfile> and it should
-update C<tmpfile> in place however it likes.
+The first method is to temporarily set C<$EDITOR> to any script or program you want to run. The script is invoked as C<$EDITOR tmpfile> and it should update C<tmpfile> in place however it likes.
-The second method is to use the I<-e> parameter of C<virt-edit> to run a
-short Perl snippet in the style of L<sed(1)>. For example to replace all
-instances of C<foo> with C<bar> in a file:
+The second method is to use the I<-e> parameter of C<virt-edit> to run a short Perl snippet in the style of L<sed(1)>. For example to replace all instances of C<foo> with C<bar> in a file:
virt-edit -d domname filename -e 's/foo/bar/'
-The full power of Perl regular expressions can be used (see L<perlre(1)>).
-For example to delete root’s password you could do:
+The full power of Perl regular expressions can be used (see L<perlre(1)>). For example to delete root’s password you could do:
virt-edit -d domname /etc/passwd -e 's/^root:.*?:/root::/'
-What really happens is that the snippet is evaluated as a Perl expression
-for each line of the file. The line, including the final C<\n>, is passed
-in C<$_> and the expression should update C<$_> or leave it unchanged.
+What really happens is that the snippet is evaluated as a Perl expression for each line of the file. The line, including the final C<\n>, is passed in C<$_> and the expression should update C<$_> or leave it unchanged.
-To delete a line, set C<$_> to the empty string. For example, to delete the
-C<apache> user account from the password file you can do:
+To delete a line, set C<$_> to the empty string. For example, to delete the C<apache> user account from the password file you can do:
virt-edit -d mydomain /etc/passwd -e '$_ = "" if /^apache:/'
-To insert a line, prepend or append it to C<$_>. However appending lines to
-the end of the file is rather difficult this way since there is no concept
-of "last line of the file" - your expression just doesn't get called again.
-You might want to use the first method (setting C<$EDITOR>) if you want to
-do this.
+To insert a line, prepend or append it to C<$_>. However appending lines to the end of the file is rather difficult this way since there is no concept of "last line of the file" - your expression just doesn't get called again. You might want to use the first method (setting C<$EDITOR>) if you want to do this.
-The variable C<$lineno> contains the current line number. As is
-traditional, the first line in the file is number C<1>.
+The variable C<$lineno> contains the current line number. As is traditional, the first line in the file is number C<1>.
-The return value from the expression is ignored, but the expression may call
-C<die> in order to abort the whole program, leaving the original file
-untouched.
+The return value from the expression is ignored, but the expression may call C<die> in order to abort the whole program, leaving the original file untouched.
-Remember when matching the end of a line that C<$_> may contain the final
-C<\n>, or (for DOS files) C<\r\n>, or if the file does not end with a
-newline then neither of these. Thus to match or substitute some text at the
-end of a line, use this regular expression:
+Remember when matching the end of a line that C<$_> may contain the final C<\n>, or (for DOS files) C<\r\n>, or if the file does not end with a newline then neither of these. Thus to match or substitute some text at the end of a line, use this regular expression:
/some text(\r?\n)?$/
-Alternately, use the perl C<chomp> function, being careful not to chomp
-C<$_> itself (since that would remove all newlines from the file):
+Alternately, use the perl C<chomp> function, being careful not to chomp C<$_> itself (since that would remove all newlines from the file):
my $m = $_; chomp $m; $m =~ /some text$/
=head1 Windows のパス
-C<virt-edit> has a limited ability to understand Windows drive letters and
-paths (eg. F<E:\foo\bar.txt>).
+C<virt-edit> has a limited ability to understand Windows drive letters and paths (eg. F<E:\foo\bar.txt>).
仮想マシンが Windows を実行している場合に限り:
=item *
-Drive letter prefixes like C<C:> are resolved against the Windows Registry
-to the correct filesystem.
+Drive letter prefixes like C<C:> are resolved against the Windows Registry to the correct filesystem.
=item *
-Any backslash (C<\>) characters in the path are replaced with forward
-slashes so that libguestfs can process it.
+Any backslash (C<\>) characters in the path are replaced with forward slashes so that libguestfs can process it.
=item *
-The path is resolved case insensitively to locate the file that should be
-edited.
+The path is resolved case insensitively to locate the file that should be edited.
=back
=head1 guestfish の使用法
-L<guestfish(1)> is a more powerful, lower level tool which you can use when
-C<virt-edit> doesn't work.
+L<guestfish(1)> is a more powerful, lower level tool which you can use when C<virt-edit> doesn't work.
Using C<virt-edit> is approximately equivalent to doing:
guestfish --rw -i -d domname edit /file
-where C<domname> is the name of the libvirt guest, and F</file> is the full
-path to the file.
+where C<domname> is the name of the libvirt guest, and F</file> is the full path to the file.
-The command above uses libguestfs’s guest inspection feature and so does not
-work on guests that libguestfs cannot inspect, or on things like arbitrary
-disk images that don't contain guests. To edit a file on a disk image
-directly, use:
+The command above uses libguestfs’s guest inspection feature and so does not work on guests that libguestfs cannot inspect, or on things like arbitrary disk images that don't contain guests. To edit a file on a disk image directly, use:
guestfish --rw -a disk.img -m /dev/sda1 edit /file
-where F<disk.img> is the disk image, F</dev/sda1> is the filesystem within
-the disk image to edit, and F</file> is the full path to the file.
+where F<disk.img> is the disk image, F</dev/sda1> is the filesystem within the disk image to edit, and F</file> is the full path to the file.
-C<virt-edit> は新しいファイルを作成できません。代わりに guestfish コマンド C<touch>, C<write> または
-C<upload> を使用してください:
+C<virt-edit> は新しいファイルを作成できません。代わりに guestfish コマンド C<touch>, C<write> または C<upload> を使用してください:
guestfish --rw -i -d domname touch /newfile
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-in(1)>,
-L<virt-tar-in(1)>, L<http://libguestfs.org/>, L<perl(1)>, L<perlre(1)>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-in(1)>, L<virt-tar-in(1)>, L<http://libguestfs.org/>, L<perl(1)>, L<perlre(1)>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-filesystems 1"
-.TH virt-filesystems 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-filesystems 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-This tool allows you to discover filesystems, partitions, logical volumes,
-and their sizes in a disk image or virtual machine. It is a replacement for
-\&\fBvirt\-list\-filesystems\fR\|(1) and \fBvirt\-list\-partitions\fR\|(1).
+This tool allows you to discover filesystems, partitions, logical volumes, and their sizes in a disk image or virtual machine. It is a replacement for \fBvirt\-list\-filesystems\fR\|(1) and \fBvirt\-list\-partitions\fR\|(1).
.PP
-One use for this tool is from shell scripts to iterate over all filesystems
-from a disk image:
+One use for this tool is from shell scripts to iterate over all filesystems from a disk image:
.PP
.Vb 3
\& for fs in $(virt\-filesystems \-a disk.img); do
\& done
.Ve
.PP
-他の使用方法は、これらのパーティションを変更するために (\fBvirt\-resize\fR\|(1) のような)
-他のツールを使用する前に、パーティションを一覧表示することです。未知のディスクイメージが含んでいるものについてわからなければ、\fBvirt\-inspector\fR\|(1)
-とともにこのツールを使用します。
+他の使用方法は、これらのパーティションを変更するために (\fBvirt\-resize\fR\|(1) のような) 他のツールを使用する前に、パーティションを一覧表示することです。未知のディスクイメージが含んでいるものについてわからなければ、\fBvirt\-inspector\fR\|(1) とともにこのツールを使用します。
.PP
-さまざまなコマンドラインオプションがこのプログラムが表示するものを制御します。それぞれディスクイメージまたは libvirt 仮想マシンを指定するには
-\&\fI\-a\fR または \fI\-d\fR オプションを与える必要があります。単にそれを指定すると、見つけたファイルシステムを 1 行ごとに 1
-つずつこのように表示します:
+さまざまなコマンドラインオプションがこのプログラムが表示するものを制御します。それぞれディスクイメージまたは libvirt 仮想マシンを指定するには \fI\-a\fR または \fI\-d\fR オプションを与える必要があります。単にそれを指定すると、見つけたファイルシステムを 1 行ごとに 1 つずつこのように表示します:
.PP
.Vb 3
\& $ virt\-filesystems \-a disk.img
\& /dev/sda2
.Ve
.PP
-同様に、それらの項目を一覧表示するには \fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR,
-\&\fI\-\-physical\-volumes\fR, \fI\-\-block\-devices\fR を使用できます。
+同様に、それらの項目を一覧表示するには \fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR, \fI\-\-block\-devices\fR を使用できます。
.PP
-You can use these options in combination as well (if you want a combination
-including filesystems, you have to add \fI\-\-filesystems\fR). Notice that some
-items fall into several categories (eg. \fI/dev/sda1\fR might be both a
-partition and a filesystem). These items are listed several times. To get
-a list which includes absolutely everything that virt-filesystems knows
-about, use the \fI\-\-all\fR option.
+You can use these options in combination as well (if you want a combination including filesystems, you have to add \fI\-\-filesystems\fR). Notice that some items fall into several categories (eg. \fI/dev/sda1\fR might be both a partition and a filesystem). These items are listed several times. To get a list which includes absolutely everything that virt-filesystems knows about, use the \fI\-\-all\fR option.
.PP
-UUIDs (because they are quite long) are not shown by default. Add the
-\&\fI\-\-uuid\fR option to display device and filesystem UUIDs in the long output.
+UUIDs (because they are quite long) are not shown by default. Add the \fI\-\-uuid\fR option to display device and filesystem UUIDs in the long output.
.PP
-\&\fI\-\-all \-\-long \-\-uuid\fR is a useful combination to display all possible
-information about everything.
+\&\fI\-\-all \-\-long \-\-uuid\fR is a useful combination to display all possible information about everything.
.PP
.Vb 7
\& $ virt\-filesystems \-a win.img \-\-all \-\-long \-\-uuid \-h
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a \s-1URI\s0\fR" 4
リモートディスクを追加します。 \*(L"リモートストレージの追加\*(R" in \fBguestfish\fR\|(1) 参照。
.IP "\fB\-\-all\fR" 4
.IX Item "--all"
-すべてを表示します。これは現在これらのオプションを指定するのと同じです: \fI\-\-filesystems\fR, \fI\-\-extra\fR,
-\&\fI\-\-partitions\fR, \fI\-\-block\-devices\fR, \fI\-\-logical\-volumes\fR,
-\&\fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR。（将来この一覧にさらに追加されるかもしれません。）
+すべてを表示します。これは現在これらのオプションを指定するのと同じです: \fI\-\-filesystems\fR, \fI\-\-extra\fR, \fI\-\-partitions\fR, \fI\-\-block\-devices\fR, \fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR。（将来この一覧にさらに追加されるかもしれません。）
.Sp
\&\fI\-\-long\fR 参照。
.IP "\fB\-\-blkdevs\fR" 4
ゲストのブロックデバイスを直接指定していると（(\fI\-a\fR)）、libvirt は何も使用されません。
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Write out the results in \s-1CSV\s0 format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE
-ABOUT CSV FORMAT\*(R"\s0 below.
+Write out the results in \s-1CSV\s0 format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE ABOUT CSV FORMAT\*(R"\s0 below.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-キーやパスフレーズを入力するとき、通常 virt-filesystems はエコーを無効化します。 そのため、入力内容を確認できません。
-テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-filesystems はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
.IP "\fB\-\-extra\fR" 4
.IX Item "--extra"
-This causes filesystems that are not ordinary, mountable filesystems to be
-displayed. This category includes swapspace, and filesystems that are empty
-or contain unknown data.
+This causes filesystems that are not ordinary, mountable filesystems to be displayed. This category includes swapspace, and filesystems that are empty or contain unknown data.
.Sp
このオプションは \fI\-\-filesystems\fR を意味します。
.IP "\fB\-\-filesystems\fR" 4
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-filesystems \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
.Sp
A title row is added unless you also specify \fI\-\-no\-title\fR.
.Sp
-The extra columns displayed depend on what output you select, and the
-ordering of columns may change in future versions. Use the title row,
-\&\fI\-\-csv\fR output and/or \fBcsvtool\fR\|(1) to match columns to data in external
-programs.
+The extra columns displayed depend on what output you select, and the ordering of columns may change in future versions. Use the title row, \fI\-\-csv\fR output and/or \fBcsvtool\fR\|(1) to match columns to data in external programs.
.Sp
-Use \fI\-h\fR if you want sizes to be displayed in human-readable format. The
-default is to show raw numbers of \fIbytes\fR.
+Use \fI\-h\fR if you want sizes to be displayed in human-readable format. The default is to show raw numbers of \fIbytes\fR.
.Sp
\&\s-1UUID\s0 も表示するには \fI\-\-uuid\fR を使用します。
.IP "\fB\-\-lvs\fR" 4
.IX Item "--no-title"
In \fI\-\-long\fR mode, don’t add a title row.
.Sp
-Note that the order of the columns is not fixed, and may change in future
-versions of virt-filesystems, so using this option may give you unexpected
-surprises.
+Note that the order of the columns is not fixed, and may change in future versions of virt-filesystems, so using this option may give you unexpected surprises.
.IP "\fB\-\-parts\fR" 4
.IX Item "--parts"
.PD 0
.IX Item "名前"
ファイルシステム、パーティション、ブロックデバイスまたは \s-1LVM\s0 の名前。
.Sp
-For device and partition names these are displayed as canonical libguestfs
-names, so that for example \fI/dev/sda2\fR is the second partition on the first
-device.
+For device and partition names these are displayed as canonical libguestfs names, so that for example \fI/dev/sda2\fR is the second partition on the first device.
.Sp
\&\fI\-\-long\fR オプションが指定されて\fBいない\fRと、名前の列のみが出力に表示されます。
.IP "\fB種類\fR" 4
（ファイルシステムの識別とマウントのために使用される）ラベルがオブジェクトにあれば、この列はラベルを含みます。
.IP "\fB\s-1MBR\s0\fR" 4
.IX Item "MBR"
-パーティション形式のバイト、2 桁の 16 進数として表示されます。パーティション形式の完全な一覧は次のところにあります:
-http://www.win.tue.nl/~aeb/partitions/partition_types\-1.html
+パーティション形式のバイト、2 桁の 16 進数として表示されます。パーティション形式の完全な一覧は次のところにあります: http://www.win.tue.nl/~aeb/partitions/partition_types\-1.html
.Sp
これは \s-1DOS\s0 (\s-1MBR\s0) パーティションに対してのみ適用できます。
.IP "\fB容量\fR" 4
複数の親があると、この列は (内部に列を持つ) カンマ区切りの一覧になります。例: \f(CW\*(C`/dev/sda,/dev/sdb\*(C'\fR。
.IP "\fB\s-1UUID\s0\fR" 4
.IX Item "UUID"
-If the object has a \s-1UUID\s0 (used for identifying and mounting filesystems and
-block devices) then this column contains the \s-1UUID\s0 as a string.
+If the object has a \s-1UUID\s0 (used for identifying and mounting filesystems and block devices) then this column contains the \s-1UUID\s0 as a string.
.Sp
\&\fI\-\-uuid\fR オプションが指定されると、 \s-1UUID\s0 のみが表示されます。
.SH "CSV 形式に関する注意"
.IX Header "CSV 形式に関する注意"
-Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it should be easy to parse, but it is definitely not easy to parse.
.PP
神話: ただコンマで項目を区切る。 真実: これは正しく動き \fIません\fR。この例は 2 つの列があります:
.PP
\& bar",baz
.Ve
.PP
-For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv
-also packaged in major Linux distributions).
+For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv also packaged in major Linux distributions).
.PP
-For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl
-or Python’s built-in csv library).
+For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl or Python’s built-in csv library).
.PP
Most spreadsheets and databases can import \s-1CSV\s0 directly.
.SH "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-df\fR\|(1),
-\&\fBvirt\-list\-filesystems\fR\|(1), \fBvirt\-list\-partitions\fR\|(1), \fBcsvtool\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-df\fR\|(1), \fBvirt\-list\-filesystems\fR\|(1), \fBvirt\-list\-partitions\fR\|(1), \fBcsvtool\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-This tool allows you to discover filesystems, partitions, logical volumes,
-and their sizes in a disk image or virtual machine. It is a replacement for
-L<virt-list-filesystems(1)> and L<virt-list-partitions(1)>.
+This tool allows you to discover filesystems, partitions, logical volumes, and their sizes in a disk image or virtual machine. It is a replacement for L<virt-list-filesystems(1)> and L<virt-list-partitions(1)>.
-One use for this tool is from shell scripts to iterate over all filesystems
-from a disk image:
+One use for this tool is from shell scripts to iterate over all filesystems from a disk image:
for fs in $(virt-filesystems -a disk.img); do
# ...
done
-他の使用方法は、これらのパーティションを変更するために (L<virt-resize(1)> のような)
-他のツールを使用する前に、パーティションを一覧表示することです。未知のディスクイメージが含んでいるものについてわからなければ、L<virt-inspector(1)>
-とともにこのツールを使用します。
+他の使用方法は、これらのパーティションを変更するために (L<virt-resize(1)> のような) 他のツールを使用する前に、パーティションを一覧表示することです。未知のディスクイメージが含んでいるものについてわからなければ、L<virt-inspector(1)> とともにこのツールを使用します。
-さまざまなコマンドラインオプションがこのプログラムが表示するものを制御します。それぞれディスクイメージまたは libvirt 仮想マシンを指定するには
-I<-a> または I<-d> オプションを与える必要があります。単にそれを指定すると、見つけたファイルシステムを 1 行ごとに 1
-つずつこのように表示します:
+さまざまなコマンドラインオプションがこのプログラムが表示するものを制御します。それぞれディスクイメージまたは libvirt 仮想マシンを指定するには I<-a> または I<-d> オプションを与える必要があります。単にそれを指定すると、見つけたファイルシステムを 1 行ごとに 1 つずつこのように表示します:
$ virt-filesystems -a disk.img
/dev/sda1
/dev/sda1
/dev/sda2
-同様に、それらの項目を一覧表示するには I<--logical-volumes>, I<--volume-groups>,
-I<--physical-volumes>, I<--block-devices> を使用できます。
+同様に、それらの項目を一覧表示するには I<--logical-volumes>, I<--volume-groups>, I<--physical-volumes>, I<--block-devices> を使用できます。
-You can use these options in combination as well (if you want a combination
-including filesystems, you have to add I<--filesystems>). Notice that some
-items fall into several categories (eg. F</dev/sda1> might be both a
-partition and a filesystem). These items are listed several times. To get
-a list which includes absolutely everything that virt-filesystems knows
-about, use the I<--all> option.
+You can use these options in combination as well (if you want a combination including filesystems, you have to add I<--filesystems>). Notice that some items fall into several categories (eg. F</dev/sda1> might be both a partition and a filesystem). These items are listed several times. To get a list which includes absolutely everything that virt-filesystems knows about, use the I<--all> option.
-UUIDs (because they are quite long) are not shown by default. Add the
-I<--uuid> option to display device and filesystem UUIDs in the long output.
+UUIDs (because they are quite long) are not shown by default. Add the I<--uuid> option to display device and filesystem UUIDs in the long output.
-I<--all --long --uuid> is a useful combination to display all possible
-information about everything.
+I<--all --long --uuid> is a useful combination to display all possible information about everything.
$ virt-filesystems -a win.img --all --long --uuid -h
Name Type VFS Label Size Parent UUID
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--all>
-すべてを表示します。これは現在これらのオプションを指定するのと同じです: I<--filesystems>, I<--extra>,
-I<--partitions>, I<--block-devices>, I<--logical-volumes>,
-I<--volume-groups>, I<--physical-volumes>。（将来この一覧にさらに追加されるかもしれません。）
+すべてを表示します。これは現在これらのオプションを指定するのと同じです: I<--filesystems>, I<--extra>, I<--partitions>, I<--block-devices>, I<--logical-volumes>, I<--volume-groups>, I<--physical-volumes>。（将来この一覧にさらに追加されるかもしれません。）
I<--long> 参照。
=item B<--csv>
-Write out the results in CSV format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read L</NOTE
-ABOUT CSV FORMAT> below.
+Write out the results in CSV format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read L</NOTE ABOUT CSV FORMAT> below.
=item B<-d> guest
=item B<--echo-keys>
-キーやパスフレーズを入力するとき、通常 virt-filesystems はエコーを無効化します。 そのため、入力内容を確認できません。
-テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-filesystems はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
=item B<--extra>
-This causes filesystems that are not ordinary, mountable filesystems to be
-displayed. This category includes swapspace, and filesystems that are empty
-or contain unknown data.
+This causes filesystems that are not ordinary, mountable filesystems to be displayed. This category includes swapspace, and filesystems that are empty or contain unknown data.
このオプションは I<--filesystems> を意味します。
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-filesystems --format=raw -a disk.img --format -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<-h>
A title row is added unless you also specify I<--no-title>.
-The extra columns displayed depend on what output you select, and the
-ordering of columns may change in future versions. Use the title row,
-I<--csv> output and/or L<csvtool(1)> to match columns to data in external
-programs.
+The extra columns displayed depend on what output you select, and the ordering of columns may change in future versions. Use the title row, I<--csv> output and/or L<csvtool(1)> to match columns to data in external programs.
-Use I<-h> if you want sizes to be displayed in human-readable format. The
-default is to show raw numbers of I<bytes>.
+Use I<-h> if you want sizes to be displayed in human-readable format. The default is to show raw numbers of I<bytes>.
UUID も表示するには I<--uuid> を使用します。
In I<--long> mode, don’t add a title row.
-Note that the order of the columns is not fixed, and may change in future
-versions of virt-filesystems, so using this option may give you unexpected
-surprises.
+Note that the order of the columns is not fixed, and may change in future versions of virt-filesystems, so using this option may give you unexpected surprises.
=item B<--parts>
ファイルシステム、パーティション、ブロックデバイスまたは LVM の名前。
-For device and partition names these are displayed as canonical libguestfs
-names, so that for example F</dev/sda2> is the second partition on the first
-device.
+For device and partition names these are displayed as canonical libguestfs names, so that for example F</dev/sda2> is the second partition on the first device.
I<--long> オプションが指定されてB<いない>と、名前の列のみが出力に表示されます。
=item B<MBR>
-パーティション形式のバイト、2 桁の 16 進数として表示されます。パーティション形式の完全な一覧は次のところにあります:
-L<http://www.win.tue.nl/~aeb/partitions/partition_types-1.html>
+パーティション形式のバイト、2 桁の 16 進数として表示されます。パーティション形式の完全な一覧は次のところにあります: L<http://www.win.tue.nl/~aeb/partitions/partition_types-1.html>
これは DOS (MBR) パーティションに対してのみ適用できます。
=item B<UUID>
-If the object has a UUID (used for identifying and mounting filesystems and
-block devices) then this column contains the UUID as a string.
+If the object has a UUID (used for identifying and mounting filesystems and block devices) then this column contains the UUID as a string.
I<--uuid> オプションが指定されると、 UUID のみが表示されます。
=head1 CSV 形式に関する注意
-Comma-separated values (CSV) is a deceptive format. It I<seems> like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (CSV) is a deceptive format. It I<seems> like it should be easy to parse, but it is definitely not easy to parse.
神話: ただコンマで項目を区切る。 真実: これは正しく動き I<ません>。この例は 2 つの列があります:
"foo
bar",baz
-For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv>
-also packaged in major Linux distributions).
+For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv> also packaged in major Linux distributions).
-For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl
-or Python’s built-in csv library).
+For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl or Python’s built-in csv library).
Most spreadsheets and databases can import CSV directly.
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-df(1)>,
-L<virt-list-filesystems(1)>, L<virt-list-partitions(1)>, L<csvtool(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-df(1)>, L<virt-list-filesystems(1)>, L<virt-list-partitions(1)>, L<csvtool(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-format 1"
-.TH virt-format 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-format 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-format takes an existing disk file (or it can be a host partition, \s-1LV\s0
-etc), \fBerases all data on it\fR, and formats it as a blank disk. It can
-optionally create partition tables, empty filesystems, logical volumes and
-more.
+Virt-format takes an existing disk file (or it can be a host partition, \s-1LV\s0 etc), \fBerases all data on it\fR, and formats it as a blank disk. It can optionally create partition tables, empty filesystems, logical volumes and more.
.PP
-To create a disk containing data, you may be better to use
-\&\fBvirt\-make\-fs\fR\|(1). If you are creating a blank disk to use in
-\&\fBguestfish\fR\|(1), you should instead use the guestfish \fI\-N\fR option.
+To create a disk containing data, you may be better to use \fBvirt\-make\-fs\fR\|(1). If you are creating a blank disk to use in \fBguestfish\fR\|(1), you should instead use the guestfish \fI\-N\fR option.
.PP
通常の使用方法はこのようになります:
.PP
\& virt\-format \-a /dev/VG/LV
.Ve
.PP
-\&\fIdisk.qcow\fR or \fI/dev/VG/LV\fR must exist already. \fBAny data on these disks
-will be erased by these commands\fR. These commands will create a single
-empty partition covering the whole disk, with no filesystem inside it.
+\&\fIdisk.qcow\fR or \fI/dev/VG/LV\fR must exist already. \fBAny data on these disks will be erased by these commands\fR. These commands will create a single empty partition covering the whole disk, with no filesystem inside it.
.PP
-Additional parameters can be used to control the creation of partitions,
-filesystems, etc. The most commonly used options are:
+Additional parameters can be used to control the creation of partitions, filesystems, etc. The most commonly used options are:
.IP "\fB\-\-filesystem=[ext3|ntfs|vfat|...]\fR" 4
.IX Item "--filesystem=[ext3|ntfs|vfat|...]"
Create an empty filesystem (\f(CW\*(C`ext3\*(C'\fR, \f(CW\*(C`ntfs\*(C'\fR etc) inside the partition.
.IP "\fB\-\-lvm[=/dev/VG/LV]\fR" 4
.IX Item "--lvm[=/dev/VG/LV]"
-Create a Linux \s-1LVM2\s0 logical volume on the disk. When used with
-\&\fI\-\-filesystem\fR, the filesystem is created inside the \s-1LV.\s0
+Create a Linux \s-1LVM2\s0 logical volume on the disk. When used with \fI\-\-filesystem\fR, the filesystem is created inside the \s-1LV.\s0
.PP
For more information about these and other options, see \*(L"\s-1OPTIONS\*(R"\s0 below.
.PP
-The format of the disk is normally auto-detected, but you can also force it
-by using the \fI\-\-format\fR option (q.v.). In situations where you do not
-trust the existing content of the disk, then it is advisable to use this
-option to avoid possible exploits.
+The format of the disk is normally auto-detected, but you can also force it by using the \fI\-\-format\fR option (q.v.). In situations where you do not trust the existing content of the disk, then it is advisable to use this option to avoid possible exploits.
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-filesystem=ext3|ntfs|vfat|...\fR" 4
.IX Item "--filesystem=ext3|ntfs|vfat|..."
-Create an empty filesystem of the specified type. Many filesystem types are
-supported by libguestfs.
+Create an empty filesystem of the specified type. Many filesystem types are supported by libguestfs.
.IP "\fB\-\-filesystem=none\fR" 4
.IX Item "--filesystem=none"
ファイルシステムを作成しません。 これがデフォルトです。
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-format \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-label=\fR\s-1LABEL\s0" 4
.IX Item "--label=LABEL"
Set the filesystem label.
.IP "\fB\-\-lvm=/dev/\f(BI\s-1VG\s0\fB/\f(BI\s-1LV\s0\fB\fR" 4
.IX Item "--lvm=/dev/VG/LV"
-Create a Linux \s-1LVM2\s0 logical volume called \fI/dev/\fI\s-1VG\s0\fI/\fI\s-1LV\s0\fI\fR. You can
-change the name of the volume group and logical volume.
+Create a Linux \s-1LVM2\s0 logical volume called \fI/dev/\fI\s-1VG\s0\fI/\fI\s-1LV\s0\fI\fR. You can change the name of the volume group and logical volume.
.IP "\fB\-\-lvm\fR" 4
.IX Item "--lvm"
Create a Linux \s-1LVM2\s0 logical volume with the default name (\fI/dev/VG/LV\fR).
論理ボリュームを作成しません。 これがデフォルトです。
.IP "\fB\-\-partition\fR" 4
.IX Item "--partition"
-ディスク全体をカバーする \s-1MBR\s0 または \s-1GPT\s0 パーティションを作成します。ディスク容量が < 2 \s-1TB\s0 ならば \s-1MBR\s0
-が選択されます。容量が ≥ 2 \s-1TB\s0 ならば \s-1GPT\s0 が選択されます。
+ディスク全体をカバーする \s-1MBR\s0 または \s-1GPT\s0 パーティションを作成します。ディスク容量が < 2 \s-1TB\s0 ならば \s-1MBR\s0 が選択されます。容量が ≥ 2 \s-1TB\s0 ならば \s-1GPT\s0 が選択されます。
.Sp
これがデフォルトです。
.IP "\fB\-\-partition=gpt\fR" 4
バージョン番号を表示して、終了します。
.IP "\fB\-\-wipe\fR" 4
.IX Item "--wipe"
-Normally virt-format does not wipe data from the disk (because that takes a
-long time). Thus if there is data on the disk, it is only hidden and
-partially overwritten by virt-format, and it might be recovered by disk
-editing tools.
+Normally virt-format does not wipe data from the disk (because that takes a long time). Thus if there is data on the disk, it is only hidden and partially overwritten by virt-format, and it might be recovered by disk editing tools.
.Sp
-If you use this option, virt-format writes zeroes over the whole disk so
-that previous data is not recoverable.
+If you use this option, virt-format writes zeroes over the whole disk so that previous data is not recoverable.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
このプログラムは、成功すると \f(CW0\fR、失敗すると \f(CW1\fR を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-make\-fs\fR\|(1),
-\&\fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-format takes an existing disk file (or it can be a host partition, LV
-etc), B<erases all data on it>, and formats it as a blank disk. It can
-optionally create partition tables, empty filesystems, logical volumes and
-more.
+Virt-format takes an existing disk file (or it can be a host partition, LV etc), B<erases all data on it>, and formats it as a blank disk. It can optionally create partition tables, empty filesystems, logical volumes and more.
-To create a disk containing data, you may be better to use
-L<virt-make-fs(1)>. If you are creating a blank disk to use in
-L<guestfish(1)>, you should instead use the guestfish I<-N> option.
+To create a disk containing data, you may be better to use L<virt-make-fs(1)>. If you are creating a blank disk to use in L<guestfish(1)>, you should instead use the guestfish I<-N> option.
通常の使用方法はこのようになります:
virt-format -a /dev/VG/LV
-F<disk.qcow> or F</dev/VG/LV> must exist already. B<Any data on these disks
-will be erased by these commands>. These commands will create a single
-empty partition covering the whole disk, with no filesystem inside it.
+F<disk.qcow> or F</dev/VG/LV> must exist already. B<Any data on these disks will be erased by these commands>. These commands will create a single empty partition covering the whole disk, with no filesystem inside it.
-Additional parameters can be used to control the creation of partitions,
-filesystems, etc. The most commonly used options are:
+Additional parameters can be used to control the creation of partitions, filesystems, etc. The most commonly used options are:
=over 4
=item B<--lvm[=/dev/VG/LV]>
-Create a Linux LVM2 logical volume on the disk. When used with
-I<--filesystem>, the filesystem is created inside the LV.
+Create a Linux LVM2 logical volume on the disk. When used with I<--filesystem>, the filesystem is created inside the LV.
=back
For more information about these and other options, see L</OPTIONS> below.
-The format of the disk is normally auto-detected, but you can also force it
-by using the I<--format> option (q.v.). In situations where you do not
-trust the existing content of the disk, then it is advisable to use this
-option to avoid possible exploits.
+The format of the disk is normally auto-detected, but you can also force it by using the I<--format> option (q.v.). In situations where you do not trust the existing content of the disk, then it is advisable to use this option to avoid possible exploits.
=head1 オプション
=item B<--filesystem=ext3|ntfs|vfat|...>
-Create an empty filesystem of the specified type. Many filesystem types are
-supported by libguestfs.
+Create an empty filesystem of the specified type. Many filesystem types are supported by libguestfs.
=item B<--filesystem=none>
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-format --format=raw -a disk.img --format -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<--label=>LABEL
=item B<--lvm=/dev/I<VG>/I<LV>>
-Create a Linux LVM2 logical volume called F</dev/I<VG>/I<LV>>. You can
-change the name of the volume group and logical volume.
+Create a Linux LVM2 logical volume called F</dev/I<VG>/I<LV>>. You can change the name of the volume group and logical volume.
=item B<--lvm>
=item B<--partition>
-ディスク全体をカバーする MBR または GPT パーティションを作成します。ディスク容量が E<lt> 2 TB ならば MBR
-が選択されます。容量が E<ge> 2 TB ならば GPT が選択されます。
+ディスク全体をカバーする MBR または GPT パーティションを作成します。ディスク容量が E<lt> 2 TB ならば MBR が選択されます。容量が E<ge> 2 TB ならば GPT が選択されます。
これがデフォルトです。
=item B<--wipe>
-Normally virt-format does not wipe data from the disk (because that takes a
-long time). Thus if there is data on the disk, it is only hidden and
-partially overwritten by virt-format, and it might be recovered by disk
-editing tools.
+Normally virt-format does not wipe data from the disk (because that takes a long time). Thus if there is data on the disk, it is only hidden and partially overwritten by virt-format, and it might be recovered by disk editing tools.
-If you use this option, virt-format writes zeroes over the whole disk so
-that previous data is not recoverable.
+If you use this option, virt-format writes zeroes over the whole disk so that previous data is not recoverable.
=item B<-x>
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-make-fs(1)>,
-L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-make-fs(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-get-kernel 1"
-.TH virt-get-kernel 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-get-kernel 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.IX Header "説明"
This option extracts the kernel and initramfs from a guest.
.PP
-The format of the disk image is automatically detected unless you specify it
-by using the \fI\-\-format\fR option.
+The format of the disk image is automatically detected unless you specify it by using the \fI\-\-format\fR option.
.PP
-In the case where the guest contains multiple kernels, the one with the
-highest version number is chosen. To extract arbitrary kernels from the
-disk image, see \fBguestfish\fR\|(1). To extract the entire \f(CW\*(C`/boot\*(C'\fR directory
-of a guest, see \fBvirt\-copy\-out\fR\|(1).
+In the case where the guest contains multiple kernels, the one with the highest version number is chosen. To extract arbitrary kernels from the disk image, see \fBguestfish\fR\|(1). To extract the entire \f(CW\*(C`/boot\*(C'\fR directory of a guest, see \fBvirt\-copy\-out\fR\|(1).
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR \s-1URI\s0" 4
.IX Item "--add URI"
.PD
-Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See
-\&\*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
+Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See \*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
.IP "\fB\-\-blocksize\fR \fB512\fR" 4
.IX Item "--blocksize 512"
.PD 0
.IP "\fB\-\-blocksize\fR \fB4096\fR" 4
.IX Item "--blocksize 4096"
.PD
-This parameter sets the sector size of the disk image added with \fI\-a\fR
-option and is ignored for libvirt guest added with \fI\-d\fR option. See also
-\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
+This parameter sets the sector size of the disk image added with \fI\-a\fR option and is ignored for libvirt guest added with \fI\-d\fR option. See also \*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-c\fR \s-1URI\s0" 4
.IX Item "-c URI"
.PD 0
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-get-kernel normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-get-kernel normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-The default for the \fI\-a\fR option is to auto-detect the format of the disk
-image. Using this forces the disk format for the \fI\-a\fR option on the
-command line.
+The default for the \fI\-a\fR option is to auto-detect the format of the disk image. Using this forces the disk format for the \fI\-a\fR option on the command line.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IP "\fB\-\-output\fR directory" 4
.IX Item "--output directory"
.PD
-This option specifies the output directory where kernel and initramfs from
-the guest are written.
+This option specifies the output directory where kernel and initramfs from the guest are written.
.Sp
If not specified, the default output is the current directory.
.IP "\fB\-\-prefix\fR prefix" 4
.IX Item "--prefix prefix"
This option specifies a prefix for the extracted files.
.Sp
-If a prefix is specified, then there will be a dash (\f(CW\*(C`\-\*(C'\fR) after the prefix
-and before the rest of the file name; for example, a kernel in the guest
-like \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR is saved as
-\&\f(CW\*(C`mydistro\-vmlinuz\-3.19.0\-20\-generic\*(C'\fR when the prefix is \f(CW\*(C`mydistro\*(C'\fR.
+If a prefix is specified, then there will be a dash (\f(CW\*(C`\-\*(C'\fR) after the prefix and before the rest of the file name; for example, a kernel in the guest like \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR is saved as \f(CW\*(C`mydistro\-vmlinuz\-3.19.0\-20\-generic\*(C'\fR when the prefix is \f(CW\*(C`mydistro\*(C'\fR.
.Sp
See also \fI\-\-unversioned\-names\fR.
.IP "\fB\-q\fR" 4
.IX Item "--unversioned-names"
This option affects the destination file name of extracted files.
.Sp
-If enabled, files will be saved locally just with the base name; for
-example, kernel and ramdisk in the guest like \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR
-and \f(CW\*(C`initrd.img\-3.19.0\-20\-generic\*(C'\fR are saved respectively as \f(CW\*(C`vmlinuz\*(C'\fR and
-\&\f(CW\*(C`initrd.img\*(C'\fR.
+If enabled, files will be saved locally just with the base name; for example, kernel and ramdisk in the guest like \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR and \f(CW\*(C`initrd.img\-3.19.0\-20\-generic\*(C'\fR are saved respectively as \f(CW\*(C`vmlinuz\*(C'\fR and \f(CW\*(C`initrd.img\*(C'\fR.
.Sp
See also \fI\-\-prefix\fR.
.IP "\fB\-v\fR" 4
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.SH "マシン可読な出力"
.IX Header "マシン可読な出力"
-The \fI\-\-machine\-readable\fR option can be used to make the output more machine
-friendly, which is useful when calling virt-get-kernel from other programs,
-GUIs etc.
+The \fI\-\-machine\-readable\fR option can be used to make the output more machine friendly, which is useful when calling virt-get-kernel from other programs, GUIs etc.
.PP
-Use the option on its own to query the capabilities of the virt-get-kernel
-binary. Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-get-kernel binary. Typical output looks like this:
.PP
.Vb 2
\& $ virt\-get\-kernel \-\-machine\-readable
\& virt\-get\-kernel
.Ve
.PP
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
.PP
-It is possible to specify a format string for controlling the output; see
-\&\*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
+It is possible to specify a format string for controlling the output; see \*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "環境変数"
.IX Header "環境変数"
-For other environment variables which affect all libguestfs programs, see
-\&\*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+For other environment variables which affect all libguestfs programs, see \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-copy\-out\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
This option extracts the kernel and initramfs from a guest.
-The format of the disk image is automatically detected unless you specify it
-by using the I<--format> option.
+The format of the disk image is automatically detected unless you specify it by using the I<--format> option.
-In the case where the guest contains multiple kernels, the one with the
-highest version number is chosen. To extract arbitrary kernels from the
-disk image, see L<guestfish(1)>. To extract the entire C</boot> directory
-of a guest, see L<virt-copy-out(1)>.
+In the case where the guest contains multiple kernels, the one with the highest version number is chosen. To extract arbitrary kernels from the disk image, see L<guestfish(1)>. To extract the entire C</boot> directory of a guest, see L<virt-copy-out(1)>.
=head1 オプション
=item B<--add> URI
-Add a remote disk. The URI format is compatible with guestfish. See
-L<guestfish(1)/ADDING REMOTE STORAGE>.
+Add a remote disk. The URI format is compatible with guestfish. See L<guestfish(1)/ADDING REMOTE STORAGE>.
=item B<--blocksize> B<512>
=item B<--blocksize> B<4096>
-This parameter sets the sector size of the disk image added with I<-a>
-option and is ignored for libvirt guest added with I<-d> option. See also
-L<guestfs(3)/guestfs_add_drive_opts>.
+This parameter sets the sector size of the disk image added with I<-a> option and is ignored for libvirt guest added with I<-d> option. See also L<guestfs(3)/guestfs_add_drive_opts>.
=item B<--colors>
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<-c> URI
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-get-kernel normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-get-kernel normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-The default for the I<-a> option is to auto-detect the format of the disk
-image. Using this forces the disk format for the I<-a> option on the
-command line.
+The default for the I<-a> option is to auto-detect the format of the disk image. Using this forces the disk format for the I<-a> option on the command line.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
=item B<--output> directory
-This option specifies the output directory where kernel and initramfs from
-the guest are written.
+This option specifies the output directory where kernel and initramfs from the guest are written.
If not specified, the default output is the current directory.
This option specifies a prefix for the extracted files.
-If a prefix is specified, then there will be a dash (C<->) after the prefix
-and before the rest of the file name; for example, a kernel in the guest
-like C<vmlinuz-3.19.0-20-generic> is saved as
-C<mydistro-vmlinuz-3.19.0-20-generic> when the prefix is C<mydistro>.
+If a prefix is specified, then there will be a dash (C<->) after the prefix and before the rest of the file name; for example, a kernel in the guest like C<vmlinuz-3.19.0-20-generic> is saved as C<mydistro-vmlinuz-3.19.0-20-generic> when the prefix is C<mydistro>.
See also I<--unversioned-names>.
This option affects the destination file name of extracted files.
-If enabled, files will be saved locally just with the base name; for
-example, kernel and ramdisk in the guest like C<vmlinuz-3.19.0-20-generic>
-and C<initrd.img-3.19.0-20-generic> are saved respectively as C<vmlinuz> and
-C<initrd.img>.
+If enabled, files will be saved locally just with the base name; for example, kernel and ramdisk in the guest like C<vmlinuz-3.19.0-20-generic> and C<initrd.img-3.19.0-20-generic> are saved respectively as C<vmlinuz> and C<initrd.img>.
See also I<--prefix>.
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 マシン可読な出力
-The I<--machine-readable> option can be used to make the output more machine
-friendly, which is useful when calling virt-get-kernel from other programs,
-GUIs etc.
+The I<--machine-readable> option can be used to make the output more machine friendly, which is useful when calling virt-get-kernel from other programs, GUIs etc.
-Use the option on its own to query the capabilities of the virt-get-kernel
-binary. Typical output looks like this:
+Use the option on its own to query the capabilities of the virt-get-kernel binary. Typical output looks like this:
$ virt-get-kernel --machine-readable
virt-get-kernel
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 環境変数
-For other environment variables which affect all libguestfs programs, see
-L<guestfs(3)/ENVIRONMENT VARIABLES>.
+For other environment variables which affect all libguestfs programs, see L<guestfs(3)/ENVIRONMENT VARIABLES>.
=head1 終了ステータス
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-copy-out(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-copy-out(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-index-validate 1"
-.TH virt-index-validate 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-index-validate 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\fBvirt\-builder\fR\|(1) uses an index file to store metadata about templates that
-it knows how to use. This index file has a specific format which
-virt-index-validate knows how to validate.
+\&\fBvirt\-builder\fR\|(1) uses an index file to store metadata about templates that it knows how to use. This index file has a specific format which virt-index-validate knows how to validate.
.PP
-Note that virt-index-validate can validate either the signed or unsigned
-index file (ie. either \fIindex\fR or \fIindex.asc\fR). It can only validate a
-local file, not a \s-1URL.\s0
+Note that virt-index-validate can validate either the signed or unsigned index file (ie. either \fIindex\fR or \fIindex.asc\fR). It can only validate a local file, not a \s-1URL.\s0
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-compat\-1.24.0\fR" 4
.IX Item "--compat-1.24.0"
-Check for compatibility with virt-builder 1.24.0. (Using this option
-implies \fI\-\-compat\-1.24.1\fR, so you don't need to use both.)
+Check for compatibility with virt-builder 1.24.0. (Using this option implies \fI\-\-compat\-1.24.1\fR, so you don't need to use both.)
.Sp
In particular:
.RS 4
.IP "\(bu" 4
-This version of virt-builder could not handle \f(CW\*(C`[...]\*(C'\fR (square brackets) in
-field names (eg. \f(CW\*(C`checksum[sha512]=...\*(C'\fR).
+This version of virt-builder could not handle \f(CW\*(C`[...]\*(C'\fR (square brackets) in field names (eg. \f(CW\*(C`checksum[sha512]=...\*(C'\fR).
.IP "\(bu" 4
It required detached signatures (\f(CW\*(C`sig=...\*(C'\fR).
.RE
In particular:
.RS 4
.IP "\(bu" 4
-This version of virt-builder could not handle \f(CW\*(C`.\*(C'\fR (period) in field names
-or \f(CW\*(C`,\*(C'\fR (comma) in subfield names.
+This version of virt-builder could not handle \f(CW\*(C`.\*(C'\fR (period) in field names or \f(CW\*(C`,\*(C'\fR (comma) in subfield names.
.IP "\(bu" 4
It could not handle comments appearing in the file.
.RE
バージョン番号を表示して、終了します。
.SH "終了ステータス"
.IX Header "終了ステータス"
-This program returns 0 if the index file validates, or non-zero if there was
-an error.
+This program returns 0 if the index file validates, or non-zero if there was an error.
.SH "関連項目"
.IX Header "関連項目"
\&\fBvirt\-builder\fR\|(1), http://libguestfs.org/.
=head1 説明
-L<virt-builder(1)> uses an index file to store metadata about templates that
-it knows how to use. This index file has a specific format which
-virt-index-validate knows how to validate.
+L<virt-builder(1)> uses an index file to store metadata about templates that it knows how to use. This index file has a specific format which virt-index-validate knows how to validate.
-Note that virt-index-validate can validate either the signed or unsigned
-index file (ie. either F<index> or F<index.asc>). It can only validate a
-local file, not a URL.
+Note that virt-index-validate can validate either the signed or unsigned index file (ie. either F<index> or F<index.asc>). It can only validate a local file, not a URL.
=head1 オプション
=item B<--compat-1.24.0>
-Check for compatibility with virt-builder 1.24.0. (Using this option
-implies I<--compat-1.24.1>, so you don't need to use both.)
+Check for compatibility with virt-builder 1.24.0. (Using this option implies I<--compat-1.24.1>, so you don't need to use both.)
In particular:
=item *
-This version of virt-builder could not handle C<[...]> (square brackets) in
-field names (eg. C<checksum[sha512]=...>).
+This version of virt-builder could not handle C<[...]> (square brackets) in field names (eg. C<checksum[sha512]=...>).
=item *
=item *
-This version of virt-builder could not handle C<.> (period) in field names
-or C<,> (comma) in subfield names.
+This version of virt-builder could not handle C<.> (period) in field names or C<,> (comma) in subfield names.
=item *
=head1 終了ステータス
-This program returns 0 if the index file validates, or non-zero if there was
-an error.
+This program returns 0 if the index file validates, or non-zero if there was an error.
=head1 関連項目
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-inspector 1"
-.TH virt-inspector 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-inspector 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "名前"
.IX Header "名前"
-virt-inspector \- Display operating system version and other information
-about a virtual machine
+virt-inspector \- Display operating system version and other information about a virtual machine
.SH "書式"
.IX Header "書式"
.Vb 1
.Ve
.SH "説明"
.IX Header "説明"
-\&\fBvirt-inspector\fR examines a virtual machine or disk image and tries to
-determine the version of the operating system and other information about
-the virtual machine.
+\&\fBvirt-inspector\fR examines a virtual machine or disk image and tries to determine the version of the operating system and other information about the virtual machine.
.PP
Virt-inspector は他のプログラムに提供するための情報をXML形式出力で生成します。
.PP
-In the normal usage, use \f(CW\*(C`virt\-inspector \-d domname\*(C'\fR where \f(CW\*(C`domname\*(C'\fR is
-the libvirt domain (see: \f(CW\*(C`virsh list \-\-all\*(C'\fR).
+In the normal usage, use \f(CW\*(C`virt\-inspector \-d domname\*(C'\fR where \f(CW\*(C`domname\*(C'\fR is the libvirt domain (see: \f(CW\*(C`virsh list \-\-all\*(C'\fR).
.PP
-You can also run virt-inspector directly on disk images from a single
-virtual machine. Use \f(CW\*(C`virt\-inspector \-a disk.img\*(C'\fR. In rare cases a domain
-has several block devices, in which case you should list several \fI\-a\fR
-options one after another, with the first corresponding to the guest’s
-\&\fI/dev/sda\fR, the second to the guest’s \fI/dev/sdb\fR and so on.
+You can also run virt-inspector directly on disk images from a single virtual machine. Use \f(CW\*(C`virt\-inspector \-a disk.img\*(C'\fR. In rare cases a domain has several block devices, in which case you should list several \fI\-a\fR options one after another, with the first corresponding to the guest’s \fI/dev/sda\fR, the second to the guest’s \fI/dev/sdb\fR and so on.
.PP
-You can also run virt-inspector on install disks, live CDs, bootable \s-1USB\s0
-keys and similar.
+You can also run virt-inspector on install disks, live CDs, bootable \s-1USB\s0 keys and similar.
.PP
-Virt-inspector can only inspect and report upon \fIone domain at a time\fR. To
-inspect several virtual machines, you have to run virt-inspector several
-times (for example, from a shell script for-loop).
+Virt-inspector can only inspect and report upon \fIone domain at a time\fR. To inspect several virtual machines, you have to run virt-inspector several times (for example, from a shell script for-loop).
.PP
-Because virt-inspector needs direct access to guest images, it won’t
-normally work over remote libvirt connections.
+Because virt-inspector needs direct access to guest images, it won’t normally work over remote libvirt connections.
.PP
-All of the information available from virt-inspector is also available
-through the core libguestfs inspection \s-1API\s0 (see \*(L"\s-1INSPECTION\*(R"\s0 in \fBguestfs\fR\|(3)).
-The same information can also be fetched using guestfish or via libguestfs
-bindings in many programming languages (see \*(L"\s-1GETTING INSPECTION DATA FROM
-THE LIBGUESTFS API\*(R"\s0).
+All of the information available from virt-inspector is also available through the core libguestfs inspection \s-1API\s0 (see \*(L"\s-1INSPECTION\*(R"\s0 in \fBguestfs\fR\|(3)). The same information can also be fetched using guestfish or via libguestfs bindings in many programming languages (see \*(L"\s-1GETTING INSPECTION DATA FROM THE LIBGUESTFS API\*(R"\s0).
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a\fR \s-1URI\s0" 4
.PD
libvirt を使用していると、指定された \fI\s-1URI\s0\fR に接続します。 省略すると、デフォルトの libvirt ハイパーバイザーに接続します。
.Sp
-Libvirt is only used if you specify a \f(CW\*(C`domname\*(C'\fR on the command line. If
-you specify guest block devices directly (\fI\-a\fR), then libvirt is not used
-at all.
+Libvirt is only used if you specify a \f(CW\*(C`domname\*(C'\fR on the command line. If you specify guest block devices directly (\fI\-a\fR), then libvirt is not used at all.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-キーやパスフレーズを入力するとき、通常 virt-inspector はエコーを無効化します。 そのため、入力内容を確認できません。
-テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-inspector はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Specify the format of disk images given on the command line. If this is
-omitted then the format is autodetected from the content of the disk image.
+Specify the format of disk images given on the command line. If this is omitted then the format is autodetected from the content of the disk image.
.Sp
-If disk images are requested from libvirt, then this program asks libvirt
-for this information. In this case, the value of the format parameter is
-ignored.
+If disk images are requested from libvirt, then this program asks libvirt for this information. In this case, the value of the format parameter is ignored.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
multiple keys on stdin, one per line.
.IP "\fB\-\-no\-applications\fR" 4
.IX Item "--no-applications"
-By default the output of virt-inspector includes the list of all the
-applications installed in the guest, if available.
+By default the output of virt-inspector includes the list of all the applications installed in the guest, if available.
.Sp
Specify this option to disable this part of the resulting \s-1XML.\s0
.IP "\fB\-\-no\-icon\fR" 4
.IX Item "--no-icon"
-By default the output of virt-inspector includes the icon of the guest, if
-available (see \*(L"icon\*(R").
+By default the output of virt-inspector includes the icon of the guest, if available (see \*(L"icon\*(R").
.Sp
Specify this option to disable this part of the resulting \s-1XML.\s0
.IP "\fB\-v\fR" 4
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.IP "\fB\-\-xpath\fR query" 4
.IX Item "--xpath query"
-Perform an XPath query on the \s-1XML\s0 on stdin, and print the result on stdout.
-In this mode virt-inspector simply runs an XPath query; all other inspection
-functions are disabled. See \*(L"\s-1XPATH QUERIES\*(R"\s0 below for some examples.
+Perform an XPath query on the \s-1XML\s0 on stdin, and print the result on stdout. In this mode virt-inspector simply runs an XPath query; all other inspection functions are disabled. See \*(L"\s-1XPATH QUERIES\*(R"\s0 below for some examples.
.SH "旧形式のコマンドライン引数"
.IX Header "旧形式のコマンドライン引数"
Previous versions of virt-inspector allowed you to write either:
\& virt\-inspector guestname
.Ve
.PP
-whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid the confusing case where a disk image might have the same name as a guest.
.PP
互換性のため古い形式がまだサポートされています。
.SH "XML フォーマット"
.IX Header "XML フォーマット"
-The virt-inspector \s-1XML\s0 is described precisely in a \s-1RELAX NG\s0 schema file
-\&\fIvirt\-inspector.rng\fR which is supplied with libguestfs. This section is
-just an overview.
-.PP
-The top-level element is <operatingsystems>, and it contains one or
-more <operatingsystem> elements. You would only see more than one
-<operatingsystem> element if the virtual machine is multi-boot,
-which is vanishingly rare in real world VMs.
+The virt-inspector \s-1XML\s0 is described precisely in a \s-1RELAX NG\s0 schema file \fIvirt\-inspector.rng\fR which is supplied with libguestfs. This section is just an overview.
+.PP
+The top-level element is <operatingsystems>, and it contains one or more <operatingsystem> elements. You would only see more than one <operatingsystem> element if the virtual machine is multi-boot, which is vanishingly rare in real world VMs.
.SS "<operatingsystem>"
.IX Subsection "<operatingsystem>"
-In the <operatingsystem> tag are various optional fields that
-describe the operating system, its architecture, the descriptive \*(L"product
-name\*(R" string, the type of \s-1OS\s0 and so on, as in this example:
+In the <operatingsystem> tag are various optional fields that describe the operating system, its architecture, the descriptive \*(L"product name\*(R" string, the type of \s-1OS\s0 and so on, as in this example:
.PP
.Vb 11
\& <operatingsystems>
\& <windows_systemroot>/Windows</windows_systemroot>
.Ve
.PP
-In brief, <name> is the class of operating system (something like
-\&\f(CW\*(C`linux\*(C'\fR or \f(CW\*(C`windows\*(C'\fR), <distro> is the distribution (eg. \f(CW\*(C`fedora\*(C'\fR
-but many other distros are recognized) and <arch> is the guest
-architecture. The other fields are fairly self-explanatory, but because
-these fields are taken directly from the libguestfs inspection \s-1API\s0 you can
-find precise information from \*(L"\s-1INSPECTION\*(R"\s0 in \fBguestfs\fR\|(3).
+In brief, <name> is the class of operating system (something like \f(CW\*(C`linux\*(C'\fR or \f(CW\*(C`windows\*(C'\fR), <distro> is the distribution (eg. \f(CW\*(C`fedora\*(C'\fR but many other distros are recognized) and <arch> is the guest architecture. The other fields are fairly self-explanatory, but because these fields are taken directly from the libguestfs inspection \s-1API\s0 you can find precise information from \*(L"\s-1INSPECTION\*(R"\s0 in \fBguestfs\fR\|(3).
.PP
-The <root> element is the root filesystem device, but from the point
-of view of libguestfs (block devices may have completely different names
-inside the \s-1VM\s0 itself).
+The <root> element is the root filesystem device, but from the point of view of libguestfs (block devices may have completely different names inside the \s-1VM\s0 itself).
.SS "<mountpoints>"
.IX Subsection "<mountpoints>"
-Un*x\-like guests typically have multiple filesystems which are mounted at
-various mountpoints, and these are described in the <mountpoints>
-element which looks like this:
+Un*x\-like guests typically have multiple filesystems which are mounted at various mountpoints, and these are described in the <mountpoints> element which looks like this:
.PP
.Vb 7
\& <operatingsystems>
\& </mountpoints>
.Ve
.PP
-As with <root>, devices are from the point of view of libguestfs,
-and may have completely different names inside the guest. Only mountable
-filesystems appear in this list, not things like swap devices.
+As with <root>, devices are from the point of view of libguestfs, and may have completely different names inside the guest. Only mountable filesystems appear in this list, not things like swap devices.
.SS "<filesystems>"
.IX Subsection "<filesystems>"
-<filesystems> is like <mountpoints> but covers \fIall\fR
-filesystems belonging to the guest, including swap and empty partitions.
-(In the rare case of a multi-boot guest, it covers filesystems belonging to
-this \s-1OS\s0 or shared with this \s-1OS\s0 and other OSes).
+<filesystems> is like <mountpoints> but covers \fIall\fR filesystems belonging to the guest, including swap and empty partitions. (In the rare case of a multi-boot guest, it covers filesystems belonging to this \s-1OS\s0 or shared with this \s-1OS\s0 and other OSes).
.PP
次のように表示されることがあります:
.PP
\& </filesystem>
.Ve
.PP
-The optional elements within <filesystem> are the filesystem type,
-the label, and the \s-1UUID.\s0
+The optional elements within <filesystem> are the filesystem type, the label, and the \s-1UUID.\s0
.SS "<applications>"
.IX Subsection "<applications>"
-関連する要素 <package_format>, <package_management> および
-<applications> は仮想マシンにインストールされたアプリケーションを記述しています。
+関連する要素 <package_format>, <package_management> および <applications> は仮想マシンにインストールされたアプリケーションを記述しています。
.PP
-<package_format>, if present, describes the packaging system used.
-Typical values would be \f(CW\*(C`rpm\*(C'\fR and \f(CW\*(C`deb\*(C'\fR.
+<package_format>, if present, describes the packaging system used. Typical values would be \f(CW\*(C`rpm\*(C'\fR and \f(CW\*(C`deb\*(C'\fR.
.PP
-<package_management>, if present, describes the package manager.
-Typical values include \f(CW\*(C`yum\*(C'\fR, \f(CW\*(C`up2date\*(C'\fR and \f(CW\*(C`apt\*(C'\fR
+<package_management>, if present, describes the package manager. Typical values include \f(CW\*(C`yum\*(C'\fR, \f(CW\*(C`up2date\*(C'\fR and \f(CW\*(C`apt\*(C'\fR
.PP
<applications> lists the packages or applications installed.
.PP
\& </application>
.Ve
.PP
-The version and release fields may not be available for some types guests.
-Other fields are possible, see
-\&\*(L"guestfs_inspect_list_applications\*(R" in \fBguestfs\fR\|(3).
+The version and release fields may not be available for some types guests. Other fields are possible, see \*(L"guestfs_inspect_list_applications\*(R" in \fBguestfs\fR\|(3).
.SS "<drive_mappings>"
.IX Subsection "<drive_mappings>"
-For operating systems like Windows which use drive letters, virt-inspector
-is able to find out how drive letters map to filesystems.
+For operating systems like Windows which use drive letters, virt-inspector is able to find out how drive letters map to filesystems.
.PP
.Vb 7
\& <operatingsystems>
\& </drive_mappings>
.Ve
.PP
-In the example above, drive C maps to the filesystem on the second partition
-on the first disk, and drive E maps to the filesystem on the first partition
-on the second disk.
+In the example above, drive C maps to the filesystem on the second partition on the first disk, and drive E maps to the filesystem on the first partition on the second disk.
.PP
-Note that this only covers permanent local filesystem mappings, not things
-like network shares. Furthermore \s-1NTFS\s0 volume mount points may not be listed
-here.
+Note that this only covers permanent local filesystem mappings, not things like network shares. Furthermore \s-1NTFS\s0 volume mount points may not be listed here.
.SS "<icon>"
.IX Subsection "<icon>"
-Virt-inspector is sometimes able to extract an icon or logo for the guest.
-The icon is returned as base64\-encoded \s-1PNG\s0 data. Note that the icon can be
-very large and high quality.
+Virt-inspector is sometimes able to extract an icon or logo for the guest. The icon is returned as base64\-encoded \s-1PNG\s0 data. Note that the icon can be very large and high quality.
.PP
.Vb 7
\& <operatingsystems>
\& </icon>
.Ve
.PP
-To display the icon, you have to extract it and convert the base64 data back
-to a binary file. Use an XPath query or simply an editor to extract the
-data, then use the coreutils \fBbase64\fR\|(1) program to do the conversion back
-to a \s-1PNG\s0 file:
+To display the icon, you have to extract it and convert the base64 data back to a binary file. Use an XPath query or simply an editor to extract the data, then use the coreutils \fBbase64\fR\|(1) program to do the conversion back to a \s-1PNG\s0 file:
.PP
.Vb 1
\& base64 \-i \-d < icon.data > icon.png
.Ve
.SH "XPath クエリー"
.IX Header "XPath クエリー"
-Virt-inspector includes built in support for running XPath queries. The
-reason for including XPath support directly in virt-inspector is simply that
-there are no good and widely available command line programs that can do
-XPath queries. The only good one is \fBxmlstarlet\fR\|(1) and that is not
-available on Red Hat Enterprise Linux.
+Virt-inspector includes built in support for running XPath queries. The reason for including XPath support directly in virt-inspector is simply that there are no good and widely available command line programs that can do XPath queries. The only good one is \fBxmlstarlet\fR\|(1) and that is not available on Red Hat Enterprise Linux.
.PP
-To perform an XPath query, use the \fI\-\-xpath\fR option. Note that in this
-mode, virt-inspector simply reads \s-1XML\s0 from stdin and outputs the query
-result on stdout. All other inspection features are disabled in this mode.
+To perform an XPath query, use the \fI\-\-xpath\fR option. Note that in this mode, virt-inspector simply reads \s-1XML\s0 from stdin and outputs the query result on stdout. All other inspection features are disabled in this mode.
.PP
例:
.PP
.Ve
.SH "GETTING INSPECTION DATA FROM THE LIBGUESTFS API"
.IX Header "GETTING INSPECTION DATA FROM THE LIBGUESTFS API"
-In early versions of libguestfs, virt-inspector was a large Perl script that
-contained many heuristics for inspecting guests. This had several problems:
-in order to do inspection from other tools (like guestfish) we had to call
-out to this Perl script; and it privileged Perl over other languages that
-libguestfs supports.
-.PP
-By libguestfs 1.8 we had rewritten the Perl code in C, and incorporated it
-all into the core libguestfs \s-1API\s0 (\fBguestfs\fR\|(3)). Now virt-inspector is
-simply a thin C program over the core C \s-1API.\s0 All of the inspection
-information is available from all programming languages that libguestfs
-supports, and from guestfish.
+In early versions of libguestfs, virt-inspector was a large Perl script that contained many heuristics for inspecting guests. This had several problems: in order to do inspection from other tools (like guestfish) we had to call out to this Perl script; and it privileged Perl over other languages that libguestfs supports.
+.PP
+By libguestfs 1.8 we had rewritten the Perl code in C, and incorporated it all into the core libguestfs \s-1API\s0 (\fBguestfs\fR\|(3)). Now virt-inspector is simply a thin C program over the core C \s-1API.\s0 All of the inspection information is available from all programming languages that libguestfs supports, and from guestfish.
.PP
For a description of the C inspection \s-1API,\s0 read \*(L"\s-1INSPECTION\*(R"\s0 in \fBguestfs\fR\|(3).
.PP
-For example code using the C inspection \s-1API,\s0 look for \fIinspect\-vm.c\fR which
-ships with libguestfs.
+For example code using the C inspection \s-1API,\s0 look for \fIinspect\-vm.c\fR which ships with libguestfs.
.PP
-\&\fIinspect\-vm.c\fR has also been translated into other languages. For example,
-\&\fIinspect_vm.pl\fR is the Perl translation, and there are other translations
-for OCaml, Python, etc. See \*(L"\s-1USING LIBGUESTFS WITH OTHER
-PROGRAMMING LANGUAGES\*(R"\s0 in \fBguestfs\fR\|(3) for a list of man pages which contain this example
-code.
+\&\fIinspect\-vm.c\fR has also been translated into other languages. For example, \fIinspect_vm.pl\fR is the Perl translation, and there are other translations for OCaml, Python, etc. See \*(L"\s-1USING LIBGUESTFS WITH OTHER PROGRAMMING LANGUAGES\*(R"\s0 in \fBguestfs\fR\|(3) for a list of man pages which contain this example code.
.SS "\s-1GETTING INSPECTION DATA FROM GUESTFISH\s0"
.IX Subsection "GETTING INSPECTION DATA FROM GUESTFISH"
-If you use the guestfish \fI\-i\fR option, then the main C inspection \s-1API\s0
-\&\*(L"guestfs_inspect_os\*(R" in \fBguestfs\fR\|(3) is called. This is equivalent to the
-guestfish command \f(CW\*(C`inspect\-os\*(C'\fR. You can also call this guestfish command
-by hand.
-.PP
-\&\f(CW\*(C`inspect\-os\*(C'\fR performs inspection on the current disk image, returning the
-list of operating systems found. Each \s-1OS\s0 is represented by its root
-filesystem device. In the majority of cases, this command prints nothing
-(no OSes found), or a single root device, but beware that it can print
-multiple lines if there are multiple OSes or if there is an install \s-1CD\s0
-attached to the guest.
+If you use the guestfish \fI\-i\fR option, then the main C inspection \s-1API\s0 \*(L"guestfs_inspect_os\*(R" in \fBguestfs\fR\|(3) is called. This is equivalent to the guestfish command \f(CW\*(C`inspect\-os\*(C'\fR. You can also call this guestfish command by hand.
+.PP
+\&\f(CW\*(C`inspect\-os\*(C'\fR performs inspection on the current disk image, returning the list of operating systems found. Each \s-1OS\s0 is represented by its root filesystem device. In the majority of cases, this command prints nothing (no OSes found), or a single root device, but beware that it can print multiple lines if there are multiple OSes or if there is an install \s-1CD\s0 attached to the guest.
.PP
.Vb 4
\& $ guestfish \-\-ro \-a F15x32.img
\& Fedora release 15 (Lovelock)
.Ve
.PP
-Limitations of guestfish make it hard to assign the root device to a
-variable (since guestfish doesn't have variables), so if you want to do this
-reproducibly you are better off writing a script using one of the other
-languages that the libguestfs \s-1API\s0 supports.
+Limitations of guestfish make it hard to assign the root device to a variable (since guestfish doesn't have variables), so if you want to do this reproducibly you are better off writing a script using one of the other languages that the libguestfs \s-1API\s0 supports.
.PP
アプリケーションを一覧表示するには、まずディスクをマウントする必要があります:
.PP
\& }
.Ve
.PP
-To display an icon for the guest, note that filesystems must also be mounted
-as above. You can then do:
+To display an icon for the guest, note that filesystems must also be mounted as above. You can then do:
.PP
.Vb 1
\& ><fs> inspect\-get\-icon /dev/vg_f15x32/lv_root | display \-
.Ve
.SH "古いバージョンの virt-inspector"
.IX Header "古いバージョンの virt-inspector"
-As described above, early versions of libguestfs shipped with a different
-virt-inspector program written in Perl (the current version is written in
-C). The \s-1XML\s0 output of the Perl virt-inspector was different and it could
-also output in other formats like text.
+As described above, early versions of libguestfs shipped with a different virt-inspector program written in Perl (the current version is written in C). The \s-1XML\s0 output of the Perl virt-inspector was different and it could also output in other formats like text.
.PP
古い virt-inspector はもはや libguestfs でサポートされず、同梱されていません。
.PP
-さらに混乱することに、Red Hat Enterprise Linux 6 では異なる名前で 2 つのバージョンの virt-inspector
-が同梱されています:
+さらに混乱することに、Red Hat Enterprise Linux 6 では異なる名前で 2 つのバージョンの virt-inspector が同梱されています:
.PP
.Vb 2
\& virt\-inspector 古い Perl バージョンです。
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), http://www.w3.org/TR/xpath/,
-\&\fBbase64\fR\|(1), \fBxmlstarlet\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), http://www.w3.org/TR/xpath/, \fBbase64\fR\|(1), \fBxmlstarlet\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
.IP "\(bu" 4
=head1 名前
-virt-inspector - Display operating system version and other information
-about a virtual machine
+virt-inspector - Display operating system version and other information about a virtual machine
=head1 書式
=head1 説明
-B<virt-inspector> examines a virtual machine or disk image and tries to
-determine the version of the operating system and other information about
-the virtual machine.
+B<virt-inspector> examines a virtual machine or disk image and tries to determine the version of the operating system and other information about the virtual machine.
Virt-inspector は他のプログラムに提供するための情報をXML形式出力で生成します。
-In the normal usage, use C<virt-inspector -d domname> where C<domname> is
-the libvirt domain (see: C<virsh list --all>).
+In the normal usage, use C<virt-inspector -d domname> where C<domname> is the libvirt domain (see: C<virsh list --all>).
-You can also run virt-inspector directly on disk images from a single
-virtual machine. Use C<virt-inspector -a disk.img>. In rare cases a domain
-has several block devices, in which case you should list several I<-a>
-options one after another, with the first corresponding to the guest’s
-F</dev/sda>, the second to the guest’s F</dev/sdb> and so on.
+You can also run virt-inspector directly on disk images from a single virtual machine. Use C<virt-inspector -a disk.img>. In rare cases a domain has several block devices, in which case you should list several I<-a> options one after another, with the first corresponding to the guest’s F</dev/sda>, the second to the guest’s F</dev/sdb> and so on.
-You can also run virt-inspector on install disks, live CDs, bootable USB
-keys and similar.
+You can also run virt-inspector on install disks, live CDs, bootable USB keys and similar.
-Virt-inspector can only inspect and report upon I<one domain at a time>. To
-inspect several virtual machines, you have to run virt-inspector several
-times (for example, from a shell script for-loop).
+Virt-inspector can only inspect and report upon I<one domain at a time>. To inspect several virtual machines, you have to run virt-inspector several times (for example, from a shell script for-loop).
-Because virt-inspector needs direct access to guest images, it won’t
-normally work over remote libvirt connections.
+Because virt-inspector needs direct access to guest images, it won’t normally work over remote libvirt connections.
-All of the information available from virt-inspector is also available
-through the core libguestfs inspection API (see L<guestfs(3)/INSPECTION>).
-The same information can also be fetched using guestfish or via libguestfs
-bindings in many programming languages (see L</GETTING INSPECTION DATA FROM
-THE LIBGUESTFS API>).
+All of the information available from virt-inspector is also available through the core libguestfs inspection API (see L<guestfs(3)/INSPECTION>). The same information can also be fetched using guestfish or via libguestfs bindings in many programming languages (see L</GETTING INSPECTION DATA FROM THE LIBGUESTFS API>).
=head1 オプション
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
libvirt を使用していると、指定された I<URI> に接続します。 省略すると、デフォルトの libvirt ハイパーバイザーに接続します。
-Libvirt is only used if you specify a C<domname> on the command line. If
-you specify guest block devices directly (I<-a>), then libvirt is not used
-at all.
+Libvirt is only used if you specify a C<domname> on the command line. If you specify guest block devices directly (I<-a>), then libvirt is not used at all.
=item B<-d> guest
=item B<--echo-keys>
-キーやパスフレーズを入力するとき、通常 virt-inspector はエコーを無効化します。 そのため、入力内容を確認できません。
-テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-inspector はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
=item B<--format=raw|qcow2|..>
=item B<--format>
-Specify the format of disk images given on the command line. If this is
-omitted then the format is autodetected from the content of the disk image.
+Specify the format of disk images given on the command line. If this is omitted then the format is autodetected from the content of the disk image.
-If disk images are requested from libvirt, then this program asks libvirt
-for this information. In this case, the value of the format parameter is
-ignored.
+If disk images are requested from libvirt, then this program asks libvirt for this information. In this case, the value of the format parameter is ignored.
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
__INCLUDE:key-option.pod__
=item B<--no-applications>
-By default the output of virt-inspector includes the list of all the
-applications installed in the guest, if available.
+By default the output of virt-inspector includes the list of all the applications installed in the guest, if available.
Specify this option to disable this part of the resulting XML.
=item B<--no-icon>
-By default the output of virt-inspector includes the icon of the guest, if
-available (see L</icon>).
+By default the output of virt-inspector includes the icon of the guest, if available (see L</icon>).
Specify this option to disable this part of the resulting XML.
=item B<--xpath> query
-Perform an XPath query on the XML on stdin, and print the result on stdout.
-In this mode virt-inspector simply runs an XPath query; all other inspection
-functions are disabled. See L</XPATH QUERIES> below for some examples.
+Perform an XPath query on the XML on stdin, and print the result on stdout. In this mode virt-inspector simply runs an XPath query; all other inspection functions are disabled. See L</XPATH QUERIES> below for some examples.
=back
virt-inspector guestname
-whereas in this version you should use I<-a> or I<-d> respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use I<-a> or I<-d> respectively to avoid the confusing case where a disk image might have the same name as a guest.
互換性のため古い形式がまだサポートされています。
=head1 XML フォーマット
-The virt-inspector XML is described precisely in a RELAX NG schema file
-F<virt-inspector.rng> which is supplied with libguestfs. This section is
-just an overview.
+The virt-inspector XML is described precisely in a RELAX NG schema file F<virt-inspector.rng> which is supplied with libguestfs. This section is just an overview.
-The top-level element is E<lt>operatingsystemsE<gt>, and it contains one or
-more E<lt>operatingsystemE<gt> elements. You would only see more than one
-E<lt>operatingsystemE<gt> element if the virtual machine is multi-boot,
-which is vanishingly rare in real world VMs.
+The top-level element is E<lt>operatingsystemsE<gt>, and it contains one or more E<lt>operatingsystemE<gt> elements. You would only see more than one E<lt>operatingsystemE<gt> element if the virtual machine is multi-boot, which is vanishingly rare in real world VMs.
=head2 E<lt>operatingsystemE<gt>
-In the E<lt>operatingsystemE<gt> tag are various optional fields that
-describe the operating system, its architecture, the descriptive "product
-name" string, the type of OS and so on, as in this example:
+In the E<lt>operatingsystemE<gt> tag are various optional fields that describe the operating system, its architecture, the descriptive "product name" string, the type of OS and so on, as in this example:
<operatingsystems>
<operatingsystem>
<minor_version>1</minor_version>
<windows_systemroot>/Windows</windows_systemroot>
-In brief, E<lt>nameE<gt> is the class of operating system (something like
-C<linux> or C<windows>), E<lt>distroE<gt> is the distribution (eg. C<fedora>
-but many other distros are recognized) and E<lt>archE<gt> is the guest
-architecture. The other fields are fairly self-explanatory, but because
-these fields are taken directly from the libguestfs inspection API you can
-find precise information from L<guestfs(3)/INSPECTION>.
+In brief, E<lt>nameE<gt> is the class of operating system (something like C<linux> or C<windows>), E<lt>distroE<gt> is the distribution (eg. C<fedora> but many other distros are recognized) and E<lt>archE<gt> is the guest architecture. The other fields are fairly self-explanatory, but because these fields are taken directly from the libguestfs inspection API you can find precise information from L<guestfs(3)/INSPECTION>.
-The E<lt>rootE<gt> element is the root filesystem device, but from the point
-of view of libguestfs (block devices may have completely different names
-inside the VM itself).
+The E<lt>rootE<gt> element is the root filesystem device, but from the point of view of libguestfs (block devices may have completely different names inside the VM itself).
=head2 E<lt>mountpointsE<gt>
-Un*x-like guests typically have multiple filesystems which are mounted at
-various mountpoints, and these are described in the E<lt>mountpointsE<gt>
-element which looks like this:
+Un*x-like guests typically have multiple filesystems which are mounted at various mountpoints, and these are described in the E<lt>mountpointsE<gt> element which looks like this:
<operatingsystems>
<operatingsystem>
<mountpoint dev="/dev/sda1">/boot</mountpoint>
</mountpoints>
-As with E<lt>rootE<gt>, devices are from the point of view of libguestfs,
-and may have completely different names inside the guest. Only mountable
-filesystems appear in this list, not things like swap devices.
+As with E<lt>rootE<gt>, devices are from the point of view of libguestfs, and may have completely different names inside the guest. Only mountable filesystems appear in this list, not things like swap devices.
=head2 E<lt>filesystemsE<gt>
-E<lt>filesystemsE<gt> is like E<lt>mountpointsE<gt> but covers I<all>
-filesystems belonging to the guest, including swap and empty partitions.
-(In the rare case of a multi-boot guest, it covers filesystems belonging to
-this OS or shared with this OS and other OSes).
+E<lt>filesystemsE<gt> is like E<lt>mountpointsE<gt> but covers I<all> filesystems belonging to the guest, including swap and empty partitions. (In the rare case of a multi-boot guest, it covers filesystems belonging to this OS or shared with this OS and other OSes).
次のように表示されることがあります:
<uuid>e6a4db1e-15c2-477b-ac2a-699181c396aa</uuid>
</filesystem>
-The optional elements within E<lt>filesystemE<gt> are the filesystem type,
-the label, and the UUID.
+The optional elements within E<lt>filesystemE<gt> are the filesystem type, the label, and the UUID.
=head2 E<lt>applicationsE<gt>
-関連する要素 E<lt>package_formatE<gt>, E<lt>package_managementE<gt> および
-E<lt>applicationsE<gt> は仮想マシンにインストールされたアプリケーションを記述しています。
+関連する要素 E<lt>package_formatE<gt>, E<lt>package_managementE<gt> および E<lt>applicationsE<gt> は仮想マシンにインストールされたアプリケーションを記述しています。
-E<lt>package_formatE<gt>, if present, describes the packaging system used.
-Typical values would be C<rpm> and C<deb>.
+E<lt>package_formatE<gt>, if present, describes the packaging system used. Typical values would be C<rpm> and C<deb>.
-E<lt>package_managementE<gt>, if present, describes the package manager.
-Typical values include C<yum>, C<up2date> and C<apt>
+E<lt>package_managementE<gt>, if present, describes the package manager. Typical values include C<yum>, C<up2date> and C<apt>
E<lt>applicationsE<gt> lists the packages or applications installed.
<release>1</release>
</application>
-The version and release fields may not be available for some types guests.
-Other fields are possible, see
-L<guestfs(3)/guestfs_inspect_list_applications>.
+The version and release fields may not be available for some types guests. Other fields are possible, see L<guestfs(3)/guestfs_inspect_list_applications>.
=head2 E<lt>drive_mappingsE<gt>
-For operating systems like Windows which use drive letters, virt-inspector
-is able to find out how drive letters map to filesystems.
+For operating systems like Windows which use drive letters, virt-inspector is able to find out how drive letters map to filesystems.
<operatingsystems>
<operatingsystem>
<drive_mapping name="E">/dev/sdb1</drive_mapping>
</drive_mappings>
-In the example above, drive C maps to the filesystem on the second partition
-on the first disk, and drive E maps to the filesystem on the first partition
-on the second disk.
+In the example above, drive C maps to the filesystem on the second partition on the first disk, and drive E maps to the filesystem on the first partition on the second disk.
-Note that this only covers permanent local filesystem mappings, not things
-like network shares. Furthermore NTFS volume mount points may not be listed
-here.
+Note that this only covers permanent local filesystem mappings, not things like network shares. Furthermore NTFS volume mount points may not be listed here.
=head2 E<lt>iconE<gt>
-Virt-inspector is sometimes able to extract an icon or logo for the guest.
-The icon is returned as base64-encoded PNG data. Note that the icon can be
-very large and high quality.
+Virt-inspector is sometimes able to extract an icon or logo for the guest. The icon is returned as base64-encoded PNG data. Note that the icon can be very large and high quality.
<operatingsystems>
<operatingsystem>
[... many lines of base64 data ...]
</icon>
-To display the icon, you have to extract it and convert the base64 data back
-to a binary file. Use an XPath query or simply an editor to extract the
-data, then use the coreutils L<base64(1)> program to do the conversion back
-to a PNG file:
+To display the icon, you have to extract it and convert the base64 data back to a binary file. Use an XPath query or simply an editor to extract the data, then use the coreutils L<base64(1)> program to do the conversion back to a PNG file:
base64 -i -d < icon.data > icon.png
=head1 XPath クエリー
-Virt-inspector includes built in support for running XPath queries. The
-reason for including XPath support directly in virt-inspector is simply that
-there are no good and widely available command line programs that can do
-XPath queries. The only good one is L<xmlstarlet(1)> and that is not
-available on Red Hat Enterprise Linux.
+Virt-inspector includes built in support for running XPath queries. The reason for including XPath support directly in virt-inspector is simply that there are no good and widely available command line programs that can do XPath queries. The only good one is L<xmlstarlet(1)> and that is not available on Red Hat Enterprise Linux.
-To perform an XPath query, use the I<--xpath> option. Note that in this
-mode, virt-inspector simply reads XML from stdin and outputs the query
-result on stdout. All other inspection features are disabled in this mode.
+To perform an XPath query, use the I<--xpath> option. Note that in this mode, virt-inspector simply reads XML from stdin and outputs the query result on stdout. All other inspection features are disabled in this mode.
例:
=head1 GETTING INSPECTION DATA FROM THE LIBGUESTFS API
-In early versions of libguestfs, virt-inspector was a large Perl script that
-contained many heuristics for inspecting guests. This had several problems:
-in order to do inspection from other tools (like guestfish) we had to call
-out to this Perl script; and it privileged Perl over other languages that
-libguestfs supports.
+In early versions of libguestfs, virt-inspector was a large Perl script that contained many heuristics for inspecting guests. This had several problems: in order to do inspection from other tools (like guestfish) we had to call out to this Perl script; and it privileged Perl over other languages that libguestfs supports.
-By libguestfs 1.8 we had rewritten the Perl code in C, and incorporated it
-all into the core libguestfs API (L<guestfs(3)>). Now virt-inspector is
-simply a thin C program over the core C API. All of the inspection
-information is available from all programming languages that libguestfs
-supports, and from guestfish.
+By libguestfs 1.8 we had rewritten the Perl code in C, and incorporated it all into the core libguestfs API (L<guestfs(3)>). Now virt-inspector is simply a thin C program over the core C API. All of the inspection information is available from all programming languages that libguestfs supports, and from guestfish.
For a description of the C inspection API, read L<guestfs(3)/INSPECTION>.
-For example code using the C inspection API, look for F<inspect-vm.c> which
-ships with libguestfs.
+For example code using the C inspection API, look for F<inspect-vm.c> which ships with libguestfs.
-F<inspect-vm.c> has also been translated into other languages. For example,
-F<inspect_vm.pl> is the Perl translation, and there are other translations
-for OCaml, Python, etc. See L<guestfs(3)/USING LIBGUESTFS WITH OTHER
-PROGRAMMING LANGUAGES> for a list of man pages which contain this example
-code.
+F<inspect-vm.c> has also been translated into other languages. For example, F<inspect_vm.pl> is the Perl translation, and there are other translations for OCaml, Python, etc. See L<guestfs(3)/USING LIBGUESTFS WITH OTHER PROGRAMMING LANGUAGES> for a list of man pages which contain this example code.
=head2 GETTING INSPECTION DATA FROM GUESTFISH
-If you use the guestfish I<-i> option, then the main C inspection API
-L<guestfs(3)/guestfs_inspect_os> is called. This is equivalent to the
-guestfish command C<inspect-os>. You can also call this guestfish command
-by hand.
+If you use the guestfish I<-i> option, then the main C inspection API L<guestfs(3)/guestfs_inspect_os> is called. This is equivalent to the guestfish command C<inspect-os>. You can also call this guestfish command by hand.
-C<inspect-os> performs inspection on the current disk image, returning the
-list of operating systems found. Each OS is represented by its root
-filesystem device. In the majority of cases, this command prints nothing
-(no OSes found), or a single root device, but beware that it can print
-multiple lines if there are multiple OSes or if there is an install CD
-attached to the guest.
+C<inspect-os> performs inspection on the current disk image, returning the list of operating systems found. Each OS is represented by its root filesystem device. In the majority of cases, this command prints nothing (no OSes found), or a single root device, but beware that it can print multiple lines if there are multiple OSes or if there is an install CD attached to the guest.
$ guestfish --ro -a F15x32.img
><fs> run
><fs> inspect-get-product-name /dev/vg_f15x32/lv_root
Fedora release 15 (Lovelock)
-Limitations of guestfish make it hard to assign the root device to a
-variable (since guestfish doesn't have variables), so if you want to do this
-reproducibly you are better off writing a script using one of the other
-languages that the libguestfs API supports.
+Limitations of guestfish make it hard to assign the root device to a variable (since guestfish doesn't have variables), so if you want to do this reproducibly you are better off writing a script using one of the other languages that the libguestfs API supports.
アプリケーションを一覧表示するには、まずディスクをマウントする必要があります:
app_description:
}
-To display an icon for the guest, note that filesystems must also be mounted
-as above. You can then do:
+To display an icon for the guest, note that filesystems must also be mounted as above. You can then do:
><fs> inspect-get-icon /dev/vg_f15x32/lv_root | display -
=head1 古いバージョンの virt-inspector
-As described above, early versions of libguestfs shipped with a different
-virt-inspector program written in Perl (the current version is written in
-C). The XML output of the Perl virt-inspector was different and it could
-also output in other formats like text.
+As described above, early versions of libguestfs shipped with a different virt-inspector program written in Perl (the current version is written in C). The XML output of the Perl virt-inspector was different and it could also output in other formats like text.
古い virt-inspector はもはや libguestfs でサポートされず、同梱されていません。
-さらに混乱することに、Red Hat Enterprise Linux 6 では異なる名前で 2 つのバージョンの virt-inspector
-が同梱されています:
+さらに混乱することに、Red Hat Enterprise Linux 6 では異なる名前で 2 つのバージョンの virt-inspector が同梱されています:
virt-inspector 古い Perl バージョンです。
virt-inspector2 新しい C バージョンです。
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<http://www.w3.org/TR/xpath/>,
-L<base64(1)>, L<xmlstarlet(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<http://www.w3.org/TR/xpath/>, L<base64(1)>, L<xmlstarlet(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-log 1"
-.TH virt-log 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-log 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\f(CW\*(C`virt\-log\*(C'\fR is a command line tool to display the log files from the named
-virtual machine (or disk image).
+\&\f(CW\*(C`virt\-log\*(C'\fR is a command line tool to display the log files from the named virtual machine (or disk image).
.PP
-This tool understands and displays both plain text log files
-(eg. \fI/var/log/messages\fR) and binary formats such as the systemd journal.
+This tool understands and displays both plain text log files (eg. \fI/var/log/messages\fR) and binary formats such as the systemd journal.
.PP
-To display other types of files, use \fBvirt\-cat\fR\|(1). To follow (tail) text
-log files, use \fBvirt\-tail\fR\|(1). To copy files out of a virtual machine, use
-\&\fBvirt\-copy\-out\fR\|(1). To display the contents of the Windows Registry, use
-\&\fBvirt\-win\-reg\fR\|(1).
+To display other types of files, use \fBvirt\-cat\fR\|(1). To follow (tail) text log files, use \fBvirt\-tail\fR\|(1). To copy files out of a virtual machine, use \fBvirt\-copy\-out\fR\|(1). To display the contents of the Windows Registry, use \fBvirt\-win\-reg\fR\|(1).
.SH "例"
.IX Header "例"
Display the complete logs from a guest:
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a \s-1URI\s0\fR" 4
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-log normally turns echoing off
-so you cannot see what you are typing. If you are not worried about Tempest
-attacks and there is no one else in the room you can specify this flag to
-see what you are typing.
+When prompting for keys and passphrases, virt-log normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-log \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), \fBvirt\-win\-reg\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), \fBvirt\-win\-reg\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-C<virt-log> is a command line tool to display the log files from the named
-virtual machine (or disk image).
+C<virt-log> is a command line tool to display the log files from the named virtual machine (or disk image).
-This tool understands and displays both plain text log files
-(eg. F</var/log/messages>) and binary formats such as the systemd journal.
+This tool understands and displays both plain text log files (eg. F</var/log/messages>) and binary formats such as the systemd journal.
-To display other types of files, use L<virt-cat(1)>. To follow (tail) text
-log files, use L<virt-tail(1)>. To copy files out of a virtual machine, use
-L<virt-copy-out(1)>. To display the contents of the Windows Registry, use
-L<virt-win-reg(1)>.
+To display other types of files, use L<virt-cat(1)>. To follow (tail) text log files, use L<virt-tail(1)>. To copy files out of a virtual machine, use L<virt-copy-out(1)>. To display the contents of the Windows Registry, use L<virt-win-reg(1)>.
=head1 例
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-log normally turns echoing off
-so you cannot see what you are typing. If you are not worried about Tempest
-attacks and there is no one else in the room you can specify this flag to
-see what you are typing.
+When prompting for keys and passphrases, virt-log normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--format=raw|qcow2|..>
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-log --format=raw -a disk.img --format -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-tail(1)>, L<virt-tar-out(1)>, L<virt-win-reg(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>, L<virt-win-reg(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-ls 1"
-.TH virt-ls 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-ls 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-\&\f(CW\*(C`virt\-ls\*(C'\fR lists filenames, file sizes, checksums, extended attributes and
-more from a virtual machine or disk image.
+\&\f(CW\*(C`virt\-ls\*(C'\fR lists filenames, file sizes, checksums, extended attributes and more from a virtual machine or disk image.
.PP
-Multiple directory names can be given, in which case the output from each is
-concatenated.
+Multiple directory names can be given, in which case the output from each is concatenated.
.PP
-To list directories from a libvirt guest use the \fI\-d\fR option to specify the
-name of the guest. For a disk image, use the \fI\-a\fR option.
+To list directories from a libvirt guest use the \fI\-d\fR option to specify the name of the guest. For a disk image, use the \fI\-a\fR option.
.PP
-\&\f(CW\*(C`virt\-ls\*(C'\fR can do many simple file listings. For more complicated cases you
-may need to use \fBguestfish\fR\|(1), or write a program directly to the
-\&\fBguestfs\fR\|(3) \s-1API.\s0
+\&\f(CW\*(C`virt\-ls\*(C'\fR can do many simple file listings. For more complicated cases you may need to use \fBguestfish\fR\|(1), or write a program directly to the \fBguestfs\fR\|(3) \s-1API.\s0
.SH "例"
.IX Header "例"
仮想マシンにあるファイルおよびディレクトリーをすべて取得します:
.Ve
.SS "\s-1DIFFERENCES IN SNAPSHOTS AND BACKING FILES\s0"
.IX Subsection "DIFFERENCES IN SNAPSHOTS AND BACKING FILES"
-Although it is possible to use virt-ls to look for differences, since
-libguestfs ≥ 1.26 a new tool is available called \fBvirt\-diff\fR\|(1).
+Although it is possible to use virt-ls to look for differences, since libguestfs ≥ 1.26 a new tool is available called \fBvirt\-diff\fR\|(1).
.SH "出力モード"
.IX Header "出力モード"
\&\f(CW\*(C`virt\-ls\*(C'\fR は 4 つの出力モードがあります。\fI\-l\fR および \fI\-R\fR オプションの異なる組み合わせにより制御されます。
.Ve
.SS "ロング形式の一覧方法"
.IX Subsection "ロング形式の一覧方法"
-\&\fI\-l\fR (\fI\-\-long\fR) オプションを用いると、出力は \f(CW\*(C`ls \-l\*(C'\fR コマンドのようになります（より具体的には \f(CW\*(C`guestfs_ll\*(C'\fR
-関数と似ています）。
+\&\fI\-l\fR (\fI\-\-long\fR) オプションを用いると、出力は \f(CW\*(C`ls \-l\*(C'\fR コマンドのようになります（より具体的には \f(CW\*(C`guestfs_ll\*(C'\fR 関数と似ています）。
.PP
.Vb 5
\& $ virt\-ls \-l \-d guest /
\& [etc.]
.Ve
.PP
-これはディレクトリーを表示するために有用ですが、他のプログラムにおいてこの出力を解析しないよう注意してください。代わりに
-\&\*(L"再帰的なロング形式の一覧方法\*(R" を使用してください。
+これはディレクトリーを表示するために有用ですが、他のプログラムにおいてこの出力を解析しないよう注意してください。代わりに \*(L"再帰的なロング形式の一覧方法\*(R" を使用してください。
.SS "再帰的な一覧方法"
.IX Subsection "再帰的な一覧方法"
\&\fI\-R\fR (\fI\-\-recursive\fR) オプションを用いると、\f(CW\*(C`virt\-ls\*(C'\fR はファイルおよびディレクトリーを再帰的に一覧表示します:
この出力を生成するには、\f(CW\*(C`virt\-ls\*(C'\fR が \f(CW\*(C`guestfs_find0\*(C'\fR 関数を実行して、\f(CW\*(C`\e0\*(C'\fR 文字を \f(CW\*(C`\en\*(C'\fR に変換します。
.SS "再帰的なロング形式の一覧方法"
.IX Subsection "再帰的なロング形式の一覧方法"
-Using \fI\-lR\fR options together changes the output to display directories
-recursively, with file stats, and optionally other features such as
-checksums and extended attributes.
+Using \fI\-lR\fR options together changes the output to display directories recursively, with file stats, and optionally other features such as checksums and extended attributes.
.PP
-Most of the interesting features of \f(CW\*(C`virt\-ls\*(C'\fR are only available when using
-\&\fI\-lR\fR mode.
+Most of the interesting features of \f(CW\*(C`virt\-ls\*(C'\fR are only available when using \fI\-lR\fR mode.
.PP
-The fields are normally space-separated. Filenames are \fBnot\fR quoted, so
-you cannot use the output in another program (because filenames can contain
-spaces and other unsafe characters). If the guest was untrusted and someone
-knew you were using \f(CW\*(C`virt\-ls\*(C'\fR to analyze the guest, they could play tricks
-on you by creating filenames with embedded newline characters. To \fBsafely\fR
-parse the output in another program, use the \fI\-\-csv\fR (Comma-Separated
-Values) option.
+The fields are normally space-separated. Filenames are \fBnot\fR quoted, so you cannot use the output in another program (because filenames can contain spaces and other unsafe characters). If the guest was untrusted and someone knew you were using \f(CW\*(C`virt\-ls\*(C'\fR to analyze the guest, they could play tricks on you by creating filenames with embedded newline characters. To \fBsafely\fR parse the output in another program, use the \fI\-\-csv\fR (Comma-Separated Values) option.
.PP
-Note that this output format is completely unrelated to the \f(CW\*(C`ls \-lR\*(C'\fR
-command.
+Note that this output format is completely unrelated to the \f(CW\*(C`ls \-lR\*(C'\fR command.
.PP
.Vb 8
\& $ virt\-ls \-lR \-d guest /bin
これらの基本的な項目は常に表示されます:
.IP "type" 4
.IX Item "type"
-ファイル形式。次のどれかです: \f(CW\*(C`\-\*(C'\fR (通常のファイル), \f(CW\*(C`d\*(C'\fR (ディレクトリー), \f(CW\*(C`c\*(C'\fR (キャラクターデバイス), \f(CW\*(C`b\*(C'\fR
-(ブロックデバイス), \f(CW\*(C`p\*(C'\fR (名前付きパイプ), \f(CW\*(C`l\*(C'\fR (シンボリックリンク), \f(CW\*(C`s\*(C'\fR (ソケット) or \f(CW\*(C`u\*(C'\fR (不明)。
+ファイル形式。次のどれかです: \f(CW\*(C`\-\*(C'\fR (通常のファイル), \f(CW\*(C`d\*(C'\fR (ディレクトリー), \f(CW\*(C`c\*(C'\fR (キャラクターデバイス), \f(CW\*(C`b\*(C'\fR (ブロックデバイス), \f(CW\*(C`p\*(C'\fR (名前付きパイプ), \f(CW\*(C`l\*(C'\fR (シンボリックリンク), \f(CW\*(C`s\*(C'\fR (ソケット) or \f(CW\*(C`u\*(C'\fR (不明)。
.IP "パーミッション" 4
.IX Item "パーミッション"
Unix パーティション。4 桁の8進数として表示されます。
.IP "容量" 4
.IX Item "容量"
-ファイルの容量。 読みやすい形式の数値として表示する \fI\-h\fR または \fI\-\-human\-readable\fR
-オプションが指定されていなければ、バイト単位で表示されます。
+ファイルの容量。 読みやすい形式の数値として表示する \fI\-h\fR または \fI\-\-human\-readable\fR オプションが指定されていなければ、バイト単位で表示されます。
.IP "パス" 4
.IX Item "パス"
ファイルまたはディレクトリの完全パス。
.IX Item "ctime"
最終属性変更日時。
.PP
-\&\fI\-\-time\-t\fR, \fI\-\-time\-relative\fR または \fI\-\-time\-days\fR
-フラグのどれかが指定されていなければ、日付と時間の文字列として time 項目が表示されます。
+\&\fI\-\-time\-t\fR, \fI\-\-time\-relative\fR または \fI\-\-time\-days\fR フラグのどれかが指定されていなければ、日付と時間の文字列として time 項目が表示されます。
.PP
\&\fI\-\-extra\-stats\fR フラグを用いると、これらの追加項目が表示されます:
.IP "device" 4
.IX Item "device"
-The device containing the file (displayed as major:minor). This may not
-match devices as known to the guest.
+The device containing the file (displayed as major:minor). This may not match devices as known to the guest.
.IP "inode" 4
.IX Item "inode"
inode 番号。
.IX Item "ブロック"
ファイルに割り当てられた 512 バイトブロック数。
.PP
-With the \fI\-\-checksum\fR flag, the checksum of the file contents is shown
-(only for regular files). Computing file checksums can take a considerable
-amount of time.
+With the \fI\-\-checksum\fR flag, the checksum of the file contents is shown (only for regular files). Computing file checksums can take a considerable amount of time.
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR file" 4
.IX Item "--add file"
.PD
-Add \fIfile\fR which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate \fI\-a\fR options.
+Add \fIfile\fR which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate \fI\-a\fR options.
.Sp
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 \fI\-\-format=..\fR オプションを使用します。
.IP "\fB\-a \s-1URI\s0\fR" 4
.IP "\fB\-\-checksum=crc|md5|sha1|sha224|sha256|sha384|sha512\fR" 4
.IX Item "--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512"
.PD
-Display checksum over file contents for regular files. With no argument,
-this defaults to using \fImd5\fR. Using an argument, you can select the
-checksum type to use.
+Display checksum over file contents for regular files. With no argument, this defaults to using \fImd5\fR. Using an argument, you can select the checksum type to use.
.Sp
このオプションは \fI\-lR\fR 出力モードにおいてのみ効果があります。 上の \*(L"\s-1RECURSIVE LONG LISTING\*(R"\s0 参照。
.IP "\fB\-c\fR \s-1URI\s0" 4
ゲストのブロックデバイスを直接指定していると（(\fI\-a\fR)）、libvirt は何も使用されません。
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Write out the results in \s-1CSV\s0 format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE
-ABOUT CSV FORMAT\*(R"\s0 below.
+Write out the results in \s-1CSV\s0 format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read \*(L"\s-1NOTE ABOUT CSV FORMAT\*(R"\s0 below.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
名前付きの libvirt 仮想マシンからすべてのディスクを追加します。 名前の代わりに仮想マシンの \s-1UUID\s0 を使用できます。
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-キーやパスフレーズを入力するとき、通常 virt-ls はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-ls はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
.IP "\fB\-\-extra\-stats\fR" 4
.IX Item "--extra-stats"
Display extra stats.
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR
-オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR
-オプションに対して自動検知に戻せます。
+\&\fI\-a\fR オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の \fI\-a\fR オプションのディスク形式を強制的に指定できます。 引数なしで \fI\-\-format\fR を使用することにより、 後続の \fI\-a\fR オプションに対して自動検知に戻せます。
.Sp
例:
.Sp
\& virt\-ls \-\-format=raw \-a disk.img \-\-format \-a another.img /dir
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
.Sp
If the mountpoint is omitted, it defaults to \fI/\fR.
.Sp
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
.Sp
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R"
-commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" and \*(L"lvs\*(R" commands), or you can use the \fBvirt\-filesystems\fR\|(1) program.
.Sp
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または \f(CW\*(C`ro\*(C'\fR (\fI\-\-ro\fR フラグが使用されている場合) になります。
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Sp
このフラグを使用することは、 \f(CW\*(C`mount\-options\*(C'\fR コマンドを使用することと同等です。
.Sp
-パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (\f(CW\*(C`ext3\*(C'\fR や \f(CW\*(C`ntfs\*(C'\fR など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: \f(CW\*(C`ext2\*(C'\fR と \f(CW\*(C`ext3\*(C'\fR)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
.IP "\fB\-l\fR" 4
.IX Item "-l"
.PD 0
.IP "\fB\-\-recursive\fR" 4
.IX Item "--recursive"
.PD
-Select the mode. With neither of these options, \f(CW\*(C`virt\-ls\*(C'\fR produces a
-simple, flat list of the files in the named directory. See \*(L"\s-1SIMPLE
-LISTING\*(R"\s0.
+Select the mode. With neither of these options, \f(CW\*(C`virt\-ls\*(C'\fR produces a simple, flat list of the files in the named directory. See \*(L"\s-1SIMPLE LISTING\*(R"\s0.
.Sp
-\&\f(CW\*(C`virt\-ls \-l\*(C'\fR produces a \*(L"long listing\*(R", which shows more detail. See
-\&\*(L"\s-1LONG LISTING\*(R"\s0.
+\&\f(CW\*(C`virt\-ls \-l\*(C'\fR produces a \*(L"long listing\*(R", which shows more detail. See \*(L"\s-1LONG LISTING\*(R"\s0.
.Sp
-\&\f(CW\*(C`virt\-ls \-R\*(C'\fR produces a recursive list of files starting at the named
-directory. See \*(L"\s-1RECURSIVE LISTING\*(R"\s0.
+\&\f(CW\*(C`virt\-ls \-R\*(C'\fR produces a recursive list of files starting at the named directory. See \*(L"\s-1RECURSIVE LISTING\*(R"\s0.
.Sp
-\&\f(CW\*(C`virt\-ls \-lR\*(C'\fR produces a recursive long listing which can be more easily
-parsed. See \*(L"\s-1RECURSIVE LONG LISTING\*(R"\s0.
+\&\f(CW\*(C`virt\-ls \-lR\*(C'\fR produces a recursive long listing which can be more easily parsed. See \*(L"\s-1RECURSIVE LONG LISTING\*(R"\s0.
.IP "\fB\-\-times\fR" 4
.IX Item "--times"
時間の項目を表示します。
.IX Item "--time-days"
Display time fields as days before now (negative if in the future).
.Sp
-Note that \f(CW0\fR in output means \*(L"up to 1 day before now\*(R", or that the age of
-the file is between 0 and 86399 seconds.
+Note that \f(CW0\fR in output means \*(L"up to 1 day before now\*(R", or that the age of the file is between 0 and 86399 seconds.
.Sp
このオプションは \fI\-lR\fR 出力モードにおいてのみ効果があります。 上の \*(L"\s-1RECURSIVE LONG LISTING\*(R"\s0 参照。
.IP "\fB\-\-time\-relative\fR" 4
\& virt\-ls guestname /dir
.Ve
.PP
-whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively to avoid the confusing case where a disk image might have the same name as a guest.
.PP
互換性のため古い形式がまだサポートされています。
.SH "CSV 形式に関する注意"
.IX Header "CSV 形式に関する注意"
-Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (\s-1CSV\s0) is a deceptive format. It \fIseems\fR like it should be easy to parse, but it is definitely not easy to parse.
.PP
神話: ただコンマで項目を区切る。 真実: これは正しく動き \fIません\fR。この例は 2 つの列があります:
.PP
\& bar",baz
.Ve
.PP
-For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv
-also packaged in major Linux distributions).
+For shell scripts, use \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv also packaged in major Linux distributions).
.PP
-For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl
-or Python’s built-in csv library).
+For other languages, use a \s-1CSV\s0 processing library (eg. \f(CW\*(C`Text::CSV\*(C'\fR for Perl or Python’s built-in csv library).
.PP
Most spreadsheets and databases can import \s-1CSV\s0 directly.
.SH "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-diff\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-diff\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-C<virt-ls> lists filenames, file sizes, checksums, extended attributes and
-more from a virtual machine or disk image.
+C<virt-ls> lists filenames, file sizes, checksums, extended attributes and more from a virtual machine or disk image.
-Multiple directory names can be given, in which case the output from each is
-concatenated.
+Multiple directory names can be given, in which case the output from each is concatenated.
-To list directories from a libvirt guest use the I<-d> option to specify the
-name of the guest. For a disk image, use the I<-a> option.
+To list directories from a libvirt guest use the I<-d> option to specify the name of the guest. For a disk image, use the I<-a> option.
-C<virt-ls> can do many simple file listings. For more complicated cases you
-may need to use L<guestfish(1)>, or write a program directly to the
-L<guestfs(3)> API.
+C<virt-ls> can do many simple file listings. For more complicated cases you may need to use L<guestfish(1)>, or write a program directly to the L<guestfs(3)> API.
=head1 例
=head2 DIFFERENCES IN SNAPSHOTS AND BACKING FILES
-Although it is possible to use virt-ls to look for differences, since
-libguestfs E<ge> 1.26 a new tool is available called L<virt-diff(1)>.
+Although it is possible to use virt-ls to look for differences, since libguestfs E<ge> 1.26 a new tool is available called L<virt-diff(1)>.
=head1 出力モード
=head2 ロング形式の一覧方法
-I<-l> (I<--long>) オプションを用いると、出力は C<ls -l> コマンドのようになります（より具体的には C<guestfs_ll>
-関数と似ています）。
+I<-l> (I<--long>) オプションを用いると、出力は C<ls -l> コマンドのようになります（より具体的には C<guestfs_ll> 関数と似ています）。
$ virt-ls -l -d guest /
total 204
dr-xr-xr-x. 5 root root 3072 2009-08-25 19:06 boot
[etc.]
-これはディレクトリーを表示するために有用ですが、他のプログラムにおいてこの出力を解析しないよう注意してください。代わりに
-L</再帰的なロング形式の一覧方法> を使用してください。
+これはディレクトリーを表示するために有用ですが、他のプログラムにおいてこの出力を解析しないよう注意してください。代わりに L</再帰的なロング形式の一覧方法> を使用してください。
=head2 再帰的な一覧方法
=head2 再帰的なロング形式の一覧方法
-Using I<-lR> options together changes the output to display directories
-recursively, with file stats, and optionally other features such as
-checksums and extended attributes.
+Using I<-lR> options together changes the output to display directories recursively, with file stats, and optionally other features such as checksums and extended attributes.
-Most of the interesting features of C<virt-ls> are only available when using
-I<-lR> mode.
+Most of the interesting features of C<virt-ls> are only available when using I<-lR> mode.
-The fields are normally space-separated. Filenames are B<not> quoted, so
-you cannot use the output in another program (because filenames can contain
-spaces and other unsafe characters). If the guest was untrusted and someone
-knew you were using C<virt-ls> to analyze the guest, they could play tricks
-on you by creating filenames with embedded newline characters. To B<safely>
-parse the output in another program, use the I<--csv> (Comma-Separated
-Values) option.
+The fields are normally space-separated. Filenames are B<not> quoted, so you cannot use the output in another program (because filenames can contain spaces and other unsafe characters). If the guest was untrusted and someone knew you were using C<virt-ls> to analyze the guest, they could play tricks on you by creating filenames with embedded newline characters. To B<safely> parse the output in another program, use the I<--csv> (Comma-Separated Values) option.
-Note that this output format is completely unrelated to the C<ls -lR>
-command.
+Note that this output format is completely unrelated to the C<ls -lR> command.
$ virt-ls -lR -d guest /bin
d 0555 4096 /bin
=item type
-ファイル形式。次のどれかです: C<-> (通常のファイル), C<d> (ディレクトリー), C<c> (キャラクターデバイス), C<b>
-(ブロックデバイス), C<p> (名前付きパイプ), C<l> (シンボリックリンク), C<s> (ソケット) or C<u> (不明)。
+ファイル形式。次のどれかです: C<-> (通常のファイル), C<d> (ディレクトリー), C<c> (キャラクターデバイス), C<b> (ブロックデバイス), C<p> (名前付きパイプ), C<l> (シンボリックリンク), C<s> (ソケット) or C<u> (不明)。
=item パーミッション
=item 容量
-ファイルの容量。 読みやすい形式の数値として表示する I<-h> または I<--human-readable>
-オプションが指定されていなければ、バイト単位で表示されます。
+ファイルの容量。 読みやすい形式の数値として表示する I<-h> または I<--human-readable> オプションが指定されていなければ、バイト単位で表示されます。
=item パス
=back
-I<--time-t>, I<--time-relative> または I<--time-days>
-フラグのどれかが指定されていなければ、日付と時間の文字列として time 項目が表示されます。
+I<--time-t>, I<--time-relative> または I<--time-days> フラグのどれかが指定されていなければ、日付と時間の文字列として time 項目が表示されます。
I<--extra-stats> フラグを用いると、これらの追加項目が表示されます:
=item device
-The device containing the file (displayed as major:minor). This may not
-match devices as known to the guest.
+The device containing the file (displayed as major:minor). This may not match devices as known to the guest.
=item inode
=back
-With the I<--checksum> flag, the checksum of the file contents is shown
-(only for regular files). Computing file checksums can take a considerable
-amount of time.
+With the I<--checksum> flag, the checksum of the file contents is shown (only for regular files). Computing file checksums can take a considerable amount of time.
=head1 オプション
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512>
-Display checksum over file contents for regular files. With no argument,
-this defaults to using I<md5>. Using an argument, you can select the
-checksum type to use.
+Display checksum over file contents for regular files. With no argument, this defaults to using I<md5>. Using an argument, you can select the checksum type to use.
このオプションは I<-lR> 出力モードにおいてのみ効果があります。 上の L</RECURSIVE LONG LISTING> 参照。
=item B<--csv>
-Write out the results in CSV format (comma-separated values). This format
-can be imported easily into databases and spreadsheets, but read L</NOTE
-ABOUT CSV FORMAT> below.
+Write out the results in CSV format (comma-separated values). This format can be imported easily into databases and spreadsheets, but read L</NOTE ABOUT CSV FORMAT> below.
=item B<-d> guest
=item B<--echo-keys>
-キーやパスフレーズを入力するとき、通常 virt-ls はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、
-部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
+キーやパスフレーズを入力するとき、通常 virt-ls はエコーを無効化します。 そのため、入力内容を確認できません。 テンペスト攻撃の心配がなく、 部屋に誰も居なければ、 入力内容を確認するためにこのフラグを指定できます。
=item B<--extra-stats>
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-ls --format=raw -a disk.img --format -a another.img /dir
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
=item B<-h>
If the mountpoint is omitted, it defaults to F</>.
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see L</list-partitions>, L</list-filesystems> and L</lvs>
-commands), or you can use the L<virt-filesystems(1)> program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see L</list-partitions>, L</list-filesystems> and L</lvs> commands), or you can use the L<virt-filesystems(1)> program.
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro>
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro> フラグが使用されている場合) になります。
-m /dev/sda1:/:acl,user_xattr
このフラグを使用することは、 C<mount-options> コマンドを使用することと同等です。
-パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
=item B<-l>
=item B<--recursive>
-Select the mode. With neither of these options, C<virt-ls> produces a
-simple, flat list of the files in the named directory. See L</SIMPLE
-LISTING>.
+Select the mode. With neither of these options, C<virt-ls> produces a simple, flat list of the files in the named directory. See L</SIMPLE LISTING>.
-C<virt-ls -l> produces a "long listing", which shows more detail. See
-L</LONG LISTING>.
+C<virt-ls -l> produces a "long listing", which shows more detail. See L</LONG LISTING>.
-C<virt-ls -R> produces a recursive list of files starting at the named
-directory. See L</RECURSIVE LISTING>.
+C<virt-ls -R> produces a recursive list of files starting at the named directory. See L</RECURSIVE LISTING>.
-C<virt-ls -lR> produces a recursive long listing which can be more easily
-parsed. See L</RECURSIVE LONG LISTING>.
+C<virt-ls -lR> produces a recursive long listing which can be more easily parsed. See L</RECURSIVE LONG LISTING>.
=item B<--times>
Display time fields as days before now (negative if in the future).
-Note that C<0> in output means "up to 1 day before now", or that the age of
-the file is between 0 and 86399 seconds.
+Note that C<0> in output means "up to 1 day before now", or that the age of the file is between 0 and 86399 seconds.
このオプションは I<-lR> 出力モードにおいてのみ効果があります。 上の L</RECURSIVE LONG LISTING> 参照。
virt-ls guestname /dir
-whereas in this version you should use I<-a> or I<-d> respectively to avoid
-the confusing case where a disk image might have the same name as a guest.
+whereas in this version you should use I<-a> or I<-d> respectively to avoid the confusing case where a disk image might have the same name as a guest.
互換性のため古い形式がまだサポートされています。
=head1 CSV 形式に関する注意
-Comma-separated values (CSV) is a deceptive format. It I<seems> like it
-should be easy to parse, but it is definitely not easy to parse.
+Comma-separated values (CSV) is a deceptive format. It I<seems> like it should be easy to parse, but it is definitely not easy to parse.
神話: ただコンマで項目を区切る。 真実: これは正しく動き I<ません>。この例は 2 つの列があります:
"foo
bar",baz
-For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv>
-also packaged in major Linux distributions).
+For shell scripts, use C<csvtool> (L<https://github.com/Chris00/ocaml-csv> also packaged in major Linux distributions).
-For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl
-or Python’s built-in csv library).
+For other languages, use a CSV processing library (eg. C<Text::CSV> for Perl or Python’s built-in csv library).
Most spreadsheets and databases can import CSV directly.
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-diff(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-diff(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-make-fs 1"
-.TH virt-make-fs 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-make-fs 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-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
-\&\fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1) and \fBmksquashfs\fR\|(1). Unlike those tools,
-it can create common filesystem types like ext2/3 or \s-1NTFS,\s0 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 \s-1VM\s0).
+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 \fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1) and \fBmksquashfs\fR\|(1). Unlike those tools, it can create common filesystem types like ext2/3 or \s-1NTFS,\s0 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 \s-1VM\s0).
.PP
-To create blank disks, use \fBvirt\-format\fR\|(1). To create complex layouts,
-use \fBguestfish\fR\|(1).
+To create blank disks, use \fBvirt\-format\fR\|(1). To create complex layouts, use \fBguestfish\fR\|(1).
.PP
基本的な使用法は次のとおりです:
.PP
\& virt\-make\-fs input output.img
.Ve
.PP
-where \f(CW\*(C`input\*(C'\fR is either a directory containing files that you want to add,
-or a tar archive (either uncompressed tar or gzip-compressed tar); and
-\&\fIoutput.img\fR is a disk image. The input type is detected automatically.
-The output disk image defaults to a raw ext2 sparse image unless you specify
-extra flags (see \*(L"\s-1OPTIONS\*(R"\s0 below).
+where \f(CW\*(C`input\*(C'\fR is either a directory containing files that you want to add, or a tar archive (either uncompressed tar or gzip-compressed tar); and \fIoutput.img\fR is a disk image. The input type is detected automatically. The output disk image defaults to a raw ext2 sparse image unless you specify extra flags (see \*(L"\s-1OPTIONS\*(R"\s0 below).
.SS "ファイルシステム形式"
.IX Subsection "ファイルシステム形式"
-The default filesystem type is \f(CW\*(C`ext2\*(C'\fR. Just about any filesystem type that
-libguestfs supports can be used (but \fInot\fR read-only formats like
-\&\s-1ISO9660\s0). Here are some of the more common choices:
+The default filesystem type is \f(CW\*(C`ext2\*(C'\fR. Just about any filesystem type that libguestfs supports can be used (but \fInot\fR read-only formats like \s-1ISO9660\s0). Here are some of the more common choices:
.IP "\fIext3\fR" 4
.IX Item "ext3"
-Note that ext3 filesystems contain a journal, typically 1\-32 \s-1MB\s0 in size. If
-you are not going to use the filesystem in a way that requires the journal,
-then this is just wasted overhead.
+Note that ext3 filesystems contain a journal, typically 1\-32 \s-1MB\s0 in size. If you are not going to use the filesystem in a way that requires the journal, then this is just wasted overhead.
.IP "\fIntfs\fR または \fIvfat\fR" 4
.IX Item "ntfs または vfat"
Useful if exporting data to a Windows guest.
.IP "\fIminix\fR" 4
.IX Item "minix"
-Lower overhead than \f(CW\*(C`ext2\*(C'\fR, but certain limitations on filename length and
-total filesystem size.
+Lower overhead than \f(CW\*(C`ext2\*(C'\fR, but certain limitations on filename length and total filesystem size.
.PP
\fI例\fR
.IX Subsection "例"
.IX Subsection "TO PARTITION OR NOT TO PARTITION"
Optionally virt-make-fs can add a partition table to the output disk.
.PP
-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).
+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).
.PP
-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 \fBfsck\fR\|(8)
-directly on a partitioned disk image. (However libguestfs tools such as
-\&\fBguestfish\fR\|(1) and \fBvirt\-resize\fR\|(1) can still be used).
+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 \fBfsck\fR\|(8) directly on a partitioned disk image. (However libguestfs tools such as \fBguestfish\fR\|(1) and \fBvirt\-resize\fR\|(1) can still be used).
.PP
\fI例\fR
.IX Subsection "例"
\& virt\-make\-fs \-\-partition \-\- input disk.img
.Ve
.PP
-If the output disk image could be terabyte-sized or larger, it's better to
-use an EFI/GPT\-compatible partition table:
+If the output disk image could be terabyte-sized or larger, it's better to use an EFI/GPT\-compatible partition table:
.PP
.Vb 1
\& virt\-make\-fs \-\-partition=gpt \-\-size=+4T \-\-format=qcow2 input disk.img
.Ve
.SS "\s-1EXTRA SPACE\s0"
.IX Subsection "EXTRA SPACE"
-Unlike formats such as tar and squashfs, a filesystem does not \*(L"just fit\*(R"
-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 \fI\-\-size\fR flag to leave space in the filesystem if you
-want it.
+Unlike formats such as tar and squashfs, a filesystem does not \*(L"just fit\*(R" 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 \fI\-\-size\fR flag to leave space in the filesystem if you want it.
.PP
-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
-\&\*(L"raw\*(R" format). Using \fI\-\-format=qcow2\fR will use the native qemu/KVM qcow2
-image format (check your hypervisor supports this before using it). This
-allows you to choose a large \fI\-\-size\fR but the extra space won't actually be
-allocated in the image until you try to store something in it.
+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 \*(L"raw\*(R" format). Using \fI\-\-format=qcow2\fR will use the native qemu/KVM qcow2 image format (check your hypervisor supports this before using it). This allows you to choose a large \fI\-\-size\fR but the extra space won't actually be allocated in the image until you try to store something in it.
.PP
-Don’t forget that you can also use local commands including \fBresize2fs\fR\|(8)
-and \fBvirt\-resize\fR\|(1) to resize existing filesystems, or rerun virt-make-fs
-to build another image from scratch.
+Don’t forget that you can also use local commands including \fBresize2fs\fR\|(8) and \fBvirt\-resize\fR\|(1) to resize existing filesystems, or rerun virt-make-fs to build another image from scratch.
.PP
\fI例\fR
.IX Subsection "例"
.IX Item "--floppy"
仮想フロッピーディスクを作成します。
.Sp
-今のところ、容量 (1440K)、パーティション形式 (\s-1MBR\s0) およびファイルシステム形式 (\s-1VFAT\s0)
-が事前に選択されています。将来的に、ジオメトリーを選択できるようになる可能性があります。
+今のところ、容量 (1440K)、パーティション形式 (\s-1MBR\s0) およびファイルシステム形式 (\s-1VFAT\s0) が事前に選択されています。将来的に、ジオメトリーを選択できるようになる可能性があります。
.IP "\fB\-\-size=\fRN" 4
.IX Item "--size=N"
.PD 0
.PD
Use the \fI\-\-size\fR (or \fI\-s\fR) option to choose the size of the output image.
.Sp
-If this option is \fInot\fR given, then the output image will be just large
-enough to contain all the files, with not much wasted space.
+If this option is \fInot\fR given, then the output image will be just large enough to contain all the files, with not much wasted space.
.Sp
-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.
+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.
.Sp
-To leave extra space, specify \f(CW\*(C`+\*(C'\fR (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: \fI\-\-size=+200M\fR means enough space for
-the input files, and (approximately) an extra 200 \s-1MB\s0 free space.
+To leave extra space, specify \f(CW\*(C`+\*(C'\fR (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: \fI\-\-size=+200M\fR means enough space for the input files, and (approximately) an extra 200 \s-1MB\s0 free space.
.Sp
-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).
+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).
.IP "\fB\-\-format=\fR\s-1FMT\s0" 4
.IX Item "--format=FMT"
.PD 0
.PD
このフラグが指定されていると、出力ディスクイメージに \s-1MBR\s0 パーティションテーブルを追加します。
.Sp
-You can change the partition table type, eg. \fI\-\-partition=gpt\fR for large
-disks.
+You can change the partition table type, eg. \fI\-\-partition=gpt\fR for large disks.
.Sp
For \s-1MBR,\s0 virt-make-fs sets the partition type byte automatically.
.IP "\fB\-v\fR" 4
Enable libguestfs trace.
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfish\fR\|(1), \fBvirt\-format\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-tar\-in\fR\|(1),
-\&\fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1), \fBmksquashfs\fR\|(1), \fBmke2fs\fR\|(8),
-\&\fBresize2fs\fR\|(8), \fBguestfs\fR\|(3), http://libguestfs.org/.
+\&\fBguestfish\fR\|(1), \fBvirt\-format\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-tar\-in\fR\|(1), \fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1), \fBmksquashfs\fR\|(1), \fBmke2fs\fR\|(8), \fBresize2fs\fR\|(8), \fBguestfs\fR\|(3), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-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).
+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).
-To create blank disks, use L<virt-format(1)>. To create complex layouts,
-use L<guestfish(1)>.
+To create blank disks, use L<virt-format(1)>. To create complex layouts, use L<guestfish(1)>.
基本的な使用法は次のとおりです:
virt-make-fs input output.img
-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
-F<output.img> is a disk image. The input type is detected automatically.
-The output disk image defaults to a raw ext2 sparse image unless you specify
-extra flags (see L</OPTIONS> below).
+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 F<output.img> is a disk image. The input type is detected automatically. The output disk image defaults to a raw ext2 sparse image unless you specify extra flags (see L</OPTIONS> below).
=head2 ファイルシステム形式
-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:
+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:
=over 4
=item I<ext3>
-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.
+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.
=item I<ntfs> または I<vfat>
=item I<minix>
-Lower overhead than C<ext2>, but certain limitations on filename length and
-total filesystem size.
+Lower overhead than C<ext2>, but certain limitations on filename length and total filesystem size.
=back
Optionally virt-make-fs can add a partition table to the output disk.
-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).
+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).
-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).
+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).
=head3 例
virt-make-fs --partition -- input disk.img
-If the output disk image could be terabyte-sized or larger, it's better to
-use an EFI/GPT-compatible partition table:
+If the output disk image could be terabyte-sized or larger, it's better to use an EFI/GPT-compatible partition table:
virt-make-fs --partition=gpt --size=+4T --format=qcow2 input disk.img
=head2 EXTRA SPACE
-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 I<--size> flag to leave space in the filesystem if you
-want it.
-
-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 I<--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 I<--size> but the extra space won't actually be
-allocated in the image until you try to store something in it.
-
-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-fs
-to build another image from scratch.
+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 I<--size> flag to leave space in the filesystem if you want it.
+
+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 I<--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 I<--size> but the extra space won't actually be allocated in the image until you try to store something in it.
+
+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-fs to build another image from scratch.
=head3 例
仮想フロッピーディスクを作成します。
-今のところ、容量 (1440K)、パーティション形式 (MBR) およびファイルシステム形式 (VFAT)
-が事前に選択されています。将来的に、ジオメトリーを選択できるようになる可能性があります。
+今のところ、容量 (1440K)、パーティション形式 (MBR) およびファイルシステム形式 (VFAT) が事前に選択されています。将来的に、ジオメトリーを選択できるようになる可能性があります。
=item B<--size=>N
Use the I<--size> (or I<-s>) option to choose the size of the output image.
-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.
+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.
-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.
+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.
-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: I<--size=+200M> means enough space for
-the input files, and (approximately) an extra 200 MB free space.
+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: I<--size=+200M> means enough space for the input files, and (approximately) an extra 200 MB free space.
-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).
+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).
=item B<--format=>FMT
このフラグが指定されていると、出力ディスクイメージに MBR パーティションテーブルを追加します。
-You can change the partition table type, eg. I<--partition=gpt> for large
-disks.
+You can change the partition table type, eg. I<--partition=gpt> for large disks.
For MBR, virt-make-fs sets the partition type byte automatically.
=head1 関連項目
-L<guestfish(1)>, L<virt-format(1)>, L<virt-resize(1)>, L<virt-tar-in(1)>,
-L<mkisofs(1)>, L<genisoimage(1)>, L<mksquashfs(1)>, L<mke2fs(8)>,
-L<resize2fs(8)>, L<guestfs(3)>, L<http://libguestfs.org/>.
+L<guestfish(1)>, L<virt-format(1)>, L<virt-resize(1)>, L<virt-tar-in(1)>, L<mkisofs(1)>, L<genisoimage(1)>, L<mksquashfs(1)>, L<mke2fs(8)>, L<resize2fs(8)>, L<guestfs(3)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-resize 1"
-.TH virt-resize 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-resize 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-resize is a tool which can resize a virtual machine disk, making it
-larger or smaller overall, and resizing or deleting any partitions contained
-within.
+Virt-resize is a tool which can resize a virtual machine disk, making it larger or smaller overall, and resizing or deleting any partitions contained within.
.PP
-Virt-resize \fBcannot\fR resize disk images in-place. Virt-resize \fBshould
-not\fR be used on live virtual machines \- for consistent results, shut the
-virtual machine down before resizing it.
+Virt-resize \fBcannot\fR resize disk images in-place. Virt-resize \fBshould not\fR be used on live virtual machines \- for consistent results, shut the virtual machine down before resizing it.
.PP
-If you are not familiar with the associated tools: \fBvirt\-filesystems\fR\|(1)
-and \fBvirt\-df\fR\|(1), we recommend you go and read those manual pages first.
+If you are not familiar with the associated tools: \fBvirt\-filesystems\fR\|(1) and \fBvirt\-df\fR\|(1), we recommend you go and read those manual pages first.
.SH "例"
.IX Header "例"
.IP "1." 4
-This example takes \f(CW\*(C`olddisk\*(C'\fR and resizes it into \f(CW\*(C`newdisk\*(C'\fR, extending one
-of the guest’s partitions to fill the extra 5GB of space:
+This example takes \f(CW\*(C`olddisk\*(C'\fR and resizes it into \f(CW\*(C`newdisk\*(C'\fR, extending one of the guest’s partitions to fill the extra 5GB of space:
.Sp
.Vb 1
\& virt\-filesystems \-\-long \-h \-\-all \-a olddisk
\& virt\-resize \-\-expand /dev/sda2 olddisk newdisk
.Ve
.IP "2." 4
-As above, but make the /boot partition 200MB bigger, while giving the
-remaining space to /dev/sda2:
+As above, but make the /boot partition 200MB bigger, while giving the remaining space to /dev/sda2:
.Sp
.Vb 2
\& virt\-resize \-\-resize /dev/sda1=+200M \-\-expand /dev/sda2 \e
\& olddisk newdisk
.Ve
.IP "3." 4
-As in the first example, but expand a logical volume as the final step.
-This is what you would typically use for Linux guests that use \s-1LVM:\s0
+As in the first example, but expand a logical volume as the final step. This is what you would typically use for Linux guests that use \s-1LVM:\s0
.Sp
.Vb 2
\& virt\-resize \-\-expand /dev/sda2 \-\-LV\-expand /dev/vg_guest/lv_root \e
\& olddisk newdisk
.Ve
.IP "4." 4
-As in the first example, but the output format will be qcow2 instead of a
-raw disk:
+As in the first example, but the output format will be qcow2 instead of a raw disk:
.Sp
.Vb 2
\& qemu\-img create \-f qcow2 \-o preallocation=metadata newdisk.qcow2 15G
.IP "2. 入力ディスクイメージの位置を探します" 4
.IX Item "2. 入力ディスクイメージの位置を探します"
.PD
-Locate the input disk image (ie. the file or device on the host containing
-the guest’s disk). If the guest is managed by libvirt, you can use \f(CW\*(C`virsh
-dumpxml\*(C'\fR like this to find the disk image name:
+Locate the input disk image (ie. the file or device on the host containing the guest’s disk). If the guest is managed by libvirt, you can use \f(CW\*(C`virsh dumpxml\*(C'\fR like this to find the disk image name:
.Sp
.Vb 4
\& # virsh dumpxml guestname | xpath /domain/devices/disk/source
\& /dev/sda device 8.0G \-
.Ve
.Sp
-(This example is a virtual machine with an 8 \s-1GB\s0 disk which we would like to
-expand up to 10 \s-1GB\s0).
+(This example is a virtual machine with an 8 \s-1GB\s0 disk which we would like to expand up to 10 \s-1GB\s0).
.IP "4. 出力ディスクを作成します" 4
.IX Item "4. 出力ディスクを作成します"
-Virt-resize cannot do in-place disk modifications. You have to have space
-to store the resized output disk.
+Virt-resize cannot do in-place disk modifications. You have to have space to store the resized output disk.
.Sp
To store the resized disk image in a file, create a file of a suitable size:
.Sp
.Ve
.IP "5. 容量を変更します" 4
.IX Item "5. 容量を変更します"
-virt-resize takes two mandatory parameters, the input disk and the output
-disk (both can be e.g. a device, a file, or a \s-1URI\s0 to a remote disk). The
-output disk is the one created in the previous step.
+virt-resize takes two mandatory parameters, the input disk and the output disk (both can be e.g. a device, a file, or a \s-1URI\s0 to a remote disk). The output disk is the one created in the previous step.
.Sp
.Vb 1
\& # virt\-resize indisk outdisk
.Ve
.Sp
-This command just copies disk image \f(CW\*(C`indisk\*(C'\fR to disk image \f(CW\*(C`outdisk\*(C'\fR
-\&\fIwithout\fR resizing or changing any existing partitions. If \f(CW\*(C`outdisk\*(C'\fR is
-larger, then an extra, empty partition is created at the end of the disk
-covering the extra space. If \f(CW\*(C`outdisk\*(C'\fR is smaller, then it will give an
-error.
+This command just copies disk image \f(CW\*(C`indisk\*(C'\fR to disk image \f(CW\*(C`outdisk\*(C'\fR \fIwithout\fR resizing or changing any existing partitions. If \f(CW\*(C`outdisk\*(C'\fR is larger, then an extra, empty partition is created at the end of the disk covering the extra space. If \f(CW\*(C`outdisk\*(C'\fR is smaller, then it will give an error.
.Sp
-More realistically you'd want to expand existing partitions in the disk
-image by passing extra options (for the full list see the \*(L"\s-1OPTIONS\*(R"\s0
-section below).
+More realistically you'd want to expand existing partitions in the disk image by passing extra options (for the full list see the \*(L"\s-1OPTIONS\*(R"\s0 section below).
.Sp
-\&\*(L"\-\-expand\*(R" is the most useful option. It expands the named partition
-within the disk to fill any extra space:
+\&\*(L"\-\-expand\*(R" is the most useful option. It expands the named partition within the disk to fill any extra space:
.Sp
.Vb 1
\& # virt\-resize \-\-expand /dev/sda2 indisk outdisk
.Ve
.Sp
-(In this case, an extra partition is \fInot\fR created at the end of the disk,
-because there will be no unused space).
+(In this case, an extra partition is \fInot\fR created at the end of the disk, because there will be no unused space).
.Sp
-\&\*(L"\-\-resize\*(R" is the other commonly used option. The following would
-increase the size of /dev/sda1 by 200M, and expand /dev/sda2 to fill the
-rest of the available space:
+\&\*(L"\-\-resize\*(R" is the other commonly used option. The following would increase the size of /dev/sda1 by 200M, and expand /dev/sda2 to fill the rest of the available space:
.Sp
.Vb 2
\& # virt\-resize \-\-resize /dev/sda1=+200M \-\-expand /dev/sda2 \e
\& indisk outdisk
.Ve
.Sp
-If the expanded partition in the image contains a filesystem or \s-1LVM PV,\s0 then
-if virt-resize knows how, it will resize the contents, the equivalent of
-calling a command such as \fBpvresize\fR\|(8), \fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8),
-\&\fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), or \fBresize.f2fs\fR\|(8). However virt-resize
-does not know how to resize some filesystems, so you would have to online
-resize them after booting the guest.
+If the expanded partition in the image contains a filesystem or \s-1LVM PV,\s0 then if virt-resize knows how, it will resize the contents, the equivalent of calling a command such as \fBpvresize\fR\|(8), \fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), or \fBresize.f2fs\fR\|(8). However virt-resize does not know how to resize some filesystems, so you would have to online resize them after booting the guest.
.Sp
.Vb 1
\& # virt\-resize \-\-expand /dev/sda2 nbd://example.com outdisk
.Ve
.Sp
-The input disk can be a \s-1URI,\s0 in order to use a remote disk as the source.
-The \s-1URI\s0 format is compatible with guestfish. See \*(L"\s-1ADDING
-REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
+The input disk can be a \s-1URI,\s0 in order to use a remote disk as the source. The \s-1URI\s0 format is compatible with guestfish. See \*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
.Sp
他のオプションは以下に記載しています。
.IP "6. テストします" 4
\& # virsh edit guestname
.Ve
.Sp
-<source ...>
-を変更します、http://libvirt.org/formatdomain.html#elementsDisks を参照してください。
+<source ...> を変更します、http://libvirt.org/formatdomain.html#elementsDisks を参照してください。
.Sp
Then start up the domain with the new, resized disk:
.Sp
\& # virsh start guestname
.Ve
.Sp
-and check that it still works. See also the \*(L"\s-1NOTES\*(R"\s0 section below for
-additional information.
+and check that it still works. See also the \*(L"\s-1NOTES\*(R"\s0 section below for additional information.
.IP "7. Resize LVs etc inside the guest" 4
.IX Item "7. Resize LVs etc inside the guest"
(This can also be done offline using \fBguestfish\fR\|(1))
.Sp
-Once the guest has booted you should see the new space available, at least
-for filesystems that virt-resize knows how to resize, and for PVs. The user
-may need to resize LVs inside PVs, and also resize filesystem types that
-virt-resize does not know how to expand.
+Once the guest has booted you should see the new space available, at least for filesystems that virt-resize knows how to resize, and for PVs. The user may need to resize LVs inside PVs, and also resize filesystem types that virt-resize does not know how to expand.
.SS "仮想マシンのディスクの縮小"
.IX Subsection "仮想マシンのディスクの縮小"
縮小は拡張よりもいくらか複雑です。ここでは概要のみを示します。
.PP
-Firstly virt-resize will not attempt to shrink any partition content (PVs,
-filesystems). The user has to shrink content before passing the disk image
-to virt-resize, and virt-resize will check that the content has been shrunk
-properly.
+Firstly virt-resize will not attempt to shrink any partition content (PVs, filesystems). The user has to shrink content before passing the disk image to virt-resize, and virt-resize will check that the content has been shrunk properly.
.PP
(Shrinking can also be done offline using \fBguestfish\fR\|(1))
.PP
-After shrinking PVs and filesystems, shut down the guest, and proceed with
-steps 3 and 4 above to allocate a new disk image.
+After shrinking PVs and filesystems, shut down the guest, and proceed with steps 3 and 4 above to allocate a new disk image.
.PP
Then run virt-resize with any of the \fI\-\-shrink\fR and/or \fI\-\-resize\fR options.
.SS "\s-1IGNORING OR DELETING PARTITIONS\s0"
.IX Subsection "IGNORING OR DELETING PARTITIONS"
-virt-resize also gives a convenient way to ignore or delete partitions when
-copying from the input disk to the output disk. Ignoring a partition speeds
-up the copy where you don't care about the existing contents of a
-partition. Deleting a partition removes it completely, but note that it
-also renumbers any partitions after the one which is deleted, which can
-leave some guests unbootable.
+virt-resize also gives a convenient way to ignore or delete partitions when copying from the input disk to the output disk. Ignoring a partition speeds up the copy where you don't care about the existing contents of a partition. Deleting a partition removes it completely, but note that it also renumbers any partitions after the one which is deleted, which can leave some guests unbootable.
.SS "\s-1QCOW2 AND\s0 NON-SPARSE \s-1RAW FORMATS\s0"
.IX Subsection "QCOW2 AND NON-SPARSE RAW FORMATS"
-If the input disk is in qcow2 format, then you may prefer that the output is
-in qcow2 format as well. Alternately, virt-resize can convert the format on
-the fly. The output format is simply determined by the format of the empty
-output container that you provide. Thus to create qcow2 output, use:
+If the input disk is in qcow2 format, then you may prefer that the output is in qcow2 format as well. Alternately, virt-resize can convert the format on the fly. The output format is simply determined by the format of the empty output container that you provide. Thus to create qcow2 output, use:
.PP
.Vb 1
\& qemu\-img create \-f qcow2 \-o preallocation=metadata outdisk [size]
\& fallocate \-l size outdisk
.Ve
.PP
-(on older systems that don’t have the \fBfallocate\fR\|(1) command use \f(CW\*(C`dd
-if=/dev/zero of=outdisk bs=1M count=..\*(C'\fR)
+(on older systems that don’t have the \fBfallocate\fR\|(1) command use \f(CW\*(C`dd if=/dev/zero of=outdisk bs=1M count=..\*(C'\fR)
.SS "論理パーティション"
.IX Subsection "論理パーティション"
-Logical partitions (a.k.a. \fI/dev/sda5+\fR on disks using \s-1DOS\s0 partition
-tables) cannot be resized.
+Logical partitions (a.k.a. \fI/dev/sda5+\fR on disks using \s-1DOS\s0 partition tables) cannot be resized.
.PP
-To understand what is going on, firstly one of the four partitions
-\&\fI/dev/sda1\-4\fR will have \s-1MBR\s0 partition type \f(CW05\fR or \f(CW\*(C`0f\*(C'\fR. This is called
-the \fBextended partition\fR. Use \fBvirt\-filesystems\fR\|(1) to see the \s-1MBR\s0
-partition type.
+To understand what is going on, firstly one of the four partitions \fI/dev/sda1\-4\fR will have \s-1MBR\s0 partition type \f(CW05\fR or \f(CW\*(C`0f\*(C'\fR. This is called the \fBextended partition\fR. Use \fBvirt\-filesystems\fR\|(1) to see the \s-1MBR\s0 partition type.
.PP
Logical partitions live inside the extended partition.
.PP
-The extended partition can be expanded, but not shrunk (unless you force it,
-which is not advisable). When the extended partition is copied across, all
-the logical partitions contained inside are copied over implicitly.
-Virt-resize does not look inside the extended partition, so it copies the
-logical partitions blindly.
+The extended partition can be expanded, but not shrunk (unless you force it, which is not advisable). When the extended partition is copied across, all the logical partitions contained inside are copied over implicitly. Virt-resize does not look inside the extended partition, so it copies the logical partitions blindly.
.PP
-You cannot specify a logical partition (\fI/dev/sda5+\fR) at all on the command
-line. Doing so will give an error.
+You cannot specify a logical partition (\fI/dev/sda5+\fR) at all on the command line. Doing so will give an error.
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-align\-first\fR \fBalways\fR" 4
.IX Item "--align-first always"
.PD
-Align the first partition for improved performance (see also the
-\&\fI\-\-alignment\fR option).
+Align the first partition for improved performance (see also the \fI\-\-alignment\fR option).
.Sp
-The default is \fI\-\-align\-first auto\fR which only aligns the first partition
-if it is safe to do so. That is, only when we know how to fix the
-bootloader automatically, and at the moment that can only be done for
-Windows guests.
+The default is \fI\-\-align\-first auto\fR which only aligns the first partition if it is safe to do so. That is, only when we know how to fix the bootloader automatically, and at the moment that can only be done for Windows guests.
.Sp
-\&\fI\-\-align\-first never\fR means we never move the first partition. This is the
-safest option. Try this if the guest does not boot after resizing.
+\&\fI\-\-align\-first never\fR means we never move the first partition. This is the safest option. Try this if the guest does not boot after resizing.
.Sp
-\&\fI\-\-align\-first always\fR means we always align the first partition (if it
-needs to be aligned). For some guests this will break the bootloader,
-making the guest unbootable.
+\&\fI\-\-align\-first always\fR means we always align the first partition (if it needs to be aligned). For some guests this will break the bootloader, making the guest unbootable.
.IP "\fB\-\-alignment\fR N" 4
.IX Item "--alignment N"
-Set the alignment of partitions to \f(CW\*(C`N\*(C'\fR sectors. The default in virt-resize
-< 1.13.19 was 64 sectors, and after that is 128 sectors.
+Set the alignment of partitions to \f(CW\*(C`N\*(C'\fR sectors. The default in virt-resize < 1.13.19 was 64 sectors, and after that is 128 sectors.
.Sp
-Assuming 512 byte sector size inside the guest, here are some suitable
-values for this:
+Assuming 512 byte sector size inside the guest, here are some suitable values for this:
.RS 4
.IP "\fI\-\-alignment 1\fR (512 バイト)" 4
.IX Item "--alignment 1 (512 バイト)"
-The partitions would be packed together as closely as possible, but would be
-completely unaligned. In some cases this can cause very poor performance.
-See \fBvirt\-alignment\-scan\fR\|(1) for further details.
+The partitions would be packed together as closely as possible, but would be completely unaligned. In some cases this can cause very poor performance. See \fBvirt\-alignment\-scan\fR\|(1) for further details.
.IP "\fI\-\-alignment 8\fR (4K)" 4
.IX Item "--alignment 8 (4K)"
-This would be the minimum acceptable alignment for reasonable performance on
-modern hosts.
+This would be the minimum acceptable alignment for reasonable performance on modern hosts.
.IP "\fI\-\-alignment 128\fR (64K)" 4
.IX Item "--alignment 128 (64K)"
-This alignment provides good performance when the host is using high end
-network storage.
+This alignment provides good performance when the host is using high end network storage.
.IP "\fI\-\-alignment 2048\fR (1M)" 4
.IX Item "--alignment 2048 (1M)"
-This is the standard alignment used by all newly installed guests since
-around 2008.
+This is the standard alignment used by all newly installed guests since around 2008.
.RE
.RS 4
.RE
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-d\fR" 4
.IX Item "-d"
.PD 0
デバッグメッセージを有効にします。
.IP "\fB\-\-delete\fR \s-1PART\s0" 4
.IX Item "--delete PART"
-Delete the named partition. It would be more accurate to describe this as
-\&\*(L"don't copy it over\*(R", since virt-resize doesn't do in-place changes and the
-original disk image is left intact.
+Delete the named partition. It would be more accurate to describe this as \*(L"don't copy it over\*(R", since virt-resize doesn't do in-place changes and the original disk image is left intact.
.Sp
-Note that when you delete a partition, then anything contained in the
-partition is also deleted. Furthermore, this causes any partitions that
-come after to be \fIrenumbered\fR, which can easily make your guest unbootable.
+Note that when you delete a partition, then anything contained in the partition is also deleted. Furthermore, this causes any partitions that come after to be \fIrenumbered\fR, which can easily make your guest unbootable.
.Sp
このオプションは複数回指定できます。
.IP "\fB\-\-expand\fR \s-1PART\s0" 4
.IX Item "--expand PART"
-Expand the named partition so it uses up all extra space (space left over
-after any other resize changes that you request have been done).
+Expand the named partition so it uses up all extra space (space left over after any other resize changes that you request have been done).
.Sp
-If virt-resize knows how, it will expand the direct content of the
-partition. For example, if the partition is an \s-1LVM PV,\s0 it will expand the
-\&\s-1PV\s0 to fit (like calling \fBpvresize\fR\|(8)). Virt-resize leaves any other
-content it doesn't know about alone.
+If virt-resize knows how, it will expand the direct content of the partition. For example, if the partition is an \s-1LVM PV,\s0 it will expand the \s-1PV\s0 to fit (like calling \fBpvresize\fR\|(8)). Virt-resize leaves any other content it doesn't know about alone.
.Sp
Currently virt-resize can resize:
.RS 4
.IP "\(bu" 4
\&\s-1NTFS\s0 filesystems, if libguestfs was compiled with support for \s-1NTFS.\s0
.Sp
-The filesystem must have been shut down consistently last time it was used.
-Additionally, \fBntfsresize\fR\|(8) marks the resized filesystem as requiring a
-consistency check, so at the first boot after resizing Windows will check
-the disk.
+The filesystem must have been shut down consistently last time it was used. Additionally, \fBntfsresize\fR\|(8) marks the resized filesystem as requiring a consistency check, so at the first boot after resizing Windows will check the disk.
.IP "\(bu" 4
-\&\s-1LVM\s0 PVs (physical volumes). virt-resize does not usually resize anything
-inside the \s-1PV,\s0 but see the \fI\-\-LV\-expand\fR option. The user could also
-resize LVs as desired after boot.
+\&\s-1LVM\s0 PVs (physical volumes). virt-resize does not usually resize anything inside the \s-1PV,\s0 but see the \fI\-\-LV\-expand\fR option. The user could also resize LVs as desired after boot.
.IP "\(bu" 4
Btrfs filesystems, if libguestfs was compiled with support for btrfs.
.IP "\(bu" 4
.IP "\(bu" 4
Linux swap partitions.
.Sp
-Please note that libguestfs \fIdestroys\fR the existing swap content by
-recreating it with \f(CW\*(C`mkswap\*(C'\fR, so this should not be used when the guest is
-suspended.
+Please note that libguestfs \fIdestroys\fR the existing swap content by recreating it with \f(CW\*(C`mkswap\*(C'\fR, so this should not be used when the guest is suspended.
.IP "\(bu" 4
f2fs filesystems, if libguestfs was compiled with support for f2fs.
.RE
.RE
.IP "\fB\-\-format\fR \fBraw\fR" 4
.IX Item "--format raw"
-Specify the format of the input disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the input disk image. If this flag is not given then it is auto-detected from the image itself.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.Sp
-Note that this option \fIdoes not\fR affect the output format. See \*(L"\s-1QCOW2
-AND\s0 NON-SPARSE \s-1RAW FORMATS\*(R"\s0.
+Note that this option \fIdoes not\fR affect the output format. See \*(L"\s-1QCOW2 AND\s0 NON-SPARSE \s-1RAW FORMATS\*(R"\s0.
.IP "\fB\-\-ignore\fR \s-1PART\s0" 4
.IX Item "--ignore PART"
-Ignore the named partition. Effectively this means the partition is
-allocated on the destination disk, but the content is not copied across from
-the source disk. The content of the partition will be blank (all zero
-bytes).
+Ignore the named partition. Effectively this means the partition is allocated on the destination disk, but the content is not copied across from the source disk. The content of the partition will be blank (all zero bytes).
.Sp
このオプションは複数回指定できます。
.IP "\fB\-\-LV\-expand\fR \s-1LOGVOL\s0" 4
.IX Item "--LV-expand LOGVOL"
-This takes the logical volume and, as a final step, expands it to fill all
-the space available in its volume group. A typical usage, assuming a Linux
-guest with a single \s-1PV\s0 \fI/dev/sda2\fR and a root device called
-\&\fI/dev/vg_guest/lv_root\fR would be:
+This takes the logical volume and, as a final step, expands it to fill all the space available in its volume group. A typical usage, assuming a Linux guest with a single \s-1PV\s0 \fI/dev/sda2\fR and a root device called \fI/dev/vg_guest/lv_root\fR would be:
.Sp
.Vb 2
\& virt\-resize indisk outdisk \e
\& \-\-expand /dev/sda2 \-\-LV\-expand /dev/vg_guest/lv_root
.Ve
.Sp
-This would first expand the partition (and \s-1PV\s0), and then expand the root
-device to fill the extra space in the \s-1PV.\s0
+This would first expand the partition (and \s-1PV\s0), and then expand the root device to fill the extra space in the \s-1PV.\s0
.Sp
-The contents of the \s-1LV\s0 are also resized if virt-resize knows how to do
-that. You can stop virt-resize from trying to expand the content by using
-the option \fI\-\-no\-expand\-content\fR.
+The contents of the \s-1LV\s0 are also resized if virt-resize knows how to do that. You can stop virt-resize from trying to expand the content by using the option \fI\-\-no\-expand\-content\fR.
.Sp
仮想マシンにあるファイルシステムを一覧表示するには \fBvirt\-filesystems\fR\|(1) を使用します。
.Sp
-You can give this option multiple times, \fIbut\fR it doesn't make sense to do
-this unless the logical volumes you specify are all in different volume
-groups.
+You can give this option multiple times, \fIbut\fR it doesn't make sense to do this unless the logical volumes you specify are all in different volume groups.
.IP "\fB\-\-machine\-readable\fR" 4
.IX Item "--machine-readable"
.PD 0
Print a summary of what would be done, but don’t do anything.
.IP "\fB\-\-no\-copy\-boot\-loader\fR" 4
.IX Item "--no-copy-boot-loader"
-By default, virt-resize copies over some sectors at the start of the disk
-(up to the beginning of the first partition). Commonly these sectors
-contain the Master Boot Record (\s-1MBR\s0) and the boot loader, and are required
-in order for the guest to boot correctly.
+By default, virt-resize copies over some sectors at the start of the disk (up to the beginning of the first partition). Commonly these sectors contain the Master Boot Record (\s-1MBR\s0) and the boot loader, and are required in order for the guest to boot correctly.
.Sp
-If you specify this flag, then this initial copy is not done. You may need
-to reinstall the boot loader in this case.
+If you specify this flag, then this initial copy is not done. You may need to reinstall the boot loader in this case.
.IP "\fB\-\-no\-extra\-partition\fR" 4
.IX Item "--no-extra-partition"
-By default, virt-resize creates an extra partition if there is any extra,
-unused space after all resizing has happened. Use this option to prevent
-the extra partition from being created. If you do this then the extra space
-will be inaccessible until you run fdisk, parted, or some other partitioning
-tool in the guest.
-.Sp
-Note that if the surplus space is smaller than 10 \s-1MB,\s0 no extra partition
-will be created.
+By default, virt-resize creates an extra partition if there is any extra, unused space after all resizing has happened. Use this option to prevent the extra partition from being created. If you do this then the extra space will be inaccessible until you run fdisk, parted, or some other partitioning tool in the guest.
+.Sp
+Note that if the surplus space is smaller than 10 \s-1MB,\s0 no extra partition will be created.
.IP "\fB\-\-no\-expand\-content\fR" 4
.IX Item "--no-expand-content"
-By default, virt-resize will try to expand the direct contents of
-partitions, if it knows how (see \fI\-\-expand\fR option above).
+By default, virt-resize will try to expand the direct contents of partitions, if it knows how (see \fI\-\-expand\fR option above).
.Sp
\&\fI\-\-no\-expand\-content\fR オプションを指定すると、virt\-resize はこれを試行しません。
.IP "\fB\-\-no\-sparse\fR" 4
Turn off sparse copying. See \*(L"\s-1SPARSE COPYING\*(R"\s0 below.
.IP "\fB\-\-ntfsresize\-force\fR" 4
.IX Item "--ntfsresize-force"
-\&\fBntfsresize\fR\|(8) に \fI\-\-force\fR オプションを渡します。これにより、NTFS
-ディスクが整合性の確認が必要であるという印をつけたときでも、容量の変更を許可します。Windows
-仮想マシンを各容量において起動することなく、何回も容量変更したいならば、このオプションを使用する必要があります。
+\&\fBntfsresize\fR\|(8) に \fI\-\-force\fR オプションを渡します。これにより、NTFS ディスクが整合性の確認が必要であるという印をつけたときでも、容量の変更を許可します。Windows 仮想マシンを各容量において起動することなく、何回も容量変更したいならば、このオプションを使用する必要があります。
.IP "\fB\-\-output\-format\fR \fBraw\fR" 4
.IX Item "--output-format raw"
-Specify the format of the output disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the output disk image. If this flag is not given then it is auto-detected from the image itself.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.Sp
-Note that this option \fIdoes not create\fR the output format. This option
-just tells libguestfs what it is so it doesn't try to guess it. You still
-need to create the output disk with the right format. See \*(L"\s-1QCOW2 AND\s0
-NON-SPARSE \s-1RAW FORMATS\*(R"\s0.
+Note that this option \fIdoes not create\fR the output format. This option just tells libguestfs what it is so it doesn't try to guess it. You still need to create the output disk with the right format. See \*(L"\s-1QCOW2 AND\s0 NON-SPARSE \s-1RAW FORMATS\*(R"\s0.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
Don’t print the summary.
.IP "\fB\-\-resize\fR PART=SIZE" 4
.IX Item "--resize PART=SIZE"
-Resize the named partition (expanding or shrinking it) so that it has the
-given size.
+Resize the named partition (expanding or shrinking it) so that it has the given size.
.Sp
-\&\f(CW\*(C`SIZE\*(C'\fR can be expressed as an absolute number followed by b/K/M/G to mean
-bytes, Kilobytes, Megabytes, or Gigabytes; or as a percentage of the current
-size; or as a relative number or percentage. For example:
+\&\f(CW\*(C`SIZE\*(C'\fR can be expressed as an absolute number followed by b/K/M/G to mean bytes, Kilobytes, Megabytes, or Gigabytes; or as a percentage of the current size; or as a relative number or percentage. For example:
.Sp
.Vb 1
\& \-\-resize /dev/sda2=10G
\& \-\-resize /dev/sda1=\-10%
.Ve
.Sp
-You can increase the size of any partition. Virt-resize will expand the
-direct content of the partition if it knows how (see \fI\-\-expand\fR above).
+You can increase the size of any partition. Virt-resize will expand the direct content of the partition if it knows how (see \fI\-\-expand\fR above).
.Sp
-You can only \fIdecrease\fR the size of partitions that contain filesystems or
-PVs which have already been shrunk. Virt-resize will check this has been
-done before proceeding, or else will print an error (see also
-\&\fI\-\-resize\-force\fR).
+You can only \fIdecrease\fR the size of partitions that contain filesystems or PVs which have already been shrunk. Virt-resize will check this has been done before proceeding, or else will print an error (see also \fI\-\-resize\-force\fR).
.Sp
このオプションは複数回指定できます。
.IP "\fB\-\-resize\-force\fR PART=SIZE" 4
.IX Item "--resize-force PART=SIZE"
-This is the same as \fI\-\-resize\fR except that it will let you decrease the
-size of any partition. Generally this means you will lose any data which
-was at the end of the partition you shrink, but you may not care about that
-(eg. if shrinking an unused partition, or if you can easily recreate it such
-as a swap partition).
+This is the same as \fI\-\-resize\fR except that it will let you decrease the size of any partition. Generally this means you will lose any data which was at the end of the partition you shrink, but you may not care about that (eg. if shrinking an unused partition, or if you can easily recreate it such as a swap partition).
.Sp
\&\fI\-\-ignore\fR オプション参照。
.IP "\fB\-\-shrink\fR \s-1PART\s0" 4
.IX Item "--shrink PART"
-Shrink the named partition until the overall disk image fits in the
-destination. The named partition \fBmust\fR contain a filesystem or \s-1PV\s0 which
-has already been shrunk using another tool (eg. \fBguestfish\fR\|(1) or other
-online tools). Virt-resize will check this and give an error if it has not
-been done.
-.Sp
-The amount by which the overall disk must be shrunk (after carrying out all
-other operations requested by the user) is called the \*(L"deficit\*(R". For
-example, a straight copy (assume no other operations) from a 5GB disk image
-to a 4GB disk image results in a 1GB deficit. In this case, virt-resize
-would give an error unless the user specified a partition to shrink and that
-partition had more than a gigabyte of free space.
+Shrink the named partition until the overall disk image fits in the destination. The named partition \fBmust\fR contain a filesystem or \s-1PV\s0 which has already been shrunk using another tool (eg. \fBguestfish\fR\|(1) or other online tools). Virt-resize will check this and give an error if it has not been done.
+.Sp
+The amount by which the overall disk must be shrunk (after carrying out all other operations requested by the user) is called the \*(L"deficit\*(R". For example, a straight copy (assume no other operations) from a 5GB disk image to a 4GB disk image results in a 1GB deficit. In this case, virt-resize would give an error unless the user specified a partition to shrink and that partition had more than a gigabyte of free space.
.Sp
Note that you cannot use \fI\-\-expand\fR and \fI\-\-shrink\fR together.
.IP "\fB\-\-unknown\-filesystems\fR \fBignore\fR" 4
.IP "\fB\-\-unknown\-filesystems\fR \fBerror\fR" 4
.IX Item "--unknown-filesystems error"
.PD
-Configure the behaviour of virt-resize when asking to expand a filesystem,
-and neither libguestfs has the support it, nor virt-resize knows how to
-expand the content of the filesystem.
+Configure the behaviour of virt-resize when asking to expand a filesystem, and neither libguestfs has the support it, nor virt-resize knows how to expand the content of the filesystem.
.Sp
-\&\fI\-\-unknown\-filesystems ignore\fR will cause virt-resize to silently ignore
-such filesystems, and nothing is printed about them.
+\&\fI\-\-unknown\-filesystems ignore\fR will cause virt-resize to silently ignore such filesystems, and nothing is printed about them.
.Sp
-\&\fI\-\-unknown\-filesystems warn\fR (the default behaviour) will cause virt-resize
-to warn for each of the filesystem that cannot be expanded, but still
-continuing to resize the disk.
+\&\fI\-\-unknown\-filesystems warn\fR (the default behaviour) will cause virt-resize to warn for each of the filesystem that cannot be expanded, but still continuing to resize the disk.
.Sp
-\&\fI\-\-unknown\-filesystems error\fR will cause virt-resize to error out at the
-first filesystem that cannot be expanded.
+\&\fI\-\-unknown\-filesystems error\fR will cause virt-resize to error out at the first filesystem that cannot be expanded.
.Sp
-See also \*(L"unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on
-\&\s-1DEVICE/LV\*(R"\s0.
+See also \*(L"unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV\*(R"\s0.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.SH "マシン可読な出力"
.IX Header "マシン可読な出力"
-\&\fI\-\-machine\-readable\fR オプションはよりマシンに易しい出力を作成するために使用できます。これは他のプログラムや \s-1GUI\s0 などから
-virt-resize を呼び出すときに有用です。
+\&\fI\-\-machine\-readable\fR オプションはよりマシンに易しい出力を作成するために使用できます。これは他のプログラムや \s-1GUI\s0 などから virt-resize を呼び出すときに有用です。
.PP
このオプションを使用するには 2 通りの方法があります。
.PP
-Firstly use the option on its own to query the capabilities of the
-virt-resize binary. Typical output looks like this:
+Firstly use the option on its own to query the capabilities of the virt-resize binary. Typical output looks like this:
.PP
.Vb 6
\& $ virt\-resize \-\-machine\-readable
\& btrfs
.Ve
.PP
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
.PP
-Secondly use the option in conjunction with other options to make the
-regular program output more machine friendly.
+Secondly use the option in conjunction with other options to make the regular program output more machine friendly.
.PP
At the moment this means:
.IP "1." 4
-Progress bar messages can be parsed from stdout by looking for this regular
-expression:
+Progress bar messages can be parsed from stdout by looking for this regular expression:
.Sp
.Vb 1
\& ^[0\-9]+/[0\-9]+$
.Ve
.IP "2." 4
-The calling program should treat messages sent to stdout (except for
-progress bar messages) as status messages. They can be logged and/or
-displayed to the user.
+The calling program should treat messages sent to stdout (except for progress bar messages) as status messages. They can be logged and/or displayed to the user.
.IP "3." 4
-The calling program should treat messages sent to stderr as error messages.
-In addition, virt-resize exits with a non-zero status code if there was a
-fatal error.
+The calling program should treat messages sent to stderr as error messages. In addition, virt-resize exits with a non-zero status code if there was a fatal error.
.PP
-Versions of the program prior to 1.13.9 did not support the
-\&\fI\-\-machine\-readable\fR option and will return an error.
+Versions of the program prior to 1.13.9 did not support the \fI\-\-machine\-readable\fR option and will return an error.
.PP
-It is possible to specify a format string for controlling the output; see
-\&\*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
+It is possible to specify a format string for controlling the output; see \*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "注記"
.IX Header "注記"
.ie n .SS """Partition 1 does not end on cylinder boundary."""
.el .SS "``Partition 1 does not end on cylinder boundary.''"
.IX Subsection "Partition 1 does not end on cylinder boundary."
-Virt-resize aligns partitions to multiples of 128 sectors (see the
-\&\fI\-\-alignment\fR parameter). Usually this means the partitions will not be
-aligned to the ancient \s-1CHS\s0 geometry. However \s-1CHS\s0 geometry is meaningless
-for disks manufactured since the early 1990s, and doubly so for virtual hard
-drives. Alignment of partitions to cylinders is not required by any modern
-operating system.
+Virt-resize aligns partitions to multiples of 128 sectors (see the \fI\-\-alignment\fR parameter). Usually this means the partitions will not be aligned to the ancient \s-1CHS\s0 geometry. However \s-1CHS\s0 geometry is meaningless for disks manufactured since the early 1990s, and doubly so for virtual hard drives. Alignment of partitions to cylinders is not required by any modern operating system.
.ie n .SS "\s-1GUEST BOOT STUCK AT ""GRUB""\s0"
.el .SS "\s-1GUEST BOOT STUCK AT ``GRUB''\s0"
.IX Subsection "GUEST BOOT STUCK AT GRUB"
-If a Linux guest does not boot after resizing, and the boot is stuck after
-printing \f(CW\*(C`GRUB\*(C'\fR on the console, try reinstalling grub.
+If a Linux guest does not boot after resizing, and the boot is stuck after printing \f(CW\*(C`GRUB\*(C'\fR on the console, try reinstalling grub.
.PP
.Vb 6
\& guestfish \-i \-a newdisk
\& ><fs> exit
.Ve
.PP
-For more flexible guest reconfiguration, including if you need to specify
-other parameters to grub-install, use \fBvirt\-rescue\fR\|(1).
+For more flexible guest reconfiguration, including if you need to specify other parameters to grub-install, use \fBvirt\-rescue\fR\|(1).
.SS "\s-1RESIZING WINDOWS BOOT PARTITIONS\s0"
.IX Subsection "RESIZING WINDOWS BOOT PARTITIONS"
-In Windows Vista and later versions, Microsoft switched to using a separate
-boot partition. In these VMs, typically \fI/dev/sda1\fR is the boot partition
-and \fI/dev/sda2\fR is the main (C:) drive. Resizing the first (boot)
-partition causes the bootloader to fail with \f(CW0xC0000225\fR error. Resizing
-the second partition (ie. C: drive) should work.
+In Windows Vista and later versions, Microsoft switched to using a separate boot partition. In these VMs, typically \fI/dev/sda1\fR is the boot partition and \fI/dev/sda2\fR is the main (C:) drive. Resizing the first (boot) partition causes the bootloader to fail with \f(CW0xC0000225\fR error. Resizing the second partition (ie. C: drive) should work.
.SS "\s-1WINDOWS CHKDSK\s0"
.IX Subsection "WINDOWS CHKDSK"
-Windows disks which use \s-1NTFS\s0 must be consistent before virt-resize can be
-used. If the ntfsresize operation fails, try booting the original \s-1VM\s0 and
-running \f(CW\*(C`chkdsk /f\*(C'\fR on all \s-1NTFS\s0 partitions, then shut down the \s-1VM\s0 cleanly.
-For further information see:
-https://bugzilla.redhat.com/show_bug.cgi?id=975753
-.PP
-\&\fIAfter resize\fR Windows may initiate a lengthy \*(L"chkdsk\*(R" on first boot if
-\&\s-1NTFS\s0 partitions have been expanded. This is just a safety check and (unless
-it find errors) is nothing to worry about.
+Windows disks which use \s-1NTFS\s0 must be consistent before virt-resize can be used. If the ntfsresize operation fails, try booting the original \s-1VM\s0 and running \f(CW\*(C`chkdsk /f\*(C'\fR on all \s-1NTFS\s0 partitions, then shut down the \s-1VM\s0 cleanly. For further information see: https://bugzilla.redhat.com/show_bug.cgi?id=975753
+.PP
+\&\fIAfter resize\fR Windows may initiate a lengthy \*(L"chkdsk\*(R" on first boot if \s-1NTFS\s0 partitions have been expanded. This is just a safety check and (unless it find errors) is nothing to worry about.
.SS "Windows \s-1UNMOUNTABLE_BOOT_VOLUME BSOD\s0"
.IX Subsection "Windows UNMOUNTABLE_BOOT_VOLUME BSOD"
-Windows 仮想マシンを sysprep して、virt\-resize を用いて容量を変更した後、仮想マシンが
-\&\f(CW\*(C`UNMOUNTABLE_BOOT_VOLUME\*(C'\fR \s-1BSOD\s0 で起動に失敗するかもしれません。このエラーは sysprep.inf ファイルに
-\&\f(CW\*(C`ExtendOemPartition=1\*(C'\fR があることにより引き起こされます。sysprep
-する前にこの行を削除することにより、この問題を解決できます。
+Windows 仮想マシンを sysprep して、virt\-resize を用いて容量を変更した後、仮想マシンが \f(CW\*(C`UNMOUNTABLE_BOOT_VOLUME\*(C'\fR \s-1BSOD\s0 で起動に失敗するかもしれません。このエラーは sysprep.inf ファイルに \f(CW\*(C`ExtendOemPartition=1\*(C'\fR があることにより引き起こされます。sysprep する前にこの行を削除することにより、この問題を解決できます。
.SS "\s-1WINDOWS 8\s0"
.IX Subsection "WINDOWS 8"
-Windows 8 \*(L"fast startup\*(R" can prevent virt-resize from resizing \s-1NTFS\s0
-partitions. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST
-STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
+Windows 8 \*(L"fast startup\*(R" can prevent virt-resize from resizing \s-1NTFS\s0 partitions. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
.SS "\s-1SPARSE COPYING\s0"
.IX Subsection "SPARSE COPYING"
You should create a fresh, zeroed target disk image for virt-resize to use.
.PP
-Virt-resize by default performs sparse copying. This means that it does not
-copy blocks from the source disk which are all zeroes. This improves speed
-and efficiency, but will produce incorrect results if the target disk image
-contains unzeroed data.
+Virt-resize by default performs sparse copying. This means that it does not copy blocks from the source disk which are all zeroes. This improves speed and efficiency, but will produce incorrect results if the target disk image contains unzeroed data.
.PP
-The main time this can be a problem is if the target is a host partition
-(eg. \f(CW\*(C`virt\-resize source.img /dev/sda4\*(C'\fR) because the usual partitioning
-tools tend to leave whatever data happened to be on the disk before.
+The main time this can be a problem is if the target is a host partition (eg. \f(CW\*(C`virt\-resize source.img /dev/sda4\*(C'\fR) because the usual partitioning tools tend to leave whatever data happened to be on the disk before.
.PP
-If you have to reuse a target which contains data already, you should use
-the \fI\-\-no\-sparse\fR option. Note this can be much slower.
+If you have to reuse a target which contains data already, you should use the \fI\-\-no\-sparse\fR option. Note this can be much slower.
.ie n .SS """unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV""\s0"
.el .SS "``unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV''\s0"
.IX Subsection "unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV"
-Virt-resize was asked to expand a partition or a logical volume containing a
-filesystem with the type \f(CW\*(C`TYPE\*(C'\fR, but there is no available nor known
-expanding method for that filesystem.
+Virt-resize was asked to expand a partition or a logical volume containing a filesystem with the type \f(CW\*(C`TYPE\*(C'\fR, but there is no available nor known expanding method for that filesystem.
.PP
This may be due to either of the following:
.IP "1." 4
-There corresponding filesystem is not available in libguestfs, because there
-is no proper package in the host with utilities for it. This is usually the
-case for \f(CW\*(C`btrfs\*(C'\fR, \f(CW\*(C`ntfs\*(C'\fR, \f(CW\*(C`xfs\*(C'\fR, and \f(CW\*(C`f2fs\*(C'\fR filesystems.
+There corresponding filesystem is not available in libguestfs, because there is no proper package in the host with utilities for it. This is usually the case for \f(CW\*(C`btrfs\*(C'\fR, \f(CW\*(C`ntfs\*(C'\fR, \f(CW\*(C`xfs\*(C'\fR, and \f(CW\*(C`f2fs\*(C'\fR filesystems.
.Sp
Check the results of:
.Sp
\& guestfish \-a /dev/null run : filesystem_available TYPE
.Ve
.Sp
-In this case, it is enough to install the proper packages adding support for
-them. For example, \f(CW\*(C`libguestfs\-xfs\*(C'\fR on Red Hat Enterprise Linux, CentOS,
-Debian, Ubuntu, and distributions derived from them, for supporting the
-\&\f(CW\*(C`xfs\*(C'\fR filesystem.
+In this case, it is enough to install the proper packages adding support for them. For example, \f(CW\*(C`libguestfs\-xfs\*(C'\fR on Red Hat Enterprise Linux, CentOS, Debian, Ubuntu, and distributions derived from them, for supporting the \f(CW\*(C`xfs\*(C'\fR filesystem.
.IP "2." 4
Virt-resize has no support for expanding that type of filesystem.
.Sp
-In this case, there’s nothing that can be done to let virt-resize expand
-that type of filesystem.
+In this case, there’s nothing that can be done to let virt-resize expand that type of filesystem.
.PP
-In both cases, virt-resize will not expand the mentioned filesystem; the
-result (unless \fI\-\-unknown\-filesystems error\fR is specified) is that the
-partitions containing such filesystems will be actually bigger as requested,
-but the filesystems will still be usable at their older sizes.
+In both cases, virt-resize will not expand the mentioned filesystem; the result (unless \fI\-\-unknown\-filesystems error\fR is specified) is that the partitions containing such filesystems will be actually bigger as requested, but the filesystems will still be usable at their older sizes.
.SH "代替ツール"
.IX Header "代替ツール"
-There are several proprietary tools for resizing partitions. We won't
-mention any here.
-.PP
-\&\fBparted\fR\|(8) and its graphical shell gparted can do some types of resizing
-operations on disk images. They can resize and move partitions, but I don't
-think they can do anything with the contents, and they certainly don't
-understand \s-1LVM.\s0
-.PP
-\&\fBguestfish\fR\|(1) can do everything that virt-resize can do and a lot more,
-but at a much lower level. You will probably end up hand-calculating sector
-offsets, which is something that virt-resize was designed to avoid. If you
-want to see the guestfish-equivalent commands that virt-resize runs, use the
-\&\fI\-\-debug\fR flag.
-.PP
-\&\fBdracut\fR\|(8) includes a module called \f(CW\*(C`dracut\-modules\-growroot\*(C'\fR which can
-be used to grow the root partition when the guest first boots up. There is
-documentation for this module in an associated \s-1README\s0 file.
+There are several proprietary tools for resizing partitions. We won't mention any here.
+.PP
+\&\fBparted\fR\|(8) and its graphical shell gparted can do some types of resizing operations on disk images. They can resize and move partitions, but I don't think they can do anything with the contents, and they certainly don't understand \s-1LVM.\s0
+.PP
+\&\fBguestfish\fR\|(1) can do everything that virt-resize can do and a lot more, but at a much lower level. You will probably end up hand-calculating sector offsets, which is something that virt-resize was designed to avoid. If you want to see the guestfish-equivalent commands that virt-resize runs, use the \fI\-\-debug\fR flag.
+.PP
+\&\fBdracut\fR\|(8) includes a module called \f(CW\*(C`dracut\-modules\-growroot\*(C'\fR which can be used to grow the root partition when the guest first boots up. There is documentation for this module in an associated \s-1README\s0 file.
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは、成功すると 0 を、エラーがあると 0 以外を返します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBvirt\-filesystems\fR\|(1), \fBvirt\-df\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1),
-\&\fBlvm\fR\|(8), \fBpvresize\fR\|(8), \fBlvresize\fR\|(8), \fBresize2fs\fR\|(8),
-\&\fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), \fBresize.f2fs\fR\|(8),
-\&\fBvirsh\fR\|(1), \fBparted\fR\|(8), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBgrub\fR\|(8),
-\&\fBgrub\-install\fR\|(8), \fBvirt\-rescue\fR\|(1), \fBvirt\-sparsify\fR\|(1),
-\&\fBvirt\-alignment\-scan\fR\|(1), http://libguestfs.org/.
+\&\fBvirt\-filesystems\fR\|(1), \fBvirt\-df\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBlvm\fR\|(8), \fBpvresize\fR\|(8), \fBlvresize\fR\|(8), \fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), \fBresize.f2fs\fR\|(8), \fBvirsh\fR\|(1), \fBparted\fR\|(8), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBgrub\fR\|(8), \fBgrub\-install\fR\|(8), \fBvirt\-rescue\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirt\-alignment\-scan\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-resize is a tool which can resize a virtual machine disk, making it
-larger or smaller overall, and resizing or deleting any partitions contained
-within.
+Virt-resize is a tool which can resize a virtual machine disk, making it larger or smaller overall, and resizing or deleting any partitions contained within.
-Virt-resize B<cannot> resize disk images in-place. Virt-resize B<should
-not> be used on live virtual machines - for consistent results, shut the
-virtual machine down before resizing it.
+Virt-resize B<cannot> resize disk images in-place. Virt-resize B<should not> be used on live virtual machines - for consistent results, shut the virtual machine down before resizing it.
-If you are not familiar with the associated tools: L<virt-filesystems(1)>
-and L<virt-df(1)>, we recommend you go and read those manual pages first.
+If you are not familiar with the associated tools: L<virt-filesystems(1)> and L<virt-df(1)>, we recommend you go and read those manual pages first.
=head1 例
=item 1.
-This example takes C<olddisk> and resizes it into C<newdisk>, extending one
-of the guest’s partitions to fill the extra 5GB of space:
+This example takes C<olddisk> and resizes it into C<newdisk>, extending one of the guest’s partitions to fill the extra 5GB of space:
virt-filesystems --long -h --all -a olddisk
=item 2.
-As above, but make the /boot partition 200MB bigger, while giving the
-remaining space to /dev/sda2:
+As above, but make the /boot partition 200MB bigger, while giving the remaining space to /dev/sda2:
virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
olddisk newdisk
=item 3.
-As in the first example, but expand a logical volume as the final step.
-This is what you would typically use for Linux guests that use LVM:
+As in the first example, but expand a logical volume as the final step. This is what you would typically use for Linux guests that use LVM:
virt-resize --expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root \
olddisk newdisk
=item 4.
-As in the first example, but the output format will be qcow2 instead of a
-raw disk:
+As in the first example, but the output format will be qcow2 instead of a raw disk:
qemu-img create -f qcow2 -o preallocation=metadata newdisk.qcow2 15G
virt-resize --expand /dev/sda2 olddisk newdisk.qcow2
=item 2. 入力ディスクイメージの位置を探します
-Locate the input disk image (ie. the file or device on the host containing
-the guest’s disk). If the guest is managed by libvirt, you can use C<virsh
-dumpxml> like this to find the disk image name:
+Locate the input disk image (ie. the file or device on the host containing the guest’s disk). If the guest is managed by libvirt, you can use C<virsh dumpxml> like this to find the disk image name:
# virsh dumpxml guestname | xpath /domain/devices/disk/source
Found 1 nodes:
/dev/sda2 partition 7.9G /dev/sda
/dev/sda device 8.0G -
-(This example is a virtual machine with an 8 GB disk which we would like to
-expand up to 10 GB).
+(This example is a virtual machine with an 8 GB disk which we would like to expand up to 10 GB).
=item 4. 出力ディスクを作成します
-Virt-resize cannot do in-place disk modifications. You have to have space
-to store the resized output disk.
+Virt-resize cannot do in-place disk modifications. You have to have space to store the resized output disk.
To store the resized disk image in a file, create a file of a suitable size:
=item 5. 容量を変更します
-virt-resize takes two mandatory parameters, the input disk and the output
-disk (both can be e.g. a device, a file, or a URI to a remote disk). The
-output disk is the one created in the previous step.
+virt-resize takes two mandatory parameters, the input disk and the output disk (both can be e.g. a device, a file, or a URI to a remote disk). The output disk is the one created in the previous step.
# virt-resize indisk outdisk
-This command just copies disk image C<indisk> to disk image C<outdisk>
-I<without> resizing or changing any existing partitions. If C<outdisk> is
-larger, then an extra, empty partition is created at the end of the disk
-covering the extra space. If C<outdisk> is smaller, then it will give an
-error.
+This command just copies disk image C<indisk> to disk image C<outdisk> I<without> resizing or changing any existing partitions. If C<outdisk> is larger, then an extra, empty partition is created at the end of the disk covering the extra space. If C<outdisk> is smaller, then it will give an error.
-More realistically you'd want to expand existing partitions in the disk
-image by passing extra options (for the full list see the L</OPTIONS>
-section below).
+More realistically you'd want to expand existing partitions in the disk image by passing extra options (for the full list see the L</OPTIONS> section below).
-L</--expand> is the most useful option. It expands the named partition
-within the disk to fill any extra space:
+L</--expand> is the most useful option. It expands the named partition within the disk to fill any extra space:
# virt-resize --expand /dev/sda2 indisk outdisk
-(In this case, an extra partition is I<not> created at the end of the disk,
-because there will be no unused space).
+(In this case, an extra partition is I<not> created at the end of the disk, because there will be no unused space).
-L</--resize> is the other commonly used option. The following would
-increase the size of /dev/sda1 by 200M, and expand /dev/sda2 to fill the
-rest of the available space:
+L</--resize> is the other commonly used option. The following would increase the size of /dev/sda1 by 200M, and expand /dev/sda2 to fill the rest of the available space:
# virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
indisk outdisk
-If the expanded partition in the image contains a filesystem or LVM PV, then
-if virt-resize knows how, it will resize the contents, the equivalent of
-calling a command such as L<pvresize(8)>, L<resize2fs(8)>, L<ntfsresize(8)>,
-L<btrfs(8)>, L<xfs_growfs(8)>, or L<resize.f2fs(8)>. However virt-resize
-does not know how to resize some filesystems, so you would have to online
-resize them after booting the guest.
+If the expanded partition in the image contains a filesystem or LVM PV, then if virt-resize knows how, it will resize the contents, the equivalent of calling a command such as L<pvresize(8)>, L<resize2fs(8)>, L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)>, or L<resize.f2fs(8)>. However virt-resize does not know how to resize some filesystems, so you would have to online resize them after booting the guest.
# virt-resize --expand /dev/sda2 nbd://example.com outdisk
-The input disk can be a URI, in order to use a remote disk as the source.
-The URI format is compatible with guestfish. See L<guestfish(1)/ADDING
-REMOTE STORAGE>.
+The input disk can be a URI, in order to use a remote disk as the source. The URI format is compatible with guestfish. See L<guestfish(1)/ADDING REMOTE STORAGE>.
他のオプションは以下に記載しています。
# virsh edit guestname
-E<lt>source ...E<gt>
-を変更します、L<http://libvirt.org/formatdomain.html#elementsDisks> を参照してください。
+E<lt>source ...E<gt> を変更します、L<http://libvirt.org/formatdomain.html#elementsDisks> を参照してください。
Then start up the domain with the new, resized disk:
# virsh start guestname
-and check that it still works. See also the L</NOTES> section below for
-additional information.
+and check that it still works. See also the L</NOTES> section below for additional information.
=item 7. Resize LVs etc inside the guest
(This can also be done offline using L<guestfish(1)>)
-Once the guest has booted you should see the new space available, at least
-for filesystems that virt-resize knows how to resize, and for PVs. The user
-may need to resize LVs inside PVs, and also resize filesystem types that
-virt-resize does not know how to expand.
+Once the guest has booted you should see the new space available, at least for filesystems that virt-resize knows how to resize, and for PVs. The user may need to resize LVs inside PVs, and also resize filesystem types that virt-resize does not know how to expand.
=back
縮小は拡張よりもいくらか複雑です。ここでは概要のみを示します。
-Firstly virt-resize will not attempt to shrink any partition content (PVs,
-filesystems). The user has to shrink content before passing the disk image
-to virt-resize, and virt-resize will check that the content has been shrunk
-properly.
+Firstly virt-resize will not attempt to shrink any partition content (PVs, filesystems). The user has to shrink content before passing the disk image to virt-resize, and virt-resize will check that the content has been shrunk properly.
(Shrinking can also be done offline using L<guestfish(1)>)
-After shrinking PVs and filesystems, shut down the guest, and proceed with
-steps 3 and 4 above to allocate a new disk image.
+After shrinking PVs and filesystems, shut down the guest, and proceed with steps 3 and 4 above to allocate a new disk image.
Then run virt-resize with any of the I<--shrink> and/or I<--resize> options.
=head2 IGNORING OR DELETING PARTITIONS
-virt-resize also gives a convenient way to ignore or delete partitions when
-copying from the input disk to the output disk. Ignoring a partition speeds
-up the copy where you don't care about the existing contents of a
-partition. Deleting a partition removes it completely, but note that it
-also renumbers any partitions after the one which is deleted, which can
-leave some guests unbootable.
+virt-resize also gives a convenient way to ignore or delete partitions when copying from the input disk to the output disk. Ignoring a partition speeds up the copy where you don't care about the existing contents of a partition. Deleting a partition removes it completely, but note that it also renumbers any partitions after the one which is deleted, which can leave some guests unbootable.
=head2 QCOW2 AND NON-SPARSE RAW FORMATS
-If the input disk is in qcow2 format, then you may prefer that the output is
-in qcow2 format as well. Alternately, virt-resize can convert the format on
-the fly. The output format is simply determined by the format of the empty
-output container that you provide. Thus to create qcow2 output, use:
+If the input disk is in qcow2 format, then you may prefer that the output is in qcow2 format as well. Alternately, virt-resize can convert the format on the fly. The output format is simply determined by the format of the empty output container that you provide. Thus to create qcow2 output, use:
qemu-img create -f qcow2 -o preallocation=metadata outdisk [size]
fallocate -l size outdisk
-(on older systems that don’t have the L<fallocate(1)> command use C<dd
-if=/dev/zero of=outdisk bs=1M count=..>)
+(on older systems that don’t have the L<fallocate(1)> command use C<dd if=/dev/zero of=outdisk bs=1M count=..>)
=head2 論理パーティション
-Logical partitions (a.k.a. F</dev/sda5+> on disks using DOS partition
-tables) cannot be resized.
+Logical partitions (a.k.a. F</dev/sda5+> on disks using DOS partition tables) cannot be resized.
-To understand what is going on, firstly one of the four partitions
-F</dev/sda1-4> will have MBR partition type C<05> or C<0f>. This is called
-the B<extended partition>. Use L<virt-filesystems(1)> to see the MBR
-partition type.
+To understand what is going on, firstly one of the four partitions F</dev/sda1-4> will have MBR partition type C<05> or C<0f>. This is called the B<extended partition>. Use L<virt-filesystems(1)> to see the MBR partition type.
Logical partitions live inside the extended partition.
-The extended partition can be expanded, but not shrunk (unless you force it,
-which is not advisable). When the extended partition is copied across, all
-the logical partitions contained inside are copied over implicitly.
-Virt-resize does not look inside the extended partition, so it copies the
-logical partitions blindly.
+The extended partition can be expanded, but not shrunk (unless you force it, which is not advisable). When the extended partition is copied across, all the logical partitions contained inside are copied over implicitly. Virt-resize does not look inside the extended partition, so it copies the logical partitions blindly.
-You cannot specify a logical partition (F</dev/sda5+>) at all on the command
-line. Doing so will give an error.
+You cannot specify a logical partition (F</dev/sda5+>) at all on the command line. Doing so will give an error.
=head1 オプション
=item B<--align-first> B<always>
-Align the first partition for improved performance (see also the
-I<--alignment> option).
+Align the first partition for improved performance (see also the I<--alignment> option).
-The default is I<--align-first auto> which only aligns the first partition
-if it is safe to do so. That is, only when we know how to fix the
-bootloader automatically, and at the moment that can only be done for
-Windows guests.
+The default is I<--align-first auto> which only aligns the first partition if it is safe to do so. That is, only when we know how to fix the bootloader automatically, and at the moment that can only be done for Windows guests.
-I<--align-first never> means we never move the first partition. This is the
-safest option. Try this if the guest does not boot after resizing.
+I<--align-first never> means we never move the first partition. This is the safest option. Try this if the guest does not boot after resizing.
-I<--align-first always> means we always align the first partition (if it
-needs to be aligned). For some guests this will break the bootloader,
-making the guest unbootable.
+I<--align-first always> means we always align the first partition (if it needs to be aligned). For some guests this will break the bootloader, making the guest unbootable.
=item B<--alignment> N
-Set the alignment of partitions to C<N> sectors. The default in virt-resize
-E<lt> 1.13.19 was 64 sectors, and after that is 128 sectors.
+Set the alignment of partitions to C<N> sectors. The default in virt-resize E<lt> 1.13.19 was 64 sectors, and after that is 128 sectors.
-Assuming 512 byte sector size inside the guest, here are some suitable
-values for this:
+Assuming 512 byte sector size inside the guest, here are some suitable values for this:
=over 4
=item I<--alignment 1> (512 バイト)
-The partitions would be packed together as closely as possible, but would be
-completely unaligned. In some cases this can cause very poor performance.
-See L<virt-alignment-scan(1)> for further details.
+The partitions would be packed together as closely as possible, but would be completely unaligned. In some cases this can cause very poor performance. See L<virt-alignment-scan(1)> for further details.
=item I<--alignment 8> (4K)
-This would be the minimum acceptable alignment for reasonable performance on
-modern hosts.
+This would be the minimum acceptable alignment for reasonable performance on modern hosts.
=item I<--alignment 128> (64K)
-This alignment provides good performance when the host is using high end
-network storage.
+This alignment provides good performance when the host is using high end network storage.
=item I<--alignment 2048> (1M)
-This is the standard alignment used by all newly installed guests since
-around 2008.
+This is the standard alignment used by all newly installed guests since around 2008.
=back
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<-d>
=item B<--delete> PART
-Delete the named partition. It would be more accurate to describe this as
-"don't copy it over", since virt-resize doesn't do in-place changes and the
-original disk image is left intact.
+Delete the named partition. It would be more accurate to describe this as "don't copy it over", since virt-resize doesn't do in-place changes and the original disk image is left intact.
-Note that when you delete a partition, then anything contained in the
-partition is also deleted. Furthermore, this causes any partitions that
-come after to be I<renumbered>, which can easily make your guest unbootable.
+Note that when you delete a partition, then anything contained in the partition is also deleted. Furthermore, this causes any partitions that come after to be I<renumbered>, which can easily make your guest unbootable.
このオプションは複数回指定できます。
=item B<--expand> PART
-Expand the named partition so it uses up all extra space (space left over
-after any other resize changes that you request have been done).
+Expand the named partition so it uses up all extra space (space left over after any other resize changes that you request have been done).
-If virt-resize knows how, it will expand the direct content of the
-partition. For example, if the partition is an LVM PV, it will expand the
-PV to fit (like calling L<pvresize(8)>). Virt-resize leaves any other
-content it doesn't know about alone.
+If virt-resize knows how, it will expand the direct content of the partition. For example, if the partition is an LVM PV, it will expand the PV to fit (like calling L<pvresize(8)>). Virt-resize leaves any other content it doesn't know about alone.
Currently virt-resize can resize:
NTFS filesystems, if libguestfs was compiled with support for NTFS.
-The filesystem must have been shut down consistently last time it was used.
-Additionally, L<ntfsresize(8)> marks the resized filesystem as requiring a
-consistency check, so at the first boot after resizing Windows will check
-the disk.
+The filesystem must have been shut down consistently last time it was used. Additionally, L<ntfsresize(8)> marks the resized filesystem as requiring a consistency check, so at the first boot after resizing Windows will check the disk.
=item *
-LVM PVs (physical volumes). virt-resize does not usually resize anything
-inside the PV, but see the I<--LV-expand> option. The user could also
-resize LVs as desired after boot.
+LVM PVs (physical volumes). virt-resize does not usually resize anything inside the PV, but see the I<--LV-expand> option. The user could also resize LVs as desired after boot.
=item *
Linux swap partitions.
-Please note that libguestfs I<destroys> the existing swap content by
-recreating it with C<mkswap>, so this should not be used when the guest is
-suspended.
+Please note that libguestfs I<destroys> the existing swap content by recreating it with C<mkswap>, so this should not be used when the guest is suspended.
=item *
=item B<--format> B<raw>
-Specify the format of the input disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the input disk image. If this flag is not given then it is auto-detected from the image itself.
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
-Note that this option I<does not> affect the output format. See L</QCOW2
-AND NON-SPARSE RAW FORMATS>.
+Note that this option I<does not> affect the output format. See L</QCOW2 AND NON-SPARSE RAW FORMATS>.
=item B<--ignore> PART
-Ignore the named partition. Effectively this means the partition is
-allocated on the destination disk, but the content is not copied across from
-the source disk. The content of the partition will be blank (all zero
-bytes).
+Ignore the named partition. Effectively this means the partition is allocated on the destination disk, but the content is not copied across from the source disk. The content of the partition will be blank (all zero bytes).
このオプションは複数回指定できます。
=item B<--LV-expand> LOGVOL
-This takes the logical volume and, as a final step, expands it to fill all
-the space available in its volume group. A typical usage, assuming a Linux
-guest with a single PV F</dev/sda2> and a root device called
-F</dev/vg_guest/lv_root> would be:
+This takes the logical volume and, as a final step, expands it to fill all the space available in its volume group. A typical usage, assuming a Linux guest with a single PV F</dev/sda2> and a root device called F</dev/vg_guest/lv_root> would be:
virt-resize indisk outdisk \
--expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root
-This would first expand the partition (and PV), and then expand the root
-device to fill the extra space in the PV.
+This would first expand the partition (and PV), and then expand the root device to fill the extra space in the PV.
-The contents of the LV are also resized if virt-resize knows how to do
-that. You can stop virt-resize from trying to expand the content by using
-the option I<--no-expand-content>.
+The contents of the LV are also resized if virt-resize knows how to do that. You can stop virt-resize from trying to expand the content by using the option I<--no-expand-content>.
仮想マシンにあるファイルシステムを一覧表示するには L<virt-filesystems(1)> を使用します。
-You can give this option multiple times, I<but> it doesn't make sense to do
-this unless the logical volumes you specify are all in different volume
-groups.
+You can give this option multiple times, I<but> it doesn't make sense to do this unless the logical volumes you specify are all in different volume groups.
=item B<--machine-readable>
=item B<--no-copy-boot-loader>
-By default, virt-resize copies over some sectors at the start of the disk
-(up to the beginning of the first partition). Commonly these sectors
-contain the Master Boot Record (MBR) and the boot loader, and are required
-in order for the guest to boot correctly.
+By default, virt-resize copies over some sectors at the start of the disk (up to the beginning of the first partition). Commonly these sectors contain the Master Boot Record (MBR) and the boot loader, and are required in order for the guest to boot correctly.
-If you specify this flag, then this initial copy is not done. You may need
-to reinstall the boot loader in this case.
+If you specify this flag, then this initial copy is not done. You may need to reinstall the boot loader in this case.
=item B<--no-extra-partition>
-By default, virt-resize creates an extra partition if there is any extra,
-unused space after all resizing has happened. Use this option to prevent
-the extra partition from being created. If you do this then the extra space
-will be inaccessible until you run fdisk, parted, or some other partitioning
-tool in the guest.
+By default, virt-resize creates an extra partition if there is any extra, unused space after all resizing has happened. Use this option to prevent the extra partition from being created. If you do this then the extra space will be inaccessible until you run fdisk, parted, or some other partitioning tool in the guest.
-Note that if the surplus space is smaller than 10 MB, no extra partition
-will be created.
+Note that if the surplus space is smaller than 10 MB, no extra partition will be created.
=item B<--no-expand-content>
-By default, virt-resize will try to expand the direct contents of
-partitions, if it knows how (see I<--expand> option above).
+By default, virt-resize will try to expand the direct contents of partitions, if it knows how (see I<--expand> option above).
I<--no-expand-content> オプションを指定すると、virt-resize はこれを試行しません。
=item B<--ntfsresize-force>
-L<ntfsresize(8)> に I<--force> オプションを渡します。これにより、NTFS
-ディスクが整合性の確認が必要であるという印をつけたときでも、容量の変更を許可します。Windows
-仮想マシンを各容量において起動することなく、何回も容量変更したいならば、このオプションを使用する必要があります。
+L<ntfsresize(8)> に I<--force> オプションを渡します。これにより、NTFS ディスクが整合性の確認が必要であるという印をつけたときでも、容量の変更を許可します。Windows 仮想マシンを各容量において起動することなく、何回も容量変更したいならば、このオプションを使用する必要があります。
=item B<--output-format> B<raw>
-Specify the format of the output disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the output disk image. If this flag is not given then it is auto-detected from the image itself.
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
-Note that this option I<does not create> the output format. This option
-just tells libguestfs what it is so it doesn't try to guess it. You still
-need to create the output disk with the right format. See L</QCOW2 AND
-NON-SPARSE RAW FORMATS>.
+Note that this option I<does not create> the output format. This option just tells libguestfs what it is so it doesn't try to guess it. You still need to create the output disk with the right format. See L</QCOW2 AND NON-SPARSE RAW FORMATS>.
=item B<-q>
=item B<--resize> PART=SIZE
-Resize the named partition (expanding or shrinking it) so that it has the
-given size.
+Resize the named partition (expanding or shrinking it) so that it has the given size.
-C<SIZE> can be expressed as an absolute number followed by b/K/M/G to mean
-bytes, Kilobytes, Megabytes, or Gigabytes; or as a percentage of the current
-size; or as a relative number or percentage. For example:
+C<SIZE> can be expressed as an absolute number followed by b/K/M/G to mean bytes, Kilobytes, Megabytes, or Gigabytes; or as a percentage of the current size; or as a relative number or percentage. For example:
--resize /dev/sda2=10G
--resize /dev/sda1=-10%
-You can increase the size of any partition. Virt-resize will expand the
-direct content of the partition if it knows how (see I<--expand> above).
+You can increase the size of any partition. Virt-resize will expand the direct content of the partition if it knows how (see I<--expand> above).
-You can only I<decrease> the size of partitions that contain filesystems or
-PVs which have already been shrunk. Virt-resize will check this has been
-done before proceeding, or else will print an error (see also
-I<--resize-force>).
+You can only I<decrease> the size of partitions that contain filesystems or PVs which have already been shrunk. Virt-resize will check this has been done before proceeding, or else will print an error (see also I<--resize-force>).
このオプションは複数回指定できます。
=item B<--resize-force> PART=SIZE
-This is the same as I<--resize> except that it will let you decrease the
-size of any partition. Generally this means you will lose any data which
-was at the end of the partition you shrink, but you may not care about that
-(eg. if shrinking an unused partition, or if you can easily recreate it such
-as a swap partition).
+This is the same as I<--resize> except that it will let you decrease the size of any partition. Generally this means you will lose any data which was at the end of the partition you shrink, but you may not care about that (eg. if shrinking an unused partition, or if you can easily recreate it such as a swap partition).
I<--ignore> オプション参照。
=item B<--shrink> PART
-Shrink the named partition until the overall disk image fits in the
-destination. The named partition B<must> contain a filesystem or PV which
-has already been shrunk using another tool (eg. L<guestfish(1)> or other
-online tools). Virt-resize will check this and give an error if it has not
-been done.
+Shrink the named partition until the overall disk image fits in the destination. The named partition B<must> contain a filesystem or PV which has already been shrunk using another tool (eg. L<guestfish(1)> or other online tools). Virt-resize will check this and give an error if it has not been done.
-The amount by which the overall disk must be shrunk (after carrying out all
-other operations requested by the user) is called the "deficit". For
-example, a straight copy (assume no other operations) from a 5GB disk image
-to a 4GB disk image results in a 1GB deficit. In this case, virt-resize
-would give an error unless the user specified a partition to shrink and that
-partition had more than a gigabyte of free space.
+The amount by which the overall disk must be shrunk (after carrying out all other operations requested by the user) is called the "deficit". For example, a straight copy (assume no other operations) from a 5GB disk image to a 4GB disk image results in a 1GB deficit. In this case, virt-resize would give an error unless the user specified a partition to shrink and that partition had more than a gigabyte of free space.
Note that you cannot use I<--expand> and I<--shrink> together.
=item B<--unknown-filesystems> B<error>
-Configure the behaviour of virt-resize when asking to expand a filesystem,
-and neither libguestfs has the support it, nor virt-resize knows how to
-expand the content of the filesystem.
+Configure the behaviour of virt-resize when asking to expand a filesystem, and neither libguestfs has the support it, nor virt-resize knows how to expand the content of the filesystem.
-I<--unknown-filesystems ignore> will cause virt-resize to silently ignore
-such filesystems, and nothing is printed about them.
+I<--unknown-filesystems ignore> will cause virt-resize to silently ignore such filesystems, and nothing is printed about them.
-I<--unknown-filesystems warn> (the default behaviour) will cause virt-resize
-to warn for each of the filesystem that cannot be expanded, but still
-continuing to resize the disk.
+I<--unknown-filesystems warn> (the default behaviour) will cause virt-resize to warn for each of the filesystem that cannot be expanded, but still continuing to resize the disk.
-I<--unknown-filesystems error> will cause virt-resize to error out at the
-first filesystem that cannot be expanded.
+I<--unknown-filesystems error> will cause virt-resize to error out at the first filesystem that cannot be expanded.
-See also L</"unknown/unavailable method for expanding the TYPE filesystem on
-DEVICE/LV">.
+See also L</"unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV">.
=item B<-v>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 マシン可読な出力
-I<--machine-readable> オプションはよりマシンに易しい出力を作成するために使用できます。これは他のプログラムや GUI などから
-virt-resize を呼び出すときに有用です。
+I<--machine-readable> オプションはよりマシンに易しい出力を作成するために使用できます。これは他のプログラムや GUI などから virt-resize を呼び出すときに有用です。
このオプションを使用するには 2 通りの方法があります。
-Firstly use the option on its own to query the capabilities of the
-virt-resize binary. Typical output looks like this:
+Firstly use the option on its own to query the capabilities of the virt-resize binary. Typical output looks like this:
$ virt-resize --machine-readable
virt-resize
ntfs
btrfs
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-Secondly use the option in conjunction with other options to make the
-regular program output more machine friendly.
+Secondly use the option in conjunction with other options to make the regular program output more machine friendly.
At the moment this means:
=item 1.
-Progress bar messages can be parsed from stdout by looking for this regular
-expression:
+Progress bar messages can be parsed from stdout by looking for this regular expression:
^[0-9]+/[0-9]+$
=item 2.
-The calling program should treat messages sent to stdout (except for
-progress bar messages) as status messages. They can be logged and/or
-displayed to the user.
+The calling program should treat messages sent to stdout (except for progress bar messages) as status messages. They can be logged and/or displayed to the user.
=item 3.
-The calling program should treat messages sent to stderr as error messages.
-In addition, virt-resize exits with a non-zero status code if there was a
-fatal error.
+The calling program should treat messages sent to stderr as error messages. In addition, virt-resize exits with a non-zero status code if there was a fatal error.
=back
-Versions of the program prior to 1.13.9 did not support the
-I<--machine-readable> option and will return an error.
+Versions of the program prior to 1.13.9 did not support the I<--machine-readable> option and will return an error.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 注記
=head2 "Partition 1 does not end on cylinder boundary."
-Virt-resize aligns partitions to multiples of 128 sectors (see the
-I<--alignment> parameter). Usually this means the partitions will not be
-aligned to the ancient CHS geometry. However CHS geometry is meaningless
-for disks manufactured since the early 1990s, and doubly so for virtual hard
-drives. Alignment of partitions to cylinders is not required by any modern
-operating system.
+Virt-resize aligns partitions to multiples of 128 sectors (see the I<--alignment> parameter). Usually this means the partitions will not be aligned to the ancient CHS geometry. However CHS geometry is meaningless for disks manufactured since the early 1990s, and doubly so for virtual hard drives. Alignment of partitions to cylinders is not required by any modern operating system.
=head2 GUEST BOOT STUCK AT "GRUB"
-If a Linux guest does not boot after resizing, and the boot is stuck after
-printing C<GRUB> on the console, try reinstalling grub.
+If a Linux guest does not boot after resizing, and the boot is stuck after printing C<GRUB> on the console, try reinstalling grub.
guestfish -i -a newdisk
><fs> cat /boot/grub/device.map
><fs> grub-install / /dev/vda
><fs> exit
-For more flexible guest reconfiguration, including if you need to specify
-other parameters to grub-install, use L<virt-rescue(1)>.
+For more flexible guest reconfiguration, including if you need to specify other parameters to grub-install, use L<virt-rescue(1)>.
=head2 RESIZING WINDOWS BOOT PARTITIONS
-In Windows Vista and later versions, Microsoft switched to using a separate
-boot partition. In these VMs, typically F</dev/sda1> is the boot partition
-and F</dev/sda2> is the main (C:) drive. Resizing the first (boot)
-partition causes the bootloader to fail with C<0xC0000225> error. Resizing
-the second partition (ie. C: drive) should work.
+In Windows Vista and later versions, Microsoft switched to using a separate boot partition. In these VMs, typically F</dev/sda1> is the boot partition and F</dev/sda2> is the main (C:) drive. Resizing the first (boot) partition causes the bootloader to fail with C<0xC0000225> error. Resizing the second partition (ie. C: drive) should work.
=head2 WINDOWS CHKDSK
-Windows disks which use NTFS must be consistent before virt-resize can be
-used. If the ntfsresize operation fails, try booting the original VM and
-running C<chkdsk /f> on all NTFS partitions, then shut down the VM cleanly.
-For further information see:
-L<https://bugzilla.redhat.com/show_bug.cgi?id=975753>
+Windows disks which use NTFS must be consistent before virt-resize can be used. If the ntfsresize operation fails, try booting the original VM and running C<chkdsk /f> on all NTFS partitions, then shut down the VM cleanly. For further information see: L<https://bugzilla.redhat.com/show_bug.cgi?id=975753>
-I<After resize> Windows may initiate a lengthy "chkdsk" on first boot if
-NTFS partitions have been expanded. This is just a safety check and (unless
-it find errors) is nothing to worry about.
+I<After resize> Windows may initiate a lengthy "chkdsk" on first boot if NTFS partitions have been expanded. This is just a safety check and (unless it find errors) is nothing to worry about.
=head2 Windows UNMOUNTABLE_BOOT_VOLUME BSOD
-Windows 仮想マシンを sysprep して、virt-resize を用いて容量を変更した後、仮想マシンが
-C<UNMOUNTABLE_BOOT_VOLUME> BSOD で起動に失敗するかもしれません。このエラーは sysprep.inf ファイルに
-C<ExtendOemPartition=1> があることにより引き起こされます。sysprep
-する前にこの行を削除することにより、この問題を解決できます。
+Windows 仮想マシンを sysprep して、virt-resize を用いて容量を変更した後、仮想マシンが C<UNMOUNTABLE_BOOT_VOLUME> BSOD で起動に失敗するかもしれません。このエラーは sysprep.inf ファイルに C<ExtendOemPartition=1> があることにより引き起こされます。sysprep する前にこの行を削除することにより、この問題を解決できます。
=head2 WINDOWS 8
-Windows 8 "fast startup" can prevent virt-resize from resizing NTFS
-partitions. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST
-STARTUP>.
+Windows 8 "fast startup" can prevent virt-resize from resizing NTFS partitions. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
=head2 SPARSE COPYING
You should create a fresh, zeroed target disk image for virt-resize to use.
-Virt-resize by default performs sparse copying. This means that it does not
-copy blocks from the source disk which are all zeroes. This improves speed
-and efficiency, but will produce incorrect results if the target disk image
-contains unzeroed data.
+Virt-resize by default performs sparse copying. This means that it does not copy blocks from the source disk which are all zeroes. This improves speed and efficiency, but will produce incorrect results if the target disk image contains unzeroed data.
-The main time this can be a problem is if the target is a host partition
-(eg. S<C<virt-resize source.img /dev/sda4>>) because the usual partitioning
-tools tend to leave whatever data happened to be on the disk before.
+The main time this can be a problem is if the target is a host partition (eg. S<C<virt-resize source.img /dev/sda4>>) because the usual partitioning tools tend to leave whatever data happened to be on the disk before.
-If you have to reuse a target which contains data already, you should use
-the I<--no-sparse> option. Note this can be much slower.
+If you have to reuse a target which contains data already, you should use the I<--no-sparse> option. Note this can be much slower.
=head2 "unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV"
-Virt-resize was asked to expand a partition or a logical volume containing a
-filesystem with the type C<TYPE>, but there is no available nor known
-expanding method for that filesystem.
+Virt-resize was asked to expand a partition or a logical volume containing a filesystem with the type C<TYPE>, but there is no available nor known expanding method for that filesystem.
This may be due to either of the following:
=item 1.
-There corresponding filesystem is not available in libguestfs, because there
-is no proper package in the host with utilities for it. This is usually the
-case for C<btrfs>, C<ntfs>, C<xfs>, and C<f2fs> filesystems.
+There corresponding filesystem is not available in libguestfs, because there is no proper package in the host with utilities for it. This is usually the case for C<btrfs>, C<ntfs>, C<xfs>, and C<f2fs> filesystems.
Check the results of:
guestfish -a /dev/null run : available
guestfish -a /dev/null run : filesystem_available TYPE
-In this case, it is enough to install the proper packages adding support for
-them. For example, C<libguestfs-xfs> on Red Hat Enterprise Linux, CentOS,
-Debian, Ubuntu, and distributions derived from them, for supporting the
-C<xfs> filesystem.
+In this case, it is enough to install the proper packages adding support for them. For example, C<libguestfs-xfs> on Red Hat Enterprise Linux, CentOS, Debian, Ubuntu, and distributions derived from them, for supporting the C<xfs> filesystem.
=item 2.
Virt-resize has no support for expanding that type of filesystem.
-In this case, there’s nothing that can be done to let virt-resize expand
-that type of filesystem.
+In this case, there’s nothing that can be done to let virt-resize expand that type of filesystem.
=back
-In both cases, virt-resize will not expand the mentioned filesystem; the
-result (unless I<--unknown-filesystems error> is specified) is that the
-partitions containing such filesystems will be actually bigger as requested,
-but the filesystems will still be usable at their older sizes.
+In both cases, virt-resize will not expand the mentioned filesystem; the result (unless I<--unknown-filesystems error> is specified) is that the partitions containing such filesystems will be actually bigger as requested, but the filesystems will still be usable at their older sizes.
=head1 代替ツール
-There are several proprietary tools for resizing partitions. We won't
-mention any here.
+There are several proprietary tools for resizing partitions. We won't mention any here.
-L<parted(8)> and its graphical shell gparted can do some types of resizing
-operations on disk images. They can resize and move partitions, but I don't
-think they can do anything with the contents, and they certainly don't
-understand LVM.
+L<parted(8)> and its graphical shell gparted can do some types of resizing operations on disk images. They can resize and move partitions, but I don't think they can do anything with the contents, and they certainly don't understand LVM.
-L<guestfish(1)> can do everything that virt-resize can do and a lot more,
-but at a much lower level. You will probably end up hand-calculating sector
-offsets, which is something that virt-resize was designed to avoid. If you
-want to see the guestfish-equivalent commands that virt-resize runs, use the
-I<--debug> flag.
+L<guestfish(1)> can do everything that virt-resize can do and a lot more, but at a much lower level. You will probably end up hand-calculating sector offsets, which is something that virt-resize was designed to avoid. If you want to see the guestfish-equivalent commands that virt-resize runs, use the I<--debug> flag.
-L<dracut(8)> includes a module called C<dracut-modules-growroot> which can
-be used to grow the root partition when the guest first boots up. There is
-documentation for this module in an associated README file.
+L<dracut(8)> includes a module called C<dracut-modules-growroot> which can be used to grow the root partition when the guest first boots up. There is documentation for this module in an associated README file.
=head1 終了ステータス
=head1 関連項目
-L<virt-filesystems(1)>, L<virt-df(1)>, L<guestfs(3)>, L<guestfish(1)>,
-L<lvm(8)>, L<pvresize(8)>, L<lvresize(8)>, L<resize2fs(8)>,
-L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)>, L<resize.f2fs(8)>,
-L<virsh(1)>, L<parted(8)>, L<truncate(1)>, L<fallocate(1)>, L<grub(8)>,
-L<grub-install(8)>, L<virt-rescue(1)>, L<virt-sparsify(1)>,
-L<virt-alignment-scan(1)>, L<http://libguestfs.org/>.
+L<virt-filesystems(1)>, L<virt-df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<lvm(8)>, L<pvresize(8)>, L<lvresize(8)>, L<resize2fs(8)>, L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)>, L<resize.f2fs(8)>, L<virsh(1)>, L<parted(8)>, L<truncate(1)>, L<fallocate(1)>, L<grub(8)>, L<grub-install(8)>, L<virt-rescue(1)>, L<virt-sparsify(1)>, L<virt-alignment-scan(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-sparsify 1"
-.TH virt-sparsify 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-sparsify 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-sparsify is a tool which can make a virtual machine disk (or any disk
-image) sparse a.k.a. thin-provisioned. This means that free space within
-the disk image can be converted back to free space on the host.
+Virt-sparsify is a tool which can make a virtual machine disk (or any disk image) sparse a.k.a. thin-provisioned. This means that free space within the disk image can be converted back to free space on the host.
.PP
-Virt-sparsify can locate and sparsify free space in most filesystems
-(eg. ext2/3/4, btrfs, \s-1NTFS,\s0 etc.), and also in \s-1LVM\s0 physical volumes.
+Virt-sparsify can locate and sparsify free space in most filesystems (eg. ext2/3/4, btrfs, \s-1NTFS,\s0 etc.), and also in \s-1LVM\s0 physical volumes.
.PP
-Virt-sparsify はさまざまなディスクフォーマットを変換することができます。例えば、raw ディスクイメージをシンプロビジョニングされた
-qcow2 イメージに変換することができます。
+Virt-sparsify はさまざまなディスクフォーマットを変換することができます。例えば、raw ディスクイメージをシンプロビジョニングされた qcow2 イメージに変換することができます。
.PP
-Virt-sparsify can operate on any disk image, not just ones from virtual
-machines. However if a virtual machine has multiple disks and uses volume
-management, then virt-sparsify will work but not be very effective
-(http://bugzilla.redhat.com/887826).
+Virt-sparsify can operate on any disk image, not just ones from virtual machines. However if a virtual machine has multiple disks and uses volume management, then virt-sparsify will work but not be very effective (http://bugzilla.redhat.com/887826).
.SS "\s-1IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES\s0"
.IX Subsection "IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES"
-If the input is raw, then the default output is raw sparse. \fBYou must
-check the output size using a tool that understands sparseness\fR such as \f(CW\*(C`du
-\&\-sh\*(C'\fR. It can make a huge difference:
+If the input is raw, then the default output is raw sparse. \fBYou must check the output size using a tool that understands sparseness\fR such as \f(CW\*(C`du \-sh\*(C'\fR. It can make a huge difference:
.PP
.Vb 4
\& $ ls \-lh test1.img
.IP "\(bu" 4
The virtual machine \fImust be shut down\fR before using this tool.
.IP "\(bu" 4
-Virt-sparsify may require up to 2x the virtual size of the source disk image
-(1 temporary copy + 1 destination image). This is in the worst case and
-usually much less space is required.
+Virt-sparsify may require up to 2x the virtual size of the source disk image (1 temporary copy + 1 destination image). This is in the worst case and usually much less space is required.
.Sp
-If you are using the \fI\-\-in\-place\fR option, then large amounts of temporary
-space are \fBnot\fR required.
+If you are using the \fI\-\-in\-place\fR option, then large amounts of temporary space are \fBnot\fR required.
.IP "\(bu" 4
Virt-sparsify cannot resize disk images. To do that, use \fBvirt\-resize\fR\|(1).
.IP "\(bu" 4
-virt-sparsify は暗号化されたディスクを処理できません。 libguestfs
-は暗号化されたディスクをサポートしますが、暗号化されたディスク自体はスパース化できません。
+virt-sparsify は暗号化されたディスクを処理できません。 libguestfs は暗号化されたディスクをサポートしますが、暗号化されたディスク自体はスパース化できません。
.IP "\(bu" 4
-Virt-sparsify cannot yet sparsify the space between partitions. Note that
-this space is often used for critical items like bootloaders so it's not
-really unused.
+Virt-sparsify cannot yet sparsify the space between partitions. Note that this space is often used for critical items like bootloaders so it's not really unused.
.IP "\(bu" 4
-In copy mode, qcow2 internal snapshots are not copied over to the
-destination image.
+In copy mode, qcow2 internal snapshots are not copied over to the destination image.
.PP
-You may also want to read the manual pages for the associated tools
-\&\fBvirt\-filesystems\fR\|(1) and \fBvirt\-df\fR\|(1) before starting.
+You may also want to read the manual pages for the associated tools \fBvirt\-filesystems\fR\|(1) and \fBvirt\-df\fR\|(1) before starting.
.SH "例"
.IX Header "例"
一般的な使用法は次のとおりです:
\& virt\-sparsify indisk outdisk
.Ve
.PP
-which copies \f(CW\*(C`indisk\*(C'\fR to \f(CW\*(C`outdisk\*(C'\fR, making the output sparse. \f(CW\*(C`outdisk\*(C'\fR
-is created, or overwritten if it already exists. The format of the input
-disk is detected (eg. qcow2) and the same format is used for the output
-disk.
+which copies \f(CW\*(C`indisk\*(C'\fR to \f(CW\*(C`outdisk\*(C'\fR, making the output sparse. \f(CW\*(C`outdisk\*(C'\fR is created, or overwritten if it already exists. The format of the input disk is detected (eg. qcow2) and the same format is used for the output disk.
.PP
形式を変換するには \fI\-\-convert\fR オプションを使用します:
.PP
\& virt\-sparsify disk.raw \-\-convert qcow2 disk.qcow2
.Ve
.PP
-Virt-sparsify tries to zero and sparsify free space on every filesystem it
-can find within the source disk image. You can get it to ignore (don't zero
-free space on) certain filesystems by doing:
+Virt-sparsify tries to zero and sparsify free space on every filesystem it can find within the source disk image. You can get it to ignore (don't zero free space on) certain filesystems by doing:
.PP
.Vb 1
\& virt\-sparsify \-\-ignore /dev/sda1 indisk outdisk
.PP
ディスクイメージにあるファイルシステムの一覧を取得するには \fBvirt\-filesystems\fR\|(1) を参照してください。
.PP
-Since virt-sparsify ≥ 1.26, you can now sparsify a disk image in place
-by doing:
+Since virt-sparsify ≥ 1.26, you can now sparsify a disk image in place by doing:
.PP
.Vb 1
\& virt\-sparsify \-\-in\-place disk.img
.IP "\fB\-\-check\-tmpdir\fR \fBfail\fR" 4
.IX Item "--check-tmpdir fail"
.PD
-Check if \*(L"\s-1TMPDIR\*(R"\s0 or \fI\-\-tmp\fR directory has enough space to complete the
-operation. This is just an estimate.
+Check if \*(L"\s-1TMPDIR\*(R"\s0 or \fI\-\-tmp\fR directory has enough space to complete the operation. This is just an estimate.
.Sp
If the check indicates a problem, then you can either:
.RS 4
.IP "\(bu" 4
print a warning and \fBcontinue\fR,
.IP "\(bu" 4
-\&\fBwarn\fR and wait for the user to press the Return key (this is the default),
-or:
+\&\fBwarn\fR and wait for the user to press the Return key (this is the default), or:
.IP "\(bu" 4
\&\fBfail\fR and exit.
.RE
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-\-compress\fR" 4
.IX Item "--compress"
出力ファイルを圧縮します。これは 出力形式が \f(CW\*(C`qcow2\*(C'\fR の場合 \fIのみ\fR 機能します。
.IP "\fB\-\-convert\fR [other formats]" 4
.IX Item "--convert [other formats]"
.PD
-Use \f(CW\*(C`output\-format\*(C'\fR as the format for the destination image. If this is
-not specified, then the input format is used.
+Use \f(CW\*(C`output\-format\*(C'\fR as the format for the destination image. If this is not specified, then the input format is used.
.Sp
サポートされる既知の動作済み出力形式は次のとおりです: \f(CW\*(C`raw\*(C'\fR, \f(CW\*(C`qcow2\*(C'\fR, \f(CW\*(C`vdi\*(C'\fR。
.Sp
-\&\fBqemu\-img\fR\|(1) プログラムによりサポートされるすべての形式を使用できます。たとえば、\f(CW\*(C`vmdk\*(C'\fR ですが、他の形式のサポートは \s-1QEMU\s0
-に依存します。
+\&\fBqemu\-img\fR\|(1) プログラムによりサポートされるすべての形式を使用できます。たとえば、\f(CW\*(C`vmdk\*(C'\fR ですが、他の形式のサポートは \s-1QEMU\s0 に依存します。
.Sp
-Specifying the \fI\-\-convert\fR option is usually a good idea, because then
-virt-sparsify doesn't need to try to guess the input format.
+Specifying the \fI\-\-convert\fR option is usually a good idea, because then virt-sparsify doesn't need to try to guess the input format.
.Sp
出力形式を詳細に調整します。関連項目: \fI\-\-compress\fR, \fI\-o\fR.
.Sp
You cannot use this option and \fI\-\-in\-place\fR together.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-sparsify normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-sparsify normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-format\fR raw" 4
.IX Item "--format raw"
.PD 0
.IP "\fB\-\-format\fR qcow2" 4
.IX Item "--format qcow2"
.PD
-Specify the format of the input disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the input disk image. If this flag is not given then it is auto-detected from the image itself.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.IP "\fB\-\-ignore\fR filesystem" 4
.IX Item "--ignore filesystem"
.PD 0
.PD
Ignore the named filesystem.
.Sp
-When not using \fI\-\-in\-place\fR: Free space on the filesystem will not be
-zeroed, but existing blocks of zeroes will still be sparsified.
+When not using \fI\-\-in\-place\fR: Free space on the filesystem will not be zeroed, but existing blocks of zeroes will still be sparsified.
.Sp
When using \fI\-\-in\-place\fR, the filesystem is ignored completely.
.Sp
-In the second form, this ignores the named volume group. Use the volume
-group name without the \fI/dev/\fR prefix, eg. \fI\-\-ignore vg_foo\fR
+In the second form, this ignores the named volume group. Use the volume group name without the \fI/dev/\fR prefix, eg. \fI\-\-ignore vg_foo\fR
.Sp
このオプションは複数回指定できます。
.IP "\fB\-\-in\-place\fR" 4
.IX Item "--in-place"
-Do in-place sparsification instead of copying sparsification. See
-\&\*(L"IN-PLACE \s-1SPARSIFICATION\*(R"\s0 below.
+Do in-place sparsification instead of copying sparsification. See \*(L"IN-PLACE \s-1SPARSIFICATION\*(R"\s0 below.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
このオプションは、他のプログラムにより解析されるときに、よりマシンに易しい出力を作成するために使用されます。以下の \*(L"マシン可読な出力\*(R" 参照。
.IP "\fB\-o\fR option[,option,...]" 4
.IX Item "-o option[,option,...]"
-Pass \fI\-o\fR option(s) to the \fBqemu\-img\fR\|(1) command to fine-tune the output
-format. Options available depend on the output format (see \fI\-\-convert\fR)
-and the installed version of the qemu-img program.
+Pass \fI\-o\fR option(s) to the \fBqemu\-img\fR\|(1) command to fine-tune the output format. Options available depend on the output format (see \fI\-\-convert\fR) and the installed version of the qemu-img program.
.Sp
-You should use \fI\-o\fR at most once. To pass multiple options, separate them
-with commas, eg:
+You should use \fI\-o\fR at most once. To pass multiple options, separate them with commas, eg:
.Sp
.Vb 2
\& virt\-sparsify \-\-convert qcow2 \e
.IP "\fB\-\-tmp\fR dir" 4
.IX Item "--tmp dir"
.PD
-In copying mode only, use the named device or directory as the location of
-the temporary overlay (see also \*(L"\s-1TMPDIR\*(R"\s0 below).
+In copying mode only, use the named device or directory as the location of the temporary overlay (see also \*(L"\s-1TMPDIR\*(R"\s0 below).
.Sp
-If the parameter given is a block device, then the block device is written
-to directly. \fBNote this erases the existing contents of the block device\fR.
+If the parameter given is a block device, then the block device is written to directly. \fBNote this erases the existing contents of the block device\fR.
.Sp
-If the parameter is a directory, then this is the same as setting the
-\&\*(L"\s-1TMPDIR\*(R"\s0 environment variable.
+If the parameter is a directory, then this is the same as setting the \*(L"\s-1TMPDIR\*(R"\s0 environment variable.
.Sp
You cannot use this option and \fI\-\-in\-place\fR together.
.IP "\fB\-\-tmp\fR prebuilt:file" 4
.IX Item "--tmp prebuilt:file"
-In copying mode only, the specialized option \fI\-\-tmp prebuilt:file\fR (where
-\&\f(CW\*(C`prebuilt:\*(C'\fR is a literal string) causes virt-sparsify to use the qcow2
-\&\f(CW\*(C`file\*(C'\fR as temporary space.
+In copying mode only, the specialized option \fI\-\-tmp prebuilt:file\fR (where \f(CW\*(C`prebuilt:\*(C'\fR is a literal string) causes virt-sparsify to use the qcow2 \f(CW\*(C`file\*(C'\fR as temporary space.
.RS 4
.IP "\(bu" 4
-The file \fBmust\fR be freshly formatted as qcow2, with indisk as the backing
-file.
+The file \fBmust\fR be freshly formatted as qcow2, with indisk as the backing file.
.IP "\(bu" 4
If you rerun virt-sparsify, you \fBmust\fR recreate the file before each run.
.IP "\(bu" 4
.RE
.RS 4
.Sp
-This option is used by oVirt which requires a specially formatted temporary
-file.
+This option is used by oVirt which requires a specially formatted temporary file.
.RE
.IP "\fB\-v\fR" 4
.IX Item "-v"
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
仮想マシンにある名前付きパーティションまたは論理ボリュームの内容をゼロ上書きします。デバイスにあるすべてのデータは失われます。しかし、スパース化は素晴らしいことです！このオプションを複数回指定できます。
.SH "IN-PLACE SPARSIFICATION"
.IX Header "IN-PLACE SPARSIFICATION"
-Since virt-sparsify ≥ 1.26, the tool is able to do in-place
-sparsification (instead of copying from an input disk to an output disk).
-This is more efficient. It is not able to recover quite as much space as
-copying sparsification.
+Since virt-sparsify ≥ 1.26, the tool is able to do in-place sparsification (instead of copying from an input disk to an output disk). This is more efficient. It is not able to recover quite as much space as copying sparsification.
.PP
To use this mode, specify a disk image which will be modified in place:
.PP
\& virt\-sparsify \-\-in\-place disk.img
.Ve
.PP
-Some options are not compatible with this mode: \fI\-\-convert\fR, \fI\-\-compress\fR
-and \fI\-o\fR because they require wholesale disk format changes;
-\&\fI\-\-check\-tmpdir\fR because large amounts of temporary space are not required.
+Some options are not compatible with this mode: \fI\-\-convert\fR, \fI\-\-compress\fR and \fI\-o\fR because they require wholesale disk format changes; \fI\-\-check\-tmpdir\fR because large amounts of temporary space are not required.
.PP
In-place sparsification works using discard (a.k.a trim or unmap) support.
.SH "マシン可読な出力"
.IX Header "マシン可読な出力"
-The \fI\-\-machine\-readable\fR option can be used to make the output more machine
-friendly, which is useful when calling virt-sparsify from other programs,
-GUIs etc.
+The \fI\-\-machine\-readable\fR option can be used to make the output more machine friendly, which is useful when calling virt-sparsify from other programs, GUIs etc.
.PP
このオプションを使用するには 2 通りの方法があります。
.PP
-Firstly use the option on its own to query the capabilities of the
-virt-sparsify binary. Typical output looks like this:
+Firstly use the option on its own to query the capabilities of the virt-sparsify binary. Typical output looks like this:
.PP
.Vb 4
\& $ virt\-sparsify \-\-machine\-readable
\& btrfs
.Ve
.PP
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
.PP
-Secondly use the option in conjunction with other options to make the
-regular program output more machine friendly.
+Secondly use the option in conjunction with other options to make the regular program output more machine friendly.
.PP
At the moment this means:
.IP "1." 4
-Progress bar messages can be parsed from stdout by looking for this regular
-expression:
+Progress bar messages can be parsed from stdout by looking for this regular expression:
.Sp
.Vb 1
\& ^[0\-9]+/[0\-9]+$
.Ve
.IP "2." 4
-The calling program should treat messages sent to stdout (except for
-progress bar messages) as status messages. They can be logged and/or
-displayed to the user.
+The calling program should treat messages sent to stdout (except for progress bar messages) as status messages. They can be logged and/or displayed to the user.
.IP "3." 4
-The calling program should treat messages sent to stderr as error messages.
-In addition, virt-sparsify exits with a non-zero status code if there was a
-fatal error.
+The calling program should treat messages sent to stderr as error messages. In addition, virt-sparsify exits with a non-zero status code if there was a fatal error.
.PP
-All versions of virt-sparsify have supported the \fI\-\-machine\-readable\fR
-option.
+All versions of virt-sparsify have supported the \fI\-\-machine\-readable\fR option.
.PP
-It is possible to specify a format string for controlling the output; see
-\&\*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
+It is possible to specify a format string for controlling the output; see \*(L"\s-1ADVANCED MACHINE READABLE OUTPUT\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "WINDOWS 8"
.IX Header "WINDOWS 8"
-Windows 8 \*(L"fast startup\*(R" can prevent virt-sparsify from working. See
-\&\*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
+Windows 8 \*(L"fast startup\*(R" can prevent virt-sparsify from working. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "環境変数"
.IX Header "環境変数"
.IP "\s-1TMPDIR\s0" 4
.IX Item "TMPDIR"
-Location of the temporary directory used for the potentially large temporary
-overlay file.
+Location of the temporary directory used for the potentially large temporary overlay file.
.Sp
-In virt-sparsify ≥ 1.28, you can override this environment variable
-using the \fI\-\-tmp\fR option.
+In virt-sparsify ≥ 1.28, you can override this environment variable using the \fI\-\-tmp\fR option.
.Sp
-You should ensure there is enough free space in the worst case for a full
-copy of the source disk (\fIvirtual\fR size), or else set \f(CW$TMPDIR\fR to point
-to another directory that has enough space.
+You should ensure there is enough free space in the worst case for a full copy of the source disk (\fIvirtual\fR size), or else set \f(CW$TMPDIR\fR to point to another directory that has enough space.
.Sp
This defaults to \fI/tmp\fR.
.Sp
-Note that if \f(CW$TMPDIR\fR is a tmpfs (eg. if \fI/tmp\fR is on tmpfs, or if you
-use \f(CW\*(C`TMPDIR=/dev/shm\*(C'\fR), tmpfs defaults to a maximum size of \fIhalf\fR of
-physical \s-1RAM.\s0 If virt-sparsify exceeds this, it will hang. The solution is
-either to use a real disk, or to increase the maximum size of the tmpfs
-mountpoint, eg:
+Note that if \f(CW$TMPDIR\fR is a tmpfs (eg. if \fI/tmp\fR is on tmpfs, or if you use \f(CW\*(C`TMPDIR=/dev/shm\*(C'\fR), tmpfs defaults to a maximum size of \fIhalf\fR of physical \s-1RAM.\s0 If virt-sparsify exceeds this, it will hang. The solution is either to use a real disk, or to increase the maximum size of the tmpfs mountpoint, eg:
.Sp
.Vb 1
\& mount \-o remount,size=10G /tmp
.Ve
.Sp
-If you are using the \fI\-\-in\-place\fR option, then large amounts of temporary
-space are \fBnot\fR required.
+If you are using the \fI\-\-in\-place\fR option, then large amounts of temporary space are \fBnot\fR required.
.PP
他の環境変数は \*(L"環境変数\*(R" in \fBguestfs\fR\|(3) を参照してください。
.SH "終了ステータス"
.IX Header "終了ステータス"
-This program returns 0 if the operation completed without errors. (This
-doesn't necessarily mean that space could be freed up.)
+This program returns 0 if the operation completed without errors. (This doesn't necessarily mean that space could be freed up.)
.PP
A non-zero exit code indicates an error.
.PP
-If the exit code is \f(CW3\fR and the \fI\-\-in\-place\fR option was used, that
-indicates that discard support is not available in libguestfs, so copying
-mode must be used instead.
+If the exit code is \f(CW3\fR and the \fI\-\-in\-place\fR option was used, that indicates that discard support is not available in libguestfs, so copying mode must be used instead.
.SH "関連項目"
.IX Header "関連項目"
-\&\fBvirt\-df\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1),
-\&\fBqemu\-img\fR\|(1), http://libguestfs.org/.
+\&\fBvirt\-df\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBqemu\-img\fR\|(1), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-sparsify is a tool which can make a virtual machine disk (or any disk
-image) sparse a.k.a. thin-provisioned. This means that free space within
-the disk image can be converted back to free space on the host.
+Virt-sparsify is a tool which can make a virtual machine disk (or any disk image) sparse a.k.a. thin-provisioned. This means that free space within the disk image can be converted back to free space on the host.
-Virt-sparsify can locate and sparsify free space in most filesystems
-(eg. ext2/3/4, btrfs, NTFS, etc.), and also in LVM physical volumes.
+Virt-sparsify can locate and sparsify free space in most filesystems (eg. ext2/3/4, btrfs, NTFS, etc.), and also in LVM physical volumes.
-Virt-sparsify はさまざまなディスクフォーマットを変換することができます。例えば、raw ディスクイメージをシンプロビジョニングされた
-qcow2 イメージに変換することができます。
+Virt-sparsify はさまざまなディスクフォーマットを変換することができます。例えば、raw ディスクイメージをシンプロビジョニングされた qcow2 イメージに変換することができます。
-Virt-sparsify can operate on any disk image, not just ones from virtual
-machines. However if a virtual machine has multiple disks and uses volume
-management, then virt-sparsify will work but not be very effective
-(L<http://bugzilla.redhat.com/887826>).
+Virt-sparsify can operate on any disk image, not just ones from virtual machines. However if a virtual machine has multiple disks and uses volume management, then virt-sparsify will work but not be very effective (L<http://bugzilla.redhat.com/887826>).
=head2 IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES
-If the input is raw, then the default output is raw sparse. B<You must
-check the output size using a tool that understands sparseness> such as C<du
--sh>. It can make a huge difference:
+If the input is raw, then the default output is raw sparse. B<You must check the output size using a tool that understands sparseness> such as C<du -sh>. It can make a huge difference:
$ ls -lh test1.img
-rw-rw-r--. 1 rjones rjones 100M Aug 8 08:08 test1.img
=item *
-Virt-sparsify may require up to 2x the virtual size of the source disk image
-(1 temporary copy + 1 destination image). This is in the worst case and
-usually much less space is required.
+Virt-sparsify may require up to 2x the virtual size of the source disk image (1 temporary copy + 1 destination image). This is in the worst case and usually much less space is required.
-If you are using the I<--in-place> option, then large amounts of temporary
-space are B<not> required.
+If you are using the I<--in-place> option, then large amounts of temporary space are B<not> required.
=item *
=item *
-virt-sparsify は暗号化されたディスクを処理できません。 libguestfs
-は暗号化されたディスクをサポートしますが、暗号化されたディスク自体はスパース化できません。
+virt-sparsify は暗号化されたディスクを処理できません。 libguestfs は暗号化されたディスクをサポートしますが、暗号化されたディスク自体はスパース化できません。
=item *
-Virt-sparsify cannot yet sparsify the space between partitions. Note that
-this space is often used for critical items like bootloaders so it's not
-really unused.
+Virt-sparsify cannot yet sparsify the space between partitions. Note that this space is often used for critical items like bootloaders so it's not really unused.
=item *
-In copy mode, qcow2 internal snapshots are not copied over to the
-destination image.
+In copy mode, qcow2 internal snapshots are not copied over to the destination image.
=back
-You may also want to read the manual pages for the associated tools
-L<virt-filesystems(1)> and L<virt-df(1)> before starting.
+You may also want to read the manual pages for the associated tools L<virt-filesystems(1)> and L<virt-df(1)> before starting.
=head1 例
virt-sparsify indisk outdisk
-which copies C<indisk> to C<outdisk>, making the output sparse. C<outdisk>
-is created, or overwritten if it already exists. The format of the input
-disk is detected (eg. qcow2) and the same format is used for the output
-disk.
+which copies C<indisk> to C<outdisk>, making the output sparse. C<outdisk> is created, or overwritten if it already exists. The format of the input disk is detected (eg. qcow2) and the same format is used for the output disk.
形式を変換するには I<--convert> オプションを使用します:
virt-sparsify disk.raw --convert qcow2 disk.qcow2
-Virt-sparsify tries to zero and sparsify free space on every filesystem it
-can find within the source disk image. You can get it to ignore (don't zero
-free space on) certain filesystems by doing:
+Virt-sparsify tries to zero and sparsify free space on every filesystem it can find within the source disk image. You can get it to ignore (don't zero free space on) certain filesystems by doing:
virt-sparsify --ignore /dev/sda1 indisk outdisk
ディスクイメージにあるファイルシステムの一覧を取得するには L<virt-filesystems(1)> を参照してください。
-Since virt-sparsify E<ge> 1.26, you can now sparsify a disk image in place
-by doing:
+Since virt-sparsify E<ge> 1.26, you can now sparsify a disk image in place by doing:
virt-sparsify --in-place disk.img
=item B<--check-tmpdir> B<fail>
-Check if L</TMPDIR> or I<--tmp> directory has enough space to complete the
-operation. This is just an estimate.
+Check if L</TMPDIR> or I<--tmp> directory has enough space to complete the operation. This is just an estimate.
If the check indicates a problem, then you can either:
=item *
-B<warn> and wait for the user to press the Return key (this is the default),
-or:
+B<warn> and wait for the user to press the Return key (this is the default), or:
=item *
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<--compress>
=item B<--convert> [other formats]
-Use C<output-format> as the format for the destination image. If this is
-not specified, then the input format is used.
+Use C<output-format> as the format for the destination image. If this is not specified, then the input format is used.
サポートされる既知の動作済み出力形式は次のとおりです: C<raw>, C<qcow2>, C<vdi>。
-L<qemu-img(1)> プログラムによりサポートされるすべての形式を使用できます。たとえば、C<vmdk> ですが、他の形式のサポートは QEMU
-に依存します。
+L<qemu-img(1)> プログラムによりサポートされるすべての形式を使用できます。たとえば、C<vmdk> ですが、他の形式のサポートは QEMU に依存します。
-Specifying the I<--convert> option is usually a good idea, because then
-virt-sparsify doesn't need to try to guess the input format.
+Specifying the I<--convert> option is usually a good idea, because then virt-sparsify doesn't need to try to guess the input format.
出力形式を詳細に調整します。関連項目: I<--compress>, I<-o>.
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-sparsify normally turns
-echoing off so you cannot see what you are typing. If you are not worried
-about Tempest attacks and there is no one else in the room you can specify
-this flag to see what you are typing.
+When prompting for keys and passphrases, virt-sparsify normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--format> raw
=item B<--format> qcow2
-Specify the format of the input disk image. If this flag is not given then
-it is auto-detected from the image itself.
+Specify the format of the input disk image. If this flag is not given then it is auto-detected from the image itself.
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
=item B<--ignore> filesystem
Ignore the named filesystem.
-When not using I<--in-place>: Free space on the filesystem will not be
-zeroed, but existing blocks of zeroes will still be sparsified.
+When not using I<--in-place>: Free space on the filesystem will not be zeroed, but existing blocks of zeroes will still be sparsified.
When using I<--in-place>, the filesystem is ignored completely.
-In the second form, this ignores the named volume group. Use the volume
-group name without the F</dev/> prefix, eg. I<--ignore vg_foo>
+In the second form, this ignores the named volume group. Use the volume group name without the F</dev/> prefix, eg. I<--ignore vg_foo>
このオプションは複数回指定できます。
=item B<--in-place>
-Do in-place sparsification instead of copying sparsification. See
-L</IN-PLACE SPARSIFICATION> below.
+Do in-place sparsification instead of copying sparsification. See L</IN-PLACE SPARSIFICATION> below.
__INCLUDE:key-option.pod__
=item B<-o> option[,option,...]
-Pass I<-o> option(s) to the L<qemu-img(1)> command to fine-tune the output
-format. Options available depend on the output format (see I<--convert>)
-and the installed version of the qemu-img program.
+Pass I<-o> option(s) to the L<qemu-img(1)> command to fine-tune the output format. Options available depend on the output format (see I<--convert>) and the installed version of the qemu-img program.
-You should use I<-o> at most once. To pass multiple options, separate them
-with commas, eg:
+You should use I<-o> at most once. To pass multiple options, separate them with commas, eg:
virt-sparsify --convert qcow2 \
-o cluster_size=512,preallocation=metadata ...
=item B<--tmp> dir
-In copying mode only, use the named device or directory as the location of
-the temporary overlay (see also L</TMPDIR> below).
+In copying mode only, use the named device or directory as the location of the temporary overlay (see also L</TMPDIR> below).
-If the parameter given is a block device, then the block device is written
-to directly. B<Note this erases the existing contents of the block device>.
+If the parameter given is a block device, then the block device is written to directly. B<Note this erases the existing contents of the block device>.
-If the parameter is a directory, then this is the same as setting the
-L</TMPDIR> environment variable.
+If the parameter is a directory, then this is the same as setting the L</TMPDIR> environment variable.
You cannot use this option and I<--in-place> together.
=item B<--tmp> prebuilt:file
-In copying mode only, the specialized option I<--tmp prebuilt:file> (where
-C<prebuilt:> is a literal string) causes virt-sparsify to use the qcow2
-C<file> as temporary space.
+In copying mode only, the specialized option I<--tmp prebuilt:file> (where C<prebuilt:> is a literal string) causes virt-sparsify to use the qcow2 C<file> as temporary space.
=over 4
=item *
-The file B<must> be freshly formatted as qcow2, with indisk as the backing
-file.
+The file B<must> be freshly formatted as qcow2, with indisk as the backing file.
=item *
=back
-This option is used by oVirt which requires a specially formatted temporary
-file.
+This option is used by oVirt which requires a specially formatted temporary file.
=item B<-v>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 IN-PLACE SPARSIFICATION
-Since virt-sparsify E<ge> 1.26, the tool is able to do in-place
-sparsification (instead of copying from an input disk to an output disk).
-This is more efficient. It is not able to recover quite as much space as
-copying sparsification.
+Since virt-sparsify E<ge> 1.26, the tool is able to do in-place sparsification (instead of copying from an input disk to an output disk). This is more efficient. It is not able to recover quite as much space as copying sparsification.
To use this mode, specify a disk image which will be modified in place:
virt-sparsify --in-place disk.img
-Some options are not compatible with this mode: I<--convert>, I<--compress>
-and I<-o> because they require wholesale disk format changes;
-I<--check-tmpdir> because large amounts of temporary space are not required.
+Some options are not compatible with this mode: I<--convert>, I<--compress> and I<-o> because they require wholesale disk format changes; I<--check-tmpdir> because large amounts of temporary space are not required.
In-place sparsification works using discard (a.k.a trim or unmap) support.
=head1 マシン可読な出力
-The I<--machine-readable> option can be used to make the output more machine
-friendly, which is useful when calling virt-sparsify from other programs,
-GUIs etc.
+The I<--machine-readable> option can be used to make the output more machine friendly, which is useful when calling virt-sparsify from other programs, GUIs etc.
このオプションを使用するには 2 通りの方法があります。
-Firstly use the option on its own to query the capabilities of the
-virt-sparsify binary. Typical output looks like this:
+Firstly use the option on its own to query the capabilities of the virt-sparsify binary. Typical output looks like this:
$ virt-sparsify --machine-readable
virt-sparsify
ntfs
btrfs
-A list of features is printed, one per line, and the program exits with
-status 0.
+A list of features is printed, one per line, and the program exits with status 0.
-Secondly use the option in conjunction with other options to make the
-regular program output more machine friendly.
+Secondly use the option in conjunction with other options to make the regular program output more machine friendly.
At the moment this means:
=item 1.
-Progress bar messages can be parsed from stdout by looking for this regular
-expression:
+Progress bar messages can be parsed from stdout by looking for this regular expression:
^[0-9]+/[0-9]+$
=item 2.
-The calling program should treat messages sent to stdout (except for
-progress bar messages) as status messages. They can be logged and/or
-displayed to the user.
+The calling program should treat messages sent to stdout (except for progress bar messages) as status messages. They can be logged and/or displayed to the user.
=item 3.
-The calling program should treat messages sent to stderr as error messages.
-In addition, virt-sparsify exits with a non-zero status code if there was a
-fatal error.
+The calling program should treat messages sent to stderr as error messages. In addition, virt-sparsify exits with a non-zero status code if there was a fatal error.
=back
-All versions of virt-sparsify have supported the I<--machine-readable>
-option.
+All versions of virt-sparsify have supported the I<--machine-readable> option.
-It is possible to specify a format string for controlling the output; see
-L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
+It is possible to specify a format string for controlling the output; see L<guestfs(3)/ADVANCED MACHINE READABLE OUTPUT>.
=head1 WINDOWS 8
-Windows 8 "fast startup" can prevent virt-sparsify from working. See
-L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
+Windows 8 "fast startup" can prevent virt-sparsify from working. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
=head1 環境変数
=item TMPDIR
-Location of the temporary directory used for the potentially large temporary
-overlay file.
+Location of the temporary directory used for the potentially large temporary overlay file.
-In virt-sparsify E<ge> 1.28, you can override this environment variable
-using the I<--tmp> option.
+In virt-sparsify E<ge> 1.28, you can override this environment variable using the I<--tmp> option.
-You should ensure there is enough free space in the worst case for a full
-copy of the source disk (I<virtual> size), or else set C<$TMPDIR> to point
-to another directory that has enough space.
+You should ensure there is enough free space in the worst case for a full copy of the source disk (I<virtual> size), or else set C<$TMPDIR> to point to another directory that has enough space.
This defaults to F</tmp>.
-Note that if C<$TMPDIR> is a tmpfs (eg. if F</tmp> is on tmpfs, or if you
-use C<TMPDIR=/dev/shm>), tmpfs defaults to a maximum size of I<half> of
-physical RAM. If virt-sparsify exceeds this, it will hang. The solution is
-either to use a real disk, or to increase the maximum size of the tmpfs
-mountpoint, eg:
+Note that if C<$TMPDIR> is a tmpfs (eg. if F</tmp> is on tmpfs, or if you use C<TMPDIR=/dev/shm>), tmpfs defaults to a maximum size of I<half> of physical RAM. If virt-sparsify exceeds this, it will hang. The solution is either to use a real disk, or to increase the maximum size of the tmpfs mountpoint, eg:
mount -o remount,size=10G /tmp
-If you are using the I<--in-place> option, then large amounts of temporary
-space are B<not> required.
+If you are using the I<--in-place> option, then large amounts of temporary space are B<not> required.
=back
=head1 終了ステータス
-This program returns 0 if the operation completed without errors. (This
-doesn't necessarily mean that space could be freed up.)
+This program returns 0 if the operation completed without errors. (This doesn't necessarily mean that space could be freed up.)
A non-zero exit code indicates an error.
-If the exit code is C<3> and the I<--in-place> option was used, that
-indicates that discard support is not available in libguestfs, so copying
-mode must be used instead.
+If the exit code is C<3> and the I<--in-place> option was used, that indicates that discard support is not available in libguestfs, so copying mode must be used instead.
=head1 関連項目
-L<virt-df(1)>, L<virt-filesystems(1)>, L<virt-resize(1)>, L<virt-rescue(1)>,
-L<guestfs(3)>, L<guestfish(1)>, L<truncate(1)>, L<fallocate(1)>,
-L<qemu-img(1)>, L<http://libguestfs.org/>.
+L<virt-df(1)>, L<virt-filesystems(1)>, L<virt-resize(1)>, L<virt-rescue(1)>, L<guestfs(3)>, L<guestfish(1)>, L<truncate(1)>, L<fallocate(1)>, L<qemu-img(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-sysprep 1"
-.TH virt-sysprep 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-sysprep 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "説明"
.IX Header "説明"
-Virt-sysprep can reset or unconfigure a virtual machine so that clones can
-be made from it. Steps in this process include removing \s-1SSH\s0 host keys,
-removing persistent network \s-1MAC\s0 configuration, and removing user accounts.
-Virt-sysprep can also customize a virtual machine, for instance by adding
-\&\s-1SSH\s0 keys, users or logos. Each step can be enabled or disabled as required.
-.PP
-Virt-sysprep modifies the guest or disk image \fIin place\fR. The guest must
-be shut down. If you want to preserve the existing contents of the guest,
-\&\fIyou must snapshot, copy or clone the disk first\fR. See \*(L"\s-1COPYING AND
-CLONING\*(R"\s0 below.
-.PP
-You do \fInot\fR need to run virt-sysprep as root. In fact we'd generally
-recommend that you don't. The time you might want to run it as root is when
-you need root in order to access the disk image, but even in this case it
-would be better to change the permissions on the disk image to be writable
-as the non-root user running virt-sysprep.
-.PP
-\&\*(L"Sysprep\*(R" stands for \*(L"system preparation\*(R" tool. The name comes from the
-Microsoft program \fIsysprep.exe\fR which is used to unconfigure Windows
-machines in preparation for cloning them. Having said that, virt-sysprep
-does \fInot\fR currently work on Microsoft Windows guests. We plan to support
-Windows sysprepping in a future version, and we already have code to do it.
+Virt-sysprep can reset or unconfigure a virtual machine so that clones can be made from it. Steps in this process include removing \s-1SSH\s0 host keys, removing persistent network \s-1MAC\s0 configuration, and removing user accounts. Virt-sysprep can also customize a virtual machine, for instance by adding \s-1SSH\s0 keys, users or logos. Each step can be enabled or disabled as required.
+.PP
+Virt-sysprep modifies the guest or disk image \fIin place\fR. The guest must be shut down. If you want to preserve the existing contents of the guest, \fIyou must snapshot, copy or clone the disk first\fR. See \*(L"\s-1COPYING AND CLONING\*(R"\s0 below.
+.PP
+You do \fInot\fR need to run virt-sysprep as root. In fact we'd generally recommend that you don't. The time you might want to run it as root is when you need root in order to access the disk image, but even in this case it would be better to change the permissions on the disk image to be writable as the non-root user running virt-sysprep.
+.PP
+\&\*(L"Sysprep\*(R" stands for \*(L"system preparation\*(R" tool. The name comes from the Microsoft program \fIsysprep.exe\fR which is used to unconfigure Windows machines in preparation for cloning them. Having said that, virt-sysprep does \fInot\fR currently work on Microsoft Windows guests. We plan to support Windows sysprepping in a future version, and we already have code to do it.
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR \s-1URI\s0" 4
.IX Item "--add URI"
.PD
-Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See
-\&\*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
+Add a remote disk. The \s-1URI\s0 format is compatible with guestfish. See \*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-\&\s-1ANSI\s0 colour sequences are disabled unless you use this option.
+Use \s-1ANSI\s0 colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, \s-1ANSI\s0 colour sequences are disabled unless you use this option.
.IP "\fB\-c\fR \s-1URI\s0" 4
.IX Item "-c URI"
.PD 0
.IP "\fB\-\-dry\-run\fR" 4
.IX Item "--dry-run"
.PD
-Perform a read-only \*(L"dry run\*(R" on the guest. This runs the sysprep
-operation, but throws away any changes to the disk at the end.
+Perform a read-only \*(L"dry run\*(R" on the guest. This runs the sysprep operation, but throws away any changes to the disk at the end.
.IP "\fB\-\-enable\fR operations" 4
.IX Item "--enable operations"
-Choose which sysprep operations to perform. Give a comma-separated list of
-operations, for example:
+Choose which sysprep operations to perform. Give a comma-separated list of operations, for example:
.Sp
.Vb 1
\& \-\-enable ssh\-hostkeys,udev\-persistent\-net
.Sp
would enable \s-1ONLY\s0 \f(CW\*(C`ssh\-hostkeys\*(C'\fR and \f(CW\*(C`udev\-persistent\-net\*(C'\fR operations.
.Sp
-If the \fI\-\-enable\fR option is not given, then we default to trying most
-sysprep operations (see \fI\-\-list\-operations\fR to show which are enabled).
+If the \fI\-\-enable\fR option is not given, then we default to trying most sysprep operations (see \fI\-\-list\-operations\fR to show which are enabled).
.Sp
-Regardless of the \fI\-\-enable\fR option, sysprep operations are skipped for
-some guest types.
+Regardless of the \fI\-\-enable\fR option, sysprep operations are skipped for some guest types.
.Sp
特定のバージョンの virt-sysprep によりサポートされる操作の一覧を表示するには \fI\-\-list\-operations\fR を使用します。
.Sp
.IP "\fB\-\-operations\fR operations" 4
.IX Item "--operations operations"
.PD
-Choose which sysprep operations to perform. Give a comma-separated list of
-operations, for example:
+Choose which sysprep operations to perform. Give a comma-separated list of operations, for example:
.Sp
.Vb 1
\& \-\-operations ssh\-hostkeys,udev\-persistent\-net
.Sp
would enable \s-1ONLY\s0 \f(CW\*(C`ssh\-hostkeys\*(C'\fR and \f(CW\*(C`udev\-persistent\-net\*(C'\fR operations.
.Sp
-\&\fI\-\-operations\fR allows you to enable and disable any operation, including
-the default ones (which would be tried when specifying neither
-\&\fI\-\-operations\fR nor \fI\-\-enable\fR) and all the available ones; prepending a
-\&\f(CW\*(C`\-\*(C'\fR in front of an operation name removes it from the list of enabled
-operations, while the meta-names \f(CW\*(C`defaults\*(C'\fR and \f(CW\*(C`all\*(C'\fR represent
-respectively the operations enabled by default and all the available ones.
-For example:
+\&\fI\-\-operations\fR allows you to enable and disable any operation, including the default ones (which would be tried when specifying neither \fI\-\-operations\fR nor \fI\-\-enable\fR) and all the available ones; prepending a \f(CW\*(C`\-\*(C'\fR in front of an operation name removes it from the list of enabled operations, while the meta-names \f(CW\*(C`defaults\*(C'\fR and \f(CW\*(C`all\*(C'\fR represent respectively the operations enabled by default and all the available ones. For example:
.Sp
.Vb 1
\& \-\-operations firewall\-rules,defaults,\-tmp\-files
.Ve
.Sp
-would enable the \f(CW\*(C`firewall\-rules\*(C'\fR operation (regardless whether it is
-enabled by default), all the default ones, and disable the \f(CW\*(C`tmp\-files\*(C'\fR
-operation.
+would enable the \f(CW\*(C`firewall\-rules\*(C'\fR operation (regardless whether it is enabled by default), all the default ones, and disable the \f(CW\*(C`tmp\-files\*(C'\fR operation.
.Sp
-\&\fI\-\-operations\fR can be specified multiple times; the first time the set of
-enabled operations is empty, while any further \fI\-\-operations\fR affects the
-operations enabled so far.
+\&\fI\-\-operations\fR can be specified multiple times; the first time the set of enabled operations is empty, while any further \fI\-\-operations\fR affects the operations enabled so far.
.Sp
-If the \fI\-\-operations\fR option is not given, then we default to trying most
-sysprep operations (see \fI\-\-list\-operations\fR to show which are enabled).
+If the \fI\-\-operations\fR option is not given, then we default to trying most sysprep operations (see \fI\-\-list\-operations\fR to show which are enabled).
.Sp
-Regardless of the \fI\-\-operations\fR option, sysprep operations are skipped for
-some guest types.
+Regardless of the \fI\-\-operations\fR option, sysprep operations are skipped for some guest types.
.Sp
特定のバージョンの virt-sysprep によりサポートされる操作の一覧を表示するには \fI\-\-list\-operations\fR を使用します。
.Sp
See \*(L"\s-1OPERATIONS\*(R"\s0 below for a list and an explanation of each operation.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-When prompting for keys and passphrases, virt-sysprep normally turns echoing
-off so you cannot see what you are typing. If you are not worried about
-Tempest attacks and there is no one else in the room you can specify this
-flag to see what you are typing.
+When prompting for keys and passphrases, virt-sysprep normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-The default for the \fI\-a\fR option is to auto-detect the format of the disk
-image. Using this forces the disk format for \fI\-a\fR options which follow on
-the command line. Using \fI\-\-format auto\fR switches back to auto-detection
-for subsequent \fI\-a\fR options.
+The default for the \fI\-a\fR option is to auto-detect the format of the disk image. Using this forces the disk format for \fI\-a\fR options which follow on the command line. Using \fI\-\-format auto\fR switches back to auto-detection for subsequent \fI\-a\fR options.
.Sp
例:
.Sp
\& virt\-sysprep \-\-format raw \-a disk.img \-\-format auto \-a another.img
.Ve
.Sp
-forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
-auto-detection for \fIanother.img\fR.
+forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to auto-detection for \fIanother.img\fR.
.Sp
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (\s-1CVE\-2010\-3851\s0)。
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IX Item "--list-operations"
virt-sysprep プログラムによりサポートされる操作を一覧表示します。
.Sp
-These are listed one per line, with one or more single-space-separated
-fields, eg:
+These are listed one per line, with one or more single-space-separated fields, eg:
.Sp
.Vb 6
\& $ virt\-sysprep \-\-list\-operations
\& [etc]
.Ve
.Sp
-The first field is the operation name, which can be supplied to
-\&\fI\-\-enable\fR. The second field is a \f(CW\*(C`*\*(C'\fR character if the operation is
-enabled by default or blank if not. Subsequent fields on the same line are
-the description of the operation.
+The first field is the operation name, which can be supplied to \fI\-\-enable\fR. The second field is a \f(CW\*(C`*\*(C'\fR character if the operation is enabled by default or blank if not. Subsequent fields on the same line are the description of the operation.
.Sp
-Before libguestfs 1.17.33 only the first (operation name) field was shown
-and all operations were enabled by default.
+Before libguestfs 1.17.33 only the first (operation name) field was shown and all operations were enabled by default.
.IP "\fB\-\-mount\-options\fR mp:opts[;mp:opts;...]" 4
.IX Item "--mount-options mp:opts[;mp:opts;...]"
-Set the mount options used when libguestfs opens the disk image. Note this
-has no effect on the guest. It is used when opening certain guests such as
-ones using the \s-1UFS\s0 (\s-1BSD\s0) filesystem.
+Set the mount options used when libguestfs opens the disk image. Note this has no effect on the guest. It is used when opening certain guests such as ones using the \s-1UFS\s0 (\s-1BSD\s0) filesystem.
.Sp
-Use a semicolon-separated list of \f(CW\*(C`mountpoint:options\*(C'\fR pairs. You may need
-to quote this list to protect it from the shell.
+Use a semicolon-separated list of \f(CW\*(C`mountpoint:options\*(C'\fR pairs. You may need to quote this list to protect it from the shell.
.Sp
例:
.Sp
.PD
Enable or disable network access from the guest during the installation.
.Sp
-In virt-sysprep, the network is \fIdisabled\fR by default. You must use
-\&\fI\-\-network\fR to enable it, in order that options such as \fI\-\-install\fR or
-\&\fI\-\-update\fR will work.
+In virt-sysprep, the network is \fIdisabled\fR by default. You must use \fI\-\-network\fR to enable it, in order that options such as \fI\-\-install\fR or \fI\-\-update\fR will work.
.Sp
-\&\fBvirt\-builder\fR\|(1) has more information about the security advantages of
-disabling the network.
+\&\fBvirt\-builder\fR\|(1) has more information about the security advantages of disabling the network.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IX Item "--version"
.PD
バージョン番号を表示して、終了します。
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
libguestfs \s-1API\s0 呼び出しのトレースを有効にします。
.ie n .IP "\fB\-\-append\-line\fR \s-1FILE:LINE\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-append\-line\fR \s-1FILE:LINE\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--append-line FILE:LINE (see customize below)"
-Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already
-end with a newline, then one is added before the appended line. Also a
-newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
+Append a single line of text to the \f(CW\*(C`FILE\*(C'\fR. If the file does not already end with a newline, then one is added before the appended line. Also a newline is added to the end of the \f(CW\*(C`LINE\*(C'\fR string automatically.
.Sp
For example (assuming ordinary shell quoting) this command:
.Sp
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the
-latter only if the existing file does not already end with a newline.
+will add either \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR or \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR to the file, the latter only if the existing file does not already end with a newline.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the
-existing content of the file, so this command does the right thing for files
-using Unix or Windows line endings. It also works for empty or non-existent
-files.
+\&\f(CW\*(C`⏎\*(C'\fR represents a newline character, which is guessed by looking at the existing content of the file, so this command does the right thing for files using Unix or Windows line endings. It also works for empty or non-existent files.
.Sp
To insert several lines, use the same option several times:
.Sp
.IX Item "--chmod PERMISSIONS:FILE (see customize below)"
Change the permissions of \f(CW\*(C`FILE\*(C'\fR to \f(CW\*(C`PERMISSIONS\*(C'\fR.
.Sp
-\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it
-with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
+\&\fINote\fR: \f(CW\*(C`PERMISSIONS\*(C'\fR by default would be decimal, unless you prefix it with \f(CW0\fR to get octal, ie. use \f(CW0700\fR not \f(CW700\fR.
.ie n .IP "\fB\-\-commands\-from\-file\fR \s-1FILENAME\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-commands\-from\-file\fR \s-1FILENAME\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--commands-from-file FILENAME (see customize below)"
Read the customize commands from a file, one (and its arguments) each line.
.Sp
-Each line contains a single customization command and its arguments, for
-example:
+Each line contains a single customization command and its arguments, for example:
.Sp
.Vb 3
\& delete /some/file
\& password some\-user:password:its\-new\-password
.Ve
.Sp
-Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are
-ignored as well. Furthermore, arguments can be spread across multiple
-lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for
-example
+Empty lines are ignored, and lines starting with \f(CW\*(C`#\*(C'\fR are comments and are ignored as well. Furthermore, arguments can be spread across multiple lines, by adding a \f(CW\*(C`\e\*(C'\fR (continuation character) at the of a line, for example
.Sp
.Vb 2
\& edit /some/file:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-The commands are handled in the same order as they are in the file, as if
-they were specified as \fI\-\-delete /some/file\fR on the command line.
+The commands are handled in the same order as they are in the file, as if they were specified as \fI\-\-delete /some/file\fR on the command line.
.ie n .IP "\fB\-\-copy\fR \s-1SOURCE:DEST\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-copy\fR \s-1SOURCE:DEST\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--copy SOURCE:DEST (see customize below)"
.ie n .IP "\fB\-\-copy\-in\fR \s-1LOCALPATH:REMOTEDIR\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-copy\-in\fR \s-1LOCALPATH:REMOTEDIR\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--copy-in LOCALPATH:REMOTEDIR (see customize below)"
-Copy local files or directories recursively into the disk image, placing
-them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
+Copy local files or directories recursively into the disk image, placing them in the directory \f(CW\*(C`REMOTEDIR\*(C'\fR (which must exist).
.Sp
Wildcards cannot be used.
.ie n .IP "\fB\-\-delete\fR \s-1PATH\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-delete\fR \s-1PATH\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--delete PATH (see customize below)"
-Delete a file from the guest. Or delete a directory (and all its contents,
-recursively).
+Delete a file from the guest. Or delete a directory (and all its contents, recursively).
.Sp
-You can use shell glob characters in the specified path. Be careful to
-escape glob characters from the host shell, if that is required. For
-example:
+You can use shell glob characters in the specified path. Be careful to escape glob characters from the host shell, if that is required. For example:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
.ie n .IP "\fB\-\-firstboot\fR \s-1SCRIPT\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-firstboot\fR \s-1SCRIPT\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--firstboot SCRIPT (see customize below)"
-Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up,
-the script runs (as root, late in the boot process).
+Install \f(CW\*(C`SCRIPT\*(C'\fR inside the guest, so that when the guest first boots up, the script runs (as root, late in the boot process).
.Sp
The script is automatically chmod +x after installation in the guest.
.Sp
-The alternative version \fI\-\-firstboot\-command\fR is the same, but it
-conveniently wraps the command up in a single line script for you.
+The alternative version \fI\-\-firstboot\-command\fR is the same, but it conveniently wraps the command up in a single line script for you.
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.ie n .IP "\fB\-\-firstboot\-command\fR '\s-1CMD+ARGS\s0' (see ""customize"" below)" 4
.el .IP "\fB\-\-firstboot\-command\fR '\s-1CMD+ARGS\s0' (see \f(CWcustomize\fR below)" 4
.IX Item "--firstboot-command 'CMD+ARGS' (see customize below)"
-Run command (and arguments) inside the guest when the guest first boots up
-(as root, late in the boot process).
+Run command (and arguments) inside the guest when the guest first boots up (as root, late in the boot process).
.Sp
-You can have multiple \fI\-\-firstboot\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-firstboot\fR options. They run in the same order that they appear on the command line.
.Sp
-Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more
-information and caveats about the first boot scripts.
+Please take a look at \*(L"\s-1FIRST BOOT SCRIPTS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for more information and caveats about the first boot scripts.
.Sp
See also \fI\-\-run\fR.
.ie n .IP "\fB\-\-firstboot\-install\fR \s-1PKG,PKG..\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-firstboot\-install\fR \s-1PKG,PKG..\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--firstboot-install PKG,PKG.. (see customize below)"
-Install the named packages (a comma-separated list). These are installed
-when the guest first boots using the guest’s package manager (eg. apt, yum,
-etc.) and the guest’s network connection.
+Install the named packages (a comma-separated list). These are installed when the guest first boots using the guest’s package manager (eg. apt, yum, etc.) and the guest’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.ie n .IP "\fB\-\-hostname\fR \s-1HOSTNAME\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-hostname\fR \s-1HOSTNAME\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--hostname HOSTNAME (see customize below)"
-Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted
-hostname.domainname (\s-1FQDN\s0) if you want.
+Set the hostname of the guest to \f(CW\*(C`HOSTNAME\*(C'\fR. You can use a dotted hostname.domainname (\s-1FQDN\s0) if you want.
.ie n .IP "\fB\-\-install\fR \s-1PKG,PKG..\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-install\fR \s-1PKG,PKG..\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--install PKG,PKG.. (see customize below)"
-Install the named packages (a comma-separated list). These are installed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.) and the host’s network connection.
+Install the named packages (a comma-separated list). These are installed during the image build using the guest’s package manager (eg. apt, yum, etc.) and the host’s network connection.
.Sp
-For an overview on the different ways to install packages, see
-\&\*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
+For an overview on the different ways to install packages, see \*(L"\s-1INSTALLING PACKAGES\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.Sp
See also \fI\-\-update\fR, \fI\-\-uninstall\fR.
.ie n .IP "\fB\-\-keep\-user\-accounts\fR \s-1USERS\s0 (see ""user\-account"" below)" 4
.el .IP "\fB\-\-keep\-user\-accounts\fR \s-1USERS\s0 (see \f(CWuser\-account\fR below)" 4
.IX Item "--keep-user-accounts USERS (see user-account below)"
-The user accounts to be kept in the guest. The value of this option is a
-list of user names separated by comma, where specifying an user means it is
-going to be kept. For example:
+The user accounts to be kept in the guest. The value of this option is a list of user names separated by comma, where specifying an user means it is going to be kept. For example:
.Sp
.Vb 1
\& \-\-keep\-user\-accounts mary
.ie n .IP "\fB\-\-link\fR TARGET:LINK[:LINK..] (see ""customize"" below)" 4
.el .IP "\fB\-\-link\fR TARGET:LINK[:LINK..] (see \f(CWcustomize\fR below)" 4
.IX Item "--link TARGET:LINK[:LINK..] (see customize below)"
-Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at
-\&\f(CW\*(C`TARGET\*(C'\fR.
+Create symbolic link(s) in the guest, starting at \f(CW\*(C`LINK\*(C'\fR and pointing at \f(CW\*(C`TARGET\*(C'\fR.
.ie n .IP "\fB\-\-mkdir\fR \s-1DIR\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-mkdir\fR \s-1DIR\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--mkdir DIR (see customize below)"
Create a directory in the guest.
.Sp
-This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it
-also works if the directory already exists.
+This uses \f(CW\*(C`mkdir \-p\*(C'\fR so any intermediate directories are created, and it also works if the directory already exists.
.ie n .IP "\fB\-\-move\fR \s-1SOURCE:DEST\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-move\fR \s-1SOURCE:DEST\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--move SOURCE:DEST (see customize below)"
.ie n .IP "\fB\-\-no\-logfile\fR (see ""customize"" below)" 4
.el .IP "\fB\-\-no\-logfile\fR (see \f(CWcustomize\fR below)" 4
.IX Item "--no-logfile (see customize below)"
-Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after
-building is complete. If you don't want to reveal precisely how the image
-was built, use this option.
+Scrub \f(CW\*(C`builder.log\*(C'\fR (log file from build commands) from the image after building is complete. If you don't want to reveal precisely how the image was built, use this option.
.Sp
See also: \*(L"\s-1LOG FILE\*(R"\s0.
.ie n .IP "\fB\-\-password\fR \s-1USER:SELECTOR\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-password\fR \s-1USER:SELECTOR\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--password USER:SELECTOR (see customize below)"
-Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user
-account).
+Set the password for \f(CW\*(C`USER\*(C'\fR. (Note this option does \fInot\fR create the user account).
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.ie n .IP "\fB\-\-password\-crypto\fR md5|sha256|sha512 (see ""customize"" below)" 4
.el .IP "\fB\-\-password\-crypto\fR md5|sha256|sha512 (see \f(CWcustomize\fR below)" 4
.IX Item "--password-crypto md5|sha256|sha512 (see customize below)"
-When the virt tools change or set a password in the guest, this option sets
-the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
+When the virt tools change or set a password in the guest, this option sets the password encryption of that password to \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR or \f(CW\*(C`sha512\*(C'\fR.
.Sp
-\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the
-guest).
+\&\f(CW\*(C`sha256\*(C'\fR and \f(CW\*(C`sha512\*(C'\fR require glibc ≥ 2.7 (check \fBcrypt\fR\|(3) inside the guest).
.Sp
-\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not
-secure against modern attacks.
+\&\f(CW\*(C`md5\*(C'\fR will work with relatively old Linux guests (eg. \s-1RHEL 3\s0), but is not secure against modern attacks.
.Sp
-The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't
-have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can
-override libguestfs by specifying this option.
+The default is \f(CW\*(C`sha512\*(C'\fR unless libguestfs detects an old guest that didn't have support for \s-1SHA\-512,\s0 in which case it will use \f(CW\*(C`md5\*(C'\fR. You can override libguestfs by specifying this option.
.Sp
-Note this does not change the default password encryption used by the guest
-when you create new user accounts inside the guest. If you want to do that,
-then you should use the \fI\-\-edit\fR option to modify
-\&\f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR
-(Debian, Ubuntu).
+Note this does not change the default password encryption used by the guest when you create new user accounts inside the guest. If you want to do that, then you should use the \fI\-\-edit\fR option to modify \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) or \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.ie n .IP "\fB\-\-remove\-user\-accounts\fR \s-1USERS\s0 (see ""user\-account"" below)" 4
.el .IP "\fB\-\-remove\-user\-accounts\fR \s-1USERS\s0 (see \f(CWuser\-account\fR below)" 4
.IX Item "--remove-user-accounts USERS (see user-account below)"
-The user accounts to be removed from the guest. The value of this option is
-a list of user names separated by comma, where specifying an user means it
-is going to be removed. For example:
+The user accounts to be removed from the guest. The value of this option is a list of user names separated by comma, where specifying an user means it is going to be removed. For example:
.Sp
.Vb 1
\& \-\-remove\-user\-accounts bob,eve
.IX Item "--root-password SELECTOR (see customize below)"
Set the root password.
.Sp
-See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR
-field, and also how to set up user accounts.
+See \*(L"\s-1USERS AND PASSWORDS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field, and also how to set up user accounts.
.Sp
-Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest
-is given a \fIrandom\fR root password.
+Note: In virt-builder, if you \fIdon't\fR set \fI\-\-root\-password\fR then the guest is given a \fIrandom\fR root password.
.ie n .IP "\fB\-\-run\fR \s-1SCRIPT\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-run\fR \s-1SCRIPT\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--run SCRIPT (see customize below)"
-Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image.
-The script runs virtualized inside a small appliance, chrooted into the
-guest filesystem.
+Run the shell script (or any program) called \f(CW\*(C`SCRIPT\*(C'\fR on the disk image. The script runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
The script is automatically chmod +x.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\fR options. They run in the same order that
-they appear on the command line.
+You can have multiple \fI\-\-run\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.ie n .IP "\fB\-\-run\-command\fR '\s-1CMD+ARGS\s0' (see ""customize"" below)" 4
.el .IP "\fB\-\-run\-command\fR '\s-1CMD+ARGS\s0' (see \f(CWcustomize\fR below)" 4
.IX Item "--run-command 'CMD+ARGS' (see customize below)"
-Run the command and arguments on the disk image. The command runs
-virtualized inside a small appliance, chrooted into the guest filesystem.
+Run the command and arguments on the disk image. The command runs virtualized inside a small appliance, chrooted into the guest filesystem.
.Sp
-If libguestfs supports it then a limited network connection is available but
-it only allows outgoing network connections. You can also attach data disks
-(eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to
-the script without needing a network connection (\fI\-\-attach\fR). You can also
-upload data files (\fI\-\-upload\fR).
+If libguestfs supports it then a limited network connection is available but it only allows outgoing network connections. You can also attach data disks (eg. \s-1ISO\s0 files) as another way to provide data (eg. software packages) to the script without needing a network connection (\fI\-\-attach\fR). You can also upload data files (\fI\-\-upload\fR).
.Sp
-You can have multiple \fI\-\-run\-command\fR options. They run in the same order
-that they appear on the command line.
+You can have multiple \fI\-\-run\-command\fR options. They run in the same order that they appear on the command line.
.Sp
See also: \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.ie n .IP "\fB\-\-script\fR \s-1SCRIPT\s0 (see ""script"" below)" 4
.el .IP "\fB\-\-script\fR \s-1SCRIPT\s0 (see \f(CWscript\fR below)" 4
.IX Item "--script SCRIPT (see script below)"
-Run the named \f(CW\*(C`SCRIPT\*(C'\fR (a shell script or program) against the guest. The
-script can be any program on the host. The script’s current directory will
-be the guest’s root directory.
+Run the named \f(CW\*(C`SCRIPT\*(C'\fR (a shell script or program) against the guest. The script can be any program on the host. The script’s current directory will be the guest’s root directory.
.Sp
-\&\fBNote:\fR If the script is not on the \f(CW$PATH\fR, then you must give the full
-absolute path to the script.
+\&\fBNote:\fR If the script is not on the \f(CW$PATH\fR, then you must give the full absolute path to the script.
.ie n .IP "\fB\-\-scriptdir\fR \s-1SCRIPTDIR\s0 (see ""script"" below)" 4
.el .IP "\fB\-\-scriptdir\fR \s-1SCRIPTDIR\s0 (see \f(CWscript\fR below)" 4
.IX Item "--scriptdir SCRIPTDIR (see script below)"
-The mount point (an empty directory on the host) used when the \f(CW\*(C`script\*(C'\fR
-operation is enabled and one or more scripts are specified using \fI\-\-script\fR
-parameter(s).
+The mount point (an empty directory on the host) used when the \f(CW\*(C`script\*(C'\fR operation is enabled and one or more scripts are specified using \fI\-\-script\fR parameter(s).
.Sp
\&\fBNote:\fR \f(CW\*(C`SCRIPTDIR\*(C'\fR \fBmust\fR be an absolute path.
.Sp
-If \fI\-\-scriptdir\fR is not specified then a temporary mountpoint will be
-created.
+If \fI\-\-scriptdir\fR is not specified then a temporary mountpoint will be created.
.ie n .IP "\fB\-\-scrub\fR \s-1FILE\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-scrub\fR \s-1FILE\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--scrub FILE (see customize below)"
.IX Item "--selinux-relabel (see customize below)"
Relabel files in the guest so that they have the correct SELinux label.
.Sp
-This will attempt to relabel files immediately, but if the operation fails
-this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel
-operation for the next time the image boots.
+This will attempt to relabel files immediately, but if the operation fails this will instead touch \fI/.autorelabel\fR on the image to schedule a relabel operation for the next time the image boots.
.Sp
You should only use this option for guests which support SELinux.
.ie n .IP "\fB\-\-sm\-attach\fR \s-1SELECTOR\s0 (see ""customize"" below)" 4
.IX Item "--sm-attach SELECTOR (see customize below)"
Attach to a pool using \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.ie n .IP "\fB\-\-sm\-credentials\fR \s-1SELECTOR\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-sm\-credentials\fR \s-1SELECTOR\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--sm-credentials SELECTOR (see customize below)"
Set the credentials for \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the
-\&\f(CW\*(C`SELECTOR\*(C'\fR field.
+See \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.ie n .IP "\fB\-\-sm\-register\fR (see ""customize"" below)" 4
.el .IP "\fB\-\-sm\-register\fR (see \f(CWcustomize\fR below)" 4
.IX Item "--sm-register (see customize below)"
.ie n .IP "\fB\-\-ssh\-inject\fR USER[:SELECTOR] (see ""customize"" below)" 4
.el .IP "\fB\-\-ssh\-inject\fR USER[:SELECTOR] (see \f(CWcustomize\fR below)" 4
.IX Item "--ssh-inject USER[:SELECTOR] (see customize below)"
-Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh
-without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
+Inject an ssh key so the given \f(CW\*(C`USER\*(C'\fR will be able to log in over ssh without supplying a password. The \f(CW\*(C`USER\*(C'\fR must exist already in the guest.
.Sp
See \*(L"\s-1SSH KEYS\*(R"\s0 in \fBvirt\-builder\fR\|(1) for the format of the \f(CW\*(C`SELECTOR\*(C'\fR field.
.Sp
-You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also
-for more keys for each user.
+You can have multiple \fI\-\-ssh\-inject\fR options, for different users and also for more keys for each user.
.ie n .IP "\fB\-\-timezone\fR \s-1TIMEZONE\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-timezone\fR \s-1TIMEZONE\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--timezone TIMEZONE (see customize below)"
-Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string
-like \f(CW\*(C`Europe/London\*(C'\fR
+Set the default timezone of the guest to \f(CW\*(C`TIMEZONE\*(C'\fR. Use a location string like \f(CW\*(C`Europe/London\*(C'\fR
.ie n .IP "\fB\-\-touch\fR \s-1FILE\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-touch\fR \s-1FILE\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--touch FILE (see customize below)"
.ie n .IP "\fB\-\-truncate\fR \s-1FILE\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-truncate\fR \s-1FILE\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--truncate FILE (see customize below)"
-This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist
-already.
+This command truncates \f(CW\*(C`FILE\*(C'\fR to a zero-length file. The file must exist already.
.ie n .IP "\fB\-\-truncate\-recursive\fR \s-1PATH\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-truncate\-recursive\fR \s-1PATH\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--truncate-recursive PATH (see customize below)"
.ie n .IP "\fB\-\-uninstall\fR \s-1PKG,PKG..\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-uninstall\fR \s-1PKG,PKG..\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--uninstall PKG,PKG.. (see customize below)"
-Uninstall the named packages (a comma-separated list). These are removed
-during the image build using the guest’s package manager (eg. apt, yum,
-etc.). Dependent packages may also need to be uninstalled to satisfy the
-request.
+Uninstall the named packages (a comma-separated list). These are removed during the image build using the guest’s package manager (eg. apt, yum, etc.). Dependent packages may also need to be uninstalled to satisfy the request.
.Sp
See also \fI\-\-install\fR, \fI\-\-update\fR.
.ie n .IP "\fB\-\-update\fR (see ""customize"" below)" 4
.el .IP "\fB\-\-update\fR (see \f(CWcustomize\fR below)" 4
.IX Item "--update (see customize below)"
-Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command
-is required to update the packages already installed in the template to
-their latest versions.
+Do the equivalent of \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR, or whatever command is required to update the packages already installed in the template to their latest versions.
.Sp
See also \fI\-\-install\fR, \fI\-\-uninstall\fR.
.ie n .IP "\fB\-\-upload\fR \s-1FILE:DEST\s0 (see ""customize"" below)" 4
.el .IP "\fB\-\-upload\fR \s-1FILE:DEST\s0 (see \f(CWcustomize\fR below)" 4
.IX Item "--upload FILE:DEST (see customize below)"
-Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File
-owner and permissions from the original are preserved, so you should set
-them to what you want them to be in the disk image.
+Upload local file \f(CW\*(C`FILE\*(C'\fR to destination \f(CW\*(C`DEST\*(C'\fR in the disk image. File owner and permissions from the original are preserved, so you should set them to what you want them to be in the disk image.
.Sp
-\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on
-upload.
+\&\f(CW\*(C`DEST\*(C'\fR could be the final filename. This can be used to rename the file on upload.
.Sp
-If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then
-the file is uploaded into that directory, and it keeps the same name as on
-the local filesystem.
+If \f(CW\*(C`DEST\*(C'\fR is a directory name (which must already exist in the guest) then the file is uploaded into that directory, and it keeps the same name as on the local filesystem.
.Sp
See also: \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.ie n .IP "\fB\-\-write\fR \s-1FILE:CONTENT\s0 (see ""customize"" below)" 4
Write \f(CW\*(C`CONTENT\*(C'\fR to \f(CW\*(C`FILE\*(C'\fR.
.SH "OPERATIONS"
.IX Header "OPERATIONS"
-If the \fI\-\-enable\fR/\fI\-\-operations\fR option is \fInot\fR given, then most sysprep
-operations are enabled.
+If the \fI\-\-enable\fR/\fI\-\-operations\fR option is \fInot\fR given, then most sysprep operations are enabled.
.PP
-Use \f(CW\*(C`virt\-sysprep \-\-list\-operations\*(C'\fR to list all operations for your
-virt-sysprep binary. The ones which are enabled by default are marked with
-a \f(CW\*(C`*\*(C'\fR character. Regardless of the \fI\-\-enable\fR/\fI\-\-operations\fR options,
-sysprep operations are skipped for some guest types.
+Use \f(CW\*(C`virt\-sysprep \-\-list\-operations\*(C'\fR to list all operations for your virt-sysprep binary. The ones which are enabled by default are marked with a \f(CW\*(C`*\*(C'\fR character. Regardless of the \fI\-\-enable\fR/\fI\-\-operations\fR options, sysprep operations are skipped for some guest types.
.PP
-Operations can be individually enabled using the \fI\-\-enable\fR/\fI\-\-operations\fR
-options. Use a comma-separated list, for example:
+Operations can be individually enabled using the \fI\-\-enable\fR/\fI\-\-operations\fR options. Use a comma-separated list, for example:
.PP
.Vb 1
\& virt\-sysprep \-\-operations ssh\-hostkeys,udev\-persistent\-net [etc..]
.Ve
.PP
-Future versions of virt-sysprep may add more operations. If you are using
-virt-sysprep and want predictable behaviour, specify only the operations
-that you want to have enabled.
+Future versions of virt-sysprep may add more operations. If you are using virt-sysprep and want predictable behaviour, specify only the operations that you want to have enabled.
.PP
-\&\f(CW\*(C`*\*(C'\fR = enabled by default when no \fI\-\-enable\fR/\fI\-\-operations\fR option is
-given.
+\&\f(CW\*(C`*\*(C'\fR = enabled by default when no \fI\-\-enable\fR/\fI\-\-operations\fR option is given.
.SS "\fBabrt-data\fP *"
.IX Subsection "abrt-data *"
\&\s-1ABRT\s0 により生成されたクラッシュデータを削除します。
.IP "·" 4
*~
.PP
-On Linux and Unix operating systems, only the following filesystems will be
-examined:
+On Linux and Unix operating systems, only the following filesystems will be examined:
.IP "·" 4
/etc
.IP "·" 4
.IX Subsection "bash-history *"
仮想マシンにおいて bash 履歴を削除します。
.PP
-ユーザー \*(L"root\*(R" および他のあらゆるユーザーのホームディレクトリーに \f(CW\*(C`.bash_history\*(C'\fR ファイルを持つユーザーの bash
-履歴を削除します。
+ユーザー \*(L"root\*(R" および他のあらゆるユーザーのホームディレクトリーに \f(CW\*(C`.bash_history\*(C'\fR ファイルを持つユーザーの bash 履歴を削除します。
.PP
\fINotes on bash-history\fR
.IX Subsection "Notes on bash-history"
.PP
-Currently this only looks in \f(CW\*(C`/root\*(C'\fR and \f(CW\*(C`/home/*\*(C'\fR for home directories,
-so users with home directories in other locations won't have the bash
-history removed.
+Currently this only looks in \f(CW\*(C`/root\*(C'\fR and \f(CW\*(C`/home/*\*(C'\fR for home directories, so users with home directories in other locations won't have the bash history removed.
.SS "\fBblkid-tab\fP *"
.IX Subsection "blkid-tab *"
ゲストにある blkid テーブルを削除します。
.IX Subsection "customize *"
Customize the guest.
.PP
-Customize the guest by providing \fBvirt\-customize\fR\|(1) options for installing
-packages, editing files and so on.
+Customize the guest by providing \fBvirt\-customize\fR\|(1) options for installing packages, editing files and so on.
.SS "\fBdhcp-client-state\fP *"
.IX Subsection "dhcp-client-state *"
\&\s-1DHCP\s0 クライアントのリースを削除します。
.IX Subsection "firewall-rules"
ファイアウォールルールを削除します。
.PP
-This removes custom firewall rules by removing \f(CW\*(C`/etc/sysconfig/iptables\*(C'\fR or
-custom firewalld configuration in \f(CW\*(C`/etc/firewalld/*/*\*(C'\fR.
+This removes custom firewall rules by removing \f(CW\*(C`/etc/sysconfig/iptables\*(C'\fR or custom firewalld configuration in \f(CW\*(C`/etc/firewalld/*/*\*(C'\fR.
.PP
-Note this is \fInot\fR enabled by default since it may expose guests to
-exploits. Use with care.
+Note this is \fInot\fR enabled by default since it may expose guests to exploits. Use with care.
.SS "\fBflag-reconfiguration\fP"
.IX Subsection "flag-reconfiguration"
Flag the system for reconfiguration.
.PP
-For Linux guests, this touches \f(CW\*(C`/.unconfigured\*(C'\fR, which causes the first
-boot to interactively query the user for settings such as the root password
-and timezone.
+For Linux guests, this touches \f(CW\*(C`/.unconfigured\*(C'\fR, which causes the first boot to interactively query the user for settings such as the root password and timezone.
.SS "\fBfs-uuids\fP"
.IX Subsection "fs-uuids"
Change filesystem UUIDs.
.PP
-On guests and filesystem types where this is supported, new random UUIDs are
-generated and assigned to filesystems.
+On guests and filesystem types where this is supported, new random UUIDs are generated and assigned to filesystems.
.PP
\fINotes on fs-uuids\fR
.IX Subsection "Notes on fs-uuids"
.PP
-The fs-uuids operation is disabled by default because it does not yet find
-and update all the places in the guest that use the UUIDs. For example
-\&\f(CW\*(C`/etc/fstab\*(C'\fR or the bootloader. Enabling this operation is more likely
-than not to make your guest unbootable.
+The fs-uuids operation is disabled by default because it does not yet find and update all the places in the guest that use the UUIDs. For example \f(CW\*(C`/etc/fstab\*(C'\fR or the bootloader. Enabling this operation is more likely than not to make your guest unbootable.
.PP
参照: https://bugzilla.redhat.com/show_bug.cgi?id=991641
.SS "\fBipa-client\fP *"
.IX Subsection "ipa-client *"
Remove the \s-1IPA\s0 files.
.PP
-Remove all the files related to an \s-1IPA\s0 (Identity, Policy, Audit) system.
-This effectively unenrolls the guest from an \s-1IPA\s0 server without interacting
-with it.
+Remove all the files related to an \s-1IPA\s0 (Identity, Policy, Audit) system. This effectively unenrolls the guest from an \s-1IPA\s0 server without interacting with it.
.PP
This operation does not run \f(CW\*(C`ipa\-client\*(C'\fR.
.SS "\fBkerberos-data\fP"
.IX Subsection "lvm-uuids *"
\&\s-1LVM2\s0 の \s-1PV\s0 および \s-1VG\s0 の \s-1UUID\s0 を変更します。
.PP
-\&\s-1LVM2\s0 物理ボリューム (\s-1PV\s0) またはボリュームグループ (\s-1VG\s0) を持つ Linux 仮想マシンにおいて、新しいランダムな \s-1UUID\s0
-が生成され、これらの \s-1PV\s0 や \s-1VG\s0 に割り当てられます。
+\&\s-1LVM2\s0 物理ボリューム (\s-1PV\s0) またはボリュームグループ (\s-1VG\s0) を持つ Linux 仮想マシンにおいて、新しいランダムな \s-1UUID\s0 が生成され、これらの \s-1PV\s0 や \s-1VG\s0 に割り当てられます。
.SS "\fBmachine-id\fP *"
.IX Subsection "machine-id *"
ローカルマシン \s-1ID\s0 を削除します。
.PP
-The machine \s-1ID\s0 is usually generated from a random source during system
-installation and stays constant for all subsequent boots. Optionally, for
-stateless systems it is generated during runtime at boot if it is found to
-be empty.
+The machine \s-1ID\s0 is usually generated from a random source during system installation and stays constant for all subsequent boots. Optionally, for stateless systems it is generated during runtime at boot if it is found to be empty.
.SS "\fBmail-spool\fP *"
.IX Subsection "mail-spool *"
ローカルのメールスプールのディレクトリから電子メールを削除します。
\&\s-1HWADDR\s0 (ハードコードされた \s-1MAC\s0 アドレス) 設定を削除します。
.PP
Fedora および Red Hat Enterprise Linux に対して、これは \f(CW\*(C`ifcfg\-*\*(C'\fR ファイルから削除されます。
+.SS "\fBnet-nmconn\fP *"
+.IX Subsection "net-nmconn *"
+Remove system-local NetworkManager connection profiles (keyfiles).
+.PP
+On Fedora and Red Hat Enterprise Linux, remove the \f(CW\*(C`/etc/NetworkManager/system\-connections/*.nmconnection\*(C'\fR files.
.SS "\fBpacct-log\fP *"
.IX Subsection "pacct-log *"
プロセス・アカウンティングのログファイルを削除します。
.IX Subsection "rpm-db *"
Remove host-specific \s-1RPM\s0 database files.
.PP
-Remove host-specific \s-1RPM\s0 database files and locks. \s-1RPM\s0 will recreate these
-files automatically if needed.
+Remove host-specific \s-1RPM\s0 database files and locks. \s-1RPM\s0 will recreate these files automatically if needed.
.SS "\fBsamba-db-log\fP *"
.IX Subsection "samba-db-log *"
Samba のデータベースおよびログファイルを削除します。
.IX Subsection "script *"
仮想マシンに対して任意のスクリプトを実行します。
.PP
-The \f(CW\*(C`script\*(C'\fR module lets you run arbitrary shell scripts or programs
-against the guest.
+The \f(CW\*(C`script\*(C'\fR module lets you run arbitrary shell scripts or programs against the guest.
.PP
-Note this feature requires \s-1FUSE\s0 support. You may have to enable this in
-your host, for example by adding the current user to the \f(CW\*(C`fuse\*(C'\fR group, or
-by loading a kernel module.
+Note this feature requires \s-1FUSE\s0 support. You may have to enable this in your host, for example by adding the current user to the \f(CW\*(C`fuse\*(C'\fR group, or by loading a kernel module.
.PP
-Use one or more \fI\-\-script\fR parameters to specify scripts or programs that
-will be run against the guest.
+Use one or more \fI\-\-script\fR parameters to specify scripts or programs that will be run against the guest.
.PP
-The script or program is run with its current directory being the guest’s
-root directory, so relative paths should be used. For example: \f(CW\*(C`rm
-etc/resolv.conf\*(C'\fR in the script would remove a Linux guest’s \s-1DNS\s0
-configuration file, but \f(CW\*(C`rm /etc/resolv.conf\*(C'\fR would (try to) remove the
-host’s file.
+The script or program is run with its current directory being the guest’s root directory, so relative paths should be used. For example: \f(CW\*(C`rm etc/resolv.conf\*(C'\fR in the script would remove a Linux guest’s \s-1DNS\s0 configuration file, but \f(CW\*(C`rm /etc/resolv.conf\*(C'\fR would (try to) remove the host’s file.
.PP
-Normally a temporary mount point for the guest is used, but you can choose a
-specific one by using the \fI\-\-scriptdir\fR parameter.
+Normally a temporary mount point for the guest is used, but you can choose a specific one by using the \fI\-\-scriptdir\fR parameter.
.PP
-\&\fBNote:\fR This is different from \fI\-\-firstboot\fR scripts (which run in the
-context of the guest when it is booting first time). \fI\-\-script\fR scripts
-run on the host, not in the guest.
+\&\fBNote:\fR This is different from \fI\-\-firstboot\fR scripts (which run in the context of the guest when it is booting first time). \fI\-\-script\fR scripts run on the host, not in the guest.
.SS "\fBsmolt-uuid\fP *"
.IX Subsection "smolt-uuid *"
Smolt ハードウェア \s-1UUID\s0 を削除します。
.IX Subsection "ssh-userdir *"
仮想マシンにある \*(L".ssh\*(R" ディレクトリーを削除します。
.PP
-ユーザー \*(L"root\*(R" 、およびホームディレクトリーに \f(CW\*(C`.ssh\*(C'\fR ディレクトリーがある他のすべてのユーザーの、\f(CW\*(C`.ssh\*(C'\fR
-ディレクトリーを削除します。
+ユーザー \*(L"root\*(R" 、およびホームディレクトリーに \f(CW\*(C`.ssh\*(C'\fR ディレクトリーがある他のすべてのユーザーの、\f(CW\*(C`.ssh\*(C'\fR ディレクトリーを削除します。
.PP
\fINotes on ssh-userdir\fR
.IX Subsection "Notes on ssh-userdir"
.PP
-Currently this only looks in \f(CW\*(C`/root\*(C'\fR and \f(CW\*(C`/home/*\*(C'\fR for home directories,
-so users with home directories in other locations won't have the ssh files
-removed.
+Currently this only looks in \f(CW\*(C`/root\*(C'\fR and \f(CW\*(C`/home/*\*(C'\fR for home directories, so users with home directories in other locations won't have the ssh files removed.
.SS "\fBsssd-db-log\fP *"
.IX Subsection "sssd-db-log *"
\&\s-1SSSD\s0 のデータベースとログファイルを削除します。
.IX Subsection "udev-persistent-net *"
udev persistent net ルールを削除します。
.PP
-Remove udev persistent net rules which map the guest’s existing \s-1MAC\s0 address
-to a fixed ethernet device (eg. eth0).
+Remove udev persistent net rules which map the guest’s existing \s-1MAC\s0 address to a fixed ethernet device (eg. eth0).
.PP
-仮想マシンをクローンした後、通常 \s-1MAC\s0 アドレスは変わります。古い \s-1MAC\s0 アドレスは古い名前（たとえば eth0）を占有するため、このことは新しい
-\&\s-1MAC\s0 アドレスが新しい名前（たとえば eth1）に割り当てられることを意味します。それは、一般的に好ましくありません。 udev の永続的な net
-ルールを削除することにより、これを避けます。
+仮想マシンをクローンした後、通常 \s-1MAC\s0 アドレスは変わります。古い \s-1MAC\s0 アドレスは古い名前（たとえば eth0）を占有するため、このことは新しい \s-1MAC\s0 アドレスが新しい名前（たとえば eth1）に割り当てられることを意味します。それは、一般的に好ましくありません。 udev の永続的な net ルールを削除することにより、これを避けます。
.SS "\fBuser-account\fP"
.IX Subsection "user-account"
仮想マシンにあるユーザーアカウントを削除します。
.PP
-By default remove all the user accounts and their home directories. The
-\&\*(L"root\*(R" account is not removed.
+By default remove all the user accounts and their home directories. The \*(L"root\*(R" account is not removed.
.PP
-See the \fI\-\-remove\-user\-accounts\fR parameter for a way to specify how to
-remove only some users, or to not remove some others.
+See the \fI\-\-remove\-user\-accounts\fR parameter for a way to specify how to remove only some users, or to not remove some others.
.SS "\fButmp\fP *"
.IX Subsection "utmp *"
utmp ファイルを削除します。
.PP
-This file records who is currently logged in on a machine. In modern Linux
-distros it is stored in a ramdisk and hence not part of the virtual
-machine’s disk, but it was stored on disk in older distros.
+This file records who is currently logged in on a machine. In modern Linux distros it is stored in a ramdisk and hence not part of the virtual machine’s disk, but it was stored on disk in older distros.
.SS "\fByum-uuid\fP *"
.IX Subsection "yum-uuid *"
yum \s-1UUID\s0 を削除します。
yum は元々の \s-1UUID\s0 が削除されたことを通知するとき、次の実行時に新しい \s-1UUID\s0 を作成します。
.SH "コピー方法およびクローン方法"
.IX Header "コピー方法およびクローン方法"
-virt-sysprep
-は仮想マシンをクローンするプロセスの一部として使用できます。もしくは、クローンされた仮想マシンからテンプレートを準備するために使用できます。仮想化ツールを使用してこれを実現する他の方法がいろいろとあります。このセクションは単に概要を説明します。
+virt-sysprep は仮想マシンをクローンするプロセスの一部として使用できます。もしくは、クローンされた仮想マシンからテンプレートを準備するために使用できます。仮想化ツールを使用してこれを実現する他の方法がいろいろとあります。このセクションは単に概要を説明します。
.PP
仮想マシン（停止状態の場合）は 2 つの部分からなります:
.IP "\fIconfiguration\fR" 4
.IX Item "configuration"
-仮想マシンの設定または説明。 例: libvirt \s-1XML\s0 (\f(CW\*(C`virsh dumpxml\*(C'\fR 参照) 、仮想マシンの実行中の設定、または \s-1OVF\s0
-のような他の外部形式。
+仮想マシンの設定または説明。 例: libvirt \s-1XML\s0 (\f(CW\*(C`virsh dumpxml\*(C'\fR 参照) 、仮想マシンの実行中の設定、または \s-1OVF\s0 のような他の外部形式。
.Sp
いくつかの設定項目は変更する必要があるかもしれません:
.RS 4
.RE
.IP "\fIブロックデバイス\fR" 4
.IX Item "ブロックデバイス"
-One or more hard disk images, themselves containing files, directories,
-applications, kernels, configuration, etc.
+One or more hard disk images, themselves containing files, directories, applications, kernels, configuration, etc.
.Sp
Some things inside the block devices that might need to be changed:
.RS 4
.RE
.SS "ブロックデバイスのコピー法"
.IX Subsection "ブロックデバイスのコピー法"
-Starting with an original guest, you probably wish to copy the guest block
-device and its configuration to make a template. Then once you are happy
-with the template, you will want to make many clones from it.
+Starting with an original guest, you probably wish to copy the guest block device and its configuration to make a template. Then once you are happy with the template, you will want to make many clones from it.
.PP
.Vb 7
\& virt\-sysprep
\& \e\-\-\-\->
.Ve
.PP
-You may want to run virt-sysprep twice, once to reset the guest (to make a
-template) and a second time to customize the guest for a specific user:
+You may want to run virt-sysprep twice, once to reset the guest (to make a template) and a second time to customize the guest for a specific user:
.PP
.Vb 6
\& virt\-sysprep virt\-sysprep
\& qemu\-img create \-f qcow2 \-o backing_file=original snapshot.qcow
.Ve
.Sp
-The advantage is that you don’t need to copy the original (very fast) and
-only changes are stored (less storage required).
+The advantage is that you don’t need to copy the original (very fast) and only changes are stored (less storage required).
.Sp
-Note that writing to the backing file once you have created guests on top of
-it is not possible: you will corrupt the guests.
+Note that writing to the backing file once you have created guests on top of it is not possible: you will corrupt the guests.
.IP "\(bu" 4
\&\f(CW\*(C`lvcreate \-\-snapshot\*(C'\fR を使用してスナップショットを作成します。
.IP "\(bu" 4
-Other ways to create snapshots include using filesystems-level tools (for
-filesystems such as btrfs).
+Other ways to create snapshots include using filesystems-level tools (for filesystems such as btrfs).
.Sp
-Most Network Attached Storage (\s-1NAS\s0) devices can also create cheap snapshots
-from files or LUNs.
+Most Network Attached Storage (\s-1NAS\s0) devices can also create cheap snapshots from files or LUNs.
.IP "\(bu" 4
-Get your \s-1NAS\s0 to duplicate the \s-1LUN.\s0 Most \s-1NAS\s0 devices can also duplicate LUNs
-very cheaply (they copy them on-demand in the background).
+Get your \s-1NAS\s0 to duplicate the \s-1LUN.\s0 Most \s-1NAS\s0 devices can also duplicate LUNs very cheaply (they copy them on-demand in the background).
.IP "\(bu" 4
\&\fBvirt\-sparsify\fR\|(1) を使用してテンプレートを準備します。以下を参照してください。
.SS "virt-clone"
.IX Subsection "virt-clone"
-A separate tool, \fBvirt\-clone\fR\|(1), can be used to duplicate the block device
-and/or modify the external libvirt configuration of a guest. It will reset
-the name, \s-1UUID\s0 and \s-1MAC\s0 address of the guest in the libvirt \s-1XML.\s0
+A separate tool, \fBvirt\-clone\fR\|(1), can be used to duplicate the block device and/or modify the external libvirt configuration of a guest. It will reset the name, \s-1UUID\s0 and \s-1MAC\s0 address of the guest in the libvirt \s-1XML.\s0
.PP
-\&\fBvirt\-clone\fR\|(1) does not use libguestfs and cannot look inside the disk
-image. This was the original motivation to write virt-sysprep.
+\&\fBvirt\-clone\fR\|(1) does not use libguestfs and cannot look inside the disk image. This was the original motivation to write virt-sysprep.
.SS "スパース化"
.IX Subsection "スパース化"
.Vb 2
\& 元のゲスト \-\-\-\-\-\-\-\-> テンプレート
.Ve
.PP
-\&\fBvirt\-sparsify\fR\|(1) can be used to make the cloning template smaller, making
-it easier to compress and/or faster to copy.
+\&\fBvirt\-sparsify\fR\|(1) can be used to make the cloning template smaller, making it easier to compress and/or faster to copy.
.PP
-Notice that since virt-sparsify also copies the image, you can use it to
-make the initial copy (instead of \f(CW\*(C`dd\*(C'\fR).
+Notice that since virt-sparsify also copies the image, you can use it to make the initial copy (instead of \f(CW\*(C`dd\*(C'\fR).
.SS "容量変更"
.IX Subsection "容量変更"
.Vb 5
\& \e\-\-\-\->
.Ve
.PP
-If you want to give people cloned guests, but let them pick the size of the
-guest themselves (eg. depending on how much they are prepared to pay for
-disk space), then instead of copying the template, you can run
-\&\fBvirt\-resize\fR\|(1). Virt-resize performs a copy and resize, and thus is
-ideal for cloning guests from a template.
+If you want to give people cloned guests, but let them pick the size of the guest themselves (eg. depending on how much they are prepared to pay for disk space), then instead of copying the template, you can run \fBvirt\-resize\fR\|(1). Virt-resize performs a copy and resize, and thus is ideal for cloning guests from a template.
.SH "FIRSTBOOT VS SCRIPT"
.IX Header "FIRSTBOOT VS SCRIPT"
-The two options \fI\-\-firstboot\fR and \fI\-\-script\fR both supply shell scripts
-that are run against the guest. However these two options are significantly
-different.
+The two options \fI\-\-firstboot\fR and \fI\-\-script\fR both supply shell scripts that are run against the guest. However these two options are significantly different.
.PP
-\&\fI\-\-firstboot script\fR uploads the file \f(CW\*(C`script\*(C'\fR into the guest and arranges
-that it will run, in the guest, when the guest is next booted. (The script
-will only run once, at the \*(L"first boot\*(R").
+\&\fI\-\-firstboot script\fR uploads the file \f(CW\*(C`script\*(C'\fR into the guest and arranges that it will run, in the guest, when the guest is next booted. (The script will only run once, at the \*(L"first boot\*(R").
.PP
-\&\fI\-\-script script\fR runs the shell \f(CW\*(C`script\*(C'\fR \fIon the host\fR, with its current
-directory inside the guest filesystem.
+\&\fI\-\-script script\fR runs the shell \f(CW\*(C`script\*(C'\fR \fIon the host\fR, with its current directory inside the guest filesystem.
.PP
-If you needed, for example, to \f(CW\*(C`yum install\*(C'\fR new packages, then you \fImust
-not\fR use \fI\-\-script\fR for this, since that would (a) run the \f(CW\*(C`yum\*(C'\fR command
-on the host and (b) wouldn't have access to the same resources
-(repositories, keys, etc.) as the guest. Any command that needs to run on
-the guest \fImust\fR be run via \fI\-\-firstboot\fR.
+If you needed, for example, to \f(CW\*(C`yum install\*(C'\fR new packages, then you \fImust not\fR use \fI\-\-script\fR for this, since that would (a) run the \f(CW\*(C`yum\*(C'\fR command on the host and (b) wouldn't have access to the same resources (repositories, keys, etc.) as the guest. Any command that needs to run on the guest \fImust\fR be run via \fI\-\-firstboot\fR.
.PP
-On the other hand if you need to make adjustments to the guest filesystem
-(eg. copying in files), then \fI\-\-script\fR is ideal since (a) it has access
-to the host filesystem and (b) you will get immediate feedback on errors.
+On the other hand if you need to make adjustments to the guest filesystem (eg. copying in files), then \fI\-\-script\fR is ideal since (a) it has access to the host filesystem and (b) you will get immediate feedback on errors.
.PP
Either or both options can be used multiple times on the command line.
.SH "セキュリティ"
.IX Header "セキュリティ"
-Although virt-sysprep removes some sensitive information from the guest, it
-does not pretend to remove all of it. You should examine the \*(L"\s-1OPERATIONS\*(R"\s0
-above and the guest afterwards.
-.PP
-Sensitive files are simply removed. The data they contained may still exist
-on the disk, easily recovered with a hex editor or undelete tool. The
-\&\fI\-\-scrub\fR option can be used to scrub files instead of just deleting them.
-\&\fBvirt\-sparsify\fR\|(1) is another way to remove this content. See also the
-\&\fBscrub\fR\|(1) command to get rid of deleted content in directory entries and
-inodes.
+Although virt-sysprep removes some sensitive information from the guest, it does not pretend to remove all of it. You should examine the \*(L"\s-1OPERATIONS\*(R"\s0 above and the guest afterwards.
+.PP
+Sensitive files are simply removed. The data they contained may still exist on the disk, easily recovered with a hex editor or undelete tool. The \fI\-\-scrub\fR option can be used to scrub files instead of just deleting them. \fBvirt\-sparsify\fR\|(1) is another way to remove this content. See also the \fBscrub\fR\|(1) command to get rid of deleted content in directory entries and inodes.
.SS "乱数の種"
.IX Subsection "乱数の種"
\&\fI(このセクションは Linux 仮想マシンのみに適用します)\fR
.PP
-For supported guests, virt-sysprep writes a few bytes of randomness from the
-host into the guest’s random seed file.
+For supported guests, virt-sysprep writes a few bytes of randomness from the host into the guest’s random seed file.
.PP
-If this is just done once and the guest is cloned from the same template,
-then each guest will start with the same entropy, and things like \s-1SSH\s0 host
-keys and \s-1TCP\s0 sequence numbers may be predictable.
+If this is just done once and the guest is cloned from the same template, then each guest will start with the same entropy, and things like \s-1SSH\s0 host keys and \s-1TCP\s0 sequence numbers may be predictable.
.PP
-Therefore you should arrange to add more randomness \fIafter\fR cloning from a
-template too, which can be done by enabling just the customize module:
+Therefore you should arrange to add more randomness \fIafter\fR cloning from a template too, which can be done by enabling just the customize module:
.PP
.Vb 2
\& cp template.img newguest.img
.Ve
.SH "SELinux"
.IX Header "SELinux"
-For guests which make use of SELinux, special handling for them might be
-needed when using operations which create new files or alter existing ones.
+For guests which make use of SELinux, special handling for them might be needed when using operations which create new files or alter existing ones.
.PP
For further details, see \*(L"\s-1SELINUX\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.SH "WINDOWS 8"
.IX Header "WINDOWS 8"
-Windows 8 \*(L"fast startup\*(R" can prevent virt-sysprep from working. See
-\&\*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
+Windows 8 \*(L"fast startup\*(R" can prevent virt-sysprep from working. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "終了ステータス"
.IX Header "終了ステータス"
このプログラムは、成功すると 0 を返します。または、エラーが起きると 1 を返します。
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
.Sp
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like \fI/usr/share/virt\-tools\fR).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like \fI/usr/share/virt\-tools\fR).
.Sp
This directory may contain the following files:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in
-Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or
-\&\fI\-\-firstboot\-command\fR options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.Sp
See also: \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a
-\&\*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use
-the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
+This is a Windows binary shipped with \s-1SUSE VMDP,\s0 used to install a \*(L"firstboot\*(R" script in Windows guests. It is required if you intend to use the \fI\-\-firstboot\fR or \fI\-\-firstboot\-command\fR options with Windows guests.
.RE
.RS 4
.RE
他の環境変数は \*(L"環境変数\*(R" in \fBguestfs\fR\|(3) を参照してください。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1),
-\&\fBvirt\-customize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1),
-\&\fBvirt\-sparsify\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1),
-\&\fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1), \fBvirt\-customize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1), \fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 説明
-Virt-sysprep can reset or unconfigure a virtual machine so that clones can
-be made from it. Steps in this process include removing SSH host keys,
-removing persistent network MAC configuration, and removing user accounts.
-Virt-sysprep can also customize a virtual machine, for instance by adding
-SSH keys, users or logos. Each step can be enabled or disabled as required.
-
-Virt-sysprep modifies the guest or disk image I<in place>. The guest must
-be shut down. If you want to preserve the existing contents of the guest,
-I<you must snapshot, copy or clone the disk first>. See L</COPYING AND
-CLONING> below.
-
-You do I<not> need to run virt-sysprep as root. In fact we'd generally
-recommend that you don't. The time you might want to run it as root is when
-you need root in order to access the disk image, but even in this case it
-would be better to change the permissions on the disk image to be writable
-as the non-root user running virt-sysprep.
-
-"Sysprep" stands for "system preparation" tool. The name comes from the
-Microsoft program F<sysprep.exe> which is used to unconfigure Windows
-machines in preparation for cloning them. Having said that, virt-sysprep
-does I<not> currently work on Microsoft Windows guests. We plan to support
-Windows sysprepping in a future version, and we already have code to do it.
+Virt-sysprep can reset or unconfigure a virtual machine so that clones can be made from it. Steps in this process include removing SSH host keys, removing persistent network MAC configuration, and removing user accounts. Virt-sysprep can also customize a virtual machine, for instance by adding SSH keys, users or logos. Each step can be enabled or disabled as required.
+
+Virt-sysprep modifies the guest or disk image I<in place>. The guest must be shut down. If you want to preserve the existing contents of the guest, I<you must snapshot, copy or clone the disk first>. See L</COPYING AND CLONING> below.
+
+You do I<not> need to run virt-sysprep as root. In fact we'd generally recommend that you don't. The time you might want to run it as root is when you need root in order to access the disk image, but even in this case it would be better to change the permissions on the disk image to be writable as the non-root user running virt-sysprep.
+
+"Sysprep" stands for "system preparation" tool. The name comes from the Microsoft program F<sysprep.exe> which is used to unconfigure Windows machines in preparation for cloning them. Having said that, virt-sysprep does I<not> currently work on Microsoft Windows guests. We plan to support Windows sysprepping in a future version, and we already have code to do it.
=head1 オプション
=item B<--add> URI
-Add a remote disk. The URI format is compatible with guestfish. See
-L<guestfish(1)/ADDING REMOTE STORAGE>.
+Add a remote disk. The URI format is compatible with guestfish. See L<guestfish(1)/ADDING REMOTE STORAGE>.
=item B<--colors>
=item B<--colours>
-Use ANSI colour sequences to colourize messages. This is the default when
-the output is a tty. If the output of the program is redirected to a file,
-ANSI colour sequences are disabled unless you use this option.
+Use ANSI colour sequences to colourize messages. This is the default when the output is a tty. If the output of the program is redirected to a file, ANSI colour sequences are disabled unless you use this option.
=item B<-c> URI
=item B<--dry-run>
-Perform a read-only "dry run" on the guest. This runs the sysprep
-operation, but throws away any changes to the disk at the end.
+Perform a read-only "dry run" on the guest. This runs the sysprep operation, but throws away any changes to the disk at the end.
=item B<--enable> operations
-Choose which sysprep operations to perform. Give a comma-separated list of
-operations, for example:
+Choose which sysprep operations to perform. Give a comma-separated list of operations, for example:
--enable ssh-hostkeys,udev-persistent-net
would enable ONLY C<ssh-hostkeys> and C<udev-persistent-net> operations.
-If the I<--enable> option is not given, then we default to trying most
-sysprep operations (see I<--list-operations> to show which are enabled).
+If the I<--enable> option is not given, then we default to trying most sysprep operations (see I<--list-operations> to show which are enabled).
-Regardless of the I<--enable> option, sysprep operations are skipped for
-some guest types.
+Regardless of the I<--enable> option, sysprep operations are skipped for some guest types.
特定のバージョンの virt-sysprep によりサポートされる操作の一覧を表示するには I<--list-operations> を使用します。
=item B<--operations> operations
-Choose which sysprep operations to perform. Give a comma-separated list of
-operations, for example:
+Choose which sysprep operations to perform. Give a comma-separated list of operations, for example:
--operations ssh-hostkeys,udev-persistent-net
would enable ONLY C<ssh-hostkeys> and C<udev-persistent-net> operations.
-I<--operations> allows you to enable and disable any operation, including
-the default ones (which would be tried when specifying neither
-I<--operations> nor I<--enable>) and all the available ones; prepending a
-C<-> in front of an operation name removes it from the list of enabled
-operations, while the meta-names C<defaults> and C<all> represent
-respectively the operations enabled by default and all the available ones.
-For example:
+I<--operations> allows you to enable and disable any operation, including the default ones (which would be tried when specifying neither I<--operations> nor I<--enable>) and all the available ones; prepending a C<-> in front of an operation name removes it from the list of enabled operations, while the meta-names C<defaults> and C<all> represent respectively the operations enabled by default and all the available ones. For example:
--operations firewall-rules,defaults,-tmp-files
-would enable the C<firewall-rules> operation (regardless whether it is
-enabled by default), all the default ones, and disable the C<tmp-files>
-operation.
+would enable the C<firewall-rules> operation (regardless whether it is enabled by default), all the default ones, and disable the C<tmp-files> operation.
-I<--operations> can be specified multiple times; the first time the set of
-enabled operations is empty, while any further I<--operations> affects the
-operations enabled so far.
+I<--operations> can be specified multiple times; the first time the set of enabled operations is empty, while any further I<--operations> affects the operations enabled so far.
-If the I<--operations> option is not given, then we default to trying most
-sysprep operations (see I<--list-operations> to show which are enabled).
+If the I<--operations> option is not given, then we default to trying most sysprep operations (see I<--list-operations> to show which are enabled).
-Regardless of the I<--operations> option, sysprep operations are skipped for
-some guest types.
+Regardless of the I<--operations> option, sysprep operations are skipped for some guest types.
特定のバージョンの virt-sysprep によりサポートされる操作の一覧を表示するには I<--list-operations> を使用します。
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-sysprep normally turns echoing
-off so you cannot see what you are typing. If you are not worried about
-Tempest attacks and there is no one else in the room you can specify this
-flag to see what you are typing.
+When prompting for keys and passphrases, virt-sysprep normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-The default for the I<-a> option is to auto-detect the format of the disk
-image. Using this forces the disk format for I<-a> options which follow on
-the command line. Using I<--format auto> switches back to auto-detection
-for subsequent I<-a> options.
+The default for the I<-a> option is to auto-detect the format of the disk image. Using this forces the disk format for I<-a> options which follow on the command line. Using I<--format auto> switches back to auto-detection for subsequent I<-a> options.
例:
virt-sysprep --format raw -a disk.img --format auto -a another.img
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
virt-sysprep プログラムによりサポートされる操作を一覧表示します。
-These are listed one per line, with one or more single-space-separated
-fields, eg:
+These are listed one per line, with one or more single-space-separated fields, eg:
$ virt-sysprep --list-operations
bash-history * Remove the bash history in the guest
dhcp-server-state * Remove DHCP server leases
[etc]
-The first field is the operation name, which can be supplied to
-I<--enable>. The second field is a C<*> character if the operation is
-enabled by default or blank if not. Subsequent fields on the same line are
-the description of the operation.
+The first field is the operation name, which can be supplied to I<--enable>. The second field is a C<*> character if the operation is enabled by default or blank if not. Subsequent fields on the same line are the description of the operation.
-Before libguestfs 1.17.33 only the first (operation name) field was shown
-and all operations were enabled by default.
+Before libguestfs 1.17.33 only the first (operation name) field was shown and all operations were enabled by default.
=item B<--mount-options> mp:opts[;mp:opts;...]
-Set the mount options used when libguestfs opens the disk image. Note this
-has no effect on the guest. It is used when opening certain guests such as
-ones using the UFS (BSD) filesystem.
+Set the mount options used when libguestfs opens the disk image. Note this has no effect on the guest. It is used when opening certain guests such as ones using the UFS (BSD) filesystem.
-Use a semicolon-separated list of C<mountpoint:options> pairs. You may need
-to quote this list to protect it from the shell.
+Use a semicolon-separated list of C<mountpoint:options> pairs. You may need to quote this list to protect it from the shell.
例:
Enable or disable network access from the guest during the installation.
-In virt-sysprep, the network is I<disabled> by default. You must use
-I<--network> to enable it, in order that options such as I<--install> or
-I<--update> will work.
+In virt-sysprep, the network is I<disabled> by default. You must use I<--network> to enable it, in order that options such as I<--install> or I<--update> will work.
-L<virt-builder(1)> has more information about the security advantages of
-disabling the network.
+L<virt-builder(1)> has more information about the security advantages of disabling the network.
=item B<-v>
バージョン番号を表示して、終了します。
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
libguestfs API 呼び出しのトレースを有効にします。
=head1 OPERATIONS
-If the I<--enable>/I<--operations> option is I<not> given, then most sysprep
-operations are enabled.
+If the I<--enable>/I<--operations> option is I<not> given, then most sysprep operations are enabled.
-Use C<virt-sysprep --list-operations> to list all operations for your
-virt-sysprep binary. The ones which are enabled by default are marked with
-a C<*> character. Regardless of the I<--enable>/I<--operations> options,
-sysprep operations are skipped for some guest types.
+Use C<virt-sysprep --list-operations> to list all operations for your virt-sysprep binary. The ones which are enabled by default are marked with a C<*> character. Regardless of the I<--enable>/I<--operations> options, sysprep operations are skipped for some guest types.
-Operations can be individually enabled using the I<--enable>/I<--operations>
-options. Use a comma-separated list, for example:
+Operations can be individually enabled using the I<--enable>/I<--operations> options. Use a comma-separated list, for example:
virt-sysprep --operations ssh-hostkeys,udev-persistent-net [etc..]
-Future versions of virt-sysprep may add more operations. If you are using
-virt-sysprep and want predictable behaviour, specify only the operations
-that you want to have enabled.
+Future versions of virt-sysprep may add more operations. If you are using virt-sysprep and want predictable behaviour, specify only the operations that you want to have enabled.
-C<*> = enabled by default when no I<--enable>/I<--operations> option is
-given.
+C<*> = enabled by default when no I<--enable>/I<--operations> option is given.
__OPERATIONS__
=head1 コピー方法およびクローン方法
-virt-sysprep
-は仮想マシンをクローンするプロセスの一部として使用できます。もしくは、クローンされた仮想マシンからテンプレートを準備するために使用できます。仮想化ツールを使用してこれを実現する他の方法がいろいろとあります。このセクションは単に概要を説明します。
+virt-sysprep は仮想マシンをクローンするプロセスの一部として使用できます。もしくは、クローンされた仮想マシンからテンプレートを準備するために使用できます。仮想化ツールを使用してこれを実現する他の方法がいろいろとあります。このセクションは単に概要を説明します。
仮想マシン（停止状態の場合）は 2 つの部分からなります:
=item I<configuration>
-仮想マシンの設定または説明。 例: libvirt XML (C<virsh dumpxml> 参照) 、仮想マシンの実行中の設定、または OVF
-のような他の外部形式。
+仮想マシンの設定または説明。 例: libvirt XML (C<virsh dumpxml> 参照) 、仮想マシンの実行中の設定、または OVF のような他の外部形式。
いくつかの設定項目は変更する必要があるかもしれません:
=item I<ブロックデバイス>
-One or more hard disk images, themselves containing files, directories,
-applications, kernels, configuration, etc.
+One or more hard disk images, themselves containing files, directories, applications, kernels, configuration, etc.
Some things inside the block devices that might need to be changed:
=head2 ブロックデバイスのコピー法
-Starting with an original guest, you probably wish to copy the guest block
-device and its configuration to make a template. Then once you are happy
-with the template, you will want to make many clones from it.
+Starting with an original guest, you probably wish to copy the guest block device and its configuration to make a template. Then once you are happy with the template, you will want to make many clones from it.
virt-sysprep
|
\-----> 済みゲスト
\---->
-You may want to run virt-sysprep twice, once to reset the guest (to make a
-template) and a second time to customize the guest for a specific user:
+You may want to run virt-sysprep twice, once to reset the guest (to make a template) and a second time to customize the guest for a specific user:
virt-sysprep virt-sysprep
(リセット) (ユーザー、キー、ロゴの追加)
qemu-img create -f qcow2 -o backing_file=original snapshot.qcow
-The advantage is that you don’t need to copy the original (very fast) and
-only changes are stored (less storage required).
+The advantage is that you don’t need to copy the original (very fast) and only changes are stored (less storage required).
-Note that writing to the backing file once you have created guests on top of
-it is not possible: you will corrupt the guests.
+Note that writing to the backing file once you have created guests on top of it is not possible: you will corrupt the guests.
=item *
=item *
-Other ways to create snapshots include using filesystems-level tools (for
-filesystems such as btrfs).
+Other ways to create snapshots include using filesystems-level tools (for filesystems such as btrfs).
-Most Network Attached Storage (NAS) devices can also create cheap snapshots
-from files or LUNs.
+Most Network Attached Storage (NAS) devices can also create cheap snapshots from files or LUNs.
=item *
-Get your NAS to duplicate the LUN. Most NAS devices can also duplicate LUNs
-very cheaply (they copy them on-demand in the background).
+Get your NAS to duplicate the LUN. Most NAS devices can also duplicate LUNs very cheaply (they copy them on-demand in the background).
=item *
=head2 virt-clone
-A separate tool, L<virt-clone(1)>, can be used to duplicate the block device
-and/or modify the external libvirt configuration of a guest. It will reset
-the name, UUID and MAC address of the guest in the libvirt XML.
+A separate tool, L<virt-clone(1)>, can be used to duplicate the block device and/or modify the external libvirt configuration of a guest. It will reset the name, UUID and MAC address of the guest in the libvirt XML.
-L<virt-clone(1)> does not use libguestfs and cannot look inside the disk
-image. This was the original motivation to write virt-sysprep.
+L<virt-clone(1)> does not use libguestfs and cannot look inside the disk image. This was the original motivation to write virt-sysprep.
=head2 スパース化
virt-sparsify
元のゲスト --------> テンプレート
-L<virt-sparsify(1)> can be used to make the cloning template smaller, making
-it easier to compress and/or faster to copy.
+L<virt-sparsify(1)> can be used to make the cloning template smaller, making it easier to compress and/or faster to copy.
-Notice that since virt-sparsify also copies the image, you can use it to
-make the initial copy (instead of C<dd>).
+Notice that since virt-sparsify also copies the image, you can use it to make the initial copy (instead of C<dd>).
=head2 容量変更
\-----> 済みゲスト
\---->
-If you want to give people cloned guests, but let them pick the size of the
-guest themselves (eg. depending on how much they are prepared to pay for
-disk space), then instead of copying the template, you can run
-L<virt-resize(1)>. Virt-resize performs a copy and resize, and thus is
-ideal for cloning guests from a template.
+If you want to give people cloned guests, but let them pick the size of the guest themselves (eg. depending on how much they are prepared to pay for disk space), then instead of copying the template, you can run L<virt-resize(1)>. Virt-resize performs a copy and resize, and thus is ideal for cloning guests from a template.
=head1 FIRSTBOOT VS SCRIPT
-The two options I<--firstboot> and I<--script> both supply shell scripts
-that are run against the guest. However these two options are significantly
-different.
+The two options I<--firstboot> and I<--script> both supply shell scripts that are run against the guest. However these two options are significantly different.
-I<--firstboot script> uploads the file C<script> into the guest and arranges
-that it will run, in the guest, when the guest is next booted. (The script
-will only run once, at the "first boot").
+I<--firstboot script> uploads the file C<script> into the guest and arranges that it will run, in the guest, when the guest is next booted. (The script will only run once, at the "first boot").
-I<--script script> runs the shell C<script> I<on the host>, with its current
-directory inside the guest filesystem.
+I<--script script> runs the shell C<script> I<on the host>, with its current directory inside the guest filesystem.
-If you needed, for example, to C<yum install> new packages, then you I<must
-not> use I<--script> for this, since that would (a) run the C<yum> command
-on the host and (b) wouldn't have access to the same resources
-(repositories, keys, etc.) as the guest. Any command that needs to run on
-the guest I<must> be run via I<--firstboot>.
+If you needed, for example, to C<yum install> new packages, then you I<must not> use I<--script> for this, since that would (a) run the C<yum> command on the host and (b) wouldn't have access to the same resources (repositories, keys, etc.) as the guest. Any command that needs to run on the guest I<must> be run via I<--firstboot>.
-On the other hand if you need to make adjustments to the guest filesystem
-(eg. copying in files), then I<--script> is ideal since (a) it has access
-to the host filesystem and (b) you will get immediate feedback on errors.
+On the other hand if you need to make adjustments to the guest filesystem (eg. copying in files), then I<--script> is ideal since (a) it has access to the host filesystem and (b) you will get immediate feedback on errors.
Either or both options can be used multiple times on the command line.
=head1 セキュリティ
-Although virt-sysprep removes some sensitive information from the guest, it
-does not pretend to remove all of it. You should examine the L</OPERATIONS>
-above and the guest afterwards.
+Although virt-sysprep removes some sensitive information from the guest, it does not pretend to remove all of it. You should examine the L</OPERATIONS> above and the guest afterwards.
-Sensitive files are simply removed. The data they contained may still exist
-on the disk, easily recovered with a hex editor or undelete tool. The
-I<--scrub> option can be used to scrub files instead of just deleting them.
-L<virt-sparsify(1)> is another way to remove this content. See also the
-L<scrub(1)> command to get rid of deleted content in directory entries and
-inodes.
+Sensitive files are simply removed. The data they contained may still exist on the disk, easily recovered with a hex editor or undelete tool. The I<--scrub> option can be used to scrub files instead of just deleting them. L<virt-sparsify(1)> is another way to remove this content. See also the L<scrub(1)> command to get rid of deleted content in directory entries and inodes.
=head2 乱数の種
I<(このセクションは Linux 仮想マシンのみに適用します)>
-For supported guests, virt-sysprep writes a few bytes of randomness from the
-host into the guest’s random seed file.
+For supported guests, virt-sysprep writes a few bytes of randomness from the host into the guest’s random seed file.
-If this is just done once and the guest is cloned from the same template,
-then each guest will start with the same entropy, and things like SSH host
-keys and TCP sequence numbers may be predictable.
+If this is just done once and the guest is cloned from the same template, then each guest will start with the same entropy, and things like SSH host keys and TCP sequence numbers may be predictable.
-Therefore you should arrange to add more randomness I<after> cloning from a
-template too, which can be done by enabling just the customize module:
+Therefore you should arrange to add more randomness I<after> cloning from a template too, which can be done by enabling just the customize module:
cp template.img newguest.img
virt-sysprep --enable customize -a newguest.img
=head1 SELinux
-For guests which make use of SELinux, special handling for them might be
-needed when using operations which create new files or alter existing ones.
+For guests which make use of SELinux, special handling for them might be needed when using operations which create new files or alter existing ones.
For further details, see L<virt-builder(1)/SELINUX>.
=head1 WINDOWS 8
-Windows 8 "fast startup" can prevent virt-sysprep from working. See
-L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
+Windows 8 "fast startup" can prevent virt-sysprep from working. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
=head1 終了ステータス
=item C<VIRT_TOOLS_DATA_DIR>
-This can point to the directory containing data files used for Windows
-firstboot installation.
+This can point to the directory containing data files used for Windows firstboot installation.
-Normally you do not need to set this. If not set, a compiled-in default
-will be used (something like F</usr/share/virt-tools>).
+Normally you do not need to set this. If not set, a compiled-in default will be used (something like F</usr/share/virt-tools>).
This directory may contain the following files:
=item F<rhsrvany.exe>
-This is the RHSrvAny Windows binary, used to install a "firstboot" script in
-Windows guests. It is required if you intend to use the I<--firstboot> or
-I<--firstboot-command> options with Windows guests.
+This is the RHSrvAny Windows binary, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
See also: C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-This is a Windows binary shipped with SUSE VMDP, used to install a
-"firstboot" script in Windows guests. It is required if you intend to use
-the I<--firstboot> or I<--firstboot-command> options with Windows guests.
+This is a Windows binary shipped with SUSE VMDP, used to install a "firstboot" script in Windows guests. It is required if you intend to use the I<--firstboot> or I<--firstboot-command> options with Windows guests.
=back
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>,
-L<virt-customize(1)>, L<virt-rescue(1)>, L<virt-resize(1)>,
-L<virt-sparsify(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>,
-L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>, L<virt-customize(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>, L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
=head1 著者
=head1 説明
-C<virt-tail> is a command line tool to follow (tail) the contents of C<file>
-where C<file> exists in the named virtual machine (or disk image). It is
-similar to the ordinary command S<C<tail -f>>.
+C<virt-tail> is a command line tool to follow (tail) the contents of C<file> where C<file> exists in the named virtual machine (or disk image). It is similar to the ordinary command S<C<tail -f>>.
-Multiple filenames can be given, in which case each is followed separately.
-Each filename must be a full path, starting at the root directory (starting
-with '/').
+Multiple filenames can be given, in which case each is followed separately. Each filename must be a full path, starting at the root directory (starting with '/').
The command keeps running until:
=item B<--add> file
-Add I<file> which should be a disk image from a virtual machine. If the
-virtual machine has multiple block devices, you must supply all of them with
-separate I<-a> options.
+Add I<file> which should be a disk image from a virtual machine. If the virtual machine has multiple block devices, you must supply all of them with separate I<-a> options.
ディスクイメージの形式は自動検知されます。 これを上書きして強制的に特定の形式を使用する場合、 I<--format=..> オプションを使用します。
=item B<--echo-keys>
-When prompting for keys and passphrases, virt-tail normally turns echoing
-off so you cannot see what you are typing. If you are not worried about
-Tempest attacks and there is no one else in the room you can specify this
-flag to see what you are typing.
+When prompting for keys and passphrases, virt-tail normally turns echoing off so you cannot see what you are typing. If you are not worried about Tempest attacks and there is no one else in the room you can specify this flag to see what you are typing.
=item B<-f>
=item B<--follow>
-This option is ignored. virt-tail always behaves like S<L<tail(1)> I<-f>>.
-You don't need to specify the I<-f> option.
+This option is ignored. virt-tail always behaves like S<L<tail(1)> I<-f>>. You don't need to specify the I<-f> option.
=item B<--format=raw|qcow2|..>
=item B<--format>
-I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a>
-オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a>
-オプションに対して自動検知に戻せます。
+I<-a> オプションは標準状態でディスクイメージの形式を自動検知します。 これを使用することにより、コマンドラインで後続の I<-a> オプションのディスク形式を強制的に指定できます。 引数なしで I<--format> を使用することにより、 後続の I<-a> オプションに対して自動検知に戻せます。
例:
virt-tail --format=raw -a disk.img --format -a another.img file
-forces raw format (no auto-detection) for F<disk.img> and reverts to
-auto-detection for F<another.img>.
+forces raw format (no auto-detection) for F<disk.img> and reverts to auto-detection for F<another.img>.
-仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。
-これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
+仮想マシンのディスクイメージが信頼できない raw 形式である場合、 ディスク形式を指定するためにこのオプションを使用すべきです。 これにより、悪意のある仮想マシンにより起こり得る セキュリティ問題を回避できます (CVE-2010-3851)。
__INCLUDE:key-option.pod__
If the mountpoint is omitted, it defaults to F</>.
-Specifying any mountpoint disables the inspection of the guest and the mount
-of its root and all of its mountpoints, so make sure to mount all the
-mountpoints needed to work with the filenames given as arguments.
+Specifying any mountpoint disables the inspection of the guest and the mount of its root and all of its mountpoints, so make sure to mount all the mountpoints needed to work with the filenames given as arguments.
-If you don’t know what filesystems a disk image contains, you can either run
-guestfish without this option, then list the partitions, filesystems and LVs
-available (see L</list-partitions>, L</list-filesystems> and L</lvs>
-commands), or you can use the L<virt-filesystems(1)> program.
+If you don’t know what filesystems a disk image contains, you can either run guestfish without this option, then list the partitions, filesystems and LVs available (see L</list-partitions>, L</list-filesystems> and L</lvs> commands), or you can use the L<virt-filesystems(1)> program.
-マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される
-マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro>
-フラグが使用されている場合) になります。
+マウントパラメーターの三番目の (ほとんど使用されない) 項目は、 バックエンドのファイルシステムをマウントするために使用される マウントオプションの一覧です。 これが指定されていない場合、 マウントオプションは空文字列または C<ro> (I<--ro> フラグが使用されている場合) になります。
-m /dev/sda1:/:acl,user_xattr
このフラグを使用することは、 C<mount-options> コマンドを使用することと同等です。
-パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。
-しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs
-がファイルシステムを誤検知している場合、 これは有用です。
+パラメーターの四番目の項目は使用するファイルシステムドライバー (C<ext3> や C<ntfs> など) です。 これはほとんど必要ありません。 しかし、複数のドライバーがファイルシステムに対して有効である場合 (例: C<ext2> と C<ext3>)、 または libguestfs がファイルシステムを誤検知している場合、 これは有用です。
=item B<-v>
=head1 LOG FILES
-To list out the log files from guests, see the related tool L<virt-log(1)>.
-It understands binary log formats such as the systemd journal.
+To list out the log files from guests, see the related tool L<virt-log(1)>. It understands binary log formats such as the systemd journal.
=head1 Windows のパス
-C<virt-tail> has a limited ability to understand Windows drive letters and
-paths (eg. F<E:\foo\bar.txt>).
+C<virt-tail> has a limited ability to understand Windows drive letters and paths (eg. F<E:\foo\bar.txt>).
仮想マシンが Windows を実行している場合に限り:
=item *
-Drive letter prefixes like C<C:> are resolved against the Windows Registry
-to the correct filesystem.
+Drive letter prefixes like C<C:> are resolved against the Windows Registry to the correct filesystem.
=item *
-Any backslash (C<\>) characters in the path are replaced with forward
-slashes so that libguestfs can process it.
+Any backslash (C<\>) characters in the path are replaced with forward slashes so that libguestfs can process it.
=item *
-The path is resolved case insensitively to locate the file that should be
-displayed.
+The path is resolved case insensitively to locate the file that should be displayed.
=back
=head1 関連項目
-L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-cat(1)>,
-L<virt-log(1)>, L<virt-tar-out(1)>, L<tail(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-cat(1)>, L<virt-log(1)>, L<virt-tar-out(1)>, L<tail(1)>, L<http://libguestfs.org/>.
=head1 著者
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-win-reg 1"
-.TH virt-win-reg 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-win-reg 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "警告"
.IX Header "警告"
-You must \fInot\fR use \f(CW\*(C`virt\-win\-reg\*(C'\fR with the \fI\-\-merge\fR option on live
-virtual machines. If you do this, you \fIwill\fR get irreversible disk
-corruption in the \s-1VM.\s0 \f(CW\*(C`virt\-win\-reg\*(C'\fR tries to stop you from doing this,
-but doesn't catch all cases.
-.PP
-Modifying the Windows Registry is an inherently risky operation. The format
-is deliberately obscure and undocumented, and Registry changes can leave the
-system unbootable. Therefore when using the \fI\-\-merge\fR option, make sure
-you have a reliable backup first.
+You must \fInot\fR use \f(CW\*(C`virt\-win\-reg\*(C'\fR with the \fI\-\-merge\fR option on live virtual machines. If you do this, you \fIwill\fR get irreversible disk corruption in the \s-1VM.\s0 \f(CW\*(C`virt\-win\-reg\*(C'\fR tries to stop you from doing this, but doesn't catch all cases.
+.PP
+Modifying the Windows Registry is an inherently risky operation. The format is deliberately obscure and undocumented, and Registry changes can leave the system unbootable. Therefore when using the \fI\-\-merge\fR option, make sure you have a reliable backup first.
.SH "説明"
.IX Header "説明"
このプログラムは Windows 仮想マシンから Windows レジストリのエントリーをエクスポートおよびマージできます。
.PP
第一パラメーターは Windows 仮想マシンの libvirt 仮想マシン名または生のディスクイメージです。
.PP
-If \fI\-\-merge\fR is \fInot\fR specified, then the chosen registry key is
-displayed/exported (recursively). For example:
+If \fI\-\-merge\fR is \fInot\fR specified, then the chosen registry key is displayed/exported (recursively). For example:
.PP
.Vb 1
\& $ virt\-win\-reg Windows7 \*(AqHKEY_LOCAL_MACHINE\eSOFTWARE\eMicrosoft\*(Aq
.Ve
.SS "注記"
.IX Subsection "注記"
-This program is only meant for simple access to the registry. If you want
-to do complicated things with the registry, we suggest you download the
-Registry hive files from the guest using \fBlibguestfs\fR\|(3) or \fBguestfish\fR\|(1)
-and access them locally, eg. using \fBhivex\fR\|(3), \fBhivexsh\fR\|(1) or
-\&\fBhivexregedit\fR\|(1).
+This program is only meant for simple access to the registry. If you want to do complicated things with the registry, we suggest you download the Registry hive files from the guest using \fBlibguestfs\fR\|(3) or \fBguestfish\fR\|(1) and access them locally, eg. using \fBhivex\fR\|(3), \fBhivexsh\fR\|(1) or \fBhivexregedit\fR\|(1).
.SH "オプション"
.IX Header "オプション"
.IP "\fB\-\-help\fR" 4
仮想マシンのブロックデバイスを直接指定すると、libvirt はまったく使用されません。
.IP "\fB\-\-format\fR raw" 4
.IX Item "--format raw"
-Specify the format of disk images given on the command line. If this is
-omitted then the format is autodetected from the content of the disk image.
+Specify the format of disk images given on the command line. If this is omitted then the format is autodetected from the content of the disk image.
.Sp
-If disk images are requested from libvirt, then this program asks libvirt
-for this information. In this case, the value of the format parameter is
-ignored.
+If disk images are requested from libvirt, then this program asks libvirt for this information. In this case, the value of the format parameter is ignored.
.Sp
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
.IP "\fB\-\-merge\fR" 4
.IX Item "--merge"
-In merge mode, this merges a textual regedit file into the Windows Registry
-of the virtual machine. If this flag is \fInot\fR given then virt-win-reg
-displays or exports Registry entries instead.
+In merge mode, this merges a textual regedit file into the Windows Registry of the virtual machine. If this flag is \fInot\fR given then virt-win-reg displays or exports Registry entries instead.
.Sp
-Note that \fI\-\-merge\fR is \fIunsafe\fR to use on live virtual machines, and will
-result in disk corruption. However exporting (without this flag) is always
-safe.
+Note that \fI\-\-merge\fR is \fIunsafe\fR to use on live virtual machines, and will result in disk corruption. However exporting (without this flag) is always safe.
.IP "\fB\-\-encoding\fR UTF\-16LE|ASCII" 4
.IX Item "--encoding UTF-16LE|ASCII"
-When merging (only), you may need to specify the encoding for strings to be
-used in the hive file. This is explained in detail in
-\&\*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3).
+When merging (only), you may need to specify the encoding for strings to be used in the hive file. This is explained in detail in \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3).
.Sp
-The default is to use \s-1UTF\-16LE,\s0 which should work with recent versions of
-Windows.
+The default is to use \s-1UTF\-16LE,\s0 which should work with recent versions of Windows.
.IP "\fB\-\-unsafe\-printable\-strings\fR" 4
.IX Item "--unsafe-printable-strings"
-When exporting (only), assume strings are \s-1UTF\-16LE\s0 and print them as strings
-instead of hex sequences. Remove the final zero codepoint from strings if
-present.
+When exporting (only), assume strings are \s-1UTF\-16LE\s0 and print them as strings instead of hex sequences. Remove the final zero codepoint from strings if present.
.Sp
-This is unsafe and does not preserve the fidelity of strings in the original
-Registry for various reasons:
+This is unsafe and does not preserve the fidelity of strings in the original Registry for various reasons:
.RS 4
.IP "\(bu" 4
-Assumes the original encoding is \s-1UTF\-16LE.\s0 \s-1ASCII\s0 strings and strings in
-other encodings will be corrupted by this transformation.
+Assumes the original encoding is \s-1UTF\-16LE.\s0 \s-1ASCII\s0 strings and strings in other encodings will be corrupted by this transformation.
.IP "\(bu" 4
-Assumes that everything which has type 1 or 2 is really a string and that
-everything else is not a string, but the type field in real Registries is
-not reliable.
+Assumes that everything which has type 1 or 2 is really a string and that everything else is not a string, but the type field in real Registries is not reliable.
.IP "\(bu" 4
-Loses information about whether a zero codepoint followed the string in the
-Registry or not.
+Loses information about whether a zero codepoint followed the string in the Registry or not.
.RE
.RS 4
.Sp
-This all happens because the Registry itself contains no information about
-how strings are encoded (see \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3)).
+This all happens because the Registry itself contains no information about how strings are encoded (see \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3)).
.Sp
-You should only use this option for quick hacking and debugging of the
-Registry contents, and \fInever\fR use it if the output is going to be passed
-into another program or stored in another Registry.
+You should only use this option for quick hacking and debugging of the Registry contents, and \fInever\fR use it if the output is going to be passed into another program or stored in another Registry.
.RE
.SH "サポートされるシステム"
.IX Header "サポートされるシステム"
-The program currently supports Windows NT-derived guests starting with
-Windows \s-1XP\s0 through to at least Windows 8.
+The program currently supports Windows NT-derived guests starting with Windows \s-1XP\s0 through to at least Windows 8.
.PP
以下のレジストリキーがサポートされます:
.ie n .IP """HKEY_LOCAL_MACHINE\eSAM""" 4
.IX Item "HKEY_USERSusername"
ここで \fIusername\fR はローカルユーザー名です (これは libguestfs の拡張です)。
.PP
-You can use \f(CW\*(C`HKLM\*(C'\fR as a shorthand for \f(CW\*(C`HKEY_LOCAL_MACHINE\*(C'\fR, and \f(CW\*(C`HKU\*(C'\fR for
-\&\f(CW\*(C`HKEY_USERS\*(C'\fR.
+You can use \f(CW\*(C`HKLM\*(C'\fR as a shorthand for \f(CW\*(C`HKEY_LOCAL_MACHINE\*(C'\fR, and \f(CW\*(C`HKU\*(C'\fR for \f(CW\*(C`HKEY_USERS\*(C'\fR.
.PP
-The literal keys \f(CW\*(C`HKEY_USERS\e$SID\*(C'\fR and \f(CW\*(C`HKEY_CURRENT_USER\*(C'\fR are not
-supported (there is no \*(L"current user\*(R").
+The literal keys \f(CW\*(C`HKEY_USERS\e$SID\*(C'\fR and \f(CW\*(C`HKEY_CURRENT_USER\*(C'\fR are not supported (there is no \*(L"current user\*(R").
.SS "\s-1WINDOWS 8\s0"
.IX Subsection "WINDOWS 8"
-Windows 8 \*(L"fast startup\*(R" can prevent virt-win-reg from being able to edit
-the Registry. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST
-STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
+Windows 8 \*(L"fast startup\*(R" can prevent virt-win-reg from being able to edit the Registry. See \*(L"\s-1WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "エンコーディング"
.IX Header "エンコーディング"
-\&\f(CW\*(C`virt\-win\-reg\*(C'\fR expects that regedit files have already been reencoded in
-the local encoding. Usually on Linux hosts, this means \s-1UTF\-8\s0 with
-Unix-style line endings. Since Windows regedit files are often in \s-1UTF\-16LE\s0
-with Windows-style line endings, you may need to reencode the whole file
-before or after processing.
+\&\f(CW\*(C`virt\-win\-reg\*(C'\fR expects that regedit files have already been reencoded in the local encoding. Usually on Linux hosts, this means \s-1UTF\-8\s0 with Unix-style line endings. Since Windows regedit files are often in \s-1UTF\-16LE\s0 with Windows-style line endings, you may need to reencode the whole file before or after processing.
.PP
-To reencode a file from Windows format to Linux (before processing it with
-the \fI\-\-merge\fR option), you would do something like this:
+To reencode a file from Windows format to Linux (before processing it with the \fI\-\-merge\fR option), you would do something like this:
.PP
.Vb 1
\& iconv \-f utf\-16le \-t utf\-8 < win.reg | dos2unix > linux.reg
.Ve
.PP
-To go in the opposite direction, after exporting and before sending the file
-to a Windows user, do something like this:
+To go in the opposite direction, after exporting and before sending the file to a Windows user, do something like this:
.PP
.Vb 1
\& unix2dos linux.reg | iconv \-f utf\-8 \-t utf\-16le > win.reg
.PP
エンコーディングの詳細は \fBWin::Hivex::Regedit\fR\|(3) を参照してください。
.PP
-If you are unsure about the current encoding, use the \fBfile\fR\|(1) command.
-Recent versions of Windows regedit.exe produce a \s-1UTF\-16LE\s0 file with
-Windows-style (\s-1CRLF\s0) line endings, like this:
+If you are unsure about the current encoding, use the \fBfile\fR\|(1) command. Recent versions of Windows regedit.exe produce a \s-1UTF\-16LE\s0 file with Windows-style (\s-1CRLF\s0) line endings, like this:
.PP
.Vb 3
\& $ file software.reg
This file would need conversion before you could \fI\-\-merge\fR it.
.SH "CurrentControlSet など。"
.IX Header "CurrentControlSet など。"
-Registry keys like \f(CW\*(C`CurrentControlSet\*(C'\fR don’t really exist in the Windows
-Registry at the level of the hive file, and therefore you cannot modify
-these.
+Registry keys like \f(CW\*(C`CurrentControlSet\*(C'\fR don’t really exist in the Windows Registry at the level of the hive file, and therefore you cannot modify these.
.PP
-\&\f(CW\*(C`CurrentControlSet\*(C'\fR is usually an alias for \f(CW\*(C`ControlSet001\*(C'\fR. In some
-circumstances it might refer to another control set. The way to find out is
-to look at the \f(CW\*(C`HKLM\eSYSTEM\eSelect\*(C'\fR key:
+\&\f(CW\*(C`CurrentControlSet\*(C'\fR is usually an alias for \f(CW\*(C`ControlSet001\*(C'\fR. In some circumstances it might refer to another control set. The way to find out is to look at the \f(CW\*(C`HKLM\eSYSTEM\eSelect\*(C'\fR key:
.PP
.Vb 6
\& # virt\-win\-reg WindowsGuest \*(AqHKLM\eSYSTEM\eSelect\*(Aq
.Ve
.SH "Windows のヒント"
.IX Header "Windows のヒント"
-Note that some of these tips modify the guest disk image. The guest \fImust\fR
-be shut off, else you will get disk corruption.
+Note that some of these tips modify the guest disk image. The guest \fImust\fR be shut off, else you will get disk corruption.
.SS "\s-1RUNNING A BATCH SCRIPT WHEN A USER LOGS IN\s0"
.IX Subsection "RUNNING A BATCH SCRIPT WHEN A USER LOGS IN"
-Prepare a \s-1DOS\s0 batch script, VBScript or executable. Upload this using
-\&\fBguestfish\fR\|(1). For this example the script is called \f(CW\*(C`test.bat\*(C'\fR and it
-is uploaded into \f(CW\*(C`C:\e\*(C'\fR:
+Prepare a \s-1DOS\s0 batch script, VBScript or executable. Upload this using \fBguestfish\fR\|(1). For this example the script is called \f(CW\*(C`test.bat\*(C'\fR and it is uploaded into \f(CW\*(C`C:\e\*(C'\fR:
.PP
.Vb 1
\& guestfish \-i \-d WindowsGuest upload test.bat /test.bat
\& EOF
.Ve
.PP
-In this example we use the key \f(CW\*(C`RunOnce\*(C'\fR which means that the script will
-run precisely once when the first user logs in. If you want it to run every
-time a user logs in, replace \f(CW\*(C`RunOnce\*(C'\fR with \f(CW\*(C`Run\*(C'\fR.
+In this example we use the key \f(CW\*(C`RunOnce\*(C'\fR which means that the script will run precisely once when the first user logs in. If you want it to run every time a user logs in, replace \f(CW\*(C`RunOnce\*(C'\fR with \f(CW\*(C`Run\*(C'\fR.
.PP
Now update the registry:
.PP
.Ve
.SS "サービスのインストール方法"
.IX Subsection "サービスのインストール方法"
-This section assumes you are familiar with Windows services, and you either
-have a program which handles the Windows Service Control Protocol directly
-or you want to run any program using a service wrapper like SrvAny or the
-free RHSrvAny.
+This section assumes you are familiar with Windows services, and you either have a program which handles the Windows Service Control Protocol directly or you want to run any program using a service wrapper like SrvAny or the free RHSrvAny.
.PP
-First upload the program and optionally the service wrapper. In this case
-the test program is called \f(CW\*(C`test.exe\*(C'\fR and we are using the RHSrvAny
-wrapper:
+First upload the program and optionally the service wrapper. In this case the test program is called \f(CW\*(C`test.exe\*(C'\fR and we are using the RHSrvAny wrapper:
.PP
.Vb 4
\& guestfish \-i \-d WindowsGuest <<EOF
\& EOF
.Ve
.PP
-Prepare a regedit file containing the registry changes. In this example,
-the first registry change is needed for the service itself or the service
-wrapper (if used). The second registry change is only needed because I am
-using the RHSrvAny service wrapper.
+Prepare a regedit file containing the registry changes. In this example, the first registry change is needed for the service itself or the service wrapper (if used). The second registry change is only needed because I am using the RHSrvAny service wrapper.
.PP
.Vb 8
\& cat > service.reg <<\*(AqEOF\*(Aq
.PP
注:
.IP "\(bu" 4
-For use of \f(CW\*(C`ControlSet001\*(C'\fR see the section above in this manual page. You
-may need to adjust this according to the control set that is in use by the
-guest.
+For use of \f(CW\*(C`ControlSet001\*(C'\fR see the section above in this manual page. You may need to adjust this according to the control set that is in use by the guest.
.IP "\(bu" 4
-\&\f(CW"ObjectName"\fR controls the privileges that the service will have. An
-alternative is \f(CW"ObjectName"="LocalSystem"\fR which would be the most
-privileged account.
+\&\f(CW"ObjectName"\fR controls the privileges that the service will have. An alternative is \f(CW"ObjectName"="LocalSystem"\fR which would be the most privileged account.
.IP "\(bu" 4
-マジックナンバーの意味は次の Microsoft \s-1KB\s0 記事を参照してください:
-http://support.microsoft.com/kb/103000.
+マジックナンバーの意味は次の Microsoft \s-1KB\s0 記事を参照してください: http://support.microsoft.com/kb/103000.
.PP
レジストリを更新します:
.PP
.Ve
.SH "SHELL QUOTING"
.IX Header "SHELL QUOTING"
-シェルにおいて \f(CW\*(C`\e\*(C'\fR (backslash)
-を含むパラメーターを渡すとき、注意する必要があります。通常シェルからそれらを保護するには、'単一引用符' または二つのバックスラッシュ
-(しかし、両方ではない) を使用する必要があります。
+シェルにおいて \f(CW\*(C`\e\*(C'\fR (backslash) を含むパラメーターを渡すとき、注意する必要があります。通常シェルからそれらを保護するには、'単一引用符' または二つのバックスラッシュ (しかし、両方ではない) を使用する必要があります。
.PP
パスおよび値の名前は大文字小文字を区別します。
.SH "関連項目"
.IX Header "関連項目"
-\&\fBhivex\fR\|(3), \fBhivexsh\fR\|(1), \fBhivexregedit\fR\|(1), \fBguestfs\fR\|(3),
-\&\fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-tail\fR\|(1), \fBSys::Guestfs\fR\|(3),
-\&\fBWin::Hivex\fR\|(3), \fBWin::Hivex::Regedit\fR\|(3), \fBSys::Virt\fR\|(3),
-http://libguestfs.org/.
+\&\fBhivex\fR\|(3), \fBhivexsh\fR\|(1), \fBhivexregedit\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-tail\fR\|(1), \fBSys::Guestfs\fR\|(3), \fBWin::Hivex\fR\|(3), \fBWin::Hivex::Regedit\fR\|(3), \fBSys::Virt\fR\|(3), http://libguestfs.org/.
.SH "著者"
.IX Header "著者"
Richard W.M. Jones http://people.redhat.com/~rjones/
--- /dev/null
+
+=head1 名前
+
+virt-win-reg - Windows 仮想マシンからの Windows レジストリエントリーのエクスポートおよびマージ
+
+=head1 書式
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey'
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey' name
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey' @
+
+ virt-win-reg --merge domname [input.reg ...]
+
+ virt-win-reg [--options] disk.img ... # 仮想マシン名の代わり
+
+=head1 警告
+
+You must I<not> use C<virt-win-reg> with the I<--merge> option on live virtual machines. If you do this, you I<will> get irreversible disk corruption in the VM. C<virt-win-reg> tries to stop you from doing this, but doesn't catch all cases.
+
+Modifying the Windows Registry is an inherently risky operation. The format is deliberately obscure and undocumented, and Registry changes can leave the system unbootable. Therefore when using the I<--merge> option, make sure you have a reliable backup first.
+
+=head1 説明
+
+このプログラムは Windows 仮想マシンから Windows レジストリのエントリーをエクスポートおよびマージできます。
+
+第一パラメーターは Windows 仮想マシンの libvirt 仮想マシン名または生のディスクイメージです。
+
+If I<--merge> is I<not> specified, then the chosen registry key is displayed/exported (recursively). For example:
+
+ $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
+
+You can also display single values from within registry keys, for example:
+
+ $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
+ $ virt-win-reg Windows7 $cvkey ProductName
+ Windows 7 Enterprise
+
+I<--merge> を用いると、テキストの regedit ファイルを Windows レジストリーの中に結合できます:
+
+ $ virt-win-reg --merge Windows7 changes.reg
+
+=head2 注記
+
+This program is only meant for simple access to the registry. If you want to do complicated things with the registry, we suggest you download the Registry hive files from the guest using L<libguestfs(3)> or L<guestfish(1)> and access them locally, eg. using L<hivex(3)>, L<hivexsh(1)> or L<hivexregedit(1)>.
+
+=head1 オプション
+
+=over 4
+
+=item B<--help>
+
+簡単なヘルプを表示します。
+
+=item B<--version>
+
+バージョン番号を表示して、終了します。
+
+=item B<--debug>
+
+デバッグメッセージを有効にします。
+
+=item B<-c URI>
+
+=item B<--connect URI>
+
+libvirt を使用していると、指定された I<URI> に接続します。 省略すると、デフォルトの libvirt ハイパーバイザーに接続します。
+
+仮想マシンのブロックデバイスを直接指定すると、libvirt はまったく使用されません。
+
+=item B<--format> raw
+
+Specify the format of disk images given on the command line. If this is omitted then the format is autodetected from the content of the disk image.
+
+If disk images are requested from libvirt, then this program asks libvirt for this information. In this case, the value of the format parameter is ignored.
+
+If working with untrusted raw-format guest disk images, you should ensure the format is always specified.
+
+=item B<--merge>
+
+In merge mode, this merges a textual regedit file into the Windows Registry of the virtual machine. If this flag is I<not> given then virt-win-reg displays or exports Registry entries instead.
+
+Note that I<--merge> is I<unsafe> to use on live virtual machines, and will result in disk corruption. However exporting (without this flag) is always safe.
+
+=item B<--encoding> UTF-16LE|ASCII
+
+When merging (only), you may need to specify the encoding for strings to be used in the hive file. This is explained in detail in L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
+
+The default is to use UTF-16LE, which should work with recent versions of Windows.
+
+=item B<--unsafe-printable-strings>
+
+When exporting (only), assume strings are UTF-16LE and print them as strings instead of hex sequences. Remove the final zero codepoint from strings if present.
+
+This is unsafe and does not preserve the fidelity of strings in the original Registry for various reasons:
+
+=over 4
+
+=item *
+
+Assumes the original encoding is UTF-16LE. ASCII strings and strings in other encodings will be corrupted by this transformation.
+
+=item *
+
+Assumes that everything which has type 1 or 2 is really a string and that everything else is not a string, but the type field in real Registries is not reliable.
+
+=item *
+
+Loses information about whether a zero codepoint followed the string in the Registry or not.
+
+=back
+
+This all happens because the Registry itself contains no information about how strings are encoded (see L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
+
+You should only use this option for quick hacking and debugging of the Registry contents, and I<never> use it if the output is going to be passed into another program or stored in another Registry.
+
+=back
+
+=head1 サポートされるシステム
+
+The program currently supports Windows NT-derived guests starting with Windows XP through to at least Windows 8.
+
+以下のレジストリキーがサポートされます:
+
+=over 4
+
+=item C<HKEY_LOCAL_MACHINE\SAM>
+
+=item C<HKEY_LOCAL_MACHINE\SECURITY>
+
+=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
+
+=item C<HKEY_LOCAL_MACHINE\SYSTEM>
+
+=item C<HKEY_USERS\.DEFAULT>
+
+=item C<HKEY_USERS\I<SID>>
+
+ここで I<SID> は Windows User SID です (例: C<S-1-5-18>)。
+
+=item C<HKEY_USERS\I<username>>
+
+ここで I<username> はローカルユーザー名です (これは libguestfs の拡張です)。
+
+=back
+
+You can use C<HKLM> as a shorthand for C<HKEY_LOCAL_MACHINE>, and C<HKU> for C<HKEY_USERS>.
+
+The literal keys C<HKEY_USERS\$SID> and C<HKEY_CURRENT_USER> are not supported (there is no "current user").
+
+=head2 WINDOWS 8
+
+Windows 8 "fast startup" can prevent virt-win-reg from being able to edit the Registry. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
+
+=head1 エンコーディング
+
+C<virt-win-reg> expects that regedit files have already been reencoded in the local encoding. Usually on Linux hosts, this means UTF-8 with Unix-style line endings. Since Windows regedit files are often in UTF-16LE with Windows-style line endings, you may need to reencode the whole file before or after processing.
+
+To reencode a file from Windows format to Linux (before processing it with the I<--merge> option), you would do something like this:
+
+ iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
+
+To go in the opposite direction, after exporting and before sending the file to a Windows user, do something like this:
+
+ unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
+
+エンコーディングの詳細は L<Win::Hivex::Regedit(3)> を参照してください。
+
+If you are unsure about the current encoding, use the L<file(1)> command. Recent versions of Windows regedit.exe produce a UTF-16LE file with Windows-style (CRLF) line endings, like this:
+
+ $ file software.reg
+ software.reg: Little-endian UTF-16 Unicode text, with very long lines,
+ with CRLF line terminators
+
+This file would need conversion before you could I<--merge> it.
+
+=head1 CurrentControlSet など。
+
+Registry keys like C<CurrentControlSet> don’t really exist in the Windows Registry at the level of the hive file, and therefore you cannot modify these.
+
+C<CurrentControlSet> is usually an alias for C<ControlSet001>. In some circumstances it might refer to another control set. The way to find out is to look at the C<HKLM\SYSTEM\Select> key:
+
+ # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
+ [HKEY_LOCAL_MACHINE\SYSTEM\Select]
+ "Current"=dword:00000001
+ "Default"=dword:00000001
+ "Failed"=dword:00000000
+ "LastKnownGood"=dword:00000002
+
+"Current" is the one which Windows will choose when it boots.
+
+Similarly, other C<Current...> keys in the path may need to be replaced.
+
+=head1 レジストリーキーおよび値の削除方法
+
+レジストリキー全体を削除するには、この構文を使用します:
+
+ [-HKEY_LOCAL_MACHINE\Foo]
+
+キーにある単一の値を削除するには、この構文を使用します:
+
+ [HKEY_LOCAL_MACHINE\Foo]
+ "Value"=-
+
+=head1 Windows のヒント
+
+Note that some of these tips modify the guest disk image. The guest I<must> be shut off, else you will get disk corruption.
+
+=head2 RUNNING A BATCH SCRIPT WHEN A USER LOGS IN
+
+Prepare a DOS batch script, VBScript or executable. Upload this using L<guestfish(1)>. For this example the script is called C<test.bat> and it is uploaded into C<C:\>:
+
+ guestfish -i -d WindowsGuest upload test.bat /test.bat
+
+Prepare a regedit file containing the registry change:
+
+ cat > test.reg <<'EOF'
+ [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
+ "Test"="c:\\test.bat"
+ EOF
+
+In this example we use the key C<RunOnce> which means that the script will run precisely once when the first user logs in. If you want it to run every time a user logs in, replace C<RunOnce> with C<Run>.
+
+Now update the registry:
+
+ virt-win-reg --merge WindowsGuest test.reg
+
+=head2 サービスのインストール方法
+
+This section assumes you are familiar with Windows services, and you either have a program which handles the Windows Service Control Protocol directly or you want to run any program using a service wrapper like SrvAny or the free RHSrvAny.
+
+First upload the program and optionally the service wrapper. In this case the test program is called C<test.exe> and we are using the RHSrvAny wrapper:
+
+ guestfish -i -d WindowsGuest <<EOF
+ upload rhsrvany.exe /rhsrvany.exe
+ upload test.exe /test.exe
+ EOF
+
+Prepare a regedit file containing the registry changes. In this example, the first registry change is needed for the service itself or the service wrapper (if used). The second registry change is only needed because I am using the RHSrvAny service wrapper.
+
+ cat > service.reg <<'EOF'
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
+ "Type"=dword:00000010
+ "Start"=dword:00000002
+ "ErrorControl"=dword:00000001
+ "ImagePath"="c:\\rhsrvany.exe"
+ "DisplayName"="RHSrvAny"
+ "ObjectName"="NetworkService"
+
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
+ "CommandLine"="c:\\test.exe"
+ "PWD"="c:\\Temp"
+ EOF
+
+注:
+
+=over 4
+
+=item *
+
+For use of C<ControlSet001> see the section above in this manual page. You may need to adjust this according to the control set that is in use by the guest.
+
+=item *
+
+C<"ObjectName"> controls the privileges that the service will have. An alternative is C<"ObjectName"="LocalSystem"> which would be the most privileged account.
+
+=item *
+
+マジックナンバーの意味は次の Microsoft KB 記事を参照してください: L<http://support.microsoft.com/kb/103000>.
+
+=back
+
+レジストリを更新します:
+
+ virt-win-reg --merge WindowsGuest service.reg
+
+=head1 SHELL QUOTING
+
+シェルにおいて C<\> (backslash) を含むパラメーターを渡すとき、注意する必要があります。通常シェルからそれらを保護するには、'単一引用符' または二つのバックスラッシュ (しかし、両方ではない) を使用する必要があります。
+
+パスおよび値の名前は大文字小文字を区別します。
+
+=head1 関連項目
+
+L<hivex(3)>, L<hivexsh(1)>, L<hivexregedit(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-tail(1)>, L<Sys::Guestfs(3)>, L<Win::Hivex(3)>, L<Win::Hivex::Regedit(3)>, L<Sys::Virt(3)>, L<http://libguestfs.org/>.
+
+=head1 著者
+
+Richard W.M. Jones L<http://people.redhat.com/~rjones/>
+
+=head1 COPYRIGHT
+
+Copyright (C) 2010 Red Hat Inc.
+
+++ /dev/null
-
-=head1 名前
-
-virt-win-reg - Windows 仮想マシンからの Windows レジストリエントリーのエクスポートおよびマージ
-
-=head1 書式
-
- virt-win-reg domname 'HKLM\Path\To\Subkey'
-
- virt-win-reg domname 'HKLM\Path\To\Subkey' name
-
- virt-win-reg domname 'HKLM\Path\To\Subkey' @
-
- virt-win-reg --merge domname [input.reg ...]
-
- virt-win-reg [--options] disk.img ... # 仮想マシン名の代わり
-
-=head1 警告
-
-You must I<not> use C<virt-win-reg> with the I<--merge> option on live
-virtual machines. If you do this, you I<will> get irreversible disk
-corruption in the VM. C<virt-win-reg> tries to stop you from doing this,
-but doesn't catch all cases.
-
-Modifying the Windows Registry is an inherently risky operation. The format
-is deliberately obscure and undocumented, and Registry changes can leave the
-system unbootable. Therefore when using the I<--merge> option, make sure
-you have a reliable backup first.
-
-=head1 説明
-
-このプログラムは Windows 仮想マシンから Windows レジストリのエントリーをエクスポートおよびマージできます。
-
-第一パラメーターは Windows 仮想マシンの libvirt 仮想マシン名または生のディスクイメージです。
-
-If I<--merge> is I<not> specified, then the chosen registry key is
-displayed/exported (recursively). For example:
-
- $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
-
-You can also display single values from within registry keys, for example:
-
- $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
- $ virt-win-reg Windows7 $cvkey ProductName
- Windows 7 Enterprise
-
-I<--merge> を用いると、テキストの regedit ファイルを Windows レジストリーの中に結合できます:
-
- $ virt-win-reg --merge Windows7 changes.reg
-
-=head2 注記
-
-This program is only meant for simple access to the registry. If you want
-to do complicated things with the registry, we suggest you download the
-Registry hive files from the guest using L<libguestfs(3)> or L<guestfish(1)>
-and access them locally, eg. using L<hivex(3)>, L<hivexsh(1)> or
-L<hivexregedit(1)>.
-
-=head1 オプション
-
-=over 4
-
-=item B<--help>
-
-簡単なヘルプを表示します。
-
-=item B<--version>
-
-バージョン番号を表示して、終了します。
-
-=item B<--debug>
-
-デバッグメッセージを有効にします。
-
-=item B<-c URI>
-
-=item B<--connect URI>
-
-libvirt を使用していると、指定された I<URI> に接続します。 省略すると、デフォルトの libvirt ハイパーバイザーに接続します。
-
-仮想マシンのブロックデバイスを直接指定すると、libvirt はまったく使用されません。
-
-=item B<--format> raw
-
-Specify the format of disk images given on the command line. If this is
-omitted then the format is autodetected from the content of the disk image.
-
-If disk images are requested from libvirt, then this program asks libvirt
-for this information. In this case, the value of the format parameter is
-ignored.
-
-If working with untrusted raw-format guest disk images, you should ensure
-the format is always specified.
-
-=item B<--merge>
-
-In merge mode, this merges a textual regedit file into the Windows Registry
-of the virtual machine. If this flag is I<not> given then virt-win-reg
-displays or exports Registry entries instead.
-
-Note that I<--merge> is I<unsafe> to use on live virtual machines, and will
-result in disk corruption. However exporting (without this flag) is always
-safe.
-
-=item B<--encoding> UTF-16LE|ASCII
-
-When merging (only), you may need to specify the encoding for strings to be
-used in the hive file. This is explained in detail in
-L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
-
-The default is to use UTF-16LE, which should work with recent versions of
-Windows.
-
-=item B<--unsafe-printable-strings>
-
-When exporting (only), assume strings are UTF-16LE and print them as strings
-instead of hex sequences. Remove the final zero codepoint from strings if
-present.
-
-This is unsafe and does not preserve the fidelity of strings in the original
-Registry for various reasons:
-
-=over 4
-
-=item *
-
-Assumes the original encoding is UTF-16LE. ASCII strings and strings in
-other encodings will be corrupted by this transformation.
-
-=item *
-
-Assumes that everything which has type 1 or 2 is really a string and that
-everything else is not a string, but the type field in real Registries is
-not reliable.
-
-=item *
-
-Loses information about whether a zero codepoint followed the string in the
-Registry or not.
-
-=back
-
-This all happens because the Registry itself contains no information about
-how strings are encoded (see L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
-
-You should only use this option for quick hacking and debugging of the
-Registry contents, and I<never> use it if the output is going to be passed
-into another program or stored in another Registry.
-
-=back
-
-=head1 サポートされるシステム
-
-The program currently supports Windows NT-derived guests starting with
-Windows XP through to at least Windows 8.
-
-以下のレジストリキーがサポートされます:
-
-=over 4
-
-=item C<HKEY_LOCAL_MACHINE\SAM>
-
-=item C<HKEY_LOCAL_MACHINE\SECURITY>
-
-=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
-
-=item C<HKEY_LOCAL_MACHINE\SYSTEM>
-
-=item C<HKEY_USERS\.DEFAULT>
-
-=item C<HKEY_USERS\I<SID>>
-
-ここで I<SID> は Windows User SID です (例: C<S-1-5-18>)。
-
-=item C<HKEY_USERS\I<username>>
-
-ここで I<username> はローカルユーザー名です (これは libguestfs の拡張です)。
-
-=back
-
-You can use C<HKLM> as a shorthand for C<HKEY_LOCAL_MACHINE>, and C<HKU> for
-C<HKEY_USERS>.
-
-The literal keys C<HKEY_USERS\$SID> and C<HKEY_CURRENT_USER> are not
-supported (there is no "current user").
-
-=head2 WINDOWS 8
-
-Windows 8 "fast startup" can prevent virt-win-reg from being able to edit
-the Registry. See L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST
-STARTUP>.
-
-=head1 エンコーディング
-
-C<virt-win-reg> expects that regedit files have already been reencoded in
-the local encoding. Usually on Linux hosts, this means UTF-8 with
-Unix-style line endings. Since Windows regedit files are often in UTF-16LE
-with Windows-style line endings, you may need to reencode the whole file
-before or after processing.
-
-To reencode a file from Windows format to Linux (before processing it with
-the I<--merge> option), you would do something like this:
-
- iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
-
-To go in the opposite direction, after exporting and before sending the file
-to a Windows user, do something like this:
-
- unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
-
-エンコーディングの詳細は L<Win::Hivex::Regedit(3)> を参照してください。
-
-If you are unsure about the current encoding, use the L<file(1)> command.
-Recent versions of Windows regedit.exe produce a UTF-16LE file with
-Windows-style (CRLF) line endings, like this:
-
- $ file software.reg
- software.reg: Little-endian UTF-16 Unicode text, with very long lines,
- with CRLF line terminators
-
-This file would need conversion before you could I<--merge> it.
-
-=head1 CurrentControlSet など。
-
-Registry keys like C<CurrentControlSet> don’t really exist in the Windows
-Registry at the level of the hive file, and therefore you cannot modify
-these.
-
-C<CurrentControlSet> is usually an alias for C<ControlSet001>. In some
-circumstances it might refer to another control set. The way to find out is
-to look at the C<HKLM\SYSTEM\Select> key:
-
- # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
- [HKEY_LOCAL_MACHINE\SYSTEM\Select]
- "Current"=dword:00000001
- "Default"=dword:00000001
- "Failed"=dword:00000000
- "LastKnownGood"=dword:00000002
-
-"Current" is the one which Windows will choose when it boots.
-
-Similarly, other C<Current...> keys in the path may need to be replaced.
-
-=head1 レジストリーキーおよび値の削除方法
-
-レジストリキー全体を削除するには、この構文を使用します:
-
- [-HKEY_LOCAL_MACHINE\Foo]
-
-キーにある単一の値を削除するには、この構文を使用します:
-
- [HKEY_LOCAL_MACHINE\Foo]
- "Value"=-
-
-=head1 Windows のヒント
-
-Note that some of these tips modify the guest disk image. The guest I<must>
-be shut off, else you will get disk corruption.
-
-=head2 RUNNING A BATCH SCRIPT WHEN A USER LOGS IN
-
-Prepare a DOS batch script, VBScript or executable. Upload this using
-L<guestfish(1)>. For this example the script is called C<test.bat> and it
-is uploaded into C<C:\>:
-
- guestfish -i -d WindowsGuest upload test.bat /test.bat
-
-Prepare a regedit file containing the registry change:
-
- cat > test.reg <<'EOF'
- [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
- "Test"="c:\\test.bat"
- EOF
-
-In this example we use the key C<RunOnce> which means that the script will
-run precisely once when the first user logs in. If you want it to run every
-time a user logs in, replace C<RunOnce> with C<Run>.
-
-Now update the registry:
-
- virt-win-reg --merge WindowsGuest test.reg
-
-=head2 サービスのインストール方法
-
-This section assumes you are familiar with Windows services, and you either
-have a program which handles the Windows Service Control Protocol directly
-or you want to run any program using a service wrapper like SrvAny or the
-free RHSrvAny.
-
-First upload the program and optionally the service wrapper. In this case
-the test program is called C<test.exe> and we are using the RHSrvAny
-wrapper:
-
- guestfish -i -d WindowsGuest <<EOF
- upload rhsrvany.exe /rhsrvany.exe
- upload test.exe /test.exe
- EOF
-
-Prepare a regedit file containing the registry changes. In this example,
-the first registry change is needed for the service itself or the service
-wrapper (if used). The second registry change is only needed because I am
-using the RHSrvAny service wrapper.
-
- cat > service.reg <<'EOF'
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
- "Type"=dword:00000010
- "Start"=dword:00000002
- "ErrorControl"=dword:00000001
- "ImagePath"="c:\\rhsrvany.exe"
- "DisplayName"="RHSrvAny"
- "ObjectName"="NetworkService"
-
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
- "CommandLine"="c:\\test.exe"
- "PWD"="c:\\Temp"
- EOF
-
-注:
-
-=over 4
-
-=item *
-
-For use of C<ControlSet001> see the section above in this manual page. You
-may need to adjust this according to the control set that is in use by the
-guest.
-
-=item *
-
-C<"ObjectName"> controls the privileges that the service will have. An
-alternative is C<"ObjectName"="LocalSystem"> which would be the most
-privileged account.
-
-=item *
-
-マジックナンバーの意味は次の Microsoft KB 記事を参照してください:
-L<http://support.microsoft.com/kb/103000>.
-
-=back
-
-レジストリを更新します:
-
- virt-win-reg --merge WindowsGuest service.reg
-
-=head1 SHELL QUOTING
-
-シェルにおいて C<\> (backslash)
-を含むパラメーターを渡すとき、注意する必要があります。通常シェルからそれらを保護するには、'単一引用符' または二つのバックスラッシュ
-(しかし、両方ではない) を使用する必要があります。
-
-パスおよび値の名前は大文字小文字を区別します。
-
-=head1 関連項目
-
-L<hivex(3)>, L<hivexsh(1)>, L<hivexregedit(1)>, L<guestfs(3)>,
-L<guestfish(1)>, L<virt-cat(1)>, L<virt-tail(1)>, L<Sys::Guestfs(3)>,
-L<Win::Hivex(3)>, L<Win::Hivex::Regedit(3)>, L<Sys::Virt(3)>,
-L<http://libguestfs.org/>.
-
-=head1 著者
-
-Richard W.M. Jones L<http://people.redhat.com/~rjones/>
-
-=head1 COPYRIGHT
-
-Copyright (C) 2010 Red Hat Inc.
-
df/virt-df.pod
dib/virt-dib.pod
diff/virt-diff.pod
+docs/guestfs-tools-release-notes-1.48.pod
edit/virt-edit.pod
format/virt-format.pod
get-kernel/virt-get-kernel.pod
sysprep/sysprep-extra-options.pod
sysprep/sysprep-operations.pod
sysprep/virt-sysprep.pod
-win-reg/virt-win-reg
+win-reg/virt-win-reg.in
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
=item B<--blocksize>
-This parameter sets the sector size of the disk image. It affects all
-explicitly added subsequent disks after this parameter. Using
-I<--blocksize> with no argument switches the disk sector size to the default
-value which is usually 512 bytes. See also
-L<guestfs(3)/guestfs_add_drive_opts>.
+This parameter sets the sector size of the disk image. It affects all explicitly added subsequent disks after this parameter. Using I<--blocksize> with no argument switches the disk sector size to the default value which is usually 512 bytes. See also L<guestfs(3)/guestfs_add_drive_opts>.
=item B<--append-line> ФАЙЛ:РЯДОК
-Дописати один рядок тексту до файла C<ФАЙЛ>. Якщо файл ще не завершується
-порожнім рядком, такий рядок буде додано перед дописаним. Крім того,
-автоматично буде дописано символ нового рядка наприкінці рядка C<РЯДОК>.
+Дописати один рядок тексту до файла C<ФАЙЛ>. Якщо файл ще не завершується порожнім рядком, такий рядок буде додано перед дописаним. Крім того, автоматично буде дописано символ нового рядка наприкінці рядка C<РЯДОК>.
-Наприклад, (припускаємо, що у командній оболонці використовуються звичайні
-лапки) така команда:
+Наприклад, (припускаємо, що у командній оболонці використовуються звичайні лапки) така команда:
--append-line '/etc/hosts:10.0.0.1 foo'
-додасть C<10.0.0.1 foo⏎> або C<⏎10.0.0.1 foo⏎> до файла; останній запис буде
-додано, лише якщо наявний файл ще не закінчується символом нового рядка.
+додасть C<10.0.0.1 foo⏎> або C<⏎10.0.0.1 foo⏎> до файла; останній запис буде додано, лише якщо наявний файл ще не закінчується символом нового рядка.
-C<⏎> позначає символ нового рядка, конкретне значення якого визначається за
-наявним вмістом файла, отже, команда обробляє файли однаково правильно для
-варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для
-порожніх і ще не створених файлів.
+C<⏎> позначає символ нового рядка, конкретне значення якого визначається за наявним вмістом файла, отже, команда обробляє файли однаково правильно для варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для порожніх і ще не створених файлів.
-Щоб додати декілька рядків, скористайтеся тим самим параметром декілька
-разів:
+Щоб додати декілька рядків, скористайтеся тим самим параметром декілька разів:
--append-line '/etc/hosts:10.0.0.1 foo'
--append-line '/etc/hosts:10.0.0.2 bar'
-Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою
-конструкцією:
+Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою конструкцією:
--append-line '/etc/hosts:'
--append-line '/etc/hosts:10.0.0.1 foo'
Змінити права доступу до файла C<ФАЙЛ> на C<ПРАВА_ДОСТУПУ>.
-I<Зауваження>: типово C<ПРАВА_ДОСТУПУ> записуються у десятковому форматі,
-якщо ви не додасте початковий C<0> , щоб вказати вісімкове число, тобто
-скористаєтеся C<0700>, а не C<700>.
+I<Зауваження>: типово C<ПРАВА_ДОСТУПУ> записуються у десятковому форматі, якщо ви не додасте початковий C<0> , щоб вказати вісімкове число, тобто скористаєтеся C<0700>, а не C<700>.
=item B<--commands-from-file> НАЗВА_ФАЙЛА
-Прочитати команди налаштовування з файла, по одній (разом із аргументами) на
-рядок.
+Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.
Кожен рядок містить команду налаштовування та її аргументи, наприклад:
install якийсь_пакунок
password якийсь-користувач:password:його-новий-пароль
-Порожні рядки ігноруються, а рядки, що починаються з C<#>, є коментарями і
-також ігноруються. Крім того, аргументи можна розділити на декілька рядків
-додаванням C<\> (символу продовження) наприкінці рядка. Приклад:
+Порожні рядки ігноруються, а рядки, що починаються з C<#>, є коментарями і також ігноруються. Крім того, аргументи можна розділити на декілька рядків додаванням C<\> (символу продовження) наприкінці рядка. Приклад:
edit /якийсь/файл:\
s/^OPT=.*/OPT=ok/
-Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так,
-наче їх вказано як I<--delete /якийсь/файл> у рядку команди.
+Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так, наче їх вказано як I<--delete /якийсь/файл> у рядку команди.
=item B<--copy> ДЖЕРЕЛО:ПРИЗНАЧЕННЯ
=item B<--copy-in> ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ
-Скопіювати локальні файли або каталоги рекурсивно до образу диска,
-розташувавши його у каталозі C<ВІДДАЛЕНИЙ_КАТАЛОГ> (який має існувати).
+Скопіювати локальні файли або каталоги рекурсивно до образу диска, розташувавши його у каталозі C<ВІДДАЛЕНИЙ_КАТАЛОГ> (який має існувати).
Не можна використовувати символи-замінники.
=item B<--delete> ШЛЯХ
-Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
-рекурсивно).
+Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст, рекурсивно).
-Ви можете скористатися символами-замінниками у вказаному шляху. Не забудьте
-екранувати символи-замінники у командній оболонці основної системи, якщо це
-потрібно. Приклад:
+Ви можете скористатися символами-замінниками у вказаному шляху. Не забудьте екранувати символи-замінники у командній оболонці основної системи, якщо це потрібно. Приклад:
virt-customize --delete '/var/log/*.log'.
Редагувати C<ФАЙЛ> з використанням виразу Perl C<ВИРАЗ>.
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
Див. L<virt-edit(1)/NON-INTERACTIVE EDITING>.
=item B<--firstboot> СКРИПТ
-Встановити C<СКРИПТ> у гостьовій системі і запустити його під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Встановити C<СКРИПТ> у гостьовій системі і запустити його під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
-До скрипту, після встановлення до гостьової системи, буде автоматично
-застосовано команду chmod +x.
+До скрипту, після встановлення до гостьової системи, буде автоматично застосовано команду chmod +x.
-Альтернативна версія I<--firstboot-command> є такою самою, але зручно
-включає команду у однорядковому скрипті.
+Альтернативна версія I<--firstboot-command> є такою самою, але зручно включає команду у однорядковому скрипті.
-Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
-Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
Див. також I<--run>.
=item B<--firstboot-command> 'КОМАНДА+ПАРАМЕТРИ'
-Виконати команду (разом із аргументами) у гостьовій системі під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Виконати команду (разом із аргументами) у гостьовій системі під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
-Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
-Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
Див. також I<--run>.
=item B<--firstboot-install> ПАКУНОК,ПАКУНОК..
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час першого завантаження гостьової системи за
-допомогою програми для керування пакунків гостьової системи (наприклад, apt,
-yum тощо) і з'єднання із мережею гостьової системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час першого завантаження гостьової системи за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею гостьової системи.
-Огляд різних способів встановлення пакунків наведено у розділі
-L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
+Огляд різних способів встановлення пакунків наведено у розділі L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
=item B<--hostname> НАЗВА_ВУЗЛА
-Встановити як назву вузла гостьової системи значення C<НАЗВА_ВУЗЛА>. Якщо
-потрібно, можете скористатися форматом із крапкою,
-«назва_вузла.назва_домену» (FQDN).
+Встановити як назву вузла гостьової системи значення C<НАЗВА_ВУЗЛА>. Якщо потрібно, можете скористатися форматом із крапкою, «назва_вузла.назва_домену» (FQDN).
=item B<--install> ПАКУНОК,ПАКУНОК..
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання
-із мережею основної системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею основної системи.
-Огляд різних способів встановлення пакунків наведено у розділі
-L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
+Огляд різних способів встановлення пакунків наведено у розділі L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
Див. також I<--update>, I<--uninstall>.
=item B<--link> ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..]
-Створити символічне посилання або декілька посилань у гостьовій системі так,
-щоб вони з C<ПОСИЛАННЯ> вказували на C<ПРИЗНАЧЕННЯ>.
+Створити символічне посилання або декілька посилань у гостьовій системі так, щоб вони з C<ПОСИЛАННЯ> вказували на C<ПРИЗНАЧЕННЯ>.
=item B<--mkdir> КАТАЛОГ
Створити каталог у гостьовій системі.
-Використовується S<C<mkdir -p>>, отже буде створено усі проміжні
-каталоги. Також команда працює, якщо каталог вже існує.
+Використовується S<C<mkdir -p>>, отже буде створено усі проміжні каталоги. Також команда працює, якщо каталог вже існує.
=item B<--move> ДЖЕРЕЛО:ПРИЗНАЧЕННЯ
=item B<--no-logfile>
-Витерти C<builder.log> (файл журналу із командами збирання) з образу після
-завершення збирання. Якщо ви не хочете явним чином показувати, як було
-зібрано образ, скористайтеся цим параметром.
+Витерти C<builder.log> (файл журналу із командами збирання) з образу після завершення збирання. Якщо ви не хочете явним чином показувати, як було зібрано образ, скористайтеся цим параметром.
Див. також L</LOG FILE>.
=item B<--password> КОРИСТУВАЧ:ВАРІАНТ
-Встановити пароль для користувача C<КОРИСТУВАЧ>. (Зауважте, що за допомогою
-цього параметра I<не можна> створювати облікові записи користувачів.)
+Встановити пароль для користувача C<КОРИСТУВАЧ>. (Зауважте, що за допомогою цього параметра I<не можна> створювати облікові записи користувачів.)
-Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів
-користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
+Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
=item B<--password-crypto> md5|sha256|sha512
-Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою
-цього параметра можна встановити шифрування для цього пароля у значення
-C<md5>, C<sha256> або C<sha512>.
+Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою цього параметра можна встановити шифрування для цього пароля у значення C<md5>, C<sha256> або C<sha512>.
-Для використання значень C<sha256> та C<sha512> має бути встановлено glibc
-E<ge> 2.7 (перевірте у crypt(3) всередині гостьової системи).
+Для використання значень C<sha256> та C<sha512> має бути встановлено glibc E<ge> 2.7 (перевірте у crypt(3) всередині гостьової системи).
-C<md5> працюватиме з відносно давніми гостьовими системами Linux
-(наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
+C<md5> працюватиме з відносно давніми гостьовими системами Linux (наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
-Типовим способом шифрування є C<sha512>. Він використовується, якщо
-libguestfs вдасться виявити у гостьовій системі підтримку SHA-512. Якщо
-такої підтримки не буде виявлено, використовуватиметься C<md5>. За допомогою
-цього параметра ви можете перевизначити автоматично визначений libguestfs
-спосіб шифрування.
+Типовим способом шифрування є C<sha512>. Він використовується, якщо libguestfs вдасться виявити у гостьовій системі підтримку SHA-512. Якщо такої підтримки не буде виявлено, використовуватиметься C<md5>. За допомогою цього параметра ви можете перевизначити автоматично визначений libguestfs спосіб шифрування.
-Зауважте, що це не змінить типового шифрування, яке використовується
-гостьовою системою, коли ви створюєте у ній нові облікові записи
-користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися
-параметром I<--edit> для внесення змін до C</etc/sysconfig/authconfig>
-(Fedora, RHEL) або C</etc/pam.d/common-password> (Debian, Ubuntu).
+Зауважте, що це не змінить типового шифрування, яке використовується гостьовою системою, коли ви створюєте у ній нові облікові записи користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися параметром I<--edit> для внесення змін до C</etc/sysconfig/authconfig> (Fedora, RHEL) або C</etc/pam.d/common-password> (Debian, Ubuntu).
=item B<--root-password> ВАРІАНТ
Встановити пароль користувача root.
-Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів
-користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
+Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
-Зауваження: якщо у virt-builder ви I<не встановите> I<--root-password>, для
-гостьової системи буде використано I<випадковий> пароль root.
+Зауваження: якщо у virt-builder ви I<не встановите> I<--root-password>, для гостьової системи буде використано I<випадковий> пароль root.
=item B<--run> СКРИПТ
-Виконати скрипт оболонки (або будь-яку програму), яка називається C<СКРИПТ>
-у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій
-допоміжній системі, у пісочниці гостьової файлової системи.
+Виконати скрипт оболонки (або будь-яку програму), яка називається C<СКРИПТ> у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
Для скрипту буде автоматично використано команду chmod +x.
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли ISO), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з
-даними (I<--upload>).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли ISO), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з даними (I<--upload>).
-Можна вказати декілька параметрів I<--run>. Їх буде виконано у тому самому
-порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--run>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
Див. також I<--firstboot>, I<--attach>, I<--upload>.
=item B<--run-command> 'КОМАНДА+ПАРАМЕТРИ'
-Виконати команду із аргументами у образі диска. Команду буде виконано у
-віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової
-файлової системи.
+Виконати команду із аргументами у образі диска. Команду буде виконано у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли ISO), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з
-даними (I<--upload>).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли ISO), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з даними (I<--upload>).
-Можна вказати декілька параметрів I<--run-command>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--run-command>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
Див. також I<--firstboot>, I<--attach>, I<--upload>.
=item B<--selinux-relabel>
-Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були
-правильними з точки зору SELinux.
+Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були правильними з точки зору SELinux.
-Якщо буде використано цей параметр, програма спробує змінити мітки файлів
-негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла
-F</.autorelabel> на образі, щоб дію зі зміни міток було заплановано на
-наступне завантаження образу.
+Якщо буде використано цей параметр, програма спробує змінити мітки файлів негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла F</.autorelabel> на образі, щоб дію зі зміни міток було заплановано на наступне завантаження образу.
-Вам слід використовувати цей параметр лише для гостьових систем із
-підтримкою SELinux.
+Вам слід використовувати цей параметр лише для гостьових систем із підтримкою SELinux.
=item B<--sm-attach> ВАРІАНТ
Долучити систему до буфера передплати за допомогою C<subscription-manager>.
-Формат поля C<ВАРІАНТ> описано у розділі
-L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
+Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
=item B<--sm-credentials> ВАРІАНТ
Встановити реєстраційні дані для C<subscription-manager>.
-Формат поля C<ВАРІАНТ> описано у розділі
-L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
+Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
=item B<--sm-register>
=item B<--sm-remove>
-Вилучити усі передплати з гостьової системи за допомогою
-C<subscription-manager>.
+Вилучити усі передплати з гостьової системи за допомогою C<subscription-manager>.
=item B<--sm-unregister>
=item B<--ssh-inject> КОРИСТУВАЧ[:ВАРІАНТ]
-Вставити ключ ssh так, щоб вказаний C<КОРИСТУВАЧ> зміг увійти до системи з
-використанням ssh без потреби у визначенні пароля. Запис користувача
-C<КОРИСТУВАЧ> має вже існувати у гостьовій системі.
+Вставити ключ ssh так, щоб вказаний C<КОРИСТУВАЧ> зміг увійти до системи з використанням ssh без потреби у визначенні пароля. Запис користувача C<КОРИСТУВАЧ> має вже існувати у гостьовій системі.
Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/КЛЮЧІ SSH>.
-Ви можете додати декілька параметрів I<--ssh-inject> для різних
-користувачів, а також для додавання декількох ключів для кожного з
-користувачів.
+Ви можете додати декілька параметрів I<--ssh-inject> для різних користувачів, а також для додавання декількох ключів для кожного з користувачів.
=item B<--timezone> ЧАСОВИЙ_ПОЯС
-Встановити типовий часовий пояс гостьової системи у значення
-C<ЧАСОВИЙ_ПОЯС>. Скористайтеся рядком місця у форматі C<Europe/London>
+Встановити типовий часовий пояс гостьової системи у значення C<ЧАСОВИЙ_ПОЯС>. Скористайтеся рядком місця у форматі C<Europe/London>
=item B<--touch> ФАЙЛ
=item B<--truncate> ФАЙЛ
-Ця команда обрізає файл C<ФАЙЛ> до нульової довжини. Для її успішного
-виконання файл має існувати.
+Ця команда обрізає файл C<ФАЙЛ> до нульової довжини. Для її успішного виконання файл має існувати.
=item B<--truncate-recursive> ШЛЯХ
-Ця команда рекурсивно обрізає усі файли у каталозі C<ШЛЯХ> до нульової
-довжини.
+Ця команда рекурсивно обрізає усі файли у каталозі C<ШЛЯХ> до нульової довжини.
=item B<--uninstall> ПАКУНОК,ПАКУНОК..
-Вилучити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде вилучено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою
-виконання запиту також може бути вилучено пакунки, залежні від вилучених
-пакунків.
+Вилучити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде вилучено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою виконання запиту також може бути вилучено пакунки, залежні від вилучених пакунків.
Див. також I<--install>, I<--update>.
=item B<--update>
-Виконує еквівалент C<yum update>, C<apt-get upgrade> або якоїсь іншої
-команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні,
-до найсвіжіших версій.
+Виконує еквівалент C<yum update>, C<apt-get upgrade> або якоїсь іншої команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні, до найсвіжіших версій.
Див. також I<--install>, I<--uninstall>.
=item B<--upload> ФАЙЛ:ПРИЗНАЧЕННЯ
-Вивантажити локальний файл C<ФАЙЛ> до призначення C<ПРИЗНАЧЕННЯ> на образі
-диска. Буде збережено власника і права доступу, отже вам слід вказати такі
-значення для цих параметрів, які мають бути на остаточному образі диска.
+Вивантажити локальний файл C<ФАЙЛ> до призначення C<ПРИЗНАЧЕННЯ> на образі диска. Буде збережено власника і права доступу, отже вам слід вказати такі значення для цих параметрів, які мають бути на остаточному образі диска.
-Значенням параметра C<ПРИЗНАЧЕННЯ> може бути назва остаточного файла. Цим
-можна скористатися для перейменовування файла під час вивантаження.
+Значенням параметра C<ПРИЗНАЧЕННЯ> може бути назва остаточного файла. Цим можна скористатися для перейменовування файла під час вивантаження.
-Якщо значенням параметра C<ПРИЗНАЧЕННЯ> є назва каталогу (який вже має
-існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу,
-назву файла з локальної файлової системи буде збережено.
+Якщо значенням параметра C<ПРИЗНАЧЕННЯ> є назва каталогу (який вже має існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу, назву файла з локальної файлової системи буде збережено.
Див. також I<--mkdir>, I<--delete>, I<--scrub>.
--- /dev/null
+
+=head1 НАЗВА
+
+guestfs-tools-release-notes - guestfs tools release Notes
+
+=head1 RELEASE NOTES FOR GUESTFS TOOLS 1.48
+
+These are the release notes for guestfs tools stable release 1.48. This describes the major changes since 1.46.
+
+Guestfs tools 1.48.0 was released on B<14 March 2022>.
+
+=head2 virt-builder
+
+New templates: C<alma-8.5>, C<centosstream-8>, C<debian-11>, C<fedora-34>, C<fedora-34> (armv7l), C<fedora-35> C<fedora-35> (aarch64) (Lars Kaiser, Stef Walter).
+
+New fedora-34 (armv7l) template is built to use UEFI.
+
+=head2 virt-customize
+
+The yescrypt password hashing method is now supported (Björn Esser).
+
+=head2 virt-inspector
+
+Recognise C<kalilinux>, C<kylin> and C<msdos> operating systems / Linux distros (Laszlo Ersek).
+
+Inspection of LUKS encrypted filesystems placed directly on logical volumes is now supported, but you will need libguestfs E<ge> 1.48 (Laszlo Ersek).
+
+=head2 virt-sysprep
+
+Add a new default operation called C<net-nmconn> which removes NetworkManager connection profiles (Laszlo Ersek).
+
+=head2 virt-win-reg
+
+C<virt-win-reg --version> now prints both the version of guestfs tools and the libguestfs library that it is linked with.
+
+=head2 Common changes
+
+All OCaml tools now suppress line wrapping when output is redirected to a file (to make it easier to parse logs with external programs). There is a new I<--wrap> option which can be used to reenable line wrapping to files if needed (Laszlo Ersek).
+
+=head2 Зміни у збиранні
+
+Multiple fixes to make it easier to build against either the system installed libguestfs or a locally built libguestfs (Laszlo Ersek).
+
+Fix multiple OCaml warnings. Remove some deprecated OCaml features. We now require OCaml E<ge> 4.04.
+
+Multiple fixes to valgrind support for glibc 2.35, OCaml 4.13 and libvirt 7.7. C<make check-valgrind> should now work.
+
+=head2 Внутрішня частина роботи програми
+
+New OCaml C<On_exit> module (from libguestfs-common) is used instead of custom on-exit and signal handling.
+
+=head2 Виправлені вади
+
+=over 4
+
+=item L<https://bugzilla.redhat.com/2003706>
+
+virt-install armv7 guest on aarch64 host doesn't work, no LPAE support and no PCI devices
+
+=item L<https://bugzilla.redhat.com/1995391>
+
+RFE: virt-inspector fails to detect the distro and applications on Kylin-Desktop-V10 image
+
+=item L<https://bugzilla.redhat.com/1980922>
+
+virt-sysprep doesn't cleanup NetworkManager connection files
+
+=item L<https://bugzilla.redhat.com/1961160>
+
+The version is incorrect when running 'virt-win-reg --version'
+
+=item L<https://bugzilla.redhat.com/1820221>
+
+Log lines wrapping make log parsing difficult
+
+=item L<https://bugzilla.redhat.com/1658126>
+
+Virt-v2v can't convert guest using LUKS-on-LV
+
+=item L<https://bugzilla.redhat.com/1633328>
+
+Armv7 guest fails to boot with qemu-3.0.0-1
+
+=back
+
+=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
+
+L<http://libguestfs.org/>
+
+=head1 АВТОРИ
+
+=begin коментар
+
+git shortlog -s v1.46.0..
+
+=end коментар
+
+=over 4
+
+=item Björn Esser
+
+=item Lars Kaiser
+
+=item Laszlo Ersek
+
+=item Richard W.M. Jones
+
+=item Stef Walter
+
+=back
+
+=head1 АВТОРСЬКІ ПРАВА
+
+Copyright (C) 2009-2022 Red Hat Inc.
+
=item B<--key> ВАРІАНТ
-Specify a key for LUKS, to automatically open a LUKS device when using the
-inspection. C<ID> can be either the libguestfs device name, or the UUID of
-the LUKS device.
+Specify a key for LUKS, to automatically open a LUKS device when using the inspection. C<ID> can be either the libguestfs device name, or the UUID of the LUKS device.
=over 4
=item B<--keys-from-stdin>
-Прочитати параметри ключа або пароля із джерела стандартного
-введення. Типово програма намагається читати паролі від користувача
-відкриттям F</dev/tty>.
+Прочитати параметри ключа або пароля із джерела стандартного введення. Типово програма намагається читати паролі від користувача відкриттям F</dev/tty>.
-If there are multiple encrypted devices then you may need to supply multiple
-keys on stdin, one per line.
+If there are multiple encrypted devices then you may need to supply multiple keys on stdin, one per line.
=item B<--append-line> ФАЙЛ:РЯДОК (див. C<customize> нижче)
-Дописати один рядок тексту до файла C<ФАЙЛ>. Якщо файл ще не завершується
-порожнім рядком, такий рядок буде додано перед дописаним. Крім того,
-автоматично буде дописано символ нового рядка наприкінці рядка C<РЯДОК>.
+Дописати один рядок тексту до файла C<ФАЙЛ>. Якщо файл ще не завершується порожнім рядком, такий рядок буде додано перед дописаним. Крім того, автоматично буде дописано символ нового рядка наприкінці рядка C<РЯДОК>.
-Наприклад, (припускаємо, що у командній оболонці використовуються звичайні
-лапки) така команда:
+Наприклад, (припускаємо, що у командній оболонці використовуються звичайні лапки) така команда:
--append-line '/etc/hosts:10.0.0.1 foo'
-додасть C<10.0.0.1 foo⏎> або C<⏎10.0.0.1 foo⏎> до файла; останній запис буде
-додано, лише якщо наявний файл ще не закінчується символом нового рядка.
+додасть C<10.0.0.1 foo⏎> або C<⏎10.0.0.1 foo⏎> до файла; останній запис буде додано, лише якщо наявний файл ще не закінчується символом нового рядка.
-C<⏎> позначає символ нового рядка, конкретне значення якого визначається за
-наявним вмістом файла, отже, команда обробляє файли однаково правильно для
-варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для
-порожніх і ще не створених файлів.
+C<⏎> позначає символ нового рядка, конкретне значення якого визначається за наявним вмістом файла, отже, команда обробляє файли однаково правильно для варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для порожніх і ще не створених файлів.
-Щоб додати декілька рядків, скористайтеся тим самим параметром декілька
-разів:
+Щоб додати декілька рядків, скористайтеся тим самим параметром декілька разів:
--append-line '/etc/hosts:10.0.0.1 foo'
--append-line '/etc/hosts:10.0.0.2 bar'
-Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою
-конструкцією:
+Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою конструкцією:
--append-line '/etc/hosts:'
--append-line '/etc/hosts:10.0.0.1 foo'
Змінити права доступу до файла C<ФАЙЛ> на C<ПРАВА_ДОСТУПУ>.
-I<Зауваження>: типово C<ПРАВА_ДОСТУПУ> записуються у десятковому форматі,
-якщо ви не додасте початковий C<0> , щоб вказати вісімкове число, тобто
-скористаєтеся C<0700>, а не C<700>.
+I<Зауваження>: типово C<ПРАВА_ДОСТУПУ> записуються у десятковому форматі, якщо ви не додасте початковий C<0> , щоб вказати вісімкове число, тобто скористаєтеся C<0700>, а не C<700>.
=item B<--commands-from-file> НАЗВА_ФАЙЛА (див. C<customize> нижче)
-Прочитати команди налаштовування з файла, по одній (разом із аргументами) на
-рядок.
+Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.
Кожен рядок містить команду налаштовування та її аргументи, наприклад:
install якийсь_пакунок
password якийсь-користувач:password:його-новий-пароль
-Порожні рядки ігноруються, а рядки, що починаються з C<#>, є коментарями і
-також ігноруються. Крім того, аргументи можна розділити на декілька рядків
-додаванням C<\> (символу продовження) наприкінці рядка. Приклад:
+Порожні рядки ігноруються, а рядки, що починаються з C<#>, є коментарями і також ігноруються. Крім того, аргументи можна розділити на декілька рядків додаванням C<\> (символу продовження) наприкінці рядка. Приклад:
edit /якийсь/файл:\
s/^OPT=.*/OPT=ok/
-Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так,
-наче їх вказано як I<--delete /якийсь/файл> у рядку команди.
+Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так, наче їх вказано як I<--delete /якийсь/файл> у рядку команди.
=item B<--copy> ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. C<customize> нижче)
=item B<--copy-in> ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ (див. C<customize> нижче)
-Скопіювати локальні файли або каталоги рекурсивно до образу диска,
-розташувавши його у каталозі C<ВІДДАЛЕНИЙ_КАТАЛОГ> (який має існувати).
+Скопіювати локальні файли або каталоги рекурсивно до образу диска, розташувавши його у каталозі C<ВІДДАЛЕНИЙ_КАТАЛОГ> (який має існувати).
Не можна використовувати символи-замінники.
=item B<--delete> ШЛЯХ (див. C<customize> нижче)
-Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
-рекурсивно).
+Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст, рекурсивно).
-Ви можете скористатися символами-замінниками у вказаному шляху. Не забудьте
-екранувати символи-замінники у командній оболонці основної системи, якщо це
-потрібно. Приклад:
+Ви можете скористатися символами-замінниками у вказаному шляху. Не забудьте екранувати символи-замінники у командній оболонці основної системи, якщо це потрібно. Приклад:
virt-customize --delete '/var/log/*.log'.
Редагувати C<ФАЙЛ> з використанням виразу Perl C<ВИРАЗ>.
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
Див. L<virt-edit(1)/NON-INTERACTIVE EDITING>.
=item B<--firstboot> СКРИПТ (див. C<customize> нижче)
-Встановити C<СКРИПТ> у гостьовій системі і запустити його під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Встановити C<СКРИПТ> у гостьовій системі і запустити його під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
-До скрипту, після встановлення до гостьової системи, буде автоматично
-застосовано команду chmod +x.
+До скрипту, після встановлення до гостьової системи, буде автоматично застосовано команду chmod +x.
-Альтернативна версія I<--firstboot-command> є такою самою, але зручно
-включає команду у однорядковому скрипті.
+Альтернативна версія I<--firstboot-command> є такою самою, але зручно включає команду у однорядковому скрипті.
-Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
-Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
Див. також I<--run>.
=item B<--firstboot-command> 'КОМАНДА+ПАРАМЕТРИ' (див. C<customize> нижче)
-Виконати команду (разом із аргументами) у гостьовій системі під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Виконати команду (разом із аргументами) у гостьовій системі під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
-Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--firstboot>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
-Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу L<virt-builder(1)/СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ>, щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
Див. також I<--run>.
=item B<--firstboot-install> ПАКУНОК,ПАКУНОК... (див. C<customize> нижче)
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час першого завантаження гостьової системи за
-допомогою програми для керування пакунків гостьової системи (наприклад, apt,
-yum тощо) і з'єднання із мережею гостьової системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час першого завантаження гостьової системи за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею гостьової системи.
-Огляд різних способів встановлення пакунків наведено у розділі
-L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
+Огляд різних способів встановлення пакунків наведено у розділі L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
=item B<--hostname> НАЗВА_ВУЗЛА (див. C<customize> нижче)
-Встановити як назву вузла гостьової системи значення C<НАЗВА_ВУЗЛА>. Якщо
-потрібно, можете скористатися форматом із крапкою,
-«назва_вузла.назва_домену» (FQDN).
+Встановити як назву вузла гостьової системи значення C<НАЗВА_ВУЗЛА>. Якщо потрібно, можете скористатися форматом із крапкою, «назва_вузла.назва_домену» (FQDN).
=item B<--install> ПАКУНОК,ПАКУНОК... (див. C<customize> нижче)
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання
-із мережею основної системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею основної системи.
-Огляд різних способів встановлення пакунків наведено у розділі
-L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
+Огляд різних способів встановлення пакунків наведено у розділі L<virt-builder(1)/ВСТАНОВЛЕННЯ ПАКУНКІВ>.
Див. також I<--update>, I<--uninstall>.
=item B<--keep-user-accounts> КОРИСТУВАЧІ (див. C<user-account> нижче)
-Облікові записи користувачів, які слід залишити у гостьовій
-системі. Значенням цього параметра є список імен користувачів, відокремлених
-комами, який визначатиме ті записи, які слід зберегти. Приклад:
+Облікові записи користувачів, які слід залишити у гостьовій системі. Значенням цього параметра є список імен користувачів, відокремлених комами, який визначатиме ті записи, які слід зберегти. Приклад:
--keep-user-accounts mary
=item B<--link> ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..] (див. C<customize> нижче)
-Створити символічне посилання або декілька посилань у гостьовій системі так,
-щоб вони з C<ПОСИЛАННЯ> вказували на C<ПРИЗНАЧЕННЯ>.
+Створити символічне посилання або декілька посилань у гостьовій системі так, щоб вони з C<ПОСИЛАННЯ> вказували на C<ПРИЗНАЧЕННЯ>.
=item B<--mkdir> КАТАЛОГ (див. C<customize> нижче)
Створити каталог у гостьовій системі.
-Використовується S<C<mkdir -p>>, отже буде створено усі проміжні
-каталоги. Також команда працює, якщо каталог вже існує.
+Використовується S<C<mkdir -p>>, отже буде створено усі проміжні каталоги. Також команда працює, якщо каталог вже існує.
=item B<--move> ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. C<customize> нижче)
=item B<--no-logfile> (див. C<customize> нижче)
-Витерти C<builder.log> (файл журналу із командами збирання) з образу після
-завершення збирання. Якщо ви не хочете явним чином показувати, як було
-зібрано образ, скористайтеся цим параметром.
+Витерти C<builder.log> (файл журналу із командами збирання) з образу після завершення збирання. Якщо ви не хочете явним чином показувати, як було зібрано образ, скористайтеся цим параметром.
Див. також L</LOG FILE>.
=item B<--password> КОРИСТУВАЧ:ВАРІАНТ (див. C<customize> нижче)
-Встановити пароль для користувача C<КОРИСТУВАЧ>. (Зауважте, що за допомогою
-цього параметра I<не можна> створювати облікові записи користувачів.)
+Встановити пароль для користувача C<КОРИСТУВАЧ>. (Зауважте, що за допомогою цього параметра I<не можна> створювати облікові записи користувачів.)
-Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів
-користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
+Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
=item B<--password-crypto> md5|sha256|sha512 (див. C<customize> нижче)
-Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою
-цього параметра можна встановити шифрування для цього пароля у значення
-C<md5>, C<sha256> або C<sha512>.
+Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою цього параметра можна встановити шифрування для цього пароля у значення C<md5>, C<sha256> або C<sha512>.
-Для використання значень C<sha256> та C<sha512> має бути встановлено glibc
-E<ge> 2.7 (перевірте у crypt(3) всередині гостьової системи).
+Для використання значень C<sha256> та C<sha512> має бути встановлено glibc E<ge> 2.7 (перевірте у crypt(3) всередині гостьової системи).
-C<md5> працюватиме з відносно давніми гостьовими системами Linux
-(наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
+C<md5> працюватиме з відносно давніми гостьовими системами Linux (наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
-Типовим способом шифрування є C<sha512>. Він використовується, якщо
-libguestfs вдасться виявити у гостьовій системі підтримку SHA-512. Якщо
-такої підтримки не буде виявлено, використовуватиметься C<md5>. За допомогою
-цього параметра ви можете перевизначити автоматично визначений libguestfs
-спосіб шифрування.
+Типовим способом шифрування є C<sha512>. Він використовується, якщо libguestfs вдасться виявити у гостьовій системі підтримку SHA-512. Якщо такої підтримки не буде виявлено, використовуватиметься C<md5>. За допомогою цього параметра ви можете перевизначити автоматично визначений libguestfs спосіб шифрування.
-Зауважте, що це не змінить типового шифрування, яке використовується
-гостьовою системою, коли ви створюєте у ній нові облікові записи
-користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися
-параметром I<--edit> для внесення змін до C</etc/sysconfig/authconfig>
-(Fedora, RHEL) або C</etc/pam.d/common-password> (Debian, Ubuntu).
+Зауважте, що це не змінить типового шифрування, яке використовується гостьовою системою, коли ви створюєте у ній нові облікові записи користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися параметром I<--edit> для внесення змін до C</etc/sysconfig/authconfig> (Fedora, RHEL) або C</etc/pam.d/common-password> (Debian, Ubuntu).
=item B<--remove-user-accounts> КОРИСТУВАЧІ (див. C<user-account> нижче)
-Облікові записи користувачів, які слід вилучити з гостьової
-системи. Значенням цього параметра є список імен користувачів, відокремлених
-комами, який визначатиме ті записи, які слід вилучити. Приклад:
+Облікові записи користувачів, які слід вилучити з гостьової системи. Значенням цього параметра є список імен користувачів, відокремлених комами, який визначатиме ті записи, які слід вилучити. Приклад:
--remove-user-accounts bob,eve
Встановити пароль користувача root.
-Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів
-користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
+Формат поля C<ВАРІАНТ> та способи налаштовування облікових записів користувачів описано у розділі L<virt-builder(1)/КОРИСТУВАЧІ І ПАРОЛІ>.
-Зауваження: якщо у virt-builder ви I<не встановите> I<--root-password>, для
-гостьової системи буде використано I<випадковий> пароль root.
+Зауваження: якщо у virt-builder ви I<не встановите> I<--root-password>, для гостьової системи буде використано I<випадковий> пароль root.
=item B<--run> СКРИПТ (див. C<customize> нижче)
-Виконати скрипт оболонки (або будь-яку програму), яка називається C<СКРИПТ>
-у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій
-допоміжній системі, у пісочниці гостьової файлової системи.
+Виконати скрипт оболонки (або будь-яку програму), яка називається C<СКРИПТ> у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
Для скрипту буде автоматично використано команду chmod +x.
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли ISO), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з
-даними (I<--upload>).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли ISO), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з даними (I<--upload>).
-Можна вказати декілька параметрів I<--run>. Їх буде виконано у тому самому
-порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--run>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
Див. також I<--firstboot>, I<--attach>, I<--upload>.
=item B<--run-command> 'КОМАНДА+ПАРАМЕТРИ' (див. C<customize> нижче)
-Виконати команду із аргументами у образі диска. Команду буде виконано у
-віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової
-файлової системи.
+Виконати команду із аргументами у образі диска. Команду буде виконано у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли ISO), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з
-даними (I<--upload>).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли ISO), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (I<--attach>). Також ви можете вивантажувати файли з даними (I<--upload>).
-Можна вказати декілька параметрів I<--run-command>. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів I<--run-command>. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
Див. також I<--firstboot>, I<--attach>, I<--upload>.
=item B<--script> СКРИПТ (див. C<script> нижче)
-Запустити вказаний C<СКРИПТ> (скрипт оболонки або програму) над
-гостьовою системою. Скриптом може бути будь-яка програма у
-основній системі. Поточним каталогом скрипту буде кореневий
-каталог гостьової системи.
+Запустити вказаний C<СКРИПТ> (скрипт оболонки або програму) над гостьовою системою. Скриптом може бути будь-яка програма у основній системі. Поточним каталогом скрипту буде кореневий каталог гостьової системи.
-B<Нотатка:> якщо скрипт не перебуває у каталозі $PATH, вам слід вказати шлях
-до скрипту повністю.
+B<Нотатка:> якщо скрипт не перебуває у каталозі $PATH, вам слід вказати шлях до скрипту повністю.
=item B<--scriptdir> КАТАЛОГ_СКРИПТІВ (див. C<script> нижче)
-Точку монтування (порожній каталог на вузлі), використану при виконанні дії
-C<script>, увімкнено і вказано використання одного або декількох скриптів за
-допомогою I<--script>.
+Точку монтування (порожній каталог на вузлі), використану при виконанні дії C<script>, увімкнено і вказано використання одного або декількох скриптів за допомогою I<--script>.
B<Зауваження:> C<SCRIPTDIR> B<має> бути вказано повністю.
=item B<--selinux-relabel> (див. C<customize> нижче)
-Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були
-правильними з точки зору SELinux.
+Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були правильними з точки зору SELinux.
-Якщо буде використано цей параметр, програма спробує змінити мітки файлів
-негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла
-F</.autorelabel> на образі, щоб дію зі зміни міток було заплановано на
-наступне завантаження образу.
+Якщо буде використано цей параметр, програма спробує змінити мітки файлів негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла F</.autorelabel> на образі, щоб дію зі зміни міток було заплановано на наступне завантаження образу.
-Вам слід використовувати цей параметр лише для гостьових систем із
-підтримкою SELinux.
+Вам слід використовувати цей параметр лише для гостьових систем із підтримкою SELinux.
=item B<--sm-attach> ВАРІАНТ (див. C<customize> нижче)
Долучити систему до буфера передплати за допомогою C<subscription-manager>.
-Формат поля C<ВАРІАНТ> описано у розділі
-L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
+Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
=item B<--sm-credentials> ВАРІАНТ (див. C<customize> нижче)
Встановити реєстраційні дані для C<subscription-manager>.
-Формат поля C<ВАРІАНТ> описано у розділі
-L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
+Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/SUBSCRIPTION-MANAGER>.
=item B<--sm-register> (див. C<customize> нижче)
=item B<--sm-remove> (див. C<customize> нижче)
-Вилучити усі передплати з гостьової системи за допомогою
-C<subscription-manager>.
+Вилучити усі передплати з гостьової системи за допомогою C<subscription-manager>.
=item B<--sm-unregister> (див. C<customize> нижче)
=item B<--ssh-inject> КОРИСТУВАЧ[:ВАРІАНТ] (див. C<customize> нижче)
-Вставити ключ ssh так, щоб вказаний C<КОРИСТУВАЧ> зміг увійти до системи з
-використанням ssh без потреби у визначенні пароля. Запис користувача
-C<КОРИСТУВАЧ> має вже існувати у гостьовій системі.
+Вставити ключ ssh так, щоб вказаний C<КОРИСТУВАЧ> зміг увійти до системи з використанням ssh без потреби у визначенні пароля. Запис користувача C<КОРИСТУВАЧ> має вже існувати у гостьовій системі.
Формат поля C<ВАРІАНТ> описано у розділі L<virt-builder(1)/КЛЮЧІ SSH>.
-Ви можете додати декілька параметрів I<--ssh-inject> для різних
-користувачів, а також для додавання декількох ключів для кожного з
-користувачів.
+Ви можете додати декілька параметрів I<--ssh-inject> для різних користувачів, а також для додавання декількох ключів для кожного з користувачів.
=item B<--timezone> ЧАСОВИЙ_ПОЯС (див. C<customize> нижче)
-Встановити типовий часовий пояс гостьової системи у значення
-C<ЧАСОВИЙ_ПОЯС>. Скористайтеся рядком місця у форматі C<Europe/London>
+Встановити типовий часовий пояс гостьової системи у значення C<ЧАСОВИЙ_ПОЯС>. Скористайтеся рядком місця у форматі C<Europe/London>
=item B<--touch> ФАЙЛ (див. C<customize> нижче)
=item B<--truncate> ФАЙЛ (див. C<customize> нижче)
-Ця команда обрізає файл C<ФАЙЛ> до нульової довжини. Для її успішного
-виконання файл має існувати.
+Ця команда обрізає файл C<ФАЙЛ> до нульової довжини. Для її успішного виконання файл має існувати.
=item B<--truncate-recursive> ШЛЯХ (див. C<customize> нижче)
-Ця команда рекурсивно обрізає усі файли у каталозі C<ШЛЯХ> до нульової
-довжини.
+Ця команда рекурсивно обрізає усі файли у каталозі C<ШЛЯХ> до нульової довжини.
=item B<--uninstall> ПАКУНОК,ПАКУНОК... (див. C<customize> нижче)
-Вилучити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде вилучено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою
-виконання запиту також може бути вилучено пакунки, залежні від вилучених
-пакунків.
+Вилучити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде вилучено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою виконання запиту також може бути вилучено пакунки, залежні від вилучених пакунків.
Див. також I<--install>, I<--update>.
=item B<--update> (див. C<customize> нижче)
-Виконує еквівалент C<yum update>, C<apt-get upgrade> або якоїсь іншої
-команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні,
-до найсвіжіших версій.
+Виконує еквівалент C<yum update>, C<apt-get upgrade> або якоїсь іншої команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні, до найсвіжіших версій.
Див. також I<--install>, I<--uninstall>.
=item B<--upload> ФАЙЛ:ПРИЗНАЧЕННЯ (див. C<customize> нижче)
-Вивантажити локальний файл C<ФАЙЛ> до призначення C<ПРИЗНАЧЕННЯ> на образі
-диска. Буде збережено власника і права доступу, отже вам слід вказати такі
-значення для цих параметрів, які мають бути на остаточному образі диска.
+Вивантажити локальний файл C<ФАЙЛ> до призначення C<ПРИЗНАЧЕННЯ> на образі диска. Буде збережено власника і права доступу, отже вам слід вказати такі значення для цих параметрів, які мають бути на остаточному образі диска.
-Значенням параметра C<ПРИЗНАЧЕННЯ> може бути назва остаточного файла. Цим
-можна скористатися для перейменовування файла під час вивантаження.
+Значенням параметра C<ПРИЗНАЧЕННЯ> може бути назва остаточного файла. Цим можна скористатися для перейменовування файла під час вивантаження.
-Якщо значенням параметра C<ПРИЗНАЧЕННЯ> є назва каталогу (який вже має
-існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу,
-назву файла з локальної файлової системи буде збережено.
+Якщо значенням параметра C<ПРИЗНАЧЕННЯ> є назва каталогу (який вже має існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу, назву файла з локальної файлової системи буде збережено.
Див. також I<--mkdir>, I<--delete>, I<--scrub>.
Вилучити файли резервних копій редактора з гостьової системи.
-Вказані нижче файли буде вилучено з усіх каталогів файлової системи
-гостьової операційної системи:
+Вказані нижче файли буде вилучено з усіх каталогів файлової системи гостьової операційної системи:
=over 4
=back
-У операційних системах Linux та Unix оброблятимуться лише такі файлові
-системи:
+У операційних системах Linux та Unix оброблятимуться лише такі файлові системи:
=over 4
Вилучити журнал команд bash у гостьовій системі.
-Вилучити журнал команд bash користувача «root» та всіх інших користувачів, у
-домашніх каталогах яких містяться файли C<.bash_history>.
+Вилучити журнал команд bash користувача «root» та всіх інших користувачів, у домашніх каталогах яких містяться файли C<.bash_history>.
=head3 Нотатки щодо журналу команд bash
-У поточній версії пошук домашніх каталогів користувачів виконується лише у
-C</root> і C</home/*>. Отже, журнал bash користувачів, дані яких
-зберігаються у інших каталогах, не буде вилучено.
+У поточній версії пошук домашніх каталогів користувачів виконується лише у C</root> і C</home/*>. Отже, журнал bash користувачів, дані яких зберігаються у інших каталогах, не буде вилучено.
=head2 B<blkid-tab> *
Налаштувати гостьову систему.
-Налаштувати гостьову систему визначенням параметрів L<virt-customize(1)> для
-встановлення пакунків, редагування файлів тощо.
+Налаштувати гостьову систему визначенням параметрів L<virt-customize(1)> для встановлення пакунків, редагування файлів тощо.
=head2 B<dhcp-client-state> *
Вилучити правила брандмауера.
-Вилучає нетипові правила брандмауера вилученням C</etc/sysconfig/iptables>
-або нетипових налаштувань firewalld з C</etc/firewalld/*/*>.
+Вилучає нетипові правила брандмауера вилученням C</etc/sysconfig/iptables> або нетипових налаштувань firewalld з C</etc/firewalld/*/*>.
-Зауважте, що цю можливість типово I<не> увімкнено, оскільки може відкрити
-гостьову систему для вразливостей. Користуйтеся обережно.
+Зауважте, що цю можливість типово I<не> увімкнено, оскільки може відкрити гостьову систему для вразливостей. Користуйтеся обережно.
=head2 B<flag-reconfiguration>
Позначити систему для зміни налаштувань.
-Для гостьових систем Linux оновлює часову позначку C</.unconfigured>, отже,
-під час першого завантаження користувачеві буде надіслано запит щодо
-параметрів, зокрема пароля root та часового поясу.
+Для гостьових систем Linux оновлює часову позначку C</.unconfigured>, отже, під час першого завантаження користувачеві буде надіслано запит щодо параметрів, зокрема пароля root та часового поясу.
=head2 B<fs-uuids>
Змінити UUID файлових систем.
-У гостьових системах та типах файлових систем, де передбачено таку
-підтримку, буде створено нові випадкові UUID, які буде пов’язано з файловими
-системами.
+У гостьових системах та типах файлових систем, де передбачено таку підтримку, буде створено нові випадкові UUID, які буде пов’язано з файловими системами.
=head3 Зауваження щодо fs-uuids
-Типово, дію fs-uuids вимкнено, оскільки у поточній версії програма ще не
-здатна знайти і оновити усі записи у гостьовій системі, які використовують
-UUID, наприклад C</etc/fstab> або завантажувач. Вмикання цієї дії може з
-високою ймовірністю зробити вашу гостьову систему непридатною до
-завантаження.
+Типово, дію fs-uuids вимкнено, оскільки у поточній версії програма ще не здатна знайти і оновити усі записи у гостьовій системі, які використовують UUID, наприклад C</etc/fstab> або завантажувач. Вмикання цієї дії може з високою ймовірністю зробити вашу гостьову систему непридатною до завантаження.
Див. L<https://bugzilla.redhat.com/show_bug.cgi?id=991641>
Remove the IPA files.
-Remove all the files related to an IPA (Identity, Policy, Audit) system.
-This effectively unenrolls the guest from an IPA server without interacting
-with it.
+Remove all the files related to an IPA (Identity, Policy, Audit) system. This effectively unenrolls the guest from an IPA server without interacting with it.
This operation does not run C<ipa-client>.
Змінити UUID ФТ і ГТ LVM2.
-Для гостьових систем Linux, які містять фізичні томи (ФТ) або групи томів
-(ГТ) LVM2 для ФТ і ГТ буде створено і призначено випадкові UUID.
+Для гостьових систем Linux, які містять фізичні томи (ФТ) або групи томів (ГТ) LVM2 для ФТ і ГТ буде створено і призначено випадкові UUID.
=head2 B<ід-комп’ютера> *
Вилучити ідентифікатор локального комп’ютера.
-Зазвичай, ідентифікатор системи створюється на основі випадкових джерел
-даних під час встановлення системи і не змінюється під час всіх наступних її
-завантажень. За потреби у системах без певного стану цей ідентифікатор
-створюється під час роботи завантажувача,
-якщо буде виявлено порожнє значення.
+Зазвичай, ідентифікатор системи створюється на основі випадкових джерел даних під час встановлення системи і не змінюється під час всіх наступних її завантажень. За потреби у системах без певного стану цей ідентифікатор створюється під час роботи завантажувача, якщо буде виявлено порожнє значення.
=head2 B<mail-spool> *
Для Fedora і Red Hat Enterprise Linux це вилучається з файлів C<ifcfg-*>.
+=head2 B<net-nmconn> *
+
+Remove system-local NetworkManager connection profiles (keyfiles).
+
+On Fedora and Red Hat Enterprise Linux, remove the C</etc/NetworkManager/system-connections/*.nmconnection> files.
+
=head2 B<pacct-log> *
Вилучити файли журналу обліку процесів.
-Дані обліку процесів системи будуть зберігатися у файлах журналу pacct, якщо
-увімкнено облік процесів.
+Дані обліку процесів системи будуть зберігатися у файлах журналу pacct, якщо увімкнено облік процесів.
=head2 B<package-manager-cache> *
Вилучити специфічні для системи файли баз даних RPM.
-Вилучити специфічні для системи файли баз даних RPM. RPM буде повторно
-створено ці файли, якщо це потрібно.
+Вилучити специфічні для системи файли баз даних RPM. RPM буде повторно створено ці файли, якщо це потрібно.
=head2 B<samba-db-log> *
Запустити довільні скрипти дій над гостьовою системою.
-Модуль C<script> надає вам змогу запускати довільні скрипти оболонки або
-програми для обробки гостьових систем.
+Модуль C<script> надає вам змогу запускати довільні скрипти оболонки або програми для обробки гостьових систем.
-Зауважте, що використання цієї можливості потребує підтримки FUSE. Вам варто
-увімкнути цю підтримку у вашій основній системі, наприклад, додаванням
-поточного користувача до групи C<fuse> або завантаженням модуля ядра.
+Зауважте, що використання цієї можливості потребує підтримки FUSE. Вам варто увімкнути цю підтримку у вашій основній системі, наприклад, додаванням поточного користувача до групи C<fuse> або завантаженням модуля ядра.
-Скористайтеся одним або декількома параметрами I<--script> для визначення
-скриптів або програм, які слід запустити для обробки гостьової системи.
+Скористайтеся одним або декількома параметрами I<--script> для визначення скриптів або програм, які слід запустити для обробки гостьової системи.
-Скрипт або програма виконується з поточним каталогом, який є кореневим
-каталогом гостьової системи, отже слід використовувати відносні
-шляхи. Приклад: C<rm etc/resolv.conf> у скрипті призведе до вилучення файла
-налаштувань DNS у гостьовій системі Linux, а C<rm /etc/resolv.conf>
-(спробує) вилучити відповідний файл у основній системі.
+Скрипт або програма виконується з поточним каталогом, який є кореневим каталогом гостьової системи, отже слід використовувати відносні шляхи. Приклад: C<rm etc/resolv.conf> у скрипті призведе до вилучення файла налаштувань DNS у гостьовій системі Linux, а C<rm /etc/resolv.conf> (спробує) вилучити відповідний файл у основній системі.
-Зазвичай, використовується тимчасова точка монтування гостьової системи, але
-ви можете вибрати якусь іншу за допомогою параметра I<--scriptdir>.
+Зазвичай, використовується тимчасова точка монтування гостьової системи, але ви можете вибрати якусь іншу за допомогою параметра I<--scriptdir>.
-B<Зауваження:> описані тут скрипти відрізняються від скриптів I<--firstboot>
-(скриптів, які виконуються у контексті гостьової системи під час першого
-завантаження цієї системи). Скрипти I<--script> запускаються у основній
-системі, а не у гостьовій.
+B<Зауваження:> описані тут скрипти відрізняються від скриптів I<--firstboot> (скриптів, які виконуються у контексті гостьової системи під час першого завантаження цієї системи). Скрипти I<--script> запускаються у основній системі, а не у гостьовій.
=head2 B<smolt-uuid> *
Вилучити ключі вузла SSH у гостьовій системі.
-Ключі вузла SSH повторно створюються (незалежно) під час наступного
-завантаження гостьової системи.
+Ключі вузла SSH повторно створюються (незалежно) під час наступного завантаження гостьової системи.
-Якщо після клонування гостьова система отримати ту саму IP-адресу, ssh
-надасть вам додаткове попередження щодо зміни ключа вузла:
+Якщо після клонування гостьова система отримати ту саму IP-адресу, ssh надасть вам додаткове попередження щодо зміни ключа вузла:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
Вилучити каталоги «.ssh» у гостьовій системі.
-Вилучити каталог C<.ssh> користувача «root» та всіх інших користувачів,
-домашні каталоги яких містять каталог C<.ssh>.
+Вилучити каталог C<.ssh> користувача «root» та всіх інших користувачів, домашні каталоги яких містять каталог C<.ssh>.
=head3 Зауваження щодо ssh-userdir
-У поточній версії пошук домашніх каталогів користувачів виконується лише у
-C</root> і C</home/*>. Отже, файли ssh користувачів, дані яких зберігаються
-у інших каталогах, не буде вилучено.
+У поточній версії пошук домашніх каталогів користувачів виконується лише у C</root> і C</home/*>. Отже, файли ssh користувачів, дані яких зберігаються у інших каталогах, не буде вилучено.
=head2 B<sssd-db-log> *
Вилучити постійні правила мережі udev.
-Вилучити постійні правила мережі udev, які відображають вже створену
-MAC-адресу гостьової системи на фіксований пристрій ethernet (наприклад
-eth0).
+Вилучити постійні правила мережі udev, які відображають вже створену MAC-адресу гостьової системи на фіксований пристрій ethernet (наприклад eth0).
-Після клонування гостьової системи MAC-адреса зазвичай змінюється. Оскільки
-стару MAC-адресу вже пов’язано зі старою назвою (наприклад eth0), це
-означає, що нову MAC-адресу буде пов’язано з новою назвою (наприклад eth1),
-а це зазвичай є небажаним. За допомогою вилучення постійних правил мережі
-udev цьому можна запобігти.
+Після клонування гостьової системи MAC-адреса зазвичай змінюється. Оскільки стару MAC-адресу вже пов’язано зі старою назвою (наприклад eth0), це означає, що нову MAC-адресу буде пов’язано з новою назвою (наприклад eth1), а це зазвичай є небажаним. За допомогою вилучення постійних правил мережі udev цьому можна запобігти.
=head2 B<user-account>
Вилучити облікові записи користувачів у гостьовій системі.
-Типово вилучити всі облікові записи користувачів та відповідні домашні
-каталоги. Обліковий запис «root» вилучено не буде.
+Типово вилучити всі облікові записи користувачів та відповідні домашні каталоги. Обліковий запис «root» вилучено не буде.
-Див. опис параметра I<--remove-user-accounts>, щоб дізнатися про те, як
-наказати
-програмі вилучити лише деяких з користувачів і не вилучати інших.
+Див. опис параметра I<--remove-user-accounts>, щоб дізнатися про те, як наказати програмі вилучити лише деяких з користувачів і не вилучати інших.
=head2 B<utmp> *
Вилучити файл utmp.
-У цьому файлі зберігаються записи щодо входу користувачів до машини. У
-сучасних дистрибутивах Linux ці записи зберігаються на диску у пам’яті, тому
-не є частиною віртуальної машини на диску, але ці дані зберігаються на диску
-у старіших версіях дистрибутивів.
+У цьому файлі зберігаються записи щодо входу користувачів до машини. У сучасних дистрибутивах Linux ці записи зберігаються на диску у пам’яті, тому не є частиною віртуальної машини на диску, але ці дані зберігаються на диску у старіших версіях дистрибутивів.
=head2 B<yum-uuid> *
Вилучити UUID yum.
-Yum створить новий UUID під час наступного запуску, коли виявить, що
-початковий UUID було вилучено.
+Yum створить новий UUID під час наступного запуску, коли виявить, що початковий UUID було вилучено.
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-alignment-scan 1"
-.TH virt-alignment-scan 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-alignment-scan 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Під час встановлення застарілих операційних систем засоби розподілу диска
-можуть розташувати розділ на секторі з помилковим вирівнюванням відносно
-системи зберігання даних (типово, перший розділ починається з сектора
-\&\f(CW63\fR). Розділи з помилковим вирівнюванням можуть призвести до неоптимальної
-кількості запитів щодо виведення та введення даних від операційної системи.
+Під час встановлення застарілих операційних систем засоби розподілу диска можуть розташувати розділ на секторі з помилковим вирівнюванням відносно системи зберігання даних (типово, перший розділ починається з сектора \f(CW63\fR). Розділи з помилковим вирівнюванням можуть призвести до неоптимальної кількості запитів щодо виведення та введення даних від операційної системи.
.PP
-Програма virt-alignment-scan виконує перевірку вирівнювання розділів у
-віртуальних машинах та образів дисків і повідомляє вам, якщо буде виявлено
-помилки вирівнювання.
+Програма virt-alignment-scan виконує перевірку вирівнювання розділів у віртуальних машинах та образів дисків і повідомляє вам, якщо буде виявлено помилки вирівнювання.
.PP
-У поточній версії не передбачено програми для виправлення помилок,
-пов’язаних з вирівнюванням. Ви можете лише перевстановити гостьову
-операційну систему. У цьому документі можна знайти короткі описи помилок та
-можливі шляхи усування цих помилок:
-http://media.netapp.com/documents/tr\-3747.pdf
+У поточній версії не передбачено програми для виправлення помилок, пов’язаних з вирівнюванням. Ви можете лише перевстановити гостьову операційну систему. У цьому документі можна знайти короткі описи помилок та можливі шляхи усування цих помилок: http://media.netapp.com/documents/tr\-3747.pdf
.SH "ВИВЕДЕННЯ"
.IX Header "ВИВЕДЕННЯ"
-Щоб запустити цю програму безпосередньо для образу диска, скористайтеся
-параметром \fI\-a\fR:
+Щоб запустити цю програму безпосередньо для образу диска, скористайтеся параметром \fI\-a\fR:
.PP
.Vb 2
\& $ virt\-alignment\-scan \-a winxp.img
\& /dev/sda3 526385152 2048K ok
.Ve
.PP
-Щоб запустити програму на гостьовій системі, відомій libvirt, скористайтеся
-параметром \fI\-d\fR і, можливо, параметром \fI\-c\fR:
+Щоб запустити програму на гостьовій системі, відомій libvirt, скористайтеся параметром \fI\-d\fR і, можливо, параметром \fI\-c\fR:
.PP
.Vb 3
\& # virt\-alignment\-scan \-d RHEL5
\& /dev/sdb1 65536 64K ok
.Ve
.PP
-Щоб виконати сканування всіх доменів libvirt, віддайте команду
-virt-alignment-scan без параметрів \fI\-a\fR та \fI\-d\fR.
+Щоб виконати сканування всіх доменів libvirt, віддайте команду virt-alignment-scan без параметрів \fI\-a\fR та \fI\-d\fR.
.PP
.Vb 4
\& # virt\-alignment\-scan
\& F16x64:/dev/sda3 526385152 2048K ok
.Ve
.PP
-Дані буде виведено у форматі 4 або більшої кількості стовпчиків,
-відокремлених пробілами. Якщо ви маєте намір обробляти ці дані якоюсь
-програмою, до уваги слід брати лише перші 4 стовпчики. Ось ці стовпчики:
+Дані буде виведено у форматі 4 або більшої кількості стовпчиків, відокремлених пробілами. Якщо ви маєте намір обробляти ці дані якоюсь програмою, до уваги слід брати лише перші 4 стовпчики. Ось ці стовпчики:
.IP "стовпчик 1" 4
.IX Item "стовпчик 1"
-Назва пристрою і розділу (наприклад, \fI/dev/sda\fR означає перший розділ на
-першому блоковому пристрої).
+Назва пристрою і розділу (наприклад, \fI/dev/sda\fR означає перший розділ на першому блоковому пристрої).
.Sp
-У пунктах списків всіх доменів libvirt (без вказаного параметра \fI\-a\fR або
-\&\fI\-d\fR) записи у цьому стовпчику матимуть префікс назви libvirt або \s-1UUID\s0
-(якщо вказано \fI\-\-uuid\fR). Приклад: \f(CW\*(C`WinXP:/dev/sda1\*(C'\fR
+У пунктах списків всіх доменів libvirt (без вказаного параметра \fI\-a\fR або \fI\-d\fR) записи у цьому стовпчику матимуть префікс назви libvirt або \s-1UUID\s0 (якщо вказано \fI\-\-uuid\fR). Приклад: \f(CW\*(C`WinXP:/dev/sda1\*(C'\fR
.IP "стовпчик 2" 4
.IX Item "стовпчик 2"
позиція початку розділу у байтах
вирівнювання у байтах або кілобайтах (наприклад \f(CW512\fR або \f(CW\*(C`4K\*(C'\fR)
.IP "стовпчик 4" 4
.IX Item "стовпчик 4"
-\&\f(CW\*(C`ok\*(C'\fR, якщо вирівнювання є оптимальним з огляду на швидкодію, або \f(CW\*(C`bad\*(C'\fR,
-якщо вирівнювання може призвести до проблем зі швидкодією
+\&\f(CW\*(C`ok\*(C'\fR, якщо вирівнювання є оптимальним з огляду на швидкодію, або \f(CW\*(C`bad\*(C'\fR, якщо вирівнювання може призвести до проблем зі швидкодією
.IP "стовпчик 5 і далі" 4
.IX Item "стовпчик 5 і далі"
додаткові пояснення у довільному форматі.
.PP
-Код виходу програми залежить від того, чи буде знайдено розділи з помилковим
-вирівнюванням. Див. розділ \*(L"СТАН ВИХОДУ\*(R" нижче.
+Код виходу програми залежить від того, чи буде знайдено розділи з помилковим вирівнюванням. Див. розділ \*(L"СТАН ВИХОДУ\*(R" нижче.
.PP
-Якщо вам потрібен лише код виходу без виведення даних, скористайтеся
-параметром \fI\-q\fR.
+Якщо вам потрібен лише код виходу без виведення даних, скористайтеся параметром \fI\-q\fR.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.PD
Додати \fIфайл\fR, який має бути образом диска з віртуальної машини.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a адреса\fR" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-alignment\-scan \-\-format=raw \-a disk.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-cat \-\-format=raw \-a disk.img \-\-format \-a another.img file
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-P\fR кількість_потоків" 4
.IX Item "-P кількість_потоків"
-З версії libguestfs 1.22 у virt-alignment-scan передбачено обробку у
-декілька потоків і паралельне вивчення гостьових систем. Типово кількість
-потоків виконання, що використовуються, вибирається на основі доступного
-обсягу вільної пам’яті на час запуску virt-alignment-scan. Ви можете
-примусово наказати virt-alignment-scan використовувати не більше за
-\&\f(CW\*(C`кількість_потоків\*(C'\fR за допомогою параметра \fI\-P\fR.
+З версії libguestfs 1.22 у virt-alignment-scan передбачено обробку у декілька потоків і паралельне вивчення гостьових систем. Типово кількість потоків виконання, що використовуються, вибирається на основі доступного обсягу вільної пам’яті на час запуску virt-alignment-scan. Ви можете примусово наказати virt-alignment-scan використовувати не більше за \f(CW\*(C`кількість_потоків\*(C'\fR за допомогою параметра \fI\-P\fR.
.Sp
-Зауважте, що \fI\-P 0\fR означає автоматичне визначення, а \fI\-P 1\fR означає
-використання одного потоку виконання.
+Зауважте, що \fI\-P 0\fR означає автоматичне визначення, а \fI\-P 1\fR означає використання одного потоку виконання.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
.IP "\fB\-\-quiet\fR" 4
.IX Item "--quiet"
.PD
-Нічого не виводити. Просто встановити значення коду виходу (див. розділ
-\&\*(L"СТАН ВИХОДУ\*(R" нижче).
+Нічого не виводити. Просто встановити значення коду виходу (див. розділ \*(L"СТАН ВИХОДУ\*(R" нижче).
.IP "\fB\-\-uuid\fR" 4
.IX Item "--uuid"
-Виводити \s-1UUID\s0 замість назв. Корисно для слідкування за гостьовою системою,
-навіть після перенесення або перейменування, або якщо дві гостьові системи
-мають однакові назви.
+Виводити \s-1UUID\s0 замість назв. Корисно для слідкування за гостьовою системою, навіть після перенесення або перейменування, або якщо дві гостьові системи мають однакові назви.
.Sp
-Цей параметр застосовується лише для побудови списку всіх доменів libvirt
-(якщо не вказано параметрів \fI\-a\fR і \fI\-d\fR).
+Цей параметр застосовується лише для побудови списку всіх доменів libvirt (якщо не вказано параметрів \fI\-a\fR і \fI\-d\fR).
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "РЕКОМЕНДОВАНЕ ВИРІВНЮВАННЯ"
.IX Header "РЕКОМЕНДОВАНЕ ВИРІВНЮВАННЯ"
-Операційні системи, старіші за Windows 2008, та Linux до приблизно 2010 року
-розташовують перший сектор на першому розділі у секторі 63 і використовують
-розмір сектору у 512 байтів. Причини суто історичні. Драйвери мають
-повідомити дані щодо геометрії (циліндр / голівка / сектор або \s-1CHS\s0) до
-\&\s-1BIOS.\s0 Ця геометрія є повністю непотрібною на сучасних дисках, але, так
-трапляється, що повідомлені драйвером дані вказують на те, що у доріжці 63
-сектори. Тому операційна система розташовує перший розділ на початку другої
-«доріжки» у секторі 63.
+Операційні системи, старіші за Windows 2008, та Linux до приблизно 2010 року розташовують перший сектор на першому розділі у секторі 63 і використовують розмір сектору у 512 байтів. Причини суто історичні. Драйвери мають повідомити дані щодо геометрії (циліндр / голівка / сектор або \s-1CHS\s0) до \s-1BIOS.\s0 Ця геометрія є повністю непотрібною на сучасних дисках, але, так трапляється, що повідомлені драйвером дані вказують на те, що у доріжці 63 сектори. Тому операційна система розташовує перший розділ на початку другої «доріжки» у секторі 63.
.PP
-Якщо гостьову операційну систему віртуалізовано, основна операційна система
-і гіпервізор можуть надавати перевагу доступу, вирівняному за одним з таких
-значень:
+Якщо гостьову операційну систему віртуалізовано, основна операційна система і гіпервізор можуть надавати перевагу доступу, вирівняному за одним з таких значень:
.IP "\(bu" 4
512 байти
.Sp
-якщо основна операційна система використовує локальне сховище даних
-безпосередньо на розділах твердого диска, а на твердому диску розмір
-фізичних секторів дорівнює 512 байтам.
+якщо основна операційна система використовує локальне сховище даних безпосередньо на розділах твердого диска, а на твердому диску розмір фізичних секторів дорівнює 512 байтам.
.IP "\(bu" 4
4 кілобайтів
.Sp
-для локальних сховищ даних на нових твердих дисках із фізичними секторами у
-4 кілобайти; для файлових сховищ даних на файлових системах із розміром
-блоку у 4 кілобайти; або для деяких типів мережевих сховищ даних.
+для локальних сховищ даних на нових твердих дисках із фізичними секторами у 4 кілобайти; для файлових сховищ даних на файлових системах із розміром блоку у 4 кілобайти; або для деяких типів мережевих сховищ даних.
.IP "\(bu" 4
64 кілобайтів
.Sp
-для висококласних сховищ даних, з’єднаних із мережею. Оптимальний розмір
-блоку для апаратного забезпечення NetApp.
+для висококласних сховищ даних, з’єднаних із мережею. Оптимальний розмір блоку для апаратного забезпечення NetApp.
.IP "\(bu" 4
1 мегабайт
.Sp
див. \*(L"ВИРІВНЮВАННЯ РОЗДІЛІВ НА ПОЗНАЧКИ 1 МБ\*(R" нижче.
.PP
-Розділи, які не вирівняно належним чином щодо основного сховища даних,
-можуть спричиняти зайві помилки введення\-виведення. Приклад:
+Розділи, які не вирівняно належним чином щодо основного сховища даних, можуть спричиняти зайві помилки введення\-виведення. Приклад:
.PP
.Vb 8
\& розділ#63
\& ─ ┴─────────────────────────┴─────────────────────────┴ ─ ─
.Ve
.PP
-У цьому прикладі під час кожного читання блоку у 4 кілобайти гостьової
-системи має бути отримати доступ до двох блоків основної системи (отже,
-здійснено удвічі більший обмін даними введення\-виведення). Якщо у гостьовій
-системі записується блок у 4 кілобайти, у основній системі має бути
-прочитано два блоки, старі і нові дані має бути поєднано, і має бути
-записано назад два блоки (учетверо більший обмін даними введення\-виведення).
+У цьому прикладі під час кожного читання блоку у 4 кілобайти гостьової системи має бути отримати доступ до двох блоків основної системи (отже, здійснено удвічі більший обмін даними введення\-виведення). Якщо у гостьовій системі записується блок у 4 кілобайти, у основній системі має бути прочитано два блоки, старі і нові дані має бути поєднано, і має бути записано назад два блоки (учетверо більший обмін даними введення\-виведення).
.SS "БЛОК ОСНОВНОЇ СИСТЕМИ \s-1LINUX\s0 І РОЗМІР ВВЕДЕННЯ\-ВИВЕДЕННЯ"
.IX Subsection "БЛОК ОСНОВНОЇ СИСТЕМИ LINUX І РОЗМІР ВВЕДЕННЯ-ВИВЕДЕННЯ"
-У нових версіях ядра Linux можна регулювати розміри фізичних і логічних
-блоків, а також мінімальний і рекомендований розмір блоку
-введення\-виведення.
+У нових версіях ядра Linux можна регулювати розміри фізичних і логічних блоків, а також мінімальний і рекомендований розмір блоку введення\-виведення.
.PP
Для типового жорсткого диска з 512\-байтовими секторами:
.PP
\& 65536
.Ve
.PP
-NetApp дозволяє доступ до блоків у 512 байтів (хоча такий доступ буде дуже
-неефективним), надає перевагу мінімальному блоку введення\-виведення у 4 кБ,
-але оптимальним розміром блоку введення\-виведення є 64 кБ.
+NetApp дозволяє доступ до блоків у 512 байтів (хоча такий доступ буде дуже неефективним), надає перевагу мінімальному блоку введення\-виведення у 4 кБ, але оптимальним розміром блоку введення\-виведення є 64 кБ.
.PP
-Щоб дізнатися більше про призначення цих чисел, ознайомтеся зі сторінкою
-http://docs.redhat.com/docs/en\-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage\-iolimits.html
+Щоб дізнатися більше про призначення цих чисел, ознайомтеся зі сторінкою http://docs.redhat.com/docs/en\-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage\-iolimits.html
.PP
-[Дякуємо Matt Booth за надання даних щодо дисків з блоками у 4 кБ. Дякуємо
-Mike Snitzer за надання даних щодо NetApp та додаткову інформацію.]
+[Дякуємо Matt Booth за надання даних щодо дисків з блоками у 4 кБ. Дякуємо Mike Snitzer за надання даних щодо NetApp та додаткову інформацію.]
.SS "ВИРІВНЮВАННЯ РОЗДІЛІВ НА ПОЗНАЧКИ 1 МБ"
.IX Subsection "ВИРІВНЮВАННЯ РОЗДІЛІВ НА ПОЗНАЧКИ 1 МБ"
-Microsoft вибрано 1 МБ як типове вирівнювання для усіх розділів, починаючи з
-Windows 2008 Server. У Linux також почали використовувати таке вирівнювання.
+Microsoft вибрано 1 МБ як типове вирівнювання для усіх розділів, починаючи з Windows 2008 Server. У Linux також почали використовувати таке вирівнювання.
.PP
-Припускаючи у гостьовій системі сектори у 512 байтів, маємо перший розділ,
-що починається з сектора 2048 і наступні розділи (якщо такі є) будуть
-починатися з сектора, номер якого кратний до 2048.
+Припускаючи у гостьовій системі сектори у 512 байтів, маємо перший розділ, що починається з сектора 2048 і наступні розділи (якщо такі є) будуть починатися з сектора, номер якого кратний до 2048.
.PP
-Вирівнювання за 1 МБ є сумісним із усіма поточними варіантами вирівнювання
-(4 кБ, 64 кБ) і надає простір для подальшого зростання розмірів фізичних
-блоків.
+Вирівнювання за 1 МБ є сумісним із усіма поточними варіантами вирівнювання (4 кБ, 64 кБ) і надає простір для подальшого зростання розмірів фізичних блоків.
.SS "ВСТАНОВЛЕННЯ ВИРІВНЮВАННЯ"
.IX Subsection "ВСТАНОВЛЕННЯ ВИРІВНЮВАННЯ"
-\&\fBvirt\-resize\fR\|(1) може змінювати вирівнювання розділів деяких гостьових
-систем. У поточній версії програма здатна повністю вирівняти усі розділи
-усіх гостьових систем Windows і виправити завантажувач, де це потрібно. Для
-гостьових систем Linux програма може вирівняти другий і наступні розділи,
-щоб більшість доступів операційної системи, окрім часу завантаження, було
-вирівняно належним чином.
+\&\fBvirt\-resize\fR\|(1) може змінювати вирівнювання розділів деяких гостьових систем. У поточній версії програма здатна повністю вирівняти усі розділи усіх гостьових систем Windows і виправити завантажувач, де це потрібно. Для гостьових систем Linux програма може вирівняти другий і наступні розділи, щоб більшість доступів операційної системи, окрім часу завантаження, було вирівняно належним чином.
.PP
-Іншим способом виправлення проблем, пов’язаних із вирівнюванням розділів, є
-перевстановлення ваших гостьових операційних систем. Якщо ви встановлюєте
-операційні системи з шаблонів, вам також варто переконатися, що із
-вирівнюванням розділів усе гаразд.
+Іншим способом виправлення проблем, пов’язаних із вирівнюванням розділів, є перевстановлення ваших гостьових операційних систем. Якщо ви встановлюєте операційні системи з шаблонів, вам також варто переконатися, що із вирівнюванням розділів усе гаразд.
.PP
-Для старіших версій Windows корисні відомості можна знайти у цьому документі
-NetApp: http://media.netapp.com/documents/tr\-3747.pdf
+Для старіших версій Windows корисні відомості можна знайти у цьому документі NetApp: http://media.netapp.com/documents/tr\-3747.pdf
.PP
-Для Red Hat Enterprise Linux ≤ 5 слід використовувати скрипт Kickstart,
-який містить явний розділ \f(CW%pre\fR для створення вирівняних розділів диска за
-допомогою \fBparted\fR\|(8). Не використовуйте команду Kickstart \f(CW\*(C`part\*(C'\fR. У
-наведеному вище документі NetApp міститься приклад.
+Для Red Hat Enterprise Linux ≤ 5 слід використовувати скрипт Kickstart, який містить явний розділ \f(CW%pre\fR для створення вирівняних розділів диска за допомогою \fBparted\fR\|(8). Не використовуйте команду Kickstart \f(CW\*(C`part\*(C'\fR. У наведеному вище документі NetApp міститься приклад.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
Ця програма повертає:
.IP "\(bu" 4
0
.Sp
-успішне завершення, всі розділи вирівняно на ≥ 64 кБ для отримання
-найкращої швидкодії
+успішне завершення, всі розділи вирівняно на ≥ 64 кБ для отримання найкращої швидкодії
.IP "\(bu" 4
1
.Sp
.IP "\(bu" 4
2
.Sp
-успішне завершення роботи, деякі розділи може бути вирівняно на < 64 кБ,
-що може призвести до погіршення швидкодії на високошвидкісних мережевих
-сховищах
+успішне завершення роботи, деякі розділи може бути вирівняно на < 64 кБ, що може призвести до погіршення швидкодії на високошвидкісних мережевих сховищах
.IP "\(bu" 4
3
.Sp
-успішне завершення роботи, деякі розділи може бути вирівняно на < 4 кБ,
-що може призвести до погіршення швидкодії у більшості гіпервізорів
+успішне завершення роботи, деякі розділи може бути вирівняно на < 4 кБ, що може призвести до погіршення швидкодії у більшості гіпервізорів
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBvirt\-resize\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Під час встановлення застарілих операційних систем засоби розподілу диска
-можуть розташувати розділ на секторі з помилковим вирівнюванням відносно
-системи зберігання даних (типово, перший розділ починається з сектора
-C<63>). Розділи з помилковим вирівнюванням можуть призвести до неоптимальної
-кількості запитів щодо виведення та введення даних від операційної системи.
-
-Програма virt-alignment-scan виконує перевірку вирівнювання розділів у
-віртуальних машинах та образів дисків і повідомляє вам, якщо буде виявлено
-помилки вирівнювання.
-
-У поточній версії не передбачено програми для виправлення помилок,
-пов’язаних з вирівнюванням. Ви можете лише перевстановити гостьову
-операційну систему. У цьому документі можна знайти короткі описи помилок та
-можливі шляхи усування цих помилок:
-L<http://media.netapp.com/documents/tr-3747.pdf>
+Під час встановлення застарілих операційних систем засоби розподілу диска можуть розташувати розділ на секторі з помилковим вирівнюванням відносно системи зберігання даних (типово, перший розділ починається з сектора C<63>). Розділи з помилковим вирівнюванням можуть призвести до неоптимальної кількості запитів щодо виведення та введення даних від операційної системи.
+
+Програма virt-alignment-scan виконує перевірку вирівнювання розділів у віртуальних машинах та образів дисків і повідомляє вам, якщо буде виявлено помилки вирівнювання.
+
+У поточній версії не передбачено програми для виправлення помилок, пов’язаних з вирівнюванням. Ви можете лише перевстановити гостьову операційну систему. У цьому документі можна знайти короткі описи помилок та можливі шляхи усування цих помилок: L<http://media.netapp.com/documents/tr-3747.pdf>
=head1 ВИВЕДЕННЯ
-Щоб запустити цю програму безпосередньо для образу диска, скористайтеся
-параметром I<-a>:
+Щоб запустити цю програму безпосередньо для образу диска, скористайтеся параметром I<-a>:
$ virt-alignment-scan -a winxp.img
/dev/sda1 32256 512 bad (alignment < 4K)
/dev/sda2 2097152 2048K ok
/dev/sda3 526385152 2048K ok
-Щоб запустити програму на гостьовій системі, відомій libvirt, скористайтеся
-параметром I<-d> і, можливо, параметром I<-c>:
+Щоб запустити програму на гостьовій системі, відомій libvirt, скористайтеся параметром I<-d> і, можливо, параметром I<-c>:
# virt-alignment-scan -d RHEL5
/dev/sda1 32256 512 bad (alignment < 4K)
/dev/sda2 105906176 1024K ok
/dev/sdb1 65536 64K ok
-Щоб виконати сканування всіх доменів libvirt, віддайте команду
-virt-alignment-scan без параметрів I<-a> та I<-d>.
+Щоб виконати сканування всіх доменів libvirt, віддайте команду virt-alignment-scan без параметрів I<-a> та I<-d>.
# virt-alignment-scan
F16x64:/dev/sda1 1048576 1024K ok
F16x64:/dev/sda2 2097152 2048K ok
F16x64:/dev/sda3 526385152 2048K ok
-Дані буде виведено у форматі 4 або більшої кількості стовпчиків,
-відокремлених пробілами. Якщо ви маєте намір обробляти ці дані якоюсь
-програмою, до уваги слід брати лише перші 4 стовпчики. Ось ці стовпчики:
+Дані буде виведено у форматі 4 або більшої кількості стовпчиків, відокремлених пробілами. Якщо ви маєте намір обробляти ці дані якоюсь програмою, до уваги слід брати лише перші 4 стовпчики. Ось ці стовпчики:
=over 4
=item стовпчик 1
-Назва пристрою і розділу (наприклад, F</dev/sda> означає перший розділ на
-першому блоковому пристрої).
+Назва пристрою і розділу (наприклад, F</dev/sda> означає перший розділ на першому блоковому пристрої).
-У пунктах списків всіх доменів libvirt (без вказаного параметра I<-a> або
-I<-d>) записи у цьому стовпчику матимуть префікс назви libvirt або UUID
-(якщо вказано I<--uuid>). Приклад: C<WinXP:/dev/sda1>
+У пунктах списків всіх доменів libvirt (без вказаного параметра I<-a> або I<-d>) записи у цьому стовпчику матимуть префікс назви libvirt або UUID (якщо вказано I<--uuid>). Приклад: C<WinXP:/dev/sda1>
=item стовпчик 2
=item стовпчик 4
-C<ok>, якщо вирівнювання є оптимальним з огляду на швидкодію, або C<bad>,
-якщо вирівнювання може призвести до проблем зі швидкодією
+C<ok>, якщо вирівнювання є оптимальним з огляду на швидкодію, або C<bad>, якщо вирівнювання може призвести до проблем зі швидкодією
=item стовпчик 5 і далі
=back
-Код виходу програми залежить від того, чи буде знайдено розділи з помилковим
-вирівнюванням. Див. розділ L</СТАН ВИХОДУ> нижче.
+Код виходу програми залежить від того, чи буде знайдено розділи з помилковим вирівнюванням. Див. розділ L</СТАН ВИХОДУ> нижче.
-Якщо вам потрібен лише код виходу без виведення даних, скористайтеся
-параметром I<-q>.
+Якщо вам потрібен лише код виходу без виведення даних, скористайтеся параметром I<-q>.
=head1 ПАРАМЕТРИ
Додати I<файл>, який має бути образом диска з віртуальної машини.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-alignment-scan --format=raw -a disk.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-cat --format=raw -a disk.img --format -a another.img file
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<-P> кількість_потоків
-З версії libguestfs 1.22 у virt-alignment-scan передбачено обробку у
-декілька потоків і паралельне вивчення гостьових систем. Типово кількість
-потоків виконання, що використовуються, вибирається на основі доступного
-обсягу вільної пам’яті на час запуску virt-alignment-scan. Ви можете
-примусово наказати virt-alignment-scan використовувати не більше за
-C<кількість_потоків> за допомогою параметра I<-P>.
+З версії libguestfs 1.22 у virt-alignment-scan передбачено обробку у декілька потоків і паралельне вивчення гостьових систем. Типово кількість потоків виконання, що використовуються, вибирається на основі доступного обсягу вільної пам’яті на час запуску virt-alignment-scan. Ви можете примусово наказати virt-alignment-scan використовувати не більше за C<кількість_потоків> за допомогою параметра I<-P>.
-Зауважте, що I<-P 0> означає автоматичне визначення, а I<-P 1> означає
-використання одного потоку виконання.
+Зауважте, що I<-P 0> означає автоматичне визначення, а I<-P 1> означає використання одного потоку виконання.
=item B<-q>
=item B<--quiet>
-Нічого не виводити. Просто встановити значення коду виходу (див. розділ
-L</СТАН ВИХОДУ> нижче).
+Нічого не виводити. Просто встановити значення коду виходу (див. розділ L</СТАН ВИХОДУ> нижче).
=item B<--uuid>
-Виводити UUID замість назв. Корисно для слідкування за гостьовою системою,
-навіть після перенесення або перейменування, або якщо дві гостьові системи
-мають однакові назви.
+Виводити UUID замість назв. Корисно для слідкування за гостьовою системою, навіть після перенесення або перейменування, або якщо дві гостьові системи мають однакові назви.
-Цей параметр застосовується лише для побудови списку всіх доменів libvirt
-(якщо не вказано параметрів I<-a> і I<-d>).
+Цей параметр застосовується лише для побудови списку всіх доменів libvirt (якщо не вказано параметрів I<-a> і I<-d>).
=item B<-v>
=head1 РЕКОМЕНДОВАНЕ ВИРІВНЮВАННЯ
-Операційні системи, старіші за Windows 2008, та Linux до приблизно 2010 року
-розташовують перший сектор на першому розділі у секторі 63 і використовують
-розмір сектору у 512 байтів. Причини суто історичні. Драйвери мають
-повідомити дані щодо геометрії (циліндр / голівка / сектор або CHS) до
-BIOS. Ця геометрія є повністю непотрібною на сучасних дисках, але, так
-трапляється, що повідомлені драйвером дані вказують на те, що у доріжці 63
-сектори. Тому операційна система розташовує перший розділ на початку другої
-«доріжки» у секторі 63.
+Операційні системи, старіші за Windows 2008, та Linux до приблизно 2010 року розташовують перший сектор на першому розділі у секторі 63 і використовують розмір сектору у 512 байтів. Причини суто історичні. Драйвери мають повідомити дані щодо геометрії (циліндр / голівка / сектор або CHS) до BIOS. Ця геометрія є повністю непотрібною на сучасних дисках, але, так трапляється, що повідомлені драйвером дані вказують на те, що у доріжці 63 сектори. Тому операційна система розташовує перший розділ на початку другої «доріжки» у секторі 63.
-Якщо гостьову операційну систему віртуалізовано, основна операційна система
-і гіпервізор можуть надавати перевагу доступу, вирівняному за одним з таких
-значень:
+Якщо гостьову операційну систему віртуалізовано, основна операційна система і гіпервізор можуть надавати перевагу доступу, вирівняному за одним з таких значень:
=over 4
=item * 512 байти
-якщо основна операційна система використовує локальне сховище даних
-безпосередньо на розділах твердого диска, а на твердому диску розмір
-фізичних секторів дорівнює 512 байтам.
+якщо основна операційна система використовує локальне сховище даних безпосередньо на розділах твердого диска, а на твердому диску розмір фізичних секторів дорівнює 512 байтам.
=item * 4 кілобайтів
-для локальних сховищ даних на нових твердих дисках із фізичними секторами у
-4 кілобайти; для файлових сховищ даних на файлових системах із розміром
-блоку у 4 кілобайти; або для деяких типів мережевих сховищ даних.
+для локальних сховищ даних на нових твердих дисках із фізичними секторами у 4 кілобайти; для файлових сховищ даних на файлових системах із розміром блоку у 4 кілобайти; або для деяких типів мережевих сховищ даних.
=item * 64 кілобайтів
-для висококласних сховищ даних, з’єднаних із мережею. Оптимальний розмір
-блоку для апаратного забезпечення NetApp.
+для висококласних сховищ даних, з’єднаних із мережею. Оптимальний розмір блоку для апаратного забезпечення NetApp.
=item * 1 мегабайт
=back
-Розділи, які не вирівняно належним чином щодо основного сховища даних,
-можуть спричиняти зайві помилки введення-виведення. Приклад:
+Розділи, які не вирівняно належним чином щодо основного сховища даних, можуть спричиняти зайві помилки введення-виведення. Приклад:
розділ#63
┌──────────────────────────┬ ─ ─ ─ ─
│ │ │
─ ┴─────────────────────────┴─────────────────────────┴ ─ ─
-У цьому прикладі під час кожного читання блоку у 4 кілобайти гостьової
-системи має бути отримати доступ до двох блоків основної системи (отже,
-здійснено удвічі більший обмін даними введення-виведення). Якщо у гостьовій
-системі записується блок у 4 кілобайти, у основній системі має бути
-прочитано два блоки, старі і нові дані має бути поєднано, і має бути
-записано назад два блоки (учетверо більший обмін даними введення-виведення).
+У цьому прикладі під час кожного читання блоку у 4 кілобайти гостьової системи має бути отримати доступ до двох блоків основної системи (отже, здійснено удвічі більший обмін даними введення-виведення). Якщо у гостьовій системі записується блок у 4 кілобайти, у основній системі має бути прочитано два блоки, старі і нові дані має бути поєднано, і має бути записано назад два блоки (учетверо більший обмін даними введення-виведення).
=head2 БЛОК ОСНОВНОЇ СИСТЕМИ LINUX І РОЗМІР ВВЕДЕННЯ-ВИВЕДЕННЯ
-У нових версіях ядра Linux можна регулювати розміри фізичних і логічних
-блоків, а також мінімальний і рекомендований розмір блоку
-введення-виведення.
+У нових версіях ядра Linux можна регулювати розміри фізичних і логічних блоків, а також мінімальний і рекомендований розмір блоку введення-виведення.
Для типового жорсткого диска з 512-байтовими секторами:
$ cat /sys/block/sdc/queue/optimal_io_size
65536
-NetApp дозволяє доступ до блоків у 512 байтів (хоча такий доступ буде дуже
-неефективним), надає перевагу мінімальному блоку введення-виведення у 4 кБ,
-але оптимальним розміром блоку введення-виведення є 64 кБ.
+NetApp дозволяє доступ до блоків у 512 байтів (хоча такий доступ буде дуже неефективним), надає перевагу мінімальному блоку введення-виведення у 4 кБ, але оптимальним розміром блоку введення-виведення є 64 кБ.
-Щоб дізнатися більше про призначення цих чисел, ознайомтеся зі сторінкою
-L<http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage-iolimits.html>
+Щоб дізнатися більше про призначення цих чисел, ознайомтеся зі сторінкою L<http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/newstorage-iolimits.html>
-[Дякуємо Matt Booth за надання даних щодо дисків з блоками у 4 кБ. Дякуємо
-Mike Snitzer за надання даних щодо NetApp та додаткову інформацію.]
+[Дякуємо Matt Booth за надання даних щодо дисків з блоками у 4 кБ. Дякуємо Mike Snitzer за надання даних щодо NetApp та додаткову інформацію.]
=head2 ВИРІВНЮВАННЯ РОЗДІЛІВ НА ПОЗНАЧКИ 1 МБ
-Microsoft вибрано 1 МБ як типове вирівнювання для усіх розділів, починаючи з
-Windows 2008 Server. У Linux також почали використовувати таке вирівнювання.
+Microsoft вибрано 1 МБ як типове вирівнювання для усіх розділів, починаючи з Windows 2008 Server. У Linux також почали використовувати таке вирівнювання.
-Припускаючи у гостьовій системі сектори у 512 байтів, маємо перший розділ,
-що починається з сектора 2048 і наступні розділи (якщо такі є) будуть
-починатися з сектора, номер якого кратний до 2048.
+Припускаючи у гостьовій системі сектори у 512 байтів, маємо перший розділ, що починається з сектора 2048 і наступні розділи (якщо такі є) будуть починатися з сектора, номер якого кратний до 2048.
-Вирівнювання за 1 МБ є сумісним із усіма поточними варіантами вирівнювання
-(4 кБ, 64 кБ) і надає простір для подальшого зростання розмірів фізичних
-блоків.
+Вирівнювання за 1 МБ є сумісним із усіма поточними варіантами вирівнювання (4 кБ, 64 кБ) і надає простір для подальшого зростання розмірів фізичних блоків.
=head2 ВСТАНОВЛЕННЯ ВИРІВНЮВАННЯ
-L<virt-resize(1)> може змінювати вирівнювання розділів деяких гостьових
-систем. У поточній версії програма здатна повністю вирівняти усі розділи
-усіх гостьових систем Windows і виправити завантажувач, де це потрібно. Для
-гостьових систем Linux програма може вирівняти другий і наступні розділи,
-щоб більшість доступів операційної системи, окрім часу завантаження, було
-вирівняно належним чином.
+L<virt-resize(1)> може змінювати вирівнювання розділів деяких гостьових систем. У поточній версії програма здатна повністю вирівняти усі розділи усіх гостьових систем Windows і виправити завантажувач, де це потрібно. Для гостьових систем Linux програма може вирівняти другий і наступні розділи, щоб більшість доступів операційної системи, окрім часу завантаження, було вирівняно належним чином.
-Іншим способом виправлення проблем, пов’язаних із вирівнюванням розділів, є
-перевстановлення ваших гостьових операційних систем. Якщо ви встановлюєте
-операційні системи з шаблонів, вам також варто переконатися, що із
-вирівнюванням розділів усе гаразд.
+Іншим способом виправлення проблем, пов’язаних із вирівнюванням розділів, є перевстановлення ваших гостьових операційних систем. Якщо ви встановлюєте операційні системи з шаблонів, вам також варто переконатися, що із вирівнюванням розділів усе гаразд.
-Для старіших версій Windows корисні відомості можна знайти у цьому документі
-NetApp: L<http://media.netapp.com/documents/tr-3747.pdf>
+Для старіших версій Windows корисні відомості можна знайти у цьому документі NetApp: L<http://media.netapp.com/documents/tr-3747.pdf>
-Для Red Hat Enterprise Linux E<le> 5 слід використовувати скрипт Kickstart,
-який містить явний розділ C<%pre> для створення вирівняних розділів диска за
-допомогою L<parted(8)>. Не використовуйте команду Kickstart C<part>. У
-наведеному вище документі NetApp міститься приклад.
+Для Red Hat Enterprise Linux E<le> 5 слід використовувати скрипт Kickstart, який містить явний розділ C<%pre> для створення вирівняних розділів диска за допомогою L<parted(8)>. Не використовуйте команду Kickstart C<part>. У наведеному вище документі NetApp міститься приклад.
=head1 СТАН ВИХОДУ
0
-успішне завершення, всі розділи вирівняно на E<ge> 64 кБ для отримання
-найкращої швидкодії
+успішне завершення, всі розділи вирівняно на E<ge> 64 кБ для отримання найкращої швидкодії
=item *
2
-успішне завершення роботи, деякі розділи може бути вирівняно на E<lt> 64 кБ,
-що може призвести до погіршення швидкодії на високошвидкісних мережевих
-сховищах
+успішне завершення роботи, деякі розділи може бути вирівняно на E<lt> 64 кБ, що може призвести до погіршення швидкодії на високошвидкісних мережевих сховищах
=item *
3
-успішне завершення роботи, деякі розділи може бути вирівняно на E<lt> 4 кБ,
-що може призвести до погіршення швидкодії у більшості гіпервізорів
+успішне завершення роботи, деякі розділи може бути вирівняно на E<lt> 4 кБ, що може призвести до погіршення швидкодії у більшості гіпервізорів
=back
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-rescue(1)>,
-L<virt-resize(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
=head1 НАЗВА
-virt-builder-repository — засіб для полегшення побудови сховищ початкових
-даних virt-builder
+virt-builder-repository — засіб для полегшення побудови сховищ початкових даних virt-builder
=head1 КОРОТКИЙ ОПИС
=head1 ОПИС
-Virt-builder — засіб для швидкої побудови нових віртуальних машин. Його
-можна налаштувати на використання сховищ шаблонів. Втім, створення і
-супровід сховища включає багато завдань, які можна
-автоматизувати. virt-builder-repository — саме той інструмент, який допоможе
-вам у керуванні такими сховищами.
+Virt-builder — засіб для швидкої побудови нових віртуальних машин. Його можна налаштувати на використання сховищ шаблонів. Втім, створення і супровід сховища включає багато завдань, які можна автоматизувати. virt-builder-repository — саме той інструмент, який допоможе вам у керуванні такими сховищами.
-Virt-builder-repository циклічно обробляє файли у каталозі, вказаному за
-допомогою аргументу команди, стискає файли із назвою, яка завершується
-суфіксом C<qcow2>, C<raw>, C<img>, або файли без суфікса назви, видобуває
-дані з цих файлів і створює або оновлює файл C<index> (покажчик).
+Virt-builder-repository циклічно обробляє файли у каталозі, вказаному за допомогою аргументу команди, стискає файли із назвою, яка завершується суфіксом C<qcow2>, C<raw>, C<img>, або файли без суфікса назви, видобуває дані з цих файлів і створює або оновлює файл C<index> (покажчик).
-Деякі з потрібних для побудови файла покажчика даних, пов'язаних із образом,
-не можна визначати на основі файла образу. virt-builder-repository спочатку
-намагається знайти ці дані у наявному файлі покажчика. Якщо після цієї
-спроби буде виявлено нестачу певних даних, програма попросить користувача
-вказати їх у інтерактивному режимі. Якщо ж отримати ці дані не вдасться,
-буде показано повідомлення про помилку.
+Деякі з потрібних для побудови файла покажчика даних, пов'язаних із образом, не можна визначати на основі файла образу. virt-builder-repository спочатку намагається знайти ці дані у наявному файлі покажчика. Якщо після цієї спроби буде виявлено нестачу певних даних, програма попросить користувача вказати їх у інтерактивному режимі. Якщо ж отримати ці дані не вдасться, буде показано повідомлення про помилку.
-Якщо вказано C<ІДЕНТИФІКАТОР_КЛЮЧА>, створений файл покажчика буде підписано
-цим ключем GPG.
+Якщо вказано C<ІДЕНТИФІКАТОР_КЛЮЧА>, створений файл покажчика буде підписано цим ключем GPG.
=head1 ПРИКЛАДИ
=head2 Створення початкового сховища
-Створіть теку і скопіюйте до неї файли шаблонів образів дисків. Дані
-віддайте команду, подібну до такої:
+Створіть теку і скопіюйте до неї файли шаблонів образів дисків. Дані віддайте команду, подібну до такої:
virt-builder-repository --gpg-key "joe@hacker.org" -i /шлях/до/теки
-Зауважте, що вказана у нашому прикладі команда працюватиме у інтерактивному
-режимі. Щоб її було виконано у автоматизованому режимі, слід створити перед
-відданням команди мінімальний файл покажчика, який міститиме розділи,
-подібні до такого:
+Зауважте, що вказана у нашому прикладі команда працюватиме у інтерактивному режимі. Щоб її було виконано у автоматизованому режимі, слід створити перед відданням команди мінімальний файл покажчика, який міститиме розділи, подібні до такого:
[ідентифікатор_шаблона]
file=назва_файла_шаблона.qcow.xz
-Значення file має збігатися із назвою образу із додаванням суфікса C<.xz>,
-якщо не вказано параметра I<--no-compression>, або назвою образу, якщо
-стискання не використовується. Можна попередньо вказати інші необов'язкові
-дані. Типові значення буде визначено шляхом аналізу образу диска. Щоб
-дізнатися більше, ознайомтеся із розділом L<virt-builder(1)/Створення і
-підписування файла покажчика>.
+Значення file має збігатися із назвою образу із додаванням суфікса C<.xz>, якщо не вказано параметра I<--no-compression>, або назвою образу, якщо стискання не використовується. Можна попередньо вказати інші необов'язкові дані. Типові значення буде визначено шляхом аналізу образу диска. Щоб дізнатися більше, ознайомтеся із розділом L<virt-builder(1)/Створення і підписування файла покажчика>.
=head2 Оновлення образів у наявному сховищі
-У цьому випадку до сховища слід додати новий образ або нову модифікацію
-наявного образу. Розташуйте відповідні файли шаблонів образів у теці
-сховища.
+У цьому випадку до сховища слід додати новий образ або нову модифікацію наявного образу. Розташуйте відповідні файли шаблонів образів у теці сховища.
-Щоб оновити модифікацію образу, файл повинен мати таку саму назву, що і
-наявний (без суфікса назви C<xz>).
+Щоб оновити модифікацію образу, файл повинен мати таку саму назву, що і наявний (без суфікса назви C<xz>).
-Як і у випадку створення сховища, для автоматизації процесу до файла
-покажчика можна додати мінімальний фрагмент. Зробити це можна для
-підписаного покажчика, хоча це і може видатися доволі дивною ідеєю, — файл
-буде знову підписано самою програмою.
+Як і у випадку створення сховища, для автоматизації процесу до файла покажчика можна додати мінімальний фрагмент. Зробити це можна для підписаного покажчика, хоча це і може видатися доволі дивною ідеєю, — файл буде знову підписано самою програмою.
-Щоб вилучити файл образу зі сховища, просто вилучіть відповідний файл образу
-до запуску virt-builder-repository.
+Щоб вилучити файл образу зі сховища, просто вилучіть відповідний файл образу до запуску virt-builder-repository.
Далі віддайте таку команду, щоб доповнити і оновити файл покажчика:
virt-builder-repository --gpg-key "joe@hacker.org" -i /шлях/до/теки
-virt-builder-repository працює у тимчасовій теці у теці сховища. Якщо під
-час роботи програми трапиться якась прикра несподіванка, сховище лишиться
-незміненим.
+virt-builder-repository працює у тимчасовій теці у теці сховища. Якщо під час роботи програми трапиться якась прикра несподіванка, сховище лишиться незміненим.
=head1 ПАРАМЕТРИ
=item B<--gpg> GPG
-Вказати альтернативний виконуваний файл L<gpg(1)> (GNU Privacy Guard). Ви
-можете скористатися цим параметром для додавання параметрів до основної
-програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
+Вказати альтернативний виконуваний файл L<gpg(1)> (GNU Privacy Guard). Ви можете скористатися цим параметром для додавання параметрів до основної програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
virt-builder-repository --gpg "gpg --homedir /tmp" [...]
-Цим також можна скористатися, щоб засоби gpg не просили ввести пароль до
-ключа:
+Цим також можна скористатися, щоб засоби gpg не просили ввести пароль до ключа:
virt-builder-repository --gpg "gpg --passphrase-file /tmp/pass --batch" [...]
=item B<--gpg-key> ІДЕНТИФІКАТОР_КЛЮЧА
-Вказати ключ GPG, який буде використано для підписування файла покажчика
-сховища. Якщо ключ не вказано, файл покажчика підписано не
-буде. C<ІДЕНТИФІКАТОР_КЛЮЧА> використовується для визначення ключа GPG, яким
-слід скористатися. Це значення передається до параметра I<--default-key>
-gpg, а отже може бути адресою електронної пошти або відбитком.
+Вказати ключ GPG, який буде використано для підписування файла покажчика сховища. Якщо ключ не вказано, файл покажчика підписано не буде. C<ІДЕНТИФІКАТОР_КЛЮЧА> використовується для визначення ключа GPG, яким слід скористатися. Це значення передається до параметра I<--default-key> gpg, а отже може бути адресою електронної пошти або відбитком.
-B<ЗАУВАЖЕННЯ>: типово, virt-builder-repository виконує пошук ключа у сховищі
-ключів GPG користувача.
+B<ЗАУВАЖЕННЯ>: типово, virt-builder-repository виконує пошук ключа у сховищі ключів GPG користувача.
=item B<-i>
=item B<--interactive>
-Надсилати запит щодо даних, яких не вистачатиме. Типові значення
-визначатимуться за образом диска.
+Надсилати запит щодо даних, яких не вистачатиме. Типові значення визначатимуться за образом диска.
-У запитах щодо даних введення C<-> відповідає порожньому значенню. Цим можна
-скористатися, щоб уникнути встановлення автоматично визначеного значення.
+У запитах щодо даних введення C<-> відповідає порожньому значенню. Цим можна скористатися, щоб уникнути встановлення автоматично визначеного значення.
=item B<--no-compression>
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<--colors>
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<-q>
Увімкнути діагностичні повідомлення і/або режим докладних повідомлень.
-Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі
-виведені дані до звіту щодо вади.
+Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі виведені дані до звіту щодо вади.
=item B<-V>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-builder-repository з інших програм,
-графічних інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-builder-repository з інших програм, графічних інтерфейсів тощо.
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-builder-repository. Типово виведені дані
-виглядатимуть якось так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-builder-repository. Типово виведені дані виглядатимуть якось так:
$ virt-builder-repository --machine-readable
virt-builder-repository
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-builder 1"
-.TH virt-builder 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-builder 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-builder — інструмент для швидкого збирання нових віртуальних машин. За
-його допомогою ви зможете зібрати цілий спектр віртуальних машин для
-локального використання або використання у «хмарі». Зазвичай, для цього
-достатньо декількох хвилин. Крім того, у virt-builder передбачено багато
-способів налаштовування зібраних віртуальних машин. Усі команди віддаються
-за допомогою командного рядка. Для роботи програми не потрібні права доступу
-адміністратора системи, тому збирання нових віртуальних машин просто
-автоматизувати або керувати ним за допомогою скриптів.
-.PP
-Зауважте, що virt-builder не встановлює гостьові системи «з нуля». Програма
-використовує ретельного приготовані, підписані цифровими підписами шаблони
-операційних систем і налаштовує їх. Такий підхід використано, оскільки він є
-набагато швидшим за інші. Втім, якщо потрібно встановити систему «з нуля»,
-ви можете скористатися \fBvirt\-install\fR\|(1) та \fBoz\-install\fR\|(1).
+Virt-builder — інструмент для швидкого збирання нових віртуальних машин. За його допомогою ви зможете зібрати цілий спектр віртуальних машин для локального використання або використання у «хмарі». Зазвичай, для цього достатньо декількох хвилин. Крім того, у virt-builder передбачено багато способів налаштовування зібраних віртуальних машин. Усі команди віддаються за допомогою командного рядка. Для роботи програми не потрібні права доступу адміністратора системи, тому збирання нових віртуальних машин просто автоматизувати або керувати ним за допомогою скриптів.
+.PP
+Зауважте, що virt-builder не встановлює гостьові системи «з нуля». Програма використовує ретельного приготовані, підписані цифровими підписами шаблони операційних систем і налаштовує їх. Такий підхід використано, оскільки він є набагато швидшим за інші. Втім, якщо потрібно встановити систему «з нуля», ви можете скористатися \fBvirt\-install\fR\|(1) та \fBoz\-install\fR\|(1).
.PP
Найпростіше буде розпочати з прикладів з наступного розділу.
.SH "ПРИКЛАДИ"
\& virt\-builder \-\-list
.Ve
.PP
-покаже список доступних до встановлення операційних систем. Типово,
-доступний набір операційних систем із вільним поширенням. Ви також можете
-додати свою операційну систему (див. нижче).
+покаже список доступних до встановлення операційних систем. Типово, доступний набір операційних систем із вільним поширенням. Ви також можете додати свою операційну систему (див. нижче).
.PP
-Після вибору гостьової системи зі списку може виникнути потреба у
-ознайомленні із нотатками щодо встановлення:
+Після вибору гостьової системи зі списку може виникнути потреба у ознайомленні із нотатками щодо встановлення:
.PP
.Vb 1
\& virt\-builder \-\-notes fedora\-27
\& virt\-builder fedora\-27
.Ve
.PP
-збере образ Fedora 25 для тієї самої архітектури, що і virt-builder (отже
-виконання команди у системі архітектури i686 призведе до спроби збирання
-образу i686, якщо це можливо). Образ матиме типові налаштування (мінімальний
-розмір, без облікових записів користувачів, випадковий пароль root, лише
-базовий мінімальний набір встановлених програм тощо).
+збере образ Fedora 25 для тієї самої архітектури, що і virt-builder (отже виконання команди у системі архітектури i686 призведе до спроби збирання образу i686, якщо це можливо). Образ матиме типові налаштування (мінімальний розмір, без облікових записів користувачів, випадковий пароль root, лише базовий мінімальний набір встановлених програм тощо).
.PP
Потреби у запуску цієї програми від імені root \fIнемає\fR.
.PP
-Першого разу доведеться отримати шаблон мережею, а наступні операції може
-бути кешовано (див. \*(L"КЕШУВАННЯ\*(R").
+Першого разу доведеться отримати шаблон мережею, а наступні операції може бути кешовано (див. \*(L"КЕШУВАННЯ\*(R").
.PP
-Назву файла результатів буде визначено на основі назви шаблона, отже для
-наведеного вище прикладу буде \fIfedora\-27.img\fR. Змінити назву файла
-результатів можна за допомогою параметра \fI\-o\fR:
+Назву файла результатів буде визначено на основі назви шаблона, отже для наведеного вище прикладу буде \fIfedora\-27.img\fR. Змінити назву файла результатів можна за допомогою параметра \fI\-o\fR:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-o mydisk.img
.Ve
.PP
-Ви також можете скористатися параметром \fI\-o\fR для запису на наявні пристрої
-або логічні томи.
+Ви також можете скористатися параметром \fI\-o\fR для запису на наявні пристрої або логічні томи.
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-format qcow2
.Ve
.PP
-Те саме, що і вище, але виведені дані буде записано у форматі qcow2 до
-\&\fIfedora\-27.qcow2\fR.
+Те саме, що і вище, але виведені дані буде записано у форматі qcow2 до \fIfedora\-27.qcow2\fR.
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-size 20G
.Ve
.PP
-Як і вище, але обсяг виведених даних дорівнюватиме 20 ГБ. Розмір гостьової
-операційної системи буде змінено так, наче її скопійовано до виведених даних
-(автоматично, за допомогою \fBvirt\-resize\fR\|(1)).
+Як і вище, але обсяг виведених даних дорівнюватиме 20 ГБ. Розмір гостьової операційної системи буде змінено так, наче її скопійовано до виведених даних (автоматично, за допомогою \fBvirt\-resize\fR\|(1)).
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-arch i686
\& virt\-builder fedora\-27 \-\-root\-password file:/tmp/rootpw
.Ve
.PP
-Створити образ Fedora 25. Пароль користувача root буде запозичено з файла
-\&\fI/tmp/rootpw\fR.
+Створити образ Fedora 25. Пароль користувача root буде запозичено з файла \fI/tmp/rootpw\fR.
.PP
-Зауважте, що якщо ви \fIне встановите\fR \fI\-\-root\-password\fR, гостьовій системі
-буде надано \fIвипадковий\fR пароль адміністратора root, який буде виведено до
-стандартного виведення.
+Зауважте, що якщо ви \fIне встановите\fR \fI\-\-root\-password\fR, гостьовій системі буде надано \fIвипадковий\fR пароль адміністратора root, який буде виведено до стандартного виведення.
.PP
-Крім того, ви можете створювати облікові записи
-користувачів. Див. \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" нижче.
+Крім того, ви можете створювати облікові записи користувачів. Див. \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" нижче.
.SS "Встановити назву вузла"
.IX Subsection "Встановити назву вузла"
.Vb 1
Встановити назву вузла \f(CW\*(C`virt.example.com\*(C'\fR.
.SS "Встановлення програмного забезпечення"
.IX Subsection "Встановлення програмного забезпечення"
-Встановлення пакунків зі звичайного (гостьового) сховища (наприклад, за
-допомогою dnf або apt):
+Встановлення пакунків зі звичайного (гостьового) сховища (наприклад, за допомогою dnf або apt):
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-install "inkscape,@Xfce Desktop"
.Ve
.PP
-(У Fedora \f(CW\*(C`@\*(C'\fR використовується для встановлення груп пакунків. У Debian вам
-доведеться встановлювати відповідний метапакунок.)
+(У Fedora \f(CW\*(C`@\*(C'\fR використовується для встановлення груп пакунків. У Debian вам доведеться встановлювати відповідний метапакунок.)
.PP
Для оновлення встановлених пакунків до останньої версії виконайте такі дії:
.PP
\& virt\-builder debian\-7 \-\-update
.Ve
.PP
-Для гостьових систем, де використовується SELinux, зокрема Fedora і Red Hat
-Enterprise Linux, може знадобитися зміна міток SELinux після встановлення
-або оновлення пакунків (див. \*(L"\s-1SELINUX\*(R"\s0 нижче):
+Для гостьових систем, де використовується SELinux, зокрема Fedora і Red Hat Enterprise Linux, може знадобитися зміна міток SELinux після встановлення або оновлення пакунків (див. \*(L"\s-1SELINUX\*(R"\s0 нижче):
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-update \-\-selinux\-relabel
.Ve
.SS "Налаштовування встановленої системи"
.IX Subsection "Налаштовування встановленої системи"
-Передбачено багато параметрів, за допомогою яких ви можете налаштувати
-встановлення. Це зокрема параметр \fI\-\-run\fR/\fI\-\-run\-command\fR, за допомогою
-якого можна виконати скрипт оболонки або команду під час створення образу
-диска і додати або змінити файли, які буде включено до образу диска. За
-допомогою параметра \fI\-\-firstboot\fR/\fI\-\-firstboot\-command\fR можна додати
-скрипти або команди, які буде виконано під час першого завантаження
-гостьової системи. За допомогою параметра \fI\-\-edit\fR можна редагувати файли,
-а параметра \fI\-\-upload\fR — вивантажувати файли до образу.
+Передбачено багато параметрів, за допомогою яких ви можете налаштувати встановлення. Це зокрема параметр \fI\-\-run\fR/\fI\-\-run\-command\fR, за допомогою якого можна виконати скрипт оболонки або команду під час створення образу диска і додати або змінити файли, які буде включено до образу диска. За допомогою параметра \fI\-\-firstboot\fR/\fI\-\-firstboot\-command\fR можна додати скрипти або команди, які буде виконано під час першого завантаження гостьової системи. За допомогою параметра \fI\-\-edit\fR можна редагувати файли, а параметра \fI\-\-upload\fR — вивантажувати файли до образу.
.PP
Приклад:
.PP
\& virt\-builder fedora\-27 \-\-firstboot\-command \*(Aqdnf \-y \-\-best update\*(Aq
.Ve
.PP
-у результаті команду \fBdnf\fR\|(8) \f(CW\*(C`update\*(C'\fR буде один раз виконано під час
-першого завантаження гостьової системи.
+у результаті команду \fBdnf\fR\|(8) \f(CW\*(C`update\*(C'\fR буде один раз виконано під час першого завантаження гостьової системи.
.PP
або
.PP
\& s/gpgcheck=1/gpgcheck=0/\*(Aq
.Ve
.PP
-буде змінено \fI/etc/dnf/dnf.conf\fR у образі диска (під час створення образу
-диска, задовго до завантаження).
+буде змінено \fI/etc/dnf/dnf.conf\fR у образі диска (під час створення образу диска, задовго до завантаження).
.PP
Ви можете поєднувати ці параметри і додавати декілька параметрів усіх типів.
.SH "ПАРАМЕТРИ"
Показати довідкове повідомлення.
.IP "\fB\-\-arch\fR АРХІТЕКТУРА" 4
.IX Item "--arch АРХІТЕКТУРА"
-Використовувати для образу\-результату вказану архітектуру. Це означає, що
-мають бути початкові коди шаблона для вказаної архітектури.
+Використовувати для образу\-результату вказану архітектуру. Це означає, що мають бути початкові коди шаблона для вказаної архітектури.
.Sp
Див. також \*(L"АРХІТЕКТУРА\*(R".
.IP "\fB\-\-attach\fR ФАЙЛ_ISO" 4
.IX Item "--attach ФАЙЛ_ISO"
-Під час етапу налаштовування вказаний диск долучається до базової системи
-libguestfs. Цей диск використовується для отримання даних додаткових сховищ
-програмного забезпечення або інших даних для створення нетипової системи.
+Під час етапу налаштовування вказаний диск долучається до базової системи libguestfs. Цей диск використовується для отримання даних додаткових сховищ програмного забезпечення або інших даних для створення нетипової системи.
.Sp
-Ймовірно, вам варто додати мітки для долучених дисків (або скористатися
-назвою тому \s-1ISO\s0), щоб надалі монтувати диски за міткою у ваших скриптах
-запуску:
+Ймовірно, вам варто додати мітки для долучених дисків (або скористатися назвою тому \s-1ISO\s0), щоб надалі монтувати диски за міткою у ваших скриптах запуску:
.Sp
.Vb 2
\& mkdir /tmp/mount
\& mount LABEL=EXTRA /tmp/mount
.Ve
.Sp
-Параметр \fI\-\-attach\fR можна вказати декілька разів, а форматом може бути
-будь\-який формат образу (не лише \s-1ISO\s0).
+Параметр \fI\-\-attach\fR можна вказати декілька разів, а форматом може бути будь\-який формат образу (не лише \s-1ISO\s0).
.Sp
-Див. також \fI\-\-run\fR, \*(L"Встановлення пакунків зі стороннього сховища під час
-збирання\*(R", \fBgenisoimage\fR\|(1), \fBvirt\-make\-fs\fR\|(1).
+Див. також \fI\-\-run\fR, \*(L"Встановлення пакунків зі стороннього сховища під час збирання\*(R", \fBgenisoimage\fR\|(1), \fBvirt\-make\-fs\fR\|(1).
.IP "\fB\-\-attach\-format\fR ФОРМАТ" 4
.IX Item "--attach-format ФОРМАТ"
-Вказати формат диска для наступного параметра \fI\-\-attach\fR. Значенням
-аргументу \f(CW\*(C`ФОРМАТ\*(C'\fR зазвичай є \f(CW\*(C`raw\*(C'\fR або \f(CW\*(C`qcow2\*(C'\fR. Для образів \s-1ISO\s0
-скористайтеся варіантом \f(CW\*(C`raw\*(C'\fR.
+Вказати формат диска для наступного параметра \fI\-\-attach\fR. Значенням аргументу \f(CW\*(C`ФОРМАТ\*(C'\fR зазвичай є \f(CW\*(C`raw\*(C'\fR або \f(CW\*(C`qcow2\*(C'\fR. Для образів \s-1ISO\s0 скористайтеся варіантом \f(CW\*(C`raw\*(C'\fR.
.IP "\fB\-\-cache\fR КАТАЛОГ" 4
.IX Item "--cache КАТАЛОГ"
.PD 0
.IP "\fB\-\-no\-cache\fR" 4
.IX Item "--no-cache"
.PD
-\&\fI\-\-cache\fR КАТАЛОГ встановлює каталог зберігання і пошуку файлів кешованих
-шаблонів. Якщо значення не встановлено, типовим значенням буде
-\&\fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR або \fI\f(CI$HOME\fI/.cache/virt\-builder/\fR.
+\&\fI\-\-cache\fR КАТАЛОГ встановлює каталог зберігання і пошуку файлів кешованих шаблонів. Якщо значення не встановлено, типовим значенням буде \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR або \fI\f(CI$HOME\fI/.cache/virt\-builder/\fR.
.Sp
\&\fI\-\-no\-cache\fR вимикає кешування шаблонів.
.IP "\fB\-\-cache\-all\-templates\fR" 4
.IX Item "--cache-all-templates"
Отримати усі шаблони до кешу і завершити роботу. Див. \*(L"КЕШУВАННЯ\*(R".
.Sp
-Зауважте, що кешуються не усі дані. Можна вивантажити додаткові
-шаблони. Крім того, не кешуються пакунки (параметри \fI\-\-install\fR,
-\&\fI\-\-update\fR).
+Зауважте, що кешуються не усі дані. Можна вивантажити додаткові шаблони. Крім того, не кешуються пакунки (параметри \fI\-\-install\fR, \fI\-\-update\fR).
.IP "\fB\-\-check\-signature\fR" 4
.IX Item "--check-signature"
.PD 0
.IP "\fB\-\-no\-check\-signature\fR" 4
.IX Item "--no-check-signature"
.PD
-Перевіряти чи не перевіряти цифровий підпис шаблону операційної
-системи. Типово, програма перевіряє підпис і завершує роботу, якщо підпис не
-збігається із еталонним. Обійти цю перевірку можна за допомогою параметра
-\&\fI\-\-no\-check\-signature\fR.
+Перевіряти чи не перевіряти цифровий підпис шаблону операційної системи. Типово, програма перевіряє підпис і завершує роботу, якщо підпис не збігається із еталонним. Обійти цю перевірку можна за допомогою параметра \fI\-\-no\-check\-signature\fR.
.Sp
Див. також \fI\-\-fingerprint\fR.
.IP "\fB\-\-colors\fR" 4
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-\-curl\fR \s-1CURL\s0" 4
.IX Item "--curl CURL"
-Вказати альтернативний виконуваний файл \fBcurl\fR\|(1). Ви також можете
-скористатися цим параметром для додавання параметрів curl, наприклад, щоб
-вимкнути перевірку сертифікатів https:
+Вказати альтернативний виконуваний файл \fBcurl\fR\|(1). Ви також можете скористатися цим параметром для додавання параметрів curl, наприклад, щоб вимкнути перевірку сертифікатів https:
.Sp
.Vb 1
\& virt\-builder \-\-curl "curl \-\-insecure" [...]
Вилучити кеш шаблонів. Див. \*(L"КЕШУВАННЯ\*(R".
.IP "\fB\-\-no\-delete\-on\-failure\fR" 4
.IX Item "--no-delete-on-failure"
-Не вилучати файл виведених даних, якщо під час збирання станеться
-помилка. Даними з цього файла можна скористатися для діагностування причин
-помилки. Див. \*(L"ДІАГНОСТИЧНІ ЗБІРКИ\*(R", щоб дізнатися більше про діагностику
-образів.
-.Sp
-Типовою є поведінка, коли файл результатів буде вилучено, якщо станеться
-помилка у virt-builder (або, наприклад, помилка у одному зі скриптів, які
-запускає ця програма).
+Не вилучати файл виведених даних, якщо під час збирання станеться помилка. Даними з цього файла можна скористатися для діагностування причин помилки. Див. \*(L"ДІАГНОСТИЧНІ ЗБІРКИ\*(R", щоб дізнатися більше про діагностику образів.
+.Sp
+Типовою є поведінка, коли файл результатів буде вилучено, якщо станеться помилка у virt-builder (або, наприклад, помилка у одному зі скриптів, які запускає ця програма).
.IP "\fB\-\-fingerprint\fR '\s-1AAAA BBBB ...\s0'" 4
.IX Item "--fingerprint 'AAAA BBBB ...'"
-Перевірка того, що покажчик та шаблони підписано ключем із вказаним
-відбитком (Відбитком, зазвичай, є доволі довгий рядок, що складається з 10
-груп 4 шістнадцяткових цифр).
-.Sp
-Ви можете скористатися цим параметром декілька разів. Якщо у вас декілька
-адрес початкового коду, у вас або не буде відбитка, або буде один відбиток
-або буде декілька відбитків. Якщо відбитків декілька, вам слід вказати для
-кожного адресу початкового коду.
+Перевірка того, що покажчик та шаблони підписано ключем із вказаним відбитком (Відбитком, зазвичай, є доволі довгий рядок, що складається з 10 груп 4 шістнадцяткових цифр).
+.Sp
+Ви можете скористатися цим параметром декілька разів. Якщо у вас декілька адрес початкового коду, у вас або не буде відбитка, або буде один відбиток або буде декілька відбитків. Якщо відбитків декілька, вам слід вказати для кожного адресу початкового коду.
.IP "\fB\-\-format\fR qcow2" 4
.IX Item "--format qcow2"
.PD 0
.IP "\fB\-\-format\fR raw" 4
.IX Item "--format raw"
.PD
-Для звичайних процедур збирання визначає формат виведення даних. Типовим
-значенням є \fIraw\fR.
+Для звичайних процедур збирання визначає формат виведення даних. Типовим значенням є \fIraw\fR.
.Sp
З \fI\-\-get\-kernel\fR визначає формат вхідних даних.
.Sp
-Для створення файла qcow2 у застарілому стилі (для сумісності з \s-1RHEL 6\s0 або
-дуже старим qemu < 1.1) після виконання програми virt-builder
-скористайтеся такою командою:
+Для створення файла qcow2 у застарілому стилі (для сумісності з \s-1RHEL 6\s0 або дуже старим qemu < 1.1) після виконання програми virt-builder скористайтеся такою командою:
.Sp
.Vb 1
\& qemu\-img amend \-f qcow2 \-o compat=0.10 output.qcow2
.Ve
.IP "\fB\-\-get\-kernel\fR ОБРАЗ" 4
.IX Item "--get-kernel ОБРАЗ"
-За допомогою цього параметра можна видобути ядро і initramfs з раніше
-зібраного образу диска із назвою \f(CW\*(C`ОБРАЗ\*(C'\fR (фактично, це працює для
-будь\-якого образу диска віртуальної машини, не лише для образів, які зібрано
-за допомогою virt-builder).
-.Sp
-Зауважте, що цей метод є \fBзастарілим\fR: для виконання цього завдання є
-окрема програма, \fBvirt\-get\-kernel\fR\|(1), у якій передбачено більше варіантів
-видобування файлів.
-.Sp
-Ядро і initramfs буде записано до поточного каталогу, якщо ви не вкажете
-додатково назву каталогу результатів за допомогою параметра \fI\-\-output\fR
-\&\f(CW\*(C`каталог результатівr\*(C'\fR.
-.Sp
-Формат образу диска буде визначено автоматично, якщо ви не вкажете його за
-допомогою параметра \fI\-\-format\fR.
-.Sp
-Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим
-номером. Щоб видобути із образу диска ядро з певним номером версії,
-скористайтеся \fBguestfish\fR\|(1). Щоб видобути із гостьової системи увесь вміст
-каталогу \fI/boot\fR, скористайтеся \fBvirt\-copy\-out\fR\|(1).
+За допомогою цього параметра можна видобути ядро і initramfs з раніше зібраного образу диска із назвою \f(CW\*(C`ОБРАЗ\*(C'\fR (фактично, це працює для будь\-якого образу диска віртуальної машини, не лише для образів, які зібрано за допомогою virt-builder).
+.Sp
+Зауважте, що цей метод є \fBзастарілим\fR: для виконання цього завдання є окрема програма, \fBvirt\-get\-kernel\fR\|(1), у якій передбачено більше варіантів видобування файлів.
+.Sp
+Ядро і initramfs буде записано до поточного каталогу, якщо ви не вкажете додатково назву каталогу результатів за допомогою параметра \fI\-\-output\fR \f(CW\*(C`каталог результатівr\*(C'\fR.
+.Sp
+Формат образу диска буде визначено автоматично, якщо ви не вкажете його за допомогою параметра \fI\-\-format\fR.
+.Sp
+Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим номером. Щоб видобути із образу диска ядро з певним номером версії, скористайтеся \fBguestfish\fR\|(1). Щоб видобути із гостьової системи увесь вміст каталогу \fI/boot\fR, скористайтеся \fBvirt\-copy\-out\fR\|(1).
.IP "\fB\-\-gpg\fR \s-1GPG\s0" 4
.IX Item "--gpg GPG"
-Вказати альтернативний виконуваний файл \fBgpg\fR\|(1) (\s-1GNU\s0 Privacy
-Guard). Типово, virt-builder шукає \f(CW\*(C`gpg2\*(C'\fR або \f(CW\*(C`gpg\*(C'\fR у каталогах, вказаних
-за допомогою змінної \f(CW$PATH\fR.
+Вказати альтернативний виконуваний файл \fBgpg\fR\|(1) (\s-1GNU\s0 Privacy Guard). Типово, virt-builder шукає \f(CW\*(C`gpg2\*(C'\fR або \f(CW\*(C`gpg\*(C'\fR у каталогах, вказаних за допомогою змінної \f(CW$PATH\fR.
.Sp
-Ви можете скористатися цим параметром для додавання параметрів до основної
-програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
+Ви можете скористатися цим параметром для додавання параметрів до основної програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
.Sp
.Vb 1
\& virt\-builder \-\-gpg "gpg \-\-homedir /tmp" [...]
.IP "\fB\-\-list\fR \fB\-\-long\fR [версія ОС]" 4
.IX Item "--list --long [версія ОС]"
.PD
-Вивести усі доступні шаблони, якщо не вказано гостьової системи, або вивести
-шаблони лише для вказаної гостьової системи.
+Вивести усі доступні шаблони, якщо не вказано гостьової системи, або вивести шаблони лише для вказаної гостьової системи.
.Sp
-Ви можете вибрати формат виведення за допомогою параметра \fI\-\-list\-format\fR
-для шаблонів списку:
+Ви можете вибрати формат виведення за допомогою параметра \fI\-\-list\-format\fR для шаблонів списку:
.RS 4
.IP "\fBshort\fR" 4
.IX Item "short"
-Типовий формат: виводиться лише ідентифікатор шаблона і, поряд з ним, його
-короткий опис.
+Типовий формат: виводиться лише ідентифікатор шаблона і, поряд з ним, його короткий опис.
.IP "\fBlong\fR" 4
.IX Item "long"
-Виводить тестовий список із даними щодо доступних джерел і список даних щодо
-доступних шаблонів після нього.
+Виводить тестовий список із даними щодо доступних джерел і список даних щодо доступних шаблонів після нього.
.IP "\fBjson\fR" 4
.IX Item "json"
-Вивести об’єкт \s-1JSON\s0 із подробицями щодо доступних джерел та подробиці щодо
-доступних шаблонів.
+Вивести об’єкт \s-1JSON\s0 із подробицями щодо доступних джерел та подробиці щодо доступних шаблонів.
.Sp
-Ключ \f(CW\*(C`version\*(C'\fR у основному об'єкті визначає «версію сумісності», його
-значення слід збільшувати кожного разу, коли результат використання \s-1JSON\s0
-ставатиме несумісним із попередніми версіями (наприклад, через зміну
-структури або прибирання основних ключів).
+Ключ \f(CW\*(C`version\*(C'\fR у основному об'єкті визначає «версію сумісності», його значення слід збільшувати кожного разу, коли результат використання \s-1JSON\s0 ставатиме несумісним із попередніми версіями (наприклад, через зміну структури або прибирання основних ключів).
.RE
.RS 4
.Sp
.IP "\fB\-\-machine\-readable\fR=формат" 4
.IX Item "--machine-readable=формат"
.PD
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
.IP "\fB\-m\fR МБ" 4
.IX Item "-m МБ"
.PD 0
.IP "\fB\-\-memsize\fR МБ" 4
.IX Item "--memsize МБ"
.PD
-Зміна обсягу пам'яті, наданого скриптам \fI\-\-run\fR. Збільште це значення, якщо
-виявиться, що для використання скриптів \fI\-\-run\fR або параметра \fI\-\-install\fR
-не вистачає пам'яті.
+Зміна обсягу пам'яті, наданого скриптам \fI\-\-run\fR. Збільште це значення, якщо виявиться, що для використання скриптів \fI\-\-run\fR або параметра \fI\-\-install\fR не вистачає пам'яті.
.Sp
Типові значення можна визначити за допомогою такої команди:
.Sp
.IP "\fB\-\-no\-network\fR" 4
.IX Item "--no-network"
.PD
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
.Sp
-Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути доступ.
.Sp
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
.Sp
-Якщо ви скористаєтеся параметром \fI\-\-no\-network\fR, тоді інші параметри,
-зокрема \fI\-\-install\fR, не працюватимуть.
+Якщо ви скористаєтеся параметром \fI\-\-no\-network\fR, тоді інші параметри, зокрема \fI\-\-install\fR, не працюватимуть.
.Sp
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-builder.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-builder.
.Sp
-Загалом кажучи, вам \fIне варто\fR використовувати \fI\-\-no\-network\fR. Але ось
-декілька випадків, коли у вас може виникнути потреба у використанні цього
-параметра:
+Загалом кажучи, вам \fIне варто\fR використовувати \fI\-\-no\-network\fR. Але ось декілька випадків, коли у вас може виникнути потреба у використанні цього параметра:
.RS 4
.IP "1." 4
-У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки
-мережі. (Див. \*(L"МОДУЛЬ\*(R" in \fBguestfs\fR\|(3)).
+У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки мережі. (Див. \*(L"МОДУЛЬ\*(R" in \fBguestfs\fR\|(3)).
.IP "2." 4
-Усе програмне забезпечення, яке ви маєте намір встановити, походить з
-долученого образу \s-1ISO,\s0 отже потреби у мережі немає.
+Усе програмне забезпечення, яке ви маєте намір встановити, походить з долученого образу \s-1ISO,\s0 отже потреби у мережі немає.
.IP "3." 4
-Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати
-доступ до мережевого з'єднання вашої основної системи під час роботи
-virt-builder. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу
-шаблонів операційних систем. (Див. \*(L"БЕЗПЕКА\*(R" нижче).
+Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати доступ до мережевого з'єднання вашої основної системи під час роботи virt-builder. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу шаблонів операційних систем. (Див. \*(L"БЕЗПЕКА\*(R" нижче).
.IP "4." 4
-Ви не хочете користуватися мережею основної системи (наприклад, через
-захищеність або обмеженість середовища у ній).
+Ви не хочете користуватися мережею основної системи (наприклад, через захищеність або обмеженість середовища у ній).
.RE
.RS 4
.RE
.IX Item "--no-sync"
Не синхронізувати файл виведення під час завершення роботи.
.Sp
-Virt-builder виконує синхронізацію \f(CW\*(C`fsync\*(C'\fR файла результатів або образу
-диска, якщо такий існує.
+Virt-builder виконує синхронізацію \f(CW\*(C`fsync\*(C'\fR файла результатів або образу диска, якщо такий існує.
.Sp
-Причина полягає у тому, що типовим режимом кешування у qemu та \s-1KVM\s0 є \f(CW\*(C`none\*(C'\fR
-або \f(CW\*(C`directsync\*(C'\fR, і у обох цих режимах не використовується кеш сторінок
-основної системи. Тому ці режими не працюватимуть належним чином, якщо ви
-негайно запустите гостьову систему після запуску virt-builder — гостьова
-система просто не побачить файл результатів повністю . (Зауважте, що вам не
-варто користуватися обома цими режимами кешування — вони непрацездатні на
-базовому рівні з цієї та інших причин.)
+Причина полягає у тому, що типовим режимом кешування у qemu та \s-1KVM\s0 є \f(CW\*(C`none\*(C'\fR або \f(CW\*(C`directsync\*(C'\fR, і у обох цих режимах не використовується кеш сторінок основної системи. Тому ці режими не працюватимуть належним чином, якщо ви негайно запустите гостьову систему після запуску virt-builder — гостьова система просто не побачить файл результатів повністю . (Зауважте, що вам не варто користуватися обома цими режимами кешування — вони непрацездатні на базовому рівні з цієї та інших причин.)
.Sp
-Якщо ви не використовуєте ці помилкові режими кешування, ви можете
-скористатися параметром \fI\-\-no\-sync\fR, щоб усунути непотрібну синхронізацію і
-значно пришвидшити роботу програми.
+Якщо ви не використовуєте ці помилкові режими кешування, ви можете скористатися параметром \fI\-\-no\-sync\fR, щоб усунути непотрібну синхронізацію і значно пришвидшити роботу програми.
.IP "\fB\-\-notes\fR версія\-ОС" 4
.IX Item "--notes версія-ОС"
-Показує список нотаток, пов’язаних із гостьовою системою, потім завершує
-роботу (встановлення не виконується).
+Показує список нотаток, пов’язаних із гостьовою системою, потім завершує роботу (встановлення не виконується).
.IP "\fB\-o\fR назва_файла" 4
.IX Item "-o назва_файла"
.PD 0
.IP "\fB\-\-output\fR назва_файла" 4
.IX Item "--output назва_файла"
.PD
-Записати виведені дані до файла \fIназва_файла\fR. Якщо цей параметр не буде
-вказано, назву файла для виведення даних буде створено на основі рядка
-\&\f(CW\*(C`версія\-ос\*(C'\fR із додаванням суфікса \f(CW\*(C`.img\*(C'\fR (для формату без обробки) або
-\&\f(CW\*(C`.qcow2\*(C'\fR (для формату qcow2).
+Записати виведені дані до файла \fIназва_файла\fR. Якщо цей параметр не буде вказано, назву файла для виведення даних буде створено на основі рядка \f(CW\*(C`версія\-ос\*(C'\fR із додаванням суфікса \f(CW\*(C`.img\*(C'\fR (для формату без обробки) або \f(CW\*(C`.qcow2\*(C'\fR (для формату qcow2).
.Sp
-Зауважте, що назвою файла виведення результатів може бути пристрій, розділ
-або логічний том.
+Зауважте, що назвою файла виведення результатів може бути пристрій, розділ або логічний том.
.Sp
-Якщо використовується з \fI\-\-get\-kernel\fR, цей параметр задає каталог
-виведення даних.
+Якщо використовується з \fI\-\-get\-kernel\fR, цей параметр задає каталог виведення даних.
.IP "\fB\-\-print\-cache\fR" 4
.IX Item "--print-cache"
Вивести інформацію щодо кешу шаблонів. Див. \*(L"КЕШУВАННЯ\*(R".
Не виводити звичайних повідомлень щодо поступу.
.IP "\fB\-\-size\fR РОЗМІР" 4
.IX Item "--size РОЗМІР"
-Вибір розміру диска\-результату, де розмір можна вказати за допомогою типових
-записів, зокрема \f(CW\*(C`32G\*(C'\fR (32 гігабайти) тощо.
+Вибір розміру диска\-результату, де розмір можна вказати за допомогою типових записів, зокрема \f(CW\*(C`32G\*(C'\fR (32 гігабайти) тощо.
.Sp
Virt-builder змінить розміри файлових систем у образі диска автоматично.
.Sp
-Якщо розмір не задано, можлива реалізація двох сценаріїв. Якщо дані
-виводяться до файла, його розмір буде таким самим, як у шаблона. Якщо дані
-виводяться на пристрій, розділ тощо, буде використано розмір відповідного
-пристрою.
+Якщо розмір не задано, можлива реалізація двох сценаріїв. Якщо дані виводяться до файла, його розмір буде таким самим, як у шаблона. Якщо дані виводяться на пристрій, розділ тощо, буде використано розмір відповідного пристрою.
.Sp
-Щоб вказати розмір у байтах, додайте до числа малу літеру \fIb\fR, наприклад
-\&\f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
+Щоб вказати розмір у байтах, додайте до числа малу літеру \fIb\fR, наприклад \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
.IP "\fB\-\-smp\fR N" 4
.IX Item "--smp N"
-Увімкнути N ≥ 2 віртуальних процесорів для використання у скриптах
-\&\fI\-\-run\fR.
+Увімкнути N ≥ 2 віртуальних процесорів для використання у скриптах \fI\-\-run\fR.
.IP "\fB\-\-source\fR АДРЕСА" 4
.IX Item "--source АДРЕСА"
Встановити адресу початкових даних для пошуку покажчиків.
.Sp
Див. також \*(L"ДЖЕРЕЛА ШАБЛОНІВ\*(R" нижче.
.Sp
-Зауважте, що не варто вказувати для \fI\-\-source\fR джерела, яким ви не
-довіряєте (якщо їх не підписано кимось, кому ви довіряєте). Див. також
-параметр \fI\-\-no\-network\fR.
+Зауважте, що не варто вказувати для \fI\-\-source\fR джерела, яким ви не довіряєте (якщо їх не підписано кимось, кому ви довіряєте). Див. також параметр \fI\-\-no\-network\fR.
.IP "\fB\-\-no\-warn\-if\-partition\fR" 4
.IX Item "--no-warn-if-partition"
-Не видавати попередження, якщо пристроєм виведення даних є розділ. Це
-попередження надає змогу уникнути типової помилки користувача під час
-записування на флеш\-накопичувач \s-1USB\s0 або зовнішній диск — запису на розділ,
-коли слід виконувати перезапис усього пристрою (\fI\-\-output /dev/sdX\fR), а
-не розділу на ньому (\fI\-\-output /dev/sdX1\fR). Скористайтеся цим
-параметром, щоб \fIпридушити\fR відповідне попередження.
+Не видавати попередження, якщо пристроєм виведення даних є розділ. Це попередження надає змогу уникнути типової помилки користувача під час записування на флеш\-накопичувач \s-1USB\s0 або зовнішній диск — запису на розділ, коли слід виконувати перезапис усього пристрою (\fI\-\-output /dev/sdX\fR), а не розділу на ньому (\fI\-\-output /dev/sdX1\fR). Скористайтеся цим параметром, щоб \fIпридушити\fR відповідне попередження.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.PD
Увімкнути діагностичні повідомлення і/або режим докладних повідомлень.
.Sp
-Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі
-виведені дані до звіту щодо вади.
+Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі виведені дані до звіту щодо вади.
.IP "\fB\-V\fR" 4
.IX Item "-V"
.PD 0
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.IX Subsection "Параметри налаштовування"
.IP "\fB\-\-append\-line\fR ФАЙЛ:РЯДОК" 4
.IX Item "--append-line ФАЙЛ:РЯДОК"
-Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується
-порожнім рядком, такий рядок буде додано перед дописаним. Крім того,
-автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
+Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується порожнім рядком, такий рядок буде додано перед дописаним. Крім того, автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
.Sp
-Наприклад, (припускаємо, що у командній оболонці використовуються звичайні
-лапки) така команда:
+Наприклад, (припускаємо, що у командній оболонці використовуються звичайні лапки) така команда:
.Sp
.Vb 1
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде
-додано, лише якщо наявний файл ще не закінчується символом нового рядка.
+додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде додано, лише якщо наявний файл ще не закінчується символом нового рядка.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за
-наявним вмістом файла, отже, команда обробляє файли однаково правильно для
-варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для
-порожніх і ще не створених файлів.
+\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за наявним вмістом файла, отже, команда обробляє файли однаково правильно для варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для порожніх і ще не створених файлів.
.Sp
-Щоб додати декілька рядків, скористайтеся тим самим параметром декілька
-разів:
+Щоб додати декілька рядків, скористайтеся тим самим параметром декілька разів:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.2 bar\*(Aq
.Ve
.Sp
-Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою
-конструкцією:
+Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою конструкцією:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:\*(Aq
.IX Item "--chmod ПРАВА_ДОСТУПУ:ФАЙЛ"
Змінити права доступу до файла \f(CW\*(C`ФАЙЛ\*(C'\fR на \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR.
.Sp
-\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі,
-якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто
-скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
+\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі, якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
.IP "\fB\-\-commands\-from\-file\fR НАЗВА_ФАЙЛА" 4
.IX Item "--commands-from-file НАЗВА_ФАЙЛА"
-Прочитати команди налаштовування з файла, по одній (разом із аргументами) на
-рядок.
+Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.
.Sp
Кожен рядок містить команду налаштовування та її аргументи, наприклад:
.Sp
\& password якийсь\-користувач:password:його\-новий\-пароль
.Ve
.Sp
-Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і
-також ігноруються. Крім того, аргументи можна розділити на декілька рядків
-додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
+Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і також ігноруються. Крім того, аргументи можна розділити на декілька рядків додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
.Sp
.Vb 2
\& edit /якийсь/файл:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так,
-наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
+Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так, наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
.IP "\fB\-\-copy\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ" 4
.IX Item "--copy ДЖЕРЕЛО:ПРИЗНАЧЕННЯ"
Копіювати файли або каталоги рекурсивно у межах гостьової системи.
Не можна використовувати символи\-замінники.
.IP "\fB\-\-copy\-in\fR ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ" 4
.IX Item "--copy-in ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ"
-Скопіювати локальні файли або каталоги рекурсивно до образу диска,
-розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
+Скопіювати локальні файли або каталоги рекурсивно до образу диска, розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
.Sp
Не можна використовувати символи\-замінники.
.IP "\fB\-\-delete\fR ШЛЯХ" 4
.IX Item "--delete ШЛЯХ"
-Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
-рекурсивно).
+Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст, рекурсивно).
.Sp
-Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте
-екранувати символи\-замінники у командній оболонці основної системи, якщо це
-потрібно. Приклад:
+Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте екранувати символи\-замінники у командній оболонці основної системи, якщо це потрібно. Приклад:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
.IX Item "--edit ФАЙЛ:ВИРАЗ"
Редагувати \f(CW\*(C`ФАЙЛ\*(C'\fR з використанням виразу Perl \f(CW\*(C`ВИРАЗ\*(C'\fR.
.Sp
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
.Sp
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
.Sp
Див. \*(L"NON-INTERACTIVE \s-1EDITING\*(R"\s0 in \fBvirt\-edit\fR\|(1).
.IP "\fB\-\-firstboot\fR СКРИПТ" 4
.IX Item "--firstboot СКРИПТ"
-Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-До скрипту, після встановлення до гостьової системи, буде автоматично
-застосовано команду chmod +x.
+До скрипту, після встановлення до гостьової системи, буде автоматично застосовано команду chmod +x.
.Sp
-Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно
-включає команду у однорядковому скрипті.
+Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно включає команду у однорядковому скрипті.
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R", щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R", щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-command\fR 'КОМАНДА+ПАРАМЕТРИ'" 4
.IX Item "--firstboot-command 'КОМАНДА+ПАРАМЕТРИ'"
-Виконати команду (разом із аргументами) у гостьовій системі під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Виконати команду (разом із аргументами) у гостьовій системі під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R", щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R", щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-install\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--firstboot-install ПАКУНОК,ПАКУНОК.."
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час першого завантаження гостьової системи за
-допомогою програми для керування пакунків гостьової системи (наприклад, apt,
-yum тощо) і з'єднання із мережею гостьової системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час першого завантаження гостьової системи за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею гостьової системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R".
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R".
.IP "\fB\-\-hostname\fR НАЗВА_ВУЗЛА" 4
.IX Item "--hostname НАЗВА_ВУЗЛА"
-Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо
-потрібно, можете скористатися форматом із крапкою,
-«назва_вузла.назва_домену» (\s-1FQDN\s0).
+Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо потрібно, можете скористатися форматом із крапкою, «назва_вузла.назва_домену» (\s-1FQDN\s0).
.IP "\fB\-\-install\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--install ПАКУНОК,ПАКУНОК.."
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання
-із мережею основної системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею основної системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R".
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R".
.Sp
Див. також \fI\-\-update\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-link\fR ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..]" 4
.IX Item "--link ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..]"
-Створити символічне посилання або декілька посилань у гостьовій системі так,
-щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
+Створити символічне посилання або декілька посилань у гостьовій системі так, щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
.IP "\fB\-\-mkdir\fR КАТАЛОГ" 4
.IX Item "--mkdir КАТАЛОГ"
Створити каталог у гостьовій системі.
.Sp
-Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні
-каталоги. Також команда працює, якщо каталог вже існує.
+Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні каталоги. Також команда працює, якщо каталог вже існує.
.IP "\fB\-\-move\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ" 4
.IX Item "--move ДЖЕРЕЛО:ПРИЗНАЧЕННЯ"
Пересунути файли або каталоги у межах гостьової системи.
Не можна використовувати символи\-замінники.
.IP "\fB\-\-no\-logfile\fR" 4
.IX Item "--no-logfile"
-Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після
-завершення збирання. Якщо ви не хочете явним чином показувати, як було
-зібрано образ, скористайтеся цим параметром.
+Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після завершення збирання. Якщо ви не хочете явним чином показувати, як було зібрано образ, скористайтеся цим параметром.
.Sp
Див. також \*(L"\s-1LOG FILE\*(R"\s0.
.IP "\fB\-\-password\fR КОРИСТУВАЧ:ВАРІАНТ" 4
.IX Item "--password КОРИСТУВАЧ:ВАРІАНТ"
-Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою
-цього параметра \fIне можна\fR створювати облікові записи користувачів.)
+Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою цього параметра \fIне можна\fR створювати облікові записи користувачів.)
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R".
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R".
.IP "\fB\-\-password\-crypto\fR md5|sha256|sha512" 4
.IX Item "--password-crypto md5|sha256|sha512"
-Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою
-цього параметра можна встановити шифрування для цього пароля у значення
-\&\f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
-.Sp
-Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc
-≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
-.Sp
-\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux
-(наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
-.Sp
-Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо
-libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо
-такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою
-цього параметра ви можете перевизначити автоматично визначений libguestfs
-спосіб шифрування.
-.Sp
-Зауважте, що це не змінить типового шифрування, яке використовується
-гостьовою системою, коли ви створюєте у ній нові облікові записи
-користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися
-параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR
-(Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
+Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою цього параметра можна встановити шифрування для цього пароля у значення \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
+.Sp
+Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc ≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
+.Sp
+\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux (наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
+.Sp
+Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою цього параметра ви можете перевизначити автоматично визначений libguestfs спосіб шифрування.
+.Sp
+Зауважте, що це не змінить типового шифрування, яке використовується гостьовою системою, коли ви створюєте у ній нові облікові записи користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.IP "\fB\-\-root\-password\fR ВАРІАНТ" 4
.IX Item "--root-password ВАРІАНТ"
Встановити пароль користувача root.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R".
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R".
.Sp
-Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для
-гостьової системи буде використано \fIвипадковий\fR пароль root.
+Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для гостьової системи буде використано \fIвипадковий\fR пароль root.
.IP "\fB\-\-run\fR СКРИПТ" 4
.IX Item "--run СКРИПТ"
-Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR
-у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій
-допоміжній системі, у пісочниці гостьової файлової системи.
+Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
Для скрипту буде автоматично використано команду chmod +x.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому
-порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-run\-command\fR 'КОМАНДА+ПАРАМЕТРИ'" 4
.IX Item "--run-command 'КОМАНДА+ПАРАМЕТРИ'"
-Виконати команду із аргументами у образі диска. Команду буде виконано у
-віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової
-файлової системи.
+Виконати команду із аргументами у образі диска. Команду буде виконано у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-scrub\fR ФАЙЛ" 4
.RE
.IP "\fB\-\-selinux\-relabel\fR" 4
.IX Item "--selinux-relabel"
-Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були
-правильними з точки зору SELinux.
+Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були правильними з точки зору SELinux.
.Sp
-Якщо буде використано цей параметр, програма спробує змінити мітки файлів
-негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла
-\&\fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на
-наступне завантаження образу.
+Якщо буде використано цей параметр, програма спробує змінити мітки файлів негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла \fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на наступне завантаження образу.
.Sp
-Вам слід використовувати цей параметр лише для гостьових систем із
-підтримкою SELinux.
+Вам слід використовувати цей параметр лише для гостьових систем із підтримкою SELinux.
.IP "\fB\-\-sm\-attach\fR ВАРІАНТ" 4
.IX Item "--sm-attach ВАРІАНТ"
Долучити систему до буфера передплати за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R".
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R".
.IP "\fB\-\-sm\-credentials\fR ВАРІАНТ" 4
.IX Item "--sm-credentials ВАРІАНТ"
Встановити реєстраційні дані для \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R".
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R".
.IP "\fB\-\-sm\-register\fR" 4
.IX Item "--sm-register"
Зареєструвати гостьову систему за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
Потребує встановлення реєстраційних даних за допомогою \fI\-\-sm\-credentials\fR.
.IP "\fB\-\-sm\-remove\fR" 4
.IX Item "--sm-remove"
-Вилучити усі передплати з гостьової системи за допомогою
-\&\f(CW\*(C`subscription\-manager\*(C'\fR.
+Вилучити усі передплати з гостьової системи за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-sm\-unregister\fR" 4
.IX Item "--sm-unregister"
Зняти гостьову систему з реєстрації за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ[:ВАРІАНТ]" 4
.IX Item "--ssh-inject КОРИСТУВАЧ[:ВАРІАНТ]"
-Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з
-використанням ssh без потреби у визначенні пароля. Запис користувача
-\&\f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
+Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з використанням ssh без потреби у визначенні пароля. Запис користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
.Sp
Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"КЛЮЧІ \s-1SSH\*(R"\s0.
.Sp
-Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних
-користувачів, а також для додавання декількох ключів для кожного з
-користувачів.
+Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних користувачів, а також для додавання декількох ключів для кожного з користувачів.
.IP "\fB\-\-timezone\fR ЧАСОВИЙ_ПОЯС" 4
.IX Item "--timezone ЧАСОВИЙ_ПОЯС"
-Встановити типовий часовий пояс гостьової системи у значення
-\&\f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
+Встановити типовий часовий пояс гостьової системи у значення \f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
.IP "\fB\-\-touch\fR ФАЙЛ" 4
.IX Item "--touch ФАЙЛ"
Ця команда виконує подібну до \fBtouch\fR\|(1) дію над файлом \f(CW\*(C`ФАЙЛ\*(C'\fR.
.IP "\fB\-\-truncate\fR ФАЙЛ" 4
.IX Item "--truncate ФАЙЛ"
-Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного
-виконання файл має існувати.
+Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного виконання файл має існувати.
.IP "\fB\-\-truncate\-recursive\fR ШЛЯХ" 4
.IX Item "--truncate-recursive ШЛЯХ"
-Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової
-довжини.
+Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової довжини.
.IP "\fB\-\-uninstall\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--uninstall ПАКУНОК,ПАКУНОК.."
-Вилучити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде вилучено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою
-виконання запиту також може бути вилучено пакунки, залежні від вилучених
-пакунків.
+Вилучити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде вилучено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою виконання запиту також може бути вилучено пакунки, залежні від вилучених пакунків.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-update\fR.
.IP "\fB\-\-update\fR" 4
.IX Item "--update"
-Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої
-команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні,
-до найсвіжіших версій.
+Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні, до найсвіжіших версій.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-upload\fR ФАЙЛ:ПРИЗНАЧЕННЯ" 4
.IX Item "--upload ФАЙЛ:ПРИЗНАЧЕННЯ"
-Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі
-диска. Буде збережено власника і права доступу, отже вам слід вказати такі
-значення для цих параметрів, які мають бути на остаточному образі диска.
+Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі диска. Буде збережено власника і права доступу, отже вам слід вказати такі значення для цих параметрів, які мають бути на остаточному образі диска.
.Sp
-Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим
-можна скористатися для перейменовування файла під час вивантаження.
+Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим можна скористатися для перейменовування файла під час вивантаження.
.Sp
-Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має
-існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу,
-назву файла з локальної файлової системи буде збережено.
+Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу, назву файла з локальної файлової системи буде збережено.
.Sp
Див. також \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.IP "\fB\-\-write\fR ФАЙЛ:ДАНІ" 4
.IX Header "ДОВІДНИК"
.SS "ВСТАНОВЛЕННЯ ПАКУНКІВ"
.IX Subsection "ВСТАНОВЛЕННЯ ПАКУНКІВ"
-Існує декілька підходів до встановлення пакунків або програм у гостьовій
-системі, використання кожного з яких має власні переваги і недоліки.
+Існує декілька підходів до встановлення пакунків або програм у гостьовій системі, використання кожного з яких має власні переваги і недоліки.
.PP
\fIВстановлення пакунків під час збирання\fR
.IX Subsection "Встановлення пакунків під час збирання"
.PP
-Якщо гостьова операційна система є подібною до основної операційної системи
-(наприклад, обидві є операційними системами Linux), і у libguestfs
-передбачено підтримку з'єднань мережею, ви можете скористатися параметром
-\&\fI\-\-install\fR для встановлення пакунків у такий спосіб:
+Якщо гостьова операційна система є подібною до основної операційної системи (наприклад, обидві є операційними системами Linux), і у libguestfs передбачено підтримку з'єднань мережею, ви можете скористатися параметром \fI\-\-install\fR для встановлення пакунків у такий спосіб:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-install inkscape
.Ve
.PP
-Тут використано засіб керування пакунками гостьової системи і з'єднання із
-мережею основної системи.
+Тут використано засіб керування пакунками гостьової системи і з'єднання із мережею основної системи.
.PP
\fIОновлення пакунків під час збирання\fR
.IX Subsection "Оновлення пакунків під час збирання"
.PP
-Щоб оновити встановлений набір пакунків у шаблоні під час збирання, віддайте
-таку команду:
+Щоб оновити встановлений набір пакунків у шаблоні під час збирання, віддайте таку команду:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-update
.Ve
.PP
-У більшості шаблонів, які постачаються разом із virt-builder, передбачено
-дуже вузький набір пакунків (відомий як «JEOS» або «Just Enough Operating
-System» («Достатньо для того, щоб бути операційною системою»), які є
-актуальними на час створення шаблону, але можу виявитися застарілими на час,
-коли ви встановлюватимете операційну систему з шаблона. За допомогою цього
-параметра можна оновити пакунки з шаблона.
+У більшості шаблонів, які постачаються разом із virt-builder, передбачено дуже вузький набір пакунків (відомий як «JEOS» або «Just Enough Operating System» («Достатньо для того, щоб бути операційною системою»), які є актуальними на час створення шаблону, але можу виявитися застарілими на час, коли ви встановлюватимете операційну систему з шаблона. За допомогою цього параметра можна оновити пакунки з шаблона.
.PP
\fIВстановлення пакунків під час першого завантаження\fR
.IX Subsection "Встановлення пакунків під час першого завантаження"
.PP
-Іншим варіантом є встановлення пакунків під час першого завантаження
-гостьової системи:
+Іншим варіантом є встановлення пакунків під час першого завантаження гостьової системи:
.PP
.Vb 1
\& virt\-builder fedora\-27 \-\-firstboot\-install inkscape
.Ve
.PP
-Тут використано засіб керування пакунками гостьової системи і з'єднання із
-мережею гостьової системи.
+Тут використано засіб керування пакунками гостьової системи і з'єднання із мережею гостьової системи.
.PP
-Недоліком використання цього підходу є те, що гостьова система
-завантажуватиметься вперше набагато довше, а також те, що ви не зможете
-нічого зробити, якщо під час встановлення пакунків станеться помилка
-(наприклад, через проблеми із мережею гостьова система не зможе встановити
-зв'язок зі сховищем пакунків).
+Недоліком використання цього підходу є те, що гостьова система завантажуватиметься вперше набагато довше, а також те, що ви не зможете нічого зробити, якщо під час встановлення пакунків станеться помилка (наприклад, через проблеми із мережею гостьова система не зможе встановити зв'язок зі сховищем пакунків).
.PP
\fIВстановлення пакунків зі стороннього сховища під час збирання\fR
.IX Subsection "Встановлення пакунків зі стороннього сховища під час збирання"
.PP
-Якщо програмного забезпечення, яке ви хочете встановити, немає у основному
-сховищі пакунків гостьової системи, ви можете додати стороннє
-сховище. Зазвичай, таке сховище є файлом образу \s-1ISO\s0 (образом компакт\-диска),
-у якому містяться дані додаткових пакунків.
+Якщо програмного забезпечення, яке ви хочете встановити, немає у основному сховищі пакунків гостьової системи, ви можете додати стороннє сховище. Зазвичай, таке сховище є файлом образу \s-1ISO\s0 (образом компакт\-диска), у якому містяться дані додаткових пакунків.
.PP
-Ви можете створити образ диска за допомогою \fBgenisoimage\fR\|(1) або
-\&\fBvirt\-make\-fs\fR\|(1). Для genisoimage скористайтеся такою командою:
+Ви можете створити образ диска за допомогою \fBgenisoimage\fR\|(1) або \fBvirt\-make\-fs\fR\|(1). Для genisoimage скористайтеся такою командою:
.PP
.Vb 1
\& genisoimage \-o extra\-packages.iso \-R \-J \-V EXTRA cdcontents/
.Ve
.PP
-Створіть скрипт, який монтує \s-1ISO\s0 і налаштовує сховище. Для dnf створіть
-/tmp/install.sh з таким вмістом:
+Створіть скрипт, який монтує \s-1ISO\s0 і налаштовує сховище. Для dnf створіть /tmp/install.sh з таким вмістом:
.PP
.Vb 2
\& mkdir /tmp/mount
\& apt\-get \-y install famousdatabase
.Ve
.PP
-Скористайтеся параметром \fI\-\-attach\fR для долучення компакт\-диска або образу
-диска та параметром \fI\-\-run\fR для запуску скрипту:
+Скористайтеся параметром \fI\-\-attach\fR для долучення компакт\-диска або образу диска та параметром \fI\-\-run\fR для запуску скрипту:
.PP
.Vb 3
\& virt\-builder fedora\-27 \e
.Ve
.SS "КОРИСТУВАЧІ І ПАРОЛІ"
.IX Subsection "КОРИСТУВАЧІ І ПАРОЛІ"
-Параметр \fI\-\-root\-password\fR використовується для зміни пароля адміністратора
-(root) (якщо ви не скористаєтеся цим параметром, буде використано випадковий
-пароль). Цьому параметру можна передати \f(CW\*(C`ВАРІАНТ\*(C'\fR пароля у одному з таких
-форматів:
+Параметр \fI\-\-root\-password\fR використовується для зміни пароля адміністратора (root) (якщо ви не скористаєтеся цим параметром, буде використано випадковий пароль). Цьому параметру можна передати \f(CW\*(C`ВАРІАНТ\*(C'\fR пароля у одному з таких форматів:
.IP "\fB\-\-root\-password\fR file:НАЗВА_ФАЙЛА" 4
.IX Item "--root-password file:НАЗВА_ФАЙЛА"
-Прочитати пароль адміністратора з файла \f(CW\*(C`НАЗВА_ФАЙЛА\*(C'\fR. Паролем
-вважатиметься вміст усього першого рядка цього файла. Усі інші рядки файла
-буде проігноровано. Файл має бути створено із режимом доступу 0600, щоб його
-не могли читати сторонні користувачі.
+Прочитати пароль адміністратора з файла \f(CW\*(C`НАЗВА_ФАЙЛА\*(C'\fR. Паролем вважатиметься вміст усього першого рядка цього файла. Усі інші рядки файла буде проігноровано. Файл має бути створено із режимом доступу 0600, щоб його не могли читати сторонні користувачі.
.IP "\fB\-\-root\-password\fR password:ПАРОЛЬ" 4
.IX Item "--root-password password:ПАРОЛЬ"
Встановити для пароля root буквальне значення рядка \f(CW\*(C`ПАРОЛЬ\*(C'\fR.
.Sp
-\&\fBЗауваження: цей спосіб не є безпечним\fR, оскільки будь\-який користувач
-комп'ютера зможе побачити пароль явним чином за допомогою команди \fBps\fR\|(1).
+\&\fBЗауваження: цей спосіб не є безпечним\fR, оскільки будь\-який користувач комп'ютера зможе побачити пароль явним чином за допомогою команди \fBps\fR\|(1).
.IP "\fB\-\-root\-password\fR random" 4
.IX Item "--root-password random"
-Вибрати випадковий пароль, який буде виведено до stdout. Випадковість пароля
-наближено відповідатиме 120\-бітовій.
+Вибрати випадковий пароль, який буде виведено до stdout. Випадковість пароля наближено відповідатиме 120\-бітовій.
.Sp
Типове значення.
.IP "\fB\-\-root\-password\fR disabled" 4
.IX Item "--root-password disabled"
-Пароль для облікового запису root вимкнено. Це так, ніби у полі пароля
-використано \f(CW\*(C`*\*(C'\fR.
+Пароль для облікового запису root вимкнено. Це так, ніби у полі пароля використано \f(CW\*(C`*\*(C'\fR.
.IP "\fB\-\-root\-password\fR locked:file:НАЗВА_ФАЙЛА" 4
.IX Item "--root-password locked:file:НАЗВА_ФАЙЛА"
.PD 0
.IP "\fB\-\-root\-password\fR locked:random" 4
.IX Item "--root-password locked:random"
.PD
-Обліковий запис root заблоковано, але для нього визначено пароль. Якщо
-обліковий запис буде вперше розблоковано (за допомогою \f(CW\*(C`passwd \-u\*(C'\fR), для
-входу до нього буде використано вказаний пароль.
+Обліковий запис root заблоковано, але для нього визначено пароль. Якщо обліковий запис буде вперше розблоковано (за допомогою \f(CW\*(C`passwd \-u\*(C'\fR), для входу до нього буде використано вказаний пароль.
.IP "\fB\-\-root\-password\fR locked" 4
.IX Item "--root-password locked"
.PD 0
\fIСтворення облікових записів користувачів\fR
.IX Subsection "Створення облікових записів користувачів"
.PP
-Для створення облікових записів користувачів скористайтеся командою
-\&\fBuseradd\fR\|(8) з параметром \-\-firstboot\-command, ось так:
+Для створення облікових записів користувачів скористайтеся командою \fBuseradd\fR\|(8) з параметром \-\-firstboot\-command, ось так:
.PP
.Vb 2
\& virt\-builder \-\-firstboot\-command \e
\& \*(Aquseradd \-m \-p "" rjones ; chage \-d 0 rjones\*(Aq
.Ve
.PP
-Вказана вище команда створить обліковий запис \f(CW\*(C`rjones\*(C'\fR без пароля і
-примусить користувача встановити пароль під час першого входу до
-системи. Існують і інші способи керування паролями, див. \fBuseradd\fR\|(8), щоб
-дізнатися більше.
+Вказана вище команда створить обліковий запис \f(CW\*(C`rjones\*(C'\fR без пароля і примусить користувача встановити пароль під час першого входу до системи. Існують і інші способи керування паролями, див. \fBuseradd\fR\|(8), щоб дізнатися більше.
.SS "РОЗКЛАДКА КЛАВІАТУРИ"
.IX Subsection "РОЗКЛАДКА КЛАВІАТУРИ"
-Оскільки існує багато різних способів встановити розкладку клавіатури у
-дистрибутивах Linux, у virt-builder усе ще немає простого параметра
-командного рядка для виконання цієї дії. У цьому розділі наведено настанови
-щодо встановлення розкладки для деяких типових дистрибутивів Linux.
+Оскільки існує багато різних способів встановити розкладку клавіатури у дистрибутивах Linux, у virt-builder усе ще немає простого параметра командного рядка для виконання цієї дії. У цьому розділі наведено настанови щодо встановлення розкладки для деяких типових дистрибутивів Linux.
.PP
\fIВизначення розкладки клавіатури за допомогою systemd\fR
.IX Subsection "Визначення розкладки клавіатури за допомогою systemd"
.PP
-У дистрибутивах, де використовується \f(CW\*(C`localectl\*(C'\fR зі складу systemd,
-скористайтеся такою командою:
+У дистрибутивах, де використовується \f(CW\*(C`localectl\*(C'\fR зі складу systemd, скористайтеся такою командою:
.PP
.Vb 2
\& virt\-builder fedora\-27 \e
\& \-\-firstboot\-command \*(Aqlocalectl set\-keymap uk\*(Aq
.Ve
.PP
-Докладніший опис можна знайти за посиланнями \fBlocalectl\fR\|(1) та
-https://www.happyassassin.net/2013/11/23/keyboard\-layouts\-in\-fedora\-20\-and\-previously/.
+Докладніший опис можна знайти за посиланнями \fBlocalectl\fR\|(1) та https://www.happyassassin.net/2013/11/23/keyboard\-layouts\-in\-fedora\-20\-and\-previously/.
.PP
\fIВизначення розкладки клавіатури за допомогою \fI/etc/sysconfig/keyboard\fI\fR
.IX Subsection "Визначення розкладки клавіатури за допомогою /etc/sysconfig/keyboard"
.PP
-Для \s-1RHEL\s0 ≤ 6, Fedora ≤ 18 та подібних систем можна вивантажити із
-змінити файл налаштувань клавіатури за допомогою параметрів \fI\-\-upload\fR,
-\&\fI\-\-write\fR або \fI\-\-edit\fR. Приклад:
+Для \s-1RHEL\s0 ≤ 6, Fedora ≤ 18 та подібних систем можна вивантажити із змінити файл налаштувань клавіатури за допомогою параметрів \fI\-\-upload\fR, \fI\-\-write\fR або \fI\-\-edit\fR. Приклад:
.PP
.Vb 2
\& virt\-builder centos\-6 \e
\& \-\-edit \*(Aq/etc/sysconfig/keyboard: s/^KEYTABLE=.*/KEYTABLE="uk"/\*(Aq
.Ve
.PP
-Документацію щодо формату даних цього файла можна знайти на багатьох
-сторінках інтернету.
+Документацію щодо формату даних цього файла можна знайти на багатьох сторінках інтернету.
.PP
\fIВизначення розкладки клавіатури у дистрибутивах на основі Debian\fR
.IX Subsection "Визначення розкладки клавіатури у дистрибутивах на основі Debian"
.PP
-У заснованих на Debian дистрибутивах мети можна досягти за допомогою файла
-\&\fI/etc/default/keyboard\fR. Вивантажити або внести зміни до цього файла можна
-за допомогою параметрів \fI\-\-upload\fR, \fI\-\-write\fR та \fI\-\-edit\fR. Приклад:
+У заснованих на Debian дистрибутивах мети можна досягти за допомогою файла \fI/etc/default/keyboard\fR. Вивантажити або внести зміни до цього файла можна за допомогою параметрів \fI\-\-upload\fR, \fI\-\-write\fR та \fI\-\-edit\fR. Приклад:
.PP
.Vb 2
\& virt\-builder debian\-8 \e
Див. https://wiki.debian.org/Keyboard.
.SS "МОВА"
.IX Subsection "МОВА"
-У більшості дистрибутивів Linux передбачено можливість зміни локалі, отже ви
-можете бачити повідомлення гостьової системи нестандартною мовою, наприклад
-українською.
+У більшості дистрибутивів Linux передбачено можливість зміни локалі, отже ви можете бачити повідомлення гостьової системи нестандартною мовою, наприклад українською.
.PP
-Втім, єдиного параметра, який контролює локаль, немає, оскільки для
-реалізації підтримки мови може знадобитися встановлення додаткових пакунків,
-зокрема шрифтів для консолі і графічної оболонки, способів введення символів
-запису мови з клавіатури. Назви потрібних для цього пакунків та їхні
-налаштування залежать від дистрибутиву, отже, virt-builder просто не може
-про них знати.
+Втім, єдиного параметра, який контролює локаль, немає, оскільки для реалізації підтримки мови може знадобитися встановлення додаткових пакунків, зокрема шрифтів для консолі і графічної оболонки, способів введення символів запису мови з клавіатури. Назви потрібних для цього пакунків та їхні налаштування залежать від дистрибутиву, отже, virt-builder просто не може про них знати.
.PP
У цьому розділі наведено приклади для типових дистрибутивів Linux.
.PP
\fIВстановлення японської мови для Debian 8 (Jessie)\fR
.IX Subsection "Встановлення японської мови для Debian 8 (Jessie)"
.PP
-Зауважте, що, хоча вказана команда вмикає японську і у текстовій консолі,
-навряд чи у консолі ви побачите належним чином показані ієрогліфи. Втім,
-японські ієрогліфи має бути показано у графічних програмах і терміналах.
+Зауважте, що, хоча вказана команда вмикає японську і у текстовій консолі, навряд чи у консолі ви побачите належним чином показані ієрогліфи. Втім, японські ієрогліфи має бути показано у графічних програмах і терміналах.
.PP
.Vb 6
\& pkgs=locales,xfce4,\e
.Ve
.SS "ФАЙЛ ЖУРНАЛУ"
.IX Subsection "ФАЙЛ ЖУРНАЛУ"
-Скрипти та засоби встановлення пакунків, які працюватимуть під час збирання
-(\fI\-\-run\fR, \fI\-\-run\-command\fR, \fI\-\-install\fR, \fI\-\-update\fR, але \fIне\fR
-firstboot), записуватимуть повідомлення до одного з таких файлів:
+Скрипти та засоби встановлення пакунків, які працюватимуть під час збирання (\fI\-\-run\fR, \fI\-\-run\-command\fR, \fI\-\-install\fR, \fI\-\-update\fR, але \fIне\fR firstboot), записуватимуть повідомлення до одного з таких файлів:
.IP "\fI/tmp/builder.log\fR" 4
.IX Item "/tmp/builder.log"
У Linux, \s-1BSD\s0 та інших гостьових системах, відмінних від Windows.
.IX Item "/builder.log"
Якщо немає \fI/tmp\fR або \fIC:\eTemp\fR.
.PP
-Якщо ви не хочете, щоб до остаточного образу було записано файл журналу,
-скористайтеся параметром рядка команди \fI\-\-no\-logfile\fR.
+Якщо ви не хочете, щоб до остаточного образу було записано файл журналу, скористайтеся параметром рядка команди \fI\-\-no\-logfile\fR.
.SS "КЛЮЧІ \s-1SSH\s0"
.IX Subsection "КЛЮЧІ SSH"
-Параметр \fI\-\-ssh\-inject\fR використовується для вставляння ключів ssh для
-користувачів у гостьовій системі, щоб вони могли входити до системи без
-зазначення пароля.
+Параметр \fI\-\-ssh\-inject\fR використовується для вставляння ключів ssh для користувачів у гостьовій системі, щоб вони могли входити до системи без зазначення пароля.
.PP
-Частина \f(CW\*(C`ВАРІАНТ\*(C'\fR параметра є необов'язковою; у нашому випадку
-\&\fI\-\-ssh\-inject\fR \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR означає, що ми шукаємо \fI~/.ssh\fR у каталозі
-\&\fIпоточного\fR користувача для визначення типового файла відкритого
-ідентифікатора. Саме знайдений ключ і буде вивантажено до гостьової
-системи. «Типовий відкритий ідентифікатор» є файлом \fIdefault_ID_file\fR, який
-описано у підручнику з \fBssh\-copy\-id\fR\|(1).
+Частина \f(CW\*(C`ВАРІАНТ\*(C'\fR параметра є необов'язковою; у нашому випадку \fI\-\-ssh\-inject\fR \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR означає, що ми шукаємо \fI~/.ssh\fR у каталозі \fIпоточного\fR користувача для визначення типового файла відкритого ідентифікатора. Саме знайдений ключ і буде вивантажено до гостьової системи. «Типовий відкритий ідентифікатор» є файлом \fIdefault_ID_file\fR, який описано у підручнику з \fBssh\-copy\-id\fR\|(1).
.PP
Якщо вказано, \f(CW\*(C`ВАРІАНТ\*(C'\fR можна зазначити у одному з таких форматів:
.IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА" 4
Прочитати ключ ssh з файла \fIНАЗВА ФАЙЛА\fR. Файлом зазвичай є файл \fI.pub\fR.
.IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ:string:РЯДОК_КЛЮЧА" 4
.IX Item "--ssh-inject КОРИСТУВАЧ:string:РЯДОК_КЛЮЧА"
-Використати вказаний \f(CW\*(C`РЯДОК_КЛЮЧА\*(C'\fR. Зазвичай, \f(CW\*(C`РЯДОК_КЛЮЧА\*(C'\fR — рядок
-відкритого ключа у форматі \fIssh-rsa \s-1AAAA....\s0 user@localhost\fR.
+Використати вказаний \f(CW\*(C`РЯДОК_КЛЮЧА\*(C'\fR. Зазвичай, \f(CW\*(C`РЯДОК_КЛЮЧА\*(C'\fR — рядок відкритого ключа у форматі \fIssh-rsa \s-1AAAA....\s0 user@localhost\fR.
.PP
-Який би з варіантів не було вибрано, буде створено каталог \fI~USER/.ssh\fR і
-файл \fI~USER/.ssh/authorized_keys\fR, якщо вони досі не існували.
+Який би з варіантів не було вибрано, буде створено каталог \fI~USER/.ssh\fR і файл \fI~USER/.ssh/authorized_keys\fR, якщо вони досі не існували.
.SS "СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ"
.IX Subsection "СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ"
-За допомогою параметрів \fI\-\-firstboot\fR та \fI\-\-firstboot\-command\fR ви можете
-визначити команди, які буде виконано під час першого завантаження гостьової
-системи. Для цього у гостьовій системі встановлюється скрипт ініціалізації,
-який виконує завдання із запуску усіх доданих скриптів і виконання усіх
-доданих команд.
+За допомогою параметрів \fI\-\-firstboot\fR та \fI\-\-firstboot\-command\fR ви можете визначити команди, які буде виконано під час першого завантаження гостьової системи. Для цього у гостьовій системі встановлюється скрипт ініціалізації, який виконує завдання із запуску усіх доданих скриптів і виконання усіх доданих команд.
.PP
Підтримувані операційні системи:
.IP "Linux" 4
.IX Item "Linux"
-Передбачено підтримку таких систем ініціалізації: systemd, System-V init
-(також відома як sysvinit) та Upstart (з використанням скриптів System-V).
+Передбачено підтримку таких систем ініціалізації: systemd, System-V init (також відома як sysvinit) та Upstart (з використанням скриптів System-V).
.Sp
-Зауважте, що, зазвичай, скрипти ініціалізації виконуються від імені
-адміністратора (root), але у набагато обмеженішому середовищі ніж те, яке
-доступне зі звичайної оболонки. Наприклад, значення змінної середовища
-\&\f(CW$HOME\fR може бути не встановленим або порожнім.
+Зауважте, що, зазвичай, скрипти ініціалізації виконуються від імені адміністратора (root), але у набагато обмеженішому середовищі ніж те, яке доступне зі звичайної оболонки. Наприклад, значення змінної середовища \f(CW$HOME\fR може бути не встановленим або порожнім.
.Sp
-Дані, виведені скриптами першого запуску, у гостьовій системі
-зберігатимуться у \fI~root/virt\-sysprep\-firstboot.log\fR.
+Дані, виведені скриптами першого запуску, у гостьовій системі зберігатимуться у \fI~root/virt\-sysprep\-firstboot.log\fR.
.IP "Windows" 4
.IX Item "Windows"
-Для запуску скриптів першого завантаження встановлюється \fIrhsrvany.exe\fR,
-початковий код якого можна знайти у https://github.com/rwmjones/rhsrvany,
-або \fIpvvxsvc.exe\fR, який є частиною \s-1SUSE VMDP.\s0 Наявність цих файлів є
-обов'язковою. Якщо файлів не буде знайдено, скрипти першого завантаження
-виконати не вдасться.
-.Sp
-\&\fIrhsrvany.exe\fR або \fIpvvxsvc.exe\fR буде просто скопійовано з місця, на яке
-вказує змінна середовища \f(CW\*(C`VIRT_TOOLS_DATA_DIR\*(C'\fR; якщо значення змінної
-середовища не встановлено, буде використано типове місце, визначене під час
-компіляції (щось схоже на \fI/usr/share/virt\-tools\fR).
-.Sp
-Дані, виведені скриптами першого завантаження, можна знайти у гостьовій
-системі за адресою \fIC:\eProgram Files\eGuestfs\eFirstboot\elog.txt\fR.
+Для запуску скриптів першого завантаження встановлюється \fIrhsrvany.exe\fR, початковий код якого можна знайти у https://github.com/rwmjones/rhsrvany, або \fIpvvxsvc.exe\fR, який є частиною \s-1SUSE VMDP.\s0 Наявність цих файлів є обов'язковою. Якщо файлів не буде знайдено, скрипти першого завантаження виконати не вдасться.
+.Sp
+\&\fIrhsrvany.exe\fR або \fIpvvxsvc.exe\fR буде просто скопійовано з місця, на яке вказує змінна середовища \f(CW\*(C`VIRT_TOOLS_DATA_DIR\*(C'\fR; якщо значення змінної середовища не встановлено, буде використано типове місце, визначене під час компіляції (щось схоже на \fI/usr/share/virt\-tools\fR).
+.Sp
+Дані, виведені скриптами першого завантаження, можна знайти у гостьовій системі за адресою \fIC:\eProgram Files\eGuestfs\eFirstboot\elog.txt\fR.
.SS "SUBSCRIPTION-MANAGER"
.IX Subsection "SUBSCRIPTION-MANAGER"
-Передбачено можливість автоматизації реєстрації та долучення до системи
-передплат за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR. Потреба у подібному
-налаштовуванні типово виникає у системах Red Hat Enterprise
-Linux. Передбачено декілька параметрів, які спрощують процедуру, усувають
-потребу у введенні команд вручну та не роблять загальнодоступними паролі,
-вказані у рядку команди.
-.PP
-\&\fI\-\-sm\-register\fR запускає процедуру реєстрації і потребує зазначення
-\&\fI\-\-sm\-credentials\fR. Слід використовувати для параметра \f(CW\*(C`ВАРІАНТ\*(C'\fR
-\&\fI\-\-sm\-credentials\fR один з таких форматів:
+Передбачено можливість автоматизації реєстрації та долучення до системи передплат за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR. Потреба у подібному налаштовуванні типово виникає у системах Red Hat Enterprise Linux. Передбачено декілька параметрів, які спрощують процедуру, усувають потребу у введенні команд вручну та не роблять загальнодоступними паролі, вказані у рядку команди.
+.PP
+\&\fI\-\-sm\-register\fR запускає процедуру реєстрації і потребує зазначення \fI\-\-sm\-credentials\fR. Слід використовувати для параметра \f(CW\*(C`ВАРІАНТ\*(C'\fR \fI\-\-sm\-credentials\fR один з таких форматів:
.IP "\fB\-\-sm\-credentials\fR КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА" 4
.IX Item "--sm-credentials КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА"
-Прочитати пароль для вказаного користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR з файла
-\&\fIНАЗВА_ФАЙЛА\fR.
+Прочитати пароль для вказаного користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR з файла \fIНАЗВА_ФАЙЛА\fR.
.IP "\fB\-\-sm\-credentials\fR КОРИСТУВАЧ:password:ПАРОЛЬ" 4
.IX Item "--sm-credentials КОРИСТУВАЧ:password:ПАРОЛЬ"
Використати рядок \f(CW\*(C`ПАРОЛЬ\*(C'\fR для вказаного користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR.
.PP
-\&\fI\-\-sm\-attach\fR долучає систему до передплачених послуг; формат варіантів
-команди може бути одним з таких:
+\&\fI\-\-sm\-attach\fR долучає систему до передплачених послуг; формат варіантів команди може бути одним з таких:
.IP "\fB\-\-sm\-attach\fR auto" 4
.IX Item "--sm-attach auto"
-\&\f(CW\*(C`subscription\-manager\*(C'\fR долучається до найвідповідніших передплат для
-системи.
+\&\f(CW\*(C`subscription\-manager\*(C'\fR долучається до найвідповідніших передплат для системи.
.IP "\fB\-\-sm\-attach\fR file:НАЗВА_ФАЙЛА" 4
.IX Item "--sm-attach file:НАЗВА_ФАЙЛА"
Прочитати ідентифікатор буфера з файла \fIНАЗВА_ФАЙЛА\fR.
.IX Item "--sm-attach pool:БУФЕР"
Використовувати рядок \f(CW\*(C`БУФЕР\*(C'\fR як ідентифікатор буфера.
.PP
-\&\fI\-\-sm\-remove\fR вилучає усі передплати з гостьової системи, а
-\&\fI\-\-sm\-unregister\fR повністю знімає систему з реєстрації.
+\&\fI\-\-sm\-remove\fR вилучає усі передплати з гостьової системи, а \fI\-\-sm\-unregister\fR повністю знімає систему з реєстрації.
.SS "ПРОЦЕДУРА ВСТАНОВЛЕННЯ"
.IX Subsection "ПРОЦЕДУРА ВСТАНОВЛЕННЯ"
Після виклику virt-builder встановлення виконується таким чином:
.IP "\(bu" 4
Отримується образ шаблону.
.Sp
-Якщо образ шаблону вже є у кеші, використовується кешована
-версія. (Див. \*(L"КЕШУВАННЯ\*(R").
+Якщо образ шаблону вже є у кеші, використовується кешована версія. (Див. \*(L"КЕШУВАННЯ\*(R").
.IP "\(bu" 4
Перевіряється підпис шаблону.
.IP "\(bu" 4
Шаблон розпаковується до файла tmp.
.IP "\(bu" 4
-Розмір образ шаблону змінюється так, щоб від дорівнював розміру системи
-призначення, за допомогою \fBvirt\-resize\fR\|(1).
+Розмір образ шаблону змінюється так, щоб від дорівнював розміру системи призначення, за допомогою \fBvirt\-resize\fR\|(1).
.IP "\(bu" 4
Долучаються додаткові диски (\fI\-\-attach\fR).
.IP "\(bu" 4
Створюється нова база псевдовипадкових чисел для гостьової системи.
.IP "\(bu" 4
-Виконується налаштовування гостьової системи у порядку, який задається
-рядком команди.
+Виконується налаштовування гостьової системи у порядку, який задається рядком команди.
.IP "\(bu" 4
Виконується зміна міток SELinux виконано (\fI\-\-selinux\-relabel\fR).
.SS "ІМПОРТУВАННЯ ОБРАЗУ ДИСКА"
\fIІмпортування до libvirt\fR
.IX Subsection "Імпортування до libvirt"
.PP
-Імпортування образу диска до libvirt за допомогою параметра
-\&\fBvirt\-install\fR\|(1) \fI\-\-import\fR.
+Імпортування образу диска до libvirt за допомогою параметра \fBvirt\-install\fR\|(1) \fI\-\-import\fR.
.PP
.Vb 3
\& virt\-install \-\-import \e
.PP
Нотатки:
.IP "1." 4
-Вам \fIслід\fR вказати правильний формат. Форматом є \f(CW\*(C`raw\*(C'\fR, якщо вами не було
-використано параметр virt-builder \fI\-\-format\fR.
+Вам \fIслід\fR вказати правильний формат. Форматом є \f(CW\*(C`raw\*(C'\fR, якщо вами не було використано параметр virt-builder \fI\-\-format\fR.
.IP "2." 4
-Наполегливо рекомендуємо скористатися \fI\-\-os\-variant\fR, оскільки він надає
-змогу підібрати оптимальний набір пристроїв, які слід увімкнути у системі,
-щоб гостьова система працювала найефективніше. Щоб отримати список усіх
-варіантів, скористайтеся такою командою:
+Наполегливо рекомендуємо скористатися \fI\-\-os\-variant\fR, оскільки він надає змогу підібрати оптимальний набір пристроїв, які слід увімкнути у системі, щоб гостьова система працювала найефективніше. Щоб отримати список усіх варіантів, скористайтеся такою командою:
.Sp
.Vb 1
\& osinfo\-query ОС
.Sp
Вказана вище програма є частиною пакунка libosinfo.
.IP "3." 4
-Запускати virt-install можна від імені адміністратора (root) або від імені
-простого користувача. Між цими способами є незначні відмінності, оскільки
-libvirt керує різними наборами віртуальних машин для кожного
-користувача. Зокрема, virt-manager показує віртуальні машини, власником яких
-є root, а «Коробки» з \s-1GNOME\s0 показують лише віртуальні машини поточного
-користувача. Інші ж програми можуть також мати свої особливості показу.
+Запускати virt-install можна від імені адміністратора (root) або від імені простого користувача. Між цими способами є незначні відмінності, оскільки libvirt керує різними наборами віртуальних машин для кожного користувача. Зокрема, virt-manager показує віртуальні машини, власником яких є root, а «Коробки» з \s-1GNOME\s0 показують лише віртуальні машини поточного користувача. Інші ж програми можуть також мати свої особливості показу.
.PP
\fIІмпортування до OpenStack\fR
.IX Subsection "Імпортування до OpenStack"
.PP
-Імпортувати образ до Glance (сховища образів OpenStack) можна такими
-командами:
+Імпортувати образ до Glance (сховища образів OpenStack) можна такими командами:
.PP
.Vb 3
\& glance image\-create \-\-name fedora\-27\-image \-\-file fedora\-27.img \e
\& \-\-is\-public True
.Ve
.PP
-Параметр \fI\-\-file\fR визначає створений за допомогою virt-builder образ
-диска. Його значення має узгоджуватися із значення параметра \fI\-\-output\fR
-virt-builder. Значення параметра \fI\-\-disk\-format\fR має узгоджуватися зі
-значенням параметра \fI\-\-format\fR virt-builder (або бути рівним \f(CW\*(C`raw\*(C'\fR, якщо
-ви не вказували цього параметра). Значенням параметра \fI\-\-container\-format\fR
-завжди має бути \f(CW\*(C`bare\*(C'\fR, оскільки virt-builder ніколи не вкладає образ до
-контейнерів.
+Параметр \fI\-\-file\fR визначає створений за допомогою virt-builder образ диска. Його значення має узгоджуватися із значення параметра \fI\-\-output\fR virt-builder. Значення параметра \fI\-\-disk\-format\fR має узгоджуватися зі значенням параметра \fI\-\-format\fR virt-builder (або бути рівним \f(CW\*(C`raw\*(C'\fR, якщо ви не вказували цього параметра). Значенням параметра \fI\-\-container\-format\fR завжди має бути \f(CW\*(C`bare\*(C'\fR, оскільки virt-builder ніколи не вкладає образ до контейнерів.
.PP
-Ви можете скористатися командою \f(CW\*(C`glance image\-show \f(CIfedora\-27\-image\f(CW\*(C'\fR,
-щоб переглянути властивості образу.
+Ви можете скористатися командою \f(CW\*(C`glance image\-show \f(CIfedora\-27\-image\f(CW\*(C'\fR, щоб переглянути властивості образу.
.PP
-Для завантаження екземпляра вашого образу на обчислювальному вузлі Nova
-віддайте таку команду:
+Для завантаження екземпляра вашого образу на обчислювальному вузлі Nova віддайте таку команду:
.PP
.Vb 2
\& nova boot fedora\-27\-server \-\-image fedora\-27\-image \e
\& \-\-flavor m1.medium
.Ve
.PP
-Скористайтеся командою \f(CW\*(C`nova flavor\-list\*(C'\fR, щоб переглянути список
-можливих варіантів машин. Скористайтеся командою \f(CW\*(C`nova list\*(C'\fR, щоб
-переглянути список запущених екземплярів.
+Скористайтеся командою \f(CW\*(C`nova flavor\-list\*(C'\fR, щоб переглянути список можливих варіантів машин. Скористайтеся командою \f(CW\*(C`nova list\*(C'\fR, щоб переглянути список запущених екземплярів.
.PP
\fIБезпосереднє завантаження за допомогою qemu або \s-1KVM\s0\fR
.IX Subsection "Безпосереднє завантаження за допомогою qemu або KVM"
.PP
-Командний рядок qemu не є ні надто стабільним, ні простим у користуванні,
-тому, якщо це можливо, слід користуватися libvirt. Втім, для завантаження
-віртуальної машини можна скористатися чимось подібним до вказаного нижче:
+Командний рядок qemu не є ні надто стабільним, ні простим у користуванні, тому, якщо це можливо, слід користуватися libvirt. Втім, для завантаження віртуальної машини можна скористатися чимось подібним до вказаного нижче:
.PP
.Vb 5
\& qemu\-system\-x86_64 \e
\& \-drive file=disk.img,format=raw,if=virtio
.Ve
.PP
-Як і з libvirt, дуже важливо вибрати правильний формат. Цим форматом буде
-\&\f(CW\*(C`raw\*(C'\fR, якщо раніше не було використано параметр \fI\-\-format\fR.
+Як і з libvirt, дуже важливо вибрати правильний формат. Цим форматом буде \f(CW\*(C`raw\*(C'\fR, якщо раніше не було використано параметр \fI\-\-format\fR.
.SS "КЕРУВАННЯ НАЛАШТУВАННЯМИ"
.IX Subsection "КЕРУВАННЯ НАЛАШТУВАННЯМИ"
\fIPuppet\fR
.IX Subsection "Puppet"
.PP
-Щоб увімкнути агент Puppet у гостьовій системі, встановіть пакунок, вкажіть
-налаштування на вашому Puppetmaster і забезпечте запуск агента під час
-завантаження.
+Щоб увімкнути агент Puppet у гостьовій системі, встановіть пакунок, вкажіть налаштування на вашому Puppetmaster і забезпечте запуск агента під час завантаження.
.PP
Типовою командою virt-builder буде:
.PP
\& \-\-selinux\-relabel
.Ve
.PP
-Точний перелік настанов залежить від дистрибутива Linux. Докладніше про це
-тут: https://docs.puppet.com/puppet/latest/install_pre.html
+Точний перелік настанов залежить від дистрибутива Linux. Докладніше про це тут: https://docs.puppet.com/puppet/latest/install_pre.html
.SS "ДІАГНОСТИКА ЗБИРАННЯ"
.IX Subsection "ДІАГНОСТИКА ЗБИРАННЯ"
-Якщо сам virt-builder не може виконати роботу, слід увімкнути діагностику
-(\fI\-v\fR) і повідомити про ваду розробників (див. розділ \*(L"ВАДИ\*(R" нижче).
+Якщо сам virt-builder не може виконати роботу, слід увімкнути діагностику (\fI\-v\fR) і повідомити про ваду розробників (див. розділ \*(L"ВАДИ\*(R" нижче).
.PP
-Якщо причиною неможливості виконання завдання virt-builder є який скрипт або
-пакунок, який програма не може встановити, спробуйте скористатися параметром
-\&\fI\-\-no\-delete\-on\-failure\fR, щоб зберегти файл результатів, і продовжіть
-вивчення цього розділу підручника.
+Якщо причиною неможливості виконання завдання virt-builder є який скрипт або пакунок, який програма не може встановити, спробуйте скористатися параметром \fI\-\-no\-delete\-on\-failure\fR, щоб зберегти файл результатів, і продовжіть вивчення цього розділу підручника.
.PP
-Якщо virt-builder успішно завершує роботу, але образ не працює, ось чим слід
-скористатися:
+Якщо virt-builder успішно завершує роботу, але образ не працює, ось чим слід скористатися:
.IP "Використання virt-rescue" 4
.IX Item "Використання virt-rescue"
Запустити \fBvirt\-rescue\fR\|(1) над образом диска:
\& virt\-rescue \-a disk.img
.Ve
.Sp
-Ви потрапите до оболонки порятунку. Ви зможете змонтувати файлові системи з
-образу диска до \fI/sysroot\fR і вивчити їх за допомогою звичних команд
-Linux. Ви також можете скористатися chroot щодо гостьової системи і
-перевстановити у ній завантажувач. На сторінці підручника з virt-rescue
-наведено набагато більше інформації та прикладів.
+Ви потрапите до оболонки порятунку. Ви зможете змонтувати файлові системи з образу диска до \fI/sysroot\fR і вивчити їх за допомогою звичних команд Linux. Ви також можете скористатися chroot щодо гостьової системи і перевстановити у ній завантажувач. На сторінці підручника з virt-rescue наведено набагато більше інформації та прикладів.
.IP "Використання guestfish" 4
.IX Item "Використання guestfish"
Запустити \fBguestfish\fR\|(1) над образом диска:
\& guestfish \-a disk.img \-i
.Ve
.Sp
-Скористайтеся командами guestfish, зокрема \f(CW\*(C`ll /каталог\*(C'\fR і \f(CW\*(C`cat /файл\*(C'\fR,
-для перевірки каталогів та файлів.
+Скористайтеся командами guestfish, зокрема \f(CW\*(C`ll /каталог\*(C'\fR і \f(CW\*(C`cat /файл\*(C'\fR, для перевірки каталогів та файлів.
.IP "Використання guestmount" 4
.IX Item "Використання guestmount"
-Безпечно змонтувати образ диска у основній системі за допомогою \s-1FUSE\s0 і
-\&\fBguestmount\fR\|(1):
+Безпечно змонтувати образ диска у основній системі за допомогою \s-1FUSE\s0 і \fBguestmount\fR\|(1):
.Sp
.Vb 3
\& mkdir /tmp/mp
.Ve
.IP "Додати послідовну консоль" 4
.IX Item "Додати послідовну консоль"
-Якщо гостьова система повисає під час завантаження, може допомогти додавання
-послідовної консолі у гостьову систему і спрямовування повідомлень ядра до
-послідовної консолі. Додавання послідовної консолі потребує вивчення
-документації до вашого гіпервізору. Щоб спрямувати повідомлення ядра до
-послідовної консолі, додайте таку частину до командного рядка ядра:
+Якщо гостьова система повисає під час завантаження, може допомогти додавання послідовної консолі у гостьову систему і спрямовування повідомлень ядра до послідовної консолі. Додавання послідовної консолі потребує вивчення документації до вашого гіпервізору. Щоб спрямувати повідомлення ядра до послідовної консолі, додайте таку частину до командного рядка ядра:
.Sp
.Vb 1
\& console=tty0 console=ttyS0,115200
.Ve
.SS "ДЖЕРЕЛА ШАБЛОНІВ"
.IX Subsection "ДЖЕРЕЛА ШАБЛОНІВ"
-virt-builder читає доступні джерела із файлів налаштування, файлів із
-суфіксом назви \fI.conf\fR, які зберігаються у одному з таких місць:
+virt-builder читає доступні джерела із файлів налаштування, файлів із суфіксом назви \fI.conf\fR, які зберігаються у одному з таких місць:
.IP "\(bu" 4
-\&\f(CW$XDG_CONFIG_HOME\fR/virt\-builder/reposd/ (\f(CW$XDG_CONFIG_HOME\fR дорівнює
-\&\fI\f(CI$HOME\fI/.config\fR, якщо не встановлено).
+\&\f(CW$XDG_CONFIG_HOME\fR/virt\-builder/reposd/ (\f(CW$XDG_CONFIG_HOME\fR дорівнює \fI\f(CI$HOME\fI/.config\fR, якщо не встановлено).
.IP "\(bu" 4
-\&\f(CW$VIRT_BUILDER_DIRS\fR/virt\-builder/repos.d/ (where \f(CW$VIRT_BUILDER_DIRS\fR means
-any of the directories in that environment variable, or just \fI/etc\fR if not
-set).
+\&\f(CW$VIRT_BUILDER_DIRS\fR/virt\-builder/repos.d/ (where \f(CW$VIRT_BUILDER_DIRS\fR means any of the directories in that environment variable, or just \fI/etc\fR if not set).
.PP
-Кожен з файлів \fI.conf\fR у вказаних каталогах зберігає дані у простому
-текстовому форматі, ось так:
+Кожен з файлів \fI.conf\fR у вказаних каталогах зберігає дані у простому текстовому форматі, ось так:
.PP
.Vb 3
\& [libguestfs.org]
\& gpgkey=file:///etc/xdg/virt\-builder/repos.d/libguestfs.gpg
.Ve
.PP
-Частина у квадратних дужках є ідентифікатором сховища, який використовується
-як унікальний ідентифікатор.
+Частина у квадратних дужках є ідентифікатором сховища, який використовується як унікальний ідентифікатор.
.PP
Можуть з’явитися такі поля:
.ie n .IP """uri=АДРЕСА""" 4
.ie n .IP """gpgkey=АДРЕСА""" 4
.el .IP "\f(CWgpgkey=АДРЕСА\fR" 4
.IX Item "gpgkey=АДРЕСА"
-Це необов'язкове поле відповідає адресі (хоча прийнятними є лише адреси
-\&\fIfile://\fR) ключа, який використано для підписування файла покажчика. Якщо
-поля немає, файл покажчика, на який посилається \fIuri=..\fR, не підписано.
+Це необов'язкове поле відповідає адресі (хоча прийнятними є лише адреси \fIfile://\fR) ключа, який використано для підписування файла покажчика. Якщо поля немає, файл покажчика, на який посилається \fIuri=..\fR, не підписано.
.ie n .IP """proxy=РЕЖИМ""" 4
.el .IP "\f(CWproxy=РЕЖИМ\fR" 4
.IX Item "proxy=РЕЖИМ"
-Це необов'язкове поле вказує на режим проксі, яким слід скористатися для
-отримання файла покажчика цього сховища. Можливі значення:
+Це необов'язкове поле вказує на режим проксі, яким слід скористатися для отримання файла покажчика цього сховища. Можливі значення:
.RS 4
.IP "\fBno\fR, \fBoff\fR" 4
.IX Item "no, off"
Використаний проксі\-сервер є системним.
.IP "\fIусе інше\fR" 4
.IX Item "усе інше"
-Задає справжні налаштування проксі, якими слід скористатися, незважаючи на
-налаштування системи.
+Задає справжні налаштування проксі, якими слід скористатися, незважаючи на налаштування системи.
.RE
.RS 4
.Sp
-Якщо значення не вказано, буде використано параметри проксі\-сервера системи
-(тобто все буде так, наче вказано \fBsystem\fR).
+Якщо значення не вказано, буде використано параметри проксі\-сервера системи (тобто все буде так, наче вказано \fBsystem\fR).
.RE
.ie n .IP """format=ФОРМАТ""" 4
.el .IP "\f(CWformat=ФОРМАТ\fR" 4
.RS 4
.IP "\fBnative\fR" 4
.IX Item "native"
-Природний формат сховища \f(CW\*(C`virt\-builder\*(C'\fR. Див. також розділ \*(L"Створення і
-підписування файла покажчика\*(R" нижче.
+Природний формат сховища \f(CW\*(C`virt\-builder\*(C'\fR. Див. також розділ \*(L"Створення і підписування файла покажчика\*(R" нижче.
.IP "\fBsimplestreams\fR" 4
.IX Item "simplestreams"
-Адреса, яка визначає кореневий каталог ієрархії метаданих Simple Streams
-версії 1.0.
+Адреса, яка визначає кореневий каталог ієрархії метаданих Simple Streams версії 1.0.
.Sp
-Докладніший опис Simple Streams наведено тут:
-https://launchpad.net/simplestreams.
+Докладніший опис Simple Streams наведено тут: https://launchpad.net/simplestreams.
.RE
.RS 4
.Sp
Якщо не вказано, типовим значенням буде \f(CW\*(C`native\*(C'\fR.
.RE
.PP
-Якщо ви часто користуватиметеся virt-builder, варто створити власне сховище
-шаблонів.
+Якщо ви часто користуватиметеся virt-builder, варто створити власне сховище шаблонів.
.PP
\fIСховище libguestfs.org\fR
.IX Subsection "Сховище libguestfs.org"
.PP
-Від початку, virt-builder отримує файл
-http://libguestfs.org/download/builder/index.asc, який є покажчиком усіх
-доступних шаблонів, і деяку інформацію щодо кожного з них, яку додано до
-цифрового підпису. За допомогою команди \f(CW\*(C`virt\-builder \-\-list\*(C'\fR можна
-ознайомитися із усіма даними щодо цього файла покажчика.
+Від початку, virt-builder отримує файл http://libguestfs.org/download/builder/index.asc, який є покажчиком усіх доступних шаблонів, і деяку інформацію щодо кожного з них, яку додано до цифрового підпису. За допомогою команди \f(CW\*(C`virt\-builder \-\-list\*(C'\fR можна ознайомитися із усіма даними щодо цього файла покажчика.
.PP
-Шаблони, які зберігаються на libguestfs.org, було створено за допомогою
-скриптів командної оболонки, файлів kickstart та файлів, які можна знайти у
-ієрархії коду libguestfs, у каталозі \f(CW\*(C`builder/templates\*(C'\fR.
+Шаблони, які зберігаються на libguestfs.org, було створено за допомогою скриптів командної оболонки, файлів kickstart та файлів, які можна знайти у ієрархії коду libguestfs, у каталозі \f(CW\*(C`builder/templates\*(C'\fR.
.PP
\fIНалаштовування доступу до сховища\fR
.IX Subsection "Налаштовування доступу до сховища"
.PP
-Ви можете створити власний сайт із файлом покажчика (index) і деякими
-шаблонами, а потім вказати virt-builder на цей сайт за допомогою вмісту
-файла \fI.conf\fR.
+Ви можете створити власний сайт із файлом покажчика (index) і деякими шаблонами, а потім вказати virt-builder на цей сайт за допомогою вмісту файла \fI.conf\fR.
.PP
-Зауважте, що якщо ваш покажчик підписано, вам слід належним чином заповнити
-поле \fIgpgkey=..\fR у вашому файлі \fI.conf\fR, а також додати файл ключа \s-1GPG.\s0
+Зауважте, що якщо ваш покажчик підписано, вам слід належним чином заповнити поле \fIgpgkey=..\fR у вашому файлі \fI.conf\fR, а також додати файл ключа \s-1GPG.\s0
.PP
.Vb 3
\& virt\-builder \-\-source https://example.com/builder/index.asc \e
\& \-\-list
.Ve
.PP
-Ви можете розмістити сайт будь\-якому мережевому сервері або сервері \s-1FTP\s0 чи у
-локальній або мережевій файловій системі.
+Ви можете розмістити сайт будь\-якому мережевому сервері або сервері \s-1FTP\s0 чи у локальній або мережевій файловій системі.
.PP
\fIВстановлення ключа \s-1GPG\s0\fR
.IX Subsection "Встановлення ключа GPG"
.PP
-Якщо у вас ще немає ключа GnuPG, вам слід налаштувати такий. (Строго кажучи,
-це не є обов'язковою умовою, але якщо ваш файл покажчика і файл шаблона не
-буде підписано, користувачам virt-builder доведеться додавати параметр
-\&\fI\-\-no\-check\-signature\fR до команди кожного разу, коли їм потрібно буде
-скористатися virt-builder.)
+Якщо у вас ще немає ключа GnuPG, вам слід налаштувати такий. (Строго кажучи, це не є обов'язковою умовою, але якщо ваш файл покажчика і файл шаблона не буде підписано, користувачам virt-builder доведеться додавати параметр \fI\-\-no\-check\-signature\fR до команди кожного разу, коли їм потрібно буде скористатися virt-builder.)
.PP
-Інструкцію зі створення ключа можна знайти у підручнику з \s-1GPG:\s0
-http://www.gnupg.org/gph/en/manual.html.
+Інструкцію зі створення ключа можна знайти у підручнику з \s-1GPG:\s0 http://www.gnupg.org/gph/en/manual.html.
.PP
Експортувати ваш відкрити ключ \s-1GPG:\s0
.PP
\fIСтворення шаблонів\fR
.IX Subsection "Створення шаблонів"
.PP
-Існує багато способів створення шаблонів. Наприклад, ви можете клонувати
-наявні гостьові системи (див. \fBvirt\-sysprep\fR\|(1)) або встановити гостьову
-систему вручну (\fBvirt\-install\fR\|(1)). Щоб ознайомитися із способами створення
-шаблонів для virt-builder, вивчіть скрипти у \f(CW\*(C`builder/templates\*(C'\fR
+Існує багато способів створення шаблонів. Наприклад, ви можете клонувати наявні гостьові системи (див. \fBvirt\-sysprep\fR\|(1)) або встановити гостьову систему вручну (\fBvirt\-install\fR\|(1)). Щоб ознайомитися із способами створення шаблонів для virt-builder, вивчіть скрипти у \f(CW\*(C`builder/templates\*(C'\fR
.PP
-У virt-builder передбачено підтримку усіх форматів образів (наприклад, raw,
-qcow2 тощо) як шаблонів, у звичайному форматі та у форматі, стисненому
-\&\s-1XZ.\s0 Таким чином, як шаблонами можна скористатися наявними образами
-(наприклад, образами, очищеними за допомогою \fBvirt\-sysprep\fR\|(1)).
+У virt-builder передбачено підтримку усіх форматів образів (наприклад, raw, qcow2 тощо) як шаблонів, у звичайному форматі та у форматі, стисненому \s-1XZ.\s0 Таким чином, як шаблонами можна скористатися наявними образами (наприклад, образами, очищеними за допомогою \fBvirt\-sysprep\fR\|(1)).
.PP
-Для досягнення найкращих результатів під час стискання шаблонів
-скористайтеся такими параметрами програми xz (пояснення щодо цих параметрів
-можна знайти на сторінці довідки до \fBnbdkit\-xz\-plugin\fR\|(1)):
+Для досягнення найкращих результатів під час стискання шаблонів скористайтеся такими параметрами програми xz (пояснення щодо цих параметрів можна знайти на сторінці довідки до \fBnbdkit\-xz\-plugin\fR\|(1)):
.PP
.Vb 1
\& xz \-\-best \-\-block\-size=16777216 disk
\fIСтворення і підписування файла покажчика\fR
.IX Subsection "Створення і підписування файла покажчика"
.PP
-Файл покажчика записується у простому текстовому форматі (тут показано без
-цифрового підпису):
+Файл покажчика записується у простому текстовому форматі (тут показано без цифрового підпису):
.PP
.Vb 10
\& [fedora\-18]
\& expand=/dev/sda3
.Ve
.PP
-Частина у квадратних дужках є \f(CW\*(C`версією\-ОС\*(C'\fR, тим самим рядком, який
-використано у рядку команди virt-builder, використаному для збирання цієї
-операційної системи.
+Частина у квадратних дужках є \f(CW\*(C`версією\-ОС\*(C'\fR, тим самим рядком, який використано у рядку команди virt-builder, використаному для збирання цієї операційної системи.
.PP
-Спростити створення і підписування файла покажчика можна за допомогою
-програми \fBvirt\-builder\-repository\fR\|(1).
+Спростити створення і підписування файла покажчика можна за допомогою програми \fBvirt\-builder\-repository\fR\|(1).
.PP
-Після приготування файла \f(CW\*(C`index\*(C'\fR у належному форматі підпишіть його такою
-командою:
+Після приготування файла \f(CW\*(C`index\*(C'\fR у належному форматі підпишіть його такою командою:
.PP
.Vb 1
\& gpg \-\-clearsign \-\-armor index
.Ve
.PP
-У результаті виконання цієї команди буде створено остаточний файл із назвою
-\&\fIindex.asc\fR, який можна вивантажити на сервер (і додати у запис адреси
-\&\fIuri=..\fR). Як ми вже зауважували вище, підписування файла покажчика є
-необов'язковим, але рекомендованим.
+У результаті виконання цієї команди буде створено остаточний файл із назвою \fIindex.asc\fR, який можна вивантажити на сервер (і додати у запис адреси \fIuri=..\fR). Як ми вже зауважували вище, підписування файла покажчика є необов'язковим, але рекомендованим.
.PP
Можуть з’явитися такі поля:
.ie n .IP """name=НАЗВА""" 4
.el .IP "\f(CWname=НАЗВА\fR" 4
.IX Item "name=НАЗВА"
-Зручна для користувача назва цього шаблона. Назву буде показано у виведених
-даних команди з параметром \fI\-\-list\fR, більше ніде програма її не
-використовує.
+Зручна для користувача назва цього шаблона. Назву буде показано у виведених даних команди з параметром \fI\-\-list\fR, більше ніде програма її не використовує.
.ie n .IP """osinfo=ІДЕНТИФІКАТОР""" 4
.el .IP "\f(CWosinfo=ІДЕНТИФІКАТОР\fR" 4
.IX Item "osinfo=ІДЕНТИФІКАТОР"
-Це додаткове поле пов'язує операційну систему із відповідним ідентифікатором
-libosinfo. Virt-builder (ще) не використовує ці дані.
+Це додаткове поле пов'язує операційну систему із відповідним ідентифікатором libosinfo. Virt-builder (ще) не використовує ці дані.
.ie n .IP """arch=АРХІТЕКТУРА""" 4
.el .IP "\f(CWarch=АРХІТЕКТУРА\fR" 4
.IX Item "arch=АРХІТЕКТУРА"
-Архітектура операційної системи, яку встановлено у цьому шаблоні. Це поле є
-обов'язковим.
+Архітектура операційної системи, яку встановлено у цьому шаблоні. Це поле є обов'язковим.
.ie n .IP """file=ШЛЯХ""" 4
.el .IP "\f(CWfile=ШЛЯХ\fR" 4
.IX Item "file=ШЛЯХ"
Шлях (відносно покажчика) стисненого xz шаблона.
.Sp
-Зауважте, що тут \fBне\fR можна використовувати абсолютні шляхи або адреси
-файлів. Причиною є те, що у virt-builder використовується правило «одного
-походження» для шаблонів, тому вони не можуть походити з інших серверів.
+Зауважте, що тут \fBне\fR можна використовувати абсолютні шляхи або адреси файлів. Причиною є те, що у virt-builder використовується правило «одного походження» для шаблонів, тому вони не можуть походити з інших серверів.
.ie n .IP """sig=ШЛЯХ""" 4
.el .IP "\f(CWsig=ШЛЯХ\fR" 4
.IX Item "sig=ШЛЯХ"
-\&\fBЦей параметр вважається застарілим\fR. Використовуйте замість нього поле
-контрольної суми (checksum).
+\&\fBЦей параметр вважається застарілим\fR. Використовуйте замість нього поле контрольної суми (checksum).
.Sp
Шлях (відносно покажчика) від'єднаного підпису \s-1GPG\s0 файла xz.
.Sp
-Зауважте, що тут \fBне\fR можна використовувати абсолютні шляхи або адреси
-файлів. Причиною є те, що у virt-builder використовується правило «одного
-походження» для шаблонів, тому вони не можуть походити з інших серверів.
+Зауважте, що тут \fBне\fR можна використовувати абсолютні шляхи або адреси файлів. Причиною є те, що у virt-builder використовується правило «одного походження» для шаблонів, тому вони не можуть походити з інших серверів.
.Sp
Файл можна створити такою командою:
.Sp
.ie n .IP """checksum[sha512]=7b882fe9b82eb0fef...""" 4
.el .IP "\f(CWchecksum[sha512]=7b882fe9b82eb0fef...\fR" 4
.IX Item "checksum[sha512]=7b882fe9b82eb0fef..."
-Контрольну суму \s-1SHA\-512\s0 файла, вказаного у виразі \fIfile=..\fR, буде
-перевірено після завершення отримання даних. Для визначення підпису
-скористайтеся такою командою:
+Контрольну суму \s-1SHA\-512\s0 файла, вказаного у виразі \fIfile=..\fR, буде перевірено після завершення отримання даних. Для визначення підпису скористайтеся такою командою:
.Sp
.Vb 1
\& sha512sum disk.xz
.Ve
.Sp
-Зауважте, що якщо ви користуєтеся цим параметром, вам не потрібно
-підписувати файл, тобто використовувати параметр \f(CW\*(C`sig\*(C'\fR. Цей параметр має
-вищий пріоритет за параметра \f(CW\*(C`sig\*(C'\fR.
+Зауважте, що якщо ви користуєтеся цим параметром, вам не потрібно підписувати файл, тобто використовувати параметр \f(CW\*(C`sig\*(C'\fR. Цей параметр має вищий пріоритет за параметра \f(CW\*(C`sig\*(C'\fR.
.ie n .IP """checksum=7b882fe9b82eb0fef...""" 4
.el .IP "\f(CWchecksum=7b882fe9b82eb0fef...\fR" 4
.IX Item "checksum=7b882fe9b82eb0fef..."
\&\f(CW\*(C`checksum\*(C'\fR є скороченою формою запису \f(CW\*(C`checksum[sha512]\*(C'\fR.
.Sp
-Якщо вам доводиться працювати з virt-builder = 1.24.0, слід користуватися
-\&\f(CW\*(C`checksum\*(C'\fR, оскільки ця версію видаватиме повідомлення про помилку обробки,
-якщо у ключі поля використано квадратні дужки і цифри. Цю помилку виправлено
-у версіях virt-builder ≥ 1.24.1.
+Якщо вам доводиться працювати з virt-builder = 1.24.0, слід користуватися \f(CW\*(C`checksum\*(C'\fR, оскільки ця версію видаватиме повідомлення про помилку обробки, якщо у ключі поля використано квадратні дужки і цифри. Цю помилку виправлено у версіях virt-builder ≥ 1.24.1.
.ie n .IP """revision=N""" 4
.el .IP "\f(CWrevision=N\fR" 4
.IX Item "revision=N"
-Модифікація (revision) — ціле число, яке використовується для керування
-кешем шаблонів. Збільшення номера модифікації призводить до того, що клієнти
-отримують шаблон, навіть якщо у них є копія у кеші.
+Модифікація (revision) — ціле число, яке використовується для керування кешем шаблонів. Збільшення номера модифікації призводить до того, що клієнти отримують шаблон, навіть якщо у них є копія у кеші.
.Sp
-Номер модифікації є необов’язковим. Якщо його не вказано, типовим значенням
-вважається \f(CW1\fR.
+Номер модифікації є необов’язковим. Якщо його не вказано, типовим значенням вважається \f(CW1\fR.
.ie n .IP """format=raw""" 4
.el .IP "\f(CWformat=raw\fR" 4
.IX Item "format=raw"
.el .IP "\f(CWformat=qcow2\fR" 4
.IX Item "format=qcow2"
.PD
-Визначає формат образу диска; якщо дані стиснено, слід вказати формат до
-стискання. Якщо формат не вказано, його буде визначено автоматично, але все
-ж варто явним чином вказати бажаний формат.
+Визначає формат образу диска; якщо дані стиснено, слід вказати формат до стискання. Якщо формат не вказано, його буде визначено автоматично, але все ж варто явним чином вказати бажаний формат.
.Sp
-Зауважте, що це формат початкових даних, який відрізняється від параметра
-\&\fI\-\-format\fR (бажаний формат результату). Virt-builder виконує перетворення
-«на льоту» з початкового формату до бажаного формату результату.
+Зауважте, що це формат початкових даних, який відрізняється від параметра \fI\-\-format\fR (бажаний формат результату). Virt-builder виконує перетворення «на льоту» з початкового формату до бажаного формату результату.
.ie n .IP """size=NNN""" 4
.el .IP "\f(CWsize=NNN\fR" 4
.IX Item "size=NNN"
-Віртуальний розмір образу у байтах. Це розмір нестисненого образу. Якщо
-використано формат, відмінний від raw, зокрема qcow2, це значення означає
-розмір віртуального диска, а не розмір файла qcow2.
+Віртуальний розмір образу у байтах. Це розмір нестисненого образу. Якщо використано формат, відмінний від raw, зокрема qcow2, це значення означає розмір віртуального диска, а не розмір файла qcow2.
.Sp
Це поле слід заповнити.
.Sp
-Virt-builder також використовує це значення як мінімальний розмір, запит
-щодо якого можуть надсилати користувачів за допомогою параметра \fI\-\-size\fR,
-або типовий розмір, якщо не вказано параметр \fI\-\-size\fR.
+Virt-builder також використовує це значення як мінімальний розмір, запит щодо якого можуть надсилати користувачів за допомогою параметра \fI\-\-size\fR, або типовий розмір, якщо не вказано параметр \fI\-\-size\fR.
.ie n .IP """compressed_size=NNN""" 4
.el .IP "\f(CWcompressed_size=NNN\fR" 4
.IX Item "compressed_size=NNN"
-Справжній розмір образу диска у байтах, тобто розмір, який було вказано у
-\&\fIfile=..\fR. Це значення використовується лише для інформування (якщо
-використовуються формати \f(CW\*(C`long\*(C'\fR і \f(CW\*(C`json\*(C'\fR у параметрі \fI\-\-list\fR).
+Справжній розмір образу диска у байтах, тобто розмір, який було вказано у \fIfile=..\fR. Це значення використовується лише для інформування (якщо використовуються формати \f(CW\*(C`long\*(C'\fR і \f(CW\*(C`json\*(C'\fR у параметрі \fI\-\-list\fR).
.ie n .IP """expand=/dev/sdaX""" 4
.el .IP "\f(CWexpand=/dev/sdaX\fR" 4
.IX Item "expand=/dev/sdaX"
-При розпаковуванні образу до його остаточного розміру, наказати
-\&\fBvirt\-resize\fR\|(1) розпакувати дані до іменованого розділу у образі гостьової
-системи для заповнення усього доступного місця. Це працює подібно до
-параметра \fI\-\-expand\fR virt-resize.
+При розпаковуванні образу до його остаточного розміру, наказати \fBvirt\-resize\fR\|(1) розпакувати дані до іменованого розділу у образі гостьової системи для заповнення усього доступного місця. Це працює подібно до параметра \fI\-\-expand\fR virt-resize.
.Sp
-Тут вам зазвичай слід вказати назву пристрою у кореневій файловій системі
-гостьової операційної системи.
+Тут вам зазвичай слід вказати назву пристрою у кореневій файловій системі гостьової операційної системи.
.Sp
-Цим елементом варто скористатися, але це не обов'язково. Якщо поле
-пропущено, virt-resize створить додатковий розділ наприкінці диска для
-заповнення порожнього місця, що набагато менш зручно.
+Цим елементом варто скористатися, але це не обов'язково. Якщо поле пропущено, virt-resize створить додатковий розділ наприкінці диска для заповнення порожнього місця, що набагато менш зручно.
.ie n .IP """lvexpand=/пристрій/група_томів/логічний_том""" 4
.el .IP "\f(CWlvexpand=/пристрій/група_томів/логічний_том\fR" 4
.IX Item "lvexpand=/пристрій/група_томів/логічний_том"
-При розпаковуванні образу до його остаточного розміру, наказати
-\&\fBvirt\-resize\fR\|(1) розпакувати дані до іменованого логічного тому у образі
-гостьової системи для заповнення усього доступного місця. Це працює подібно
-до параметра \fI\-\-lv\-expand\fR virt-resize.
-.Sp
-Якщо у гостьовій системі використовується \s-1LVM2,\s0 тут слід вказати логічний
-том кореневої файлової системи гостьової операційної системи. Якщо у
-гостьовій операційній системі не використовується \s-1LVM2\s0 або її коренева
-файлова система не зберігається на логічному томі, не використовуйте цей
-параметр.
+При розпаковуванні образу до його остаточного розміру, наказати \fBvirt\-resize\fR\|(1) розпакувати дані до іменованого логічного тому у образі гостьової системи для заповнення усього доступного місця. Це працює подібно до параметра \fI\-\-lv\-expand\fR virt-resize.
+.Sp
+Якщо у гостьовій системі використовується \s-1LVM2,\s0 тут слід вказати логічний том кореневої файлової системи гостьової операційної системи. Якщо у гостьовій операційній системі не використовується \s-1LVM2\s0 або її коренева файлова система не зберігається на логічному томі, не використовуйте цей параметр.
.ie n .IP """notes=НОТАТКИ""" 4
.el .IP "\f(CWnotes=НОТАТКИ\fR" 4
.IX Item "notes=НОТАТКИ"
-Будь\-які нотатки, які стосуються цього образу, особливо нотатки із описом
-пакунків образу, способу створення образу та даних щодо ліцензування.
+Будь\-які нотатки, які стосуються цього образу, особливо нотатки із описом пакунків образу, способу створення образу та даних щодо ліцензування.
.Sp
Ці дані буде виведено у режимах \fI\-\-notes\fR і \fI\-\-list\fR \fI\-\-long\fR.
.Sp
-Ви можете створювати багаторядкові нотатки додаванням принаймні одного
-пробілу на початку кожного рядка (навіть порожнього):
+Ви можете створювати багаторядкові нотатки додаванням принаймні одного пробілу на початку кожного рядка (навіть порожнього):
.Sp
.Vb 5
\& notes=Цей образ було створено за допомогою
.ie n .IP """hidden=true""" 4
.el .IP "\f(CWhidden=true\fR" 4
.IX Item "hidden=true"
-Використання прапорця hidden усуває шаблон зі списку, який буде показано у
-відповідь на використання параметра \fI\-\-list\fR (лишаючи образ придатним до
-встановлення). Цей прапорець використовується для тестових образів.
+Використання прапорця hidden усуває шаблон зі списку, який буде показано у відповідь на використання параметра \fI\-\-list\fR (лишаючи образ придатним до встановлення). Цей прапорець використовується для тестових образів.
.ie n .IP """aliases=ПСЕВДОНІМ1 ПСЕВДОНІМ2 ...""" 4
.el .IP "\f(CWaliases=ПСЕВДОНІМ1 ПСЕВДОНІМ2 ...\fR" 4
.IX Item "aliases=ПСЕВДОНІМ1 ПСЕВДОНІМ2 ..."
-Це необов'язкове поле визначає список альтернативних назв, відокремлених
-пробілами, для образу. Альтернативною назвою, наприклад, можна скористатися
-так, щоб вона завжди вказувала на найсвіжішу версію певного образу, лишаючи
-інші, старіші версії доступними у покажчику, замість оновлення того самого
-образу (див. поле \f(CW\*(C`revision\*(C'\fR).
+Це необов'язкове поле визначає список альтернативних назв, відокремлених пробілами, для образу. Альтернативною назвою, наприклад, можна скористатися так, щоб вона завжди вказувала на найсвіжішу версію певного образу, лишаючи інші, старіші версії доступними у покажчику, замість оновлення того самого образу (див. поле \f(CW\*(C`revision\*(C'\fR).
.PP
\fIЗапуск virt-builder для декількох джерел одночасно\fR
.IX Subsection "Запуск virt-builder для декількох джерел одночасно"
.PP
-У virt-builder передбачено можливість використання декількох
-джерел. Рекомендованим способом є розгортання файлів \fI.conf\fR, які вказують
-на файли покажчика. Іншим способом є визначення джерел за допомогою
-декількох параметрів \fI\-\-source\fR і/або \fI\-\-fingerprint\fR:
+У virt-builder передбачено можливість використання декількох джерел. Рекомендованим способом є розгортання файлів \fI.conf\fR, які вказують на файли покажчика. Іншим способом є визначення джерел за допомогою декількох параметрів \fI\-\-source\fR і/або \fI\-\-fingerprint\fR:
.PP
.Vb 3
\& virt\-builder \e
\& \-\-source http://example.com/s2/index.asc
.Ve
.PP
-Ви можете надати N відбитків або 1 відбиток. Якщо буде надано N відбитків, N
-= кількості джерел, а між джерелом і відбитком є однозначна відповідність:
+Ви можете надати N відбитків або 1 відбиток. Якщо буде надано N відбитків, N = кількості джерел, а між джерелом і відбитком є однозначна відповідність:
.PP
.Vb 3
\& virt\-builder \e
\fIЛіцензування шаблонів\fR
.IX Subsection "Ліцензування шаблонів"
.PP
-Вам слід зважати на ліцензування образів, які ви розповсюджуєте. Для
-гостьових систем із відкритим кодом слід надавати посилання на початковий
-код у полі \f(CW\*(C`notes\*(C'\fR і виконувати інші вимоги (наприклад, вимоги щодо
-торгівельних знаків).
+Вам слід зважати на ліцензування образів, які ви розповсюджуєте. Для гостьових систем із відкритим кодом слід надавати посилання на початковий код у полі \f(CW\*(C`notes\*(C'\fR і виконувати інші вимоги (наприклад, вимоги щодо торгівельних знаків).
.PP
\fIФормальна специфікація файла покажчика\fR
.IX Subsection "Формальна специфікація файла покажчика"
.PP
-Формат файла покажчика має формальну специфікацію, що визначається сканером
-flex і обробником bison, що використовуються для обробки файла. Її можна
-знайти у таких файлах у ієрархію коду libguestfs:
+Формат файла покажчика має формальну специфікацію, що визначається сканером flex і обробником bison, що використовуються для обробки файла. Її можна знайти у таких файлах у ієрархію коду libguestfs:
.PP
.Vb 2
\& builder/index\-scan.l
\& builder/index\-parse.y
.Ve
.PP
-Для перевірки коректності файла покажчика використовується програма із
-назвою \fBvirt\-index\-validate\fR\|(1).
+Для перевірки коректності файла покажчика використовується програма із назвою \fBvirt\-index\-validate\fR\|(1).
.PP
-Зауважте, що обробник і інструмент може працювати як із підписаним, так і з
-непідписаним файлом покажчика (тобто з \fIindex\fR або з\fIindex.asc\fR).
+Зауважте, що обробник і інструмент може працювати як із підписаним, так і з непідписаним файлом покажчика (тобто з \fIindex\fR або з\fIindex.asc\fR).
.PP
Кодуванням покажчика завжди є \s-1UTF\-8.\s0
.SS "КЕШУВАННЯ"
\fIКешування шаблонів\fR
.IX Subsection "Кешування шаблонів"
.PP
-Оскільки шаблоні зазвичай є дуже великими, отримані шаблони зберігають у
-кеші домашнього каталогу користувача.
+Оскільки шаблоні зазвичай є дуже великими, отримані шаблони зберігають у кеші домашнього каталогу користувача.
.PP
-Кеш розміщується у \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR або
-\&\fI\f(CI$HOME\fI/.cache/virt\-builder\fR.
+Кеш розміщується у \fI\f(CI$XDG_CACHE_HOME\fI/virt\-builder/\fR або \fI\f(CI$HOME\fI/.cache/virt\-builder\fR.
.PP
-Ви можете отримати дані щодо каталогу кешу, зокрема дані щодо того, які
-гостьові системи кешуються, за допомогою такої команди:
+Ви можете отримати дані щодо каталогу кешу, зокрема дані щодо того, які гостьові системи кешуються, за допомогою такої команди:
.PP
.Vb 1
\& virt\-builder \-\-print\-cache
.PP
Щоб вимкнути кешування шаблонів, скористайтеся параметром \fI\-\-no\-cache\fR.
.PP
-Кешуванню підлягають лише шаблони. Для покажчика та цифрових підписів
-кешування не використовується.
+Кешуванню підлягають лише шаблони. Для покажчика та цифрових підписів кешування не використовується.
.PP
\fIКешування пакунків\fR
.IX Subsection "Кешування пакунків"
.PP
-Virt-builder використовує для отримання файлів \fBcurl\fR\|(1), а також
-використовує поточні параметри \f(CW\*(C`http_proxy\*(C'\fR (та інші) під час встановлення
-пакунків (\fI\-\-install\fR, \fI\-\-update\fR).
+Virt-builder використовує для отримання файлів \fBcurl\fR\|(1), а також використовує поточні параметри \f(CW\*(C`http_proxy\*(C'\fR (та інші) під час встановлення пакунків (\fI\-\-install\fR, \fI\-\-update\fR).
.PP
-Тому ви можете встановити ці змінні середовища з метою максимізації обсягу
-локального кешування. Див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" та \fBcurl\fR\|(1).
+Тому ви можете встановити ці змінні середовища з метою максимізації обсягу локального кешування. Див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" та \fBcurl\fR\|(1).
.PP
\fIЛокальні дзеркала\fR
.IX Subsection "Локальні дзеркала"
.PP
-Щоб збільшити швидкість і надійність встановлення пакунків, ви можете
-налаштувати локальне дзеркало для дистрибутива призначення і вказати на
-нього засобу керування пакунками гостьової системи.
+Щоб збільшити швидкість і надійність встановлення пакунків, ви можете налаштувати локальне дзеркало для дистрибутива призначення і вказати на нього засобу керування пакунками гостьової системи.
.PP
Використання локального дзеркала з Fedora
.IX Subsection "Використання локального дзеркала з Fedora"
Використання локального дзеркала з Debian
.IX Subsection "Використання локального дзеркала з Debian"
.PP
-Припускаємо, що ви використовуєте \f(CW\*(C`apt\-proxy\*(C'\fR для віддзеркалення сховища,
-тоді вам слід створити новий файл \fIsources.list\fR для визначення вашого
-проксі\-сервера (див. https://help.ubuntu.com/community/AptProxy), а потім
-віддайте таку команду:
+Припускаємо, що ви використовуєте \f(CW\*(C`apt\-proxy\*(C'\fR для віддзеркалення сховища, тоді вам слід створити новий файл \fIsources.list\fR для визначення вашого проксі\-сервера (див. https://help.ubuntu.com/community/AptProxy), а потім віддайте таку команду:
.PP
.Vb 4
\& virt\-builder debian\-8 \e
.Ve
.SS "ЦИФРОВІ ПІДПИСИ"
.IX Subsection "ЦИФРОВІ ПІДПИСИ"
-Virt-builder використовує \s-1GNU\s0 Privacy Guard (GnuPG або gpg) для забезпечення
-невтручання до покажчика і шаблонів.
+Virt-builder використовує \s-1GNU\s0 Privacy Guard (GnuPG або gpg) для забезпечення невтручання до покажчика і шаблонів.
.PP
Джерело вказує на файл покажчика, який можна підписати.
.PP
-Virt-builder отримує покажчик і перевіряє, чи є підпис коректним і чи
-збігається відбиток підписника із вказаним відбитком (тобто відбитком,
-вказаним за допомогою \fIgpgkey=..\fR у \fI.conf\fR або за допомогою
-\&\fI\-\-fingerprint\fR, саме у цьому порядку).
+Virt-builder отримує покажчик і перевіряє, чи є підпис коректним і чи збігається відбиток підписника із вказаним відбитком (тобто відбитком, вказаним за допомогою \fIgpgkey=..\fR у \fI.conf\fR або за допомогою \fI\-\-fingerprint\fR, саме у цьому порядку).
.PP
-Для перевірки відповідності щодо вбудованого відкритого ключа або відбитка,
-відкритий ключ слід імпортувати до локального сховища ключів gpg користувача
-(саме так працює gpg).
+Для перевірки відповідності щодо вбудованого відкритого ключа або відбитка, відкритий ключ слід імпортувати до локального сховища ключів gpg користувача (саме так працює gpg).
.PP
Під час отримання шаблона його підпис буде перевірено у той самий спосіб.
.PP
-Хоча підписи і не є обов'язковими, якщо ви їх не використаєте, користувачам
-virt-builder доведеться використовувати параметр \fI\-\-no\-check\-signature\fR у
-рядку команди. За допомогою підпису можна запобігти заміні зловмисником
-підписаного файла покажчика непідписаним файлом. При цьому virt-builder без
-перевірки підпису не повідомлятиме про підміну. Щоб там не сталося,
-наполегливо рекомендуємо вам створювати підписаний покажчик і шаблони.
+Хоча підписи і не є обов'язковими, якщо ви їх не використаєте, користувачам virt-builder доведеться використовувати параметр \fI\-\-no\-check\-signature\fR у рядку команди. За допомогою підпису можна запобігти заміні зловмисником підписаного файла покажчика непідписаним файлом. При цьому virt-builder без перевірки підпису не повідомлятиме про підміну. Щоб там не сталося, наполегливо рекомендуємо вам створювати підписаний покажчик і шаблони.
.SS "АРХІТЕКТУРА"
.IX Subsection "АРХІТЕКТУРА"
-Virt-builder може збирати образ гостьової системи для будь\-якої архітектури,
-незалежно від архітектури основної системи. Наприклад, можна зібрати образ
-гостьової системи архітектури x86\-64 на основній системі архітектури \s-1ARM.\s0
-.PP
-Втім, деякі з параметрів не працюватимуть, особливо параметри, які
-потребують виконання команд у гостьовій системі під час процесу збирання:
-\&\fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR, \fI\-\-run\-command\fR. Вам варто замінити ці
-команди на їхні еквіваленти у firstboot.
-.PP
-Основна система архітектури x86\-64, збираючи гостьові системи 32\-бітової
-архітектури i686, має працювати без використання будь\-яких додаткових кроків
-налаштовування.
+Virt-builder може збирати образ гостьової системи для будь\-якої архітектури, незалежно від архітектури основної системи. Наприклад, можна зібрати образ гостьової системи архітектури x86\-64 на основній системі архітектури \s-1ARM.\s0
+.PP
+Втім, деякі з параметрів не працюватимуть, особливо параметри, які потребують виконання команд у гостьовій системі під час процесу збирання: \fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR, \fI\-\-run\-command\fR. Вам варто замінити ці команди на їхні еквіваленти у firstboot.
+.PP
+Основна система архітектури x86\-64, збираючи гостьові системи 32\-бітової архітектури i686, має працювати без використання будь\-яких додаткових кроків налаштовування.
.SS "БЕЗПЕКА"
.IX Subsection "БЕЗПЕКА"
-Virt-builder не потребує запуску від імені користувача root (фактично,
-програму не слід запускати від імені root) і не використовує setuid, \f(CW\*(C`sudo\*(C'\fR
-або будь\-яких інших подібних механізмів.
-.PP
-\&\fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR і \fI\-\-run\-command\fR реалізовано за
-допомогою базової системи (невеличкої віртуальної машини), тому ці команди
-не працюватимуть у основній системі. Якщо ви користуєтеся модулем libvirt
-libguestfs і у системі увімкнено SELinux , віртуальну машину буде додатково
-огорнуто у контейнер SELinux (sVirt).
-.PP
-Втім, ці параметри отримуватимуть доступ до мережі основної системи і,
-оскільки шаблон може містити шахрайський код, цей код може намагатися
-отримати доступ до ресурсів мережі основної системи, які мають бути
-недоступними для нього. Для запобігання небажаному доступу ви можете
-скористатися параметром \fI\-\-no\-network\fR.
-.PP
-Команди першого завантаження виконуються у контексті гостьової системи, тому
-слід брати до уваги параметри захисту у вашому гіпервізорі або
-обчислювальній хмарі.
-.PP
-Virt-builder додає випадкову базу псевдовипадкових чисел до кожної гостьової
-системи, яку зібрано за його допомогою. Це допомагає забезпеченню справжньої
-випадковості номерів послідовності \s-1TCP, UUID,\s0 ключів вузла ssh тощо під час
-завантаження гостьової системи.
-.PP
-Вам слід перевіряти цифрові підписи і не ігнорувати повідомлення про помилки
-під час таких перевірок.
+Virt-builder не потребує запуску від імені користувача root (фактично, програму не слід запускати від імені root) і не використовує setuid, \f(CW\*(C`sudo\*(C'\fR або будь\-яких інших подібних механізмів.
+.PP
+\&\fI\-\-install\fR, \fI\-\-update\fR, \fI\-\-run\fR і \fI\-\-run\-command\fR реалізовано за допомогою базової системи (невеличкої віртуальної машини), тому ці команди не працюватимуть у основній системі. Якщо ви користуєтеся модулем libvirt libguestfs і у системі увімкнено SELinux , віртуальну машину буде додатково огорнуто у контейнер SELinux (sVirt).
+.PP
+Втім, ці параметри отримуватимуть доступ до мережі основної системи і, оскільки шаблон може містити шахрайський код, цей код може намагатися отримати доступ до ресурсів мережі основної системи, які мають бути недоступними для нього. Для запобігання небажаному доступу ви можете скористатися параметром \fI\-\-no\-network\fR.
+.PP
+Команди першого завантаження виконуються у контексті гостьової системи, тому слід брати до уваги параметри захисту у вашому гіпервізорі або обчислювальній хмарі.
+.PP
+Virt-builder додає випадкову базу псевдовипадкових чисел до кожної гостьової системи, яку зібрано за його допомогою. Це допомагає забезпеченню справжньої випадковості номерів послідовності \s-1TCP, UUID,\s0 ключів вузла ssh тощо під час завантаження гостьової системи.
+.PP
+Вам слід перевіряти цифрові підписи і не ігнорувати повідомлення про помилки під час таких перевірок.
.SS "КЛОНИ"
.IX Subsection "КЛОНИ"
-Якщо вам потрібно створити багато гостьових систем одного типу, виникає
-спокуса запустити virt-builder один раз, а потім просто скопіювати
-файл\-результат. Втім, так \fBне\fR слід робити. Вам слід запустити virt-builder
-окремо для кожної нової гостьової системи, яку ви хочете створити.
+Якщо вам потрібно створити багато гостьових систем одного типу, виникає спокуса запустити virt-builder один раз, а потім просто скопіювати файл\-результат. Втім, так \fBне\fR слід робити. Вам слід запустити virt-builder окремо для кожної нової гостьової системи, яку ви хочете створити.
.PP
-Так слід робити тому, що кожен клон повинен мати (принаймні) окрему базу для
-псевдовипадкових чисел, а також, ймовірно, інші унікальні властивості
-(зокрема \s-1UUID\s0 файлових систем) у майбутніх версіях virt-builder.
+Так слід робити тому, що кожен клон повинен мати (принаймні) окрему базу для псевдовипадкових чисел, а також, ймовірно, інші унікальні властивості (зокрема \s-1UUID\s0 файлових систем) у майбутніх версіях virt-builder.
.PP
-Ще однією річчю, яку вам \fIне\fR слід робити, є клонування завантаженого
-образу диска. Причиною цього є те, що деякі гостьові системи створюють
-унікальні ідентифікатори машини, ключі \s-1SSH\s0 вузла та інші дані під час
-першого завантаження, а дублювання таких ідентифікаторів у клонах є вкрай
-небажаним.
+Ще однією річчю, яку вам \fIне\fR слід робити, є клонування завантаженого образу диска. Причиною цього є те, що деякі гостьові системи створюють унікальні ідентифікатори машини, ключі \s-1SSH\s0 вузла та інші дані під час першого завантаження, а дублювання таких ідентифікаторів у клонах є вкрай небажаним.
.PP
Див. також \fBvirt\-sysprep\fR\|(1).
.SS "ШВИДКОДІЯ"
.IX Subsection "ШВИДКОДІЯ"
-Найважливішим аспектом пришвидшення роботи програми є кешування. Шаблон
-завантажується до кешу, коли його вперше використовують, або якщо було
-використано параметр команди \fI\-\-cache\-all\-templates\fR. Докладніше про це у
-розділі \*(L"КЕШУВАННЯ\*(R" вище.
-.PP
-Пакунки, потрібні для виконання завдань із параметрами \fI\-\-install\fR та
-\&\fI\-\-update\fR, отримуються за допомогою з'єднання з мережею основної
-системи. Встановлення значень змінних середовища \f(CW\*(C`http_proxy\*(C'\fR,
-\&\f(CW\*(C`https_proxy\*(C'\fR та \f(CW\*(C`ftp_proxy\*(C'\fR таким чином, щоб вони вказували на локальний
-кеш, може забезпечити режим, за якого ці пакунки отримуватимуться із
-інтернету лише один раз. Ви також можете спробувати скористатися локальним
-сховищем пакунків, хоча налаштовування такого сховища може бути складною
-справою, специфічною для того дистрибутива Linux, який ви намагаєтеся
-встановити.
+Найважливішим аспектом пришвидшення роботи програми є кешування. Шаблон завантажується до кешу, коли його вперше використовують, або якщо було використано параметр команди \fI\-\-cache\-all\-templates\fR. Докладніше про це у розділі \*(L"КЕШУВАННЯ\*(R" вище.
+.PP
+Пакунки, потрібні для виконання завдань із параметрами \fI\-\-install\fR та \fI\-\-update\fR, отримуються за допомогою з'єднання з мережею основної системи. Встановлення значень змінних середовища \f(CW\*(C`http_proxy\*(C'\fR, \f(CW\*(C`https_proxy\*(C'\fR та \f(CW\*(C`ftp_proxy\*(C'\fR таким чином, щоб вони вказували на локальний кеш, може забезпечити режим, за якого ці пакунки отримуватимуться із інтернету лише один раз. Ви також можете спробувати скористатися локальним сховищем пакунків, хоча налаштовування такого сховища може бути складною справою, специфічною для того дистрибутива Linux, який ви намагаєтеся встановити.
.PP
\fIКористування \fI\-\-no\-sync\fI\fR
.IX Subsection "Користування --no-sync"
.PP
-Скористайтеся \fI\-\-no\-sync\fR. Втім, ознайомтеся із можливими проблемами,
-описаними у розділі \*(L"ПАРАМЕТРИ\*(R" вище, оскільки це може призвести до
-пошкодження даних на диску, якщо використовувати неправильно.
+Скористайтеся \fI\-\-no\-sync\fR. Втім, ознайомтеся із можливими проблемами, описаними у розділі \*(L"ПАРАМЕТРИ\*(R" вище, оскільки це може призвести до пошкодження даних на диску, якщо використовувати неправильно.
.PP
\fIПропускання virt-resize\fR
.IX Subsection "Пропускання virt-resize"
.PP
-За певних умов virt-builder може пропускати крок virt-resize. Це значно
-пришвидшує роботу virt-builder. Умови пропускання є такими:
+За певних умов virt-builder може пропускати крок virt-resize. Це значно пришвидшує роботу virt-builder. Умови пропускання є такими:
.IP "\(bu" 4
дані слід виводити до звичайного файла (не на блоковий пристрій), \fBі\fR
.IP "\(bu" 4
\fIpxzcat\fR
.IX Subsection "pxzcat"
.PP
-Virt-builder використовує внутрішню реалізацію pxzcat (паралельного xzcat),
-якщо під час збирання програми було знайдено liblzma. Якщо liblzma не було
-знайдено під час збирання, використовуватиметься звичайний \f(CW\*(C`xzcat\*(C'\fR, який
-працює у один потік.
-.PP
-\fIUser-Mode Linux\fR
-.IX Subsection "User-Mode Linux"
-.PP
-Ви можете використовувати virt-builder у поєднанні з модулем User-Mode Linux
-(\s-1UML\s0). У такому режимі програма може працювати швидше, якщо virt-builder
-запущено у віртуальній машині (наприклад у хмарі).
-.PP
-Щоб увімкнути модуль \s-1UML,\s0 ознайомтеся із настановами у розділі
-\&\*(L"USER-MODE \s-1LINUX BACKEND\*(R"\s0 in \fBguestfs\fR\|(3).
-.PP
-У поточній версії вам слід користуватися параметром \fI\-\-no\-network\fR. Це буде
-виправлено у майбутній версії.
-.PP
-Підтримки формату виведення результатів qcow2 у \s-1UML\s0 не передбачено. Ви
-можете створювати гостьові системи лише у форматі raw.
+Virt-builder використовує внутрішню реалізацію pxzcat (паралельного xzcat), якщо під час збирання програми було знайдено liblzma. Якщо liblzma не було знайдено під час збирання, використовуватиметься звичайний \f(CW\*(C`xzcat\*(C'\fR, який працює у один потік.
.SS "\s-1SELINUX\s0"
.IX Subsection "SELINUX"
-Гостьові системи, у яких використовується SELinux (зокрема Fedora і Red Hat
-Enterprise Linux) потребують коректної мітки SELinux для кожного файла.
+Гостьові системи, у яких використовується SELinux (зокрема Fedora і Red Hat Enterprise Linux) потребують коректної мітки SELinux для кожного файла.
.PP
-Virt-builder не може знайти про спосіб, у який новим файлам надаються
-мітки. Тому існує дві можливі стратегії, використання яких забезпечує
-встановлення належних міток:
+Virt-builder не може знайти про спосіб, у який новим файлам надаються мітки. Тому існує дві можливі стратегії, використання яких забезпечує встановлення належних міток:
.IP "Користування \fI\-\-selinux\-relabel\fR" 4
.IX Item "Користування --selinux-relabel"
-Запуск \fBsetfiles\fR\|(8) безпосередньо перед завершенням збирання образу
-гостьової системи для встановлення належних міток SELinux на образі диска.
+Запуск \fBsetfiles\fR\|(8) безпосередньо перед завершенням збирання образу гостьової системи для встановлення належних міток SELinux на образі диска.
.Sp
Це рекомендований метод.
.IP "\fI\-\-touch\fR \fI/.autorelabel\fR" 4
.IX Item "--touch /.autorelabel"
-Наявність у гостьовій системі файла із назвою \fI/.autorelabel\fR або можливе
-його створення.
-.Sp
-У гостьових системах, де використовується SELinux, це спричиняє запуск
-\&\fBrestorecon\fR\|(8) під час першого завантаження. Гостьові системи самостійно
-перезавантажуються під час першого використання — це нормальна і нешкідлива
-поведінка.
-.PP
-Будь ласка, зауважте, що якщо у вашій гостьовій системі використовується
-SELinux, і ви виконуєте над цією системою дії, які можуть призвести до
-створення файлів або внесення змін до наявних файлів, варто скористатися
-\&\fI\-\-selinux\-relabel\fR. Так можна забезпечити встановлення належних міток
-SELinux для цих файлів.
+Наявність у гостьовій системі файла із назвою \fI/.autorelabel\fR або можливе його створення.
+.Sp
+У гостьових системах, де використовується SELinux, це спричиняє запуск \fBrestorecon\fR\|(8) під час першого завантаження. Гостьові системи самостійно перезавантажуються під час першого використання — це нормальна і нешкідлива поведінка.
+.PP
+Будь ласка, зауважте, що якщо у вашій гостьовій системі використовується SELinux, і ви виконуєте над цією системою дії, які можуть призвести до створення файлів або внесення змін до наявних файлів, варто скористатися \fI\-\-selinux\-relabel\fR. Так можна забезпечити встановлення належних міток SELinux для цих файлів.
.SH "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
.IX Header "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра
-робить зручним використання virt-builder з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра робить зручним використання virt-builder з інших програм, графічних інтерфейсів тощо.
.PP
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-builder. Типово виведені дані виглядатимуть якось
-так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-builder. Типово виведені дані виглядатимуть якось так:
.PP
.Vb 7
\& $ virt\-builder \-\-machine\-readable
\& pxzcat
.Ve
.PP
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
.PP
-Можна вказати рядок форматування для керування виведенням,
-див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
+Можна вказати рядок форматування для керування виведенням, див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
-Опис інших змінних середовища, які стосуються усіх програм libguestfs,
-наведено у розділі \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
+Опис інших змінних середовища, які стосуються усіх програм libguestfs, наведено у розділі \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
.ie n .IP """http_proxy""" 4
.el .IP "\f(CWhttp_proxy\fR" 4
.IX Item "http_proxy"
.el .IP "\f(CWno_proxy\fR" 4
.IX Item "no_proxy"
.PD
-Встановити проксі\-сервер для отримання даних. Ці змінні середовища (та інші)
-насправді обробляються \fBcurl\fR\|(1), а не virt-builder.
+Встановити проксі\-сервер для отримання даних. Ці змінні середовища (та інші) насправді обробляються \fBcurl\fR\|(1), а не virt-builder.
.ie n .IP """HOME""" 4
.el .IP "\f(CWHOME\fR" 4
.IX Item "HOME"
-Використовується для визначення місця кешу шаблонів та місця джерел
-користувача. Див. \*(L"КЕШУВАННЯ\*(R" і \*(L"ДЖЕРЕЛА ШАБЛОНІВ\*(R".
+Використовується для визначення місця кешу шаблонів та місця джерел користувача. Див. \*(L"КЕШУВАННЯ\*(R" і \*(L"ДЖЕРЕЛА ШАБЛОНІВ\*(R".
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
.Sp
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-\&\fI/usr/share/virt\-tools\fR).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на \fI/usr/share/virt\-tools\fR).
.Sp
Цей каталог може містити такі файли:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і
-\&\fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.Sp
Див. також \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-\&\fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0 використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.RE
.RS 4
.RE
.ie n .IP """XDG_CONFIG_HOME""" 4
.el .IP "\f(CWXDG_CONFIG_HOME\fR" 4
.IX Item "XDG_CONFIG_HOME"
-Використовується для визначення місця джерел користувача. Див. \*(L"ДЖЕРЕЛА
-ШАБЛОНІВ\*(R".
+Використовується для визначення місця джерел користувача. Див. \*(L"ДЖЕРЕЛА ШАБЛОНІВ\*(R".
.ie n .IP """VIRT_BUILDER_DIRS""" 4
.el .IP "\f(CWVIRT_BUILDER_DIRS\fR" 4
.IX Item "VIRT_BUILDER_DIRS"
-Використовується для визначення місця джерел системи. Див. \*(L"ДЖЕРЕЛА
-ШАБЛОНІВ\*(R".
+Використовується для визначення місця джерел системи. Див. \*(L"ДЖЕРЕЛА ШАБЛОНІВ\*(R".
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1),
-\&\fBvirt\-builder\-repository\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-customize\fR\|(1),
-\&\fBvirt\-get\-kernel\fR\|(1), \fBvirt\-install\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBvirt\-resize\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBoz\-install\fR\|(1), \fBgpg\fR\|(1),
-\&\fBgpg2\fR\|(1), \fBcurl\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBgenisoimage\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-builder\-repository\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-customize\fR\|(1), \fBvirt\-get\-kernel\fR\|(1), \fBvirt\-install\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBoz\-install\fR\|(1), \fBgpg\fR\|(1), \fBgpg2\fR\|(1), \fBcurl\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBgenisoimage\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Virt-builder — інструмент для швидкого збирання нових віртуальних машин. За
-його допомогою ви зможете зібрати цілий спектр віртуальних машин для
-локального використання або використання у «хмарі». Зазвичай, для цього
-достатньо декількох хвилин. Крім того, у virt-builder передбачено багато
-способів налаштовування зібраних віртуальних машин. Усі команди віддаються
-за допомогою командного рядка. Для роботи програми не потрібні права доступу
-адміністратора системи, тому збирання нових віртуальних машин просто
-автоматизувати або керувати ним за допомогою скриптів.
-
-Зауважте, що virt-builder не встановлює гостьові системи «з нуля». Програма
-використовує ретельного приготовані, підписані цифровими підписами шаблони
-операційних систем і налаштовує їх. Такий підхід використано, оскільки він є
-набагато швидшим за інші. Втім, якщо потрібно встановити систему «з нуля»,
-ви можете скористатися L<virt-install(1)> та L<oz-install(1)>.
+Virt-builder — інструмент для швидкого збирання нових віртуальних машин. За його допомогою ви зможете зібрати цілий спектр віртуальних машин для локального використання або використання у «хмарі». Зазвичай, для цього достатньо декількох хвилин. Крім того, у virt-builder передбачено багато способів налаштовування зібраних віртуальних машин. Усі команди віддаються за допомогою командного рядка. Для роботи програми не потрібні права доступу адміністратора системи, тому збирання нових віртуальних машин просто автоматизувати або керувати ним за допомогою скриптів.
+
+Зауважте, що virt-builder не встановлює гостьові системи «з нуля». Програма використовує ретельного приготовані, підписані цифровими підписами шаблони операційних систем і налаштовує їх. Такий підхід використано, оскільки він є набагато швидшим за інші. Втім, якщо потрібно встановити систему «з нуля», ви можете скористатися L<virt-install(1)> та L<oz-install(1)>.
Найпростіше буде розпочати з прикладів з наступного розділу.
virt-builder --list
-покаже список доступних до встановлення операційних систем. Типово,
-доступний набір операційних систем із вільним поширенням. Ви також можете
-додати свою операційну систему (див. нижче).
+покаже список доступних до встановлення операційних систем. Типово, доступний набір операційних систем із вільним поширенням. Ви також можете додати свою операційну систему (див. нижче).
-Після вибору гостьової системи зі списку може виникнути потреба у
-ознайомленні із нотатками щодо встановлення:
+Після вибору гостьової системи зі списку може виникнути потреба у ознайомленні із нотатками щодо встановлення:
virt-builder --notes fedora-27
virt-builder fedora-27
-збере образ Fedora 25 для тієї самої архітектури, що і virt-builder (отже
-виконання команди у системі архітектури i686 призведе до спроби збирання
-образу i686, якщо це можливо). Образ матиме типові налаштування (мінімальний
-розмір, без облікових записів користувачів, випадковий пароль root, лише
-базовий мінімальний набір встановлених програм тощо).
+збере образ Fedora 25 для тієї самої архітектури, що і virt-builder (отже виконання команди у системі архітектури i686 призведе до спроби збирання образу i686, якщо це можливо). Образ матиме типові налаштування (мінімальний розмір, без облікових записів користувачів, випадковий пароль root, лише базовий мінімальний набір встановлених програм тощо).
Потреби у запуску цієї програми від імені root I<немає>.
-Першого разу доведеться отримати шаблон мережею, а наступні операції може
-бути кешовано (див. L</КЕШУВАННЯ>).
+Першого разу доведеться отримати шаблон мережею, а наступні операції може бути кешовано (див. L</КЕШУВАННЯ>).
-Назву файла результатів буде визначено на основі назви шаблона, отже для
-наведеного вище прикладу буде F<fedora-27.img>. Змінити назву файла
-результатів можна за допомогою параметра I<-o>:
+Назву файла результатів буде визначено на основі назви шаблона, отже для наведеного вище прикладу буде F<fedora-27.img>. Змінити назву файла результатів можна за допомогою параметра I<-o>:
virt-builder fedora-27 -o mydisk.img
-Ви також можете скористатися параметром I<-o> для запису на наявні пристрої
-або логічні томи.
+Ви також можете скористатися параметром I<-o> для запису на наявні пристрої або логічні томи.
virt-builder fedora-27 --format qcow2
-Те саме, що і вище, але виведені дані буде записано у форматі qcow2 до
-F<fedora-27.qcow2>.
+Те саме, що і вище, але виведені дані буде записано у форматі qcow2 до F<fedora-27.qcow2>.
virt-builder fedora-27 --size 20G
-Як і вище, але обсяг виведених даних дорівнюватиме 20 ГБ. Розмір гостьової
-операційної системи буде змінено так, наче її скопійовано до виведених даних
-(автоматично, за допомогою L<virt-resize(1)>).
+Як і вище, але обсяг виведених даних дорівнюватиме 20 ГБ. Розмір гостьової операційної системи буде змінено так, наче її скопійовано до виведених даних (автоматично, за допомогою L<virt-resize(1)>).
virt-builder fedora-27 --arch i686
virt-builder fedora-27 --root-password file:/tmp/rootpw
-Створити образ Fedora 25. Пароль користувача root буде запозичено з файла
-F</tmp/rootpw>.
+Створити образ Fedora 25. Пароль користувача root буде запозичено з файла F</tmp/rootpw>.
-Зауважте, що якщо ви I<не встановите> I<--root-password>, гостьовій системі
-буде надано I<випадковий> пароль адміністратора root, який буде виведено до
-стандартного виведення.
+Зауважте, що якщо ви I<не встановите> I<--root-password>, гостьовій системі буде надано I<випадковий> пароль адміністратора root, який буде виведено до стандартного виведення.
-Крім того, ви можете створювати облікові записи
-користувачів. Див. L</КОРИСТУВАЧІ І ПАРОЛІ> нижче.
+Крім того, ви можете створювати облікові записи користувачів. Див. L</КОРИСТУВАЧІ І ПАРОЛІ> нижче.
=head2 Встановити назву вузла
=head2 Встановлення програмного забезпечення
-Встановлення пакунків зі звичайного (гостьового) сховища (наприклад, за
-допомогою dnf або apt):
+Встановлення пакунків зі звичайного (гостьового) сховища (наприклад, за допомогою dnf або apt):
virt-builder fedora-27 --install "inkscape,@Xfce Desktop"
-(У Fedora C<@> використовується для встановлення груп пакунків. У Debian вам
-доведеться встановлювати відповідний метапакунок.)
+(У Fedora C<@> використовується для встановлення груп пакунків. У Debian вам доведеться встановлювати відповідний метапакунок.)
Для оновлення встановлених пакунків до останньої версії виконайте такі дії:
virt-builder debian-7 --update
-Для гостьових систем, де використовується SELinux, зокрема Fedora і Red Hat
-Enterprise Linux, може знадобитися зміна міток SELinux після встановлення
-або оновлення пакунків (див. L</SELINUX> нижче):
+Для гостьових систем, де використовується SELinux, зокрема Fedora і Red Hat Enterprise Linux, може знадобитися зміна міток SELinux після встановлення або оновлення пакунків (див. L</SELINUX> нижче):
virt-builder fedora-27 --update --selinux-relabel
=head2 Налаштовування встановленої системи
-Передбачено багато параметрів, за допомогою яких ви можете налаштувати
-встановлення. Це зокрема параметр I<--run>/I<--run-command>, за допомогою
-якого можна виконати скрипт оболонки або команду під час створення образу
-диска і додати або змінити файли, які буде включено до образу диска. За
-допомогою параметра I<--firstboot>/I<--firstboot-command> можна додати
-скрипти або команди, які буде виконано під час першого завантаження
-гостьової системи. За допомогою параметра I<--edit> можна редагувати файли,
-а параметра I<--upload> — вивантажувати файли до образу.
+Передбачено багато параметрів, за допомогою яких ви можете налаштувати встановлення. Це зокрема параметр I<--run>/I<--run-command>, за допомогою якого можна виконати скрипт оболонки або команду під час створення образу диска і додати або змінити файли, які буде включено до образу диска. За допомогою параметра I<--firstboot>/I<--firstboot-command> можна додати скрипти або команди, які буде виконано під час першого завантаження гостьової системи. За допомогою параметра I<--edit> можна редагувати файли, а параметра I<--upload> — вивантажувати файли до образу.
Приклад:
virt-builder fedora-27 --firstboot-command 'dnf -y --best update'
-у результаті команду L<dnf(8)> C<update> буде один раз виконано під час
-першого завантаження гостьової системи.
+у результаті команду L<dnf(8)> C<update> буде один раз виконано під час першого завантаження гостьової системи.
або
--edit '/etc/dnf/dnf.conf:
s/gpgcheck=1/gpgcheck=0/'
-буде змінено F</etc/dnf/dnf.conf> у образі диска (під час створення образу
-диска, задовго до завантаження).
+буде змінено F</etc/dnf/dnf.conf> у образі диска (під час створення образу диска, задовго до завантаження).
Ви можете поєднувати ці параметри і додавати декілька параметрів усіх типів.
=item B<--arch> АРХІТЕКТУРА
-Використовувати для образу-результату вказану архітектуру. Це означає, що
-мають бути початкові коди шаблона для вказаної архітектури.
+Використовувати для образу-результату вказану архітектуру. Це означає, що мають бути початкові коди шаблона для вказаної архітектури.
Див. також L</АРХІТЕКТУРА>.
=item B<--attach> ФАЙЛ_ISO
-Під час етапу налаштовування вказаний диск долучається до базової системи
-libguestfs. Цей диск використовується для отримання даних додаткових сховищ
-програмного забезпечення або інших даних для створення нетипової системи.
+Під час етапу налаштовування вказаний диск долучається до базової системи libguestfs. Цей диск використовується для отримання даних додаткових сховищ програмного забезпечення або інших даних для створення нетипової системи.
-Ймовірно, вам варто додати мітки для долучених дисків (або скористатися
-назвою тому ISO), щоб надалі монтувати диски за міткою у ваших скриптах
-запуску:
+Ймовірно, вам варто додати мітки для долучених дисків (або скористатися назвою тому ISO), щоб надалі монтувати диски за міткою у ваших скриптах запуску:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
-Параметр I<--attach> можна вказати декілька разів, а форматом може бути
-будь-який формат образу (не лише ISO).
+Параметр I<--attach> можна вказати декілька разів, а форматом може бути будь-який формат образу (не лише ISO).
-Див. також I<--run>, L</Встановлення пакунків зі стороннього сховища під час
-збирання>, L<genisoimage(1)>, L<virt-make-fs(1)>.
+Див. також I<--run>, L</Встановлення пакунків зі стороннього сховища під час збирання>, L<genisoimage(1)>, L<virt-make-fs(1)>.
=item B<--attach-format> ФОРМАТ
-Вказати формат диска для наступного параметра I<--attach>. Значенням
-аргументу C<ФОРМАТ> зазвичай є C<raw> або C<qcow2>. Для образів ISO
-скористайтеся варіантом C<raw>.
+Вказати формат диска для наступного параметра I<--attach>. Значенням аргументу C<ФОРМАТ> зазвичай є C<raw> або C<qcow2>. Для образів ISO скористайтеся варіантом C<raw>.
=item B<--cache> КАТАЛОГ
=item B<--no-cache>
-I<--cache> КАТАЛОГ встановлює каталог зберігання і пошуку файлів кешованих
-шаблонів. Якщо значення не встановлено, типовим значенням буде
-F<$XDG_CACHE_HOME/virt-builder/> або F<$HOME/.cache/virt-builder/>.
+I<--cache> КАТАЛОГ встановлює каталог зберігання і пошуку файлів кешованих шаблонів. Якщо значення не встановлено, типовим значенням буде F<$XDG_CACHE_HOME/virt-builder/> або F<$HOME/.cache/virt-builder/>.
I<--no-cache> вимикає кешування шаблонів.
Отримати усі шаблони до кешу і завершити роботу. Див. L</КЕШУВАННЯ>.
-Зауважте, що кешуються не усі дані. Можна вивантажити додаткові
-шаблони. Крім того, не кешуються пакунки (параметри I<--install>,
-I<--update>).
+Зауважте, що кешуються не усі дані. Можна вивантажити додаткові шаблони. Крім того, не кешуються пакунки (параметри I<--install>, I<--update>).
=item B<--check-signature>
=item B<--no-check-signature>
-Перевіряти чи не перевіряти цифровий підпис шаблону операційної
-системи. Типово, програма перевіряє підпис і завершує роботу, якщо підпис не
-збігається із еталонним. Обійти цю перевірку можна за допомогою параметра
-I<--no-check-signature>.
+Перевіряти чи не перевіряти цифровий підпис шаблону операційної системи. Типово, програма перевіряє підпис і завершує роботу, якщо підпис не збігається із еталонним. Обійти цю перевірку можна за допомогою параметра I<--no-check-signature>.
Див. також I<--fingerprint>.
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<--curl> CURL
-Вказати альтернативний виконуваний файл L<curl(1)>. Ви також можете
-скористатися цим параметром для додавання параметрів curl, наприклад, щоб
-вимкнути перевірку сертифікатів https:
+Вказати альтернативний виконуваний файл L<curl(1)>. Ви також можете скористатися цим параметром для додавання параметрів curl, наприклад, щоб вимкнути перевірку сертифікатів https:
virt-builder --curl "curl --insecure" [...]
=item B<--no-delete-on-failure>
-Не вилучати файл виведених даних, якщо під час збирання станеться
-помилка. Даними з цього файла можна скористатися для діагностування причин
-помилки. Див. L</ДІАГНОСТИЧНІ ЗБІРКИ>, щоб дізнатися більше про діагностику
-образів.
+Не вилучати файл виведених даних, якщо під час збирання станеться помилка. Даними з цього файла можна скористатися для діагностування причин помилки. Див. L</ДІАГНОСТИЧНІ ЗБІРКИ>, щоб дізнатися більше про діагностику образів.
-Типовою є поведінка, коли файл результатів буде вилучено, якщо станеться
-помилка у virt-builder (або, наприклад, помилка у одному зі скриптів, які
-запускає ця програма).
+Типовою є поведінка, коли файл результатів буде вилучено, якщо станеться помилка у virt-builder (або, наприклад, помилка у одному зі скриптів, які запускає ця програма).
=item B<--fingerprint> 'AAAA BBBB ...'
-Перевірка того, що покажчик та шаблони підписано ключем із вказаним
-відбитком (Відбитком, зазвичай, є доволі довгий рядок, що складається з 10
-груп 4 шістнадцяткових цифр).
+Перевірка того, що покажчик та шаблони підписано ключем із вказаним відбитком (Відбитком, зазвичай, є доволі довгий рядок, що складається з 10 груп 4 шістнадцяткових цифр).
-Ви можете скористатися цим параметром декілька разів. Якщо у вас декілька
-адрес початкового коду, у вас або не буде відбитка, або буде один відбиток
-або буде декілька відбитків. Якщо відбитків декілька, вам слід вказати для
-кожного адресу початкового коду.
+Ви можете скористатися цим параметром декілька разів. Якщо у вас декілька адрес початкового коду, у вас або не буде відбитка, або буде один відбиток або буде декілька відбитків. Якщо відбитків декілька, вам слід вказати для кожного адресу початкового коду.
=item B<--format> qcow2
=item B<--format> raw
-Для звичайних процедур збирання визначає формат виведення даних. Типовим
-значенням є I<raw>.
+Для звичайних процедур збирання визначає формат виведення даних. Типовим значенням є I<raw>.
З I<--get-kernel> визначає формат вхідних даних.
-Для створення файла qcow2 у застарілому стилі (для сумісності з RHEL 6 або
-дуже старим qemu E<lt> 1.1) після виконання програми virt-builder
-скористайтеся такою командою:
+Для створення файла qcow2 у застарілому стилі (для сумісності з RHEL 6 або дуже старим qemu E<lt> 1.1) після виконання програми virt-builder скористайтеся такою командою:
qemu-img amend -f qcow2 -o compat=0.10 output.qcow2
=item B<--get-kernel> ОБРАЗ
-За допомогою цього параметра можна видобути ядро і initramfs з раніше
-зібраного образу диска із назвою C<ОБРАЗ> (фактично, це працює для
-будь-якого образу диска віртуальної машини, не лише для образів, які зібрано
-за допомогою virt-builder).
+За допомогою цього параметра можна видобути ядро і initramfs з раніше зібраного образу диска із назвою C<ОБРАЗ> (фактично, це працює для будь-якого образу диска віртуальної машини, не лише для образів, які зібрано за допомогою virt-builder).
-Зауважте, що цей метод є B<застарілим>: для виконання цього завдання є
-окрема програма, L<virt-get-kernel(1)>, у якій передбачено більше варіантів
-видобування файлів.
+Зауважте, що цей метод є B<застарілим>: для виконання цього завдання є окрема програма, L<virt-get-kernel(1)>, у якій передбачено більше варіантів видобування файлів.
-Ядро і initramfs буде записано до поточного каталогу, якщо ви не вкажете
-додатково назву каталогу результатів за допомогою параметра I<--output>
-C<каталог результатівr>.
+Ядро і initramfs буде записано до поточного каталогу, якщо ви не вкажете додатково назву каталогу результатів за допомогою параметра I<--output> C<каталог результатівr>.
-Формат образу диска буде визначено автоматично, якщо ви не вкажете його за
-допомогою параметра I<--format>.
+Формат образу диска буде визначено автоматично, якщо ви не вкажете його за допомогою параметра I<--format>.
-Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим
-номером. Щоб видобути із образу диска ядро з певним номером версії,
-скористайтеся L<guestfish(1)>. Щоб видобути із гостьової системи увесь вміст
-каталогу F</boot>, скористайтеся L<virt-copy-out(1)>.
+Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим номером. Щоб видобути із образу диска ядро з певним номером версії, скористайтеся L<guestfish(1)>. Щоб видобути із гостьової системи увесь вміст каталогу F</boot>, скористайтеся L<virt-copy-out(1)>.
=item B<--gpg> GPG
-Вказати альтернативний виконуваний файл L<gpg(1)> (GNU Privacy
-Guard). Типово, virt-builder шукає C<gpg2> або C<gpg> у каталогах, вказаних
-за допомогою змінної C<$PATH>.
+Вказати альтернативний виконуваний файл L<gpg(1)> (GNU Privacy Guard). Типово, virt-builder шукає C<gpg2> або C<gpg> у каталогах, вказаних за допомогою змінної C<$PATH>.
-Ви можете скористатися цим параметром для додавання параметрів до основної
-програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
+Ви можете скористатися цим параметром для додавання параметрів до основної програми gpg, наприклад, для визначення альтернативного домашнього каталогу:
virt-builder --gpg "gpg --homedir /tmp" [...]
=item B<--list> B<--long> [версія ОС]
-Вивести усі доступні шаблони, якщо не вказано гостьової системи, або вивести
-шаблони лише для вказаної гостьової системи.
+Вивести усі доступні шаблони, якщо не вказано гостьової системи, або вивести шаблони лише для вказаної гостьової системи.
-Ви можете вибрати формат виведення за допомогою параметра I<--list-format>
-для шаблонів списку:
+Ви можете вибрати формат виведення за допомогою параметра I<--list-format> для шаблонів списку:
=over 4
=item B<short>
-Типовий формат: виводиться лише ідентифікатор шаблона і, поряд з ним, його
-короткий опис.
+Типовий формат: виводиться лише ідентифікатор шаблона і, поряд з ним, його короткий опис.
=item B<long>
-Виводить тестовий список із даними щодо доступних джерел і список даних щодо
-доступних шаблонів після нього.
+Виводить тестовий список із даними щодо доступних джерел і список даних щодо доступних шаблонів після нього.
=item B<json>
-Вивести об’єкт JSON із подробицями щодо доступних джерел та подробиці щодо
-доступних шаблонів.
+Вивести об’єкт JSON із подробицями щодо доступних джерел та подробиці щодо доступних шаблонів.
-Ключ C<version> у основному об'єкті визначає «версію сумісності», його
-значення слід збільшувати кожного разу, коли результат використання JSON
-ставатиме несумісним із попередніми версіями (наприклад, через зміну
-структури або прибирання основних ключів).
+Ключ C<version> у основному об'єкті визначає «версію сумісності», його значення слід збільшувати кожного разу, коли результат використання JSON ставатиме несумісним із попередніми версіями (наприклад, через зміну структури або прибирання основних ключів).
=back
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<-m> МБ
=item B<--memsize> МБ
-Зміна обсягу пам'яті, наданого скриптам I<--run>. Збільште це значення, якщо
-виявиться, що для використання скриптів I<--run> або параметра I<--install>
-не вистачає пам'яті.
+Зміна обсягу пам'яті, наданого скриптам I<--run>. Збільште це значення, якщо виявиться, що для використання скриптів I<--run> або параметра I<--install> не вистачає пам'яті.
Типові значення можна визначити за допомогою такої команди:
=item B<--no-network>
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
-Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути доступ.
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
-Якщо ви скористаєтеся параметром I<--no-network>, тоді інші параметри,
-зокрема I<--install>, не працюватимуть.
+Якщо ви скористаєтеся параметром I<--no-network>, тоді інші параметри, зокрема I<--install>, не працюватимуть.
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-builder.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-builder.
-Загалом кажучи, вам I<не варто> використовувати I<--no-network>. Але ось
-декілька випадків, коли у вас може виникнути потреба у використанні цього
-параметра:
+Загалом кажучи, вам I<не варто> використовувати I<--no-network>. Але ось декілька випадків, коли у вас може виникнути потреба у використанні цього параметра:
=over 4
=item 1.
-У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки
-мережі. (Див. L<guestfs(3)/МОДУЛЬ>).
+У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки мережі. (Див. L<guestfs(3)/МОДУЛЬ>).
=item 2.
-Усе програмне забезпечення, яке ви маєте намір встановити, походить з
-долученого образу ISO, отже потреби у мережі немає.
+Усе програмне забезпечення, яке ви маєте намір встановити, походить з долученого образу ISO, отже потреби у мережі немає.
=item 3.
-Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати
-доступ до мережевого з'єднання вашої основної системи під час роботи
-virt-builder. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу
-шаблонів операційних систем. (Див. L</БЕЗПЕКА> нижче).
+Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати доступ до мережевого з'єднання вашої основної системи під час роботи virt-builder. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу шаблонів операційних систем. (Див. L</БЕЗПЕКА> нижче).
=item 4.
-Ви не хочете користуватися мережею основної системи (наприклад, через
-захищеність або обмеженість середовища у ній).
+Ви не хочете користуватися мережею основної системи (наприклад, через захищеність або обмеженість середовища у ній).
=back
Не синхронізувати файл виведення під час завершення роботи.
-Virt-builder виконує синхронізацію C<fsync> файла результатів або образу
-диска, якщо такий існує.
+Virt-builder виконує синхронізацію C<fsync> файла результатів або образу диска, якщо такий існує.
-Причина полягає у тому, що типовим режимом кешування у qemu та KVM є C<none>
-або C<directsync>, і у обох цих режимах не використовується кеш сторінок
-основної системи. Тому ці режими не працюватимуть належним чином, якщо ви
-негайно запустите гостьову систему після запуску virt-builder — гостьова
-система просто не побачить файл результатів повністю . (Зауважте, що вам не
-варто користуватися обома цими режимами кешування — вони непрацездатні на
-базовому рівні з цієї та інших причин.)
+Причина полягає у тому, що типовим режимом кешування у qemu та KVM є C<none> або C<directsync>, і у обох цих режимах не використовується кеш сторінок основної системи. Тому ці режими не працюватимуть належним чином, якщо ви негайно запустите гостьову систему після запуску virt-builder — гостьова система просто не побачить файл результатів повністю . (Зауважте, що вам не варто користуватися обома цими режимами кешування — вони непрацездатні на базовому рівні з цієї та інших причин.)
-Якщо ви не використовуєте ці помилкові режими кешування, ви можете
-скористатися параметром I<--no-sync>, щоб усунути непотрібну синхронізацію і
-значно пришвидшити роботу програми.
+Якщо ви не використовуєте ці помилкові режими кешування, ви можете скористатися параметром I<--no-sync>, щоб усунути непотрібну синхронізацію і значно пришвидшити роботу програми.
=item B<--notes> версія-ОС
-Показує список нотаток, пов’язаних із гостьовою системою, потім завершує
-роботу (встановлення не виконується).
+Показує список нотаток, пов’язаних із гостьовою системою, потім завершує роботу (встановлення не виконується).
=item B<-o> назва_файла
=item B<--output> назва_файла
-Записати виведені дані до файла F<назва_файла>. Якщо цей параметр не буде
-вказано, назву файла для виведення даних буде створено на основі рядка
-C<версія-ос> із додаванням суфікса C<.img> (для формату без обробки) або
-C<.qcow2> (для формату qcow2).
+Записати виведені дані до файла F<назва_файла>. Якщо цей параметр не буде вказано, назву файла для виведення даних буде створено на основі рядка C<версія-ос> із додаванням суфікса C<.img> (для формату без обробки) або C<.qcow2> (для формату qcow2).
-Зауважте, що назвою файла виведення результатів може бути пристрій, розділ
-або логічний том.
+Зауважте, що назвою файла виведення результатів може бути пристрій, розділ або логічний том.
-Якщо використовується з I<--get-kernel>, цей параметр задає каталог
-виведення даних.
+Якщо використовується з I<--get-kernel>, цей параметр задає каталог виведення даних.
=item B<--print-cache>
=item B<--size> РОЗМІР
-Вибір розміру диска-результату, де розмір можна вказати за допомогою типових
-записів, зокрема C<32G> (32 гігабайти) тощо.
+Вибір розміру диска-результату, де розмір можна вказати за допомогою типових записів, зокрема C<32G> (32 гігабайти) тощо.
Virt-builder змінить розміри файлових систем у образі диска автоматично.
-Якщо розмір не задано, можлива реалізація двох сценаріїв. Якщо дані
-виводяться до файла, його розмір буде таким самим, як у шаблона. Якщо дані
-виводяться на пристрій, розділ тощо, буде використано розмір відповідного
-пристрою.
+Якщо розмір не задано, можлива реалізація двох сценаріїв. Якщо дані виводяться до файла, його розмір буде таким самим, як у шаблона. Якщо дані виводяться на пристрій, розділ тощо, буде використано розмір відповідного пристрою.
-Щоб вказати розмір у байтах, додайте до числа малу літеру I<b>, наприклад
-S<C<--size 10737418240b>>.
+Щоб вказати розмір у байтах, додайте до числа малу літеру I<b>, наприклад S<C<--size 10737418240b>>.
=item B<--smp> N
-Увімкнути N E<ge> 2 віртуальних процесорів для використання у скриптах
-I<--run>.
+Увімкнути N E<ge> 2 віртуальних процесорів для використання у скриптах I<--run>.
=item B<--source> АДРЕСА
Див. також L</ДЖЕРЕЛА ШАБЛОНІВ> нижче.
-Зауважте, що не варто вказувати для I<--source> джерела, яким ви не
-довіряєте (якщо їх не підписано кимось, кому ви довіряєте). Див. також
-параметр I<--no-network>.
+Зауважте, що не варто вказувати для I<--source> джерела, яким ви не довіряєте (якщо їх не підписано кимось, кому ви довіряєте). Див. також параметр I<--no-network>.
=item B<--no-warn-if-partition>
-Не видавати попередження, якщо пристроєм виведення даних є розділ. Це
-попередження надає змогу уникнути типової помилки користувача під час
-записування на флеш-накопичувач USB або зовнішній диск — запису на розділ,
-коли слід виконувати перезапис усього пристрою (S<I<--output /dev/sdX>>), а
-не розділу на ньому (S<I<--output /dev/sdX1>>). Скористайтеся цим
-параметром, щоб I<придушити> відповідне попередження.
+Не видавати попередження, якщо пристроєм виведення даних є розділ. Це попередження надає змогу уникнути типової помилки користувача під час записування на флеш-накопичувач USB або зовнішній диск — запису на розділ, коли слід виконувати перезапис усього пристрою (S<I<--output /dev/sdX>>), а не розділу на ньому (S<I<--output /dev/sdX1>>). Скористайтеся цим параметром, щоб I<придушити> відповідне попередження.
=item B<-v>
Увімкнути діагностичні повідомлення і/або режим докладних повідомлень.
-Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі
-виведені дані до звіту щодо вади.
+Коли повідомлятимете про вади, скористайтеся цим параметром і долучіть усі виведені дані до звіту щодо вади.
=item B<-V>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head2 ВСТАНОВЛЕННЯ ПАКУНКІВ
-Існує декілька підходів до встановлення пакунків або програм у гостьовій
-системі, використання кожного з яких має власні переваги і недоліки.
+Існує декілька підходів до встановлення пакунків або програм у гостьовій системі, використання кожного з яких має власні переваги і недоліки.
=head3 Встановлення пакунків під час збирання
-Якщо гостьова операційна система є подібною до основної операційної системи
-(наприклад, обидві є операційними системами Linux), і у libguestfs
-передбачено підтримку з'єднань мережею, ви можете скористатися параметром
-I<--install> для встановлення пакунків у такий спосіб:
+Якщо гостьова операційна система є подібною до основної операційної системи (наприклад, обидві є операційними системами Linux), і у libguestfs передбачено підтримку з'єднань мережею, ви можете скористатися параметром I<--install> для встановлення пакунків у такий спосіб:
virt-builder fedora-27 --install inkscape
-Тут використано засіб керування пакунками гостьової системи і з'єднання із
-мережею основної системи.
+Тут використано засіб керування пакунками гостьової системи і з'єднання із мережею основної системи.
=head3 Оновлення пакунків під час збирання
-Щоб оновити встановлений набір пакунків у шаблоні під час збирання, віддайте
-таку команду:
+Щоб оновити встановлений набір пакунків у шаблоні під час збирання, віддайте таку команду:
virt-builder fedora-27 --update
-У більшості шаблонів, які постачаються разом із virt-builder, передбачено
-дуже вузький набір пакунків (відомий як «JEOS» або «Just Enough Operating
-System» («Достатньо для того, щоб бути операційною системою»), які є
-актуальними на час створення шаблону, але можу виявитися застарілими на час,
-коли ви встановлюватимете операційну систему з шаблона. За допомогою цього
-параметра можна оновити пакунки з шаблона.
+У більшості шаблонів, які постачаються разом із virt-builder, передбачено дуже вузький набір пакунків (відомий як «JEOS» або «Just Enough Operating System» («Достатньо для того, щоб бути операційною системою»), які є актуальними на час створення шаблону, але можу виявитися застарілими на час, коли ви встановлюватимете операційну систему з шаблона. За допомогою цього параметра можна оновити пакунки з шаблона.
=head3 Встановлення пакунків під час першого завантаження
-Іншим варіантом є встановлення пакунків під час першого завантаження
-гостьової системи:
+Іншим варіантом є встановлення пакунків під час першого завантаження гостьової системи:
virt-builder fedora-27 --firstboot-install inkscape
-Тут використано засіб керування пакунками гостьової системи і з'єднання із
-мережею гостьової системи.
+Тут використано засіб керування пакунками гостьової системи і з'єднання із мережею гостьової системи.
-Недоліком використання цього підходу є те, що гостьова система
-завантажуватиметься вперше набагато довше, а також те, що ви не зможете
-нічого зробити, якщо під час встановлення пакунків станеться помилка
-(наприклад, через проблеми із мережею гостьова система не зможе встановити
-зв'язок зі сховищем пакунків).
+Недоліком використання цього підходу є те, що гостьова система завантажуватиметься вперше набагато довше, а також те, що ви не зможете нічого зробити, якщо під час встановлення пакунків станеться помилка (наприклад, через проблеми із мережею гостьова система не зможе встановити зв'язок зі сховищем пакунків).
=head3 Встановлення пакунків зі стороннього сховища під час збирання
-Якщо програмного забезпечення, яке ви хочете встановити, немає у основному
-сховищі пакунків гостьової системи, ви можете додати стороннє
-сховище. Зазвичай, таке сховище є файлом образу ISO (образом компакт-диска),
-у якому містяться дані додаткових пакунків.
+Якщо програмного забезпечення, яке ви хочете встановити, немає у основному сховищі пакунків гостьової системи, ви можете додати стороннє сховище. Зазвичай, таке сховище є файлом образу ISO (образом компакт-диска), у якому містяться дані додаткових пакунків.
-Ви можете створити образ диска за допомогою L<genisoimage(1)> або
-L<virt-make-fs(1)>. Для genisoimage скористайтеся такою командою:
+Ви можете створити образ диска за допомогою L<genisoimage(1)> або L<virt-make-fs(1)>. Для genisoimage скористайтеся такою командою:
genisoimage -o extra-packages.iso -R -J -V EXTRA cdcontents/
-Створіть скрипт, який монтує ISO і налаштовує сховище. Для dnf створіть
-/tmp/install.sh з таким вмістом:
+Створіть скрипт, який монтує ISO і налаштовує сховище. Для dnf створіть /tmp/install.sh з таким вмістом:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
apt-cdrom -d=/tmp/mount add
apt-get -y install famousdatabase
-Скористайтеся параметром I<--attach> для долучення компакт-диска або образу
-диска та параметром I<--run> для запуску скрипту:
+Скористайтеся параметром I<--attach> для долучення компакт-диска або образу диска та параметром I<--run> для запуску скрипту:
virt-builder fedora-27 \
--attach extra-packages.iso \
=head2 КОРИСТУВАЧІ І ПАРОЛІ
-Параметр I<--root-password> використовується для зміни пароля адміністратора
-(root) (якщо ви не скористаєтеся цим параметром, буде використано випадковий
-пароль). Цьому параметру можна передати C<ВАРІАНТ> пароля у одному з таких
-форматів:
+Параметр I<--root-password> використовується для зміни пароля адміністратора (root) (якщо ви не скористаєтеся цим параметром, буде використано випадковий пароль). Цьому параметру можна передати C<ВАРІАНТ> пароля у одному з таких форматів:
=over 4
=item B<--root-password> file:НАЗВА_ФАЙЛА
-Прочитати пароль адміністратора з файла C<НАЗВА_ФАЙЛА>. Паролем
-вважатиметься вміст усього першого рядка цього файла. Усі інші рядки файла
-буде проігноровано. Файл має бути створено із режимом доступу 0600, щоб його
-не могли читати сторонні користувачі.
+Прочитати пароль адміністратора з файла C<НАЗВА_ФАЙЛА>. Паролем вважатиметься вміст усього першого рядка цього файла. Усі інші рядки файла буде проігноровано. Файл має бути створено із режимом доступу 0600, щоб його не могли читати сторонні користувачі.
=item B<--root-password> password:ПАРОЛЬ
Встановити для пароля root буквальне значення рядка C<ПАРОЛЬ>.
-B<Зауваження: цей спосіб не є безпечним>, оскільки будь-який користувач
-комп'ютера зможе побачити пароль явним чином за допомогою команди L<ps(1)>.
+B<Зауваження: цей спосіб не є безпечним>, оскільки будь-який користувач комп'ютера зможе побачити пароль явним чином за допомогою команди L<ps(1)>.
=item B<--root-password> random
-Вибрати випадковий пароль, який буде виведено до stdout. Випадковість пароля
-наближено відповідатиме 120-бітовій.
+Вибрати випадковий пароль, який буде виведено до stdout. Випадковість пароля наближено відповідатиме 120-бітовій.
Типове значення.
=item B<--root-password> disabled
-Пароль для облікового запису root вимкнено. Це так, ніби у полі пароля
-використано C<*>.
+Пароль для облікового запису root вимкнено. Це так, ніби у полі пароля використано C<*>.
=item B<--root-password> locked:file:НАЗВА_ФАЙЛА
=item B<--root-password> locked:random
-Обліковий запис root заблоковано, але для нього визначено пароль. Якщо
-обліковий запис буде вперше розблоковано (за допомогою C<passwd -u>), для
-входу до нього буде використано вказаний пароль.
+Обліковий запис root заблоковано, але для нього визначено пароль. Якщо обліковий запис буде вперше розблоковано (за допомогою C<passwd -u>), для входу до нього буде використано вказаний пароль.
=item B<--root-password> locked
=head3 Створення облікових записів користувачів
-Для створення облікових записів користувачів скористайтеся командою
-L<useradd(8)> з параметром L<--firstboot-command>, ось так:
+Для створення облікових записів користувачів скористайтеся командою L<useradd(8)> з параметром L<--firstboot-command>, ось так:
virt-builder --firstboot-command \
'useradd -m -p "" rjones ; chage -d 0 rjones'
-Вказана вище команда створить обліковий запис C<rjones> без пароля і
-примусить користувача встановити пароль під час першого входу до
-системи. Існують і інші способи керування паролями, див. L<useradd(8)>, щоб
-дізнатися більше.
+Вказана вище команда створить обліковий запис C<rjones> без пароля і примусить користувача встановити пароль під час першого входу до системи. Існують і інші способи керування паролями, див. L<useradd(8)>, щоб дізнатися більше.
=head2 РОЗКЛАДКА КЛАВІАТУРИ
-Оскільки існує багато різних способів встановити розкладку клавіатури у
-дистрибутивах Linux, у virt-builder усе ще немає простого параметра
-командного рядка для виконання цієї дії. У цьому розділі наведено настанови
-щодо встановлення розкладки для деяких типових дистрибутивів Linux.
+Оскільки існує багато різних способів встановити розкладку клавіатури у дистрибутивах Linux, у virt-builder усе ще немає простого параметра командного рядка для виконання цієї дії. У цьому розділі наведено настанови щодо встановлення розкладки для деяких типових дистрибутивів Linux.
=head3 Визначення розкладки клавіатури за допомогою systemd
-У дистрибутивах, де використовується C<localectl> зі складу systemd,
-скористайтеся такою командою:
+У дистрибутивах, де використовується C<localectl> зі складу systemd, скористайтеся такою командою:
virt-builder fedora-27 \
--firstboot-command 'localectl set-keymap uk'
-Докладніший опис можна знайти за посиланнями L<localectl(1)> та
-L<https://www.happyassassin.net/2013/11/23/keyboard-layouts-in-fedora-20-and-previously/>.
+Докладніший опис можна знайти за посиланнями L<localectl(1)> та L<https://www.happyassassin.net/2013/11/23/keyboard-layouts-in-fedora-20-and-previously/>.
=head3 Визначення розкладки клавіатури за допомогою F</etc/sysconfig/keyboard>
-Для RHEL E<le> 6, Fedora E<le> 18 та подібних систем можна вивантажити із
-змінити файл налаштувань клавіатури за допомогою параметрів I<--upload>,
-I<--write> або I<--edit>. Приклад:
+Для RHEL E<le> 6, Fedora E<le> 18 та подібних систем можна вивантажити із змінити файл налаштувань клавіатури за допомогою параметрів I<--upload>, I<--write> або I<--edit>. Приклад:
virt-builder centos-6 \
--edit '/etc/sysconfig/keyboard: s/^KEYTABLE=.*/KEYTABLE="uk"/'
-Документацію щодо формату даних цього файла можна знайти на багатьох
-сторінках інтернету.
+Документацію щодо формату даних цього файла можна знайти на багатьох сторінках інтернету.
=head3 Визначення розкладки клавіатури у дистрибутивах на основі Debian
-У заснованих на Debian дистрибутивах мети можна досягти за допомогою файла
-F</etc/default/keyboard>. Вивантажити або внести зміни до цього файла можна
-за допомогою параметрів I<--upload>, I<--write> та I<--edit>. Приклад:
+У заснованих на Debian дистрибутивах мети можна досягти за допомогою файла F</etc/default/keyboard>. Вивантажити або внести зміни до цього файла можна за допомогою параметрів I<--upload>, I<--write> та I<--edit>. Приклад:
virt-builder debian-8 \
--edit '/etc/default/keyboard: s/^XKBLAYOUT=.*/XKBLAYOUT="gb"/'
=head2 МОВА
-У більшості дистрибутивів Linux передбачено можливість зміни локалі, отже ви
-можете бачити повідомлення гостьової системи нестандартною мовою, наприклад
-українською.
+У більшості дистрибутивів Linux передбачено можливість зміни локалі, отже ви можете бачити повідомлення гостьової системи нестандартною мовою, наприклад українською.
-Втім, єдиного параметра, який контролює локаль, немає, оскільки для
-реалізації підтримки мови може знадобитися встановлення додаткових пакунків,
-зокрема шрифтів для консолі і графічної оболонки, способів введення символів
-запису мови з клавіатури. Назви потрібних для цього пакунків та їхні
-налаштування залежать від дистрибутиву, отже, virt-builder просто не може
-про них знати.
+Втім, єдиного параметра, який контролює локаль, немає, оскільки для реалізації підтримки мови може знадобитися встановлення додаткових пакунків, зокрема шрифтів для консолі і графічної оболонки, способів введення символів запису мови з клавіатури. Назви потрібних для цього пакунків та їхні налаштування залежать від дистрибутиву, отже, virt-builder просто не може про них знати.
У цьому розділі наведено приклади для типових дистрибутивів Linux.
=head3 Встановлення японської мови для Debian 8 (Jessie)
-Зауважте, що, хоча вказана команда вмикає японську і у текстовій консолі,
-навряд чи у консолі ви побачите належним чином показані ієрогліфи. Втім,
-японські ієрогліфи має бути показано у графічних програмах і терміналах.
+Зауважте, що, хоча вказана команда вмикає японську і у текстовій консолі, навряд чи у консолі ви побачите належним чином показані ієрогліфи. Втім, японські ієрогліфи має бути показано у графічних програмах і терміналах.
pkgs=locales,xfce4,\
ibus,ibus-anthy,\
=head2 ФАЙЛ ЖУРНАЛУ
-Скрипти та засоби встановлення пакунків, які працюватимуть під час збирання
-(I<--run>, I<--run-command>, I<--install>, I<--update>, але I<не>
-firstboot), записуватимуть повідомлення до одного з таких файлів:
+Скрипти та засоби встановлення пакунків, які працюватимуть під час збирання (I<--run>, I<--run-command>, I<--install>, I<--update>, але I<не> firstboot), записуватимуть повідомлення до одного з таких файлів:
=over 4
=back
-Якщо ви не хочете, щоб до остаточного образу було записано файл журналу,
-скористайтеся параметром рядка команди I<--no-logfile>.
+Якщо ви не хочете, щоб до остаточного образу було записано файл журналу, скористайтеся параметром рядка команди I<--no-logfile>.
=head2 КЛЮЧІ SSH
-Параметр I<--ssh-inject> використовується для вставляння ключів ssh для
-користувачів у гостьовій системі, щоб вони могли входити до системи без
-зазначення пароля.
+Параметр I<--ssh-inject> використовується для вставляння ключів ssh для користувачів у гостьовій системі, щоб вони могли входити до системи без зазначення пароля.
-Частина C<ВАРІАНТ> параметра є необов'язковою; у нашому випадку
-I<--ssh-inject> C<КОРИСТУВАЧ> означає, що ми шукаємо F<~/.ssh> у каталозі
-I<поточного> користувача для визначення типового файла відкритого
-ідентифікатора. Саме знайдений ключ і буде вивантажено до гостьової
-системи. «Типовий відкритий ідентифікатор» є файлом I<default_ID_file>, який
-описано у підручнику з L<ssh-copy-id(1)>.
+Частина C<ВАРІАНТ> параметра є необов'язковою; у нашому випадку I<--ssh-inject> C<КОРИСТУВАЧ> означає, що ми шукаємо F<~/.ssh> у каталозі I<поточного> користувача для визначення типового файла відкритого ідентифікатора. Саме знайдений ключ і буде вивантажено до гостьової системи. «Типовий відкритий ідентифікатор» є файлом I<default_ID_file>, який описано у підручнику з L<ssh-copy-id(1)>.
Якщо вказано, C<ВАРІАНТ> можна зазначити у одному з таких форматів:
=item B<--ssh-inject> КОРИСТУВАЧ:string:РЯДОК_КЛЮЧА
-Використати вказаний C<РЯДОК_КЛЮЧА>. Зазвичай, C<РЯДОК_КЛЮЧА> — рядок
-відкритого ключа у форматі I<ssh-rsa AAAA.... user@localhost>.
+Використати вказаний C<РЯДОК_КЛЮЧА>. Зазвичай, C<РЯДОК_КЛЮЧА> — рядок відкритого ключа у форматі I<ssh-rsa AAAA.... user@localhost>.
=back
-Який би з варіантів не було вибрано, буде створено каталог F<~USER/.ssh> і
-файл F<~USER/.ssh/authorized_keys>, якщо вони досі не існували.
+Який би з варіантів не було вибрано, буде створено каталог F<~USER/.ssh> і файл F<~USER/.ssh/authorized_keys>, якщо вони досі не існували.
=head2 СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ
-За допомогою параметрів I<--firstboot> та I<--firstboot-command> ви можете
-визначити команди, які буде виконано під час першого завантаження гостьової
-системи. Для цього у гостьовій системі встановлюється скрипт ініціалізації,
-який виконує завдання із запуску усіх доданих скриптів і виконання усіх
-доданих команд.
+За допомогою параметрів I<--firstboot> та I<--firstboot-command> ви можете визначити команди, які буде виконано під час першого завантаження гостьової системи. Для цього у гостьовій системі встановлюється скрипт ініціалізації, який виконує завдання із запуску усіх доданих скриптів і виконання усіх доданих команд.
Підтримувані операційні системи:
=item Linux
-Передбачено підтримку таких систем ініціалізації: systemd, System-V init
-(також відома як sysvinit) та Upstart (з використанням скриптів System-V).
+Передбачено підтримку таких систем ініціалізації: systemd, System-V init (також відома як sysvinit) та Upstart (з використанням скриптів System-V).
-Зауважте, що, зазвичай, скрипти ініціалізації виконуються від імені
-адміністратора (root), але у набагато обмеженішому середовищі ніж те, яке
-доступне зі звичайної оболонки. Наприклад, значення змінної середовища
-C<$HOME> може бути не встановленим або порожнім.
+Зауважте, що, зазвичай, скрипти ініціалізації виконуються від імені адміністратора (root), але у набагато обмеженішому середовищі ніж те, яке доступне зі звичайної оболонки. Наприклад, значення змінної середовища C<$HOME> може бути не встановленим або порожнім.
-Дані, виведені скриптами першого запуску, у гостьовій системі
-зберігатимуться у F<~root/virt-sysprep-firstboot.log>.
+Дані, виведені скриптами першого запуску, у гостьовій системі зберігатимуться у F<~root/virt-sysprep-firstboot.log>.
=item Windows
-Для запуску скриптів першого завантаження встановлюється F<rhsrvany.exe>,
-початковий код якого можна знайти у L<https://github.com/rwmjones/rhsrvany>,
-або F<pvvxsvc.exe>, який є частиною SUSE VMDP. Наявність цих файлів є
-обов'язковою. Якщо файлів не буде знайдено, скрипти першого завантаження
-виконати не вдасться.
+Для запуску скриптів першого завантаження встановлюється F<rhsrvany.exe>, початковий код якого можна знайти у L<https://github.com/rwmjones/rhsrvany>, або F<pvvxsvc.exe>, який є частиною SUSE VMDP. Наявність цих файлів є обов'язковою. Якщо файлів не буде знайдено, скрипти першого завантаження виконати не вдасться.
-F<rhsrvany.exe> або F<pvvxsvc.exe> буде просто скопійовано з місця, на яке
-вказує змінна середовища C<VIRT_TOOLS_DATA_DIR>; якщо значення змінної
-середовища не встановлено, буде використано типове місце, визначене під час
-компіляції (щось схоже на F</usr/share/virt-tools>).
+F<rhsrvany.exe> або F<pvvxsvc.exe> буде просто скопійовано з місця, на яке вказує змінна середовища C<VIRT_TOOLS_DATA_DIR>; якщо значення змінної середовища не встановлено, буде використано типове місце, визначене під час компіляції (щось схоже на F</usr/share/virt-tools>).
-Дані, виведені скриптами першого завантаження, можна знайти у гостьовій
-системі за адресою F<C:\Program Files\Guestfs\Firstboot\log.txt>.
+Дані, виведені скриптами першого завантаження, можна знайти у гостьовій системі за адресою F<C:\Program Files\Guestfs\Firstboot\log.txt>.
=back
=head2 SUBSCRIPTION-MANAGER
-Передбачено можливість автоматизації реєстрації та долучення до системи
-передплат за допомогою C<subscription-manager>. Потреба у подібному
-налаштовуванні типово виникає у системах Red Hat Enterprise
-Linux. Передбачено декілька параметрів, які спрощують процедуру, усувають
-потребу у введенні команд вручну та не роблять загальнодоступними паролі,
-вказані у рядку команди.
+Передбачено можливість автоматизації реєстрації та долучення до системи передплат за допомогою C<subscription-manager>. Потреба у подібному налаштовуванні типово виникає у системах Red Hat Enterprise Linux. Передбачено декілька параметрів, які спрощують процедуру, усувають потребу у введенні команд вручну та не роблять загальнодоступними паролі, вказані у рядку команди.
-I<--sm-register> запускає процедуру реєстрації і потребує зазначення
-I<--sm-credentials>. Слід використовувати для параметра C<ВАРІАНТ>
-I<--sm-credentials> один з таких форматів:
+I<--sm-register> запускає процедуру реєстрації і потребує зазначення I<--sm-credentials>. Слід використовувати для параметра C<ВАРІАНТ> I<--sm-credentials> один з таких форматів:
=over 4
=item B<--sm-credentials> КОРИСТУВАЧ:file:НАЗВА_ФАЙЛА
-Прочитати пароль для вказаного користувача C<КОРИСТУВАЧ> з файла
-F<НАЗВА_ФАЙЛА>.
+Прочитати пароль для вказаного користувача C<КОРИСТУВАЧ> з файла F<НАЗВА_ФАЙЛА>.
=item B<--sm-credentials> КОРИСТУВАЧ:password:ПАРОЛЬ
=back
-I<--sm-attach> долучає систему до передплачених послуг; формат варіантів
-команди може бути одним з таких:
+I<--sm-attach> долучає систему до передплачених послуг; формат варіантів команди може бути одним з таких:
=over 4
=item B<--sm-attach> auto
-C<subscription-manager> долучається до найвідповідніших передплат для
-системи.
+C<subscription-manager> долучається до найвідповідніших передплат для системи.
=item B<--sm-attach> file:НАЗВА_ФАЙЛА
=back
-I<--sm-remove> вилучає усі передплати з гостьової системи, а
-I<--sm-unregister> повністю знімає систему з реєстрації.
+I<--sm-remove> вилучає усі передплати з гостьової системи, а I<--sm-unregister> повністю знімає систему з реєстрації.
=head2 ПРОЦЕДУРА ВСТАНОВЛЕННЯ
Отримується образ шаблону.
-Якщо образ шаблону вже є у кеші, використовується кешована
-версія. (Див. L</КЕШУВАННЯ>).
+Якщо образ шаблону вже є у кеші, використовується кешована версія. (Див. L</КЕШУВАННЯ>).
=item *
=item *
-Розмір образ шаблону змінюється так, щоб від дорівнював розміру системи
-призначення, за допомогою L<virt-resize(1)>.
+Розмір образ шаблону змінюється так, щоб від дорівнював розміру системи призначення, за допомогою L<virt-resize(1)>.
=item *
=item *
-Виконується налаштовування гостьової системи у порядку, який задається
-рядком команди.
+Виконується налаштовування гостьової системи у порядку, який задається рядком команди.
=item *
=head3 Імпортування до libvirt
-Імпортування образу диска до libvirt за допомогою параметра
-L<virt-install(1)> I<--import>.
+Імпортування образу диска до libvirt за допомогою параметра L<virt-install(1)> I<--import>.
virt-install --import \
--name guest --ram 2048 \
=item 1.
-Вам I<слід> вказати правильний формат. Форматом є C<raw>, якщо вами не було
-використано параметр virt-builder I<--format>.
+Вам I<слід> вказати правильний формат. Форматом є C<raw>, якщо вами не було використано параметр virt-builder I<--format>.
=item 2.
-Наполегливо рекомендуємо скористатися I<--os-variant>, оскільки він надає
-змогу підібрати оптимальний набір пристроїв, які слід увімкнути у системі,
-щоб гостьова система працювала найефективніше. Щоб отримати список усіх
-варіантів, скористайтеся такою командою:
+Наполегливо рекомендуємо скористатися I<--os-variant>, оскільки він надає змогу підібрати оптимальний набір пристроїв, які слід увімкнути у системі, щоб гостьова система працювала найефективніше. Щоб отримати список усіх варіантів, скористайтеся такою командою:
osinfo-query ОС
=item 3.
-Запускати virt-install можна від імені адміністратора (root) або від імені
-простого користувача. Між цими способами є незначні відмінності, оскільки
-libvirt керує різними наборами віртуальних машин для кожного
-користувача. Зокрема, virt-manager показує віртуальні машини, власником яких
-є root, а «Коробки» з GNOME показують лише віртуальні машини поточного
-користувача. Інші ж програми можуть також мати свої особливості показу.
+Запускати virt-install можна від імені адміністратора (root) або від імені простого користувача. Між цими способами є незначні відмінності, оскільки libvirt керує різними наборами віртуальних машин для кожного користувача. Зокрема, virt-manager показує віртуальні машини, власником яких є root, а «Коробки» з GNOME показують лише віртуальні машини поточного користувача. Інші ж програми можуть також мати свої особливості показу.
=back
=head3 Імпортування до OpenStack
-Імпортувати образ до Glance (сховища образів OpenStack) можна такими
-командами:
+Імпортувати образ до Glance (сховища образів OpenStack) можна такими командами:
glance image-create --name fedora-27-image --file fedora-27.img \
--disk-format raw --container-format bare \
--is-public True
-Параметр I<--file> визначає створений за допомогою virt-builder образ
-диска. Його значення має узгоджуватися із значення параметра I<--output>
-virt-builder. Значення параметра I<--disk-format> має узгоджуватися зі
-значенням параметра I<--format> virt-builder (або бути рівним C<raw>, якщо
-ви не вказували цього параметра). Значенням параметра I<--container-format>
-завжди має бути C<bare>, оскільки virt-builder ніколи не вкладає образ до
-контейнерів.
+Параметр I<--file> визначає створений за допомогою virt-builder образ диска. Його значення має узгоджуватися із значення параметра I<--output> virt-builder. Значення параметра I<--disk-format> має узгоджуватися зі значенням параметра I<--format> virt-builder (або бути рівним C<raw>, якщо ви не вказували цього параметра). Значенням параметра I<--container-format> завжди має бути C<bare>, оскільки virt-builder ніколи не вкладає образ до контейнерів.
-Ви можете скористатися командою S<C<glance image-show I<fedora-27-image>>>,
-щоб переглянути властивості образу.
+Ви можете скористатися командою S<C<glance image-show I<fedora-27-image>>>, щоб переглянути властивості образу.
-Для завантаження екземпляра вашого образу на обчислювальному вузлі Nova
-віддайте таку команду:
+Для завантаження екземпляра вашого образу на обчислювальному вузлі Nova віддайте таку команду:
nova boot fedora-27-server --image fedora-27-image \
--flavor m1.medium
-Скористайтеся командою S<C<nova flavor-list>>, щоб переглянути список
-можливих варіантів машин. Скористайтеся командою S<C<nova list>>, щоб
-переглянути список запущених екземплярів.
+Скористайтеся командою S<C<nova flavor-list>>, щоб переглянути список можливих варіантів машин. Скористайтеся командою S<C<nova list>>, щоб переглянути список запущених екземплярів.
=head3 Безпосереднє завантаження за допомогою qemu або KVM
-Командний рядок qemu не є ні надто стабільним, ні простим у користуванні,
-тому, якщо це можливо, слід користуватися libvirt. Втім, для завантаження
-віртуальної машини можна скористатися чимось подібним до вказаного нижче:
+Командний рядок qemu не є ні надто стабільним, ні простим у користуванні, тому, якщо це можливо, слід користуватися libvirt. Втім, для завантаження віртуальної машини можна скористатися чимось подібним до вказаного нижче:
qemu-system-x86_64 \
-machine accel=kvm:tcg \
-m 2048 \
-drive file=disk.img,format=raw,if=virtio
-Як і з libvirt, дуже важливо вибрати правильний формат. Цим форматом буде
-C<raw>, якщо раніше не було використано параметр I<--format>.
+Як і з libvirt, дуже важливо вибрати правильний формат. Цим форматом буде C<raw>, якщо раніше не було використано параметр I<--format>.
=head2 КЕРУВАННЯ НАЛАШТУВАННЯМИ
=head3 Puppet
-Щоб увімкнути агент Puppet у гостьовій системі, встановіть пакунок, вкажіть
-налаштування на вашому Puppetmaster і забезпечте запуск агента під час
-завантаження.
+Щоб увімкнути агент Puppet у гостьовій системі, встановіть пакунок, вкажіть налаштування на вашому Puppetmaster і забезпечте запуск агента під час завантаження.
Типовою командою virt-builder буде:
--run-command 'systemctl enable puppet' \
--selinux-relabel
-Точний перелік настанов залежить від дистрибутива Linux. Докладніше про це
-тут: L<https://docs.puppet.com/puppet/latest/install_pre.html>
+Точний перелік настанов залежить від дистрибутива Linux. Докладніше про це тут: L<https://docs.puppet.com/puppet/latest/install_pre.html>
=head2 ДІАГНОСТИКА ЗБИРАННЯ
-Якщо сам virt-builder не може виконати роботу, слід увімкнути діагностику
-(I<-v>) і повідомити про ваду розробників (див. розділ L</ВАДИ> нижче).
+Якщо сам virt-builder не може виконати роботу, слід увімкнути діагностику (I<-v>) і повідомити про ваду розробників (див. розділ L</ВАДИ> нижче).
-Якщо причиною неможливості виконання завдання virt-builder є який скрипт або
-пакунок, який програма не може встановити, спробуйте скористатися параметром
-I<--no-delete-on-failure>, щоб зберегти файл результатів, і продовжіть
-вивчення цього розділу підручника.
+Якщо причиною неможливості виконання завдання virt-builder є який скрипт або пакунок, який програма не може встановити, спробуйте скористатися параметром I<--no-delete-on-failure>, щоб зберегти файл результатів, і продовжіть вивчення цього розділу підручника.
-Якщо virt-builder успішно завершує роботу, але образ не працює, ось чим слід
-скористатися:
+Якщо virt-builder успішно завершує роботу, але образ не працює, ось чим слід скористатися:
=over 4
virt-rescue -a disk.img
-Ви потрапите до оболонки порятунку. Ви зможете змонтувати файлові системи з
-образу диска до F</sysroot> і вивчити їх за допомогою звичних команд
-Linux. Ви також можете скористатися chroot щодо гостьової системи і
-перевстановити у ній завантажувач. На сторінці підручника з virt-rescue
-наведено набагато більше інформації та прикладів.
+Ви потрапите до оболонки порятунку. Ви зможете змонтувати файлові системи з образу диска до F</sysroot> і вивчити їх за допомогою звичних команд Linux. Ви також можете скористатися chroot щодо гостьової системи і перевстановити у ній завантажувач. На сторінці підручника з virt-rescue наведено набагато більше інформації та прикладів.
=item Використання guestfish
guestfish -a disk.img -i
-Скористайтеся командами guestfish, зокрема C<ll /каталог> і C<cat /файл>,
-для перевірки каталогів та файлів.
+Скористайтеся командами guestfish, зокрема C<ll /каталог> і C<cat /файл>, для перевірки каталогів та файлів.
=item Використання guestmount
-Безпечно змонтувати образ диска у основній системі за допомогою FUSE і
-L<guestmount(1)>:
+Безпечно змонтувати образ диска у основній системі за допомогою FUSE і L<guestmount(1)>:
mkdir /tmp/mp
guestmount -a disk.img -i /tmp/mp
=item Додати послідовну консоль
-Якщо гостьова система повисає під час завантаження, може допомогти додавання
-послідовної консолі у гостьову систему і спрямовування повідомлень ядра до
-послідовної консолі. Додавання послідовної консолі потребує вивчення
-документації до вашого гіпервізору. Щоб спрямувати повідомлення ядра до
-послідовної консолі, додайте таку частину до командного рядка ядра:
+Якщо гостьова система повисає під час завантаження, може допомогти додавання послідовної консолі у гостьову систему і спрямовування повідомлень ядра до послідовної консолі. Додавання послідовної консолі потребує вивчення документації до вашого гіпервізору. Щоб спрямувати повідомлення ядра до послідовної консолі, додайте таку частину до командного рядка ядра:
console=tty0 console=ttyS0,115200
=head2 ДЖЕРЕЛА ШАБЛОНІВ
-virt-builder читає доступні джерела із файлів налаштування, файлів із
-суфіксом назви I<.conf>, які зберігаються у одному з таких місць:
+virt-builder читає доступні джерела із файлів налаштування, файлів із суфіксом назви I<.conf>, які зберігаються у одному з таких місць:
=over 4
=item *
-$XDG_CONFIG_HOME/virt-builder/reposd/ (C<$XDG_CONFIG_HOME> дорівнює
-F<$HOME/.config>, якщо не встановлено).
+$XDG_CONFIG_HOME/virt-builder/reposd/ (C<$XDG_CONFIG_HOME> дорівнює F<$HOME/.config>, якщо не встановлено).
=item *
-$VIRT_BUILDER_DIRS/virt-builder/repos.d/ (where C<$VIRT_BUILDER_DIRS> means
-any of the directories in that environment variable, or just F</etc> if not
-set).
+$VIRT_BUILDER_DIRS/virt-builder/repos.d/ (where C<$VIRT_BUILDER_DIRS> means any of the directories in that environment variable, or just F</etc> if not set).
=back
-Кожен з файлів I<.conf> у вказаних каталогах зберігає дані у простому
-текстовому форматі, ось так:
+Кожен з файлів I<.conf> у вказаних каталогах зберігає дані у простому текстовому форматі, ось так:
[libguestfs.org]
uri=http://libguestfs.org/download/builder/index.asc
gpgkey=file:///etc/xdg/virt-builder/repos.d/libguestfs.gpg
-Частина у квадратних дужках є ідентифікатором сховища, який використовується
-як унікальний ідентифікатор.
+Частина у квадратних дужках є ідентифікатором сховища, який використовується як унікальний ідентифікатор.
Можуть з’явитися такі поля:
=item C<gpgkey=АДРЕСА>
-Це необов'язкове поле відповідає адресі (хоча прийнятними є лише адреси
-I<file://>) ключа, який використано для підписування файла покажчика. Якщо
-поля немає, файл покажчика, на який посилається I<uri=..>, не підписано.
+Це необов'язкове поле відповідає адресі (хоча прийнятними є лише адреси I<file://>) ключа, який використано для підписування файла покажчика. Якщо поля немає, файл покажчика, на який посилається I<uri=..>, не підписано.
=item C<proxy=РЕЖИМ>
-Це необов'язкове поле вказує на режим проксі, яким слід скористатися для
-отримання файла покажчика цього сховища. Можливі значення:
+Це необов'язкове поле вказує на режим проксі, яким слід скористатися для отримання файла покажчика цього сховища. Можливі значення:
=over 4
=item I<усе інше>
-Задає справжні налаштування проксі, якими слід скористатися, незважаючи на
-налаштування системи.
+Задає справжні налаштування проксі, якими слід скористатися, незважаючи на налаштування системи.
=back
-Якщо значення не вказано, буде використано параметри проксі-сервера системи
-(тобто все буде так, наче вказано B<system>).
+Якщо значення не вказано, буде використано параметри проксі-сервера системи (тобто все буде так, наче вказано B<system>).
=item C<format=ФОРМАТ>
=item B<native>
-Природний формат сховища C<virt-builder>. Див. також розділ L</Створення і
-підписування файла покажчика> нижче.
+Природний формат сховища C<virt-builder>. Див. також розділ L</Створення і підписування файла покажчика> нижче.
=item B<simplestreams>
-Адреса, яка визначає кореневий каталог ієрархії метаданих Simple Streams
-версії 1.0.
+Адреса, яка визначає кореневий каталог ієрархії метаданих Simple Streams версії 1.0.
-Докладніший опис Simple Streams наведено тут:
-L<https://launchpad.net/simplestreams>.
+Докладніший опис Simple Streams наведено тут: L<https://launchpad.net/simplestreams>.
=back
=back
-Якщо ви часто користуватиметеся virt-builder, варто створити власне сховище
-шаблонів.
+Якщо ви часто користуватиметеся virt-builder, варто створити власне сховище шаблонів.
=head3 Сховище libguestfs.org
-Від початку, virt-builder отримує файл
-L<http://libguestfs.org/download/builder/index.asc>, який є покажчиком усіх
-доступних шаблонів, і деяку інформацію щодо кожного з них, яку додано до
-цифрового підпису. За допомогою команди C<virt-builder --list> можна
-ознайомитися із усіма даними щодо цього файла покажчика.
+Від початку, virt-builder отримує файл L<http://libguestfs.org/download/builder/index.asc>, який є покажчиком усіх доступних шаблонів, і деяку інформацію щодо кожного з них, яку додано до цифрового підпису. За допомогою команди C<virt-builder --list> можна ознайомитися із усіма даними щодо цього файла покажчика.
-Шаблони, які зберігаються на libguestfs.org, було створено за допомогою
-скриптів командної оболонки, файлів kickstart та файлів, які можна знайти у
-ієрархії коду libguestfs, у каталозі C<builder/templates>.
+Шаблони, які зберігаються на libguestfs.org, було створено за допомогою скриптів командної оболонки, файлів kickstart та файлів, які можна знайти у ієрархії коду libguestfs, у каталозі C<builder/templates>.
=head3 Налаштовування доступу до сховища
-Ви можете створити власний сайт із файлом покажчика (index) і деякими
-шаблонами, а потім вказати virt-builder на цей сайт за допомогою вмісту
-файла I<.conf>.
+Ви можете створити власний сайт із файлом покажчика (index) і деякими шаблонами, а потім вказати virt-builder на цей сайт за допомогою вмісту файла I<.conf>.
-Зауважте, що якщо ваш покажчик підписано, вам слід належним чином заповнити
-поле I<gpgkey=..> у вашому файлі I<.conf>, а також додати файл ключа GPG.
+Зауважте, що якщо ваш покажчик підписано, вам слід належним чином заповнити поле I<gpgkey=..> у вашому файлі I<.conf>, а також додати файл ключа GPG.
virt-builder --source https://example.com/builder/index.asc \
--fingerprint 'AAAA BBBB ...' \
--list
-Ви можете розмістити сайт будь-якому мережевому сервері або сервері FTP чи у
-локальній або мережевій файловій системі.
+Ви можете розмістити сайт будь-якому мережевому сервері або сервері FTP чи у локальній або мережевій файловій системі.
=head3 Встановлення ключа GPG
-Якщо у вас ще немає ключа GnuPG, вам слід налаштувати такий. (Строго кажучи,
-це не є обов'язковою умовою, але якщо ваш файл покажчика і файл шаблона не
-буде підписано, користувачам virt-builder доведеться додавати параметр
-I<--no-check-signature> до команди кожного разу, коли їм потрібно буде
-скористатися virt-builder.)
+Якщо у вас ще немає ключа GnuPG, вам слід налаштувати такий. (Строго кажучи, це не є обов'язковою умовою, але якщо ваш файл покажчика і файл шаблона не буде підписано, користувачам virt-builder доведеться додавати параметр I<--no-check-signature> до команди кожного разу, коли їм потрібно буде скористатися virt-builder.)
-Інструкцію зі створення ключа можна знайти у підручнику з GPG:
-L<http://www.gnupg.org/gph/en/manual.html>.
+Інструкцію зі створення ключа можна знайти у підручнику з GPG: L<http://www.gnupg.org/gph/en/manual.html>.
Експортувати ваш відкрити ключ GPG:
=head3 Створення шаблонів
-Існує багато способів створення шаблонів. Наприклад, ви можете клонувати
-наявні гостьові системи (див. L<virt-sysprep(1)>) або встановити гостьову
-систему вручну (L<virt-install(1)>). Щоб ознайомитися із способами створення
-шаблонів для virt-builder, вивчіть скрипти у C<builder/templates>
+Існує багато способів створення шаблонів. Наприклад, ви можете клонувати наявні гостьові системи (див. L<virt-sysprep(1)>) або встановити гостьову систему вручну (L<virt-install(1)>). Щоб ознайомитися із способами створення шаблонів для virt-builder, вивчіть скрипти у C<builder/templates>
-У virt-builder передбачено підтримку усіх форматів образів (наприклад, raw,
-qcow2 тощо) як шаблонів, у звичайному форматі та у форматі, стисненому
-XZ. Таким чином, як шаблонами можна скористатися наявними образами
-(наприклад, образами, очищеними за допомогою L<virt-sysprep(1)>).
+У virt-builder передбачено підтримку усіх форматів образів (наприклад, raw, qcow2 тощо) як шаблонів, у звичайному форматі та у форматі, стисненому XZ. Таким чином, як шаблонами можна скористатися наявними образами (наприклад, образами, очищеними за допомогою L<virt-sysprep(1)>).
-Для досягнення найкращих результатів під час стискання шаблонів
-скористайтеся такими параметрами програми xz (пояснення щодо цих параметрів
-можна знайти на сторінці довідки до L<nbdkit-xz-plugin(1)>):
+Для досягнення найкращих результатів під час стискання шаблонів скористайтеся такими параметрами програми xz (пояснення щодо цих параметрів можна знайти на сторінці довідки до L<nbdkit-xz-plugin(1)>):
xz --best --block-size=16777216 disk
=head3 Створення і підписування файла покажчика
-Файл покажчика записується у простому текстовому форматі (тут показано без
-цифрового підпису):
+Файл покажчика записується у простому текстовому форматі (тут показано без цифрового підпису):
[fedora-18]
name=Fedora® 18
compressed_size=172190964
expand=/dev/sda3
-Частина у квадратних дужках є C<версією-ОС>, тим самим рядком, який
-використано у рядку команди virt-builder, використаному для збирання цієї
-операційної системи.
+Частина у квадратних дужках є C<версією-ОС>, тим самим рядком, який використано у рядку команди virt-builder, використаному для збирання цієї операційної системи.
-Спростити створення і підписування файла покажчика можна за допомогою
-програми L<virt-builder-repository(1)>.
+Спростити створення і підписування файла покажчика можна за допомогою програми L<virt-builder-repository(1)>.
-Після приготування файла C<index> у належному форматі підпишіть його такою
-командою:
+Після приготування файла C<index> у належному форматі підпишіть його такою командою:
gpg --clearsign --armor index
-У результаті виконання цієї команди буде створено остаточний файл із назвою
-F<index.asc>, який можна вивантажити на сервер (і додати у запис адреси
-I<uri=..>). Як ми вже зауважували вище, підписування файла покажчика є
-необов'язковим, але рекомендованим.
+У результаті виконання цієї команди буде створено остаточний файл із назвою F<index.asc>, який можна вивантажити на сервер (і додати у запис адреси I<uri=..>). Як ми вже зауважували вище, підписування файла покажчика є необов'язковим, але рекомендованим.
Можуть з’явитися такі поля:
=item C<name=НАЗВА>
-Зручна для користувача назва цього шаблона. Назву буде показано у виведених
-даних команди з параметром I<--list>, більше ніде програма її не
-використовує.
+Зручна для користувача назва цього шаблона. Назву буде показано у виведених даних команди з параметром I<--list>, більше ніде програма її не використовує.
=item C<osinfo=ІДЕНТИФІКАТОР>
-Це додаткове поле пов'язує операційну систему із відповідним ідентифікатором
-libosinfo. Virt-builder (ще) не використовує ці дані.
+Це додаткове поле пов'язує операційну систему із відповідним ідентифікатором libosinfo. Virt-builder (ще) не використовує ці дані.
=item C<arch=АРХІТЕКТУРА>
-Архітектура операційної системи, яку встановлено у цьому шаблоні. Це поле є
-обов'язковим.
+Архітектура операційної системи, яку встановлено у цьому шаблоні. Це поле є обов'язковим.
=item C<file=ШЛЯХ>
Шлях (відносно покажчика) стисненого xz шаблона.
-Зауважте, що тут B<не> можна використовувати абсолютні шляхи або адреси
-файлів. Причиною є те, що у virt-builder використовується правило «одного
-походження» для шаблонів, тому вони не можуть походити з інших серверів.
+Зауважте, що тут B<не> можна використовувати абсолютні шляхи або адреси файлів. Причиною є те, що у virt-builder використовується правило «одного походження» для шаблонів, тому вони не можуть походити з інших серверів.
=item C<sig=ШЛЯХ>
-B<Цей параметр вважається застарілим>. Використовуйте замість нього поле
-контрольної суми (checksum).
+B<Цей параметр вважається застарілим>. Використовуйте замість нього поле контрольної суми (checksum).
Шлях (відносно покажчика) від'єднаного підпису GPG файла xz.
-Зауважте, що тут B<не> можна використовувати абсолютні шляхи або адреси
-файлів. Причиною є те, що у virt-builder використовується правило «одного
-походження» для шаблонів, тому вони не можуть походити з інших серверів.
+Зауважте, що тут B<не> можна використовувати абсолютні шляхи або адреси файлів. Причиною є те, що у virt-builder використовується правило «одного походження» для шаблонів, тому вони не можуть походити з інших серверів.
Файл можна створити такою командою:
=item C<checksum[sha512]=7b882fe9b82eb0fef...>
-Контрольну суму SHA-512 файла, вказаного у виразі I<file=..>, буде
-перевірено після завершення отримання даних. Для визначення підпису
-скористайтеся такою командою:
+Контрольну суму SHA-512 файла, вказаного у виразі I<file=..>, буде перевірено після завершення отримання даних. Для визначення підпису скористайтеся такою командою:
sha512sum disk.xz
-Зауважте, що якщо ви користуєтеся цим параметром, вам не потрібно
-підписувати файл, тобто використовувати параметр C<sig>. Цей параметр має
-вищий пріоритет за параметра C<sig>.
+Зауважте, що якщо ви користуєтеся цим параметром, вам не потрібно підписувати файл, тобто використовувати параметр C<sig>. Цей параметр має вищий пріоритет за параметра C<sig>.
=item C<checksum=7b882fe9b82eb0fef...>
C<checksum> є скороченою формою запису C<checksum[sha512]>.
-Якщо вам доводиться працювати з virt-builder = 1.24.0, слід користуватися
-C<checksum>, оскільки ця версію видаватиме повідомлення про помилку обробки,
-якщо у ключі поля використано квадратні дужки і цифри. Цю помилку виправлено
-у версіях virt-builder E<ge> 1.24.1.
+Якщо вам доводиться працювати з virt-builder = 1.24.0, слід користуватися C<checksum>, оскільки ця версію видаватиме повідомлення про помилку обробки, якщо у ключі поля використано квадратні дужки і цифри. Цю помилку виправлено у версіях virt-builder E<ge> 1.24.1.
=item C<revision=N>
-Модифікація (revision) — ціле число, яке використовується для керування
-кешем шаблонів. Збільшення номера модифікації призводить до того, що клієнти
-отримують шаблон, навіть якщо у них є копія у кеші.
+Модифікація (revision) — ціле число, яке використовується для керування кешем шаблонів. Збільшення номера модифікації призводить до того, що клієнти отримують шаблон, навіть якщо у них є копія у кеші.
-Номер модифікації є необов’язковим. Якщо його не вказано, типовим значенням
-вважається C<1>.
+Номер модифікації є необов’язковим. Якщо його не вказано, типовим значенням вважається C<1>.
=item C<format=raw>
=item C<format=qcow2>
-Визначає формат образу диска; якщо дані стиснено, слід вказати формат до
-стискання. Якщо формат не вказано, його буде визначено автоматично, але все
-ж варто явним чином вказати бажаний формат.
+Визначає формат образу диска; якщо дані стиснено, слід вказати формат до стискання. Якщо формат не вказано, його буде визначено автоматично, але все ж варто явним чином вказати бажаний формат.
-Зауважте, що це формат початкових даних, який відрізняється від параметра
-I<--format> (бажаний формат результату). Virt-builder виконує перетворення
-«на льоту» з початкового формату до бажаного формату результату.
+Зауважте, що це формат початкових даних, який відрізняється від параметра I<--format> (бажаний формат результату). Virt-builder виконує перетворення «на льоту» з початкового формату до бажаного формату результату.
=item C<size=NNN>
-Віртуальний розмір образу у байтах. Це розмір нестисненого образу. Якщо
-використано формат, відмінний від raw, зокрема qcow2, це значення означає
-розмір віртуального диска, а не розмір файла qcow2.
+Віртуальний розмір образу у байтах. Це розмір нестисненого образу. Якщо використано формат, відмінний від raw, зокрема qcow2, це значення означає розмір віртуального диска, а не розмір файла qcow2.
Це поле слід заповнити.
-Virt-builder також використовує це значення як мінімальний розмір, запит
-щодо якого можуть надсилати користувачів за допомогою параметра I<--size>,
-або типовий розмір, якщо не вказано параметр I<--size>.
+Virt-builder також використовує це значення як мінімальний розмір, запит щодо якого можуть надсилати користувачів за допомогою параметра I<--size>, або типовий розмір, якщо не вказано параметр I<--size>.
=item C<compressed_size=NNN>
-Справжній розмір образу диска у байтах, тобто розмір, який було вказано у
-I<file=..>. Це значення використовується лише для інформування (якщо
-використовуються формати C<long> і C<json> у параметрі I<--list>).
+Справжній розмір образу диска у байтах, тобто розмір, який було вказано у I<file=..>. Це значення використовується лише для інформування (якщо використовуються формати C<long> і C<json> у параметрі I<--list>).
=item C<expand=/dev/sdaX>
-При розпаковуванні образу до його остаточного розміру, наказати
-L<virt-resize(1)> розпакувати дані до іменованого розділу у образі гостьової
-системи для заповнення усього доступного місця. Це працює подібно до
-параметра I<--expand> virt-resize.
+При розпаковуванні образу до його остаточного розміру, наказати L<virt-resize(1)> розпакувати дані до іменованого розділу у образі гостьової системи для заповнення усього доступного місця. Це працює подібно до параметра I<--expand> virt-resize.
-Тут вам зазвичай слід вказати назву пристрою у кореневій файловій системі
-гостьової операційної системи.
+Тут вам зазвичай слід вказати назву пристрою у кореневій файловій системі гостьової операційної системи.
-Цим елементом варто скористатися, але це не обов'язково. Якщо поле
-пропущено, virt-resize створить додатковий розділ наприкінці диска для
-заповнення порожнього місця, що набагато менш зручно.
+Цим елементом варто скористатися, але це не обов'язково. Якщо поле пропущено, virt-resize створить додатковий розділ наприкінці диска для заповнення порожнього місця, що набагато менш зручно.
=item C<lvexpand=/пристрій/група_томів/логічний_том>
-При розпаковуванні образу до його остаточного розміру, наказати
-L<virt-resize(1)> розпакувати дані до іменованого логічного тому у образі
-гостьової системи для заповнення усього доступного місця. Це працює подібно
-до параметра I<--lv-expand> virt-resize.
+При розпаковуванні образу до його остаточного розміру, наказати L<virt-resize(1)> розпакувати дані до іменованого логічного тому у образі гостьової системи для заповнення усього доступного місця. Це працює подібно до параметра I<--lv-expand> virt-resize.
-Якщо у гостьовій системі використовується LVM2, тут слід вказати логічний
-том кореневої файлової системи гостьової операційної системи. Якщо у
-гостьовій операційній системі не використовується LVM2 або її коренева
-файлова система не зберігається на логічному томі, не використовуйте цей
-параметр.
+Якщо у гостьовій системі використовується LVM2, тут слід вказати логічний том кореневої файлової системи гостьової операційної системи. Якщо у гостьовій операційній системі не використовується LVM2 або її коренева файлова система не зберігається на логічному томі, не використовуйте цей параметр.
=item C<notes=НОТАТКИ>
-Будь-які нотатки, які стосуються цього образу, особливо нотатки із описом
-пакунків образу, способу створення образу та даних щодо ліцензування.
+Будь-які нотатки, які стосуються цього образу, особливо нотатки із описом пакунків образу, способу створення образу та даних щодо ліцензування.
Ці дані буде виведено у режимах I<--notes> і I<--list> I<--long>.
-Ви можете створювати багаторядкові нотатки додаванням принаймні одного
-пробілу на початку кожного рядка (навіть порожнього):
+Ви можете створювати багаторядкові нотатки додаванням принаймні одного пробілу на початку кожного рядка (навіть порожнього):
notes=Цей образ було створено за допомогою
такого скрипту kickstart:
=item C<hidden=true>
-Використання прапорця hidden усуває шаблон зі списку, який буде показано у
-відповідь на використання параметра I<--list> (лишаючи образ придатним до
-встановлення). Цей прапорець використовується для тестових образів.
+Використання прапорця hidden усуває шаблон зі списку, який буде показано у відповідь на використання параметра I<--list> (лишаючи образ придатним до встановлення). Цей прапорець використовується для тестових образів.
=item C<aliases=ПСЕВДОНІМ1 ПСЕВДОНІМ2 ...>
-Це необов'язкове поле визначає список альтернативних назв, відокремлених
-пробілами, для образу. Альтернативною назвою, наприклад, можна скористатися
-так, щоб вона завжди вказувала на найсвіжішу версію певного образу, лишаючи
-інші, старіші версії доступними у покажчику, замість оновлення того самого
-образу (див. поле C<revision>).
+Це необов'язкове поле визначає список альтернативних назв, відокремлених пробілами, для образу. Альтернативною назвою, наприклад, можна скористатися так, щоб вона завжди вказувала на найсвіжішу версію певного образу, лишаючи інші, старіші версії доступними у покажчику, замість оновлення того самого образу (див. поле C<revision>).
=back
=head3 Запуск virt-builder для декількох джерел одночасно
-У virt-builder передбачено можливість використання декількох
-джерел. Рекомендованим способом є розгортання файлів I<.conf>, які вказують
-на файли покажчика. Іншим способом є визначення джерел за допомогою
-декількох параметрів I<--source> і/або I<--fingerprint>:
+У virt-builder передбачено можливість використання декількох джерел. Рекомендованим способом є розгортання файлів I<.conf>, які вказують на файли покажчика. Іншим способом є визначення джерел за допомогою декількох параметрів I<--source> і/або I<--fingerprint>:
virt-builder \
--source http://example.com/s1/index.asc \
--source http://example.com/s2/index.asc
-Ви можете надати N відбитків або 1 відбиток. Якщо буде надано N відбитків, N
-= кількості джерел, а між джерелом і відбитком є однозначна відповідність:
+Ви можете надати N відбитків або 1 відбиток. Якщо буде надано N відбитків, N = кількості джерел, а між джерелом і відбитком є однозначна відповідність:
virt-builder \
--source http://example.com/s1/index.asc --fingerprint '0123 ...' \
=head3 Ліцензування шаблонів
-Вам слід зважати на ліцензування образів, які ви розповсюджуєте. Для
-гостьових систем із відкритим кодом слід надавати посилання на початковий
-код у полі C<notes> і виконувати інші вимоги (наприклад, вимоги щодо
-торгівельних знаків).
+Вам слід зважати на ліцензування образів, які ви розповсюджуєте. Для гостьових систем із відкритим кодом слід надавати посилання на початковий код у полі C<notes> і виконувати інші вимоги (наприклад, вимоги щодо торгівельних знаків).
=head3 Формальна специфікація файла покажчика
-Формат файла покажчика має формальну специфікацію, що визначається сканером
-flex і обробником bison, що використовуються для обробки файла. Її можна
-знайти у таких файлах у ієрархію коду libguestfs:
+Формат файла покажчика має формальну специфікацію, що визначається сканером flex і обробником bison, що використовуються для обробки файла. Її можна знайти у таких файлах у ієрархію коду libguestfs:
builder/index-scan.l
builder/index-parse.y
-Для перевірки коректності файла покажчика використовується програма із
-назвою L<virt-index-validate(1)>.
+Для перевірки коректності файла покажчика використовується програма із назвою L<virt-index-validate(1)>.
-Зауважте, що обробник і інструмент може працювати як із підписаним, так і з
-непідписаним файлом покажчика (тобто з F<index> або зF<index.asc>).
+Зауважте, що обробник і інструмент може працювати як із підписаним, так і з непідписаним файлом покажчика (тобто з F<index> або зF<index.asc>).
Кодуванням покажчика завжди є UTF-8.
=head3 Кешування шаблонів
-Оскільки шаблоні зазвичай є дуже великими, отримані шаблони зберігають у
-кеші домашнього каталогу користувача.
+Оскільки шаблоні зазвичай є дуже великими, отримані шаблони зберігають у кеші домашнього каталогу користувача.
-Кеш розміщується у F<$XDG_CACHE_HOME/virt-builder/> або
-F<$HOME/.cache/virt-builder>.
+Кеш розміщується у F<$XDG_CACHE_HOME/virt-builder/> або F<$HOME/.cache/virt-builder>.
-Ви можете отримати дані щодо каталогу кешу, зокрема дані щодо того, які
-гостьові системи кешуються, за допомогою такої команди:
+Ви можете отримати дані щодо каталогу кешу, зокрема дані щодо того, які гостьові системи кешуються, за допомогою такої команди:
virt-builder --print-cache
Щоб вимкнути кешування шаблонів, скористайтеся параметром I<--no-cache>.
-Кешуванню підлягають лише шаблони. Для покажчика та цифрових підписів
-кешування не використовується.
+Кешуванню підлягають лише шаблони. Для покажчика та цифрових підписів кешування не використовується.
=head3 Кешування пакунків
-Virt-builder використовує для отримання файлів L<curl(1)>, а також
-використовує поточні параметри C<http_proxy> (та інші) під час встановлення
-пакунків (I<--install>, I<--update>).
+Virt-builder використовує для отримання файлів L<curl(1)>, а також використовує поточні параметри C<http_proxy> (та інші) під час встановлення пакунків (I<--install>, I<--update>).
-Тому ви можете встановити ці змінні середовища з метою максимізації обсягу
-локального кешування. Див. L</ЗМІННІ СЕРЕДОВИЩА> та L<curl(1)>.
+Тому ви можете встановити ці змінні середовища з метою максимізації обсягу локального кешування. Див. L</ЗМІННІ СЕРЕДОВИЩА> та L<curl(1)>.
=head3 Локальні дзеркала
-Щоб збільшити швидкість і надійність встановлення пакунків, ви можете
-налаштувати локальне дзеркало для дистрибутива призначення і вказати на
-нього засобу керування пакунками гостьової системи.
+Щоб збільшити швидкість і надійність встановлення пакунків, ви можете налаштувати локальне дзеркало для дистрибутива призначення і вказати на нього засобу керування пакунками гостьової системи.
=head4 Використання локального дзеркала з Fedora
=head4 Використання локального дзеркала з Debian
-Припускаємо, що ви використовуєте C<apt-proxy> для віддзеркалення сховища,
-тоді вам слід створити новий файл F<sources.list> для визначення вашого
-проксі-сервера (див. L<https://help.ubuntu.com/community/AptProxy>), а потім
-віддайте таку команду:
+Припускаємо, що ви використовуєте C<apt-proxy> для віддзеркалення сховища, тоді вам слід створити новий файл F<sources.list> для визначення вашого проксі-сервера (див. L<https://help.ubuntu.com/community/AptProxy>), а потім віддайте таку команду:
virt-builder debian-8 \
--upload sources.list:/etc/apt/sources.list \
=head2 ЦИФРОВІ ПІДПИСИ
-Virt-builder використовує GNU Privacy Guard (GnuPG або gpg) для забезпечення
-невтручання до покажчика і шаблонів.
+Virt-builder використовує GNU Privacy Guard (GnuPG або gpg) для забезпечення невтручання до покажчика і шаблонів.
Джерело вказує на файл покажчика, який можна підписати.
-Virt-builder отримує покажчик і перевіряє, чи є підпис коректним і чи
-збігається відбиток підписника із вказаним відбитком (тобто відбитком,
-вказаним за допомогою I<gpgkey=..> у I<.conf> або за допомогою
-I<--fingerprint>, саме у цьому порядку).
+Virt-builder отримує покажчик і перевіряє, чи є підпис коректним і чи збігається відбиток підписника із вказаним відбитком (тобто відбитком, вказаним за допомогою I<gpgkey=..> у I<.conf> або за допомогою I<--fingerprint>, саме у цьому порядку).
-Для перевірки відповідності щодо вбудованого відкритого ключа або відбитка,
-відкритий ключ слід імпортувати до локального сховища ключів gpg користувача
-(саме так працює gpg).
+Для перевірки відповідності щодо вбудованого відкритого ключа або відбитка, відкритий ключ слід імпортувати до локального сховища ключів gpg користувача (саме так працює gpg).
Під час отримання шаблона його підпис буде перевірено у той самий спосіб.
-Хоча підписи і не є обов'язковими, якщо ви їх не використаєте, користувачам
-virt-builder доведеться використовувати параметр I<--no-check-signature> у
-рядку команди. За допомогою підпису можна запобігти заміні зловмисником
-підписаного файла покажчика непідписаним файлом. При цьому virt-builder без
-перевірки підпису не повідомлятиме про підміну. Щоб там не сталося,
-наполегливо рекомендуємо вам створювати підписаний покажчик і шаблони.
+Хоча підписи і не є обов'язковими, якщо ви їх не використаєте, користувачам virt-builder доведеться використовувати параметр I<--no-check-signature> у рядку команди. За допомогою підпису можна запобігти заміні зловмисником підписаного файла покажчика непідписаним файлом. При цьому virt-builder без перевірки підпису не повідомлятиме про підміну. Щоб там не сталося, наполегливо рекомендуємо вам створювати підписаний покажчик і шаблони.
=head2 АРХІТЕКТУРА
-Virt-builder може збирати образ гостьової системи для будь-якої архітектури,
-незалежно від архітектури основної системи. Наприклад, можна зібрати образ
-гостьової системи архітектури x86-64 на основній системі архітектури ARM.
+Virt-builder може збирати образ гостьової системи для будь-якої архітектури, незалежно від архітектури основної системи. Наприклад, можна зібрати образ гостьової системи архітектури x86-64 на основній системі архітектури ARM.
-Втім, деякі з параметрів не працюватимуть, особливо параметри, які
-потребують виконання команд у гостьовій системі під час процесу збирання:
-I<--install>, I<--update>, I<--run>, I<--run-command>. Вам варто замінити ці
-команди на їхні еквіваленти у firstboot.
+Втім, деякі з параметрів не працюватимуть, особливо параметри, які потребують виконання команд у гостьовій системі під час процесу збирання: I<--install>, I<--update>, I<--run>, I<--run-command>. Вам варто замінити ці команди на їхні еквіваленти у firstboot.
-Основна система архітектури x86-64, збираючи гостьові системи 32-бітової
-архітектури i686, має працювати без використання будь-яких додаткових кроків
-налаштовування.
+Основна система архітектури x86-64, збираючи гостьові системи 32-бітової архітектури i686, має працювати без використання будь-яких додаткових кроків налаштовування.
=head2 БЕЗПЕКА
-Virt-builder не потребує запуску від імені користувача root (фактично,
-програму не слід запускати від імені root) і не використовує setuid, C<sudo>
-або будь-яких інших подібних механізмів.
+Virt-builder не потребує запуску від імені користувача root (фактично, програму не слід запускати від імені root) і не використовує setuid, C<sudo> або будь-яких інших подібних механізмів.
-I<--install>, I<--update>, I<--run> і I<--run-command> реалізовано за
-допомогою базової системи (невеличкої віртуальної машини), тому ці команди
-не працюватимуть у основній системі. Якщо ви користуєтеся модулем libvirt
-libguestfs і у системі увімкнено SELinux , віртуальну машину буде додатково
-огорнуто у контейнер SELinux (sVirt).
+I<--install>, I<--update>, I<--run> і I<--run-command> реалізовано за допомогою базової системи (невеличкої віртуальної машини), тому ці команди не працюватимуть у основній системі. Якщо ви користуєтеся модулем libvirt libguestfs і у системі увімкнено SELinux , віртуальну машину буде додатково огорнуто у контейнер SELinux (sVirt).
-Втім, ці параметри отримуватимуть доступ до мережі основної системи і,
-оскільки шаблон може містити шахрайський код, цей код може намагатися
-отримати доступ до ресурсів мережі основної системи, які мають бути
-недоступними для нього. Для запобігання небажаному доступу ви можете
-скористатися параметром I<--no-network>.
+Втім, ці параметри отримуватимуть доступ до мережі основної системи і, оскільки шаблон може містити шахрайський код, цей код може намагатися отримати доступ до ресурсів мережі основної системи, які мають бути недоступними для нього. Для запобігання небажаному доступу ви можете скористатися параметром I<--no-network>.
-Команди першого завантаження виконуються у контексті гостьової системи, тому
-слід брати до уваги параметри захисту у вашому гіпервізорі або
-обчислювальній хмарі.
+Команди першого завантаження виконуються у контексті гостьової системи, тому слід брати до уваги параметри захисту у вашому гіпервізорі або обчислювальній хмарі.
-Virt-builder додає випадкову базу псевдовипадкових чисел до кожної гостьової
-системи, яку зібрано за його допомогою. Це допомагає забезпеченню справжньої
-випадковості номерів послідовності TCP, UUID, ключів вузла ssh тощо під час
-завантаження гостьової системи.
+Virt-builder додає випадкову базу псевдовипадкових чисел до кожної гостьової системи, яку зібрано за його допомогою. Це допомагає забезпеченню справжньої випадковості номерів послідовності TCP, UUID, ключів вузла ssh тощо під час завантаження гостьової системи.
-Вам слід перевіряти цифрові підписи і не ігнорувати повідомлення про помилки
-під час таких перевірок.
+Вам слід перевіряти цифрові підписи і не ігнорувати повідомлення про помилки під час таких перевірок.
=head2 КЛОНИ
-Якщо вам потрібно створити багато гостьових систем одного типу, виникає
-спокуса запустити virt-builder один раз, а потім просто скопіювати
-файл-результат. Втім, так B<не> слід робити. Вам слід запустити virt-builder
-окремо для кожної нової гостьової системи, яку ви хочете створити.
+Якщо вам потрібно створити багато гостьових систем одного типу, виникає спокуса запустити virt-builder один раз, а потім просто скопіювати файл-результат. Втім, так B<не> слід робити. Вам слід запустити virt-builder окремо для кожної нової гостьової системи, яку ви хочете створити.
-Так слід робити тому, що кожен клон повинен мати (принаймні) окрему базу для
-псевдовипадкових чисел, а також, ймовірно, інші унікальні властивості
-(зокрема UUID файлових систем) у майбутніх версіях virt-builder.
+Так слід робити тому, що кожен клон повинен мати (принаймні) окрему базу для псевдовипадкових чисел, а також, ймовірно, інші унікальні властивості (зокрема UUID файлових систем) у майбутніх версіях virt-builder.
-Ще однією річчю, яку вам I<не> слід робити, є клонування завантаженого
-образу диска. Причиною цього є те, що деякі гостьові системи створюють
-унікальні ідентифікатори машини, ключі SSH вузла та інші дані під час
-першого завантаження, а дублювання таких ідентифікаторів у клонах є вкрай
-небажаним.
+Ще однією річчю, яку вам I<не> слід робити, є клонування завантаженого образу диска. Причиною цього є те, що деякі гостьові системи створюють унікальні ідентифікатори машини, ключі SSH вузла та інші дані під час першого завантаження, а дублювання таких ідентифікаторів у клонах є вкрай небажаним.
Див. також L<virt-sysprep(1)>.
=head2 ШВИДКОДІЯ
-Найважливішим аспектом пришвидшення роботи програми є кешування. Шаблон
-завантажується до кешу, коли його вперше використовують, або якщо було
-використано параметр команди I<--cache-all-templates>. Докладніше про це у
-розділі L</КЕШУВАННЯ> вище.
-
-Пакунки, потрібні для виконання завдань із параметрами I<--install> та
-I<--update>, отримуються за допомогою з'єднання з мережею основної
-системи. Встановлення значень змінних середовища C<http_proxy>,
-C<https_proxy> та C<ftp_proxy> таким чином, щоб вони вказували на локальний
-кеш, може забезпечити режим, за якого ці пакунки отримуватимуться із
-інтернету лише один раз. Ви також можете спробувати скористатися локальним
-сховищем пакунків, хоча налаштовування такого сховища може бути складною
-справою, специфічною для того дистрибутива Linux, який ви намагаєтеся
-встановити.
+Найважливішим аспектом пришвидшення роботи програми є кешування. Шаблон завантажується до кешу, коли його вперше використовують, або якщо було використано параметр команди I<--cache-all-templates>. Докладніше про це у розділі L</КЕШУВАННЯ> вище.
+
+Пакунки, потрібні для виконання завдань із параметрами I<--install> та I<--update>, отримуються за допомогою з'єднання з мережею основної системи. Встановлення значень змінних середовища C<http_proxy>, C<https_proxy> та C<ftp_proxy> таким чином, щоб вони вказували на локальний кеш, може забезпечити режим, за якого ці пакунки отримуватимуться із інтернету лише один раз. Ви також можете спробувати скористатися локальним сховищем пакунків, хоча налаштовування такого сховища може бути складною справою, специфічною для того дистрибутива Linux, який ви намагаєтеся встановити.
=head3 Користування I<--no-sync>
-Скористайтеся I<--no-sync>. Втім, ознайомтеся із можливими проблемами,
-описаними у розділі L</ПАРАМЕТРИ> вище, оскільки це може призвести до
-пошкодження даних на диску, якщо використовувати неправильно.
+Скористайтеся I<--no-sync>. Втім, ознайомтеся із можливими проблемами, описаними у розділі L</ПАРАМЕТРИ> вище, оскільки це може призвести до пошкодження даних на диску, якщо використовувати неправильно.
=head3 Пропускання virt-resize
-За певних умов virt-builder може пропускати крок virt-resize. Це значно
-пришвидшує роботу virt-builder. Умови пропускання є такими:
+За певних умов virt-builder може пропускати крок virt-resize. Це значно пришвидшує роботу virt-builder. Умови пропускання є такими:
=over 4
=head3 pxzcat
-Virt-builder використовує внутрішню реалізацію pxzcat (паралельного xzcat),
-якщо під час збирання програми було знайдено liblzma. Якщо liblzma не було
-знайдено під час збирання, використовуватиметься звичайний C<xzcat>, який
-працює у один потік.
-
-=head3 User-Mode Linux
-
-Ви можете використовувати virt-builder у поєднанні з модулем User-Mode Linux
-(UML). У такому режимі програма може працювати швидше, якщо virt-builder
-запущено у віртуальній машині (наприклад у хмарі).
-
-Щоб увімкнути модуль UML, ознайомтеся із настановами у розділі
-L<guestfs(3)/USER-MODE LINUX BACKEND>.
-
-У поточній версії вам слід користуватися параметром I<--no-network>. Це буде
-виправлено у майбутній версії.
-
-Підтримки формату виведення результатів qcow2 у UML не передбачено. Ви
-можете створювати гостьові системи лише у форматі raw.
+Virt-builder використовує внутрішню реалізацію pxzcat (паралельного xzcat), якщо під час збирання програми було знайдено liblzma. Якщо liblzma не було знайдено під час збирання, використовуватиметься звичайний C<xzcat>, який працює у один потік.
=head2 SELINUX
-Гостьові системи, у яких використовується SELinux (зокрема Fedora і Red Hat
-Enterprise Linux) потребують коректної мітки SELinux для кожного файла.
+Гостьові системи, у яких використовується SELinux (зокрема Fedora і Red Hat Enterprise Linux) потребують коректної мітки SELinux для кожного файла.
-Virt-builder не може знайти про спосіб, у який новим файлам надаються
-мітки. Тому існує дві можливі стратегії, використання яких забезпечує
-встановлення належних міток:
+Virt-builder не може знайти про спосіб, у який новим файлам надаються мітки. Тому існує дві можливі стратегії, використання яких забезпечує встановлення належних міток:
=over 4
=item Користування I<--selinux-relabel>
-Запуск L<setfiles(8)> безпосередньо перед завершенням збирання образу
-гостьової системи для встановлення належних міток SELinux на образі диска.
+Запуск L<setfiles(8)> безпосередньо перед завершенням збирання образу гостьової системи для встановлення належних міток SELinux на образі диска.
Це рекомендований метод.
=item I<--touch> F</.autorelabel>
-Наявність у гостьовій системі файла із назвою F</.autorelabel> або можливе
-його створення.
+Наявність у гостьовій системі файла із назвою F</.autorelabel> або можливе його створення.
-У гостьових системах, де використовується SELinux, це спричиняє запуск
-L<restorecon(8)> під час першого завантаження. Гостьові системи самостійно
-перезавантажуються під час першого використання — це нормальна і нешкідлива
-поведінка.
+У гостьових системах, де використовується SELinux, це спричиняє запуск L<restorecon(8)> під час першого завантаження. Гостьові системи самостійно перезавантажуються під час першого використання — це нормальна і нешкідлива поведінка.
=back
-Будь ласка, зауважте, що якщо у вашій гостьовій системі використовується
-SELinux, і ви виконуєте над цією системою дії, які можуть призвести до
-створення файлів або внесення змін до наявних файлів, варто скористатися
-I<--selinux-relabel>. Так можна забезпечити встановлення належних міток
-SELinux для цих файлів.
+Будь ласка, зауважте, що якщо у вашій гостьовій системі використовується SELinux, і ви виконуєте над цією системою дії, які можуть призвести до створення файлів або внесення змін до наявних файлів, варто скористатися I<--selinux-relabel>. Так можна забезпечити встановлення належних міток SELinux для цих файлів.
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-builder з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-builder з інших програм, графічних інтерфейсів тощо.
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-builder. Типово виведені дані виглядатимуть якось
-так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-builder. Типово виведені дані виглядатимуть якось так:
$ virt-builder --machine-readable
virt-builder
json-list
pxzcat
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 ЗМІННІ СЕРЕДОВИЩА
-Опис інших змінних середовища, які стосуються усіх програм libguestfs,
-наведено у розділі L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
+Опис інших змінних середовища, які стосуються усіх програм libguestfs, наведено у розділі L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
=over 4
=item C<no_proxy>
-Встановити проксі-сервер для отримання даних. Ці змінні середовища (та інші)
-насправді обробляються L<curl(1)>, а не virt-builder.
+Встановити проксі-сервер для отримання даних. Ці змінні середовища (та інші) насправді обробляються L<curl(1)>, а не virt-builder.
=item C<HOME>
-Використовується для визначення місця кешу шаблонів та місця джерел
-користувача. Див. L</КЕШУВАННЯ> і L</ДЖЕРЕЛА ШАБЛОНІВ>.
+Використовується для визначення місця кешу шаблонів та місця джерел користувача. Див. L</КЕШУВАННЯ> і L</ДЖЕРЕЛА ШАБЛОНІВ>.
=item C<VIRT_TOOLS_DATA_DIR>
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-F</usr/share/virt-tools>).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на F</usr/share/virt-tools>).
Цей каталог може містити такі файли:
=item F<rhsrvany.exe>
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і
-I<--firstboot-command> для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
Див. також C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-Це виконуваний файл Windows, що постачається разом із VMDP SUSE,
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-I<--firstboot> і I<--firstboot-command> для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із VMDP SUSE, використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
=back
=item C<XDG_CONFIG_HOME>
-Використовується для визначення місця джерел користувача. Див. L</ДЖЕРЕЛА
-ШАБЛОНІВ>.
+Використовується для визначення місця джерел користувача. Див. L</ДЖЕРЕЛА ШАБЛОНІВ>.
=item C<VIRT_BUILDER_DIRS>
-Використовується для визначення місця джерел системи. Див. L</ДЖЕРЕЛА
-ШАБЛОНІВ>.
+Використовується для визначення місця джерел системи. Див. L</ДЖЕРЕЛА ШАБЛОНІВ>.
=back
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>,
-L<virt-builder-repository(1)>, L<virt-copy-out(1)>, L<virt-customize(1)>,
-L<virt-get-kernel(1)>, L<virt-install(1)>, L<virt-rescue(1)>,
-L<virt-resize(1)>, L<virt-sysprep(1)>, L<oz-install(1)>, L<gpg(1)>,
-L<gpg2(1)>, L<curl(1)>, L<virt-make-fs(1)>, L<genisoimage(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-builder-repository(1)>, L<virt-copy-out(1)>, L<virt-customize(1)>, L<virt-get-kernel(1)>, L<virt-install(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sysprep(1)>, L<oz-install(1)>, L<gpg(1)>, L<gpg2(1)>, L<curl(1)>, L<virt-make-fs(1)>, L<genisoimage(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-cat 1"
-.TH virt-cat 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-cat 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-cat\*(C'\fR — інструмент командного рядка для показу вмісту \f(CW\*(C`файла\*(C'\fR, який
-зберігається у вказаній віртуальній машині (або образі диска).
+\&\f(CW\*(C`virt\-cat\*(C'\fR — інструмент командного рядка для показу вмісту \f(CW\*(C`файла\*(C'\fR, який зберігається у вказаній віртуальній машині (або образі диска).
.PP
-Ви можете вказати декілька назв файлів. Вміст таких файлів буде
-об’єднано. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи
-з кореневого каталогу (тобто назва має починатися з «/»).
+Ви можете вказати декілька назв файлів. Вміст таких файлів буде об’єднано. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи з кореневого каталогу (тобто назва має починатися з «/»).
.PP
-\&\f(CW\*(C`virt\-cat\*(C'\fR можна скористатися для пришвидшення перегляду файла. Для
-редагування даних слід користуватися \f(CW\*(C`virt\-edit\*(C'\fR. Для виконання складніших
-дій можна скористатися програмою \fBguestfish\fR\|(1) (див. \*(L"ВИКОРИСТАННЯ
-\&\s-1GUESTFISH\*(R"\s0 нижче).
+\&\f(CW\*(C`virt\-cat\*(C'\fR можна скористатися для пришвидшення перегляду файла. Для редагування даних слід користуватися \f(CW\*(C`virt\-edit\*(C'\fR. Для виконання складніших дій можна скористатися програмою \fBguestfish\fR\|(1) (див. \*(L"ВИКОРИСТАННЯ \s-1GUESTFISH\*(R"\s0 нижче).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
-Показати вміст файл \fI/etc/fstab\fR у віртуальній машині libvirt з назвою
-\&\f(CW\*(C`mydomain\*(C'\fR:
+Показати вміст файл \fI/etc/fstab\fR у віртуальній машині libvirt з назвою \f(CW\*(C`mydomain\*(C'\fR:
.PP
.Vb 1
\& virt\-cat \-d mydomain /etc/fstab
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a адреса\fR" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-cat попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-cat попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-cat \-\-format=raw \-a disk.img file
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-cat \-\-format=raw \-a disk.img \-\-format \-a another.img file
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.Sp
Якщо точку монтування не вказано, типовим значенням є \fI/\fR.
.Sp
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
.Sp
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-\&\*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися
-програмою \fBvirt\-filesystems\fR\|(1).
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися програмою \fBvirt\-filesystems\fR\|(1).
.Sp
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант
-використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Ve
.Sp
-Використання цього прапорця є еквівалентним до використання команди
-\&\f(CW\*(C`mount\-options\*(C'\fR.
+Використання цього прапорця є еквівалентним до використання команди \f(CW\*(C`mount\-options\*(C'\fR.
.Sp
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR
-і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
\& virt\-cat назва_гостьової_системи файл
.Ve
.PP
-тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
.PP
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
.SH "ФАЙЛИ ЖУРНАЛІВ"
.IX Header "ФАЙЛИ ЖУРНАЛІВ"
-Щоб отримати список файлів журналів у гостьових системах, скористайтеся
-відповідним інструментом — \fBvirt\-log\fR\|(1). Ця програма може обробляти
-журнали у двійкових форматах, зокрема журнал systemd.
+Щоб отримати список файлів журналів у гостьових системах, скористайтеся відповідним інструментом — \fBvirt\-log\fR\|(1). Ця програма може обробляти журнали у двійкових форматах, зокрема журнал systemd.
.PP
-Для стеження за вмістом (хвостом) файлів журналу скористайтеся
-\&\fBvirt\-tail\fR\|(1).
+Для стеження за вмістом (хвостом) файлів журналу скористайтеся \fBvirt\-tail\fR\|(1).
.SH "ШЛЯХИ У WINDOWS"
.IX Header "ШЛЯХИ У WINDOWS"
-У \f(CW\*(C`virt\-cat\*(C'\fR передбачено обмежені можливості щодо обробки літерних дисків
-та шляхів у Windows (наприклад \fIE:\efoo\ebar.txt\fR).
+У \f(CW\*(C`virt\-cat\*(C'\fR передбачено обмежені можливості щодо обробки літерних дисків та шляхів у Windows (наприклад \fIE:\efoo\ebar.txt\fR).
.PP
Тоді і лише тоді, коли у гостьовій системі працює Windows:
.IP "\(bu" 4
-Літери дисків, наприклад \f(CW\*(C`C:\*(C'\fR, замінюються на адреси відповідних файлових
-систем на основі даних з регістру Windows.
+Літери дисків, наприклад \f(CW\*(C`C:\*(C'\fR, замінюються на адреси відповідних файлових систем на основі даних з регістру Windows.
.IP "\(bu" 4
-Усі символи зворотної похилої риски (\f(CW\*(C`\e\*(C'\fR) у шляху замінюються символами
-звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
+Усі символи зворотної похилої риски (\f(CW\*(C`\e\*(C'\fR) у шляху замінюються символами звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
.IP "\(bu" 4
-Шлях до файла, вміст якого має бути показано, визначається без врахування
-регістру символів у його записі.
+Шлях до файла, вміст якого має бути показано, визначається без врахування регістру символів у його записі.
.PP
Відомі певні недоліки програми:
.IP "\(bu" 4
-Перехід за деякими символічними посиланнями \s-1NTFS\s0 може здійснюватися з
-помилками.
+Перехід за деякими символічними посиланнями \s-1NTFS\s0 може здійснюватися з помилками.
.IP "\(bu" 4
-Точки з'єднання \s-1NTFS,\s0 які виходять за межі однією файлової системи
-використовувати не можна.
+Точки з'єднання \s-1NTFS,\s0 які виходять за межі однією файлової системи використовувати не можна.
.SH "ВИКОРИСТАННЯ GUESTFISH"
.IX Header "ВИКОРИСТАННЯ GUESTFISH"
-\&\fBguestfish\fR\|(1) є потужнішим інструментом нижчого рівня, яким можна
-скористатися, якщо \f(CW\*(C`virt\-cat\*(C'\fR не працює.
+\&\fBguestfish\fR\|(1) є потужнішим інструментом нижчого рівня, яким можна скористатися, якщо \f(CW\*(C`virt\-cat\*(C'\fR не працює.
.PP
Використання \f(CW\*(C`virt\-cat\*(C'\fR є приблизним еквівалентом такого:
.PP
\& guestfish \-\-ro \-i \-d назва_домену download файл \-
.Ve
.PP
-де \f(CW\*(C`назва_домену\*(C'\fR — назва гостьової системи libvirt, а \f(CW\*(C`файл\*(C'\fR — шлях до
-файла повністю. Зауважте, що кінцеве \f(CW\*(C`\-\*(C'\fR означає «вивести дані до
-стандартного виведення».
+де \f(CW\*(C`назва_домену\*(C'\fR — назва гостьової системи libvirt, а \f(CW\*(C`файл\*(C'\fR — шлях до файла повністю. Зауважте, що кінцеве \f(CW\*(C`\-\*(C'\fR означає «вивести дані до стандартного виведення».
.PP
-У вказаній вище команді використано можливість інспектування гостьових
-систем засобами libguestfs, отже, вона не працюватиме у гостьових системах,
-які libguestfs не може інспектувати, або у довільних образах дисків, які не
-містять гостьових систем. Щоб отримати дані файла безпосередньо з образу
-диска, скористайтеся такою командою:
+У вказаній вище команді використано можливість інспектування гостьових систем засобами libguestfs, отже, вона не працюватиме у гостьових системах, які libguestfs не може інспектувати, або у довільних образах дисків, які не містять гостьових систем. Щоб отримати дані файла безпосередньо з образу диска, скористайтеся такою командою:
.PP
.Vb 1
\& guestfish \-\-ro \-a диск.img \-m /dev/sda1 download файл \-
.Ve
.PP
-де \fIдиск.img\fR — образ диска, \fI/dev/sda1\fR — файлова система у образі диска,
-а \f(CW\*(C`файл\*(C'\fR — шлях до файла повністю.
+де \fIдиск.img\fR — образ диска, \fI/dev/sda1\fR — файлова система у образі диска, а \f(CW\*(C`файл\*(C'\fR — шлях до файла повністю.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-edit\fR\|(1),
-\&\fBvirt\-log\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-edit\fR\|(1), \fBvirt\-log\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-C<virt-cat> — інструмент командного рядка для показу вмісту C<файла>, який
-зберігається у вказаній віртуальній машині (або образі диска).
+C<virt-cat> — інструмент командного рядка для показу вмісту C<файла>, який зберігається у вказаній віртуальній машині (або образі диска).
-Ви можете вказати декілька назв файлів. Вміст таких файлів буде
-об’єднано. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи
-з кореневого каталогу (тобто назва має починатися з «/»).
+Ви можете вказати декілька назв файлів. Вміст таких файлів буде об’єднано. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи з кореневого каталогу (тобто назва має починатися з «/»).
-C<virt-cat> можна скористатися для пришвидшення перегляду файла. Для
-редагування даних слід користуватися C<virt-edit>. Для виконання складніших
-дій можна скористатися програмою L<guestfish(1)> (див. L</ВИКОРИСТАННЯ
-GUESTFISH> нижче).
+C<virt-cat> можна скористатися для пришвидшення перегляду файла. Для редагування даних слід користуватися C<virt-edit>. Для виконання складніших дій можна скористатися програмою L<guestfish(1)> (див. L</ВИКОРИСТАННЯ GUESTFISH> нижче).
=head1 ПРИКЛАДИ
-Показати вміст файл F</etc/fstab> у віртуальній машині libvirt з назвою
-C<mydomain>:
+Показати вміст файл F</etc/fstab> у віртуальній машині libvirt з назвою C<mydomain>:
virt-cat -d mydomain /etc/fstab
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-cat попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-cat попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-cat --format=raw -a disk.img file
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-cat --format=raw -a disk.img --format -a another.img file
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
Якщо точку монтування не вказано, типовим значенням є F</>.
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
-
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися
-програмою L<virt-filesystems(1)>.
-
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або C<ro> (другий варіант
-використовується, якщо використано прапорець I<--ro>). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
+
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися програмою L<virt-filesystems(1)>.
+
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або C<ro> (другий варіант використовується, якщо використано прапорець I<--ro>). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
-m /dev/sda1:/:acl,user_xattr
-Використання цього прапорця є еквівалентним до використання команди
-C<mount-options>.
+Використання цього прапорця є еквівалентним до використання команди C<mount-options>.
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: C<ext2>
-і C<ext3>), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: C<ext2> і C<ext3>), або libguestfs визначає файлову систему помилково.
=item B<-v>
virt-cat назва_гостьової_системи файл
-тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
=head1 ФАЙЛИ ЖУРНАЛІВ
-Щоб отримати список файлів журналів у гостьових системах, скористайтеся
-відповідним інструментом — L<virt-log(1)>. Ця програма може обробляти
-журнали у двійкових форматах, зокрема журнал systemd.
+Щоб отримати список файлів журналів у гостьових системах, скористайтеся відповідним інструментом — L<virt-log(1)>. Ця програма може обробляти журнали у двійкових форматах, зокрема журнал systemd.
-Для стеження за вмістом (хвостом) файлів журналу скористайтеся
-L<virt-tail(1)>.
+Для стеження за вмістом (хвостом) файлів журналу скористайтеся L<virt-tail(1)>.
=head1 ШЛЯХИ У WINDOWS
-У C<virt-cat> передбачено обмежені можливості щодо обробки літерних дисків
-та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
+У C<virt-cat> передбачено обмежені можливості щодо обробки літерних дисків та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
Тоді і лише тоді, коли у гостьовій системі працює Windows:
=item *
-Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових
-систем на основі даних з регістру Windows.
+Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових систем на основі даних з регістру Windows.
=item *
-Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами
-звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
+Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
=item *
-Шлях до файла, вміст якого має бути показано, визначається без врахування
-регістру символів у його записі.
+Шлях до файла, вміст якого має бути показано, визначається без врахування регістру символів у його записі.
=back
=item *
-Перехід за деякими символічними посиланнями NTFS може здійснюватися з
-помилками.
+Перехід за деякими символічними посиланнями NTFS може здійснюватися з помилками.
=item *
-Точки з'єднання NTFS, які виходять за межі однією файлової системи
-використовувати не можна.
+Точки з'єднання NTFS, які виходять за межі однією файлової системи використовувати не можна.
=back
=head1 ВИКОРИСТАННЯ GUESTFISH
-L<guestfish(1)> є потужнішим інструментом нижчого рівня, яким можна
-скористатися, якщо C<virt-cat> не працює.
+L<guestfish(1)> є потужнішим інструментом нижчого рівня, яким можна скористатися, якщо C<virt-cat> не працює.
Використання C<virt-cat> є приблизним еквівалентом такого:
guestfish --ro -i -d назва_домену download файл -
-де C<назва_домену> — назва гостьової системи libvirt, а C<файл> — шлях до
-файла повністю. Зауважте, що кінцеве C<-> означає «вивести дані до
-стандартного виведення».
+де C<назва_домену> — назва гостьової системи libvirt, а C<файл> — шлях до файла повністю. Зауважте, що кінцеве C<-> означає «вивести дані до стандартного виведення».
-У вказаній вище команді використано можливість інспектування гостьових
-систем засобами libguestfs, отже, вона не працюватиме у гостьових системах,
-які libguestfs не може інспектувати, або у довільних образах дисків, які не
-містять гостьових систем. Щоб отримати дані файла безпосередньо з образу
-диска, скористайтеся такою командою:
+У вказаній вище команді використано можливість інспектування гостьових систем засобами libguestfs, отже, вона не працюватиме у гостьових системах, які libguestfs не може інспектувати, або у довільних образах дисків, які не містять гостьових систем. Щоб отримати дані файла безпосередньо з образу диска, скористайтеся такою командою:
guestfish --ro -a диск.img -m /dev/sda1 download файл -
-де F<диск.img> — образ диска, F</dev/sda1> — файлова система у образі диска,
-а C<файл> — шлях до файла повністю.
+де F<диск.img> — образ диска, F</dev/sda1> — файлова система у образі диска, а C<файл> — шлях до файла повністю.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-edit(1)>,
-L<virt-log(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-edit(1)>, L<virt-log(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-customize 1"
-.TH virt-customize 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-customize 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-За допомогою virt-customize можна налаштувати віртуальну машину (образ
-диска) встановленням пакунків, редагуванням файлів налаштувань тощо.
+За допомогою virt-customize можна налаштувати віртуальну машину (образ диска) встановленням пакунків, редагуванням файлів налаштувань тощо.
.PP
-Virt-customize вносить зміни до гостьової системи або образу диска \fIна
-місці\fR. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний
-вміст гостьової системи, \fIвам слід спочатку зробити її знімок, скопіювати
-або клонувати її диск\fR.
+Virt-customize вносить зміни до гостьової системи або образу диска \fIна місці\fR. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний вміст гостьової системи, \fIвам слід спочатку зробити її знімок, скопіювати або клонувати її диск\fR.
.PP
-Вам \fIне потрібно\fR запускати virt-customize від імені користувача
-root. Фактично, запуск у такому режимі є нерекомендованим.
+Вам \fIне потрібно\fR запускати virt-customize від імені користувача root. Фактично, запуск у такому режимі є нерекомендованим.
.PP
Пов'язані інструменти: \fBvirt\-sysprep\fR\|(1) і \fBvirt\-builder\fR\|(1).
.SH "ПАРАМЕТРИ"
.PD
Додати \fIфайл\fR, який має бути образом диска з віртуальної машини.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-add\fR адреса" 4
.IX Item "--add адреса"
.PD
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
.IP "\fB\-\-attach\fR ФАЙЛ_ISO" 4
.IX Item "--attach ФАЙЛ_ISO"
-Вказаний диск долучається до базової системи libguestfs. Цей диск
-використовується для отримання даних додаткових сховищ програмного
-забезпечення або інших даних для створення нетипової системи.
+Вказаний диск долучається до базової системи libguestfs. Цей диск використовується для отримання даних додаткових сховищ програмного забезпечення або інших даних для створення нетипової системи.
.Sp
-Ймовірно, вам варто додати мітки для долучених дисків (або скористатися
-назвою тому \s-1ISO\s0), щоб надалі монтувати диски за міткою у ваших скриптах
-запуску:
+Ймовірно, вам варто додати мітки для долучених дисків (або скористатися назвою тому \s-1ISO\s0), щоб надалі монтувати диски за міткою у ваших скриптах запуску:
.Sp
.Vb 2
\& mkdir /tmp/mount
\& mount LABEL=EXTRA /tmp/mount
.Ve
.Sp
-Параметр \fI\-\-attach\fR можна вказати декілька разів, а форматом може бути
-будь\-який формат образу (не лише \s-1ISO\s0).
+Параметр \fI\-\-attach\fR можна вказати декілька разів, а форматом може бути будь\-який формат образу (не лише \s-1ISO\s0).
.IP "\fB\-\-attach\-format\fR ФОРМАТ" 4
.IX Item "--attach-format ФОРМАТ"
-Вказати формат диска для наступного параметра \fI\-\-attach\fR. Значенням
-аргументу \f(CW\*(C`ФОРМАТ\*(C'\fR зазвичай є \f(CW\*(C`raw\*(C'\fR або \f(CW\*(C`qcow2\*(C'\fR. Для образів \s-1ISO\s0
-скористайтеся варіантом \f(CW\*(C`raw\*(C'\fR.
+Вказати формат диска для наступного параметра \fI\-\-attach\fR. Значенням аргументу \f(CW\*(C`ФОРМАТ\*(C'\fR зазвичай є \f(CW\*(C`raw\*(C'\fR або \f(CW\*(C`qcow2\*(C'\fR. Для образів \s-1ISO\s0 скористайтеся варіантом \f(CW\*(C`raw\*(C'\fR.
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-c\fR адреса" 4
.IX Item "-c адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-n\fR" 4
.IX Item "-n"
.PD 0
.IP "\fB\-\-dry\-run\fR" 4
.IX Item "--dry-run"
.PD
-Виконати тестову обробку гостьової системи у режимі «лише читання». Буде
-виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
+Виконати тестову обробку гостьової системи у режимі «лише читання». Буде виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-customize попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-customize попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format auto\fR перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format auto\fR перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-customize \-\-format raw \-a диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-customize \-\-format raw \-a диск.img \-\-format auto \-a іще_диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IP "\fB\-\-memsize\fR МБ" 4
.IX Item "--memsize МБ"
.PD
-Зміна обсягу пам'яті, наданого скриптам \fI\-\-run\fR. Збільште це значення, якщо
-виявиться, що для використання скриптів \fI\-\-run\fR або параметра \fI\-\-install\fR
-не вистачає пам'яті.
+Зміна обсягу пам'яті, наданого скриптам \fI\-\-run\fR. Збільште це значення, якщо виявиться, що для використання скриптів \fI\-\-run\fR або параметра \fI\-\-install\fR не вистачає пам'яті.
.Sp
Типові значення можна визначити за допомогою такої команди:
.Sp
.IP "\fB\-\-no\-network\fR" 4
.IX Item "--no-network"
.PD
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
.Sp
-Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути доступ.
.Sp
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
.Sp
-Якщо ви скористаєтеся параметром \fI\-\-no\-network\fR, тоді інші параметри,
-зокрема \fI\-\-install\fR, не працюватимуть.
+Якщо ви скористаєтеся параметром \fI\-\-no\-network\fR, тоді інші параметри, зокрема \fI\-\-install\fR, не працюватимуть.
.Sp
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-customize.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-customize.
.Sp
-Загалом кажучи, вам \fIне варто\fR використовувати \fI\-\-no\-network\fR. Але ось
-декілька випадків, коли у вас може виникнути потреба у використанні цього
-параметра:
+Загалом кажучи, вам \fIне варто\fR використовувати \fI\-\-no\-network\fR. Але ось декілька випадків, коли у вас може виникнути потреба у використанні цього параметра:
.RS 4
.IP "1." 4
-У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки
-мережі. (Див. \*(L"МОДУЛЬ\*(R" in \fBguestfs\fR\|(3)).
+У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки мережі. (Див. \*(L"МОДУЛЬ\*(R" in \fBguestfs\fR\|(3)).
.IP "2." 4
-Усе програмне забезпечення, яке ви маєте намір встановити, походить з
-долученого образу \s-1ISO,\s0 отже потреби у мережі немає.
+Усе програмне забезпечення, яке ви маєте намір встановити, походить з долученого образу \s-1ISO,\s0 отже потреби у мережі немає.
.IP "3." 4
-Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати
-доступ до мережевого з'єднання вашої основної системи під час роботи
-virt-customize. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу
-шаблонів операційних систем. (Див. \*(L"БЕЗПЕКА\*(R" нижче).
+Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати доступ до мережевого з'єднання вашої основної системи під час роботи virt-customize. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу шаблонів операційних систем. (Див. \*(L"БЕЗПЕКА\*(R" нижче).
.IP "4." 4
-Ви не хочете користуватися мережею основної системи (наприклад, через
-захищеність або обмеженість середовища у ній).
+Ви не хочете користуватися мережею основної системи (наприклад, через захищеність або обмеженість середовища у ній).
.RE
.RS 4
.RE
.PD
Не виводити повідомлення до журналу.
.Sp
-Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся
-\&\fI\-x\fR.
+Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся \fI\-x\fR.
.IP "\fB\-\-smp\fR N" 4
.IX Item "--smp N"
-Увімкнути N ≥ 2 віртуальних процесорів для використання у скриптах
-\&\fI\-\-run\fR.
+Увімкнути N ≥ 2 віртуальних процесорів для використання у скриптах \fI\-\-run\fR.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.IX Subsection "Параметри налаштовування"
.IP "\fB\-\-append\-line\fR ФАЙЛ:РЯДОК" 4
.IX Item "--append-line ФАЙЛ:РЯДОК"
-Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується
-порожнім рядком, такий рядок буде додано перед дописаним. Крім того,
-автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
+Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується порожнім рядком, такий рядок буде додано перед дописаним. Крім того, автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
.Sp
-Наприклад, (припускаємо, що у командній оболонці використовуються звичайні
-лапки) така команда:
+Наприклад, (припускаємо, що у командній оболонці використовуються звичайні лапки) така команда:
.Sp
.Vb 1
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде
-додано, лише якщо наявний файл ще не закінчується символом нового рядка.
+додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде додано, лише якщо наявний файл ще не закінчується символом нового рядка.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за
-наявним вмістом файла, отже, команда обробляє файли однаково правильно для
-варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для
-порожніх і ще не створених файлів.
+\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за наявним вмістом файла, отже, команда обробляє файли однаково правильно для варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для порожніх і ще не створених файлів.
.Sp
-Щоб додати декілька рядків, скористайтеся тим самим параметром декілька
-разів:
+Щоб додати декілька рядків, скористайтеся тим самим параметром декілька разів:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.2 bar\*(Aq
.Ve
.Sp
-Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою
-конструкцією:
+Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою конструкцією:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:\*(Aq
.IX Item "--chmod ПРАВА_ДОСТУПУ:ФАЙЛ"
Змінити права доступу до файла \f(CW\*(C`ФАЙЛ\*(C'\fR на \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR.
.Sp
-\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі,
-якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто
-скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
+\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі, якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
.IP "\fB\-\-commands\-from\-file\fR НАЗВА_ФАЙЛА" 4
.IX Item "--commands-from-file НАЗВА_ФАЙЛА"
-Прочитати команди налаштовування з файла, по одній (разом із аргументами) на
-рядок.
+Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.
.Sp
Кожен рядок містить команду налаштовування та її аргументи, наприклад:
.Sp
\& password якийсь\-користувач:password:його\-новий\-пароль
.Ve
.Sp
-Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і
-також ігноруються. Крім того, аргументи можна розділити на декілька рядків
-додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
+Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і також ігноруються. Крім того, аргументи можна розділити на декілька рядків додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
.Sp
.Vb 2
\& edit /якийсь/файл:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так,
-наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
+Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так, наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
.IP "\fB\-\-copy\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ" 4
.IX Item "--copy ДЖЕРЕЛО:ПРИЗНАЧЕННЯ"
Копіювати файли або каталоги рекурсивно у межах гостьової системи.
Не можна використовувати символи\-замінники.
.IP "\fB\-\-copy\-in\fR ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ" 4
.IX Item "--copy-in ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ"
-Скопіювати локальні файли або каталоги рекурсивно до образу диска,
-розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
+Скопіювати локальні файли або каталоги рекурсивно до образу диска, розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
.Sp
Не можна використовувати символи\-замінники.
.IP "\fB\-\-delete\fR ШЛЯХ" 4
.IX Item "--delete ШЛЯХ"
-Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
-рекурсивно).
+Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст, рекурсивно).
.Sp
-Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте
-екранувати символи\-замінники у командній оболонці основної системи, якщо це
-потрібно. Приклад:
+Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте екранувати символи\-замінники у командній оболонці основної системи, якщо це потрібно. Приклад:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
.IX Item "--edit ФАЙЛ:ВИРАЗ"
Редагувати \f(CW\*(C`ФАЙЛ\*(C'\fR з використанням виразу Perl \f(CW\*(C`ВИРАЗ\*(C'\fR.
.Sp
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
.Sp
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
.Sp
Див. \*(L"NON-INTERACTIVE \s-1EDITING\*(R"\s0 in \fBvirt\-edit\fR\|(1).
.IP "\fB\-\-firstboot\fR СКРИПТ" 4
.IX Item "--firstboot СКРИПТ"
-Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-До скрипту, після встановлення до гостьової системи, буде автоматично
-застосовано команду chmod +x.
+До скрипту, після встановлення до гостьової системи, буде автоматично застосовано команду chmod +x.
.Sp
-Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно
-включає команду у однорядковому скрипті.
+Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно включає команду у однорядковому скрипті.
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-command\fR 'КОМАНДА+ПАРАМЕТРИ'" 4
.IX Item "--firstboot-command 'КОМАНДА+ПАРАМЕТРИ'"
-Виконати команду (разом із аргументами) у гостьовій системі під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Виконати команду (разом із аргументами) у гостьовій системі під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.IP "\fB\-\-firstboot\-install\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--firstboot-install ПАКУНОК,ПАКУНОК.."
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час першого завантаження гостьової системи за
-допомогою програми для керування пакунків гостьової системи (наприклад, apt,
-yum тощо) і з'єднання із мережею гостьової системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час першого завантаження гостьової системи за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею гостьової системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
.IP "\fB\-\-hostname\fR НАЗВА_ВУЗЛА" 4
.IX Item "--hostname НАЗВА_ВУЗЛА"
-Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо
-потрібно, можете скористатися форматом із крапкою,
-«назва_вузла.назва_домену» (\s-1FQDN\s0).
+Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо потрібно, можете скористатися форматом із крапкою, «назва_вузла.назва_домену» (\s-1FQDN\s0).
.IP "\fB\-\-install\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--install ПАКУНОК,ПАКУНОК.."
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання
-із мережею основної системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею основної системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
.Sp
Див. також \fI\-\-update\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-link\fR ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..]" 4
.IX Item "--link ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..]"
-Створити символічне посилання або декілька посилань у гостьовій системі так,
-щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
+Створити символічне посилання або декілька посилань у гостьовій системі так, щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
.IP "\fB\-\-mkdir\fR КАТАЛОГ" 4
.IX Item "--mkdir КАТАЛОГ"
Створити каталог у гостьовій системі.
.Sp
-Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні
-каталоги. Також команда працює, якщо каталог вже існує.
+Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні каталоги. Також команда працює, якщо каталог вже існує.
.IP "\fB\-\-move\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ" 4
.IX Item "--move ДЖЕРЕЛО:ПРИЗНАЧЕННЯ"
Пересунути файли або каталоги у межах гостьової системи.
Не можна використовувати символи\-замінники.
.IP "\fB\-\-no\-logfile\fR" 4
.IX Item "--no-logfile"
-Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після
-завершення збирання. Якщо ви не хочете явним чином показувати, як було
-зібрано образ, скористайтеся цим параметром.
+Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після завершення збирання. Якщо ви не хочете явним чином показувати, як було зібрано образ, скористайтеся цим параметром.
.Sp
Див. також \*(L"\s-1LOG FILE\*(R"\s0.
.IP "\fB\-\-password\fR КОРИСТУВАЧ:ВАРІАНТ" 4
.IX Item "--password КОРИСТУВАЧ:ВАРІАНТ"
-Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою
-цього параметра \fIне можна\fR створювати облікові записи користувачів.)
+Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою цього параметра \fIне можна\fR створювати облікові записи користувачів.)
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
.IP "\fB\-\-password\-crypto\fR md5|sha256|sha512" 4
.IX Item "--password-crypto md5|sha256|sha512"
-Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою
-цього параметра можна встановити шифрування для цього пароля у значення
-\&\f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
-.Sp
-Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc
-≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
-.Sp
-\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux
-(наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
-.Sp
-Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо
-libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо
-такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою
-цього параметра ви можете перевизначити автоматично визначений libguestfs
-спосіб шифрування.
-.Sp
-Зауважте, що це не змінить типового шифрування, яке використовується
-гостьовою системою, коли ви створюєте у ній нові облікові записи
-користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися
-параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR
-(Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
+Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою цього параметра можна встановити шифрування для цього пароля у значення \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
+.Sp
+Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc ≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
+.Sp
+\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux (наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
+.Sp
+Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою цього параметра ви можете перевизначити автоматично визначений libguestfs спосіб шифрування.
+.Sp
+Зауважте, що це не змінить типового шифрування, яке використовується гостьовою системою, коли ви створюєте у ній нові облікові записи користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.IP "\fB\-\-root\-password\fR ВАРІАНТ" 4
.IX Item "--root-password ВАРІАНТ"
Встановити пароль користувача root.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
.Sp
-Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для
-гостьової системи буде використано \fIвипадковий\fR пароль root.
+Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для гостьової системи буде використано \fIвипадковий\fR пароль root.
.IP "\fB\-\-run\fR СКРИПТ" 4
.IX Item "--run СКРИПТ"
-Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR
-у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій
-допоміжній системі, у пісочниці гостьової файлової системи.
+Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
Для скрипту буде автоматично використано команду chmod +x.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому
-порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-run\-command\fR 'КОМАНДА+ПАРАМЕТРИ'" 4
.IX Item "--run-command 'КОМАНДА+ПАРАМЕТРИ'"
-Виконати команду із аргументами у образі диска. Команду буде виконано у
-віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової
-файлової системи.
+Виконати команду із аргументами у образі диска. Команду буде виконано у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.IP "\fB\-\-scrub\fR ФАЙЛ" 4
.RE
.IP "\fB\-\-selinux\-relabel\fR" 4
.IX Item "--selinux-relabel"
-Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були
-правильними з точки зору SELinux.
+Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були правильними з точки зору SELinux.
.Sp
-Якщо буде використано цей параметр, програма спробує змінити мітки файлів
-негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла
-\&\fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на
-наступне завантаження образу.
+Якщо буде використано цей параметр, програма спробує змінити мітки файлів негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла \fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на наступне завантаження образу.
.Sp
-Вам слід використовувати цей параметр лише для гостьових систем із
-підтримкою SELinux.
+Вам слід використовувати цей параметр лише для гостьових систем із підтримкою SELinux.
.IP "\fB\-\-sm\-attach\fR ВАРІАНТ" 4
.IX Item "--sm-attach ВАРІАНТ"
Долучити систему до буфера передплати за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
.IP "\fB\-\-sm\-credentials\fR ВАРІАНТ" 4
.IX Item "--sm-credentials ВАРІАНТ"
Встановити реєстраційні дані для \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
.IP "\fB\-\-sm\-register\fR" 4
.IX Item "--sm-register"
Зареєструвати гостьову систему за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
Потребує встановлення реєстраційних даних за допомогою \fI\-\-sm\-credentials\fR.
.IP "\fB\-\-sm\-remove\fR" 4
.IX Item "--sm-remove"
-Вилучити усі передплати з гостьової системи за допомогою
-\&\f(CW\*(C`subscription\-manager\*(C'\fR.
+Вилучити усі передплати з гостьової системи за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-sm\-unregister\fR" 4
.IX Item "--sm-unregister"
Зняти гостьову систему з реєстрації за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ[:ВАРІАНТ]" 4
.IX Item "--ssh-inject КОРИСТУВАЧ[:ВАРІАНТ]"
-Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з
-використанням ssh без потреби у визначенні пароля. Запис користувача
-\&\f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
+Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з використанням ssh без потреби у визначенні пароля. Запис користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
.Sp
Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"КЛЮЧІ \s-1SSH\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.Sp
-Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних
-користувачів, а також для додавання декількох ключів для кожного з
-користувачів.
+Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних користувачів, а також для додавання декількох ключів для кожного з користувачів.
.IP "\fB\-\-timezone\fR ЧАСОВИЙ_ПОЯС" 4
.IX Item "--timezone ЧАСОВИЙ_ПОЯС"
-Встановити типовий часовий пояс гостьової системи у значення
-\&\f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
+Встановити типовий часовий пояс гостьової системи у значення \f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
.IP "\fB\-\-touch\fR ФАЙЛ" 4
.IX Item "--touch ФАЙЛ"
Ця команда виконує подібну до \fBtouch\fR\|(1) дію над файлом \f(CW\*(C`ФАЙЛ\*(C'\fR.
.IP "\fB\-\-truncate\fR ФАЙЛ" 4
.IX Item "--truncate ФАЙЛ"
-Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного
-виконання файл має існувати.
+Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного виконання файл має існувати.
.IP "\fB\-\-truncate\-recursive\fR ШЛЯХ" 4
.IX Item "--truncate-recursive ШЛЯХ"
-Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової
-довжини.
+Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової довжини.
.IP "\fB\-\-uninstall\fR ПАКУНОК,ПАКУНОК.." 4
.IX Item "--uninstall ПАКУНОК,ПАКУНОК.."
-Вилучити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде вилучено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою
-виконання запиту також може бути вилучено пакунки, залежні від вилучених
-пакунків.
+Вилучити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде вилучено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою виконання запиту також може бути вилучено пакунки, залежні від вилучених пакунків.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-update\fR.
.IP "\fB\-\-update\fR" 4
.IX Item "--update"
-Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої
-команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні,
-до найсвіжіших версій.
+Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні, до найсвіжіших версій.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-uninstall\fR.
.IP "\fB\-\-upload\fR ФАЙЛ:ПРИЗНАЧЕННЯ" 4
.IX Item "--upload ФАЙЛ:ПРИЗНАЧЕННЯ"
-Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі
-диска. Буде збережено власника і права доступу, отже вам слід вказати такі
-значення для цих параметрів, які мають бути на остаточному образі диска.
+Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі диска. Буде збережено власника і права доступу, отже вам слід вказати такі значення для цих параметрів, які мають бути на остаточному образі диска.
.Sp
-Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим
-можна скористатися для перейменовування файла під час вивантаження.
+Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим можна скористатися для перейменовування файла під час вивантаження.
.Sp
-Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має
-існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу,
-назву файла з локальної файлової системи буде збережено.
+Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу, назву файла з локальної файлової системи буде збережено.
.Sp
Див. також \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.IP "\fB\-\-write\fR ФАЙЛ:ДАНІ" 4
Записати \f(CW\*(C`ДАНІ\*(C'\fR до файла \f(CW\*(C`ФАЙЛ\*(C'\fR.
.SH "SELINUX"
.IX Header "SELINUX"
-Для гостьових систем, у яких використовується SELinux, може знадобитися
-спеціальна обробка, якщо використовуються дії, які створюють нові файли або
-вносять зміни до наявних файлів.
+Для гостьових систем, у яких використовується SELinux, може знадобитися спеціальна обробка, якщо використовуються дії, які створюють нові файли або вносять зміни до наявних файлів.
.PP
Докладніший опис наведено у розділі \*(L"\s-1SELINUX\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися
-помилки.
+Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися помилки.
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
.Sp
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-\&\fI/usr/share/virt\-tools\fR).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на \fI/usr/share/virt\-tools\fR).
.Sp
Цей каталог може містити такі файли:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і
-\&\fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.Sp
Див. також \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-\&\fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0 використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.RE
.RS 4
.RE
.PP
-Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT
-VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1),
-\&\fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1),
-\&\fBvirt\-sysprep\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1),
-\&\fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirt\-sysprep\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1), \fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
.SH "АВТОРИ"
.IX Header "АВТОРИ"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-За допомогою virt-customize можна налаштувати віртуальну машину (образ
-диска) встановленням пакунків, редагуванням файлів налаштувань тощо.
+За допомогою virt-customize можна налаштувати віртуальну машину (образ диска) встановленням пакунків, редагуванням файлів налаштувань тощо.
-Virt-customize вносить зміни до гостьової системи або образу диска I<на
-місці>. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний
-вміст гостьової системи, I<вам слід спочатку зробити її знімок, скопіювати
-або клонувати її диск>.
+Virt-customize вносить зміни до гостьової системи або образу диска I<на місці>. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний вміст гостьової системи, I<вам слід спочатку зробити її знімок, скопіювати або клонувати її диск>.
-Вам I<не потрібно> запускати virt-customize від імені користувача
-root. Фактично, запуск у такому режимі є нерекомендованим.
+Вам I<не потрібно> запускати virt-customize від імені користувача root. Фактично, запуск у такому режимі є нерекомендованим.
Пов'язані інструменти: L<virt-sysprep(1)> і L<virt-builder(1)>.
Додати I<файл>, який має бути образом диска з віртуальної машини.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром I<--format>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format>.
=item B<-a> адреса
=item B<--add> адреса
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
=item B<--attach> ФАЙЛ_ISO
-Вказаний диск долучається до базової системи libguestfs. Цей диск
-використовується для отримання даних додаткових сховищ програмного
-забезпечення або інших даних для створення нетипової системи.
+Вказаний диск долучається до базової системи libguestfs. Цей диск використовується для отримання даних додаткових сховищ програмного забезпечення або інших даних для створення нетипової системи.
-Ймовірно, вам варто додати мітки для долучених дисків (або скористатися
-назвою тому ISO), щоб надалі монтувати диски за міткою у ваших скриптах
-запуску:
+Ймовірно, вам варто додати мітки для долучених дисків (або скористатися назвою тому ISO), щоб надалі монтувати диски за міткою у ваших скриптах запуску:
mkdir /tmp/mount
mount LABEL=EXTRA /tmp/mount
-Параметр I<--attach> можна вказати декілька разів, а форматом може бути
-будь-який формат образу (не лише ISO).
+Параметр I<--attach> можна вказати декілька разів, а форматом може бути будь-який формат образу (не лише ISO).
=item B<--attach-format> ФОРМАТ
-Вказати формат диска для наступного параметра I<--attach>. Значенням
-аргументу C<ФОРМАТ> зазвичай є C<raw> або C<qcow2>. Для образів ISO
-скористайтеся варіантом C<raw>.
+Вказати формат диска для наступного параметра I<--attach>. Значенням аргументу C<ФОРМАТ> зазвичай є C<raw> або C<qcow2>. Для образів ISO скористайтеся варіантом C<raw>.
=item B<--colors>
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<-c> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<-n>
=item B<--dry-run>
-Виконати тестову обробку гостьової системи у режимі «лише читання». Буде
-виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
+Виконати тестову обробку гостьової системи у режимі «лише читання». Буде виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
=item B<--echo-keys>
-Типово, якщо virt-customize попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-customize попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format auto> перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format auto> перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-customize --format raw -a диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-customize --format raw -a диск.img --format auto -a іще_диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
=item B<--memsize> МБ
-Зміна обсягу пам'яті, наданого скриптам I<--run>. Збільште це значення, якщо
-виявиться, що для використання скриптів I<--run> або параметра I<--install>
-не вистачає пам'яті.
+Зміна обсягу пам'яті, наданого скриптам I<--run>. Збільште це значення, якщо виявиться, що для використання скриптів I<--run> або параметра I<--install> не вистачає пам'яті.
Типові значення можна визначити за допомогою такої команди:
=item B<--no-network>
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
-Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути доступ.
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
-Якщо ви скористаєтеся параметром I<--no-network>, тоді інші параметри,
-зокрема I<--install>, не працюватимуть.
+Якщо ви скористаєтеся параметром I<--no-network>, тоді інші параметри, зокрема I<--install>, не працюватимуть.
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-customize.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-customize.
-Загалом кажучи, вам I<не варто> використовувати I<--no-network>. Але ось
-декілька випадків, коли у вас може виникнути потреба у використанні цього
-параметра:
+Загалом кажучи, вам I<не варто> використовувати I<--no-network>. Але ось декілька випадків, коли у вас може виникнути потреба у використанні цього параметра:
=over 4
=item 1.
-У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки
-мережі. (Див. L<guestfs(3)/МОДУЛЬ>).
+У модулі обробки libguestfs, яким ви користуєтеся, не передбачено підтримки мережі. (Див. L<guestfs(3)/МОДУЛЬ>).
=item 2.
-Усе програмне забезпечення, яке ви маєте намір встановити, походить з
-долученого образу ISO, отже потреби у мережі немає.
+Усе програмне забезпечення, яке ви маєте намір встановити, походить з долученого образу ISO, отже потреби у мережі немає.
=item 3.
-Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати
-доступ до мережевого з'єднання вашої основної системи під час роботи
-virt-customize. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу
-шаблонів операційних систем. (Див. L</БЕЗПЕКА> нижче).
+Ви не хочете, щоб ненадійний код із гостьової системи намагався отримати доступ до мережевого з'єднання вашої основної системи під час роботи virt-customize. Таке, зокрема, може трапитися, якщо ви не довіряєте джерелу шаблонів операційних систем. (Див. L</БЕЗПЕКА> нижче).
=item 4.
-Ви не хочете користуватися мережею основної системи (наприклад, через
-захищеність або обмеженість середовища у ній).
+Ви не хочете користуватися мережею основної системи (наприклад, через захищеність або обмеженість середовища у ній).
=back
Не виводити повідомлення до журналу.
-Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся
-I<-x>.
+Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся I<-x>.
=item B<--smp> N
-Увімкнути N E<ge> 2 віртуальних процесорів для використання у скриптах
-I<--run>.
+Увімкнути N E<ge> 2 віртуальних процесорів для використання у скриптах I<--run>.
=item B<-v>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 SELINUX
-Для гостьових систем, у яких використовується SELinux, може знадобитися
-спеціальна обробка, якщо використовуються дії, які створюють нові файли або
-вносять зміни до наявних файлів.
+Для гостьових систем, у яких використовується SELinux, може знадобитися спеціальна обробка, якщо використовуються дії, які створюють нові файли або вносять зміни до наявних файлів.
Докладніший опис наведено у розділі L<virt-builder(1)/SELINUX>.
=head1 СТАН ВИХОДУ
-Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися
-помилки.
+Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися помилки.
=head1 ЗМІННІ СЕРЕДОВИЩА
=item C<VIRT_TOOLS_DATA_DIR>
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-F</usr/share/virt-tools>).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на F</usr/share/virt-tools>).
Цей каталог може містити такі файли:
=item F<rhsrvany.exe>
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і
-I<--firstboot-command> для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
Див. також C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-Це виконуваний файл Windows, що постачається разом із VMDP SUSE,
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-I<--firstboot> і I<--firstboot-command> для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із VMDP SUSE, використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
=back
=back
-Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT
-VARIABLES>.
+Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT VARIABLES>.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>,
-L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>,
-L<virt-sysprep(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>,
-L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>, L<virt-sysprep(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>, L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
=head1 АВТОРИ
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-df 1"
-.TH virt-df 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-df 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "НАЗВА"
.IX Header "НАЗВА"
-virt-df — програма для показу даних щодо вільного місця на віртуальних
-файлових системах
+virt-df — програма для показу даних щодо вільного місця на віртуальних файлових системах
.SH "КОРОТКИЙ ОПИС"
.IX Header "КОРОТКИЙ ОПИС"
Всі гостьові системи:
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-df\*(C'\fR — інструмент командного рядка для показу вільного місця у
-файлових системах віртуальної машини. На відміну від інших інструментів, він
-не показує розмір диску, який отримано для віртуальної машини, а може
-зазирнути всередину образу диска і визначити, скільки саме місця насправді
-використовується.
+\&\f(CW\*(C`virt\-df\*(C'\fR — інструмент командного рядка для показу вільного місця у файлових системах віртуальної машини. На відміну від інших інструментів, він не показує розмір диску, який отримано для віртуальної машини, а може зазирнути всередину образу диска і визначити, скільки саме місця насправді використовується.
.PP
-Якщо команду віддано без аргументів \fI\-a\fR або \fI\-d\fR, \f(CW\*(C`virt\-df\*(C'\fR отримає від
-libvirt список активних і неактивних гостьових систем і виконає дію типу
-\&\f(CW\*(C`df\*(C'\fR для кожного з них послідовно, а потім виведе результати.
+Якщо команду віддано без аргументів \fI\-a\fR або \fI\-d\fR, \f(CW\*(C`virt\-df\*(C'\fR отримає від libvirt список активних і неактивних гостьових систем і виконає дію типу \f(CW\*(C`df\*(C'\fR для кожного з них послідовно, а потім виведе результати.
.PP
-Якщо вказано якийсь із аргументів, \fI\-a\fR або \fI\-d\fR, \f(CW\*(C`virt\-df\*(C'\fR виконає дію
-типу \f(CW\*(C`df\*(C'\fR або над окремим вказаним за назвою доменом libvirt, або над
-образами дисків, вказаних у форматі списку у командному рядку (усі вони
-мають належати до однієї віртуальної машини). \fBУ цьому режимі (з
-аргументами), \f(CB\*(C`virt\-df\*(C'\fB працюватиме для однієї гостьової системи\fR. Якщо ви
-хочете обробити декілька гостьових систем, вам слід викликати \f(CW\*(C`virt\-df\*(C'\fR
-декілька разів.
+Якщо вказано якийсь із аргументів, \fI\-a\fR або \fI\-d\fR, \f(CW\*(C`virt\-df\*(C'\fR виконає дію типу \f(CW\*(C`df\*(C'\fR або над окремим вказаним за назвою доменом libvirt, або над образами дисків, вказаних у форматі списку у командному рядку (усі вони мають належати до однієї віртуальної машини). \fBУ цьому режимі (з аргументами), \f(CB\*(C`virt\-df\*(C'\fB працюватиме для однієї гостьової системи\fR. Якщо ви хочете обробити декілька гостьових систем, вам слід викликати \f(CW\*(C`virt\-df\*(C'\fR декілька разів.
.PP
-Скористайтеся параметром \fI\-\-csv\fR, щоб отримати формат у вигляді даних, які
-може бути просто оброблено у інших програмах. Інші параметри подібні до
-параметрів стандартної команди \fBdf\fR\|(1).
+Скористайтеся параметром \fI\-\-csv\fR, щоб отримати формат у вигляді даних, які може бути просто оброблено у інших програмах. Інші параметри подібні до параметрів стандартної команди \fBdf\fR\|(1).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
-Показати використання диска для окремої гостьової системи libvirt, яка
-називається \f(CW\*(C`F14x64\*(C'\fR. Зробити виведені дані зручними для читання:
+Показати використання диска для окремої гостьової системи libvirt, яка називається \f(CW\*(C`F14x64\*(C'\fR. Зробити виведені дані зручними для читання:
.PP
.Vb 4
\& # virt\-df \-d F14x64 \-h
\& F14x64:/dev/vg_f13x64/lv_root 7.4G 3.4G 4.0G 46%
.Ve
.PP
-Показати дані щодо використання диска у файлі образу диска з назвою
-\&\fItest.img\fR:
+Показати дані щодо використання диска у файлі образу диска з назвою \fItest.img\fR:
.PP
.Vb 3
\& $ virt\-df \-a test1.img
\& test1.img:/dev/sda1 99099 1551 92432 2%
.Ve
.PP
-Якщо у одній гостьовій системі декілька дисків, скористайтеся параметром
-\&\fI\-a\fR декілька разів. Для кожного з додаткових дисків буде показано символ
-«плюс» (\f(CW\*(C`+\*(C'\fR). \fBЗауваження: не робіть цього для непов'язаних дисків
-гостьових систем.\fR
+Якщо у одній гостьовій системі декілька дисків, скористайтеся параметром \fI\-a\fR декілька разів. Для кожного з додаткових дисків буде показано символ «плюс» (\f(CW\*(C`+\*(C'\fR). \fBЗауваження: не робіть цього для непов'язаних дисків гостьових систем.\fR
.PP
.Vb 5
\& $ virt\-df \-a Win7x32TwoDisks\-a \-a Win7x32TwoDisks\-b
.IP "\fB\-\-add\fR ФАЙЛ" 4
.IX Item "--add ФАЙЛ"
.PD
-Додати \fIФАЙЛ\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIФАЙЛ\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0,
-наведеним нижче.
+Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0, наведеним нижче.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-df \-\-format=raw \-a disk.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-df \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
Вивести дані щодо inode замість даних щодо блоків.
.IP "\fB\-\-one\-per\-guest\fR" 4
.IX Item "--one-per-guest"
-З версії libguestfs 1.22 ця поведінка є типовою. Використання цього
-параметра не має жодних наслідків. Параметр збережено лише з міркувань
-зворотної сумісності із давніми скриптами.
+З версії libguestfs 1.22 ця поведінка є типовою. Використання цього параметра не має жодних наслідків. Параметр збережено лише з міркувань зворотної сумісності із давніми скриптами.
.IP "\fB\-P\fR кількість_потоків" 4
.IX Item "-P кількість_потоків"
-З версії libguestfs 1.22 у virt-df передбачено обробку у декілька потоків і
-паралельне вивчення гостьових систем. Типово кількість потоків виконання, що
-використовуються, вибирається на основі доступного обсягу вільної пам’яті на
-час запуску virt-df. Ви можете примусово наказати virt-df використовувати не
-більше за \f(CW\*(C`кількість_потоків\*(C'\fR за допомогою параметра \fI\-P\fR.
+З версії libguestfs 1.22 у virt-df передбачено обробку у декілька потоків і паралельне вивчення гостьових систем. Типово кількість потоків виконання, що використовуються, вибирається на основі доступного обсягу вільної пам’яті на час запуску virt-df. Ви можете примусово наказати virt-df використовувати не більше за \f(CW\*(C`кількість_потоків\*(C'\fR за допомогою параметра \fI\-P\fR.
.Sp
-Зауважте, що \fI\-P 0\fR означає автоматичне визначення, а \fI\-P 1\fR означає
-використання одного потоку виконання.
+Зауважте, що \fI\-P 0\fR означає автоматичне визначення, а \fI\-P 1\fR означає використання одного потоку виконання.
.IP "\fB\-\-uuid\fR" 4
.IX Item "--uuid"
-Виводити \s-1UUID\s0 замість назв. Корисно для слідкування за гостьовою системою,
-навіть після перенесення або перейменування, або якщо дві гостьові системи
-мають однакові назви.
+Виводити \s-1UUID\s0 замість назв. Корисно для слідкування за гостьовою системою, навіть після перенесення або перейменування, або якщо дві гостьові системи мають однакові назви.
.Sp
-Зауважте, що \s-1UUID\s0 матимуть лише ті домени, які ми отримуємо з libvirt. Для
-образів дисків ми виводимо назви образів дисків, навіть якщо вказано цей
-параметр.
+Зауважте, що \s-1UUID\s0 матимуть лише ті домени, які ми отримуємо з libvirt. Для образів дисків ми виводимо назви образів дисків, навіть якщо вказано цей параметр.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "ЧИСЛОВІ ДАНІ ЩОДО STATVFS"
.IX Header "ЧИСЛОВІ ДАНІ ЩОДО STATVFS"
-\&\f(CW\*(C`virt\-df\*(C'\fR (і \fBdf\fR\|(1)) отримує інформацію, виконуючи системний виклик
-\&\fBstatvfs\fR\|(3). Ви можете отримати ті самі дані безпосередньо або від
-основної системи (за допомогою libguestfs), або з самої гостьової системи:
+\&\f(CW\*(C`virt\-df\*(C'\fR (і \fBdf\fR\|(1)) отримує інформацію, виконуючи системний виклик \fBstatvfs\fR\|(3). Ви можете отримати ті самі дані безпосередньо або від основної системи (за допомогою libguestfs), або з самої гостьової системи:
.IP "З основної системи" 4
.IX Item "З основної системи"
Віддайте таку команду:
(замініть \fI/\fR, щоб переглянути статистику для інших файлових систем).
.SH "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
.IX Header "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
-Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може
-\&\fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може \fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
.PP
-Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR працює у надійний спосіб. Ось приклад із двома стовпчиками:
.PP
.Vb 1
\& "foo,bar",baz
.Ve
.PP
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось приклад із одним рядком:
.PP
.Vb 2
\& "foo
\& bar",baz
.Ve
.PP
-Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR
-(https://github.com/Chris00/ocaml\-csv також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv також є серед пакунків основних дистрибутивів Linux).
.PP
-Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0
-(наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0 (наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
.PP
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних \s-1CSV.\s0
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних \s-1CSV.\s0
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBdf\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1),
-http://libguestfs.org/.
+\&\fBdf\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 НАЗВА
-virt-df — програма для показу даних щодо вільного місця на віртуальних
-файлових системах
+virt-df — програма для показу даних щодо вільного місця на віртуальних файлових системах
=head1 КОРОТКИЙ ОПИС
=head1 ОПИС
-C<virt-df> — інструмент командного рядка для показу вільного місця у
-файлових системах віртуальної машини. На відміну від інших інструментів, він
-не показує розмір диску, який отримано для віртуальної машини, а може
-зазирнути всередину образу диска і визначити, скільки саме місця насправді
-використовується.
+C<virt-df> — інструмент командного рядка для показу вільного місця у файлових системах віртуальної машини. На відміну від інших інструментів, він не показує розмір диску, який отримано для віртуальної машини, а може зазирнути всередину образу диска і визначити, скільки саме місця насправді використовується.
-Якщо команду віддано без аргументів I<-a> або I<-d>, C<virt-df> отримає від
-libvirt список активних і неактивних гостьових систем і виконає дію типу
-C<df> для кожного з них послідовно, а потім виведе результати.
+Якщо команду віддано без аргументів I<-a> або I<-d>, C<virt-df> отримає від libvirt список активних і неактивних гостьових систем і виконає дію типу C<df> для кожного з них послідовно, а потім виведе результати.
-Якщо вказано якийсь із аргументів, I<-a> або I<-d>, C<virt-df> виконає дію
-типу C<df> або над окремим вказаним за назвою доменом libvirt, або над
-образами дисків, вказаних у форматі списку у командному рядку (усі вони
-мають належати до однієї віртуальної машини). B<У цьому режимі (з
-аргументами), C<virt-df> працюватиме для однієї гостьової системи>. Якщо ви
-хочете обробити декілька гостьових систем, вам слід викликати C<virt-df>
-декілька разів.
+Якщо вказано якийсь із аргументів, I<-a> або I<-d>, C<virt-df> виконає дію типу C<df> або над окремим вказаним за назвою доменом libvirt, або над образами дисків, вказаних у форматі списку у командному рядку (усі вони мають належати до однієї віртуальної машини). B<У цьому режимі (з аргументами), C<virt-df> працюватиме для однієї гостьової системи>. Якщо ви хочете обробити декілька гостьових систем, вам слід викликати C<virt-df> декілька разів.
-Скористайтеся параметром I<--csv>, щоб отримати формат у вигляді даних, які
-може бути просто оброблено у інших програмах. Інші параметри подібні до
-параметрів стандартної команди L<df(1)>.
+Скористайтеся параметром I<--csv>, щоб отримати формат у вигляді даних, які може бути просто оброблено у інших програмах. Інші параметри подібні до параметрів стандартної команди L<df(1)>.
=head1 ПРИКЛАДИ
-Показати використання диска для окремої гостьової системи libvirt, яка
-називається C<F14x64>. Зробити виведені дані зручними для читання:
+Показати використання диска для окремої гостьової системи libvirt, яка називається C<F14x64>. Зробити виведені дані зручними для читання:
# virt-df -d F14x64 -h
Filesystem Size Used Available Use%
F14x64:/dev/sda1 484M 66M 393M 14%
F14x64:/dev/vg_f13x64/lv_root 7.4G 3.4G 4.0G 46%
-Показати дані щодо використання диска у файлі образу диска з назвою
-F<test.img>:
+Показати дані щодо використання диска у файлі образу диска з назвою F<test.img>:
$ virt-df -a test1.img
Filesystem 1K-blocks Used Available Use%
test1.img:/dev/sda1 99099 1551 92432 2%
-Якщо у одній гостьовій системі декілька дисків, скористайтеся параметром
-I<-a> декілька разів. Для кожного з додаткових дисків буде показано символ
-«плюс» (C<+>). B<Зауваження: не робіть цього для непов'язаних дисків
-гостьових систем.>
+Якщо у одній гостьовій системі декілька дисків, скористайтеся параметром I<-a> декілька разів. Для кожного з додаткових дисків буде показано символ «плюс» (C<+>). B<Зауваження: не робіть цього для непов'язаних дисків гостьових систем.>
$ virt-df -a Win7x32TwoDisks-a -a Win7x32TwoDisks-b
Файлова система 1K-блоків Вик. Доступно %Вик.
=item B<--add> ФАЙЛ
-Додати I<ФАЙЛ>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<ФАЙЛ>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<--csv>
-Вивести результати до формату CSV (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>,
-наведеним нижче.
+Вивести результати до формату CSV (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>, наведеним нижче.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-df --format=raw -a disk.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-df --format=raw -a disk.img --format -a another.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<-h>
=item B<--one-per-guest>
-З версії libguestfs 1.22 ця поведінка є типовою. Використання цього
-параметра не має жодних наслідків. Параметр збережено лише з міркувань
-зворотної сумісності із давніми скриптами.
+З версії libguestfs 1.22 ця поведінка є типовою. Використання цього параметра не має жодних наслідків. Параметр збережено лише з міркувань зворотної сумісності із давніми скриптами.
=item B<-P> кількість_потоків
-З версії libguestfs 1.22 у virt-df передбачено обробку у декілька потоків і
-паралельне вивчення гостьових систем. Типово кількість потоків виконання, що
-використовуються, вибирається на основі доступного обсягу вільної пам’яті на
-час запуску virt-df. Ви можете примусово наказати virt-df використовувати не
-більше за C<кількість_потоків> за допомогою параметра I<-P>.
+З версії libguestfs 1.22 у virt-df передбачено обробку у декілька потоків і паралельне вивчення гостьових систем. Типово кількість потоків виконання, що використовуються, вибирається на основі доступного обсягу вільної пам’яті на час запуску virt-df. Ви можете примусово наказати virt-df використовувати не більше за C<кількість_потоків> за допомогою параметра I<-P>.
-Зауважте, що I<-P 0> означає автоматичне визначення, а I<-P 1> означає
-використання одного потоку виконання.
+Зауважте, що I<-P 0> означає автоматичне визначення, а I<-P 1> означає використання одного потоку виконання.
=item B<--uuid>
-Виводити UUID замість назв. Корисно для слідкування за гостьовою системою,
-навіть після перенесення або перейменування, або якщо дві гостьові системи
-мають однакові назви.
+Виводити UUID замість назв. Корисно для слідкування за гостьовою системою, навіть після перенесення або перейменування, або якщо дві гостьові системи мають однакові назви.
-Зауважте, що UUID матимуть лише ті домени, які ми отримуємо з libvirt. Для
-образів дисків ми виводимо назви образів дисків, навіть якщо вказано цей
-параметр.
+Зауважте, що UUID матимуть лише ті домени, які ми отримуємо з libvirt. Для образів дисків ми виводимо назви образів дисків, навіть якщо вказано цей параметр.
=item B<-v>
=head1 ЧИСЛОВІ ДАНІ ЩОДО STATVFS
-C<virt-df> (і L<df(1)>) отримує інформацію, виконуючи системний виклик
-L<statvfs(3)>. Ви можете отримати ті самі дані безпосередньо або від
-основної системи (за допомогою libguestfs), або з самої гостьової системи:
+C<virt-df> (і L<df(1)>) отримує інформацію, виконуючи системний виклик L<statvfs(3)>. Ви можете отримати ті самі дані безпосередньо або від основної системи (за допомогою libguestfs), або з самої гостьової системи:
=over 4
=head1 ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV
-Формат значень, які відокремлено комами (CSV), є оманливо простим. Може
-I<здатися>, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (CSV), є оманливо простим. Може I<здатися>, що його просто обробляти, але насправді це зовсім не так.
-Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не>
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не> працює у надійний спосіб. Ось приклад із двома стовпчиками:
"foo,bar",baz
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось приклад із одним рядком:
"foo
bar",baz
-Для скриптів командної оболонки скористайтеся C<csvtool>
-(L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся C<csvtool> (L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних дистрибутивів Linux).
-Для інших мов програмування використовуйте бібліотеку для обробки даних CSV
-(наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних CSV (наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних CSV.
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних CSV.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>,
-L<http://libguestfs.org/>.
+L<df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-dib 1"
-.TH virt-dib 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-dib 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-dib — інструмент для використання елементів \f(CW\*(C`diskimage\-builder\*(C'\fR з
-метою побудови нового образу диска, створення нових дисків у пам'яті тощо.
+Virt-dib — інструмент для використання елементів \f(CW\*(C`diskimage\-builder\*(C'\fR з метою побудови нового образу диска, створення нових дисків у пам'яті тощо.
.PP
-Virt-dib призначено для безпечної заміни \f(CW\*(C`diskimage\-builder\*(C'\fR і її режиму
-\&\f(CW\*(C`ramdisk\-image\-create\*(C'\fR, див. \*(L"ПОРІВНЯННЯ З DISKIMAGE-BUILDER\*(R", щоб
-ознайомитися із коротким порівнянням із використанням \f(CW\*(C`diskimage\-builder\*(C'\fR.
+Virt-dib призначено для безпечної заміни \f(CW\*(C`diskimage\-builder\*(C'\fR і її режиму \f(CW\*(C`ramdisk\-image\-create\*(C'\fR, див. \*(L"ПОРІВНЯННЯ З DISKIMAGE-BUILDER\*(R", щоб ознайомитися із коротким порівнянням із використанням \f(CW\*(C`diskimage\-builder\*(C'\fR.
.PP
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR є частиною проєкту TripleO OpenStack:
-https://wiki.openstack.org/wiki/TripleO.
+\&\f(CW\*(C`diskimage\-builder\*(C'\fR є частиною проєкту TripleO OpenStack: https://wiki.openstack.org/wiki/TripleO.
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
.SS "Збирання простих образів дистрибутивів"
\& debian vm
.Ve
.PP
-Ця команда збирає образ диска Debian Jessie (8.x), який є придатним для
-запуску у форматі віртуальної машини, який буде збережено як
-\&\fIdebian\-jessie.qcow2\fR.
+Ця команда збирає образ диска Debian Jessie (8.x), який є придатним для запуску у форматі віртуальної машини, який буде збережено як \fIdebian\-jessie.qcow2\fR.
.SS "Збирання дисків у пам’яті"
.IX Subsection "Збирання дисків у пам’яті"
.Vb 6
\& ubuntu deploy\-ironic
.Ve
.PP
-Ця команда збирає диск у пам’яті для компонента Ironic OpenStack на основі
-дистрибутива Ubuntu.
+Ця команда збирає диск у пам’яті для компонента Ironic OpenStack на основі дистрибутива Ubuntu.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
Показати довідкове повідомлення.
.IP "\fB\-B\fR ШЛЯХ" 4
.IX Item "-B ШЛЯХ"
-Встановити шлях до каталогу бібліотеки \f(CW\*(C`diskimage\-builder\*(C'\fR. Типово, це
-підкаталог \fIlib\fR у початкових кодах, а після встановлення до \fI/usr\fR
-каталог \fI/usr/share/diskimage\-builder/lib\fR.
+Встановити шлях до каталогу бібліотеки \f(CW\*(C`diskimage\-builder\*(C'\fR. Типово, це підкаталог \fIlib\fR у початкових кодах, а після встановлення до \fI/usr\fR каталог \fI/usr/share/diskimage\-builder/lib\fR.
.Sp
-Цей параметр є \fBобов'язковим\fR, оскільки virt-dib має надати його елементам
-(оскільки деякі з них можуть використовувати скрипти у каталозі). Сама ж
-програма virt-dib не використовує цей каталог бібліотеки безпосередньо.
+Цей параметр є \fBобов'язковим\fR, оскільки virt-dib має надати його елементам (оскільки деякі з них можуть використовувати скрипти у каталозі). Сама ж програма virt-dib не використовує цей каталог бібліотеки безпосередньо.
.IP "\fB\-\-arch\fR АРХІТЕКТУРА" 4
.IX Item "--arch АРХІТЕКТУРА"
-Використовувати для образу\-результату вказану архітектуру. Типовим є
-значення, яке збігається зі значенням архітектури для основної системи, на
-якій запущено virt-dib.
+Використовувати для образу\-результату вказану архітектуру. Типовим є значення, яке збігається зі значенням архітектури для основної системи, на якій запущено virt-dib.
.Sp
-У поточній версії цей параметр виконує лише встановлення змінної середовища
-\&\f(CW\*(C`ARCH\*(C'\fR для елементів, а елементи вже створюють образ для потрібної
-користувачу архітектури.
+У поточній версії цей параметр виконує лише встановлення змінної середовища \f(CW\*(C`ARCH\*(C'\fR для елементів, а елементи вже створюють образ для потрібної користувачу архітектури.
.IP "\fB\-\-checksum\fR" 4
.IX Item "--checksum"
-Створювати файли контрольних сум для образу. Підтримуваними є контрольні
-суми \s-1MD5\s0 та \s-1SHA256.\s0
+Створювати файли контрольних сум для образу. Підтримуваними є контрольні суми \s-1MD5\s0 та \s-1SHA256.\s0
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-\-debug\fR РІВЕНЬ" 4
.IX Item "--debug РІВЕНЬ"
-Встановити значення рівня діагностики \f(CW\*(C`РІВЕНЬ\*(C'\fR. Рівнем є невід'ємне ціле
-число. Типовим є рівень \f(CW0\fR.
+Встановити значення рівня діагностики \f(CW\*(C`РІВЕНЬ\*(C'\fR. Рівнем є невід'ємне ціле число. Типовим є рівень \f(CW0\fR.
.Sp
-Цей рівень діагностики відрізняється від рівня, який встановлюється \fI\-x\fR і
-\&\fI\-v\fR, він збільшує обсяг діагностичної інформації, яка виводиться. Зокрема,
-він встановлює \f(CW\*(C`DIB_DEBUG_TRACE\*(C'\fR, усі значення рівня > \f(CW0\fR
-уможливлюють трасування у виконуваних скриптах.
+Цей рівень діагностики відрізняється від рівня, який встановлюється \fI\-x\fR і \fI\-v\fR, він збільшує обсяг діагностичної інформації, яка виводиться. Зокрема, він встановлює \f(CW\*(C`DIB_DEBUG_TRACE\*(C'\fR, усі значення рівня > \f(CW0\fR уможливлюють трасування у виконуваних скриптах.
.IP "\fB\-\-docker\-target\fR ЦІЛЬ" 4
.IX Item "--docker-target ЦІЛЬ"
Встановити сховище і мітку для docker.
.Sp
-Використовується лише тоді, коли серед форматів є \f(CW\*(C`docker\*(C'\fR, і є
-обов'язковим у цьому випадку.
+Використовується лише тоді, коли серед форматів є \f(CW\*(C`docker\*(C'\fR, і є обов'язковим у цьому випадку.
.IP "\fB\-\-drive\fR ДИСК" 4
.IX Item "--drive ДИСК"
-Додати вказаний диск як допоміжний, такий, де зберігатимуться файли кешу
-елементів, зокрема образи дисків, пакунки дистрибутива тощо.
+Додати вказаний диск як допоміжний, такий, де зберігатимуться файли кешу елементів, зокрема образи дисків, пакунки дистрибутива тощо.
.Sp
Див. \*(L"ДОПОМІЖНИЙ ДИСК\*(R".
.IP "\fB\-\-drive\-format\fR raw" 4
.IP "\fB\-\-drive\-format\fR qcow2" 4
.IX Item "--drive-format qcow2"
.PD
-Вказати формат допоміжного диска. Якщо цей прапорець не вказано, його буде
-автоматично визначено на основі даних самого диска.
+Вказати формат допоміжного диска. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого диска.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.Sp
Цей параметр використовується, лише якщо вказано \fI\-\-drive\fR.
.Sp
.IP "\fB\-\-element\-path\fR ШЛЯХ" 4
.IX Item "--element-path ШЛЯХ"
.PD
-Додати новий шлях з елементами. Шляхи використовуватимуться у тому самому
-порядку, у якому з’являються параметри \fI\-p\fR, отже, пошук за шляхом,
-вказаним першим, відбуватиметься спочатку.
+Додати новий шлях з елементами. Шляхи використовуватимуться у тому самому порядку, у якому з’являються параметри \fI\-p\fR, отже, пошук за шляхом, вказаним першим, відбуватиметься спочатку.
.Sp
-Очевидно, варто додати шлях до власних елементів \f(CW\*(C`diskimage\-builder\*(C'\fR,
-оскільки більшість інших елементів покладатимуться на ці дані.
+Очевидно, варто додати шлях до власних елементів \f(CW\*(C`diskimage\-builder\*(C'\fR, оскільки більшість інших елементів покладатимуться на ці дані.
.IP "\fB\-\-extra\-packages\fR ПАКУНОК,..." 4
.IX Item "--extra-packages ПАКУНОК,..."
Встановити додаткові пакунки у образ, який збиратиметься.
.Sp
-Робота цього параметра залежить від виконуваного файла \f(CW\*(C`install\-packages\*(C'\fR,
-який визначається елементами керування пакунками.
+Робота цього параметра залежить від виконуваного файла \f(CW\*(C`install\-packages\*(C'\fR, який визначається елементами керування пакунками.
.Sp
-Цей параметр може бути використано декілька разів, декілька пакунків у
-аргументах слід відокремлювати комами.
+Цей параметр може бути використано декілька разів, декілька пакунків у аргументах слід відокремлювати комами.
.IP "\fB\-\-envvar\fR ЗМІННА" 4
.IX Item "--envvar ЗМІННА"
.PD 0
.PD
Передати або встановити змінну середовища для елементів.
.Sp
-Див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" нижче, щоб дізнатися більше про взаємодію і
-використання змінних середовища.
+Див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" нижче, щоб дізнатися більше про взаємодію і використання змінних середовища.
.Sp
Цим параметром можна скористатися у декілька способів:
.RS 4
.IP "\fB\-\-envvar\fR ЗМІННА" 4
.IX Item "--envvar ЗМІННА"
-Передати змінну середовища \f(CW\*(C`ЗМІННА\*(C'\fR. Якщо змінну не встановлено, до
-елементів нічого не експортуватиметься.
+Передати змінну середовища \f(CW\*(C`ЗМІННА\*(C'\fR. Якщо змінну не встановлено, до елементів нічого не експортуватиметься.
.IP "\fB\-\-envvar\fR ЗМІННА=ЗНАЧЕННЯ" 4
.IX Item "--envvar ЗМІННА=ЗНАЧЕННЯ"
-Встановити для змінної середовища \f(CW\*(C`ЗМІННА\*(C'\fR значення \f(CW\*(C`ЗНАЧЕННЯ\*(C'\fR для
-елементів, незалежно від того, чи вже існує змінна середовища із тією самою
-назвою.
+Встановити для змінної середовища \f(CW\*(C`ЗМІННА\*(C'\fR значення \f(CW\*(C`ЗНАЧЕННЯ\*(C'\fR для елементів, незалежно від того, чи вже існує змінна середовища із тією самою назвою.
.Sp
-Може бути корисним для передавання змінної середовища без експортування у
-середовище, де запущено virt-dib.
+Може бути корисним для передавання змінної середовища без експортування у середовище, де запущено virt-dib.
.RE
.RS 4
.RE
Ігнорувати вказаний елемент.
.IP "\fB\-\-exclude\-script\fR СКРИПТ" 4
.IX Item "--exclude-script СКРИПТ"
-Ігнорувати будь\-який скрипт елемента із назвою \f(CW\*(C`СКРИПТ\*(C'\fR, байдуже, до якого
-елемента він належатиме.
+Ігнорувати будь\-який скрипт елемента із назвою \f(CW\*(C`СКРИПТ\*(C'\fR, байдуже, до якого елемента він належатиме.
.Sp
-Це може бути корисним, якщо якийсь скрипт погано працює з virt-dib,
-наприклад, якщо скриптові справді потрібне середовище \f(CW\*(C`diskimage\-builder\*(C'\fR.
+Це може бути корисним, якщо якийсь скрипт погано працює з virt-dib, наприклад, якщо скриптові справді потрібне середовище \f(CW\*(C`diskimage\-builder\*(C'\fR.
.IP "\fB\-\-formats\fR ФОРМАТ,..." 4
.IX Item "--formats ФОРМАТ,..."
Встановити список форматів виведення даних, відокремлених комами.
.ie n .IP """docker""" 4
.el .IP "\f(CWdocker\fR" 4
.IX Item "docker"
-Імпортувати образ до docker за допомогою команди \fBdocker
-import\fR. Призначення для образу \fBмає\fR бути вказано за допомогою
-\&\fI\-\-docker\-target\fR.
-.Sp
-Будь ласка, зауважте, що виконання цієї дії зазвичай потребує вмикання
-служби docker, інакше його не вдасться виконати. Крім того, \fBdocker\fR працює
-з використанням \fBsudo\fR\|(8), отже, переконайтеся, що користувач має право
-запускати принаймні \fBdocker\fR.
+Імпортувати образ до docker за допомогою команди \fBdocker import\fR. Призначення для образу \fBмає\fR бути вказано за допомогою \fI\-\-docker\-target\fR.
+.Sp
+Будь ласка, зауважте, що виконання цієї дії зазвичай потребує вмикання служби docker, інакше його не вдасться виконати. Крім того, \fBdocker\fR працює з використанням \fBsudo\fR\|(8), отже, переконайтеся, що користувач має право запускати принаймні \fBdocker\fR.
.ie n .IP """qcow2"" (типово увімкнено)" 4
.el .IP "\f(CWqcow2\fR (типово увімкнено)" 4
.IX Item "qcow2 (типово увімкнено)"
.ie n .IP """squashfs""" 4
.el .IP "\f(CWsquashfs\fR" 4
.IX Item "squashfs"
-Файлова система squashfs, яку стиснуто за допомогою \s-1XZ.\s0 Для користування цим
-форматом виведення даних потрібна можливість \f(CW\*(C`squashfs\*(C'\fR; див. також
-\&\*(L"ДОСТУПНІСТЬ\*(R" in \fBguestfs\fR\|(3).
+Файлова система squashfs, яку стиснуто за допомогою \s-1XZ.\s0 Для користування цим форматом виведення даних потрібна можливість \f(CW\*(C`squashfs\*(C'\fR; див. також \*(L"ДОСТУПНІСТЬ\*(R" in \fBguestfs\fR\|(3).
.ie n .IP """tar""" 4
.el .IP "\f(CWtar\fR" 4
.IX Item "tar"
.ie n .IP """vhd""" 4
.el .IP "\f(CWvhd\fR" 4
.IX Item "vhd"
-Образ диска \f(CW\*(C`Virtual Hard Disk\*(C'\fR. Виведення даних у цьому форматі вимагає
-наявності \f(CW\*(C`vhd\-util\*(C'\fR.
+Образ диска \f(CW\*(C`Virtual Hard Disk\*(C'\fR. Виведення даних у цьому форматі вимагає наявності \f(CW\*(C`vhd\-util\*(C'\fR.
.Sp
-Будь ласка, зверніть увагу на те, що версія \f(CW\*(C`vhd\-util\*(C'\fR повинна бути
-зібраною із латкою, яка вмикає підтримку підкоманди \f(CW\*(C`convert\*(C'\fR, і бути
-придатною до завантаження. Латку можна знайти тут:
-https://github.com/emonty/vhd\-util/blob/master/debian/patches/citrix.
+Будь ласка, зверніть увагу на те, що версія \f(CW\*(C`vhd\-util\*(C'\fR повинна бути зібраною із латкою, яка вмикає підтримку підкоманди \f(CW\*(C`convert\*(C'\fR, і бути придатною до завантаження. Латку можна знайти тут: https://github.com/emonty/vhd\-util/blob/master/debian/patches/citrix.
.RE
.RS 4
.RE
.IP "\fB\-\-fs\-type\fR ФАЙЛОВА СИСТЕМА" 4
.IX Item "--fs-type ФАЙЛОВА СИСТЕМА"
-Встановити файлову систему, яку буде використано для кореневої теки
-системи. Типовою є \f(CW\*(C`ext4\*(C'\fR.
+Встановити файлову систему, яку буде використано для кореневої теки системи. Типовою є \f(CW\*(C`ext4\*(C'\fR.
.Sp
Див. також \*(L"guestfs_filesystem_available\*(R" in \fBguestfs\fR\|(3)
.IP "\fB\-\-image\-cache\fR КАТАЛОГ" 4
.IX Item "--image-cache КАТАЛОГ"
-Встановити каталог у основній системі, до якого кешуватимуться ресурси, які
-використовуються елементами фази \f(CW\*(C`extra\-data.d\*(C'\fR. Типовим є
-\&\fI~/.cache/image\-create\fR.
+Встановити каталог у основній системі, до якого кешуватимуться ресурси, які використовуються елементами фази \f(CW\*(C`extra\-data.d\*(C'\fR. Типовим є \fI~/.cache/image\-create\fR.
.Sp
-Будь ласка, зауважте, що більшість ресурсів, які отримуватимуться на фазах,
-відмінних від \f(CW\*(C`extra\-data.d\*(C'\fR, кешуватимуться на допоміжному диску,
-вказаному за допомогою \fI\-\-drive\fR; див. також \*(L"ДОПОМІЖНИЙ ДИСК\*(R".
+Будь ласка, зауважте, що більшість ресурсів, які отримуватимуться на фазах, відмінних від \f(CW\*(C`extra\-data.d\*(C'\fR, кешуватимуться на допоміжному диску, вказаному за допомогою \fI\-\-drive\fR; див. також \*(L"ДОПОМІЖНИЙ ДИСК\*(R".
.IP "\fB\-\-install\-type\fR ТИП" 4
.IX Item "--install-type ТИП"
Вказати типовий тип встановлення. Стандартним є \f(CW\*(C`source\*(C'\fR.
.Sp
-Встановіть значення \f(CW\*(C`package\*(C'\fR, щоб типово використовувати засноване на
-пакунках встановлення.
+Встановіть значення \f(CW\*(C`package\*(C'\fR, щоб типово використовувати засноване на пакунках встановлення.
.IP "\fB\-\-machine\-readable\fR" 4
.IX Item "--machine-readable"
.PD 0
.IP "\fB\-\-machine\-readable\fR=формат" 4
.IX Item "--machine-readable=формат"
.PD
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
.IP "\fB\-m\fR МБ" 4
.IX Item "-m МБ"
.PD 0
.IP "\fB\-\-memsize\fR МБ" 4
.IX Item "--memsize МБ"
.PD
-Змінити обсяг пам'яті, який надаватиметься для базової системи. Збільште це
-значення, якщо для виконання virt-dib не вистачає пам'яті.
+Змінити обсяг пам'яті, який надаватиметься для базової системи. Збільште це значення, якщо для виконання virt-dib не вистачає пам'яті.
.Sp
Типові значення можна визначити за допомогою такої команди:
.Sp
.ie n .IP "\fB\-\-mkfs\-options\fR ""РЯДОК ПАРАМЕТРІВ""" 4
.el .IP "\fB\-\-mkfs\-options\fR \f(CWРЯДОК ПАРАМЕТРІВ\fR" 4
.IX Item "--mkfs-options РЯДОК ПАРАМЕТРІВ"
-Додати вказані параметри до \fBmkfs\fR\|(1), щоб мати змогу скоригувати параметри
-створення кореневої файлової системи; параметри передаються драйверу
-\&\fBmfks\fR\|(1), а не самій \fBmfks\fR\|(1). Зауважте, що для зміни типу файлової
-системи використовується \fI\-\-fs\-type\fR.
+Додати вказані параметри до \fBmkfs\fR\|(1), щоб мати змогу скоригувати параметри створення кореневої файлової системи; параметри передаються драйверу \fBmfks\fR\|(1), а не самій \fBmfks\fR\|(1). Зауважте, що для зміни типу файлової системи використовується \fI\-\-fs\-type\fR.
.Sp
-Вам слід скористатися \fI\-\-mkfs\-options\fR не більше одного разу. Щоб передати
-декілька параметрів, відокремте їх пробілами. Приклад:
+Вам слід скористатися \fI\-\-mkfs\-options\fR не більше одного разу. Щоб передати декілька параметрів, відокремте їх пробілами. Приклад:
.Sp
.Vb 1
\& virt\-dib ... \-\-mkfs\-options \*(Aq\-O якийсь_параметр \-I щось_ще\*(Aq
.IP "\fB\-\-no\-network\fR" 4
.IX Item "--no-network"
.PD
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
.Sp
-Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром \fI\-\-no\-network\fR, щоб вимкнути доступ.
.Sp
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. \*(L"МЕРЕЖА\*(R" in \fBvirt\-rescue\fR\|(1).
.Sp
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-dib.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-dib.
.Sp
-Якщо ви використаєте параметр \fI\-\-no\-network\fR, змінній середовища
-\&\f(CW\*(C`DIB_OFFLINE\*(C'\fR буде надано значення \f(CW1\fR, що сигналізуватиме елементам про
-те, що їм слід використовувати лише кешовані ресурси, якщо вони
-доступні. Також слід зауважити, що, на відміну від \f(CW\*(C`diskimage\-builder\*(C'\fR, де
-елементи все ще можуть отримувати доступ до мережі навіть із
-\&\f(CW\*(C`DIB_OFFLINE=\*(C'\fR, у virt-dib мережа буде зовсім недоступною.
+Якщо ви використаєте параметр \fI\-\-no\-network\fR, змінній середовища \f(CW\*(C`DIB_OFFLINE\*(C'\fR буде надано значення \f(CW1\fR, що сигналізуватиме елементам про те, що їм слід використовувати лише кешовані ресурси, якщо вони доступні. Також слід зауважити, що, на відміну від \f(CW\*(C`diskimage\-builder\*(C'\fR, де елементи все ще можуть отримувати доступ до мережі навіть із \f(CW\*(C`DIB_OFFLINE=\*(C'\fR, у virt-dib мережа буде зовсім недоступною.
.IP "\fB\-\-name\fR НАЗВА" 4
.IX Item "--name НАЗВА"
Встановити назву для файла із виведеним образом. Типовою є \f(CW\*(C`image\*(C'\fR.
.RS 4
.IP "\fI\f(CI$NAME\fI.ext\fR" 4
.IX Item "$NAME.ext"
-Для кожного з форматів виведення назву файла буде взято з назви
-образу\-результату, а суфікс назви залежатиме від формату. Приклад:
-\&\fI\f(CI$NAME\fI.qcow2\fR, \fI\f(CI$NAME\fI.raw\fR тощо.
+Для кожного з форматів виведення назву файла буде взято з назви образу\-результату, а суфікс назви залежатиме від формату. Приклад: \fI\f(CI$NAME\fI.qcow2\fR, \fI\f(CI$NAME\fI.raw\fR тощо.
.Sp
-Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. \*(L"ЗБИРАННЯ
-ДИСКА У ПАМ'ЯТІ\*(R".
+Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. \*(L"ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ\*(R".
.IP "\fI\f(CI$NAME\fI.d\fR" 4
.IX Item "$NAME.d"
-Каталог, що містить будь\-які файли, створені елементами, наприклад каталог
-\&\fIdib-manifests\fR (створено елементом \f(CW\*(C`manifests\*(C'\fR), диски у пам'яті та ядра
-у режимі диску у пам'яті тощо.
+Каталог, що містить будь\-які файли, створені елементами, наприклад каталог \fIdib-manifests\fR (створено елементом \f(CW\*(C`manifests\*(C'\fR), диски у пам'яті та ядра у режимі диску у пам'яті тощо.
.IP "\fI\f(CI$NAME\fI.ext.checksum\fR" 4
.IX Item "$NAME.ext.checksum"
-Якщо вказано \fI\-\-checksum\fR, буде створено файли для усіх підтримуваних типів
-контрольних сум; приклади: \fI\f(CI$NAME\fI.ext.md5\fR, \fI\f(CI$NAME\fI.ext.sha256\fR тощо.
+Якщо вказано \fI\-\-checksum\fR, буде створено файли для усіх підтримуваних типів контрольних сум; приклади: \fI\f(CI$NAME\fI.ext.md5\fR, \fI\f(CI$NAME\fI.ext.sha256\fR тощо.
.Sp
-Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. \*(L"ЗБИРАННЯ
-ДИСКА У ПАМ'ЯТІ\*(R".
+Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. \*(L"ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ\*(R".
.RE
.RS 4
.RE
.IP "\fB\-\-no\-delete\-on\-failure\fR" 4
.IX Item "--no-delete-on-failure"
-Не вилучати файли з виведеними даними, якщо під час збирання станеться
-помилка. Цими файлами можна скористатися для діагностики помилок у запущених
-скриптах.
+Не вилучати файли з виведеними даними, якщо під час збирання станеться помилка. Цими файлами можна скористатися для діагностики помилок у запущених скриптах.
.Sp
-Типовою є поведінка, коли файли результатів буде вилучено, якщо станеться
-помилка у virt-dib (або, наприклад, помилка у одному зі скриптів, які
-запускає ця програма).
+Типовою є поведінка, коли файли результатів буде вилучено, якщо станеться помилка у virt-dib (або, наприклад, помилка у одному зі скриптів, які запускає ця програма).
.IP "\fB\-\-python\fR \s-1PYTHON\s0" 4
.IX Item "--python PYTHON"
-Вказати для використання інший інтерпретатор Python. Частину
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR реалізовано мовою Python, тому інтерпретатор є
-обов'язковим.
-.Sp
-Значенням \f(CW\*(C`PYTHON\*(C'\fR може бути або повна назва виконуваного файла (наприклад
-\&\fIpython2\fR, пошук якого буде виконано у каталогах змінної \f(CW$PATH\fR), або
-шлях повністю (наприклад \fI/usr/bin/python2\fR). Якщо не вказано, типовим
-значенням буде \fIpython\fR.
+Вказати для використання інший інтерпретатор Python. Частину \f(CW\*(C`diskimage\-builder\*(C'\fR реалізовано мовою Python, тому інтерпретатор є обов'язковим.
+.Sp
+Значенням \f(CW\*(C`PYTHON\*(C'\fR може бути або повна назва виконуваного файла (наприклад \fIpython2\fR, пошук якого буде виконано у каталогах змінної \f(CW$PATH\fR), або шлях повністю (наприклад \fI/usr/bin/python2\fR). Якщо не вказано, типовим значенням буде \fIpython\fR.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
Не виводити звичайних повідомлень щодо поступу.
.IP "\fB\-\-qemu\-img\-options\fR параметр[,параметр,...]" 4
.IX Item "--qemu-img-options параметр[,параметр,...]"
-Передати параметри \fI\-\-qemu\-img\-options\fR до програми \fBqemu\-img\fR\|(1) для
-коригування формату виведення даних. Перелік доступних параметрів залежить
-від формату виведення (див. \fI\-\-formats\fR) і встановленої версії програми
-qemu-img.
+Передати параметри \fI\-\-qemu\-img\-options\fR до програми \fBqemu\-img\fR\|(1) для коригування формату виведення даних. Перелік доступних параметрів залежить від формату виведення (див. \fI\-\-formats\fR) і встановленої версії програми qemu-img.
.Sp
-Вам слід скористатися \fI\-\-qemu\-img\-options\fR не більше одного разу. Щоб
-передати декілька параметрів, відокремте їх комами. Приклад:
+Вам слід скористатися \fI\-\-qemu\-img\-options\fR не більше одного разу. Щоб передати декілька параметрів, відокремте їх комами. Приклад:
.Sp
.Vb 1
\& virt\-dib ... \-\-qemu\-img\-options cluster_size=512,preallocation=metadata ...
Див. \*(L"ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ\*(R".
.IP "\fB\-\-ramdisk\-element\fR НАЗВА" 4
.IX Item "--ramdisk-element НАЗВА"
-Встановити назву для додаткового елемента, який буде додано у режимі
-збирання диска у пам'яті. Типовою є назва \f(CW\*(C`ramdisk\*(C'\fR.
+Встановити назву для додаткового елемента, який буде додано у режимі збирання диска у пам'яті. Типовою є назва \f(CW\*(C`ramdisk\*(C'\fR.
.Sp
Див. \*(L"ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ\*(R".
.IP "\fB\-\-root\-label\fR МІТКА" 4
.IX Item "--root-label МІТКА"
Встановити мітку для кореневої файлової системи у створеному образі.
.Sp
-Будь ласка, зауважте, що у деяких файлових системах обмеження на мітки може
-бути іншим. Наприклад, у файлових системах \f(CW\*(C`ext2/3/4\*(C'\fR мітки не можуть бути
-довшими за 16 символів, а у \f(CW\*(C`xfs\*(C'\fR найбільшою довжиною мітки є 12 символів.
+Будь ласка, зауважте, що у деяких файлових системах обмеження на мітки може бути іншим. Наприклад, у файлових системах \f(CW\*(C`ext2/3/4\*(C'\fR мітки не можуть бути довшими за 16 символів, а у \f(CW\*(C`xfs\*(C'\fR найбільшою довжиною мітки є 12 символів.
.Sp
-Типове значення залежить від типу файлової системи для кореневого розділу
-(див. \fI\-\-fs\-type\fR): на \f(CW\*(C`xfs\*(C'\fR — це \f(CW\*(C`img\-rootfs\*(C'\fR, а на будь\-якій іншій
-файловій системі — \f(CW\*(C`cloudimg\-rootfs\*(C'\fR.
+Типове значення залежить від типу файлової системи для кореневого розділу (див. \fI\-\-fs\-type\fR): на \f(CW\*(C`xfs\*(C'\fR — це \f(CW\*(C`img\-rootfs\*(C'\fR, а на будь\-якій іншій файловій системі — \f(CW\*(C`cloudimg\-rootfs\*(C'\fR.
.IP "\fB\-\-size\fR РОЗМІР" 4
.IX Item "--size РОЗМІР"
-Вибір розміру диска\-результату, де розмір можна вказати за допомогою типових
-записів, зокрема \f(CW\*(C`32G\*(C'\fR (32 гігабайти) тощо. Типовим є розмір \f(CW\*(C`5G\*(C'\fR.
+Вибір розміру диска\-результату, де розмір можна вказати за допомогою типових записів, зокрема \f(CW\*(C`32G\*(C'\fR (32 гігабайти) тощо. Типовим є розмір \f(CW\*(C`5G\*(C'\fR.
.Sp
-Щоб вказати розмір у байтах, додайте до числа малу літеру \fIb\fR, наприклад
-\&\f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
+Щоб вказати розмір у байтах, додайте до числа малу літеру \fIb\fR, наприклад \f(CW\*(C`\-\-size 10737418240b\*(C'\fR.
.Sp
-Див. також \fBvirt\-resize\fR\|(1) щодо зміни розмірів розділів на наявному образі
-диска.
+Див. також \fBvirt\-resize\fR\|(1) щодо зміни розмірів розділів на наявному образі диска.
.IP "\fB\-\-skip\-base\fR" 4
.IX Item "--skip-base"
Пропустити включення елемента \f(CW\*(C`base\*(C'\fR.
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
-На відміну від \f(CW\*(C`diskimage\-builder\*(C'\fR, середовище основної системи \fBне\fR
-успадковується у базовій системі під час запуску більшості елементів (тобто
-усіх, окрім елементів у фазі \f(CW\*(C`extra\-data.d\*(C'\fR).
+На відміну від \f(CW\*(C`diskimage\-builder\*(C'\fR, середовище основної системи \fBне\fR успадковується у базовій системі під час запуску більшості елементів (тобто усіх, окрім елементів у фазі \f(CW\*(C`extra\-data.d\*(C'\fR).
.PP
-Щоб встановити змінні середовища для виконання елементів, слід повідомити
-virt-dib, що слід використовувати ці змінні, за допомогою параметра
-\&\fI\-\-envvar\fR. Такий параметр надасть змогу вибірково експортувати змінні
-середовища під час виконання елементі. Це також пріоритетний шлях
-передавання змінних середовища елементам.
+Щоб встановити змінні середовища для виконання елементів, слід повідомити virt-dib, що слід використовувати ці змінні, за допомогою параметра \fI\-\-envvar\fR. Такий параметр надасть змогу вибірково експортувати змінні середовища під час виконання елементі. Це також пріоритетний шлях передавання змінних середовища елементам.
.PP
-І ще раз: якщо вам потрібно, щоб змінна середовища \f(CW\*(C`MYVAR\*(C'\fR (і її вміст)
-були доступні елементам, вам слід або віддати команду
+І ще раз: якщо вам потрібно, щоб змінна середовища \f(CW\*(C`MYVAR\*(C'\fR (і її вміст) були доступні елементам, вам слід або віддати команду
.PP
.Vb 2
\& export MYVAR # яким би не було її значення
.Ve
.SH "ДОПОМІЖНИЙ ДИСК"
.IX Header "ДОПОМІЖНИЙ ДИСК"
-Virt-dib виконує більшість елементів у власній базовій системі, отже, не на
-основній системі. Через це, елементи не можуть кешувати ресурси
-безпосередньо на основній системі.
+Virt-dib виконує більшість елементів у власній базовій системі, отже, не на основній системі. Через це, елементи не можуть кешувати ресурси безпосередньо на основній системі.
.PP
-Щоб усунути цю незручність, у virt-dib передбачено можливість використання
-допоміжного диска, на якому можна зберігати кешовані ресурси, зокрема образи
-дисків, пакунки дистрибутивів тощо. Хоча це означає, що для кешування буде
-доступним менше місця, принаймні, це надає змогу обмежити простір у основній
-системі для кешів без потреби у виконанні цього завдання засобами самих
-елементів.
+Щоб усунути цю незручність, у virt-dib передбачено можливість використання допоміжного диска, на якому можна зберігати кешовані ресурси, зокрема образи дисків, пакунки дистрибутивів тощо. Хоча це означає, що для кешування буде доступним менше місця, принаймні, це надає змогу обмежити простір у основній системі для кешів без потреби у виконанні цього завдання засобами самих елементів.
.PP
-У поточній версії або цей диск має містити лише один розділ, або має
-використовуватися лише перший розділ з диска. Диск із другим варіантом
-конфігурації доволі просто створити за допомогою \fBguestfish\fR\|(1) ось так:
+У поточній версії або цей диск має містити лише один розділ, або має використовуватися лише перший розділ з диска. Диск із другим варіантом конфігурації доволі просто створити за допомогою \fBguestfish\fR\|(1) ось так:
.PP
.Vb 1
\& guestfish \-N filename.img=fs:ext4:10G exit
.Ve
.PP
-У результаті виконання наведеної вище команди буде створено образ диска із
-назвою \fIfilename.img\fR об'ємом у 10 ГБ з одним розділом типу ext4;
-див. \*(L"ОБРАЗИ ПРИГОТОВАНИХ ДИСКІВ\*(R" in \fBguestfish\fR\|(1).
+У результаті виконання наведеної вище команди буде створено образ диска із назвою \fIfilename.img\fR об'ємом у 10 ГБ з одним розділом типу ext4; див. \*(L"ОБРАЗИ ПРИГОТОВАНИХ ДИСКІВ\*(R" in \fBguestfish\fR\|(1).
.PP
-Рекомендованим розміром диска є ≥ 10 ГБ, оскільки елементи кешуватимуть
-образи дисків, пакунки дистрибутивів тощо. Як і розмір будь\-якого образу
-диска, розмір допоміжного диска можна змінити за допомогою
-\&\fBvirt\-resize\fR\|(1), якщо раптом він стане замалим.
+Рекомендованим розміром диска є ≥ 10 ГБ, оскільки елементи кешуватимуть образи дисків, пакунки дистрибутивів тощо. Як і розмір будь\-якого образу диска, розмір допоміжного диска можна змінити за допомогою \fBvirt\-resize\fR\|(1), якщо раптом він стане замалим.
.PP
-Доступ до диска може здійснюватися у спосіб, який є подібним до способу
-доступу до будь\-яких інших образів дисків, наприклад, за допомогою інших
-інструментів libguestfs, зокрема \fBguestfish\fR\|(1):
+Доступ до диска може здійснюватися у спосіб, який є подібним до способу доступу до будь\-яких інших образів дисків, наприклад, за допомогою інших інструментів libguestfs, зокрема \fBguestfish\fR\|(1):
.PP
.Vb 1
\& guestfish \-a filename.img \-m /dev/sda1
.Ve
.PP
-Якщо за допомогою \fI\-\-drive\fR не вказано жодного допоміжного диска, усі
-ресурси, кешовані під час запуску virt-dib, буде відкинуто.
+Якщо за допомогою \fI\-\-drive\fR не вказано жодного допоміжного диска, усі ресурси, кешовані під час запуску virt-dib, буде відкинуто.
.SS "РЕСУРСИ НА ДИСКУ"
.IX Subsection "РЕСУРСИ НА ДИСКУ"
У допоміжному диску можна шукати такі ресурси:
.IP "\fI/home\fR" 4
.IX Item "/home"
-Цей каталог задається за допомогою змінної середовища \f(CW\*(C`HOME\*(C'\fR під час
-збирання. У ньому, здебільшого, міститься кеш образів (збережений до
-\&\fI/home/.cache/image\-create\fR) та усі інші ресурси у домашньому каталозі
-користувача, який запускає різні інструменти.
+Цей каталог задається за допомогою змінної середовища \f(CW\*(C`HOME\*(C'\fR під час збирання. У ньому, здебільшого, міститься кеш образів (збережений до \fI/home/.cache/image\-create\fR) та усі інші ресурси у домашньому каталозі користувача, який запускає різні інструменти.
.IP "\fI/virt\-dib\-*.log\fR" 4
.IX Item "/virt-dib-*.log"
-Це журнали елементів, які виконуються у базовій системі libguestfs, тобто
-усі фази, окрім \f(CW\*(C`extra\-data.d\*(C'\fR.
+Це журнали елементів, які виконуються у базовій системі libguestfs, тобто усі фази, окрім \f(CW\*(C`extra\-data.d\*(C'\fR.
.SH "ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ"
.IX Header "ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ"
-Virt-dib може також емулювати \f(CW\*(C`ramdisk\-image\-create\*(C'\fR, вторинний режим
-роботи \f(CW\*(C`diskimage\-builder\*(C'\fR. Замість використання якогось інструмента із
-іншою назвою, virt-dib надає простий доступ до режиму за допомогою параметра
-\&\fI\-\-ramdisk\fR.
+Virt-dib може також емулювати \f(CW\*(C`ramdisk\-image\-create\*(C'\fR, вторинний режим роботи \f(CW\*(C`diskimage\-builder\*(C'\fR. Замість використання якогось інструмента із іншою назвою, virt-dib надає простий доступ до режиму за допомогою параметра \fI\-\-ramdisk\fR.
.PP
У цьому режимі:
.IP "\(bu" 4
\&\fI\f(CI$NAME\fI.d\fR (див. \fI\-\-name\fR) міститиме initrd, kernel, тощо.
.SH "ТИМЧАСОВИЙ КАТАЛОГ"
.IX Header "ТИМЧАСОВИЙ КАТАЛОГ"
-Virt-dib використовує стандартний каталог для тимчасових файлів, який
-використовується libguestfs, див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
+Virt-dib використовує стандартний каталог для тимчасових файлів, який використовується libguestfs, див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
.PP
-Типово, цим каталогом є \fI/tmp\fR (типове значення для \f(CW\*(C`TMPDIR\*(C'\fR). У деяких
-системах для цього каталогу може використовуватися файлова система
-tmpfs. Таким чином, типовим максимальним розміром для нього є \fIполовина\fR
-фізичного розміру оперативної пам'яті. Якщо під час роботи virt-dib
-перевищить це обмеження, програма може повиснути або завершити роботу
-передчасно із повідомленням про помилку. Усунути цю проблему можна, вказавши
-для \f(CW\*(C`TMPDIR\*(C'\fR тимчасовий каталог. Приклад:
+Типово, цим каталогом є \fI/tmp\fR (типове значення для \f(CW\*(C`TMPDIR\*(C'\fR). У деяких системах для цього каталогу може використовуватися файлова система tmpfs. Таким чином, типовим максимальним розміром для нього є \fIполовина\fR фізичного розміру оперативної пам'яті. Якщо під час роботи virt-dib перевищить це обмеження, програма може повиснути або завершити роботу передчасно із повідомленням про помилку. Усунути цю проблему можна, вказавши для \f(CW\*(C`TMPDIR\*(C'\fR тимчасовий каталог. Приклад:
.PP
.Vb 3
\& mkdir local\-tmp
.Ve
.SH "ДОДАТКОВІ ЗАЛЕЖНОСТІ"
.IX Header "ДОДАТКОВІ ЗАЛЕЖНОСТІ"
-Оскільки virt-dib запускає більшість елементів у власній базовій системі,
-усі інструменти та бібліотеки, які використовуються елементами, що
-запускаються поза межами гостьової системи (типово \f(CW\*(C`root.d\*(C'\fR,
-\&\f(CW\*(C`block\-device.d\*(C'\fR та \f(CW\*(C`cleanup.d\*(C'\fR) мають бути і у базовій системі. Якщо їх
-не буде, скрипти не зможуть працювати і типово повідомлять про помилку
-\&\f(CW\*(C`команду не знайдено\*(C'\fR.
-.PP
-Для інструментів і бібліотек, які містяться у пакунках дистрибутивів,
-простим рішенням цієї проблеми буде віддання наказу libguestfs включити
-додаткові пакунки до базової системи. Зробити це можна, наприклад, створення
-файла із додатковими пакунками:
+Оскільки virt-dib запускає більшість елементів у власній базовій системі, усі інструменти та бібліотеки, які використовуються елементами, що запускаються поза межами гостьової системи (типово \f(CW\*(C`root.d\*(C'\fR, \f(CW\*(C`block\-device.d\*(C'\fR та \f(CW\*(C`cleanup.d\*(C'\fR) мають бути і у базовій системі. Якщо їх не буде, скрипти не зможуть працювати і типово повідомлять про помилку \f(CW\*(C`команду не знайдено\*(C'\fR.
+.PP
+Для інструментів і бібліотек, які містяться у пакунках дистрибутивів, простим рішенням цієї проблеми буде віддання наказу libguestfs включити додаткові пакунки до базової системи. Зробити це можна, наприклад, створення файла із додатковими пакунками:
.PP
.Vb 1
\& # echo wget > /usr/lib64/guestfs/supermin.d/dib\-my\-extra
.Ve
.PP
-Шлях до каталогу \fIsupermin.d\fR, звичайно ж, залежить від дистрибутива. У
-додаткових файлах може бути список із багатьма пакунками, кожен з яких слід
-вказувати окремому рядку. Докладніший опис можна знайти у підручнику з
-\&\fBsupermin\fR\|(1).
+Шлях до каталогу \fIsupermin.d\fR, звичайно ж, залежить від дистрибутива. У додаткових файлах може бути список із багатьма пакунками, кожен з яких слід вказувати окремому рядку. Докладніший опис можна знайти у підручнику з \fBsupermin\fR\|(1).
.SH "ПОРІВНЯННЯ ІЗ DISKIMAGE-BUILDER"
.IX Header "ПОРІВНЯННЯ ІЗ DISKIMAGE-BUILDER"
-Призначенням virt-dib є бути безпечним замінником програми
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR і її режиму \f(CW\*(C`ramdisk\-image\-create\*(C'\fR. Помітні для
-користувача відмінності полягають ось у чому:
+Призначенням virt-dib є бути безпечним замінником програми \f(CW\*(C`diskimage\-builder\*(C'\fR і її режиму \f(CW\*(C`ramdisk\-image\-create\*(C'\fR. Помітні для користувача відмінності полягають ось у чому:
.IP "\(bu" 4
-аргументи командного рядка; деякі з аргументів збігаються із аргументами
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR, але деякі є іншими:
+аргументи командного рядка; деякі з аргументів збігаються із аргументами \f(CW\*(C`diskimage\-builder\*(C'\fR, але деякі є іншими:
.Sp
.Vb 12
\& disk\-image\-create virt\-dib
\& \-x \-x [\-x ...] \-\-debug 3/4/etc
.Ve
.IP "\(bu" 4
-розташування файлів\-результатів, які не є образами (зокрема дисків у пам'яті
-і ядер)
+розташування файлів\-результатів, які не є образами (зокрема дисків у пам'яті і ядер)
.IP "\(bu" 4
-спосіб зберігання деяких кешованих ресурсів: використання допоміжного диска,
-а не диска, на якому запущено virt-dib
+спосіб зберігання деяких кешованих ресурсів: використання допоміжного диска, а не диска, на якому запущено virt-dib
.IP "\(bu" 4
-потреба у визначення розміру диска\-результату, тоді як програма
-\&\f(CW\*(C`diskimage\-builder\*(C'\fR автоматично обчислює оптимальний розмір
+потреба у визначення розміру диска\-результату, тоді як програма \f(CW\*(C`diskimage\-builder\*(C'\fR автоматично обчислює оптимальний розмір
.IP "\(bu" 4
обробка змінних середовища, див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R".
.Sp
-До того ж, окрім власних змінних середовища libguestfs
-(див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3)), virt-dib не виконує читання жодних
-інших змінних середовища. Це означає, що зміни у параметрах і поведінці
-програми визначаються лише переданими їй аргументами рядка команди.
+До того ж, окрім власних змінних середовища libguestfs (див. \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3)), virt-dib не виконує читання жодних інших змінних середовища. Це означає, що зміни у параметрах і поведінці програми визначаються лише переданими їй аргументами рядка команди.
.IP "\(bu" 4
-потрібно, щоб додаткові інструменти на деяких фазах поза chroot були
-доступні у базовій системі, див. \*(L"ДОДАТКОВІ ЗАЛЕЖНОСТІ\*(R".
+потрібно, щоб додаткові інструменти на деяких фазах поза chroot були доступні у базовій системі, див. \*(L"ДОДАТКОВІ ЗАЛЕЖНОСТІ\*(R".
.PP
-Робота самих елементів не повинна зазнати змін; причиною відмінностей у
-поведінці можуть бути помилкові припущення у коді самих елементів або
-некоректна емуляція virt-dib.
+Робота самих елементів не повинна зазнати змін; причиною відмінностей у поведінці можуть бути помилкові припущення у коді самих елементів або некоректна емуляція virt-dib.
.PP
Відомі вади:
.IP "\(bu" 4
(нічого)
.SH "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
.IX Header "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра
-робить зручним використання virt-dib з інших програм, графічних інтерфейсів
-тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра робить зручним використання virt-dib з інших програм, графічних інтерфейсів тощо.
.PP
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-dib. Типово виведені дані виглядатимуть якось так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-dib. Типово виведені дані виглядатимуть якось так:
.PP
.Vb 6
\& $ virt\-dib \-\-machine\-readable
\& output:vhd
.Ve
.PP
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
.PP
-\&\f(CW\*(C`output:\*(C'\fR є вказівкою на формати виведення (параметр рядка команди
-\&\fI\-\-formats\fR), підтримку яких передбачено у цьому виконуваному файлі.
+\&\f(CW\*(C`output:\*(C'\fR є вказівкою на формати виведення (параметр рядка команди \fI\-\-formats\fR), підтримку яких передбачено у цьому виконуваному файлі.
.PP
-Можна вказати рядок форматування для керування виведенням,
-див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
+Можна вказати рядок форматування для керування виведенням, див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
.SH "ТЕСТУВАННЯ"
.IX Header "ТЕСТУВАННЯ"
-Перевірку працездатності virt-dib було виконано для \f(CW\*(C`diskimage\-builder\*(C'\fR (та
-його елементів) ≥ 0.1.43. Час від часу виконується також перевірка для
-\&\f(CW\*(C`tripleo\-image\-elements\*(C'\fR та \f(CW\*(C`sahara\-image\-elements\*(C'\fR.
+Перевірку працездатності virt-dib було виконано для \f(CW\*(C`diskimage\-builder\*(C'\fR (та його елементів) ≥ 0.1.43. Час від часу виконується також перевірка для \f(CW\*(C`tripleo\-image\-elements\*(C'\fR та \f(CW\*(C`sahara\-image\-elements\*(C'\fR.
.PP
Попередні версії також можуть працювати, але цього не можна гарантувати.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-resize\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Pino Toscano (\f(CW\*(C`ptoscano at redhat dot com\*(C'\fR)
=head1 ОПИС
-Virt-dib — інструмент для використання елементів C<diskimage-builder> з
-метою побудови нового образу диска, створення нових дисків у пам'яті тощо.
+Virt-dib — інструмент для використання елементів C<diskimage-builder> з метою побудови нового образу диска, створення нових дисків у пам'яті тощо.
-Virt-dib призначено для безпечної заміни C<diskimage-builder> і її режиму
-C<ramdisk-image-create>, див. L</ПОРІВНЯННЯ З DISKIMAGE-BUILDER>, щоб
-ознайомитися із коротким порівнянням із використанням C<diskimage-builder>.
+Virt-dib призначено для безпечної заміни C<diskimage-builder> і її режиму C<ramdisk-image-create>, див. L</ПОРІВНЯННЯ З DISKIMAGE-BUILDER>, щоб ознайомитися із коротким порівнянням із використанням C<diskimage-builder>.
-C<diskimage-builder> є частиною проєкту TripleO OpenStack:
-L<https://wiki.openstack.org/wiki/TripleO>.
+C<diskimage-builder> є частиною проєкту TripleO OpenStack: L<https://wiki.openstack.org/wiki/TripleO>.
=head1 ПРИКЛАДИ
--name debian-jessie \
debian vm
-Ця команда збирає образ диска Debian Jessie (8.x), який є придатним для
-запуску у форматі віртуальної машини, який буде збережено як
-F<debian-jessie.qcow2>.
+Ця команда збирає образ диска Debian Jessie (8.x), який є придатним для запуску у форматі віртуальної машини, який буде збережено як F<debian-jessie.qcow2>.
=head2 Збирання дисків у пам’яті
--name ramdisk \
ubuntu deploy-ironic
-Ця команда збирає диск у пам’яті для компонента Ironic OpenStack на основі
-дистрибутива Ubuntu.
+Ця команда збирає диск у пам’яті для компонента Ironic OpenStack на основі дистрибутива Ubuntu.
=head1 ПАРАМЕТРИ
=item B<-B> ШЛЯХ
-Встановити шлях до каталогу бібліотеки C<diskimage-builder>. Типово, це
-підкаталог F<lib> у початкових кодах, а після встановлення до F</usr>
-каталог F</usr/share/diskimage-builder/lib>.
+Встановити шлях до каталогу бібліотеки C<diskimage-builder>. Типово, це підкаталог F<lib> у початкових кодах, а після встановлення до F</usr> каталог F</usr/share/diskimage-builder/lib>.
-Цей параметр є B<обов'язковим>, оскільки virt-dib має надати його елементам
-(оскільки деякі з них можуть використовувати скрипти у каталозі). Сама ж
-програма virt-dib не використовує цей каталог бібліотеки безпосередньо.
+Цей параметр є B<обов'язковим>, оскільки virt-dib має надати його елементам (оскільки деякі з них можуть використовувати скрипти у каталозі). Сама ж програма virt-dib не використовує цей каталог бібліотеки безпосередньо.
=item B<--arch> АРХІТЕКТУРА
-Використовувати для образу-результату вказану архітектуру. Типовим є
-значення, яке збігається зі значенням архітектури для основної системи, на
-якій запущено virt-dib.
+Використовувати для образу-результату вказану архітектуру. Типовим є значення, яке збігається зі значенням архітектури для основної системи, на якій запущено virt-dib.
-У поточній версії цей параметр виконує лише встановлення змінної середовища
-C<ARCH> для елементів, а елементи вже створюють образ для потрібної
-користувачу архітектури.
+У поточній версії цей параметр виконує лише встановлення змінної середовища C<ARCH> для елементів, а елементи вже створюють образ для потрібної користувачу архітектури.
=item B<--checksum>
-Створювати файли контрольних сум для образу. Підтримуваними є контрольні
-суми MD5 та SHA256.
+Створювати файли контрольних сум для образу. Підтримуваними є контрольні суми MD5 та SHA256.
=item B<--colors>
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<--debug> РІВЕНЬ
-Встановити значення рівня діагностики C<РІВЕНЬ>. Рівнем є невід'ємне ціле
-число. Типовим є рівень C<0>.
+Встановити значення рівня діагностики C<РІВЕНЬ>. Рівнем є невід'ємне ціле число. Типовим є рівень C<0>.
-Цей рівень діагностики відрізняється від рівня, який встановлюється I<-x> і
-I<-v>, він збільшує обсяг діагностичної інформації, яка виводиться. Зокрема,
-він встановлює C<DIB_DEBUG_TRACE>, усі значення рівня E<gt> C<0>
-уможливлюють трасування у виконуваних скриптах.
+Цей рівень діагностики відрізняється від рівня, який встановлюється I<-x> і I<-v>, він збільшує обсяг діагностичної інформації, яка виводиться. Зокрема, він встановлює C<DIB_DEBUG_TRACE>, усі значення рівня E<gt> C<0> уможливлюють трасування у виконуваних скриптах.
=item B<--docker-target> ЦІЛЬ
Встановити сховище і мітку для docker.
-Використовується лише тоді, коли серед форматів є C<docker>, і є
-обов'язковим у цьому випадку.
+Використовується лише тоді, коли серед форматів є C<docker>, і є обов'язковим у цьому випадку.
=item B<--drive> ДИСК
-Додати вказаний диск як допоміжний, такий, де зберігатимуться файли кешу
-елементів, зокрема образи дисків, пакунки дистрибутива тощо.
+Додати вказаний диск як допоміжний, такий, де зберігатимуться файли кешу елементів, зокрема образи дисків, пакунки дистрибутива тощо.
Див. L</ДОПОМІЖНИЙ ДИСК>.
=item B<--drive-format> qcow2
-Вказати формат допоміжного диска. Якщо цей прапорець не вказано, його буде
-автоматично визначено на основі даних самого диска.
+Вказати формат допоміжного диска. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого диска.
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
Цей параметр використовується, лише якщо вказано I<--drive>.
=item B<--element-path> ШЛЯХ
-Додати новий шлях з елементами. Шляхи використовуватимуться у тому самому
-порядку, у якому з’являються параметри I<-p>, отже, пошук за шляхом,
-вказаним першим, відбуватиметься спочатку.
+Додати новий шлях з елементами. Шляхи використовуватимуться у тому самому порядку, у якому з’являються параметри I<-p>, отже, пошук за шляхом, вказаним першим, відбуватиметься спочатку.
-Очевидно, варто додати шлях до власних елементів C<diskimage-builder>,
-оскільки більшість інших елементів покладатимуться на ці дані.
+Очевидно, варто додати шлях до власних елементів C<diskimage-builder>, оскільки більшість інших елементів покладатимуться на ці дані.
=item B<--extra-packages> ПАКУНОК,...
Встановити додаткові пакунки у образ, який збиратиметься.
-Робота цього параметра залежить від виконуваного файла C<install-packages>,
-який визначається елементами керування пакунками.
+Робота цього параметра залежить від виконуваного файла C<install-packages>, який визначається елементами керування пакунками.
-Цей параметр може бути використано декілька разів, декілька пакунків у
-аргументах слід відокремлювати комами.
+Цей параметр може бути використано декілька разів, декілька пакунків у аргументах слід відокремлювати комами.
=item B<--envvar> ЗМІННА
Передати або встановити змінну середовища для елементів.
-Див. L</ЗМІННІ СЕРЕДОВИЩА> нижче, щоб дізнатися більше про взаємодію і
-використання змінних середовища.
+Див. L</ЗМІННІ СЕРЕДОВИЩА> нижче, щоб дізнатися більше про взаємодію і використання змінних середовища.
Цим параметром можна скористатися у декілька способів:
=item B<--envvar> ЗМІННА
-Передати змінну середовища C<ЗМІННА>. Якщо змінну не встановлено, до
-елементів нічого не експортуватиметься.
+Передати змінну середовища C<ЗМІННА>. Якщо змінну не встановлено, до елементів нічого не експортуватиметься.
=item B<--envvar> ЗМІННА=ЗНАЧЕННЯ
-Встановити для змінної середовища C<ЗМІННА> значення C<ЗНАЧЕННЯ> для
-елементів, незалежно від того, чи вже існує змінна середовища із тією самою
-назвою.
+Встановити для змінної середовища C<ЗМІННА> значення C<ЗНАЧЕННЯ> для елементів, незалежно від того, чи вже існує змінна середовища із тією самою назвою.
-Може бути корисним для передавання змінної середовища без експортування у
-середовище, де запущено virt-dib.
+Може бути корисним для передавання змінної середовища без експортування у середовище, де запущено virt-dib.
=back
=item B<--exclude-script> СКРИПТ
-Ігнорувати будь-який скрипт елемента із назвою C<СКРИПТ>, байдуже, до якого
-елемента він належатиме.
+Ігнорувати будь-який скрипт елемента із назвою C<СКРИПТ>, байдуже, до якого елемента він належатиме.
-Це може бути корисним, якщо якийсь скрипт погано працює з virt-dib,
-наприклад, якщо скриптові справді потрібне середовище C<diskimage-builder>.
+Це може бути корисним, якщо якийсь скрипт погано працює з virt-dib, наприклад, якщо скриптові справді потрібне середовище C<diskimage-builder>.
=item B<--formats> ФОРМАТ,...
=item C<docker>
-Імпортувати образ до docker за допомогою команди B<docker
-import>. Призначення для образу B<має> бути вказано за допомогою
-I<--docker-target>.
+Імпортувати образ до docker за допомогою команди B<docker import>. Призначення для образу B<має> бути вказано за допомогою I<--docker-target>.
-Будь ласка, зауважте, що виконання цієї дії зазвичай потребує вмикання
-служби docker, інакше його не вдасться виконати. Крім того, B<docker> працює
-з використанням L<sudo(8)>, отже, переконайтеся, що користувач має право
-запускати принаймні B<docker>.
+Будь ласка, зауважте, що виконання цієї дії зазвичай потребує вмикання служби docker, інакше його не вдасться виконати. Крім того, B<docker> працює з використанням L<sudo(8)>, отже, переконайтеся, що користувач має право запускати принаймні B<docker>.
=item C<qcow2> (типово увімкнено)
=item C<squashfs>
-Файлова система squashfs, яку стиснуто за допомогою XZ. Для користування цим
-форматом виведення даних потрібна можливість C<squashfs>; див. також
-L<guestfs(3)/ДОСТУПНІСТЬ>.
+Файлова система squashfs, яку стиснуто за допомогою XZ. Для користування цим форматом виведення даних потрібна можливість C<squashfs>; див. також L<guestfs(3)/ДОСТУПНІСТЬ>.
=item C<tar>
=item C<vhd>
-Образ диска C<Virtual Hard Disk>. Виведення даних у цьому форматі вимагає
-наявності C<vhd-util>.
+Образ диска C<Virtual Hard Disk>. Виведення даних у цьому форматі вимагає наявності C<vhd-util>.
-Будь ласка, зверніть увагу на те, що версія C<vhd-util> повинна бути
-зібраною із латкою, яка вмикає підтримку підкоманди C<convert>, і бути
-придатною до завантаження. Латку можна знайти тут:
-L<https://github.com/emonty/vhd-util/blob/master/debian/patches/citrix>.
+Будь ласка, зверніть увагу на те, що версія C<vhd-util> повинна бути зібраною із латкою, яка вмикає підтримку підкоманди C<convert>, і бути придатною до завантаження. Латку можна знайти тут: L<https://github.com/emonty/vhd-util/blob/master/debian/patches/citrix>.
=back
=item B<--fs-type> ФАЙЛОВА СИСТЕМА
-Встановити файлову систему, яку буде використано для кореневої теки
-системи. Типовою є C<ext4>.
+Встановити файлову систему, яку буде використано для кореневої теки системи. Типовою є C<ext4>.
Див. також L<guestfs(3)/guestfs_filesystem_available>
=item B<--image-cache> КАТАЛОГ
-Встановити каталог у основній системі, до якого кешуватимуться ресурси, які
-використовуються елементами фази C<extra-data.d>. Типовим є
-F<~/.cache/image-create>.
+Встановити каталог у основній системі, до якого кешуватимуться ресурси, які використовуються елементами фази C<extra-data.d>. Типовим є F<~/.cache/image-create>.
-Будь ласка, зауважте, що більшість ресурсів, які отримуватимуться на фазах,
-відмінних від C<extra-data.d>, кешуватимуться на допоміжному диску,
-вказаному за допомогою I<--drive>; див. також L</ДОПОМІЖНИЙ ДИСК>.
+Будь ласка, зауважте, що більшість ресурсів, які отримуватимуться на фазах, відмінних від C<extra-data.d>, кешуватимуться на допоміжному диску, вказаному за допомогою I<--drive>; див. також L</ДОПОМІЖНИЙ ДИСК>.
=item B<--install-type> ТИП
Вказати типовий тип встановлення. Стандартним є C<source>.
-Встановіть значення C<package>, щоб типово використовувати засноване на
-пакунках встановлення.
+Встановіть значення C<package>, щоб типово використовувати засноване на пакунках встановлення.
=item B<--machine-readable>
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<-m> МБ
=item B<--memsize> МБ
-Змінити обсяг пам'яті, який надаватиметься для базової системи. Збільште це
-значення, якщо для виконання virt-dib не вистачає пам'яті.
+Змінити обсяг пам'яті, який надаватиметься для базової системи. Збільште це значення, якщо для виконання virt-dib не вистачає пам'яті.
Типові значення можна визначити за допомогою такої команди:
=item B<--mkfs-options> C<РЯДОК ПАРАМЕТРІВ>
-Додати вказані параметри до L<mkfs(1)>, щоб мати змогу скоригувати параметри
-створення кореневої файлової системи; параметри передаються драйверу
-L<mfks(1)>, а не самій L<mfks(1)>. Зауважте, що для зміни типу файлової
-системи використовується I<--fs-type>.
+Додати вказані параметри до L<mkfs(1)>, щоб мати змогу скоригувати параметри створення кореневої файлової системи; параметри передаються драйверу L<mfks(1)>, а не самій L<mfks(1)>. Зауважте, що для зміни типу файлової системи використовується I<--fs-type>.
-Вам слід скористатися I<--mkfs-options> не більше одного разу. Щоб передати
-декілька параметрів, відокремте їх пробілами. Приклад:
+Вам слід скористатися I<--mkfs-options> не більше одного разу. Щоб передати декілька параметрів, відокремте їх пробілами. Приклад:
virt-dib ... --mkfs-options '-O якийсь_параметр -I щось_ще'
=item B<--no-network>
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
-Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути
-доступ.
+Типово увімкнено. Скористайтеся параметром I<--no-network>, щоб вимкнути доступ.
-У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших
-незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
+У мережі працюватимуть лише вихідні з'єднання, а також буде декілька інших незначних обмежень. Див. L<virt-rescue(1)/МЕРЕЖА>.
-Це не вплине на доступність мережі для гостьової системи після її
-завантаження, оскільки така доступність керується вашим гіпервізором або
-хмарним середовищем і не має нічого спільного з virt-dib.
+Це не вплине на доступність мережі для гостьової системи після її завантаження, оскільки така доступність керується вашим гіпервізором або хмарним середовищем і не має нічого спільного з virt-dib.
-Якщо ви використаєте параметр I<--no-network>, змінній середовища
-C<DIB_OFFLINE> буде надано значення C<1>, що сигналізуватиме елементам про
-те, що їм слід використовувати лише кешовані ресурси, якщо вони
-доступні. Також слід зауважити, що, на відміну від C<diskimage-builder>, де
-елементи все ще можуть отримувати доступ до мережі навіть із
-C<DIB_OFFLINE=>, у virt-dib мережа буде зовсім недоступною.
+Якщо ви використаєте параметр I<--no-network>, змінній середовища C<DIB_OFFLINE> буде надано значення C<1>, що сигналізуватиме елементам про те, що їм слід використовувати лише кешовані ресурси, якщо вони доступні. Також слід зауважити, що, на відміну від C<diskimage-builder>, де елементи все ще можуть отримувати доступ до мережі навіть із C<DIB_OFFLINE=>, у virt-dib мережа буде зовсім недоступною.
=item B<--name> НАЗВА
=item F<$NAME.ext>
-Для кожного з форматів виведення назву файла буде взято з назви
-образу-результату, а суфікс назви залежатиме від формату. Приклад:
-F<$NAME.qcow2>, F<$NAME.raw> тощо.
+Для кожного з форматів виведення назву файла буде взято з назви образу-результату, а суфікс назви залежатиме від формату. Приклад: F<$NAME.qcow2>, F<$NAME.raw> тощо.
-Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. L</ЗБИРАННЯ
-ДИСКА У ПАМ'ЯТІ>.
+Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. L</ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ>.
=item F<$NAME.d>
-Каталог, що містить будь-які файли, створені елементами, наприклад каталог
-F<dib-manifests> (створено елементом C<manifests>), диски у пам'яті та ядра
-у режимі диску у пам'яті тощо.
+Каталог, що містить будь-які файли, створені елементами, наприклад каталог F<dib-manifests> (створено елементом C<manifests>), диски у пам'яті та ядра у режимі диску у пам'яті тощо.
=item F<$NAME.ext.checksum>
-Якщо вказано I<--checksum>, буде створено файли для усіх підтримуваних типів
-контрольних сум; приклади: F<$NAME.ext.md5>, F<$NAME.ext.sha256> тощо.
+Якщо вказано I<--checksum>, буде створено файли для усіх підтримуваних типів контрольних сум; приклади: F<$NAME.ext.md5>, F<$NAME.ext.sha256> тощо.
-Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. L</ЗБИРАННЯ
-ДИСКА У ПАМ'ЯТІ>.
+Не можна застосовувати у режимі диска у пам'яті (ramdisk), див. L</ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ>.
=back
=item B<--no-delete-on-failure>
-Не вилучати файли з виведеними даними, якщо під час збирання станеться
-помилка. Цими файлами можна скористатися для діагностики помилок у запущених
-скриптах.
+Не вилучати файли з виведеними даними, якщо під час збирання станеться помилка. Цими файлами можна скористатися для діагностики помилок у запущених скриптах.
-Типовою є поведінка, коли файли результатів буде вилучено, якщо станеться
-помилка у virt-dib (або, наприклад, помилка у одному зі скриптів, які
-запускає ця програма).
+Типовою є поведінка, коли файли результатів буде вилучено, якщо станеться помилка у virt-dib (або, наприклад, помилка у одному зі скриптів, які запускає ця програма).
=item B<--python> PYTHON
-Вказати для використання інший інтерпретатор Python. Частину
-C<diskimage-builder> реалізовано мовою Python, тому інтерпретатор є
-обов'язковим.
+Вказати для використання інший інтерпретатор Python. Частину C<diskimage-builder> реалізовано мовою Python, тому інтерпретатор є обов'язковим.
-Значенням C<PYTHON> може бути або повна назва виконуваного файла (наприклад
-F<python2>, пошук якого буде виконано у каталогах змінної C<$PATH>), або
-шлях повністю (наприклад F</usr/bin/python2>). Якщо не вказано, типовим
-значенням буде F<python>.
+Значенням C<PYTHON> може бути або повна назва виконуваного файла (наприклад F<python2>, пошук якого буде виконано у каталогах змінної C<$PATH>), або шлях повністю (наприклад F</usr/bin/python2>). Якщо не вказано, типовим значенням буде F<python>.
=item B<-q>
=item B<--qemu-img-options> параметр[,параметр,...]
-Передати параметри I<--qemu-img-options> до програми L<qemu-img(1)> для
-коригування формату виведення даних. Перелік доступних параметрів залежить
-від формату виведення (див. I<--formats>) і встановленої версії програми
-qemu-img.
+Передати параметри I<--qemu-img-options> до програми L<qemu-img(1)> для коригування формату виведення даних. Перелік доступних параметрів залежить від формату виведення (див. I<--formats>) і встановленої версії програми qemu-img.
-Вам слід скористатися I<--qemu-img-options> не більше одного разу. Щоб
-передати декілька параметрів, відокремте їх комами. Приклад:
+Вам слід скористатися I<--qemu-img-options> не більше одного разу. Щоб передати декілька параметрів, відокремте їх комами. Приклад:
virt-dib ... --qemu-img-options cluster_size=512,preallocation=metadata ...
=item B<--ramdisk-element> НАЗВА
-Встановити назву для додаткового елемента, який буде додано у режимі
-збирання диска у пам'яті. Типовою є назва C<ramdisk>.
+Встановити назву для додаткового елемента, який буде додано у режимі збирання диска у пам'яті. Типовою є назва C<ramdisk>.
Див. L</ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ>.
Встановити мітку для кореневої файлової системи у створеному образі.
-Будь ласка, зауважте, що у деяких файлових системах обмеження на мітки може
-бути іншим. Наприклад, у файлових системах C<ext2/3/4> мітки не можуть бути
-довшими за 16 символів, а у C<xfs> найбільшою довжиною мітки є 12 символів.
+Будь ласка, зауважте, що у деяких файлових системах обмеження на мітки може бути іншим. Наприклад, у файлових системах C<ext2/3/4> мітки не можуть бути довшими за 16 символів, а у C<xfs> найбільшою довжиною мітки є 12 символів.
-Типове значення залежить від типу файлової системи для кореневого розділу
-(див. I<--fs-type>): на C<xfs> — це C<img-rootfs>, а на будь-якій іншій
-файловій системі — C<cloudimg-rootfs>.
+Типове значення залежить від типу файлової системи для кореневого розділу (див. I<--fs-type>): на C<xfs> — це C<img-rootfs>, а на будь-якій іншій файловій системі — C<cloudimg-rootfs>.
=item B<--size> РОЗМІР
-Вибір розміру диска-результату, де розмір можна вказати за допомогою типових
-записів, зокрема C<32G> (32 гігабайти) тощо. Типовим є розмір C<5G>.
+Вибір розміру диска-результату, де розмір можна вказати за допомогою типових записів, зокрема C<32G> (32 гігабайти) тощо. Типовим є розмір C<5G>.
-Щоб вказати розмір у байтах, додайте до числа малу літеру I<b>, наприклад
-S<C<--size 10737418240b>>.
+Щоб вказати розмір у байтах, додайте до числа малу літеру I<b>, наприклад S<C<--size 10737418240b>>.
-Див. також L<virt-resize(1)> щодо зміни розмірів розділів на наявному образі
-диска.
+Див. також L<virt-resize(1)> щодо зміни розмірів розділів на наявному образі диска.
=item B<--skip-base>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 ЗМІННІ СЕРЕДОВИЩА
-На відміну від C<diskimage-builder>, середовище основної системи B<не>
-успадковується у базовій системі під час запуску більшості елементів (тобто
-усіх, окрім елементів у фазі C<extra-data.d>).
+На відміну від C<diskimage-builder>, середовище основної системи B<не> успадковується у базовій системі під час запуску більшості елементів (тобто усіх, окрім елементів у фазі C<extra-data.d>).
-Щоб встановити змінні середовища для виконання елементів, слід повідомити
-virt-dib, що слід використовувати ці змінні, за допомогою параметра
-I<--envvar>. Такий параметр надасть змогу вибірково експортувати змінні
-середовища під час виконання елементі. Це також пріоритетний шлях
-передавання змінних середовища елементам.
+Щоб встановити змінні середовища для виконання елементів, слід повідомити virt-dib, що слід використовувати ці змінні, за допомогою параметра I<--envvar>. Такий параметр надасть змогу вибірково експортувати змінні середовища під час виконання елементі. Це також пріоритетний шлях передавання змінних середовища елементам.
-І ще раз: якщо вам потрібно, щоб змінна середовища C<MYVAR> (і її вміст)
-були доступні елементам, вам слід або віддати команду
+І ще раз: якщо вам потрібно, щоб змінна середовища C<MYVAR> (і її вміст) були доступні елементам, вам слід або віддати команду
export MYVAR # яким би не було її значення
virt-dib ... --envvar MYVAR ...
=head1 ДОПОМІЖНИЙ ДИСК
-Virt-dib виконує більшість елементів у власній базовій системі, отже, не на
-основній системі. Через це, елементи не можуть кешувати ресурси
-безпосередньо на основній системі.
+Virt-dib виконує більшість елементів у власній базовій системі, отже, не на основній системі. Через це, елементи не можуть кешувати ресурси безпосередньо на основній системі.
-Щоб усунути цю незручність, у virt-dib передбачено можливість використання
-допоміжного диска, на якому можна зберігати кешовані ресурси, зокрема образи
-дисків, пакунки дистрибутивів тощо. Хоча це означає, що для кешування буде
-доступним менше місця, принаймні, це надає змогу обмежити простір у основній
-системі для кешів без потреби у виконанні цього завдання засобами самих
-елементів.
+Щоб усунути цю незручність, у virt-dib передбачено можливість використання допоміжного диска, на якому можна зберігати кешовані ресурси, зокрема образи дисків, пакунки дистрибутивів тощо. Хоча це означає, що для кешування буде доступним менше місця, принаймні, це надає змогу обмежити простір у основній системі для кешів без потреби у виконанні цього завдання засобами самих елементів.
-У поточній версії або цей диск має містити лише один розділ, або має
-використовуватися лише перший розділ з диска. Диск із другим варіантом
-конфігурації доволі просто створити за допомогою L<guestfish(1)> ось так:
+У поточній версії або цей диск має містити лише один розділ, або має використовуватися лише перший розділ з диска. Диск із другим варіантом конфігурації доволі просто створити за допомогою L<guestfish(1)> ось так:
guestfish -N filename.img=fs:ext4:10G exit
-У результаті виконання наведеної вище команди буде створено образ диска із
-назвою F<filename.img> об'ємом у 10 ГБ з одним розділом типу ext4;
-див. L<guestfish(1)/ОБРАЗИ ПРИГОТОВАНИХ ДИСКІВ>.
+У результаті виконання наведеної вище команди буде створено образ диска із назвою F<filename.img> об'ємом у 10 ГБ з одним розділом типу ext4; див. L<guestfish(1)/ОБРАЗИ ПРИГОТОВАНИХ ДИСКІВ>.
-Рекомендованим розміром диска є E<ge> 10 ГБ, оскільки елементи кешуватимуть
-образи дисків, пакунки дистрибутивів тощо. Як і розмір будь-якого образу
-диска, розмір допоміжного диска можна змінити за допомогою
-L<virt-resize(1)>, якщо раптом він стане замалим.
+Рекомендованим розміром диска є E<ge> 10 ГБ, оскільки елементи кешуватимуть образи дисків, пакунки дистрибутивів тощо. Як і розмір будь-якого образу диска, розмір допоміжного диска можна змінити за допомогою L<virt-resize(1)>, якщо раптом він стане замалим.
-Доступ до диска може здійснюватися у спосіб, який є подібним до способу
-доступу до будь-яких інших образів дисків, наприклад, за допомогою інших
-інструментів libguestfs, зокрема L<guestfish(1)>:
+Доступ до диска може здійснюватися у спосіб, який є подібним до способу доступу до будь-яких інших образів дисків, наприклад, за допомогою інших інструментів libguestfs, зокрема L<guestfish(1)>:
guestfish -a filename.img -m /dev/sda1
-Якщо за допомогою I<--drive> не вказано жодного допоміжного диска, усі
-ресурси, кешовані під час запуску virt-dib, буде відкинуто.
+Якщо за допомогою I<--drive> не вказано жодного допоміжного диска, усі ресурси, кешовані під час запуску virt-dib, буде відкинуто.
=head2 РЕСУРСИ НА ДИСКУ
=item F</home>
-Цей каталог задається за допомогою змінної середовища C<HOME> під час
-збирання. У ньому, здебільшого, міститься кеш образів (збережений до
-F</home/.cache/image-create>) та усі інші ресурси у домашньому каталозі
-користувача, який запускає різні інструменти.
+Цей каталог задається за допомогою змінної середовища C<HOME> під час збирання. У ньому, здебільшого, міститься кеш образів (збережений до F</home/.cache/image-create>) та усі інші ресурси у домашньому каталозі користувача, який запускає різні інструменти.
=item F</virt-dib-*.log>
-Це журнали елементів, які виконуються у базовій системі libguestfs, тобто
-усі фази, окрім C<extra-data.d>.
+Це журнали елементів, які виконуються у базовій системі libguestfs, тобто усі фази, окрім C<extra-data.d>.
=back
=head1 ЗБИРАННЯ ДИСКА У ПАМ'ЯТІ
-Virt-dib може також емулювати C<ramdisk-image-create>, вторинний режим
-роботи C<diskimage-builder>. Замість використання якогось інструмента із
-іншою назвою, virt-dib надає простий доступ до режиму за допомогою параметра
-I<--ramdisk>.
+Virt-dib може також емулювати C<ramdisk-image-create>, вторинний режим роботи C<diskimage-builder>. Замість використання якогось інструмента із іншою назвою, virt-dib надає простий доступ до режиму за допомогою параметра I<--ramdisk>.
У цьому режимі:
=head1 ТИМЧАСОВИЙ КАТАЛОГ
-Virt-dib використовує стандартний каталог для тимчасових файлів, який
-використовується libguestfs, див. L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
+Virt-dib використовує стандартний каталог для тимчасових файлів, який використовується libguestfs, див. L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
-Типово, цим каталогом є F</tmp> (типове значення для C<TMPDIR>). У деяких
-системах для цього каталогу може використовуватися файлова система
-tmpfs. Таким чином, типовим максимальним розміром для нього є I<половина>
-фізичного розміру оперативної пам'яті. Якщо під час роботи virt-dib
-перевищить це обмеження, програма може повиснути або завершити роботу
-передчасно із повідомленням про помилку. Усунути цю проблему можна, вказавши
-для C<TMPDIR> тимчасовий каталог. Приклад:
+Типово, цим каталогом є F</tmp> (типове значення для C<TMPDIR>). У деяких системах для цього каталогу може використовуватися файлова система tmpfs. Таким чином, типовим максимальним розміром для нього є I<половина> фізичного розміру оперативної пам'яті. Якщо під час роботи virt-dib перевищить це обмеження, програма може повиснути або завершити роботу передчасно із повідомленням про помилку. Усунути цю проблему можна, вказавши для C<TMPDIR> тимчасовий каталог. Приклад:
mkdir local-tmp
env TMPDIR=$PWD/local-tmp virt-dib ...
=head1 ДОДАТКОВІ ЗАЛЕЖНОСТІ
-Оскільки virt-dib запускає більшість елементів у власній базовій системі,
-усі інструменти та бібліотеки, які використовуються елементами, що
-запускаються поза межами гостьової системи (типово C<root.d>,
-C<block-device.d> та C<cleanup.d>) мають бути і у базовій системі. Якщо їх
-не буде, скрипти не зможуть працювати і типово повідомлять про помилку
-C<команду не знайдено>.
+Оскільки virt-dib запускає більшість елементів у власній базовій системі, усі інструменти та бібліотеки, які використовуються елементами, що запускаються поза межами гостьової системи (типово C<root.d>, C<block-device.d> та C<cleanup.d>) мають бути і у базовій системі. Якщо їх не буде, скрипти не зможуть працювати і типово повідомлять про помилку C<команду не знайдено>.
-Для інструментів і бібліотек, які містяться у пакунках дистрибутивів,
-простим рішенням цієї проблеми буде віддання наказу libguestfs включити
-додаткові пакунки до базової системи. Зробити це можна, наприклад, створення
-файла із додатковими пакунками:
+Для інструментів і бібліотек, які містяться у пакунках дистрибутивів, простим рішенням цієї проблеми буде віддання наказу libguestfs включити додаткові пакунки до базової системи. Зробити це можна, наприклад, створення файла із додатковими пакунками:
# echo wget > /usr/lib64/guestfs/supermin.d/dib-my-extra
-Шлях до каталогу F<supermin.d>, звичайно ж, залежить від дистрибутива. У
-додаткових файлах може бути список із багатьма пакунками, кожен з яких слід
-вказувати окремому рядку. Докладніший опис можна знайти у підручнику з
-L<supermin(1)>.
+Шлях до каталогу F<supermin.d>, звичайно ж, залежить від дистрибутива. У додаткових файлах може бути список із багатьма пакунками, кожен з яких слід вказувати окремому рядку. Докладніший опис можна знайти у підручнику з L<supermin(1)>.
=head1 ПОРІВНЯННЯ ІЗ DISKIMAGE-BUILDER
-Призначенням virt-dib є бути безпечним замінником програми
-C<diskimage-builder> і її режиму C<ramdisk-image-create>. Помітні для
-користувача відмінності полягають ось у чому:
+Призначенням virt-dib є бути безпечним замінником програми C<diskimage-builder> і її режиму C<ramdisk-image-create>. Помітні для користувача відмінності полягають ось у чому:
=over 4
=item
-аргументи командного рядка; деякі з аргументів збігаються із аргументами
-C<diskimage-builder>, але деякі є іншими:
+аргументи командного рядка; деякі з аргументів збігаються із аргументами C<diskimage-builder>, але деякі є іншими:
disk-image-create virt-dib
----------------- --------
=item
-розташування файлів-результатів, які не є образами (зокрема дисків у пам'яті
-і ядер)
+розташування файлів-результатів, які не є образами (зокрема дисків у пам'яті і ядер)
=item
-спосіб зберігання деяких кешованих ресурсів: використання допоміжного диска,
-а не диска, на якому запущено virt-dib
+спосіб зберігання деяких кешованих ресурсів: використання допоміжного диска, а не диска, на якому запущено virt-dib
=item
-потреба у визначення розміру диска-результату, тоді як програма
-C<diskimage-builder> автоматично обчислює оптимальний розмір
+потреба у визначення розміру диска-результату, тоді як програма C<diskimage-builder> автоматично обчислює оптимальний розмір
=item
обробка змінних середовища, див. L</ЗМІННІ СЕРЕДОВИЩА>.
-До того ж, окрім власних змінних середовища libguestfs
-(див. L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>), virt-dib не виконує читання жодних
-інших змінних середовища. Це означає, що зміни у параметрах і поведінці
-програми визначаються лише переданими їй аргументами рядка команди.
+До того ж, окрім власних змінних середовища libguestfs (див. L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>), virt-dib не виконує читання жодних інших змінних середовища. Це означає, що зміни у параметрах і поведінці програми визначаються лише переданими їй аргументами рядка команди.
=item
-потрібно, щоб додаткові інструменти на деяких фазах поза chroot були
-доступні у базовій системі, див. L</ДОДАТКОВІ ЗАЛЕЖНОСТІ>.
+потрібно, щоб додаткові інструменти на деяких фазах поза chroot були доступні у базовій системі, див. L</ДОДАТКОВІ ЗАЛЕЖНОСТІ>.
=back
-Робота самих елементів не повинна зазнати змін; причиною відмінностей у
-поведінці можуть бути помилкові припущення у коді самих елементів або
-некоректна емуляція virt-dib.
+Робота самих елементів не повинна зазнати змін; причиною відмінностей у поведінці можуть бути помилкові припущення у коді самих елементів або некоректна емуляція virt-dib.
Відомі вади:
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-dib з інших програм, графічних інтерфейсів
-тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-dib з інших програм, графічних інтерфейсів тощо.
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-dib. Типово виведені дані виглядатимуть якось так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-dib. Типово виведені дані виглядатимуть якось так:
$ virt-dib --machine-readable
virt-dib
output:raw
output:vhd
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-C<output:> є вказівкою на формати виведення (параметр рядка команди
-I<--formats>), підтримку яких передбачено у цьому виконуваному файлі.
+C<output:> є вказівкою на формати виведення (параметр рядка команди I<--formats>), підтримку яких передбачено у цьому виконуваному файлі.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 ТЕСТУВАННЯ
-Перевірку працездатності virt-dib було виконано для C<diskimage-builder> (та
-його елементів) E<ge> 0.1.43. Час від часу виконується також перевірка для
-C<tripleo-image-elements> та C<sahara-image-elements>.
+Перевірку працездатності virt-dib було виконано для C<diskimage-builder> (та його елементів) E<ge> 0.1.43. Час від часу виконується також перевірка для C<tripleo-image-elements> та C<sahara-image-elements>.
Попередні версії також можуть працювати, але цього не можна гарантувати.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-resize(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-diff 1"
-.TH virt-diff 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-diff 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-diff\*(C'\fR показує список відмінностей між файлами у двох віртуальних
-машинах або на двох образах дисків. Звичайним випадком застосування є показ
-змін у віртуальній машині після певного проміжку роботи: можна зробити
-знімок, запустити віртуальну машину, а потім скористатися цією програмою для
-перегляду змін, які відрізняють новий стан віртуальної машини і старий її
-знімок.
+\&\f(CW\*(C`virt\-diff\*(C'\fR показує список відмінностей між файлами у двох віртуальних машинах або на двох образах дисків. Звичайним випадком застосування є показ змін у віртуальній машині після певного проміжку роботи: можна зробити знімок, запустити віртуальну машину, а потім скористатися цією програмою для перегляду змін, які відрізняють новий стан віртуальної машини і старий її знімок.
.PP
-Ця програма виявить відмінності у назвах файлів, розмірах файлів,
-контрольних сумах, розширених атрибутах, вмісті файлів та інших даних з
-віртуальної машини або образу диска. Втім, вона \fBне\fR шукатиме відмінності у
-завантажувачі, невикористаному місці між розділами або всередині файлових
-систем, «прихованих» секторах тощо. Іншими словами, це не інструмент
-вивчення питань безпеки або ретельного дослідження.
+Ця програма виявить відмінності у назвах файлів, розмірах файлів, контрольних сумах, розширених атрибутах, вмісті файлів та інших даних з віртуальної машини або образу диска. Втім, вона \fBне\fR шукатиме відмінності у завантажувачі, невикористаному місці між розділами або всередині файлових систем, «прихованих» секторах тощо. Іншими словами, це не інструмент вивчення питань безпеки або ретельного дослідження.
.PP
-Щоб вказати дві гостьові системи, вам слід скористатися параметром \fI\-a\fR або
-\&\fI\-d\fR для першої гостьової системи і параметром \fI\-A\fR або \fI\-D\fR для
-другої. Типовий варіант команди:
+Щоб вказати дві гостьові системи, вам слід скористатися параметром \fI\-a\fR або \fI\-d\fR для першої гостьової системи і параметром \fI\-A\fR або \fI\-D\fR для другої. Типовий варіант команди:
.PP
.Vb 1
\& virt\-diff \-a старий.img \-A новий.img
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з першої віртуальної
-машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід
-вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з першої віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
Те саме, що \fI\-\-extra\-stats\fR \fI\-\-times\fR \fI\-\-uids\fR \fI\-\-xattrs\fR.
.IP "\fB\-\-atime\fR" 4
.IX Item "--atime"
-Типово, зміни у часі доступу до файла ігноруватимуться, оскільки вони,
-зазвичай, не варті уваги. Якщо буде використано цей параметр, програма
-показуватиме і відмінності у значеннях часу доступу.
+Типово, зміни у часі доступу до файла ігноруватимуться, оскільки вони, зазвичай, не варті уваги. Якщо буде використано цей параметр, програма показуватиме і відмінності у значеннях часу доступу.
.IP "\fB\-A\fR файл" 4
.IX Item "-A файл"
.PD 0
.IP "\fB\-\-checksum=crc|md5|sha1|sha224|sha256|sha384|sha512\fR" 4
.IX Item "--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512"
.PD
-Використовувати контрольну суму вмісту файла для визначення випадків зміни
-вмісту файла.
+Використовувати контрольну суму вмісту файла для визначення випадків зміни вмісту файла.
.Sp
-Без аргументів, типово, буде використано \fImd5\fR. За допомогою аргументу ви
-можете вказати тип контрольної суми, яку буде використано. Якщо прапорець не
-вказано, для визначення того, чи було змінено файл, буде використано часові
-параметри та розмір файла.
+Без аргументів, типово, буде використано \fImd5\fR. За допомогою аргументу ви можете вказати тип контрольної суми, яку буде використано. Якщо прапорець не вказано, для визначення того, чи було змінено файл, буде використано часові параметри та розмір файла.
.IP "\fB\-c\fR адреса" 4
.IX Item "-c адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0,
-наведеним нижче.
+Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0, наведеним нижче.
.IP "\fB\-\-dir\-links\fR" 4
.IX Item "--dir-links"
-Типово, програма ігнорує зміну у кількості посилань для записів каталогів,
-оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього
-прапорця ви можете наказати програмі показувати зміни у полі nlink для
-каталогів.
+Типово, програма ігнорує зміну у кількості посилань для записів каталогів, оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього прапорця ви можете наказати програмі показувати зміни у полі nlink для каталогів.
.IP "\fB\-\-dir\-times\fR" 4
.IX Item "--dir-times"
-Типово, програма ігнорує зміну часових параметрів для записів каталогів,
-оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього
-прапорця ви можете наказати програмі показувати зміни у полях часових
-параметрів каталогів.
+Типово, програма ігнорує зміну часових параметрів для записів каталогів, оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього прапорця ви можете наказати програмі показувати зміни у полях часових параметрів каталогів.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt як першої гостьової
-системи. \s-1UUID\s0 доменів можна використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt як першої гостьової системи. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-D\fR гість" 4
.IX Item "-D гість"
-Додати всі диски з вказаної гостьової системи libvirt як другої гостьової
-системи. \s-1UUID\s0 доменів можна використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt як другої гостьової системи. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-diff попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-diff попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-extra\-stats\fR" 4
.IX Item "--extra-stats"
Показати додаткові дані.
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR/\fI\-A\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR/\fI\-A\fR формату диска у наступному рядку
-команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму
-у режим автоматичного визначення у наступних параметрах \fI\-a\fR/\fI\-A\fR.
+Типовим значенням для параметра \fI\-a\fR/\fI\-A\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR/\fI\-A\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR/\fI\-A\fR.
.Sp
Приклад:
.Sp
\& virt\-diff \-\-format=raw \-a disk.img [...]
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-diff \-\-format=raw \-a disk.img \-\-format \-a another.img [...]
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
Показати поля часу.
.IP "\fB\-\-time\-days\fR" 4
.IX Item "--time-days"
-Показувати поля часу у форматі днів до поточного (від’ємні значення для днів
-у майбутньому).
+Показувати поля часу у форматі днів до поточного (від’ємні значення для днів у майбутньому).
.Sp
-Зауважте, що \f(CW0\fR у виведених даних означає «менше 1 одного дня до поточного
-моменту» або «вік файла — від 0 до 86399 секунд».
+Зауважте, що \f(CW0\fR у виведених даних означає «менше 1 одного дня до поточного моменту» або «вік файла — від 0 до 86399 секунд».
.IP "\fB\-\-time\-relative\fR" 4
.IX Item "--time-relative"
-Показувати поля часу у форматі секунд до поточного моменту (від’ємні
-значення для часу у майбутньому).
+Показувати поля часу у форматі секунд до поточного моменту (від’ємні значення для часу у майбутньому).
.IP "\fB\-\-time\-t\fR" 4
.IX Item "--time-t"
Показувати поля часу у форматі секунд з моменту початку епохи \s-1UNIX.\s0
Показати розширені атрибути.
.SH "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
.IX Header "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
-Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може
-\&\fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може \fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
.PP
-Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR працює у надійний спосіб. Ось приклад із двома стовпчиками:
.PP
.Vb 1
\& "foo,bar",baz
.Ve
.PP
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось приклад із одним рядком:
.PP
.Vb 2
\& "foo
\& bar",baz
.Ve
.PP
-Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR
-(https://github.com/Chris00/ocaml\-csv також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv також є серед пакунків основних дистрибутивів Linux).
.PP
-Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0
-(наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0 (наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
.PP
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних \s-1CSV.\s0
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних \s-1CSV.\s0
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-ls\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-ls\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-C<virt-diff> показує список відмінностей між файлами у двох віртуальних
-машинах або на двох образах дисків. Звичайним випадком застосування є показ
-змін у віртуальній машині після певного проміжку роботи: можна зробити
-знімок, запустити віртуальну машину, а потім скористатися цією програмою для
-перегляду змін, які відрізняють новий стан віртуальної машини і старий її
-знімок.
-
-Ця програма виявить відмінності у назвах файлів, розмірах файлів,
-контрольних сумах, розширених атрибутах, вмісті файлів та інших даних з
-віртуальної машини або образу диска. Втім, вона B<не> шукатиме відмінності у
-завантажувачі, невикористаному місці між розділами або всередині файлових
-систем, «прихованих» секторах тощо. Іншими словами, це не інструмент
-вивчення питань безпеки або ретельного дослідження.
-
-Щоб вказати дві гостьові системи, вам слід скористатися параметром I<-a> або
-I<-d> для першої гостьової системи і параметром I<-A> або I<-D> для
-другої. Типовий варіант команди:
+C<virt-diff> показує список відмінностей між файлами у двох віртуальних машинах або на двох образах дисків. Звичайним випадком застосування є показ змін у віртуальній машині після певного проміжку роботи: можна зробити знімок, запустити віртуальну машину, а потім скористатися цією програмою для перегляду змін, які відрізняють новий стан віртуальної машини і старий її знімок.
+
+Ця програма виявить відмінності у назвах файлів, розмірах файлів, контрольних сумах, розширених атрибутах, вмісті файлів та інших даних з віртуальної машини або образу диска. Втім, вона B<не> шукатиме відмінності у завантажувачі, невикористаному місці між розділами або всередині файлових систем, «прихованих» секторах тощо. Іншими словами, це не інструмент вивчення питань безпеки або ретельного дослідження.
+
+Щоб вказати дві гостьові системи, вам слід скористатися параметром I<-a> або I<-d> для першої гостьової системи і параметром I<-A> або I<-D> для другої. Типовий варіант команди:
virt-diff -a старий.img -A новий.img
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з першої віртуальної
-машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід
-вказати їх усі за допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з першої віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a> адреса
=item B<--atime>
-Типово, зміни у часі доступу до файла ігноруватимуться, оскільки вони,
-зазвичай, не варті уваги. Якщо буде використано цей параметр, програма
-показуватиме і відмінності у значеннях часу доступу.
+Типово, зміни у часі доступу до файла ігноруватимуться, оскільки вони, зазвичай, не варті уваги. Якщо буде використано цей параметр, програма показуватиме і відмінності у значеннях часу доступу.
=item B<-A> файл
=item B<--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512>
-Використовувати контрольну суму вмісту файла для визначення випадків зміни
-вмісту файла.
+Використовувати контрольну суму вмісту файла для визначення випадків зміни вмісту файла.
-Без аргументів, типово, буде використано I<md5>. За допомогою аргументу ви
-можете вказати тип контрольної суми, яку буде використано. Якщо прапорець не
-вказано, для визначення того, чи було змінено файл, буде використано часові
-параметри та розмір файла.
+Без аргументів, типово, буде використано I<md5>. За допомогою аргументу ви можете вказати тип контрольної суми, яку буде використано. Якщо прапорець не вказано, для визначення того, чи було змінено файл, буде використано часові параметри та розмір файла.
=item B<-c> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<--csv>
-Вивести результати до формату CSV (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>,
-наведеним нижче.
+Вивести результати до формату CSV (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>, наведеним нижче.
=item B<--dir-links>
-Типово, програма ігнорує зміну у кількості посилань для записів каталогів,
-оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього
-прапорця ви можете наказати програмі показувати зміни у полі nlink для
-каталогів.
+Типово, програма ігнорує зміну у кількості посилань для записів каталогів, оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього прапорця ви можете наказати програмі показувати зміни у полі nlink для каталогів.
=item B<--dir-times>
-Типово, програма ігнорує зміну часових параметрів для записів каталогів,
-оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього
-прапорця ви можете наказати програмі показувати зміни у полях часових
-параметрів каталогів.
+Типово, програма ігнорує зміну часових параметрів для записів каталогів, оскільки така зміна навряд чи є цікавою для користувача. За допомогою цього прапорця ви можете наказати програмі показувати зміни у полях часових параметрів каталогів.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt як першої гостьової
-системи. UUID доменів можна використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt як першої гостьової системи. UUID доменів можна використовувати замість назв.
=item B<-D> гість
-Додати всі диски з вказаної гостьової системи libvirt як другої гостьової
-системи. UUID доменів можна використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt як другої гостьової системи. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-diff попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-diff попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--extra-stats>
=item B<--format>
-Типовим значенням для параметра I<-a>/I<-A> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a>/I<-A> формату диска у наступному рядку
-команди. Використання параметра I<--format> без аргументу перемикає програму
-у режим автоматичного визначення у наступних параметрах I<-a>/I<-A>.
+Типовим значенням для параметра I<-a>/I<-A> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a>/I<-A> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>/I<-A>.
Приклад:
virt-diff --format=raw -a disk.img [...]
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-diff --format=raw -a disk.img --format -a another.img [...]
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<-h>
=item B<--time-days>
-Показувати поля часу у форматі днів до поточного (від’ємні значення для днів
-у майбутньому).
+Показувати поля часу у форматі днів до поточного (від’ємні значення для днів у майбутньому).
-Зауважте, що C<0> у виведених даних означає «менше 1 одного дня до поточного
-моменту» або «вік файла — від 0 до 86399 секунд».
+Зауважте, що C<0> у виведених даних означає «менше 1 одного дня до поточного моменту» або «вік файла — від 0 до 86399 секунд».
=item B<--time-relative>
-Показувати поля часу у форматі секунд до поточного моменту (від’ємні
-значення для часу у майбутньому).
+Показувати поля часу у форматі секунд до поточного моменту (від’ємні значення для часу у майбутньому).
=item B<--time-t>
=head1 ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV
-Формат значень, які відокремлено комами (CSV), є оманливо простим. Може
-I<здатися>, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (CSV), є оманливо простим. Може I<здатися>, що його просто обробляти, але насправді це зовсім не так.
-Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не>
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не> працює у надійний спосіб. Ось приклад із двома стовпчиками:
"foo,bar",baz
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось приклад із одним рядком:
"foo
bar",baz
-Для скриптів командної оболонки скористайтеся C<csvtool>
-(L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся C<csvtool> (L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних дистрибутивів Linux).
-Для інших мов програмування використовуйте бібліотеку для обробки даних CSV
-(наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних CSV (наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних CSV.
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних CSV.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-ls(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-ls(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-edit 1"
-.TH virt-edit 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-edit 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-edit\*(C'\fR — інструмент командного рядка для редагування \f(CW\*(C`файла\*(C'\fR, який
-зберігається у вказаній віртуальній машині (або образі диска).
+\&\f(CW\*(C`virt\-edit\*(C'\fR — інструмент командного рядка для редагування \f(CW\*(C`файла\*(C'\fR, який зберігається у вказаній віртуальній машині (або образі диска).
.PP
-Ви можете вказати декілька назв файлів. Вміст таких файлів буде редаговано
-послідовно. Назви файлів слід вказувати повністю (разом зі шляхом),
-починаючи з кореневого каталогу (тобто назва має починатися з «/»).
+Ви можете вказати декілька назв файлів. Вміст таких файлів буде редаговано послідовно. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи з кореневого каталогу (тобто назва має починатися з «/»).
.PP
Якщо ви просто хочете переглянути файл, скористайтеся \fBvirt\-cat\fR\|(1).
.PP
-Для виконання складніших дій можна скористатися програмою \fBguestfish\fR\|(1)
-(див. \*(L"ВИКОРИСТАННЯ \s-1GUESTFISH\*(R"\s0 нижче).
+Для виконання складніших дій можна скористатися програмою \fBguestfish\fR\|(1) (див. \*(L"ВИКОРИСТАННЯ \s-1GUESTFISH\*(R"\s0 нижче).
.PP
-\&\f(CW\*(C`virt\-edit\*(C'\fR не можна використовувати для створення файлів. Для цього, та
-багатьох інших завдань, слід використовувати \fBguestfish\fR\|(1).
+\&\f(CW\*(C`virt\-edit\*(C'\fR не можна використовувати для створення файлів. Для цього, та багатьох інших завдань, слід використовувати \fBguestfish\fR\|(1).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
Інтерактивне редагування іменованих файлів:
\& virt\-edit \-d mydomain /etc/passwd
.Ve
.PP
-Для гостьових систем Windows передбачено розпізнавання таких шляхів у
-Windows:
+Для гостьових систем Windows передбачено розпізнавання таких шляхів у Windows:
.PP
.Vb 1
\& virt\-edit \-d mywindomain \*(Aqc:\eautoexec.bat\*(Aq
.Ve
.PP
-Якщо встановлено Perl, ви також можете редагувати файли у неінтерактивному
-режимі (див. \*(L"НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ\*(R" нижче). Щоб змінити типовий
-рівень init на 5:
+Якщо встановлено Perl, ви також можете редагувати файли у неінтерактивному режимі (див. \*(L"НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ\*(R" нижче). Щоб змінити типовий рівень init на 5:
.PP
.Vb 1
\& virt\-edit \-d mydomain /etc/inittab \-e \*(Aqs/^id:.*/id:5:initdefault:/\*(Aq
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-backup\fR СУФІКС" 4
.IX Item "--backup СУФІКС"
.PD
-Створити резервну копію початкового файла \fIу образі диска гостьової
-системи\fR. Резервна копія матиме таку саму назву, що і початковий файл, із
-додаванням суфікса \f(CW\*(C`суфікс\*(C'\fR.
+Створити резервну копію початкового файла \fIу образі диска гостьової системи\fR. Резервна копія матиме таку саму назву, що і початковий файл, із додаванням суфікса \f(CW\*(C`суфікс\*(C'\fR.
.Sp
-Зазвичай, першим символом суфікса \f(CW\*(C`суфікс\*(C'\fR буде крапка, \f(CW\*(C`.\*(C'\fR, отже, можна
-віддати таку команду:
+Зазвичай, першим символом суфікса \f(CW\*(C`суфікс\*(C'\fR буде крапка, \f(CW\*(C`.\*(C'\fR, отже, можна віддати таку команду:
.Sp
.Vb 1
\& virt\-edit \-b .orig [тощо]
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не
-буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR ГІСТЬ" 4
.IX Item "-d ГІСТЬ"
.PD 0
.IP "\fB\-\-domain\fR ГІСТЬ" 4
.IX Item "--domain ГІСТЬ"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-edit попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-edit попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-e\fR вираз" 4
.IX Item "-e вираз"
.PD 0
.IP "\fB\-\-expr\fR вираз" 4
.IX Item "--expr вираз"
.PD
-Замість запуску зовнішнього редактора, неінтерактивно застосувати вираз Perl
-\&\f(CW\*(C`ВИРАЗ\*(C'\fR до усіх рядків файла. Див. \*(L"НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ\*(R" нижче.
+Замість запуску зовнішнього редактора, неінтерактивно застосувати вираз Perl \f(CW\*(C`ВИРАЗ\*(C'\fR до усіх рядків файла. Див. \*(L"НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ\*(R" нижче.
.Sp
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
.Sp
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-edit \-\-format=raw \-a диск.img файл
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-cat \-\-format=raw \-a диск.img \-\-format \-a інший.img файл
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.Sp
Якщо точку монтування не вказано, типовим значенням є \fI/\fR.
.Sp
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
.Sp
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-\&\*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися
-програмою \fBvirt\-filesystems\fR\|(1).
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися програмою \fBvirt\-filesystems\fR\|(1).
.Sp
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант
-використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Ve
.Sp
-Використання цього прапорця є еквівалентним до використання команди
-\&\f(CW\*(C`mount\-options\*(C'\fR.
+Використання цього прапорця є еквівалентним до використання команди \f(CW\*(C`mount\-options\*(C'\fR.
.Sp
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR
-і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
\& virt\-edit назва_гостьової_системи файл
.Ve
.PP
-тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
.PP
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
.SH "НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ"
.IX Header "НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ"
-\&\f(CW\*(C`virt\-edit\*(C'\fR зазвичай викликає \f(CW$EDITOR\fR (або vi), щоб адміністратор
-системи зміг інтерактивно редагувати файл.
+\&\f(CW\*(C`virt\-edit\*(C'\fR зазвичай викликає \f(CW$EDITOR\fR (або vi), щоб адміністратор системи зміг інтерактивно редагувати файл.
.PP
-Передбачено також два способи використання \f(CW\*(C`virt\-edit\*(C'\fR зі скриптів з метою
-автоматизації редагування файлів. (Зауважте, що хоча ви \fIможете\fR
-користуватися \f(CW\*(C`virt\-edit\*(C'\fR у цей спосіб, стійкішим до помилок буде написання
-скриптів, які безпосередньо використовують програмний інтерфейс libguestfs
-та Augeas для редагування файлів налаштувань.)
+Передбачено також два способи використання \f(CW\*(C`virt\-edit\*(C'\fR зі скриптів з метою автоматизації редагування файлів. (Зауважте, що хоча ви \fIможете\fR користуватися \f(CW\*(C`virt\-edit\*(C'\fR у цей спосіб, стійкішим до помилок буде написання скриптів, які безпосередньо використовують програмний інтерфейс libguestfs та Augeas для редагування файлів налаштувань.)
.PP
-Першим методом є тимчасове встановлення \f(CW$EDITOR\fR у значення назви скрипту
-або програми, яку ви хочете запустити. Скрипт буде викликано у форматі
-\&\f(CW\*(C`$EDITOR tmpfile\*(C'\fR, він має оновлювати \f(CW\*(C`tmpfile\*(C'\fR на місці у будь\-який
-спосіб.
+Першим методом є тимчасове встановлення \f(CW$EDITOR\fR у значення назви скрипту або програми, яку ви хочете запустити. Скрипт буде викликано у форматі \f(CW\*(C`$EDITOR tmpfile\*(C'\fR, він має оновлювати \f(CW\*(C`tmpfile\*(C'\fR на місці у будь\-який спосіб.
.PP
-Другим методом є використання параметра \fI\-e\fR програми \f(CW\*(C`virt\-edit\*(C'\fR для
-запуску короткого фрагмента коду Perl у стилі \fBsed\fR\|(1). Наприклад, щоб
-змінити усі екземпляри \f(CW\*(C`foo\*(C'\fR на \f(CW\*(C`bar\*(C'\fR у файлі, віддайте таку команду:
+Другим методом є використання параметра \fI\-e\fR програми \f(CW\*(C`virt\-edit\*(C'\fR для запуску короткого фрагмента коду Perl у стилі \fBsed\fR\|(1). Наприклад, щоб змінити усі екземпляри \f(CW\*(C`foo\*(C'\fR на \f(CW\*(C`bar\*(C'\fR у файлі, віддайте таку команду:
.PP
.Vb 1
\& virt\-edit \-d назва_домену назва_файла \-e \*(Aqs/foo/bar/\*(Aq
.Ve
.PP
-Можна скористатися усією потужністю формальних виразів Perl
-(див. \fBperlre\fR\|(1)). Наприклад, для вилучення пароля root ви можете віддати
-таку команду:
+Можна скористатися усією потужністю формальних виразів Perl (див. \fBperlre\fR\|(1)). Наприклад, для вилучення пароля root ви можете віддати таку команду:
.PP
.Vb 1
\& virt\-edit \-d назва_домену /etc/passwd \-e \*(Aqs/^root:.*?:/root::/\*(Aq
.Ve
.PP
-Під час обробки команди вираз Perl застосовується до кожного з рядків
-файла. Рядок, разом із кінцевим \f(CW\*(C`\en\*(C'\fR, передається у \f(CW$_\fR, а вираз має
-оновити \f(CW$_\fR або лишити його вміст без змін.
+Під час обробки команди вираз Perl застосовується до кожного з рядків файла. Рядок, разом із кінцевим \f(CW\*(C`\en\*(C'\fR, передається у \f(CW$_\fR, а вираз має оновити \f(CW$_\fR або лишити його вміст без змін.
.PP
-Щоб вилучити рядок, встановіть для \f(CW$_\fR значення порожнього
-рядка. Наприклад, щоб вилучити обліковий запис \f(CW\*(C`apache\*(C'\fR з файла паролів, ви
-можете віддати таку команду:
+Щоб вилучити рядок, встановіть для \f(CW$_\fR значення порожнього рядка. Наприклад, щоб вилучити обліковий запис \f(CW\*(C`apache\*(C'\fR з файла паролів, ви можете віддати таку команду:
.PP
.Vb 1
\& virt\-edit \-d mydomain /etc/passwd \-e \*(Aq$_ = "" if /^apache:/\*(Aq
.Ve
.PP
-Щоб вставити рядок, допишіть його на початку або наприкінці \f(CW$_\fR. Втім,
-дописування рядків наприкінці файла у цей спосіб є доволі складною справою —
-оскільки не існує загального поняття «останній рядок файла», ваш вираз
-просто не буде викликано ще раз. Якщо ви хочете дописати рядок наприкінці
-файла, вам варто скористатися першим методом (встановленням значення для
-\&\f(CW$EDITOR\fR).
+Щоб вставити рядок, допишіть його на початку або наприкінці \f(CW$_\fR. Втім, дописування рядків наприкінці файла у цей спосіб є доволі складною справою — оскільки не існує загального поняття «останній рядок файла», ваш вираз просто не буде викликано ще раз. Якщо ви хочете дописати рядок наприкінці файла, вам варто скористатися першим методом (встановленням значення для \f(CW$EDITOR\fR).
.PP
-Змінна \f(CW$lineno\fR містить значення номера поточного рядка. За традицією,
-перший рядок файла має номер \f(CW1\fR.
+Змінна \f(CW$lineno\fR містить значення номера поточного рядка. За традицією, перший рядок файла має номер \f(CW1\fR.
.PP
-Значення, повернуте у результаті обробки виразу, ігнорується, але вираз може
-викликати \f(CW\*(C`die\*(C'\fR з метою переривання усієї програми без внесення змін до
-початкового файла.
+Значення, повернуте у результаті обробки виразу, ігнорується, але вираз може викликати \f(CW\*(C`die\*(C'\fR з метою переривання усієї програми без внесення змін до початкового файла.
.PP
-Слід пам'ятати, що відповідник кінця рядка при використанні \f(CW$_\fR може
-містити кінцеве \f(CW\*(C`\en\*(C'\fR або (у файлах \s-1DOS\s0) \f(CW\*(C`\er\en\*(C'\fR, або, якщо файл не
-закінчується символом нового рядка, жодну з цих послідовностей. Тому для
-пошуку або заміни певного тексту наприкінці рядка слід використовувати такий
-формальний вираз:
+Слід пам'ятати, що відповідник кінця рядка при використанні \f(CW$_\fR може містити кінцеве \f(CW\*(C`\en\*(C'\fR або (у файлах \s-1DOS\s0) \f(CW\*(C`\er\en\*(C'\fR, або, якщо файл не закінчується символом нового рядка, жодну з цих послідовностей. Тому для пошуку або заміни певного тексту наприкінці рядка слід використовувати такий формальний вираз:
.PP
.Vb 1
\& /якийсь текст(\er?\en)?$/
.Ve
.PP
-Альтернативним варіантом є використання функції \f(CW\*(C`chomp\*(C'\fR Perl, але так, щоб
-не обрізати саме \f(CW$_\fR (оскільки ця функція вилучає усі символи нового рядка
-з файла):
+Альтернативним варіантом є використання функції \f(CW\*(C`chomp\*(C'\fR Perl, але так, щоб не обрізати саме \f(CW$_\fR (оскільки ця функція вилучає усі символи нового рядка з файла):
.PP
.Vb 1
\& my $m = $_; chomp $m; $m =~ /якийсь текст$/
.Ve
.SH "ШЛЯХИ У WINDOWS"
.IX Header "ШЛЯХИ У WINDOWS"
-У \f(CW\*(C`virt\-edit\*(C'\fR передбачено обмежені можливості щодо обробки літерних дисків
-та шляхів у Windows (наприклад \fIE:\efoo\ebar.txt\fR).
+У \f(CW\*(C`virt\-edit\*(C'\fR передбачено обмежені можливості щодо обробки літерних дисків та шляхів у Windows (наприклад \fIE:\efoo\ebar.txt\fR).
.PP
Тоді і лише тоді, коли у гостьовій системі працює Windows:
.IP "\(bu" 4
-Літери дисків, наприклад \f(CW\*(C`C:\*(C'\fR, замінюються на адреси відповідних файлових
-систем на основі даних з регістру Windows.
+Літери дисків, наприклад \f(CW\*(C`C:\*(C'\fR, замінюються на адреси відповідних файлових систем на основі даних з регістру Windows.
.IP "\(bu" 4
-Усі символи зворотної похилої риски (\f(CW\*(C`\e\*(C'\fR) у шляху замінюються символами
-звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
+Усі символи зворотної похилої риски (\f(CW\*(C`\e\*(C'\fR) у шляху замінюються символами звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
.IP "\(bu" 4
-Шлях до файла, вміст якого має бути редаговано, визначається без врахування
-регістру символів у його записі.
+Шлях до файла, вміст якого має бути редаговано, визначається без врахування регістру символів у його записі.
.PP
Відомі певні недоліки програми:
.IP "\(bu" 4
-Перехід за деякими символічними посиланнями \s-1NTFS\s0 може здійснюватися з
-помилками.
+Перехід за деякими символічними посиланнями \s-1NTFS\s0 може здійснюватися з помилками.
.IP "\(bu" 4
-Точки з'єднання \s-1NTFS,\s0 які виходять за межі однією файлової системи
-використовувати не можна.
+Точки з'єднання \s-1NTFS,\s0 які виходять за межі однією файлової системи використовувати не можна.
.SH "ВИКОРИСТАННЯ GUESTFISH"
.IX Header "ВИКОРИСТАННЯ GUESTFISH"
-\&\fBguestfish\fR\|(1) є потужнішим інструментом нижчого рівня, яким можна
-скористатися, якщо \f(CW\*(C`virt\-edit\*(C'\fR не працює.
+\&\fBguestfish\fR\|(1) є потужнішим інструментом нижчого рівня, яким можна скористатися, якщо \f(CW\*(C`virt\-edit\*(C'\fR не працює.
.PP
Використання \f(CW\*(C`virt\-edit\*(C'\fR є приблизним еквівалентом такого:
.PP
\& guestfish \-\-rw \-i \-d назва_домену edit /файл
.Ve
.PP
-де \f(CW\*(C`назва_домену\*(C'\fR — назва гостьової системи libvirt, а \fIфайл\fR — шлях до
-файла повністю.
+де \f(CW\*(C`назва_домену\*(C'\fR — назва гостьової системи libvirt, а \fIфайл\fR — шлях до файла повністю.
.PP
-У вказаній вище команді використано можливість інспектування гостьових
-систем засобами libguestfs, отже, вона не працюватиме у гостьових системах,
-які libguestfs не може інспектувати, або у довільних образах дисків, які не
-містять гостьових систем. Щоб редагувати дані файла безпосередньо на образі
-диска, скористайтеся такою командою:
+У вказаній вище команді використано можливість інспектування гостьових систем засобами libguestfs, отже, вона не працюватиме у гостьових системах, які libguestfs не може інспектувати, або у довільних образах дисків, які не містять гостьових систем. Щоб редагувати дані файла безпосередньо на образі диска, скористайтеся такою командою:
.PP
.Vb 1
\& guestfish \-\-rw \-a диск.img \-m /dev/sda1 edit /файл
.Ve
.PP
-де \fIдиск.img\fR — образ диска, \fI/dev/sda1\fR — файлова система у образі диска
-для редагування, а \fIфайл\fR — шлях до файла повністю.
+де \fIдиск.img\fR — образ диска, \fI/dev/sda1\fR — файлова система у образі диска для редагування, а \fIфайл\fR — шлях до файла повністю.
.PP
-Програма \f(CW\*(C`virt\-edit\*(C'\fR не здатна створювати файли. Для створення слід
-користуватися командами guestfish \f(CW\*(C`touch\*(C'\fR, \f(CW\*(C`write\*(C'\fR та \f(CW\*(C`upload\*(C'\fR:
+Програма \f(CW\*(C`virt\-edit\*(C'\fR не здатна створювати файли. Для створення слід користуватися командами guestfish \f(CW\*(C`touch\*(C'\fR, \f(CW\*(C`write\*(C'\fR та \f(CW\*(C`upload\*(C'\fR:
.PP
.Vb 1
\& guestfish \-\-rw \-i \-d назва_домену touch /новий_файл
.ie n .IP """EDITOR""" 4
.el .IP "\f(CWEDITOR\fR" 4
.IX Item "EDITOR"
-Якщо встановлено, цей рядок використовуватиметься для виклику
-редактора. Рядок може містити аргументи, наприклад, \f(CW"emacs \-nw"\fR
+Якщо встановлено, цей рядок використовуватиметься для виклику редактора. Рядок може містити аргументи, наприклад, \f(CW"emacs \-nw"\fR
.Sp
Якщо не встановлено, використовуватиметься \f(CW\*(C`vi\*(C'\fR.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-in\fR\|(1),
-\&\fBvirt\-tar\-in\fR\|(1), http://libguestfs.org/, \fBperl\fR\|(1), \fBperlre\fR\|(1).
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-in\fR\|(1), \fBvirt\-tar\-in\fR\|(1), http://libguestfs.org/, \fBperl\fR\|(1), \fBperlre\fR\|(1).
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-C<virt-edit> — інструмент командного рядка для редагування C<файла>, який
-зберігається у вказаній віртуальній машині (або образі диска).
+C<virt-edit> — інструмент командного рядка для редагування C<файла>, який зберігається у вказаній віртуальній машині (або образі диска).
-Ви можете вказати декілька назв файлів. Вміст таких файлів буде редаговано
-послідовно. Назви файлів слід вказувати повністю (разом зі шляхом),
-починаючи з кореневого каталогу (тобто назва має починатися з «/»).
+Ви можете вказати декілька назв файлів. Вміст таких файлів буде редаговано послідовно. Назви файлів слід вказувати повністю (разом зі шляхом), починаючи з кореневого каталогу (тобто назва має починатися з «/»).
Якщо ви просто хочете переглянути файл, скористайтеся L<virt-cat(1)>.
-Для виконання складніших дій можна скористатися програмою L<guestfish(1)>
-(див. L</ВИКОРИСТАННЯ GUESTFISH> нижче).
+Для виконання складніших дій можна скористатися програмою L<guestfish(1)> (див. L</ВИКОРИСТАННЯ GUESTFISH> нижче).
-C<virt-edit> не можна використовувати для створення файлів. Для цього, та
-багатьох інших завдань, слід використовувати L<guestfish(1)>.
+C<virt-edit> не можна використовувати для створення файлів. Для цього, та багатьох інших завдань, слід використовувати L<guestfish(1)>.
=head1 ПРИКЛАДИ
virt-edit -d mydomain /etc/passwd
-Для гостьових систем Windows передбачено розпізнавання таких шляхів у
-Windows:
+Для гостьових систем Windows передбачено розпізнавання таких шляхів у Windows:
virt-edit -d mywindomain 'c:\autoexec.bat'
-Якщо встановлено Perl, ви також можете редагувати файли у неінтерактивному
-режимі (див. L</НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ> нижче). Щоб змінити типовий
-рівень init на 5:
+Якщо встановлено Perl, ви також можете редагувати файли у неінтерактивному режимі (див. L</НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ> нижче). Щоб змінити типовий рівень init на 5:
virt-edit -d mydomain /etc/inittab -e 's/^id:.*/id:5:initdefault:/'
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a> адреса
=item B<--backup> СУФІКС
-Створити резервну копію початкового файла I<у образі диска гостьової
-системи>. Резервна копія матиме таку саму назву, що і початковий файл, із
-додаванням суфікса C<суфікс>.
+Створити резервну копію початкового файла I<у образі диска гостьової системи>. Резервна копія матиме таку саму назву, що і початковий файл, із додаванням суфікса C<суфікс>.
-Зазвичай, першим символом суфікса C<суфікс> буде крапка, C<.>, отже, можна
-віддати таку команду:
+Зазвичай, першим символом суфікса C<суфікс> буде крапка, C<.>, отже, можна віддати таку команду:
virt-edit -b .orig [тощо]
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не
-буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не буде використовуватися взагалі.
=item B<-d> ГІСТЬ
=item B<--domain> ГІСТЬ
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-edit попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-edit попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<-e> вираз
=item B<--expr> вираз
-Замість запуску зовнішнього редактора, неінтерактивно застосувати вираз Perl
-C<ВИРАЗ> до усіх рядків файла. Див. L</НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ> нижче.
+Замість запуску зовнішнього редактора, неінтерактивно застосувати вираз Perl C<ВИРАЗ> до усіх рядків файла. Див. L</НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ> нижче.
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-edit --format=raw -a диск.img файл
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-cat --format=raw -a диск.img --format -a інший.img файл
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
Якщо точку монтування не вказано, типовим значенням є F</>.
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
-
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися
-програмою L<virt-filesystems(1)>.
-
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або C<ro> (другий варіант
-використовується, якщо використано прапорець I<--ro>). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
+
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися програмою L<virt-filesystems(1)>.
+
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або C<ro> (другий варіант використовується, якщо використано прапорець I<--ro>). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
-m /dev/sda1:/:acl,user_xattr
-Використання цього прапорця є еквівалентним до використання команди
-C<mount-options>.
+Використання цього прапорця є еквівалентним до використання команди C<mount-options>.
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: C<ext2>
-і C<ext3>), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: C<ext2> і C<ext3>), або libguestfs визначає файлову систему помилково.
=item B<-v>
virt-edit назва_гостьової_системи файл
-тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
=head1 НЕІНТЕРАКТИВНЕ РЕДАГУВАННЯ
-C<virt-edit> зазвичай викликає C<$EDITOR> (або vi), щоб адміністратор
-системи зміг інтерактивно редагувати файл.
+C<virt-edit> зазвичай викликає C<$EDITOR> (або vi), щоб адміністратор системи зміг інтерактивно редагувати файл.
-Передбачено також два способи використання C<virt-edit> зі скриптів з метою
-автоматизації редагування файлів. (Зауважте, що хоча ви I<можете>
-користуватися C<virt-edit> у цей спосіб, стійкішим до помилок буде написання
-скриптів, які безпосередньо використовують програмний інтерфейс libguestfs
-та Augeas для редагування файлів налаштувань.)
+Передбачено також два способи використання C<virt-edit> зі скриптів з метою автоматизації редагування файлів. (Зауважте, що хоча ви I<можете> користуватися C<virt-edit> у цей спосіб, стійкішим до помилок буде написання скриптів, які безпосередньо використовують програмний інтерфейс libguestfs та Augeas для редагування файлів налаштувань.)
-Першим методом є тимчасове встановлення C<$EDITOR> у значення назви скрипту
-або програми, яку ви хочете запустити. Скрипт буде викликано у форматі
-C<$EDITOR tmpfile>, він має оновлювати C<tmpfile> на місці у будь-який
-спосіб.
+Першим методом є тимчасове встановлення C<$EDITOR> у значення назви скрипту або програми, яку ви хочете запустити. Скрипт буде викликано у форматі C<$EDITOR tmpfile>, він має оновлювати C<tmpfile> на місці у будь-який спосіб.
-Другим методом є використання параметра I<-e> програми C<virt-edit> для
-запуску короткого фрагмента коду Perl у стилі L<sed(1)>. Наприклад, щоб
-змінити усі екземпляри C<foo> на C<bar> у файлі, віддайте таку команду:
+Другим методом є використання параметра I<-e> програми C<virt-edit> для запуску короткого фрагмента коду Perl у стилі L<sed(1)>. Наприклад, щоб змінити усі екземпляри C<foo> на C<bar> у файлі, віддайте таку команду:
virt-edit -d назва_домену назва_файла -e 's/foo/bar/'
-Можна скористатися усією потужністю формальних виразів Perl
-(див. L<perlre(1)>). Наприклад, для вилучення пароля root ви можете віддати
-таку команду:
+Можна скористатися усією потужністю формальних виразів Perl (див. L<perlre(1)>). Наприклад, для вилучення пароля root ви можете віддати таку команду:
virt-edit -d назва_домену /etc/passwd -e 's/^root:.*?:/root::/'
-Під час обробки команди вираз Perl застосовується до кожного з рядків
-файла. Рядок, разом із кінцевим C<\n>, передається у C<$_>, а вираз має
-оновити C<$_> або лишити його вміст без змін.
+Під час обробки команди вираз Perl застосовується до кожного з рядків файла. Рядок, разом із кінцевим C<\n>, передається у C<$_>, а вираз має оновити C<$_> або лишити його вміст без змін.
-Щоб вилучити рядок, встановіть для C<$_> значення порожнього
-рядка. Наприклад, щоб вилучити обліковий запис C<apache> з файла паролів, ви
-можете віддати таку команду:
+Щоб вилучити рядок, встановіть для C<$_> значення порожнього рядка. Наприклад, щоб вилучити обліковий запис C<apache> з файла паролів, ви можете віддати таку команду:
virt-edit -d mydomain /etc/passwd -e '$_ = "" if /^apache:/'
-Щоб вставити рядок, допишіть його на початку або наприкінці C<$_>. Втім,
-дописування рядків наприкінці файла у цей спосіб є доволі складною справою —
-оскільки не існує загального поняття «останній рядок файла», ваш вираз
-просто не буде викликано ще раз. Якщо ви хочете дописати рядок наприкінці
-файла, вам варто скористатися першим методом (встановленням значення для
-C<$EDITOR>).
+Щоб вставити рядок, допишіть його на початку або наприкінці C<$_>. Втім, дописування рядків наприкінці файла у цей спосіб є доволі складною справою — оскільки не існує загального поняття «останній рядок файла», ваш вираз просто не буде викликано ще раз. Якщо ви хочете дописати рядок наприкінці файла, вам варто скористатися першим методом (встановленням значення для C<$EDITOR>).
-Змінна C<$lineno> містить значення номера поточного рядка. За традицією,
-перший рядок файла має номер C<1>.
+Змінна C<$lineno> містить значення номера поточного рядка. За традицією, перший рядок файла має номер C<1>.
-Значення, повернуте у результаті обробки виразу, ігнорується, але вираз може
-викликати C<die> з метою переривання усієї програми без внесення змін до
-початкового файла.
+Значення, повернуте у результаті обробки виразу, ігнорується, але вираз може викликати C<die> з метою переривання усієї програми без внесення змін до початкового файла.
-Слід пам'ятати, що відповідник кінця рядка при використанні C<$_> може
-містити кінцеве C<\n> або (у файлах DOS) C<\r\n>, або, якщо файл не
-закінчується символом нового рядка, жодну з цих послідовностей. Тому для
-пошуку або заміни певного тексту наприкінці рядка слід використовувати такий
-формальний вираз:
+Слід пам'ятати, що відповідник кінця рядка при використанні C<$_> може містити кінцеве C<\n> або (у файлах DOS) C<\r\n>, або, якщо файл не закінчується символом нового рядка, жодну з цих послідовностей. Тому для пошуку або заміни певного тексту наприкінці рядка слід використовувати такий формальний вираз:
/якийсь текст(\r?\n)?$/
-Альтернативним варіантом є використання функції C<chomp> Perl, але так, щоб
-не обрізати саме C<$_> (оскільки ця функція вилучає усі символи нового рядка
-з файла):
+Альтернативним варіантом є використання функції C<chomp> Perl, але так, щоб не обрізати саме C<$_> (оскільки ця функція вилучає усі символи нового рядка з файла):
my $m = $_; chomp $m; $m =~ /якийсь текст$/
=head1 ШЛЯХИ У WINDOWS
-У C<virt-edit> передбачено обмежені можливості щодо обробки літерних дисків
-та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
+У C<virt-edit> передбачено обмежені можливості щодо обробки літерних дисків та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
Тоді і лише тоді, коли у гостьовій системі працює Windows:
=item *
-Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових
-систем на основі даних з регістру Windows.
+Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових систем на основі даних з регістру Windows.
=item *
-Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами
-звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
+Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
=item *
-Шлях до файла, вміст якого має бути редаговано, визначається без врахування
-регістру символів у його записі.
+Шлях до файла, вміст якого має бути редаговано, визначається без врахування регістру символів у його записі.
=back
=item *
-Перехід за деякими символічними посиланнями NTFS може здійснюватися з
-помилками.
+Перехід за деякими символічними посиланнями NTFS може здійснюватися з помилками.
=item *
-Точки з'єднання NTFS, які виходять за межі однією файлової системи
-використовувати не можна.
+Точки з'єднання NTFS, які виходять за межі однією файлової системи використовувати не можна.
=back
=head1 ВИКОРИСТАННЯ GUESTFISH
-L<guestfish(1)> є потужнішим інструментом нижчого рівня, яким можна
-скористатися, якщо C<virt-edit> не працює.
+L<guestfish(1)> є потужнішим інструментом нижчого рівня, яким можна скористатися, якщо C<virt-edit> не працює.
Використання C<virt-edit> є приблизним еквівалентом такого:
guestfish --rw -i -d назва_домену edit /файл
-де C<назва_домену> — назва гостьової системи libvirt, а F<файл> — шлях до
-файла повністю.
+де C<назва_домену> — назва гостьової системи libvirt, а F<файл> — шлях до файла повністю.
-У вказаній вище команді використано можливість інспектування гостьових
-систем засобами libguestfs, отже, вона не працюватиме у гостьових системах,
-які libguestfs не може інспектувати, або у довільних образах дисків, які не
-містять гостьових систем. Щоб редагувати дані файла безпосередньо на образі
-диска, скористайтеся такою командою:
+У вказаній вище команді використано можливість інспектування гостьових систем засобами libguestfs, отже, вона не працюватиме у гостьових системах, які libguestfs не може інспектувати, або у довільних образах дисків, які не містять гостьових систем. Щоб редагувати дані файла безпосередньо на образі диска, скористайтеся такою командою:
guestfish --rw -a диск.img -m /dev/sda1 edit /файл
-де F<диск.img> — образ диска, F</dev/sda1> — файлова система у образі диска
-для редагування, а F<файл> — шлях до файла повністю.
+де F<диск.img> — образ диска, F</dev/sda1> — файлова система у образі диска для редагування, а F<файл> — шлях до файла повністю.
-Програма C<virt-edit> не здатна створювати файли. Для створення слід
-користуватися командами guestfish C<touch>, C<write> та C<upload>:
+Програма C<virt-edit> не здатна створювати файли. Для створення слід користуватися командами guestfish C<touch>, C<write> та C<upload>:
guestfish --rw -i -d назва_домену touch /новий_файл
=item C<EDITOR>
-Якщо встановлено, цей рядок використовуватиметься для виклику
-редактора. Рядок може містити аргументи, наприклад, C<"emacs -nw">
+Якщо встановлено, цей рядок використовуватиметься для виклику редактора. Рядок може містити аргументи, наприклад, C<"emacs -nw">
Якщо не встановлено, використовуватиметься C<vi>.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-in(1)>,
-L<virt-tar-in(1)>, L<http://libguestfs.org/>, L<perl(1)>, L<perlre(1)>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-in(1)>, L<virt-tar-in(1)>, L<http://libguestfs.org/>, L<perl(1)>, L<perlre(1)>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-filesystems 1"
-.TH virt-filesystems 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-filesystems 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "НАЗВА"
.IX Header "НАЗВА"
-virt-filesystems — програма для показу списку файлових систем, розділів,
-блокових пристроїв, \s-1LVM\s0 у віртуальних машинах або образах дисків
+virt-filesystems — програма для показу списку файлових систем, розділів, блокових пристроїв, \s-1LVM\s0 у віртуальних машинах або образах дисків
.SH "КОРОТКИЙ ОПИС"
.IX Header "КОРОТКИЙ ОПИС"
.Vb 1
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-За допомогою цієї програми ви зможете виявляти файлові системи, розділи
-диска, логічні томи та визначати їхні розміри у образі диска або у
-віртуальній машині. Програма є замінником \fBvirt\-list\-filesystems\fR\|(1) та
-\&\fBvirt\-list\-partitions\fR\|(1).
+За допомогою цієї програми ви зможете виявляти файлові системи, розділи диска, логічні томи та визначати їхні розміри у образі диска або у віртуальній машині. Програма є замінником \fBvirt\-list\-filesystems\fR\|(1) та \fBvirt\-list\-partitions\fR\|(1).
.PP
-Одним із варіантів використання цієї програми є додавання її у скрипти для
-ітеративного обходу усіх файлових систем на образі диска:
+Одним із варіантів використання цієї програми є додавання її у скрипти для ітеративного обходу усіх файлових систем на образі диска:
.PP
.Vb 3
\& for fs in $(virt\-filesystems \-a disk.img); do
\& done
.Ve
.PP
-Це одним використанням програми є виведення списку розділів до використання
-іншого інструмента для внесення змін до цих розділів (зокрема програми
-\&\fBvirt\-resize\fR\|(1)). Якщо вам цікавий вміст невідомого образу диска,
-скористайтеся цим інструментом разом із \fBvirt\-inspector\fR\|(1).
+Це одним використанням програми є виведення списку розділів до використання іншого інструмента для внесення змін до цих розділів (зокрема програми \fBvirt\-resize\fR\|(1)). Якщо вам цікавий вміст невідомого образу диска, скористайтеся цим інструментом разом із \fBvirt\-inspector\fR\|(1).
.PP
-Керувати виведенням даних цією програмою можна за допомогою різноманітних
-параметрів командного рядка. Вам слід задати параметр \fI\-a\fR або \fI\-d\fR, щоб
-визначити образ диска або гостьову систему libvirt. Якщо ви вкажете один з
-цих параметрів, програма покаже знайдені файлові системи, по одній на рядок,
-ось так:
+Керувати виведенням даних цією програмою можна за допомогою різноманітних параметрів командного рядка. Вам слід задати параметр \fI\-a\fR або \fI\-d\fR, щоб визначити образ диска або гостьову систему libvirt. Якщо ви вкажете один з цих параметрів, програма покаже знайдені файлові системи, по одній на рядок, ось так:
.PP
.Vb 3
\& $ virt\-filesystems \-a disk.img
\& /dev/vg_guest/lv_root
.Ve
.PP
-Якщо ви додасте \fI\-l\fR або \fI\-\-long\fR, у виведених даних буде показано
-додаткову інформацію:
+Якщо ви додасте \fI\-l\fR або \fI\-\-long\fR, у виведених даних буде показано додаткову інформацію:
.PP
.Vb 4
\& $ virt\-filesystems \-a disk.img \-l
\& /dev/vg_guest/lv_root filesystem ext4 root 10212081664
.Ve
.PP
-Якщо ви додасте параметр \fI\-\-extra\fR, буде показано і файлові системи, які
-непридатні до монтування (резервна пам'ять, невідомий формат):
+Якщо ви додасте параметр \fI\-\-extra\fR, буде показано і файлові системи, які непридатні до монтування (резервна пам'ять, невідомий формат):
.PP
.Vb 5
\& $ virt\-filesystems \-a disk.img \-\-extra
\& /dev/vg_guest/lv_data
.Ve
.PP
-Якщо ви додасте параметр \fI\-\-partitions\fR, буде показано розділи, а не
-файлові системи:
+Якщо ви додасте параметр \fI\-\-partitions\fR, буде показано розділи, а не файлові системи:
.PP
.Vb 3
\& $ virt\-filesystems \-a disk.img \-\-partitions
\& /dev/sda2
.Ve
.PP
-У подібний спосіб, ви можете скористатися параметрами \fI\-\-logical\-volumes\fR,
-\&\fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR, \fI\-\-block\-devices\fR, щоб отримати
-список цих записів.
+У подібний спосіб, ви можете скористатися параметрами \fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR, \fI\-\-block\-devices\fR, щоб отримати список цих записів.
.PP
-Ви можете також скористатися цими параметрами у поєднанні (якщо вам потрібна
-комбінація із файловими системами, вам слід додати
-\&\fI\-\-filesystems\fR). Зауважте, що деякі з пунктів списку можуть належати
-одночасно декільком категоріям (наприклад, \fI/dev/sda1\fR може бути як
-розділом, так і файловою системою). Такі пункти буде показано відповідну
-кількість разів. Щоб отримати список, який міститиме абсолютно усе, про що
-знає virt-filesystems, скористайтеся параметром \fI\-\-all\fR.
+Ви можете також скористатися цими параметрами у поєднанні (якщо вам потрібна комбінація із файловими системами, вам слід додати \fI\-\-filesystems\fR). Зауважте, що деякі з пунктів списку можуть належати одночасно декільком категоріям (наприклад, \fI/dev/sda1\fR може бути як розділом, так і файловою системою). Такі пункти буде показано відповідну кількість разів. Щоб отримати список, який міститиме абсолютно усе, про що знає virt-filesystems, скористайтеся параметром \fI\-\-all\fR.
.PP
-\&\s-1UUID\s0 (оскільки вони є доволі довгими) типово показано не буде. Додайте
-параметр \fI\-\-uuid\fR, щоб ознайомитися із \s-1UUID\s0 пристроїв і файлових систем у
-розширених даних.
+\&\s-1UUID\s0 (оскільки вони є доволі довгими) типово показано не буде. Додайте параметр \fI\-\-uuid\fR, щоб ознайомитися із \s-1UUID\s0 пристроїв і файлових систем у розширених даних.
.PP
-\&\fI\-\-all \-\-long \-\-uuid\fR є корисною комбінацією для показу усіх доступних
-даних щодо усього.
+\&\fI\-\-all \-\-long \-\-uuid\fR є корисною комбінацією для показу усіх доступних даних щодо усього.
.PP
.Vb 7
\& $ virt\-filesystems \-a win.img \-\-all \-\-long \-\-uuid \-h
\& /dev/sda device \- \- 20G \- \-
.Ve
.PP
-Для отримання зручних для машинної обробки даних скористайтеся параметром
-\&\fI\-\-csv\fR. Дані буде виведено у форматі значень відокремлених комами.
+Для отримання зручних для машинної обробки даних скористайтеся параметром \fI\-\-csv\fR. Дані буде виведено у форматі значень відокремлених комами.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a адреса\fR" 4
.IX Item "-a адреса"
.PD 0
Додати віддалений диск. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
.IP "\fB\-\-all\fR" 4
.IX Item "--all"
-Вивести усе. У поточній версії це те саме, що вказати такі параметри:
-\&\fI\-\-filesystems\fR, \fI\-\-extra\fR, \fI\-\-partitions\fR, \fI\-\-block\-devices\fR,
-\&\fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR. (У
-майбутньому до цього списку може бути додано інші пункти).
+Вивести усе. У поточній версії це те саме, що вказати такі параметри: \fI\-\-filesystems\fR, \fI\-\-extra\fR, \fI\-\-partitions\fR, \fI\-\-block\-devices\fR, \fI\-\-logical\-volumes\fR, \fI\-\-volume\-groups\fR, \fI\-\-physical\-volumes\fR. (У майбутньому до цього списку може бути додано інші пункти).
.Sp
Див. також \fI\-\-long\fR.
.IP "\fB\-\-blkdevs\fR" 4
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0,
-наведеним нижче.
+Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0, наведеним нижче.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-filesystems попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-filesystems попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-extra\fR" 4
.IX Item "--extra"
-Це спричинить показ файлових систем, які не є звичайними файловими
-системами, які придатні до монтування. До цієї категорії включено розділи
-резервної пам'яті та файлові системи, які є порожніми або містять невідомі
-дані.
+Це спричинить показ файлових систем, які не є звичайними файловими системами, які придатні до монтування. До цієї категорії включено розділи резервної пам'яті та файлові системи, які є порожніми або містять невідомі дані.
.Sp
Цей параметр автоматично встановлює параметр \fI\-\-filesystems\fR.
.IP "\fB\-\-filesystems\fR" 4
.IX Item "--filesystems"
-Показати список придатних до монтування систем. Якщо параметр показу не було
-визначено, цей параметр буде додано до команди.
+Показати список придатних до монтування систем. Якщо параметр показу не було визначено, цей параметр буде додано до команди.
.Sp
-Якщо було використано параметр \fI\-\-extra\fR, буде показано і непридатні до
-монтування файлові системи.
+Якщо було використано параметр \fI\-\-extra\fR, буде показано і непридатні до монтування файлові системи.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-filesystems \-\-format=raw \-a диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-filesystems \-\-format=raw \-a диск.img \-\-format \-a інший_диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
.Sp
Якщо ви не додасте параметр \fI\-\-no\-title\fR, буде додано рядок заголовка.
.Sp
-Вміст додаткових стовпчиків залежить від вибраного виведення, а
-упорядкування стовпчиків може змінитися у майбутніх версіях. Для того, щоб
-виведені дані відповідали вхідним даним зовнішніх програм, скористайтеся
-рядком заголовків, виведенням \fI\-\-csv\fR і/або \fBcsvtool\fR\|(1).
+Вміст додаткових стовпчиків залежить від вибраного виведення, а упорядкування стовпчиків може змінитися у майбутніх версіях. Для того, щоб виведені дані відповідали вхідним даним зовнішніх програм, скористайтеся рядком заголовків, виведенням \fI\-\-csv\fR і/або \fBcsvtool\fR\|(1).
.Sp
-Якщо дані має бути виведено у зручному для читання людиною форматі,
-скористайтеся параметром \fI\-h\fR. Типово, буде показано розміри у \fIбайтах\fR.
+Якщо дані має бути виведено у зручному для читання людиною форматі, скористайтеся параметром \fI\-h\fR. Типово, буде показано розміри у \fIбайтах\fR.
.Sp
Скористайтеся параметром \fI\-\-uuid\fR, щоб було показано також \s-1UUID.\s0
.IP "\fB\-\-lvs\fR" 4
.IP "\fB\-\-logical\-volumes\fR" 4
.IX Item "--logical-volumes"
.PD
-Показати логічні томи \s-1LVM.\s0 У цьому режимі томи буде показано незалежно від
-того, чи містяться на логічних томах файлові системи.
+Показати логічні томи \s-1LVM.\s0 У цьому режимі томи буде показано незалежно від того, чи містяться на логічних томах файлові системи.
.IP "\fB\-\-no\-title\fR" 4
.IX Item "--no-title"
У режимі \fI\-\-long\fR не додавати рядок заголовків.
.Sp
-Зауважте, що порядок стовпчиків не є фіксованим і може змінитися у майбутніх
-версіях virt-filesystems; отже, використання цього параметра може призвести
-до не зовсім очікуваних наслідків.
+Зауважте, що порядок стовпчиків не є фіксованим і може змінитися у майбутніх версіях virt-filesystems; отже, використання цього параметра може призвести до не зовсім очікуваних наслідків.
.IP "\fB\-\-parts\fR" 4
.IX Item "--parts"
.PD 0
.IP "\fB\-\-partitions\fR" 4
.IX Item "--partitions"
.PD
-Показати розділи. У цьому режимі розділи буде показано незалежно від того,
-чи містяться на розділах файлові системи.
+Показати розділи. У цьому режимі розділи буде показано незалежно від того, чи містяться на розділах файлові системи.
.IP "\fB\-\-pvs\fR" 4
.IX Item "--pvs"
.PD 0
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "СТОВПЧИКИ"
.IX Header "СТОВПЧИКИ"
-Зауважте, що порядок і перелік стовпчиків у виведених даних у майбутніх
-версіях може бути змінено.
+Зауважте, що порядок і перелік стовпчиків у виведених даних у майбутніх версіях може бути змінено.
.IP "\fBНазва\fR" 4
.IX Item "Назва"
Назва файлової системи, розділу, блокового пристрою або \s-1LVM.\s0
.Sp
-Назви пристроїв та розділів буде показано у форматі канонічних назв
-libguestfs. Таким чином, наприклад, \fI/dev/sda2\fR означатиме другий розділ на
-першому пристрої.
+Назви пристроїв та розділів буде показано у форматі канонічних назв libguestfs. Таким чином, наприклад, \fI/dev/sda2\fR означатиме другий розділ на першому пристрої.
.Sp
-Якщо параметр \fI\-\-long\fR \fBне\fR вказано, у виведених даних буде лише стовпчик
-назв.
+Якщо параметр \fI\-\-long\fR \fBне\fR вказано, у виведених даних буде лише стовпчик назв.
.IP "\fBТип\fR" 4
.IX Item "Тип"
Тип об'єкта. Наприклад, \f(CW\*(C`filesystem\*(C'\fR, \f(CW\*(C`lv\*(C'\fR, \f(CW\*(C`device\*(C'\fR тощо.
.IP "\fB\s-1VFS\s0\fR" 4
.IX Item "VFS"
-Якщо буде виявлено відому програмі файлову систему, у цьому стовпчику буде
-показано дані щодо неї, наприклад \f(CW\*(C`ext4\*(C'\fR.
+Якщо буде виявлено відому програмі файлову систему, у цьому стовпчику буде показано дані щодо неї, наприклад \f(CW\*(C`ext4\*(C'\fR.
.IP "\fBМітка\fR" 4
.IX Item "Мітка"
-Якщо у об'єкта є мітка (яка використовується для ідентифікації та монтування
-файлових систем), у цьому стовпчику міститься мітка.
+Якщо у об'єкта є мітка (яка використовується для ідентифікації та монтування файлових систем), у цьому стовпчику міститься мітка.
.IP "\fB\s-1MBR\s0\fR" 4
.IX Item "MBR"
-Байт типу розділу, буде показано у форматі двоцифрового шістнадцяткового
-числа. Довідковий список типів розділів наведено тут:
-http://www.win.tue.nl/~aeb/partitions/partition_types\-1.html
+Байт типу розділу, буде показано у форматі двоцифрового шістнадцяткового числа. Довідковий список типів розділів наведено тут: http://www.win.tue.nl/~aeb/partitions/partition_types\-1.html
.Sp
Це стосується лише розділів \s-1DOS\s0 (\s-1MBR\s0).
.IP "\fBРозмір\fR" 4
.IX Item "Розмір"
-Розмір об'єкта у байтах. Якщо використано параметр \fI\-\-human\fR, розмір буде
-вказано у зручному для читання форматі.
+Розмір об'єкта у байтах. Якщо використано параметр \fI\-\-human\fR, розмір буде вказано у зручному для читання форматі.
.IP "\fBОснова\fR" 4
.IX Item "Основа"
-У стовпчику батьківських об'єктів показано відношення батьківських і
-дочірніх об'єктів.
+У стовпчику батьківських об'єктів показано відношення батьківських і дочірніх об'єктів.
.Sp
-Наприклад, якщо об'єкт є розділом, у цьому стовпчику міститиметься назва
-пристрою, на якому цей розділ розташовано. Якщо об'єкт є логічним томом, у
-цьому стовпчику буде наведено назву групи томів.
+Наприклад, якщо об'єкт є розділом, у цьому стовпчику міститиметься назва пристрою, на якому цей розділ розташовано. Якщо об'єкт є логічним томом, у цьому стовпчику буде наведено назву групи томів.
.Sp
-Якщо батьківських об'єктів декілька, вмістом стовпчика буде список значень
-відокремлених комами, наприклад \f(CW\*(C`/dev/sda,/dev/sdb\*(C'\fR.
+Якщо батьківських об'єктів декілька, вмістом стовпчика буде список значень відокремлених комами, наприклад \f(CW\*(C`/dev/sda,/dev/sdb\*(C'\fR.
.IP "\fB\s-1UUID\s0\fR" 4
.IX Item "UUID"
-Якщо у об'єкта є \s-1UUID\s0 (який використовується для ідентифікації та монтування
-файлових систем та блокових пристроїв), у цьому стовпчику міститься \s-1UUID\s0 у
-форматі рядка.
+Якщо у об'єкта є \s-1UUID\s0 (який використовується для ідентифікації та монтування файлових систем та блокових пристроїв), у цьому стовпчику міститься \s-1UUID\s0 у форматі рядка.
.Sp
\&\s-1UUID\s0 буде показано, лише якщо вказано параметр \fI\-\-uuid\fR.
.SH "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
.IX Header "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
-Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може
-\&\fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може \fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
.PP
-Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR працює у надійний спосіб. Ось приклад із двома стовпчиками:
.PP
.Vb 1
\& "foo,bar",baz
.Ve
.PP
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось приклад із одним рядком:
.PP
.Vb 2
\& "foo
\& bar",baz
.Ve
.PP
-Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR
-(https://github.com/Chris00/ocaml\-csv також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv також є серед пакунків основних дистрибутивів Linux).
.PP
-Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0
-(наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0 (наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
.PP
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних \s-1CSV.\s0
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних \s-1CSV.\s0
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-df\fR\|(1),
-\&\fBvirt\-list\-filesystems\fR\|(1), \fBvirt\-list\-partitions\fR\|(1), \fBcsvtool\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-df\fR\|(1), \fBvirt\-list\-filesystems\fR\|(1), \fBvirt\-list\-partitions\fR\|(1), \fBcsvtool\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 НАЗВА
-virt-filesystems — програма для показу списку файлових систем, розділів,
-блокових пристроїв, LVM у віртуальних машинах або образах дисків
+virt-filesystems — програма для показу списку файлових систем, розділів, блокових пристроїв, LVM у віртуальних машинах або образах дисків
=head1 КОРОТКИЙ ОПИС
=head1 ОПИС
-За допомогою цієї програми ви зможете виявляти файлові системи, розділи
-диска, логічні томи та визначати їхні розміри у образі диска або у
-віртуальній машині. Програма є замінником L<virt-list-filesystems(1)> та
-L<virt-list-partitions(1)>.
+За допомогою цієї програми ви зможете виявляти файлові системи, розділи диска, логічні томи та визначати їхні розміри у образі диска або у віртуальній машині. Програма є замінником L<virt-list-filesystems(1)> та L<virt-list-partitions(1)>.
-Одним із варіантів використання цієї програми є додавання її у скрипти для
-ітеративного обходу усіх файлових систем на образі диска:
+Одним із варіантів використання цієї програми є додавання її у скрипти для ітеративного обходу усіх файлових систем на образі диска:
for fs in $(virt-filesystems -a disk.img); do
# ...
done
-Це одним використанням програми є виведення списку розділів до використання
-іншого інструмента для внесення змін до цих розділів (зокрема програми
-L<virt-resize(1)>). Якщо вам цікавий вміст невідомого образу диска,
-скористайтеся цим інструментом разом із L<virt-inspector(1)>.
+Це одним використанням програми є виведення списку розділів до використання іншого інструмента для внесення змін до цих розділів (зокрема програми L<virt-resize(1)>). Якщо вам цікавий вміст невідомого образу диска, скористайтеся цим інструментом разом із L<virt-inspector(1)>.
-Керувати виведенням даних цією програмою можна за допомогою різноманітних
-параметрів командного рядка. Вам слід задати параметр I<-a> або I<-d>, щоб
-визначити образ диска або гостьову систему libvirt. Якщо ви вкажете один з
-цих параметрів, програма покаже знайдені файлові системи, по одній на рядок,
-ось так:
+Керувати виведенням даних цією програмою можна за допомогою різноманітних параметрів командного рядка. Вам слід задати параметр I<-a> або I<-d>, щоб визначити образ диска або гостьову систему libvirt. Якщо ви вкажете один з цих параметрів, програма покаже знайдені файлові системи, по одній на рядок, ось так:
$ virt-filesystems -a disk.img
/dev/sda1
/dev/vg_guest/lv_root
-Якщо ви додасте I<-l> або I<--long>, у виведених даних буде показано
-додаткову інформацію:
+Якщо ви додасте I<-l> або I<--long>, у виведених даних буде показано додаткову інформацію:
$ virt-filesystems -a disk.img -l
Назва Тип ВФС Мітка Розмір
/dev/sda1 filesystem ext4 boot 524288000
/dev/vg_guest/lv_root filesystem ext4 root 10212081664
-Якщо ви додасте параметр I<--extra>, буде показано і файлові системи, які
-непридатні до монтування (резервна пам'ять, невідомий формат):
+Якщо ви додасте параметр I<--extra>, буде показано і файлові системи, які непридатні до монтування (резервна пам'ять, невідомий формат):
$ virt-filesystems -a disk.img --extra
/dev/sda1
/dev/vg_guest/lv_swap
/dev/vg_guest/lv_data
-Якщо ви додасте параметр I<--partitions>, буде показано розділи, а не
-файлові системи:
+Якщо ви додасте параметр I<--partitions>, буде показано розділи, а не файлові системи:
$ virt-filesystems -a disk.img --partitions
/dev/sda1
/dev/sda2
-У подібний спосіб, ви можете скористатися параметрами I<--logical-volumes>,
-I<--volume-groups>, I<--physical-volumes>, I<--block-devices>, щоб отримати
-список цих записів.
+У подібний спосіб, ви можете скористатися параметрами I<--logical-volumes>, I<--volume-groups>, I<--physical-volumes>, I<--block-devices>, щоб отримати список цих записів.
-Ви можете також скористатися цими параметрами у поєднанні (якщо вам потрібна
-комбінація із файловими системами, вам слід додати
-I<--filesystems>). Зауважте, що деякі з пунктів списку можуть належати
-одночасно декільком категоріям (наприклад, F</dev/sda1> може бути як
-розділом, так і файловою системою). Такі пункти буде показано відповідну
-кількість разів. Щоб отримати список, який міститиме абсолютно усе, про що
-знає virt-filesystems, скористайтеся параметром I<--all>.
+Ви можете також скористатися цими параметрами у поєднанні (якщо вам потрібна комбінація із файловими системами, вам слід додати I<--filesystems>). Зауважте, що деякі з пунктів списку можуть належати одночасно декільком категоріям (наприклад, F</dev/sda1> може бути як розділом, так і файловою системою). Такі пункти буде показано відповідну кількість разів. Щоб отримати список, який міститиме абсолютно усе, про що знає virt-filesystems, скористайтеся параметром I<--all>.
-UUID (оскільки вони є доволі довгими) типово показано не буде. Додайте
-параметр I<--uuid>, щоб ознайомитися із UUID пристроїв і файлових систем у
-розширених даних.
+UUID (оскільки вони є доволі довгими) типово показано не буде. Додайте параметр I<--uuid>, щоб ознайомитися із UUID пристроїв і файлових систем у розширених даних.
-I<--all --long --uuid> є корисною комбінацією для показу усіх доступних
-даних щодо усього.
+I<--all --long --uuid> є корисною комбінацією для показу усіх доступних даних щодо усього.
$ virt-filesystems -a win.img --all --long --uuid -h
Назва Тип VFS Мітка Розмір Батьк. UUID
/dev/sda2 partition - - 20G /dev/sda -
/dev/sda device - - 20G - -
-Для отримання зручних для машинної обробки даних скористайтеся параметром
-I<--csv>. Дані буде виведено у форматі значень відокремлених комами.
+Для отримання зручних для машинної обробки даних скористайтеся параметром I<--csv>. Дані буде виведено у форматі значень відокремлених комами.
=head1 ПАРАМЕТРИ
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--all>
-Вивести усе. У поточній версії це те саме, що вказати такі параметри:
-I<--filesystems>, I<--extra>, I<--partitions>, I<--block-devices>,
-I<--logical-volumes>, I<--volume-groups>, I<--physical-volumes>. (У
-майбутньому до цього списку може бути додано інші пункти).
+Вивести усе. У поточній версії це те саме, що вказати такі параметри: I<--filesystems>, I<--extra>, I<--partitions>, I<--block-devices>, I<--logical-volumes>, I<--volume-groups>, I<--physical-volumes>. (У майбутньому до цього списку може бути додано інші пункти).
Див. також I<--long>.
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<--csv>
-Вивести результати до формату CSV (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>,
-наведеним нижче.
+Вивести результати до формату CSV (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>, наведеним нижче.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-filesystems попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-filesystems попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--extra>
-Це спричинить показ файлових систем, які не є звичайними файловими
-системами, які придатні до монтування. До цієї категорії включено розділи
-резервної пам'яті та файлові системи, які є порожніми або містять невідомі
-дані.
+Це спричинить показ файлових систем, які не є звичайними файловими системами, які придатні до монтування. До цієї категорії включено розділи резервної пам'яті та файлові системи, які є порожніми або містять невідомі дані.
Цей параметр автоматично встановлює параметр I<--filesystems>.
=item B<--filesystems>
-Показати список придатних до монтування систем. Якщо параметр показу не було
-визначено, цей параметр буде додано до команди.
+Показати список придатних до монтування систем. Якщо параметр показу не було визначено, цей параметр буде додано до команди.
-Якщо було використано параметр I<--extra>, буде показано і непридатні до
-монтування файлові системи.
+Якщо було використано параметр I<--extra>, буде показано і непридатні до монтування файлові системи.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-filesystems --format=raw -a диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-filesystems --format=raw -a диск.img --format -a інший_диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<-h>
Якщо ви не додасте параметр I<--no-title>, буде додано рядок заголовка.
-Вміст додаткових стовпчиків залежить від вибраного виведення, а
-упорядкування стовпчиків може змінитися у майбутніх версіях. Для того, щоб
-виведені дані відповідали вхідним даним зовнішніх програм, скористайтеся
-рядком заголовків, виведенням I<--csv> і/або L<csvtool(1)>.
+Вміст додаткових стовпчиків залежить від вибраного виведення, а упорядкування стовпчиків може змінитися у майбутніх версіях. Для того, щоб виведені дані відповідали вхідним даним зовнішніх програм, скористайтеся рядком заголовків, виведенням I<--csv> і/або L<csvtool(1)>.
-Якщо дані має бути виведено у зручному для читання людиною форматі,
-скористайтеся параметром I<-h>. Типово, буде показано розміри у I<байтах>.
+Якщо дані має бути виведено у зручному для читання людиною форматі, скористайтеся параметром I<-h>. Типово, буде показано розміри у I<байтах>.
Скористайтеся параметром I<--uuid>, щоб було показано також UUID.
=item B<--logical-volumes>
-Показати логічні томи LVM. У цьому режимі томи буде показано незалежно від
-того, чи містяться на логічних томах файлові системи.
+Показати логічні томи LVM. У цьому режимі томи буде показано незалежно від того, чи містяться на логічних томах файлові системи.
=item B<--no-title>
У режимі I<--long> не додавати рядок заголовків.
-Зауважте, що порядок стовпчиків не є фіксованим і може змінитися у майбутніх
-версіях virt-filesystems; отже, використання цього параметра може призвести
-до не зовсім очікуваних наслідків.
+Зауважте, що порядок стовпчиків не є фіксованим і може змінитися у майбутніх версіях virt-filesystems; отже, використання цього параметра може призвести до не зовсім очікуваних наслідків.
=item B<--parts>
=item B<--partitions>
-Показати розділи. У цьому режимі розділи буде показано незалежно від того,
-чи містяться на розділах файлові системи.
+Показати розділи. У цьому режимі розділи буде показано незалежно від того, чи містяться на розділах файлові системи.
=item B<--pvs>
=head1 СТОВПЧИКИ
-Зауважте, що порядок і перелік стовпчиків у виведених даних у майбутніх
-версіях може бути змінено.
+Зауважте, що порядок і перелік стовпчиків у виведених даних у майбутніх версіях може бути змінено.
=over 4
Назва файлової системи, розділу, блокового пристрою або LVM.
-Назви пристроїв та розділів буде показано у форматі канонічних назв
-libguestfs. Таким чином, наприклад, F</dev/sda2> означатиме другий розділ на
-першому пристрої.
+Назви пристроїв та розділів буде показано у форматі канонічних назв libguestfs. Таким чином, наприклад, F</dev/sda2> означатиме другий розділ на першому пристрої.
-Якщо параметр I<--long> B<не> вказано, у виведених даних буде лише стовпчик
-назв.
+Якщо параметр I<--long> B<не> вказано, у виведених даних буде лише стовпчик назв.
=item B<Тип>
=item B<VFS>
-Якщо буде виявлено відому програмі файлову систему, у цьому стовпчику буде
-показано дані щодо неї, наприклад C<ext4>.
+Якщо буде виявлено відому програмі файлову систему, у цьому стовпчику буде показано дані щодо неї, наприклад C<ext4>.
=item B<Мітка>
-Якщо у об'єкта є мітка (яка використовується для ідентифікації та монтування
-файлових систем), у цьому стовпчику міститься мітка.
+Якщо у об'єкта є мітка (яка використовується для ідентифікації та монтування файлових систем), у цьому стовпчику міститься мітка.
=item B<MBR>
-Байт типу розділу, буде показано у форматі двоцифрового шістнадцяткового
-числа. Довідковий список типів розділів наведено тут:
-L<http://www.win.tue.nl/~aeb/partitions/partition_types-1.html>
+Байт типу розділу, буде показано у форматі двоцифрового шістнадцяткового числа. Довідковий список типів розділів наведено тут: L<http://www.win.tue.nl/~aeb/partitions/partition_types-1.html>
Це стосується лише розділів DOS (MBR).
=item B<Розмір>
-Розмір об'єкта у байтах. Якщо використано параметр I<--human>, розмір буде
-вказано у зручному для читання форматі.
+Розмір об'єкта у байтах. Якщо використано параметр I<--human>, розмір буде вказано у зручному для читання форматі.
=item B<Основа>
-У стовпчику батьківських об'єктів показано відношення батьківських і
-дочірніх об'єктів.
+У стовпчику батьківських об'єктів показано відношення батьківських і дочірніх об'єктів.
-Наприклад, якщо об'єкт є розділом, у цьому стовпчику міститиметься назва
-пристрою, на якому цей розділ розташовано. Якщо об'єкт є логічним томом, у
-цьому стовпчику буде наведено назву групи томів.
+Наприклад, якщо об'єкт є розділом, у цьому стовпчику міститиметься назва пристрою, на якому цей розділ розташовано. Якщо об'єкт є логічним томом, у цьому стовпчику буде наведено назву групи томів.
-Якщо батьківських об'єктів декілька, вмістом стовпчика буде список значень
-відокремлених комами, наприклад C</dev/sda,/dev/sdb>.
+Якщо батьківських об'єктів декілька, вмістом стовпчика буде список значень відокремлених комами, наприклад C</dev/sda,/dev/sdb>.
=item B<UUID>
-Якщо у об'єкта є UUID (який використовується для ідентифікації та монтування
-файлових систем та блокових пристроїв), у цьому стовпчику міститься UUID у
-форматі рядка.
+Якщо у об'єкта є UUID (який використовується для ідентифікації та монтування файлових систем та блокових пристроїв), у цьому стовпчику міститься UUID у форматі рядка.
UUID буде показано, лише якщо вказано параметр I<--uuid>.
=head1 ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV
-Формат значень, які відокремлено комами (CSV), є оманливо простим. Може
-I<здатися>, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (CSV), є оманливо простим. Може I<здатися>, що його просто обробляти, але насправді це зовсім не так.
-Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не>
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не> працює у надійний спосіб. Ось приклад із двома стовпчиками:
"foo,bar",baz
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось приклад із одним рядком:
"foo
bar",baz
-Для скриптів командної оболонки скористайтеся C<csvtool>
-(L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся C<csvtool> (L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних дистрибутивів Linux).
-Для інших мов програмування використовуйте бібліотеку для обробки даних CSV
-(наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних CSV (наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних CSV.
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних CSV.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-df(1)>,
-L<virt-list-filesystems(1)>, L<virt-list-partitions(1)>, L<csvtool(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-df(1)>, L<virt-list-filesystems(1)>, L<virt-list-partitions(1)>, L<csvtool(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-format 1"
-.TH virt-format 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-format 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-format отримує назву наявного файла на диску (або розділу, логічного
-тому основної системи), \fBвитирає з нього усі дані\fR і форматує його як
-порожній диск. Якщо потрібно, програма може створити таблиці розділів,
-порожні файлові системи, логічні томи тощо.
+Virt-format отримує назву наявного файла на диску (або розділу, логічного тому основної системи), \fBвитирає з нього усі дані\fR і форматує його як порожній диск. Якщо потрібно, програма може створити таблиці розділів, порожні файлові системи, логічні томи тощо.
.PP
-Для створення диска, що містить дані, краще скористатися
-\&\fBvirt\-make\-fs\fR\|(1). Якщо ви створюєте порожній диск для використання у
-\&\fBguestfish\fR\|(1), вам слід скористатися для цього параметром \fI\-N\fR guestfish.
+Для створення диска, що містить дані, краще скористатися \fBvirt\-make\-fs\fR\|(1). Якщо ви створюєте порожній диск для використання у \fBguestfish\fR\|(1), вам слід скористатися для цього параметром \fI\-N\fR guestfish.
.PP
Зазвичай, програмою слід користуватися десь так:
.PP
\& virt\-format \-a /dev/VG/LV
.Ve
.PP
-\&\fIdisk.qcow\fR або \fI/dev/VG/LV\fR має вже існувати. \fBУ результаті виконання
-команд усі дані на вказаних дисках буде витерто\fR. Ці команди створять єдиний
-порожній розділ, який займатиме увесь диск, без файлових систем на ньому.
+\&\fIdisk.qcow\fR або \fI/dev/VG/LV\fR має вже існувати. \fBУ результаті виконання команд усі дані на вказаних дисках буде витерто\fR. Ці команди створять єдиний порожній розділ, який займатиме увесь диск, без файлових систем на ньому.
.PP
-Додатковими параметрами команди можна скористатися для керування створенням
-розділів, файлових систем тощо. Найрозповсюдженішим є використання таких
-параметрів:
+Додатковими параметрами команди можна скористатися для керування створенням розділів, файлових систем тощо. Найрозповсюдженішим є використання таких параметрів:
.IP "\fB\-\-filesystem=[ext3|ntfs|vfat|...]\fR" 4
.IX Item "--filesystem=[ext3|ntfs|vfat|...]"
Створити на розділі порожню файлову систему (\f(CW\*(C`ext3\*(C'\fR, \f(CW\*(C`ntfs\*(C'\fR тощо).
.IP "\fB\-\-lvm[=/dev/VG/LV]\fR" 4
.IX Item "--lvm[=/dev/VG/LV]"
-Створити логічний том Linux \s-1LVM2\s0 на диску. Якщо використовується разом із
-\&\fI\-\-filesystem\fR, на логічному томі створюється файлова система.
+Створити логічний том Linux \s-1LVM2\s0 на диску. Якщо використовується разом із \fI\-\-filesystem\fR, на логічному томі створюється файлова система.
.PP
-Щоб дізнатися більше про ці та інші параметри, ознайомтеся із розділом
-\&\*(L"ПАРАМЕТРИ\*(R" нижче.
+Щоб дізнатися більше про ці та інші параметри, ознайомтеся із розділом \*(L"ПАРАМЕТРИ\*(R" нижче.
.PP
-Зазвичай, формат диска визначається автоматично, але ви також можете вказати
-його за допомогою параметра \fI\-\-format\fR. У випадках, коли ви вважаєте
-ненадійним наявний вміст диска, радимо скористатися цим параметром для
-знищення можливого коду зловмисників.
+Зазвичай, формат диска визначається автоматично, але ви також можете вказати його за допомогою параметра \fI\-\-format\fR. У випадках, коли ви вважаєте ненадійним наявний вміст диска, радимо скористатися цим параметром для знищення можливого коду зловмисників.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска, розділом основної системи,
-логічним томом, зовнішнім диском \s-1USB\s0 тощо.
+Додати \fIфайл\fR, який має бути образом диска, розділом основної системи, логічним томом, зовнішнім диском \s-1USB\s0 тощо.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.Sp
\&\fBВсі поточні дані на диску буде витерто.\fR
.IP "\fB\-a\fR адреса" 4
\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-filesystem=ext3|ntfs|vfat|...\fR" 4
.IX Item "--filesystem=ext3|ntfs|vfat|..."
-Створити порожню файлову систему вказаного типу. У libguestfs передбачено
-підтримку багатьох файлових систем.
+Створити порожню файлову систему вказаного типу. У libguestfs передбачено підтримку багатьох файлових систем.
.IP "\fB\-\-filesystem=none\fR" 4
.IX Item "--filesystem=none"
Не створювати файлової системи. Типова поведінка.
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-format \-\-format=raw \-a диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-format \-\-format=raw \-a диск.img \-\-format \-a ще_один_диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-label=\fRМІТКА" 4
.IX Item "--label=МІТКА"
Встановити мітку файлової системи.
.IP "\fB\-\-lvm=/dev/\f(BI\s-1VG\s0\fB/\f(BI\s-1LV\s0\fB\fR" 4
.IX Item "--lvm=/dev/VG/LV"
-Створити логічний том \s-1LVM2\s0 Linux із назвою \fI/dev/\fI\s-1VG\s0\fI/\fI\s-1LV\s0\fI\fR. Ви можете
-змінити назву групи томів і логічного тому.
+Створити логічний том \s-1LVM2\s0 Linux із назвою \fI/dev/\fI\s-1VG\s0\fI/\fI\s-1LV\s0\fI\fR. Ви можете змінити назву групи томів і логічного тому.
.IP "\fB\-\-lvm\fR" 4
.IX Item "--lvm"
Створити логічний том Linux \s-1LVM2\s0 на із типовою назвою (\fI/dev/VG/LV\fR).
Не створювати логічного тому. Типове поведінка.
.IP "\fB\-\-partition\fR" 4
.IX Item "--partition"
-Створити розділ \s-1MBR\s0 або \s-1GPT\s0 для усього диска. \s-1MBR\s0 буде вибрано, якщо розмір
-диска < 2 ТБ, \s-1GPT\s0 — якщо ≥ 2 ТБ.
+Створити розділ \s-1MBR\s0 або \s-1GPT\s0 для усього диска. \s-1MBR\s0 буде вибрано, якщо розмір диска < 2 ТБ, \s-1GPT\s0 — якщо ≥ 2 ТБ.
.Sp
Типове значення.
.IP "\fB\-\-partition=gpt\fR" 4
Створити розділ \s-1MBR.\s0
.IP "\fB\-\-partition=none\fR" 4
.IX Item "--partition=none"
-Не створювати таблиці розділів. Зауважте, що такі диски можуть бути
-невидимими для Windows.
+Не створювати таблиці розділів. Зауважте, що такі диски можуть бути невидимими для Windows.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
Показати дані щодо версії і завершити роботу.
.IP "\fB\-\-wipe\fR" 4
.IX Item "--wipe"
-У поточній версії virt-format не витирає дані з диска (оскільки ця дія є
-надто тривалою). Тому, якщо на диску є дані, їх буде лише приховано і
-частково перезаписано virt-format. Ймовірно, такі дані можна відновити за
-допомогою інструментів для редагування дисків.
+У поточній версії virt-format не витирає дані з диска (оскільки ця дія є надто тривалою). Тому, якщо на диску є дані, їх буде лише приховано і частково перезаписано virt-format. Ймовірно, такі дані можна відновити за допомогою інструментів для редагування дисків.
.Sp
-Якщо ви скористаєтеся цим параметром, virt-format перезапише нулями увесь
-диск, щоб попередньо записані дані не можна було відновити.
+Якщо ви скористаєтеся цим параметром, virt-format перезапише нулями увесь диск, щоб попередньо записані дані не можна було відновити.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає \f(CW0\fR, якщо роботу виконано успішно, і \f(CW1\fR, якщо
-сталися помилки.
+Ця програма повертає \f(CW0\fR, якщо роботу виконано успішно, і \f(CW1\fR, якщо сталися помилки.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-make\-fs\fR\|(1),
-\&\fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-make\-fs\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Virt-format отримує назву наявного файла на диску (або розділу, логічного
-тому основної системи), B<витирає з нього усі дані> і форматує його як
-порожній диск. Якщо потрібно, програма може створити таблиці розділів,
-порожні файлові системи, логічні томи тощо.
+Virt-format отримує назву наявного файла на диску (або розділу, логічного тому основної системи), B<витирає з нього усі дані> і форматує його як порожній диск. Якщо потрібно, програма може створити таблиці розділів, порожні файлові системи, логічні томи тощо.
-Для створення диска, що містить дані, краще скористатися
-L<virt-make-fs(1)>. Якщо ви створюєте порожній диск для використання у
-L<guestfish(1)>, вам слід скористатися для цього параметром I<-N> guestfish.
+Для створення диска, що містить дані, краще скористатися L<virt-make-fs(1)>. Якщо ви створюєте порожній диск для використання у L<guestfish(1)>, вам слід скористатися для цього параметром I<-N> guestfish.
Зазвичай, програмою слід користуватися десь так:
virt-format -a /dev/VG/LV
-F<disk.qcow> або F</dev/VG/LV> має вже існувати. B<У результаті виконання
-команд усі дані на вказаних дисках буде витерто>. Ці команди створять єдиний
-порожній розділ, який займатиме увесь диск, без файлових систем на ньому.
+F<disk.qcow> або F</dev/VG/LV> має вже існувати. B<У результаті виконання команд усі дані на вказаних дисках буде витерто>. Ці команди створять єдиний порожній розділ, який займатиме увесь диск, без файлових систем на ньому.
-Додатковими параметрами команди можна скористатися для керування створенням
-розділів, файлових систем тощо. Найрозповсюдженішим є використання таких
-параметрів:
+Додатковими параметрами команди можна скористатися для керування створенням розділів, файлових систем тощо. Найрозповсюдженішим є використання таких параметрів:
=over 4
=item B<--lvm[=/dev/VG/LV]>
-Створити логічний том Linux LVM2 на диску. Якщо використовується разом із
-I<--filesystem>, на логічному томі створюється файлова система.
+Створити логічний том Linux LVM2 на диску. Якщо використовується разом із I<--filesystem>, на логічному томі створюється файлова система.
=back
-Щоб дізнатися більше про ці та інші параметри, ознайомтеся із розділом
-L</ПАРАМЕТРИ> нижче.
+Щоб дізнатися більше про ці та інші параметри, ознайомтеся із розділом L</ПАРАМЕТРИ> нижче.
-Зазвичай, формат диска визначається автоматично, але ви також можете вказати
-його за допомогою параметра I<--format>. У випадках, коли ви вважаєте
-ненадійним наявний вміст диска, радимо скористатися цим параметром для
-знищення можливого коду зловмисників.
+Зазвичай, формат диска визначається автоматично, але ви також можете вказати його за допомогою параметра I<--format>. У випадках, коли ви вважаєте ненадійним наявний вміст диска, радимо скористатися цим параметром для знищення можливого коду зловмисників.
=head1 ПАРАМЕТРИ
=item B<--add> файл
-Додати I<файл>, який має бути образом диска, розділом основної системи,
-логічним томом, зовнішнім диском USB тощо.
+Додати I<файл>, який має бути образом диска, розділом основної системи, логічним томом, зовнішнім диском USB тощо.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
B<Всі поточні дані на диску буде витерто.>
=item B<--filesystem=ext3|ntfs|vfat|...>
-Створити порожню файлову систему вказаного типу. У libguestfs передбачено
-підтримку багатьох файлових систем.
+Створити порожню файлову систему вказаного типу. У libguestfs передбачено підтримку багатьох файлових систем.
=item B<--filesystem=none>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-format --format=raw -a диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-format --format=raw -a диск.img --format -a ще_один_диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<--label=>МІТКА
=item B<--lvm=/dev/I<VG>/I<LV>>
-Створити логічний том LVM2 Linux із назвою F</dev/I<VG>/I<LV>>. Ви можете
-змінити назву групи томів і логічного тому.
+Створити логічний том LVM2 Linux із назвою F</dev/I<VG>/I<LV>>. Ви можете змінити назву групи томів і логічного тому.
=item B<--lvm>
=item B<--partition>
-Створити розділ MBR або GPT для усього диска. MBR буде вибрано, якщо розмір
-диска E<lt> 2 ТБ, GPT — якщо E<ge> 2 ТБ.
+Створити розділ MBR або GPT для усього диска. MBR буде вибрано, якщо розмір диска E<lt> 2 ТБ, GPT — якщо E<ge> 2 ТБ.
Типове значення.
=item B<--partition=none>
-Не створювати таблиці розділів. Зауважте, що такі диски можуть бути
-невидимими для Windows.
+Не створювати таблиці розділів. Зауважте, що такі диски можуть бути невидимими для Windows.
=item B<-v>
=item B<--wipe>
-У поточній версії virt-format не витирає дані з диска (оскільки ця дія є
-надто тривалою). Тому, якщо на диску є дані, їх буде лише приховано і
-частково перезаписано virt-format. Ймовірно, такі дані можна відновити за
-допомогою інструментів для редагування дисків.
+У поточній версії virt-format не витирає дані з диска (оскільки ця дія є надто тривалою). Тому, якщо на диску є дані, їх буде лише приховано і частково перезаписано virt-format. Ймовірно, такі дані можна відновити за допомогою інструментів для редагування дисків.
-Якщо ви скористаєтеся цим параметром, virt-format перезапише нулями увесь
-диск, щоб попередньо записані дані не можна було відновити.
+Якщо ви скористаєтеся цим параметром, virt-format перезапише нулями увесь диск, щоб попередньо записані дані не можна було відновити.
=item B<-x>
=head1 СТАН ВИХОДУ
-Ця програма повертає C<0>, якщо роботу виконано успішно, і C<1>, якщо
-сталися помилки.
+Ця програма повертає C<0>, якщо роботу виконано успішно, і C<1>, якщо сталися помилки.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-make-fs(1)>,
-L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-filesystems(1)>, L<virt-make-fs(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-get-kernel 1"
-.TH virt-get-kernel 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-get-kernel 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-За допомогою цього параметра можна видобути ядро та initramfs з гостьової
-системи.
+За допомогою цього параметра можна видобути ядро та initramfs з гостьової системи.
.PP
-Формат образу диска буде визначено автоматично, якщо ви не вкажете його за
-допомогою параметра \fI\-\-format\fR.
+Формат образу диска буде визначено автоматично, якщо ви не вкажете його за допомогою параметра \fI\-\-format\fR.
.PP
-Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим
-номером. Щоб видобути із образу диска ядро з певним номером версії,
-скористайтеся \fBguestfish\fR\|(1). Щоб видобути із гостьової системи увесь вміст
-каталогу \f(CW\*(C`/boot\*(C'\fR, скористайтеся \fBvirt\-copy\-out\fR\|(1).
+Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим номером. Щоб видобути із образу диска ядро з певним номером версії, скористайтеся \fBguestfish\fR\|(1). Щоб видобути із гостьової системи увесь вміст каталогу \f(CW\*(C`/boot\*(C'\fR, скористайтеся \fBvirt\-copy\-out\fR\|(1).
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.PD
Додати \fIфайл\fR, який має бути образом диска з віртуальної машини.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-add\fR адреса" 4
.IX Item "--add адреса"
.PD
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
.IP "\fB\-\-blocksize\fR \fB512\fR" 4
.IX Item "--blocksize 512"
.PD 0
.IP "\fB\-\-blocksize\fR \fB4096\fR" 4
.IX Item "--blocksize 4096"
.PD
-This parameter sets the sector size of the disk image added with \fI\-a\fR
-option and is ignored for libvirt guest added with \fI\-d\fR option. See also
-\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
+This parameter sets the sector size of the disk image added with \fI\-a\fR option and is ignored for libvirt guest added with \fI\-d\fR option. See also \*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-c\fR адреса" 4
.IX Item "-c адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-get-kernel попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-get-kernel попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у рядку команди.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у рядку команди.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IP "\fB\-\-machine\-readable\fR=формат" 4
.IX Item "--machine-readable=формат"
.PD
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
.IP "\fB\-o\fR каталог" 4
.IX Item "-o каталог"
.PD 0
.IP "\fB\-\-output\fR каталог" 4
.IX Item "--output каталог"
.PD
-Цей параметр визначає каталог виведення, куди буде записано ядро і initramfs
-з гостьової системи.
+Цей параметр визначає каталог виведення, куди буде записано ядро і initramfs з гостьової системи.
.Sp
Якщо не вказано, типово, дані буде виведено до поточного каталогу.
.IP "\fB\-\-prefix\fR префікс" 4
.IX Item "--prefix префікс"
За допомогою цього параметра можна вказати префікс для видобутих файлів.
.Sp
-Якщо вказано префікс, програма додасть дефіс (\f(CW\*(C`\-\*(C'\fR) після префікса і перед
-рештою назви файла. Наприклад, якщо у гостьовій системі ядро називалося
-\&\f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR, його буде збережено як
-\&\f(CW\*(C`mydistro\-vmlinuz\-3.19.0\-20\-generic\*(C'\fR, якщо було вказано префікс
-\&\f(CW\*(C`mydistro\*(C'\fR.
+Якщо вказано префікс, програма додасть дефіс (\f(CW\*(C`\-\*(C'\fR) після префікса і перед рештою назви файла. Наприклад, якщо у гостьовій системі ядро називалося \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR, його буде збережено як \f(CW\*(C`mydistro\-vmlinuz\-3.19.0\-20\-generic\*(C'\fR, якщо було вказано префікс \f(CW\*(C`mydistro\*(C'\fR.
.Sp
Див. також \fI\-\-unversioned\-names\fR.
.IP "\fB\-q\fR" 4
.IX Item "--unversioned-names"
Цей параметр впливає на назву файла призначення для видобутих файлів.
.Sp
-Якщо увімкнено, файли буде збережено локально лише з базовою
-назвою. Наприклад, якщо ядро та диск у пам'яті у гостьовій системі
-називалися \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR та \f(CW\*(C`initrd.img\-3.19.0\-20\-generic\*(C'\fR,
-їх буде збережено, відповідно, як \f(CW\*(C`vmlinuz\*(C'\fR та \f(CW\*(C`initrd.img\*(C'\fR.
+Якщо увімкнено, файли буде збережено локально лише з базовою назвою. Наприклад, якщо ядро та диск у пам'яті у гостьовій системі називалися \f(CW\*(C`vmlinuz\-3.19.0\-20\-generic\*(C'\fR та \f(CW\*(C`initrd.img\-3.19.0\-20\-generic\*(C'\fR, їх буде збережено, відповідно, як \f(CW\*(C`vmlinuz\*(C'\fR та \f(CW\*(C`initrd.img\*(C'\fR.
.Sp
Див. також \fI\-\-prefix\fR.
.IP "\fB\-v\fR" 4
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
.IX Header "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра
-робить зручним використання virt-get-kernel з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра робить зручним використання virt-get-kernel з інших програм, графічних інтерфейсів тощо.
.PP
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-get-kernel. Типово виведені дані виглядатимуть якось
-так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-get-kernel. Типово виведені дані виглядатимуть якось так:
.PP
.Vb 2
\& $ virt\-get\-kernel \-\-machine\-readable
\& virt\-get\-kernel
.Ve
.PP
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
.PP
-Можна вказати рядок форматування для керування виведенням,
-див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
+Можна вказати рядок форматування для керування виведенням, див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
-Опис інших змінних середовища, які стосуються усіх програм libguestfs,
-наведено у розділі \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
+Опис інших змінних середовища, які стосуються усіх програм libguestfs, наведено у розділі \*(L"ЗМІННІ СЕРЕДОВИЩА\*(R" in \fBguestfs\fR\|(3).
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBguestmount\fR\|(1), \fBvirt\-copy\-out\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-За допомогою цього параметра можна видобути ядро та initramfs з гостьової
-системи.
+За допомогою цього параметра можна видобути ядро та initramfs з гостьової системи.
-Формат образу диска буде визначено автоматично, якщо ви не вкажете його за
-допомогою параметра I<--format>.
+Формат образу диска буде визначено автоматично, якщо ви не вкажете його за допомогою параметра I<--format>.
-Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим
-номером. Щоб видобути із образу диска ядро з певним номером версії,
-скористайтеся L<guestfish(1)>. Щоб видобути із гостьової системи увесь вміст
-каталогу C</boot>, скористайтеся L<virt-copy-out(1)>.
+Якщо у гостьовій системі декілька ядер, буде вибрано ядро із найбільшим номером. Щоб видобути із образу диска ядро з певним номером версії, скористайтеся L<guestfish(1)>. Щоб видобути із гостьової системи увесь вміст каталогу C</boot>, скористайтеся L<virt-copy-out(1)>.
=head1 ПАРАМЕТРИ
Додати I<файл>, який має бути образом диска з віртуальної машини.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром I<--format>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format>.
=item B<-a> адреса
=item B<--add> адреса
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
=item B<--blocksize> B<512>
=item B<--blocksize> B<4096>
-This parameter sets the sector size of the disk image added with I<-a>
-option and is ignored for libvirt guest added with I<-d> option. See also
-L<guestfs(3)/guestfs_add_drive_opts>.
+This parameter sets the sector size of the disk image added with I<-a> option and is ignored for libvirt guest added with I<-d> option. See also L<guestfs(3)/guestfs_add_drive_opts>.
=item B<--colors>
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<-c> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-get-kernel попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-get-kernel попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у рядку команди.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у рядку команди.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<-o> каталог
=item B<--output> каталог
-Цей параметр визначає каталог виведення, куди буде записано ядро і initramfs
-з гостьової системи.
+Цей параметр визначає каталог виведення, куди буде записано ядро і initramfs з гостьової системи.
Якщо не вказано, типово, дані буде виведено до поточного каталогу.
За допомогою цього параметра можна вказати префікс для видобутих файлів.
-Якщо вказано префікс, програма додасть дефіс (C<->) після префікса і перед
-рештою назви файла. Наприклад, якщо у гостьовій системі ядро називалося
-C<vmlinuz-3.19.0-20-generic>, його буде збережено як
-C<mydistro-vmlinuz-3.19.0-20-generic>, якщо було вказано префікс
-C<mydistro>.
+Якщо вказано префікс, програма додасть дефіс (C<->) після префікса і перед рештою назви файла. Наприклад, якщо у гостьовій системі ядро називалося C<vmlinuz-3.19.0-20-generic>, його буде збережено як C<mydistro-vmlinuz-3.19.0-20-generic>, якщо було вказано префікс C<mydistro>.
Див. також I<--unversioned-names>.
Цей параметр впливає на назву файла призначення для видобутих файлів.
-Якщо увімкнено, файли буде збережено локально лише з базовою
-назвою. Наприклад, якщо ядро та диск у пам'яті у гостьовій системі
-називалися C<vmlinuz-3.19.0-20-generic> та C<initrd.img-3.19.0-20-generic>,
-їх буде збережено, відповідно, як C<vmlinuz> та C<initrd.img>.
+Якщо увімкнено, файли буде збережено локально лише з базовою назвою. Наприклад, якщо ядро та диск у пам'яті у гостьовій системі називалися C<vmlinuz-3.19.0-20-generic> та C<initrd.img-3.19.0-20-generic>, їх буде збережено, відповідно, як C<vmlinuz> та C<initrd.img>.
Див. також I<--prefix>.
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-get-kernel з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-get-kernel з інших програм, графічних інтерфейсів тощо.
-Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей
-виконуваного файла virt-get-kernel. Типово виведені дані виглядатимуть якось
-так:
+Скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-get-kernel. Типово виведені дані виглядатимуть якось так:
$ virt-get-kernel --machine-readable
virt-get-kernel
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 ЗМІННІ СЕРЕДОВИЩА
-Опис інших змінних середовища, які стосуються усіх програм libguestfs,
-наведено у розділі L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
+Опис інших змінних середовища, які стосуються усіх програм libguestfs, наведено у розділі L<guestfs(3)/ЗМІННІ СЕРЕДОВИЩА>.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-copy-out(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, L<virt-copy-out(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-index-validate 1"
-.TH virt-index-validate 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-index-validate 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\fBvirt\-builder\fR\|(1) використовує файл покажчика (index) для зберігання
-метаданих щодо шаблонів, способи використання яких відомі програмі. Цей файл
-покажчика має специфічний формат, перевірку якого виконує програма
-virt-index-validate.
+\&\fBvirt\-builder\fR\|(1) використовує файл покажчика (index) для зберігання метаданих щодо шаблонів, способи використання яких відомі програмі. Цей файл покажчика має специфічний формат, перевірку якого виконує програма virt-index-validate.
.PP
-Зауважте, що virt-index-validate може перевіряти як підписані, так і
-непідписані файли покажчиків (тобто, як \fIindex\fR, так і
-\&\fIindex.asc\fR). Програма здатна перевіряти лише локальні файли і не може
-працювати із зовнішніми адресами.
+Зауважте, що virt-index-validate може перевіряти як підписані, так і непідписані файли покажчиків (тобто, як \fIindex\fR, так і \fIindex.asc\fR). Програма здатна перевіряти лише локальні файли і не може працювати із зовнішніми адресами.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-compat\-1.24.0\fR" 4
.IX Item "--compat-1.24.0"
-Перевірити на сумісність за допомогою virt-builder 1.24.0. (Використання
-цього параметра автоматично додає \fI\-\-compat\-1.24.1\fR, тому немає потреби у
-додатковому параметрі, якщо ви вже вказали цей.)
+Перевірити на сумісність за допомогою virt-builder 1.24.0. (Використання цього параметра автоматично додає \fI\-\-compat\-1.24.1\fR, тому немає потреби у додатковому параметрі, якщо ви вже вказали цей.)
.Sp
Зокрема:
.RS 4
.IP "\(bu" 4
-Ця версія virt-builder не здатна обробляти \f(CW\*(C`[...]\*(C'\fR (квадратні дужки) у
-назвах полів (наприклад, \f(CW\*(C`checksum[sha512]=...\*(C'\fR).
+Ця версія virt-builder не здатна обробляти \f(CW\*(C`[...]\*(C'\fR (квадратні дужки) у назвах полів (наприклад, \f(CW\*(C`checksum[sha512]=...\*(C'\fR).
.IP "\(bu" 4
Потребувало від'єднаних підписів (\f(CW\*(C`sig=...\*(C'\fR).
.RE
Зокрема:
.RS 4
.IP "\(bu" 4
-У цій версії virt-builder не було передбачено обробки \f(CW\*(C`.\*(C'\fR (крапки) у назвах
-полів або \f(CW\*(C`,\*(C'\fR (коми) у назвах підполів.
+У цій версії virt-builder не було передбачено обробки \f(CW\*(C`.\*(C'\fR (крапки) у назвах полів або \f(CW\*(C`,\*(C'\fR (коми) у назвах підполів.
.IP "\(bu" 4
Вона не може обробляти коментарі, які є у цьому файлі.
.RE
Показати дані щодо версії і завершити роботу.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає 0, якщо файл покажчика пройде перевірку, або ненульове
-значення, якщо сталася помилка.
+Ця програма повертає 0, якщо файл покажчика пройде перевірку, або ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
\&\fBvirt\-builder\fR\|(1), http://libguestfs.org/.
=head1 ОПИС
-L<virt-builder(1)> використовує файл покажчика (index) для зберігання
-метаданих щодо шаблонів, способи використання яких відомі програмі. Цей файл
-покажчика має специфічний формат, перевірку якого виконує програма
-virt-index-validate.
+L<virt-builder(1)> використовує файл покажчика (index) для зберігання метаданих щодо шаблонів, способи використання яких відомі програмі. Цей файл покажчика має специфічний формат, перевірку якого виконує програма virt-index-validate.
-Зауважте, що virt-index-validate може перевіряти як підписані, так і
-непідписані файли покажчиків (тобто, як F<index>, так і
-F<index.asc>). Програма здатна перевіряти лише локальні файли і не може
-працювати із зовнішніми адресами.
+Зауважте, що virt-index-validate може перевіряти як підписані, так і непідписані файли покажчиків (тобто, як F<index>, так і F<index.asc>). Програма здатна перевіряти лише локальні файли і не може працювати із зовнішніми адресами.
=head1 ПАРАМЕТРИ
=item B<--compat-1.24.0>
-Перевірити на сумісність за допомогою virt-builder 1.24.0. (Використання
-цього параметра автоматично додає I<--compat-1.24.1>, тому немає потреби у
-додатковому параметрі, якщо ви вже вказали цей.)
+Перевірити на сумісність за допомогою virt-builder 1.24.0. (Використання цього параметра автоматично додає I<--compat-1.24.1>, тому немає потреби у додатковому параметрі, якщо ви вже вказали цей.)
Зокрема:
=item *
-Ця версія virt-builder не здатна обробляти C<[...]> (квадратні дужки) у
-назвах полів (наприклад, C<checksum[sha512]=...>).
+Ця версія virt-builder не здатна обробляти C<[...]> (квадратні дужки) у назвах полів (наприклад, C<checksum[sha512]=...>).
=item *
=item *
-У цій версії virt-builder не було передбачено обробки C<.> (крапки) у назвах
-полів або C<,> (коми) у назвах підполів.
+У цій версії virt-builder не було передбачено обробки C<.> (крапки) у назвах полів або C<,> (коми) у назвах підполів.
=item *
=head1 СТАН ВИХОДУ
-Ця програма повертає 0, якщо файл покажчика пройде перевірку, або ненульове
-значення, якщо сталася помилка.
+Ця програма повертає 0, якщо файл покажчика пройде перевірку, або ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-inspector 1"
-.TH virt-inspector 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-inspector 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "НАЗВА"
.IX Header "НАЗВА"
-virt-inspector — показ версії операційної системи та інших даних щодо
-віртуальної машини
+virt-inspector — показ версії операційної системи та інших даних щодо віртуальної машини
.SH "КОРОТКИЙ ОПИС"
.IX Header "КОРОТКИЙ ОПИС"
.Vb 1
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\fBvirt-inspector\fR виконує вивчення віртуальної машини або образу диска і
-намагається визначити версію операційної системи та інші дані щодо
-віртуальної машини.
+\&\fBvirt-inspector\fR виконує вивчення віртуальної машини або образу диска і намагається визначити версію операційної системи та інші дані щодо віртуальної машини.
.PP
Virt-inspector виводить дані \s-1XML\s0 для обробки у інших програмах.
.PP
-У звичайному режимі користуйтеся командою \f(CW\*(C`virt\-inspector \-d назва_домену\*(C'\fR,
-де \f(CW\*(C`назва_домену\*(C'\fR — назва домену libvirt (див. \f(CW\*(C`virsh list \-\-all\*(C'\fR).
-.PP
-Ви також можете запускати virt-inspector безпосередньо для образів дисків з
-однієї віртуальної машини. Для цього слід використовувати команду
-\&\f(CW\*(C`virt\-inspector \-a образ.диска\*(C'\fR. У рідкісних випадках у домені може бути
-декілька блокових пристроїв. У цьому випадку вам слід вказати список із
-декількох параметрів \fI\-a\fR, один за одним. Перший має відповідати пристрою
-\&\fI/dev/sda\fR гостьової системи, другий — пристрою \fI/dev/sdb\fR гостьової
-системи тощо.
-.PP
-Ви також можете запускати virt-inspector для дисків для встановлення
-системи, образів компакт\-дисків для портативних систем, призначених для
-завантаження образів флешок \s-1USB\s0 тощо.
-.PP
-Virt-inspector може одночасно інспектувати і створювати звіт лише для
-\&\fIодного домену\fR. Для інспектування декількох віртуальних машин вам
-доведеться запускати virt-inspector декілька разів (наприклад, із циклу for
-скрипту оболонки).
-.PP
-Оскільки virt-inspector потрібен безпосередній доступ до образів гостьової
-системи, програма, зазвичай, не працюватиме, якщо використовується віддалене
-з'єднання із libvirt.
-.PP
-Усі дані, які доступні за допомогою virt-inspector, також доступні і з
-основного програмного інтерфейсу інспектування libguestfs
-(див. \*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3)). Ті самі дані можна також отримати за
-допомогою guestfish або прив'язок до libguestfs багатьма мовами
-програмування (див. \*(L"ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ
-ПРОГРАМНОГО ІНТЕРФЕЙСУ \s-1LIBGUESTFS\*(R"\s0).
+У звичайному режимі користуйтеся командою \f(CW\*(C`virt\-inspector \-d назва_домену\*(C'\fR, де \f(CW\*(C`назва_домену\*(C'\fR — назва домену libvirt (див. \f(CW\*(C`virsh list \-\-all\*(C'\fR).
+.PP
+Ви також можете запускати virt-inspector безпосередньо для образів дисків з однієї віртуальної машини. Для цього слід використовувати команду \f(CW\*(C`virt\-inspector \-a образ.диска\*(C'\fR. У рідкісних випадках у домені може бути декілька блокових пристроїв. У цьому випадку вам слід вказати список із декількох параметрів \fI\-a\fR, один за одним. Перший має відповідати пристрою \fI/dev/sda\fR гостьової системи, другий — пристрою \fI/dev/sdb\fR гостьової системи тощо.
+.PP
+Ви також можете запускати virt-inspector для дисків для встановлення системи, образів компакт\-дисків для портативних систем, призначених для завантаження образів флешок \s-1USB\s0 тощо.
+.PP
+Virt-inspector може одночасно інспектувати і створювати звіт лише для \fIодного домену\fR. Для інспектування декількох віртуальних машин вам доведеться запускати virt-inspector декілька разів (наприклад, із циклу for скрипту оболонки).
+.PP
+Оскільки virt-inspector потрібен безпосередній доступ до образів гостьової системи, програма, зазвичай, не працюватиме, якщо використовується віддалене з'єднання із libvirt.
+.PP
+Усі дані, які доступні за допомогою virt-inspector, також доступні і з основного програмного інтерфейсу інспектування libguestfs (див. \*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3)). Ті самі дані можна також отримати за допомогою guestfish або прив'язок до libguestfs багатьма мовами програмування (див. \*(L"ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ ПРОГРАМНОГО ІНТЕРФЕЙСУ \s-1LIBGUESTFS\*(R"\s0).
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Libvirt використовуватиметься, лише якщо ви вкажете \f(CW\*(C`назву домену\*(C'\fR у рядку
-команди. Якщо вказати блокові пристрої гостьових систем безпосередньо
-(\fI\-a\fR), libvirt не буде використовуватися взагалі.
+Libvirt використовуватиметься, лише якщо ви вкажете \f(CW\*(C`назву домену\*(C'\fR у рядку команди. Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-inspector попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-inspector попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Визначає формат образу диска, назву якого вказано у рядку команди. Якщо
-формат не вказано, його буде визначено автоматично на основі вмісту образу
-диска.
+Визначає формат образу диска, назву якого вказано у рядку команди. Якщо формат не вказано, його буде визначено автоматично на основі вмісту образу диска.
.Sp
-Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних
-до libvirt. У цьому випадку вказане значення параметра формату буде
-проігноровано.
+Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних до libvirt. У цьому випадку вказане значення параметра формату буде проігноровано.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
multiple keys on stdin, one per line.
.IP "\fB\-\-no\-applications\fR" 4
.IX Item "--no-applications"
-Типово, виведені virt-inspector дані містять список програм, які встановлено
-у гостьовій системі, якщо такий список доступний.
+Типово, виведені virt-inspector дані містять список програм, які встановлено у гостьовій системі, якщо такий список доступний.
.Sp
Вкажіть цей параметр, щоб вимкнути частину \s-1XML\s0 результату.
.IP "\fB\-\-no\-icon\fR" 4
.IX Item "--no-icon"
-Типово, виведені virt-inspector дані містять список програм, які встановлено
-у гостьовій системі, якщо такий список доступний (див. \*(L"icon\*(R").
+Типово, виведені virt-inspector дані містять список програм, які встановлено у гостьовій системі, якщо такий список доступний (див. \*(L"icon\*(R").
.Sp
Вкажіть цей параметр, щоб вимкнути частину \s-1XML\s0 результату.
.IP "\fB\-v\fR" 4
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.IP "\fB\-\-xpath\fR запит" 4
.IX Item "--xpath запит"
-Виконати запит XPath до \s-1XML\s0 у stdin і вивести результат до stdout. У цьому
-режимі virt-inspector просто виконує запит XPath; усі інші функції
-інспектування буде вимкнено. Приклади запитів наведено у розділі \*(L"ЗАПИТИ
-\&\s-1XPATH\*(R"\s0 нижче.
+Виконати запит XPath до \s-1XML\s0 у stdin і вивести результат до stdout. У цьому режимі virt-inspector просто виконує запит XPath; усі інші функції інспектування буде вимкнено. Приклади запитів наведено у розділі \*(L"ЗАПИТИ \s-1XPATH\*(R"\s0 нижче.
.SH "ПАРАМЕТРИ КОМАНДНОГО РЯДКА У ФОРМАТІ ПОПЕРЕДНІХ ВЕРСІЙ"
.IX Header "ПАРАМЕТРИ КОМАНДНОГО РЯДКА У ФОРМАТІ ПОПЕРЕДНІХ ВЕРСІЙ"
У попередніх версіях virt-inspector можна було використовувати або
\& virt\-inspector назва_гостьової_системи
.Ve
.PP
-тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
.PP
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
.SH "ФОРМАТ XML"
.IX Header "ФОРМАТ XML"
-Точний опис \s-1XML\s0 virt-inspector наведено у файлі схеми \s-1RELAX NG\s0
-\&\fIvirt\-inspector.rng\fR, який постачається разом із libguestfs. Цей розділ
-містить лише поверхневий огляд.
-.PP
-Елементом верхнього рівня є <operatingsystems>. Він містить один або
-декілька елементів <operatingsystem>. Елементів
-<operatingsystem> буде декілька, лише якщо у віртуальній машині
-передбачено декілька варіантів завантаження. Такі випадки є дуже рідкісними
-у світі віртуальних машин.
+Точний опис \s-1XML\s0 virt-inspector наведено у файлі схеми \s-1RELAX NG\s0 \fIvirt\-inspector.rng\fR, який постачається разом із libguestfs. Цей розділ містить лише поверхневий огляд.
+.PP
+Елементом верхнього рівня є <operatingsystems>. Він містить один або декілька елементів <operatingsystem>. Елементів <operatingsystem> буде декілька, лише якщо у віртуальній машині передбачено декілька варіантів завантаження. Такі випадки є дуже рідкісними у світі віртуальних машин.
.SS "<operatingsystem>"
.IX Subsection "<operatingsystem>"
-Всередині теґу <operatingsystem> містяться різноманітні
-необов'язкові поля, які описують операційну систему, її архітектуру, містять
-описовий рядок «назва продукту», тип операційної системи тощо. Ось приклад:
+Всередині теґу <operatingsystem> містяться різноманітні необов'язкові поля, які описують операційну систему, її архітектуру, містять описовий рядок «назва продукту», тип операційної системи тощо. Ось приклад:
.PP
.Vb 11
\& <operatingsystems>
\& <windows_systemroot>/Windows</windows_systemroot>
.Ve
.PP
-Якщо коротко, <name> — клас операційної системи (щось подібне до
-\&\f(CW\*(C`linux\*(C'\fR або \f(CW\*(C`windows\*(C'\fR), <distro> — дистрибутив (наприклад,
-\&\f(CW\*(C`fedora\*(C'\fR, але передбачено розпізнавання багатьох інших дистрибутивів), а
-<arch> — архітектура гостьової системи. Інші поля мають доволі
-зрозуміле призначення, але оскільки ці поля взято безпосередньо з
-програмного інтерфейсу інспектування libguestfs, їхній повний опис можна
-знайти у розділі \*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3).
-.PP
-Елемент <root> є пристроєм кореневої файлової системи, але з точки
-зору libguestfs (блокові пристрої можуть мати зовсім інші назви у самій
-віртуальній машині).
+Якщо коротко, <name> — клас операційної системи (щось подібне до \f(CW\*(C`linux\*(C'\fR або \f(CW\*(C`windows\*(C'\fR), <distro> — дистрибутив (наприклад, \f(CW\*(C`fedora\*(C'\fR, але передбачено розпізнавання багатьох інших дистрибутивів), а <arch> — архітектура гостьової системи. Інші поля мають доволі зрозуміле призначення, але оскільки ці поля взято безпосередньо з програмного інтерфейсу інспектування libguestfs, їхній повний опис можна знайти у розділі \*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3).
+.PP
+Елемент <root> є пристроєм кореневої файлової системи, але з точки зору libguestfs (блокові пристрої можуть мати зовсім інші назви у самій віртуальній машині).
.SS "<mountpoints>"
.IX Subsection "<mountpoints>"
-У Un*x\-подібних гостьових системах типово міститься декілька файлових
-систем, які монтуються як різні точки монтування. Ці файлові системи описано
-у елементі <mountpoints>, який виглядає ось так:
+У Un*x\-подібних гостьових системах типово міститься декілька файлових систем, які монтуються як різні точки монтування. Ці файлові системи описано у елементі <mountpoints>, який виглядає ось так:
.PP
.Vb 7
\& <operatingsystems>
\& </mountpoints>
.Ve
.PP
-Як і з <root>, пристрої подано з точки зору libguestfs, отже вони
-можуть мати зовсім інші назви у гостьовій системі. У списку буде наведено
-лише монтовані файлові системи, а не щось подібне до пристроїв резервної
-пам'яті на диску.
+Як і з <root>, пристрої подано з точки зору libguestfs, отже вони можуть мати зовсім інші назви у гостьовій системі. У списку буде наведено лише монтовані файлові системи, а не щось подібне до пристроїв резервної пам'яті на диску.
.SS "<filesystems>"
.IX Subsection "<filesystems>"
-Елемент <filesystems> подібний до <mountpoints>, але
-стосується файлових \fIусіх\fR файлових систем, що належать гостьовій
-операційній системі, зокрема розділів резервної пам'яті на диску та порожніх
-розділів. (У рідкісних випадках гостьової системи із варіантами
-завантаження, цей елемент стосується файлових систем, що належать цій
-операційній системі або є спільними для цієї операційної системи та інших
-операційних систем.)
+Елемент <filesystems> подібний до <mountpoints>, але стосується файлових \fIусіх\fR файлових систем, що належать гостьовій операційній системі, зокрема розділів резервної пам'яті на диску та порожніх розділів. (У рідкісних випадках гостьової системи із варіантами завантаження, цей елемент стосується файлових систем, що належать цій операційній системі або є спільними для цієї операційної системи та інших операційних систем.)
.PP
Ви побачите щось таке:
.PP
\& </filesystem>
.Ve
.PP
-Необов'язкові елементи у <filesystem> стосуються типу, мітки та \s-1UUID\s0
-файлової системи.
+Необов'язкові елементи у <filesystem> стосуються типу, мітки та \s-1UUID\s0 файлової системи.
.SS "<applications>"
.IX Subsection "<applications>"
-Пов'язані елементи <package_format>, <package_management> та
-<applications> описують програми, які встановлено у віртуальній
-машині.
+Пов'язані елементи <package_format>, <package_management> та <applications> описують програми, які встановлено у віртуальній машині.
.PP
-Елемент <package_format>, якщо він є, описує використану систему
-пакунків. Типовими значеннями цього елемента є \f(CW\*(C`rpm\*(C'\fR та \f(CW\*(C`deb\*(C'\fR.
+Елемент <package_format>, якщо він є, описує використану систему пакунків. Типовими значеннями цього елемента є \f(CW\*(C`rpm\*(C'\fR та \f(CW\*(C`deb\*(C'\fR.
.PP
-Елемент <package_management>, якщо такий є, описує засіб для
-керування пакунками. Серед типових значень елемента є \f(CW\*(C`yum\*(C'\fR, \f(CW\*(C`up2date\*(C'\fR та
-\&\f(CW\*(C`apt\*(C'\fR.
+Елемент <package_management>, якщо такий є, описує засіб для керування пакунками. Серед типових значень елемента є \f(CW\*(C`yum\*(C'\fR, \f(CW\*(C`up2date\*(C'\fR та \f(CW\*(C`apt\*(C'\fR.
.PP
<applications> містить список пакунків або встановлених програм.
.PP
\& </application>
.Ve
.PP
-Для деяких типів гостьових системи дані полів версії і випуску можуть бути
-недоступними. Можлива поява інших полів,
-див. \*(L"guestfs_inspect_list_applications\*(R" in \fBguestfs\fR\|(3).
+Для деяких типів гостьових системи дані полів версії і випуску можуть бути недоступними. Можлива поява інших полів, див. \*(L"guestfs_inspect_list_applications\*(R" in \fBguestfs\fR\|(3).
.SS "<drive_mappings>"
.IX Subsection "<drive_mappings>"
-Для операційних систем, подібних до Windows, де для позначення дисків
-використовуються літери, virt-inspector може визначати прив'язки літер
-дисків до файлових систем.
+Для операційних систем, подібних до Windows, де для позначення дисків використовуються літери, virt-inspector може визначати прив'язки літер дисків до файлових систем.
.PP
.Vb 7
\& <operatingsystems>
\& </drive_mappings>
.Ve
.PP
-У наведеному вище прикладі диск C пов'язано із файловою системою на другому
-розділі першого диска, диск E — із файловою системою на першому розділі
-другого диска.
+У наведеному вище прикладі диск C пов'язано із файловою системою на другому розділі першого диска, диск E — із файловою системою на першому розділі другого диска.
.PP
-Зауважте, що це стосується лише постійних прив'язок дисків, а не прив'язок,
-які подібні до прив'язок до спільних ресурсів у мережі. Крім того, до цього
-списку може бути не включено точки монтування томів \s-1NTFS.\s0
+Зауважте, що це стосується лише постійних прив'язок дисків, а не прив'язок, які подібні до прив'язок до спільних ресурсів у мережі. Крім того, до цього списку може бути не включено точки монтування томів \s-1NTFS.\s0
.SS "<icon>"
.IX Subsection "<icon>"
-Іноді virt-inspector може видобути піктограму або логотип гостьової
-системи. Піктограму буде повернуто у форматі даних \s-1PNG\s0 у кодуванні
-base64. Зауважте, що піктограма може бути доволі великою і дуже якісною.
+Іноді virt-inspector може видобути піктограму або логотип гостьової системи. Піктограму буде повернуто у форматі даних \s-1PNG\s0 у кодуванні base64. Зауважте, що піктограма може бути доволі великою і дуже якісною.
.PP
.Vb 7
\& <operatingsystems>
\& </icon>
.Ve
.PP
-Для показу піктограми вам слід видобути ї і перетворити дані у кодуванні
-base64 знову у двійковий файл. Скористайтеся запитом XPath або простим
-редактором для видобування даних, а потім програмою \fBbase64\fR\|(1) з coreutils
-для перетворення цих даних на файл \s-1PNG:\s0
+Для показу піктограми вам слід видобути ї і перетворити дані у кодуванні base64 знову у двійковий файл. Скористайтеся запитом XPath або простим редактором для видобування даних, а потім програмою \fBbase64\fR\|(1) з coreutils для перетворення цих даних на файл \s-1PNG:\s0
.PP
.Vb 1
\& base64 \-i \-d < дані.піктограми > icon.png
.Ve
.SH "ЗАПИТИ XPATH"
.IX Header "ЗАПИТИ XPATH"
-У virt-inspector передбачено вбудовану підтримку виконання запитів
-XPath. Причиною включення підтримкиXPath безпосередньо до virt-inspector є
-те, що не існує добрих і широкодоступних засобів командного рядка, які
-можуть виконувати запити XPath. Єдиним добрим засобом є \fBxmlstarlet\fR\|(1),
-але ця програма недоступна у Red Hat Enterprise Linux.
+У virt-inspector передбачено вбудовану підтримку виконання запитів XPath. Причиною включення підтримкиXPath безпосередньо до virt-inspector є те, що не існує добрих і широкодоступних засобів командного рядка, які можуть виконувати запити XPath. Єдиним добрим засобом є \fBxmlstarlet\fR\|(1), але ця програма недоступна у Red Hat Enterprise Linux.
.PP
-Для виконання запиту XPath скористайтеся параметром \fI\-\-xpath\fR. Зауважте, що
-у цьому режимі virt-inspector просто читає \s-1XML\s0 зі stdin і виводить результат
-запиту до stdout. Усі інші можливості інспектування у цьому режимі вимкнено.
+Для виконання запиту XPath скористайтеся параметром \fI\-\-xpath\fR. Зауважте, що у цьому режимі virt-inspector просто читає \s-1XML\s0 зі stdin і виводить результат запиту до stdout. Усі інші можливості інспектування у цьому режимі вимкнено.
.PP
Приклад:
.PP
.Ve
.SH "ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ ПРОГРАМНОГО ІНТЕРФЕЙСУ LIBGUESTFS"
.IX Header "ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ ПРОГРАМНОГО ІНТЕРФЕЙСУ LIBGUESTFS"
-У ранніх версіях libguestfs virt-inspector був великим скриптом Perl, до
-якого було включено багато евристики для інспектування гостьових систем. Цей
-підхід мав декілька проблем: для виконання інспектування з інших
-інструментів (зокрема guestfish) нам доводилося викликати цей скрипт Perl;
-він ставив у пріоритетне становище Perl над іншими мовами програмування,
-підтримку яких передбачено у libguestfs.
-.PP
-До libguestfs 1.8 ми переписали код Perl на C і включили його до програмного
-інтерфейсу основи libguestfs (\fBguestfs\fR\|(3)). Тепер virt-inspector є простим
-тонким прошарком C над основним програмним інтерфейсом мовою C. Усі дані
-інспектування доступні з усіх мов програмування, підтримку яких передбачено
-у libguestfs, і з guestfish.
-.PP
-Опис програмного інтерфейсу інспектування мовою C наведено у розділі
-\&\*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3).
-.PP
-Приклад коду, де використовується програмний інтерфейс інспектування мовою
-C, наведено у файлі \fIinspect\-vm.c\fR, який постачається разом із libguestfs.
-.PP
-Крім того, \fIinspect\-vm.c\fR трансльовано іншими мовами
-програмування. Наприклад, \fIinspect_vm.pl\fR є трансляцією на Perl. Також
-передбачено інші трансляції на OCaml, Python
-тощо. Див. \*(L"ВИКОРИСТАННЯ \s-1LIBGUESTFS\s0 ЗА ДОПОМОГОЮ ІНШИХ МОВ
-ПРОГРАМУВАННЯ\*(R" in \fBguestfs\fR\|(3), де наведено список сторінок підручника, де містяться
-приклади коду.
+У ранніх версіях libguestfs virt-inspector був великим скриптом Perl, до якого було включено багато евристики для інспектування гостьових систем. Цей підхід мав декілька проблем: для виконання інспектування з інших інструментів (зокрема guestfish) нам доводилося викликати цей скрипт Perl; він ставив у пріоритетне становище Perl над іншими мовами програмування, підтримку яких передбачено у libguestfs.
+.PP
+До libguestfs 1.8 ми переписали код Perl на C і включили його до програмного інтерфейсу основи libguestfs (\fBguestfs\fR\|(3)). Тепер virt-inspector є простим тонким прошарком C над основним програмним інтерфейсом мовою C. Усі дані інспектування доступні з усіх мов програмування, підтримку яких передбачено у libguestfs, і з guestfish.
+.PP
+Опис програмного інтерфейсу інспектування мовою C наведено у розділі \*(L"ІНСПЕКТУВАННЯ\*(R" in \fBguestfs\fR\|(3).
+.PP
+Приклад коду, де використовується програмний інтерфейс інспектування мовою C, наведено у файлі \fIinspect\-vm.c\fR, який постачається разом із libguestfs.
+.PP
+Крім того, \fIinspect\-vm.c\fR трансльовано іншими мовами програмування. Наприклад, \fIinspect_vm.pl\fR є трансляцією на Perl. Також передбачено інші трансляції на OCaml, Python тощо. Див. \*(L"ВИКОРИСТАННЯ \s-1LIBGUESTFS\s0 ЗА ДОПОМОГОЮ ІНШИХ МОВ ПРОГРАМУВАННЯ\*(R" in \fBguestfs\fR\|(3), де наведено список сторінок підручника, де містяться приклади коду.
.SS "ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ВІД \s-1GUESTFISH\s0"
.IX Subsection "ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ВІД GUESTFISH"
-Якщо ви використовуєте параметр guestfish \fI\-i\fR, викликається основний
-програмний інтерфейс інспектування \*(L"guestfs_inspect_os\*(R" in \fBguestfs\fR\|(3) мовою
-C. Це еквівалент команди guestfish \f(CW\*(C`inspect\-os\*(C'\fR. Ви також можете викликати
-цю команду guestfish вручну.
-.PP
-\&\f(CW\*(C`inspect\-os\*(C'\fR виконує інспектування поточного образу диска, повертаючи
-список знайдених операційних систем. Кожну операційну систему представлено
-її пристроєм кореневої файлової системи. У більшості випадків ця команда не
-виводить ніяких даних (не знайдено жодної операційної системи) або виводить
-єдиний кореневий пристрій, але ви маєте зважати на те, що ця команда може
-вивести декілька рядків, якщо у образі декілька операційних систем або із
-гостьовою системою з'єднано компакт\-диск для встановлення.
+Якщо ви використовуєте параметр guestfish \fI\-i\fR, викликається основний програмний інтерфейс інспектування \*(L"guestfs_inspect_os\*(R" in \fBguestfs\fR\|(3) мовою C. Це еквівалент команди guestfish \f(CW\*(C`inspect\-os\*(C'\fR. Ви також можете викликати цю команду guestfish вручну.
+.PP
+\&\f(CW\*(C`inspect\-os\*(C'\fR виконує інспектування поточного образу диска, повертаючи список знайдених операційних систем. Кожну операційну систему представлено її пристроєм кореневої файлової системи. У більшості випадків ця команда не виводить ніяких даних (не знайдено жодної операційної системи) або виводить єдиний кореневий пристрій, але ви маєте зважати на те, що ця команда може вивести декілька рядків, якщо у образі декілька операційних систем або із гостьовою системою з'єднано компакт\-диск для встановлення.
.PP
.Vb 4
\& $ guestfish \-\-ro \-a F15x32.img
\& /dev/vg_f15x32/lv_root
.Ve
.PP
-За допомогою кореневого пристрою ви можете отримати подальшу інформацію щодо
-гостьової системи:
+За допомогою кореневого пристрою ви можете отримати подальшу інформацію щодо гостьової системи:
.PP
.Vb 8
\& ><fs> inspect\-get\-type /dev/vg_f15x32/lv_root
\& Fedora release 15 (Lovelock)
.Ve
.PP
-Обмеження guestfish ускладнюють прив'язку кореневого пристрою до змінної
-(оскільки у guestfish немає змінних), отже, якщо вам потрібно робити це
-декілька разів, варто написати скрипт якоюсь іншою мовою програмування,
-підтримку якої передбачено програмним інтерфейсом libguestfs.
+Обмеження guestfish ускладнюють прив'язку кореневого пристрою до змінної (оскільки у guestfish немає змінних), отже, якщо вам потрібно робити це декілька разів, варто написати скрипт якоюсь іншою мовою програмування, підтримку якої передбачено програмним інтерфейсом libguestfs.
.PP
Для отримання списку програм вам спочатку слід змонтувати диски:
.PP
\& }
.Ve
.PP
-Зауважте, що для показу піктограми гостьової системи файлові системи має
-бути змонтовано у означений вище спосіб. Далі, ви можете зробити так:
+Зауважте, що для показу піктограми гостьової системи файлові системи має бути змонтовано у означений вище спосіб. Далі, ви можете зробити так:
.PP
.Vb 1
\& ><fs> inspect\-get\-icon /dev/vg_f15x32/lv_root | display \-
.Ve
.SH "ПОПЕРЕДНІ ВЕРСІЇ VIRT-INSPECTOR"
.IX Header "ПОПЕРЕДНІ ВЕРСІЇ VIRT-INSPECTOR"
-Як ми вже вказували вище, ранні версії libguestfs постачалися із іншою
-програмою virt-inspector, написаною на Perl (поточну версію написано на
-C). Виведені дані \s-1XML\s0 virt-inspector на Perl були іншими, програма також
-могла виводити дані у інших форматах, зокрема текстовому.
+Як ми вже вказували вище, ранні версії libguestfs постачалися із іншою програмою virt-inspector, написаною на Perl (поточну версію написано на C). Виведені дані \s-1XML\s0 virt-inspector на Perl були іншими, програма також могла виводити дані у інших форматах, зокрема текстовому.
.PP
-Підтримку застарілої версії virt-inspector припинено, вона більше не
-постачається з libguestfs.
+Підтримку застарілої версії virt-inspector припинено, вона більше не постачається з libguestfs.
.PP
-Крім того, до непорозумінь може призвести і те, що разом із Red Hat
-Enterprise Linux 6 ми постачаємо дві версії virt-inspector із різними
-назвами:
+Крім того, до непорозумінь може призвести і те, що разом із Red Hat Enterprise Linux 6 ми постачаємо дві версії virt-inspector із різними назвами:
.PP
.Vb 2
\& virt\-inspector Стара версія на Perl.
.Ve
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), http://www.w3.org/TR/xpath/,
-\&\fBbase64\fR\|(1), \fBxmlstarlet\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), http://www.w3.org/TR/xpath/, \fBbase64\fR\|(1), \fBxmlstarlet\fR\|(1), http://libguestfs.org/.
.SH "АВТОРИ"
.IX Header "АВТОРИ"
.IP "\(bu" 4
=head1 НАЗВА
-virt-inspector — показ версії операційної системи та інших даних щодо
-віртуальної машини
+virt-inspector — показ версії операційної системи та інших даних щодо віртуальної машини
=head1 КОРОТКИЙ ОПИС
=head1 ОПИС
-B<virt-inspector> виконує вивчення віртуальної машини або образу диска і
-намагається визначити версію операційної системи та інші дані щодо
-віртуальної машини.
+B<virt-inspector> виконує вивчення віртуальної машини або образу диска і намагається визначити версію операційної системи та інші дані щодо віртуальної машини.
Virt-inspector виводить дані XML для обробки у інших програмах.
-У звичайному режимі користуйтеся командою C<virt-inspector -d назва_домену>,
-де C<назва_домену> — назва домену libvirt (див. C<virsh list --all>).
-
-Ви також можете запускати virt-inspector безпосередньо для образів дисків з
-однієї віртуальної машини. Для цього слід використовувати команду
-C<virt-inspector -a образ.диска>. У рідкісних випадках у домені може бути
-декілька блокових пристроїв. У цьому випадку вам слід вказати список із
-декількох параметрів I<-a>, один за одним. Перший має відповідати пристрою
-F</dev/sda> гостьової системи, другий — пристрою F</dev/sdb> гостьової
-системи тощо.
-
-Ви також можете запускати virt-inspector для дисків для встановлення
-системи, образів компакт-дисків для портативних систем, призначених для
-завантаження образів флешок USB тощо.
-
-Virt-inspector може одночасно інспектувати і створювати звіт лише для
-I<одного домену>. Для інспектування декількох віртуальних машин вам
-доведеться запускати virt-inspector декілька разів (наприклад, із циклу for
-скрипту оболонки).
-
-Оскільки virt-inspector потрібен безпосередній доступ до образів гостьової
-системи, програма, зазвичай, не працюватиме, якщо використовується віддалене
-з'єднання із libvirt.
-
-Усі дані, які доступні за допомогою virt-inspector, також доступні і з
-основного програмного інтерфейсу інспектування libguestfs
-(див. L<guestfs(3)/ІНСПЕКТУВАННЯ>). Ті самі дані можна також отримати за
-допомогою guestfish або прив'язок до libguestfs багатьма мовами
-програмування (див. L</ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ
-ПРОГРАМНОГО ІНТЕРФЕЙСУ LIBGUESTFS>).
+У звичайному режимі користуйтеся командою C<virt-inspector -d назва_домену>, де C<назва_домену> — назва домену libvirt (див. C<virsh list --all>).
+
+Ви також можете запускати virt-inspector безпосередньо для образів дисків з однієї віртуальної машини. Для цього слід використовувати команду C<virt-inspector -a образ.диска>. У рідкісних випадках у домені може бути декілька блокових пристроїв. У цьому випадку вам слід вказати список із декількох параметрів I<-a>, один за одним. Перший має відповідати пристрою F</dev/sda> гостьової системи, другий — пристрою F</dev/sdb> гостьової системи тощо.
+
+Ви також можете запускати virt-inspector для дисків для встановлення системи, образів компакт-дисків для портативних систем, призначених для завантаження образів флешок USB тощо.
+
+Virt-inspector може одночасно інспектувати і створювати звіт лише для I<одного домену>. Для інспектування декількох віртуальних машин вам доведеться запускати virt-inspector декілька разів (наприклад, із циклу for скрипту оболонки).
+
+Оскільки virt-inspector потрібен безпосередній доступ до образів гостьової системи, програма, зазвичай, не працюватиме, якщо використовується віддалене з'єднання із libvirt.
+
+Усі дані, які доступні за допомогою virt-inspector, також доступні і з основного програмного інтерфейсу інспектування libguestfs (див. L<guestfs(3)/ІНСПЕКТУВАННЯ>). Ті самі дані можна також отримати за допомогою guestfish або прив'язок до libguestfs багатьма мовами програмування (див. L</ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ ПРОГРАМНОГО ІНТЕРФЕЙСУ LIBGUESTFS>).
=head1 ПАРАМЕТРИ
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Libvirt використовуватиметься, лише якщо ви вкажете C<назву домену> у рядку
-команди. Якщо вказати блокові пристрої гостьових систем безпосередньо
-(I<-a>), libvirt не буде використовуватися взагалі.
+Libvirt використовуватиметься, лише якщо ви вкажете C<назву домену> у рядку команди. Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-inspector попросить вас ввести ключ або пароль, програма
-не відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-inspector попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Визначає формат образу диска, назву якого вказано у рядку команди. Якщо
-формат не вказано, його буде визначено автоматично на основі вмісту образу
-диска.
+Визначає формат образу диска, назву якого вказано у рядку команди. Якщо формат не вказано, його буде визначено автоматично на основі вмісту образу диска.
-Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних
-до libvirt. У цьому випадку вказане значення параметра формату буде
-проігноровано.
+Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних до libvirt. У цьому випадку вказане значення параметра формату буде проігноровано.
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
__INCLUDE:key-option.pod__
=item B<--no-applications>
-Типово, виведені virt-inspector дані містять список програм, які встановлено
-у гостьовій системі, якщо такий список доступний.
+Типово, виведені virt-inspector дані містять список програм, які встановлено у гостьовій системі, якщо такий список доступний.
Вкажіть цей параметр, щоб вимкнути частину XML результату.
=item B<--no-icon>
-Типово, виведені virt-inspector дані містять список програм, які встановлено
-у гостьовій системі, якщо такий список доступний (див. L</icon>).
+Типово, виведені virt-inspector дані містять список програм, які встановлено у гостьовій системі, якщо такий список доступний (див. L</icon>).
Вкажіть цей параметр, щоб вимкнути частину XML результату.
=item B<--xpath> запит
-Виконати запит XPath до XML у stdin і вивести результат до stdout. У цьому
-режимі virt-inspector просто виконує запит XPath; усі інші функції
-інспектування буде вимкнено. Приклади запитів наведено у розділі L</ЗАПИТИ
-XPATH> нижче.
+Виконати запит XPath до XML у stdin і вивести результат до stdout. У цьому режимі virt-inspector просто виконує запит XPath; усі інші функції інспектування буде вимкнено. Приклади запитів наведено у розділі L</ЗАПИТИ XPATH> нижче.
=back
virt-inspector назва_гостьової_системи
-тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
=head1 ФОРМАТ XML
-Точний опис XML virt-inspector наведено у файлі схеми RELAX NG
-F<virt-inspector.rng>, який постачається разом із libguestfs. Цей розділ
-містить лише поверхневий огляд.
+Точний опис XML virt-inspector наведено у файлі схеми RELAX NG F<virt-inspector.rng>, який постачається разом із libguestfs. Цей розділ містить лише поверхневий огляд.
-Елементом верхнього рівня є E<lt>operatingsystemsE<gt>. Він містить один або
-декілька елементів E<lt>operatingsystemE<gt>. Елементів
-E<lt>operatingsystemE<gt> буде декілька, лише якщо у віртуальній машині
-передбачено декілька варіантів завантаження. Такі випадки є дуже рідкісними
-у світі віртуальних машин.
+Елементом верхнього рівня є E<lt>operatingsystemsE<gt>. Він містить один або декілька елементів E<lt>operatingsystemE<gt>. Елементів E<lt>operatingsystemE<gt> буде декілька, лише якщо у віртуальній машині передбачено декілька варіантів завантаження. Такі випадки є дуже рідкісними у світі віртуальних машин.
=head2 E<lt>operatingsystemE<gt>
-Всередині теґу E<lt>operatingsystemE<gt> містяться різноманітні
-необов'язкові поля, які описують операційну систему, її архітектуру, містять
-описовий рядок «назва продукту», тип операційної системи тощо. Ось приклад:
+Всередині теґу E<lt>operatingsystemE<gt> містяться різноманітні необов'язкові поля, які описують операційну систему, її архітектуру, містять описовий рядок «назва продукту», тип операційної системи тощо. Ось приклад:
<operatingsystems>
<operatingsystem>
<minor_version>1</minor_version>
<windows_systemroot>/Windows</windows_systemroot>
-Якщо коротко, E<lt>nameE<gt> — клас операційної системи (щось подібне до
-C<linux> або C<windows>), E<lt>distroE<gt> — дистрибутив (наприклад,
-C<fedora>, але передбачено розпізнавання багатьох інших дистрибутивів), а
-E<lt>archE<gt> — архітектура гостьової системи. Інші поля мають доволі
-зрозуміле призначення, але оскільки ці поля взято безпосередньо з
-програмного інтерфейсу інспектування libguestfs, їхній повний опис можна
-знайти у розділі L<guestfs(3)/ІНСПЕКТУВАННЯ>.
+Якщо коротко, E<lt>nameE<gt> — клас операційної системи (щось подібне до C<linux> або C<windows>), E<lt>distroE<gt> — дистрибутив (наприклад, C<fedora>, але передбачено розпізнавання багатьох інших дистрибутивів), а E<lt>archE<gt> — архітектура гостьової системи. Інші поля мають доволі зрозуміле призначення, але оскільки ці поля взято безпосередньо з програмного інтерфейсу інспектування libguestfs, їхній повний опис можна знайти у розділі L<guestfs(3)/ІНСПЕКТУВАННЯ>.
-Елемент E<lt>rootE<gt> є пристроєм кореневої файлової системи, але з точки
-зору libguestfs (блокові пристрої можуть мати зовсім інші назви у самій
-віртуальній машині).
+Елемент E<lt>rootE<gt> є пристроєм кореневої файлової системи, але з точки зору libguestfs (блокові пристрої можуть мати зовсім інші назви у самій віртуальній машині).
=head2 E<lt>mountpointsE<gt>
-У Un*x-подібних гостьових системах типово міститься декілька файлових
-систем, які монтуються як різні точки монтування. Ці файлові системи описано
-у елементі E<lt>mountpointsE<gt>, який виглядає ось так:
+У Un*x-подібних гостьових системах типово міститься декілька файлових систем, які монтуються як різні точки монтування. Ці файлові системи описано у елементі E<lt>mountpointsE<gt>, який виглядає ось так:
<operatingsystems>
<operatingsystem>
<mountpoint dev="/dev/sda1">/boot</mountpoint>
</mountpoints>
-Як і з E<lt>rootE<gt>, пристрої подано з точки зору libguestfs, отже вони
-можуть мати зовсім інші назви у гостьовій системі. У списку буде наведено
-лише монтовані файлові системи, а не щось подібне до пристроїв резервної
-пам'яті на диску.
+Як і з E<lt>rootE<gt>, пристрої подано з точки зору libguestfs, отже вони можуть мати зовсім інші назви у гостьовій системі. У списку буде наведено лише монтовані файлові системи, а не щось подібне до пристроїв резервної пам'яті на диску.
=head2 E<lt>filesystemsE<gt>
-Елемент E<lt>filesystemsE<gt> подібний до E<lt>mountpointsE<gt>, але
-стосується файлових I<усіх> файлових систем, що належать гостьовій
-операційній системі, зокрема розділів резервної пам'яті на диску та порожніх
-розділів. (У рідкісних випадках гостьової системи із варіантами
-завантаження, цей елемент стосується файлових систем, що належать цій
-операційній системі або є спільними для цієї операційної системи та інших
-операційних систем.)
+Елемент E<lt>filesystemsE<gt> подібний до E<lt>mountpointsE<gt>, але стосується файлових I<усіх> файлових систем, що належать гостьовій операційній системі, зокрема розділів резервної пам'яті на диску та порожніх розділів. (У рідкісних випадках гостьової системи із варіантами завантаження, цей елемент стосується файлових систем, що належать цій операційній системі або є спільними для цієї операційної системи та інших операційних систем.)
Ви побачите щось таке:
<uuid>e6a4db1e-15c2-477b-ac2a-699181c396aa</uuid>
</filesystem>
-Необов'язкові елементи у E<lt>filesystemE<gt> стосуються типу, мітки та UUID
-файлової системи.
+Необов'язкові елементи у E<lt>filesystemE<gt> стосуються типу, мітки та UUID файлової системи.
=head2 E<lt>applicationsE<gt>
-Пов'язані елементи E<lt>package_formatE<gt>, E<lt>package_managementE<gt> та
-E<lt>applicationsE<gt> описують програми, які встановлено у віртуальній
-машині.
+Пов'язані елементи E<lt>package_formatE<gt>, E<lt>package_managementE<gt> та E<lt>applicationsE<gt> описують програми, які встановлено у віртуальній машині.
-Елемент E<lt>package_formatE<gt>, якщо він є, описує використану систему
-пакунків. Типовими значеннями цього елемента є C<rpm> та C<deb>.
+Елемент E<lt>package_formatE<gt>, якщо він є, описує використану систему пакунків. Типовими значеннями цього елемента є C<rpm> та C<deb>.
-Елемент E<lt>package_managementE<gt>, якщо такий є, описує засіб для
-керування пакунками. Серед типових значень елемента є C<yum>, C<up2date> та
-C<apt>.
+Елемент E<lt>package_managementE<gt>, якщо такий є, описує засіб для керування пакунками. Серед типових значень елемента є C<yum>, C<up2date> та C<apt>.
E<lt>applicationsE<gt> містить список пакунків або встановлених програм.
<release>1</release>
</application>
-Для деяких типів гостьових системи дані полів версії і випуску можуть бути
-недоступними. Можлива поява інших полів,
-див. L<guestfs(3)/guestfs_inspect_list_applications>.
+Для деяких типів гостьових системи дані полів версії і випуску можуть бути недоступними. Можлива поява інших полів, див. L<guestfs(3)/guestfs_inspect_list_applications>.
=head2 E<lt>drive_mappingsE<gt>
-Для операційних систем, подібних до Windows, де для позначення дисків
-використовуються літери, virt-inspector може визначати прив'язки літер
-дисків до файлових систем.
+Для операційних систем, подібних до Windows, де для позначення дисків використовуються літери, virt-inspector може визначати прив'язки літер дисків до файлових систем.
<operatingsystems>
<operatingsystem>
<drive_mapping name="E">/dev/sdb1</drive_mapping>
</drive_mappings>
-У наведеному вище прикладі диск C пов'язано із файловою системою на другому
-розділі першого диска, диск E — із файловою системою на першому розділі
-другого диска.
+У наведеному вище прикладі диск C пов'язано із файловою системою на другому розділі першого диска, диск E — із файловою системою на першому розділі другого диска.
-Зауважте, що це стосується лише постійних прив'язок дисків, а не прив'язок,
-які подібні до прив'язок до спільних ресурсів у мережі. Крім того, до цього
-списку може бути не включено точки монтування томів NTFS.
+Зауважте, що це стосується лише постійних прив'язок дисків, а не прив'язок, які подібні до прив'язок до спільних ресурсів у мережі. Крім того, до цього списку може бути не включено точки монтування томів NTFS.
=head2 E<lt>iconE<gt>
-Іноді virt-inspector може видобути піктограму або логотип гостьової
-системи. Піктограму буде повернуто у форматі даних PNG у кодуванні
-base64. Зауважте, що піктограма може бути доволі великою і дуже якісною.
+Іноді virt-inspector може видобути піктограму або логотип гостьової системи. Піктограму буде повернуто у форматі даних PNG у кодуванні base64. Зауважте, що піктограма може бути доволі великою і дуже якісною.
<operatingsystems>
<operatingsystem>
[... багато рядків даних base64 ...]
</icon>
-Для показу піктограми вам слід видобути ї і перетворити дані у кодуванні
-base64 знову у двійковий файл. Скористайтеся запитом XPath або простим
-редактором для видобування даних, а потім програмою L<base64(1)> з coreutils
-для перетворення цих даних на файл PNG:
+Для показу піктограми вам слід видобути ї і перетворити дані у кодуванні base64 знову у двійковий файл. Скористайтеся запитом XPath або простим редактором для видобування даних, а потім програмою L<base64(1)> з coreutils для перетворення цих даних на файл PNG:
base64 -i -d < дані.піктограми > icon.png
=head1 ЗАПИТИ XPATH
-У virt-inspector передбачено вбудовану підтримку виконання запитів
-XPath. Причиною включення підтримкиXPath безпосередньо до virt-inspector є
-те, що не існує добрих і широкодоступних засобів командного рядка, які
-можуть виконувати запити XPath. Єдиним добрим засобом є L<xmlstarlet(1)>,
-але ця програма недоступна у Red Hat Enterprise Linux.
+У virt-inspector передбачено вбудовану підтримку виконання запитів XPath. Причиною включення підтримкиXPath безпосередньо до virt-inspector є те, що не існує добрих і широкодоступних засобів командного рядка, які можуть виконувати запити XPath. Єдиним добрим засобом є L<xmlstarlet(1)>, але ця програма недоступна у Red Hat Enterprise Linux.
-Для виконання запиту XPath скористайтеся параметром I<--xpath>. Зауважте, що
-у цьому режимі virt-inspector просто читає XML зі stdin і виводить результат
-запиту до stdout. Усі інші можливості інспектування у цьому режимі вимкнено.
+Для виконання запиту XPath скористайтеся параметром I<--xpath>. Зауважте, що у цьому режимі virt-inspector просто читає XML зі stdin і виводить результат запиту до stdout. Усі інші можливості інспектування у цьому режимі вимкнено.
Приклад:
=head1 ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ЗА ДОПОМОГОЮ ПРОГРАМНОГО ІНТЕРФЕЙСУ LIBGUESTFS
-У ранніх версіях libguestfs virt-inspector був великим скриптом Perl, до
-якого було включено багато евристики для інспектування гостьових систем. Цей
-підхід мав декілька проблем: для виконання інспектування з інших
-інструментів (зокрема guestfish) нам доводилося викликати цей скрипт Perl;
-він ставив у пріоритетне становище Perl над іншими мовами програмування,
-підтримку яких передбачено у libguestfs.
+У ранніх версіях libguestfs virt-inspector був великим скриптом Perl, до якого було включено багато евристики для інспектування гостьових систем. Цей підхід мав декілька проблем: для виконання інспектування з інших інструментів (зокрема guestfish) нам доводилося викликати цей скрипт Perl; він ставив у пріоритетне становище Perl над іншими мовами програмування, підтримку яких передбачено у libguestfs.
-До libguestfs 1.8 ми переписали код Perl на C і включили його до програмного
-інтерфейсу основи libguestfs (L<guestfs(3)>). Тепер virt-inspector є простим
-тонким прошарком C над основним програмним інтерфейсом мовою C. Усі дані
-інспектування доступні з усіх мов програмування, підтримку яких передбачено
-у libguestfs, і з guestfish.
+До libguestfs 1.8 ми переписали код Perl на C і включили його до програмного інтерфейсу основи libguestfs (L<guestfs(3)>). Тепер virt-inspector є простим тонким прошарком C над основним програмним інтерфейсом мовою C. Усі дані інспектування доступні з усіх мов програмування, підтримку яких передбачено у libguestfs, і з guestfish.
-Опис програмного інтерфейсу інспектування мовою C наведено у розділі
-L<guestfs(3)/ІНСПЕКТУВАННЯ>.
+Опис програмного інтерфейсу інспектування мовою C наведено у розділі L<guestfs(3)/ІНСПЕКТУВАННЯ>.
-Приклад коду, де використовується програмний інтерфейс інспектування мовою
-C, наведено у файлі F<inspect-vm.c>, який постачається разом із libguestfs.
+Приклад коду, де використовується програмний інтерфейс інспектування мовою C, наведено у файлі F<inspect-vm.c>, який постачається разом із libguestfs.
-Крім того, F<inspect-vm.c> трансльовано іншими мовами
-програмування. Наприклад, F<inspect_vm.pl> є трансляцією на Perl. Також
-передбачено інші трансляції на OCaml, Python
-тощо. Див. L<guestfs(3)/ВИКОРИСТАННЯ LIBGUESTFS ЗА ДОПОМОГОЮ ІНШИХ МОВ
-ПРОГРАМУВАННЯ>, де наведено список сторінок підручника, де містяться
-приклади коду.
+Крім того, F<inspect-vm.c> трансльовано іншими мовами програмування. Наприклад, F<inspect_vm.pl> є трансляцією на Perl. Також передбачено інші трансляції на OCaml, Python тощо. Див. L<guestfs(3)/ВИКОРИСТАННЯ LIBGUESTFS ЗА ДОПОМОГОЮ ІНШИХ МОВ ПРОГРАМУВАННЯ>, де наведено список сторінок підручника, де містяться приклади коду.
=head2 ОТРИМАННЯ ДАНИХ ІНСПЕКТУВАННЯ ВІД GUESTFISH
-Якщо ви використовуєте параметр guestfish I<-i>, викликається основний
-програмний інтерфейс інспектування L<guestfs(3)/guestfs_inspect_os> мовою
-C. Це еквівалент команди guestfish C<inspect-os>. Ви також можете викликати
-цю команду guestfish вручну.
+Якщо ви використовуєте параметр guestfish I<-i>, викликається основний програмний інтерфейс інспектування L<guestfs(3)/guestfs_inspect_os> мовою C. Це еквівалент команди guestfish C<inspect-os>. Ви також можете викликати цю команду guestfish вручну.
-C<inspect-os> виконує інспектування поточного образу диска, повертаючи
-список знайдених операційних систем. Кожну операційну систему представлено
-її пристроєм кореневої файлової системи. У більшості випадків ця команда не
-виводить ніяких даних (не знайдено жодної операційної системи) або виводить
-єдиний кореневий пристрій, але ви маєте зважати на те, що ця команда може
-вивести декілька рядків, якщо у образі декілька операційних систем або із
-гостьовою системою з'єднано компакт-диск для встановлення.
+C<inspect-os> виконує інспектування поточного образу диска, повертаючи список знайдених операційних систем. Кожну операційну систему представлено її пристроєм кореневої файлової системи. У більшості випадків ця команда не виводить ніяких даних (не знайдено жодної операційної системи) або виводить єдиний кореневий пристрій, але ви маєте зважати на те, що ця команда може вивести декілька рядків, якщо у образі декілька операційних систем або із гостьовою системою з'єднано компакт-диск для встановлення.
$ guestfish --ro -a F15x32.img
><fs> run
><fs> inspect-os
/dev/vg_f15x32/lv_root
-За допомогою кореневого пристрою ви можете отримати подальшу інформацію щодо
-гостьової системи:
+За допомогою кореневого пристрою ви можете отримати подальшу інформацію щодо гостьової системи:
><fs> inspect-get-type /dev/vg_f15x32/lv_root
linux
><fs> inspect-get-product-name /dev/vg_f15x32/lv_root
Fedora release 15 (Lovelock)
-Обмеження guestfish ускладнюють прив'язку кореневого пристрою до змінної
-(оскільки у guestfish немає змінних), отже, якщо вам потрібно робити це
-декілька разів, варто написати скрипт якоюсь іншою мовою програмування,
-підтримку якої передбачено програмним інтерфейсом libguestfs.
+Обмеження guestfish ускладнюють прив'язку кореневого пристрою до змінної (оскільки у guestfish немає змінних), отже, якщо вам потрібно робити це декілька разів, варто написати скрипт якоюсь іншою мовою програмування, підтримку якої передбачено програмним інтерфейсом libguestfs.
Для отримання списку програм вам спочатку слід змонтувати диски:
app_description:
}
-Зауважте, що для показу піктограми гостьової системи файлові системи має
-бути змонтовано у означений вище спосіб. Далі, ви можете зробити так:
+Зауважте, що для показу піктограми гостьової системи файлові системи має бути змонтовано у означений вище спосіб. Далі, ви можете зробити так:
><fs> inspect-get-icon /dev/vg_f15x32/lv_root | display -
=head1 ПОПЕРЕДНІ ВЕРСІЇ VIRT-INSPECTOR
-Як ми вже вказували вище, ранні версії libguestfs постачалися із іншою
-програмою virt-inspector, написаною на Perl (поточну версію написано на
-C). Виведені дані XML virt-inspector на Perl були іншими, програма також
-могла виводити дані у інших форматах, зокрема текстовому.
+Як ми вже вказували вище, ранні версії libguestfs постачалися із іншою програмою virt-inspector, написаною на Perl (поточну версію написано на C). Виведені дані XML virt-inspector на Perl були іншими, програма також могла виводити дані у інших форматах, зокрема текстовому.
-Підтримку застарілої версії virt-inspector припинено, вона більше не
-постачається з libguestfs.
+Підтримку застарілої версії virt-inspector припинено, вона більше не постачається з libguestfs.
-Крім того, до непорозумінь може призвести і те, що разом із Red Hat
-Enterprise Linux 6 ми постачаємо дві версії virt-inspector із різними
-назвами:
+Крім того, до непорозумінь може призвести і те, що разом із Red Hat Enterprise Linux 6 ми постачаємо дві версії virt-inspector із різними назвами:
virt-inspector Стара версія на Perl.
virt-inspector2 Нова версія на C.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<http://www.w3.org/TR/xpath/>,
-L<base64(1)>, L<xmlstarlet(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<http://www.w3.org/TR/xpath/>, L<base64(1)>, L<xmlstarlet(1)>, L<http://libguestfs.org/>.
=head1 АВТОРИ
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-log 1"
-.TH virt-log 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-log 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-log\*(C'\fR — інструмент командного рядка для показу файлів журналів з
-вказаної віртуальної машини (або образу диска).
+\&\f(CW\*(C`virt\-log\*(C'\fR — інструмент командного рядка для показу файлів журналів з вказаної віртуальної машини (або образу диска).
.PP
-Ця програма може працювати як зі звичайними текстовими файлами журналу
-(наприклад \fI/var/log/messages\fR), такі із файлами журналів у двійкових
-форматах, зокрема журналом systemd.
+Ця програма може працювати як зі звичайними текстовими файлами журналу (наприклад \fI/var/log/messages\fR), такі із файлами журналів у двійкових форматах, зокрема журналом systemd.
.PP
-Для виведення вмісту файлів інших типів скористайтеся \fBvirt\-cat\fR\|(1). Для
-стеження (tail) за текстовими файлами журналу, скористайтеся
-\&\fBvirt\-tail\fR\|(1). Щоб скопіювати файли з віртуальної машини, скористайтеся
-\&\fBvirt\-copy\-out\fR\|(1). Щоб вивести вміст реєстру Windows, скористайтеся
-\&\fBvirt\-win\-reg\fR\|(1).
+Для виведення вмісту файлів інших типів скористайтеся \fBvirt\-cat\fR\|(1). Для стеження (tail) за текстовими файлами журналу, скористайтеся \fBvirt\-tail\fR\|(1). Щоб скопіювати файли з віртуальної машини, скористайтеся \fBvirt\-copy\-out\fR\|(1). Щоб вивести вміст реєстру Windows, скористайтеся \fBvirt\-win\-reg\fR\|(1).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
Показ журналу з гостьової системи повністю:
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a адреса\fR" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-log попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-log попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-log \-\-format=raw \-a диск.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-log \-\-format=raw \-a диск.img \-\-format \-a інший.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), \fBvirt\-win\-reg\fR\|(1),
-http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-tail\fR\|(1), \fBvirt\-tar\-out\fR\|(1), \fBvirt\-win\-reg\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-C<virt-log> — інструмент командного рядка для показу файлів журналів з
-вказаної віртуальної машини (або образу диска).
+C<virt-log> — інструмент командного рядка для показу файлів журналів з вказаної віртуальної машини (або образу диска).
-Ця програма може працювати як зі звичайними текстовими файлами журналу
-(наприклад F</var/log/messages>), такі із файлами журналів у двійкових
-форматах, зокрема журналом systemd.
+Ця програма може працювати як зі звичайними текстовими файлами журналу (наприклад F</var/log/messages>), такі із файлами журналів у двійкових форматах, зокрема журналом systemd.
-Для виведення вмісту файлів інших типів скористайтеся L<virt-cat(1)>. Для
-стеження (tail) за текстовими файлами журналу, скористайтеся
-L<virt-tail(1)>. Щоб скопіювати файли з віртуальної машини, скористайтеся
-L<virt-copy-out(1)>. Щоб вивести вміст реєстру Windows, скористайтеся
-L<virt-win-reg(1)>.
+Для виведення вмісту файлів інших типів скористайтеся L<virt-cat(1)>. Для стеження (tail) за текстовими файлами журналу, скористайтеся L<virt-tail(1)>. Щоб скопіювати файли з віртуальної машини, скористайтеся L<virt-copy-out(1)>. Щоб вивести вміст реєстру Windows, скористайтеся L<virt-win-reg(1)>.
=head1 ПРИКЛАДИ
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-log попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-log попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-log --format=raw -a диск.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-log --format=raw -a диск.img --format -a інший.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-tail(1)>, L<virt-tar-out(1)>, L<virt-win-reg(1)>,
-L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-tail(1)>, L<virt-tar-out(1)>, L<virt-win-reg(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-ls 1"
-.TH virt-ls 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-ls 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-\&\f(CW\*(C`virt\-ls\*(C'\fR виводить списки назв файлів, розмірів файлів, контрольних сум,
-розширених атрибутів та інші дані з віртуальної машини або образу диска.
+\&\f(CW\*(C`virt\-ls\*(C'\fR виводить списки назв файлів, розмірів файлів, контрольних сум, розширених атрибутів та інші дані з віртуальної машини або образу диска.
.PP
-Можна вказати декілька назв каталогів. У цьому випадку виведені дані для
-кожного з них буде об'єднано.
+Можна вказати декілька назв каталогів. У цьому випадку виведені дані для кожного з них буде об'єднано.
.PP
-Щоб отримати список вмісту каталогів з гостьової системи libvirt,
-скористайтеся параметром \fI\-d\fR для задання назви гостьової системи. Для
-роботи з образом диска скористайтеся параметром \fI\-a\fR.
+Щоб отримати список вмісту каталогів з гостьової системи libvirt, скористайтеся параметром \fI\-d\fR для задання назви гостьової системи. Для роботи з образом диска скористайтеся параметром \fI\-a\fR.
.PP
-\&\f(CW\*(C`virt\-ls\*(C'\fR може створювати багато простих списків файлів. Складніші списки
-можна створити за допомогою \fBguestfish\fR\|(1) або програми, яка безпосередньо
-використовує програмний інтерфейс \fBguestfs\fR\|(3).
+\&\f(CW\*(C`virt\-ls\*(C'\fR може створювати багато простих списків файлів. Складніші списки можна створити за допомогою \fBguestfish\fR\|(1) або програми, яка безпосередньо використовує програмний інтерфейс \fBguestfs\fR\|(3).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
Отримати список всіх файлів і каталогів у віртуальній машині:
\& virt\-ls \-lR \-d guest / | grep \*(Aq^\- [42]\*(Aq
.Ve
.PP
-Показати список всіх каталогів з відкритим для всіх доступом на запис у
-віртуальній машині Linux:
+Показати список всіх каталогів з відкритим для всіх доступом на запис у віртуальній машині Linux:
.PP
.Vb 1
\& virt\-ls \-lR \-d guest / | grep \*(Aq^d ...7\*(Aq
\& virt\-ls \-lR \-d guest / | grep \-i \*(Aq^\-.*\e.png$\*(Aq
.Ve
.PP
-Щоб переглянути список файлів у домашніх каталогах, розмір яких перевищує 10
-МБ:
+Щоб переглянути список файлів у домашніх каталогах, розмір яких перевищує 10 МБ:
.PP
.Vb 1
\& virt\-ls \-lR \-d guest /home | awk \*(Aq$3 > 10*1024*1024\*(Aq
\& virt\-ls \-lR \-d guest \-\-time\-days / | awk \*(Aq$6 <= 7\*(Aq
.Ve
.PP
-Знайти звичайні файли, зміни до яких було внесено протягом попередніх 24
-годин:
+Знайти звичайні файли, зміни до яких було внесено протягом попередніх 24 годин:
.PP
.Vb 1
\& virt\-ls \-lR \-d guest \-\-time\-days / | grep \*(Aq^\-\*(Aq | awk \*(Aq$6 < 1\*(Aq
.Ve
.SS "ВІДМІННОСТІ МІЖ ЗНІМКАМИ ТА ФАЙЛАМИ РЕЗЕРВНИХ КОПІЙ"
.IX Subsection "ВІДМІННОСТІ МІЖ ЗНІМКАМИ ТА ФАЙЛАМИ РЕЗЕРВНИХ КОПІЙ"
-Хоча virt-ls можна скористатися для пошуку відмінностей між каталогами, з
-випуску libguestfs ≥ 1.26 з цією метою краще користуватися новим
-інструментом, \fBvirt\-diff\fR\|(1).
+Хоча virt-ls можна скористатися для пошуку відмінностей між каталогами, з випуску libguestfs ≥ 1.26 з цією метою краще користуватися новим інструментом, \fBvirt\-diff\fR\|(1).
.SH "РЕЖИМИ ВИВЕДЕННЯ ДАНИХ"
.IX Header "РЕЖИМИ ВИВЕДЕННЯ ДАНИХ"
-У \f(CW\*(C`virt\-ls\*(C'\fR передбачено чотири режими виведення даних, керування якими
-здійснюється різними комбінаціями параметрів \fI\-l\fR та \fI\-R\fR.
+У \f(CW\*(C`virt\-ls\*(C'\fR передбачено чотири режими виведення даних, керування якими здійснюється різними комбінаціями параметрів \fI\-l\fR та \fI\-R\fR.
.SS "ПРОСТИЙ СПИСОК"
.IX Subsection "ПРОСТИЙ СПИСОК"
Простий список, подібний до списку звичайної команди \fBls\fR\|(1):
.Ve
.SS "ДОВГИЙ СПИСОК"
.IX Subsection "ДОВГИЙ СПИСОК"
-З параметром \fI\-l\fR (\fI\-\-long\fR) виведені дані будуть подібними до даних, які
-виводить команда \f(CW\*(C`ls \-l\*(C'\fR (якщо точніше, функція \f(CW\*(C`guestfs_ll\*(C'\fR).
+З параметром \fI\-l\fR (\fI\-\-long\fR) виведені дані будуть подібними до даних, які виводить команда \f(CW\*(C`ls \-l\*(C'\fR (якщо точніше, функція \f(CW\*(C`guestfs_ll\*(C'\fR).
.PP
.Vb 5
\& $ virt\-ls \-l \-d guest /
\& [тощо]
.Ve
.PP
-Зауважте, що хоча такий список зручний для перегляду вмісту каталогу, не
-варто обробляти його за допомогою іншої програми. Для обробки іншими
-програмами слід скористатися варіантом \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R".
+Зауважте, що хоча такий список зручний для перегляду вмісту каталогу, не варто обробляти його за допомогою іншої програми. Для обробки іншими програмами слід скористатися варіантом \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R".
.SS "РЕКУРСИВНИЙ СПИСОК"
.IX Subsection "РЕКУРСИВНИЙ СПИСОК"
-Із параметром \fI\-R\fR (\fI\-\-recursive\fR) \f(CW\*(C`virt\-ls\*(C'\fR виводить список назв файлів
-і каталогів рекурсивно:
+Із параметром \fI\-R\fR (\fI\-\-recursive\fR) \f(CW\*(C`virt\-ls\*(C'\fR виводить список назв файлів і каталогів рекурсивно:
.PP
.Vb 4
\& $ virt\-ls \-R \-d guest /tmp
\& [тощо]
.Ve
.PP
-Для створення такого списку \f(CW\*(C`virt\-ls\*(C'\fR викликає функцію \f(CW\*(C`guestfs_find0\*(C'\fR і
-перетворює символи \f(CW\*(C`\e0\*(C'\fR на \f(CW\*(C`\en\*(C'\fR.
+Для створення такого списку \f(CW\*(C`virt\-ls\*(C'\fR викликає функцію \f(CW\*(C`guestfs_find0\*(C'\fR і перетворює символи \f(CW\*(C`\e0\*(C'\fR на \f(CW\*(C`\en\*(C'\fR.
.SS "РЕКУРСИВНИЙ ДОВГИЙ СПИСОК"
.IX Subsection "РЕКУРСИВНИЙ ДОВГИЙ СПИСОК"
-Використання параметрів \fI\-lR\fR разом змінює виведені дані так, що вміст
-каталогів показується рекурсивно, із даними щодо файлів, а також, якщо
-використано відповідні параметри, іншими даними, зокрема контрольними сумами
-та розширеними атрибутами.
-.PP
-Доступ до більшості цікавих можливостей \f(CW\*(C`virt\-ls\*(C'\fR можна отримати лише у
-режимі \fI\-lR\fR.
-.PP
-Зазвичай, поля відокремлюються пробілами. До назв файлів \fBне додаються\fR
-лапки. Отже, ви не зможете скористатися виведеними даними у іншій програмі
-(оскільки у назвах файлів можуть міститися пробіли та інші нестандартні
-символи). Якщо до гостьової системи мають доступ сторонні люди і відомо, що
-ви використовуєте \f(CW\*(C`virt\-ls\*(C'\fR для аналізу вмісту гостьової системи,
-зловмисники можуть створити файли зі спеціально сконструйованими назвами та
-вбудованими до назв символами розриву рядка. Щоб виведені дані можна було
-\&\fBбезпечно\fR обробити у сторонній програмі, скористайтеся параметром \fI\-\-csv\fR
-для виведення даних у форматі значень, відокремлених комами.
-.PP
-Зауважте, що цей формат виведення є повністю незалежним від формату команди
-\&\f(CW\*(C`ls \-lR\*(C'\fR.
+Використання параметрів \fI\-lR\fR разом змінює виведені дані так, що вміст каталогів показується рекурсивно, із даними щодо файлів, а також, якщо використано відповідні параметри, іншими даними, зокрема контрольними сумами та розширеними атрибутами.
+.PP
+Доступ до більшості цікавих можливостей \f(CW\*(C`virt\-ls\*(C'\fR можна отримати лише у режимі \fI\-lR\fR.
+.PP
+Зазвичай, поля відокремлюються пробілами. До назв файлів \fBне додаються\fR лапки. Отже, ви не зможете скористатися виведеними даними у іншій програмі (оскільки у назвах файлів можуть міститися пробіли та інші нестандартні символи). Якщо до гостьової системи мають доступ сторонні люди і відомо, що ви використовуєте \f(CW\*(C`virt\-ls\*(C'\fR для аналізу вмісту гостьової системи, зловмисники можуть створити файли зі спеціально сконструйованими назвами та вбудованими до назв символами розриву рядка. Щоб виведені дані можна було \fBбезпечно\fR обробити у сторонній програмі, скористайтеся параметром \fI\-\-csv\fR для виведення даних у форматі значень, відокремлених комами.
+.PP
+Зауважте, що цей формат виведення є повністю незалежним від формату команди \f(CW\*(C`ls \-lR\*(C'\fR.
.PP
.Vb 8
\& $ virt\-ls \-lR \-d guest /bin
Ці основні поля буде показано завжди:
.IP "тип" 4
.IX Item "тип"
-Тип файла, одне з таких значень: \f(CW\*(C`\-\*(C'\fR (звичайний файл), \f(CW\*(C`d\*(C'\fR (каталог), \f(CW\*(C`c\*(C'\fR
-(символьний пристрій), \f(CW\*(C`b\*(C'\fR (блоковий пристрій), \f(CW\*(C`p\*(C'\fR (іменований канал),
-\&\f(CW\*(C`l\*(C'\fR (символічне посилання), \f(CW\*(C`s\*(C'\fR (сокет) або \f(CW\*(C`u\*(C'\fR (невідомо).
+Тип файла, одне з таких значень: \f(CW\*(C`\-\*(C'\fR (звичайний файл), \f(CW\*(C`d\*(C'\fR (каталог), \f(CW\*(C`c\*(C'\fR (символьний пристрій), \f(CW\*(C`b\*(C'\fR (блоковий пристрій), \f(CW\*(C`p\*(C'\fR (іменований канал), \f(CW\*(C`l\*(C'\fR (символічне посилання), \f(CW\*(C`s\*(C'\fR (сокет) або \f(CW\*(C`u\*(C'\fR (невідомо).
.IP "права доступу" 4
.IX Item "права доступу"
Права доступу Unix, показані у форматі вісімкового числа із 4 цифр.
.IP "розмір" 4
.IX Item "розмір"
-Розмір файла. Його буде показано у байтах, якщо не використано параметр
-\&\fI\-h\fR або \fI\-\-human\-readable\fR. Якщо такий параметр використано, дані буде
-показано у зручному для читанні вигляді.
+Розмір файла. Його буде показано у байтах, якщо не використано параметр \fI\-h\fR або \fI\-\-human\-readable\fR. Якщо такий параметр використано, дані буде показано у зручному для читанні вигляді.
.IP "шлях" 4
.IX Item "шлях"
Шлях до файла або каталогу повністю.
.IX Item "посилання"
Лише для символічних посилань, призначення посилання.
.PP
-У режимі \fI\-lR\fR додаткові параметри командного рядка уможливлюють показ
-додаткових полів.
+У режимі \fI\-lR\fR додаткові параметри командного рядка уможливлюють показ додаткових полів.
.PP
З прапорцем \fI\-\-uids\fR ці додаткові поля буде показано до шляху:
.IP "uid" 4
.IP "gid" 4
.IX Item "gid"
.PD
-\&\s-1UID\s0 та \s-1GID\s0 власника файла (буде показано у числовій формі). Зауважте, що ці
-дані мають сенс лише у контексті Unix\-подібної гостьової системи.
+\&\s-1UID\s0 та \s-1GID\s0 власника файла (буде показано у числовій формі). Зауважте, що ці дані мають сенс лише у контексті Unix\-подібної гостьової системи.
.PP
Із прапорцем \fI\-\-times\fR буде показано такі додаткові поля:
.IP "atime" 4
.IX Item "ctime"
Час останньої зміни стану.
.PP
-Вміст полів дат і часу буде показано у форматі рядків, якщо не вказано
-одного з таких параметрів: \fI\-\-time\-t\fR, \fI\-\-time\-relative\fR або
-\&\fI\-\-time\-days\fR.
+Вміст полів дат і часу буде показано у форматі рядків, якщо не вказано одного з таких параметрів: \fI\-\-time\-t\fR, \fI\-\-time\-relative\fR або \fI\-\-time\-days\fR.
.PP
Із прапорцем \fI\-\-extra\-stats\fR буде показано такі додаткові поля:
.IP "пристрій" 4
.IX Item "пристрій"
-Пристрій на якому міститься файл (буде показано у форматі
-основний:підлеглий). Запис пристрою може не збігатися із записом пристрою,
-який відомий гостьовій системі.
+Пристрій на якому міститься файл (буде показано у форматі основний:підлеглий). Запис пристрою може не збігатися із записом пристрою, який відомий гостьовій системі.
.IP "inode" 4
.IX Item "inode"
Номер inode.
Кількість жорстких посилань.
.IP "rdev" 4
.IX Item "rdev"
-Для блоковий і символьних спеціальних файлів пристрій (буде показано у
-форматі основний:підлеглий).
+Для блоковий і символьних спеціальних файлів пристрій (буде показано у форматі основний:підлеглий).
.IP "блоки" 4
.IX Item "блоки"
Кількість 512\-байтових блоків, виділених під файл.
.PP
-Якщо використано прапорець \fI\-\-checksum\fR, програма покаже контрольну суму
-вмісту файла (лише для звичайних файлів). Обчислення контрольної суми може
-бути доволі тривалою дією.
+Якщо використано прапорець \fI\-\-checksum\fR, програма покаже контрольну суму вмісту файла (лише для звичайних файлів). Обчислення контрольної суми може бути доволі тривалою дією.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-add\fR файл" 4
.IX Item "--add файл"
.PD
-Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра \fI\-a\fR.
+Додати \fIфайл\fR, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра \fI\-a\fR.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-\&\fI\-\-format=..\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format=..\fR.
.IP "\fB\-a адреса\fR" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-checksum=crc|md5|sha1|sha224|sha256|sha384|sha512\fR" 4
.IX Item "--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512"
.PD
-Вивести контрольну суму вмісту звичайного файла. Без аргументу для створення
-контрольної суми буде використано \fImd5\fR. За допомогою аргументу ви можете
-визначити потрібний вам тип контрольної суми.
+Вивести контрольну суму вмісту звичайного файла. Без аргументу для створення контрольної суми буде використано \fImd5\fR. За допомогою аргументу ви можете визначити потрібний вам тип контрольної суми.
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-c\fR адреса" 4
.IX Item "-c адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-\-csv\fR" 4
.IX Item "--csv"
-Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0,
-наведеним нижче.
+Вивести результати до формату \s-1CSV\s0 (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом \*(L"НОТАТКА ЩОДО ФОРМАТУ \s-1CSV\*(R"\s0, наведеним нижче.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-ls попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-ls попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-extra\-stats\fR" 4
.IX Item "--extra-stats"
Показати додаткові дані.
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-format=raw|qcow2|..\fR" 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR" 4
.IX Item "--format"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format\fR без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-ls \-\-format=raw \-a диск.img /каталог
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-ls \-\-format=raw \-a диск.img \-\-format \-a інший_диск.img /каталог
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-h\fR" 4
.IX Item "-h"
.PD 0
.PD
Показати розміри файлів у зручному для читання форматі.
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.Sp
Якщо точку монтування не вказано, типовим значенням є \fI/\fR.
.Sp
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
.Sp
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-\&\*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися
-програмою \fBvirt\-filesystems\fR\|(1).
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди \*(L"list-partitions\*(R", \*(L"list-filesystems\*(R" і \*(L"lvs\*(R"), або скористатися програмою \fBvirt\-filesystems\fR\|(1).
.Sp
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант
-використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або \f(CW\*(C`ro\*(C'\fR (другий варіант використовується, якщо використано прапорець \fI\-\-ro\fR). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (\s-1ACL\s0) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Ve
.Sp
-Використання цього прапорця є еквівалентним до використання команди
-\&\f(CW\*(C`mount\-options\*(C'\fR.
+Використання цього прапорця є еквівалентним до використання команди \f(CW\*(C`mount\-options\*(C'\fR.
.Sp
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR
-і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема \f(CW\*(C`ext3\*(C'\fR або \f(CW\*(C`ntfs\*(C'\fR. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: \f(CW\*(C`ext2\*(C'\fR і \f(CW\*(C`ext3\*(C'\fR), або libguestfs визначає файлову систему помилково.
.IP "\fB\-l\fR" 4
.IX Item "-l"
.PD 0
.IP "\fB\-\-recursive\fR" 4
.IX Item "--recursive"
.PD
-Вибір режиму. Якщо не буде вказано жодного з варіантів, \f(CW\*(C`virt\-ls\*(C'\fR створює
-простий плоский список файлів у вказаному каталозі. Див. \*(L"ПРОСТИЙ СПИСОК\*(R".
+Вибір режиму. Якщо не буде вказано жодного з варіантів, \f(CW\*(C`virt\-ls\*(C'\fR створює простий плоский список файлів у вказаному каталозі. Див. \*(L"ПРОСТИЙ СПИСОК\*(R".
.Sp
-\&\f(CW\*(C`virt\-ls \-l\*(C'\fR створює «довгий список», у якому більше
-подробиць. Див. \*(L"ДОВГИЙ СПИСОК\*(R".
+\&\f(CW\*(C`virt\-ls \-l\*(C'\fR створює «довгий список», у якому більше подробиць. Див. \*(L"ДОВГИЙ СПИСОК\*(R".
.Sp
-\&\f(CW\*(C`virt\-ls \-R\*(C'\fR створює рекурсивний список файлів, починаючи з вказаного
-каталогу. Див. \*(L"РЕКУРСИВНИЙ СПИСОК\*(R".
+\&\f(CW\*(C`virt\-ls \-R\*(C'\fR створює рекурсивний список файлів, починаючи з вказаного каталогу. Див. \*(L"РЕКУРСИВНИЙ СПИСОК\*(R".
.Sp
-\&\f(CW\*(C`virt\-ls \-lR\*(C'\fR створює рекурсивні довгі списки, які простіше
-обробляти. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R".
+\&\f(CW\*(C`virt\-ls \-lR\*(C'\fR створює рекурсивні довгі списки, які простіше обробляти. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R".
.IP "\fB\-\-times\fR" 4
.IX Item "--times"
Показати поля часу.
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-time\-days\fR" 4
.IX Item "--time-days"
-Показувати поля часу у форматі днів до поточного (від’ємні значення для днів
-у майбутньому).
+Показувати поля часу у форматі днів до поточного (від’ємні значення для днів у майбутньому).
.Sp
-Зауважте, що \f(CW0\fR у виведених даних означає «менше 1 одного дня до поточного
-моменту» або «вік файла — від 0 до 86399 секунд».
+Зауважте, що \f(CW0\fR у виведених даних означає «менше 1 одного дня до поточного моменту» або «вік файла — від 0 до 86399 секунд».
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-time\-relative\fR" 4
.IX Item "--time-relative"
-Показувати поля часу у форматі секунд до поточного моменту (від’ємні
-значення для часу у майбутньому).
+Показувати поля часу у форматі секунд до поточного моменту (від’ємні значення для часу у майбутньому).
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-time\-t\fR" 4
.IX Item "--time-t"
Показувати поля часу у форматі секунд з моменту початку епохи \s-1UNIX.\s0
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-\-uids\fR" 4
.IX Item "--uids"
Показати поля \s-1UID\s0 і \s-1GID.\s0
.Sp
-Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК\*(R" вище.
+Цей параметр працюватиме лише у режимі виведення \fI\-lR\fR. Див. \*(L"РЕКУРСИВНИЙ ДОВГИЙ СПИСОК\*(R" вище.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
\& virt\-ls назва_гостьової_системи /каталог
.Ve
.PP
-тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися \fI\-a\fR або \fI\-d\fR, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
.PP
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
.SH "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
.IX Header "ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV"
-Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може
-\&\fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (\s-1CSV\s0), є оманливо простим. Може \fIздатися\fR, що його просто обробляти, але насправді це зовсім не так.
.PP
-Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами \fIне\fR працює у надійний спосіб. Ось приклад із двома стовпчиками:
.PP
.Vb 1
\& "foo,bar",baz
.Ve
.PP
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками \fIне\fR працює у надійний спосіб. Ось приклад із одним рядком:
.PP
.Vb 2
\& "foo
\& bar",baz
.Ve
.PP
-Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR
-(https://github.com/Chris00/ocaml\-csv також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся \f(CW\*(C`csvtool\*(C'\fR (https://github.com/Chris00/ocaml\-csv також є серед пакунків основних дистрибутивів Linux).
.PP
-Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0
-(наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних \s-1CSV\s0 (наприклад, \f(CW\*(C`Text::CSV\*(C'\fR для Perl або вбудовану бібліотеку csv Python).
.PP
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних \s-1CSV.\s0
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних \s-1CSV.\s0
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1),
-\&\fBvirt\-diff\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-copy\-out\fR\|(1), \fBvirt\-diff\fR\|(1), \fBvirt\-tar\-out\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-C<virt-ls> виводить списки назв файлів, розмірів файлів, контрольних сум,
-розширених атрибутів та інші дані з віртуальної машини або образу диска.
+C<virt-ls> виводить списки назв файлів, розмірів файлів, контрольних сум, розширених атрибутів та інші дані з віртуальної машини або образу диска.
-Можна вказати декілька назв каталогів. У цьому випадку виведені дані для
-кожного з них буде об'єднано.
+Можна вказати декілька назв каталогів. У цьому випадку виведені дані для кожного з них буде об'єднано.
-Щоб отримати список вмісту каталогів з гостьової системи libvirt,
-скористайтеся параметром I<-d> для задання назви гостьової системи. Для
-роботи з образом диска скористайтеся параметром I<-a>.
+Щоб отримати список вмісту каталогів з гостьової системи libvirt, скористайтеся параметром I<-d> для задання назви гостьової системи. Для роботи з образом диска скористайтеся параметром I<-a>.
-C<virt-ls> може створювати багато простих списків файлів. Складніші списки
-можна створити за допомогою L<guestfish(1)> або програми, яка безпосередньо
-використовує програмний інтерфейс L<guestfs(3)>.
+C<virt-ls> може створювати багато простих списків файлів. Складніші списки можна створити за допомогою L<guestfish(1)> або програми, яка безпосередньо використовує програмний інтерфейс L<guestfs(3)>.
=head1 ПРИКЛАДИ
virt-ls -lR -d guest / | grep '^- [42]'
-Показати список всіх каталогів з відкритим для всіх доступом на запис у
-віртуальній машині Linux:
+Показати список всіх каталогів з відкритим для всіх доступом на запис у віртуальній машині Linux:
virt-ls -lR -d guest / | grep '^d ...7'
virt-ls -lR -d guest / | grep -i '^-.*\.png$'
-Щоб переглянути список файлів у домашніх каталогах, розмір яких перевищує 10
-МБ:
+Щоб переглянути список файлів у домашніх каталогах, розмір яких перевищує 10 МБ:
virt-ls -lR -d guest /home | awk '$3 > 10*1024*1024'
virt-ls -lR -d guest --time-days / | awk '$6 <= 7'
-Знайти звичайні файли, зміни до яких було внесено протягом попередніх 24
-годин:
+Знайти звичайні файли, зміни до яких було внесено протягом попередніх 24 годин:
virt-ls -lR -d guest --time-days / | grep '^-' | awk '$6 < 1'
=head2 ВІДМІННОСТІ МІЖ ЗНІМКАМИ ТА ФАЙЛАМИ РЕЗЕРВНИХ КОПІЙ
-Хоча virt-ls можна скористатися для пошуку відмінностей між каталогами, з
-випуску libguestfs E<ge> 1.26 з цією метою краще користуватися новим
-інструментом, L<virt-diff(1)>.
+Хоча virt-ls можна скористатися для пошуку відмінностей між каталогами, з випуску libguestfs E<ge> 1.26 з цією метою краще користуватися новим інструментом, L<virt-diff(1)>.
=head1 РЕЖИМИ ВИВЕДЕННЯ ДАНИХ
-У C<virt-ls> передбачено чотири режими виведення даних, керування якими
-здійснюється різними комбінаціями параметрів I<-l> та I<-R>.
+У C<virt-ls> передбачено чотири режими виведення даних, керування якими здійснюється різними комбінаціями параметрів I<-l> та I<-R>.
=head2 ПРОСТИЙ СПИСОК
=head2 ДОВГИЙ СПИСОК
-З параметром I<-l> (I<--long>) виведені дані будуть подібними до даних, які
-виводить команда C<ls -l> (якщо точніше, функція C<guestfs_ll>).
+З параметром I<-l> (I<--long>) виведені дані будуть подібними до даних, які виводить команда C<ls -l> (якщо точніше, функція C<guestfs_ll>).
$ virt-ls -l -d guest /
total 204
dr-xr-xr-x. 5 root root 3072 2009-08-25 19:06 boot
[тощо]
-Зауважте, що хоча такий список зручний для перегляду вмісту каталогу, не
-варто обробляти його за допомогою іншої програми. Для обробки іншими
-програмами слід скористатися варіантом L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК>.
+Зауважте, що хоча такий список зручний для перегляду вмісту каталогу, не варто обробляти його за допомогою іншої програми. Для обробки іншими програмами слід скористатися варіантом L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК>.
=head2 РЕКУРСИВНИЙ СПИСОК
-Із параметром I<-R> (I<--recursive>) C<virt-ls> виводить список назв файлів
-і каталогів рекурсивно:
+Із параметром I<-R> (I<--recursive>) C<virt-ls> виводить список назв файлів і каталогів рекурсивно:
$ virt-ls -R -d guest /tmp
foo
foo/bar
[тощо]
-Для створення такого списку C<virt-ls> викликає функцію C<guestfs_find0> і
-перетворює символи C<\0> на C<\n>.
+Для створення такого списку C<virt-ls> викликає функцію C<guestfs_find0> і перетворює символи C<\0> на C<\n>.
=head2 РЕКУРСИВНИЙ ДОВГИЙ СПИСОК
-Використання параметрів I<-lR> разом змінює виведені дані так, що вміст
-каталогів показується рекурсивно, із даними щодо файлів, а також, якщо
-використано відповідні параметри, іншими даними, зокрема контрольними сумами
-та розширеними атрибутами.
+Використання параметрів I<-lR> разом змінює виведені дані так, що вміст каталогів показується рекурсивно, із даними щодо файлів, а також, якщо використано відповідні параметри, іншими даними, зокрема контрольними сумами та розширеними атрибутами.
-Доступ до більшості цікавих можливостей C<virt-ls> можна отримати лише у
-режимі I<-lR>.
+Доступ до більшості цікавих можливостей C<virt-ls> можна отримати лише у режимі I<-lR>.
-Зазвичай, поля відокремлюються пробілами. До назв файлів B<не додаються>
-лапки. Отже, ви не зможете скористатися виведеними даними у іншій програмі
-(оскільки у назвах файлів можуть міститися пробіли та інші нестандартні
-символи). Якщо до гостьової системи мають доступ сторонні люди і відомо, що
-ви використовуєте C<virt-ls> для аналізу вмісту гостьової системи,
-зловмисники можуть створити файли зі спеціально сконструйованими назвами та
-вбудованими до назв символами розриву рядка. Щоб виведені дані можна було
-B<безпечно> обробити у сторонній програмі, скористайтеся параметром I<--csv>
-для виведення даних у форматі значень, відокремлених комами.
+Зазвичай, поля відокремлюються пробілами. До назв файлів B<не додаються> лапки. Отже, ви не зможете скористатися виведеними даними у іншій програмі (оскільки у назвах файлів можуть міститися пробіли та інші нестандартні символи). Якщо до гостьової системи мають доступ сторонні люди і відомо, що ви використовуєте C<virt-ls> для аналізу вмісту гостьової системи, зловмисники можуть створити файли зі спеціально сконструйованими назвами та вбудованими до назв символами розриву рядка. Щоб виведені дані можна було B<безпечно> обробити у сторонній програмі, скористайтеся параметром I<--csv> для виведення даних у форматі значень, відокремлених комами.
-Зауважте, що цей формат виведення є повністю незалежним від формату команди
-C<ls -lR>.
+Зауважте, що цей формат виведення є повністю незалежним від формату команди C<ls -lR>.
$ virt-ls -lR -d guest /bin
d 0555 4096 /bin
=item тип
-Тип файла, одне з таких значень: C<-> (звичайний файл), C<d> (каталог), C<c>
-(символьний пристрій), C<b> (блоковий пристрій), C<p> (іменований канал),
-C<l> (символічне посилання), C<s> (сокет) або C<u> (невідомо).
+Тип файла, одне з таких значень: C<-> (звичайний файл), C<d> (каталог), C<c> (символьний пристрій), C<b> (блоковий пристрій), C<p> (іменований канал), C<l> (символічне посилання), C<s> (сокет) або C<u> (невідомо).
=item права доступу
=item розмір
-Розмір файла. Його буде показано у байтах, якщо не використано параметр
-I<-h> або I<--human-readable>. Якщо такий параметр використано, дані буде
-показано у зручному для читанні вигляді.
+Розмір файла. Його буде показано у байтах, якщо не використано параметр I<-h> або I<--human-readable>. Якщо такий параметр використано, дані буде показано у зручному для читанні вигляді.
=item шлях
=back
-У режимі I<-lR> додаткові параметри командного рядка уможливлюють показ
-додаткових полів.
+У режимі I<-lR> додаткові параметри командного рядка уможливлюють показ додаткових полів.
З прапорцем I<--uids> ці додаткові поля буде показано до шляху:
=item gid
-UID та GID власника файла (буде показано у числовій формі). Зауважте, що ці
-дані мають сенс лише у контексті Unix-подібної гостьової системи.
+UID та GID власника файла (буде показано у числовій формі). Зауважте, що ці дані мають сенс лише у контексті Unix-подібної гостьової системи.
=back
=back
-Вміст полів дат і часу буде показано у форматі рядків, якщо не вказано
-одного з таких параметрів: I<--time-t>, I<--time-relative> або
-I<--time-days>.
+Вміст полів дат і часу буде показано у форматі рядків, якщо не вказано одного з таких параметрів: I<--time-t>, I<--time-relative> або I<--time-days>.
Із прапорцем I<--extra-stats> буде показано такі додаткові поля:
=item пристрій
-Пристрій на якому міститься файл (буде показано у форматі
-основний:підлеглий). Запис пристрою може не збігатися із записом пристрою,
-який відомий гостьовій системі.
+Пристрій на якому міститься файл (буде показано у форматі основний:підлеглий). Запис пристрою може не збігатися із записом пристрою, який відомий гостьовій системі.
=item inode
=item rdev
-Для блоковий і символьних спеціальних файлів пристрій (буде показано у
-форматі основний:підлеглий).
+Для блоковий і символьних спеціальних файлів пристрій (буде показано у форматі основний:підлеглий).
=item блоки
=back
-Якщо використано прапорець I<--checksum>, програма покаже контрольну суму
-вмісту файла (лише для звичайних файлів). Обчислення контрольної суми може
-бути доволі тривалою дією.
+Якщо використано прапорець I<--checksum>, програма покаже контрольну суму вмісту файла (лише для звичайних файлів). Обчислення контрольної суми може бути доволі тривалою дією.
=head1 ПАРАМЕТРИ
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--checksum=crc|md5|sha1|sha224|sha256|sha384|sha512>
-Вивести контрольну суму вмісту звичайного файла. Без аргументу для створення
-контрольної суми буде використано I<md5>. За допомогою аргументу ви можете
-визначити потрібний вам тип контрольної суми.
+Вивести контрольну суму вмісту звичайного файла. Без аргументу для створення контрольної суми буде використано I<md5>. За допомогою аргументу ви можете визначити потрібний вам тип контрольної суми.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<-c> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<--csv>
-Вивести результати до формату CSV (записів, відокремлених комами). Дані у
-цьому форматі можна просто імпортувати до баз даних і електронних
-таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>,
-наведеним нижче.
+Вивести результати до формату CSV (записів, відокремлених комами). Дані у цьому форматі можна просто імпортувати до баз даних і електронних таблиць. Втім, варто ознайомитися із розділом L</НОТАТКА ЩОДО ФОРМАТУ CSV>, наведеним нижче.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-ls попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-ls попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--extra-stats>
Показати додаткові дані.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-ls --format=raw -a диск.img /каталог
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-ls --format=raw -a диск.img --format -a інший_диск.img /каталог
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
=item B<-h>
Показати розміри файлів у зручному для читання форматі.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
__INCLUDE:key-option.pod__
Якщо точку монтування не вказано, типовим значенням є F</>.
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
-
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися
-програмою L<virt-filesystems(1)>.
-
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або C<ro> (другий варіант
-використовується, якщо використано прапорець I<--ro>). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
+
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися програмою L<virt-filesystems(1)>.
+
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або C<ro> (другий варіант використовується, якщо використано прапорець I<--ro>). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
-m /dev/sda1:/:acl,user_xattr
-Використання цього прапорця є еквівалентним до використання команди
-C<mount-options>.
+Використання цього прапорця є еквівалентним до використання команди C<mount-options>.
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: C<ext2>
-і C<ext3>), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: C<ext2> і C<ext3>), або libguestfs визначає файлову систему помилково.
=item B<-l>
=item B<--recursive>
-Вибір режиму. Якщо не буде вказано жодного з варіантів, C<virt-ls> створює
-простий плоский список файлів у вказаному каталозі. Див. L</ПРОСТИЙ СПИСОК>.
+Вибір режиму. Якщо не буде вказано жодного з варіантів, C<virt-ls> створює простий плоский список файлів у вказаному каталозі. Див. L</ПРОСТИЙ СПИСОК>.
-C<virt-ls -l> створює «довгий список», у якому більше
-подробиць. Див. L</ДОВГИЙ СПИСОК>.
+C<virt-ls -l> створює «довгий список», у якому більше подробиць. Див. L</ДОВГИЙ СПИСОК>.
-C<virt-ls -R> створює рекурсивний список файлів, починаючи з вказаного
-каталогу. Див. L</РЕКУРСИВНИЙ СПИСОК>.
+C<virt-ls -R> створює рекурсивний список файлів, починаючи з вказаного каталогу. Див. L</РЕКУРСИВНИЙ СПИСОК>.
-C<virt-ls -lR> створює рекурсивні довгі списки, які простіше
-обробляти. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК>.
+C<virt-ls -lR> створює рекурсивні довгі списки, які простіше обробляти. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК>.
=item B<--times>
Показати поля часу.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<--time-days>
-Показувати поля часу у форматі днів до поточного (від’ємні значення для днів
-у майбутньому).
+Показувати поля часу у форматі днів до поточного (від’ємні значення для днів у майбутньому).
-Зауважте, що C<0> у виведених даних означає «менше 1 одного дня до поточного
-моменту» або «вік файла — від 0 до 86399 секунд».
+Зауважте, що C<0> у виведених даних означає «менше 1 одного дня до поточного моменту» або «вік файла — від 0 до 86399 секунд».
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<--time-relative>
-Показувати поля часу у форматі секунд до поточного моменту (від’ємні
-значення для часу у майбутньому).
+Показувати поля часу у форматі секунд до поточного моменту (від’ємні значення для часу у майбутньому).
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<--time-t>
Показувати поля часу у форматі секунд з моменту початку епохи UNIX.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<--uids>
Показати поля UID і GID.
-Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ
-ДОВГИЙ СПИСОК> вище.
+Цей параметр працюватиме лише у режимі виведення I<-lR>. Див. L</РЕКУРСИВНИЙ ДОВГИЙ СПИСОК> вище.
=item B<-v>
virt-ls назва_гостьової_системи /каталог
-тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб
-уникнути помилок у випадках, коли назва образу диска може збігатися із
-назвою гостьової системи.
+тоді як у цій версії вам слід скористатися I<-a> або I<-d>, відповідно, щоб уникнути помилок у випадках, коли назва образу диска може збігатися із назвою гостьової системи.
-З міркувань зворотної сумісності передбачено підтримку запису параметрів у
-застарілому форматі.
+З міркувань зворотної сумісності передбачено підтримку запису параметрів у застарілому форматі.
=head1 ЗАУВАЖЕННЯ ЩОДО ФОРМАТУ CSV
-Формат значень, які відокремлено комами (CSV), є оманливо простим. Може
-I<здатися>, що його просто обробляти, але насправді це зовсім не так.
+Формат значень, які відокремлено комами (CSV), є оманливо простим. Може I<здатися>, що його просто обробляти, але насправді це зовсім не так.
-Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не>
-працює у надійний спосіб. Ось приклад із двома стовпчиками:
+Міф: достатньо розділити поля за комами. Реальність: поділ комами I<не> працює у надійний спосіб. Ось приклад із двома стовпчиками:
"foo,bar",baz
-Міф: слід читати файл за рядками, один рядок за одну операцію
-читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось
-приклад із одним рядком:
+Міф: слід читати файл за рядками, один рядок за одну операцію читання. Реальність: читання за рядками I<не> працює у надійний спосіб. Ось приклад із одним рядком:
"foo
bar",baz
-Для скриптів командної оболонки скористайтеся C<csvtool>
-(L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних
-дистрибутивів Linux).
+Для скриптів командної оболонки скористайтеся C<csvtool> (L<https://github.com/Chris00/ocaml-csv> також є серед пакунків основних дистрибутивів Linux).
-Для інших мов програмування використовуйте бібліотеку для обробки даних CSV
-(наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
+Для інших мов програмування використовуйте бібліотеку для обробки даних CSV (наприклад, C<Text::CSV> для Perl або вбудовану бібліотеку csv Python).
-У більшості електронних таблиць та баз даних передбачено можливості
-безпосереднього імпортування даних CSV.
+У більшості електронних таблиць та баз даних передбачено можливості безпосереднього імпортування даних CSV.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>,
-L<virt-diff(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-copy-out(1)>, L<virt-diff(1)>, L<virt-tar-out(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-make-fs 1"
-.TH virt-make-fs 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-make-fs 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-make-fs — інструмент командного рядка для створення файлової системи на
-основі архіву tar або якихось файлів у каталозі. Подібний для інструментів
-\&\fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1) та \fBmksquashfs\fR\|(1). На відміну від цих
-інструментів він може створювати файлові системи стандартних типів, зокрема
-ext2/3 або \s-1NTFS,\s0 що може бути корисним, якщо ви хочете долучити ці файлові
-системи до наявних віртуальних машин (наприклад, щоб імпортувати великі
-обсяги доступних лише для читання даних до віртуальної машини).
+Virt-make-fs — інструмент командного рядка для створення файлової системи на основі архіву tar або якихось файлів у каталозі. Подібний для інструментів \fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1) та \fBmksquashfs\fR\|(1). На відміну від цих інструментів він може створювати файлові системи стандартних типів, зокрема ext2/3 або \s-1NTFS,\s0 що може бути корисним, якщо ви хочете долучити ці файлові системи до наявних віртуальних машин (наприклад, щоб імпортувати великі обсяги доступних лише для читання даних до віртуальної машини).
.PP
-Для створення порожніх дисків скористайтеся \fBvirt\-format\fR\|(1). Для створення
-складних компонувань скористайтеся \fBguestfish\fR\|(1).
+Для створення порожніх дисків скористайтеся \fBvirt\-format\fR\|(1). Для створення складних компонувань скористайтеся \fBguestfish\fR\|(1).
.PP
Базовий варіант використання:
.PP
\& virt\-make\-fs вхідні_дані вихідний.образ
.Ve
.PP
-де \f(CW\*(C`вхідні_дані\*(C'\fR є або каталогом, де зберігаються файли, які ви хочете
-додати, або архів tar (нестиснений або стиснений за допомогою gzip); а
-\&\fIвиведений.образ\fR є образом диска. Тип виведених даних визначається
-автоматично. Типовим виведеним образом диска є простий (raw) розріджений
-образ ext2, якщо ви не вкажете додаткових прапорців (див. розділ
-\&\*(L"ПАРАМЕТРИ\*(R" нижче).
+де \f(CW\*(C`вхідні_дані\*(C'\fR є або каталогом, де зберігаються файли, які ви хочете додати, або архів tar (нестиснений або стиснений за допомогою gzip); а \fIвиведений.образ\fR є образом диска. Тип виведених даних визначається автоматично. Типовим виведеним образом диска є простий (raw) розріджений образ ext2, якщо ви не вкажете додаткових прапорців (див. розділ \*(L"ПАРАМЕТРИ\*(R" нижче).
.SS "ТИП ФАЙЛОВОЇ СИСТЕМИ"
.IX Subsection "ТИП ФАЙЛОВОЇ СИСТЕМИ"
-Типовим типом файлової системи є \f(CW\*(C`ext2\*(C'\fR. Можна використовувати майже
-будь\-який тип файлової системи, підтримку якого передбачено у libguestfs
-(але \fIне\fR придатний лише для читання формат, зокрема \s-1ISO9660\s0). Ось декілька
-із найпоширеніших варіантів:
+Типовим типом файлової системи є \f(CW\*(C`ext2\*(C'\fR. Можна використовувати майже будь\-який тип файлової системи, підтримку якого передбачено у libguestfs (але \fIне\fR придатний лише для читання формат, зокрема \s-1ISO9660\s0). Ось декілька із найпоширеніших варіантів:
.IP "\fIext3\fR" 4
.IX Item "ext3"
-Зауважте, що у файлових системах ext3 міститься журнал із типовим розміром
-1\-32 МБ. Якщо ви не збираєтеся використовувати файлову систему у спосіб,
-який потребує журналу, цей журнал є лише непотрібним доповненням файлової
-системи.
+Зауважте, що у файлових системах ext3 міститься журнал із типовим розміром 1\-32 МБ. Якщо ви не збираєтеся використовувати файлову систему у спосіб, який потребує журналу, цей журнал є лише непотрібним доповненням файлової системи.
.IP "\fIntfs\fR або \fIvfat\fR" 4
.IX Item "ntfs або vfat"
Корисно, якщо дані експортуються до гостьової системи Windows.
.IP "\fIminix\fR" 4
.IX Item "minix"
-Менша зайва витрата місця за \f(CW\*(C`ext2\*(C'\fR, але є певні обмеження щодо довжини
-назви файла і загального розміру файлової системи.
+Менша зайва витрата місця за \f(CW\*(C`ext2\*(C'\fR, але є певні обмеження щодо довжини назви файла і загального розміру файлової системи.
.PP
\fIПРИКЛАД\fR
.IX Subsection "ПРИКЛАД"
.IX Subsection "ДІЛИТИ ЧИ НЕ ДІЛИТИ НА РОЗДІЛИ"
На вимогу, virt-make-fs може додавати на диск\-результат таблицю розділів.
.PP
-Додавання розділу може зробити образ диска суміснішим із деякими
-віртуалізованими операційними системами, які не можуть працювати із
-файловими системами, які безпосередньо розміщено на блоковому пристрої
-(Linux не звертає на це уваги і може успішно працювати із обома типами
-образів).
+Додавання розділу може зробити образ диска суміснішим із деякими віртуалізованими операційними системами, які не можуть працювати із файловими системами, які безпосередньо розміщено на блоковому пристрої (Linux не звертає на це уваги і може успішно працювати із обома типами образів).
.PP
-З іншого боку, якщо у вас є таблиця розділів, образ\-результат вже не буде
-простою файловою системою. Наприклад, ви не зможете запустити \fBfsck\fR\|(8)
-безпосередньо для поділеного на розділи образу диска. (Втім, можна буде
-користуватися засобами libguestfs, зокрема \fBguestfish\fR\|(1) і
-\&\fBvirt\-resize\fR\|(1)).
+З іншого боку, якщо у вас є таблиця розділів, образ\-результат вже не буде простою файловою системою. Наприклад, ви не зможете запустити \fBfsck\fR\|(8) безпосередньо для поділеного на розділи образу диска. (Втім, можна буде користуватися засобами libguestfs, зокрема \fBguestfish\fR\|(1) і \fBvirt\-resize\fR\|(1)).
.PP
\fIПРИКЛАД\fR
.IX Subsection "ПРИКЛАД"
\& virt\-make\-fs \-\-partition \-\- input образ.img
.Ve
.PP
-Якщо виведений образ диска може бути розміром у терабайт або більше, краще
-скористатися сумісною із \s-1EFI/GPT\s0 таблицею розділів:
+Якщо виведений образ диска може бути розміром у терабайт або більше, краще скористатися сумісною із \s-1EFI/GPT\s0 таблицею розділів:
.PP
.Vb 1
\& virt\-make\-fs \-\-partition=gpt \-\-size=+4T \-\-format=qcow2 input диск.img
.Ve
.SS "ЗАЙВЕ МІСЦЕ"
.IX Subsection "ЗАЙВЕ МІСЦЕ"
-На відміну від форматів, таких як tar і squashfs, файлова система не може
-«просто підлаштуватися» під файли, які вона містить, — вона може потребувати
-зайвого місця. Залежно від того, як ви збираєтеся використовувати виведений
-образ, зайве місце може бути небажаним, таким, яке слід мінімізувати, або
-бажаним для додавання згодом файлів. Типовою поведінкою virt-make-fs є
-мінімізація зайвого місця, але ви можете скористатися прапорцем \fI\-\-size\fR
-для створення зайвого місця, якщо вам це потрібно.
+На відміну від форматів, таких як tar і squashfs, файлова система не може «просто підлаштуватися» під файли, які вона містить, — вона може потребувати зайвого місця. Залежно від того, як ви збираєтеся використовувати виведений образ, зайве місце може бути небажаним, таким, яке слід мінімізувати, або бажаним для додавання згодом файлів. Типовою поведінкою virt-make-fs є мінімізація зайвого місця, але ви можете скористатися прапорцем \fI\-\-size\fR для створення зайвого місця, якщо вам це потрібно.
.PP
-Альтернативним способом створити зайве місце без збільшення
-образу\-результату є використання альтернативного формату образів дисків
-(замість типового формату «raw"»). За допомогою параметра \fI\-\-format=qcow2\fR
-можна визначити природний для qemu/KVM формат образів qcow2 (перш ніж
-користуватися ним, перевірте, чи передбачено підтримку цього формату у
-вашому гіпервізорі). Це надасть вам змогу вибрати більший розмір за
-допомогою \fI\-\-size\fR так, щоб зайве місце було розподілено у образі лише
-після того, як ви спробуєте на ньому щось зберегти.
+Альтернативним способом створити зайве місце без збільшення образу\-результату є використання альтернативного формату образів дисків (замість типового формату «raw"»). За допомогою параметра \fI\-\-format=qcow2\fR можна визначити природний для qemu/KVM формат образів qcow2 (перш ніж користуватися ним, перевірте, чи передбачено підтримку цього формату у вашому гіпервізорі). Це надасть вам змогу вибрати більший розмір за допомогою \fI\-\-size\fR так, щоб зайве місце було розподілено у образі лише після того, як ви спробуєте на ньому щось зберегти.
.PP
-Не забувайте, що ви також можете скористатися локальними командами, зокрема
-\&\fBresize2fs\fR\|(8) та \fBvirt\-resize\fR\|(1), для зміни розмірів наявних файлових
-систем або повторно запустити virt-make-fs для збирання іншого образу «з
-нуля».
+Не забувайте, що ви також можете скористатися локальними командами, зокрема \fBresize2fs\fR\|(8) та \fBvirt\-resize\fR\|(1), для зміни розмірів наявних файлових систем або повторно запустити virt-make-fs для збирання іншого образу «з нуля».
.PP
\fIПРИКЛАД\fR
.IX Subsection "ПРИКЛАД"
.IX Item "--floppy"
Створити віртуальну дискету.
.Sp
-У поточній версії буде попередньо вибрано розмір (1440 кБ), тип розділу
-(\s-1MBR\s0) і тип файлової системи (\s-1VFAT\s0). У майбутньому також може бути вибрано
-геометрію.
+У поточній версії буде попередньо вибрано розмір (1440 кБ), тип розділу (\s-1MBR\s0) і тип файлової системи (\s-1VFAT\s0). У майбутньому також може бути вибрано геометрію.
.IP "\fB\-\-size=\fRN" 4
.IX Item "--size=N"
.PD 0
.IP "\fB\-s\fR \fB+\fRN" 4
.IX Item "-s +N"
.PD
-Скористайтеся параметром \fI\-\-size\fR (або \fI\-s\fR), щоб вибрати розмір
-образу\-результату.
+Скористайтеся параметром \fI\-\-size\fR (або \fI\-s\fR), щоб вибрати розмір образу\-результату.
.Sp
-Якщо цей параметр \fIне\fR вказано, образ\-результат буде точно таким великим,
-щоб умістити усі файли без зайвої витрати місця.
+Якщо цей параметр \fIне\fR вказано, образ\-результат буде точно таким великим, щоб умістити усі файли без зайвої витрати місця.
.Sp
-Щоб вибрати для диска\-результату фіксований розмір, вкажіть значення розміру
-з суфіксом b/K/M/G/T/P/E, який позначає байти, кілобайти, мегабайти,
-гігабайти, терабайти, петабайти або ексабайти. Диск має бути достатньо
-об'ємним, щоб умістити усі вхідні файли. Якщо розмір диска виявиться
-недостатнім, вам буде повідомлено про помилку.
+Щоб вибрати для диска\-результату фіксований розмір, вкажіть значення розміру з суфіксом b/K/M/G/T/P/E, який позначає байти, кілобайти, мегабайти, гігабайти, терабайти, петабайти або ексабайти. Диск має бути достатньо об'ємним, щоб умістити усі вхідні файли. Якщо розмір диска виявиться недостатнім, вам буде повідомлено про помилку.
.Sp
-Щоб лишити на диску зайве місце, вкажіть \f(CW\*(C`+\*(C'\fR (символ «плюс») із числовим
-значенням та суфіксом b/K/M/G/T/P/E , який позначає байти, кілобайти,
-мегабайти, гігабайти, терабайти, петабайти або ексабайти. Наприклад,
-\&\fI\-\-size=+200M\fR означає «достатньо місця для вхідних файлів та (приблизно)
-зайві 200 МБ вільного місця».
+Щоб лишити на диску зайве місце, вкажіть \f(CW\*(C`+\*(C'\fR (символ «плюс») із числовим значенням та суфіксом b/K/M/G/T/P/E , який позначає байти, кілобайти, мегабайти, гігабайти, терабайти, петабайти або ексабайти. Наприклад, \fI\-\-size=+200M\fR означає «достатньо місця для вхідних файлів та (приблизно) зайві 200 МБ вільного місця».
.Sp
-Зауважте, що virt-make-fs estimates використовує оцінки вільного місця на
-диску, тому створені програмою файлові системи не міститимуть рівно стільки
-вільного місця, скільки ви вкажете. (Створення файлової системи, яка
-міститиме рівно стільки місця, скільки було вказано користувачем, є доволі
-складним і тривалим завданням.)
+Зауважте, що virt-make-fs estimates використовує оцінки вільного місця на диску, тому створені програмою файлові системи не міститимуть рівно стільки вільного місця, скільки ви вкажете. (Створення файлової системи, яка міститиме рівно стільки місця, скільки було вказано користувачем, є доволі складним і тривалим завданням.)
.IP "\fB\-\-format=\fRФОРМАТ" 4
.IX Item "--format=ФОРМАТ"
.PD 0
.Sp
Типовим значенням є \f(CW\*(C`ext2\*(C'\fR.
.Sp
-Тут можна скористатися будь\-якою файловою системою, підтримку читання і
-запису для якої передбачено у libguestfs.
+Тут можна скористатися будь\-якою файловою системою, підтримку читання і запису для якої передбачено у libguestfs.
.IP "\fB\-\-label=\fRМІТКА" 4
.IX Item "--label=МІТКА"
Встановити мітку файлової системи.
.IP "\fB\-\-partition=\fRТИП РОЗДІЛУ" 4
.IX Item "--partition=ТИП РОЗДІЛУ"
.PD
-Якщо його вказано, цей прапорець додає таблицю розділів \s-1MBR\s0 на виведений
-програмою образ диска.
+Якщо його вказано, цей прапорець додає таблицю розділів \s-1MBR\s0 на виведений програмою образ диска.
.Sp
-Ви можете змінити тип таблиці розділів, наприклад, вказати
-\&\fI\-\-partition=gpt\fR для великих дисків.
+Ви можете змінити тип таблиці розділів, наприклад, вказати \fI\-\-partition=gpt\fR для великих дисків.
.Sp
Для \s-1MBR\s0 virt-make-fs встановлює значення байта типу розділу автоматично.
.IP "\fB\-v\fR" 4
Увімкнути трасування libguestfs.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfish\fR\|(1), \fBvirt\-format\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-tar\-in\fR\|(1),
-\&\fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1), \fBmksquashfs\fR\|(1), \fBmke2fs\fR\|(8),
-\&\fBresize2fs\fR\|(8), \fBguestfs\fR\|(3), http://libguestfs.org/.
+\&\fBguestfish\fR\|(1), \fBvirt\-format\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-tar\-in\fR\|(1), \fBmkisofs\fR\|(1), \fBgenisoimage\fR\|(1), \fBmksquashfs\fR\|(1), \fBmke2fs\fR\|(8), \fBresize2fs\fR\|(8), \fBguestfs\fR\|(3), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Virt-make-fs — інструмент командного рядка для створення файлової системи на
-основі архіву tar або якихось файлів у каталозі. Подібний для інструментів
-L<mkisofs(1)>, L<genisoimage(1)> та L<mksquashfs(1)>. На відміну від цих
-інструментів він може створювати файлові системи стандартних типів, зокрема
-ext2/3 або NTFS, що може бути корисним, якщо ви хочете долучити ці файлові
-системи до наявних віртуальних машин (наприклад, щоб імпортувати великі
-обсяги доступних лише для читання даних до віртуальної машини).
+Virt-make-fs — інструмент командного рядка для створення файлової системи на основі архіву tar або якихось файлів у каталозі. Подібний для інструментів L<mkisofs(1)>, L<genisoimage(1)> та L<mksquashfs(1)>. На відміну від цих інструментів він може створювати файлові системи стандартних типів, зокрема ext2/3 або NTFS, що може бути корисним, якщо ви хочете долучити ці файлові системи до наявних віртуальних машин (наприклад, щоб імпортувати великі обсяги доступних лише для читання даних до віртуальної машини).
-Для створення порожніх дисків скористайтеся L<virt-format(1)>. Для створення
-складних компонувань скористайтеся L<guestfish(1)>.
+Для створення порожніх дисків скористайтеся L<virt-format(1)>. Для створення складних компонувань скористайтеся L<guestfish(1)>.
Базовий варіант використання:
virt-make-fs вхідні_дані вихідний.образ
-де C<вхідні_дані> є або каталогом, де зберігаються файли, які ви хочете
-додати, або архів tar (нестиснений або стиснений за допомогою gzip); а
-F<виведений.образ> є образом диска. Тип виведених даних визначається
-автоматично. Типовим виведеним образом диска є простий (raw) розріджений
-образ ext2, якщо ви не вкажете додаткових прапорців (див. розділ
-L</ПАРАМЕТРИ> нижче).
+де C<вхідні_дані> є або каталогом, де зберігаються файли, які ви хочете додати, або архів tar (нестиснений або стиснений за допомогою gzip); а F<виведений.образ> є образом диска. Тип виведених даних визначається автоматично. Типовим виведеним образом диска є простий (raw) розріджений образ ext2, якщо ви не вкажете додаткових прапорців (див. розділ L</ПАРАМЕТРИ> нижче).
=head2 ТИП ФАЙЛОВОЇ СИСТЕМИ
-Типовим типом файлової системи є C<ext2>. Можна використовувати майже
-будь-який тип файлової системи, підтримку якого передбачено у libguestfs
-(але I<не> придатний лише для читання формат, зокрема ISO9660). Ось декілька
-із найпоширеніших варіантів:
+Типовим типом файлової системи є C<ext2>. Можна використовувати майже будь-який тип файлової системи, підтримку якого передбачено у libguestfs (але I<не> придатний лише для читання формат, зокрема ISO9660). Ось декілька із найпоширеніших варіантів:
=over 4
=item I<ext3>
-Зауважте, що у файлових системах ext3 міститься журнал із типовим розміром
-1-32 МБ. Якщо ви не збираєтеся використовувати файлову систему у спосіб,
-який потребує журналу, цей журнал є лише непотрібним доповненням файлової
-системи.
+Зауважте, що у файлових системах ext3 міститься журнал із типовим розміром 1-32 МБ. Якщо ви не збираєтеся використовувати файлову систему у спосіб, який потребує журналу, цей журнал є лише непотрібним доповненням файлової системи.
=item I<ntfs> або I<vfat>
=item I<minix>
-Менша зайва витрата місця за C<ext2>, але є певні обмеження щодо довжини
-назви файла і загального розміру файлової системи.
+Менша зайва витрата місця за C<ext2>, але є певні обмеження щодо довжини назви файла і загального розміру файлової системи.
=back
На вимогу, virt-make-fs може додавати на диск-результат таблицю розділів.
-Додавання розділу може зробити образ диска суміснішим із деякими
-віртуалізованими операційними системами, які не можуть працювати із
-файловими системами, які безпосередньо розміщено на блоковому пристрої
-(Linux не звертає на це уваги і може успішно працювати із обома типами
-образів).
+Додавання розділу може зробити образ диска суміснішим із деякими віртуалізованими операційними системами, які не можуть працювати із файловими системами, які безпосередньо розміщено на блоковому пристрої (Linux не звертає на це уваги і може успішно працювати із обома типами образів).
-З іншого боку, якщо у вас є таблиця розділів, образ-результат вже не буде
-простою файловою системою. Наприклад, ви не зможете запустити L<fsck(8)>
-безпосередньо для поділеного на розділи образу диска. (Втім, можна буде
-користуватися засобами libguestfs, зокрема L<guestfish(1)> і
-L<virt-resize(1)>).
+З іншого боку, якщо у вас є таблиця розділів, образ-результат вже не буде простою файловою системою. Наприклад, ви не зможете запустити L<fsck(8)> безпосередньо для поділеного на розділи образу диска. (Втім, можна буде користуватися засобами libguestfs, зокрема L<guestfish(1)> і L<virt-resize(1)>).
=head3 ПРИКЛАД
virt-make-fs --partition -- input образ.img
-Якщо виведений образ диска може бути розміром у терабайт або більше, краще
-скористатися сумісною із EFI/GPT таблицею розділів:
+Якщо виведений образ диска може бути розміром у терабайт або більше, краще скористатися сумісною із EFI/GPT таблицею розділів:
virt-make-fs --partition=gpt --size=+4T --format=qcow2 input диск.img
=head2 ЗАЙВЕ МІСЦЕ
-На відміну від форматів, таких як tar і squashfs, файлова система не може
-«просто підлаштуватися» під файли, які вона містить, — вона може потребувати
-зайвого місця. Залежно від того, як ви збираєтеся використовувати виведений
-образ, зайве місце може бути небажаним, таким, яке слід мінімізувати, або
-бажаним для додавання згодом файлів. Типовою поведінкою virt-make-fs є
-мінімізація зайвого місця, але ви можете скористатися прапорцем I<--size>
-для створення зайвого місця, якщо вам це потрібно.
-
-Альтернативним способом створити зайве місце без збільшення
-образу-результату є використання альтернативного формату образів дисків
-(замість типового формату «raw"»). За допомогою параметра I<--format=qcow2>
-можна визначити природний для qemu/KVM формат образів qcow2 (перш ніж
-користуватися ним, перевірте, чи передбачено підтримку цього формату у
-вашому гіпервізорі). Це надасть вам змогу вибрати більший розмір за
-допомогою I<--size> так, щоб зайве місце було розподілено у образі лише
-після того, як ви спробуєте на ньому щось зберегти.
-
-Не забувайте, що ви також можете скористатися локальними командами, зокрема
-L<resize2fs(8)> та L<virt-resize(1)>, для зміни розмірів наявних файлових
-систем або повторно запустити virt-make-fs для збирання іншого образу «з
-нуля».
+На відміну від форматів, таких як tar і squashfs, файлова система не може «просто підлаштуватися» під файли, які вона містить, — вона може потребувати зайвого місця. Залежно від того, як ви збираєтеся використовувати виведений образ, зайве місце може бути небажаним, таким, яке слід мінімізувати, або бажаним для додавання згодом файлів. Типовою поведінкою virt-make-fs є мінімізація зайвого місця, але ви можете скористатися прапорцем I<--size> для створення зайвого місця, якщо вам це потрібно.
+
+Альтернативним способом створити зайве місце без збільшення образу-результату є використання альтернативного формату образів дисків (замість типового формату «raw"»). За допомогою параметра I<--format=qcow2> можна визначити природний для qemu/KVM формат образів qcow2 (перш ніж користуватися ним, перевірте, чи передбачено підтримку цього формату у вашому гіпервізорі). Це надасть вам змогу вибрати більший розмір за допомогою I<--size> так, щоб зайве місце було розподілено у образі лише після того, як ви спробуєте на ньому щось зберегти.
+
+Не забувайте, що ви також можете скористатися локальними командами, зокрема L<resize2fs(8)> та L<virt-resize(1)>, для зміни розмірів наявних файлових систем або повторно запустити virt-make-fs для збирання іншого образу «з нуля».
=head3 ПРИКЛАД
Створити віртуальну дискету.
-У поточній версії буде попередньо вибрано розмір (1440 кБ), тип розділу
-(MBR) і тип файлової системи (VFAT). У майбутньому також може бути вибрано
-геометрію.
+У поточній версії буде попередньо вибрано розмір (1440 кБ), тип розділу (MBR) і тип файлової системи (VFAT). У майбутньому також може бути вибрано геометрію.
=item B<--size=>N
=item B<-s> B<+>N
-Скористайтеся параметром I<--size> (або I<-s>), щоб вибрати розмір
-образу-результату.
+Скористайтеся параметром I<--size> (або I<-s>), щоб вибрати розмір образу-результату.
-Якщо цей параметр I<не> вказано, образ-результат буде точно таким великим,
-щоб умістити усі файли без зайвої витрати місця.
+Якщо цей параметр I<не> вказано, образ-результат буде точно таким великим, щоб умістити усі файли без зайвої витрати місця.
-Щоб вибрати для диска-результату фіксований розмір, вкажіть значення розміру
-з суфіксом b/K/M/G/T/P/E, який позначає байти, кілобайти, мегабайти,
-гігабайти, терабайти, петабайти або ексабайти. Диск має бути достатньо
-об'ємним, щоб умістити усі вхідні файли. Якщо розмір диска виявиться
-недостатнім, вам буде повідомлено про помилку.
+Щоб вибрати для диска-результату фіксований розмір, вкажіть значення розміру з суфіксом b/K/M/G/T/P/E, який позначає байти, кілобайти, мегабайти, гігабайти, терабайти, петабайти або ексабайти. Диск має бути достатньо об'ємним, щоб умістити усі вхідні файли. Якщо розмір диска виявиться недостатнім, вам буде повідомлено про помилку.
-Щоб лишити на диску зайве місце, вкажіть C<+> (символ «плюс») із числовим
-значенням та суфіксом b/K/M/G/T/P/E , який позначає байти, кілобайти,
-мегабайти, гігабайти, терабайти, петабайти або ексабайти. Наприклад,
-I<--size=+200M> означає «достатньо місця для вхідних файлів та (приблизно)
-зайві 200 МБ вільного місця».
+Щоб лишити на диску зайве місце, вкажіть C<+> (символ «плюс») із числовим значенням та суфіксом b/K/M/G/T/P/E , який позначає байти, кілобайти, мегабайти, гігабайти, терабайти, петабайти або ексабайти. Наприклад, I<--size=+200M> означає «достатньо місця для вхідних файлів та (приблизно) зайві 200 МБ вільного місця».
-Зауважте, що virt-make-fs estimates використовує оцінки вільного місця на
-диску, тому створені програмою файлові системи не міститимуть рівно стільки
-вільного місця, скільки ви вкажете. (Створення файлової системи, яка
-міститиме рівно стільки місця, скільки було вказано користувачем, є доволі
-складним і тривалим завданням.)
+Зауважте, що virt-make-fs estimates використовує оцінки вільного місця на диску, тому створені програмою файлові системи не міститимуть рівно стільки вільного місця, скільки ви вкажете. (Створення файлової системи, яка міститиме рівно стільки місця, скільки було вказано користувачем, є доволі складним і тривалим завданням.)
=item B<--format=>ФОРМАТ
Типовим значенням є C<ext2>.
-Тут можна скористатися будь-якою файловою системою, підтримку читання і
-запису для якої передбачено у libguestfs.
+Тут можна скористатися будь-якою файловою системою, підтримку читання і запису для якої передбачено у libguestfs.
=item B<--label=>МІТКА
=item B<--partition=>ТИП РОЗДІЛУ
-Якщо його вказано, цей прапорець додає таблицю розділів MBR на виведений
-програмою образ диска.
+Якщо його вказано, цей прапорець додає таблицю розділів MBR на виведений програмою образ диска.
-Ви можете змінити тип таблиці розділів, наприклад, вказати
-I<--partition=gpt> для великих дисків.
+Ви можете змінити тип таблиці розділів, наприклад, вказати I<--partition=gpt> для великих дисків.
Для MBR virt-make-fs встановлює значення байта типу розділу автоматично.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfish(1)>, L<virt-format(1)>, L<virt-resize(1)>, L<virt-tar-in(1)>,
-L<mkisofs(1)>, L<genisoimage(1)>, L<mksquashfs(1)>, L<mke2fs(8)>,
-L<resize2fs(8)>, L<guestfs(3)>, L<http://libguestfs.org/>.
+L<guestfish(1)>, L<virt-format(1)>, L<virt-resize(1)>, L<virt-tar-in(1)>, L<mkisofs(1)>, L<genisoimage(1)>, L<mksquashfs(1)>, L<mke2fs(8)>, L<resize2fs(8)>, L<guestfs(3)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-resize 1"
-.TH virt-resize 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-resize 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-resize — програма, за допомогою якої можна змінити розміри диска
-віртуальної машини, зробивши його більшим або меншим чи змінивши розміри
-розділів, які містяться на диску, або вилучивши їх.
-.PP
-Virt-resize \fBне може\fR змінювати розмір образів дисків «на
-місці». Virt-resize \fBне слід\fR використовувати для активних віртуальних
-машин — щоб отримати належний результат, перш ніж змінювати розміри дисків,
-зупиніть роботу віртуальної машини.
-.PP
-Якщо ви ще не знайомі з принципами роботи пов'язаних інструментів,
-\&\fBvirt\-filesystems\fR\|(1) і \fBvirt\-df\fR\|(1), рекомендуємо вам спершу ознайомитися
-із документацією щодо цих інструментів.
+Virt-resize — програма, за допомогою якої можна змінити розміри диска віртуальної машини, зробивши його більшим або меншим чи змінивши розміри розділів, які містяться на диску, або вилучивши їх.
+.PP
+Virt-resize \fBне може\fR змінювати розмір образів дисків «на місці». Virt-resize \fBне слід\fR використовувати для активних віртуальних машин — щоб отримати належний результат, перш ніж змінювати розміри дисків, зупиніть роботу віртуальної машини.
+.PP
+Якщо ви ще не знайомі з принципами роботи пов'язаних інструментів, \fBvirt\-filesystems\fR\|(1) і \fBvirt\-df\fR\|(1), рекомендуємо вам спершу ознайомитися із документацією щодо цих інструментів.
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
.IP "1." 4
-У цьому прикладі ми візьмемо \f(CW\*(C`старий_диск\*(C'\fR, змінимо його розміри і запишемо
-як \f(CW\*(C`новий_диск\*(C'\fR, розширивши один із розділів гостьової системи на додаткові
-5 ГБ:
+У цьому прикладі ми візьмемо \f(CW\*(C`старий_диск\*(C'\fR, змінимо його розміри і запишемо як \f(CW\*(C`новий_диск\*(C'\fR, розширивши один із розділів гостьової системи на додаткові 5 ГБ:
.Sp
.Vb 1
\& virt\-filesystems \-\-long \-h \-\-all \-a старий_диск
\& virt\-resize \-\-expand /dev/sda2 старий_диск новий_диск
.Ve
.IP "2." 4
-Те саме, що і вище, але зі збільшенням розділу /boot на 200 МБ, з наданням
-решти місця для /dev/sda2:
+Те саме, що і вище, але зі збільшенням розділу /boot на 200 МБ, з наданням решти місця для /dev/sda2:
.Sp
.Vb 2
\& virt\-resize \-\-resize /dev/sda1=+200M \-\-expand /dev/sda2 \e
\& старий_диск новий_диск
.Ve
.IP "3." 4
-Як у першому прикладі, але із розширенням логічного тому на останньому
-кроці. Саме цю команду типово використовують для гостьових систем Linux, де
-використовується \s-1LVM:\s0
+Як у першому прикладі, але із розширенням логічного тому на останньому кроці. Саме цю команду типово використовують для гостьових систем Linux, де використовується \s-1LVM:\s0
.Sp
.Vb 2
\& virt\-resize \-\-expand /dev/sda2 \-\-LV\-expand /dev/vg_guest/lv_root \e
\& старий_диск новий_диск
.Ve
.IP "4." 4
-Як у першому прикладі, але дані буде виведено у форматі qcow2, а не у
-простому (raw) форматі:
+Як у першому прикладі, але дані буде виведено у форматі qcow2, а не у простому (raw) форматі:
.Sp
.Vb 2
\& qemu\-img create \-f qcow2 \-o preallocation=metadata newdisk.qcow2 15G
.IP "2. Встановіть розташування образу диска із вхідними даними" 4
.IX Item "2. Встановіть розташування образу диска із вхідними даними"
.PD
-Встановіть розташування образу диска із вхідними даними (тобто файла або
-пристрою у основній системі, де містяться дані диска гостьової
-системи). Якщо гостьовою системою керує libvirt, ви можете скористатися для
-визначення назви образу диска командою \f(CW\*(C`virsh dumpxml\*(C'\fR, ось так:
+Встановіть розташування образу диска із вхідними даними (тобто файла або пристрою у основній системі, де містяться дані диска гостьової системи). Якщо гостьовою системою керує libvirt, ви можете скористатися для визначення назви образу диска командою \f(CW\*(C`virsh dumpxml\*(C'\fR, ось так:
.Sp
.Vb 4
\& # virsh dumpxml guestname | xpath /domain/devices/disk/source
.Ve
.IP "3. Визначте поточні розміри" 4
.IX Item "3. Визначте поточні розміри"
-Скористайтеся програмою \fBvirt\-filesystems\fR\|(1) для перегляду списку поточних
-розділів і їхніх розмірів:
+Скористайтеся програмою \fBvirt\-filesystems\fR\|(1) для перегляду списку поточних розділів і їхніх розмірів:
.Sp
.Vb 5
\& # virt\-filesystems \-\-long \-\-parts \-\-blkdevs \-h \-a /dev/vg/lv_guest
\& /dev/sda device 8.0G \-
.Ve
.Sp
-(У цьому прикладі маємо справу з віртуальною машиною з диском у 8 ГБ, який
-ми хочемо розширити до 10 ГБ).
+(У цьому прикладі маємо справу з віртуальною машиною з диском у 8 ГБ, який ми хочемо розширити до 10 ГБ).
.IP "4. Створіть диск для виведення даних" 4
.IX Item "4. Створіть диск для виведення даних"
-Virt-resize не може виконувати внесення змін до дисків «на місці». У вашій
-системі має бути достатньо місця для зберігання диска\-результату зі зміненим
-розміром.
+Virt-resize не може виконувати внесення змін до дисків «на місці». У вашій системі має бути достатньо місця для зберігання диска\-результату зі зміненим розміром.
.Sp
-Для збереження образу диска зі зміненим розміром створіть файл відповідного
-розміру:
+Для збереження образу диска зі зміненим розміром створіть файл відповідного розміру:
.Sp
.Vb 2
\& # rm \-f outdisk
\& # lvcreate \-L 10G \-n lv_name vg_name
.Ve
.Sp
-Або скористайтеся \fBvirsh\fR\|(1) vol-create-as для створення тому сховища даних
-libvirt:
+Або скористайтеся \fBvirsh\fR\|(1) vol-create-as для створення тому сховища даних libvirt:
.Sp
.Vb 2
\& # virsh pool\-list
.Ve
.IP "5. Зміна розміру" 4
.IX Item "5. Зміна розміру"
-virt-resize має отримати два обов'язкових параметри, назву диска із вхідними
-даними і назву диска із вихідними даними (обидві можуть бути, наприклад,
-пристроями, файлами або адресами на віддаленому диску). Диском з виведеними
-даними має бути диск, створений на попередньому кроці.
+virt-resize має отримати два обов'язкових параметри, назву диска із вхідними даними і назву диска із вихідними даними (обидві можуть бути, наприклад, пристроями, файлами або адресами на віддаленому диску). Диском з виведеними даними має бути диск, створений на попередньому кроці.
.Sp
.Vb 1
\& # virt\-resize indisk outdisk
.Ve
.Sp
-Ця команда просто копіює образ диска \f(CW\*(C`indisk\*(C'\fR до образу диска \f(CW\*(C`outdisk\*(C'\fR
-\&\fIбез\fR зміни розмірів або будь\-яких змін у наявних розділах. Якщо диск
-\&\f(CW\*(C`outdisk\*(C'\fR є завеликим для даних, створюється додатковий порожній розділ
-наприкінці диска, розмір якого відповідатиме зайвому місцю. Якщо диск
-\&\f(CW\*(C`outdisk\*(C'\fR виявиться замалим, програма повідомить про помилку.
+Ця команда просто копіює образ диска \f(CW\*(C`indisk\*(C'\fR до образу диска \f(CW\*(C`outdisk\*(C'\fR \fIбез\fR зміни розмірів або будь\-яких змін у наявних розділах. Якщо диск \f(CW\*(C`outdisk\*(C'\fR є завеликим для даних, створюється додатковий порожній розділ наприкінці диска, розмір якого відповідатиме зайвому місцю. Якщо диск \f(CW\*(C`outdisk\*(C'\fR виявиться замалим, програма повідомить про помилку.
.Sp
-Реалістичнішим буде варіант, коли вам потрібно розширити наявні розділи на
-образі диска передаванням додаткових параметрів (повний список параметрів
-наведено у розділі \*(L"ПАРАМЕТРИ\*(R" нижче).
+Реалістичнішим буде варіант, коли вам потрібно розширити наявні розділи на образі диска передаванням додаткових параметрів (повний список параметрів наведено у розділі \*(L"ПАРАМЕТРИ\*(R" нижче).
.Sp
-\&\*(L"\-\-expand\*(R" є найкориснішим параметром. За його допомогою можна розширити
-вказаний за назвою розділ на диску так, щоб він зайняв усе зайве місце:
+\&\*(L"\-\-expand\*(R" є найкориснішим параметром. За його допомогою можна розширити вказаний за назвою розділ на диску так, щоб він зайняв усе зайве місце:
.Sp
.Vb 1
\& # virt\-resize \-\-expand /dev/sda2 indisk outdisk
.Ve
.Sp
-(У цьому випадку наприкінці диска \fIне\fR створюватиметься додаткових
-розділів, оскільки невикористаного місця просто не буде).
+(У цьому випадку наприкінці диска \fIне\fR створюватиметься додаткових розділів, оскільки невикористаного місця просто не буде).
.Sp
-\&\*(L"\-\-resize\*(R" — ще один широковживаний параметр. Наступна команда збільшить
-розмір /dev/sda1 на 200 МБ і розширить /dev/sda2 так, щоб той заповнив решту
-доступного місця:
+\&\*(L"\-\-resize\*(R" — ще один широковживаний параметр. Наступна команда збільшить розмір /dev/sda1 на 200 МБ і розширить /dev/sda2 так, щоб той заповнив решту доступного місця:
.Sp
.Vb 2
\& # virt\-resize \-\-resize /dev/sda1=+200M \-\-expand /dev/sda2 \e
\& indisk outdisk
.Ve
.Sp
-Якщо на розширюваному розділі у образі міститься файлова система або
-фізичний том \s-1LVM,\s0 тоді, якщо virt-resize відомий спосіб, програма змінить
-розміри вмісту так, як це роблять виклики команд \fBpvresize\fR\|(8),
-\&\fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8) або
-\&\fBresize.f2fs\fR\|(8). Втім, virt-resize не відомі способи зміни розмірів деяких
-файлових систем, тому вам доведеться якось змінювати їхні розміри після
-завантаження гостьової системи.
+Якщо на розширюваному розділі у образі міститься файлова система або фізичний том \s-1LVM,\s0 тоді, якщо virt-resize відомий спосіб, програма змінить розміри вмісту так, як це роблять виклики команд \fBpvresize\fR\|(8), \fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8) або \fBresize.f2fs\fR\|(8). Втім, virt-resize не відомі способи зміни розмірів деяких файлових систем, тому вам доведеться якось змінювати їхні розміри після завантаження гостьової системи.
.Sp
.Vb 1
\& # virt\-resize \-\-expand /dev/sda2 nbd://example.com outdisk
.Ve
.Sp
-Диском із вхідними даними може бути адреса, якщо як джерело слід використати
-віддалений диск. Формат адреси є сумісним із
-guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
+Диском із вхідними даними може бути адреса, якщо як джерело слід використати віддалений диск. Формат адреси є сумісним із guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
.Sp
Інші параметри описано нижче.
.IP "6. Перевірка" 4
.IX Item "6. Перевірка"
-Виконайте належне тестування нового образу диска, \fIперш ніж\fR витирати
-старий.
+Виконайте належне тестування нового образу диска, \fIперш ніж\fR витирати старий.
.Sp
-Якщо ви користуєтеся libvirt, внесіть зміни до \s-1XML\s0 так, щоб він вказував на
-новий диск:
+Якщо ви користуєтеся libvirt, внесіть зміни до \s-1XML\s0 так, щоб він вказував на новий диск:
.Sp
.Vb 1
\& # virsh edit назва_гостьової_системи
.Ve
.Sp
-Змініть <source ...>,
-див. http://libvirt.org/formatdomain.html#elementsDisks
+Змініть <source ...>, див. http://libvirt.org/formatdomain.html#elementsDisks
.Sp
Далі, запустіть домен з новим диском, розмір якого було змінено:
.Sp
\& # virsh start назва_гостьової_системи
.Ve
.Sp
-і перевірте, чи все лишається працездатним. Див. також додаткові зауваження
-у розділі \*(L"ПРИМІТКИ\*(R" нижче.
+і перевірте, чи все лишається працездатним. Див. також додаткові зауваження у розділі \*(L"ПРИМІТКИ\*(R" нижче.
.IP "7. Зміна розмірів логічних томів та інших сховищ у гостьовій системі" 4
.IX Item "7. Зміна розмірів логічних томів та інших сховищ у гостьовій системі"
-(Це завдання можна виконати без завантаження гостьової системи за допомогою
-\&\fBguestfish\fR\|(1))
-.Sp
-Після завантаження гостьової системи у ній має з'явитися вільне місце,
-принаймні для файлових систем, способи зміни розмірів яких відомі
-virt-resize, та фізичних томів. Користувачеві, ймовірно, слід буде змінити
-логічні томи у фізичних томах, а також змінити розміри типів файлових
-систем, способи розширення яких не відомі virt-resize.
+(Це завдання можна виконати без завантаження гостьової системи за допомогою \fBguestfish\fR\|(1))
+.Sp
+Після завантаження гостьової системи у ній має з'явитися вільне місце, принаймні для файлових систем, способи зміни розмірів яких відомі virt-resize, та фізичних томів. Користувачеві, ймовірно, слід буде змінити логічні томи у фізичних томах, а також змінити розміри типів файлових систем, способи розширення яких не відомі virt-resize.
.SS "ЗМЕНШЕННЯ РОЗМІРІВ ДИСКА ВІРТУАЛЬНОЇ МАШИНИ"
.IX Subsection "ЗМЕНШЕННЯ РОЗМІРІВ ДИСКА ВІРТУАЛЬНОЇ МАШИНИ"
-Зменшення розмірів є дещо складнішим завданням за збільшення. У цьому
-розділі наведено лише загальний огляд.
+Зменшення розмірів є дещо складнішим завданням за збільшення. У цьому розділі наведено лише загальний огляд.
.PP
-По\-перше, virt-resize не робитиме спроб стиснути будь\-який вміст розділу
-(фізичні томи, файлові системи). Користувачеві слід подбати про зменшення
-розмірів вмісту до передавання диска на обробку до virt-resize, і
-virt-resize перевірить, чи було стиснено вміст належним чином.
+По\-перше, virt-resize не робитиме спроб стиснути будь\-який вміст розділу (фізичні томи, файлові системи). Користувачеві слід подбати про зменшення розмірів вмісту до передавання диска на обробку до virt-resize, і virt-resize перевірить, чи було стиснено вміст належним чином.
.PP
-(Зменшення розмірів також можна виконати без завантаження системи за
-допомогою \fBguestfish\fR\|(1))
+(Зменшення розмірів також можна виконати без завантаження системи за допомогою \fBguestfish\fR\|(1))
.PP
-Після стискання фізичних томів і файлових систем, вимкніть гостьову систему
-і виконайте описані вище кроки 3 і 4 для розміщення нового образу диска.
+Після стискання фізичних томів і файлових систем, вимкніть гостьову систему і виконайте описані вище кроки 3 і 4 для розміщення нового образу диска.
.PP
-Потім запустіть virt-resize із відповідними параметрами \fI\-\-shrink\fR і/або
-\&\fI\-\-resize\fR.
+Потім запустіть virt-resize із відповідними параметрами \fI\-\-shrink\fR і/або \fI\-\-resize\fR.
.SS "ІГНОРУВАННЯ І ВИЛУЧЕННЯ РОЗДІЛІВ"
.IX Subsection "ІГНОРУВАННЯ І ВИЛУЧЕННЯ РОЗДІЛІВ"
-Крім того, virt-resize надає вам зручний спосіб ігнорувати або вилучати
-розділи при копіюванні з диска вхідних даних на диск вихідних
-даних. Ігнорування розділу пришвидшує копіювання там, де вам все одно що
-станеться із наявним вмістом розділу. Вилучення розділу вилучає його
-повністю, але зауважте, що це також призводить до перенумерування усіх
-розділів після вилучено, що може призвести до неможливості завантаження
-деяких гостьових систем.
+Крім того, virt-resize надає вам зручний спосіб ігнорувати або вилучати розділи при копіюванні з диска вхідних даних на диск вихідних даних. Ігнорування розділу пришвидшує копіювання там, де вам все одно що станеться із наявним вмістом розділу. Вилучення розділу вилучає його повністю, але зауважте, що це також призводить до перенумерування усіх розділів після вилучено, що може призвести до неможливості завантаження деяких гостьових систем.
.SS "\s-1QCOW2\s0 І НЕРОЗРІДЖЕНІ ФОРМАТИ \s-1RAW\s0"
.IX Subsection "QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW"
-Якщо дисх вхідних даних записано у форматі qcow2, ймовірно, варто записати
-вихідні дані теж у форматі qcow2. Крім того, virt-resize може перетворювати
-дані з одного формату на інший «на льоту». Формат виведених даних просто
-визначається форматом порожнього контейнера для виведення даних, який ви
-надасте. Таким чином, щоб записати виведені дані у форматі qcow2,
-скористайтеся такою командою:
+Якщо дисх вхідних даних записано у форматі qcow2, ймовірно, варто записати вихідні дані теж у форматі qcow2. Крім того, virt-resize може перетворювати дані з одного формату на інший «на льоту». Формат виведених даних просто визначається форматом порожнього контейнера для виведення даних, який ви надасте. Таким чином, щоб записати виведені дані у форматі qcow2, скористайтеся такою командою:
.PP
.Vb 1
\& qemu\-img create \-f qcow2 \-o preallocation=metadata outdisk [розмір]
.PP
замість команди truncate.
.PP
-Так само, щоб отримати дані у нерозрідженому простому форматі (raw)
-скористайтеся такою командою:
+Так само, щоб отримати дані у нерозрідженому простому форматі (raw) скористайтеся такою командою:
.PP
.Vb 1
\& fallocate \-l розмір вихідний_диск
.Ve
.PP
-(у застарілих системах, де немає команди \fBfallocate\fR\|(1), скористайтеся
-командою \f(CW\*(C`dd if=/dev/zero of=outdisk bs=1M count=..\*(C'\fR)
+(у застарілих системах, де немає команди \fBfallocate\fR\|(1), скористайтеся командою \f(CW\*(C`dd if=/dev/zero of=outdisk bs=1M count=..\*(C'\fR)
.SS "ЛОГІЧНІ РОЗДІЛИ"
.IX Subsection "ЛОГІЧНІ РОЗДІЛИ"
-Розміри логічних розділів (тобто \fI/dev/sda5+\fR на дисках із таблицею
-розділів \s-1DOS\s0) не може бути змінено.
+Розміри логічних розділів (тобто \fI/dev/sda5+\fR на дисках із таблицею розділів \s-1DOS\s0) не може бути змінено.
.PP
-Щоб розібратися у тому, що відбувається, по\-перше, слід пам'ятати, що один
-із чотирьох розділів \fI/dev/sda1\-4\fR матиме тип розділу \s-1MBR\s0 \f(CW05\fR або
-\&\f(CW\*(C`0f\*(C'\fR. Такий розділ називається \fBрозширеним розділом\fR. Для перегляду типу
-розділу \s-1MBR\s0 скористайтеся \fBvirt\-filesystems\fR\|(1).
+Щоб розібратися у тому, що відбувається, по\-перше, слід пам'ятати, що один із чотирьох розділів \fI/dev/sda1\-4\fR матиме тип розділу \s-1MBR\s0 \f(CW05\fR або \f(CW\*(C`0f\*(C'\fR. Такий розділ називається \fBрозширеним розділом\fR. Для перегляду типу розділу \s-1MBR\s0 скористайтеся \fBvirt\-filesystems\fR\|(1).
.PP
Логічні розділи містяться у розширеному розділі.
.PP
-Розширений розділ може бути збільшено, але не може бути зменшено (це можна
-зробити у примусовому режимі, але ми не радимо так робити). При копіюванні
-розширеного розділу неявним чином копіюються усі логічні розділи, які на
-ньому містяться. Virt-resize не зазирає до розширеного розділу, отже сліпо
-копіює логічні розділи.
+Розширений розділ може бути збільшено, але не може бути зменшено (це можна зробити у примусовому режимі, але ми не радимо так робити). При копіюванні розширеного розділу неявним чином копіюються усі логічні розділи, які на ньому містяться. Virt-resize не зазирає до розширеного розділу, отже сліпо копіює логічні розділи.
.PP
-Вказати логічний розділ (\fI/dev/sda5+\fR) у рядку команди не можна. Якщо ви це
-зробите, програма повідомить про помилку.
+Вказати логічний розділ (\fI/dev/sda5+\fR) у рядку команди не можна. Якщо ви це зробите, програма повідомить про помилку.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-align\-first\fR \fBalways\fR" 4
.IX Item "--align-first always"
.PD
-Вирівняти перший розділ, щоб підвищити швидкодію (див. параметр
-\&\fI\-\-alignment\fR).
-.Sp
-Типовою поведінкою є використання параметра \fI\-\-align\-first auto\fR, який
-вирівнює лише перший розділ, якщо це безпечно робити. Тобто, лише якщо
-програмі достеменно відомо, як виправити завантажувач автоматично, і, у
-поточній версії, лише для гостьових систем Windows.
-.Sp
-\&\fI\-\-align\-first never\fR означає, що пересування першого розділу ніколи не
-відбуватиметься. Це найбезпечніший варіант. Скористайтеся ним, якщо після
-зміни розмірів гостьова система відмовляється завантажуватися.
-.Sp
-\&\fI\-\-align\-first always\fR означає, що завжди відбуватиметься вирівнювання
-першого розділу (якщо його треба вирівнювати). Для деяких гостьових систем
-це може завадити роботи завантажувача, зробивши гостьову систему непридатною
-до завантаження.
+Вирівняти перший розділ, щоб підвищити швидкодію (див. параметр \fI\-\-alignment\fR).
+.Sp
+Типовою поведінкою є використання параметра \fI\-\-align\-first auto\fR, який вирівнює лише перший розділ, якщо це безпечно робити. Тобто, лише якщо програмі достеменно відомо, як виправити завантажувач автоматично, і, у поточній версії, лише для гостьових систем Windows.
+.Sp
+\&\fI\-\-align\-first never\fR означає, що пересування першого розділу ніколи не відбуватиметься. Це найбезпечніший варіант. Скористайтеся ним, якщо після зміни розмірів гостьова система відмовляється завантажуватися.
+.Sp
+\&\fI\-\-align\-first always\fR означає, що завжди відбуватиметься вирівнювання першого розділу (якщо його треба вирівнювати). Для деяких гостьових систем це може завадити роботи завантажувача, зробивши гостьову систему непридатною до завантаження.
.IP "\fB\-\-alignment\fR N" 4
.IX Item "--alignment N"
-Встановити вирівнювання розділів на межу \f(CW\*(C`N\*(C'\fR секторів. Типовою у
-virt-resize < 1.13.19 було межа у 64 сектори. Після цієї версії типове
-значення було змінено на 128 секторів.
+Встановити вирівнювання розділів на межу \f(CW\*(C`N\*(C'\fR секторів. Типовою у virt-resize < 1.13.19 було межа у 64 сектори. Після цієї версії типове значення було змінено на 128 секторів.
.Sp
-Якщо припускати розмір сектора у гостьовій системі у 512 байтів, ось
-придатні значення для цього параметра:
+Якщо припускати розмір сектора у гостьовій системі у 512 байтів, ось придатні значення для цього параметра:
.RS 4
.IP "\fI\-\-alignment 1\fR (512 байтів)" 4
.IX Item "--alignment 1 (512 байтів)"
-Розділи буде розташовано поруч один із одним якомога ближче, але буде не
-вирівняно. У деяких випадках це може призвести до жахливої втрати
-швидкодії. Докладніший опис можна знайти на сторінці підручника щодо
-\&\fBvirt\-alignment\-scan\fR\|(1).
+Розділи буде розташовано поруч один із одним якомога ближче, але буде не вирівняно. У деяких випадках це може призвести до жахливої втрати швидкодії. Докладніший опис можна знайти на сторінці підручника щодо \fBvirt\-alignment\-scan\fR\|(1).
.IP "\fI\-\-alignment 8\fR (4K)" 4
.IX Item "--alignment 8 (4K)"
-Це мінімальне прийнятне вирівнювання для придатного значення швидкодії на
-сучасних основних системах.
+Це мінімальне прийнятне вирівнювання для придатного значення швидкодії на сучасних основних системах.
.IP "\fI\-\-alignment 128\fR (64K)" 4
.IX Item "--alignment 128 (64K)"
-Таке вирівнювання надасть змогу скористатися непоганою швидкодією, якщо
-основна система зберігається на високоякісних носіях для мережі.
+Таке вирівнювання надасть змогу скористатися непоганою швидкодією, якщо основна система зберігається на високоякісних носіях для мережі.
.IP "\fI\-\-alignment 2048\fR (1M)" 4
.IX Item "--alignment 2048 (1M)"
-Це стандартне вирівнювання, яке використовується в усіх нововстановлених
-гостьових системах з приблизно 2008 року.
+Це стандартне вирівнювання, яке використовується в усіх нововстановлених гостьових системах з приблизно 2008 року.
.RE
.RS 4
.RE
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-d\fR" 4
.IX Item "-d"
.PD 0
Увімкнути показ діагностичних повідомлень.
.IP "\fB\-\-delete\fR РОЗДІЛ" 4
.IX Item "--delete РОЗДІЛ"
-Вилучити вказаний за назвою розділ. Точнішим визначенням цієї дії буде «не
-копіювати», оскільки virt-resize не вносить зміни до початкового образу
-диска.
+Вилучити вказаний за назвою розділ. Точнішим визначенням цієї дії буде «не копіювати», оскільки virt-resize не вносить зміни до початкового образу диска.
.Sp
-Зауважте, що коли ви вилучаєте розділ, вилучаються і усі дані, які
-зберігалися на ньому. Більше того, у результаті усі розділи за вилученим
-\&\fIперенумеровуються\fR, що може призвести до неможливості завантаження
-гостьової системи.
+Зауважте, що коли ви вилучаєте розділ, вилучаються і усі дані, які зберігалися на ньому. Більше того, у результаті усі розділи за вилученим \fIперенумеровуються\fR, що може призвести до неможливості завантаження гостьової системи.
.Sp
Цей параметр можна вказувати декілька разів.
.IP "\fB\-\-expand\fR РОЗДІЛ" 4
.IX Item "--expand РОЗДІЛ"
-Розширити вказаний за назвою розділ так, щоб він зайняв усе вільне місце
-(місце, яке лишатиметься вільним після усіх інших вказаних вами змін у
-розмірах).
+Розширити вказаний за назвою розділ так, щоб він зайняв усе вільне місце (місце, яке лишатиметься вільним після усіх інших вказаних вами змін у розмірах).
.Sp
-Якщо virt-resize відомий спосіб, програма розширить безпосередній вміст
-розділу. Наприклад, якщо розділ є фізичним томом \s-1LVM,\s0 програма розширить
-фізичний том так, щоб він зайняв усе місце (подібно до виклику
-\&\fBpvresize\fR\|(8)). Якщо спосіб розширення виявиться невідомим virt-resize,
-програма не чіпатиме вмісту розділу.
+Якщо virt-resize відомий спосіб, програма розширить безпосередній вміст розділу. Наприклад, якщо розділ є фізичним томом \s-1LVM,\s0 програма розширить фізичний том так, щоб він зайняв усе місце (подібно до виклику \fBpvresize\fR\|(8)). Якщо спосіб розширення виявиться невідомим virt-resize, програма не чіпатиме вмісту розділу.
.Sp
У поточній версії virt-resize може змінювати розміри таких файлових систем:
.RS 4
.IP "\(bu" 4
Файлових систем \s-1NTFS,\s0 якщо libguestfs було зібрано з підтримкою \s-1NTFS.\s0
.Sp
-Роботу файлової системи під час її останнього використання має бути
-завершено у штатному режимі. Крім того, \fBntfsresize\fR\|(8) позначає файлові
-системи зі зміненими розмірами як такі, що потребують перевірки, отже під
-час першого наступного запуску Windows на розділі зі зміненим розміром буде
-виконано перевірку диска.
+Роботу файлової системи під час її останнього використання має бути завершено у штатному режимі. Крім того, \fBntfsresize\fR\|(8) позначає файлові системи зі зміненими розмірами як такі, що потребують перевірки, отже під час першого наступного запуску Windows на розділі зі зміненим розміром буде виконано перевірку диска.
.IP "\(bu" 4
-Фізичні томи \s-1LVM.\s0 Зазвичай, virt-resize не змінює розміри вмісту фізичних
-томів, втім, див. параметр \fI\-\-LV\-expand\fR. Користувач також може змінити
-розміри логічних томів бажаним чином після завантаження системи.
+Фізичні томи \s-1LVM.\s0 Зазвичай, virt-resize не змінює розміри вмісту фізичних томів, втім, див. параметр \fI\-\-LV\-expand\fR. Користувач також може змінити розміри логічних томів бажаним чином після завантаження системи.
.IP "\(bu" 4
Файлові системи btrfs, якщо libguestfs було зібрано із підтримкою btrfs.
.IP "\(bu" 4
.IP "\(bu" 4
Розділи резервної пам'яті на диску Linux.
.Sp
-Будь ласка, зауважте, що libguestfs \fIзнищує\fR наявний вміст розділу
-резервної пам'яті на диску, відтворюючи його за допомогою \f(CW\*(C`mkswap\*(C'\fR, тому
-такі розділи не слід використовувати, якщо гостьова система присипляється.
+Будь ласка, зауважте, що libguestfs \fIзнищує\fR наявний вміст розділу резервної пам'яті на диску, відтворюючи його за допомогою \f(CW\*(C`mkswap\*(C'\fR, тому такі розділи не слід використовувати, якщо гостьова система присипляється.
.IP "\(bu" 4
Файлові системи f2fs, якщо libguestfs було зібрано із підтримкою f2fs.
.RE
.RS 4
.Sp
-Зауважте, що параметри \fI\-\-expand\fR і \fI\-\-shrink\fR не можна використовувати у
-одній і тій самій команді.
+Зауважте, що параметри \fI\-\-expand\fR і \fI\-\-shrink\fR не можна використовувати у одній і тій самій команді.
.RE
.IP "\fB\-\-format\fR \fBraw\fR" 4
.IX Item "--format raw"
-Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано,
-його буде автоматично визначено на основі даних самого образу.
+Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого образу.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.Sp
-Зауважте, що цей параметр \fIне\fR впливає на формат виведених
-даних. Див. \*(L"\s-1QCOW2\s0 І НЕРОЗРІДЖЕНІ ФОРМАТИ \s-1RAW\*(R"\s0.
+Зауважте, що цей параметр \fIне\fR впливає на формат виведених даних. Див. \*(L"\s-1QCOW2\s0 І НЕРОЗРІДЖЕНІ ФОРМАТИ \s-1RAW\*(R"\s0.
.IP "\fB\-\-ignore\fR РОЗДІЛ" 4
.IX Item "--ignore РОЗДІЛ"
-Ігнорувати вказаний за назвою розділ. По суті, це означає, що розділ
-розміщується на диску призначення, але його вміст з початкового диска не
-копіюється. Розділ лишатиметься порожнім (заповненим нулями).
+Ігнорувати вказаний за назвою розділ. По суті, це означає, що розділ розміщується на диску призначення, але його вміст з початкового диска не копіюється. Розділ лишатиметься порожнім (заповненим нулями).
.Sp
Цей параметр можна вказувати декілька разів.
.IP "\fB\-\-LV\-expand\fR ЛОГІЧНИЙ_ТОМ" 4
.IX Item "--LV-expand ЛОГІЧНИЙ_ТОМ"
-Цій команді передається логічний том і, як останній крок, вона розширює цей
-том так, щоб він зайняв усе вільне місце, яке доступне у групі
-томів. Типовим використанням, якщо припускати, що ви працюєте із гостьовою
-системою Linux із єдиним фізичним томом \s-1PV\s0 \fI/dev/sda2\fR і кореневим
-пристроєм із назвою \fI/dev/vg_guest/lv_root\fR, є:
+Цій команді передається логічний том і, як останній крок, вона розширює цей том так, щоб він зайняв усе вільне місце, яке доступне у групі томів. Типовим використанням, якщо припускати, що ви працюєте із гостьовою системою Linux із єдиним фізичним томом \s-1PV\s0 \fI/dev/sda2\fR і кореневим пристроєм із назвою \fI/dev/vg_guest/lv_root\fR, є:
.Sp
.Vb 2
\& virt\-resize indisk outdisk \e
\& \-\-expand /dev/sda2 \-\-LV\-expand /dev/vg_guest/lv_root
.Ve
.Sp
-Ця команда спершу розширить розділ (і фізичний том), а потім розширить
-кореневий пристрій так, що він займе усе наявне зайве місце на фізичному
-томі.
+Ця команда спершу розширить розділ (і фізичний том), а потім розширить кореневий пристрій так, що він займе усе наявне зайве місце на фізичному томі.
.Sp
-Розмір вмісту логічного тому також буде змінено, якщо virt-resize відомий
-спосіб, як це зробити. Ви можете заборонити virt-resize змінювати розміри
-вмісту за допомогою параметра \fI\-\-no\-expand\-content\fR.
+Розмір вмісту логічного тому також буде змінено, якщо virt-resize відомий спосіб, як це зробити. Ви можете заборонити virt-resize змінювати розміри вмісту за допомогою параметра \fI\-\-no\-expand\-content\fR.
.Sp
-Скористайтеся \fBvirt\-filesystems\fR\|(1) для отримання списку файлових систем у
-гостьовій системі.
+Скористайтеся \fBvirt\-filesystems\fR\|(1) для отримання списку файлових систем у гостьовій системі.
.Sp
-Ви можете вказати у одній команді цей параметр декілька разів, \fIале\fR сенсу
-у цьому небагато, хіба що вказані вами логічні томи належать до різних груп
-томів.
+Ви можете вказати у одній команді цей параметр декілька разів, \fIале\fR сенсу у цьому небагато, хіба що вказані вами логічні томи належать до різних груп томів.
.IP "\fB\-\-machine\-readable\fR" 4
.IX Item "--machine-readable"
.PD 0
.IP "\fB\-\-machine\-readable\fR=формат" 4
.IX Item "--machine-readable=формат"
.PD
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
.IP "\fB\-n\fR" 4
.IX Item "-n"
.PD 0
Вивести резюме щодо дій, але не виконувати ці дії.
.IP "\fB\-\-no\-copy\-boot\-loader\fR" 4
.IX Item "--no-copy-boot-loader"
-Типово, virt-resize копіює деякі сектори на початку диска (аж до початку
-першого розділу). Найчастіше, у цих секторах міститься Master Boot Record
-(\s-1MBR\s0) та завантажувач. Вони потрібні для того, щоб гостьова система
-завантажувалася належним чином.
-.Sp
-Якщо ви вкажете цей прапорець, це початкове копіювання не
-виконуватиметься. У цьому випадку може виникнути потреба у перевстановленні
-завантажувача.
+Типово, virt-resize копіює деякі сектори на початку диска (аж до початку першого розділу). Найчастіше, у цих секторах міститься Master Boot Record (\s-1MBR\s0) та завантажувач. Вони потрібні для того, щоб гостьова система завантажувалася належним чином.
+.Sp
+Якщо ви вкажете цей прапорець, це початкове копіювання не виконуватиметься. У цьому випадку може виникнути потреба у перевстановленні завантажувача.
.IP "\fB\-\-no\-extra\-partition\fR" 4
.IX Item "--no-extra-partition"
-Типово, virt-resize створює додатковий розділ, якщо буде виявлено зайве
-невикористане місце після усіх змін розмірів. Скористайтеся цим параметром
-для того, щоб запобігти створенню цього додаткового розділу. Якщо ви так
-зробите, зайве місце буде недоступним, аж доки ви не запустите fdisk, parted
-або якийсь інший інструмент поділу на розділи у гостьовій системі.
-.Sp
-Зауважте, що якщо зайвого місця виявиться менше за 10 МБ, додатковий розділ
-не створюватиметься.
+Типово, virt-resize створює додатковий розділ, якщо буде виявлено зайве невикористане місце після усіх змін розмірів. Скористайтеся цим параметром для того, щоб запобігти створенню цього додаткового розділу. Якщо ви так зробите, зайве місце буде недоступним, аж доки ви не запустите fdisk, parted або якийсь інший інструмент поділу на розділи у гостьовій системі.
+.Sp
+Зауважте, що якщо зайвого місця виявиться менше за 10 МБ, додатковий розділ не створюватиметься.
.IP "\fB\-\-no\-expand\-content\fR" 4
.IX Item "--no-expand-content"
-Типово, virt-resize намагатиметься розширити безпосередній вміст розділів,
-якщо програмі відомий спосіб виконати таке розширення (див. параметр
-\&\fI\-\-expand\fR вище).
+Типово, virt-resize намагатиметься розширити безпосередній вміст розділів, якщо програмі відомий спосіб виконати таке розширення (див. параметр \fI\-\-expand\fR вище).
.Sp
-Якщо ви вкажете параметр \fI\-\-no\-expand\-content\fR, virt-resize не виконуватиме
-таких спроб.
+Якщо ви вкажете параметр \fI\-\-no\-expand\-content\fR, virt-resize не виконуватиме таких спроб.
.IP "\fB\-\-no\-sparse\fR" 4
.IX Item "--no-sparse"
Вимкнути розріджене копіювання. Див. \*(L"РОЗРІДЖЕНЕ КОПІЮВАННЯ\*(R" нижче.
.IP "\fB\-\-ntfsresize\-force\fR" 4
.IX Item "--ntfsresize-force"
-Передавання параметра \fI\-\-force\fR до \fBntfsresize\fR\|(8) уможливить зміну
-розмірів, навіть якщо диск \s-1NTFS\s0 буде позначено як такий, що потребує
-перевірки коректності. Вам доведеться скористатися цим параметром, якщо ви
-хочете змінити розміри гостьової системи Windows без потреби у завантаженні
-Windows кожного разу між командами зміни розмірів.
+Передавання параметра \fI\-\-force\fR до \fBntfsresize\fR\|(8) уможливить зміну розмірів, навіть якщо диск \s-1NTFS\s0 буде позначено як такий, що потребує перевірки коректності. Вам доведеться скористатися цим параметром, якщо ви хочете змінити розміри гостьової системи Windows без потреби у завантаженні Windows кожного разу між командами зміни розмірів.
.IP "\fB\-\-output\-format\fR \fBraw\fR" 4
.IX Item "--output-format raw"
-Визначає формат виведеного образу диска. Якщо цей прапорець не вказано,
-формат буде автоматично визначено на основі даних щодо образу диска.
+Визначає формат виведеного образу диска. Якщо цей прапорець не вказано, формат буде автоматично визначено на основі даних щодо образу диска.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.Sp
-Зауважте, що цей параметр \fIне створює\fR образ диска у визначеному
-форматі. Цей параметр призначено лише для того, щоб libguestfs не намагалася
-вгадати формат. Створити диск у належному форматі маєте ви
-самі. Див. \*(L"\s-1QCOW2\s0 І НЕРОЗРІДЖЕНІ ФОРМАТИ \s-1RAW\*(R"\s0.
+Зауважте, що цей параметр \fIне створює\fR образ диска у визначеному форматі. Цей параметр призначено лише для того, щоб libguestfs не намагалася вгадати формат. Створити диск у належному форматі маєте ви самі. Див. \*(L"\s-1QCOW2\s0 І НЕРОЗРІДЖЕНІ ФОРМАТИ \s-1RAW\*(R"\s0.
.IP "\fB\-q\fR" 4
.IX Item "-q"
.PD 0
Не виводити резюме.
.IP "\fB\-\-resize\fR РОЗДІЛ=РОЗМІР" 4
.IX Item "--resize РОЗДІЛ=РОЗМІР"
-Змінити розмір вказаного за назвою розділу (розширити або стиснути його)
-так, щоб він мав вказаний розмір.
+Змінити розмір вказаного за назвою розділу (розширити або стиснути його) так, щоб він мав вказаний розмір.
.Sp
-\&\f(CW\*(C`РОЗМІР\*(C'\fR можна вказати як значення за модулем із додаванням суфікса b/K/M/G
-на позначення байтів, кілобайтів, мегабайтів або гігабайтів, або як відсоток
-від поточного розміру, або як відносну частку. Приклад:
+\&\f(CW\*(C`РОЗМІР\*(C'\fR можна вказати як значення за модулем із додаванням суфікса b/K/M/G на позначення байтів, кілобайтів, мегабайтів або гігабайтів, або як відсоток від поточного розміру, або як відносну частку. Приклад:
.Sp
.Vb 1
\& \-\-resize /dev/sda2=10G
\& \-\-resize /dev/sda1=\-10%
.Ve
.Sp
-Ви можете збільшити розмір будь\-якого розділу. Virt-resize розширить
-безпосередній вміст розділу, якщо програмі відомий спосіб виконати таке
-розширення (див. \fI\-\-expand\fR вище).
+Ви можете збільшити розмір будь\-якого розділу. Virt-resize розширить безпосередній вміст розділу, якщо програмі відомий спосіб виконати таке розширення (див. \fI\-\-expand\fR вище).
.Sp
-\&\fIЗменшити\fR розмір розділів, які містять файлові системи або фізичні томи,
-можна лише якщо ці файлові системи або фізичні томи вже зменшено у розмірах
-всередині розділу. Virt-resize виконає перевірку виконання цієї умови до
-того, як розпочне обробку даних. Якщо умову не виконано, програма повідомить
-про помилку (див. також \fI\-\-resize\-force\fR).
+\&\fIЗменшити\fR розмір розділів, які містять файлові системи або фізичні томи, можна лише якщо ці файлові системи або фізичні томи вже зменшено у розмірах всередині розділу. Virt-resize виконає перевірку виконання цієї умови до того, як розпочне обробку даних. Якщо умову не виконано, програма повідомить про помилку (див. також \fI\-\-resize\-force\fR).
.Sp
Цей параметр можна вказувати декілька разів.
.IP "\fB\-\-resize\-force\fR РОЗДІЛ=РОЗМІР" 4
.IX Item "--resize-force РОЗДІЛ=РОЗМІР"
-Це те саме, що і \fI\-\-resize\fR, але із можливістю зменшувати розміри будь\-яких
-розділів. Загалом, це означає, що ви можете втратити якісь дані, які
-зберігалися наприкінці зменшуваного розділу, але, можливо, ви цим не
-переймаєтеся (наприклад, якщо зменшуєте розмір невикористаного розділу або
-можете легко відтворити вміст розділу, зокрема розділу резервної пам'яті на
-диску).
+Це те саме, що і \fI\-\-resize\fR, але із можливістю зменшувати розміри будь\-яких розділів. Загалом, це означає, що ви можете втратити якісь дані, які зберігалися наприкінці зменшуваного розділу, але, можливо, ви цим не переймаєтеся (наприклад, якщо зменшуєте розмір невикористаного розділу або можете легко відтворити вміст розділу, зокрема розділу резервної пам'яті на диску).
.Sp
Див. також опис параметра \fI\-\-ignore\fR.
.IP "\fB\-\-shrink\fR РОЗДІЛ" 4
.IX Item "--shrink РОЗДІЛ"
-Зменшити вказаний за назвою розділ у розмірах так, щоб увесь образ диска
-вмістився у образ призначення. Вказаний за назвою розділ \fBмає\fR містити
-файлову систему або фізичний том, які вже було зменшено у розмірах за
-допомогою іншого засобу (наприклад \fBguestfish\fR\|(1) або інших
-програм). Virt-resize виконає перевірку виконання цієї умови і повідомить
-про помилку, якщо попереднього зменшення файлової системи або фізичного тому
-не виконано.
-.Sp
-Об'єм, на який має бути зменшено увесь диск (після виконання усіх інших дій,
-вказаних користувачем), називається «дефіцитом». Наприклад, просте
-копіювання (якщо не виконується жодних інших дій) з образу диска у 5 ГБ на
-образ диска у 4 ГБ дає дефіцит у 1 ГБ. У цьому випадку virt-resize
-повідомить про помилку, якщо користувач не вказав такий розділ для
-стискання, на якому є понад гігабайт вільного місця.
-.Sp
-Зауважте, що параметри \fI\-\-expand\fR і \fI\-\-shrink\fR не можна використовувати у
-одній і тій самій команді.
+Зменшити вказаний за назвою розділ у розмірах так, щоб увесь образ диска вмістився у образ призначення. Вказаний за назвою розділ \fBмає\fR містити файлову систему або фізичний том, які вже було зменшено у розмірах за допомогою іншого засобу (наприклад \fBguestfish\fR\|(1) або інших програм). Virt-resize виконає перевірку виконання цієї умови і повідомить про помилку, якщо попереднього зменшення файлової системи або фізичного тому не виконано.
+.Sp
+Об'єм, на який має бути зменшено увесь диск (після виконання усіх інших дій, вказаних користувачем), називається «дефіцитом». Наприклад, просте копіювання (якщо не виконується жодних інших дій) з образу диска у 5 ГБ на образ диска у 4 ГБ дає дефіцит у 1 ГБ. У цьому випадку virt-resize повідомить про помилку, якщо користувач не вказав такий розділ для стискання, на якому є понад гігабайт вільного місця.
+.Sp
+Зауважте, що параметри \fI\-\-expand\fR і \fI\-\-shrink\fR не можна використовувати у одній і тій самій команді.
.IP "\fB\-\-unknown\-filesystems\fR \fBignore\fR" 4
.IX Item "--unknown-filesystems ignore"
.PD 0
.IP "\fB\-\-unknown\-filesystems\fR \fBerror\fR" 4
.IX Item "--unknown-filesystems error"
.PD
-Налаштувати поведінку virt-resize, якщо програмі надійшла команда розширити
-файлову систему, а у libguestfs не передбачено її підтримки і virt-resize не
-знає способу, як розширити вміст файлової системи.
+Налаштувати поведінку virt-resize, якщо програмі надійшла команда розширити файлову систему, а у libguestfs не передбачено її підтримки і virt-resize не знає способу, як розширити вміст файлової системи.
.Sp
-Використання параметра \fI\-\-unknown\-filesystems ignore\fR призведе до того, що
-virt-resize без додаткових повідомлень ігноруватиме такі файлові системи і
-нічого не виводитиме щодо них.
+Використання параметра \fI\-\-unknown\-filesystems ignore\fR призведе до того, що virt-resize без додаткових повідомлень ігноруватиме такі файлові системи і нічого не виводитиме щодо них.
.Sp
-Використання параметра \fI\-\-unknown\-filesystems warn\fR (типове поведінка)
-призводитиме до того, що virt-resize попереджатиме про кожну файлову
-систему, яку не може бути розширено, але продовжуватиме зміну розмірів
-розділів на диску.
+Використання параметра \fI\-\-unknown\-filesystems warn\fR (типове поведінка) призводитиме до того, що virt-resize попереджатиме про кожну файлову систему, яку не може бути розширено, але продовжуватиме зміну розмірів розділів на диску.
.Sp
-Використання параметра \fI\-\-unknown\-filesystems error\fR призведе до того, що
-virt-resize повідомлятиме про помилку, якщо виявить файлову систему, розміри
-якої не можна збільшити.
+Використання параметра \fI\-\-unknown\-filesystems error\fR призведе до того, що virt-resize повідомлятиме про помилку, якщо виявить файлову систему, розміри якої не можна збільшити.
.Sp
-Див. також \*(L"unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem
-on \s-1DEVICE/LV\*(R"\s0.
+Див. також \*(L"unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV\*(R"\s0.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.SH "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
.IX Header "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра
-робить зручним використання virt-resize з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра робить зручним використання virt-resize з інших програм, графічних інтерфейсів тощо.
.PP
Існує два способи використання цього параметра.
.PP
-По\-перше, можна скористатися ним без інших параметрів для того, щоб
-дізнатися про можливості виконуваного файла virt-resize. Типові виведені
-дані виглядатимуть так:
+По\-перше, можна скористатися ним без інших параметрів для того, щоб дізнатися про можливості виконуваного файла virt-resize. Типові виведені дані виглядатимуть так:
.PP
.Vb 6
\& $ virt\-resize \-\-machine\-readable
\& btrfs
.Ve
.PP
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
.PP
-По\-друге, можна скористатися цим параметром у поєднанні із іншими
-параметрами для того, щоб зробити звичайні виведені програмою дані
-придатнішими для подальшої машинної обробки.
+По\-друге, можна скористатися цим параметром у поєднанні із іншими параметрами для того, щоб зробити звичайні виведені програмою дані придатнішими для подальшої машинної обробки.
.PP
У поточній версії це означає таке:
.IP "1." 4
-Повідомлення смужки поступу можна обробляти зі стандартного виведення,
-шукаючи їх за таким формальним виразом:
+Повідомлення смужки поступу можна обробляти зі стандартного виведення, шукаючи їх за таким формальним виразом:
.Sp
.Vb 1
\& ^[0\-9]+/[0\-9]+$
.Ve
.IP "2." 4
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення
-щодо стану. Ці повідомлення може бути записано до журналу і/або показано
-користувачеві.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення щодо стану. Ці повідомлення може бути записано до журналу і/або показано користувачеві.
.IP "3." 4
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-stderr як повідомлення про помилки. Крім того, virt-resize завершує роботу
-із ненульовим кодом стану, якщо станеться критична помилка.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до stderr як повідомлення про помилки. Крім того, virt-resize завершує роботу із ненульовим кодом стану, якщо станеться критична помилка.
.PP
-У версіях програми до 1.13.9 не передбачено використання параметра
-\&\fI\-\-machine\-readable\fR. Якщо цей параметр буде використано для такої версії,
-програма поверне повідомлення про помилку.
+У версіях програми до 1.13.9 не передбачено використання параметра \fI\-\-machine\-readable\fR. Якщо цей параметр буде використано для такої версії, програма поверне повідомлення про помилку.
.PP
-Можна вказати рядок форматування для керування виведенням,
-див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
+Можна вказати рядок форматування для керування виведенням, див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
.SH "ПРИМІТКИ"
.IX Header "ПРИМІТКИ"
.SS "«Розділ 1 не закінчується на межі циліндра.»"
.IX Subsection "«Розділ 1 не закінчується на межі циліндра.»"
-Virt-resize вирівнює розділи на позиції, кратні до 128 секторів
-(див. параметр \fI\-\-alignment\fR). Зазвичай, це означає, що розділи не буде
-вирівняно за давньою геометрією \s-1CHS\s0 (циліндр\-голівка\-сектор). Втім,
-геометрія \s-1CHS\s0 не має сенсу для дисків, які вироблено після ранніх 1990\-х, і
-зовсім не має сенсу для віртуальних жорстких дисків. Вирівнювання розділів
-за циліндрами не є вимогою жодної сучасної операційної системи.
+Virt-resize вирівнює розділи на позиції, кратні до 128 секторів (див. параметр \fI\-\-alignment\fR). Зазвичай, це означає, що розділи не буде вирівняно за давньою геометрією \s-1CHS\s0 (циліндр\-голівка\-сектор). Втім, геометрія \s-1CHS\s0 не має сенсу для дисків, які вироблено після ранніх 1990\-х, і зовсім не має сенсу для віртуальних жорстких дисків. Вирівнювання розділів за циліндрами не є вимогою жодної сучасної операційної системи.
.SS "ЗАВАНТАЖЕННЯ ГОСТЬОВОЇ СИСТЕМИ ЗУПИНЯЄТЬСЯ НА «GRUB»"
.IX Subsection "ЗАВАНТАЖЕННЯ ГОСТЬОВОЇ СИСТЕМИ ЗУПИНЯЄТЬСЯ НА «GRUB»"
-Якщо гостьова система Linux не завантажується після зміни розміру, і
-завантаження зупиняється після виведення слова \f(CW\*(C`GRUB\*(C'\fR до консолі, спробуйте
-перевстановити grub.
+Якщо гостьова система Linux не завантажується після зміни розміру, і завантаження зупиняється після виведення слова \f(CW\*(C`GRUB\*(C'\fR до консолі, спробуйте перевстановити grub.
.PP
.Vb 6
\& guestfish \-i \-a newdisk
\& ><fs> exit
.Ve
.PP
-Для гнучкішого переналаштовування гостьової системи, зокрема випадків, коли
-вам потрібно вказати інші параметри grub-install, скористайтеся
-\&\fBvirt\-rescue\fR\|(1).
+Для гнучкішого переналаштовування гостьової системи, зокрема випадків, коли вам потрібно вказати інші параметри grub-install, скористайтеся \fBvirt\-rescue\fR\|(1).
.SS "ЗМІНА РОЗМІРІВ ЗАВАНТАЖУВАЛЬНИХ РОЗДІЛІВ \s-1WINDOWS\s0"
.IX Subsection "ЗМІНА РОЗМІРІВ ЗАВАНТАЖУВАЛЬНИХ РОЗДІЛІВ WINDOWS"
-У Windows Vista і новіших версіях компанія Microsoft перейшла до
-використання окремого розділу завантаження. У віртуальних машинах із цими
-операційними системами, типово, \fI/dev/sda1\fR є розділом завантаження, а
-\&\fI/dev/sda2\fR є основним диском (C:). Зміна розмірів першого розділу (розділу
-завантаження) спричиняє помилку завантажувача \f(CW0xC0000225\fR. Зміна розмірів
-другого розділу (тобто диска C:) має працювати.
+У Windows Vista і новіших версіях компанія Microsoft перейшла до використання окремого розділу завантаження. У віртуальних машинах із цими операційними системами, типово, \fI/dev/sda1\fR є розділом завантаження, а \fI/dev/sda2\fR є основним диском (C:). Зміна розмірів першого розділу (розділу завантаження) спричиняє помилку завантажувача \f(CW0xC0000225\fR. Зміна розмірів другого розділу (тобто диска C:) має працювати.
.SS "\s-1WINDOWS CHKDSK\s0"
.IX Subsection "WINDOWS CHKDSK"
-Диск Windows, на якому використовується \s-1NTFS,\s0 має бути коректним, перш ніж
-virt-resize зможе ним скористатися. Якщо спроба виконати дію ntfsresize
-завершиться повідомленням про помилку, спробуйте завантажити початкову
-віртуальну машину і запустіть \f(CW\*(C`chkdsk /f\*(C'\fR для усіх розділів \s-1NTFS,\s0 потім
-завершіть роботу віртуальної машини у штатний спосіб. Докладнішу інформацію
-наведено тут: https://bugzilla.redhat.com/show_bug.cgi?id=975753
-.PP
-\&\fIПісля зміни розмірів\fR Windows може ініціювати тривалу обробку chkdsk при
-першому завантаженні, якщо було розширено розділи \s-1NTFS.\s0 Це усього лише для
-забезпечення надійного зберігання даних, і (якщо не буде знайдено помилок)
-ви можете бути спокійні.
+Диск Windows, на якому використовується \s-1NTFS,\s0 має бути коректним, перш ніж virt-resize зможе ним скористатися. Якщо спроба виконати дію ntfsresize завершиться повідомленням про помилку, спробуйте завантажити початкову віртуальну машину і запустіть \f(CW\*(C`chkdsk /f\*(C'\fR для усіх розділів \s-1NTFS,\s0 потім завершіть роботу віртуальної машини у штатний спосіб. Докладнішу інформацію наведено тут: https://bugzilla.redhat.com/show_bug.cgi?id=975753
+.PP
+\&\fIПісля зміни розмірів\fR Windows може ініціювати тривалу обробку chkdsk при першому завантаженні, якщо було розширено розділи \s-1NTFS.\s0 Це усього лише для забезпечення надійного зберігання даних, і (якщо не буде знайдено помилок) ви можете бути спокійні.
.SS "СИНІЙ ЕКРАН СМЕРТІ \s-1UNMOUNTABLE_BOOT_VOLUME\s0 У \s-1WINDOWS\s0"
.IX Subsection "СИНІЙ ЕКРАН СМЕРТІ UNMOUNTABLE_BOOT_VOLUME У WINDOWS"
-Після приготування системи гостьової операційної системи Windows із
-наступною зміною її розміру за допомогою virt-resize ви можете отримати
-непридатну до завантаження систему, яка показуватиме синій екран смерті із
-помилкою \f(CW\*(C`UNMOUNTABLE_BOOT_VOLUME\*(C'\fR. Цю помилку спричинено наявністю рядка
-\&\f(CW\*(C`ExtendOemPartition=1\*(C'\fR у файлі sysprep.inf. Якщо вилучити цей рядок до
-обробки sysprep, проблема зникає.
+Після приготування системи гостьової операційної системи Windows із наступною зміною її розміру за допомогою virt-resize ви можете отримати непридатну до завантаження систему, яка показуватиме синій екран смерті із помилкою \f(CW\*(C`UNMOUNTABLE_BOOT_VOLUME\*(C'\fR. Цю помилку спричинено наявністю рядка \f(CW\*(C`ExtendOemPartition=1\*(C'\fR у файлі sysprep.inf. Якщо вилучити цей рядок до обробки sysprep, проблема зникає.
.SS "\s-1WINDOWS 8\s0"
.IX Subsection "WINDOWS 8"
-«Швидкий запуск» Windows 8 може заважати virt-resize змінювати розмір
-розділів \s-1NTFS.\s0 Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК
-\&\s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
+«Швидкий запуск» Windows 8 може заважати virt-resize змінювати розмір розділів \s-1NTFS.\s0 Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК \s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
.SS "РОЗРІДЖЕНЕ КОПІЮВАННЯ"
.IX Subsection "РОЗРІДЖЕНЕ КОПІЮВАННЯ"
-Вам слід створити новий, заповнений нулями образ диска призначення, який
-використовуватиме virt-resize.
-.PP
-Virt-resize типово виконує розріджене копіювання. Це означає, що програма не
-копіює ті блоки з початкового диска, які заповнено лише нулями. Це підвищує
-швидкість та ефективність роботи, але може призвести до некоректних
-результатів, якщо на образі диска призначення є незанулені дані.
-.PP
-В основному, така проблема виникає, якщо образом призначення є розділ
-основної системи (наприклад, \f(CW\*(C`virt\-resize source.img /dev/sda4\*(C'\fR),
-оскільки звичайні інструменти поділу диска на розділи лишають недоторканними
-усі дані, які раніше зберігалися на диску.
-.PP
-Якщо ви змушені використатися образ призначення, на якому вже зберігалися
-дані, вам слід скористатися параметром \fI\-\-no\-sparse\fR. Зауважте, що це
-значно уповільнить роботу програми.
+Вам слід створити новий, заповнений нулями образ диска призначення, який використовуватиме virt-resize.
+.PP
+Virt-resize типово виконує розріджене копіювання. Це означає, що програма не копіює ті блоки з початкового диска, які заповнено лише нулями. Це підвищує швидкість та ефективність роботи, але може призвести до некоректних результатів, якщо на образі диска призначення є незанулені дані.
+.PP
+В основному, така проблема виникає, якщо образом призначення є розділ основної системи (наприклад, \f(CW\*(C`virt\-resize source.img /dev/sda4\*(C'\fR), оскільки звичайні інструменти поділу диска на розділи лишають недоторканними усі дані, які раніше зберігалися на диску.
+.PP
+Якщо ви змушені використатися образ призначення, на якому вже зберігалися дані, вам слід скористатися параметром \fI\-\-no\-sparse\fR. Зауважте, що це значно уповільнить роботу програми.
.ie n .SS """unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV""\s0"
.el .SS "``unknown/unavailable method for expanding the \s-1TYPE\s0 filesystem on \s-1DEVICE/LV''\s0"
.IX Subsection "unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV"
-Virt-resize було наказано розширити розділ або логічний том, на якому
-міститься файлова система типу \f(CW\*(C`TYPE\*(C'\fR, але програмі недоступний або
-невідомий спосіб розширення цієї файлової системи.
+Virt-resize було наказано розширити розділ або логічний том, на якому міститься файлова система типу \f(CW\*(C`TYPE\*(C'\fR, але програмі недоступний або невідомий спосіб розширення цієї файлової системи.
.PP
Причиною може бути будь\-що із наведеного нижче:
.IP "1." 4
-Відповідна файлова система недоступна у libguestfs, оскільки у основній
-системі немає належного пакунка із інструментами для роботи з цією файловою
-системою. Таке, зазвичай, трапляється із файловими системами \f(CW\*(C`btrfs\*(C'\fR,
-\&\f(CW\*(C`ntfs\*(C'\fR, \f(CW\*(C`xfs\*(C'\fR та \f(CW\*(C`f2fs\*(C'\fR.
+Відповідна файлова система недоступна у libguestfs, оскільки у основній системі немає належного пакунка із інструментами для роботи з цією файловою системою. Таке, зазвичай, трапляється із файловими системами \f(CW\*(C`btrfs\*(C'\fR, \f(CW\*(C`ntfs\*(C'\fR, \f(CW\*(C`xfs\*(C'\fR та \f(CW\*(C`f2fs\*(C'\fR.
.Sp
Спробуйте такі команди:
.Sp
\& guestfish \-a /dev/null run : filesystem_available TYPE
.Ve
.Sp
-У цьому випадку достатньо встановити належні пакунки із підтримкою файлових
-систем. Наприклад, достатньо встановити \f(CW\*(C`libguestfs\-xfs\*(C'\fR у Red Hat
-Enterprise Linux, CentOS, Debian, Ubuntu та дистрибутивах, які від них
-походять, щоб можна було працювати із файловою системою \f(CW\*(C`xfs\*(C'\fR.
+У цьому випадку достатньо встановити належні пакунки із підтримкою файлових систем. Наприклад, достатньо встановити \f(CW\*(C`libguestfs\-xfs\*(C'\fR у Red Hat Enterprise Linux, CentOS, Debian, Ubuntu та дистрибутивах, які від них походять, щоб можна було працювати із файловою системою \f(CW\*(C`xfs\*(C'\fR.
.IP "2." 4
-У virt-resize не передбачено підтримки розширення цього типу файлових
-систем.
+У virt-resize не передбачено підтримки розширення цього типу файлових систем.
.Sp
-У цьому випадку нічого не поробиш: virt-resize не зможе розширити файлову
-систему цього типу.
+У цьому випадку нічого не поробиш: virt-resize не зможе розширити файлову систему цього типу.
.PP
-In both cases, virt-resize will not expand the mentioned filesystem; the
-result (unless \fI\-\-unknown\-filesystems error\fR is specified) is that the
-partitions containing such filesystems will be actually bigger as requested,
-but the filesystems will still be usable at their older sizes.
+In both cases, virt-resize will not expand the mentioned filesystem; the result (unless \fI\-\-unknown\-filesystems error\fR is specified) is that the partitions containing such filesystems will be actually bigger as requested, but the filesystems will still be usable at their older sizes.
.SH "АЛЬТЕРНАТИВНІ ІНСТРУМЕНТИ"
.IX Header "АЛЬТЕРНАТИВНІ ІНСТРУМЕНТИ"
-Існує декілька пропрієтарних інструментів для зміни розмірів розділів. Тут
-ми не будемо згадувати назви жодного з таких інструментів.
-.PP
-\&\fBparted\fR\|(8) і її графічний інтерфейс, gparted, можуть виконувати певні типи
-дій із зміни розміру образів дисків. Ці програми можуть змінювати розмір і
-пересувати розділи, але не слід вважати, що вони можуть виконувати будь\-які
-дії із вмістом розділів, і, звичайно ж, вони не можуть працювати з \s-1LVM.\s0
-.PP
-\&\fBguestfish\fR\|(1) може виконувати усі ті дії, які може виконувати virt-resize,
-і набагато більше, але на суттєво нижчому рівні. Ймовірно, вам доведеться
-вручну обчислювати відступи у секторах, робити те, що за означенням має
-робити virt-resize. Якщо хочете дізнатися, які команди у guestfish запускає
-virt-resize, скористайтеся параметром \fI\-\-debug\fR.
-.PP
-До складу \fBdracut\fR\|(8) включено модуль із назвою \f(CW\*(C`dracut\-modules\-growroot\*(C'\fR,
-яким можна скористатися для збільшення розмірів кореневого розділу під час
-першого завантаження гостьової системи. Документацію з цього модуля наведено
-у пов'язаному із ним файлі \s-1README.\s0
+Існує декілька пропрієтарних інструментів для зміни розмірів розділів. Тут ми не будемо згадувати назви жодного з таких інструментів.
+.PP
+\&\fBparted\fR\|(8) і її графічний інтерфейс, gparted, можуть виконувати певні типи дій із зміни розміру образів дисків. Ці програми можуть змінювати розмір і пересувати розділи, але не слід вважати, що вони можуть виконувати будь\-які дії із вмістом розділів, і, звичайно ж, вони не можуть працювати з \s-1LVM.\s0
+.PP
+\&\fBguestfish\fR\|(1) може виконувати усі ті дії, які може виконувати virt-resize, і набагато більше, але на суттєво нижчому рівні. Ймовірно, вам доведеться вручну обчислювати відступи у секторах, робити те, що за означенням має робити virt-resize. Якщо хочете дізнатися, які команди у guestfish запускає virt-resize, скористайтеся параметром \fI\-\-debug\fR.
+.PP
+До складу \fBdracut\fR\|(8) включено модуль із назвою \f(CW\*(C`dracut\-modules\-growroot\*(C'\fR, яким можна скористатися для збільшення розмірів кореневого розділу під час першого завантаження гостьової системи. Документацію з цього модуля наведено у пов'язаному із ним файлі \s-1README.\s0
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBvirt\-filesystems\fR\|(1), \fBvirt\-df\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1),
-\&\fBlvm\fR\|(8), \fBpvresize\fR\|(8), \fBlvresize\fR\|(8), \fBresize2fs\fR\|(8),
-\&\fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), \fBresize.f2fs\fR\|(8),
-\&\fBvirsh\fR\|(1), \fBparted\fR\|(8), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBgrub\fR\|(8),
-\&\fBgrub\-install\fR\|(8), \fBvirt\-rescue\fR\|(1), \fBvirt\-sparsify\fR\|(1),
-\&\fBvirt\-alignment\-scan\fR\|(1), http://libguestfs.org/.
+\&\fBvirt\-filesystems\fR\|(1), \fBvirt\-df\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBlvm\fR\|(8), \fBpvresize\fR\|(8), \fBlvresize\fR\|(8), \fBresize2fs\fR\|(8), \fBntfsresize\fR\|(8), \fBbtrfs\fR\|(8), \fBxfs_growfs\fR\|(8), \fBresize.f2fs\fR\|(8), \fBvirsh\fR\|(1), \fBparted\fR\|(8), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBgrub\fR\|(8), \fBgrub\-install\fR\|(8), \fBvirt\-rescue\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirt\-alignment\-scan\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Virt-resize — програма, за допомогою якої можна змінити розміри диска
-віртуальної машини, зробивши його більшим або меншим чи змінивши розміри
-розділів, які містяться на диску, або вилучивши їх.
+Virt-resize — програма, за допомогою якої можна змінити розміри диска віртуальної машини, зробивши його більшим або меншим чи змінивши розміри розділів, які містяться на диску, або вилучивши їх.
-Virt-resize B<не може> змінювати розмір образів дисків «на
-місці». Virt-resize B<не слід> використовувати для активних віртуальних
-машин — щоб отримати належний результат, перш ніж змінювати розміри дисків,
-зупиніть роботу віртуальної машини.
+Virt-resize B<не може> змінювати розмір образів дисків «на місці». Virt-resize B<не слід> використовувати для активних віртуальних машин — щоб отримати належний результат, перш ніж змінювати розміри дисків, зупиніть роботу віртуальної машини.
-Якщо ви ще не знайомі з принципами роботи пов'язаних інструментів,
-L<virt-filesystems(1)> і L<virt-df(1)>, рекомендуємо вам спершу ознайомитися
-із документацією щодо цих інструментів.
+Якщо ви ще не знайомі з принципами роботи пов'язаних інструментів, L<virt-filesystems(1)> і L<virt-df(1)>, рекомендуємо вам спершу ознайомитися із документацією щодо цих інструментів.
=head1 ПРИКЛАДИ
=item 1.
-У цьому прикладі ми візьмемо C<старий_диск>, змінимо його розміри і запишемо
-як C<новий_диск>, розширивши один із розділів гостьової системи на додаткові
-5 ГБ:
+У цьому прикладі ми візьмемо C<старий_диск>, змінимо його розміри і запишемо як C<новий_диск>, розширивши один із розділів гостьової системи на додаткові 5 ГБ:
virt-filesystems --long -h --all -a старий_диск
=item 2.
-Те саме, що і вище, але зі збільшенням розділу /boot на 200 МБ, з наданням
-решти місця для /dev/sda2:
+Те саме, що і вище, але зі збільшенням розділу /boot на 200 МБ, з наданням решти місця для /dev/sda2:
virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
старий_диск новий_диск
=item 3.
-Як у першому прикладі, але із розширенням логічного тому на останньому
-кроці. Саме цю команду типово використовують для гостьових систем Linux, де
-використовується LVM:
+Як у першому прикладі, але із розширенням логічного тому на останньому кроці. Саме цю команду типово використовують для гостьових систем Linux, де використовується LVM:
virt-resize --expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root \
старий_диск новий_диск
=item 4.
-Як у першому прикладі, але дані буде виведено у форматі qcow2, а не у
-простому (raw) форматі:
+Як у першому прикладі, але дані буде виведено у форматі qcow2, а не у простому (raw) форматі:
qemu-img create -f qcow2 -o preallocation=metadata newdisk.qcow2 15G
virt-resize --expand /dev/sda2 olddisk newdisk.qcow2
=item 2. Встановіть розташування образу диска із вхідними даними
-Встановіть розташування образу диска із вхідними даними (тобто файла або
-пристрою у основній системі, де містяться дані диска гостьової
-системи). Якщо гостьовою системою керує libvirt, ви можете скористатися для
-визначення назви образу диска командою C<virsh dumpxml>, ось так:
+Встановіть розташування образу диска із вхідними даними (тобто файла або пристрою у основній системі, де містяться дані диска гостьової системи). Якщо гостьовою системою керує libvirt, ви можете скористатися для визначення назви образу диска командою C<virsh dumpxml>, ось так:
# virsh dumpxml guestname | xpath /domain/devices/disk/source
Знайдено 1 вузли:
=item 3. Визначте поточні розміри
-Скористайтеся програмою L<virt-filesystems(1)> для перегляду списку поточних
-розділів і їхніх розмірів:
+Скористайтеся програмою L<virt-filesystems(1)> для перегляду списку поточних розділів і їхніх розмірів:
# virt-filesystems --long --parts --blkdevs -h -a /dev/vg/lv_guest
Name Type Size Parent
/dev/sda2 partition 7.9G /dev/sda
/dev/sda device 8.0G -
-(У цьому прикладі маємо справу з віртуальною машиною з диском у 8 ГБ, який
-ми хочемо розширити до 10 ГБ).
+(У цьому прикладі маємо справу з віртуальною машиною з диском у 8 ГБ, який ми хочемо розширити до 10 ГБ).
=item 4. Створіть диск для виведення даних
-Virt-resize не може виконувати внесення змін до дисків «на місці». У вашій
-системі має бути достатньо місця для зберігання диска-результату зі зміненим
-розміром.
+Virt-resize не може виконувати внесення змін до дисків «на місці». У вашій системі має бути достатньо місця для зберігання диска-результату зі зміненим розміром.
-Для збереження образу диска зі зміненим розміром створіть файл відповідного
-розміру:
+Для збереження образу диска зі зміненим розміром створіть файл відповідного розміру:
# rm -f outdisk
# truncate -s 10G outdisk
# lvcreate -L 10G -n lv_name vg_name
-Або скористайтеся L<virsh(1)> vol-create-as для створення тому сховища даних
-libvirt:
+Або скористайтеся L<virsh(1)> vol-create-as для створення тому сховища даних libvirt:
# virsh pool-list
# virsh vol-create-as poolname newvol 10G
=item 5. Зміна розміру
-virt-resize має отримати два обов'язкових параметри, назву диска із вхідними
-даними і назву диска із вихідними даними (обидві можуть бути, наприклад,
-пристроями, файлами або адресами на віддаленому диску). Диском з виведеними
-даними має бути диск, створений на попередньому кроці.
+virt-resize має отримати два обов'язкових параметри, назву диска із вхідними даними і назву диска із вихідними даними (обидві можуть бути, наприклад, пристроями, файлами або адресами на віддаленому диску). Диском з виведеними даними має бути диск, створений на попередньому кроці.
# virt-resize indisk outdisk
-Ця команда просто копіює образ диска C<indisk> до образу диска C<outdisk>
-I<без> зміни розмірів або будь-яких змін у наявних розділах. Якщо диск
-C<outdisk> є завеликим для даних, створюється додатковий порожній розділ
-наприкінці диска, розмір якого відповідатиме зайвому місцю. Якщо диск
-C<outdisk> виявиться замалим, програма повідомить про помилку.
+Ця команда просто копіює образ диска C<indisk> до образу диска C<outdisk> I<без> зміни розмірів або будь-яких змін у наявних розділах. Якщо диск C<outdisk> є завеликим для даних, створюється додатковий порожній розділ наприкінці диска, розмір якого відповідатиме зайвому місцю. Якщо диск C<outdisk> виявиться замалим, програма повідомить про помилку.
-Реалістичнішим буде варіант, коли вам потрібно розширити наявні розділи на
-образі диска передаванням додаткових параметрів (повний список параметрів
-наведено у розділі L</ПАРАМЕТРИ> нижче).
+Реалістичнішим буде варіант, коли вам потрібно розширити наявні розділи на образі диска передаванням додаткових параметрів (повний список параметрів наведено у розділі L</ПАРАМЕТРИ> нижче).
-L</--expand> є найкориснішим параметром. За його допомогою можна розширити
-вказаний за назвою розділ на диску так, щоб він зайняв усе зайве місце:
+L</--expand> є найкориснішим параметром. За його допомогою можна розширити вказаний за назвою розділ на диску так, щоб він зайняв усе зайве місце:
# virt-resize --expand /dev/sda2 indisk outdisk
-(У цьому випадку наприкінці диска I<не> створюватиметься додаткових
-розділів, оскільки невикористаного місця просто не буде).
+(У цьому випадку наприкінці диска I<не> створюватиметься додаткових розділів, оскільки невикористаного місця просто не буде).
-L</--resize> — ще один широковживаний параметр. Наступна команда збільшить
-розмір /dev/sda1 на 200 МБ і розширить /dev/sda2 так, щоб той заповнив решту
-доступного місця:
+L</--resize> — ще один широковживаний параметр. Наступна команда збільшить розмір /dev/sda1 на 200 МБ і розширить /dev/sda2 так, щоб той заповнив решту доступного місця:
# virt-resize --resize /dev/sda1=+200M --expand /dev/sda2 \
indisk outdisk
-Якщо на розширюваному розділі у образі міститься файлова система або
-фізичний том LVM, тоді, якщо virt-resize відомий спосіб, програма змінить
-розміри вмісту так, як це роблять виклики команд L<pvresize(8)>,
-L<resize2fs(8)>, L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)> або
-L<resize.f2fs(8)>. Втім, virt-resize не відомі способи зміни розмірів деяких
-файлових систем, тому вам доведеться якось змінювати їхні розміри після
-завантаження гостьової системи.
+Якщо на розширюваному розділі у образі міститься файлова система або фізичний том LVM, тоді, якщо virt-resize відомий спосіб, програма змінить розміри вмісту так, як це роблять виклики команд L<pvresize(8)>, L<resize2fs(8)>, L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)> або L<resize.f2fs(8)>. Втім, virt-resize не відомі способи зміни розмірів деяких файлових систем, тому вам доведеться якось змінювати їхні розміри після завантаження гостьової системи.
# virt-resize --expand /dev/sda2 nbd://example.com outdisk
-Диском із вхідними даними може бути адреса, якщо як джерело слід використати
-віддалений диск. Формат адреси є сумісним із
-guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
+Диском із вхідними даними може бути адреса, якщо як джерело слід використати віддалений диск. Формат адреси є сумісним із guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
Інші параметри описано нижче.
=item 6. Перевірка
-Виконайте належне тестування нового образу диска, I<перш ніж> витирати
-старий.
+Виконайте належне тестування нового образу диска, I<перш ніж> витирати старий.
-Якщо ви користуєтеся libvirt, внесіть зміни до XML так, щоб він вказував на
-новий диск:
+Якщо ви користуєтеся libvirt, внесіть зміни до XML так, щоб він вказував на новий диск:
# virsh edit назва_гостьової_системи
-Змініть E<lt>source ...E<gt>,
-див. L<http://libvirt.org/formatdomain.html#elementsDisks>
+Змініть E<lt>source ...E<gt>, див. L<http://libvirt.org/formatdomain.html#elementsDisks>
Далі, запустіть домен з новим диском, розмір якого було змінено:
# virsh start назва_гостьової_системи
-і перевірте, чи все лишається працездатним. Див. також додаткові зауваження
-у розділі L</ПРИМІТКИ> нижче.
+і перевірте, чи все лишається працездатним. Див. також додаткові зауваження у розділі L</ПРИМІТКИ> нижче.
=item 7. Зміна розмірів логічних томів та інших сховищ у гостьовій системі
-(Це завдання можна виконати без завантаження гостьової системи за допомогою
-L<guestfish(1)>)
+(Це завдання можна виконати без завантаження гостьової системи за допомогою L<guestfish(1)>)
-Після завантаження гостьової системи у ній має з'явитися вільне місце,
-принаймні для файлових систем, способи зміни розмірів яких відомі
-virt-resize, та фізичних томів. Користувачеві, ймовірно, слід буде змінити
-логічні томи у фізичних томах, а також змінити розміри типів файлових
-систем, способи розширення яких не відомі virt-resize.
+Після завантаження гостьової системи у ній має з'явитися вільне місце, принаймні для файлових систем, способи зміни розмірів яких відомі virt-resize, та фізичних томів. Користувачеві, ймовірно, слід буде змінити логічні томи у фізичних томах, а також змінити розміри типів файлових систем, способи розширення яких не відомі virt-resize.
=back
=head2 ЗМЕНШЕННЯ РОЗМІРІВ ДИСКА ВІРТУАЛЬНОЇ МАШИНИ
-Зменшення розмірів є дещо складнішим завданням за збільшення. У цьому
-розділі наведено лише загальний огляд.
+Зменшення розмірів є дещо складнішим завданням за збільшення. У цьому розділі наведено лише загальний огляд.
-По-перше, virt-resize не робитиме спроб стиснути будь-який вміст розділу
-(фізичні томи, файлові системи). Користувачеві слід подбати про зменшення
-розмірів вмісту до передавання диска на обробку до virt-resize, і
-virt-resize перевірить, чи було стиснено вміст належним чином.
+По-перше, virt-resize не робитиме спроб стиснути будь-який вміст розділу (фізичні томи, файлові системи). Користувачеві слід подбати про зменшення розмірів вмісту до передавання диска на обробку до virt-resize, і virt-resize перевірить, чи було стиснено вміст належним чином.
-(Зменшення розмірів також можна виконати без завантаження системи за
-допомогою L<guestfish(1)>)
+(Зменшення розмірів також можна виконати без завантаження системи за допомогою L<guestfish(1)>)
-Після стискання фізичних томів і файлових систем, вимкніть гостьову систему
-і виконайте описані вище кроки 3 і 4 для розміщення нового образу диска.
+Після стискання фізичних томів і файлових систем, вимкніть гостьову систему і виконайте описані вище кроки 3 і 4 для розміщення нового образу диска.
-Потім запустіть virt-resize із відповідними параметрами I<--shrink> і/або
-I<--resize>.
+Потім запустіть virt-resize із відповідними параметрами I<--shrink> і/або I<--resize>.
=head2 ІГНОРУВАННЯ І ВИЛУЧЕННЯ РОЗДІЛІВ
-Крім того, virt-resize надає вам зручний спосіб ігнорувати або вилучати
-розділи при копіюванні з диска вхідних даних на диск вихідних
-даних. Ігнорування розділу пришвидшує копіювання там, де вам все одно що
-станеться із наявним вмістом розділу. Вилучення розділу вилучає його
-повністю, але зауважте, що це також призводить до перенумерування усіх
-розділів після вилучено, що може призвести до неможливості завантаження
-деяких гостьових систем.
+Крім того, virt-resize надає вам зручний спосіб ігнорувати або вилучати розділи при копіюванні з диска вхідних даних на диск вихідних даних. Ігнорування розділу пришвидшує копіювання там, де вам все одно що станеться із наявним вмістом розділу. Вилучення розділу вилучає його повністю, але зауважте, що це також призводить до перенумерування усіх розділів після вилучено, що може призвести до неможливості завантаження деяких гостьових систем.
=head2 QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW
-Якщо дисх вхідних даних записано у форматі qcow2, ймовірно, варто записати
-вихідні дані теж у форматі qcow2. Крім того, virt-resize може перетворювати
-дані з одного формату на інший «на льоту». Формат виведених даних просто
-визначається форматом порожнього контейнера для виведення даних, який ви
-надасте. Таким чином, щоб записати виведені дані у форматі qcow2,
-скористайтеся такою командою:
+Якщо дисх вхідних даних записано у форматі qcow2, ймовірно, варто записати вихідні дані теж у форматі qcow2. Крім того, virt-resize може перетворювати дані з одного формату на інший «на льоту». Формат виведених даних просто визначається форматом порожнього контейнера для виведення даних, який ви надасте. Таким чином, щоб записати виведені дані у форматі qcow2, скористайтеся такою командою:
qemu-img create -f qcow2 -o preallocation=metadata outdisk [розмір]
замість команди truncate.
-Так само, щоб отримати дані у нерозрідженому простому форматі (raw)
-скористайтеся такою командою:
+Так само, щоб отримати дані у нерозрідженому простому форматі (raw) скористайтеся такою командою:
fallocate -l розмір вихідний_диск
-(у застарілих системах, де немає команди L<fallocate(1)>, скористайтеся
-командою C<dd if=/dev/zero of=outdisk bs=1M count=..>)
+(у застарілих системах, де немає команди L<fallocate(1)>, скористайтеся командою C<dd if=/dev/zero of=outdisk bs=1M count=..>)
=head2 ЛОГІЧНІ РОЗДІЛИ
-Розміри логічних розділів (тобто F</dev/sda5+> на дисках із таблицею
-розділів DOS) не може бути змінено.
+Розміри логічних розділів (тобто F</dev/sda5+> на дисках із таблицею розділів DOS) не може бути змінено.
-Щоб розібратися у тому, що відбувається, по-перше, слід пам'ятати, що один
-із чотирьох розділів F</dev/sda1-4> матиме тип розділу MBR C<05> або
-C<0f>. Такий розділ називається B<розширеним розділом>. Для перегляду типу
-розділу MBR скористайтеся L<virt-filesystems(1)>.
+Щоб розібратися у тому, що відбувається, по-перше, слід пам'ятати, що один із чотирьох розділів F</dev/sda1-4> матиме тип розділу MBR C<05> або C<0f>. Такий розділ називається B<розширеним розділом>. Для перегляду типу розділу MBR скористайтеся L<virt-filesystems(1)>.
Логічні розділи містяться у розширеному розділі.
-Розширений розділ може бути збільшено, але не може бути зменшено (це можна
-зробити у примусовому режимі, але ми не радимо так робити). При копіюванні
-розширеного розділу неявним чином копіюються усі логічні розділи, які на
-ньому містяться. Virt-resize не зазирає до розширеного розділу, отже сліпо
-копіює логічні розділи.
+Розширений розділ може бути збільшено, але не може бути зменшено (це можна зробити у примусовому режимі, але ми не радимо так робити). При копіюванні розширеного розділу неявним чином копіюються усі логічні розділи, які на ньому містяться. Virt-resize не зазирає до розширеного розділу, отже сліпо копіює логічні розділи.
-Вказати логічний розділ (F</dev/sda5+>) у рядку команди не можна. Якщо ви це
-зробите, програма повідомить про помилку.
+Вказати логічний розділ (F</dev/sda5+>) у рядку команди не можна. Якщо ви це зробите, програма повідомить про помилку.
=head1 ПАРАМЕТРИ
=item B<--align-first> B<always>
-Вирівняти перший розділ, щоб підвищити швидкодію (див. параметр
-I<--alignment>).
+Вирівняти перший розділ, щоб підвищити швидкодію (див. параметр I<--alignment>).
-Типовою поведінкою є використання параметра I<--align-first auto>, який
-вирівнює лише перший розділ, якщо це безпечно робити. Тобто, лише якщо
-програмі достеменно відомо, як виправити завантажувач автоматично, і, у
-поточній версії, лише для гостьових систем Windows.
+Типовою поведінкою є використання параметра I<--align-first auto>, який вирівнює лише перший розділ, якщо це безпечно робити. Тобто, лише якщо програмі достеменно відомо, як виправити завантажувач автоматично, і, у поточній версії, лише для гостьових систем Windows.
-I<--align-first never> означає, що пересування першого розділу ніколи не
-відбуватиметься. Це найбезпечніший варіант. Скористайтеся ним, якщо після
-зміни розмірів гостьова система відмовляється завантажуватися.
+I<--align-first never> означає, що пересування першого розділу ніколи не відбуватиметься. Це найбезпечніший варіант. Скористайтеся ним, якщо після зміни розмірів гостьова система відмовляється завантажуватися.
-I<--align-first always> означає, що завжди відбуватиметься вирівнювання
-першого розділу (якщо його треба вирівнювати). Для деяких гостьових систем
-це може завадити роботи завантажувача, зробивши гостьову систему непридатною
-до завантаження.
+I<--align-first always> означає, що завжди відбуватиметься вирівнювання першого розділу (якщо його треба вирівнювати). Для деяких гостьових систем це може завадити роботи завантажувача, зробивши гостьову систему непридатною до завантаження.
=item B<--alignment> N
-Встановити вирівнювання розділів на межу C<N> секторів. Типовою у
-virt-resize E<lt> 1.13.19 було межа у 64 сектори. Після цієї версії типове
-значення було змінено на 128 секторів.
+Встановити вирівнювання розділів на межу C<N> секторів. Типовою у virt-resize E<lt> 1.13.19 було межа у 64 сектори. Після цієї версії типове значення було змінено на 128 секторів.
-Якщо припускати розмір сектора у гостьовій системі у 512 байтів, ось
-придатні значення для цього параметра:
+Якщо припускати розмір сектора у гостьовій системі у 512 байтів, ось придатні значення для цього параметра:
=over 4
=item I<--alignment 1> (512 байтів)
-Розділи буде розташовано поруч один із одним якомога ближче, але буде не
-вирівняно. У деяких випадках це може призвести до жахливої втрати
-швидкодії. Докладніший опис можна знайти на сторінці підручника щодо
-L<virt-alignment-scan(1)>.
+Розділи буде розташовано поруч один із одним якомога ближче, але буде не вирівняно. У деяких випадках це може призвести до жахливої втрати швидкодії. Докладніший опис можна знайти на сторінці підручника щодо L<virt-alignment-scan(1)>.
=item I<--alignment 8> (4K)
-Це мінімальне прийнятне вирівнювання для придатного значення швидкодії на
-сучасних основних системах.
+Це мінімальне прийнятне вирівнювання для придатного значення швидкодії на сучасних основних системах.
=item I<--alignment 128> (64K)
-Таке вирівнювання надасть змогу скористатися непоганою швидкодією, якщо
-основна система зберігається на високоякісних носіях для мережі.
+Таке вирівнювання надасть змогу скористатися непоганою швидкодією, якщо основна система зберігається на високоякісних носіях для мережі.
=item I<--alignment 2048> (1M)
-Це стандартне вирівнювання, яке використовується в усіх нововстановлених
-гостьових системах з приблизно 2008 року.
+Це стандартне вирівнювання, яке використовується в усіх нововстановлених гостьових системах з приблизно 2008 року.
=back
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<-d>
=item B<--delete> РОЗДІЛ
-Вилучити вказаний за назвою розділ. Точнішим визначенням цієї дії буде «не
-копіювати», оскільки virt-resize не вносить зміни до початкового образу
-диска.
+Вилучити вказаний за назвою розділ. Точнішим визначенням цієї дії буде «не копіювати», оскільки virt-resize не вносить зміни до початкового образу диска.
-Зауважте, що коли ви вилучаєте розділ, вилучаються і усі дані, які
-зберігалися на ньому. Більше того, у результаті усі розділи за вилученим
-I<перенумеровуються>, що може призвести до неможливості завантаження
-гостьової системи.
+Зауважте, що коли ви вилучаєте розділ, вилучаються і усі дані, які зберігалися на ньому. Більше того, у результаті усі розділи за вилученим I<перенумеровуються>, що може призвести до неможливості завантаження гостьової системи.
Цей параметр можна вказувати декілька разів.
=item B<--expand> РОЗДІЛ
-Розширити вказаний за назвою розділ так, щоб він зайняв усе вільне місце
-(місце, яке лишатиметься вільним після усіх інших вказаних вами змін у
-розмірах).
+Розширити вказаний за назвою розділ так, щоб він зайняв усе вільне місце (місце, яке лишатиметься вільним після усіх інших вказаних вами змін у розмірах).
-Якщо virt-resize відомий спосіб, програма розширить безпосередній вміст
-розділу. Наприклад, якщо розділ є фізичним томом LVM, програма розширить
-фізичний том так, щоб він зайняв усе місце (подібно до виклику
-L<pvresize(8)>). Якщо спосіб розширення виявиться невідомим virt-resize,
-програма не чіпатиме вмісту розділу.
+Якщо virt-resize відомий спосіб, програма розширить безпосередній вміст розділу. Наприклад, якщо розділ є фізичним томом LVM, програма розширить фізичний том так, щоб він зайняв усе місце (подібно до виклику L<pvresize(8)>). Якщо спосіб розширення виявиться невідомим virt-resize, програма не чіпатиме вмісту розділу.
У поточній версії virt-resize може змінювати розміри таких файлових систем:
Файлових систем NTFS, якщо libguestfs було зібрано з підтримкою NTFS.
-Роботу файлової системи під час її останнього використання має бути
-завершено у штатному режимі. Крім того, L<ntfsresize(8)> позначає файлові
-системи зі зміненими розмірами як такі, що потребують перевірки, отже під
-час першого наступного запуску Windows на розділі зі зміненим розміром буде
-виконано перевірку диска.
+Роботу файлової системи під час її останнього використання має бути завершено у штатному режимі. Крім того, L<ntfsresize(8)> позначає файлові системи зі зміненими розмірами як такі, що потребують перевірки, отже під час першого наступного запуску Windows на розділі зі зміненим розміром буде виконано перевірку диска.
=item *
-Фізичні томи LVM. Зазвичай, virt-resize не змінює розміри вмісту фізичних
-томів, втім, див. параметр I<--LV-expand>. Користувач також може змінити
-розміри логічних томів бажаним чином після завантаження системи.
+Фізичні томи LVM. Зазвичай, virt-resize не змінює розміри вмісту фізичних томів, втім, див. параметр I<--LV-expand>. Користувач також може змінити розміри логічних томів бажаним чином після завантаження системи.
=item *
Розділи резервної пам'яті на диску Linux.
-Будь ласка, зауважте, що libguestfs I<знищує> наявний вміст розділу
-резервної пам'яті на диску, відтворюючи його за допомогою C<mkswap>, тому
-такі розділи не слід використовувати, якщо гостьова система присипляється.
+Будь ласка, зауважте, що libguestfs I<знищує> наявний вміст розділу резервної пам'яті на диску, відтворюючи його за допомогою C<mkswap>, тому такі розділи не слід використовувати, якщо гостьова система присипляється.
=item *
=back
-Зауважте, що параметри I<--expand> і I<--shrink> не можна використовувати у
-одній і тій самій команді.
+Зауважте, що параметри I<--expand> і I<--shrink> не можна використовувати у одній і тій самій команді.
=item B<--format> B<raw>
-Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано,
-його буде автоматично визначено на основі даних самого образу.
+Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого образу.
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
-Зауважте, що цей параметр I<не> впливає на формат виведених
-даних. Див. L</QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW>.
+Зауважте, що цей параметр I<не> впливає на формат виведених даних. Див. L</QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW>.
=item B<--ignore> РОЗДІЛ
-Ігнорувати вказаний за назвою розділ. По суті, це означає, що розділ
-розміщується на диску призначення, але його вміст з початкового диска не
-копіюється. Розділ лишатиметься порожнім (заповненим нулями).
+Ігнорувати вказаний за назвою розділ. По суті, це означає, що розділ розміщується на диску призначення, але його вміст з початкового диска не копіюється. Розділ лишатиметься порожнім (заповненим нулями).
Цей параметр можна вказувати декілька разів.
=item B<--LV-expand> ЛОГІЧНИЙ_ТОМ
-Цій команді передається логічний том і, як останній крок, вона розширює цей
-том так, щоб він зайняв усе вільне місце, яке доступне у групі
-томів. Типовим використанням, якщо припускати, що ви працюєте із гостьовою
-системою Linux із єдиним фізичним томом PV F</dev/sda2> і кореневим
-пристроєм із назвою F</dev/vg_guest/lv_root>, є:
+Цій команді передається логічний том і, як останній крок, вона розширює цей том так, щоб він зайняв усе вільне місце, яке доступне у групі томів. Типовим використанням, якщо припускати, що ви працюєте із гостьовою системою Linux із єдиним фізичним томом PV F</dev/sda2> і кореневим пристроєм із назвою F</dev/vg_guest/lv_root>, є:
virt-resize indisk outdisk \
--expand /dev/sda2 --LV-expand /dev/vg_guest/lv_root
-Ця команда спершу розширить розділ (і фізичний том), а потім розширить
-кореневий пристрій так, що він займе усе наявне зайве місце на фізичному
-томі.
+Ця команда спершу розширить розділ (і фізичний том), а потім розширить кореневий пристрій так, що він займе усе наявне зайве місце на фізичному томі.
-Розмір вмісту логічного тому також буде змінено, якщо virt-resize відомий
-спосіб, як це зробити. Ви можете заборонити virt-resize змінювати розміри
-вмісту за допомогою параметра I<--no-expand-content>.
+Розмір вмісту логічного тому також буде змінено, якщо virt-resize відомий спосіб, як це зробити. Ви можете заборонити virt-resize змінювати розміри вмісту за допомогою параметра I<--no-expand-content>.
-Скористайтеся L<virt-filesystems(1)> для отримання списку файлових систем у
-гостьовій системі.
+Скористайтеся L<virt-filesystems(1)> для отримання списку файлових систем у гостьовій системі.
-Ви можете вказати у одній команді цей параметр декілька разів, I<але> сенсу
-у цьому небагато, хіба що вказані вами логічні томи належать до різних груп
-томів.
+Ви можете вказати у одній команді цей параметр декілька разів, I<але> сенсу у цьому небагато, хіба що вказані вами логічні томи належать до різних груп томів.
=item B<--machine-readable>
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<-n>
=item B<--no-copy-boot-loader>
-Типово, virt-resize копіює деякі сектори на початку диска (аж до початку
-першого розділу). Найчастіше, у цих секторах міститься Master Boot Record
-(MBR) та завантажувач. Вони потрібні для того, щоб гостьова система
-завантажувалася належним чином.
+Типово, virt-resize копіює деякі сектори на початку диска (аж до початку першого розділу). Найчастіше, у цих секторах міститься Master Boot Record (MBR) та завантажувач. Вони потрібні для того, щоб гостьова система завантажувалася належним чином.
-Якщо ви вкажете цей прапорець, це початкове копіювання не
-виконуватиметься. У цьому випадку може виникнути потреба у перевстановленні
-завантажувача.
+Якщо ви вкажете цей прапорець, це початкове копіювання не виконуватиметься. У цьому випадку може виникнути потреба у перевстановленні завантажувача.
=item B<--no-extra-partition>
-Типово, virt-resize створює додатковий розділ, якщо буде виявлено зайве
-невикористане місце після усіх змін розмірів. Скористайтеся цим параметром
-для того, щоб запобігти створенню цього додаткового розділу. Якщо ви так
-зробите, зайве місце буде недоступним, аж доки ви не запустите fdisk, parted
-або якийсь інший інструмент поділу на розділи у гостьовій системі.
+Типово, virt-resize створює додатковий розділ, якщо буде виявлено зайве невикористане місце після усіх змін розмірів. Скористайтеся цим параметром для того, щоб запобігти створенню цього додаткового розділу. Якщо ви так зробите, зайве місце буде недоступним, аж доки ви не запустите fdisk, parted або якийсь інший інструмент поділу на розділи у гостьовій системі.
-Зауважте, що якщо зайвого місця виявиться менше за 10 МБ, додатковий розділ
-не створюватиметься.
+Зауважте, що якщо зайвого місця виявиться менше за 10 МБ, додатковий розділ не створюватиметься.
=item B<--no-expand-content>
-Типово, virt-resize намагатиметься розширити безпосередній вміст розділів,
-якщо програмі відомий спосіб виконати таке розширення (див. параметр
-I<--expand> вище).
+Типово, virt-resize намагатиметься розширити безпосередній вміст розділів, якщо програмі відомий спосіб виконати таке розширення (див. параметр I<--expand> вище).
-Якщо ви вкажете параметр I<--no-expand-content>, virt-resize не виконуватиме
-таких спроб.
+Якщо ви вкажете параметр I<--no-expand-content>, virt-resize не виконуватиме таких спроб.
=item B<--no-sparse>
=item B<--ntfsresize-force>
-Передавання параметра I<--force> до L<ntfsresize(8)> уможливить зміну
-розмірів, навіть якщо диск NTFS буде позначено як такий, що потребує
-перевірки коректності. Вам доведеться скористатися цим параметром, якщо ви
-хочете змінити розміри гостьової системи Windows без потреби у завантаженні
-Windows кожного разу між командами зміни розмірів.
+Передавання параметра I<--force> до L<ntfsresize(8)> уможливить зміну розмірів, навіть якщо диск NTFS буде позначено як такий, що потребує перевірки коректності. Вам доведеться скористатися цим параметром, якщо ви хочете змінити розміри гостьової системи Windows без потреби у завантаженні Windows кожного разу між командами зміни розмірів.
=item B<--output-format> B<raw>
-Визначає формат виведеного образу диска. Якщо цей прапорець не вказано,
-формат буде автоматично визначено на основі даних щодо образу диска.
+Визначає формат виведеного образу диска. Якщо цей прапорець не вказано, формат буде автоматично визначено на основі даних щодо образу диска.
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
-Зауважте, що цей параметр I<не створює> образ диска у визначеному
-форматі. Цей параметр призначено лише для того, щоб libguestfs не намагалася
-вгадати формат. Створити диск у належному форматі маєте ви
-самі. Див. L</QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW>.
+Зауважте, що цей параметр I<не створює> образ диска у визначеному форматі. Цей параметр призначено лише для того, щоб libguestfs не намагалася вгадати формат. Створити диск у належному форматі маєте ви самі. Див. L</QCOW2 І НЕРОЗРІДЖЕНІ ФОРМАТИ RAW>.
=item B<-q>
=item B<--resize> РОЗДІЛ=РОЗМІР
-Змінити розмір вказаного за назвою розділу (розширити або стиснути його)
-так, щоб він мав вказаний розмір.
+Змінити розмір вказаного за назвою розділу (розширити або стиснути його) так, щоб він мав вказаний розмір.
-C<РОЗМІР> можна вказати як значення за модулем із додаванням суфікса b/K/M/G
-на позначення байтів, кілобайтів, мегабайтів або гігабайтів, або як відсоток
-від поточного розміру, або як відносну частку. Приклад:
+C<РОЗМІР> можна вказати як значення за модулем із додаванням суфікса b/K/M/G на позначення байтів, кілобайтів, мегабайтів або гігабайтів, або як відсоток від поточного розміру, або як відносну частку. Приклад:
--resize /dev/sda2=10G
--resize /dev/sda1=-10%
-Ви можете збільшити розмір будь-якого розділу. Virt-resize розширить
-безпосередній вміст розділу, якщо програмі відомий спосіб виконати таке
-розширення (див. I<--expand> вище).
+Ви можете збільшити розмір будь-якого розділу. Virt-resize розширить безпосередній вміст розділу, якщо програмі відомий спосіб виконати таке розширення (див. I<--expand> вище).
-I<Зменшити> розмір розділів, які містять файлові системи або фізичні томи,
-можна лише якщо ці файлові системи або фізичні томи вже зменшено у розмірах
-всередині розділу. Virt-resize виконає перевірку виконання цієї умови до
-того, як розпочне обробку даних. Якщо умову не виконано, програма повідомить
-про помилку (див. також I<--resize-force>).
+I<Зменшити> розмір розділів, які містять файлові системи або фізичні томи, можна лише якщо ці файлові системи або фізичні томи вже зменшено у розмірах всередині розділу. Virt-resize виконає перевірку виконання цієї умови до того, як розпочне обробку даних. Якщо умову не виконано, програма повідомить про помилку (див. також I<--resize-force>).
Цей параметр можна вказувати декілька разів.
=item B<--resize-force> РОЗДІЛ=РОЗМІР
-Це те саме, що і I<--resize>, але із можливістю зменшувати розміри будь-яких
-розділів. Загалом, це означає, що ви можете втратити якісь дані, які
-зберігалися наприкінці зменшуваного розділу, але, можливо, ви цим не
-переймаєтеся (наприклад, якщо зменшуєте розмір невикористаного розділу або
-можете легко відтворити вміст розділу, зокрема розділу резервної пам'яті на
-диску).
+Це те саме, що і I<--resize>, але із можливістю зменшувати розміри будь-яких розділів. Загалом, це означає, що ви можете втратити якісь дані, які зберігалися наприкінці зменшуваного розділу, але, можливо, ви цим не переймаєтеся (наприклад, якщо зменшуєте розмір невикористаного розділу або можете легко відтворити вміст розділу, зокрема розділу резервної пам'яті на диску).
Див. також опис параметра I<--ignore>.
=item B<--shrink> РОЗДІЛ
-Зменшити вказаний за назвою розділ у розмірах так, щоб увесь образ диска
-вмістився у образ призначення. Вказаний за назвою розділ B<має> містити
-файлову систему або фізичний том, які вже було зменшено у розмірах за
-допомогою іншого засобу (наприклад L<guestfish(1)> або інших
-програм). Virt-resize виконає перевірку виконання цієї умови і повідомить
-про помилку, якщо попереднього зменшення файлової системи або фізичного тому
-не виконано.
+Зменшити вказаний за назвою розділ у розмірах так, щоб увесь образ диска вмістився у образ призначення. Вказаний за назвою розділ B<має> містити файлову систему або фізичний том, які вже було зменшено у розмірах за допомогою іншого засобу (наприклад L<guestfish(1)> або інших програм). Virt-resize виконає перевірку виконання цієї умови і повідомить про помилку, якщо попереднього зменшення файлової системи або фізичного тому не виконано.
-Об'єм, на який має бути зменшено увесь диск (після виконання усіх інших дій,
-вказаних користувачем), називається «дефіцитом». Наприклад, просте
-копіювання (якщо не виконується жодних інших дій) з образу диска у 5 ГБ на
-образ диска у 4 ГБ дає дефіцит у 1 ГБ. У цьому випадку virt-resize
-повідомить про помилку, якщо користувач не вказав такий розділ для
-стискання, на якому є понад гігабайт вільного місця.
+Об'єм, на який має бути зменшено увесь диск (після виконання усіх інших дій, вказаних користувачем), називається «дефіцитом». Наприклад, просте копіювання (якщо не виконується жодних інших дій) з образу диска у 5 ГБ на образ диска у 4 ГБ дає дефіцит у 1 ГБ. У цьому випадку virt-resize повідомить про помилку, якщо користувач не вказав такий розділ для стискання, на якому є понад гігабайт вільного місця.
-Зауважте, що параметри I<--expand> і I<--shrink> не можна використовувати у
-одній і тій самій команді.
+Зауважте, що параметри I<--expand> і I<--shrink> не можна використовувати у одній і тій самій команді.
=item B<--unknown-filesystems> B<ignore>
=item B<--unknown-filesystems> B<error>
-Налаштувати поведінку virt-resize, якщо програмі надійшла команда розширити
-файлову систему, а у libguestfs не передбачено її підтримки і virt-resize не
-знає способу, як розширити вміст файлової системи.
+Налаштувати поведінку virt-resize, якщо програмі надійшла команда розширити файлову систему, а у libguestfs не передбачено її підтримки і virt-resize не знає способу, як розширити вміст файлової системи.
-Використання параметра I<--unknown-filesystems ignore> призведе до того, що
-virt-resize без додаткових повідомлень ігноруватиме такі файлові системи і
-нічого не виводитиме щодо них.
+Використання параметра I<--unknown-filesystems ignore> призведе до того, що virt-resize без додаткових повідомлень ігноруватиме такі файлові системи і нічого не виводитиме щодо них.
-Використання параметра I<--unknown-filesystems warn> (типове поведінка)
-призводитиме до того, що virt-resize попереджатиме про кожну файлову
-систему, яку не може бути розширено, але продовжуватиме зміну розмірів
-розділів на диску.
+Використання параметра I<--unknown-filesystems warn> (типове поведінка) призводитиме до того, що virt-resize попереджатиме про кожну файлову систему, яку не може бути розширено, але продовжуватиме зміну розмірів розділів на диску.
-Використання параметра I<--unknown-filesystems error> призведе до того, що
-virt-resize повідомлятиме про помилку, якщо виявить файлову систему, розміри
-якої не можна збільшити.
+Використання параметра I<--unknown-filesystems error> призведе до того, що virt-resize повідомлятиме про помилку, якщо виявить файлову систему, розміри якої не можна збільшити.
-Див. також L</"unknown/unavailable method for expanding the TYPE filesystem
-on DEVICE/LV">.
+Див. також L</"unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV">.
=item B<-v>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-resize з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-resize з інших програм, графічних інтерфейсів тощо.
Існує два способи використання цього параметра.
-По-перше, можна скористатися ним без інших параметрів для того, щоб
-дізнатися про можливості виконуваного файла virt-resize. Типові виведені
-дані виглядатимуть так:
+По-перше, можна скористатися ним без інших параметрів для того, щоб дізнатися про можливості виконуваного файла virt-resize. Типові виведені дані виглядатимуть так:
$ virt-resize --machine-readable
virt-resize
ntfs
btrfs
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-По-друге, можна скористатися цим параметром у поєднанні із іншими
-параметрами для того, щоб зробити звичайні виведені програмою дані
-придатнішими для подальшої машинної обробки.
+По-друге, можна скористатися цим параметром у поєднанні із іншими параметрами для того, щоб зробити звичайні виведені програмою дані придатнішими для подальшої машинної обробки.
У поточній версії це означає таке:
=item 1.
-Повідомлення смужки поступу можна обробляти зі стандартного виведення,
-шукаючи їх за таким формальним виразом:
+Повідомлення смужки поступу можна обробляти зі стандартного виведення, шукаючи їх за таким формальним виразом:
^[0-9]+/[0-9]+$
=item 2.
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення
-щодо стану. Ці повідомлення може бути записано до журналу і/або показано
-користувачеві.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення щодо стану. Ці повідомлення може бути записано до журналу і/або показано користувачеві.
=item 3.
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-stderr як повідомлення про помилки. Крім того, virt-resize завершує роботу
-із ненульовим кодом стану, якщо станеться критична помилка.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до stderr як повідомлення про помилки. Крім того, virt-resize завершує роботу із ненульовим кодом стану, якщо станеться критична помилка.
=back
-У версіях програми до 1.13.9 не передбачено використання параметра
-I<--machine-readable>. Якщо цей параметр буде використано для такої версії,
-програма поверне повідомлення про помилку.
+У версіях програми до 1.13.9 не передбачено використання параметра I<--machine-readable>. Якщо цей параметр буде використано для такої версії, програма поверне повідомлення про помилку.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 ПРИМІТКИ
=head2 «Розділ 1 не закінчується на межі циліндра.»
-Virt-resize вирівнює розділи на позиції, кратні до 128 секторів
-(див. параметр I<--alignment>). Зазвичай, це означає, що розділи не буде
-вирівняно за давньою геометрією CHS (циліндр-голівка-сектор). Втім,
-геометрія CHS не має сенсу для дисків, які вироблено після ранніх 1990-х, і
-зовсім не має сенсу для віртуальних жорстких дисків. Вирівнювання розділів
-за циліндрами не є вимогою жодної сучасної операційної системи.
+Virt-resize вирівнює розділи на позиції, кратні до 128 секторів (див. параметр I<--alignment>). Зазвичай, це означає, що розділи не буде вирівняно за давньою геометрією CHS (циліндр-голівка-сектор). Втім, геометрія CHS не має сенсу для дисків, які вироблено після ранніх 1990-х, і зовсім не має сенсу для віртуальних жорстких дисків. Вирівнювання розділів за циліндрами не є вимогою жодної сучасної операційної системи.
=head2 ЗАВАНТАЖЕННЯ ГОСТЬОВОЇ СИСТЕМИ ЗУПИНЯЄТЬСЯ НА «GRUB»
-Якщо гостьова система Linux не завантажується після зміни розміру, і
-завантаження зупиняється після виведення слова C<GRUB> до консолі, спробуйте
-перевстановити grub.
+Якщо гостьова система Linux не завантажується після зміни розміру, і завантаження зупиняється після виведення слова C<GRUB> до консолі, спробуйте перевстановити grub.
guestfish -i -a newdisk
><fs> cat /boot/grub/device.map
><fs> grub-install / /dev/vda
><fs> exit
-Для гнучкішого переналаштовування гостьової системи, зокрема випадків, коли
-вам потрібно вказати інші параметри grub-install, скористайтеся
-L<virt-rescue(1)>.
+Для гнучкішого переналаштовування гостьової системи, зокрема випадків, коли вам потрібно вказати інші параметри grub-install, скористайтеся L<virt-rescue(1)>.
=head2 ЗМІНА РОЗМІРІВ ЗАВАНТАЖУВАЛЬНИХ РОЗДІЛІВ WINDOWS
-У Windows Vista і новіших версіях компанія Microsoft перейшла до
-використання окремого розділу завантаження. У віртуальних машинах із цими
-операційними системами, типово, F</dev/sda1> є розділом завантаження, а
-F</dev/sda2> є основним диском (C:). Зміна розмірів першого розділу (розділу
-завантаження) спричиняє помилку завантажувача C<0xC0000225>. Зміна розмірів
-другого розділу (тобто диска C:) має працювати.
+У Windows Vista і новіших версіях компанія Microsoft перейшла до використання окремого розділу завантаження. У віртуальних машинах із цими операційними системами, типово, F</dev/sda1> є розділом завантаження, а F</dev/sda2> є основним диском (C:). Зміна розмірів першого розділу (розділу завантаження) спричиняє помилку завантажувача C<0xC0000225>. Зміна розмірів другого розділу (тобто диска C:) має працювати.
=head2 WINDOWS CHKDSK
-Диск Windows, на якому використовується NTFS, має бути коректним, перш ніж
-virt-resize зможе ним скористатися. Якщо спроба виконати дію ntfsresize
-завершиться повідомленням про помилку, спробуйте завантажити початкову
-віртуальну машину і запустіть C<chkdsk /f> для усіх розділів NTFS, потім
-завершіть роботу віртуальної машини у штатний спосіб. Докладнішу інформацію
-наведено тут: L<https://bugzilla.redhat.com/show_bug.cgi?id=975753>
+Диск Windows, на якому використовується NTFS, має бути коректним, перш ніж virt-resize зможе ним скористатися. Якщо спроба виконати дію ntfsresize завершиться повідомленням про помилку, спробуйте завантажити початкову віртуальну машину і запустіть C<chkdsk /f> для усіх розділів NTFS, потім завершіть роботу віртуальної машини у штатний спосіб. Докладнішу інформацію наведено тут: L<https://bugzilla.redhat.com/show_bug.cgi?id=975753>
-I<Після зміни розмірів> Windows може ініціювати тривалу обробку chkdsk при
-першому завантаженні, якщо було розширено розділи NTFS. Це усього лише для
-забезпечення надійного зберігання даних, і (якщо не буде знайдено помилок)
-ви можете бути спокійні.
+I<Після зміни розмірів> Windows може ініціювати тривалу обробку chkdsk при першому завантаженні, якщо було розширено розділи NTFS. Це усього лише для забезпечення надійного зберігання даних, і (якщо не буде знайдено помилок) ви можете бути спокійні.
=head2 СИНІЙ ЕКРАН СМЕРТІ UNMOUNTABLE_BOOT_VOLUME У WINDOWS
-Після приготування системи гостьової операційної системи Windows із
-наступною зміною її розміру за допомогою virt-resize ви можете отримати
-непридатну до завантаження систему, яка показуватиме синій екран смерті із
-помилкою C<UNMOUNTABLE_BOOT_VOLUME>. Цю помилку спричинено наявністю рядка
-C<ExtendOemPartition=1> у файлі sysprep.inf. Якщо вилучити цей рядок до
-обробки sysprep, проблема зникає.
+Після приготування системи гостьової операційної системи Windows із наступною зміною її розміру за допомогою virt-resize ви можете отримати непридатну до завантаження систему, яка показуватиме синій екран смерті із помилкою C<UNMOUNTABLE_BOOT_VOLUME>. Цю помилку спричинено наявністю рядка C<ExtendOemPartition=1> у файлі sysprep.inf. Якщо вилучити цей рядок до обробки sysprep, проблема зникає.
=head2 WINDOWS 8
-«Швидкий запуск» Windows 8 може заважати virt-resize змінювати розмір
-розділів NTFS. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК
-WINDOWS 8>.
+«Швидкий запуск» Windows 8 може заважати virt-resize змінювати розмір розділів NTFS. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК WINDOWS 8>.
=head2 РОЗРІДЖЕНЕ КОПІЮВАННЯ
-Вам слід створити новий, заповнений нулями образ диска призначення, який
-використовуватиме virt-resize.
+Вам слід створити новий, заповнений нулями образ диска призначення, який використовуватиме virt-resize.
-Virt-resize типово виконує розріджене копіювання. Це означає, що програма не
-копіює ті блоки з початкового диска, які заповнено лише нулями. Це підвищує
-швидкість та ефективність роботи, але може призвести до некоректних
-результатів, якщо на образі диска призначення є незанулені дані.
+Virt-resize типово виконує розріджене копіювання. Це означає, що програма не копіює ті блоки з початкового диска, які заповнено лише нулями. Це підвищує швидкість та ефективність роботи, але може призвести до некоректних результатів, якщо на образі диска призначення є незанулені дані.
-В основному, така проблема виникає, якщо образом призначення є розділ
-основної системи (наприклад, S<C<virt-resize source.img /dev/sda4>>),
-оскільки звичайні інструменти поділу диска на розділи лишають недоторканними
-усі дані, які раніше зберігалися на диску.
+В основному, така проблема виникає, якщо образом призначення є розділ основної системи (наприклад, S<C<virt-resize source.img /dev/sda4>>), оскільки звичайні інструменти поділу диска на розділи лишають недоторканними усі дані, які раніше зберігалися на диску.
-Якщо ви змушені використатися образ призначення, на якому вже зберігалися
-дані, вам слід скористатися параметром I<--no-sparse>. Зауважте, що це
-значно уповільнить роботу програми.
+Якщо ви змушені використатися образ призначення, на якому вже зберігалися дані, вам слід скористатися параметром I<--no-sparse>. Зауважте, що це значно уповільнить роботу програми.
=head2 "unknown/unavailable method for expanding the TYPE filesystem on DEVICE/LV"
-Virt-resize було наказано розширити розділ або логічний том, на якому
-міститься файлова система типу C<TYPE>, але програмі недоступний або
-невідомий спосіб розширення цієї файлової системи.
+Virt-resize було наказано розширити розділ або логічний том, на якому міститься файлова система типу C<TYPE>, але програмі недоступний або невідомий спосіб розширення цієї файлової системи.
Причиною може бути будь-що із наведеного нижче:
=item 1.
-Відповідна файлова система недоступна у libguestfs, оскільки у основній
-системі немає належного пакунка із інструментами для роботи з цією файловою
-системою. Таке, зазвичай, трапляється із файловими системами C<btrfs>,
-C<ntfs>, C<xfs> та C<f2fs>.
+Відповідна файлова система недоступна у libguestfs, оскільки у основній системі немає належного пакунка із інструментами для роботи з цією файловою системою. Таке, зазвичай, трапляється із файловими системами C<btrfs>, C<ntfs>, C<xfs> та C<f2fs>.
Спробуйте такі команди:
guestfish -a /dev/null run : available
guestfish -a /dev/null run : filesystem_available TYPE
-У цьому випадку достатньо встановити належні пакунки із підтримкою файлових
-систем. Наприклад, достатньо встановити C<libguestfs-xfs> у Red Hat
-Enterprise Linux, CentOS, Debian, Ubuntu та дистрибутивах, які від них
-походять, щоб можна було працювати із файловою системою C<xfs>.
+У цьому випадку достатньо встановити належні пакунки із підтримкою файлових систем. Наприклад, достатньо встановити C<libguestfs-xfs> у Red Hat Enterprise Linux, CentOS, Debian, Ubuntu та дистрибутивах, які від них походять, щоб можна було працювати із файловою системою C<xfs>.
=item 2.
-У virt-resize не передбачено підтримки розширення цього типу файлових
-систем.
+У virt-resize не передбачено підтримки розширення цього типу файлових систем.
-У цьому випадку нічого не поробиш: virt-resize не зможе розширити файлову
-систему цього типу.
+У цьому випадку нічого не поробиш: virt-resize не зможе розширити файлову систему цього типу.
=back
-In both cases, virt-resize will not expand the mentioned filesystem; the
-result (unless I<--unknown-filesystems error> is specified) is that the
-partitions containing such filesystems will be actually bigger as requested,
-but the filesystems will still be usable at their older sizes.
+In both cases, virt-resize will not expand the mentioned filesystem; the result (unless I<--unknown-filesystems error> is specified) is that the partitions containing such filesystems will be actually bigger as requested, but the filesystems will still be usable at their older sizes.
=head1 АЛЬТЕРНАТИВНІ ІНСТРУМЕНТИ
-Існує декілька пропрієтарних інструментів для зміни розмірів розділів. Тут
-ми не будемо згадувати назви жодного з таких інструментів.
+Існує декілька пропрієтарних інструментів для зміни розмірів розділів. Тут ми не будемо згадувати назви жодного з таких інструментів.
-L<parted(8)> і її графічний інтерфейс, gparted, можуть виконувати певні типи
-дій із зміни розміру образів дисків. Ці програми можуть змінювати розмір і
-пересувати розділи, але не слід вважати, що вони можуть виконувати будь-які
-дії із вмістом розділів, і, звичайно ж, вони не можуть працювати з LVM.
+L<parted(8)> і її графічний інтерфейс, gparted, можуть виконувати певні типи дій із зміни розміру образів дисків. Ці програми можуть змінювати розмір і пересувати розділи, але не слід вважати, що вони можуть виконувати будь-які дії із вмістом розділів, і, звичайно ж, вони не можуть працювати з LVM.
-L<guestfish(1)> може виконувати усі ті дії, які може виконувати virt-resize,
-і набагато більше, але на суттєво нижчому рівні. Ймовірно, вам доведеться
-вручну обчислювати відступи у секторах, робити те, що за означенням має
-робити virt-resize. Якщо хочете дізнатися, які команди у guestfish запускає
-virt-resize, скористайтеся параметром I<--debug>.
+L<guestfish(1)> може виконувати усі ті дії, які може виконувати virt-resize, і набагато більше, але на суттєво нижчому рівні. Ймовірно, вам доведеться вручну обчислювати відступи у секторах, робити те, що за означенням має робити virt-resize. Якщо хочете дізнатися, які команди у guestfish запускає virt-resize, скористайтеся параметром I<--debug>.
-До складу L<dracut(8)> включено модуль із назвою C<dracut-modules-growroot>,
-яким можна скористатися для збільшення розмірів кореневого розділу під час
-першого завантаження гостьової системи. Документацію з цього модуля наведено
-у пов'язаному із ним файлі README.
+До складу L<dracut(8)> включено модуль із назвою C<dracut-modules-growroot>, яким можна скористатися для збільшення розмірів кореневого розділу під час першого завантаження гостьової системи. Документацію з цього модуля наведено у пов'язаному із ним файлі README.
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<virt-filesystems(1)>, L<virt-df(1)>, L<guestfs(3)>, L<guestfish(1)>,
-L<lvm(8)>, L<pvresize(8)>, L<lvresize(8)>, L<resize2fs(8)>,
-L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)>, L<resize.f2fs(8)>,
-L<virsh(1)>, L<parted(8)>, L<truncate(1)>, L<fallocate(1)>, L<grub(8)>,
-L<grub-install(8)>, L<virt-rescue(1)>, L<virt-sparsify(1)>,
-L<virt-alignment-scan(1)>, L<http://libguestfs.org/>.
+L<virt-filesystems(1)>, L<virt-df(1)>, L<guestfs(3)>, L<guestfish(1)>, L<lvm(8)>, L<pvresize(8)>, L<lvresize(8)>, L<resize2fs(8)>, L<ntfsresize(8)>, L<btrfs(8)>, L<xfs_growfs(8)>, L<resize.f2fs(8)>, L<virsh(1)>, L<parted(8)>, L<truncate(1)>, L<fallocate(1)>, L<grub(8)>, L<grub-install(8)>, L<virt-rescue(1)>, L<virt-sparsify(1)>, L<virt-alignment-scan(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-sparsify 1"
-.TH virt-sparsify 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-sparsify 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-sparsify — інструмент, який може зробити диск віртуальної машини (або
-будь\-який образ диска) розрідженим, тобто спеціально зменшеним. Це означає,
-що вільне місце в образі диска можна буде перетворити на вільне місце в
-основній системі.
-.PP
-Virt-sparsify може знаходити і розріджувати вільне місце у більшості
-файлових систем (наприклад у ext2/3/4, btrfs, \s-1NTFS\s0 тощо), а також у фізичних
-томах \s-1LVM.\s0
-.PP
-Крім того, програма virt-sparsify може перетворювати диски з одного формату
-на інший, наприклад, перетворити образ диска у простому форматі (raw) на
-розріджений образ у форматі qcow2.
-.PP
-Virt-sparsify може працювати з будь\-яким образом диска, не лише з образами
-віртуальних машин. Втім, якщо у вашій віртуальній машині декілька дисків і
-використано керування томами, virt-sparsify працюватиме, але не дуже
-ефективно (http://bugzilla.redhat.com/887826).
+Virt-sparsify — інструмент, який може зробити диск віртуальної машини (або будь\-який образ диска) розрідженим, тобто спеціально зменшеним. Це означає, що вільне місце в образі диска можна буде перетворити на вільне місце в основній системі.
+.PP
+Virt-sparsify може знаходити і розріджувати вільне місце у більшості файлових систем (наприклад у ext2/3/4, btrfs, \s-1NTFS\s0 тощо), а також у фізичних томах \s-1LVM.\s0
+.PP
+Крім того, програма virt-sparsify може перетворювати диски з одного формату на інший, наприклад, перетворити образ диска у простому форматі (raw) на розріджений образ у форматі qcow2.
+.PP
+Virt-sparsify може працювати з будь\-яким образом диска, не лише з образами віртуальних машин. Втім, якщо у вашій віртуальній машині декілька дисків і використано керування томами, virt-sparsify працюватиме, але не дуже ефективно (http://bugzilla.redhat.com/887826).
.SS "ВАЖЛИВЕ ЗАУВАЖЕННЯ ЩОДО РОЗРІДЖЕНИХ ВИВЕДЕНИХ ОБРАЗІВ"
.IX Subsection "ВАЖЛИВЕ ЗАУВАЖЕННЯ ЩОДО РОЗРІДЖЕНИХ ВИВЕДЕНИХ ОБРАЗІВ"
-Якщо вхідними даними є образ raw, буде виведено розріджені дані raw. \fBВам
-слід перевірити розмір виведених даних за допомогою інструмента, який
-обробляє розріджені дані\fR, наприклад \f(CW\*(C`du \-sh\*(C'\fR. Різниця може бути досить
-значною:
+Якщо вхідними даними є образ raw, буде виведено розріджені дані raw. \fBВам слід перевірити розмір виведених даних за допомогою інструмента, який обробляє розріджені дані\fR, наприклад \f(CW\*(C`du \-sh\*(C'\fR. Різниця може бути досить значною:
.PP
.Vb 4
\& $ ls \-lh test1.img
.IP "\(bu" 4
До використання цього інструмента віртуальну машину \fIслід зупинити\fR.
.IP "\(bu" 4
-Virt-sparsify може потребувати для роботи удвічі більшого місця на диску,
-ніж розмір початкового образу диска (1 тимчасова копія + 1 образ
-призначення). Ця оцінка є максимальною, і зазвичай потрібно набагато менше
-місця.
+Virt-sparsify може потребувати для роботи удвічі більшого місця на диску, ніж розмір початкового образу диска (1 тимчасова копія + 1 образ призначення). Ця оцінка є максимальною, і зазвичай потрібно набагато менше місця.
.Sp
-Якщо ви використовуєте параметр \fI\-\-in\-place\fR, значні обсяги місця на диску
-для тимчасового зберігання даних \fBне\fR знадобляться.
+Якщо ви використовуєте параметр \fI\-\-in\-place\fR, значні обсяги місця на диску для тимчасового зберігання даних \fBне\fR знадобляться.
.IP "\(bu" 4
-Virt-sparsify не може змінювати розміри образів дисків. Для зміни розмірів
-дисків скористайтеся \fBvirt\-resize\fR\|(1).
+Virt-sparsify не може змінювати розміри образів дисків. Для зміни розмірів дисків скористайтеся \fBvirt\-resize\fR\|(1).
.IP "\(bu" 4
-Virt-sparsify не може працювати із зашифрованими дисками. У libguestfs
-передбачено підтримку самих зашифрованих дисків, але зашифровані диски не
-може бути розріджено.
+Virt-sparsify не може працювати із зашифрованими дисками. У libguestfs передбачено підтримку самих зашифрованих дисків, але зашифровані диски не може бути розріджено.
.IP "\(bu" 4
-Virt-sparsify ще не може розріджувати місце між розділами. Зауважте, що це
-місце часто використовується для критичних даних, зокрема завантажувачів,
-тому, насправді, воно може бути зовсім не таким зайвим, як може здатися.
+Virt-sparsify ще не може розріджувати місце між розділами. Зауважте, що це місце часто використовується для критичних даних, зокрема завантажувачів, тому, насправді, воно може бути зовсім не таким зайвим, як може здатися.
.IP "\(bu" 4
-У режимі копіювання внутрішні знімки qcow2 не копіюються на образ
-призначення.
+У режимі копіювання внутрішні знімки qcow2 не копіюються на образ призначення.
.PP
-Перш ніж розпочати користування цією програмою, вам також варто ознайомитися
-зі сторінками підручника щодо пов'язаних із нею інструментів,
-\&\fBvirt\-filesystems\fR\|(1) та \fBvirt\-df\fR\|(1).
+Перш ніж розпочати користування цією програмою, вам також варто ознайомитися зі сторінками підручника щодо пов'язаних із нею інструментів, \fBvirt\-filesystems\fR\|(1) та \fBvirt\-df\fR\|(1).
.SH "ПРИКЛАДИ"
.IX Header "ПРИКЛАДИ"
Типовий приклад використання:
\& virt\-sparsify вхідний_диск вихідний_диск
.Ve
.PP
-Ця команда копіює \f(CW\*(C`вхідний_диск\*(C'\fR на диск \f(CW\*(C`вихідний_диск\*(C'\fR, роблячи
-результат розрідженим. Диск \f(CW\*(C`вихідний_диск\*(C'\fR буде створено або перезаписано,
-якщо такий диск уже існує. Програма сама визначить формат вхідного диска
-(наприклад qcow2) і використає той самий формат для вихідного диска.
+Ця команда копіює \f(CW\*(C`вхідний_диск\*(C'\fR на диск \f(CW\*(C`вихідний_диск\*(C'\fR, роблячи результат розрідженим. Диск \f(CW\*(C`вихідний_диск\*(C'\fR буде створено або перезаписано, якщо такий диск уже існує. Програма сама визначить формат вхідного диска (наприклад qcow2) і використає той самий формат для вихідного диска.
.PP
-Для перетворення диска з одного формату на інший скористайтеся параметром
-\&\fI\-\-convert\fR:
+Для перетворення диска з одного формату на інший скористайтеся параметром \fI\-\-convert\fR:
.PP
.Vb 1
\& virt\-sparsify disk.raw \-\-convert qcow2 disk.qcow2
.Ve
.PP
-Virt-sparsify намагається занулити і розрідити вільне місце на усіх файлових
-системах, які вдасться знайти на початковому образі диска. Ви можете
-наказати програмі ігнорувати (не занулювати вільне місце) певні файлові
-системи за допомогою такої команди:
+Virt-sparsify намагається занулити і розрідити вільне місце на усіх файлових системах, які вдасться знайти на початковому образі диска. Ви можете наказати програмі ігнорувати (не занулювати вільне місце) певні файлові системи за допомогою такої команди:
.PP
.Vb 1
\& virt\-sparsify \-\-ignore /dev/sda1 вхідний_диск вихідний_диск
.Ve
.PP
-Щоб отримати список файлових систем на образі диска, скористайтеся командою
-\&\fBvirt\-filesystems\fR\|(1).
+Щоб отримати список файлових систем на образі диска, скористайтеся командою \fBvirt\-filesystems\fR\|(1).
.PP
-Починаючи з версії virt-sparsify ≥ 1.26, ви можете розріджувати образ
-диска на місці, ось так:
+Починаючи з версії virt-sparsify ≥ 1.26, ви можете розріджувати образ диска на місці, ось так:
.PP
.Vb 1
\& virt\-sparsify \-\-in\-place disk.img
.IP "\fB\-\-check\-tmpdir\fR \fBfail\fR" 4
.IX Item "--check-tmpdir fail"
.PD
-Переконайтеся, чи достатньо вільного місця у каталозі, вказаному за
-допомогою змінної середовища \*(L"\s-1TMPDIR\*(R"\s0 або параметра \fI\-\-tmp\fR, для
-завершення дії. Це лише оцінка.
+Переконайтеся, чи достатньо вільного місця у каталозі, вказаному за допомогою змінної середовища \*(L"\s-1TMPDIR\*(R"\s0 або параметра \fI\-\-tmp\fR, для завершення дії. Це лише оцінка.
.Sp
-Якщо під час перевірки буде виявлено проблему, ви можете піти одним з таких
-шляхів:
+Якщо під час перевірки буде виявлено проблему, ви можете піти одним з таких шляхів:
.RS 4
.IP "\(bu" 4
\&\fBігнорувати\fR її,
.IP "\(bu" 4
вивести попередження і \fBпродовжити\fR,
.IP "\(bu" 4
-\&\fBпопередити\fR і почекати, доки користувач натисне клавішу Enter (типова
-поведінка) або
+\&\fBпопередити\fR і почекати, доки користувач натисне клавішу Enter (типова поведінка) або
.IP "\(bu" 4
\&\fBвивести попередження про помилку\fR і завершити роботу.
.RE
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-\-compress\fR" 4
.IX Item "--compress"
-Стиснути файл виведених даних. Це працює, \fIлише\fR якщо форматом виведення
-даних є \f(CW\*(C`qcow2\*(C'\fR.
+Стиснути файл виведених даних. Це працює, \fIлише\fR якщо форматом виведення даних є \f(CW\*(C`qcow2\*(C'\fR.
.Sp
Цей параметр не можна поєднувати із параметром \fI\-\-in\-place\fR.
.IP "\fB\-\-convert\fR raw" 4
.IP "\fB\-\-convert\fR [інші формати]" 4
.IX Item "--convert [інші формати]"
.PD
-Використовувати \f(CW\*(C`формат виведення\*(C'\fR як формат образу призначення. Якщо цей
-параметр не вказано, буде використано той самий формат, що і у вхідних
-даних.
+Використовувати \f(CW\*(C`формат виведення\*(C'\fR як формат образу призначення. Якщо цей параметр не вказано, буде використано той самий формат, що і у вхідних даних.
.Sp
-Підтримуваними і працездатними форматами виведення є такі: \f(CW\*(C`raw\*(C'\fR, \f(CW\*(C`qcow2\*(C'\fR,
-\&\f(CW\*(C`vdi\*(C'\fR.
+Підтримуваними і працездатними форматами виведення є такі: \f(CW\*(C`raw\*(C'\fR, \f(CW\*(C`qcow2\*(C'\fR, \f(CW\*(C`vdi\*(C'\fR.
.Sp
-Ви також можете скористатися будь\-яким іншим форматом, підтримку якого
-передбачено у програми \fBqemu\-img\fR\|(1), наприклад \f(CW\*(C`vmdk\*(C'\fR, але підтримка
-інших форматів повністю залежить від можливостей qemu.
+Ви також можете скористатися будь\-яким іншим форматом, підтримку якого передбачено у програми \fBqemu\-img\fR\|(1), наприклад \f(CW\*(C`vmdk\*(C'\fR, але підтримка інших форматів повністю залежить від можливостей qemu.
.Sp
-Зазвичай, варто визначати формат за допомогою \fI\-\-convert\fR, оскільки тоді
-virt-sparsify не доведеться вгадувати формат вхідних даних.
+Зазвичай, варто визначати формат за допомогою \fI\-\-convert\fR, оскільки тоді virt-sparsify не доведеться вгадувати формат вхідних даних.
.Sp
-Скоригувати формат виведення даних можна за допомогою параметрів
-\&\fI\-\-compress\fR, \fI\-o\fR.
+Скоригувати формат виведення даних можна за допомогою параметрів \fI\-\-compress\fR, \fI\-o\fR.
.Sp
Цей параметр не можна поєднувати із параметром \fI\-\-in\-place\fR.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-sparcify попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-sparcify попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format\fR raw" 4
.IX Item "--format raw"
.PD 0
.IP "\fB\-\-format\fR qcow2" 4
.IX Item "--format qcow2"
.PD
-Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано,
-його буде автоматично визначено на основі даних самого образу.
+Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого образу.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.IP "\fB\-\-ignore\fR файлова_система" 4
.IX Item "--ignore файлова_система"
.PD 0
.PD
Ігнорувати вказану файлову систему.
.Sp
-Якщо не використовується \fI\-\-in\-place\fR, вільне місце у файловій системі не
-буде занулено, але наявні нульові блоки все одно буде розріджено.
+Якщо не використовується \fI\-\-in\-place\fR, вільне місце у файловій системі не буде занулено, але наявні нульові блоки все одно буде розріджено.
.Sp
-Якщо використовується \fI\-\-in\-place\fR, файлову систему буде повністю
-проігноровано.
+Якщо використовується \fI\-\-in\-place\fR, файлову систему буде повністю проігноровано.
.Sp
-У другій формі команда призведе до ігнорування вказаної за назвою групи
-томів. Використовуйте назву групи томів без префікса \fI/dev/\fR, наприклад
-\&\fI\-\-ignore vg_foo\fR
+У другій формі команда призведе до ігнорування вказаної за назвою групи томів. Використовуйте назву групи томів без префікса \fI/dev/\fR, наприклад \fI\-\-ignore vg_foo\fR
.Sp
Цей параметр можна вказувати декілька разів.
.IP "\fB\-\-in\-place\fR" 4
.IX Item "--in-place"
-Виконати розрідження на місці замість розрідження копіюванням. Див. розділ
-\&\*(L"РОЗРІДЖЕННЯ НА МІСЦІ\*(R" нижче.
+Виконати розрідження на місці замість розрідження копіюванням. Див. розділ \*(L"РОЗРІДЖЕННЯ НА МІСЦІ\*(R" нижче.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IP "\fB\-\-machine\-readable\fR=формат" 4
.IX Item "--machine-readable=формат"
.PD
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. \*(L"ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" нижче.
.IP "\fB\-o\fR параметр[,параметр,...]" 4
.IX Item "-o параметр[,параметр,...]"
-Передати параметри \fI\-o\fR до програми \fBqemu\-img\fR\|(1) для коригування формату
-виведення даних. Перелік доступних параметрів залежить від формату
-виведення (див. \fI\-\-convert\fR) і встановленої версії програми qemu-img.
+Передати параметри \fI\-o\fR до програми \fBqemu\-img\fR\|(1) для коригування формату виведення даних. Перелік доступних параметрів залежить від формату виведення (див. \fI\-\-convert\fR) і встановленої версії програми qemu-img.
.Sp
-Вам слід скористатися \fI\-o\fR не більше одного разу. Щоб передати декілька
-параметрів, відокремте їх комами. Приклад:
+Вам слід скористатися \fI\-o\fR не більше одного разу. Щоб передати декілька параметрів, відокремте їх комами. Приклад:
.Sp
.Vb 2
\& virt\-sparsify \-\-convert qcow2 \e
.IP "\fB\-\-tmp\fR каталог" 4
.IX Item "--tmp каталог"
.PD
-Лише у режимі копіювання, використати вказаний за назвою пристрій або
-каталог як місце для тимчасової накладки (див. також \*(L"\s-1TMPDIR\*(R"\s0 нижче).
+Лише у режимі копіювання, використати вказаний за назвою пристрій або каталог як місце для тимчасової накладки (див. також \*(L"\s-1TMPDIR\*(R"\s0 нижче).
.Sp
-Якщо як параметр вказано блоковий пристрій, блоковий пристрій буде записано
-безпосередньо. \fBЗауважте, що при цьому з блокового пристрою буде повністю
-витерто наявні дані\fR.
+Якщо як параметр вказано блоковий пристрій, блоковий пристрій буде записано безпосередньо. \fBЗауважте, що при цьому з блокового пристрою буде повністю витерто наявні дані\fR.
.Sp
-Якщо як параметр вказано каталог, визначення параметра буде рівнозначним
-заданню значення змінної середовища \*(L"\s-1TMPDIR\*(R"\s0.
+Якщо як параметр вказано каталог, визначення параметра буде рівнозначним заданню значення змінної середовища \*(L"\s-1TMPDIR\*(R"\s0.
.Sp
Цей параметр не можна поєднувати із параметром \fI\-\-in\-place\fR.
.IP "\fB\-\-tmp\fR prebuilt:файл" 4
.IX Item "--tmp prebuilt:файл"
-Лише у режимі копіювання, спеціалізований параметр \fI\-\-tmp prebuilt:файл\fR
-(де \f(CW\*(C`prebuilt:\*(C'\fR слід записувати буквально) наказує virt-sparsify
-використовувати як місце зберігання тимчасових даних файл qcow2 \f(CW\*(C`файл\*(C'\fR.
+Лише у режимі копіювання, спеціалізований параметр \fI\-\-tmp prebuilt:файл\fR (де \f(CW\*(C`prebuilt:\*(C'\fR слід записувати буквально) наказує virt-sparsify використовувати як місце зберігання тимчасових даних файл qcow2 \f(CW\*(C`файл\*(C'\fR.
.RS 4
.IP "\(bu" 4
-Файл \fBмає\fR бути наново форматовано як qcow2, а вхідний диск буде резервним
-файлом.
+Файл \fBмає\fR бути наново форматовано як qcow2, а вхідний диск буде резервним файлом.
.IP "\(bu" 4
-Якщо ви повторно запускатимете virt-sparsify, вам \fBслід\fR повторно
-створювати файл перед кожним запуском.
+Якщо ви повторно запускатимете virt-sparsify, вам \fBслід\fR повторно створювати файл перед кожним запуском.
.IP "\(bu" 4
Virt-sparsify не вилучає цей файл.
.RE
.RS 4
.Sp
-Цей параметр використовується oVirt, де потрібен спеціальним чином
-форматований тимчасовий файл.
+Цей параметр використовується oVirt, де потрібен спеціальним чином форматований тимчасовий файл.
.RE
.IP "\fB\-v\fR" 4
.IX Item "-v"
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.IP "\fB\-\-zero\fR логічний_том" 4
.IX Item "--zero логічний_том"
.PD
-Занулити вміст вказаного за назвою розділу або логічного тому у гостьовій
-системі. Усі дані на пристрої буде втрачено, але буде досягнуто чудової
-розрідженості! Цей параметр можна вказувати в одній команді декілька разів.
+Занулити вміст вказаного за назвою розділу або логічного тому у гостьовій системі. Усі дані на пристрої буде втрачено, але буде досягнуто чудової розрідженості! Цей параметр можна вказувати в одній команді декілька разів.
.SH "РОЗРІДЖЕННЯ НА МІСЦІ"
.IX Header "РОЗРІДЖЕННЯ НА МІСЦІ"
-Починаючи з virt-sparsify ≥ 1.26, програма може виконувати розрідження
-на місці (замість копіювання з вхідного диска до вихідного диска). Таке
-розрідження є ефективнішим. Втім, за його використання не можна отримати
-більше місця у основній системі, якщо порівнювати із розрідженням із
-копіюванням.
+Починаючи з virt-sparsify ≥ 1.26, програма може виконувати розрідження на місці (замість копіювання з вхідного диска до вихідного диска). Таке розрідження є ефективнішим. Втім, за його використання не можна отримати більше місця у основній системі, якщо порівнювати із розрідженням із копіюванням.
.PP
-Щоб скористатися цим режимом, вкажіть образ диска, який буде змінено на
-місці:
+Щоб скористатися цим режимом, вкажіть образ диска, який буде змінено на місці:
.PP
.Vb 1
\& virt\-sparsify \-\-in\-place disk.img
.Ve
.PP
-Деякі параметри несумісні із цим режимом: \fI\-\-convert\fR, \fI\-\-compress\fR і
-\&\fI\-o\fR, оскільки їхнє використання вимагає загальної зміни формату диска;
-\&\fI\-\-check\-tmpdir\fR, оскільки великі обсяги для зберігання тимчасових даних не
-потрібні.
+Деякі параметри несумісні із цим режимом: \fI\-\-convert\fR, \fI\-\-compress\fR і \fI\-o\fR, оскільки їхнє використання вимагає загальної зміни формату диска; \fI\-\-check\-tmpdir\fR, оскільки великі обсяги для зберігання тимчасових даних не потрібні.
.PP
-Розрідження на місці працює завдяки підтримці відкидання (або обрізання чи
-скасування отримання пам'яті).
+Розрідження на місці працює завдяки підтримці відкидання (або обрізання чи скасування отримання пам'яті).
.SH "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
.IX Header "ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ"
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра
-робить зручним використання virt-sparcify з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром \fI\-\-machine\-readable\fR. Додавання цього параметра робить зручним використання virt-sparcify з інших програм, графічних інтерфейсів тощо.
.PP
Існує два способи використання цього параметра.
.PP
-Спочатку, скористайтеся цим параметром окремо, щоб опитати систему щодо
-можливостей виконуваного файла virt-sparcify. Типово виведені дані
-виглядатимуть якось так:
+Спочатку, скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-sparcify. Типово виведені дані виглядатимуть якось так:
.PP
.Vb 4
\& $ virt\-sparsify \-\-machine\-readable
\& btrfs
.Ve
.PP
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
.PP
-По\-друге, можна скористатися цим параметром у поєднанні із іншими
-параметрами для того, щоб зробити звичайні виведені програмою дані
-придатнішими для подальшої машинної обробки.
+По\-друге, можна скористатися цим параметром у поєднанні із іншими параметрами для того, щоб зробити звичайні виведені програмою дані придатнішими для подальшої машинної обробки.
.PP
У поточній версії це означає таке:
.IP "1." 4
-Повідомлення смужки поступу можна обробляти зі стандартного виведення,
-шукаючи їх за таким формальним виразом:
+Повідомлення смужки поступу можна обробляти зі стандартного виведення, шукаючи їх за таким формальним виразом:
.Sp
.Vb 1
\& ^[0\-9]+/[0\-9]+$
.Ve
.IP "2." 4
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення
-щодо стану. Ці повідомлення може бути записано до журналу і/або показано
-користувачеві.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення щодо стану. Ці повідомлення може бути записано до журналу і/або показано користувачеві.
.IP "3." 4
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-stderr як повідомлення про помилки. Крім того, virt-sparcify завершує роботу
-із ненульовим кодом стану, якщо станеться критична помилка.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до stderr як повідомлення про помилки. Крім того, virt-sparcify завершує роботу із ненульовим кодом стану, якщо станеться критична помилка.
.PP
-Підтримку параметра \fI\-\-machine\-readable\fR передбачено у всіх версіях
-virt-sparsify.
+Підтримку параметра \fI\-\-machine\-readable\fR передбачено у всіх версіях virt-sparsify.
.PP
-Можна вказати рядок форматування для керування виведенням,
-див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
+Можна вказати рядок форматування для керування виведенням, див. \*(L"РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ\*(R" in \fBguestfs\fR\|(3).
.SH "WINDOWS 8"
.IX Header "WINDOWS 8"
-«Швидкий запуск» Windows 8 може заважати роботі
-virt-sparsify. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК
-\&\s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
+«Швидкий запуск» Windows 8 може заважати роботі virt-sparsify. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК \s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
.IP "ТИМЧАСОВИЙ КАТАЛОГ" 4
.IX Item "ТИМЧАСОВИЙ КАТАЛОГ"
-Розташування каталогу тимчасових даних, який використовуватиметься для
-потенційно великих тимчасових файлів\-накладок.
+Розташування каталогу тимчасових даних, який використовуватиметься для потенційно великих тимчасових файлів\-накладок.
.Sp
-У virt-sparsify ≥ 1.28 ви можете перевизначити цю змінну середовища за
-допомогою параметра \fI\-\-tmp\fR.
+У virt-sparsify ≥ 1.28 ви можете перевизначити цю змінну середовища за допомогою параметра \fI\-\-tmp\fR.
.Sp
-На диску має бути достатньо вільного місця для найгіршого варіанта для
-повної копії початкового диска (\fIвіртуального\fR розміру). Якщо місця
-недостатньо, слід встановити для \f(CW$TMPDIR\fR значення, яке вказує на інший
-каталог, де достатньо місця.
+На диску має бути достатньо вільного місця для найгіршого варіанта для повної копії початкового диска (\fIвіртуального\fR розміру). Якщо місця недостатньо, слід встановити для \f(CW$TMPDIR\fR значення, яке вказує на інший каталог, де достатньо місця.
.Sp
Типовим значенням є \fI/tmp\fR.
.Sp
-Зауважте, що якщо файловою системою у \f(CW$TMPDIR\fR є tmpfs (наприклад, якщо
-файловою системою \fI/tmp\fR є tmpfs, або якщо ви використовуєте
-\&\f(CW\*(C`TMPDIR=/dev/shm\*(C'\fR), типовим розміром tmpfs є максимальне значення
-\&\fIполовини\fR фізичної оперативної пам'яті. Якщо virt-sparsify знадобиться
-більше місця, програма просто «повисне». Якщо ви побоюєтеся такого перебігу
-подій, або скористайтеся реальним диском, або збільште максимальний розмір
-точки монтування tmpfs, наприклад так:
+Зауважте, що якщо файловою системою у \f(CW$TMPDIR\fR є tmpfs (наприклад, якщо файловою системою \fI/tmp\fR є tmpfs, або якщо ви використовуєте \f(CW\*(C`TMPDIR=/dev/shm\*(C'\fR), типовим розміром tmpfs є максимальне значення \fIполовини\fR фізичної оперативної пам'яті. Якщо virt-sparsify знадобиться більше місця, програма просто «повисне». Якщо ви побоюєтеся такого перебігу подій, або скористайтеся реальним диском, або збільште максимальний розмір точки монтування tmpfs, наприклад так:
.Sp
.Vb 1
\& mount \-o remount,size=10G /tmp
.Ve
.Sp
-Якщо ви використовуєте параметр \fI\-\-in\-place\fR, значні обсяги місця на диску
-для тимчасового зберігання даних \fBне\fR знадобляться.
+Якщо ви використовуєте параметр \fI\-\-in\-place\fR, значні обсяги місця на диску для тимчасового зберігання даних \fBне\fR знадобляться.
.PP
-Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT
-VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає 0, якщо дію виконано без жодної помилки (це не
-обов'язково означає, що місце на диску звільнилося).
+Ця програма повертає 0, якщо дію виконано без жодної помилки (це не обов'язково означає, що місце на диску звільнилося).
.PP
Ненульовий код виходу вказує на помилку.
.PP
-Якщо повернуто код виходу \f(CW3\fR і було використано параметр \fI\-\-in\-place\fR, це
-означає, що у libguestfs не передбачено підтримки відкидання зайвого місця
-на диску, отже, доведеться користуватися режимом копіювання.
+Якщо повернуто код виходу \f(CW3\fR і було використано параметр \fI\-\-in\-place\fR, це означає, що у libguestfs не передбачено підтримки відкидання зайвого місця на диску, отже, доведеться користуватися режимом копіювання.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBvirt\-df\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-rescue\fR\|(1),
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1),
-\&\fBqemu\-img\fR\|(1), http://libguestfs.org/.
+\&\fBvirt\-df\fR\|(1), \fBvirt\-filesystems\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBtruncate\fR\|(1), \fBfallocate\fR\|(1), \fBqemu\-img\fR\|(1), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 ОПИС
-Virt-sparsify — інструмент, який може зробити диск віртуальної машини (або
-будь-який образ диска) розрідженим, тобто спеціально зменшеним. Це означає,
-що вільне місце в образі диска можна буде перетворити на вільне місце в
-основній системі.
+Virt-sparsify — інструмент, який може зробити диск віртуальної машини (або будь-який образ диска) розрідженим, тобто спеціально зменшеним. Це означає, що вільне місце в образі диска можна буде перетворити на вільне місце в основній системі.
-Virt-sparsify може знаходити і розріджувати вільне місце у більшості
-файлових систем (наприклад у ext2/3/4, btrfs, NTFS тощо), а також у фізичних
-томах LVM.
+Virt-sparsify може знаходити і розріджувати вільне місце у більшості файлових систем (наприклад у ext2/3/4, btrfs, NTFS тощо), а також у фізичних томах LVM.
-Крім того, програма virt-sparsify може перетворювати диски з одного формату
-на інший, наприклад, перетворити образ диска у простому форматі (raw) на
-розріджений образ у форматі qcow2.
+Крім того, програма virt-sparsify може перетворювати диски з одного формату на інший, наприклад, перетворити образ диска у простому форматі (raw) на розріджений образ у форматі qcow2.
-Virt-sparsify може працювати з будь-яким образом диска, не лише з образами
-віртуальних машин. Втім, якщо у вашій віртуальній машині декілька дисків і
-використано керування томами, virt-sparsify працюватиме, але не дуже
-ефективно (L<http://bugzilla.redhat.com/887826>).
+Virt-sparsify може працювати з будь-яким образом диска, не лише з образами віртуальних машин. Втім, якщо у вашій віртуальній машині декілька дисків і використано керування томами, virt-sparsify працюватиме, але не дуже ефективно (L<http://bugzilla.redhat.com/887826>).
=head2 ВАЖЛИВЕ ЗАУВАЖЕННЯ ЩОДО РОЗРІДЖЕНИХ ВИВЕДЕНИХ ОБРАЗІВ
-Якщо вхідними даними є образ raw, буде виведено розріджені дані raw. B<Вам
-слід перевірити розмір виведених даних за допомогою інструмента, який
-обробляє розріджені дані>, наприклад C<du -sh>. Різниця може бути досить
-значною:
+Якщо вхідними даними є образ raw, буде виведено розріджені дані raw. B<Вам слід перевірити розмір виведених даних за допомогою інструмента, який обробляє розріджені дані>, наприклад C<du -sh>. Різниця може бути досить значною:
$ ls -lh test1.img
-rw-rw-r--. 1 rjones rjones 100M Aug 8 08:08 test1.img
=item *
-Virt-sparsify може потребувати для роботи удвічі більшого місця на диску,
-ніж розмір початкового образу диска (1 тимчасова копія + 1 образ
-призначення). Ця оцінка є максимальною, і зазвичай потрібно набагато менше
-місця.
+Virt-sparsify може потребувати для роботи удвічі більшого місця на диску, ніж розмір початкового образу диска (1 тимчасова копія + 1 образ призначення). Ця оцінка є максимальною, і зазвичай потрібно набагато менше місця.
-Якщо ви використовуєте параметр I<--in-place>, значні обсяги місця на диску
-для тимчасового зберігання даних B<не> знадобляться.
+Якщо ви використовуєте параметр I<--in-place>, значні обсяги місця на диску для тимчасового зберігання даних B<не> знадобляться.
=item *
-Virt-sparsify не може змінювати розміри образів дисків. Для зміни розмірів
-дисків скористайтеся L<virt-resize(1)>.
+Virt-sparsify не може змінювати розміри образів дисків. Для зміни розмірів дисків скористайтеся L<virt-resize(1)>.
=item *
-Virt-sparsify не може працювати із зашифрованими дисками. У libguestfs
-передбачено підтримку самих зашифрованих дисків, але зашифровані диски не
-може бути розріджено.
+Virt-sparsify не може працювати із зашифрованими дисками. У libguestfs передбачено підтримку самих зашифрованих дисків, але зашифровані диски не може бути розріджено.
=item *
-Virt-sparsify ще не може розріджувати місце між розділами. Зауважте, що це
-місце часто використовується для критичних даних, зокрема завантажувачів,
-тому, насправді, воно може бути зовсім не таким зайвим, як може здатися.
+Virt-sparsify ще не може розріджувати місце між розділами. Зауважте, що це місце часто використовується для критичних даних, зокрема завантажувачів, тому, насправді, воно може бути зовсім не таким зайвим, як може здатися.
=item *
-У режимі копіювання внутрішні знімки qcow2 не копіюються на образ
-призначення.
+У режимі копіювання внутрішні знімки qcow2 не копіюються на образ призначення.
=back
-Перш ніж розпочати користування цією програмою, вам також варто ознайомитися
-зі сторінками підручника щодо пов'язаних із нею інструментів,
-L<virt-filesystems(1)> та L<virt-df(1)>.
+Перш ніж розпочати користування цією програмою, вам також варто ознайомитися зі сторінками підручника щодо пов'язаних із нею інструментів, L<virt-filesystems(1)> та L<virt-df(1)>.
=head1 ПРИКЛАДИ
virt-sparsify вхідний_диск вихідний_диск
-Ця команда копіює C<вхідний_диск> на диск C<вихідний_диск>, роблячи
-результат розрідженим. Диск C<вихідний_диск> буде створено або перезаписано,
-якщо такий диск уже існує. Програма сама визначить формат вхідного диска
-(наприклад qcow2) і використає той самий формат для вихідного диска.
+Ця команда копіює C<вхідний_диск> на диск C<вихідний_диск>, роблячи результат розрідженим. Диск C<вихідний_диск> буде створено або перезаписано, якщо такий диск уже існує. Програма сама визначить формат вхідного диска (наприклад qcow2) і використає той самий формат для вихідного диска.
-Для перетворення диска з одного формату на інший скористайтеся параметром
-I<--convert>:
+Для перетворення диска з одного формату на інший скористайтеся параметром I<--convert>:
virt-sparsify disk.raw --convert qcow2 disk.qcow2
-Virt-sparsify намагається занулити і розрідити вільне місце на усіх файлових
-системах, які вдасться знайти на початковому образі диска. Ви можете
-наказати програмі ігнорувати (не занулювати вільне місце) певні файлові
-системи за допомогою такої команди:
+Virt-sparsify намагається занулити і розрідити вільне місце на усіх файлових системах, які вдасться знайти на початковому образі диска. Ви можете наказати програмі ігнорувати (не занулювати вільне місце) певні файлові системи за допомогою такої команди:
virt-sparsify --ignore /dev/sda1 вхідний_диск вихідний_диск
-Щоб отримати список файлових систем на образі диска, скористайтеся командою
-L<virt-filesystems(1)>.
+Щоб отримати список файлових систем на образі диска, скористайтеся командою L<virt-filesystems(1)>.
-Починаючи з версії virt-sparsify E<ge> 1.26, ви можете розріджувати образ
-диска на місці, ось так:
+Починаючи з версії virt-sparsify E<ge> 1.26, ви можете розріджувати образ диска на місці, ось так:
virt-sparsify --in-place disk.img
=item B<--check-tmpdir> B<fail>
-Переконайтеся, чи достатньо вільного місця у каталозі, вказаному за
-допомогою змінної середовища L</TMPDIR> або параметра I<--tmp>, для
-завершення дії. Це лише оцінка.
+Переконайтеся, чи достатньо вільного місця у каталозі, вказаному за допомогою змінної середовища L</TMPDIR> або параметра I<--tmp>, для завершення дії. Це лише оцінка.
-Якщо під час перевірки буде виявлено проблему, ви можете піти одним з таких
-шляхів:
+Якщо під час перевірки буде виявлено проблему, ви можете піти одним з таких шляхів:
=over 4
=item *
-B<попередити> і почекати, доки користувач натисне клавішу Enter (типова
-поведінка) або
+B<попередити> і почекати, доки користувач натисне клавішу Enter (типова поведінка) або
=item *
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<--compress>
-Стиснути файл виведених даних. Це працює, I<лише> якщо форматом виведення
-даних є C<qcow2>.
+Стиснути файл виведених даних. Це працює, I<лише> якщо форматом виведення даних є C<qcow2>.
Цей параметр не можна поєднувати із параметром I<--in-place>.
=item B<--convert> [інші формати]
-Використовувати C<формат виведення> як формат образу призначення. Якщо цей
-параметр не вказано, буде використано той самий формат, що і у вхідних
-даних.
+Використовувати C<формат виведення> як формат образу призначення. Якщо цей параметр не вказано, буде використано той самий формат, що і у вхідних даних.
-Підтримуваними і працездатними форматами виведення є такі: C<raw>, C<qcow2>,
-C<vdi>.
+Підтримуваними і працездатними форматами виведення є такі: C<raw>, C<qcow2>, C<vdi>.
-Ви також можете скористатися будь-яким іншим форматом, підтримку якого
-передбачено у програми L<qemu-img(1)>, наприклад C<vmdk>, але підтримка
-інших форматів повністю залежить від можливостей qemu.
+Ви також можете скористатися будь-яким іншим форматом, підтримку якого передбачено у програми L<qemu-img(1)>, наприклад C<vmdk>, але підтримка інших форматів повністю залежить від можливостей qemu.
-Зазвичай, варто визначати формат за допомогою I<--convert>, оскільки тоді
-virt-sparsify не доведеться вгадувати формат вхідних даних.
+Зазвичай, варто визначати формат за допомогою I<--convert>, оскільки тоді virt-sparsify не доведеться вгадувати формат вхідних даних.
-Скоригувати формат виведення даних можна за допомогою параметрів
-I<--compress>, I<-o>.
+Скоригувати формат виведення даних можна за допомогою параметрів I<--compress>, I<-o>.
Цей параметр не можна поєднувати із параметром I<--in-place>.
=item B<--echo-keys>
-Типово, якщо virt-sparcify попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-sparcify попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format> raw
=item B<--format> qcow2
-Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано,
-його буде автоматично визначено на основі даних самого образу.
+Вказати формат образу диска вхідних даних. Якщо цей прапорець не вказано, його буде автоматично визначено на основі даних самого образу.
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
=item B<--ignore> файлова_система
Ігнорувати вказану файлову систему.
-Якщо не використовується I<--in-place>, вільне місце у файловій системі не
-буде занулено, але наявні нульові блоки все одно буде розріджено.
+Якщо не використовується I<--in-place>, вільне місце у файловій системі не буде занулено, але наявні нульові блоки все одно буде розріджено.
-Якщо використовується I<--in-place>, файлову систему буде повністю
-проігноровано.
+Якщо використовується I<--in-place>, файлову систему буде повністю проігноровано.
-У другій формі команда призведе до ігнорування вказаної за назвою групи
-томів. Використовуйте назву групи томів без префікса F</dev/>, наприклад
-I<--ignore vg_foo>
+У другій формі команда призведе до ігнорування вказаної за назвою групи томів. Використовуйте назву групи томів без префікса F</dev/>, наприклад I<--ignore vg_foo>
Цей параметр можна вказувати декілька разів.
=item B<--in-place>
-Виконати розрідження на місці замість розрідження копіюванням. Див. розділ
-L</РОЗРІДЖЕННЯ НА МІСЦІ> нижче.
+Виконати розрідження на місці замість розрідження копіюванням. Див. розділ L</РОЗРІДЖЕННЯ НА МІСЦІ> нижче.
__INCLUDE:key-option.pod__
=item B<--machine-readable>=формат
-За допомогою цього параметра можна зробити виведені дані придатнішими для
-обробки комп'ютером, якщо для цієї обробки використовуються інші
-програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
+За допомогою цього параметра можна зробити виведені дані придатнішими для обробки комп'ютером, якщо для цієї обробки використовуються інші програми. Див. L</ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ> нижче.
=item B<-o> параметр[,параметр,...]
-Передати параметри I<-o> до програми L<qemu-img(1)> для коригування формату
-виведення даних. Перелік доступних параметрів залежить від формату
-виведення (див. I<--convert>) і встановленої версії програми qemu-img.
+Передати параметри I<-o> до програми L<qemu-img(1)> для коригування формату виведення даних. Перелік доступних параметрів залежить від формату виведення (див. I<--convert>) і встановленої версії програми qemu-img.
-Вам слід скористатися I<-o> не більше одного разу. Щоб передати декілька
-параметрів, відокремте їх комами. Приклад:
+Вам слід скористатися I<-o> не більше одного разу. Щоб передати декілька параметрів, відокремте їх комами. Приклад:
virt-sparsify --convert qcow2 \
-o cluster_size=512,preallocation=metadata ...
=item B<--tmp> каталог
-Лише у режимі копіювання, використати вказаний за назвою пристрій або
-каталог як місце для тимчасової накладки (див. також L</TMPDIR> нижче).
+Лише у режимі копіювання, використати вказаний за назвою пристрій або каталог як місце для тимчасової накладки (див. також L</TMPDIR> нижче).
-Якщо як параметр вказано блоковий пристрій, блоковий пристрій буде записано
-безпосередньо. B<Зауважте, що при цьому з блокового пристрою буде повністю
-витерто наявні дані>.
+Якщо як параметр вказано блоковий пристрій, блоковий пристрій буде записано безпосередньо. B<Зауважте, що при цьому з блокового пристрою буде повністю витерто наявні дані>.
-Якщо як параметр вказано каталог, визначення параметра буде рівнозначним
-заданню значення змінної середовища L</TMPDIR>.
+Якщо як параметр вказано каталог, визначення параметра буде рівнозначним заданню значення змінної середовища L</TMPDIR>.
Цей параметр не можна поєднувати із параметром I<--in-place>.
=item B<--tmp> prebuilt:файл
-Лише у режимі копіювання, спеціалізований параметр I<--tmp prebuilt:файл>
-(де C<prebuilt:> слід записувати буквально) наказує virt-sparsify
-використовувати як місце зберігання тимчасових даних файл qcow2 C<файл>.
+Лише у режимі копіювання, спеціалізований параметр I<--tmp prebuilt:файл> (де C<prebuilt:> слід записувати буквально) наказує virt-sparsify використовувати як місце зберігання тимчасових даних файл qcow2 C<файл>.
=over 4
=item *
-Файл B<має> бути наново форматовано як qcow2, а вхідний диск буде резервним
-файлом.
+Файл B<має> бути наново форматовано як qcow2, а вхідний диск буде резервним файлом.
=item *
-Якщо ви повторно запускатимете virt-sparsify, вам B<слід> повторно
-створювати файл перед кожним запуском.
+Якщо ви повторно запускатимете virt-sparsify, вам B<слід> повторно створювати файл перед кожним запуском.
=item *
=back
-Цей параметр використовується oVirt, де потрібен спеціальним чином
-форматований тимчасовий файл.
+Цей параметр використовується oVirt, де потрібен спеціальним чином форматований тимчасовий файл.
=item B<-v>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=item B<--zero> логічний_том
-Занулити вміст вказаного за назвою розділу або логічного тому у гостьовій
-системі. Усі дані на пристрої буде втрачено, але буде досягнуто чудової
-розрідженості! Цей параметр можна вказувати в одній команді декілька разів.
+Занулити вміст вказаного за назвою розділу або логічного тому у гостьовій системі. Усі дані на пристрої буде втрачено, але буде досягнуто чудової розрідженості! Цей параметр можна вказувати в одній команді декілька разів.
=back
=head1 РОЗРІДЖЕННЯ НА МІСЦІ
-Починаючи з virt-sparsify E<ge> 1.26, програма може виконувати розрідження
-на місці (замість копіювання з вхідного диска до вихідного диска). Таке
-розрідження є ефективнішим. Втім, за його використання не можна отримати
-більше місця у основній системі, якщо порівнювати із розрідженням із
-копіюванням.
+Починаючи з virt-sparsify E<ge> 1.26, програма може виконувати розрідження на місці (замість копіювання з вхідного диска до вихідного диска). Таке розрідження є ефективнішим. Втім, за його використання не можна отримати більше місця у основній системі, якщо порівнювати із розрідженням із копіюванням.
-Щоб скористатися цим режимом, вкажіть образ диска, який буде змінено на
-місці:
+Щоб скористатися цим режимом, вкажіть образ диска, який буде змінено на місці:
virt-sparsify --in-place disk.img
-Деякі параметри несумісні із цим режимом: I<--convert>, I<--compress> і
-I<-o>, оскільки їхнє використання вимагає загальної зміни формату диска;
-I<--check-tmpdir>, оскільки великі обсяги для зберігання тимчасових даних не
-потрібні.
+Деякі параметри несумісні із цим режимом: I<--convert>, I<--compress> і I<-o>, оскільки їхнє використання вимагає загальної зміни формату диска; I<--check-tmpdir>, оскільки великі обсяги для зберігання тимчасових даних не потрібні.
-Розрідження на місці працює завдяки підтримці відкидання (або обрізання чи
-скасування отримання пам'яті).
+Розрідження на місці працює завдяки підтримці відкидання (або обрізання чи скасування отримання пам'яті).
=head1 ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ
-Для виведення даних у зручному для машинної обробки форматі можна
-скористатися параметром I<--machine-readable>. Додавання цього параметра
-робить зручним використання virt-sparcify з інших програм, графічних
-інтерфейсів тощо.
+Для виведення даних у зручному для машинної обробки форматі можна скористатися параметром I<--machine-readable>. Додавання цього параметра робить зручним використання virt-sparcify з інших програм, графічних інтерфейсів тощо.
Існує два способи використання цього параметра.
-Спочатку, скористайтеся цим параметром окремо, щоб опитати систему щодо
-можливостей виконуваного файла virt-sparcify. Типово виведені дані
-виглядатимуть якось так:
+Спочатку, скористайтеся цим параметром окремо, щоб опитати систему щодо можливостей виконуваного файла virt-sparcify. Типово виведені дані виглядатимуть якось так:
$ virt-sparsify --machine-readable
virt-sparsify
ntfs
btrfs
-Виводиться список можливостей, по одній на рядок, і програма завершує роботу
-зі станом 0.
+Виводиться список можливостей, по одній на рядок, і програма завершує роботу зі станом 0.
-По-друге, можна скористатися цим параметром у поєднанні із іншими
-параметрами для того, щоб зробити звичайні виведені програмою дані
-придатнішими для подальшої машинної обробки.
+По-друге, можна скористатися цим параметром у поєднанні із іншими параметрами для того, щоб зробити звичайні виведені програмою дані придатнішими для подальшої машинної обробки.
У поточній версії це означає таке:
=item 1.
-Повідомлення смужки поступу можна обробляти зі стандартного виведення,
-шукаючи їх за таким формальним виразом:
+Повідомлення смужки поступу можна обробляти зі стандартного виведення, шукаючи їх за таким формальним виразом:
^[0-9]+/[0-9]+$
=item 2.
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення
-щодо стану. Ці повідомлення може бути записано до журналу і/або показано
-користувачеві.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до стандартного виведення, (окрім повідомлень смужки поступу) як повідомлення щодо стану. Ці повідомлення може бути записано до журналу і/або показано користувачеві.
=item 3.
-Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до
-stderr як повідомлення про помилки. Крім того, virt-sparcify завершує роботу
-із ненульовим кодом стану, якщо станеться критична помилка.
+Програма, яка надсилає виклик, має обробляти повідомлення, надіслані до stderr як повідомлення про помилки. Крім того, virt-sparcify завершує роботу із ненульовим кодом стану, якщо станеться критична помилка.
=back
-Підтримку параметра I<--machine-readable> передбачено у всіх версіях
-virt-sparsify.
+Підтримку параметра I<--machine-readable> передбачено у всіх версіях virt-sparsify.
-Можна вказати рядок форматування для керування виведенням,
-див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
+Можна вказати рядок форматування для керування виведенням, див. L<guestfs(3)/РОЗШИРЕНЕ ПРИДАТНЕ ДО ЧИТАННЯ КОМП'ЮТЕРОМ ВИВЕДЕННЯ>.
=head1 WINDOWS 8
-«Швидкий запуск» Windows 8 може заважати роботі
-virt-sparsify. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК
-WINDOWS 8>.
+«Швидкий запуск» Windows 8 може заважати роботі virt-sparsify. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК WINDOWS 8>.
=head1 ЗМІННІ СЕРЕДОВИЩА
=item ТИМЧАСОВИЙ КАТАЛОГ
-Розташування каталогу тимчасових даних, який використовуватиметься для
-потенційно великих тимчасових файлів-накладок.
+Розташування каталогу тимчасових даних, який використовуватиметься для потенційно великих тимчасових файлів-накладок.
-У virt-sparsify E<ge> 1.28 ви можете перевизначити цю змінну середовища за
-допомогою параметра I<--tmp>.
+У virt-sparsify E<ge> 1.28 ви можете перевизначити цю змінну середовища за допомогою параметра I<--tmp>.
-На диску має бути достатньо вільного місця для найгіршого варіанта для
-повної копії початкового диска (I<віртуального> розміру). Якщо місця
-недостатньо, слід встановити для C<$TMPDIR> значення, яке вказує на інший
-каталог, де достатньо місця.
+На диску має бути достатньо вільного місця для найгіршого варіанта для повної копії початкового диска (I<віртуального> розміру). Якщо місця недостатньо, слід встановити для C<$TMPDIR> значення, яке вказує на інший каталог, де достатньо місця.
Типовим значенням є F</tmp>.
-Зауважте, що якщо файловою системою у C<$TMPDIR> є tmpfs (наприклад, якщо
-файловою системою F</tmp> є tmpfs, або якщо ви використовуєте
-C<TMPDIR=/dev/shm>), типовим розміром tmpfs є максимальне значення
-I<половини> фізичної оперативної пам'яті. Якщо virt-sparsify знадобиться
-більше місця, програма просто «повисне». Якщо ви побоюєтеся такого перебігу
-подій, або скористайтеся реальним диском, або збільште максимальний розмір
-точки монтування tmpfs, наприклад так:
+Зауважте, що якщо файловою системою у C<$TMPDIR> є tmpfs (наприклад, якщо файловою системою F</tmp> є tmpfs, або якщо ви використовуєте C<TMPDIR=/dev/shm>), типовим розміром tmpfs є максимальне значення I<половини> фізичної оперативної пам'яті. Якщо virt-sparsify знадобиться більше місця, програма просто «повисне». Якщо ви побоюєтеся такого перебігу подій, або скористайтеся реальним диском, або збільште максимальний розмір точки монтування tmpfs, наприклад так:
mount -o remount,size=10G /tmp
-Якщо ви використовуєте параметр I<--in-place>, значні обсяги місця на диску
-для тимчасового зберігання даних B<не> знадобляться.
+Якщо ви використовуєте параметр I<--in-place>, значні обсяги місця на диску для тимчасового зберігання даних B<не> знадобляться.
=back
-Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT
-VARIABLES>.
+Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT VARIABLES>.
=head1 СТАН ВИХОДУ
-Ця програма повертає 0, якщо дію виконано без жодної помилки (це не
-обов'язково означає, що місце на диску звільнилося).
+Ця програма повертає 0, якщо дію виконано без жодної помилки (це не обов'язково означає, що місце на диску звільнилося).
Ненульовий код виходу вказує на помилку.
-Якщо повернуто код виходу C<3> і було використано параметр I<--in-place>, це
-означає, що у libguestfs не передбачено підтримки відкидання зайвого місця
-на диску, отже, доведеться користуватися режимом копіювання.
+Якщо повернуто код виходу C<3> і було використано параметр I<--in-place>, це означає, що у libguestfs не передбачено підтримки відкидання зайвого місця на диску, отже, доведеться користуватися режимом копіювання.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<virt-df(1)>, L<virt-filesystems(1)>, L<virt-resize(1)>, L<virt-rescue(1)>,
-L<guestfs(3)>, L<guestfish(1)>, L<truncate(1)>, L<fallocate(1)>,
-L<qemu-img(1)>, L<http://libguestfs.org/>.
+L<virt-df(1)>, L<virt-filesystems(1)>, L<virt-resize(1)>, L<virt-rescue(1)>, L<guestfs(3)>, L<guestfish(1)>, L<truncate(1)>, L<fallocate(1)>, L<qemu-img(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-sysprep 1"
-.TH virt-sysprep 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-sysprep 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "НАЗВА"
.IX Header "НАЗВА"
-virt-sysprep — скидання налаштувань віртуальної машини до початкових, так,
-щоб з неї можна було роботи клони
+virt-sysprep — скидання налаштувань віртуальної машини до початкових, так, щоб з неї можна було роботи клони
.SH "КОРОТКИЙ ОПИС"
.IX Header "КОРОТКИЙ ОПИС"
.Vb 1
.Ve
.SH "ОПИС"
.IX Header "ОПИС"
-Virt-sysprep може відновити початковий стан або зняти налаштовування з
-віртуальної машини, щоб з неї можна було робити клони. Кроками цієї
-процедури є вилучення ключів вузла \s-1SSH,\s0 вилучення сталих налаштувань мережі
-щодо \s-1MAC\s0 та вилучення облікових записів користувачів. Крім того,
-virt-sysprep може налаштовувати віртуальну машину, наприклад, додаванням
-ключів \s-1SSH,\s0 користувачів чи логотипів. Ви можете вмикати або вимикати кожен
-з цих кроків.
-.PP
-Virt-sysprep вносить зміни до гостьової системи або образу диска \fIна
-місці\fR. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний
-вміст гостьової системи, \fIвам слід спочатку зробити її знімок, скопіювати
-або клонувати її диск\fR. Див. \*(L"КОПІЮВАННЯ І КЛОНУВАННЯ\*(R" нижче.
-.PP
-Вам \fIне потрібно\fR запускати virt-sysprep від імені користувача
-root. Фактично, запуск у такому режимі є нерекомендованим. Єдиною причиною
-запускати програму від імені root може бути потреба у доступі до образу
-диска, але навіть у цьому випадку, доцільніше змінити права доступу до
-образу диска так, щоб запис до нього став доступним від імені користувача,
-який запускає virt-sysprep.
-.PP
-«Sysprep» — скорочення від «system preparation» («приготування
-системи»). Назва походить від програми Microsoft \fIsysprep.exe\fR, яка
-використовується для вилучення налаштувань з Windows у приготуваннях до
-клонування системи. Маємо зауважити, що у поточній версії virt-sysprep \fIне\fR
-може працювати із гостьовими системами Microsoft Windows. Ми плануємо
-впровадити підтримку приготування Windows у майбутніх версіях і вже маємо
-певні напрацювання щодо цього.
+Virt-sysprep може відновити початковий стан або зняти налаштовування з віртуальної машини, щоб з неї можна було робити клони. Кроками цієї процедури є вилучення ключів вузла \s-1SSH,\s0 вилучення сталих налаштувань мережі щодо \s-1MAC\s0 та вилучення облікових записів користувачів. Крім того, virt-sysprep може налаштовувати віртуальну машину, наприклад, додаванням ключів \s-1SSH,\s0 користувачів чи логотипів. Ви можете вмикати або вимикати кожен з цих кроків.
+.PP
+Virt-sysprep вносить зміни до гостьової системи або образу диска \fIна місці\fR. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний вміст гостьової системи, \fIвам слід спочатку зробити її знімок, скопіювати або клонувати її диск\fR. Див. \*(L"КОПІЮВАННЯ І КЛОНУВАННЯ\*(R" нижче.
+.PP
+Вам \fIне потрібно\fR запускати virt-sysprep від імені користувача root. Фактично, запуск у такому режимі є нерекомендованим. Єдиною причиною запускати програму від імені root може бути потреба у доступі до образу диска, але навіть у цьому випадку, доцільніше змінити права доступу до образу диска так, щоб запис до нього став доступним від імені користувача, який запускає virt-sysprep.
+.PP
+«Sysprep» — скорочення від «system preparation» («приготування системи»). Назва походить від програми Microsoft \fIsysprep.exe\fR, яка використовується для вилучення налаштувань з Windows у приготуваннях до клонування системи. Маємо зауважити, що у поточній версії virt-sysprep \fIне\fR може працювати із гостьовими системами Microsoft Windows. Ми плануємо впровадити підтримку приготування Windows у майбутніх версіях і вже маємо певні напрацювання щодо цього.
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.PD
Додати \fIфайл\fR, який має бути образом диска з віртуальної машини.
.Sp
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром \fI\-\-format\fR.
.IP "\fB\-a\fR адреса" 4
.IX Item "-a адреса"
.PD 0
.IP "\fB\-\-add\fR адреса" 4
.IX Item "--add адреса"
.PD
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. \*(L"ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА\*(R" in \fBguestfish\fR\|(1).
.IP "\fB\-\-colors\fR" 4
.IX Item "--colors"
.PD 0
.IP "\fB\-\-colours\fR" 4
.IX Item "--colours"
.PD
-Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів \s-1ANSI\s0 для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів \s-1ANSI\s0 буде вимкнено, якщо ви не додасте до команди цей параметр.
.IP "\fB\-c\fR адреса" 4
.IX Item "-c адреса"
.PD 0
.IP "\fB\-\-connect\fR адреса" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (\fI\-a\fR), libvirt не буде використовуватися взагалі.
.IP "\fB\-d\fR гість" 4
.IX Item "-d гість"
.PD 0
.IP "\fB\-\-domain\fR гість" 4
.IX Item "--domain гість"
.PD
-Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. \s-1UUID\s0 доменів можна використовувати замість назв.
.IP "\fB\-n\fR" 4
.IX Item "-n"
.PD 0
.IP "\fB\-\-dry\-run\fR" 4
.IX Item "--dry-run"
.PD
-Виконати тестову обробку гостьової системи у режимі «лише читання». Буде
-виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
+Виконати тестову обробку гостьової системи у режимі «лише читання». Буде виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
.IP "\fB\-\-enable\fR дії" 4
.IX Item "--enable дії"
-Визначає дії з приготування, які слід виконати. Ви можете вказати список
-дій, відокремлених комами, ось так:
+Визначає дії з приготування, які слід виконати. Ви можете вказати список дій, відокремлених комами, ось так:
.Sp
.Vb 1
\& \-\-enable ssh\-hostkeys,udev\-persistent\-net
.Sp
Тут увімкнено лише дії \f(CW\*(C`ssh\-hostkeys\*(C'\fR і \f(CW\*(C`udev\-persistent\-net\*(C'\fR.
.Sp
-Якщо параметр \fI\-\-enable\fR не вказано, типово буде виконано якомога більше
-дій з приготування системи (див. \fI\-\-list\-operations\fR, щоб переглянути
-список увімкнених дій).
+Якщо параметр \fI\-\-enable\fR не вказано, типово буде виконано якомога більше дій з приготування системи (див. \fI\-\-list\-operations\fR, щоб переглянути список увімкнених дій).
.Sp
-Незалежно від вказаного параметра \fI\-\-enable\fR, для певних типів гостьових
-систем деякі дії пропускаються.
+Незалежно від вказаного параметра \fI\-\-enable\fR, для певних типів гостьових систем деякі дії пропускаються.
.Sp
-Скористайтеся параметром \fI\-\-list\-operations\fR, щоб переглянути список дій,
-підтримку яких передбачено у вашій версії virt-sysprep.
+Скористайтеся параметром \fI\-\-list\-operations\fR, щоб переглянути список дій, підтримку яких передбачено у вашій версії virt-sysprep.
.Sp
Список дій із поясненнями щодо них наведено у розділі \*(L"ДІЇ\*(R" нижче.
.IP "\fB\-\-operation\fR дії" 4
.IP "\fB\-\-operations\fR дії" 4
.IX Item "--operations дії"
.PD
-Визначає дії з приготування, які слід виконати. Ви можете вказати список
-дій, відокремлених комами, ось так:
+Визначає дії з приготування, які слід виконати. Ви можете вказати список дій, відокремлених комами, ось так:
.Sp
.Vb 1
\& \-\-operations ssh\-hostkeys,udev\-persistent\-net
.Sp
Тут увімкнено лише дії \f(CW\*(C`ssh\-hostkeys\*(C'\fR і \f(CW\*(C`udev\-persistent\-net\*(C'\fR.
.Sp
-За допомогою параметра \fI\-\-operations\fR ви зможете увімкнути або вимкнути
-будь\-які дї, зокрема типові (ті, які виконуватимуться, якщо не вказано ні
-\&\fI\-\-operations\fR, ні \fI\-\-enable\fR) та усі доступні; додавання \f(CW\*(C`\-\*(C'\fR перед
-назвою дії вилучає її зі списку увімкнених дій, а метаназви \f(CW\*(C`defaults\*(C'\fR і
-\&\f(CW\*(C`all\*(C'\fR відповідають діям, які типово увімкнено і усім доступним
-діям. Приклад:
+За допомогою параметра \fI\-\-operations\fR ви зможете увімкнути або вимкнути будь\-які дї, зокрема типові (ті, які виконуватимуться, якщо не вказано ні \fI\-\-operations\fR, ні \fI\-\-enable\fR) та усі доступні; додавання \f(CW\*(C`\-\*(C'\fR перед назвою дії вилучає її зі списку увімкнених дій, а метаназви \f(CW\*(C`defaults\*(C'\fR і \f(CW\*(C`all\*(C'\fR відповідають діям, які типово увімкнено і усім доступним діям. Приклад:
.Sp
.Vb 1
\& \-\-operations firewall\-rules,defaults,\-tmp\-files
.Ve
.Sp
-Ця команда вмикає дію \f(CW\*(C`firewall\-rules\*(C'\fR (незалежно від того, чи було її
-типово увімкнено), усі типові дії і вимикає дію \f(CW\*(C`tmp\-files\*(C'\fR.
+Ця команда вмикає дію \f(CW\*(C`firewall\-rules\*(C'\fR (незалежно від того, чи було її типово увімкнено), усі типові дії і вимикає дію \f(CW\*(C`tmp\-files\*(C'\fR.
.Sp
-Параметр \fI\-\-operations\fR може бути вказано декілька разів; під час першого
-використання набір увімкнених дій вважається порожнім, усі наступні
-використання \fI\-\-operations\fR стосуватимуться уже увімкненого набору дій.
+Параметр \fI\-\-operations\fR може бути вказано декілька разів; під час першого використання набір увімкнених дій вважається порожнім, усі наступні використання \fI\-\-operations\fR стосуватимуться уже увімкненого набору дій.
.Sp
-Якщо параметр \fI\-\-operations\fR не вказано, типово буде виконано якомога
-більше дій з приготування системи (див. \fI\-\-list\-operations\fR, щоб
-переглянути список увімкнених дій).
+Якщо параметр \fI\-\-operations\fR не вказано, типово буде виконано якомога більше дій з приготування системи (див. \fI\-\-list\-operations\fR, щоб переглянути список увімкнених дій).
.Sp
-Незалежно від вказаного параметра \fI\-\-operations\fR, для певних типів
-гостьових систем деякі дії пропускаються.
+Незалежно від вказаного параметра \fI\-\-operations\fR, для певних типів гостьових систем деякі дії пропускаються.
.Sp
-Скористайтеся параметром \fI\-\-list\-operations\fR, щоб переглянути список дій,
-підтримку яких передбачено у вашій версії virt-sysprep.
+Скористайтеся параметром \fI\-\-list\-operations\fR, щоб переглянути список дій, підтримку яких передбачено у вашій версії virt-sysprep.
.Sp
Список дій із поясненнями щодо них наведено у розділі \*(L"ДІЇ\*(R" нижче.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
-Типово, якщо virt-sysprep попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-sysprep попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST\-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
.IP "\fB\-\-format\fR raw|qcow2|.." 4
.IX Item "--format raw|qcow2|.."
.PD 0
.IP "\fB\-\-format\fR auto" 4
.IX Item "--format auto"
.PD
-Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання
-параметра \fI\-\-format auto\fR перемикає програму у режим автоматичного
-визначення у наступних параметрах \fI\-a\fR.
+Типовим значенням для параметра \fI\-a\fR є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів \fI\-a\fR формату диска у наступному рядку команди. Використання параметра \fI\-\-format auto\fR перемикає програму у режим автоматичного визначення у наступних параметрах \fI\-a\fR.
.Sp
Приклад:
.Sp
\& virt\-sysprep \-\-format raw \-a disk.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdisk.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-sysprep \-\-format raw \-a disk.img \-\-format auto \-a another.img
.Ve
.Sp
-примусове встановлення формату без обробки (без автоматичного визначення)
-для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
+примусове встановлення формату без обробки (без автоматичного визначення) для \fIdiskimg\fR і повернення до автоматичного визначення для \fIanother.img\fR.
.Sp
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (\s-1CVE\-2010\-3851\s0).
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
.IX Item "--list-operations"
Список дій, підтримку яких передбачено у програмі virt-sysprep.
.Sp
-Дії буде показано по одній на рядок із одним або декількома полями,
-відокремленими комами. Приклад:
+Дії буде показано по одній на рядок із одним або декількома полями, відокремленими комами. Приклад:
.Sp
.Vb 6
\& $ virt\-sysprep \-\-list\-operations
\& [тощо]
.Ve
.Sp
-У першому полі міститься назва дії, яку можна додати до параметра
-\&\fI\-\-enable\fR. У другому полі міститься символ \f(CW\*(C`*\*(C'\fR, якщо дію типово
-увімкнено, і пробіл, якщо дію вимкнено. Наступні поля у тому самому рядку є
-описом дії.
+У першому полі міститься назва дії, яку можна додати до параметра \fI\-\-enable\fR. У другому полі міститься символ \f(CW\*(C`*\*(C'\fR, якщо дію типово увімкнено, і пробіл, якщо дію вимкнено. Наступні поля у тому самому рядку є описом дії.
.Sp
-До libguestfs 1.17.33 показувалося лише перше поле (назва дії) і усі дії
-було типово увімкнено.
+До libguestfs 1.17.33 показувалося лише перше поле (назва дії) і усі дії було типово увімкнено.
.IP "\fB\-\-mount\-options\fR точка_монтування:параметри[;точка_монтування:параметри;...]" 4
.IX Item "--mount-options точка_монтування:параметри[;точка_монтування:параметри;...]"
-Встановлює параметри монтування, які використовуються, коли libguestfs
-відкриває образ диска. Зауважте, що це не впливає на гостьову систему. Ці
-дані використовуються при відкритті певних гостьових систем, зокрема тих, де
-використовується файлова система \s-1UFS\s0 (\s-1BSD\s0).
+Встановлює параметри монтування, які використовуються, коли libguestfs відкриває образ диска. Зауважте, що це не впливає на гостьову систему. Ці дані використовуються при відкритті певних гостьових систем, зокрема тих, де використовується файлова система \s-1UFS\s0 (\s-1BSD\s0).
.Sp
-Слід використовувати список відокремлених крапкою з комою пар
-\&\f(CW\*(C`точка_монтування:параметри\*(C'\fR. Ймовірно, список слід взяти у лапки, щоб
-захистити його від обробки командною оболонкою.
+Слід використовувати список відокремлених крапкою з комою пар \f(CW\*(C`точка_монтування:параметри\*(C'\fR. Ймовірно, список слід взяти у лапки, щоб захистити його від обробки командною оболонкою.
.Sp
Приклад:
.Sp
.PD
Не виводити повідомлення до журналу.
.Sp
-Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся
-\&\fI\-x\fR.
+Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся \fI\-x\fR.
.IP "\fB\-\-network\fR" 4
.IX Item "--network"
.PD 0
.IP "\fB\-\-no\-network\fR" 4
.IX Item "--no-network"
.PD
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
.Sp
-У virt-sysprep роботу у мережі типово \fIвимкнено\fR. Вам слід скористатися
-параметром \fI\-\-network\fR, щоб увімкнути її та мати змогу скористатися
-параметрами, подібними до \fI\-\-install\fR або \fI\-\-update\fR.
+У virt-sysprep роботу у мережі типово \fIвимкнено\fR. Вам слід скористатися параметром \fI\-\-network\fR, щоб увімкнути її та мати змогу скористатися параметрами, подібними до \fI\-\-install\fR або \fI\-\-update\fR.
.Sp
-На сторінці підручника \fBvirt\-builder\fR\|(1) можна знайти додаткові дані щодо
-переваг у захисті від вимикання мережі.
+На сторінці підручника \fBvirt\-builder\fR\|(1) можна знайти додаткові дані щодо переваг у захисті від вимикання мережі.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IX Item "--version"
.PD
Показати дані щодо версії і завершити роботу.
+.IP "\fB\-\-wrap\fR" 4
+.IX Item "--wrap"
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
.IP "\fB\-x\fR" 4
.IX Item "-x"
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
.ie n .IP "\fB\-\-append\-line\fR ФАЙЛ:РЯДОК (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-append\-line\fR ФАЙЛ:РЯДОК (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--append-line ФАЙЛ:РЯДОК (див. customize нижче)"
-Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується
-порожнім рядком, такий рядок буде додано перед дописаним. Крім того,
-автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
+Дописати один рядок тексту до файла \f(CW\*(C`ФАЙЛ\*(C'\fR. Якщо файл ще не завершується порожнім рядком, такий рядок буде додано перед дописаним. Крім того, автоматично буде дописано символ нового рядка наприкінці рядка \f(CW\*(C`РЯДОК\*(C'\fR.
.Sp
-Наприклад, (припускаємо, що у командній оболонці використовуються звичайні
-лапки) така команда:
+Наприклад, (припускаємо, що у командній оболонці використовуються звичайні лапки) така команда:
.Sp
.Vb 1
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
.Ve
.Sp
-додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде
-додано, лише якщо наявний файл ще не закінчується символом нового рядка.
+додасть \f(CW\*(C`10.0.0.1 foo⏎\*(C'\fR або \f(CW\*(C`⏎10.0.0.1 foo⏎\*(C'\fR до файла; останній запис буде додано, лише якщо наявний файл ще не закінчується символом нового рядка.
.Sp
-\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за
-наявним вмістом файла, отже, команда обробляє файли однаково правильно для
-варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для
-порожніх і ще не створених файлів.
+\&\f(CW\*(C`⏎\*(C'\fR позначає символ нового рядка, конкретне значення якого визначається за наявним вмістом файла, отже, команда обробляє файли однаково правильно для варіантів із завершеннями рядка у форматах Unix і Windows. Це працює і для порожніх і ще не створених файлів.
.Sp
-Щоб додати декілька рядків, скористайтеся тим самим параметром декілька
-разів:
+Щоб додати декілька рядків, скористайтеся тим самим параметром декілька разів:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.1 foo\*(Aq
\& \-\-append\-line \*(Aq/etc/hosts:10.0.0.2 bar\*(Aq
.Ve
.Sp
-Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою
-конструкцією:
+Щоб додати порожній рядок перед дописаним рядком, скористайтеся такою конструкцією:
.Sp
.Vb 2
\& \-\-append\-line \*(Aq/etc/hosts:\*(Aq
.IX Item "--chmod ПРАВА_ДОСТУПУ:ФАЙЛ (див. customize нижче)"
Змінити права доступу до файла \f(CW\*(C`ФАЙЛ\*(C'\fR на \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR.
.Sp
-\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі,
-якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто
-скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
+\&\fIЗауваження\fR: типово \f(CW\*(C`ПРАВА_ДОСТУПУ\*(C'\fR записуються у десятковому форматі, якщо ви не додасте початковий \f(CW0\fR , щоб вказати вісімкове число, тобто скористаєтеся \f(CW0700\fR, а не \f(CW700\fR.
.ie n .IP "\fB\-\-commands\-from\-file\fR НАЗВА_ФАЙЛА (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-commands\-from\-file\fR НАЗВА_ФАЙЛА (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--commands-from-file НАЗВА_ФАЙЛА (див. customize нижче)"
-Прочитати команди налаштовування з файла, по одній (разом із аргументами) на
-рядок.
+Прочитати команди налаштовування з файла, по одній (разом із аргументами) на рядок.
.Sp
Кожен рядок містить команду налаштовування та її аргументи, наприклад:
.Sp
\& password якийсь\-користувач:password:його\-новий\-пароль
.Ve
.Sp
-Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і
-також ігноруються. Крім того, аргументи можна розділити на декілька рядків
-додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
+Порожні рядки ігноруються, а рядки, що починаються з \f(CW\*(C`#\*(C'\fR, є коментарями і також ігноруються. Крім того, аргументи можна розділити на декілька рядків додаванням \f(CW\*(C`\e\*(C'\fR (символу продовження) наприкінці рядка. Приклад:
.Sp
.Vb 2
\& edit /якийсь/файл:\e
\& s/^OPT=.*/OPT=ok/
.Ve
.Sp
-Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так,
-наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
+Команди обробляються у тому самому порядку, у якому їх вказано у файлі, так, наче їх вказано як \fI\-\-delete /якийсь/файл\fR у рядку команди.
.ie n .IP "\fB\-\-copy\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-copy\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--copy ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. customize нижче)"
.ie n .IP "\fB\-\-copy\-in\fR ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-copy\-in\fR ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--copy-in ЛОКАЛЬНИЙ_ШЛЯХ:ВІДДАЛЕНИЙ_КАТАЛОГ (див. customize нижче)"
-Скопіювати локальні файли або каталоги рекурсивно до образу диска,
-розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
+Скопіювати локальні файли або каталоги рекурсивно до образу диска, розташувавши його у каталозі \f(CW\*(C`ВІДДАЛЕНИЙ_КАТАЛОГ\*(C'\fR (який має існувати).
.Sp
Не можна використовувати символи\-замінники.
.ie n .IP "\fB\-\-delete\fR ШЛЯХ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-delete\fR ШЛЯХ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--delete ШЛЯХ (див. customize нижче)"
-Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст,
-рекурсивно).
+Вилучити файл з гостьової системи. Або вилучити каталог (і увесь його вміст, рекурсивно).
.Sp
-Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте
-екранувати символи\-замінники у командній оболонці основної системи, якщо це
-потрібно. Приклад:
+Ви можете скористатися символами\-замінниками у вказаному шляху. Не забудьте екранувати символи\-замінники у командній оболонці основної системи, якщо це потрібно. Приклад:
.Sp
.Vb 1
\& virt\-customize \-\-delete \*(Aq/var/log/*.log\*(Aq.
.IX Item "--edit ФАЙЛ:ВИРАЗ (див. customize нижче)"
Редагувати \f(CW\*(C`ФАЙЛ\*(C'\fR з використанням виразу Perl \f(CW\*(C`ВИРАЗ\*(C'\fR.
.Sp
-Слід подбати про належне розставлення лапок у виразі, щоб запобігти його
-зміні у командній оболонці.
+Слід подбати про належне розставлення лапок у виразі, щоб запобігти його зміні у командній оболонці.
.Sp
-Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено
-Perl 5.
+Зауважте, що цим параметром можна буде скористатися, лише якщо встановлено Perl 5.
.Sp
Див. \*(L"NON-INTERACTIVE \s-1EDITING\*(R"\s0 in \fBvirt\-edit\fR\|(1).
.ie n .IP "\fB\-\-firstboot\fR СКРИПТ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-firstboot\fR СКРИПТ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--firstboot СКРИПТ (див. customize нижче)"
-Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Встановити \f(CW\*(C`СКРИПТ\*(C'\fR у гостьовій системі і запустити його під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-До скрипту, після встановлення до гостьової системи, буде автоматично
-застосовано команду chmod +x.
+До скрипту, після встановлення до гостьової системи, буде автоматично застосовано команду chmod +x.
.Sp
-Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно
-включає команду у однорядковому скрипті.
+Альтернативна версія \fI\-\-firstboot\-command\fR є такою самою, але зручно включає команду у однорядковому скрипті.
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.ie n .IP "\fB\-\-firstboot\-command\fR 'КОМАНДА+ПАРАМЕТРИ' (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-firstboot\-command\fR 'КОМАНДА+ПАРАМЕТРИ' (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--firstboot-command 'КОМАНДА+ПАРАМЕТРИ' (див. customize нижче)"
-Виконати команду (разом із аргументами) у гостьовій системі під час першого
-завантаження гостьової системи (від імені root, у останній частині процесу
-завантаження).
+Виконати команду (разом із аргументами) у гостьовій системі під час першого завантаження гостьової системи (від імені root, у останній частині процесу завантаження).
.Sp
-Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-firstboot\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
-Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО
-ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого
-завантаження і проблемами у їх використанні.
+Будь ласка, зверніться до розділу \*(L"СКРИПТИ ПЕРШОГО ЗАВАНТАЖЕННЯ\*(R" in \fBvirt\-builder\fR\|(1), щоб ознайомитися із відомостями щодо скриптів першого завантаження і проблемами у їх використанні.
.Sp
Див. також \fI\-\-run\fR.
.ie n .IP "\fB\-\-firstboot\-install\fR ПАКУНОК,ПАКУНОК... (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-firstboot\-install\fR ПАКУНОК,ПАКУНОК... (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--firstboot-install ПАКУНОК,ПАКУНОК... (див. customize нижче)"
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час першого завантаження гостьової системи за
-допомогою програми для керування пакунків гостьової системи (наприклад, apt,
-yum тощо) і з'єднання із мережею гостьової системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час першого завантаження гостьової системи за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею гостьової системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
.ie n .IP "\fB\-\-hostname\fR НАЗВА_ВУЗЛА (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-hostname\fR НАЗВА_ВУЗЛА (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--hostname НАЗВА_ВУЗЛА (див. customize нижче)"
-Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо
-потрібно, можете скористатися форматом із крапкою,
-«назва_вузла.назва_домену» (\s-1FQDN\s0).
+Встановити як назву вузла гостьової системи значення \f(CW\*(C`НАЗВА_ВУЗЛА\*(C'\fR. Якщо потрібно, можете скористатися форматом із крапкою, «назва_вузла.назва_домену» (\s-1FQDN\s0).
.ie n .IP "\fB\-\-install\fR ПАКУНОК,ПАКУНОК... (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-install\fR ПАКУНОК,ПАКУНОК... (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--install ПАКУНОК,ПАКУНОК... (див. customize нижче)"
-Встановити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде встановлено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання
-із мережею основної системи.
+Встановити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде встановлено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо) і з'єднання із мережею основної системи.
.Sp
-Огляд різних способів встановлення пакунків наведено у розділі
-\&\*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
+Огляд різних способів встановлення пакунків наведено у розділі \*(L"ВСТАНОВЛЕННЯ ПАКУНКІВ\*(R" in \fBvirt\-builder\fR\|(1).
.Sp
Див. також \fI\-\-update\fR, \fI\-\-uninstall\fR.
.ie n .IP "\fB\-\-keep\-user\-accounts\fR КОРИСТУВАЧІ (див. ""user\-account"" нижче)" 4
.el .IP "\fB\-\-keep\-user\-accounts\fR КОРИСТУВАЧІ (див. \f(CWuser\-account\fR нижче)" 4
.IX Item "--keep-user-accounts КОРИСТУВАЧІ (див. user-account нижче)"
-Облікові записи користувачів, які слід залишити у гостьовій
-системі. Значенням цього параметра є список імен користувачів, відокремлених
-комами, який визначатиме ті записи, які слід зберегти. Приклад:
+Облікові записи користувачів, які слід залишити у гостьовій системі. Значенням цього параметра є список імен користувачів, відокремлених комами, який визначатиме ті записи, які слід зберегти. Приклад:
.Sp
.Vb 1
\& \-\-keep\-user\-accounts mary
.ie n .IP "\fB\-\-link\fR ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..] (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-link\fR ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..] (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--link ПРИЗНАЧЕННЯ:ПОСИЛАННЯ[:ПОСИЛАННЯ..] (див. customize нижче)"
-Створити символічне посилання або декілька посилань у гостьовій системі так,
-щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
+Створити символічне посилання або декілька посилань у гостьовій системі так, щоб вони з \f(CW\*(C`ПОСИЛАННЯ\*(C'\fR вказували на \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR.
.ie n .IP "\fB\-\-mkdir\fR КАТАЛОГ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-mkdir\fR КАТАЛОГ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--mkdir КАТАЛОГ (див. customize нижче)"
Створити каталог у гостьовій системі.
.Sp
-Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні
-каталоги. Також команда працює, якщо каталог вже існує.
+Використовується \f(CW\*(C`mkdir \-p\*(C'\fR, отже буде створено усі проміжні каталоги. Також команда працює, якщо каталог вже існує.
.ie n .IP "\fB\-\-move\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-move\fR ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--move ДЖЕРЕЛО:ПРИЗНАЧЕННЯ (див. customize нижче)"
.ie n .IP "\fB\-\-no\-logfile\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-no\-logfile\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--no-logfile (див. customize нижче)"
-Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після
-завершення збирання. Якщо ви не хочете явним чином показувати, як було
-зібрано образ, скористайтеся цим параметром.
+Витерти \f(CW\*(C`builder.log\*(C'\fR (файл журналу із командами збирання) з образу після завершення збирання. Якщо ви не хочете явним чином показувати, як було зібрано образ, скористайтеся цим параметром.
.Sp
Див. також \*(L"\s-1LOG FILE\*(R"\s0.
.ie n .IP "\fB\-\-password\fR КОРИСТУВАЧ:ВАРІАНТ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-password\fR КОРИСТУВАЧ:ВАРІАНТ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--password КОРИСТУВАЧ:ВАРІАНТ (див. customize нижче)"
-Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою
-цього параметра \fIне можна\fR створювати облікові записи користувачів.)
+Встановити пароль для користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR. (Зауважте, що за допомогою цього параметра \fIне можна\fR створювати облікові записи користувачів.)
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
.ie n .IP "\fB\-\-password\-crypto\fR md5|sha256|sha512 (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-password\-crypto\fR md5|sha256|sha512 (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--password-crypto md5|sha256|sha512 (див. customize нижче)"
-Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою
-цього параметра можна встановити шифрування для цього пароля у значення
-\&\f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
-.Sp
-Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc
-≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
-.Sp
-\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux
-(наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
-.Sp
-Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо
-libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо
-такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою
-цього параметра ви можете перевизначити автоматично визначений libguestfs
-спосіб шифрування.
-.Sp
-Зауважте, що це не змінить типового шифрування, яке використовується
-гостьовою системою, коли ви створюєте у ній нові облікові записи
-користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися
-параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR
-(Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
+Якщо змінюється чи встановлюється пароль для гостьової системи, за допомогою цього параметра можна встановити шифрування для цього пароля у значення \f(CW\*(C`md5\*(C'\fR, \f(CW\*(C`sha256\*(C'\fR або \f(CW\*(C`sha512\*(C'\fR.
+.Sp
+Для використання значень \f(CW\*(C`sha256\*(C'\fR та \f(CW\*(C`sha512\*(C'\fR має бути встановлено glibc ≥ 2.7 (перевірте у \fBcrypt\fR\|(3) всередині гостьової системи).
+.Sp
+\&\f(CW\*(C`md5\*(C'\fR працюватиме з відносно давніми гостьовими системами Linux (наприкладRHEL 3), але є незахищеним щодо новітніх способів атак.
+.Sp
+Типовим способом шифрування є \f(CW\*(C`sha512\*(C'\fR. Він використовується, якщо libguestfs вдасться виявити у гостьовій системі підтримку \s-1SHA\-512.\s0 Якщо такої підтримки не буде виявлено, використовуватиметься \f(CW\*(C`md5\*(C'\fR. За допомогою цього параметра ви можете перевизначити автоматично визначений libguestfs спосіб шифрування.
+.Sp
+Зауважте, що це не змінить типового шифрування, яке використовується гостьовою системою, коли ви створюєте у ній нові облікові записи користувачів. Якщо ви хочете змінити це шифрування, вам слід скористатися параметром \fI\-\-edit\fR для внесення змін до \f(CW\*(C`/etc/sysconfig/authconfig\*(C'\fR (Fedora, \s-1RHEL\s0) або \f(CW\*(C`/etc/pam.d/common\-password\*(C'\fR (Debian, Ubuntu).
.ie n .IP "\fB\-\-remove\-user\-accounts\fR КОРИСТУВАЧІ (див. ""user\-account"" нижче)" 4
.el .IP "\fB\-\-remove\-user\-accounts\fR КОРИСТУВАЧІ (див. \f(CWuser\-account\fR нижче)" 4
.IX Item "--remove-user-accounts КОРИСТУВАЧІ (див. user-account нижче)"
-Облікові записи користувачів, які слід вилучити з гостьової
-системи. Значенням цього параметра є список імен користувачів, відокремлених
-комами, який визначатиме ті записи, які слід вилучити. Приклад:
+Облікові записи користувачів, які слід вилучити з гостьової системи. Значенням цього параметра є список імен користувачів, відокремлених комами, який визначатиме ті записи, які слід вилучити. Приклад:
.Sp
.Vb 1
\& \-\-remove\-user\-accounts bob,eve
.IX Item "--root-password ВАРІАНТ (див. customize нижче)"
Встановити пароль користувача root.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів
-користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR та способи налаштовування облікових записів користувачів описано у розділі \*(L"КОРИСТУВАЧІ І ПАРОЛІ\*(R" in \fBvirt\-builder\fR\|(1).
.Sp
-Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для
-гостьової системи буде використано \fIвипадковий\fR пароль root.
+Зауваження: якщо у virt-builder ви \fIне встановите\fR \fI\-\-root\-password\fR, для гостьової системи буде використано \fIвипадковий\fR пароль root.
.ie n .IP "\fB\-\-run\fR СКРИПТ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-run\fR СКРИПТ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--run СКРИПТ (див. customize нижче)"
-Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR
-у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій
-допоміжній системі, у пісочниці гостьової файлової системи.
+Виконати скрипт оболонки (або будь\-яку програму), яка називається \f(CW\*(C`СКРИПТ\*(C'\fR у образі диска. Скрипт буде запущено у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
Для скрипту буде автоматично використано команду chmod +x.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому
-порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.ie n .IP "\fB\-\-run\-command\fR 'КОМАНДА+ПАРАМЕТРИ' (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-run\-command\fR 'КОМАНДА+ПАРАМЕТРИ' (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--run-command 'КОМАНДА+ПАРАМЕТРИ' (див. customize нижче)"
-Виконати команду із аргументами у образі диска. Команду буде виконано у
-віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової
-файлової системи.
+Виконати команду із аргументами у образі диска. Команду буде виконано у віртуалізованому режимі у малій допоміжній системі, у пісочниці гостьової файлової системи.
.Sp
-Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене
-мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати
-диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних
-(наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у
-з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з
-даними (\fI\-\-upload\fR).
+Якщо у libguestfs передбачено підтримку цього, буде доступним обмежене мережеве з'єднання, але лише для вихідних з'єднань. Ви також можете долучати диски з даними (наприклад, файли \s-1ISO\s0), як ще один спосіб надання даних (наприклад, пакунків із програмним забезпеченням) для скрипту без потреби у з'єднанні із мережею (\fI\-\-attach\fR). Також ви можете вивантажувати файли з даними (\fI\-\-upload\fR).
.Sp
-Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому
-самому порядку, у якому їх вказано у рядку команди.
+Можна вказати декілька параметрів \fI\-\-run\-command\fR. Їх буде виконано у тому самому порядку, у якому їх вказано у рядку команди.
.Sp
Див. також \fI\-\-firstboot\fR, \fI\-\-attach\fR, \fI\-\-upload\fR.
.ie n .IP "\fB\-\-script\fR СКРИПТ (див. ""script"" нижче)" 4
.el .IP "\fB\-\-script\fR СКРИПТ (див. \f(CWscript\fR нижче)" 4
.IX Item "--script СКРИПТ (див. script нижче)"
-Запустити вказаний \f(CW\*(C`СКРИПТ\*(C'\fR (скрипт оболонки або програму) над
-гостьовою системою. Скриптом може бути будь\-яка програма у
-основній системі. Поточним каталогом скрипту буде кореневий
-каталог гостьової системи.
+Запустити вказаний \f(CW\*(C`СКРИПТ\*(C'\fR (скрипт оболонки або програму) над гостьовою системою. Скриптом може бути будь\-яка програма у основній системі. Поточним каталогом скрипту буде кореневий каталог гостьової системи.
.Sp
-\&\fBНотатка:\fR якщо скрипт не перебуває у каталозі \f(CW$PATH\fR, вам слід вказати шлях
-до скрипту повністю.
+\&\fBНотатка:\fR якщо скрипт не перебуває у каталозі \f(CW$PATH\fR, вам слід вказати шлях до скрипту повністю.
.ie n .IP "\fB\-\-scriptdir\fR КАТАЛОГ_СКРИПТІВ (див. ""script"" нижче)" 4
.el .IP "\fB\-\-scriptdir\fR КАТАЛОГ_СКРИПТІВ (див. \f(CWscript\fR нижче)" 4
.IX Item "--scriptdir КАТАЛОГ_СКРИПТІВ (див. script нижче)"
-Точку монтування (порожній каталог на вузлі), використану при виконанні дії
-\&\f(CW\*(C`script\*(C'\fR, увімкнено і вказано використання одного або декількох скриптів за
-допомогою \fI\-\-script\fR.
+Точку монтування (порожній каталог на вузлі), використану при виконанні дії \f(CW\*(C`script\*(C'\fR, увімкнено і вказано використання одного або декількох скриптів за допомогою \fI\-\-script\fR.
.Sp
\&\fBЗауваження:\fR \f(CW\*(C`SCRIPTDIR\*(C'\fR \fBмає\fR бути вказано повністю.
.Sp
.ie n .IP "\fB\-\-selinux\-relabel\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-selinux\-relabel\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--selinux-relabel (див. customize нижче)"
-Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були
-правильними з точки зору SELinux.
+Повторно встановити мітки для файлів у гостьовій системі так, щоб вони були правильними з точки зору SELinux.
.Sp
-Якщо буде використано цей параметр, програма спробує змінити мітки файлів
-негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла
-\&\fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на
-наступне завантаження образу.
+Якщо буде використано цей параметр, програма спробує змінити мітки файлів негайно, але якщо цього зробити не вдасться, вона змінить часову мітку файла \fI/.autorelabel\fR на образі, щоб дію зі зміни міток було заплановано на наступне завантаження образу.
.Sp
-Вам слід використовувати цей параметр лише для гостьових систем із
-підтримкою SELinux.
+Вам слід використовувати цей параметр лише для гостьових систем із підтримкою SELinux.
.ie n .IP "\fB\-\-sm\-attach\fR ВАРІАНТ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-sm\-attach\fR ВАРІАНТ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--sm-attach ВАРІАНТ (див. customize нижче)"
Долучити систему до буфера передплати за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
.ie n .IP "\fB\-\-sm\-credentials\fR ВАРІАНТ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-sm\-credentials\fR ВАРІАНТ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--sm-credentials ВАРІАНТ (див. customize нижче)"
Встановити реєстраційні дані для \f(CW\*(C`subscription\-manager\*(C'\fR.
.Sp
-Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі
-\&\*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
+Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"SUBSCRIPTION-MANAGER\*(R" in \fBvirt\-builder\fR\|(1).
.ie n .IP "\fB\-\-sm\-register\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-sm\-register\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--sm-register (див. customize нижче)"
.ie n .IP "\fB\-\-sm\-remove\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-sm\-remove\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--sm-remove (див. customize нижче)"
-Вилучити усі передплати з гостьової системи за допомогою
-\&\f(CW\*(C`subscription\-manager\*(C'\fR.
+Вилучити усі передплати з гостьової системи за допомогою \f(CW\*(C`subscription\-manager\*(C'\fR.
.ie n .IP "\fB\-\-sm\-unregister\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-sm\-unregister\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--sm-unregister (див. customize нижче)"
.ie n .IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ[:ВАРІАНТ] (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-ssh\-inject\fR КОРИСТУВАЧ[:ВАРІАНТ] (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--ssh-inject КОРИСТУВАЧ[:ВАРІАНТ] (див. customize нижче)"
-Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з
-використанням ssh без потреби у визначенні пароля. Запис користувача
-\&\f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
+Вставити ключ ssh так, щоб вказаний \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR зміг увійти до системи з використанням ssh без потреби у визначенні пароля. Запис користувача \f(CW\*(C`КОРИСТУВАЧ\*(C'\fR має вже існувати у гостьовій системі.
.Sp
Формат поля \f(CW\*(C`ВАРІАНТ\*(C'\fR описано у розділі \*(L"КЛЮЧІ \s-1SSH\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.Sp
-Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних
-користувачів, а також для додавання декількох ключів для кожного з
-користувачів.
+Ви можете додати декілька параметрів \fI\-\-ssh\-inject\fR для різних користувачів, а також для додавання декількох ключів для кожного з користувачів.
.ie n .IP "\fB\-\-timezone\fR ЧАСОВИЙ_ПОЯС (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-timezone\fR ЧАСОВИЙ_ПОЯС (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--timezone ЧАСОВИЙ_ПОЯС (див. customize нижче)"
-Встановити типовий часовий пояс гостьової системи у значення
-\&\f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
+Встановити типовий часовий пояс гостьової системи у значення \f(CW\*(C`ЧАСОВИЙ_ПОЯС\*(C'\fR. Скористайтеся рядком місця у форматі \f(CW\*(C`Europe/London\*(C'\fR
.ie n .IP "\fB\-\-touch\fR ФАЙЛ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-touch\fR ФАЙЛ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--touch ФАЙЛ (див. customize нижче)"
.ie n .IP "\fB\-\-truncate\fR ФАЙЛ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-truncate\fR ФАЙЛ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--truncate ФАЙЛ (див. customize нижче)"
-Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного
-виконання файл має існувати.
+Ця команда обрізає файл \f(CW\*(C`ФАЙЛ\*(C'\fR до нульової довжини. Для її успішного виконання файл має існувати.
.ie n .IP "\fB\-\-truncate\-recursive\fR ШЛЯХ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-truncate\-recursive\fR ШЛЯХ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--truncate-recursive ШЛЯХ (див. customize нижче)"
-Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової
-довжини.
+Ця команда рекурсивно обрізає усі файли у каталозі \f(CW\*(C`ШЛЯХ\*(C'\fR до нульової довжини.
.ie n .IP "\fB\-\-uninstall\fR ПАКУНОК,ПАКУНОК... (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-uninstall\fR ПАКУНОК,ПАКУНОК... (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--uninstall ПАКУНОК,ПАКУНОК... (див. customize нижче)"
-Вилучити іменовані пакунки (список значень, відокремлених комами). Ці
-пакунки буде вилучено під час збирання образу за допомогою програми для
-керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою
-виконання запиту також може бути вилучено пакунки, залежні від вилучених
-пакунків.
+Вилучити іменовані пакунки (список значень, відокремлених комами). Ці пакунки буде вилучено під час збирання образу за допомогою програми для керування пакунків гостьової системи (наприклад, apt, yum тощо). З метою виконання запиту також може бути вилучено пакунки, залежні від вилучених пакунків.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-update\fR.
.ie n .IP "\fB\-\-update\fR (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-update\fR (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--update (див. customize нижче)"
-Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої
-команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні,
-до найсвіжіших версій.
+Виконує еквівалент \f(CW\*(C`yum update\*(C'\fR, \f(CW\*(C`apt\-get upgrade\*(C'\fR або якоїсь іншої команди, яка потрібна для оновлення пакунків, які вже встановлено у шаблоні, до найсвіжіших версій.
.Sp
Див. також \fI\-\-install\fR, \fI\-\-uninstall\fR.
.ie n .IP "\fB\-\-upload\fR ФАЙЛ:ПРИЗНАЧЕННЯ (див. ""customize"" нижче)" 4
.el .IP "\fB\-\-upload\fR ФАЙЛ:ПРИЗНАЧЕННЯ (див. \f(CWcustomize\fR нижче)" 4
.IX Item "--upload ФАЙЛ:ПРИЗНАЧЕННЯ (див. customize нижче)"
-Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі
-диска. Буде збережено власника і права доступу, отже вам слід вказати такі
-значення для цих параметрів, які мають бути на остаточному образі диска.
+Вивантажити локальний файл \f(CW\*(C`ФАЙЛ\*(C'\fR до призначення \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR на образі диска. Буде збережено власника і права доступу, отже вам слід вказати такі значення для цих параметрів, які мають бути на остаточному образі диска.
.Sp
-Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим
-можна скористатися для перейменовування файла під час вивантаження.
+Значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR може бути назва остаточного файла. Цим можна скористатися для перейменовування файла під час вивантаження.
.Sp
-Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має
-існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу,
-назву файла з локальної файлової системи буде збережено.
+Якщо значенням параметра \f(CW\*(C`ПРИЗНАЧЕННЯ\*(C'\fR є назва каталогу (який вже має існувати у гостьовій системі), файл буде вивантажено до вказаного каталогу, назву файла з локальної файлової системи буде збережено.
.Sp
Див. також \fI\-\-mkdir\fR, \fI\-\-delete\fR, \fI\-\-scrub\fR.
.ie n .IP "\fB\-\-write\fR ФАЙЛ:ВМІСТ (див. ""customize"" нижче)" 4
Записати \f(CW\*(C`ДАНІ\*(C'\fR до файла \f(CW\*(C`ФАЙЛ\*(C'\fR.
.SH "ДІЇ"
.IX Header "ДІЇ"
-Якщо параметр \fI\-\-enable\fR/\fI\-\-operations\fR \fIне\fR вказано, більшу частину дій
-з приготування системи буде увімкнено.
+Якщо параметр \fI\-\-enable\fR/\fI\-\-operations\fR \fIне\fR вказано, більшу частину дій з приготування системи буде увімкнено.
.PP
-Скористайтеся командою \f(CW\*(C`virt\-sysprep \-\-list\-operations\*(C'\fR, щоб переглянути
-список усіх дій, які передбачено у вашому виконуваному файлі
-virt-sysprep. Дії, які типово увімкнено, буде позначено у списку символом
-\&\f(CW\*(C`*\*(C'\fR. Незалежно від вказаних параметрів \fI\-\-enable\fR/\fI\-\-operations\fR для
-певних типів гостьових систем деякі з дій з приготування системи
-пропускатимуться.
+Скористайтеся командою \f(CW\*(C`virt\-sysprep \-\-list\-operations\*(C'\fR, щоб переглянути список усіх дій, які передбачено у вашому виконуваному файлі virt-sysprep. Дії, які типово увімкнено, буде позначено у списку символом \f(CW\*(C`*\*(C'\fR. Незалежно від вказаних параметрів \fI\-\-enable\fR/\fI\-\-operations\fR для певних типів гостьових систем деякі з дій з приготування системи пропускатимуться.
.PP
-Окремі дії можна увімкнути за допомогою параметрів
-\&\fI\-\-enable\fR/\fI\-\-operations\fR. Записи дій у списку слід відокремлювати
-комами. Приклад:
+Окремі дії можна увімкнути за допомогою параметрів \fI\-\-enable\fR/\fI\-\-operations\fR. Записи дій у списку слід відокремлювати комами. Приклад:
.PP
.Vb 1
\& virt\-sysprep \-\-operations ssh\-hostkeys,udev\-persistent\-net [тощо..]
.Ve
.PP
-У майбутніх версіях virt-sysprep може бути додано інші дії. Якщо ви
-використовуєте virt-sysprep, і вам потрібна передбачувана поведінка,
-вказуйте лише ті дії, які ви хочете увімкнути.
+У майбутніх версіях virt-sysprep може бути додано інші дії. Якщо ви використовуєте virt-sysprep, і вам потрібна передбачувана поведінка, вказуйте лише ті дії, які ви хочете увімкнути.
.PP
-\&\f(CW\*(C`*\*(C'\fR = типово увімкнено, якщо не вказано параметрів
-\&\fI\-\-enable\fR/\fI\-\-operations\fR.
+\&\f(CW\*(C`*\*(C'\fR = типово увімкнено, якщо не вказано параметрів \fI\-\-enable\fR/\fI\-\-operations\fR.
.SS "\fBabrt-data\fP *"
.IX Subsection "abrt-data *"
Вилучити дані щодо аварії, створені \s-1ABRT.\s0
.IX Subsection "backup-files *"
Вилучити файли резервних копій редактора з гостьової системи.
.PP
-Вказані нижче файли буде вилучено з усіх каталогів файлової системи
-гостьової операційної системи:
+Вказані нижче файли буде вилучено з усіх каталогів файлової системи гостьової операційної системи:
.IP "·" 4
*.bak
.IP "·" 4
*~
.PP
-У операційних системах Linux та Unix оброблятимуться лише такі файлові
-системи:
+У операційних системах Linux та Unix оброблятимуться лише такі файлові системи:
.IP "·" 4
/etc
.IP "·" 4
.IX Subsection "bash-history *"
Вилучити журнал команд bash у гостьовій системі.
.PP
-Вилучити журнал команд bash користувача «root» та всіх інших користувачів, у
-домашніх каталогах яких містяться файли \f(CW\*(C`.bash_history\*(C'\fR.
+Вилучити журнал команд bash користувача «root» та всіх інших користувачів, у домашніх каталогах яких містяться файли \f(CW\*(C`.bash_history\*(C'\fR.
.PP
\fIНотатки щодо журналу команд bash\fR
.IX Subsection "Нотатки щодо журналу команд bash"
.PP
-У поточній версії пошук домашніх каталогів користувачів виконується лише у
-\&\f(CW\*(C`/root\*(C'\fR і \f(CW\*(C`/home/*\*(C'\fR. Отже, журнал bash користувачів, дані яких
-зберігаються у інших каталогах, не буде вилучено.
+У поточній версії пошук домашніх каталогів користувачів виконується лише у \f(CW\*(C`/root\*(C'\fR і \f(CW\*(C`/home/*\*(C'\fR. Отже, журнал bash користувачів, дані яких зберігаються у інших каталогах, не буде вилучено.
.SS "\fBblkid-tab\fP *"
.IX Subsection "blkid-tab *"
Вилучити вкладку ідентифікаторів блоків у гостьовій системі.
.IX Subsection "customize *"
Налаштувати гостьову систему.
.PP
-Налаштувати гостьову систему визначенням параметрів \fBvirt\-customize\fR\|(1) для
-встановлення пакунків, редагування файлів тощо.
+Налаштувати гостьову систему визначенням параметрів \fBvirt\-customize\fR\|(1) для встановлення пакунків, редагування файлів тощо.
.SS "\fBdhcp-client-state\fP *"
.IX Subsection "dhcp-client-state *"
Вилучити надані клієнтські адреси \s-1DHCP.\s0
.IX Subsection "firewall-rules"
Вилучити правила брандмауера.
.PP
-Вилучає нетипові правила брандмауера вилученням \f(CW\*(C`/etc/sysconfig/iptables\*(C'\fR
-або нетипових налаштувань firewalld з \f(CW\*(C`/etc/firewalld/*/*\*(C'\fR.
+Вилучає нетипові правила брандмауера вилученням \f(CW\*(C`/etc/sysconfig/iptables\*(C'\fR або нетипових налаштувань firewalld з \f(CW\*(C`/etc/firewalld/*/*\*(C'\fR.
.PP
-Зауважте, що цю можливість типово \fIне\fR увімкнено, оскільки може відкрити
-гостьову систему для вразливостей. Користуйтеся обережно.
+Зауважте, що цю можливість типово \fIне\fR увімкнено, оскільки може відкрити гостьову систему для вразливостей. Користуйтеся обережно.
.SS "\fBflag-reconfiguration\fP"
.IX Subsection "flag-reconfiguration"
Позначити систему для зміни налаштувань.
.PP
-Для гостьових систем Linux оновлює часову позначку \f(CW\*(C`/.unconfigured\*(C'\fR, отже,
-під час першого завантаження користувачеві буде надіслано запит щодо
-параметрів, зокрема пароля root та часового поясу.
+Для гостьових систем Linux оновлює часову позначку \f(CW\*(C`/.unconfigured\*(C'\fR, отже, під час першого завантаження користувачеві буде надіслано запит щодо параметрів, зокрема пароля root та часового поясу.
.SS "\fBfs-uuids\fP"
.IX Subsection "fs-uuids"
Змінити \s-1UUID\s0 файлових систем.
.PP
-У гостьових системах та типах файлових систем, де передбачено таку
-підтримку, буде створено нові випадкові \s-1UUID,\s0 які буде пов’язано з файловими
-системами.
+У гостьових системах та типах файлових систем, де передбачено таку підтримку, буде створено нові випадкові \s-1UUID,\s0 які буде пов’язано з файловими системами.
.PP
\fIЗауваження щодо fs-uuids\fR
.IX Subsection "Зауваження щодо fs-uuids"
.PP
-Типово, дію fs-uuids вимкнено, оскільки у поточній версії програма ще не
-здатна знайти і оновити усі записи у гостьовій системі, які використовують
-\&\s-1UUID,\s0 наприклад \f(CW\*(C`/etc/fstab\*(C'\fR або завантажувач. Вмикання цієї дії може з
-високою ймовірністю зробити вашу гостьову систему непридатною до
-завантаження.
+Типово, дію fs-uuids вимкнено, оскільки у поточній версії програма ще не здатна знайти і оновити усі записи у гостьовій системі, які використовують \s-1UUID,\s0 наприклад \f(CW\*(C`/etc/fstab\*(C'\fR або завантажувач. Вмикання цієї дії може з високою ймовірністю зробити вашу гостьову систему непридатною до завантаження.
.PP
Див. https://bugzilla.redhat.com/show_bug.cgi?id=991641
.SS "\fBipa-client\fP *"
.IX Subsection "ipa-client *"
Remove the \s-1IPA\s0 files.
.PP
-Remove all the files related to an \s-1IPA\s0 (Identity, Policy, Audit) system.
-This effectively unenrolls the guest from an \s-1IPA\s0 server without interacting
-with it.
+Remove all the files related to an \s-1IPA\s0 (Identity, Policy, Audit) system. This effectively unenrolls the guest from an \s-1IPA\s0 server without interacting with it.
.PP
This operation does not run \f(CW\*(C`ipa\-client\*(C'\fR.
.SS "\fBдані\-kerberos\fP"
.IX Subsection "lvm-uuids *"
Змінити \s-1UUID\s0 ФТ і ГТ \s-1LVM2.\s0
.PP
-Для гостьових систем Linux, які містять фізичні томи (ФТ) або групи томів
-(ГТ) \s-1LVM2\s0 для ФТ і ГТ буде створено і призначено випадкові \s-1UUID.\s0
+Для гостьових систем Linux, які містять фізичні томи (ФТ) або групи томів (ГТ) \s-1LVM2\s0 для ФТ і ГТ буде створено і призначено випадкові \s-1UUID.\s0
.SS "\fBід\-комп’ютера\fP *"
.IX Subsection "ід-комп’ютера *"
Вилучити ідентифікатор локального комп’ютера.
.PP
-Зазвичай, ідентифікатор системи створюється на основі випадкових джерел
-даних під час встановлення системи і не змінюється під час всіх наступних її
-завантажень. За потреби у системах без певного стану цей ідентифікатор
-створюється під час роботи завантажувача,
-якщо буде виявлено порожнє значення.
+Зазвичай, ідентифікатор системи створюється на основі випадкових джерел даних під час встановлення системи і не змінюється під час всіх наступних її завантажень. За потреби у системах без певного стану цей ідентифікатор створюється під час роботи завантажувача, якщо буде виявлено порожнє значення.
.SS "\fBmail-spool\fP *"
.IX Subsection "mail-spool *"
Вилучити поштове повідомлення з локального каталогу поштового буфера.
Вилучити налаштування \s-1HWADDR\s0 (апаратної адреси \s-1MAC\s0).
.PP
Для Fedora і Red Hat Enterprise Linux це вилучається з файлів \f(CW\*(C`ifcfg\-*\*(C'\fR.
+.SS "\fBnet-nmconn\fP *"
+.IX Subsection "net-nmconn *"
+Remove system-local NetworkManager connection profiles (keyfiles).
+.PP
+On Fedora and Red Hat Enterprise Linux, remove the \f(CW\*(C`/etc/NetworkManager/system\-connections/*.nmconnection\*(C'\fR files.
.SS "\fBpacct-log\fP *"
.IX Subsection "pacct-log *"
Вилучити файли журналу обліку процесів.
.PP
-Дані обліку процесів системи будуть зберігатися у файлах журналу pacct, якщо
-увімкнено облік процесів.
+Дані обліку процесів системи будуть зберігатися у файлах журналу pacct, якщо увімкнено облік процесів.
.SS "\fBpackage-manager-cache\fP *"
.IX Subsection "package-manager-cache *"
Вилучити кеш керування пакунками.
.IX Subsection "rpm-db *"
Вилучити специфічні для системи файли баз даних \s-1RPM.\s0
.PP
-Вилучити специфічні для системи файли баз даних \s-1RPM. RPM\s0 буде повторно
-створено ці файли, якщо це потрібно.
+Вилучити специфічні для системи файли баз даних \s-1RPM. RPM\s0 буде повторно створено ці файли, якщо це потрібно.
.SS "\fBsamba-db-log\fP *"
.IX Subsection "samba-db-log *"
Вилучити бази даних та файли журналів Samba.
.IX Subsection "script *"
Запустити довільні скрипти дій над гостьовою системою.
.PP
-Модуль \f(CW\*(C`script\*(C'\fR надає вам змогу запускати довільні скрипти оболонки або
-програми для обробки гостьових систем.
+Модуль \f(CW\*(C`script\*(C'\fR надає вам змогу запускати довільні скрипти оболонки або програми для обробки гостьових систем.
.PP
-Зауважте, що використання цієї можливості потребує підтримки \s-1FUSE.\s0 Вам варто
-увімкнути цю підтримку у вашій основній системі, наприклад, додаванням
-поточного користувача до групи \f(CW\*(C`fuse\*(C'\fR або завантаженням модуля ядра.
+Зауважте, що використання цієї можливості потребує підтримки \s-1FUSE.\s0 Вам варто увімкнути цю підтримку у вашій основній системі, наприклад, додаванням поточного користувача до групи \f(CW\*(C`fuse\*(C'\fR або завантаженням модуля ядра.
.PP
-Скористайтеся одним або декількома параметрами \fI\-\-script\fR для визначення
-скриптів або програм, які слід запустити для обробки гостьової системи.
+Скористайтеся одним або декількома параметрами \fI\-\-script\fR для визначення скриптів або програм, які слід запустити для обробки гостьової системи.
.PP
-Скрипт або програма виконується з поточним каталогом, який є кореневим
-каталогом гостьової системи, отже слід використовувати відносні
-шляхи. Приклад: \f(CW\*(C`rm etc/resolv.conf\*(C'\fR у скрипті призведе до вилучення файла
-налаштувань \s-1DNS\s0 у гостьовій системі Linux, а \f(CW\*(C`rm /etc/resolv.conf\*(C'\fR
-(спробує) вилучити відповідний файл у основній системі.
+Скрипт або програма виконується з поточним каталогом, який є кореневим каталогом гостьової системи, отже слід використовувати відносні шляхи. Приклад: \f(CW\*(C`rm etc/resolv.conf\*(C'\fR у скрипті призведе до вилучення файла налаштувань \s-1DNS\s0 у гостьовій системі Linux, а \f(CW\*(C`rm /etc/resolv.conf\*(C'\fR (спробує) вилучити відповідний файл у основній системі.
.PP
-Зазвичай, використовується тимчасова точка монтування гостьової системи, але
-ви можете вибрати якусь іншу за допомогою параметра \fI\-\-scriptdir\fR.
+Зазвичай, використовується тимчасова точка монтування гостьової системи, але ви можете вибрати якусь іншу за допомогою параметра \fI\-\-scriptdir\fR.
.PP
-\&\fBЗауваження:\fR описані тут скрипти відрізняються від скриптів \fI\-\-firstboot\fR
-(скриптів, які виконуються у контексті гостьової системи під час першого
-завантаження цієї системи). Скрипти \fI\-\-script\fR запускаються у основній
-системі, а не у гостьовій.
+\&\fBЗауваження:\fR описані тут скрипти відрізняються від скриптів \fI\-\-firstboot\fR (скриптів, які виконуються у контексті гостьової системи під час першого завантаження цієї системи). Скрипти \fI\-\-script\fR запускаються у основній системі, а не у гостьовій.
.SS "\fBsmolt-uuid\fP *"
.IX Subsection "smolt-uuid *"
Вилучити \s-1UUID\s0 обладнання Smolt.
.IX Subsection "ssh-hostkeys *"
Вилучити ключі вузла \s-1SSH\s0 у гостьовій системі.
.PP
-Ключі вузла \s-1SSH\s0 повторно створюються (незалежно) під час наступного
-завантаження гостьової системи.
+Ключі вузла \s-1SSH\s0 повторно створюються (незалежно) під час наступного завантаження гостьової системи.
.PP
-Якщо після клонування гостьова система отримати ту саму IP\-адресу, ssh
-надасть вам додаткове попередження щодо зміни ключа вузла:
+Якщо після клонування гостьова система отримати ту саму IP\-адресу, ssh надасть вам додаткове попередження щодо зміни ключа вузла:
.PP
.Vb 4
\& @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
.IX Subsection "ssh-userdir *"
Вилучити каталоги «.ssh» у гостьовій системі.
.PP
-Вилучити каталог \f(CW\*(C`.ssh\*(C'\fR користувача «root» та всіх інших користувачів,
-домашні каталоги яких містять каталог \f(CW\*(C`.ssh\*(C'\fR.
+Вилучити каталог \f(CW\*(C`.ssh\*(C'\fR користувача «root» та всіх інших користувачів, домашні каталоги яких містять каталог \f(CW\*(C`.ssh\*(C'\fR.
.PP
\fIЗауваження щодо ssh-userdir\fR
.IX Subsection "Зауваження щодо ssh-userdir"
.PP
-У поточній версії пошук домашніх каталогів користувачів виконується лише у
-\&\f(CW\*(C`/root\*(C'\fR і \f(CW\*(C`/home/*\*(C'\fR. Отже, файли ssh користувачів, дані яких зберігаються
-у інших каталогах, не буде вилучено.
+У поточній версії пошук домашніх каталогів користувачів виконується лише у \f(CW\*(C`/root\*(C'\fR і \f(CW\*(C`/home/*\*(C'\fR. Отже, файли ssh користувачів, дані яких зберігаються у інших каталогах, не буде вилучено.
.SS "\fBsssd-db-log\fP *"
.IX Subsection "sssd-db-log *"
Вилучити бази даних і файли журналів sssd.
.IX Subsection "udev-persistent-net *"
Вилучити постійні правила мережі udev.
.PP
-Вилучити постійні правила мережі udev, які відображають вже створену
-MAC\-адресу гостьової системи на фіксований пристрій ethernet (наприклад
-eth0).
+Вилучити постійні правила мережі udev, які відображають вже створену MAC\-адресу гостьової системи на фіксований пристрій ethernet (наприклад eth0).
.PP
-Після клонування гостьової системи MAC\-адреса зазвичай змінюється. Оскільки
-стару MAC\-адресу вже пов’язано зі старою назвою (наприклад eth0), це
-означає, що нову MAC\-адресу буде пов’язано з новою назвою (наприклад eth1),
-а це зазвичай є небажаним. За допомогою вилучення постійних правил мережі
-udev цьому можна запобігти.
+Після клонування гостьової системи MAC\-адреса зазвичай змінюється. Оскільки стару MAC\-адресу вже пов’язано зі старою назвою (наприклад eth0), це означає, що нову MAC\-адресу буде пов’язано з новою назвою (наприклад eth1), а це зазвичай є небажаним. За допомогою вилучення постійних правил мережі udev цьому можна запобігти.
.SS "\fBuser-account\fP"
.IX Subsection "user-account"
Вилучити облікові записи користувачів у гостьовій системі.
.PP
-Типово вилучити всі облікові записи користувачів та відповідні домашні
-каталоги. Обліковий запис «root» вилучено не буде.
+Типово вилучити всі облікові записи користувачів та відповідні домашні каталоги. Обліковий запис «root» вилучено не буде.
.PP
-Див. опис параметра \fI\-\-remove\-user\-accounts\fR, щоб дізнатися про те, як
-наказати
-програмі вилучити лише деяких з користувачів і не вилучати інших.
+Див. опис параметра \fI\-\-remove\-user\-accounts\fR, щоб дізнатися про те, як наказати програмі вилучити лише деяких з користувачів і не вилучати інших.
.SS "\fButmp\fP *"
.IX Subsection "utmp *"
Вилучити файл utmp.
.PP
-У цьому файлі зберігаються записи щодо входу користувачів до машини. У
-сучасних дистрибутивах Linux ці записи зберігаються на диску у пам’яті, тому
-не є частиною віртуальної машини на диску, але ці дані зберігаються на диску
-у старіших версіях дистрибутивів.
+У цьому файлі зберігаються записи щодо входу користувачів до машини. У сучасних дистрибутивах Linux ці записи зберігаються на диску у пам’яті, тому не є частиною віртуальної машини на диску, але ці дані зберігаються на диску у старіших версіях дистрибутивів.
.SS "\fByum-uuid\fP *"
.IX Subsection "yum-uuid *"
Вилучити \s-1UUID\s0 yum.
.PP
-Yum створить новий \s-1UUID\s0 під час наступного запуску, коли виявить, що
-початковий \s-1UUID\s0 було вилучено.
+Yum створить новий \s-1UUID\s0 під час наступного запуску, коли виявить, що початковий \s-1UUID\s0 було вилучено.
.SH "КОПІЮВАННЯ ТА КЛОНУВАННЯ"
.IX Header "КОПІЮВАННЯ ТА КЛОНУВАННЯ"
-Virt-sysprep можна скористатися як частиною процедури клонування гостьових
-систем або приготування шаблона, з якого можна буде клонувати гостьові
-системи. Існує багато різних способів досягти цього за допомогою засобів
-віртуалізації, — цей розділ є лише вступом.
+Virt-sysprep можна скористатися як частиною процедури клонування гостьових систем або приготування шаблона, з якого можна буде клонувати гостьові системи. Існує багато різних способів досягти цього за допомогою засобів віртуалізації, — цей розділ є лише вступом.
.PP
Віртуальна машина (коли її вимкнено) складається з двох частин:
.IP "\fIналаштування\fR" 4
.IX Item "налаштування"
-Налаштування або опис гостьової системи. Приклади: \s-1XML\s0 libvirt (див. \f(CW\*(C`virsh
-dumpxml\*(C'\fR), поточні налаштування гостьової системи або інший зовнішній
-формат, наприклад \s-1OVF.\s0
+Налаштування або опис гостьової системи. Приклади: \s-1XML\s0 libvirt (див. \f(CW\*(C`virsh dumpxml\*(C'\fR), поточні налаштування гостьової системи або інший зовнішній формат, наприклад \s-1OVF.\s0
.Sp
Деякі пункти налаштувань, які варто було б змінити:
.RS 4
.RE
.IP "\fIблокові пристрої\fR" 4
.IX Item "блокові пристрої"
-Один або декілька образів дисків, які самі містять файли, каталоги,
-програми, ядра, налаштування тощо.
+Один або декілька образів дисків, які самі містять файли, каталоги, програми, ядра, налаштування тощо.
.Sp
-Ось деякі параметри всередині блокових пристроїв, які, можливо, доведеться
-змінити:
+Ось деякі параметри всередині блокових пристроїв, які, можливо, доведеться змінити:
.RS 4
.IP "\(bu" 4
назва вузла та інші налаштування мережі
.RE
.SS "КОПІЮВАННЯ БЛОКОВОГО ПРИСТРОЮ"
.IX Subsection "КОПІЮВАННЯ БЛОКОВОГО ПРИСТРОЮ"
-Маючи початкову гостьову систему, ви, ймовірно, хочете скопіювати блоковий
-пристрій гостьової системи і його налаштування, щоб створити шаблон. Далі,
-коли вас задовольнятимуть характеристики шаблона, ви захочете створити на
-його основі клони.
+Маючи початкову гостьову систему, ви, ймовірно, хочете скопіювати блоковий пристрій гостьової системи і його налаштування, щоб створити шаблон. Далі, коли вас задовольнятимуть характеристики шаблона, ви захочете створити на його основі клони.
.PP
.Vb 7
\& virt\-sysprep
\& \e\-\-\-\->
.Ve
.PP
-Ви, звичайно ж, можете просто скопіювати блоковий пристрій на основну
-систему за допомогою \fBcp\fR\|(1) або \fBdd\fR\|(1).
+Ви, звичайно ж, можете просто скопіювати блоковий пристрій на основну систему за допомогою \fBcp\fR\|(1) або \fBdd\fR\|(1).
.PP
.Vb 5
\& dd dd
\& \e\-\-\-\->
.Ve
.PP
-Ймовірно, virt-sysprep доведеться запустити двічі — один раз для відновлення
-початкового стану гостьової системи (для створення шаблона) і другий раз для
-налаштовування гостьової системи для певного користувача:
+Ймовірно, virt-sysprep доведеться запустити двічі — один раз для відновлення початкового стану гостьової системи (для створення шаблона) і другий раз для налаштовування гостьової системи для певного користувача:
.PP
.Vb 6
\& virt\-sysprep virt\-sysprep
\& qemu\-img create \-f qcow2 \-o backing_file=original snapshot.qcow
.Ve
.Sp
-Перевагою є те, що вам не потрібно буде копіювати оригінал (дуже швидко), і
-те, що зберігатимуться лише зміни (менше вживання місця у сховищі даних).
+Перевагою є те, що вам не потрібно буде копіювати оригінал (дуже швидко), і те, що зберігатимуться лише зміни (менше вживання місця у сховищі даних).
.Sp
-Зауважте, що запис резервного файла після створення на його основі гостьових
-систем неможливий: такий запис призведе до пошкодження гостьових систем.
+Зауважте, що запис резервного файла після створення на його основі гостьових систем неможливий: такий запис призведе до пошкодження гостьових систем.
.IP "\(bu" 4
Створити знімок за допомогою \f(CW\*(C`lvcreate \-\-snapshot\*(C'\fR.
.IP "\(bu" 4
-До інших способів створення знімків належить використання засобів файлової
-системи (для файлових систем, які подібні до btrfs).
+До інших способів створення знімків належить використання засобів файлової системи (для файлових систем, які подібні до btrfs).
.Sp
-На більшості пристроїв Network Attached Storage (\s-1NAS\s0) передбачено можливість
-простого створення знімків на основі файлів та \s-1LUN.\s0
+На більшості пристроїв Network Attached Storage (\s-1NAS\s0) передбачено можливість простого створення знімків на основі файлів та \s-1LUN.\s0
.IP "\(bu" 4
-Накажіть вашому \s-1NAS\s0 здублювати \s-1LUN.\s0 На більшості пристроїв \s-1NAS\s0 також
-передбачено дуже просте дублювання \s-1LUN\s0 (копіювання відбувається у фоновому
-режимі за запитом).
+Накажіть вашому \s-1NAS\s0 здублювати \s-1LUN.\s0 На більшості пристроїв \s-1NAS\s0 також передбачено дуже просте дублювання \s-1LUN\s0 (копіювання відбувається у фоновому режимі за запитом).
.IP "\(bu" 4
Приготуйте ваш шаблон за допомогою \fBvirt\-sparsify\fR\|(1). Див. нижче.
.SS "VIRT-CLONE"
.IX Subsection "VIRT-CLONE"
-Для дублювання блокового пристрою і/або внесення змін до зовнішніх
-налаштувань libvirt гостьової системи можна скористатися окремим
-інструментом, \fBvirt\-clone\fR\|(1). Ця програма відновить початкові значення
-назви, \s-1UUID\s0 та адреси \s-1MAC\s0 гостьової системи в \s-1XML\s0 libvirt.
+Для дублювання блокового пристрою і/або внесення змін до зовнішніх налаштувань libvirt гостьової системи можна скористатися окремим інструментом, \fBvirt\-clone\fR\|(1). Ця програма відновить початкові значення назви, \s-1UUID\s0 та адреси \s-1MAC\s0 гостьової системи в \s-1XML\s0 libvirt.
.PP
-\&\fBvirt\-clone\fR\|(1) не використовує libguestfs і не може «зазирнути» у образ
-диска. Це і було причиною для написання virt-sysprep.
+\&\fBvirt\-clone\fR\|(1) не використовує libguestfs і не може «зазирнути» у образ диска. Це і було причиною для написання virt-sysprep.
.SS "РОЗРІДЖЕННЯ"
.IX Subsection "РОЗРІДЖЕННЯ"
.Vb 2
\& початкова система \-\-\-\-\-\-\-\-> шаблон
.Ve
.PP
-\&\fBvirt\-sparsify\fR\|(1) можна скористатися для зменшення розмірів шаблона для
-клонування, спрощуючи стискання і/або пришвидшуючи копіювання.
+\&\fBvirt\-sparsify\fR\|(1) можна скористатися для зменшення розмірів шаблона для клонування, спрощуючи стискання і/або пришвидшуючи копіювання.
.PP
-Зауважте, що оскільки virt-sparsify також копіює образ, ви можете
-скористатися цією програмою для створення початкової копії (замість \f(CW\*(C`dd\*(C'\fR).
+Зауважте, що оскільки virt-sparsify також копіює образ, ви можете скористатися цією програмою для створення початкової копії (замість \f(CW\*(C`dd\*(C'\fR).
.SS "ЗМІНА РОЗМІРІВ"
.IX Subsection "ЗМІНА РОЗМІРІВ"
.Vb 5
\& \e\-\-\-\->
.Ve
.PP
-Якщо ви хочете надати комусь клоновані гостьові системи, але хочете надати
-можливість вибирати розмір гостьової системи (наприклад за місцем, яке
-надається гостьовій системі на диску), замість копіювання шаблона вам слід
-запустити \fBvirt\-resize\fR\|(1). Virt-resize виконує копіювання і зміну
-розмірів, тому програма є ідеальною для клонування гостьових систем з
-шаблона.
+Якщо ви хочете надати комусь клоновані гостьові системи, але хочете надати можливість вибирати розмір гостьової системи (наприклад за місцем, яке надається гостьовій системі на диску), замість копіювання шаблона вам слід запустити \fBvirt\-resize\fR\|(1). Virt-resize виконує копіювання і зміну розмірів, тому програма є ідеальною для клонування гостьових систем з шаблона.
.SH "FIRSTBOOT ЧИ SCRIPT"
.IX Header "FIRSTBOOT ЧИ SCRIPT"
-Обидва параметри, \fI\-\-firstboot\fR і \fI\-\-script\fR, запускають скрипти оболонки,
-яка виконують дії із гостьовою системою. Втім, ці параметри суттєво
-різняться.
-.PP
-\&\fI\-\-firstboot скрипт\fR вивантажує файл \f(CW\*(C`скрипт\*(C'\fR до гостьової системи і
-робить так, щоб він запускався у гостьовій системі під час наступного її
-завантаження. (Скрипт буде запущено лише один раз, при «першому
-завантаження».)
-.PP
-\&\fI\-\-script скрипт\fR запускає скрипт командної оболонки \f(CW\*(C`скрипт\*(C'\fR \fIу основній
-системі\fR, у поточному каталозі у файловій системі гостьової операційної
-системи.
-.PP
-Якщо вам, наприклад, потрібно виконати \f(CW\*(C`yum install\*(C'\fR для встановлення нових
-пакунків, вам \fIне слід\fR використовувати для цього \fI\-\-script\fR, оскільки це
-(а) запустить програму \f(CW\*(C`yum\*(C'\fR у основній системі і (б) не надасть програмі
-доступ до тих самих ресурсів (сховищ, ключів тощо), доступ до яких має
-гостьова система. Усі команди, які мають працювати у гостьовій системі
-\&\fIслід\fR запускати за допомогою \fI\-\-firstboot\fR.
-.PP
-З іншого боку, якщо вам потрібно щось скоригувати у файловій системі
-гостьової операційної системи (наприклад, копіюванням даних до файлів), тоді
-ідеально буде використатися \fI\-\-script\fR, оскільки (a) так скрипт матиме
-доступ до файлової системи основної операційної системи і (b) ви одразу
-отримаєте повідомлення про помилки.
-.PP
-Кожен з параметрів або обидва параметри можна використовувати у рядку
-команди довільну кількість разів.
+Обидва параметри, \fI\-\-firstboot\fR і \fI\-\-script\fR, запускають скрипти оболонки, яка виконують дії із гостьовою системою. Втім, ці параметри суттєво різняться.
+.PP
+\&\fI\-\-firstboot скрипт\fR вивантажує файл \f(CW\*(C`скрипт\*(C'\fR до гостьової системи і робить так, щоб він запускався у гостьовій системі під час наступного її завантаження. (Скрипт буде запущено лише один раз, при «першому завантаження».)
+.PP
+\&\fI\-\-script скрипт\fR запускає скрипт командної оболонки \f(CW\*(C`скрипт\*(C'\fR \fIу основній системі\fR, у поточному каталозі у файловій системі гостьової операційної системи.
+.PP
+Якщо вам, наприклад, потрібно виконати \f(CW\*(C`yum install\*(C'\fR для встановлення нових пакунків, вам \fIне слід\fR використовувати для цього \fI\-\-script\fR, оскільки це (а) запустить програму \f(CW\*(C`yum\*(C'\fR у основній системі і (б) не надасть програмі доступ до тих самих ресурсів (сховищ, ключів тощо), доступ до яких має гостьова система. Усі команди, які мають працювати у гостьовій системі \fIслід\fR запускати за допомогою \fI\-\-firstboot\fR.
+.PP
+З іншого боку, якщо вам потрібно щось скоригувати у файловій системі гостьової операційної системи (наприклад, копіюванням даних до файлів), тоді ідеально буде використатися \fI\-\-script\fR, оскільки (a) так скрипт матиме доступ до файлової системи основної операційної системи і (b) ви одразу отримаєте повідомлення про помилки.
+.PP
+Кожен з параметрів або обидва параметри можна використовувати у рядку команди довільну кількість разів.
.SH "БЕЗПЕКА"
.IX Header "БЕЗПЕКА"
-Хоча virt-sysprep вилучає певні конфіденційні дані з гостьової системи,
-програма не претендує на вилучення усіх цих даних. Вам слід ознайомитися із
-розділом \*(L"ДІЇ\*(R" вище і вивчити саму гостьову систему після виконання дій.
-.PP
-Файли з конфіденційними даними просто вилучаються. Дані, які у них
-містяться, можуть залишатися на диску. Такі дані доволі просто відновити за
-допомогою шістнадцяткового редактора або засобів для відновлення файлів. Ви
-можете скористатися параметром \fI\-\-scrub\fR для витирання вмісту файлів
-замість простого їх вилучення. Ще одним способом вилучити конфіденційні дані
-є використання \fBvirt\-sparsify\fR\|(1). Крім того, витерти вміст вилучених
-каталогів та inode можна за допомогою команди \fBscrub\fR\|(1).
+Хоча virt-sysprep вилучає певні конфіденційні дані з гостьової системи, програма не претендує на вилучення усіх цих даних. Вам слід ознайомитися із розділом \*(L"ДІЇ\*(R" вище і вивчити саму гостьову систему після виконання дій.
+.PP
+Файли з конфіденційними даними просто вилучаються. Дані, які у них містяться, можуть залишатися на диску. Такі дані доволі просто відновити за допомогою шістнадцяткового редактора або засобів для відновлення файлів. Ви можете скористатися параметром \fI\-\-scrub\fR для витирання вмісту файлів замість простого їх вилучення. Ще одним способом вилучити конфіденційні дані є використання \fBvirt\-sparsify\fR\|(1). Крім того, витерти вміст вилучених каталогів та inode можна за допомогою команди \fBscrub\fR\|(1).
.SS "БАЗА ВИПАДКОВОСТІ"
.IX Subsection "БАЗА ВИПАДКОВОСТІ"
\&\fI(Цей розділ стосується лише гостьових систем Linux)\fR
.PP
-У підтримуваних гостьових системах virt-sysprep записує декілька випадкових
-байтів з основної системи до файла породжувача псевдовипадкової
-послідовності гостьової системи.
+У підтримуваних гостьових системах virt-sysprep записує декілька випадкових байтів з основної системи до файла породжувача псевдовипадкової послідовності гостьової системи.
.PP
-Якщо ця процедура виконується один раз, а гостьова система клонується з того
-самого шаблона, кожна гостьова система починатиме з того самого значення
-ентропії, отже дані, подібні до ключів \s-1SSH\s0 вузла і послідовностей чисел \s-1TCP,\s0
-можуть бути передбачуваними.
+Якщо ця процедура виконується один раз, а гостьова система клонується з того самого шаблона, кожна гостьова система починатиме з того самого значення ентропії, отже дані, подібні до ключів \s-1SSH\s0 вузла і послідовностей чисел \s-1TCP,\s0 можуть бути передбачуваними.
.PP
-Тому вам слід забезпечити додавання певного рівня випадковості \fIпісля\fR
-клонування з шаблона. Зробити це можна за допомогою простого вмикання модуля
-customize:
+Тому вам слід забезпечити додавання певного рівня випадковості \fIпісля\fR клонування з шаблона. Зробити це можна за допомогою простого вмикання модуля customize:
.PP
.Vb 2
\& cp шаблон.img нова_гостьова_система.img
.Ve
.SH "SELINUX"
.IX Header "SELINUX"
-Для гостьових систем, у яких використовується SELinux, може знадобитися
-спеціальна обробка, якщо використовуються дії, які створюють нові файли або
-вносять зміни до наявних файлів.
+Для гостьових систем, у яких використовується SELinux, може знадобитися спеціальна обробка, якщо використовуються дії, які створюють нові файли або вносять зміни до наявних файлів.
.PP
Докладніший опис наведено у розділі \*(L"\s-1SELINUX\*(R"\s0 in \fBvirt\-builder\fR\|(1).
.SH "WINDOWS 8"
.IX Header "WINDOWS 8"
-«Швидкий запуск» Windows 8 може заважати роботі
-virt-sysprep. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК
-\&\s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
+«Швидкий запуск» Windows 8 може заважати роботі virt-sysprep. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК \s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "СТАН ВИХОДУ"
.IX Header "СТАН ВИХОДУ"
-Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися
-помилки.
+Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися помилки.
.SH "ЗМІННІ СЕРЕДОВИЩА"
.IX Header "ЗМІННІ СЕРЕДОВИЩА"
.ie n .IP """VIRT_TOOLS_DATA_DIR""" 4
.el .IP "\f(CWVIRT_TOOLS_DATA_DIR\fR" 4
.IX Item "VIRT_TOOLS_DATA_DIR"
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
.Sp
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-\&\fI/usr/share/virt\-tools\fR).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на \fI/usr/share/virt\-tools\fR).
.Sp
Цей каталог може містити такі файли:
.RS 4
.IP "\fIrhsrvany.exe\fR" 4
.IX Item "rhsrvany.exe"
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і
-\&\fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.Sp
Див. також \f(CW\*(C`https://github.com/rwmjones/rhsrvany\*(C'\fR
.IP "\fIpvvxsvc.exe\fR" 4
.IX Item "pvvxsvc.exe"
-Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-\&\fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із \s-1VMDP SUSE,\s0 використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри \fI\-\-firstboot\fR і \fI\-\-firstboot\-command\fR для гостьових операційних систем Windows.
.RE
.RS 4
.RE
.PP
-Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT
-VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
+Опис інших змінних середовища наведено у розділі \*(L"\s-1ENVIRONMENT VARIABLES\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1),
-\&\fBvirt\-customize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1),
-\&\fBvirt\-sparsify\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1),
-\&\fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
+\&\fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-builder\fR\|(1), \fBvirt\-clone\fR\|(1), \fBvirt\-customize\fR\|(1), \fBvirt\-rescue\fR\|(1), \fBvirt\-resize\fR\|(1), \fBvirt\-sparsify\fR\|(1), \fBvirsh\fR\|(1), \fBlvcreate\fR\|(8), \fBqemu\-img\fR\|(1), \fBscrub\fR\|(1), http://libguestfs.org/, http://libvirt.org/.
.SH "АВТОРИ"
.IX Header "АВТОРИ"
Richard W.M. Jones http://people.redhat.com/~rjones/
=head1 НАЗВА
-virt-sysprep — скидання налаштувань віртуальної машини до початкових, так,
-щоб з неї можна було роботи клони
+virt-sysprep — скидання налаштувань віртуальної машини до початкових, так, щоб з неї можна було роботи клони
=head1 КОРОТКИЙ ОПИС
=head1 ОПИС
-Virt-sysprep може відновити початковий стан або зняти налаштовування з
-віртуальної машини, щоб з неї можна було робити клони. Кроками цієї
-процедури є вилучення ключів вузла SSH, вилучення сталих налаштувань мережі
-щодо MAC та вилучення облікових записів користувачів. Крім того,
-virt-sysprep може налаштовувати віртуальну машину, наприклад, додаванням
-ключів SSH, користувачів чи логотипів. Ви можете вмикати або вимикати кожен
-з цих кроків.
-
-Virt-sysprep вносить зміни до гостьової системи або образу диска I<на
-місці>. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний
-вміст гостьової системи, I<вам слід спочатку зробити її знімок, скопіювати
-або клонувати її диск>. Див. L</КОПІЮВАННЯ І КЛОНУВАННЯ> нижче.
-
-Вам I<не потрібно> запускати virt-sysprep від імені користувача
-root. Фактично, запуск у такому режимі є нерекомендованим. Єдиною причиною
-запускати програму від імені root може бути потреба у доступі до образу
-диска, але навіть у цьому випадку, доцільніше змінити права доступу до
-образу диска так, щоб запис до нього став доступним від імені користувача,
-який запускає virt-sysprep.
-
-«Sysprep» — скорочення від «system preparation» («приготування
-системи»). Назва походить від програми Microsoft F<sysprep.exe>, яка
-використовується для вилучення налаштувань з Windows у приготуваннях до
-клонування системи. Маємо зауважити, що у поточній версії virt-sysprep I<не>
-може працювати із гостьовими системами Microsoft Windows. Ми плануємо
-впровадити підтримку приготування Windows у майбутніх версіях і вже маємо
-певні напрацювання щодо цього.
+Virt-sysprep може відновити початковий стан або зняти налаштовування з віртуальної машини, щоб з неї можна було робити клони. Кроками цієї процедури є вилучення ключів вузла SSH, вилучення сталих налаштувань мережі щодо MAC та вилучення облікових записів користувачів. Крім того, virt-sysprep може налаштовувати віртуальну машину, наприклад, додаванням ключів SSH, користувачів чи логотипів. Ви можете вмикати або вимикати кожен з цих кроків.
+
+Virt-sysprep вносить зміни до гостьової системи або образу диска I<на місці>. Гостьова система має бути вимкненою. Якщо ви хочете зберегти наявний вміст гостьової системи, I<вам слід спочатку зробити її знімок, скопіювати або клонувати її диск>. Див. L</КОПІЮВАННЯ І КЛОНУВАННЯ> нижче.
+
+Вам I<не потрібно> запускати virt-sysprep від імені користувача root. Фактично, запуск у такому режимі є нерекомендованим. Єдиною причиною запускати програму від імені root може бути потреба у доступі до образу диска, але навіть у цьому випадку, доцільніше змінити права доступу до образу диска так, щоб запис до нього став доступним від імені користувача, який запускає virt-sysprep.
+
+«Sysprep» — скорочення від «system preparation» («приготування системи»). Назва походить від програми Microsoft F<sysprep.exe>, яка використовується для вилучення налаштувань з Windows у приготуваннях до клонування системи. Маємо зауважити, що у поточній версії virt-sysprep I<не> може працювати із гостьовими системами Microsoft Windows. Ми плануємо впровадити підтримку приготування Windows у майбутніх версіях і вже маємо певні напрацювання щодо цього.
=head1 ПАРАМЕТРИ
Додати I<файл>, який має бути образом диска з віртуальної машини.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром I<--format>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format>.
=item B<-a> адреса
=item B<--add> адреса
-Додати віддалений диск. Формат адреси є сумісним із
-guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
+Додати віддалений диск. Формат адреси є сумісним із guestfish. Див. L<guestfish(1)/ДОДАВАННЯ ВІДДАЛЕНОГО СХОВИЩА>.
=item B<--colors>
=item B<--colours>
-Використовувати послідовності символів ANSI для розфарбовування
-повідомлень. Ці послідовності типово використовуються, якщо дані виводяться
-на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла,
-послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до
-команди цей параметр.
+Використовувати послідовності символів ANSI для розфарбовування повідомлень. Ці послідовності типово використовуються, якщо дані виводяться на термінал tty. Якщо дані, виведені програмою, спрямовуються до файла, послідовності визначення кольорів ANSI буде вимкнено, якщо ви не додасте до команди цей параметр.
=item B<-c> адреса
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<-n>
=item B<--dry-run>
-Виконати тестову обробку гостьової системи у режимі «лише читання». Буде
-виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
+Виконати тестову обробку гостьової системи у режимі «лише читання». Буде виконано дію sysprep, але наприкінці усі зміни до диска буде відкинуто.
=item B<--enable> дії
-Визначає дії з приготування, які слід виконати. Ви можете вказати список
-дій, відокремлених комами, ось так:
+Визначає дії з приготування, які слід виконати. Ви можете вказати список дій, відокремлених комами, ось так:
--enable ssh-hostkeys,udev-persistent-net
Тут увімкнено лише дії C<ssh-hostkeys> і C<udev-persistent-net>.
-Якщо параметр I<--enable> не вказано, типово буде виконано якомога більше
-дій з приготування системи (див. I<--list-operations>, щоб переглянути
-список увімкнених дій).
+Якщо параметр I<--enable> не вказано, типово буде виконано якомога більше дій з приготування системи (див. I<--list-operations>, щоб переглянути список увімкнених дій).
-Незалежно від вказаного параметра I<--enable>, для певних типів гостьових
-систем деякі дії пропускаються.
+Незалежно від вказаного параметра I<--enable>, для певних типів гостьових систем деякі дії пропускаються.
-Скористайтеся параметром I<--list-operations>, щоб переглянути список дій,
-підтримку яких передбачено у вашій версії virt-sysprep.
+Скористайтеся параметром I<--list-operations>, щоб переглянути список дій, підтримку яких передбачено у вашій версії virt-sysprep.
Список дій із поясненнями щодо них наведено у розділі L</ДІЇ> нижче.
=item B<--operations> дії
-Визначає дії з приготування, які слід виконати. Ви можете вказати список
-дій, відокремлених комами, ось так:
+Визначає дії з приготування, які слід виконати. Ви можете вказати список дій, відокремлених комами, ось так:
--operations ssh-hostkeys,udev-persistent-net
Тут увімкнено лише дії C<ssh-hostkeys> і C<udev-persistent-net>.
-За допомогою параметра I<--operations> ви зможете увімкнути або вимкнути
-будь-які дї, зокрема типові (ті, які виконуватимуться, якщо не вказано ні
-I<--operations>, ні I<--enable>) та усі доступні; додавання C<-> перед
-назвою дії вилучає її зі списку увімкнених дій, а метаназви C<defaults> і
-C<all> відповідають діям, які типово увімкнено і усім доступним
-діям. Приклад:
+За допомогою параметра I<--operations> ви зможете увімкнути або вимкнути будь-які дї, зокрема типові (ті, які виконуватимуться, якщо не вказано ні I<--operations>, ні I<--enable>) та усі доступні; додавання C<-> перед назвою дії вилучає її зі списку увімкнених дій, а метаназви C<defaults> і C<all> відповідають діям, які типово увімкнено і усім доступним діям. Приклад:
--operations firewall-rules,defaults,-tmp-files
-Ця команда вмикає дію C<firewall-rules> (незалежно від того, чи було її
-типово увімкнено), усі типові дії і вимикає дію C<tmp-files>.
+Ця команда вмикає дію C<firewall-rules> (незалежно від того, чи було її типово увімкнено), усі типові дії і вимикає дію C<tmp-files>.
-Параметр I<--operations> може бути вказано декілька разів; під час першого
-використання набір увімкнених дій вважається порожнім, усі наступні
-використання I<--operations> стосуватимуться уже увімкненого набору дій.
+Параметр I<--operations> може бути вказано декілька разів; під час першого використання набір увімкнених дій вважається порожнім, усі наступні використання I<--operations> стосуватимуться уже увімкненого набору дій.
-Якщо параметр I<--operations> не вказано, типово буде виконано якомога
-більше дій з приготування системи (див. I<--list-operations>, щоб
-переглянути список увімкнених дій).
+Якщо параметр I<--operations> не вказано, типово буде виконано якомога більше дій з приготування системи (див. I<--list-operations>, щоб переглянути список увімкнених дій).
-Незалежно від вказаного параметра I<--operations>, для певних типів
-гостьових систем деякі дії пропускаються.
+Незалежно від вказаного параметра I<--operations>, для певних типів гостьових систем деякі дії пропускаються.
-Скористайтеся параметром I<--list-operations>, щоб переглянути список дій,
-підтримку яких передбачено у вашій версії virt-sysprep.
+Скористайтеся параметром I<--list-operations>, щоб переглянути список дій, підтримку яких передбачено у вашій версії virt-sysprep.
Список дій із поясненнями щодо них наведено у розділі L</ДІЇ> нижче.
=item B<--echo-keys>
-Типово, якщо virt-sysprep попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-sysprep попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<--format> raw|qcow2|..
=item B<--format> auto
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format auto> перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format auto> перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-sysprep --format raw -a disk.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-sysprep --format raw -a disk.img --format auto -a another.img
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
Список дій, підтримку яких передбачено у програмі virt-sysprep.
-Дії буде показано по одній на рядок із одним або декількома полями,
-відокремленими комами. Приклад:
+Дії буде показано по одній на рядок із одним або декількома полями, відокремленими комами. Приклад:
$ virt-sysprep --list-operations
bash-history * Вилучити журнал команд bash у гостьовій системі
dhcp-server-state * Вилучити надані серверні адреси DHCP
[тощо]
-У першому полі міститься назва дії, яку можна додати до параметра
-I<--enable>. У другому полі міститься символ C<*>, якщо дію типово
-увімкнено, і пробіл, якщо дію вимкнено. Наступні поля у тому самому рядку є
-описом дії.
+У першому полі міститься назва дії, яку можна додати до параметра I<--enable>. У другому полі міститься символ C<*>, якщо дію типово увімкнено, і пробіл, якщо дію вимкнено. Наступні поля у тому самому рядку є описом дії.
-До libguestfs 1.17.33 показувалося лише перше поле (назва дії) і усі дії
-було типово увімкнено.
+До libguestfs 1.17.33 показувалося лише перше поле (назва дії) і усі дії було типово увімкнено.
=item B<--mount-options>
точка_монтування:параметри[;точка_монтування:параметри;...]
-Встановлює параметри монтування, які використовуються, коли libguestfs
-відкриває образ диска. Зауважте, що це не впливає на гостьову систему. Ці
-дані використовуються при відкритті певних гостьових систем, зокрема тих, де
-використовується файлова система UFS (BSD).
+Встановлює параметри монтування, які використовуються, коли libguestfs відкриває образ диска. Зауважте, що це не впливає на гостьову систему. Ці дані використовуються при відкритті певних гостьових систем, зокрема тих, де використовується файлова система UFS (BSD).
-Слід використовувати список відокремлених крапкою з комою пар
-C<точка_монтування:параметри>. Ймовірно, список слід взяти у лапки, щоб
-захистити його від обробки командною оболонкою.
+Слід використовувати список відокремлених крапкою з комою пар C<точка_монтування:параметри>. Ймовірно, список слід взяти у лапки, щоб захистити його від обробки командною оболонкою.
Приклад:
Не виводити повідомлення до журналу.
-Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся
-I<-x>.
+Для вмикання ведення докладного журналу окремих дій з файлами скористайтеся I<-x>.
=item B<--network>
=item B<--no-network>
-Увімкнути чи вимкнути доступ до мережі для гостьової системи під час
-встановлення.
+Увімкнути чи вимкнути доступ до мережі для гостьової системи під час встановлення.
-У virt-sysprep роботу у мережі типово I<вимкнено>. Вам слід скористатися
-параметром I<--network>, щоб увімкнути її та мати змогу скористатися
-параметрами, подібними до I<--install> або I<--update>.
+У virt-sysprep роботу у мережі типово I<вимкнено>. Вам слід скористатися параметром I<--network>, щоб увімкнути її та мати змогу скористатися параметрами, подібними до I<--install> або I<--update>.
-На сторінці підручника L<virt-builder(1)> можна знайти додаткові дані щодо
-переваг у захисті від вимикання мережі.
+На сторінці підручника L<virt-builder(1)> можна знайти додаткові дані щодо переваг у захисті від вимикання мережі.
=item B<-v>
Показати дані щодо версії і завершити роботу.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default when the output is a tty. If the output of the program is redirected to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Увімкнути трасування викликів програмного інтерфейсу libguestfs.
=head1 ДІЇ
-Якщо параметр I<--enable>/I<--operations> I<не> вказано, більшу частину дій
-з приготування системи буде увімкнено.
+Якщо параметр I<--enable>/I<--operations> I<не> вказано, більшу частину дій з приготування системи буде увімкнено.
-Скористайтеся командою C<virt-sysprep --list-operations>, щоб переглянути
-список усіх дій, які передбачено у вашому виконуваному файлі
-virt-sysprep. Дії, які типово увімкнено, буде позначено у списку символом
-C<*>. Незалежно від вказаних параметрів I<--enable>/I<--operations> для
-певних типів гостьових систем деякі з дій з приготування системи
-пропускатимуться.
+Скористайтеся командою C<virt-sysprep --list-operations>, щоб переглянути список усіх дій, які передбачено у вашому виконуваному файлі virt-sysprep. Дії, які типово увімкнено, буде позначено у списку символом C<*>. Незалежно від вказаних параметрів I<--enable>/I<--operations> для певних типів гостьових систем деякі з дій з приготування системи пропускатимуться.
-Окремі дії можна увімкнути за допомогою параметрів
-I<--enable>/I<--operations>. Записи дій у списку слід відокремлювати
-комами. Приклад:
+Окремі дії можна увімкнути за допомогою параметрів I<--enable>/I<--operations>. Записи дій у списку слід відокремлювати комами. Приклад:
virt-sysprep --operations ssh-hostkeys,udev-persistent-net [тощо..]
-У майбутніх версіях virt-sysprep може бути додано інші дії. Якщо ви
-використовуєте virt-sysprep, і вам потрібна передбачувана поведінка,
-вказуйте лише ті дії, які ви хочете увімкнути.
+У майбутніх версіях virt-sysprep може бути додано інші дії. Якщо ви використовуєте virt-sysprep, і вам потрібна передбачувана поведінка, вказуйте лише ті дії, які ви хочете увімкнути.
-C<*> = типово увімкнено, якщо не вказано параметрів
-I<--enable>/I<--operations>.
+C<*> = типово увімкнено, якщо не вказано параметрів I<--enable>/I<--operations>.
__OPERATIONS__
=head1 КОПІЮВАННЯ ТА КЛОНУВАННЯ
-Virt-sysprep можна скористатися як частиною процедури клонування гостьових
-систем або приготування шаблона, з якого можна буде клонувати гостьові
-системи. Існує багато різних способів досягти цього за допомогою засобів
-віртуалізації, — цей розділ є лише вступом.
+Virt-sysprep можна скористатися як частиною процедури клонування гостьових систем або приготування шаблона, з якого можна буде клонувати гостьові системи. Існує багато різних способів досягти цього за допомогою засобів віртуалізації, — цей розділ є лише вступом.
Віртуальна машина (коли її вимкнено) складається з двох частин:
=item I<налаштування>
-Налаштування або опис гостьової системи. Приклади: XML libvirt (див. C<virsh
-dumpxml>), поточні налаштування гостьової системи або інший зовнішній
-формат, наприклад OVF.
+Налаштування або опис гостьової системи. Приклади: XML libvirt (див. C<virsh dumpxml>), поточні налаштування гостьової системи або інший зовнішній формат, наприклад OVF.
Деякі пункти налаштувань, які варто було б змінити:
=item I<блокові пристрої>
-Один або декілька образів дисків, які самі містять файли, каталоги,
-програми, ядра, налаштування тощо.
+Один або декілька образів дисків, які самі містять файли, каталоги, програми, ядра, налаштування тощо.
-Ось деякі параметри всередині блокових пристроїв, які, можливо, доведеться
-змінити:
+Ось деякі параметри всередині блокових пристроїв, які, можливо, доведеться змінити:
=over 4
=head2 КОПІЮВАННЯ БЛОКОВОГО ПРИСТРОЮ
-Маючи початкову гостьову систему, ви, ймовірно, хочете скопіювати блоковий
-пристрій гостьової системи і його налаштування, щоб створити шаблон. Далі,
-коли вас задовольнятимуть характеристики шаблона, ви захочете створити на
-його основі клони.
+Маючи початкову гостьову систему, ви, ймовірно, хочете скопіювати блоковий пристрій гостьової системи і його налаштування, щоб створити шаблон. Далі, коли вас задовольнятимуть характеристики шаблона, ви захочете створити на його основі клони.
virt-sysprep
|
\-----> гостьові системи
\---->
-Ви, звичайно ж, можете просто скопіювати блоковий пристрій на основну
-систему за допомогою L<cp(1)> або L<dd(1)>.
+Ви, звичайно ж, можете просто скопіювати блоковий пристрій на основну систему за допомогою L<cp(1)> або L<dd(1)>.
dd dd
початкова система --------> шаблон ---------->
\-----> гостьові системи
\---->
-Ймовірно, virt-sysprep доведеться запустити двічі — один раз для відновлення
-початкового стану гостьової системи (для створення шаблона) і другий раз для
-налаштовування гостьової системи для певного користувача:
+Ймовірно, virt-sysprep доведеться запустити двічі — один раз для відновлення початкового стану гостьової системи (для створення шаблона) і другий раз для налаштовування гостьової системи для певного користувача:
virt-sysprep virt-sysprep
(скидання) (додавання користувача, ключів, логотипів)
qemu-img create -f qcow2 -o backing_file=original snapshot.qcow
-Перевагою є те, що вам не потрібно буде копіювати оригінал (дуже швидко), і
-те, що зберігатимуться лише зміни (менше вживання місця у сховищі даних).
+Перевагою є те, що вам не потрібно буде копіювати оригінал (дуже швидко), і те, що зберігатимуться лише зміни (менше вживання місця у сховищі даних).
-Зауважте, що запис резервного файла після створення на його основі гостьових
-систем неможливий: такий запис призведе до пошкодження гостьових систем.
+Зауважте, що запис резервного файла після створення на його основі гостьових систем неможливий: такий запис призведе до пошкодження гостьових систем.
=item *
=item *
-До інших способів створення знімків належить використання засобів файлової
-системи (для файлових систем, які подібні до btrfs).
+До інших способів створення знімків належить використання засобів файлової системи (для файлових систем, які подібні до btrfs).
-На більшості пристроїв Network Attached Storage (NAS) передбачено можливість
-простого створення знімків на основі файлів та LUN.
+На більшості пристроїв Network Attached Storage (NAS) передбачено можливість простого створення знімків на основі файлів та LUN.
=item *
-Накажіть вашому NAS здублювати LUN. На більшості пристроїв NAS також
-передбачено дуже просте дублювання LUN (копіювання відбувається у фоновому
-режимі за запитом).
+Накажіть вашому NAS здублювати LUN. На більшості пристроїв NAS також передбачено дуже просте дублювання LUN (копіювання відбувається у фоновому режимі за запитом).
=item *
=head2 VIRT-CLONE
-Для дублювання блокового пристрою і/або внесення змін до зовнішніх
-налаштувань libvirt гостьової системи можна скористатися окремим
-інструментом, L<virt-clone(1)>. Ця програма відновить початкові значення
-назви, UUID та адреси MAC гостьової системи в XML libvirt.
+Для дублювання блокового пристрою і/або внесення змін до зовнішніх налаштувань libvirt гостьової системи можна скористатися окремим інструментом, L<virt-clone(1)>. Ця програма відновить початкові значення назви, UUID та адреси MAC гостьової системи в XML libvirt.
-L<virt-clone(1)> не використовує libguestfs і не може «зазирнути» у образ
-диска. Це і було причиною для написання virt-sysprep.
+L<virt-clone(1)> не використовує libguestfs і не може «зазирнути» у образ диска. Це і було причиною для написання virt-sysprep.
=head2 РОЗРІДЖЕННЯ
virt-sparsify
початкова система --------> шаблон
-L<virt-sparsify(1)> можна скористатися для зменшення розмірів шаблона для
-клонування, спрощуючи стискання і/або пришвидшуючи копіювання.
+L<virt-sparsify(1)> можна скористатися для зменшення розмірів шаблона для клонування, спрощуючи стискання і/або пришвидшуючи копіювання.
-Зауважте, що оскільки virt-sparsify також копіює образ, ви можете
-скористатися цією програмою для створення початкової копії (замість C<dd>).
+Зауважте, що оскільки virt-sparsify також копіює образ, ви можете скористатися цією програмою для створення початкової копії (замість C<dd>).
=head2 ЗМІНА РОЗМІРІВ
\-----> гостьові системи
\---->
-Якщо ви хочете надати комусь клоновані гостьові системи, але хочете надати
-можливість вибирати розмір гостьової системи (наприклад за місцем, яке
-надається гостьовій системі на диску), замість копіювання шаблона вам слід
-запустити L<virt-resize(1)>. Virt-resize виконує копіювання і зміну
-розмірів, тому програма є ідеальною для клонування гостьових систем з
-шаблона.
+Якщо ви хочете надати комусь клоновані гостьові системи, але хочете надати можливість вибирати розмір гостьової системи (наприклад за місцем, яке надається гостьовій системі на диску), замість копіювання шаблона вам слід запустити L<virt-resize(1)>. Virt-resize виконує копіювання і зміну розмірів, тому програма є ідеальною для клонування гостьових систем з шаблона.
=head1 FIRSTBOOT ЧИ SCRIPT
-Обидва параметри, I<--firstboot> і I<--script>, запускають скрипти оболонки,
-яка виконують дії із гостьовою системою. Втім, ці параметри суттєво
-різняться.
+Обидва параметри, I<--firstboot> і I<--script>, запускають скрипти оболонки, яка виконують дії із гостьовою системою. Втім, ці параметри суттєво різняться.
-I<--firstboot скрипт> вивантажує файл C<скрипт> до гостьової системи і
-робить так, щоб він запускався у гостьовій системі під час наступного її
-завантаження. (Скрипт буде запущено лише один раз, при «першому
-завантаження».)
+I<--firstboot скрипт> вивантажує файл C<скрипт> до гостьової системи і робить так, щоб він запускався у гостьовій системі під час наступного її завантаження. (Скрипт буде запущено лише один раз, при «першому завантаження».)
-I<--script скрипт> запускає скрипт командної оболонки C<скрипт> I<у основній
-системі>, у поточному каталозі у файловій системі гостьової операційної
-системи.
+I<--script скрипт> запускає скрипт командної оболонки C<скрипт> I<у основній системі>, у поточному каталозі у файловій системі гостьової операційної системи.
-Якщо вам, наприклад, потрібно виконати C<yum install> для встановлення нових
-пакунків, вам I<не слід> використовувати для цього I<--script>, оскільки це
-(а) запустить програму C<yum> у основній системі і (б) не надасть програмі
-доступ до тих самих ресурсів (сховищ, ключів тощо), доступ до яких має
-гостьова система. Усі команди, які мають працювати у гостьовій системі
-I<слід> запускати за допомогою I<--firstboot>.
+Якщо вам, наприклад, потрібно виконати C<yum install> для встановлення нових пакунків, вам I<не слід> використовувати для цього I<--script>, оскільки це (а) запустить програму C<yum> у основній системі і (б) не надасть програмі доступ до тих самих ресурсів (сховищ, ключів тощо), доступ до яких має гостьова система. Усі команди, які мають працювати у гостьовій системі I<слід> запускати за допомогою I<--firstboot>.
-З іншого боку, якщо вам потрібно щось скоригувати у файловій системі
-гостьової операційної системи (наприклад, копіюванням даних до файлів), тоді
-ідеально буде використатися I<--script>, оскільки (a) так скрипт матиме
-доступ до файлової системи основної операційної системи і (b) ви одразу
-отримаєте повідомлення про помилки.
+З іншого боку, якщо вам потрібно щось скоригувати у файловій системі гостьової операційної системи (наприклад, копіюванням даних до файлів), тоді ідеально буде використатися I<--script>, оскільки (a) так скрипт матиме доступ до файлової системи основної операційної системи і (b) ви одразу отримаєте повідомлення про помилки.
-Кожен з параметрів або обидва параметри можна використовувати у рядку
-команди довільну кількість разів.
+Кожен з параметрів або обидва параметри можна використовувати у рядку команди довільну кількість разів.
=head1 БЕЗПЕКА
-Хоча virt-sysprep вилучає певні конфіденційні дані з гостьової системи,
-програма не претендує на вилучення усіх цих даних. Вам слід ознайомитися із
-розділом L</ДІЇ> вище і вивчити саму гостьову систему після виконання дій.
+Хоча virt-sysprep вилучає певні конфіденційні дані з гостьової системи, програма не претендує на вилучення усіх цих даних. Вам слід ознайомитися із розділом L</ДІЇ> вище і вивчити саму гостьову систему після виконання дій.
-Файли з конфіденційними даними просто вилучаються. Дані, які у них
-містяться, можуть залишатися на диску. Такі дані доволі просто відновити за
-допомогою шістнадцяткового редактора або засобів для відновлення файлів. Ви
-можете скористатися параметром I<--scrub> для витирання вмісту файлів
-замість простого їх вилучення. Ще одним способом вилучити конфіденційні дані
-є використання L<virt-sparsify(1)>. Крім того, витерти вміст вилучених
-каталогів та inode можна за допомогою команди L<scrub(1)>.
+Файли з конфіденційними даними просто вилучаються. Дані, які у них містяться, можуть залишатися на диску. Такі дані доволі просто відновити за допомогою шістнадцяткового редактора або засобів для відновлення файлів. Ви можете скористатися параметром I<--scrub> для витирання вмісту файлів замість простого їх вилучення. Ще одним способом вилучити конфіденційні дані є використання L<virt-sparsify(1)>. Крім того, витерти вміст вилучених каталогів та inode можна за допомогою команди L<scrub(1)>.
=head2 БАЗА ВИПАДКОВОСТІ
I<(Цей розділ стосується лише гостьових систем Linux)>
-У підтримуваних гостьових системах virt-sysprep записує декілька випадкових
-байтів з основної системи до файла породжувача псевдовипадкової
-послідовності гостьової системи.
+У підтримуваних гостьових системах virt-sysprep записує декілька випадкових байтів з основної системи до файла породжувача псевдовипадкової послідовності гостьової системи.
-Якщо ця процедура виконується один раз, а гостьова система клонується з того
-самого шаблона, кожна гостьова система починатиме з того самого значення
-ентропії, отже дані, подібні до ключів SSH вузла і послідовностей чисел TCP,
-можуть бути передбачуваними.
+Якщо ця процедура виконується один раз, а гостьова система клонується з того самого шаблона, кожна гостьова система починатиме з того самого значення ентропії, отже дані, подібні до ключів SSH вузла і послідовностей чисел TCP, можуть бути передбачуваними.
-Тому вам слід забезпечити додавання певного рівня випадковості I<після>
-клонування з шаблона. Зробити це можна за допомогою простого вмикання модуля
-customize:
+Тому вам слід забезпечити додавання певного рівня випадковості I<після> клонування з шаблона. Зробити це можна за допомогою простого вмикання модуля customize:
cp шаблон.img нова_гостьова_система.img
virt-sysprep --enable customize -a нова_гостьова_система.img
=head1 SELINUX
-Для гостьових систем, у яких використовується SELinux, може знадобитися
-спеціальна обробка, якщо використовуються дії, які створюють нові файли або
-вносять зміни до наявних файлів.
+Для гостьових систем, у яких використовується SELinux, може знадобитися спеціальна обробка, якщо використовуються дії, які створюють нові файли або вносять зміни до наявних файлів.
Докладніший опис наведено у розділі L<virt-builder(1)/SELINUX>.
=head1 WINDOWS 8
-«Швидкий запуск» Windows 8 може заважати роботі
-virt-sysprep. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК
-WINDOWS 8>.
+«Швидкий запуск» Windows 8 може заважати роботі virt-sysprep. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК WINDOWS 8>.
=head1 СТАН ВИХОДУ
-Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися
-помилки.
+Ця програма повертає 0, якщо роботу виконано успішно, і 1, якщо сталися помилки.
=head1 ЗМІННІ СЕРЕДОВИЩА
=item C<VIRT_TOOLS_DATA_DIR>
-Ця змінна визначає каталог, у якому містяться файли даних, які
-використовуються для встановлення Windows з першим завантаженням.
+Ця змінна визначає каталог, у якому містяться файли даних, які використовуються для встановлення Windows з першим завантаженням.
-Зазвичай, потреби у встановленні власного значення немає. Якщо значення не
-встановлено, буде використано вбудоване типове значення (щось схоже на
-F</usr/share/virt-tools>).
+Зазвичай, потреби у встановленні власного значення немає. Якщо значення не встановлено, буде використано вбудоване типове значення (щось схоже на F</usr/share/virt-tools>).
Цей каталог може містити такі файли:
=item F<rhsrvany.exe>
-Це виконуваний файл для Windows RHSrvAny, який використовується для
-встановлення скрипту «firstboot» у гостьові системи Windows. Він
-знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і
-I<--firstboot-command> для гостьових операційних систем Windows.
+Це виконуваний файл для Windows RHSrvAny, який використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
Див. також C<https://github.com/rwmjones/rhsrvany>
=item F<pvvxsvc.exe>
-Це виконуваний файл Windows, що постачається разом із VMDP SUSE,
-використовується для встановлення скрипту «firstboot» у гостьові системи
-Windows. Він знадобиться, якщо ви маєте намір використовувати параметри
-I<--firstboot> і I<--firstboot-command> для гостьових операційних систем
-Windows.
+Це виконуваний файл Windows, що постачається разом із VMDP SUSE, використовується для встановлення скрипту «firstboot» у гостьові системи Windows. Він знадобиться, якщо ви маєте намір використовувати параметри I<--firstboot> і I<--firstboot-command> для гостьових операційних систем Windows.
=back
=back
-Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT
-VARIABLES>.
+Опис інших змінних середовища наведено у розділі L<guestfs(3)/ENVIRONMENT VARIABLES>.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>,
-L<virt-customize(1)>, L<virt-rescue(1)>, L<virt-resize(1)>,
-L<virt-sparsify(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>,
-L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-builder(1)>, L<virt-clone(1)>, L<virt-customize(1)>, L<virt-rescue(1)>, L<virt-resize(1)>, L<virt-sparsify(1)>, L<virsh(1)>, L<lvcreate(8)>, L<qemu-img(1)>, L<scrub(1)>, L<http://libguestfs.org/>, L<http://libvirt.org/>.
=head1 АВТОРИ
=head1 ОПИС
-C<virt-tail> — інструмент командного рядка для стеження (за кінцем) вмісту
-файла C<файл>, де C<файл> існує у іменованій віртуальній машині (або образі
-диска). Дія інструмента подібна до звичайної команди S<C<tail -f>>.
+C<virt-tail> — інструмент командного рядка для стеження (за кінцем) вмісту файла C<файл>, де C<файл> існує у іменованій віртуальній машині (або образі диска). Дія інструмента подібна до звичайної команди S<C<tail -f>>.
-Можна вказати декілька назв файлів. У такому випадку кожна з назв
-оброблятиметься окремо. Усі назви файлів має бути вказано повністю зі
-шляхом, який має починатися з кореневого каталогу (тобто з «/»).
+Можна вказати декілька назв файлів. У такому випадку кожна з назв оброблятиметься окремо. Усі назви файлів має бути вказано повністю зі шляхом, який має починатися з кореневого каталогу (тобто з «/»).
Команда виконуватиметься, аж доки:
=item *
-Жодного з наведених у списку файлів не знайдено у гостьовій системі або усі
-ці файли вилучено.
+Жодного з наведених у списку файлів не знайдено у гостьовій системі або усі ці файли вилучено.
=item *
=item B<--add> файл
-Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у
-віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за
-допомогою окремих записів параметра I<-a>.
+Додати I<файл>, який має бути образом диска з віртуальної машини. Якщо у віртуальній машині декілька блокових пристроїв, вам слід вказати їх усі за допомогою окремих записів параметра I<-a>.
-Формат образу диска визначається автоматично. Щоб перевизначити його і
-примусово використати певний формат, скористайтеся параметром
-I<--format=..>.
+Формат образу диска визначається автоматично. Щоб перевизначити його і примусово використати певний формат, скористайтеся параметром I<--format=..>.
=item B<-a адреса>
=item B<--connect> адреса
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>),
-libvirt не буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо (I<-a>), libvirt не буде використовуватися взагалі.
=item B<-d> гість
=item B<--domain> гість
-Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна
-використовувати замість назв.
+Додати всі диски з вказаної гостьової системи libvirt. UUID доменів можна використовувати замість назв.
=item B<--echo-keys>
-Типово, якщо virt-tail попросить вас ввести ключ або пароль, програма не
-відтворюватиме введені символи на екрані. Якщо ви не боїтеся
-TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете
-скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
+Типово, якщо virt-tail попросить вас ввести ключ або пароль, програма не відтворюватиме введені символи на екрані. Якщо ви не боїтеся TEMPEST-нападів, або у вашій кімнаті нікого, окрім вас, немає, ви можете скористатися цим прапорцем, щоб бачити, які саме символи ви вводите.
=item B<-f>
=item B<--follow>
-Цей параметр буде проігноровано. virt-tail завжди поводиться як S<L<tail(1)>
-I<-f>>. Потреби у явному додаванні параметра I<-f> немає.
+Цей параметр буде проігноровано. virt-tail завжди поводиться як S<L<tail(1)> I<-f>>. Потреби у явному додаванні параметра I<-f> немає.
=item B<--format=raw|qcow2|..>
=item B<--format>
-Типовим значенням для параметра I<-a> є автоматичне визначення формату
-образу диска. Використання цього параметра примусово визначає значення
-параметрів I<-a> формату диска у наступному рядку команди. Використання
-параметра I<--format> без аргументу перемикає програму у режим автоматичного
-визначення у наступних параметрах I<-a>.
+Типовим значенням для параметра I<-a> є автоматичне визначення формату образу диска. Використання цього параметра примусово визначає значення параметрів I<-a> формату диска у наступному рядку команди. Використання параметра I<--format> без аргументу перемикає програму у режим автоматичного визначення у наступних параметрах I<-a>.
Приклад:
virt-tail --format=raw -a диск.img файл
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<disk.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<disk.img>.
virt-tail --format=raw -a диск.img --format -a щедиск.img файл
-примусове встановлення формату без обробки (без автоматичного визначення)
-для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
+примусове встановлення формату без обробки (без автоматичного визначення) для F<diskimg> і повернення до автоматичного визначення для F<another.img>.
-Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому
-форматі, вам слід скористатися цим параметром для визначення формату
-диска. Таким чином можна уникнути можливих проблем з захистом для
-сформованих зловмисниками гостьових систем (CVE-2010-3851).
+Якщо ви користуєтеся ненадійними образами гостьових систем у необробленому форматі, вам слід скористатися цим параметром для визначення формату диска. Таким чином можна уникнути можливих проблем з захистом для сформованих зловмисниками гостьових систем (CVE-2010-3851).
__INCLUDE:key-option.pod__
Якщо точку монтування не вказано, типовим значенням є F</>.
-Визначення точки монтування вимикає інспектування гостьової системи і
-призводить до монтування її кореневої системи та усіх її точок
-монтування. Тому вам слід забезпечити монтування усіх точок монтування,
-потрібних для роботи із файлами, назви яких вказано як аргументи.
-
-Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви
-можете або запустити guestfish без цього параметра і ознайомитися зі списком
-доступних розділів, файлових систем та логічних томів (див. команди
-L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися
-програмою L<virt-filesystems(1)>.
-
-Третьою (і нечасто використовуваною) частиною параметра монтування є список
-параметрів монтування, які використовуються для того, щоб змонтувати
-підлеглу файлову систему. Якщо такий список не буде задано, параметрами
-монтування вважатиметься або порожній рядок, або C<ro> (другий варіант
-використовується, якщо використано прапорець I<--ro>). Заданням параметрів
-монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком,
-коли вам може знадобитися це, є випадок вмикання списків керування доступом
-(ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню
-підтримку:
+Визначення точки монтування вимикає інспектування гостьової системи і призводить до монтування її кореневої системи та усіх її точок монтування. Тому вам слід забезпечити монтування усіх точок монтування, потрібних для роботи із файлами, назви яких вказано як аргументи.
+
+Якщо ви не знаєте, які саме файлові системи містяться у образі диска, ви можете або запустити guestfish без цього параметра і ознайомитися зі списком доступних розділів, файлових систем та логічних томів (див. команди L</list-partitions>, L</list-filesystems> і L</lvs>), або скористатися програмою L<virt-filesystems(1)>.
+
+Третьою (і нечасто використовуваною) частиною параметра монтування є список параметрів монтування, які використовуються для того, щоб змонтувати підлеглу файлову систему. Якщо такий список не буде задано, параметрами монтування вважатиметься або порожній рядок, або C<ro> (другий варіант використовується, якщо використано прапорець I<--ro>). Заданням параметрів монтування ви перевизначаєте типовий варіант. Ймовірно, єдиним випадком, коли вам може знадобитися це, є випадок вмикання списків керування доступом (ACL) і/або розширених атрибутів, якщо у файловій системі передбачено їхню підтримку:
-m /dev/sda1:/:acl,user_xattr
-Використання цього прапорця є еквівалентним до використання команди
-C<mount-options>.
+Використання цього прапорця є еквівалентним до використання команди C<mount-options>.
-Четвертою частиною параметра є назва драйвера файлової системи, якою слід
-скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини
-параметра рідко виникає потреба, але вона може бути корисною, якщо для
-файлової системи можна скористатися декількома драйверами (приклад: C<ext2>
-і C<ext3>), або libguestfs визначає файлову систему помилково.
+Четвертою частиною параметра є назва драйвера файлової системи, якою слід скористатися, зокрема C<ext3> або C<ntfs>. У визначенні цієї частини параметра рідко виникає потреба, але вона може бути корисною, якщо для файлової системи можна скористатися декількома драйверами (приклад: C<ext2> і C<ext3>), або libguestfs визначає файлову систему помилково.
=item B<-v>
=head1 ФАЙЛИ ЖУРНАЛІВ
-Щоб отримати список файлів журналів у гостьових системах, скористайтеся
-відповідним інструментом — L<virt-log(1)>. Ця програма може обробляти
-журнали у двійкових форматах, зокрема журнал systemd.
+Щоб отримати список файлів журналів у гостьових системах, скористайтеся відповідним інструментом — L<virt-log(1)>. Ця програма може обробляти журнали у двійкових форматах, зокрема журнал systemd.
=head1 ШЛЯХИ У WINDOWS
-У C<virt-tail> передбачено обмежені можливості щодо обробки літерних дисків
-та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
+У C<virt-tail> передбачено обмежені можливості щодо обробки літерних дисків та шляхів у Windows (наприклад F<E:\foo\bar.txt>).
Тоді і лише тоді, коли у гостьовій системі працює Windows:
=item *
-Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових
-систем на основі даних з регістру Windows.
+Літери дисків, наприклад C<C:>, замінюються на адреси відповідних файлових систем на основі даних з регістру Windows.
=item *
-Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами
-звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
+Усі символи зворотної похилої риски (C<\>) у шляху замінюються символами звичайної похилої риски так, щоб libguestfs змогла обробити адресу.
=item *
-Шлях до файла, вміст якого має бути показано, визначається без врахування
-регістру символів у його записі.
+Шлях до файла, вміст якого має бути показано, визначається без врахування регістру символів у його записі.
=back
=item *
-Перехід за деякими символічними посиланнями NTFS може здійснюватися з
-помилками.
+Перехід за деякими символічними посиланнями NTFS може здійснюватися з помилками.
=item *
-Точки з'єднання NTFS, які виходять за межі однією файлової системи
-використовувати не можна.
+Точки з'єднання NTFS, які виходять за межі однією файлової системи використовувати не можна.
=back
=head1 СТАН ВИХОДУ
-Ця програма повертає значення 0 у разі успішного завершення і ненульове
-значення, якщо сталася помилка.
+Ця програма повертає значення 0 у разі успішного завершення і ненульове значення, якщо сталася помилка.
=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-cat(1)>,
-L<virt-log(1)>, L<virt-tar-out(1)>, L<tail(1)>, L<http://libguestfs.org/>.
+L<guestfs(3)>, L<guestfish(1)>, L<virt-copy-out(1)>, L<virt-cat(1)>, L<virt-log(1)>, L<virt-tar-out(1)>, L<tail(1)>, L<http://libguestfs.org/>.
=head1 АВТОР
-.\" Automatically generated by Podwrapper::Man 1.46.1 (Pod::Simple 3.42)
+.\" Automatically generated by Podwrapper::Man 1.48.0 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "virt-win-reg 1"
-.TH virt-win-reg 1 "2021-05-08" "guestfs-tools-1.46.1" "Virtualization Support"
+.TH virt-win-reg 1 "2022-03-12" "guestfs-tools-1.48.0" "Virtualization Support"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "НАЗВА"
.IX Header "НАЗВА"
-virt-win-reg — програма для експортування та дописування записів реєстру
-Windows з гостьової системи Windows
+virt-win-reg — програма для експортування та дописування записів реєстру Windows з гостьової системи Windows
.SH "КОРОТКИЙ ОПИС"
.IX Header "КОРОТКИЙ ОПИС"
.Vb 1
.Ve
.SH "ПОПЕРЕДЖЕННЯ"
.IX Header "ПОПЕРЕДЖЕННЯ"
-\&\fIНе\fR використовуйте \f(CW\*(C`virt\-win\-reg\*(C'\fR з параметром \fI\-\-merge\fR для активних
-віртуальних машин. Якщо ви зробите це, ви \fIневиправно\fR ушкодите диск у
-віртуальній машині. \f(CW\*(C`virt\-win\-reg\*(C'\fR намагатиметься запобігти подібним діям,
-але програма не завжди може визначити усі можливі випадки.
-.PP
-Внесення змін до реєстру Windows є ризикованою дією. Формат реєстру доволі
-неясний і недокументований, а зміни у реєстрі можуть призвести до
-неможливості завантажити систему. Тому, якщо ви користуєтеся параметром
-\&\fI\-\-merge\fR, не забувайте спочатку створити надійну резервну копію.
+\&\fIНе\fR використовуйте \f(CW\*(C`virt\-win\-reg\*(C'\fR з параметром \fI\-\-merge\fR для активних віртуальних машин. Якщо ви зробите це, ви \fIневиправно\fR ушкодите диск у віртуальній машині. \f(CW\*(C`virt\-win\-reg\*(C'\fR намагатиметься запобігти подібним діям, але програма не завжди може визначити усі можливі випадки.
+.PP
+Внесення змін до реєстру Windows є ризикованою дією. Формат реєстру доволі неясний і недокументований, а зміни у реєстрі можуть призвести до неможливості завантажити систему. Тому, якщо ви користуєтеся параметром \fI\-\-merge\fR, не забувайте спочатку створити надійну резервну копію.
.SH "ОПИС"
.IX Header "ОПИС"
-Ця програма може експортувати і дописувати записи реєстру Windows з
-гостьової системи Windows.
+Ця програма може експортувати і дописувати записи реєстру Windows з гостьової системи Windows.
.PP
-Першим параметром є назва гостьової системи libvirt або простого (raw)
-образу гостьової системи Windows.
+Першим параметром є назва гостьової системи libvirt або простого (raw) образу гостьової системи Windows.
.PP
-Якщо \fIне\fR вказано параметр \fI\-\-merge\fR, вибраний ключ реєстру буде показано
-або експортовано (рекурсивно). Приклад:
+Якщо \fIне\fR вказано параметр \fI\-\-merge\fR, вибраний ключ реєстру буде показано або експортовано (рекурсивно). Приклад:
.PP
.Vb 1
\& $ virt\-win\-reg Windows7 \*(AqHKEY_LOCAL_MACHINE\eSOFTWARE\eMicrosoft\*(Aq
\& Windows 7 Enterprise
.Ve
.PP
-За допомогою \fI\-\-merge\fR ви можете дописати текстовий файл regedit до реєстру
-Windows:
+За допомогою \fI\-\-merge\fR ви можете дописати текстовий файл regedit до реєстру Windows:
.PP
.Vb 1
\& $ virt\-win\-reg \-\-merge Windows7 changes.reg
.Ve
.SS "ПРИМІТКА"
.IX Subsection "ПРИМІТКА"
-Цю програму призначено лише для спрощення доступу до реєстру. Якщо вам
-потрібні якісь складні дії з реєстром, рекомендуємо вам отримати файли роїв
-реєстру з гостьової системи за допомогою \fBlibguestfs\fR\|(3) або
-\&\fBguestfish\fR\|(1) і обробити їх локально, наприклад за допомогою \fBhivex\fR\|(3),
-\&\fBhivexsh\fR\|(1) або \fBhivexregedit\fR\|(1).
+Цю програму призначено лише для спрощення доступу до реєстру. Якщо вам потрібні якісь складні дії з реєстром, рекомендуємо вам отримати файли роїв реєстру з гостьової системи за допомогою \fBlibguestfs\fR\|(3) або \fBguestfish\fR\|(1) і обробити їх локально, наприклад за допомогою \fBhivex\fR\|(3), \fBhivexsh\fR\|(1) або \fBhivexregedit\fR\|(1).
.SH "ПАРАМЕТРИ"
.IX Header "ПАРАМЕТРИ"
.IP "\fB\-\-help\fR" 4
.IP "\fB\-\-connect адреса\fR" 4
.IX Item "--connect адреса"
.PD
-Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+Якщо використовується libvirt, встановити з’єднання з вказаним \fI\s-1URI\s0\fR. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
.Sp
-Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не
-буде використовуватися взагалі.
+Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не буде використовуватися взагалі.
.IP "\fB\-\-format\fR raw" 4
.IX Item "--format raw"
-Визначає формат образу диска, назву якого вказано у рядку команди. Якщо
-формат не вказано, його буде визначено автоматично на основі вмісту образу
-диска.
+Визначає формат образу диска, назву якого вказано у рядку команди. Якщо формат не вказано, його буде визначено автоматично на основі вмісту образу диска.
.Sp
-Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних
-до libvirt. У цьому випадку вказане значення параметра формату буде
-проігноровано.
+Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних до libvirt. У цьому випадку вказане значення параметра формату буде проігноровано.
.Sp
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
.IP "\fB\-\-merge\fR" 4
.IX Item "--merge"
-У режимі об'єднання програма дописує текстовий файл regedit до реєстру
-Windows віртуальної машини. Якщо цей параметр \fIне\fR вказано, virt-win-reg
-показує або експортує записи реєстру.
+У режимі об'єднання програма дописує текстовий файл regedit до реєстру Windows віртуальної машини. Якщо цей параметр \fIне\fR вказано, virt-win-reg показує або експортує записи реєстру.
.Sp
-Зауважте, що \fI\-\-merge\fR \fIне безпечно\fR використовувати для активних
-віртуальних машин. Використання цього параметра команди для активних
-віртуальних машин призводить до пошкодження вмісту диска. Втім,
-експортування (виконання команди без цього параметра) є завжди безпечним.
+Зауважте, що \fI\-\-merge\fR \fIне безпечно\fR використовувати для активних віртуальних машин. Використання цього параметра команди для активних віртуальних машин призводить до пошкодження вмісту диска. Втім, експортування (виконання команди без цього параметра) є завжди безпечним.
.IP "\fB\-\-encoding\fR UTF\-16LE|ASCII" 4
.IX Item "--encoding UTF-16LE|ASCII"
-При об'єднанні (і лише при ньому) у вас може виникнути потреба у визначення
-кодування рядків, які використовуються у файлі рою. Докладніший опис можна
-знайти у розділі \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3).
+При об'єднанні (і лише при ньому) у вас може виникнути потреба у визначення кодування рядків, які використовуються у файлі рою. Докладніший опис можна знайти у розділі \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3).
.Sp
-Типово буде використано кодування \s-1UTF\-16LE,\s0 яке має працювати у свіжих
-версіях Windows.
+Типово буде використано кодування \s-1UTF\-16LE,\s0 яке має працювати у свіжих версіях Windows.
.IP "\fB\-\-unsafe\-printable\-strings\fR" 4
.IX Item "--unsafe-printable-strings"
-Під час експортування (і лише під час нього) припускати, що рядки записано у
-кодуванні \s-1UTF\-16LE\s0 і виводити їх у форматі текстових рядків, а не
-послідовностей шістнадцяткових чисел. Вилучити завершальний нуль\-символ з
-рядків, якщо такий буде виявлено.
+Під час експортування (і лише під час нього) припускати, що рядки записано у кодуванні \s-1UTF\-16LE\s0 і виводити їх у форматі текстових рядків, а не послідовностей шістнадцяткових чисел. Вилучити завершальний нуль\-символ з рядків, якщо такий буде виявлено.
.Sp
-Така дія не є безпечною і не надає можливості зберегти точність запису
-початкових рядків реєстру з різних причин:
+Така дія не є безпечною і не надає можливості зберегти точність запису початкових рядків реєстру з різних причин:
.RS 4
.IP "\(bu" 4
-Припускається, що початковим кодуванням є \s-1UTF\-16LE.\s0 Рядки \s-1ASCII\s0 і рядки у
-інших кодуваннях буде пошкоджено під час цього перетворення.
+Припускається, що початковим кодуванням є \s-1UTF\-16LE.\s0 Рядки \s-1ASCII\s0 і рядки у інших кодуваннях буде пошкоджено під час цього перетворення.
.IP "\(bu" 4
-Припускається, що усі дані, які належать до типу 1 чи типу 2, є насправді
-рядками і що усі інші дані не є рядками, але визначений тип поля у реєстрах,
-зазвичай, не є надійним джерелом даних.
+Припускається, що усі дані, які належать до типу 1 чи типу 2, є насправді рядками і що усі інші дані не є рядками, але визначений тип поля у реєстрах, зазвичай, не є надійним джерелом даних.
.IP "\(bu" 4
Втрачаються дані щодо того, чи завершувався рядок у реєстрі нуль\-символом.
.RE
.RS 4
.Sp
-Усе це є наслідком того, що сам реєстр не містить даних щодо кодування
-рядків у ньому (див. \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3)).
+Усе це є наслідком того, що сам реєстр не містить даних щодо кодування рядків у ньому (див. \*(L"\s-1ENCODING STRINGS\*(R"\s0 in \fBWin::Hivex::Regedit\fR\|(3)).
.Sp
-Цим параметром слід користуватися лише для найпростіших рішень та
-діагностування вмісту реєстру. \fIНіколи\fR не користуйтеся ним, якщо виведені
-дані має бути передано іншій програмі або збережено у іншому реєстрі.
+Цим параметром слід користуватися лише для найпростіших рішень та діагностування вмісту реєстру. \fIНіколи\fR не користуйтеся ним, якщо виведені дані має бути передано іншій програмі або збережено у іншому реєстрі.
.RE
.SH "ПІДТРИМУВАНІ СИСТЕМИ"
.IX Header "ПІДТРИМУВАНІ СИСТЕМИ"
-У поточній версії цієї програми передбачено підтримку гостьових систем, які
-походять від Windows \s-1NT,\s0 починаючи з Windows \s-1XP\s0 і до, принаймні, Windows 8.
+У поточній версії цієї програми передбачено підтримку гостьових систем, які походять від Windows \s-1NT,\s0 починаючи з Windows \s-1XP\s0 і до, принаймні, Windows 8.
.PP
Передбачено підтримку таких ключів реєстру:
.ie n .IP """HKEY_LOCAL_MACHINE\eSAM""" 4
.ie n .IP """HKEY_USERS\e\fIкористувач\fP""" 4
.el .IP "\f(CWHKEY_USERS\e\f(CIкористувач\f(CW\fR" 4
.IX Item "HKEY_USERSкористувач"
-де \fIкористувач\fR — назва облікового запису локального користувача (це
-розширення libguestfs).
+де \fIкористувач\fR — назва облікового запису локального користувача (це розширення libguestfs).
.PP
-Ви можете використовувати \f(CW\*(C`HKLM\*(C'\fR як скорочення від \f(CW\*(C`HKEY_LOCAL_MACHINE\*(C'\fR,
-та \f(CW\*(C`HKU\*(C'\fR як скорочення від \f(CW\*(C`HKEY_USERS\*(C'\fR.
+Ви можете використовувати \f(CW\*(C`HKLM\*(C'\fR як скорочення від \f(CW\*(C`HKEY_LOCAL_MACHINE\*(C'\fR, та \f(CW\*(C`HKU\*(C'\fR як скорочення від \f(CW\*(C`HKEY_USERS\*(C'\fR.
.PP
-Підтримки буквальних ключів \f(CW\*(C`HKEY_USERS\e$SID\*(C'\fR і \f(CW\*(C`HKEY_CURRENT_USER\*(C'\fR не
-передбачено (немає «поточного користувача»).
+Підтримки буквальних ключів \f(CW\*(C`HKEY_USERS\e$SID\*(C'\fR і \f(CW\*(C`HKEY_CURRENT_USER\*(C'\fR не передбачено (немає «поточного користувача»).
.SS "\s-1WINDOWS 8\s0"
.IX Subsection "WINDOWS 8"
-«Швидкий запуск» Windows 8 може заважати virt-win-reg редагувати
-реєстр. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК \s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
+«Швидкий запуск» Windows 8 може заважати virt-win-reg редагувати реєстр. Див. \*(L"ПРИСИПЛЯННЯ \s-1WINDOWS\s0 ТА ШВИДКИЙ ЗАПУСК \s-1WINDOWS 8\*(R"\s0 in \fBguestfs\fR\|(3).
.SH "КОДУВАННЯ"
.IX Header "КОДУВАННЯ"
-\&\f(CW\*(C`virt\-win\-reg\*(C'\fR вважає, що вміст файлів regedit вже перекодовано до
-локального кодування. Зазвичай, у основних системах Linux це означає, що
-використано \s-1UTF\-8\s0 із символами завершення рядків у стилі Unix. Оскільки
-файли regedit Windows часто записуються у кодуванні \s-1UTF\-16LE\s0 із символами
-завершення рядків у стилі Windows, ймовірно, вам доведеться виконати
-перекодування усього файла до або після обробки.
+\&\f(CW\*(C`virt\-win\-reg\*(C'\fR вважає, що вміст файлів regedit вже перекодовано до локального кодування. Зазвичай, у основних системах Linux це означає, що використано \s-1UTF\-8\s0 із символами завершення рядків у стилі Unix. Оскільки файли regedit Windows часто записуються у кодуванні \s-1UTF\-16LE\s0 із символами завершення рядків у стилі Windows, ймовірно, вам доведеться виконати перекодування усього файла до або після обробки.
.PP
-Для перекодування файла з формату Windows до формату Linux (до обробки його
-за допомогою команди з параметром \fI\-\-merge\fR) вам слід зробити щось таке:
+Для перекодування файла з формату Windows до формату Linux (до обробки його за допомогою команди з параметром \fI\-\-merge\fR) вам слід зробити щось таке:
.PP
.Vb 1
\& iconv \-f utf\-16le \-t utf\-8 < win.reg | dos2unix > linux.reg
.Ve
.PP
-Щоб виконати зворотне перетворення після експортування і перед надсиланням
-файла користувачеві Windows, слід зробити щось таке:
+Щоб виконати зворотне перетворення після експортування і перед надсиланням файла користувачеві Windows, слід зробити щось таке:
.PP
.Vb 1
\& unix2dos linux.reg | iconv \-f utf\-8 \-t utf\-16le > win.reg
.Ve
.PP
-Щоб дізнатися більше про кодування, ознайомтеся зі сторінкою підручника щодо
-\&\fBWin::Hivex::Regedit\fR\|(3).
+Щоб дізнатися більше про кодування, ознайомтеся зі сторінкою підручника щодо \fBWin::Hivex::Regedit\fR\|(3).
.PP
-Якщо ви не певні щодо поточного кодування, скористайтеся командою
-\&\fBfile\fR\|(1). У свіжих версіях Windows regedit.exe створює файли кодування
-\&\s-1UTF\-16LE\s0 із символами завершення рядків у стилі Windows (\s-1CRLF\s0), ось такі:
+Якщо ви не певні щодо поточного кодування, скористайтеся командою \fBfile\fR\|(1). У свіжих версіях Windows regedit.exe створює файли кодування \s-1UTF\-16LE\s0 із символами завершення рядків у стилі Windows (\s-1CRLF\s0), ось такі:
.PP
.Vb 3
\& $ file software.reg
\& with CRLF line terminators
.Ve
.PP
-Цей файл потребуватиме перетворення, перш ніж ви зможете скористатися для
-нього параметром \fI\-\-merge\fR.
+Цей файл потребуватиме перетворення, перш ніж ви зможете скористатися для нього параметром \fI\-\-merge\fR.
.SH "CurrentControlSet тощо."
.IX Header "CurrentControlSet тощо."
-Ключі реєстру, подібні до \f(CW\*(C`CurrentControlSet\*(C'\fR, насправді не існують у
-реєстрі Windows на рівні файла рою, і тому ви не зможете вносити до них
-зміни.
+Ключі реєстру, подібні до \f(CW\*(C`CurrentControlSet\*(C'\fR, насправді не існують у реєстрі Windows на рівні файла рою, і тому ви не зможете вносити до них зміни.
.PP
-Насправді, \f(CW\*(C`CurrentControlSet\*(C'\fR є альтернативною назвою \f(CW\*(C`ControlSet001\*(C'\fR. За
-певних обставин це може бути посиланням на інший керівний набір. Визначити
-набір можна за допомогою ключа \f(CW\*(C`HKLM\eSYSTEM\eSelect\*(C'\fR:
+Насправді, \f(CW\*(C`CurrentControlSet\*(C'\fR є альтернативною назвою \f(CW\*(C`ControlSet001\*(C'\fR. За певних обставин це може бути посиланням на інший керівний набір. Визначити набір можна за допомогою ключа \f(CW\*(C`HKLM\eSYSTEM\eSelect\*(C'\fR:
.PP
.Vb 6
\& # virt\-win\-reg WindowsGuest \*(AqHKLM\eSYSTEM\eSelect\*(Aq
Аналогічно, інші ключі \f(CW\*(C`Current...\*(C'\fR у шляху можуть потребувати заміни.
.SH "ВИЛУЧЕННЯ КЛЮЧІВ ТА ЗНАЧЕНЬ РЕЄСТРУ"
.IX Header "ВИЛУЧЕННЯ КЛЮЧІВ ТА ЗНАЧЕНЬ РЕЄСТРУ"
-Для вилучення усього ключа реєстру скористайтеся такою синтаксичною
-конструкцією:
+Для вилучення усього ключа реєстру скористайтеся такою синтаксичною конструкцією:
.PP
.Vb 1
\& [\-HKEY_LOCAL_MACHINE\eFoo]
.Ve
.PP
-Для вилучення окремого значення у ключі скористайтеся такою синтаксичною
-конструкцією:
+Для вилучення окремого значення у ключі скористайтеся такою синтаксичною конструкцією:
.PP
.Vb 2
\& [HKEY_LOCAL_MACHINE\eFoo]
.Ve
.SH "ПІДКАЗКИ ЩОДО WINDOWS"
.IX Header "ПІДКАЗКИ ЩОДО WINDOWS"
-Зауважте, що у результаті деяких із команд у підказках буде змінено образ
-диска гостьової системи. Гостьову систему \fIмає\fR бути вимкнено, щоб
-запобігти пошкодженню даних на диску.
+Зауважте, що у результаті деяких із команд у підказках буде змінено образ диска гостьової системи. Гостьову систему \fIмає\fR бути вимкнено, щоб запобігти пошкодженню даних на диску.
.SS "ЗАПУСК ПАКЕТНОГО СКРИПТУ ПІД ЧАС ВХОДУ КОРИСТУВАЧА ДО СИСТЕМИ"
.IX Subsection "ЗАПУСК ПАКЕТНОГО СКРИПТУ ПІД ЧАС ВХОДУ КОРИСТУВАЧА ДО СИСТЕМИ"
-Приготуйте пакетний скрипт \s-1DOS\s0 (.bat), скрипт VBScript або виконуваний
-файл. Вивантажте його до гостьової системи за допомогою \fBguestfish\fR\|(1). У
-цьому прикладі скрипт називається \f(CW\*(C`test.bat\*(C'\fR і його вивантажено до \f(CW\*(C`C:\e\*(C'\fR:
+Приготуйте пакетний скрипт \s-1DOS\s0 (.bat), скрипт VBScript або виконуваний файл. Вивантажте його до гостьової системи за допомогою \fBguestfish\fR\|(1). У цьому прикладі скрипт називається \f(CW\*(C`test.bat\*(C'\fR і його вивантажено до \f(CW\*(C`C:\e\*(C'\fR:
.PP
.Vb 1
\& guestfish \-i \-d WindowsGuest upload test.bat /test.bat
\& EOF
.Ve
.PP
-У цьому прикладі ми використовуємо ключ \f(CW\*(C`RunOnce\*(C'\fR, який означає, що скрипт
-буде запущено лише один раз під час першого входу користувача до
-системи. Якщо вам потрібно, щоб скрипт запускався кожного разу, коли
-користувач входить до системи, замініть \f(CW\*(C`RunOnce\*(C'\fR на \f(CW\*(C`Run\*(C'\fR.
+У цьому прикладі ми використовуємо ключ \f(CW\*(C`RunOnce\*(C'\fR, який означає, що скрипт буде запущено лише один раз під час першого входу користувача до системи. Якщо вам потрібно, щоб скрипт запускався кожного разу, коли користувач входить до системи, замініть \f(CW\*(C`RunOnce\*(C'\fR на \f(CW\*(C`Run\*(C'\fR.
.PP
Оновіть регістр:
.PP
.Ve
.SS "ВСТАНОВЛЕННЯ СЛУЖБИ"
.IX Subsection "ВСТАНОВЛЕННЯ СЛУЖБИ"
-У цьому розділі ми припускаємо, що ви обізнані із роботою служб Windows і
-маєте програму, яка обробляє протокол керування службами Windows
-безпосередньо або хочете запустити будь\-яку програму за допомогою обгортки
-служби, наприклад SrvAny або безкоштовної RHSrvAny.
+У цьому розділі ми припускаємо, що ви обізнані із роботою служб Windows і маєте програму, яка обробляє протокол керування службами Windows безпосередньо або хочете запустити будь\-яку програму за допомогою обгортки служби, наприклад SrvAny або безкоштовної RHSrvAny.
.PP
-Спочатку вивантажте програму і, якщо потрібно, обгортку служби. У нашому
-прикладі тестова програма має назву \f(CW\*(C`test.exe\*(C'\fR і використано обгортку
-RHSrvAny:
+Спочатку вивантажте програму і, якщо потрібно, обгортку служби. У нашому прикладі тестова програма має назву \f(CW\*(C`test.exe\*(C'\fR і використано обгортку RHSrvAny:
.PP
.Vb 4
\& guestfish \-i \-d WindowsGuest <<EOF
\& EOF
.Ve
.PP
-Приготуйте файл regedit зі змінами до реєстру. У нашому прикладі перша зміна
-до реєстру потрібна для самої служби або обгортки служби (якщо така
-використовується). Друга зміна потрібна лише через те, що ми використовуємо
-обгортку служби RHSrvAny.
+Приготуйте файл regedit зі змінами до реєстру. У нашому прикладі перша зміна до реєстру потрібна для самої служби або обгортки служби (якщо така використовується). Друга зміна потрібна лише через те, що ми використовуємо обгортку служби RHSrvAny.
.PP
.Vb 8
\& cat > service.reg <<\*(AqEOF\*(Aq
.PP
Нотатки:
.IP "\(bu" 4
-Щодо використання \f(CW\*(C`ControlSet001\*(C'\fR див. розділ вище на цій сторінці
-підручника. Ймовірно, вам слід скоригувати цей запис відповідно до керівного
-набору, який використовується вашою гостьовою системою.
+Щодо використання \f(CW\*(C`ControlSet001\*(C'\fR див. розділ вище на цій сторінці підручника. Ймовірно, вам слід скоригувати цей запис відповідно до керівного набору, який використовується вашою гостьовою системою.
.IP "\(bu" 4
-\&\f(CW"ObjectName"\fR керує правами доступу, які матиме служба. Альтернативою є
-\&\f(CW"ObjectName"="LocalSystem"\fR, яка надає права доступу найпривілейованішого
-облікового запису.
+\&\f(CW"ObjectName"\fR керує правами доступу, які матиме служба. Альтернативою є \f(CW"ObjectName"="LocalSystem"\fR, яка надає права доступу найпривілейованішого облікового запису.
.IP "\(bu" 4
-Щодо значення «магічних чисел» ознайомтеся із цією статтею бази даних знань
-Microsoft: http://support.microsoft.com/kb/103000.
+Щодо значення «магічних чисел» ознайомтеся із цією статтею бази даних знань Microsoft: http://support.microsoft.com/kb/103000.
.PP
Оновіть регістр:
.PP
.Ve
.SH "ЕКРАНУВАННЯ СИМВОЛІВ У ОБОЛОНЦІ"
.IX Header "ЕКРАНУВАННЯ СИМВОЛІВ У ОБОЛОНЦІ"
-Будьте обережні із передаванням параметрів, які містять символ \f(CW\*(C`\e\*(C'\fR
-(зворотну похилу риску), до командної оболонки. Зазвичай, вам слід
-використати одинарні лапки або подвійні зворотні похилі риски (але не те і
-інше одразу) для захисту від обробки інтерпретатором командної оболонки.
+Будьте обережні із передаванням параметрів, які містять символ \f(CW\*(C`\e\*(C'\fR (зворотну похилу риску), до командної оболонки. Зазвичай, вам слід використати одинарні лапки або подвійні зворотні похилі риски (але не те і інше одразу) для захисту від обробки інтерпретатором командної оболонки.
.PP
Регістр символів шляхів і назв значень береться до уваги під час обробки.
.SH "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
.IX Header "ТАКОЖ ПЕРЕГЛЯНЬТЕ"
-\&\fBhivex\fR\|(3), \fBhivexsh\fR\|(1), \fBhivexregedit\fR\|(1), \fBguestfs\fR\|(3),
-\&\fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-tail\fR\|(1), \fBSys::Guestfs\fR\|(3),
-\&\fBWin::Hivex\fR\|(3), \fBWin::Hivex::Regedit\fR\|(3), \fBSys::Virt\fR\|(3),
-http://libguestfs.org/.
+\&\fBhivex\fR\|(3), \fBhivexsh\fR\|(1), \fBhivexregedit\fR\|(1), \fBguestfs\fR\|(3), \fBguestfish\fR\|(1), \fBvirt\-cat\fR\|(1), \fBvirt\-tail\fR\|(1), \fBSys::Guestfs\fR\|(3), \fBWin::Hivex\fR\|(3), \fBWin::Hivex::Regedit\fR\|(3), \fBSys::Virt\fR\|(3), http://libguestfs.org/.
.SH "АВТОР"
.IX Header "АВТОР"
Richard W.M. Jones http://people.redhat.com/~rjones/
--- /dev/null
+
+=head1 НАЗВА
+
+virt-win-reg — програма для експортування та дописування записів реєстру Windows з гостьової системи Windows
+
+=head1 КОРОТКИЙ ОПИС
+
+ virt-win-reg назва_домену 'HKLM\Шлях\до\підключа'
+
+ virt-win-reg назва_домену 'HKLM\Шлях\до\підключа' назва
+
+ virt-win-reg назва_домену 'HKLM\Шлях\до\підключа' @
+
+ virt-win-reg --merge назва_домену [вхідний.reg ...]
+
+ virt-win-reg [--параметри] диск.img ... # замість назва_домену
+
+=head1 ПОПЕРЕДЖЕННЯ
+
+I<Не> використовуйте C<virt-win-reg> з параметром I<--merge> для активних віртуальних машин. Якщо ви зробите це, ви I<невиправно> ушкодите диск у віртуальній машині. C<virt-win-reg> намагатиметься запобігти подібним діям, але програма не завжди може визначити усі можливі випадки.
+
+Внесення змін до реєстру Windows є ризикованою дією. Формат реєстру доволі неясний і недокументований, а зміни у реєстрі можуть призвести до неможливості завантажити систему. Тому, якщо ви користуєтеся параметром I<--merge>, не забувайте спочатку створити надійну резервну копію.
+
+=head1 ОПИС
+
+Ця програма може експортувати і дописувати записи реєстру Windows з гостьової системи Windows.
+
+Першим параметром є назва гостьової системи libvirt або простого (raw) образу гостьової системи Windows.
+
+Якщо I<не> вказано параметр I<--merge>, вибраний ключ реєстру буде показано або експортовано (рекурсивно). Приклад:
+
+ $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
+
+Крім того, ви можете переглядати окремі значення у ключах реєстру. Приклад:
+
+ $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
+ $ virt-win-reg Windows7 $cvkey ProductName
+ Windows 7 Enterprise
+
+За допомогою I<--merge> ви можете дописати текстовий файл regedit до реєстру Windows:
+
+ $ virt-win-reg --merge Windows7 changes.reg
+
+=head2 ПРИМІТКА
+
+Цю програму призначено лише для спрощення доступу до реєстру. Якщо вам потрібні якісь складні дії з реєстром, рекомендуємо вам отримати файли роїв реєстру з гостьової системи за допомогою L<libguestfs(3)> або L<guestfish(1)> і обробити їх локально, наприклад за допомогою L<hivex(3)>, L<hivexsh(1)> або L<hivexregedit(1)>.
+
+=head1 ПАРАМЕТРИ
+
+=over 4
+
+=item B<--help>
+
+Показати коротку довідку.
+
+=item B<--version>
+
+Показати дані щодо версії і завершити роботу.
+
+=item B<--debug>
+
+Увімкнути показ діагностичних повідомлень.
+
+=item B<-c адреса>
+
+=item B<--connect адреса>
+
+Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
+
+Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не буде використовуватися взагалі.
+
+=item B<--format> raw
+
+Визначає формат образу диска, назву якого вказано у рядку команди. Якщо формат не вказано, його буде визначено автоматично на основі вмісту образу диска.
+
+Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних до libvirt. У цьому випадку вказане значення параметра формату буде проігноровано.
+
+Якщо ви працюєте із образами дисків гостьових систем у форматі raw із ненадійних джерел, вам слід завжди вказувати назву формату.
+
+=item B<--merge>
+
+У режимі об'єднання програма дописує текстовий файл regedit до реєстру Windows віртуальної машини. Якщо цей параметр I<не> вказано, virt-win-reg показує або експортує записи реєстру.
+
+Зауважте, що I<--merge> I<не безпечно> використовувати для активних віртуальних машин. Використання цього параметра команди для активних віртуальних машин призводить до пошкодження вмісту диска. Втім, експортування (виконання команди без цього параметра) є завжди безпечним.
+
+=item B<--encoding> UTF-16LE|ASCII
+
+При об'єднанні (і лише при ньому) у вас може виникнути потреба у визначення кодування рядків, які використовуються у файлі рою. Докладніший опис можна знайти у розділі L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
+
+Типово буде використано кодування UTF-16LE, яке має працювати у свіжих версіях Windows.
+
+=item B<--unsafe-printable-strings>
+
+Під час експортування (і лише під час нього) припускати, що рядки записано у кодуванні UTF-16LE і виводити їх у форматі текстових рядків, а не послідовностей шістнадцяткових чисел. Вилучити завершальний нуль-символ з рядків, якщо такий буде виявлено.
+
+Така дія не є безпечною і не надає можливості зберегти точність запису початкових рядків реєстру з різних причин:
+
+=over 4
+
+=item *
+
+Припускається, що початковим кодуванням є UTF-16LE. Рядки ASCII і рядки у інших кодуваннях буде пошкоджено під час цього перетворення.
+
+=item *
+
+Припускається, що усі дані, які належать до типу 1 чи типу 2, є насправді рядками і що усі інші дані не є рядками, але визначений тип поля у реєстрах, зазвичай, не є надійним джерелом даних.
+
+=item *
+
+Втрачаються дані щодо того, чи завершувався рядок у реєстрі нуль-символом.
+
+=back
+
+Усе це є наслідком того, що сам реєстр не містить даних щодо кодування рядків у ньому (див. L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
+
+Цим параметром слід користуватися лише для найпростіших рішень та діагностування вмісту реєстру. I<Ніколи> не користуйтеся ним, якщо виведені дані має бути передано іншій програмі або збережено у іншому реєстрі.
+
+=back
+
+=head1 ПІДТРИМУВАНІ СИСТЕМИ
+
+У поточній версії цієї програми передбачено підтримку гостьових систем, які походять від Windows NT, починаючи з Windows XP і до, принаймні, Windows 8.
+
+Передбачено підтримку таких ключів реєстру:
+
+=over 4
+
+=item C<HKEY_LOCAL_MACHINE\SAM>
+
+=item C<HKEY_LOCAL_MACHINE\SECURITY>
+
+=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
+
+=item C<HKEY_LOCAL_MACHINE\SYSTEM>
+
+=item C<HKEY_USERS\.DEFAULT>
+
+=item C<HKEY_USERS\I<SID>>
+
+де I<SID> — SID користувача Windows (наприклад C<S-1-5-18>).
+
+=item C<HKEY_USERS\I<користувач>>
+
+де I<користувач> — назва облікового запису локального користувача (це розширення libguestfs).
+
+=back
+
+Ви можете використовувати C<HKLM> як скорочення від C<HKEY_LOCAL_MACHINE>, та C<HKU> як скорочення від C<HKEY_USERS>.
+
+Підтримки буквальних ключів C<HKEY_USERS\$SID> і C<HKEY_CURRENT_USER> не передбачено (немає «поточного користувача»).
+
+=head2 WINDOWS 8
+
+«Швидкий запуск» Windows 8 може заважати virt-win-reg редагувати реєстр. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК WINDOWS 8>.
+
+=head1 КОДУВАННЯ
+
+C<virt-win-reg> вважає, що вміст файлів regedit вже перекодовано до локального кодування. Зазвичай, у основних системах Linux це означає, що використано UTF-8 із символами завершення рядків у стилі Unix. Оскільки файли regedit Windows часто записуються у кодуванні UTF-16LE із символами завершення рядків у стилі Windows, ймовірно, вам доведеться виконати перекодування усього файла до або після обробки.
+
+Для перекодування файла з формату Windows до формату Linux (до обробки його за допомогою команди з параметром I<--merge>) вам слід зробити щось таке:
+
+ iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
+
+Щоб виконати зворотне перетворення після експортування і перед надсиланням файла користувачеві Windows, слід зробити щось таке:
+
+ unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
+
+Щоб дізнатися більше про кодування, ознайомтеся зі сторінкою підручника щодо L<Win::Hivex::Regedit(3)>.
+
+Якщо ви не певні щодо поточного кодування, скористайтеся командою L<file(1)>. У свіжих версіях Windows regedit.exe створює файли кодування UTF-16LE із символами завершення рядків у стилі Windows (CRLF), ось такі:
+
+ $ file software.reg
+ software.reg: Little-endian UTF-16 Unicode text, with very long lines,
+ with CRLF line terminators
+
+Цей файл потребуватиме перетворення, перш ніж ви зможете скористатися для нього параметром I<--merge>.
+
+=head1 CurrentControlSet тощо.
+
+Ключі реєстру, подібні до C<CurrentControlSet>, насправді не існують у реєстрі Windows на рівні файла рою, і тому ви не зможете вносити до них зміни.
+
+Насправді, C<CurrentControlSet> є альтернативною назвою C<ControlSet001>. За певних обставин це може бути посиланням на інший керівний набір. Визначити набір можна за допомогою ключа C<HKLM\SYSTEM\Select>:
+
+ # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
+ [HKEY_LOCAL_MACHINE\SYSTEM\Select]
+ "Current"=dword:00000001
+ "Default"=dword:00000001
+ "Failed"=dword:00000000
+ "LastKnownGood"=dword:00000002
+
+«Поточним» є той набір, який Windows вибере під час завантаження.
+
+Аналогічно, інші ключі C<Current...> у шляху можуть потребувати заміни.
+
+=head1 ВИЛУЧЕННЯ КЛЮЧІВ ТА ЗНАЧЕНЬ РЕЄСТРУ
+
+Для вилучення усього ключа реєстру скористайтеся такою синтаксичною конструкцією:
+
+ [-HKEY_LOCAL_MACHINE\Foo]
+
+Для вилучення окремого значення у ключі скористайтеся такою синтаксичною конструкцією:
+
+ [HKEY_LOCAL_MACHINE\Foo]
+ "Value"=-
+
+=head1 ПІДКАЗКИ ЩОДО WINDOWS
+
+Зауважте, що у результаті деяких із команд у підказках буде змінено образ диска гостьової системи. Гостьову систему I<має> бути вимкнено, щоб запобігти пошкодженню даних на диску.
+
+=head2 ЗАПУСК ПАКЕТНОГО СКРИПТУ ПІД ЧАС ВХОДУ КОРИСТУВАЧА ДО СИСТЕМИ
+
+Приготуйте пакетний скрипт DOS (.bat), скрипт VBScript або виконуваний файл. Вивантажте його до гостьової системи за допомогою L<guestfish(1)>. У цьому прикладі скрипт називається C<test.bat> і його вивантажено до C<C:\>:
+
+ guestfish -i -d WindowsGuest upload test.bat /test.bat
+
+Приготуйте файл regedit, який міститиме зміни до реєстру:
+
+ cat > test.reg <<'EOF'
+ [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
+ "Test"="c:\\test.bat"
+ EOF
+
+У цьому прикладі ми використовуємо ключ C<RunOnce>, який означає, що скрипт буде запущено лише один раз під час першого входу користувача до системи. Якщо вам потрібно, щоб скрипт запускався кожного разу, коли користувач входить до системи, замініть C<RunOnce> на C<Run>.
+
+Оновіть регістр:
+
+ virt-win-reg --merge WindowsGuest test.reg
+
+=head2 ВСТАНОВЛЕННЯ СЛУЖБИ
+
+У цьому розділі ми припускаємо, що ви обізнані із роботою служб Windows і маєте програму, яка обробляє протокол керування службами Windows безпосередньо або хочете запустити будь-яку програму за допомогою обгортки служби, наприклад SrvAny або безкоштовної RHSrvAny.
+
+Спочатку вивантажте програму і, якщо потрібно, обгортку служби. У нашому прикладі тестова програма має назву C<test.exe> і використано обгортку RHSrvAny:
+
+ guestfish -i -d WindowsGuest <<EOF
+ upload rhsrvany.exe /rhsrvany.exe
+ upload test.exe /test.exe
+ EOF
+
+Приготуйте файл regedit зі змінами до реєстру. У нашому прикладі перша зміна до реєстру потрібна для самої служби або обгортки служби (якщо така використовується). Друга зміна потрібна лише через те, що ми використовуємо обгортку служби RHSrvAny.
+
+ cat > service.reg <<'EOF'
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
+ "Type"=dword:00000010
+ "Start"=dword:00000002
+ "ErrorControl"=dword:00000001
+ "ImagePath"="c:\\rhsrvany.exe"
+ "DisplayName"="RHSrvAny"
+ "ObjectName"="NetworkService"
+
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
+ "CommandLine"="c:\\test.exe"
+ "PWD"="c:\\Temp"
+ EOF
+
+Нотатки:
+
+=over 4
+
+=item *
+
+Щодо використання C<ControlSet001> див. розділ вище на цій сторінці підручника. Ймовірно, вам слід скоригувати цей запис відповідно до керівного набору, який використовується вашою гостьовою системою.
+
+=item *
+
+C<"ObjectName"> керує правами доступу, які матиме служба. Альтернативою є C<"ObjectName"="LocalSystem">, яка надає права доступу найпривілейованішого облікового запису.
+
+=item *
+
+Щодо значення «магічних чисел» ознайомтеся із цією статтею бази даних знань Microsoft: L<http://support.microsoft.com/kb/103000>.
+
+=back
+
+Оновіть регістр:
+
+ virt-win-reg --merge WindowsGuest service.reg
+
+=head1 ЕКРАНУВАННЯ СИМВОЛІВ У ОБОЛОНЦІ
+
+Будьте обережні із передаванням параметрів, які містять символ C<\> (зворотну похилу риску), до командної оболонки. Зазвичай, вам слід використати одинарні лапки або подвійні зворотні похилі риски (але не те і інше одразу) для захисту від обробки інтерпретатором командної оболонки.
+
+Регістр символів шляхів і назв значень береться до уваги під час обробки.
+
+=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
+
+L<hivex(3)>, L<hivexsh(1)>, L<hivexregedit(1)>, L<guestfs(3)>, L<guestfish(1)>, L<virt-cat(1)>, L<virt-tail(1)>, L<Sys::Guestfs(3)>, L<Win::Hivex(3)>, L<Win::Hivex::Regedit(3)>, L<Sys::Virt(3)>, L<http://libguestfs.org/>.
+
+=head1 АВТОР
+
+Richard W.M. Jones L<http://people.redhat.com/~rjones/>
+
+=head1 АВТОРСЬКІ ПРАВА
+
+©Red Hat Inc., 2010
+
+++ /dev/null
-
-=head1 НАЗВА
-
-virt-win-reg — програма для експортування та дописування записів реєстру
-Windows з гостьової системи Windows
-
-=head1 КОРОТКИЙ ОПИС
-
- virt-win-reg назва_домену 'HKLM\Шлях\до\підключа'
-
- virt-win-reg назва_домену 'HKLM\Шлях\до\підключа' назва
-
- virt-win-reg назва_домену 'HKLM\Шлях\до\підключа' @
-
- virt-win-reg --merge назва_домену [вхідний.reg ...]
-
- virt-win-reg [--параметри] диск.img ... # замість назва_домену
-
-=head1 ПОПЕРЕДЖЕННЯ
-
-I<Не> використовуйте C<virt-win-reg> з параметром I<--merge> для активних
-віртуальних машин. Якщо ви зробите це, ви I<невиправно> ушкодите диск у
-віртуальній машині. C<virt-win-reg> намагатиметься запобігти подібним діям,
-але програма не завжди може визначити усі можливі випадки.
-
-Внесення змін до реєстру Windows є ризикованою дією. Формат реєстру доволі
-неясний і недокументований, а зміни у реєстрі можуть призвести до
-неможливості завантажити систему. Тому, якщо ви користуєтеся параметром
-I<--merge>, не забувайте спочатку створити надійну резервну копію.
-
-=head1 ОПИС
-
-Ця програма може експортувати і дописувати записи реєстру Windows з
-гостьової системи Windows.
-
-Першим параметром є назва гостьової системи libvirt або простого (raw)
-образу гостьової системи Windows.
-
-Якщо I<не> вказано параметр I<--merge>, вибраний ключ реєстру буде показано
-або експортовано (рекурсивно). Приклад:
-
- $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
-
-Крім того, ви можете переглядати окремі значення у ключах реєстру. Приклад:
-
- $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
- $ virt-win-reg Windows7 $cvkey ProductName
- Windows 7 Enterprise
-
-За допомогою I<--merge> ви можете дописати текстовий файл regedit до реєстру
-Windows:
-
- $ virt-win-reg --merge Windows7 changes.reg
-
-=head2 ПРИМІТКА
-
-Цю програму призначено лише для спрощення доступу до реєстру. Якщо вам
-потрібні якісь складні дії з реєстром, рекомендуємо вам отримати файли роїв
-реєстру з гостьової системи за допомогою L<libguestfs(3)> або
-L<guestfish(1)> і обробити їх локально, наприклад за допомогою L<hivex(3)>,
-L<hivexsh(1)> або L<hivexregedit(1)>.
-
-=head1 ПАРАМЕТРИ
-
-=over 4
-
-=item B<--help>
-
-Показати коротку довідку.
-
-=item B<--version>
-
-Показати дані щодо версії і завершити роботу.
-
-=item B<--debug>
-
-Увімкнути показ діагностичних повідомлень.
-
-=item B<-c адреса>
-
-=item B<--connect адреса>
-
-Якщо використовується libvirt, встановити з’єднання з вказаним I<URI>. Якщо
-пропущено, з’єднання буде встановлено з типовим гіпервізором libvirt.
-
-Якщо вказати блокові пристрої гостьових систем безпосередньо, libvirt не
-буде використовуватися взагалі.
-
-=item B<--format> raw
-
-Визначає формат образу диска, назву якого вказано у рядку команди. Якщо
-формат не вказано, його буде визначено автоматично на основі вмісту образу
-диска.
-
-Якщо вказаний диск походить з libvirt, ця програма надішле запит щодо даних
-до libvirt. У цьому випадку вказане значення параметра формату буде
-проігноровано.
-
-Якщо ви працюєте із образами дисків гостьових систем у форматі raw із
-ненадійних джерел, вам слід завжди вказувати назву формату.
-
-=item B<--merge>
-
-У режимі об'єднання програма дописує текстовий файл regedit до реєстру
-Windows віртуальної машини. Якщо цей параметр I<не> вказано, virt-win-reg
-показує або експортує записи реєстру.
-
-Зауважте, що I<--merge> I<не безпечно> використовувати для активних
-віртуальних машин. Використання цього параметра команди для активних
-віртуальних машин призводить до пошкодження вмісту диска. Втім,
-експортування (виконання команди без цього параметра) є завжди безпечним.
-
-=item B<--encoding> UTF-16LE|ASCII
-
-При об'єднанні (і лише при ньому) у вас може виникнути потреба у визначення
-кодування рядків, які використовуються у файлі рою. Докладніший опис можна
-знайти у розділі L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
-
-Типово буде використано кодування UTF-16LE, яке має працювати у свіжих
-версіях Windows.
-
-=item B<--unsafe-printable-strings>
-
-Під час експортування (і лише під час нього) припускати, що рядки записано у
-кодуванні UTF-16LE і виводити їх у форматі текстових рядків, а не
-послідовностей шістнадцяткових чисел. Вилучити завершальний нуль-символ з
-рядків, якщо такий буде виявлено.
-
-Така дія не є безпечною і не надає можливості зберегти точність запису
-початкових рядків реєстру з різних причин:
-
-=over 4
-
-=item *
-
-Припускається, що початковим кодуванням є UTF-16LE. Рядки ASCII і рядки у
-інших кодуваннях буде пошкоджено під час цього перетворення.
-
-=item *
-
-Припускається, що усі дані, які належать до типу 1 чи типу 2, є насправді
-рядками і що усі інші дані не є рядками, але визначений тип поля у реєстрах,
-зазвичай, не є надійним джерелом даних.
-
-=item *
-
-Втрачаються дані щодо того, чи завершувався рядок у реєстрі нуль-символом.
-
-=back
-
-Усе це є наслідком того, що сам реєстр не містить даних щодо кодування
-рядків у ньому (див. L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
-
-Цим параметром слід користуватися лише для найпростіших рішень та
-діагностування вмісту реєстру. I<Ніколи> не користуйтеся ним, якщо виведені
-дані має бути передано іншій програмі або збережено у іншому реєстрі.
-
-=back
-
-=head1 ПІДТРИМУВАНІ СИСТЕМИ
-
-У поточній версії цієї програми передбачено підтримку гостьових систем, які
-походять від Windows NT, починаючи з Windows XP і до, принаймні, Windows 8.
-
-Передбачено підтримку таких ключів реєстру:
-
-=over 4
-
-=item C<HKEY_LOCAL_MACHINE\SAM>
-
-=item C<HKEY_LOCAL_MACHINE\SECURITY>
-
-=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
-
-=item C<HKEY_LOCAL_MACHINE\SYSTEM>
-
-=item C<HKEY_USERS\.DEFAULT>
-
-=item C<HKEY_USERS\I<SID>>
-
-де I<SID> — SID користувача Windows (наприклад C<S-1-5-18>).
-
-=item C<HKEY_USERS\I<користувач>>
-
-де I<користувач> — назва облікового запису локального користувача (це
-розширення libguestfs).
-
-=back
-
-Ви можете використовувати C<HKLM> як скорочення від C<HKEY_LOCAL_MACHINE>,
-та C<HKU> як скорочення від C<HKEY_USERS>.
-
-Підтримки буквальних ключів C<HKEY_USERS\$SID> і C<HKEY_CURRENT_USER> не
-передбачено (немає «поточного користувача»).
-
-=head2 WINDOWS 8
-
-«Швидкий запуск» Windows 8 може заважати virt-win-reg редагувати
-реєстр. Див. L<guestfs(3)/ПРИСИПЛЯННЯ WINDOWS ТА ШВИДКИЙ ЗАПУСК WINDOWS 8>.
-
-=head1 КОДУВАННЯ
-
-C<virt-win-reg> вважає, що вміст файлів regedit вже перекодовано до
-локального кодування. Зазвичай, у основних системах Linux це означає, що
-використано UTF-8 із символами завершення рядків у стилі Unix. Оскільки
-файли regedit Windows часто записуються у кодуванні UTF-16LE із символами
-завершення рядків у стилі Windows, ймовірно, вам доведеться виконати
-перекодування усього файла до або після обробки.
-
-Для перекодування файла з формату Windows до формату Linux (до обробки його
-за допомогою команди з параметром I<--merge>) вам слід зробити щось таке:
-
- iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
-
-Щоб виконати зворотне перетворення після експортування і перед надсиланням
-файла користувачеві Windows, слід зробити щось таке:
-
- unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
-
-Щоб дізнатися більше про кодування, ознайомтеся зі сторінкою підручника щодо
-L<Win::Hivex::Regedit(3)>.
-
-Якщо ви не певні щодо поточного кодування, скористайтеся командою
-L<file(1)>. У свіжих версіях Windows regedit.exe створює файли кодування
-UTF-16LE із символами завершення рядків у стилі Windows (CRLF), ось такі:
-
- $ file software.reg
- software.reg: Little-endian UTF-16 Unicode text, with very long lines,
- with CRLF line terminators
-
-Цей файл потребуватиме перетворення, перш ніж ви зможете скористатися для
-нього параметром I<--merge>.
-
-=head1 CurrentControlSet тощо.
-
-Ключі реєстру, подібні до C<CurrentControlSet>, насправді не існують у
-реєстрі Windows на рівні файла рою, і тому ви не зможете вносити до них
-зміни.
-
-Насправді, C<CurrentControlSet> є альтернативною назвою C<ControlSet001>. За
-певних обставин це може бути посиланням на інший керівний набір. Визначити
-набір можна за допомогою ключа C<HKLM\SYSTEM\Select>:
-
- # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
- [HKEY_LOCAL_MACHINE\SYSTEM\Select]
- "Current"=dword:00000001
- "Default"=dword:00000001
- "Failed"=dword:00000000
- "LastKnownGood"=dword:00000002
-
-«Поточним» є той набір, який Windows вибере під час завантаження.
-
-Аналогічно, інші ключі C<Current...> у шляху можуть потребувати заміни.
-
-=head1 ВИЛУЧЕННЯ КЛЮЧІВ ТА ЗНАЧЕНЬ РЕЄСТРУ
-
-Для вилучення усього ключа реєстру скористайтеся такою синтаксичною
-конструкцією:
-
- [-HKEY_LOCAL_MACHINE\Foo]
-
-Для вилучення окремого значення у ключі скористайтеся такою синтаксичною
-конструкцією:
-
- [HKEY_LOCAL_MACHINE\Foo]
- "Value"=-
-
-=head1 ПІДКАЗКИ ЩОДО WINDOWS
-
-Зауважте, що у результаті деяких із команд у підказках буде змінено образ
-диска гостьової системи. Гостьову систему I<має> бути вимкнено, щоб
-запобігти пошкодженню даних на диску.
-
-=head2 ЗАПУСК ПАКЕТНОГО СКРИПТУ ПІД ЧАС ВХОДУ КОРИСТУВАЧА ДО СИСТЕМИ
-
-Приготуйте пакетний скрипт DOS (.bat), скрипт VBScript або виконуваний
-файл. Вивантажте його до гостьової системи за допомогою L<guestfish(1)>. У
-цьому прикладі скрипт називається C<test.bat> і його вивантажено до C<C:\>:
-
- guestfish -i -d WindowsGuest upload test.bat /test.bat
-
-Приготуйте файл regedit, який міститиме зміни до реєстру:
-
- cat > test.reg <<'EOF'
- [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
- "Test"="c:\\test.bat"
- EOF
-
-У цьому прикладі ми використовуємо ключ C<RunOnce>, який означає, що скрипт
-буде запущено лише один раз під час першого входу користувача до
-системи. Якщо вам потрібно, щоб скрипт запускався кожного разу, коли
-користувач входить до системи, замініть C<RunOnce> на C<Run>.
-
-Оновіть регістр:
-
- virt-win-reg --merge WindowsGuest test.reg
-
-=head2 ВСТАНОВЛЕННЯ СЛУЖБИ
-
-У цьому розділі ми припускаємо, що ви обізнані із роботою служб Windows і
-маєте програму, яка обробляє протокол керування службами Windows
-безпосередньо або хочете запустити будь-яку програму за допомогою обгортки
-служби, наприклад SrvAny або безкоштовної RHSrvAny.
-
-Спочатку вивантажте програму і, якщо потрібно, обгортку служби. У нашому
-прикладі тестова програма має назву C<test.exe> і використано обгортку
-RHSrvAny:
-
- guestfish -i -d WindowsGuest <<EOF
- upload rhsrvany.exe /rhsrvany.exe
- upload test.exe /test.exe
- EOF
-
-Приготуйте файл regedit зі змінами до реєстру. У нашому прикладі перша зміна
-до реєстру потрібна для самої служби або обгортки служби (якщо така
-використовується). Друга зміна потрібна лише через те, що ми використовуємо
-обгортку служби RHSrvAny.
-
- cat > service.reg <<'EOF'
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
- "Type"=dword:00000010
- "Start"=dword:00000002
- "ErrorControl"=dword:00000001
- "ImagePath"="c:\\rhsrvany.exe"
- "DisplayName"="RHSrvAny"
- "ObjectName"="NetworkService"
-
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
- "CommandLine"="c:\\test.exe"
- "PWD"="c:\\Temp"
- EOF
-
-Нотатки:
-
-=over 4
-
-=item *
-
-Щодо використання C<ControlSet001> див. розділ вище на цій сторінці
-підручника. Ймовірно, вам слід скоригувати цей запис відповідно до керівного
-набору, який використовується вашою гостьовою системою.
-
-=item *
-
-C<"ObjectName"> керує правами доступу, які матиме служба. Альтернативою є
-C<"ObjectName"="LocalSystem">, яка надає права доступу найпривілейованішого
-облікового запису.
-
-=item *
-
-Щодо значення «магічних чисел» ознайомтеся із цією статтею бази даних знань
-Microsoft: L<http://support.microsoft.com/kb/103000>.
-
-=back
-
-Оновіть регістр:
-
- virt-win-reg --merge WindowsGuest service.reg
-
-=head1 ЕКРАНУВАННЯ СИМВОЛІВ У ОБОЛОНЦІ
-
-Будьте обережні із передаванням параметрів, які містять символ C<\>
-(зворотну похилу риску), до командної оболонки. Зазвичай, вам слід
-використати одинарні лапки або подвійні зворотні похилі риски (але не те і
-інше одразу) для захисту від обробки інтерпретатором командної оболонки.
-
-Регістр символів шляхів і назв значень береться до уваги під час обробки.
-
-=head1 ТАКОЖ ПЕРЕГЛЯНЬТЕ
-
-L<hivex(3)>, L<hivexsh(1)>, L<hivexregedit(1)>, L<guestfs(3)>,
-L<guestfish(1)>, L<virt-cat(1)>, L<virt-tail(1)>, L<Sys::Guestfs(3)>,
-L<Win::Hivex(3)>, L<Win::Hivex::Regedit(3)>, L<Sys::Virt(3)>,
-L<http://libguestfs.org/>.
-
-=head1 АВТОР
-
-Richard W.M. Jones L<http://people.redhat.com/~rjones/>
-
-=head1 АВТОРСЬКІ ПРАВА
-
-©Red Hat Inc., 2010
-
# libguestfs
-# Copyright (C) 2009-2020 Red Hat Inc.
+# Copyright (C) 2009-2021 Red Hat Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
$(DOMAIN).pot: Makefile POTFILES $(POTFILES) POTFILES-pl $(POTFILES_PL) POTFILES-ml $(POTFILES_ML)
rm -f $@-t
touch $@-t
-if HAVE_OCAML_GETTEXT
+if HAVE_OCAML_PKG_GETTEXT
cd $(top_srcdir) && $(OCAML_GETTEXT) --action extract --extract-pot $(abs_srcdir)/$@-t $(shell cat $(abs_srcdir)/POTFILES-ml)
\
$(FIX_CHARSET) $@-t
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
@SET_MAKE@
# libguestfs
-# Copyright (C) 2009-2020 Red Hat Inc.
+# Copyright (C) 2009-2021 Red Hat Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
@HAVE_GNU_GETTEXT_TRUE@$(DOMAIN).pot: Makefile POTFILES $(POTFILES) POTFILES-pl $(POTFILES_PL) POTFILES-ml $(POTFILES_ML)
@HAVE_GNU_GETTEXT_TRUE@ rm -f $@-t
@HAVE_GNU_GETTEXT_TRUE@ touch $@-t
-@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_GETTEXT_TRUE@ cd $(top_srcdir) && $(OCAML_GETTEXT) --action extract --extract-pot $(abs_srcdir)/$@-t $(shell cat $(abs_srcdir)/POTFILES-ml)
-@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_GETTEXT_TRUE@ \
-@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_GETTEXT_TRUE@ $(FIX_CHARSET) $@-t
+@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_PKG_GETTEXT_TRUE@ cd $(top_srcdir) && $(OCAML_GETTEXT) --action extract --extract-pot $(abs_srcdir)/$@-t $(shell cat $(abs_srcdir)/POTFILES-ml)
+@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_PKG_GETTEXT_TRUE@ \
+@HAVE_GNU_GETTEXT_TRUE@@HAVE_OCAML_PKG_GETTEXT_TRUE@ $(FIX_CHARSET) $@-t
@HAVE_GNU_GETTEXT_TRUE@ $(XGETTEXT) -j -o $@-t $(XGETTEXT_ARGS) \
@HAVE_GNU_GETTEXT_TRUE@ --files-from=$(abs_srcdir)/POTFILES
@HAVE_GNU_GETTEXT_TRUE@ $(FIX_CHARSET) $@-t
common/mltools/checksums.ml
common/mltools/curl.ml
common/mltools/getopt.ml
+common/mltools/on_exit.ml
common/mltools/planner.ml
common/mltools/regedit.ml
common/mltools/registry.ml
sysprep/sysprep_operation_mail_spool.ml
sysprep/sysprep_operation_net_hostname.ml
sysprep/sysprep_operation_net_hwaddr.ml
+sysprep/sysprep_operation_net_nmconn.ml
sysprep/sysprep_operation_pacct_log.ml
sysprep/sysprep_operation_package_manager_cache.ml
sysprep/sysprep_operation_pam_data.ml
-win-reg/virt-win-reg
+win-reg/virt-win-reg.in
#, fuzzy
msgid ""
msgstr ""
-"Project-Id-Version: guestfs-tools 1.46.1\n"
+"Project-Id-Version: guestfs-tools 1.48.0\n"
"Report-Msgid-Bugs-To: https://bugzilla.redhat.com/enter_bug.cgi?"
"component=libguestfs&product=Virtualization+Tools\n"
-"POT-Creation-Date: 2021-05-08 08:57+0100\n"
+"POT-Creation-Date: 2022-03-14 13:33+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"guest to partition this extra space if you want."
msgstr ""
-#: common/mltools/tools_utils.ml:187
+#: common/mltools/tools_utils.ml:234
msgid "%s"
msgstr ""
"Options:\n"
msgstr ""
-#: customize/customize_run.ml:446 common/mltools/tools_utils.ml:640
+#: customize/customize_run.ml:446 common/mltools/tools_utils.ml:681
msgid "%s (ignored)"
msgstr ""
msgid "%s needed but not found"
msgstr ""
-#: common/mltools/tools_utils.ml:183 common/mltools/tools_utils.ml:155
+#: common/mltools/tools_utils.ml:230 common/mltools/tools_utils.ml:201
msgid "%s: %s"
msgstr ""
-#: common/mltools/tools_utils.ml:185
+#: common/mltools/tools_utils.ml:232
msgid "%s: %s: %s"
msgstr ""
+#: common/mltools/on_exit.ml:77
+msgid ""
+"%s: Exiting on signal %s\n"
+"%!"
+msgstr ""
+
#: resize/resize.ml:706
msgid ""
"%s: This extended partition contains logical partitions which might be "
"read the man page virt-customize(1).\n"
msgstr ""
-#: common/mltools/tools_utils.ml:125
+#: common/mltools/tools_utils.ml:171
msgid "%s: error: %s"
msgstr ""
msgid "%s: no ‘uri’ entry for ‘%s’ in %s, skipping it\n"
msgstr ""
-#: common/mltools/tools_utils.ml:673
+#: common/mltools/tools_utils.ml:714
msgid "%s: operation timed out"
msgstr ""
"virt-resize only supports MBR (DOS) and GPT partition tables."
msgstr ""
-#: common/mltools/tools_utils.ml:144
+#: common/mltools/tools_utils.ml:190
msgid "%s: warning: %s"
msgstr ""
msgid "--check-tmpdir: unknown argument ‘%s’"
msgstr ""
-#: sparsify/copying.ml:69
+#: sparsify/copying.ml:73
msgid ""
"--compress cannot be used for raw output. Remove this option or use --"
"convert qcow2."
msgid "--shrink option given more than once"
msgstr ""
-#: sparsify/copying.ml:89
+#: sparsify/copying.ml:93
msgid ""
"--tmp parameter must point to a directory, block device or prebuilt file"
msgstr ""
-#: sparsify/copying.ml:80
+#: sparsify/copying.ml:84
msgid "--tmp prebuilt:file: %s: file does not exist"
msgstr ""
-#: sparsify/copying.ml:85
+#: sparsify/copying.ml:89
msgid "--tmp prebuilt:file: %s: file does not have backing file"
msgstr ""
-#: sparsify/copying.ml:83
+#: sparsify/copying.ml:87
msgid "--tmp prebuilt:file: %s: file format is not qcow2"
msgstr ""
msgid "Base path of diskimage-builder library"
msgstr ""
-#: sparsify/copying.ml:340
+#: sparsify/copying.ml:344
msgid ""
"Before deleting the old disk, carefully check that the target disk boots and "
"works correctly."
" %s\n"
msgstr ""
-#: sparsify/in_place.ml:119 sparsify/copying.ml:271
+#: sparsify/in_place.ml:124 sparsify/copying.ml:275
msgid "Clearing Linux swap on %s"
msgstr ""
msgid "Create a directory"
msgstr ""
-#: sparsify/copying.ml:145
+#: sparsify/copying.ml:149
msgid "Create overlay device %s to protect source disk"
msgstr ""
-#: sparsify/copying.ml:143
+#: sparsify/copying.ml:147
msgid "Create overlay file in %s to protect source disk"
msgstr ""
msgid "Disable template cache"
msgstr ""
-#: sparsify/in_place.ml:154
+#: sparsify/in_place.ml:159
msgid "Discard space in volgroup %s"
msgstr ""
msgid "Display name: "
msgstr ""
-#: common/mltools/tools_utils.ml:332
+#: common/mltools/tools_utils.ml:384
msgid "Display version and exit"
msgstr ""
msgid "Don’t perform changes"
msgstr ""
-#: common/mltools/tools_utils.ml:336
+#: common/mltools/tools_utils.ml:388
msgid "Don’t print progress messages"
msgstr ""
-#: common/mltools/tools_utils.ml:354
+#: common/mltools/tools_utils.ml:405
msgid "Don’t turn off echo for passphrases"
msgstr ""
msgid "Enable debugging messages"
msgstr ""
-#: common/mltools/tools_utils.ml:333
+#: common/mltools/tools_utils.ml:385
msgid "Enable libguestfs debugging messages"
msgstr ""
msgid "Enable specific operations"
msgstr ""
-#: common/mltools/tools_utils.ml:334
+#: common/mltools/tools_utils.ml:386
msgid "Enable tracing of libguestfs calls"
msgstr ""
msgid "Enable/disable specific operations"
msgstr ""
-#: sparsify/copying.ml:173
+#: sparsify/copying.ml:177
msgid "Examine source disk"
msgstr ""
msgid "Filesystem for the image"
msgstr ""
-#: sparsify/copying.ml:256
+#: sparsify/copying.ml:260
msgid "Fill free space in %s with zero"
msgstr ""
-#: sparsify/copying.ml:304
+#: sparsify/copying.ml:308
msgid "Fill free space in volgroup %s with zero"
msgstr ""
msgid "Identifier: "
msgstr ""
-#: common/mltools/tools_utils.ml:130
+#: common/mltools/tools_utils.ml:176
msgid ""
"If reporting bugs, run %s with debugging enabled and include the complete "
"output:\n"
msgid "Main element for building ramdisks"
msgstr ""
-#: common/mltools/tools_utils.ml:361
+#: common/mltools/tools_utils.ml:411
msgid "Make output machine readable"
msgstr ""
"%s\n"
msgstr ""
+#: sysprep/sysprep_operation_net_nmconn.ml:38
+msgid "On Fedora and Red Hat Enterprise Linux, remove the C<"
+msgstr ""
+
#: sysprep/sysprep_operation_lvm_uuids.ml:45
msgid ""
"On Linux guests that have LVM2 physical volumes (PVs) or volume groups "
msgid "Read customize commands from file"
msgstr ""
-#: common/mltools/tools_utils.ml:355
+#: common/mltools/tools_utils.ml:406
msgid "Read passphrases from stdin"
msgstr ""
msgid "Remove package manager cache"
msgstr ""
+#: sysprep/sysprep_operation_net_nmconn.ml:36
+msgid "Remove system-local NetworkManager connection profiles (keyfiles)"
+msgstr ""
+
#: sysprep/sysprep_operation_tmp_files.ml:50
msgid "Remove temporary files"
msgstr ""
#: resize/resize.ml:1443
msgid ""
"Resize operation completed with no errors. Before deleting the old disk, "
-"carefully check that the resized disk boots and works correctly.\n"
+"carefully check that the resized disk boots and works correctly."
msgstr ""
#: resize/resize.ml:209
msgstr ""
#. customize/customize_cmdline.ml:315
-#. common/mltools/tools_utils.ml:356
+#. common/mltools/tools_utils.ml:407
#. common/mlcustomize/customize_cmdline.ml:470
#. common/mlcustomize/customize_cmdline.ml:344
#. common/mlcustomize/customize_cmdline.ml:315
msgid "Set password crypto"
msgstr ""
+#: common/mltools/tools_utils.ml:415
+msgid "Set program name"
+msgstr ""
+
#: customize/customize_cmdline.ml:320
#: common/mlcustomize/customize_cmdline.ml:320
msgid "Set root password"
msgid "Setting passwords"
msgstr ""
-#: customize/password.ml:110
+#: customize/password.ml:111
msgid "Setting random password of %s to %s"
msgstr ""
msgid "Skip the inclusion of the ‘base’ element"
msgstr ""
-#: sparsify/copying.ml:252
+#: sparsify/copying.ml:256
msgid "Skipping %s, as it is a read-only btrfs snapshot."
msgstr ""
-#: sparsify/copying.ml:254
+#: sparsify/copying.ml:258
msgid "Skipping %s, as it is a read-only device."
msgstr ""
msgid "Source URI: %s\n"
msgstr ""
-#: sparsify/in_place.ml:177
+#: sparsify/in_place.ml:182
msgid "Sparsify in-place operation completed with no errors"
msgstr ""
-#: sparsify/copying.ml:338
+#: sparsify/copying.ml:342
msgid "Sparsify operation completed with no errors."
msgstr ""
-#: common/mltools/tools_utils.ml:356
+#: common/mltools/tools_utils.ml:407
msgid "Specify a LUKS key"
msgstr ""
msgid "There is a surplus of %s."
msgstr ""
-#: sparsify/copying.ml:105
+#: sparsify/copying.ml:109
msgid ""
"There may not be enough free space on %s.\n"
"You may need to set TMPDIR to point to a directory with more free space.\n"
msgid "Total usable space"
msgstr ""
-#: sparsify/in_place.ml:97
+#: sparsify/in_place.ml:102
msgid "Trimming %s"
msgstr ""
msgid "Uploading: %s to %s"
msgstr ""
-#: common/mltools/tools_utils.ml:338
+#: common/mltools/tools_utils.ml:390
msgid "Use ANSI colour sequences even if not tty"
msgstr ""
msgid "Users to remove"
msgstr ""
-#: sparsify/copying.ml:147
+#: sparsify/copying.ml:151
msgid "Using prebuilt file %s as overlay"
msgstr ""
"‘convert’"
msgstr ""
+#: common/mltools/tools_utils.ml:391
+msgid "Wrap log messages even if not tty"
+msgstr ""
+
#: customize/customize_cmdline.ml:442
#: common/mlcustomize/customize_cmdline.ml:442
msgid "Write file"
msgid "Zero filesystem"
msgstr ""
-#: sparsify/in_place.ml:86 sparsify/copying.ml:242
+#: sparsify/in_place.ml:91 sparsify/copying.ml:246
msgid "Zeroing %s"
msgstr ""
msgid "cached"
msgstr ""
-#: sparsify/copying.ml:64
+#: sparsify/copying.ml:68
msgid "cannot detect input disk format; use the --format parameter"
msgstr ""
msgid "disallowed character (%c) in operation name"
msgstr ""
-#: sparsify/in_place.ml:62
+#: sparsify/in_place.ml:67
msgid "discard/trim is not supported"
msgstr ""
msgid "error parsing URI ‘%s’. Look for error messages printed above."
msgstr ""
-#: common/mltools/tools_utils.ml:200
+#: common/mltools/tools_utils.ml:247
msgid "exception: %s"
msgstr ""
"string: %s)"
msgstr ""
-#: sparsify/copying.ml:335
+#: sparsify/copying.ml:339
msgid "external command failed: %s"
msgstr ""
-#: dib/dib.ml:998 common/mltools/tools_utils.ml:382
+#: dib/dib.ml:998 common/mltools/tools_utils.ml:446
msgid "external command ‘%s’ exited with error %d"
msgstr ""
-#: common/mltools/tools_utils.ml:463 common/mltools/tools_utils.ml:384
+#: common/mltools/tools_utils.ml:527 common/mltools/tools_utils.ml:448
msgid "external command ‘%s’ killed by signal %d"
msgstr ""
-#: common/mltools/tools_utils.ml:465 common/mltools/tools_utils.ml:386
+#: common/mltools/tools_utils.ml:529 common/mltools/tools_utils.ml:450
msgid "external command ‘%s’ stopped by signal %d"
msgstr ""
msgid "failed to sign index"
msgstr ""
-#: common/mltools/tools_utils.ml:191
+#: common/mltools/tools_utils.ml:238
msgid "failure: %s"
msgstr ""
msgid "fs"
msgstr ""
-#: sparsify/in_place.ml:103
+#: sparsify/in_place.ml:108
msgid ""
"fstrim operation is not supported on %s (%s). Suppress this warning using "
"'--ignore %s', or use copying mode instead."
msgstr ""
-#: common/mltools/tools_utils.ml:210
+#: common/mltools/tools_utils.ml:257
msgid "generated by %s %s"
msgstr ""
msgid "input file (%s) has an unsupported type"
msgstr ""
-#: common/mltools/tools_utils.ml:198
+#: common/mltools/tools_utils.ml:245
msgid "internal error: Not_found exception was thrown"
msgstr ""
-#: common/mltools/tools_utils.ml:195
+#: common/mltools/tools_utils.ml:242
msgid "internal error: assertion failed at %s, line %d, char %d"
msgstr ""
-#: common/mltools/tools_utils.ml:193
+#: common/mltools/tools_utils.ml:240
msgid "internal error: invalid argument: %s"
msgstr ""
msgid "invalid format for '--%s' parameter, see the man page"
msgstr ""
-#: common/mltools/tools_utils.ml:308
+#: common/mltools/tools_utils.ml:358
msgid "invalid format string for --machine-readable: %s"
msgstr ""
msgid "invalid format ‘%s’ in --formats"
msgstr ""
-#: common/mltools/tools_utils.ml:323
+#: common/mltools/tools_utils.ml:373
msgid "invalid output fd for --machine-readable: %s"
msgstr ""
-#: common/mltools/tools_utils.ml:325
+#: common/mltools/tools_utils.ml:375
msgid "invalid output for --machine-readable: %s"
msgstr ""
-#: common/mltools/tools_utils.ml:317
+#: common/mltools/tools_utils.ml:367
msgid "invalid output stream for --machine-readable: %s"
msgstr ""
-#: customize/password.ml:71
+#: customize/password.ml:72
msgid "invalid password selector ‘%s’; see the man page"
msgstr ""
-#: common/mltools/tools_utils.ml:351
+#: common/mltools/tools_utils.ml:402
msgid "invalid selector string for --key: %s"
msgstr ""
msgid "invalid ssh-inject selector ‘%s’; see the man page"
msgstr ""
-#: common/mltools/tools_utils.ml:189
+#: common/mltools/tools_utils.ml:236
msgid "libguestfs error: %s"
msgstr ""
msgid "part=size"
msgstr ""
-#: customize/password.ml:50
+#: customize/password.ml:51
msgid ""
-"password-crypto: unknown algorithm %s, use \"md5\", \"sha256\" or \"sha512\""
+"password-crypto: unknown algorithm %s, use \"md5\", \"sha256\", \"sha512\" "
+"or \"yescrypt\""
msgstr ""
-#: customize/password.ml:172
+#: customize/password.ml:192
msgid ""
"password: using insecure md5 password encryption for guest of type %s "
"version %d.%d.\n"
msgid "pvresize"
msgstr ""
-#: sparsify/in_place.ml:128 sparsify/copying.ml:280
+#: sparsify/in_place.ml:133 sparsify/copying.ml:284
msgid "pwrite: short write restoring swap partition header"
msgstr ""
-#: sparsify/in_place.ml:181
+#: sparsify/in_place.ml:186
msgid "quit (^C) at user request"
msgstr ""
"removing ‘--no-network’ or adding ‘--network’ on the command line."
msgstr ""
-#: common/mltools/JSON_parser.ml:76
+#: common/mltools/JSON_parser.ml:81
msgid "the key ‘%s’ was not found in a list of objects"
msgstr ""
msgid "the specified base path is not the diskimage-builder library"
msgstr ""
-#: common/mltools/JSON_parser.ml:70
+#: common/mltools/JSON_parser.ml:75
msgid "the value for key ‘%s’ is not a string as expected"
msgstr ""
+#: common/mltools/JSON_parser.ml:47
+msgid "the value for the key ‘%s’ is not a bool"
+msgstr ""
+
#: common/mltools/JSON_parser.ml:42
msgid "the value for the key ‘%s’ is not a string"
msgstr ""
-#: common/mltools/JSON_parser.ml:62
+#: common/mltools/JSON_parser.ml:67
msgid "the value for the key ‘%s’ is not an integer"
msgstr ""
-#: common/mltools/JSON_parser.ml:47
+#: common/mltools/JSON_parser.ml:52
msgid "the value for the key ‘%s’ is not an object"
msgstr ""
-#: common/mltools/JSON_parser.ml:51
+#: common/mltools/JSON_parser.ml:56
msgid "the value is not an object"
msgstr ""
msgid "‘xz’ command failed"
msgstr ""
-#: align/scan.c:81 cat/cat.c:60 cat/filesystems.c:93 cat/log.c:70 cat/ls.c:98
-#: cat/tail.c:68 df/main.c:73 diff/diff.c:106 edit/edit.c:68
-#: inspector/inspector.c:85 make-fs/make-fs.c:83
+#: align/scan.c:80 cat/cat.c:59 cat/filesystems.c:92 cat/log.c:69 cat/ls.c:97
+#: cat/tail.c:67 df/main.c:72 diff/diff.c:105 edit/edit.c:67
+#: inspector/inspector.c:84 make-fs/make-fs.c:82
#, c-format
msgid "Try ‘%s --help’ for more information.\n"
msgstr ""
-#: align/scan.c:84
+#: align/scan.c:83
#, c-format
msgid ""
"%s: check alignment of virtual machine partitions\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: align/scan.c:168 builder/index-validate.c:90 cat/cat.c:158
-#: cat/filesystems.c:253 cat/log.c:161 cat/ls.c:256 cat/tail.c:167
-#: df/main.c:170 diff/diff.c:289 edit/edit.c:170 format/format.c:193
-#: inspector/inspector.c:188 make-fs/make-fs.c:158
+#: align/scan.c:167 builder/index-validate.c:90 cat/cat.c:157
+#: cat/filesystems.c:252 cat/log.c:160 cat/ls.c:255 cat/tail.c:166
+#: df/main.c:169 diff/diff.c:288 edit/edit.c:169 format/format.c:192
+#: inspector/inspector.c:187 make-fs/make-fs.c:157
#, c-format
msgid "unknown long option: %s (%d)"
msgstr ""
-#: align/scan.c:186 df/main.c:196
+#: align/scan.c:185 df/main.c:195
#, c-format
msgid "-P option is not numeric"
msgstr ""
-#: align/scan.c:242
+#: align/scan.c:240
#, c-format
msgid "compiled without support for libvirt"
msgstr ""
-#: align/scan.c:246
+#: align/scan.c:244
#, c-format
msgid "--uuid option cannot be used with -a or -d"
msgstr ""
-#: align/scan.c:345
+#: align/scan.c:343
msgid "alignment < 4K"
msgstr ""
-#: align/scan.c:348
+#: align/scan.c:346
msgid "alignment < 64K"
msgstr ""
"builder 1.24.0"
msgstr ""
-#: cat/cat.c:63
+#: cat/cat.c:62
#, c-format
msgid ""
"%s: display files in a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: cat/cat.c:247 cat/filesystems.c:351 cat/log.c:219 cat/ls.c:371
-#: cat/tail.c:233 diff/diff.c:343 edit/edit.c:271 inspector/inspector.c:289
+#: cat/cat.c:245 cat/filesystems.c:349 cat/log.c:217 cat/ls.c:369
+#: cat/tail.c:231 diff/diff.c:342 edit/edit.c:269 inspector/inspector.c:287
#, c-format
msgid "%s: error: you must specify at least one -a or -d option.\n"
msgstr ""
-#: cat/filesystems.c:96
+#: cat/filesystems.c:95
#, c-format
msgid ""
"%s: list filesystems, partitions, block devices, LVM in a VM\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: cat/filesystems.c:307 cat/log.c:207 inspector/inspector.c:264
+#: cat/filesystems.c:305 cat/log.c:205 inspector/inspector.c:262
#, c-format
msgid ""
"%s: error: extra argument ‘%s’ on command line.\n"
"Make sure to specify the argument for --format like '--format=%s'.\n"
msgstr ""
-#: cat/filesystems.c:322 cat/ls.c:363 df/main.c:268 diff/diff.c:357
+#: cat/filesystems.c:320 cat/ls.c:361 df/main.c:266 diff/diff.c:356
#, c-format
msgid "you cannot use -h and --csv options together."
msgstr ""
-#: cat/filesystems.c:500
+#: cat/filesystems.c:498
#, c-format
msgid "%s: cannot determine the subvolume for %s: %s: %s\n"
msgstr ""
-#: cat/log.c:73
+#: cat/log.c:72
#, c-format
msgid ""
"%s: display log files in a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: cat/log.c:272
+#: cat/log.c:270
#, c-format
msgid "%s: Windows Event Log for pre-Vista guests is not supported.\n"
msgstr ""
-#: cat/log.c:380
+#: cat/log.c:378
#, c-format
msgid "%s: could not format journal entry timestamp\n"
msgstr ""
-#: cat/log.c:446
+#: cat/log.c:444
#, c-format
msgid ""
"%s: you need to install ‘evtxdump.py’ (from the python-evtx package)\n"
"from this guest, and examine in a binary file viewer.\n"
msgstr ""
-#: cat/log.c:465
+#: cat/log.c:463
#, c-format
msgid "%s: Windows Event Log file (%s) not found\n"
msgstr ""
-#: cat/ls.c:101
+#: cat/ls.c:100
#, c-format
msgid ""
"%s: list files in a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: cat/ls.c:356
+#: cat/ls.c:354
#, c-format
msgid ""
"used a flag which can only be combined with -lR mode\n"
"For more information, read the virt-ls(1) man page."
msgstr ""
-#: cat/tail.c:71
+#: cat/tail.c:70
#, c-format
msgid ""
"%s: follow (tail) files in a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: cat/tail.c:222
+#: cat/tail.c:220
#, c-format
msgid ""
"%s: error: missing filenames on command line.\n"
"Please specify at least one file to follow.\n"
msgstr ""
-#: cat/tail.c:426
+#: cat/tail.c:424
#, c-format
msgid "%s: error: none of the files were found in the disk image\n"
msgstr ""
-#: cat/tail.c:431
+#: cat/tail.c:429
#, c-format
msgid "%s: all files deleted, exiting\n"
msgstr ""
msgid "%s: line %d: error parsing configuration file: %s"
msgstr ""
-#: common/options/decrypt.c:122
+#: common/options/decrypt.c:48
+#, c-format
+msgid "string size overflow"
+msgstr ""
+
+#: common/options/decrypt.c:170
#, c-format
msgid ""
"could not find key to open LUKS encrypted %s.\n"
"Original error: %s (%d)"
msgstr ""
-#: common/options/inspect.c:71
-#, c-format
-msgid "don’t use --live and -i options together"
-msgstr ""
-
-#: common/options/inspect.c:81
+#: common/options/inspect.c:78
#, c-format
msgid ""
"%s: no operating system was found on this disk\n"
"(see the virt tool manual page).\n"
msgstr ""
-#: common/options/inspect.c:102
+#: common/options/inspect.c:99
#, c-format
msgid ""
"%s: multi-boot operating systems are not supported\n"
"(see the virt tool manual page).\n"
msgstr ""
-#: common/options/inspect.c:164
+#: common/options/inspect.c:161
#, c-format
msgid "%s: some filesystems could not be mounted (ignored)\n"
msgstr ""
-#: common/options/inspect.c:181
+#: common/options/inspect.c:178
#, c-format
msgid "Operating system: %s\n"
msgstr ""
-#: common/options/inspect.c:199
+#: common/options/inspect.c:196
#, c-format
msgid "%s mounted on %s\n"
msgstr ""
msgid "drive '%c:' not found."
msgstr ""
-#: df/main.c:76
+#: df/main.c:75
#, c-format
msgid ""
"%s: display free space on virtual filesystems\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: df/main.c:283
+#: df/main.c:281
#, c-format
msgid "compiled without support for libvirt."
msgstr ""
msgid "IUse%"
msgstr ""
-#: diff/diff.c:109
+#: diff/diff.c:108
#, c-format
msgid ""
"%s: list differences between virtual machines\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: diff/diff.c:348
+#: diff/diff.c:347
#, c-format
msgid "%s: error: you must specify at least one -A or -D option.\n"
msgstr ""
-#: diff/diff.c:360
+#: diff/diff.c:359
#, c-format
msgid ""
"%s: error: extra argument ‘%s’ on command line.\n"
-"Make sure to specify the argument for --checksum or --format like '--format="
-"%s'.\n"
+"Make sure to specify the argument for --checksum or --format like '--"
+"format=%s'.\n"
msgstr ""
-#: diff/diff.c:769
+#: diff/diff.c:767
#, c-format
msgid "%s: external diff command failed\n"
msgstr ""
-#: diff/diff.c:773
+#: diff/diff.c:771
msgid "End of diff"
msgstr ""
-#: edit/edit.c:71
+#: edit/edit.c:70
#, c-format
msgid ""
"%s: Edit a file in a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: edit/edit.c:180
+#: edit/edit.c:179
#, c-format
msgid "-b option given multiple times"
msgstr ""
-#: edit/edit.c:194
+#: edit/edit.c:193
#, c-format
msgid "-e option given multiple times"
msgstr ""
-#: format/format.c:69
+#: format/format.c:68
msgid "IMPORTANT NOTE: This program ERASES ALL DATA on disks."
msgstr ""
-#: format/format.c:72
+#: format/format.c:71
#, c-format
msgid ""
"Try ‘%s --help’ for more information.\n"
"%s\n"
msgstr ""
-#: format/format.c:75
+#: format/format.c:74
#, c-format
msgid ""
"%s: erase and make a blank disk\n"
"\n"
msgstr ""
-#: format/format.c:163
+#: format/format.c:162
#, c-format
msgid "no filesystem was specified"
msgstr ""
-#: format/format.c:169
+#: format/format.c:168
#, c-format
msgid "--lvm option cannot be given multiple times"
msgstr ""
-#: format/format.c:236
+#: format/format.c:234
#, c-format
msgid ""
"%s: error: extra argument ‘%s’ on command line.\n"
"format=%s'.\n"
msgstr ""
-#: format/format.c:248
+#: format/format.c:246
#, c-format
msgid "%s: error: you must specify at least one -a option.\n"
msgstr ""
-#: format/format.c:290
+#: format/format.c:288
#, c-format
msgid ""
"failed to rescan the disks after two attempts. This\n"
"is a bug, please file a bug at http://libguestfs.org/\n"
msgstr ""
-#: format/format.c:328
+#: format/format.c:326
#, c-format
msgid "cannot parse --lvm option (%s)"
msgstr ""
-#: inspector/inspector.c:88
+#: inspector/inspector.c:87
#, c-format
msgid ""
"%s: display information about a virtual machine\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: inspector/inspector.c:280
+#: inspector/inspector.c:278
#, c-format
msgid "cannot use --xpath together with other options."
msgstr ""
-#: inspector/inspector.c:317
+#: inspector/inspector.c:315
#, c-format
msgid ""
"no operating system could be detected inside this disk image.\n"
"information about the disk image as possible.\n"
msgstr ""
-#: inspector/inspector.c:333
+#: inspector/inspector.c:331
#, c-format
msgid "xmlOutputBufferCreateFd: failed to open stdout"
msgstr ""
-#: inspector/inspector.c:339
+#: inspector/inspector.c:337
#, c-format
msgid "xmlNewTextWriter: failed to create libxml2 writer"
msgstr ""
-#: inspector/inspector.c:711
+#: inspector/inspector.c:709
#, c-format
msgid "unable to parse XML from stdin"
msgstr ""
-#: inspector/inspector.c:715
+#: inspector/inspector.c:713
#, c-format
msgid "unable to create new XPath context"
msgstr ""
-#: inspector/inspector.c:719
+#: inspector/inspector.c:717
#, c-format
msgid "unable to evaluate XPath expression"
msgstr ""
-#: inspector/inspector.c:730
+#: inspector/inspector.c:728
#, c-format
msgid "xmlSaveToFd failed"
msgstr ""
-#: inspector/inspector.c:735
+#: inspector/inspector.c:733
#, c-format
msgid "xmlNewDoc failed"
msgstr ""
-#: inspector/inspector.c:738
+#: inspector/inspector.c:736
#, c-format
msgid "xmlCopyNode failed"
msgstr ""
-#: inspector/inspector.c:743
+#: inspector/inspector.c:741
#, c-format
msgid "xmlSaveDoc failed"
msgstr ""
-#: make-fs/make-fs.c:86
+#: make-fs/make-fs.c:85
#, c-format
msgid ""
"%s: make a filesystem from a tar archive or files\n"
"For more information, see the manpage %s(1).\n"
msgstr ""
-#: make-fs/make-fs.c:155
+#: make-fs/make-fs.c:154
#, c-format
msgid "--blocksize option is not numeric"
msgstr ""
-#: make-fs/make-fs.c:196
+#: make-fs/make-fs.c:195
#, c-format
msgid "%s: missing input and output arguments on the command line\n"
msgstr ""
-#: make-fs/make-fs.c:215
+#: make-fs/make-fs.c:214
#, c-format
msgid "%s: NTFS support was disabled when libguestfs was compiled\n"
msgstr ""
-#: make-fs/make-fs.c:265 make-fs/make-fs.c:329
+#: make-fs/make-fs.c:264 make-fs/make-fs.c:328
#, c-format
msgid "%s: %s command failed\n"
msgstr ""
-#: make-fs/make-fs.c:454
+#: make-fs/make-fs.c:453
#, c-format
msgid "%s: cannot parse the output of ‘du’ command: %s\n"
msgstr ""
-#: make-fs/make-fs.c:489
+#: make-fs/make-fs.c:488
#, c-format
msgid ""
"%s: %s: input is not a directory, tar archive or compressed tar archive\n"
msgstr ""
-#: make-fs/make-fs.c:520
+#: make-fs/make-fs.c:519
#, c-format
msgid "%s: %s: unknown compressed input format (%s)\n"
msgstr ""
-#: make-fs/make-fs.c:643
+#: make-fs/make-fs.c:642
#, c-format
msgid "%s: %s: invalid size parameter ‘%s’ (%s returned %u)\n"
msgstr ""
-#: make-fs/make-fs.c:869
+#: make-fs/make-fs.c:868
#, c-format
msgid "%s: subprocess failed\n"
msgstr ""
-#: win-reg/virt-win-reg:260
+#: win-reg/virt-win-reg.in:261
msgid "no libvirt domain name or disk image given\n"
msgstr ""
-#: win-reg/virt-win-reg:316
+#: win-reg/virt-win-reg.in:317
#, perl-brace-format
msgid ""
"{prog}: No operating system could be detected inside this disk image.\n"
"information about the disk image as possible.\n"
msgstr ""
-#: win-reg/virt-win-reg:320
+#: win-reg/virt-win-reg.in:321
#, perl-brace-format
msgid "{prog}: multiboot operating systems are not supported.\n"
msgstr ""
-#: win-reg/virt-win-reg:342
+#: win-reg/virt-win-reg.in:343
msgid ""
"expecting 1 or 2 more parameters, subkey path and optionally the value to "
"export\n"
msgstr ""
-#: win-reg/virt-win-reg:502
+#: win-reg/virt-win-reg.in:503
#, perl-brace-format
msgid "virt-win-reg: {p}: cannot find user directory\n"
msgstr ""
-#: win-reg/virt-win-reg:507
+#: win-reg/virt-win-reg.in:508
#, perl-brace-format
msgid "virt-win-reg: {p}: not a supported Windows Registry path\n"
msgstr ""
-#: win-reg/virt-win-reg:580
+#: win-reg/virt-win-reg.in:581
#, perl-brace-format
msgid "virt-win-reg: {p}: could not download registry file: {err}\n"
msgstr ""
-#: win-reg/virt-win-reg:597
+#: win-reg/virt-win-reg.in:598
#, perl-brace-format
msgid "virt-win-reg: {p}: could not upload registry file: {err}\n"
msgstr ""
-lutils \
$(LIBTINFO_LIBS) \
$(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBINTL) \
-lgnu
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBTINFO_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBINTL) \
@HAVE_OCAML_TRUE@ -lgnu
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
""
) in
- wrap (text ^ "\n\n") in
+ info "%s" (text ^ "\n") in
List.iter print_summary partitions;
""
) in
- wrap (text ^ "\n\n")
+ info "%s" (text ^ "\n")
) lvs;
if surplus > 0L then (
) else
s_" The surplus space will be ignored. Run a partitioning program in the guest to partition this extra space if you want." in
- wrap (text ^ "\n\n")
+ info "%s" (text ^ "\n")
);
printf "**********\n";
if not (quiet ()) then (
print_newline ();
- wrap (s_"Resize operation completed with no errors. Before deleting the old disk, carefully check that the resized disk boots and works correctly.\n");
+ info "%s" (s_"Resize operation completed with no errors. Before deleting \
+ the old disk, carefully check that the resized disk boots and \
+ works correctly.");
)
let () = run_main_and_handle_errors main
$expand = 1;
}
my $source_format = "raw";
-if ($backend ne "uml" && rand () < 0.2) {
+if (rand () < 0.2) {
$source_format = "qcow2";
}
my $target_format = "raw";
-if ($backend ne "uml" && rand () < 0.2) {
+if (rand () < 0.2) {
$target_format = "qcow2";
}
my $no_extra_partition = 0;
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
-lutils \
$(LIBTINFO_LIBS) \
$(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBINTL) \
-lgnu
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
@HAVE_OCAML_TRUE@ -lutils \
@HAVE_OCAML_TRUE@ $(LIBTINFO_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBINTL) \
@HAVE_OCAML_TRUE@ -lgnu
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
* need to catch SIGINT (^C) and exit cleanly so the temporary file
* goes away. Note that we don't delete temporaries in the signal
* handler.
+ *
+ * To safely set a signal handler, we must call [On_exit.register]
+ * because that may register signal handlers which we override.
*)
+ On_exit.register ();
let do_sigint _ = exit 1 in
Sys.set_signal Sys.sigint (Sys.Signal_handle do_sigint);
match tmp_place with
| Directory temp_dir ->
let tmp = Filename.temp_file ~temp_dir "sparsify" ".qcow2" in
- unlink_on_exit tmp;
+ On_exit.unlink tmp;
create tmp;
tmp
(* Connect to libguestfs. *)
let g = open_guestfs () in
- (* Capture ^C and clean up gracefully. *)
+ (* Capture ^C and clean up gracefully.
+ *
+ * To safely set a signal handler, we must call [On_exit.register]
+ * because that may register signal handlers which we override.
+ *)
+ On_exit.register ();
let quit = ref false in
let set_quit _ = quit := true in
Sys.set_signal Sys.sigint (Sys.Signal_handle set_quit);
$TEST_FUNCTIONS
skip_if_skipped
-# UML does not support discard.
-skip_if_backend uml
skip_unless_filesystem_available minix
img=test-virt-sparsify-in-place-fstrim-unsupported.img
$TEST_FUNCTIONS
skip_if_skipped
-# UML does not support discard.
-skip_if_backend uml
rm -f test-virt-sparsify-in-place.img
$TEST_FUNCTIONS
skip_if_skipped
-# UML does not support qcow2.
-skip_if_backend uml
rm -f test-virt-sparsify-1.img test-virt-sparsify-2.img
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
mail_spool \
net_hostname \
net_hwaddr \
+ net_nmconn \
pacct_log \
package_manager_cache \
pam_data \
$(LIBTINFO_LIBS) \
$(LIBCRYPT_LIBS) \
$(LIBXML2_LIBS) \
+ $(LIBGUESTFS_LIBS) \
$(LIBINTL) \
-lgnu
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
am__tty_colors_dummy = \
mgn= red= grn= lgn= blu= brg= std=; \
am__color_tests=no
bases='$(TEST_LOGS)'; \
bases=`for i in $$bases; do echo $$i; done | sed 's/\.log$$//'`; \
bases=`echo $$bases`
+AM_TESTSUITE_SUMMARY_HEADER = ' for $(PACKAGE_STRING)'
RECHECK_LOGS = $(TEST_LOGS)
AM_RECURSIVE_TARGETS = check recheck
TEST_SUITE_LOG = test-suite.log
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
mail_spool \
net_hostname \
net_hwaddr \
+ net_nmconn \
pacct_log \
package_manager_cache \
pam_data \
@HAVE_OCAML_TRUE@ $(LIBTINFO_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBCRYPT_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBXML2_LIBS) \
+@HAVE_OCAML_TRUE@ $(LIBGUESTFS_LIBS) \
@HAVE_OCAML_TRUE@ $(LIBINTL) \
@HAVE_OCAML_TRUE@ -lgnu
test x"$$VERBOSE" = x || cat $(TEST_SUITE_LOG); \
fi; \
echo "$${col}$$br$${std}"; \
- echo "$${col}Testsuite summary for $(PACKAGE_STRING)$${std}"; \
+ echo "$${col}Testsuite summary"$(AM_TESTSUITE_SUMMARY_HEADER)"$${std}"; \
echo "$${col}$$br$${std}"; \
create_testsuite_report --maybe-color; \
echo "$$col$$br$$std"; \
@am__EXEEXT_TRUE@ --log-file $$b.log --trs-file $$b.trs \
@am__EXEEXT_TRUE@ $(am__common_driver_flags) $(AM_TEST_LOG_DRIVER_FLAGS) $(TEST_LOG_DRIVER_FLAGS) -- $(TEST_LOG_COMPILE) \
@am__EXEEXT_TRUE@ "$$tst" $(AM_TESTS_FD_REDIRECT)
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
--- /dev/null
+(* virt-sysprep
+ * Copyright (C) 2012-2021 Red Hat Inc.
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program 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 General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License along
+ * with this program; if not, write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ *)
+
+open Common_gettext.Gettext
+open Sysprep_operation
+
+let glob = "/etc/NetworkManager/system-connections/*.nmconnection"
+
+let net_nmconn_perform (g : Guestfs.guestfs) root side_effects =
+ let typ = g#inspect_get_type root in
+ let distro = g#inspect_get_distro root in
+ match typ, distro with
+ | "linux", ("fedora"|"rhel"|"centos"|"scientificlinux"|"oraclelinux"|
+ "redhat-based") -> Array.iter g#rm_f (g#glob_expand glob)
+ | _ -> ()
+
+let op = {
+ defaults with
+ name = "net-nmconn";
+ enabled_by_default = true;
+ heading = s_"Remove system-local NetworkManager connection profiles \
+ (keyfiles)";
+ pod_description = Some (s_"On Fedora and Red Hat Enterprise Linux, remove \
+ the C<" ^ glob ^ "> files.");
+ perform_on_filesystems = Some net_nmconn_perform;
+}
+
+let () = register_operation op
--- /dev/null
+(* This file is generated by Makefile.am. *)
+(* Nothing is exported from operation modules. *)
$TEST_FUNCTIONS
skip_if_skipped
-# UML does not support qcow2.
-skip_if_backend uml
skip_unless_phony_guest fedora.img
f=$top_builddir/test-data/phony-guests/fedora.img
$TEST_FUNCTIONS
skip_if_skipped
-# UML backend does not support qcow2.
-skip_if_backend uml
skip_unless_phony_guest fedora.img
f=$top_builddir/test-data/phony-guests/fedora.img
Display version number and exit.
+=item B<--wrap>
+
+Wrap error, warning, and informative messages. This is the default
+when the output is a tty. If the output of the program is redirected
+to a file, wrapping is disabled unless you use this option.
+
=item B<-x>
Enable tracing of libguestfs API calls.
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
unique=`for i in $$list; do \
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | $(am__uniquify_input)`
-ETAGS = etags
-CTAGS = ctags
DIST_SUBDIRS = $(SUBDIRS)
am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/common-rules.mk \
$(top_srcdir)/subdir-rules.mk
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
distclean-tags:
-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
fedora-md1.img \
fedora-md2.img \
fedora-btrfs.img \
- fedora-luks.img \
+ fedora-luks-on-lvm.img \
+ fedora-lvm-on-luks.img \
ubuntu.img \
archlinux.img \
coreos.img \
fedora.db
SRCDIR=$(srcdir) LAYOUT=btrfs $(top_builddir)/run --test ./$<
-# Make a (dummy) Fedora image with LVM encrypted with LUKS.
-fedora-luks.img: make-fedora-img.pl \
+# Make a (dummy) Fedora image with LUKS-on-LVM.
+fedora-luks-on-lvm.img: make-fedora-img.pl \
fedora-journal.tar.xz \
fedora.db
- SRCDIR=$(srcdir) LAYOUT=lvm-luks $(top_builddir)/run --test ./$<
+ SRCDIR=$(srcdir) LAYOUT=luks-on-lvm $(top_builddir)/run --test ./$<
+
+# Make a (dummy) Fedora image with LVM-on-LUKS.
+fedora-lvm-on-luks.img: make-fedora-img.pl \
+ fedora-journal.tar.xz \
+ fedora.db
+ SRCDIR=$(srcdir) LAYOUT=lvm-on-luks $(top_builddir)/run --test ./$<
# Make a (dummy) Debian image.
debian.img: make-debian-img.sh
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
fedora-md1.img \
fedora-md2.img \
fedora-btrfs.img \
- fedora-luks.img \
+ fedora-luks-on-lvm.img \
+ fedora-lvm-on-luks.img \
ubuntu.img \
archlinux.img \
coreos.img \
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
fedora.db
SRCDIR=$(srcdir) LAYOUT=btrfs $(top_builddir)/run --test ./$<
-# Make a (dummy) Fedora image with LVM encrypted with LUKS.
-fedora-luks.img: make-fedora-img.pl \
+# Make a (dummy) Fedora image with LUKS-on-LVM.
+fedora-luks-on-lvm.img: make-fedora-img.pl \
+ fedora-journal.tar.xz \
+ fedora.db
+ SRCDIR=$(srcdir) LAYOUT=luks-on-lvm $(top_builddir)/run --test ./$<
+
+# Make a (dummy) Fedora image with LVM-on-LUKS.
+fedora-lvm-on-luks.img: make-fedora-img.pl \
fedora-journal.tar.xz \
fedora.db
- SRCDIR=$(srcdir) LAYOUT=lvm-luks $(top_builddir)/run --test ./$<
+ SRCDIR=$(srcdir) LAYOUT=lvm-on-luks $(top_builddir)/run --test ./$<
# Make a (dummy) Debian image.
debian.img: make-debian-img.sh
</devices>
</domain>
+ <!-- LUKS passwords are 'FEDORA-Root', 'FEDORA-LV1', 'FEDORA-LV2',
+ 'FEDORA-LV3' -->
+ <domain type='test'>
+ <name>fedora-luks-on-lvm</name>
+ <memory>1048576</memory>
+ <os>
+ <type>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <devices>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='raw'/>
+ <source file='@abs_builddir@/fedora-luks-on-lvm.img'/>
+ <target dev='vda' bus='virtio'/>
+ </disk>
+ </devices>
+ </domain>
+
<!-- LUKS password is 'FEDORA' -->
<domain type='test'>
- <name>fedora-luks</name>
+ <name>fedora-lvm-on-luks</name>
<memory>1048576</memory>
<os>
<type>hvm</type>
<devices>
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
- <source file='@abs_builddir@/fedora-luks.img'/>
+ <source file='@abs_builddir@/fedora-lvm-on-luks.img'/>
<target dev='vda' bus='virtio'/>
</disk>
</devices>
}
}
-elsif ($ENV{LAYOUT} eq 'lvm-luks') {
- push (@images, "fedora-luks.img-t");
+elsif ($ENV{LAYOUT} eq 'lvm-on-luks') {
+ push (@images, "fedora-lvm-on-luks.img-t");
open (my $fstab, '>', "fedora.fstab") or die;
print $fstab <<EOF;
$bootdev = '/dev/sda1';
- $g->disk_create ("fedora-luks.img-t", "raw", $IMAGE_SIZE);
+ $g->disk_create ("fedora-lvm-on-luks.img-t", "raw", $IMAGE_SIZE);
- $g->add_drive ("fedora-luks.img-t", format => "raw");
+ $g->add_drive ("fedora-lvm-on-luks.img-t", format => "raw");
$g->launch ();
$g->part_init ('/dev/sda', 'mbr');
# Put LUKS on the second partition.
$g->luks_format ('/dev/sda2', 'FEDORA', 0);
- $g->luks_open ('/dev/sda2', 'FEDORA', 'luks');
+ $g->cryptsetup_open ('/dev/sda2', 'FEDORA', 'luks');
init_lvm_root ('/dev/mapper/luks');
}
+elsif ($ENV{LAYOUT} eq 'luks-on-lvm') {
+ push (@images, "fedora-luks-on-lvm.img-t");
+
+ open (my $fstab, '>', "fedora.fstab") or die;
+ print $fstab <<EOF;
+LABEL=BOOT /boot ext2 default 0 0
+LABEL=ROOT / ext2 default 0 0
+EOF
+ close ($fstab) or die;
+
+ $bootdev = '/dev/sda1';
+
+ $g->disk_create ("fedora-luks-on-lvm.img-t", "raw", $IMAGE_SIZE);
+
+ $g->add_drive ("fedora-luks-on-lvm.img-t", format => "raw");
+ $g->launch ();
+
+ $g->part_init ('/dev/sda', 'mbr');
+ foreach my $p (@PARTITIONS) {
+ $g->part_add('/dev/sda', @$p);
+ }
+
+ # Create the Volume Group on /dev/sda2.
+ $g->pvcreate ('/dev/sda2');
+ $g->vgcreate ('VG', ['/dev/sda2']);
+ $g->lvcreate ('Root', 'VG', 32);
+ $g->lvcreate ('LV1', 'VG', 32);
+ $g->lvcreate ('LV2', 'VG', 32);
+ $g->lvcreate ('LV3', 'VG', 64);
+
+ # Format each Logical Group as a LUKS device, with a different password.
+ $g->luks_format ('/dev/VG/Root', 'FEDORA-Root', 0);
+ $g->luks_format ('/dev/VG/LV1', 'FEDORA-LV1', 0);
+ $g->luks_format ('/dev/VG/LV2', 'FEDORA-LV2', 0);
+ $g->luks_format ('/dev/VG/LV3', 'FEDORA-LV3', 0);
+
+ # Open the LUKS devices. This creates nodes like /dev/mapper/*-luks.
+ $g->cryptsetup_open ('/dev/VG/Root', 'FEDORA-Root', 'Root-luks');
+ $g->cryptsetup_open ('/dev/VG/LV1', 'FEDORA-LV1', 'LV1-luks');
+ $g->cryptsetup_open ('/dev/VG/LV2', 'FEDORA-LV2', 'LV2-luks');
+ $g->cryptsetup_open ('/dev/VG/LV3', 'FEDORA-LV3', 'LV3-luks');
+
+ # Phony root filesystem.
+ $g->mkfs ('ext2', '/dev/mapper/Root-luks', blocksize => 4096, label => 'ROOT');
+ $g->set_uuid ('/dev/mapper/Root-luks', '01234567-0123-0123-0123-012345678902');
+
+ # Other filesystems, just for testing findfs-label.
+ $g->mkfs ('ext2', '/dev/mapper/LV1-luks', blocksize => 4096, label => 'LV1');
+ $g->mkfs ('ext2', '/dev/mapper/LV2-luks', blocksize => 1024, label => 'LV2');
+ $g->mkfs ('ext2', '/dev/mapper/LV3-luks', blocksize => 2048, label => 'LV3');
+
+ $g->mount ('/dev/mapper/Root-luks', '/');
+}
+
else {
print STDERR "$0: Unknown LAYOUT: ",$ENV{LAYOUT},"\n";
exit 1;
}
# Skip if the current libguestfs backend is $1.
-# eg. skip_if_backend uml
+# eg. skip_if_backend libvirt
skip_if_backend ()
{
local b="$(guestfish get-backend)"
# OCaml, by design, doesn't bother to free the major heap before
# calling exit. Ignore that leak.
{
- ocaml_heap_leak
+ caml_alloc_for_heap
Memcheck:Leak
...
fun:caml_alloc_for_heap
}
-# On the other hand, these seem to be a real bugs in OCaml:
-{
- ocaml_heap_leak_2
- Memcheck:Leak
- fun:malloc
- fun:caml_thread_new_descriptor
- fun:caml_thread_new
-}
-{
- ocaml_heap_leak_3
- Memcheck:Leak
- fun:malloc
- fun:caml_thread_new_descriptor
- fun:caml_thread_initialize
-}
+
+# OCaml caml_stat_* allocations are meant to be "static" so OCaml will
+# never free them by design. See the OCaml manual, chapter
+# "Interfacing C with OCaml".
{
- ocaml_heap_leak_4
+ caml_stat_allocations
Memcheck:Leak
...
- fun:pthread_create*
- ...
- fun:caml_thread_new
-}
-{
- ocaml_heap_leak_5
- Memcheck:Leak
- fun:malloc
- fun:caml_stat_alloc
+ fun:caml_stat_alloc*
}
+
+# Real leak in OCaml 4.13, later fixed:
+# https://github.com/ocaml/ocaml/issues/10698
{
- ocaml_heap_leak_6
+ caml_setup_stack_overflow_detection
Memcheck:Leak
- fun:malloc
...
- fun:caml_build_primitive_table
+ fun:caml_setup_stack_overflow_detection
}
-# Add for OCaml 4.10.
+# Real leak in bytecode programs.
{
- ocaml_heap_leak_7
+ caml_init_atom_table
Memcheck:Leak
- fun:malloc
...
- fun:caml_init_domain
+ fun:caml_init_atom_table
}
+
+# Real leak in bytecode programs.
{
- ocaml_heap_leak_8
+ caml_executable_name
Memcheck:Leak
fun:malloc
...
- fun:caml_init_atom_table
+ fun:caml_executable_name
+ fun:caml_main
}
# The OCaml PCRE.compile function calls pcre_compile2 which allocates
fun:setenv
}
+# These appeared in glibc 2.35.
+# See also nbdkit commit f6409b4137c1aeb97d01eef5753f22033d64bfd4
+{
+ glibc_leak_4
+ Memcheck:Leak
+ ...
+ fun:dlopen@@*
+}
+
# libvirt calls gnutls_global_init but doesn't call the
# corresponding gnutls_global_deinit function because of
# thread-safety issues (in GnuTLS).
...
fun:virFileFindResourceFull
}
+
# RHBZ#1135388
{
libvirt_leak_6
...
fun:testDomainGenerateIfnames
}
+
# Possibly RHBZ#1145649
{
libvirt_leak_7
fun:selabel_close
fun:virSecuritySELinuxSecurityDriverClose
}
+
# RHBZ#1215042
{
libvirt_leak_8
fun:virNetSocketNewConnectUNIX
}
+{
+ libvirt_leak_9
+ Memcheck:Leak
+ ...
+ fun:g_malloc0
+ fun:virClassNew
+ ...
+ fun:virDataTypesOnce
+}
+
# FUSE leaks the per-thread context (although the code looks
# like it attempts to clean it up). In older fuse, it uses
# malloc. In newer fuse it uses calloc.
include $(top_srcdir)/subdir-rules.mk
-EXTRA_DIST = virt-win-reg
-
bin_SCRIPTS = virt-win-reg
# Manual pages and HTML files for the website.
--warning custom \
$<
touch $@
-
-all-local:
- for f in virt-win-reg; do echo win-reg/$$f; done \
- > $(top_srcdir)/po/POTFILES-pl
-# Makefile.in generated by automake 1.16.2 from Makefile.am.
+# Makefile.in generated by automake 1.16.5 from Makefile.am.
# @configure_input@
-# Copyright (C) 1994-2020 Free Software Foundation, Inc.
+# Copyright (C) 1994-2021 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
DIST_COMMON = $(srcdir)/Makefile.am $(am__DIST_COMMON)
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = $(top_builddir)/config.h
-CONFIG_CLEAN_FILES =
+CONFIG_CLEAN_FILES = virt-win-reg
CONFIG_CLEAN_VPATH_FILES =
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
am__vpath_adj = case $$p in \
NROFF = nroff
MANS = $(man_MANS)
am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP)
-am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/common-rules.mk \
- $(top_srcdir)/subdir-rules.mk
+am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/virt-win-reg.in \
+ $(top_srcdir)/common-rules.mk $(top_srcdir)/subdir-rules.mk
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
ACLOCAL = @ACLOCAL@
AMTAR = @AMTAR@
CFLAGS = @CFLAGS@
CPP = @CPP@
CPPFLAGS = @CPPFLAGS@
+CSCOPE = @CSCOPE@
+CTAGS = @CTAGS@
CYGPATH_W = @CYGPATH_W@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EGREP = @EGREP@
+ETAGS = @ETAGS@
EXEEXT = @EXEEXT@
FGREP = @FGREP@
GCC_VISIBILITY_HIDDEN = @GCC_VISIBILITY_HIDDEN@
guestfs_am_v_po4a_translate = $(guestfs_am_v_po4a_translate_@AM_V@)
guestfs_am_v_po4a_translate_ = $(guestfs_am_v_po4a_translate_@AM_DEFAULT_V@)
guestfs_am_v_po4a_translate_0 = @echo " PO4A-T " $@;
-EXTRA_DIST = virt-win-reg
bin_SCRIPTS = virt-win-reg
# Manual pages and HTML files for the website.
$(ACLOCAL_M4): $(am__aclocal_m4_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(am__aclocal_m4_deps):
+virt-win-reg: $(top_builddir)/config.status $(srcdir)/virt-win-reg.in
+ cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
install-binSCRIPTS: $(bin_SCRIPTS)
@$(NORMAL_INSTALL)
@list='$(bin_SCRIPTS)'; test -n "$(bindir)" || list=; \
cscope cscopelist:
-
distdir: $(BUILT_SOURCES)
$(MAKE) $(AM_MAKEFLAGS) distdir-am
done
check-am: all-am
check: check-am
-all-am: Makefile $(SCRIPTS) $(MANS) all-local
+all-am: Makefile $(SCRIPTS) $(MANS)
installdirs:
for dir in "$(DESTDIR)$(bindir)" "$(DESTDIR)$(man1dir)"; do \
test -z "$$dir" || $(MKDIR_P) "$$dir"; \
.MAKE: install-am install-strip
-.PHONY: all all-am all-local check check-am clean clean-generic \
- clean-libtool cscopelist-am ctags-am distclean \
- distclean-generic distclean-libtool distdir dvi dvi-am html \
- html-am info info-am install install-am install-binSCRIPTS \
- install-data install-data-am install-dvi install-dvi-am \
- install-exec install-exec-am install-html install-html-am \
- install-info install-info-am install-man install-man1 \
- install-pdf install-pdf-am install-ps install-ps-am \
- install-strip installcheck installcheck-am installdirs \
- maintainer-clean maintainer-clean-generic mostlyclean \
- mostlyclean-generic mostlyclean-libtool pdf pdf-am ps ps-am \
- tags-am uninstall uninstall-am uninstall-binSCRIPTS \
- uninstall-man uninstall-man1
+.PHONY: all all-am check check-am clean clean-generic clean-libtool \
+ cscopelist-am ctags-am distclean distclean-generic \
+ distclean-libtool distdir dvi dvi-am html html-am info info-am \
+ install install-am install-binSCRIPTS install-data \
+ install-data-am install-dvi install-dvi-am install-exec \
+ install-exec-am install-html install-html-am install-info \
+ install-info-am install-man install-man1 install-pdf \
+ install-pdf-am install-ps install-ps-am install-strip \
+ installcheck installcheck-am installdirs maintainer-clean \
+ maintainer-clean-generic mostlyclean mostlyclean-generic \
+ mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \
+ uninstall-am uninstall-binSCRIPTS uninstall-man uninstall-man1
.PRECIOUS: Makefile
$<
touch $@
-all-local:
- for f in virt-win-reg; do echo win-reg/$$f; done \
- > $(top_srcdir)/po/POTFILES-pl
-
# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
+++ /dev/null
-#!/usr/bin/env perl
-# virt-win-reg
-# Copyright (C) 2010 Red Hat Inc.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program 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 General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-use warnings;
-use strict;
-
-use Sys::Guestfs;
-use Win::Hivex;
-use Win::Hivex::Regedit qw(reg_import reg_export);
-
-use Pod::Usage;
-use Getopt::Long;
-use File::Temp qw/tempdir/;
-use File::Basename;
-use Locale::TextDomain 'libguestfs';
-
-=head1 NAME
-
-virt-win-reg - Export and merge Windows Registry entries from a Windows guest
-
-=head1 SYNOPSIS
-
- virt-win-reg domname 'HKLM\Path\To\Subkey'
-
- virt-win-reg domname 'HKLM\Path\To\Subkey' name
-
- virt-win-reg domname 'HKLM\Path\To\Subkey' @
-
- virt-win-reg --merge domname [input.reg ...]
-
- virt-win-reg [--options] disk.img ... # instead of domname
-
-=head1 WARNING
-
-You must I<not> use C<virt-win-reg> with the I<--merge> option on live
-virtual machines. If you do this, you I<will> get irreversible disk
-corruption in the VM. C<virt-win-reg> tries to stop you from doing
-this, but doesn't catch all cases.
-
-Modifying the Windows Registry is an inherently risky operation. The format
-is deliberately obscure and undocumented, and Registry changes
-can leave the system unbootable. Therefore when using the I<--merge>
-option, make sure you have a reliable backup first.
-
-=head1 DESCRIPTION
-
-This program can export and merge Windows Registry entries from a
-Windows guest.
-
-The first parameter is the libvirt guest name or the raw disk image of
-a Windows guest.
-
-If I<--merge> is I<not> specified, then the chosen registry
-key is displayed/exported (recursively). For example:
-
- $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
-
-You can also display single values from within registry keys,
-for example:
-
- $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
- $ virt-win-reg Windows7 $cvkey ProductName
- Windows 7 Enterprise
-
-With I<--merge>, you can merge a textual regedit file into
-the Windows Registry:
-
- $ virt-win-reg --merge Windows7 changes.reg
-
-=head2 NOTE
-
-This program is only meant for simple access to the registry. If you
-want to do complicated things with the registry, we suggest you
-download the Registry hive files from the guest using L<libguestfs(3)>
-or L<guestfish(1)> and access them locally, eg. using L<hivex(3)>,
-L<hivexsh(1)> or L<hivexregedit(1)>.
-
-=head1 OPTIONS
-
-=over 4
-
-=cut
-
-my $help;
-
-=item B<--help>
-
-Display brief help.
-
-=cut
-
-my $version;
-
-=item B<--version>
-
-Display version number and exit.
-
-=cut
-
-my $debug;
-
-=item B<--debug>
-
-Enable debugging messages.
-
-=cut
-
-my $uri;
-
-=item B<-c URI>
-
-=item B<--connect URI>
-
-If using libvirt, connect to the given I<URI>. If omitted, then we
-connect to the default libvirt hypervisor.
-
-If you specify guest block devices directly, then libvirt is not used
-at all.
-
-=cut
-
-my $format;
-
-=item B<--format> raw
-
-Specify the format of disk images given on the command line. If this
-is omitted then the format is autodetected from the content of the
-disk image.
-
-If disk images are requested from libvirt, then this program asks
-libvirt for this information. In this case, the value of the format
-parameter is ignored.
-
-If working with untrusted raw-format guest disk images, you should
-ensure the format is always specified.
-
-=cut
-
-my $merge;
-
-=item B<--merge>
-
-In merge mode, this merges a textual regedit file into the Windows
-Registry of the virtual machine. If this flag is I<not> given then
-virt-win-reg displays or exports Registry entries instead.
-
-Note that I<--merge> is I<unsafe> to use on live virtual machines, and
-will result in disk corruption. However exporting (without this flag)
-is always safe.
-
-=cut
-
-my $encoding;
-
-=item B<--encoding> UTF-16LE|ASCII
-
-When merging (only), you may need to specify the encoding for strings
-to be used in the hive file. This is explained in detail in
-L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
-
-The default is to use UTF-16LE, which should work with recent versions
-of Windows.
-
-=cut
-
-my $unsafe_printable_strings;
-
-=item B<--unsafe-printable-strings>
-
-When exporting (only), assume strings are UTF-16LE and print them as
-strings instead of hex sequences. Remove the final zero codepoint
-from strings if present.
-
-This is unsafe and does not preserve the fidelity of strings in the
-original Registry for various reasons:
-
-=over 4
-
-=item *
-
-Assumes the original encoding is UTF-16LE. ASCII strings and strings
-in other encodings will be corrupted by this transformation.
-
-=item *
-
-Assumes that everything which has type 1 or 2 is really a string
-and that everything else is not a string, but the type field in
-real Registries is not reliable.
-
-=item *
-
-Loses information about whether a zero codepoint followed the string
-in the Registry or not.
-
-=back
-
-This all happens because the Registry itself contains no information
-about how strings are encoded (see
-L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
-
-You should only use this option for quick hacking and debugging of the
-Registry contents, and I<never> use it if the output is going to be
-passed into another program or stored in another Registry.
-
-=back
-
-=cut
-
-my %opts = ("help|?" => \$help,
- "version" => \$version,
- "connect|c=s" => \$uri,
- "debug|d" => \$debug,
- "format=s" => \$format,
- "merge" => \$merge,
- "encoding=s" => \$encoding,
- "unsafe-printable-strings" => \$unsafe_printable_strings,
- "long-options" => \&display_long_options,
- "short-options" => \&display_short_options);
-GetOptions (%opts) or pod2usage (2);
-pod2usage (1) if $help;
-if ($version) {
- my $g = Sys::Guestfs->new ();
- my %h = $g->version ();
- print "virt-win-reg $h{major}.$h{minor}.$h{release}$h{extra}\n";
- exit
-}
-
-sub display_long_options
-{
- foreach (sort keys %opts) {
- if (m/^(.*?)([\|=].*)?$/ && !/-options$/) { print "--$1\n" }
- }
- exit
-}
-
-sub display_short_options
-{
- foreach (sort keys %opts) {
- if (m/\|(.)/) { print "-$1\n" }
- }
- exit
-}
-
-# virt-win-reg only takes a single disk image ...
-die __"no libvirt domain name or disk image given\n" if @ARGV == 0;
-my $domname_or_image = shift @ARGV;
-
-warn "launching libguestfs ..." if $debug;
-
-my @lib_args = ();
-push @lib_args, readonly => 1 unless $merge;
-push @lib_args, format => $format if defined $format;
-
-my $g = Sys::Guestfs->new ();
-
-# If the parameter looks like a URI, try parsing it using guestfish.
-# This is a massive hack, but we'll fix it when virt-win-reg gets
-# rewritten in C ...
-if ($domname_or_image =~ m|://|) {
- # Whitelist the characters permitted in the URI.
- die "$0: $domname_or_image: URI parameter contains invalid characters"
- unless $domname_or_image =~ m|^[A-Za-z0-9/:#%&*+,-.=?@_~]+$|;
-
- my $cmd = "LANG=C guestfish -a '$domname_or_image' -x exit 2>&1 | grep 'trace: add_drive [^=]'";
- open CMD, "$cmd|" or die "open: $cmd: $!";
- $_ = <CMD>;
- close CMD or die "close: $cmd: $!";
- chomp;
- die "$0: could not parse '$_'"
- unless m/^libguestfs: trace: add_drive "(.*?)"(.*)/;
- my @args = ($1, @lib_args);
- $_ = $2;
- while (/\S/) {
- die "$0: cound not parse remainder from '$_'"
- unless $_ =~ /^\s*"([a-z]+):(.*?)"(.*)/;
- if ($1 ne "server") {
- push @args, $1, $2;
- } else {
- push @args, $1, [$2];
- }
- $_ = $3;
- }
- $g->add_drive (@args);
-}
-# If the parameter looks like a local file:
-elsif (-e $domname_or_image) {
- $g->add_drive ($domname_or_image, @lib_args);
-}
-# Try a libvirt domain name:
-else {
- push @lib_args, libvirturi => $uri if defined $uri;
- $g->add_domain ($domname_or_image, @lib_args);
-}
-
-$g->launch ();
-
-warn "inspecting guest ..." if $debug;
-
-my @roots = $g->inspect_os ();
-if (@roots == 0) {
- die __x("{prog}: No operating system could be detected inside this disk image.\n\nThis may be because the file is not a disk image, or is not a virtual machine\nimage, or because the OS type is not understood by libguestfs.\n\nIf you feel this is an error, please file a bug report including as much\ninformation about the disk image as possible.\n",
- prog => basename ($0));
-}
-if (@roots > 1) {
- die __x("{prog}: multiboot operating systems are not supported.\n",
- prog => basename ($0))
-}
-my %fses = $g->inspect_get_mountpoints ($roots[0]);
-my @fses = sort { length $a <=> length $b } keys %fses;
-my $mountopts = $merge ? "" : "ro";
-foreach (@fses) {
- $g->mount_options ($mountopts, $fses{$_}, $_);
-}
-
-my $systemroot = $g->inspect_get_windows_systemroot ($roots[0]);
-
-# Create a working directory to store the downloaded registry files.
-my $tmpdir = tempdir (CLEANUP => 1);
-
-# Used when merging (only) to map from the downloaded hiveshortname to
-# various properties about the hive. The key is hiveshortname. The
-# value is a hashref containing {h} (hive handle) and {hivefile} (full
-# hive path on the Windows side).
-my %hives;
-
-if (!$merge) { # Export mode.
- die __"expecting 1 or 2 more parameters, subkey path and optionally the value to export\n"
- if @ARGV < 1 || @ARGV > 2;
-
- my $path = shift @ARGV;
- my $name = shift @ARGV; # or undef
-
- # Map this to the hive name. This function dies on failure.
- my ($hiveshortname, $hivefile, $prefix);
- ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($path);
-
- # Download the chosen hive.
- download_hive ($hivefile, $hiveshortname);
-
- # Open it.
- my $h = Win::Hivex->open ("$tmpdir/$hiveshortname",
- unsafe => 1, debug => $debug);
-
- unless ($name) {
- # Export it.
- warn "exporting $path from $hiveshortname with prefix $prefix ..."
- if $debug;
- reg_export ($h, $path, \*STDOUT,
- prefix => $prefix,
- unsafe_printable_strings => $unsafe_printable_strings);
- } else {
- # Export a single key using hivexget.
- my @args = ("hivexget", "$tmpdir/$hiveshortname", $path, $name);
- warn "running ", join (" ", @args), " ..." if $debug;
- system (@args) == 0 or die "hivexget failed: $?"
- }
-}
-else { # Import mode.
- if (@ARGV == 0) {
- reg_import (\*STDIN, \&import_mapper, encoding => $encoding);
- } else {
- foreach (@ARGV) {
- open my $fh, $_ or die "open: $_: $!";
- reg_import ($fh, \&import_mapper, encoding => $encoding);
- }
- }
-
- # Now we've done importing, commit all the hive handles and
- # close them all.
- foreach (values %hives) {
- my $h = $_->{h};
- delete $_->{h};
- $h->commit (undef);
- }
-
- # Upload all the downloaded hives.
- foreach my $hiveshortname (keys %hives) {
- upload_hive ($hiveshortname, $hives{$hiveshortname}->{hivefile})
- }
-
- # Close.
- $g->shutdown ();
- $g->close ();
-}
-
-exit 0;
-
-# map function passed to reg_import.
-sub import_mapper
-{
- local $_ = shift;
-
- my ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($_);
-
- # Need to download this hive?
- unless (-f "$tmpdir/$hiveshortname") {
- download_hive ($hivefile, $hiveshortname);
-
- my $h = Win::Hivex->open ("$tmpdir/$hiveshortname",
- write => 1, debug => $debug);
- my %hash = ( h => $h, hivefile => $hivefile );
- $hives{$hiveshortname} = \%hash;
- }
-
- return ($hives{$hiveshortname}->{h}, $path);
-}
-
-# Given a path, map that to the name of the hive and the true path
-# within that hive.
-sub map_path_to_hive
-{
- local $_ = shift;
- my ($hiveshortname, $hivefile, $path, $prefix);
-
- if (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SAM(\\.*)?$/i) {
- $hiveshortname = "sam";
- $hivefile = "$systemroot/system32/config/$hiveshortname";
- $path = defined $1 ? $1 : "\\";
- $prefix = "HKEY_LOCAL_MACHINE\\SAM";
- }
- elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SECURITY(\\.*)?$/i) {
- $hiveshortname = "security";
- $hivefile = "$systemroot/system32/config/$hiveshortname";
- $path = defined $1 ? $1 : "\\";
- $prefix = "HKEY_LOCAL_MACHINE\\SECURITY";
- }
- elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SOFTWARE(\\.*)?$/i) {
- $hiveshortname = "software";
- $hivefile = "$systemroot/system32/config/$hiveshortname";
- $path = defined $1 ? $1 : "\\";
- $prefix = "HKEY_LOCAL_MACHINE\\SOFTWARE";
- }
- elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SYSTEM(\\.*)?$/i) {
- $hiveshortname = "system";
- $hivefile = "$systemroot/system32/config/$hiveshortname";
- $path = defined $1 ? $1 : "\\";
- $prefix = "HKEY_LOCAL_MACHINE\\SYSTEM";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\.DEFAULT(\\.*)?$/i) {
- $hiveshortname = "default";
- $hivefile = "$systemroot/system32/config/$hiveshortname";
- $path = defined $1 ? $1 : "\\";
- $prefix = "HKEY_LOCAL_MACHINE\\.DEFAULT";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\(S-1-5-[-\d]+)(\\.*)?$/i) {
- my $sid = $1;
- $hiveshortname = $sid;
- $prefix = "HKEY_USERS\\$sid";
- $path = defined $2 ? $2 : "\\";
- # This requires a recursive call to download the SOFTWARE hive.
- $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\LocalSystem(\\.*)?$/i) {
- my $sid = "S-1-5-18";
- $hiveshortname = $sid;
- $prefix = "HKEY_USERS\\$sid";
- $path = defined $1 ? $1 : "\\";
- # This requires a recursive call to download the SOFTWARE hive.
- $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\LocalService(\\.*)?$/i) {
- my $sid = "S-1-5-19";
- $hiveshortname = $sid;
- $prefix = "HKEY_USERS\\$sid";
- $path = defined $1 ? $1 : "\\";
- # This requires a recursive call to download the SOFTWARE hive.
- $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\NetworkService(\\.*)?$/i) {
- my $sid = "S-1-5-20";
- $hiveshortname = $sid;
- $prefix = "HKEY_USERS\\$sid";
- $path = defined $1 ? $1 : "\\";
- # This requires a recursive call to download the SOFTWARE hive.
- $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
- }
- elsif (/^\\?(?:HKEY_USERS|HKU)\\(.*?)(\\.*)?$/i) {
- $hiveshortname = "user_$1";
- $prefix = "HKEY_USERS\\$1";
- $path = defined $2 ? $2 : "\\";
- # XXX We should probably look this up properly.
- if (is_dir_nocase ("/Users/$1")) {
- $hivefile = "/Users/$1/ntuser.dat"
- } elsif (is_dir_nocase ("/Documents and Settings/$1")) {
- $hivefile = "/Documents and Settings/$1/ntuser.dat"
- } else {
- die __x("virt-win-reg: {p}: cannot find user directory\n",
- p => $1)
- }
- }
- else {
- die __x("virt-win-reg: {p}: not a supported Windows Registry path\n",
- p => $_)
- }
-
- return ($hiveshortname, $hivefile, $path, $prefix);
-}
-
-# Given a User SID, consult
-# HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\$sid
-# and return the ProfileImagePath value.
-sub lookup_pip_of_user_sid
-{
- local $_;
- my $sid = shift;
-
- my $path =
- "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList\\".
- $sid;
-
- my ($hiveshortname, $hivefile, $prefix);
- ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($path);
-
- download_hive ($hivefile, $hiveshortname)
- unless -f "$tmpdir/$hiveshortname";
-
- my @args = ("$tmpdir/$hiveshortname", $path, "ProfileImagePath");
- warn "running hivexget ", join (" ", @args), " ..." if $debug;
-
- my $fh;
- open $fh, "-|", "hivexget", @args
- or die "hivexget: see earlier errors: $!";
- $_ = <$fh>;
- close $fh or die "hivexget: see earlier errors: $!";
-
- chomp;
-
- # The contents of the registry are a windows path, possibly
- # containing %systemroot% and %systemdrive% (on Win XP). Expand
- # it and remove some other windows-isms. The caller will do
- # case_sensitive_path for us, so we don't need to do that.
- s/%systemroot%/$systemroot/i;
- s/%systemdrive%//i;
- s/^c://i;
- s,\\,/,g;
-
- $_;
-}
-
-sub is_dir_nocase
-{
- local $_;
- my $dir = shift;
-
- my $windir;
- eval { $windir = $g->case_sensitive_path ($dir); };
- if ($@) {
- return 0;
- }
- return $g->is_dir ($windir);
-}
-
-# Download a named hive file. Die on failure.
-sub download_hive
-{
- local $_;
- my $hivefile = shift;
- my $hiveshortname = shift;
-
- my $winfile = $g->case_sensitive_path ($hivefile);
-
- warn "downloading $winfile ..." if $debug;
- eval { $g->download ($winfile, "$tmpdir/$hiveshortname"); };
- if ($@) {
- die __x("virt-win-reg: {p}: could not download registry file: {err}\n",
- p => $winfile, err => $@);
- }
-}
-
-# Upload a named hive file. Die on failure.
-sub upload_hive
-{
- local $_;
- my $hiveshortname = shift;
- my $hivefile = shift;
-
- my $winfile = $g->case_sensitive_path ($hivefile);
-
- warn "uploading $winfile ..." if $debug;
- eval { $g->upload ("$tmpdir/$hiveshortname", $winfile); };
- if ($@) {
- die __x("virt-win-reg: {p}: could not upload registry file: {err}\n",
- p => $winfile, err => $@);
- }
-}
-
-=head1 SUPPORTED SYSTEMS
-
-The program currently supports Windows NT-derived guests starting with
-Windows XP through to at least Windows 8.
-
-The following Registry keys are supported:
-
-=over 4
-
-=item C<HKEY_LOCAL_MACHINE\SAM>
-
-=item C<HKEY_LOCAL_MACHINE\SECURITY>
-
-=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
-
-=item C<HKEY_LOCAL_MACHINE\SYSTEM>
-
-=item C<HKEY_USERS\.DEFAULT>
-
-=item C<HKEY_USERS\I<SID>>
-
-where I<SID> is a Windows User SID (eg. C<S-1-5-18>).
-
-=item C<HKEY_USERS\I<username>>
-
-where I<username> is a local user name (this is a libguestfs extension).
-
-=back
-
-You can use C<HKLM> as a shorthand for C<HKEY_LOCAL_MACHINE>, and
-C<HKU> for C<HKEY_USERS>.
-
-The literal keys C<HKEY_USERS\$SID> and C<HKEY_CURRENT_USER> are not
-supported (there is no "current user").
-
-=head2 WINDOWS 8
-
-Windows 8 "fast startup" can prevent virt-win-reg from being
-able to edit the Registry. See
-L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
-
-=head1 ENCODING
-
-C<virt-win-reg> expects that regedit files have already been reencoded
-in the local encoding. Usually on Linux hosts, this means UTF-8 with
-Unix-style line endings. Since Windows regedit files are often in
-UTF-16LE with Windows-style line endings, you may need to reencode the
-whole file before or after processing.
-
-To reencode a file from Windows format to Linux (before processing it
-with the I<--merge> option), you would do something like this:
-
- iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
-
-To go in the opposite direction, after exporting and before sending
-the file to a Windows user, do something like this:
-
- unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
-
-For more information about encoding, see L<Win::Hivex::Regedit(3)>.
-
-If you are unsure about the current encoding, use the L<file(1)>
-command. Recent versions of Windows regedit.exe produce a UTF-16LE
-file with Windows-style (CRLF) line endings, like this:
-
- $ file software.reg
- software.reg: Little-endian UTF-16 Unicode text, with very long lines,
- with CRLF line terminators
-
-This file would need conversion before you could I<--merge> it.
-
-=head1 CurrentControlSet etc.
-
-Registry keys like C<CurrentControlSet> don’t really exist in the
-Windows Registry at the level of the hive file, and therefore you
-cannot modify these.
-
-C<CurrentControlSet> is usually an alias for C<ControlSet001>. In
-some circumstances it might refer to another control set. The way
-to find out is to look at the C<HKLM\SYSTEM\Select> key:
-
- # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
- [HKEY_LOCAL_MACHINE\SYSTEM\Select]
- "Current"=dword:00000001
- "Default"=dword:00000001
- "Failed"=dword:00000000
- "LastKnownGood"=dword:00000002
-
-"Current" is the one which Windows will choose when it boots.
-
-Similarly, other C<Current...> keys in the path may need to
-be replaced.
-
-=head1 DELETING REGISTRY KEYS AND VALUES
-
-To delete a whole registry key, use the syntax:
-
- [-HKEY_LOCAL_MACHINE\Foo]
-
-To delete a single value within a key, use the syntax:
-
- [HKEY_LOCAL_MACHINE\Foo]
- "Value"=-
-
-=head1 WINDOWS TIPS
-
-Note that some of these tips modify the guest disk image. The guest
-I<must> be shut off, else you will get disk corruption.
-
-=head2 RUNNING A BATCH SCRIPT WHEN A USER LOGS IN
-
-Prepare a DOS batch script, VBScript or executable. Upload this using
-L<guestfish(1)>. For this example the script is called C<test.bat>
-and it is uploaded into C<C:\>:
-
- guestfish -i -d WindowsGuest upload test.bat /test.bat
-
-Prepare a regedit file containing the registry change:
-
- cat > test.reg <<'EOF'
- [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
- "Test"="c:\\test.bat"
- EOF
-
-In this example we use the key C<RunOnce> which means that the script
-will run precisely once when the first user logs in. If you want it
-to run every time a user logs in, replace C<RunOnce> with C<Run>.
-
-Now update the registry:
-
- virt-win-reg --merge WindowsGuest test.reg
-
-=head2 INSTALLING A SERVICE
-
-This section assumes you are familiar with Windows services, and you
-either have a program which handles the Windows Service Control
-Protocol directly or you want to run any program using a service
-wrapper like SrvAny or the free RHSrvAny.
-
-First upload the program and optionally the service wrapper. In this
-case the test program is called C<test.exe> and we are using the
-RHSrvAny wrapper:
-
- guestfish -i -d WindowsGuest <<EOF
- upload rhsrvany.exe /rhsrvany.exe
- upload test.exe /test.exe
- EOF
-
-Prepare a regedit file containing the registry changes. In this
-example, the first registry change is needed for the service itself or
-the service wrapper (if used). The second registry change is only
-needed because I am using the RHSrvAny service wrapper.
-
- cat > service.reg <<'EOF'
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
- "Type"=dword:00000010
- "Start"=dword:00000002
- "ErrorControl"=dword:00000001
- "ImagePath"="c:\\rhsrvany.exe"
- "DisplayName"="RHSrvAny"
- "ObjectName"="NetworkService"
-
- [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
- "CommandLine"="c:\\test.exe"
- "PWD"="c:\\Temp"
- EOF
-
-Notes:
-
-=over 4
-
-=item *
-
-For use of C<ControlSet001> see the section above in this manual page.
-You may need to adjust this according to the control set that is in
-use by the guest.
-
-=item *
-
-C<"ObjectName"> controls the privileges that the service will have.
-An alternative is C<"ObjectName"="LocalSystem"> which would be the
-most privileged account.
-
-=item *
-
-For the meaning of the magic numbers, see this Microsoft KB article:
-L<http://support.microsoft.com/kb/103000>.
-
-=back
-
-Update the registry:
-
- virt-win-reg --merge WindowsGuest service.reg
-
-=head1 SHELL QUOTING
-
-Be careful when passing parameters containing C<\> (backslash) in the
-shell. Usually you will have to use 'single quotes' or double
-backslashes (but not both) to protect them from the shell.
-
-Paths and value names are case-insensitive.
-
-=head1 SEE ALSO
-
-L<hivex(3)>,
-L<hivexsh(1)>,
-L<hivexregedit(1)>,
-L<guestfs(3)>,
-L<guestfish(1)>,
-L<virt-cat(1)>,
-L<virt-tail(1)>,
-L<Sys::Guestfs(3)>,
-L<Win::Hivex(3)>,
-L<Win::Hivex::Regedit(3)>,
-L<Sys::Virt(3)>,
-L<http://libguestfs.org/>.
-
-=head1 AUTHOR
-
-Richard W.M. Jones L<http://people.redhat.com/~rjones/>
-
-=head1 COPYRIGHT
-
-Copyright (C) 2010 Red Hat Inc.
--- /dev/null
+#!/usr/bin/env perl
+# virt-win-reg
+# Copyright (C) 2010-2021 Red Hat Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program 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 General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+use warnings;
+use strict;
+
+use Sys::Guestfs;
+use Win::Hivex;
+use Win::Hivex::Regedit qw(reg_import reg_export);
+
+use Pod::Usage;
+use Getopt::Long;
+use File::Temp qw/tempdir/;
+use File::Basename;
+use Locale::TextDomain 'libguestfs';
+
+=head1 NAME
+
+virt-win-reg - Export and merge Windows Registry entries from a Windows guest
+
+=head1 SYNOPSIS
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey'
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey' name
+
+ virt-win-reg domname 'HKLM\Path\To\Subkey' @
+
+ virt-win-reg --merge domname [input.reg ...]
+
+ virt-win-reg [--options] disk.img ... # instead of domname
+
+=head1 WARNING
+
+You must I<not> use C<virt-win-reg> with the I<--merge> option on live
+virtual machines. If you do this, you I<will> get irreversible disk
+corruption in the VM. C<virt-win-reg> tries to stop you from doing
+this, but doesn't catch all cases.
+
+Modifying the Windows Registry is an inherently risky operation. The format
+is deliberately obscure and undocumented, and Registry changes
+can leave the system unbootable. Therefore when using the I<--merge>
+option, make sure you have a reliable backup first.
+
+=head1 DESCRIPTION
+
+This program can export and merge Windows Registry entries from a
+Windows guest.
+
+The first parameter is the libvirt guest name or the raw disk image of
+a Windows guest.
+
+If I<--merge> is I<not> specified, then the chosen registry
+key is displayed/exported (recursively). For example:
+
+ $ virt-win-reg Windows7 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft'
+
+You can also display single values from within registry keys,
+for example:
+
+ $ cvkey='HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
+ $ virt-win-reg Windows7 $cvkey ProductName
+ Windows 7 Enterprise
+
+With I<--merge>, you can merge a textual regedit file into
+the Windows Registry:
+
+ $ virt-win-reg --merge Windows7 changes.reg
+
+=head2 NOTE
+
+This program is only meant for simple access to the registry. If you
+want to do complicated things with the registry, we suggest you
+download the Registry hive files from the guest using L<libguestfs(3)>
+or L<guestfish(1)> and access them locally, eg. using L<hivex(3)>,
+L<hivexsh(1)> or L<hivexregedit(1)>.
+
+=head1 OPTIONS
+
+=over 4
+
+=cut
+
+my $help;
+
+=item B<--help>
+
+Display brief help.
+
+=cut
+
+my $version;
+
+=item B<--version>
+
+Display version number and exit.
+
+=cut
+
+my $debug;
+
+=item B<--debug>
+
+Enable debugging messages.
+
+=cut
+
+my $uri;
+
+=item B<-c URI>
+
+=item B<--connect URI>
+
+If using libvirt, connect to the given I<URI>. If omitted, then we
+connect to the default libvirt hypervisor.
+
+If you specify guest block devices directly, then libvirt is not used
+at all.
+
+=cut
+
+my $format;
+
+=item B<--format> raw
+
+Specify the format of disk images given on the command line. If this
+is omitted then the format is autodetected from the content of the
+disk image.
+
+If disk images are requested from libvirt, then this program asks
+libvirt for this information. In this case, the value of the format
+parameter is ignored.
+
+If working with untrusted raw-format guest disk images, you should
+ensure the format is always specified.
+
+=cut
+
+my $merge;
+
+=item B<--merge>
+
+In merge mode, this merges a textual regedit file into the Windows
+Registry of the virtual machine. If this flag is I<not> given then
+virt-win-reg displays or exports Registry entries instead.
+
+Note that I<--merge> is I<unsafe> to use on live virtual machines, and
+will result in disk corruption. However exporting (without this flag)
+is always safe.
+
+=cut
+
+my $encoding;
+
+=item B<--encoding> UTF-16LE|ASCII
+
+When merging (only), you may need to specify the encoding for strings
+to be used in the hive file. This is explained in detail in
+L<Win::Hivex::Regedit(3)/ENCODING STRINGS>.
+
+The default is to use UTF-16LE, which should work with recent versions
+of Windows.
+
+=cut
+
+my $unsafe_printable_strings;
+
+=item B<--unsafe-printable-strings>
+
+When exporting (only), assume strings are UTF-16LE and print them as
+strings instead of hex sequences. Remove the final zero codepoint
+from strings if present.
+
+This is unsafe and does not preserve the fidelity of strings in the
+original Registry for various reasons:
+
+=over 4
+
+=item *
+
+Assumes the original encoding is UTF-16LE. ASCII strings and strings
+in other encodings will be corrupted by this transformation.
+
+=item *
+
+Assumes that everything which has type 1 or 2 is really a string
+and that everything else is not a string, but the type field in
+real Registries is not reliable.
+
+=item *
+
+Loses information about whether a zero codepoint followed the string
+in the Registry or not.
+
+=back
+
+This all happens because the Registry itself contains no information
+about how strings are encoded (see
+L<Win::Hivex::Regedit(3)/ENCODING STRINGS>).
+
+You should only use this option for quick hacking and debugging of the
+Registry contents, and I<never> use it if the output is going to be
+passed into another program or stored in another Registry.
+
+=back
+
+=cut
+
+my %opts = ("help|?" => \$help,
+ "version" => \$version,
+ "connect|c=s" => \$uri,
+ "debug|d" => \$debug,
+ "format=s" => \$format,
+ "merge" => \$merge,
+ "encoding=s" => \$encoding,
+ "unsafe-printable-strings" => \$unsafe_printable_strings,
+ "long-options" => \&display_long_options,
+ "short-options" => \&display_short_options);
+GetOptions (%opts) or pod2usage (2);
+pod2usage (1) if $help;
+if ($version) {
+ print "virt-win-reg @PACKAGE_VERSION@\n";
+ my $g = Sys::Guestfs->new ();
+ my %h = $g->version ();
+ print "libguestfs $h{major}.$h{minor}.$h{release}$h{extra}\n";
+ exit
+}
+
+sub display_long_options
+{
+ foreach (sort keys %opts) {
+ if (m/^(.*?)([\|=].*)?$/ && !/-options$/) { print "--$1\n" }
+ }
+ exit
+}
+
+sub display_short_options
+{
+ foreach (sort keys %opts) {
+ if (m/\|(.)/) { print "-$1\n" }
+ }
+ exit
+}
+
+# virt-win-reg only takes a single disk image ...
+die __"no libvirt domain name or disk image given\n" if @ARGV == 0;
+my $domname_or_image = shift @ARGV;
+
+warn "launching libguestfs ..." if $debug;
+
+my @lib_args = ();
+push @lib_args, readonly => 1 unless $merge;
+push @lib_args, format => $format if defined $format;
+
+my $g = Sys::Guestfs->new ();
+
+# If the parameter looks like a URI, try parsing it using guestfish.
+# This is a massive hack, but we'll fix it when virt-win-reg gets
+# rewritten in C ...
+if ($domname_or_image =~ m|://|) {
+ # Whitelist the characters permitted in the URI.
+ die "$0: $domname_or_image: URI parameter contains invalid characters"
+ unless $domname_or_image =~ m|^[A-Za-z0-9/:#%&*+,-.=?@_~]+$|;
+
+ my $cmd = "LANG=C guestfish -a '$domname_or_image' -x exit 2>&1 | grep 'trace: add_drive [^=]'";
+ open CMD, "$cmd|" or die "open: $cmd: $!";
+ $_ = <CMD>;
+ close CMD or die "close: $cmd: $!";
+ chomp;
+ die "$0: could not parse '$_'"
+ unless m/^libguestfs: trace: add_drive "(.*?)"(.*)/;
+ my @args = ($1, @lib_args);
+ $_ = $2;
+ while (/\S/) {
+ die "$0: cound not parse remainder from '$_'"
+ unless $_ =~ /^\s*"([a-z]+):(.*?)"(.*)/;
+ if ($1 ne "server") {
+ push @args, $1, $2;
+ } else {
+ push @args, $1, [$2];
+ }
+ $_ = $3;
+ }
+ $g->add_drive (@args);
+}
+# If the parameter looks like a local file:
+elsif (-e $domname_or_image) {
+ $g->add_drive ($domname_or_image, @lib_args);
+}
+# Try a libvirt domain name:
+else {
+ push @lib_args, libvirturi => $uri if defined $uri;
+ $g->add_domain ($domname_or_image, @lib_args);
+}
+
+$g->launch ();
+
+warn "inspecting guest ..." if $debug;
+
+my @roots = $g->inspect_os ();
+if (@roots == 0) {
+ die __x("{prog}: No operating system could be detected inside this disk image.\n\nThis may be because the file is not a disk image, or is not a virtual machine\nimage, or because the OS type is not understood by libguestfs.\n\nIf you feel this is an error, please file a bug report including as much\ninformation about the disk image as possible.\n",
+ prog => basename ($0));
+}
+if (@roots > 1) {
+ die __x("{prog}: multiboot operating systems are not supported.\n",
+ prog => basename ($0))
+}
+my %fses = $g->inspect_get_mountpoints ($roots[0]);
+my @fses = sort { length $a <=> length $b } keys %fses;
+my $mountopts = $merge ? "" : "ro";
+foreach (@fses) {
+ $g->mount_options ($mountopts, $fses{$_}, $_);
+}
+
+my $systemroot = $g->inspect_get_windows_systemroot ($roots[0]);
+
+# Create a working directory to store the downloaded registry files.
+my $tmpdir = tempdir (CLEANUP => 1);
+
+# Used when merging (only) to map from the downloaded hiveshortname to
+# various properties about the hive. The key is hiveshortname. The
+# value is a hashref containing {h} (hive handle) and {hivefile} (full
+# hive path on the Windows side).
+my %hives;
+
+if (!$merge) { # Export mode.
+ die __"expecting 1 or 2 more parameters, subkey path and optionally the value to export\n"
+ if @ARGV < 1 || @ARGV > 2;
+
+ my $path = shift @ARGV;
+ my $name = shift @ARGV; # or undef
+
+ # Map this to the hive name. This function dies on failure.
+ my ($hiveshortname, $hivefile, $prefix);
+ ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($path);
+
+ # Download the chosen hive.
+ download_hive ($hivefile, $hiveshortname);
+
+ # Open it.
+ my $h = Win::Hivex->open ("$tmpdir/$hiveshortname",
+ unsafe => 1, debug => $debug);
+
+ unless ($name) {
+ # Export it.
+ warn "exporting $path from $hiveshortname with prefix $prefix ..."
+ if $debug;
+ reg_export ($h, $path, \*STDOUT,
+ prefix => $prefix,
+ unsafe_printable_strings => $unsafe_printable_strings);
+ } else {
+ # Export a single key using hivexget.
+ my @args = ("hivexget", "$tmpdir/$hiveshortname", $path, $name);
+ warn "running ", join (" ", @args), " ..." if $debug;
+ system (@args) == 0 or die "hivexget failed: $?"
+ }
+}
+else { # Import mode.
+ if (@ARGV == 0) {
+ reg_import (\*STDIN, \&import_mapper, encoding => $encoding);
+ } else {
+ foreach (@ARGV) {
+ open my $fh, $_ or die "open: $_: $!";
+ reg_import ($fh, \&import_mapper, encoding => $encoding);
+ }
+ }
+
+ # Now we've done importing, commit all the hive handles and
+ # close them all.
+ foreach (values %hives) {
+ my $h = $_->{h};
+ delete $_->{h};
+ $h->commit (undef);
+ }
+
+ # Upload all the downloaded hives.
+ foreach my $hiveshortname (keys %hives) {
+ upload_hive ($hiveshortname, $hives{$hiveshortname}->{hivefile})
+ }
+
+ # Close.
+ $g->shutdown ();
+ $g->close ();
+}
+
+exit 0;
+
+# map function passed to reg_import.
+sub import_mapper
+{
+ local $_ = shift;
+
+ my ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($_);
+
+ # Need to download this hive?
+ unless (-f "$tmpdir/$hiveshortname") {
+ download_hive ($hivefile, $hiveshortname);
+
+ my $h = Win::Hivex->open ("$tmpdir/$hiveshortname",
+ write => 1, debug => $debug);
+ my %hash = ( h => $h, hivefile => $hivefile );
+ $hives{$hiveshortname} = \%hash;
+ }
+
+ return ($hives{$hiveshortname}->{h}, $path);
+}
+
+# Given a path, map that to the name of the hive and the true path
+# within that hive.
+sub map_path_to_hive
+{
+ local $_ = shift;
+ my ($hiveshortname, $hivefile, $path, $prefix);
+
+ if (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SAM(\\.*)?$/i) {
+ $hiveshortname = "sam";
+ $hivefile = "$systemroot/system32/config/$hiveshortname";
+ $path = defined $1 ? $1 : "\\";
+ $prefix = "HKEY_LOCAL_MACHINE\\SAM";
+ }
+ elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SECURITY(\\.*)?$/i) {
+ $hiveshortname = "security";
+ $hivefile = "$systemroot/system32/config/$hiveshortname";
+ $path = defined $1 ? $1 : "\\";
+ $prefix = "HKEY_LOCAL_MACHINE\\SECURITY";
+ }
+ elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SOFTWARE(\\.*)?$/i) {
+ $hiveshortname = "software";
+ $hivefile = "$systemroot/system32/config/$hiveshortname";
+ $path = defined $1 ? $1 : "\\";
+ $prefix = "HKEY_LOCAL_MACHINE\\SOFTWARE";
+ }
+ elsif (/^\\?(?:HKEY_LOCAL_MACHINE|HKLM)\\SYSTEM(\\.*)?$/i) {
+ $hiveshortname = "system";
+ $hivefile = "$systemroot/system32/config/$hiveshortname";
+ $path = defined $1 ? $1 : "\\";
+ $prefix = "HKEY_LOCAL_MACHINE\\SYSTEM";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\.DEFAULT(\\.*)?$/i) {
+ $hiveshortname = "default";
+ $hivefile = "$systemroot/system32/config/$hiveshortname";
+ $path = defined $1 ? $1 : "\\";
+ $prefix = "HKEY_LOCAL_MACHINE\\.DEFAULT";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\(S-1-5-[-\d]+)(\\.*)?$/i) {
+ my $sid = $1;
+ $hiveshortname = $sid;
+ $prefix = "HKEY_USERS\\$sid";
+ $path = defined $2 ? $2 : "\\";
+ # This requires a recursive call to download the SOFTWARE hive.
+ $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\LocalSystem(\\.*)?$/i) {
+ my $sid = "S-1-5-18";
+ $hiveshortname = $sid;
+ $prefix = "HKEY_USERS\\$sid";
+ $path = defined $1 ? $1 : "\\";
+ # This requires a recursive call to download the SOFTWARE hive.
+ $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\LocalService(\\.*)?$/i) {
+ my $sid = "S-1-5-19";
+ $hiveshortname = $sid;
+ $prefix = "HKEY_USERS\\$sid";
+ $path = defined $1 ? $1 : "\\";
+ # This requires a recursive call to download the SOFTWARE hive.
+ $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\NetworkService(\\.*)?$/i) {
+ my $sid = "S-1-5-20";
+ $hiveshortname = $sid;
+ $prefix = "HKEY_USERS\\$sid";
+ $path = defined $1 ? $1 : "\\";
+ # This requires a recursive call to download the SOFTWARE hive.
+ $hivefile = lookup_pip_of_user_sid ($sid) . "/ntuser.dat";
+ }
+ elsif (/^\\?(?:HKEY_USERS|HKU)\\(.*?)(\\.*)?$/i) {
+ $hiveshortname = "user_$1";
+ $prefix = "HKEY_USERS\\$1";
+ $path = defined $2 ? $2 : "\\";
+ # XXX We should probably look this up properly.
+ if (is_dir_nocase ("/Users/$1")) {
+ $hivefile = "/Users/$1/ntuser.dat"
+ } elsif (is_dir_nocase ("/Documents and Settings/$1")) {
+ $hivefile = "/Documents and Settings/$1/ntuser.dat"
+ } else {
+ die __x("virt-win-reg: {p}: cannot find user directory\n",
+ p => $1)
+ }
+ }
+ else {
+ die __x("virt-win-reg: {p}: not a supported Windows Registry path\n",
+ p => $_)
+ }
+
+ return ($hiveshortname, $hivefile, $path, $prefix);
+}
+
+# Given a User SID, consult
+# HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\$sid
+# and return the ProfileImagePath value.
+sub lookup_pip_of_user_sid
+{
+ local $_;
+ my $sid = shift;
+
+ my $path =
+ "HKLM\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList\\".
+ $sid;
+
+ my ($hiveshortname, $hivefile, $prefix);
+ ($hiveshortname, $hivefile, $path, $prefix) = map_path_to_hive ($path);
+
+ download_hive ($hivefile, $hiveshortname)
+ unless -f "$tmpdir/$hiveshortname";
+
+ my @args = ("$tmpdir/$hiveshortname", $path, "ProfileImagePath");
+ warn "running hivexget ", join (" ", @args), " ..." if $debug;
+
+ my $fh;
+ open $fh, "-|", "hivexget", @args
+ or die "hivexget: see earlier errors: $!";
+ $_ = <$fh>;
+ close $fh or die "hivexget: see earlier errors: $!";
+
+ chomp;
+
+ # The contents of the registry are a windows path, possibly
+ # containing %systemroot% and %systemdrive% (on Win XP). Expand
+ # it and remove some other windows-isms. The caller will do
+ # case_sensitive_path for us, so we don't need to do that.
+ s/%systemroot%/$systemroot/i;
+ s/%systemdrive%//i;
+ s/^c://i;
+ s,\\,/,g;
+
+ $_;
+}
+
+sub is_dir_nocase
+{
+ local $_;
+ my $dir = shift;
+
+ my $windir;
+ eval { $windir = $g->case_sensitive_path ($dir); };
+ if ($@) {
+ return 0;
+ }
+ return $g->is_dir ($windir);
+}
+
+# Download a named hive file. Die on failure.
+sub download_hive
+{
+ local $_;
+ my $hivefile = shift;
+ my $hiveshortname = shift;
+
+ my $winfile = $g->case_sensitive_path ($hivefile);
+
+ warn "downloading $winfile ..." if $debug;
+ eval { $g->download ($winfile, "$tmpdir/$hiveshortname"); };
+ if ($@) {
+ die __x("virt-win-reg: {p}: could not download registry file: {err}\n",
+ p => $winfile, err => $@);
+ }
+}
+
+# Upload a named hive file. Die on failure.
+sub upload_hive
+{
+ local $_;
+ my $hiveshortname = shift;
+ my $hivefile = shift;
+
+ my $winfile = $g->case_sensitive_path ($hivefile);
+
+ warn "uploading $winfile ..." if $debug;
+ eval { $g->upload ("$tmpdir/$hiveshortname", $winfile); };
+ if ($@) {
+ die __x("virt-win-reg: {p}: could not upload registry file: {err}\n",
+ p => $winfile, err => $@);
+ }
+}
+
+=head1 SUPPORTED SYSTEMS
+
+The program currently supports Windows NT-derived guests starting with
+Windows XP through to at least Windows 8.
+
+The following Registry keys are supported:
+
+=over 4
+
+=item C<HKEY_LOCAL_MACHINE\SAM>
+
+=item C<HKEY_LOCAL_MACHINE\SECURITY>
+
+=item C<HKEY_LOCAL_MACHINE\SOFTWARE>
+
+=item C<HKEY_LOCAL_MACHINE\SYSTEM>
+
+=item C<HKEY_USERS\.DEFAULT>
+
+=item C<HKEY_USERS\I<SID>>
+
+where I<SID> is a Windows User SID (eg. C<S-1-5-18>).
+
+=item C<HKEY_USERS\I<username>>
+
+where I<username> is a local user name (this is a libguestfs extension).
+
+=back
+
+You can use C<HKLM> as a shorthand for C<HKEY_LOCAL_MACHINE>, and
+C<HKU> for C<HKEY_USERS>.
+
+The literal keys C<HKEY_USERS\$SID> and C<HKEY_CURRENT_USER> are not
+supported (there is no "current user").
+
+=head2 WINDOWS 8
+
+Windows 8 "fast startup" can prevent virt-win-reg from being
+able to edit the Registry. See
+L<guestfs(3)/WINDOWS HIBERNATION AND WINDOWS 8 FAST STARTUP>.
+
+=head1 ENCODING
+
+C<virt-win-reg> expects that regedit files have already been reencoded
+in the local encoding. Usually on Linux hosts, this means UTF-8 with
+Unix-style line endings. Since Windows regedit files are often in
+UTF-16LE with Windows-style line endings, you may need to reencode the
+whole file before or after processing.
+
+To reencode a file from Windows format to Linux (before processing it
+with the I<--merge> option), you would do something like this:
+
+ iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg
+
+To go in the opposite direction, after exporting and before sending
+the file to a Windows user, do something like this:
+
+ unix2dos linux.reg | iconv -f utf-8 -t utf-16le > win.reg
+
+For more information about encoding, see L<Win::Hivex::Regedit(3)>.
+
+If you are unsure about the current encoding, use the L<file(1)>
+command. Recent versions of Windows regedit.exe produce a UTF-16LE
+file with Windows-style (CRLF) line endings, like this:
+
+ $ file software.reg
+ software.reg: Little-endian UTF-16 Unicode text, with very long lines,
+ with CRLF line terminators
+
+This file would need conversion before you could I<--merge> it.
+
+=head1 CurrentControlSet etc.
+
+Registry keys like C<CurrentControlSet> don’t really exist in the
+Windows Registry at the level of the hive file, and therefore you
+cannot modify these.
+
+C<CurrentControlSet> is usually an alias for C<ControlSet001>. In
+some circumstances it might refer to another control set. The way
+to find out is to look at the C<HKLM\SYSTEM\Select> key:
+
+ # virt-win-reg WindowsGuest 'HKLM\SYSTEM\Select'
+ [HKEY_LOCAL_MACHINE\SYSTEM\Select]
+ "Current"=dword:00000001
+ "Default"=dword:00000001
+ "Failed"=dword:00000000
+ "LastKnownGood"=dword:00000002
+
+"Current" is the one which Windows will choose when it boots.
+
+Similarly, other C<Current...> keys in the path may need to
+be replaced.
+
+=head1 DELETING REGISTRY KEYS AND VALUES
+
+To delete a whole registry key, use the syntax:
+
+ [-HKEY_LOCAL_MACHINE\Foo]
+
+To delete a single value within a key, use the syntax:
+
+ [HKEY_LOCAL_MACHINE\Foo]
+ "Value"=-
+
+=head1 WINDOWS TIPS
+
+Note that some of these tips modify the guest disk image. The guest
+I<must> be shut off, else you will get disk corruption.
+
+=head2 RUNNING A BATCH SCRIPT WHEN A USER LOGS IN
+
+Prepare a DOS batch script, VBScript or executable. Upload this using
+L<guestfish(1)>. For this example the script is called C<test.bat>
+and it is uploaded into C<C:\>:
+
+ guestfish -i -d WindowsGuest upload test.bat /test.bat
+
+Prepare a regedit file containing the registry change:
+
+ cat > test.reg <<'EOF'
+ [HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce]
+ "Test"="c:\\test.bat"
+ EOF
+
+In this example we use the key C<RunOnce> which means that the script
+will run precisely once when the first user logs in. If you want it
+to run every time a user logs in, replace C<RunOnce> with C<Run>.
+
+Now update the registry:
+
+ virt-win-reg --merge WindowsGuest test.reg
+
+=head2 INSTALLING A SERVICE
+
+This section assumes you are familiar with Windows services, and you
+either have a program which handles the Windows Service Control
+Protocol directly or you want to run any program using a service
+wrapper like SrvAny or the free RHSrvAny.
+
+First upload the program and optionally the service wrapper. In this
+case the test program is called C<test.exe> and we are using the
+RHSrvAny wrapper:
+
+ guestfish -i -d WindowsGuest <<EOF
+ upload rhsrvany.exe /rhsrvany.exe
+ upload test.exe /test.exe
+ EOF
+
+Prepare a regedit file containing the registry changes. In this
+example, the first registry change is needed for the service itself or
+the service wrapper (if used). The second registry change is only
+needed because I am using the RHSrvAny service wrapper.
+
+ cat > service.reg <<'EOF'
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny]
+ "Type"=dword:00000010
+ "Start"=dword:00000002
+ "ErrorControl"=dword:00000001
+ "ImagePath"="c:\\rhsrvany.exe"
+ "DisplayName"="RHSrvAny"
+ "ObjectName"="NetworkService"
+
+ [HKLM\SYSTEM\ControlSet001\services\RHSrvAny\Parameters]
+ "CommandLine"="c:\\test.exe"
+ "PWD"="c:\\Temp"
+ EOF
+
+Notes:
+
+=over 4
+
+=item *
+
+For use of C<ControlSet001> see the section above in this manual page.
+You may need to adjust this according to the control set that is in
+use by the guest.
+
+=item *
+
+C<"ObjectName"> controls the privileges that the service will have.
+An alternative is C<"ObjectName"="LocalSystem"> which would be the
+most privileged account.
+
+=item *
+
+For the meaning of the magic numbers, see this Microsoft KB article:
+L<http://support.microsoft.com/kb/103000>.
+
+=back
+
+Update the registry:
+
+ virt-win-reg --merge WindowsGuest service.reg
+
+=head1 SHELL QUOTING
+
+Be careful when passing parameters containing C<\> (backslash) in the
+shell. Usually you will have to use 'single quotes' or double
+backslashes (but not both) to protect them from the shell.
+
+Paths and value names are case-insensitive.
+
+=head1 SEE ALSO
+
+L<hivex(3)>,
+L<hivexsh(1)>,
+L<hivexregedit(1)>,
+L<guestfs(3)>,
+L<guestfish(1)>,
+L<virt-cat(1)>,
+L<virt-tail(1)>,
+L<Sys::Guestfs(3)>,
+L<Win::Hivex(3)>,
+L<Win::Hivex::Regedit(3)>,
+L<Sys::Virt(3)>,
+L<http://libguestfs.org/>.
+
+=head1 AUTHOR
+
+Richard W.M. Jones L<http://people.redhat.com/~rjones/>
+
+=head1 COPYRIGHT
+
+Copyright (C) 2010 Red Hat Inc.
projects / guestfs-tools.git / commitdiff