X-Git-Url: https://wimlib.net/git/?a=blobdiff_plain;f=doc%2Fimagex-export.1.in;h=ff76516e02291dc9085e10fdd09eaf8cea1b7b13;hb=5cdd60306facd14cc9dcc24471386451294ca73c;hp=9825e56a80e7dc12e8664c2300d48254ad70974d;hpb=7b5a88bcb70a3bdb24f3df414e8c71fdb95ee602;p=wimlib

diff --git a/doc/imagex-export.1.in b/doc/imagex-export.1.in
index 9825e56a..ff76516e 100644
--- a/doc/imagex-export.1.in
+++ b/doc/imagex-export.1.in
@@ -68,6 +68,12 @@ with the same compression type as the source WIM, additional threads will not
 be used, regardless of this parameter, since no data compression needs to be
 done in these cases.
 .TP
+\fB--rebuild\fR
+When exporting image(s) to an existing WIM: rebuild the entire WIM rather than
+appending data to the end of it.  Rebuilding the WIM is slower, but will save a
+little bit of space that would otherwise be left as a hole in the WIM.  Also see
+\fBimagex optimize\fR.
+.TP
 \fB--ref\fR="\fIGLOB\fR"
 File glob of additional split WIM parts that are part of the split WIM being
 exported.  See \fBSPLIT_WIMS\fR.
@@ -104,6 +110,15 @@ imagex export mywim.swm 1 other.wim --ref="mywim*.swm"
 .RE
 .PP
 
+.SH NOTES
+
+Unless --rebuild is specified, aborting an \fBimagex export\fR command mid-way
+through has a small chance of corrupting the destination WIM file.  However, a
+precaution is taken against this, so it should be very unlikely.  In the event
+of an aborted \fBimagex export\fR, \fBimagex optimize\fR can be run to remove
+extra data that may have been partially appended to the physical destination WIM
+file but not yet incorporated into the structure of the WIM.
+
 .SH EXAMPLES
 Export the second image of 'boot.wim' to the new WIM file 'new.wim', and
 change the compression type to maximum, if it wasn't maximum already: