.TH IMAGEX "1" "March 2013" "imagex (wimlib) wimlib @VERSION@" "User Commands"
.SH NAME
-imagex-capture, imagex-append \- Capture a WIM image from a directory tree
+imagex-capture, imagex-append \- Create or append a WIM image
.SH SYNOPSIS
\fBimagex capture\fR \fISOURCE\fR \fIWIMFILE\fR [\fIIMAGE_NAME\fR] \
creates a new WIM file containing the captured image, while the \fBimagex
append\fR command appends the captured image to an existing WIM file.
+Note: this man page primarily documents the UNIX behavior. See \fBWINDOWS
+VERSION\fR for information specific to the Windows build of wimlib.
+
A WIM image is an independent directory tree in the WIM file. A WIM file may
contain any number of separate images. However, files are stored only one time
in the entire WIM, regardless of how many images the file appears in.
directory. The WIM image will be captured from the directory tree rooted at
this directory. The directory may be on any type of filesystem.
-In this normal image capture mode, we capture the following information from the
-directory tree:
+In this mode, the following information is captured from the directory tree:
.IP \[bu] 4
The "normal" name and contents of each file and directory
.PP
-However, in the normal image capture mode, we do \fInot\fR capture the following
-information from the directory tree:
+However, in this mode, the following information is \fInot\fR captured from the
+directory tree:
.IP \[bu] 4
File permissions. The resulting WIM image will not contain any security
.IP \[bu]
No alternate data streams will be captured, since these do not exist on
POSIX-compliant filesystems. The resulting WIM image will not contain any
-alternate data streams.
+alternate data streams. (Exception: see the \fB--unix-data\fR option.)
.SH NTFS MODE
\fISOURCE\fR. You must specify the NTFS volume itself (and it must be
unmounted, and you must have permission to read from it).
-More specifically, in this mode, we capture the following types of information
+More specifically, in this mode, the following types of information are captured
from the NTFS volume:
.IP \[bu] 4
Yet another capture mode is entered when the \fB--source-list\fR option is
given. It is essentially an extension of the \fBNORMAL MODE\fR that allows
multiple files or directories to be incorporated into a WIM image using a single
-\fBimagex capture\fR command. See the documentation for \fB--source-list\fR
-below.
+\fBimagex capture\fR or \fBimagex append\fR command. See the documentation for
+\fB--source-list\fR below.
+
+.SH WINDOWS VERSION
+
+This section documents the differences between \fBimagex capture\fR and
+\fBimagex append\fR in the Windows builds of wimlib versus the rest of this man
+page, which is written to document UNIX build.
+
+\fBimagex capture\fR and \fBimagex append\fR do not have separate "normal" and
+"NTFS" modes on Windows. There is simply one mode, and it uses the Windows API
+to capture NTFS-specific information, including alternate data streams, reparse
+points, hard links, and file attributes. So, you essentially get the advantages
+of the "NTFS mode" documented above, but you can capture a WIM image from any
+directory, not just an entire NTFS volume. This is essentially the same
+behavior as Microsoft's ImageX.
+
+The \fB--source-list\fR option is supported on Windows, but the
+\fB--dereference\fR option is not.
+
+Except for the differences documented in this section, the Windows build of
+\fBimagex capture\fR and \fBimagex append\fR should be essentially equivalent to
+the UNIX build. However, one additional thing to note is that wimlib's Windows
+ImageX is NOT written to be command-line compatible with Microsoft's ImageX,
+although they are very similar.
.SH OPTIONS
.TP 6
directories. 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 \fBimagex\fR to archive files on
-UNIX. Microsoft's software will not understand this special information.
+UNIX. Microsoft's software will not understand this special
+information.
.TP
\fB--source-list\fR
-\fBimagex capture\fR and \fBimagex append\fR, as of wimlib 1.2.7, support a new
+\fBimagex capture\fR and \fBimagex append\fR, as of wimlib 1.3.0, support a new
option to create a WIM image from multiple 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
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.
+if the same file appears in different overlays to the same directory.
Filenames containing whitespace may be quoted with either single quotes or
double quotes. Quotes may not be escaped.
.RE
.PP
Append an image to the WIM we just captured, but do it from a NTFS volume on the
-partition /dev/sda2, and name the image "Windows 7" and give it a description.
-You do not need to specify the compression type, because the WIM already is
-using LZX compression and this cannot be changed. You need to specify
-\fB--check\fR if you don't want the integrity table to be discarded.
+partition /dev/sda2 and name the image "Windows 7". You do not need to specify
+the compression type, because the WIM already is using LZX compression and this
+cannot be changed. You need to specify \fB--check\fR if you don't want the
+integrity table to be discarded.
.RS
.PP
-imagex append /dev/sda2 mywim.wim --check "Windows 7" "Warning: This operating
-system has been approved by Bill Gates"
+imagex append /dev/sda2 mywim.wim --check "Windows 7"
.RE
.PP
git://wimlib.net / wimlib / blobdiff