-.TH WIMLIB-IMAGEX "1" "March 2014" "@IMAGEX_PROGNAME@ @VERSION@" "User Commands"
+.TH WIMLIB-IMAGEX "1" "November 2014" "wimlib-imagex @VERSION@" "User Commands"
.SH NAME
-@IMAGEX_PROGNAME@-capture, @IMAGEX_PROGNAME@-append \- Create or append a WIM image
+wimlib-imagex-capture, wimlib-imagex-append \- Create or append a WIM image
.SH SYNOPSIS
-\fB@IMAGEX_PROGNAME@ capture\fR \fISOURCE\fR \fIWIMFILE\fR [\fIIMAGE_NAME\fR \
+\fBwimlib-imagex capture\fR \fISOURCE\fR \fIWIMFILE\fR [\fIIMAGE_NAME\fR \
[\fIIMAGE_DESCRIPTION\fR]] [\fIOPTION\fR...]
.br
-\fB@IMAGEX_PROGNAME@ append\fR \fISOURCE\fR \fIWIMFILE\fR [\fIIMAGE_NAME\fR \
+\fBwimlib-imagex append\fR \fISOURCE\fR \fIWIMFILE\fR [\fIIMAGE_NAME\fR \
[\fIIMAGE_DESCRIPTION\fR]] [\fIOPTION\fR...]
.SH DESCRIPTION
-The \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR commands
+The \fBwimlib-imagex capture\fR and \fBwimlib-imagex append\fR commands
create a Windows Imaging (WIM) image from a directory tree. The
-\fB@IMAGEX_PROGNAME@ capture\fR command creates a new WIM file containing the
-captured image, while the \fB@IMAGEX_PROGNAME@ append\fR command appends the
+\fBwimlib-imagex capture\fR command creates a new WIM file containing the
+captured image, while the \fBwimlib-imagex append\fR command appends the
captured image to an existing WIM file.
These commands are also available as simply \fBwimcapture\fR and \fBwimappend\fR
if the appropriate hard links or batch files are installed.
assumed and the WIM file is written to standard output in a special pipable
format. See the documentation for \fB--pipable\fR for more details.
.SH DIRECTORY CAPTURE (UNIX)
-This section documents how \fB@IMAGEX_PROGNAME@\fR captures files from a
+This section documents how \fBwimlib-imagex\fR captures files from a
directory tree on UNIX-like systems. See \fBDIRECTORY CAPTURE (WINDOWS)\fR for
the corresponding documentation for Windows.
.PP
metadata from filesystems used on UNIX-like systems. The main information that
will \fInot\fR be stored is:
.IP \[bu] 4
-UNIX file owners, groups, and modes. (Exception: see the \fB--unix-data\fR
-option.) As a result, file permissions will not be stored, and files that are
-neither regular files, directories, nor symbolic links, such as device files and
-FIFOs, cannot be captured and will be excluded by default.
+UNIX file owners, groups, modes, and device IDs (major and minor numbers),
+unless the \fB--unix-data\fR option is specified. By default (without
+\fB--unix-data\fR), files that are neither regular files, directories, nor
+symbolic links, such as device nodes and FIFOs, will be excluded.
.IP \[bu]
Extended attributes. This mainly includes extensions to the traditional UNIX
security model, such as SELinux security labels, POSIX ACLs, and capabilities
change time (ctime). Hard links and symbolic links are supported by the WIM
format and \fIare\fR stored. Symbolic links are turned into "native" Windows
symbolic links, or "reparse points"; this process is fully reversible, e.g.
-automatically by \fB@IMAGEX_PROGNAME@ apply\fR, unless the symbolic link target
+automatically by \fBwimlib-imagex apply\fR, unless the symbolic link target
contains backslash characters.
.PP
Pedantic note: A limitation of the WIM format prevents the unusual case where a
single symbolic link file itself has multiple names (hard links); in this
unlikely case, each symbolic link is stored as an independent file.
.SH NTFS VOLUME CAPTURE (UNIX)
-This section documents how \fB@IMAGEX_PROGNAME@\fR captures files directly from
+This section documents how \fBwimlib-imagex\fR captures files directly from
an NTFS volume image on UNIX-like systems.
.PP
On UNIX-like systems, a special image capture mode is entered when \fISOURCE\fR
is a regular file or block device. In this mode, \fISOURCE\fR is assumed to be
-an NTFS volume or volume image, and \fB@IMAGEX_PROGNAME@\fR will capture a WIM
+an NTFS volume or volume image, and \fBwimlib-imagex\fR will capture a WIM
image containing the full contents of the NTFS volume, including NTFS-specific
data. This is done using libntfs-3g.
.PP
the full data of the file rather than the "sparse" data. (The data is, however,
subject to the WIM format's compression.)
.SH DIRECTORY CAPTURE (WINDOWS)
-On Windows, \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR
+On Windows, \fBwimlib-imagex capture\fR and \fBwimlib-imagex append\fR
natively support Windows-specific and NTFS-specific data. They therefore act
-similarly to the corresponding commands of Microsoft's ImageX. For best
+similarly to the corresponding commands of Microsoft's ImageX or DISM. For best
results, the directory being captured should be on an NTFS volume and
-\fB@IMAGEX_PROGNAME@\fR should be run with Administrator privileges; however,
+\fBwimlib-imagex\fR should be run with Administrator privileges; however,
non-NTFS filesystems and running without Administrator privileges are also
supported.
.PP
-On Windows, \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR
+On Windows, \fBwimlib-imagex capture\fR and \fBwimlib-imagex append\fR
try to archive as much data and metadata as possible, including:
.IP \[bu] 4
All data streams of all files.
is not specified. However, beware that unless \fB--strict-acls\fR is specified,
the security descriptors for individual files or directories may be omitted or
only partially captured if the user does not have permission to read them, which
-can be a problem if \fB@IMAGEX_PROGNAME@\fR is run as a non-Administrator.
+can be a problem if \fBwimlib-imagex\fR is run as a non-Administrator.
.IP \[bu]
File attributes, including hidden, sparse, compressed, encrypted, etc.
Encrypted files will be stored in encrypted form rather than in plain text.
.IP \[bu]
Hard links, if supported by the source filesystem.
.PP
-Note: the capture process is reversible, since when \fB@IMAGEX_PROGNAME@
+Note: the capture process is reversible, since when \fBwimlib-imagex
apply\fR (on Windows) extracts the captured WIM image, it will extract all of
the above information, at least to the extent supported by the destination
filesystem. One exception is that since encrypted files are stored as
Specifies that the new image is to be made the bootable image of the WIM archive.
.TP
\fB--check\fR
-For \fB@IMAGEX_PROGNAME@ append\fR, before performing the append operation,
+For \fBwimlib-imagex append\fR, before performing the append operation,
check the integrity of \fIWIMFILE\fR if an integrity table is present.
Furthermore, include an integrity table in the new WIM file
-(\fB@IMAGEX_PROGNAME@ capture\fR) or the modified WIM file (\fB@IMAGEX_PROGNAME@
+(\fBwimlib-imagex capture\fR) or the modified WIM file (\fBwimlib-imagex
append\fR). If this option is not specified, no integrity table is included in
-a WIM file created with \fB@IMAGEX_PROGNAME@ capture\fR, while a WIM file
-updated with \fB@IMAGEX_PROGNAME@ append\fR will be written with an integrity
+a WIM file created with \fBwimlib-imagex capture\fR, while a WIM file
+updated with \fBwimlib-imagex append\fR will be written with an integrity
table if and only if one was present before.
.TP
-\fB--compress\fR=\fITYPE\fR
-Specifies the compression type for the new WIM file. This flag is only valid
-for \fB@IMAGEX_PROGNAME@ capture\fR, since the compression mode for
-\fB@IMAGEX_PROGNAME@ append\fR must be the same as that of the existing
-WIM (and is automatically set as such). \fITYPE\fR may be "none",
-"fast", or "maximum". As of wimlib v1.5.3, the default is LZX compression, but
-in a special mode that is somewhere in between "fast" and "maximum" in terms of
-speed and compression ratio. Use \fB--compress\fR=\fImaximum\fR to explicitly
-request a better compression ratio at the cost of more time spent compressing.
-.IP ""
-You may also specify the actual names of the compression algorithms, "XPRESS"
-and "LZX", instead of "fast" and "maximum", respectively.
-.IP ""
-As of wimlib v1.6.0, a third compression type, "recovery" or "LZMS", is also
-available. Its use is generally not recommended because other than wimlib
-itself, as of Windows 8 it is only compatible with WIMGAPI and Windows Setup
-(not even ImageX or Dism). However, LZMS is the compression algorithm used in
-packed resources created if the \fB--pack-streams\fR option is specified.
-.TP
-\fB--compress-slow\fR
-Spend even more time compressing the data to achieve a very slightly better
-compression ratio. This currently only has an effect for LZX ("maximum", the
-default) and LZMS ("recovery") compression.
+\fB--compress\fR=\fITYPE\fR[:\fILEVEL\fR]
+Specifies the compression format for the new WIM file. \fITYPE\fR may be
+"none", "XPRESS" (alias: "fast"), "LZX" (alias: "maximum"), or "LZMS" (alias:
+"recovery"). \fITYPE\fR is matched case-insensitively. The default is "LZX".
+.IP ""
+You can optionally also specify an integer compression \fILEVEL\fR. The
+compression level specifies how hard the compression algorithm for the specified
+compression \fITYPE\fR will work to compress the data. The values are scaled so
+that 20 is quick compression, 50 is medium compression, and 100 is high
+compression. However, you can choose any value, and not just these particular
+values. The default is 50.
+.IP ""
+Be careful if you choose LZMS compression. It is not compatible with wimlib
+before v1.6.0, WIMGAPI before Windows 8, DISM before Windows 8.1, and 7-Zip.
.TP
\fB--chunk-size\fR=\fISIZE\fR
-Set the WIM compression chunk size to \fISIZE\fR. Larger chunks mean larger
+Set the WIM compression chunk size to \fISIZE\fR bytes. Larger chunks mean larger
LZ77 dictionaries and better compression ratios on sufficiently large files, but
slower random access. \fBUsing this option is generally not recommended because
of the compatibility limitations detailed in the next paragraph.\fR But if you
-decide to use this option regardless, you may choose a chunk size that is a
-power of 2 greater than or equal to 2^15 (32768) up to a maximum determined by
-the compression format. For LZX ("maximum") compression, the maximum allowed
-chunk size is 2^21 (2097152), and for XPRESS ("fast") and LZMS ("recovery")
-compression, the maximum allowed chunk size is 2^30 (1073741824).
-.IP ""
-For XPRESS and LZX compression, Microsoft's implementation (as of Windows 8)
-does not appear to support alternate chunk sizes; although it will still open
-such files, it will crash, extract the data incorrectly, or report that the data
-is invalid. For LZMS compression, Microsoft's implementation (as of Windows 8)
-appears to only support chunk sizes that are powers of 2 between 2^15 (32768)
-and 2^20 (1048576) inclusively. In addition, wimlib versions before 1.6.0 do
-not support alternate chunk sizes.
+decide to use this option regardless, you may choose a chunk size that is
+allowed by the compression format. All formats only allow power-of-2 chunk
+sizes. For LZX ("maximum") compression the maximum allowed chunk size is 2^21
+(2097152), for XPRESS ("fast") compression the maximum allowed chunk size is
+2^16 (65536), and for LZMS ("recovery") compression the maximum allowed chunk
+size is 2^30 (1073741824).
+.IP ""
+Beware that Microsoft's implementation has limited support for non-default chunk
+sizes. Depending on the version, their software may refuse to open the WIM, or
+open it and crash, or open it and report the data is invalid, or even extract
+the data incorrectly. In addition, wimlib versions before 1.6.0 do not support
+alternate chunk sizes.
.TP
-\fB--pack-streams\fR, \fB--solid\fR
+\fB--solid\fR
Create a "solid" archive that compresses multiple unique streams ("files")
together, rather than each unique stream ("file") independently. This can
result in a significantly better compression ratio, but this format greatly
decreases the performance of random access to the data, as may occur on a WIM
-mounted with \fB@IMAGEX_PROGNAME@ mount\fR. Also, WIMs created using this
-option use a different version number in their header and as of Windows 8 are
-only compatible with Windows Setup and WIMGAPI, not even ImageX and Dism.
-.IP ""
-Packed resources use a compression type and chunk size that is independent of
-the WIM's "default compression type" and "default chunk size" (which may be
-adjusted by the \fB--compress\fR and \fB--chunk-size\fR options, respectively).
-For compatibility reasons, \fB@IMAGEX_PROGNAME@ capture\fR currently has no
-option to change the compression type used in packed resources; however, the
-\fB--pack-chunk-size\fR option may be used to set the chunk size.
+mounted with \fBwimlib-imagex mount\fR. Also, WIMs created using this
+option use a different version number in their header and are only compatible
+with WIMGAPI Windows 8 and later, and DISM Windows 8.1 and later.
+.IP ""
+The default compression type and chunk size in solid blocks is LZMS with 2^25
+(33554432) byte chunks. This is independent of the WIM's main compression type
+and chunk size.
.TP
-\fB--pack-chunk-size\fR=\fISIZE\fR, \fB--solid-chunk-size\fR=\fISIZE\fR
-Like \fB--chunk-size\fR, but set the chunk size used in packed resources. The
-compression format is LZMS, so the chunk size can be any power of 2 between 2^15
-and 2^30, inclusively. WIMGAPI (Windows 8) appears to be compatible with these
-sizes up to 2^26 inclusively, despite not being compatible with sizes greater
-than 2^20 in non-packed resources. The default is currently 2^25 (33554432).
-Note: currently, the LZMS compression algorithm uses about 15 times the chunk
-size in memory per thread, which is about 500 MB per thread for the default pack
-chunk size of 2^25 or 1 GB per thread if you change it to 2^26 (67108864).
+\fB--solid-chunk-size\fR=\fISIZE\fR
+Like \fB--chunk-size\fR, but set the chunk size used in solid blocks. The
+default is LZMS compression with 2^25 (33554432) byte chunks. This option only
+has an effect when \fB--solid\fR is also specified. For maximum compatibility
+with the Microsoft implementation, do not use either of these options.
+.TP
+\fB--solid-compress\fR=\fITYPE\fR[:\fILEVEL\fR]
+Like \fB--compress\fR, but set the compression type used in solid blocks. The
+default is LZMS compression with 2^25 (33554432) byte chunks. This option only
+has an effect when \fB--solid\fR is also specified. For maximum compatibility
+with the Microsoft implementation, do not use either of these options.
.TP
\fB--threads\fR=\fINUM_THREADS\fR
Number of threads to use for compressing data. Default: autodetect (number of
available CPUs).
.TP
\fB--rebuild\fR
-For \fB@IMAGEX_PROGNAME@ append\fR: rebuild the entire WIM rather than appending the new
+For \fBwimlib-imagex append\fR: rebuild the entire WIM rather than appending the new
data to the end of it. Rebuilding the WIM is slower, but will save a little bit
-of space that would otherwise be left as a hole in the WIM. Also see \fB@IMAGEX_PROGNAME@
+of space that would otherwise be left as a hole in the WIM. Also see \fBwimlib-imagex
optimize\fR(1).
.TP
\fB--flags\fR=\fIEDITIONID\fR
to, rather than archiving the links themselves.
.TP
\fB--config\fR=\fIFILE\fR
-Specifies a configuration file (UTF-8 or UTF-16LE encoded) for capturing the new
-image. The configuration file specifies files that are to be treated specially
-during the image capture.
-.IP ""
-The format of the configuration file is a number of sections containing path
-globs one per line, where each section begins with the tag [ExclusionList],
-[ExclusionException], [CompressionExclusionList], or [AlignmentList].
-Currently, only the [ExclusionList] and [ExclusionException] sections are
-implemented. The [ExclusionList] section specifies a list of path globs to
-exclude from capture, while the [ExclusionException] section specifies a list of
-path globs to include in the capture even if the matched file or directory name
-also appears in the [ExclusionList].
-.IP ""
-Relative globs with only one path component (e.g. *.mp3) match against a
-filename in any directory. Relative globs with multiple path components (e.g.
-dir/file), as well as absolute globs (e.g. /dir/file), are treated as paths
-starting at the root directory of capture, or the root of the NTFS volume for
-NTFS volume capture mode. If a directory is matched by a glob in the
-[ExclusionList], the entire directory tree rooted at that directory is excluded
-from the capture, unless \fB--dereference\fR is specified and there is another
-path into that directory through a symbolic link.
-.IP ""
-For compatibility with Windows, the path separators in the globs may be either
-forward slashes or backslashes, and the line separators may be either UNIX-style
-or DOS-style. Trailing and leading whitespace is ignored. Lines beginning with
-the '#' or ';' characters are treated as comments and ignored. Globs with
-whitespace in them need not be quoted, unless the whitespace is leading or
-trailing. Both double and single quotes are accepted.
-.IP ""
-Paths may not have drive letters in them, as they are all relative to the root
-of capture and not absolute external paths.
+Specifies a configuration file (UTF-8 or UTF-16LE encoded; plain ASCII also
+works) for capturing the new image. The configuration file specifies files that
+are to be treated specially during the image capture.
+.IP ""
+The format of the configuration file is INI-style; that is, it is arranged in
+bracketed sections. Currently, only the following sections are recognized:
+.RS
+.IP \[bu] 4
+[ExclusionList] --- contains a list of path globs to exclude from capture. If
+a directory is matched, both the directory and its contents are excluded.
+.IP \[bu]
+[ExclusionException] --- contains a list of path globs to include in the
+capture, even when the file or directory also matches a glob in [ExclusionList].
+.IP \[bu]
+[PrepopulateList] --- this does not affect capture, but if the image is applied
+later with \fB--wimboot\fR, these are globs of files that shall be extracted
+normally, not as WIMBoot "pointer files". If a directory is matched, all files
+and subdirectories are also matched recursively.
+.RE
+.IP ""
+Any unrecognized sections will be ignored, with a warning printed. Sections
+dealing with compression (e.g. [CompressionExclusion]) are not particularly
+important.
+.IP ""
+Path globs may contain the '*' and '?' meta-characters. Relative globs (e.g.
+*.mp3) match against a filename in any directory. Absolute globs (e.g.
+/dir/file), are treated as paths starting at the main directory being captured,
+or the root of the NTFS volume for NTFS volume capture mode. Do not use drive
+letters in the paths; they will be ignored. Path separators may be either
+forwards slashes or backwards slashes.
+.IP ""
+Lines beginning with the '#' or ';' characters are treated as comments and
+ignored. Globs with whitespace in them need not be quoted; however, if they
+are, both double and single quotes are accepted.
.IP ""
If this option is not specified the following default configuration file is
used:
\\$ntfs.log
\\hiberfil.sys
\\pagefile.sys
+\\swapfile.sys
\\System Volume Information
\\RECYCLER
\\Windows\\CSC
.RE
.RE
.fi
+.IP ""
+However, special behavior applies if \fB--wimboot\fR is also specified. By
+default, with \fB--wimboot\fR specified, the file
+Windows/System32/WimBootCompress.ini in the directory being captured will be
+used as the configuration file. However, this can be overridden using
+\fB--config\fR; and this also causes the specified configuration file to be
+saved in the WIM image as Windows/System32/WimBootCompress.ini, overriding any
+that may be present on the filesystem.
.TP
\fB--unix-data\fR
-(UNIX-like systems only) Store the UNIX owner, group, and mode of all captured
-files. This is done by adding a special alternate data stream to each directory
-entry that contains this information. Please note that this flag is for
-convenience only, in case you want to use \fB@IMAGEX_PROGNAME@\fR to archive
-files on UNIX. Microsoft's software will not understand this special
-information. You also may run into problems when applying an image with UNIX
-data from a pipable WIM.
+(UNIX-like systems only) Store the UNIX owner, group, mode, and device ID (major
+and minor number) of each captured file. As of wimlib v1.7.0, you can backup
+and restore not only the standard UNIX file permission information, but also
+character device nodes, block device nodes, named pipes (FIFOs), and UNIX domain
+sockets.
+.IP
+wimlib stores UNIX data by adding a special tagged metadata item to each
+directory entry of each file that contains this information. This extra
+information is ignored by the Microsoft implementation. Note: UNIX data stored
+by wimlib before v1.7.0 used a different format that is no longer supported. If
+you have old WIM files with UNIX data, apply them with v1.6.2 and recapture them
+with v1.7.0 or later.
.TP
\fB--no-acls\fR
Do not capture files' security descriptors.
Set whether to fix targets of absolute symbolic links (reparse points in Windows
terminology) or not. When enabled (\fB--rpfix\fR), absolute symbolic links that
point inside the directory tree being captured will be adjusted to be absolute
-relative to the root of the directory tree being captured. In addition,
-absolute symbolic links that point outside the directory tree being captured
-will be ignored and not be captured at all. When disabled (\fB--norpfix\fR),
-absolute symbolic links will be captured exactly as is.
+relative to the root of the directory tree being captured. When disabled
+(\fB--norpfix\fR), absolute symbolic links will be captured exactly as is.
.IP ""
-The default behavior for \fB@IMAGEX_PROGNAME@ capture\fR is equivalent to
-\fB--rpfix\fR. The default behavior for \fB@IMAGEX_PROGNAME@ append\fR will be
+The default behavior for \fBwimlib-imagex capture\fR is equivalent to
+\fB--rpfix\fR. The default behavior for \fBwimlib-imagex append\fR will be
\fB--rpfix\fR if reparse point fixups have previously been done on
\fIWIMFILE\fR, otherwise \fB--norpfix\fR.
.IP ""
behavior from the previous paragraph.
.TP
\fB--source-list\fR
-\fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR support
+\fBwimlib-imagex capture\fR and \fBwimlib-imagex append\fR support
creating a WIM image from multiple separate files or directories. When
\fB--source-list\fR is specified, the \fISOURCE\fR argument specifies the name
of a text file, each line of which is either 1 or 2 whitespace separated file
overlay /overlay
# Overlay a separate directory directly on the root of the WIM image.
-# This is only legal if there are no conflicting files.
/data/stuff /
.RE
.RE
.fi
.IP ""
Subdirectories in the WIM are created as needed. Multiple source directories
-may share the same target, which implies an overlay; however, an error is issued
-if the same file appears in different overlays to the same directory.
+may share the same target, which implies an overlay. In the event that this
+results a nondirectory file being added to the WIM image multiple times, the
+last version (as listed in the source list file) overrides any earlier version.
.IP ""
File paths containing whitespace may be quoted with either single quotes or
double quotes. Quotes may not be escaped.
.TP
\fB--pipable\fR
Create a "pipable" WIM, which can be applied fully sequentially, including from
-a pipe. An image in the resulting WIM can be applied with \fB@IMAGEX_PROGNAME@
+a pipe. An image in the resulting WIM can be applied with \fBwimlib-imagex
apply\fR, either normally by specifying the WIM file name, or with
-\fB@IMAGEX_PROGNAME@ apply -\fR to read the WIM from standard input. See
-\fB@IMAGEX_PROGNAME@ apply\fR(1) for more details.
+\fBwimlib-imagex apply -\fR to read the WIM from standard input. See
+\fBwimlib-imagex apply\fR(1) for more details.
.IP ""
For append operations, this option will result in a full rebuild of the WIM to
make it pipable. For capture operations, the captured WIM is simply created as
the WIM so that they can be read sequentially and also makes several other
modifications. As a result, these "pipable" WIMs are \fInot compatible with
Microsoft's software\fR, so keep this in mind if you're going to use them. If
-desired, you can use \fB@IMAGEX_PROGNAME@ optimize --not-pipable\fR to re-write
-a pipable WIM as a regular WIM. (\fB@IMAGEX_PROGNAME@ export\fR also provides
+desired, you can use \fBwimlib-imagex optimize --not-pipable\fR to re-write
+a pipable WIM as a regular WIM. (\fBwimlib-imagex export\fR also provides
the capability to export images from a pipable WIM into a non-pipable WIM, or
vice versa.)
.IP ""
(\fB--rebuild\fR is always implied), and also they aren't compatible with
Microsoft's software.
.IP ""
-\fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR can both
+\fBwimlib-imagex capture\fR and \fBwimlib-imagex append\fR can both
write a pipable WIM directly to standard output; this is done automatically if
\fIWIMFILE\fR is specified as "-". (In that case, \fB--pipable\fR is assumed.)
.TP
\fB--not-pipable\fR
Ensure the resulting WIM is in the normal, non-pipable WIM format. This is the
-default for \fB@IMAGEX_PROGNAME@ capture\fR, except when writing to standard
-output (\fIWIMFILE\fR specified as "-"), and also for \fB@IMAGEX_PROGNAME@
+default for \fBwimlib-imagex capture\fR, except when writing to standard
+output (\fIWIMFILE\fR specified as "-"), and also for \fBwimlib-imagex
append\fR, except when appending to a WIM that is already pipable.
.TP
\fB--update-of\fR=[\fIWIMFILE\fR:]\fIIMAGE\fR
once) for capture operations.
.TP
\fB--delta-from\fR=\fIWIMFILE\fR
-For \fB@IMAGEX_PROGNAME@ capture\fR only: capture the new WIM as a "delta" from
+For \fBwimlib-imagex capture\fR only: capture the new WIM as a "delta" from
\fIWIMFILE\fR. Any streams that would ordinarily need to be archived in the new
WIM are omitted if they are already present in the \fIWIMFILE\fR on which the
delta is being based. The new WIM will still contain a full copy of the image
metadata, but this is typically only a small fraction of a WIM's total size.
.IP ""
This option can be specified multiple times, in which case the resulting delta
-WIM will only contain streams not present in any of the specified base
+WIM will only contain streams not present in any of the specified base WIMs.
.IP ""
To operate on the resulting delta WIM using other commands such as
-\fB@IMAGEX_PROGNAME@ apply\fR, you must specify the delta WIM as the WIM file to
+\fBwimlib-imagex apply\fR, you must specify the delta WIM as the WIM file to
operate on, but also reference the base WIM(s) using the \fB--ref\fR option.
Beware: to retain the proper functioning of the delta WIM, you can only add, not
delete, files and images to the base WIM(s) following the capture of a delta
.IP ""
However, note that as an alternative to the above sequence that used a delta
WIM, the second backup could have simply been appended to the WIM as new image
-using \fB@IMAGEX_PROGNAME@ append\fR. Delta WIMs should be used only if it's
+using \fBwimlib-imagex append\fR. Delta WIMs should be used only if it's
desired to base the backups or images on a separate, large file that is rarely
modified.
.IP ""
Note: unlike "pipable" WIMs (created with the \fB--pipable\fR option), "delta"
WIMs (created with the \fB--delta-from\fR option) are compatible with
-Microsoft's software. You can use the /ref option of imagex.exe to reference
-the base WIM(s), similar to above.
+Microsoft's software. For example, you can use the /ref option of ImageX to
+reference the base WIM(s), similar to above.
.IP ""
-Additional note: \fB@IMAGEX_PROGNAME@\fR is generalized enough that you can in
+Additional note: \fBwimlib-imagex\fR is generalized enough that you can in
fact combine \fB--pipable\fR and \fB--delta-from\fR to create pipable delta
WIMs. In such cases, the base WIM(s) must be captured as pipable as well as the
delta WIM, and when applying an image, the base WIM(s) must be sent over the
pipe after the delta WIM.
.TP
\fB--wimboot\fR
-Windows only: mark the image as WIMBoot-compatible. See Microsoft's
+Mark the image as WIMBoot-compatible. See Microsoft's
documentation for more information about WIMBoot. This option will, by default,
-change the compression type to XPRESS and the chunk size to 4096 bytes; these
+set the compression type to XPRESS and the chunk size to 4096 bytes; these
can, however, still be overridden through the \fB--compress\fR and
\fB--chunk-size\fR parameters, respectively. In addition, this option will, by
default, set the configuration file to
\fISOURCE\fR\\Windows\\System32\\WimBootCompress.ini if present and accessible;
however, this may still be overridden through the \fB--config\fR parameter.
.SH NOTES
-\fB@IMAGEX_PROGNAME@ append\fR does not support appending an image to a split WIM.
+\fBwimlib-imagex append\fR does not support appending an image to a split WIM.
.PP
-It is safe to abort an \fB@IMAGEX_PROGNAME@ append\fR command partway through;
-however, after doing this, it is recommended to run \fB@IMAGEX_PROGNAME@
+It is safe to abort an \fBwimlib-imagex append\fR command partway through;
+however, after doing this, it is recommended to run \fBwimlib-imagex
optimize\fR to remove any data that was appended to the physical WIM file but
not yet incorporated into the structure of the WIM, unless the WIM was being
fully rebuilt (e.g. with \fB--rebuild\fR), in which case you should delete the
temporary file left over.
.PP
-\fB@IMAGEX_PROGNAME@\fR creates WIMs compatible with Microsoft's software
-(imagex.exe, Dism.exe, wimgapi.dll), with some caveats:
+\fBwimlib-imagex\fR creates WIMs compatible with Microsoft's software
+(WIMGAPI, ImageX, DISM), with some caveats:
.IP \[bu] 4
-With \fB@IMAGEX_PROGNAME@\fR on UNIX-like systems, it is possible to create a
+With \fBwimlib-imagex\fR on UNIX-like systems, it is possible to create a
WIM image containing files with names differing only in case, or files with
names containing the characters ':', '*', '?', '"', '<', '>', '|', or '\\',
which are valid on POSIX-compliant filesystems but not Windows. Be warned that
such files will not be extracted by default by the Windows version of
-\fB@IMAGEX_PROGNAME@\fR, and (even worse) Microsoft's ImageX can be confused by
+\fBwimlib-imagex\fR, and (even worse) Microsoft's ImageX can be confused by
such names and quit extracting the image partway through. (It perhaps is worth
pointing out that Windows' own default filesystem, NTFS, supports these
characters, although Windows does not!)
.IP \[bu]
-WIMs captured with \fB--unix-data\fR should be assumed to be incompatible with
-Microsoft's software.
-.IP \[bu]
Pipable WIMs are incompatible with Microsoft's software. Pipable WIMs are
created only if \fIWIMFILE\fR was specified as "-" (standard output) or if
the \fB--pipable\fR flag was specified.
.IP \[bu]
WIMs captured with a non-default chunk size (with the \fB--chunk-size\fR option)
-or as solid archives (with the \fB--pack-streams\fR option) or with LZMS
+or as solid archives (with the \fB--solid\fR option) or with LZMS
compression (with \fB--compress\fR=LZMS or \fB--compress\fR=recovery) have
-varying levels of compatibility with Microsoft's software. The best
-compatibility is achieved with WIMGAPI itself (not ImageX or Dism) on Windows 8
-or later.
+varying levels of compatibility with Microsoft's software. Generally, more
+recent versions of Microsoft's software are more compatible.
.SH EXAMPLES
-First example: Create a new WIM 'mywim.wim' with "maximum" (LZX) compression
+First example: Create a new WIM 'mywim.wim' with LZX ("maximum") compression
that will contain a captured image of the directory tree 'somedir'. Note that
the image name need not be specified and will default to 'somedir':
.RS
.PP
-@IMAGEX_PROGNAME@ capture somedir mywim.wim --compress=maximum
+wimlib-imagex capture somedir mywim.wim
.RE
.PP
or, if the \fBwimcapture\fR hard link or batch file has been installed, the
abbreviated form can be used:
.RS
.PP
-wimcapture somedir mywim.wim --compress=maximum
+wimcapture somedir mywim.wim
.RE
.PP
The remaining examples will use the long form, however. Next, append the image
of a different directory tree to the WIM created above:
.RS
.PP
-@IMAGEX_PROGNAME@ append anotherdir mywim.wim
+wimlib-imagex append anotherdir mywim.wim
.RE
.PP
Easy enough, and the above examples of imaging directory trees work on both
UNIX-like systems and Windows. Next, capture a WIM with several non-default
-options, including "fast" (XPRESS) compression, an integrity table, no messing
+options, including XPRESS ("fast") compression, an integrity table, no messing
with absolute symbolic links, and an image name and description:
.RS
.PP
-@IMAGEX_PROGNAME@ capture somedir mywim.wim --compress=fast \\
+wimlib-imagex capture somedir mywim.wim --compress=fast \\
.RS
--check --norpfix "Some Name" "Some Description"
.RE
containing an NTFS filesystem:
.RS
.PP
-@IMAGEX_PROGNAME@ capture /dev/sda2 windows7.wim "Windows 7"
+wimlib-imagex capture /dev/sda2 windows7.wim "Windows 7"
.RE
.PP
or, on Windows, to capture a full NTFS volume you instead need to specify the
root directory of the mounted volume, for example:
.RS
.PP
-@IMAGEX_PROGNAME@ capture E:\\ windows7.wim "Windows 7"
+wimlib-imagex capture E:\\ windows7.wim "Windows 7"
.RE
.PP
-Same as above example with capturing an NTFS volume from \fB@IMAGEX_PROGNAME@\fR
+Same as above example with capturing an NTFS volume from \fBwimlib-imagex\fR
running on a UNIX-like system, but capture the WIM in the wimlib-specific
-"pipable" format that can be piped to \fB@IMAGEX_PROGNAME@ apply\fR:
+"pipable" format that can be piped to \fBwimlib-imagex apply\fR:
.RS
.PP
-@IMAGEX_PROGNAME@ capture /dev/sda2 windows7.wim "Windows 7" \\
+wimlib-imagex capture /dev/sda2 windows7.wim "Windows 7" \\
.br
.RS
--pipable
specified when using standard output as the WIM "file":
.RS
.PP
-@IMAGEX_PROGNAME@ capture /dev/sda2 - "Windows 7" | someprog
+wimlib-imagex capture /dev/sda2 - "Windows 7" | someprog
.RE
.SH SEE ALSO
-.BR @IMAGEX_PROGNAME@ (1),
-.BR @IMAGEX_PROGNAME@-apply (1)
+.BR wimlib-imagex (1),
+.BR wimlib-imagex-apply (1)
git://wimlib.net / wimlib / blobdiff