-.TH WIMLIB-IMAGEX "1" "August 2015" "wimlib 1.8.2" "User Commands"
+.TH WIMLIB-IMAGEX "1" "January 2016" "wimlib 1.9.0" "User Commands"
.SH NAME
wimlib-imagex-apply \- Extract one image, or all images, from a WIM archive
.SH SYNOPSIS
.IP \[bu]
All names of all files, including names in the Win32 namespace, DOS namespace,
Win32+DOS namespace, and POSIX namespace. This includes hard links.
+.IP \[bu]
+Object IDs.
.PP
However, there are also several known limitations of the NTFS volume extraction
mode:
DOS names (8.3) names of files; however, the failure to set them is not
considered an error condition.
.IP \[bu]
-Hard links, if supported by the filesystem.
+Hard links, if supported by the target filesystem.
+.IP \[bu]
+Object IDs, if supported by the target filesystem.
.PP
Additional notes about extracting files on Windows:
.IP \[bu] 4
concatenated together on standard input. They can be provided in any order,
with the exception of the first part, which must be first.
.SH PIPABLE WIMS
-As of wimlib 1.5.0, \fBwimlib-imagex apply\fR supports applying a WIM from a
+Since wimlib v1.5.0, \fBwimlib-imagex apply\fR supports applying a WIM from a
nonseekable file, such as a pipe, provided that the WIM was captured with
-\fB--pipable\fR (see \fBwimlib-imagex capture\fR(1)). To use standard input
-as the WIM, specify "-" as \fIWIMFILE\fR. A useful use of this ability is to
-apply an image from a WIM while streaming it from a server. For example, to
-apply the first image from a WIM file available on a HTTP server to an NTFS
-volume on /dev/sda1, run something like:
+\fB--pipable\fR (see \fBwimlib-imagex capture\fR(1)). To use standard input as
+the WIM, specify "-" as \fIWIMFILE\fR. A useful use of this ability is to apply
+an image from a WIM while streaming it from a server. For example, to apply the
+first image from a WIM file available on a HTTP server to an NTFS volume on
+/dev/sda1, run something like:
.PP
.RS
wget -O - http://myserver/mywim.wim | wimapply - 1 /dev/sda1
.TP
\fB--unix-data\fR
(UNIX-like systems only) Restore UNIX owners, groups, modes, and device IDs
-(major and minor numbers) that were captured by \fBwimlib-imagex capture\fR
-with the \fB--unix-data\fR option. 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.
+(major and minor numbers) that were captured by \fBwimlib-imagex capture\fR with
+the \fB--unix-data\fR option. Since 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.
.TP
\fB--no-acls\fR
Do not restore security descriptors on extracted files and directories.
option.
.TP
\fB--compact\fR=\fIFORMAT\fR
-EXPERIMENTAL, Windows-only: compress the extracted files using System
-Compression, when possible. This only works on either Windows 10 or later, or
-on an older Windows to which Microsoft's wofadk.sys driver has been added.
-Several different compression formats may be used with System Compression, and
-one must be specified as \fIFORMAT\fR. The choices are: xpress4k, xpress8k,
-xpress16k, and lzx.
+Windows-only: compress the extracted files using System Compression, when
+possible. This only works on either Windows 10 or later, or on an older Windows
+to which Microsoft's wofadk.sys driver has been added. Several different
+compression formats may be used with System Compression, and one must be
+specified as \fIFORMAT\fR. The choices are: xpress4k, xpress8k, xpress16k, and
+lzx.
.IP ""
Exclusions are handled in the same way as with the \fB--wimboot\fR option.
That is: if it exists, the [PrepopulateList] section of the file
\\Windows\\System32\\WimBootCompress.ini in the WIM image will be read, and
files matching any of the patterns in this section will not be compressed.
-In addition, wimlib has a hardcoded list of files which it knows to, for
-compatibility with the Windows bootloader which only supports
-XPRESS4K-compressed files, always extract using either XPRESS4K or no
-compression.
+In addition, wimlib has a hardcoded list of files for which it knows, for
+compatibility with the Windows bootloader, to override the requested compression
+format.
.SH NOTES
\fIData integrity\fR: WIM files include SHA1 message digests for file data.
\fBwimlib-imagex apply\fR calculates the SHA1 message digest of every file
git://wimlib.net / wimlib / blobdiff