1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216 |
- GNU tar NEWS - User visible changes. 2010-01-26
- Please send GNU tar bug reports to <bug-tar@gnu.org>
- version 1.22.90 (Git)
- When listing or extracting archives, the actual record size is
- reported only if the archive is read from a device (as opposed
- to regular files and pipes).
- When a read-only operation (e.g. --list or --extract) is requested
- on a regular file, tar attemtps to speed up accesses by using lseek.
- The `--warning' command line option allows to suppress or enable
- particular warning messages during `tar' run. It takes a single
- argument (a `keyword'), identifying the class of warning messages
- to affect. If the argument is prefixed with `no-', such warning
- messages are suppressed. For example,
- tar --warning=no-alone-zero-block -x -f archive
- suppresses the output of `A lone zero block' diagnostics, which is
- normally issued if `archive' ends with a single block of zeros.
- See Tar Manual, section 3.9 "Controlling Warning Messages", for a
- detailed discussion.
- The `--level=N' option sets the incremental dump level N. It
- is valid when used in conjunction with the -c and --listed-incremental
- options. So far the only meaningful value for N is 0. The
- `--level=0' option forces creating the level 0 dump, by truncating
- the snapshot file if it exists.
- If a file or directory is removed while incremental dump is
- in progress, tar exact actions depend on whether this file
- was explicitly listed in the command line, or was gathered
- during file system scan.
- If the file was explicitly listed in the command line, tar
- issues error message and exits with the code 2, meaning
- fatal error.
- Otherwise, if the file was gathered during the file system
- scan, tar issues a warning, saying "File removed before we read it",
- and sets the exit code to 1, which means "some files differ".
- If the --warning=no-file-removed option is given, no warning
- is issued and the exit code remains 0.
- Modification times in the ustar header blocks for the
- extended headers are set to the mtimes of the corresponding archive
- members. This can be overridden by the
- --pax-opion='exthdr.mtime=STRING'
- command line option. The STRING is either the number of seconds since
- the Epoch or a `Time reference' (see below).
- Modification times in the ustar header blocks for the global
- extended headers are set to the time when tar was invoked.
- This can be overridden by the
- --pax-opion='globexthdr.mtime=STRING'
- command line option. The STRING is either the number of seconds since
- the Epoch or a `Time reference' (see below).
- Any value from the --pax-option argument that is enclosed in a pair
- of curly braces represents a time reference. The string between the
- braces is understood either as a textual time representation, as described in
- chapter 7, "Date input formats", of the Tar manual, or as a name of
- an existing file, starting with `/' or `.'. In the latter
- case, the value is replaced with the modification time of that file.
- succesfully stored in the archive.
- format).
- version 1.22 - Sergey Poznyakoff, 2009-03-05
- Tar uses xz for compression if one of the following conditions is met:
- 1. The option --xz or -J (see below) is used.
- 2. The xz binary is set as compressor using --use-compress-program option.
- 3. The file name of the archive being created ends in `.xz' and
- auto-compress option (-a) is used.
- Xz is used for decompression if one of the following conditions is met:
- 1. The option --xz or -J is used.
- 2. The xz binary is set as compressor using --use-compress-program option.
- 3. The file is recognized as xz compressed stream data.
- The -I option is assigned as a short equivalent for
- --use-compress-program.
- version 1.21 - Sergey Poznyakoff, 2008-12-27
- A shortcut for --lzma.
- Cancels the effect of previous --auto-compress (-a) option.
- Cancels the effect of previous --null option.
- If tar is unable to determine archive compression format, it falls
- back to using archive suffix to determine it.
- Using --exclude-vcs handles also files used internally by Bazaar,
- Mercurial and Darcs.
- Name transformation expressions understand additional flags that
- control type of archive members affected by them. The flags are:
- - r
- Apply transformation to regular archive members.
- - s
- Apply transformation to symbolic link targets.
- - h
- Apply transformation to hard link targets.
- Corresponding upper-case letters negate the meaning, so that
- `H' means ``do not apply transformation to hard link targets.''
- The scope flags are listed in the third part of an `s' expression,
- e.g.:
- tar --transform 's|^|/usr/local/|S'
- Default is `rsh', which means that transformations are applied to
- both regular archive members and to the targets of symbolic and hard
- links. If several transform expressions are used, the default flags
- can be changed using `flags=' statement before the expressions, e.g.:
- tar --transform 'flags=S;s|^|/usr/local/|S'
- is fixed.
- the expected value (either default, or set on the command line), tar
- always prints a warning if verbosity level is set to 1 or greater,
- i.e. if either -t or -v option is given.
- version 1.20 - Sergey Poznyakoff, 2008-04-14
- With --create, selects compression algorithm basing on the suffix
- of the archive file name.
- Selects LZMA compression algorithm
- During archive creation, dereferences hard links and stores the files
- they refer to, instead of creating usual hard link members (type '1').
- This action allows to specify an action to be executed upon hitting a
- checkpoint. Recognized actions are: dot, echo (the default),
- echo=string, ttyout=string, exec=cmdline, and sleep=value. Any number
- of `--checkpoint-action' options can be specified, the actions will be
- executed in order of their appearance in the command line. See
- chapter 3.8 "Checkpoints" for a complete description.
- The `--no-check-device' option disables comparing device numbers during
- preparatory stage of an incremental dump. This allows to avoid
- creating full dumps if the device numbers change (e.g. when using an
- LVM snapshot).
- The `--check-device' option enables comparing device numbers. This is
- the default. This option is provided to undo the effect of the previous
- `--no-check-device' option, e.g. if it was set in TAR_OPTIONS
- environment variable.
- Any number of `--transform' options can be given in the command line.
- The specified transformations will be applied in turn.
- The argument to `--transform' option can be a list of replace
- expressions, separated by a semicolon (as in `sed').
- Filename transformations are applied to symbolic link targets
- during both creation and extraction. Tar 1.19 used them only
- during extraction.
- For a detailed description, see chapter 6.7 "Modifying File and Member
- Names".
- The value of the blocking factor is made available to info and
- checkpoint scripts via environment variable TAR_BLOCKING_FACTOR.
- Improved (sped up) extracting from incremental archives.
- archives.
- version 1.19 - Sergey Poznyakoff, 2007-10-10
- Excludes directories and files, created by several widely used version
- control systems, e.g. "CVS/", ".svn/", etc.
- The following options now work with incremental archives as well:
- --exclude-caches
- --exclude-caches-all
- --exclude-tag
- --exclude-tag-all
- --exclude-tag-under
- Previous versions always stored absolute file names in rename
- records, even if -P was not used. This is fixed: rename records
- contain file names processed in accordance with the command line
- settings.
-
- When supplied an archive smaller than 512 bytes in reading mode (-x,
- -t), the previous version of tar silently ignored it, exiting with
- code 0. It is fixed. Tar now issues the following diagnostic message:
- 'This does not look like a tar archive', and exits with code 2.
- version 1.18 - Sergey Poznyakoff, 2007-06-29
- version 1.17 - Sergey Poznyakoff, 2007-06-08
- sparse members with spurious zero blocks.
- a full dump when both options were given.
- even though all requested members has already been extracted.
- In addition to affecting regular archive members, the --transform
- option affects hard and soft link targets and the --strip-components
- option affects hard link targets as well.
- it to the file descriptor stored in the environment variable `TAR_FD'.
- version 1.16.1 - Sergey Poznyakoff, 2006-12-09
- files whose presence in a directory means that the directory should not
- be archived.
- CACHEDIR.TAG file from being archived. Previous versions excluded
- directory contents only, while the directories themselves were
- still added to the archive.
- This GNU extension was generated only by very old versions of GNU 'tar'.
- Unfortunately its implementation had security holes; see
- <http:
- We don't expect that any tar archives in practical use have type 'N'
- records, but if you have one and you trust its contents, you can
- decode it with GNU tar 1.16 or earlier.
- files extracted by 'tar -x --same-owner' (or plain 'tar -x', when
- running as root) to be accessed by users that they shouldn't have been.
- version 1.16 - Sergey Poznyakoff, 2006-10-21
- changed while being read. Previous versions exited with code 2 (fatal
- error), and only if some files were truncated while being archived.
- members during creation.
- the listing to stderr.
- version 1.15.91 - Sergey Poznyakoff, 2006-06-16
- Previous versions of GNU tar assumed shell-style globbing when
- extracting from or listing an archive. For example:
- tar xf foo.tar '*.c'
- would extract all files whose names end in '.c'. This behavior
- was not documented and was incompatible with traditional tar
- implementations. Therefore, starting from this version, GNU tar
- no longer uses globbing by default. For example, the above invocation
- is now interpreted as a request to extract from the archive the file
- named '*.c'.
- To treat member names as globbing patterns, use --wildcards option.
- If you wish tar to mimic the behavior of versions up to 1.15.90,
- add --wildcards to the value of the environment variable TAR_OPTIONS.
- The exact way in which tar interprets member names is controlled by the
- following command line options:
- --wildcards use wildcards
- --anchored patterns match file name start
- --ignore-case ignore case
- --wildcards-match-slash wildcards match `/'
- Each of these options has a '--no-' counterpart that disables its
- effect (e.g. --no-wildcards).
- These options affect both the interpretation of member names from
- command line and that of the exclusion patterns (given with --exclude
- and --exclude-from options). The defaults are:
- 1. For member names: --no-wildcards --anchored
- 2. For exclusion patterns: --wildcards --no-anchored --wildcards-match-slash
- The options can appear multiple times in the command line, thereby
- changing the way command line arguments are interpreted. For example,
- to use case-insensitive matching in exclude patterns and to revert to
- case-sensitive matching for the rest of command line, one could write:
- tar xf foo.tar --ignore-case --exclude-from=FILE --no-ignore-case file.name
- with UNIX98. This ends the transition period started with version 1.14.
- in the archive or member names before extracting. The option takes a
- sed replace expression as its argument. For example,
- tar cf foo.tar --transform 's,^,prefix/,'
- will add 'prefix/' to all file names stored in foo.tar.
- versions it worked only with --extract.
- or archive. It generalizes --show-stored-names option, introduced in
- 1.15.90. In particular, when creating an archive in verbose mode, it lists
- member names as stored in the archive, i.e., with any eventual prefixes
- removed and file name transformations applied. The option is useful,
- for example, while comparing `tar cv' and `tar tv' outputs.
- as well as that about directories.
- of records between the two successive checkpoints. Optional dot
- starting the argument intructs tar to print dots instead of textual
- checkpoints.
- understood it only with --create). If an argument to this option is
- given, it specifies the signal upon delivery of which the statistics
- is to be printed. Both forms of this option (with and without
- argument) can be given to in a single invocation of tar.
- version 1.15.90 - Sergey Poznyakoff, 2006-02-19
- The file specified with -T may include any valid `tar' options,
- including another -T option.
- Compatibility note: older versions of tar would only recognize -C
- as an option name within the file list file. Now any file whose name
- starts with - is handled as an option. To insert file names starting with
- dash, use the --add-file option.
- automatically. It is no longer necessary to give the --null option.
- This is useful for processing output from `find dir -print0'.
- An orthogonal option --unquote is provided as well.
- If an argument is specified, the label is compared against its value.
- Tar exits with code 0 if the two strings match, and with code 2 if
- they do not.
- If no argument is given, the --verbose option is implied. In this case,
- tar prints the label name if present and exits with code 0.
- it lists member names as stored in the archive, i.e., with any eventual
- prefixes removed. The option is useful, for example, while comparing
- `tar cv' and `tar tv' outputs.
- specified command.
- of recent Linux kernels to avoid some problems when preserving file
- access times.
- and permissions of extracted directories until the end of extraction.
- This is necessary for restoring from archives with unusual member
- ordering (in particular, those created with --no-recursion option).
- This option is implied when restoring from incremental archives.
- options. Currently it disables '!' escape in multi-volume name menu.
- quotes member names on output. The --quoting-style takes an argument
- specifying the quoting style to use (literal, shell, shell-always,
- c, escape, locale, clocale). The argument to --quote-chars is a string
- specifying characters to quote, even if the selected quoting style
- would not quote them otherwise. The option --no-quote-chars is
- provided to disable quoting certain characters.
- get current archive name from the environment variable TAR_ARCHIVE and
- the volume number from the variable TAR_VOLUME. It can alter the
- archive name by writing new name to the file descriptor 3.
- time stamps to full nanosecond resolution, though, until the kernel
- guys get their act together and give us a system call to set file time
- stamps to nanosecond resolution.
- not full resolution, to avoid using up too many output columns.
- Nanosecond resolution is now supported, but that would be too much.
- used to read an extra block of data after a long name header
- if length of the member name was divisible by block size (512).
- Consequently, the file pointer was set off and the next member
- was not processed correctly.
- during reading.
- modification times.
- meta-data cannot be stored in the header due to format limitations
- (for ustar and v7 formats).
- license, and credits. This reverts to the behavior of tar 1.14 and
- earlier, and conforms to the GNU coding standards. The --license (-L)
- option introduced in tar 1.15 has been removed, since it's no longer
- needed.
- version 1.15.1 - Sergey Poznyakoff, 2004-12-21
- This version fixes a bug introduced in 1.15 which caused
- tar to refuse to extract files from standard input.
- version 1.15 - Sergey Poznyakoff, 2004-12-20
- necessary to specify -Z, -z, or -j options to read them. Thus, you can
- now run `tar tf archive.tar.gz'.
- prevents directory hierarchies residing on different devices
- from being purged.
- With the previous versions of tar it was dangerous to create
- incremental dumps with --one-file-system option, since they
- would recursively remove mount points when restoring from the
- back up. This change fixes the bug.
- the GNU convention.
- seeks.
- or some patterns. This is to prevent accidental restores.
- the file names had their prefixes stripped off.
- automatically on archive creation. Cache directories are those
- containing a standardized tag file, as specified at:
- http:
- the `rmt' utility. This supersedes DEFAULT_RMT_COMMAND variable
- introduced in version 1.14
- where to install `rmt' utility. This is necessary since modifying
- --libexecdir as was suggested for version 1.14 produced a side effect: it
- also modified installation prefix for backup scripts (if
- --enable-backup-scripts was given).
- Do not allow multivolume archives to begin with such filenames.
- previous versions of tar were not able to extract it, since they
- were trying to link the file to itself, which always failed and
- lead to removing the already extracted copy. Preserve the first
- extracted copy in such cases.
- didn't affect the functionality, but was logically incorrect).
- versions failed to recognize \a and \v).
- versions of tar used to overwrite last archive block with zeroes.
- version 1.14 - Sergey Poznyakoff, 2004-05-11
- by presetting the environment variable DEFAULT_ARCHIVE_FORMAT.
- Allowed values are GNU, V7, OLDGNU and POSIX.
- path elements from the name of the file being extracted.
- option is now the default; use --no-overwrite-dir if you prefer
- the previous default behavior.
- does the same as --no-same-owner GNU tar option. This is compatible
- with UNIX98 tar. Otherwise, its effect is the same as that of
- --old-archive option. This latter is deprecated and will be removed
- in future.
- for a file being archived. This corresponds to the UNIX98 -l option.
- The current semantics of the -l option is retained for compatibility
- with previous releases, however such usage is strongly deprecated as
- the option will change to its UNIX98 semantics in the future releases.
- the subcommands --delete, --diff, --extract or --list when a list of
- files is given either on the command line or via -T option. This
- option instructs tar to process only the Nth occurrence of each named
- file. N defaults to 1, so `tar -x -f archive --occurrence filename'
- extracts the first occurrence of `filename' from `archive'
- and terminates without scanning to the end of the archive.
- keywords in `pax' extended headers. It is equivalent to `pax'
- -o option.
- individual files, as well as on directories.
- The scripts are compiled and installed if --enable-backup-scripts
- option is given to configure.
- which is consistent with the location where the version of "rmt"
- included in the package is installed. Previous versions of tar
- used "/etc/rmt". To install "rmt" to its traditional location,
- run configure with option --libexecdir=/etc. Otherwise, if you
- already have rmt installed and wish to use it, instead of the
- shipped in version, set the variable DEFAULT_RMT_COMMAND to
- the full path name of the utility, e.g., ./configure
- DEFAULT_RMT_COMMAND=/etc/rmt.
- Notice also that the full path name of the "rmt" utility to
- use can be set at runtime, by giving option --rmt-command to
- tar.
- hu (Hungarian), ms (Malaysian), nb (Norwegian), ro (Romanian), sk
- (Slovak), zh_CN (Chinese simplified), zh_TW (Chinese traditional).
- The code 'no' for Norwegian (Bokmål) has been withdrawn; use 'nb' instead.
- version 1.13.25 - Paul Eggert, 2001-09-26
- version 1.13.24 - Paul Eggert, 2001-09-22
- version 1.13.23 - Paul Eggert, 2001-09-13
- version 1.13.22 - Paul Eggert, 2001-08-29
- version 1.13.21 - Paul Eggert, 2001-08-28
- version 1.13.20 - Paul Eggert, 2001-08-27
- - security problems
- - hard links to symbolic links
- --wildcards-match-slash, and their negations (e.g., --no-anchored).
- Along with --recursion and --no-recursion, these options control how
- exclude patterns are interpreted.
- --no-ignore-case --recursion --wildcards --wildcards-match-slash.
- This is a quiet change to the semantics of --exclude. The previous
- semantics were a failed attempt at backward compatibility but it
- became clear that the semantics were puzzling and did not satisfy
- everybody. Rather than continue to try to revive that dead horse we
- thought it better to substitute cleaner semantics, with options so
- that you can change the behavior more to your liking.
- The translation for Korean has been withdrawn due to encoding errors.
- It will be reissued once those are fixed.
- version 1.13.19 - Paul Eggert, 2001-01-13
- Eventually it is planned to be reintroduced, with the same meaning as -T.
- to be a file name; the last-modified time of that file is used as the date.
- version 1.13.18 - Paul Eggert, 2000-10-29
- files under the working directory, unless you also specify an unsafe
- option like --absolute-names or --overwrite.
- and -I is now an alias for -T, for compatibility with Solaris tar.
- The new file format is upward- and downward-compatible with the old.
- If you still use such a compiler, please use GCC instead.
- Please see <ftp:
- version 1.13.17 - Paul Eggert, 2000-01-07.
- version 1.13.16 - Paul Eggert, 1999-12-13.
- extracting files from an archive; instead, it removes the file
- before extracting it. If the existing file is a symbolic link, the
- link is removed and not the pointed-to file. There is one
- exception: existing nonempty directories are not removed, nor are
- their ownerships or permissions extracted. This fixes some
- longstanding security problems.
- The new --overwrite option enables the old default behavior.
- For regular files, tar implements this change by using the O_EXCL
- option of `open' to ensure that it creates the file; if this fails, it
- removes the file and tries again. This is similar to the behavior of
- the --unlink-first option, but it is faster in the common case of
- extracting a new directory.
- when extracting, and warns about such file names when creating an archive.
- To enable the old behavior, use the -P or --absolute-names option.
- correctly. It relies on the mbrtowc function to handle multibyte characters.
- that is independent of locale, so that users need not worry about
- locale when restoring a backup. This is needed for proper support
- of multibyte characters. Old-format files can still be read, and
- older versions of GNU tar can read new-format files, unless member
- names have multibyte chars.
- now output unambiguously. File names in diagnostics now are either
- `quoted like this' (in the default C locale) or are followed by
- colon, newline, or space, depending on context. Unprintable
- characters are escaped with a C-like backslash conventions.
- Terminating characters (e.g., close-quote, colon, newline)
- are also escaped as needed.
- Previously tar archived sockets as fifos, which caused problems.
- version 1.13.15 - Paul Eggert, 1999-12-03.
- Previously tar looked at mtime, which missed some errors.
- version 1.13.14 - Paul Eggert, 1999-11-07.
- version 1.13.13 - Paul Eggert, 1999-10-11.
- version 1.13.12 - Paul Eggert, 1999-09-24.
- values that are out of the range of the standard unsigned base-8
- format. This affects archive members with negative or huge time
- stamps or uids, and archive members 8 GB or larger. The new tar
- archives cannot be read by traditional tar, or by older versions of
- GNU tar. Use the --old-archive option to revert to the old
- behavior, which uses unportable representations for negative values,
- and which rejects large files.
- the range 2**31 <= T < 2**32 represents the negative time (T -
- 2**32). This behavior is nonstandard and is not portable to 64-bit
- time_t hosts, so `tar' issues a warning.
- that an archive contains garbage at the end. It attempts to extract
- as many files as possible from the good data before the garbage.
- version 1.13.11 - Paul Eggert, 1999-08-23.
- for compatibility with paxutils.
- if no explicit operands were given.
- it causes later operands to be interpreted as file names, not options,
- even if they begin with `-'.
- abbreviations like `EST' has been updated to match current practice.
- Also, local time abbreviations are now recognized, even if they are
- not in tar's hardwired table. Remember, though, that you should use
- numeric UTC offsets like `-0500' instead of abbreviations like
- `EST', as abbreviations are not standardized and are ambiguous.
- version 1.13.10 - Paul Eggert, 1999-08-20.
- out of the range of the standard unsigned base-8 format. [This
- change was superseded in 1.13.12, described above.]
- version 1.13.9 - Paul Eggert, 1999-08-18.
- POSIX.1 requires this, and some other `tar' implementations check for it.
- as a zero block.
- numeric header field.
- version 1.13.8 - Paul Eggert, 1999-08-16.
- created automatically by root are no longer given the uid and gid of
- the original file or directory.
- version 1.13.7 - Paul Eggert, 1999-08-14.
- to match traditional tar's behavior (and simplify the documentation).
- version 1.13.6 - Paul Eggert, 1999-08-11.
- initial prefix of the file name; a pattern without / continues to
- exclude a file if it matches any file name component.
- Open flags are now communicated in symbolic format as well as numeric.
- The symbolic format (e.g., "O_WRONLY|O_CREAT|O_TRUNC") is for portability
- when rmt is operating on a different operating system from tar.
- The numeric format is retained, and rmt uses it if symbolic format is absent,
- for backward compatibility with older versions of tar and rmt.
- for values that cannot be represented in unsigned octal.
- This supports larger files (2**66 - 1 bytes instead of 2**33 - 1 bytes),
- larger uids, negative time stamps, etc.
- uid and gid "nobody" on hosts whose headers do not define UID_NOBODY
- and GID_NOBODY, and falls back on uid/gid -2 if there is no "nobody".
- version 1.13.5 - Paul Eggert, 1999-07-20.
- version 1.13.4 - Paul Eggert, 1999-07-20.
- this matches historical practice.
- version 1.13.3 - Paul Eggert, 1999-07-16.
- excluded pattern, even if the path name was specified on the command line.
- Also see 1.13.6 for later changes in this area.
- version 1.13.2 - Paul Eggert, 1999-07-14.
- version 1.13.1 - Paul Eggert, 1999-07-12.
- version 1.13 - Paul Eggert, 1999-07-08.
- Also, support for larger uids, device ids, etc.
- with new features, is available as part of the paxutils. Please see:
- ftp:
- The fixes in this release are intended to be merged with paxutils
- at some point, but they haven't been merged yet.
- but they have been removed to maintain compatibility with paxutils.
- Please try --use=bzip2 instead of --bzip2.
- Version 1.12 - François Pinard, 1997-04.
- Sensitive matters
- Output for humans
- Creation
- Extraction
- Various changes
- Many bugs are squashed, while others still run free.
- Version 1.11.8 - François Pinard, 1995-06.
- Most changes are internal, and should yield better portability.
- Version 1.11.2 - Michael Bushnell, 1993-03.
- conditions better over rsh; DUMP_REMIND_SCRIPT is now an option in
- backup-specs; new file dump-remind is an example of a
- DUMP_REMIND_SCRIPT.
- of compress. Also, --use-compress-program lets you specify any
- compress program. --compress-block is renamed --block-compress and
- now requires one of the three compression options to be specified.
- for --info-script.
- Version 1.11.1 - Michael Bushnell, 1992-09.
- Version 1.11 - Michael Bushnell, 1992-09.
- Version 1.10.16 - 1992-07.
- Version 1.10.15 - 1992-06.
- Version 1.10.14 - 1992-05.
- Version 1.10.13 - 1992-01.
- for it will eventually be removed.
- null-terminated, and causes -C to be ignored.
- after they are added to the archive.
- the exit status.
- is being read or written.
- omitted from the archive.
- end-of-tape now work correctly with multi-tape archives.
- (but not in recording volume ID's on the archive) from a file.
- the various tape drives will get used in sequence and then wrap
- around to the beginning.
- `:' is interpreted as remote. If new option --force-local is given,
- then even archive files with a `:' are considered local.
- their original values after dumping the file.
- what to dump.
- modification and access times.
- precedes the long-named file or link in the archive, so you no
- longer have to wait for the extract to hit the end of the tape for
- long names to work.
- Version 1.10 - Michael Bushnell, 1991-07.
- +newer-mtime work right.
- what +exclude used to do.
- dump: you tell tar how big the tape is and it will prompt at that
- point instead of waiting for a write error.
- to people. They use a file "backup-specs" for information, and
- shouldn't need local modification. These are what we use to do
- all our backups at the FSF.
- Version 1.09 - Jay Fenlason, 1990-10.
- Version 1.08 - Jay Fenlason, 1990-01.
- Versions 1.07 back to 1.00 by Jay Fenlason.
- Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2003,
- 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
- This file is part of GNU tar.
- GNU tar is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 3, or (at your option)
- any later version.
- GNU tar is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
- You should have received a copy of the GNU General Public License
- along with tar; see the file COPYING. If not, write to
- the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
- Boston, MA 02110-1301, USA.
- Local variables:
- mode: outline
- paragraph-separate: "[ ]*$"
- eval: (add-hook 'write-file-hooks 'time-stamp)
- time-stamp-start: "changes. "
- time-stamp-format: "%:y-%02m-%02d"
- time-stamp-end: "\n"
- end:
|