X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=doc%2Ftar.info-2;h=3c726720da652a9b1129b23a6cdd0d9fa71a91f3;hb=1a44d77d50f4fb37c0410eed04b82303624ea2ec;hp=18117aba932b1a7bc4059cbbb8af2eff4193dc08;hpb=dda6367c9eac71da8f2ab1c60b3df60f19ce4755;p=debian%2Ftar diff --git a/doc/tar.info-2 b/doc/tar.info-2 index 18117aba..3c726720 100644 --- a/doc/tar.info-2 +++ b/doc/tar.info-2 @@ -1,6 +1,6 @@ This is tar.info, produced by makeinfo version 4.13 from tar.texi. -This manual is for GNU `tar' (version 1.25, 5 November 2010), which +This manual is for GNU `tar' (version 1.26, 12 March 2011), which creates and extracts files from archives. Copyright (C) 1992, 1994, 1995, 1996, 1997, 1999, 2000, 2001, 2003, @@ -77,7 +77,7 @@ v7 Makefiles. This practice will change in the future, in the meantime, however this means that projects containing file names more than 99 characters long will not be able to use GNU `tar' - 1.25 and Automake prior to 1.9. + 1.26 and Automake prior to 1.9. ustar Archive format defined by POSIX.1-1988 specification. It stores @@ -213,7 +213,7 @@ a list of recognized suffixes). Some compression programs are able to handle different compression formats. GNU `tar' uses this, if the principal decompressor for the given format is not available. For example, if `compress' is not -installed, `tar' will try to use `gzip'. As of version 1.25 the +installed, `tar' will try to use `gzip'. As of version 1.26 the following alternatives are tried(2): Format Main decompressor Alternatives @@ -692,9 +692,9 @@ archive naming the target of the link (a `1' type block). In that way, the actual file contents is stored in file only once. For example, consider the following two files: - $ ls - -rw-r--r-- 2 gray staff 4 2007-10-30 15:11 one - -rw-r--r-- 2 gray staff 4 2007-10-30 15:11 jeden + $ ls -l + -rw-r--r-- 2 gray staff 4 2007-10-30 15:11 one + -rw-r--r-- 2 gray staff 4 2007-10-30 15:11 jeden Here, `jeden' is a link to `one'. When archiving this directory with a verbose level 2, you will get an output similar to the following: @@ -2605,8 +2605,8 @@ contents. If verbose display is requested, it will also be explicitly marked as in the example below: $ tar --verbose --list --file=iamanarchive - V--------- 0 0 0 1992-03-07 12:01 iamalabel--Volume Header-- - -rw-r--r-- ringo user 40 1990-05-21 13:30 iamafilename + V--------- 0/0 0 1992-03-07 12:01 iamalabel--Volume Header-- + -rw-r--r-- ringo/user 40 1990-05-21 13:30 iamafilename However, `--list' option will cause listing entire contents of the archive, which may be undesirable (for example, if the archive is @@ -3069,7 +3069,7 @@ Appendix A Changes ****************** This appendix lists some important user-visible changes between version -GNU `tar' 1.25 and previous versions. An up-to-date version of this +GNU `tar' 1.26 and previous versions. An up-to-date version of this document is available at the GNU `tar' documentation page (http://www.gnu.org/software/tar/manual/changes.html). @@ -4105,12 +4105,12 @@ backups (*note Incremental Dumps::). It contains the status of the file system at the time of the dump and is used to determine which files were modified since the last backup. - GNU `tar' version 1.25 supports three snapshot file formats. The + GNU `tar' version 1.26 supports three snapshot file formats. The first format, called "format 0", is the one used by GNU `tar' versions up to 1.15.1. The second format, called "format 1" is an extended version of this format, that contains more metadata and allows for further extensions. It was used by version 1.15.1. Starting from -version 1.16 and up to 1.25, the "format 2" is used. +version 1.16 and up to 1.26, the "format 2" is used. GNU `tar' is able to read all three formats, but will create snapshots only in format 2. @@ -4166,7 +4166,7 @@ snapshots only in format 2. 2. `Format 2' snapshot file begins with a format identifier, as described for version 1, e.g.: - GNU tar-1.25-2 + GNU tar-1.26-2 This line is followed by newline. Rest of file consists of records, separated by null (ASCII 0) characters. Thus, in contrast