thereof, in the case of \fB@IMAGEX_PROGNAME@ extract\fR) to a directory on
UNIX-like systems. See \fBDIRECTORY EXTRACTION (WINDOWS)\fR for the
corresponding documentation for Windows.
-
+.PP
As mentioned, a WIM image can be applied to a directory on a UNIX-like system by
providing a \fITARGET\fR directory. However, it is important to keep in mind
that the WIM format was designed for Windows, and as a result WIM files can
.IP \[bu] 4
Encrypted files will not be extracted.
.IP \[bu]
-wimlib v1.6.3 and later: Sparse file attributes will not be extracted (same
+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.
Reparse point fixups are never done in the NTFS volume extraction mode on
UNIX-like systems.
.TP
-\fB--hardlink\fR
-When extracting a file from the WIM that is identical to a file that has already
-extracted, create a hard link rather than creating a separate file. This option
-causes all identical files to be hard-linked, overriding the hard link groups
-that are specified in the WIM image(s). In the case of extracting all images
-from the WIM, files may be hard-linked even if they are in different WIM images.
-.IP ""
-However, hard-linked extraction mode does have some additional quirks. Named
-data streams will not be extracted, and files can be hard linked even if their
-metadata is not fully consistent.
-.TP
-\fB--symlink\fR
-This option is similar to \fB--hardlink\fR, except symbolic links are created
-instead.
-.TP
\fB--unix-data\fR
(UNIX-like systems only) By default, in the directory extraction mode on UNIX,
\fB@IMAGEX_PROGNAME@ apply\fR will ignore both Windows-style security
git://wimlib.net / wimlib / blobdiff