mount_image.c: add fallback definitions of RENAME_* constants

[wimlib] / doc / man1 / wimapply.1

diff --git a/doc/man1/wimapply.1 b/doc/man1/wimapply.1
index b2181361f24fb285f92135ea354980f5d7c4723b..448fafda7ad511907bc958ea9a5d36064ca480f3 100644 (file)
--- a/doc/man1/wimapply.1
+++ b/doc/man1/wimapply.1
@@ -1,4 +1,4 @@
-.TH WIMAPPLY "1" "November 2018" "wimlib 1.13.0" "User Commands"
+.TH WIMAPPLY "1" "February 2024" "wimlib 1.14.4" "User Commands"
 .SH NAME
 wimapply \- Apply a WIM image
 .SH SYNOPSIS
@@ -217,7 +217,7 @@ 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
+wget -O - https://myserver/mywim.wim | wimapply - 1 /dev/sda1
 .RE
 .PP
 Pipable WIMs may also be split into multiple parts, just like normal WIMs.  To
@@ -355,15 +355,22 @@ files matching any of the patterns in this section will not be compressed.
 In addition, wimlib has a hardcoded list of files for which it knows, for
 compatibility with the Windows bootloader, to override the requested compression
 format.
+.TP
+\fB--recover-data\fR
+If a file is corrupted (its stored hash doesn't match its actual hash, or some
+parts of it can't be decompressed), extract the corrupted file anyway with a
+warning, rather than aborting with an error.  This may be useful to recover data
+if a WIM archive was corrupted.  Note that recovering data is not guaranteed to
+succeed, as it depends on the type of corruption that occurred.
 .SH NOTES
 \fIData integrity\fR: WIM files include checksums of file data.  To detect
 accidental (non-malicious) data corruption, wimlib calculates the checksum of
 every file it extracts and issues an error if it does not have the expected
-value.  (This default behavior seems equivalent to the \fB/verify\fR option of
-ImageX.)  In addition, a WIM file can include an integrity table (extra
-checksums) over the raw data of the entire WIM file.  For performance reasons
-wimlib does not check the integrity table by default, but the \fB--check\fR
-option can be passed to make it do so.
+value, unless the \fB--recover-data\fR option is given.  (This default behavior
+seems equivalent to the \fB/verify\fR option of ImageX.)  In addition, a WIM
+file can include an integrity table (extra checksums) over the raw data of the
+entire WIM file.  For performance reasons wimlib does not check the integrity
+table by default, but the \fB--check\fR option can be passed to make it do so.
 .PP
 \fIESD files\fR: wimlib can extract files from solid-compressed WIMs, or "ESD"
 (.esd) files, just like from normal WIM (.wim) files.  However, Microsoft