X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=doc%2Fman1%2Fwimlib-imagex-apply.1;h=1245b7ba4865f93c23293fffc705078d64af459e;hp=e9f032e61d377a8c7ada35375941bc076b2dc8bf;hb=4fd6ac2eb3d871d0beb949d88c144e0ca64ea0cb;hpb=b8efa8686896d10fe2b2287eabc85d5a470c8202

diff --git a/doc/man1/wimlib-imagex-apply.1 b/doc/man1/wimlib-imagex-apply.1
index e9f032e6..1245b7ba 100644
--- a/doc/man1/wimlib-imagex-apply.1
+++ b/doc/man1/wimlib-imagex-apply.1
@@ -1,4 +1,4 @@
-.TH WIMLIB-IMAGEX "1" "November 2015" "wimlib 1.8.3" "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
@@ -118,16 +118,15 @@ DOS/Windows file attribute flags.
 .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:
 .IP \[bu] 4
 Encrypted files will not be extracted.
 .IP \[bu]
-wimlib v1.7.0 and later:  Sparse file attributes will not be extracted (same
-behavior as ImageX/DISM/WIMGAPI).  wimlib v1.6.2 and earlier:  Although sparse
-file attributes will be applied, the full data will be extracted to each sparse
-file, so extracted "sparse" files may not actually contain any sparse regions.
+Sparse file attributes will not be extracted.
 .PP
 Regardless, since almost all information from the WIM image is restored in this
 mode, it is possible (and fully supported) to restore an image of an actual
@@ -175,13 +174,15 @@ descriptors for individual files or directories may be omitted or only partially
 set if the user does not have permission to set them, which can be a problem if
 \fBwimlib-imagex\fR is run as a non-Administrator.
 .IP \[bu]
-File attributes, including hidden, sparse, compressed, encrypted, etc, when
-supported by the filesystem.
+File attributes, including hidden, compressed, encrypted, etc, when supported by
+the filesystem.
 .IP \[bu]
 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
@@ -189,6 +190,8 @@ Additional notes about extracting files on Windows:
 exact metadata and data of the WIM image, for example due to features mentioned
 above not being supported by the target filesystem.
 .IP \[bu]
+Sparse file attributes will not be extracted.
+.IP \[bu]
 Since encrypted files (with FILE_ATTRIBUTE_ENCRYPTED) are not stored in
 plaintext in the WIM image, \fBwimlib-imagex\fR cannot restore encrypted
 files to filesystems not supporting encryption.  Therefore, on such filesystems,
@@ -250,13 +253,13 @@ option is unneeded; instead you must ensure that all the split WIM parts are
 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
@@ -301,11 +304,10 @@ UNIX-like systems.
 .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.