WIMLIB
-This is wimlib version 1.2.2 (December 2012). wimlib can be used to read,
+This is wimlib version 1.3.0 (March 2013). wimlib can be used to read,
write, and mount files in the Windows Imaging Format (WIM files). These files
are normally created by using the `imagex.exe' utility on Windows, but this
library provides a free implementation of imagex for UNIX-based systems.
+wimlib 1.3.0 has added experimental support for Windows. See the file
+"README.WINDOWS" for more details.
+
WIM FILES
A Windows Imaging (WIM) file is an archive. Like some other archive formats
and headers for libntfs-3g version 2011-4-12 or later to be installed.
Versions dated 2010-3-6 and earlier do not work because they are missing
the header xattrs.h (and the file xattrs.c, which contains functions we
- need).
+ need). libntfs-3g version 2013-1-13 is compatible only with wimlib
+ 1.2.4 and later.
* OpenSSL / libcrypto (optional)
wimlib can use the SHA1 message digest code from OpenSSL instead of
file format. 7-zip is able to extract and create WIMs (as well as files in many
other archive formats). However, wimlib is designed specifically to handle WIM
files and provides features previously only available in Microsoft's imagex.exe,
-such as the ability to mount WIMs read-write as well as read-only, and the
-ability to create LZX or XPRESS compressed WIMs.
+such as the ability to mount WIMs read-write as well as read-only, the ability
+to create LZX or XPRESS compressed WIMs, and the correct handling of security
+descriptors and hard links.
An earlier version of wimlib is being used to deploy Windows 7 from the Ultimate
Deployment Appliance. For more information see
probably will be OpenSSL. Some people believe that GPL code cannot be linked to
OpenSSL without a linking exception. As far as I know, I cannot officially
include a linking exception with the license of this library because several
-files could be considered derived works of LGPL code copyrighted by others. If
-you believe this to be a problem, configure with --without-libcrypto to avoid
+files could be considered derived works of code copyrighted by others. If you
+believe this to be a problem, configure with --without-libcrypto to avoid
linking with OpenSSL. There is no difference in functionality--- there will
just be stand-alone SHA1 message digest code built into the library.