From 75616449d7d57594867e785eba40d8594411c9d2 Mon Sep 17 00:00:00 2001 From: Eric Biggers Date: Thu, 30 Aug 2012 00:06:10 -0500 Subject: [PATCH] Update NEWS, docs --- NEWS | 21 +++++++++++++++++++++ README | 22 ++++++++++++---------- doc/imagex-apply.1.in | 16 ++++++++-------- 3 files changed, 41 insertions(+), 18 deletions(-) diff --git a/NEWS b/NEWS index a37eb6d9..78c8eb1c 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,26 @@ Only the most important changes more recent than version 0.6 are noted here. +Version 1.0.0: + Enough changes to call it version 1.0.0! + + Capturing a WIM directly from a NTFS volume, and applying a WIM directly + to a NTFS volume, is now supported. + + Hard links and symbolic links have much improved support. They are + supported for WIM capture, WIM application, and mounted WIMs (you can + even make them on read-write mounted WIMs). + + Alternate data streams are now supported on mounted WIMs through an + xattr or a Windows-style stream interface. Also they are supported when + capturing a WIM from NTFS or applying a WIM to NTFS. + + Using a capture configuration file is now supported (but not fully yet). + + SHA1 message digests are checked in more places, so we can make sure + applied and captured data is correct. + + Man pages have been updated and consolidated. + Version 0.7.2: Fixed segfault when unmounting read-only WIM. diff --git a/README b/README index 39f44784..c0dadaad 100644 --- a/README +++ b/README @@ -82,19 +82,21 @@ server for PXE booting. See the main page `doc/mkwinpeiso.1' for more details. * libfuse Unless configured with --without-fuse, wimlib requires a non-ancient - version of libfuse to be installed. see above). Most GNU/Linux - distributions already include this, but make sure you have the libfuse - package installed (libfuse-dev if your distribution distributes header - files separately). FUSE also requires a kernel module. - If the kernel module is available it will automatically be loaded if you - try to mount a WIM file. For more information see - http://fuse.sourceforge.net/. FUSE is also available for FreeBSD. + version of libfuse to be installed. Most GNU/Linux distributions + already include this, but make sure you have the libfuse package + installed, and also libfuse-dev if your distribution distributes header + files separately. FUSE also requires a kernel module. If the kernel + module is available it will automatically be loaded if you try to mount + a WIM file. For more information see http://fuse.sourceforge.net/. + FUSE is also available for FreeBSD. * libntfs-3g Unless configured with --without-ntfs-3g, wimlib requires the library - and headers for libntfs-3g to be installed. Currently, the version - dated 2012-1-15 is required because I've cloned some of the code from - the library. + and headers for libntfs-3g to be installed. Currently, the libntfs-3g + version dated 2012-1-15 is required because I've cloned some of the code + from the library, and it needs to compiled against the same version. + I'm hoping to be able to use future version of libntfs-3g without code + cloning after submitting some patches, however. * cdrkit (optional) * mtools (optional) diff --git a/doc/imagex-apply.1.in b/doc/imagex-apply.1.in index b4b16eae..06caf05e 100644 --- a/doc/imagex-apply.1.in +++ b/doc/imagex-apply.1.in @@ -16,19 +16,19 @@ image in the WIM, the name of an image in the WIM, or the keyword "all" to indicate that all images are to be extracted. Use the \fBimagex info\fR (1) command to show what images a WIM file contains. -\fBTARGET\fR specifies where to extract the WIM image(s) to. If \fBTARGET\fR +\fITARGET\fR specifies where to extract the WIM image(s) to. If \fITARGET\fR specifies a directory, the WIM image(s) are extracted to that directory. If -\fBTARGET\fR specifies a non-existent file, a directory is created in that -location and the WIM image(s) are extracted to that directory. If \fBTARGET\fR +\fITARGET\fR specifies a non-existent file, a directory is created in that +location and the WIM image(s) are extracted to that directory. If \fITARGET\fR specifies a regular file or block device, it is interpreted as a NTFS volume to which the WIM image is to be extracted. .SH NORMAL MODE -The normal extraction mode is entered when \fBTARGET\fR is a directory or +The normal extraction mode is entered when \fITARGET\fR is a directory or non-existent file. If a single WIM image is being extracted, it will be extracted with the root of the image corresponding to the directory named by -\fBTARGET\fR; or, if the keyword \fBall\fR is given, the images are extracted +\fITARGET\fR; or, if the keyword \fBall\fR is given, the images are extracted into subdirectories of \fITARGET\fR that will be named after the image names, falling back to the image indices if there is an image with no name. \fITARGET\fR can specify a directory on any type of filesystem. @@ -65,11 +65,11 @@ Short (DOS) names for files .SH NTFS MODE -A special extraction mode is entered when \fBTARGET\fR is a regular file or -block device. \fBTARGET\fR is interpreted as an NTFS volume and opened using +A special extraction mode is entered when \fITARGET\fR is a regular file or +block device. \fITARGET\fR is interpreted as an NTFS volume and opened using libntfs-3g. If successful, the WIM image is extracted to the root of the NTFS volume in a special mode that preserves all, or almost all, information -contained in the WIM. \fBIMAGE\fR may not be "all" for this action. +contained in the WIM. \fIIMAGE\fR may not be "all" for this action. The NTFS volume does not need to be empty, although it's expected that it be empty for the intended use cases. A new NTFS filesystem can be created using -- 2.43.0