This is tar.info, produced by makeinfo version 4.13 from tar.texi.
-This manual is for GNU `tar' (version 1.23, 9 March 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,
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
- Version 1.1 or any later version published by the Free Software
+ Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, with the Front-Cover Texts
- being "A GNU Manual," and with the Back-Cover Texts as in (a)
+ being "A GNU Manual", and with the Back-Cover Texts as in (a)
below. A copy of the license is included in the section entitled
"GNU Free Documentation License".
GNU tar: an archiver tool
*************************
-This manual is for GNU `tar' (version 1.23, 9 March 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,
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
- Version 1.1 or any later version published by the Free Software
+ Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, with the Front-Cover Texts
- being "A GNU Manual," and with the Back-Cover Texts as in (a)
+ being "A GNU Manual", and with the Back-Cover Texts as in (a)
below. A copy of the license is included in the section entitled
"GNU Free Documentation License".
* Date input formats::
* Formats::
* Media::
+* Reliability and security::
Appendices
* Tar Internals::
* Genfile::
* Free Software Needs Free Documentation::
-* Copying This Manual::
+* GNU Free Documentation License::
* Index of Command Line Options::
* Index::
* Pure numbers in date strings:: 19931219, 1440.
* Seconds since the Epoch:: @1078100502.
* Specifying time zone rules:: TZ="America/New_York", TZ="UTC0".
-* Authors of get_date:: Bellovin, Eggert, Salz, Berets, et al.
+* Authors of parse_datetime:: Bellovin, Eggert, Salz, Berets, et al.
Controlling the Archive Format
* gzip:: Creating and Reading Compressed Archives
* sparse:: Archiving Sparse Files
+Creating and Reading Compressed Archives
+
+* lbzip2:: Using lbzip2 with GNU `tar'.
+
Making `tar' Archives More Portable
* Portable Names:: Portable Names
(`create', `list', and `extract') as well as two frequently used
options (`file' and `verbose'). The other chapters do not refer to the
tutorial frequently; however, if a section discusses something which is
-a complex variant of a basic concept, there may be a cross reference to
+a complex variant of a basic concept, there may be a cross-reference to
that basic concept. (The entire book, including the tutorial, assumes
that the reader understands some basic concepts of using a Unix-type
operating system; *note Tutorial::.)
tutorial and manual for GNU `tar'. Franc,ois Pinard put version 1.11.8
of the manual together by taking information from all these sources and
merging them. Melissa Weisshaus finally edited and redesigned the book
-to create version 1.12. The book for versions from 1.14 up to 1.23
+to create version 1.12. The book for versions from 1.14 up to 1.26
were edited by the current maintainer, Sergey Poznyakoff.
For version 1.12, Daniel Hagerty contributed a great deal of
For example, here is an archive listing containing most of the
special suffixes explained above:
- V--------- 0/0 1536 2006-06-09 13:07 MyVolume--Volume Header--
- -rw-r--r-- gray/staff 456783 2006-06-09 12:06 aspic--Continued at
- byte 32456--
- -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
- lrwxrwxrwx gray/staff 0 2006-06-09 13:01 angst -> apple
- -rw-r--r-- gray/staff 35793 2006-06-09 12:06 blues
- hrw-r--r-- gray/staff 0 2006-06-09 12:06 music link to blues
+ V--------- 0/0 1536 2006-06-09 13:07 MyVolume--Volume Header--
+ -rw-r--r-- gray/staff 456783 2006-06-09 12:06 aspic--Continued at byte 32456--
+ -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
+ lrwxrwxrwx gray/staff 0 2006-06-09 13:01 angst -> apple
+ -rw-r--r-- gray/staff 35793 2006-06-09 12:06 blues
+ hrw-r--r-- gray/staff 0 2006-06-09 12:06 music link to blues
\1f
look like:
$ tar --list --verbose --file=collection.tar folk
- -rw-r--r-- myself user 62 1990-05-23 10:55 folk
+ -rw-r--r-- myself/user 62 1990-05-23 10:55 folk
It is important to notice that the output of `tar --list --verbose'
does not necessarily match that produced by `tar --create --verbose'
`tar' responds:
- drwxrwxrwx myself user 0 1990-05-31 21:49 practice/
- -rw-r--r-- myself user 42 1990-05-21 13:29 practice/blues
- -rw-r--r-- myself user 62 1990-05-23 10:55 practice/folk
- -rw-r--r-- myself user 40 1990-05-21 13:30 practice/jazz
- -rw-r--r-- myself user 10240 1990-05-31 21:49 practice/collection.tar
+ drwxrwxrwx myself/user 0 1990-05-31 21:49 practice/
+ -rw-r--r-- myself/user 42 1990-05-21 13:29 practice/blues
+ -rw-r--r-- myself/user 62 1990-05-23 10:55 practice/folk
+ -rw-r--r-- myself/user 40 1990-05-21 13:30 practice/jazz
+ -rw-r--r-- myself/user 10240 1990-05-31 21:49 practice/collection.tar
When you use a directory name as a file name argument, `tar' acts on
all the files (including sub-directories) in that directory.
produces this:
- -rw-r--r-- me user 28 1996-10-18 16:31 jazz
- -rw-r--r-- me user 21 1996-09-23 16:44 blues
- -rw-r--r-- me user 20 1996-09-23 16:44 folk
+ -rw-r--r-- me/user 28 1996-10-18 16:31 jazz
+ -rw-r--r-- me/user 21 1996-09-23 16:44 blues
+ -rw-r--r-- me/user 20 1996-09-23 16:44 folk
\1f
File: tar.info, Node: extracting files, Next: extract dir, Prev: extracting archives, Up: extract
example below:
$ tar -xvvf music.tar practice/folk practice/jazz
- -rw-r--r-- me user 28 1996-10-18 16:31 practice/jazz
- -rw-r--r-- me user 20 1996-09-23 16:44 practice/folk
+ -rw-r--r-- me/user 28 1996-10-18 16:31 practice/jazz
+ -rw-r--r-- me/user 20 1996-09-23 16:44 practice/folk
Because you created the directory with `practice' as part of the file
names of each of the files by archiving the `practice' directory as
`--dereference'
`-h'
- When creating a `tar' archive, `tar' will archive the file that a
- symbolic link points to, rather than archiving the symlink. *Note
- dereference::.
+ When reading or writing a file to be archived, `tar' accesses the
+ file that a symbolic link points to, rather than the symlink
+ itself. *Note dereference::.
`--directory=DIR'
`-C DIR'
*Note Formats::, for a detailed discussion of these formats.
+`--full-time'
+ This option instructs `tar' to print file times to their full
+ resolution. Usually this means 1-second resolution, but that
+ depends on the underlying file system. The `--full-time' option
+ takes effect only when detailed output (verbosity level 2 or
+ higher) has been requested using the `--verbose' option, e.g.,
+ when listing or extracting archives:
+
+ $ tar -t -v --full-time -f archive.tar
+
+ or, when creating an archive:
+
+ $ tar -c -vv --full-time -f archive.tar .
+
+ Notice, thar when creating the archive you need to specify
+ `--verbose' twice to get a detailed output (*note verbose
+ tutorial::).
+
`--group=GROUP'
Files added to the `tar' archive will have a group ID of GROUP,
rather than the group from the source file. GROUP is first decoded
`--level=N'
Force incremental backup of level N. As of GNU `tar' version
- 1.23, the option `--level=0' truncates the snapshot file, thereby
+ 1.26, the option `--level=0' truncates the snapshot file, thereby
forcing the level 0 dump. Other values of N are effectively
ignored. *Note --level=0::, for details and examples.
Specifies that `tar' should reblock its input, for reading from
pipes on systems with buggy implementations. *Note Reading::.
-`--record-size=SIZE'
+`--record-size=SIZE[SUF]'
Instructs `tar' to use SIZE bytes per record when accessing the
- archive. *Note Blocking Factor::.
+ archive. The argument can be suffixed with a "size suffix", e.g.
+ `--record-size=10K' for 10 Kilobytes. *Note size-suffixes::, for
+ a list of valid suffixes. *Note Blocking Factor::, for a detailed
+ description of this option.
`--recursion'
With this option, `tar' recurses into directories (default).
Alters the suffix `tar' uses when backing up files from the default
`~'. *Note backup::.
-`--tape-length=NUM'
-`-L NUM'
+`--tape-length=NUM[SUF]'
+`-L NUM[SUF]'
Specifies the length of tapes that `tar' is writing as being
- NUM x 1024 bytes long. *Note Using Multiple Tapes::.
+ NUM x 1024 bytes long. If optional SUF is given, it specifies a
+ multiplicative factor to be used instead of 1024. For example,
+ `-L2M' means 2 megabytes. *Note size-suffixes::, for a list of
+ allowed suffixes. *Note Using Multiple Tapes::, for a detailed
+ discussion of this option.
`--test-label'
Reads the volume label. If an argument is specified, test whether
`--show-transformed-names' option (*note show-transformed-names::).
`--uncompress'
- (See `--compress'. *note gzip::)
+ (See `--compress', *note gzip::)
`--ungzip'
- (See `--gzip'. *note gzip::)
+ (See `--gzip', *note gzip::)
`--unlink-first'
`-U'
standard output, and then exit successfully. For example,
`tar --version' might print:
- tar (GNU tar) 1.23
+ tar (GNU tar) 1.26
Copyright (C) 2010 Free Software Foundation, Inc.
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
`Current %s is newer or same age'
unknown-keyword
- `Ignoring unknown extended header keyword `%s''
+ `Ignoring unknown extended header keyword `%s''
+
+decompress-program
+ Controls verbose description of failures occurring when trying to
+ run alternative decompressor programs (*note alternative
+ decompression programs::). This warning is disabled by default
+ (unless `--verbose' is used). A common example of what you can get
+ when using this warning is:
+
+ $ tar --warning=decompress-program -x -f archive.Z
+ tar (child): cannot run compress: No such file or directory
+ tar (child): trying gzip
+
+ This means that `tar' first tried to decompress `archive.Z' using
+ `compress', and, when that failed, switched to `gzip'.
Keywords controlling incremental extraction:
--------------------------------------------
has been added to the archive:
$ tar --list --file=collection.tar
- -rw-r--r-- me user 28 1996-10-18 16:31 jazz
- -rw-r--r-- me user 21 1996-09-23 16:44 blues
- -rw-r--r-- me user 20 1996-09-23 16:44 folk
- -rw-r--r-- me user 20 1996-09-23 16:44 rock
+ -rw-r--r-- me/user 28 1996-10-18 16:31 jazz
+ -rw-r--r-- me/user 21 1996-09-23 16:44 blues
+ -rw-r--r-- me/user 20 1996-09-23 16:44 folk
+ -rw-r--r-- me/user 20 1996-09-23 16:44 rock
\1f
File: tar.info, Node: multiple, Prev: appending files, Up: append
contents of the archive:
$ tar --list --verbose --file=collection.tar
- -rw-r--r-- me user 28 1996-10-18 16:31 jazz
- -rw-r--r-- me user 21 1996-09-23 16:44 blues
- -rw-r--r-- me user 20 1996-09-23 16:44 folk
- -rw-r--r-- me user 20 1996-09-23 16:44 rock
- -rw-r--r-- me user 58 1996-10-24 18:30 blues
+ -rw-r--r-- me/user 28 1996-10-18 16:31 jazz
+ -rw-r--r-- me/user 21 1996-09-23 16:44 blues
+ -rw-r--r-- me/user 20 1996-09-23 16:44 folk
+ -rw-r--r-- me/user 20 1996-09-23 16:44 rock
+ -rw-r--r-- me/user 58 1996-10-24 18:30 blues
The newest version of `blues' is now at the end of the archive (note
the different creation dates and file sizes). If you extract the
example:
$ tar --extract -vv --occurrence --file=collection.tar blues
- -rw-r--r-- me user 21 1996-09-23 16:44 blues
+ -rw-r--r-- me/user 21 1996-09-23 16:44 blues
- *Note Writing::, for more information on `--extract' and *Note
--occurrence: Option Summary, for the description of `--occurrence'
-option.
+ *Note Writing::, for more information on `--extract' and see *note
+-occurrence: Option Summary, for a description of `--occurrence' option.
\1f
File: tar.info, Node: update, Next: concatenate, Prev: append, Up: Advanced tar
`classical', in your practice directory, and some extra text to the
file `blues', using any text editor. Then invoke `tar' with the
`update' operation and the `--verbose' (`-v') option specified, using
-the names of all the files in the practice directory as file name
+the names of all the files in the `practice' directory as file name
arguments:
$ tar --update -v -f collection.tar blues folk rock classical
what they are supposed to:
$ tar -tvf bluesrock.tar
- -rw-r--r-- melissa user 105 1997-01-21 19:42 blues
- -rw-r--r-- melissa user 33 1997-01-20 15:34 rock
+ -rw-r--r-- melissa/user 105 1997-01-21 19:42 blues
+ -rw-r--r-- melissa/user 33 1997-01-20 15:34 rock
$ tar -tvf jazzfolk.tar
- -rw-r--r-- melissa user 20 1996-09-23 16:44 folk
- -rw-r--r-- melissa user 65 1997-01-30 14:15 jazz
+ -rw-r--r-- melissa/user 20 1996-09-23 16:44 folk
+ -rw-r--r-- melissa/user 65 1997-01-30 14:15 jazz
We can concatenate these two archives with `tar':
---------- Footnotes ----------
- (1) This can cause multiple members to have the same name, for
-information on how this affects reading the archive, *note multiple::.
+ (1) This can cause multiple members to have the same name. For
+information on how this affects reading the archive, see *note
+multiple::.
\1f
File: tar.info, Node: delete, Next: compare, Prev: concatenate, Up: Advanced tar
The spirit behind the `--compare' (`--diff', `-d') option is to
check whether the archive represents the current state of files on
disk, more than validating the integrity of the archive media. For
-this latter goal, *Note verify::.
+this latter goal, see *note verify::.
\1f
File: tar.info, Node: create options, Next: extract options, Prev: Advanced tar, Up: operations
`/' or `.'. In the latter case, the modification time of that
file will be used.
- The following example will set the modification date to 00:00:00
- UTC, January 1, 1970:
+ The following example will set the modification date to 00:00:00,
+ January 1, 1970:
$ tar -c -f archive.tar --mtime='1970-01-01' .
extracting only after member NAME of the archive. This assumes, of
course, that there is now free space, or that you are now extracting
into a different file system. (You could also choose to suspend `tar',
-remove unnecessary files from the file system, and then restart the
-same `tar' operation. In this case, `--starting-file' is not necessary.
-*Note Incremental Dumps::, *Note interactive::, and *note exclude::.)
+remove unnecessary files from the file system, and then resume the same
+`tar' operation. In this case, `--starting-file' is not necessary.)
+See also *note interactive::, and *note exclude::.
\1f
File: tar.info, Node: Same Order, Prev: Starting File, Up: Scarce
or
- $ tar --directory sourcedir --create --file=- . ) \
+ $ tar --directory sourcedir --create --file=- . \
| tar --directory targetdir --extract --file=-
This is one of the easiest methods to transfer a `tar' archive.
To list the contents of an incremental archive, use `--list' (*note
list::), as usual. To obtain more information about the archive, use
`--listed-incremental' or `--incremental' combined with two `--verbose'
-optionsTwo
-`--verbose' options were selected to avoid breaking usual
-verbose listing output (`--list --verbose') when using in
-scripts.
-
-
-
-
-
-Versions of GNU `tar' up to 1.15.1 used to dump verbatim binary
-contents of the DUMPDIR header (with terminating nulls) when
-`--incremental' or `--listed-incremental' option was
-given, no matter what the verbosity level(2):
+options(2):
tar --list --incremental --verbose --verbose archive.tar
libc.a
-
Notice that the option parsing algorithm used with `-T' is stricter
than the one used by shell. Namely, when specifying option arguments,
you should observe the following rules:
systems: `CVS', `RCS', `SCCS', `SVN', `Arch', `Bazaar',
`Mercurial', and `Darcs'.
- As of version 1.23, the following files are excluded:
+ As of version 1.26, the following files are excluded:
* `CVS/', and everything under it
--show-transformed /lib
drwxr-xr-x root/root 0 2008-07-08 16:20 /usr/local/lib/
-rwxr-xr-x root/root 1250840 2008-05-25 07:44 /usr/local/lib/libc-2.3.2.so
- lrwxrwxrwx root/root 0 2008-06-24 17:12 /usr/local/lib/libc.so.6 ->
- libc-2.3.2.so
+ lrwxrwxrwx root/root 0 2008-06-24 17:12 /usr/local/lib/libc.so.6 \
+ -> libc-2.3.2.so
Unlike `--strip-components', `--transform' can be used in any GNU
`tar' operation mode. For example, the following command adds files to
$ tar -c -f archive.tar -C / home
+ *Note Integrity::, for some of the security-related implications of
+using this option.
+
---------- Footnotes ----------
(1) A side effect of this is that when `--create' is used with
This section describes the textual date representations that GNU
programs accept. These are the strings you, as a user, can supply as
-arguments to the various programs. The C interface (via the `get_date'
-function) is not described here.
+arguments to the various programs. The C interface (via the
+`parse_datetime' function) is not described here.
* Menu:
* Pure numbers in date strings:: 19931219, 1440.
* Seconds since the Epoch:: @1078100502.
* Specifying time zone rules:: TZ="America/New_York", TZ="UTC0".
-* Authors of get_date:: Bellovin, Eggert, Salz, Berets, et al.
+* Authors of parse_datetime:: Bellovin, Eggert, Salz, Berets, et al.
\1f
File: tar.info, Node: General date syntax, Next: Calendar date items, Up: Date input formats
way to represent the intervening leap second 1998-12-31 23:59:60 UTC.
\1f
-File: tar.info, Node: Specifying time zone rules, Next: Authors of get_date, Prev: Seconds since the Epoch, Up: Date input formats
+File: tar.info, Node: Specifying time zone rules, Next: Authors of parse_datetime, Prev: Seconds since the Epoch, Up: Date input formats
7.9 Specifying time zone rules
==============================
Variable.
\1f
-File: tar.info, Node: Authors of get_date, Prev: Specifying time zone rules, Up: Date input formats
+File: tar.info, Node: Authors of parse_datetime, Prev: Specifying time zone rules, Up: Date input formats
-7.10 Authors of `get_date'
-==========================
+7.10 Authors of `parse_datetime'
+================================
-`get_date' was originally implemented by Steven M. Bellovin
-(<smb@research.att.com>) while at the University of North Carolina at
-Chapel Hill. The code was later tweaked by a couple of people on
-Usenet, then completely overhauled by Rich $alz (<rsalz@bbn.com>) and
-Jim Berets (<jberets@bbn.com>) in August, 1990. Various revisions for
-the GNU system were made by David MacKenzie, Jim Meyering, Paul Eggert
-and others.
+`parse_datetime' started life as `getdate', as originally implemented
+by Steven M. Bellovin (<smb@research.att.com>) while at the University
+of North Carolina at Chapel Hill. The code was later tweaked by a
+couple of people on Usenet, then completely overhauled by Rich $alz
+(<rsalz@bbn.com>) and Jim Berets (<jberets@bbn.com>) in August, 1990.
+Various revisions for the GNU system were made by David MacKenzie, Jim
+Meyering, Paul Eggert and others, including renaming it to `get_date' to
+avoid a conflict with the alternative Posix function `getdate', and a
+later rename to `parse_datetime'. The Posix function `getdate' can
+parse more locale-specific dates using `strptime', but relies on an
+environment variable and external file, and lacks the thread-safety of
+`parse_datetime'.
This chapter was originally produced by Franc,ois Pinard
-(<pinard@iro.umontreal.ca>) from the `getdate.y' source code, and then
-edited by K. Berry (<kb@cs.umb.edu>).
+(<pinard@iro.umontreal.ca>) from the `parse_datetime.y' source code,
+and then edited by K. Berry (<kb@cs.umb.edu>).
projects / debian / tar / blobdiff