X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=doc%2Ftar.texi;h=fe09c1275df27554bbf012ddc63046ea5097774f;hb=67cad07;hp=ac867659f28c3b69a62deb24e5f65153a3972761;hpb=7a968d67c82c81ee3c33be4d2cf34da20425f298;p=chaz%2Ftar diff --git a/doc/tar.texi b/doc/tar.texi index ac86765..fe09c12 100644 --- a/doc/tar.texi +++ b/doc/tar.texi @@ -35,7 +35,7 @@ This manual is for @acronym{GNU} @command{tar} (version from archives. Copyright @copyright{} 1992, 1994, 1995, 1996, 1997, 1999, 2000, 2001, -2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -1429,12 +1429,12 @@ example: @smallexample @group -$ @kbd{tar cfv archive /etc/mail} +$ @kbd{tar --create --verbose --file archive /etc/mail} tar: Removing leading `/' from member names /etc/mail/ /etc/mail/sendmail.cf /etc/mail/aliases -$ @kbd{tar tf archive} +$ @kbd{tar --test --file archive} etc/mail/ etc/mail/sendmail.cf etc/mail/aliases @@ -1879,15 +1879,14 @@ will act on the entire contents of the archive. @cindex return status Besides successful exits, @GNUTAR{} may fail for many reasons. Some reasons correspond to bad usage, that is, when the -@command{tar} command is improperly written. Errors may be -encountered later, while encountering an error processing the archive -or the files. Some errors are recoverable, in which case the failure -is delayed until @command{tar} has completed all its work. Some -errors are such that it would not meaningful, or at least risky, to -continue processing: @command{tar} then aborts processing immediately. -All abnormal exits, whether immediate or delayed, should always be -clearly diagnosed on @code{stderr}, after a line stating the nature of -the error. +@command{tar} command line is improperly written. Errors may be +encountered later, while processing the archive or the files. Some +errors are recoverable, in which case the failure is delayed until +@command{tar} has completed all its work. Some errors are such that +it would be not meaningful, or at least risky, to continue processing: +@command{tar} then aborts processing immediately. All abnormal exits, +whether immediate or delayed, should always be clearly diagnosed on +@code{stderr}, after a line stating the nature of the error. Possible exit codes of @GNUTAR{} are summarized in the following table: @@ -1924,7 +1923,7 @@ remote device (@pxref{Remote Tape Server}). allow you to perform a variety of tasks. You are required to choose one operating mode each time you employ the @command{tar} program by specifying one, and only one operation as an argument to the -@command{tar} command (two lists of four operations each may be found +@command{tar} command (the corresponding options may be found at @ref{frequent operations} and @ref{Operations}). Depending on circumstances, you may also wish to customize how the chosen operating mode behaves. For example, you may wish to change the way the output @@ -2786,7 +2785,6 @@ incremental format. @xref{Incremental Dumps}. @opsummary{lzma} @item --lzma -@itemx -J This option tells @command{tar} to read or write archives through @command{lzma}. @xref{gzip}. @@ -3359,6 +3357,12 @@ Use wildcards when matching member names with patterns. @item --wildcards-match-slash Wildcards match @samp{/}. @xref{controlling pattern-matching}. + +@opsummary{xz} +@item --xz +@itemx -J +Use @command{xz} for compressing or decompressing the archives. @xref{gzip}. + @end table @node Short Option Summary @@ -3380,7 +3384,7 @@ them with the equivalent long option. @item -G @tab @ref{--incremental}. -@item -J @tab @ref{--lzma}. +@item -J @tab @ref{--xz}. @item -K @tab @ref{--starting-file}. @@ -3742,7 +3746,7 @@ If @option{--block-number} (@option{-R}) is used, @command{tar} prints, along wi every message it would normally produce, the block number within the archive where the message was triggered. Also, supplementary messages are triggered when reading blocks full of NULs, or when hitting end of -file on the archive. As of now, if the archive if properly terminated +file on the archive. As of now, if the archive is properly terminated with a NUL block, the reading of the file may stop before end of file is met, so the position of end of file will not usually show when @option{--block-number} (@option{-R}) is used. Note that @GNUTAR{} @@ -5347,9 +5351,9 @@ and @command{mv}, for example) offer similar options. Backup options may prove unexpectedly useful when extracting archives containing many members having identical name, or when extracting archives on systems having file name limitations, making different members appear -has having similar names through the side-effect of name truncation. -(This is true only if we have a good scheme for truncated backup names, -which I'm not sure at all: I suspect work is needed in this area.) +as having similar names through the side-effect of name truncation. +@FIXME{This is true only if we have a good scheme for truncated backup names, +which I'm not sure at all: I suspect work is needed in this area.} When any existing file is backed up before being overwritten by extraction, then clashing files are automatically be renamed to be unique, and the true name is kept for only the last file of a series of clashing files. @@ -8406,7 +8410,8 @@ Creating a compressed archive is simple: you just specify a commands. The compression option is @option{-z} (@option{--gzip}) to create a @command{gzip} compressed archive, @option{-j} (@option{--bzip2}) to create a @command{bzip2} compressed archive, -@option{-J} (@option{--lzma}) to create an @asis{LZMA} compressed +@option{-J} (@option{--xz}) to create an @asis{XZ} archive, +@option{--lzma} to create an @asis{LZMA} compressed archive, @option{--lzop} to create an @asis{LSOP} archive, and @option{-Z} (@option{--compress}) to use @command{compress} program. For example: @@ -8504,6 +8509,7 @@ suffix. The following suffixes are recognized: @item @samp{.lzma} @tab @command{lzma} @item @samp{.tlz} @tab @command{lzma} @item @samp{.lzo} @tab @command{lzop} +@item @samp{.xz} @tab @command{xz} @end multitable @opindex gzip @@ -8548,13 +8554,17 @@ lose some compressibility. But this would have make recovering easier. So, there are pros and cons. We'll see! @opindex bzip2 +@item -J +@itemx --xz +Filter the archive through @code{xz}. Otherwise like +@option{--gzip}. + @item -j @itemx --bzip2 Filter the archive through @code{bzip2}. Otherwise like @option{--gzip}. @opindex lzma @item --lzma -@itemx -J Filter the archive through @command{lzma}. Otherwise like @option{--gzip}. @opindex lzop @@ -8889,11 +8899,7 @@ This option is meaningless with @option{--list} (@option{-t}). @item --preserve Same as both @option{--same-permissions} and @option{--same-order}. -The @option{--preserve} option has no equivalent short option name. -It is equivalent to @option{--same-permissions} plus @option{--same-order}. - -@FIXME{I do not see the purpose of such an option. (Neither I. FP.) -Neither do I. --Sergey} +This option is deprecated, and will be removed in @GNUTAR{} version 1.23. @end table @@ -9279,7 +9285,7 @@ is, file names having characters with the eight bit set, because they use signed checksums, while @GNUTAR{} uses unsigned checksums while creating archives, as per @acronym{POSIX} standards. On reading, @GNUTAR{} computes both checksums and -accept any. It is somewhat worrying that a lot of people may go +accepts any. It is somewhat worrying that a lot of people may go around doing backup of their files using faulty (or at least non-standard) software, not learning about it until it's time to restore their missing files with an incompatible file extractor, or