+archive the symlinks themselves.) This flag is only valid in the normal image
+capture mode.
+.TP
+\fB--config\fR=\fIFILE\fR
+Specifies a configuration file for capturing the new image. The configuration
+file specifies files that are to be treated specially during the image capture.
+
+The format of the configuration file is a number of sections containing file
+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 file globs to
+exclude from capture, while the [ExclusionException] section specifies a list of
+file globs to include in the capture even if the matched file or directory name
+also appears in the [ExclusionList].
+
+Relative globs with only one path component match against a filename in any
+directory. Relative globs with multiple path components, as well as absolute
+globs, are treated as paths starting at the root directory of capture, or the
+root of the NTFS volume for NTFS 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.
+
+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. However, globs with spaces in them currently must not be quoted.
+Empty lines are ignored.
+
+If this option is not specified the following default configuration file is
+used:
+
+.RS
+.RS
+.PP
+.nf
+[ExclusionList]
+\\$ntfs.log
+\\hiberfil.sys
+\\pagefile.sys
+\\System Volume Information
+\\RECYCLER
+\\Windows\\CSC
+
+[CompressionExclusionList]
+*.mp3
+*.zip
+*.cab
+\\WINDOWS\\inf\\*.pnf
+.RE
+.RE
+
+.SH NOTES
+
+\fBimage append\fR does not support appending an image to a split WIM.
+
+The two different capture modes only specify the data that is captured and don't
+specify a special WIM format. A WIM file can contain images captured using
+different modes. However, all images in a WIM must have the same compression
+type, and \fBimagex\fR always enforces this.
+
+\fBimagex\fR writes WIMs having the version number 0x10d00 and a compressed
+stream chunk size of 32768. The only WIMs I've seen that are different from
+this are some pre-Vista WIMs that had a different version number.
+
+Unless \fB--rebuild\fR is specified, aborting an \fBimagex append\fR command
+mid-way through has a small chance of corrupting the WIM file. However, a
+precaution is taken against this, so it should be very unlikely. In the event
+of an aborted \fBimagex append\fR, \fBimagex optimize\fR may be run to remove
+extra data that may have been partially appended to the physical WIM file but
+not yet incorporated into the structure of the WIM.
+
+Capturing or appending an image happens in two main phases: (1) scanning the
+directory or NTFS volume to checksum all the files and determine the streams to
+be written, and (2) writing the new streams to the WIM file. Streams are not
+stored in memory after (1), since there could easily be gigabytes of data;
+instead, they are read again during step (2); however, duplicate streams in the
+image, and streams already existing in any other image in the WIM, are not read
+again. In the future, it may be possible to introduce the ability to capture an
+image with reading each file only one time, although this mode would have some
+limitations--- for example, a stream might be compressed only to be thrown away
+as a duplicate once it's been checksummed.