1 This is tar.info, produced by makeinfo version 4.13 from tar.texi.
3 This manual is for GNU `tar' (version 1.22, 5 March 2009), which
4 creates and extracts files from archives.
6 Copyright (C) 1992, 1994, 1995, 1996, 1997, 1999, 2000, 2001, 2003,
7 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
9 Permission is granted to copy, distribute and/or modify this
10 document under the terms of the GNU Free Documentation License,
11 Version 1.1 or any later version published by the Free Software
12 Foundation; with no Invariant Sections, with the Front-Cover Texts
13 being "A GNU Manual," and with the Back-Cover Texts as in (a)
14 below. A copy of the license is included in the section entitled
15 "GNU Free Documentation License".
17 (a) The FSF's Back-Cover Text is: "You have the freedom to copy
18 and modify this GNU manual. Buying copies from the FSF supports
19 it in developing GNU and promoting software freedom."
21 INFO-DIR-SECTION Archiving
23 * Tar: (tar). Making tape (or disk) archives.
26 INFO-DIR-SECTION Individual utilities
28 * tar: (tar)tar invocation. Invoking GNU `tar'.
32 File: tar.info, Node: Top, Next: Introduction, Up: (dir)
34 GNU tar: an archiver tool
35 *************************
37 This manual is for GNU `tar' (version 1.22, 5 March 2009), which
38 creates and extracts files from archives.
40 Copyright (C) 1992, 1994, 1995, 1996, 1997, 1999, 2000, 2001, 2003,
41 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
43 Permission is granted to copy, distribute and/or modify this
44 document under the terms of the GNU Free Documentation License,
45 Version 1.1 or any later version published by the Free Software
46 Foundation; with no Invariant Sections, with the Front-Cover Texts
47 being "A GNU Manual," and with the Back-Cover Texts as in (a)
48 below. A copy of the license is included in the section entitled
49 "GNU Free Documentation License".
51 (a) The FSF's Back-Cover Text is: "You have the freedom to copy
52 and modify this GNU manual. Buying copies from the FSF supports
53 it in developing GNU and promoting software freedom."
55 The first part of this master menu lists the major nodes in this Info
56 document. The rest of the menu lists all the lower level nodes.
66 * Date input formats::
73 * Configuring Help Summary::
74 * Fixing Snapshot Files::
77 * Free Software Needs Free Documentation::
78 * Copying This Manual::
79 * Index of Command Line Options::
82 --- The Detailed Node Listing ---
86 * Book Contents:: What this Book Contains
87 * Definitions:: Some Definitions
88 * What tar Does:: What `tar' Does
89 * Naming tar Archives:: How `tar' Archives are Named
90 * Authors:: GNU `tar' Authors
91 * Reports:: Reporting bugs or suggestions
93 Tutorial Introduction to `tar'
96 * stylistic conventions::
97 * basic tar options:: Basic `tar' Operations and Options
98 * frequent operations::
99 * Two Frequent Options::
100 * create:: How to Create Archives
101 * list:: How to List Archives
102 * extract:: How to Extract Members from an Archive
105 Two Frequently Used Options
111 How to Create Archives
113 * prepare for examples::
114 * Creating the archive::
123 How to Extract Members from an Archive
125 * extracting archives::
128 * extracting untrusted archives::
134 * using tar options::
143 The Three Option Styles
145 * Long Options:: Long Option Style
146 * Short Options:: Short Option Style
147 * Old Options:: Old Option Style
148 * Mixing:: Mixing Option Styles
152 * Operation Summary::
154 * Short Option Summary::
166 Advanced GNU `tar' Operations
175 How to Add Files to Existing Archives: `--append'
177 * appending files:: Appending Files to an Archive
184 Options Used by `--create'
186 * override:: Overriding File Metadata.
187 * Ignore Failed Read::
189 Options Used by `--extract'
191 * Reading:: Options to Help Read Archives
192 * Writing:: Changing How `tar' Writes Files
193 * Scarce:: Coping with Scarce Resources
195 Options to Help Read Archives
197 * read full records::
200 Changing How `tar' Writes Files
202 * Dealing with Old Files::
203 * Overwrite Old Files::
208 * Data Modification Times::
209 * Setting Access Permissions::
210 * Directory Modification Times and Permissions::
211 * Writing to Standard Output::
212 * Writing to an External Program::
215 Coping with Scarce Resources
220 Performing Backups and Restoring Files
222 * Full Dumps:: Using `tar' to Perform Full Dumps
223 * Incremental Dumps:: Using `tar' to Perform Incremental Dumps
224 * Backup Levels:: Levels of Backups
225 * Backup Parameters:: Setting Parameters for Backups and Restoration
226 * Scripted Backups:: Using the Backup Scripts
227 * Scripted Restoration:: Using the Restore Script
229 Setting Parameters for Backups and Restoration
231 * General-Purpose Variables::
232 * Magnetic Tape Control::
234 * backup-specs example:: An Example Text of `Backup-specs'
236 Choosing Files and Names for `tar'
238 * file:: Choosing the Archive's Name
239 * Selecting Archive Members::
240 * files:: Reading Names from a File
241 * exclude:: Excluding Some Files
242 * wildcards:: Wildcards Patterns and Matching
243 * quoting styles:: Ways of Quoting Special Characters in Names
244 * transform:: Modifying File and Member Names
245 * after:: Operating Only on New Files
246 * recurse:: Descending into Directories
247 * one:: Crossing File System Boundaries
249 Reading Names from a File
255 * problems with exclude::
257 Wildcards Patterns and Matching
259 * controlling pattern-matching::
261 Crossing File System Boundaries
263 * directory:: Changing Directory
264 * absolute:: Absolute File Names
268 * General date syntax:: Common rules.
269 * Calendar date items:: 19 Dec 1994.
270 * Time of day items:: 9:20pm.
271 * Time zone items:: EST, PDT, GMT.
272 * Day of week items:: Monday and others.
273 * Relative items in date strings:: next tuesday, 2 years ago.
274 * Pure numbers in date strings:: 19931219, 1440.
275 * Seconds since the Epoch:: @1078100502.
276 * Specifying time zone rules:: TZ="America/New_York", TZ="UTC0".
277 * Authors of get_date:: Bellovin, Eggert, Salz, Berets, et al.
279 Controlling the Archive Format
281 * Compression:: Using Less Space through Compression
282 * Attributes:: Handling File Attributes
283 * Portability:: Making `tar' Archives More Portable
284 * cpio:: Comparison of `tar' and `cpio'
286 Using Less Space through Compression
288 * gzip:: Creating and Reading Compressed Archives
289 * sparse:: Archiving Sparse Files
291 Making `tar' Archives More Portable
293 * Portable Names:: Portable Names
294 * dereference:: Symbolic Links
295 * hard links:: Hard Links
296 * old:: Old V7 Archives
297 * ustar:: Ustar Archives
298 * gnu:: GNU and old GNU format archives.
299 * posix:: POSIX archives
300 * Checksumming:: Checksumming Problems
301 * Large or Negative Values:: Large files, negative time stamps, etc.
302 * Other Tars:: How to Extract GNU-Specific Data Using
303 Other `tar' Implementations
305 GNU `tar' and POSIX `tar'
307 * PAX keywords:: Controlling Extended Header Keywords.
309 How to Extract GNU-Specific Data Using Other `tar' Implementations
311 * Split Recovery:: Members Split Between Volumes
312 * Sparse Recovery:: Sparse Members
314 Tapes and Other Archive Media
316 * Device:: Device selection and switching
317 * Remote Tape Server::
318 * Common Problems and Solutions::
319 * Blocking:: Blocking
320 * Many:: Many archives on one tape
321 * Using Multiple Tapes:: Using Multiple Tapes
322 * label:: Including a Label in the Archive
328 * Format Variations:: Format Variations
329 * Blocking Factor:: The Blocking Factor of an Archive
331 Many Archives on One Tape
333 * Tape Positioning:: Tape Positions and Tape Marks
334 * mt:: The `mt' Utility
338 * Multi-Volume Archives:: Archives Longer than One Tape or Disk
339 * Tape Files:: Tape Files
340 * Tarcat:: Concatenate Volumes into a Single Archive
345 * Standard:: Basic Tar Format
346 * Extensions:: GNU Extensions to the Archive Format
347 * Sparse Formats:: Storing Sparse Files
354 * PAX 0:: PAX Format, Versions 0.0 and 0.1
355 * PAX 1:: PAX Format, Version 1.0
359 * Generate Mode:: File Generation Mode.
360 * Status Mode:: File Status Mode.
361 * Exec Mode:: Synchronous Execution mode.
365 * GNU Free Documentation License:: License for copying this manual
368 File: tar.info, Node: Introduction, Next: Tutorial, Prev: Top, Up: Top
373 GNU `tar' creates and manipulates "archives" which are actually
374 collections of many other files; the program provides users with an
375 organized and systematic method for controlling a large amount of data.
376 The name "tar" originally came from the phrase "Tape ARchive", but
377 archives need not (and these days, typically do not) reside on tapes.
381 * Book Contents:: What this Book Contains
382 * Definitions:: Some Definitions
383 * What tar Does:: What `tar' Does
384 * Naming tar Archives:: How `tar' Archives are Named
385 * Authors:: GNU `tar' Authors
386 * Reports:: Reporting bugs or suggestions
389 File: tar.info, Node: Book Contents, Next: Definitions, Up: Introduction
391 1.1 What this Book Contains
392 ===========================
394 The first part of this chapter introduces you to various terms that will
395 recur throughout the book. It also tells you who has worked on GNU
396 `tar' and its documentation, and where you should send bug reports or
399 The second chapter is a tutorial (*note Tutorial::) which provides a
400 gentle introduction for people who are new to using `tar'. It is meant
401 to be self contained, not requiring any reading from subsequent
402 chapters to make sense. It moves from topic to topic in a logical,
403 progressive order, building on information already explained.
405 Although the tutorial is paced and structured to allow beginners to
406 learn how to use `tar', it is not intended solely for beginners. The
407 tutorial explains how to use the three most frequently used operations
408 (`create', `list', and `extract') as well as two frequently used
409 options (`file' and `verbose'). The other chapters do not refer to the
410 tutorial frequently; however, if a section discusses something which is
411 a complex variant of a basic concept, there may be a cross reference to
412 that basic concept. (The entire book, including the tutorial, assumes
413 that the reader understands some basic concepts of using a Unix-type
414 operating system; *note Tutorial::.)
416 The third chapter presents the remaining five operations, and
417 information about using `tar' options and option syntax.
419 The other chapters are meant to be used as a reference. Each chapter
420 presents everything that needs to be said about a specific topic.
422 One of the chapters (*note Date input formats::) exists in its
423 entirety in other GNU manuals, and is mostly self-contained. In
424 addition, one section of this manual (*note Standard::) contains a big
425 quote which is taken directly from `tar' sources.
427 In general, we give both long and short (abbreviated) option names
428 at least once in each section where the relevant option is covered, so
429 that novice readers will become familiar with both styles. (A few
430 options have no short versions, and the relevant sections will indicate
434 File: tar.info, Node: Definitions, Next: What tar Does, Prev: Book Contents, Up: Introduction
439 The `tar' program is used to create and manipulate `tar' archives. An
440 "archive" is a single file which contains the contents of many files,
441 while still identifying the names of the files, their owner(s), and so
442 forth. (In addition, archives record access permissions, user and
443 group, size in bytes, and data modification time. Some archives also
444 record the file names in each archived directory, as well as other file
445 and directory information.) You can use `tar' to "create" a new
446 archive in a specified directory.
448 The files inside an archive are called "members". Within this
449 manual, we use the term "file" to refer only to files accessible in the
450 normal ways (by `ls', `cat', and so forth), and the term "member" to
451 refer only to the members of an archive. Similarly, a "file name" is
452 the name of a file, as it resides in the file system, and a "member
453 name" is the name of an archive member within the archive.
455 The term "extraction" refers to the process of copying an archive
456 member (or multiple members) into a file in the file system. Extracting
457 all the members of an archive is often called "extracting the archive".
458 The term "unpack" can also be used to refer to the extraction of many
459 or all the members of an archive. Extracting an archive does not
460 destroy the archive's structure, just as creating an archive does not
461 destroy the copies of the files that exist outside of the archive. You
462 may also "list" the members in a given archive (this is often thought
463 of as "printing" them to the standard output, or the command line), or
464 "append" members to a pre-existing archive. All of these operations
465 can be performed using `tar'.
468 File: tar.info, Node: What tar Does, Next: Naming tar Archives, Prev: Definitions, Up: Introduction
473 The `tar' program provides the ability to create `tar' archives, as
474 well as various other kinds of manipulation. For example, you can use
475 `tar' on previously created archives to extract files, to store
476 additional files, or to update or list files which were already stored.
478 Initially, `tar' archives were used to store files conveniently on
479 magnetic tape. The name `tar' comes from this use; it stands for
480 `t'ape `ar'chiver. Despite the utility's name, `tar' can direct its
481 output to available devices, files, or other programs (using pipes).
482 `tar' may even access remote devices or files (as archives).
484 You can use `tar' archives in many ways. We want to stress a few of
485 them: storage, backup, and transportation.
488 Often, `tar' archives are used to store related files for
489 convenient file transfer over a network. For example, the GNU
490 Project distributes its software bundled into `tar' archives, so
491 that all the files relating to a particular program (or set of
492 related programs) can be transferred as a single unit.
494 A magnetic tape can store several files in sequence. However, the
495 tape has no names for these files; it only knows their relative
496 position on the tape. One way to store several files on one tape
497 and retain their names is by creating a `tar' archive. Even when
498 the basic transfer mechanism can keep track of names, as FTP can,
499 the nuisance of handling multiple files, directories, and multiple
500 links makes `tar' archives useful.
502 Archive files are also used for long-term storage. You can think
503 of this as transportation from the present into the future. (It
504 is a science-fiction idiom that you can move through time as well
505 as in space; the idea here is that `tar' can be used to move
506 archives in all dimensions, even time!)
509 Because the archive created by `tar' is capable of preserving file
510 information and directory structure, `tar' is commonly used for
511 performing full and incremental backups of disks. A backup puts a
512 collection of files (possibly pertaining to many users and
513 projects) together on a disk or a tape. This guards against
514 accidental destruction of the information in those files. GNU
515 `tar' has special features that allow it to be used to make
516 incremental and full dumps of all the files in a file system.
519 You can create an archive on one system, transfer it to another
520 system, and extract the contents there. This allows you to
521 transport a group of files from one system to another.
524 File: tar.info, Node: Naming tar Archives, Next: Authors, Prev: What tar Does, Up: Introduction
526 1.4 How `tar' Archives are Named
527 ================================
529 Conventionally, `tar' archives are given names ending with `.tar'.
530 This is not necessary for `tar' to operate properly, but this manual
531 follows that convention in order to accustom readers to it and to make
534 Often, people refer to `tar' archives as "`tar' files," and archive
535 members as "files" or "entries". For people familiar with the
536 operation of `tar', this causes no difficulty. However, in this
537 manual, we consistently refer to "archives" and "archive members" to
538 make learning to use `tar' easier for novice users.
541 File: tar.info, Node: Authors, Next: Reports, Prev: Naming tar Archives, Up: Introduction
543 1.5 GNU `tar' Authors
544 =====================
546 GNU `tar' was originally written by John Gilmore, and modified by many
547 people. The GNU enhancements were written by Jay Fenlason, then Joy
548 Kendall, and the whole package has been further maintained by Thomas
549 Bushnell, n/BSG, Franc,ois Pinard, Paul Eggert, and finally Sergey
550 Poznyakoff with the help of numerous and kind users.
552 We wish to stress that `tar' is a collective work, and owes much to
553 all those people who reported problems, offered solutions and other
554 insights, or shared their thoughts and suggestions. An impressive, yet
555 partial list of those contributors can be found in the `THANKS' file
556 from the GNU `tar' distribution.
558 Jay Fenlason put together a draft of a GNU `tar' manual, borrowing
559 notes from the original man page from John Gilmore. This was withdrawn
560 in version 1.11. Thomas Bushnell, n/BSG and Amy Gorin worked on a
561 tutorial and manual for GNU `tar'. Franc,ois Pinard put version 1.11.8
562 of the manual together by taking information from all these sources and
563 merging them. Melissa Weisshaus finally edited and redesigned the book
564 to create version 1.12. The book for versions from 1.14 up to 1.22
565 were edited by the current maintainer, Sergey Poznyakoff.
567 For version 1.12, Daniel Hagerty contributed a great deal of
568 technical consulting. In particular, he is the primary author of *note
571 In July, 2003 GNU `tar' was put on CVS at savannah.gnu.org (see
572 `http://savannah.gnu.org/projects/tar'), and active development and
573 maintenance work has started again. Currently GNU `tar' is being
574 maintained by Paul Eggert, Sergey Poznyakoff and Jeff Bailey.
576 Support for POSIX archives was added by Sergey Poznyakoff.
579 File: tar.info, Node: Reports, Prev: Authors, Up: Introduction
581 1.6 Reporting bugs or suggestions
582 =================================
584 If you find problems or have suggestions about this program or manual,
585 please report them to `bug-tar@gnu.org'.
587 When reporting a bug, please be sure to include as much detail as
588 possible, in order to reproduce it. .
591 File: tar.info, Node: Tutorial, Next: tar invocation, Prev: Introduction, Up: Top
593 2 Tutorial Introduction to `tar'
594 ********************************
596 This chapter guides you through some basic examples of three `tar'
597 operations: `--create', `--list', and `--extract'. If you already know
598 how to use some other version of `tar', then you may not need to read
599 this chapter. This chapter omits most complicated details about how
605 * stylistic conventions::
606 * basic tar options:: Basic `tar' Operations and Options
607 * frequent operations::
608 * Two Frequent Options::
609 * create:: How to Create Archives
610 * list:: How to List Archives
611 * extract:: How to Extract Members from an Archive
615 File: tar.info, Node: assumptions, Next: stylistic conventions, Up: Tutorial
617 2.1 Assumptions this Tutorial Makes
618 ===================================
620 This chapter is paced to allow beginners to learn about `tar' slowly.
621 At the same time, we will try to cover all the basic aspects of these
622 three operations. In order to accomplish both of these tasks, we have
623 made certain assumptions about your knowledge before reading this
624 manual, and the hardware you will be using:
626 * Before you start to work through this tutorial, you should
627 understand what the terms "archive" and "archive member" mean
628 (*note Definitions::). In addition, you should understand
629 something about how Unix-type operating systems work, and you
630 should know how to use some basic utilities. For example, you
631 should know how to create, list, copy, rename, edit, and delete
632 files and directories; how to change between directories; and how
633 to figure out where you are in the file system. You should have
634 some basic understanding of directory structure and how files are
635 named according to which directory they are in. You should
636 understand concepts such as standard output and standard input,
637 what various definitions of the term `argument' mean, and the
638 differences between relative and absolute file names.
640 * This manual assumes that you are working from your own home
641 directory (unless we state otherwise). In this tutorial, you will
642 create a directory to practice `tar' commands in. When we show
643 file names, we will assume that those names are relative to your
644 home directory. For example, my home directory is
645 `/home/fsf/melissa'. All of my examples are in a subdirectory of
646 the directory named by that file name; the subdirectory is called
649 * In general, we show examples of archives which exist on (or can be
650 written to, or worked with from) a directory on a hard disk. In
651 most cases, you could write those archives to, or work with them
652 on any other device, such as a tape drive. However, some of the
653 later examples in the tutorial and next chapter will not work on
654 tape drives. Additionally, working with tapes is much more
655 complicated than working with hard disks. For these reasons, the
656 tutorial does not cover working with tape drives. *Note Media::,
657 for complete information on using `tar' archives with tape drives.
661 File: tar.info, Node: stylistic conventions, Next: basic tar options, Prev: assumptions, Up: Tutorial
663 2.2 Stylistic Conventions
664 =========================
666 In the examples, `$' represents a typical shell prompt. It precedes
667 lines you should type; to make this more clear, those lines are shown
668 in `this font', as opposed to lines which represent the computer's
669 response; those lines are shown in `this font', or sometimes `like
673 File: tar.info, Node: basic tar options, Next: frequent operations, Prev: stylistic conventions, Up: Tutorial
675 2.3 Basic `tar' Operations and Options
676 ======================================
678 `tar' can take a wide variety of arguments which specify and define the
679 actions it will have on the particular set of files or the archive.
680 The main types of arguments to `tar' fall into one of two classes:
681 operations, and options.
683 Some arguments fall into a class called "operations"; exactly one of
684 these is both allowed and required for any instance of using `tar'; you
685 may _not_ specify more than one. People sometimes speak of "operating
686 modes". You are in a particular operating mode when you have specified
687 the operation which specifies it; there are eight operations in total,
688 and thus there are eight operating modes.
690 The other arguments fall into the class known as "options". You are
691 not required to specify any options, and you are allowed to specify more
692 than one at a time (depending on the way you are using `tar' at that
693 time). Some options are used so frequently, and are so useful for
694 helping you type commands more carefully that they are effectively
695 "required". We will discuss them in this chapter.
697 You can write most of the `tar' operations and options in any of
698 three forms: long (mnemonic) form, short form, and old style. Some of
699 the operations and options have no short or "old" forms; however, the
700 operations and options which we will cover in this tutorial have
701 corresponding abbreviations. We will indicate those abbreviations
702 appropriately to get you used to seeing them. (Note that the "old
703 style" option forms exist in GNU `tar' for compatibility with Unix
704 `tar'. In this book we present a full discussion of this way of
705 writing options and operations (*note Old Options::), and we discuss
706 the other two styles of writing options (*Note Long Options::, and
707 *note Short Options::).
709 In the examples and in the text of this tutorial, we usually use the
710 long forms of operations and options; but the "short" forms produce the
711 same result and can make typing long `tar' commands easier. For
712 example, instead of typing
714 tar --create --verbose --file=afiles.tar apple angst aspic
717 tar -c -v -f afiles.tar apple angst aspic
720 tar -cvf afiles.tar apple angst aspic
722 For more information on option syntax, see *note Advanced tar::. In
723 discussions in the text, when we name an option by its long form, we
724 also give the corresponding short option in parentheses.
726 The term, "option", can be confusing at times, since "operations"
727 are often lumped in with the actual, _optional_ "options" in certain
728 general class statements. For example, we just talked about "short and
729 long forms of options and operations". However, experienced `tar'
730 users often refer to these by shorthand terms such as, "short and long
731 options". This term assumes that the "operations" are included, also.
732 Context will help you determine which definition of "options" to use.
734 Similarly, the term "command" can be confusing, as it is often used
735 in two different ways. People sometimes refer to `tar' "commands". A
736 `tar' "command" is the entire command line of user input which tells
737 `tar' what to do -- including the operation, options, and any arguments
738 (file names, pipes, other commands, etc.). However, you will also
739 sometimes hear the term "the `tar' command". When the word "command"
740 is used specifically like this, a person is usually referring to the
741 `tar' _operation_, not the whole line. Again, use context to figure
742 out which of the meanings the speaker intends.
745 File: tar.info, Node: frequent operations, Next: Two Frequent Options, Prev: basic tar options, Up: Tutorial
747 2.4 The Three Most Frequently Used Operations
748 =============================================
750 Here are the three most frequently used operations (both short and long
751 forms), as well as a brief description of their meanings. The rest of
752 this chapter will cover how to use these operations in detail. We will
753 present the rest of the operations in the next chapter.
757 Create a new `tar' archive.
761 List the contents of an archive.
765 Extract one or more members from an archive.
768 File: tar.info, Node: Two Frequent Options, Next: create, Prev: frequent operations, Up: Tutorial
770 2.5 Two Frequently Used Options
771 ===============================
773 To understand how to run `tar' in the three operating modes listed
774 previously, you also need to understand how to use two of the options to
775 `tar': `--file' (which takes an archive file as an argument) and
776 `--verbose'. (You are usually not _required_ to specify either of
777 these options when you run `tar', but they can be very useful in making
778 things more clear and helping you avoid errors.)
787 File: tar.info, Node: file tutorial, Next: verbose tutorial, Up: Two Frequent Options
792 `--file=ARCHIVE-NAME'
794 Specify the name of an archive file.
796 You can specify an argument for the `--file=ARCHIVE-NAME' (`-f
797 ARCHIVE-NAME') option whenever you use `tar'; this option determines
798 the name of the archive file that `tar' will work on.
800 If you don't specify this argument, then `tar' will examine the
801 environment variable `TAPE'. If it is set, its value will be used as
802 the archive name. Otherwise, `tar' will use the default archive,
803 determined at the compile time. Usually it is standard output or some
804 physical tape drive attached to your machine (you can verify what the
805 default is by running `tar --show-defaults', *note defaults::). If
806 there is no tape drive attached, or the default is not meaningful, then
807 `tar' will print an error message. The error message might look
808 roughly like one of the following:
810 tar: can't open /dev/rmt8 : No such device or address
811 tar: can't open /dev/rsmt0 : I/O error
813 To avoid confusion, we recommend that you always specify an archive file
814 name by using `--file=ARCHIVE-NAME' (`-f ARCHIVE-NAME') when writing
815 your `tar' commands. For more information on using the
816 `--file=ARCHIVE-NAME' (`-f ARCHIVE-NAME') option, see *note file::.
819 File: tar.info, Node: verbose tutorial, Next: help tutorial, Prev: file tutorial, Up: Two Frequent Options
821 The `--verbose' Option
822 ----------------------
826 Show the files being worked on as `tar' is running.
828 `--verbose' (`-v') shows details about the results of running `tar'.
829 This can be especially useful when the results might not be obvious.
830 For example, if you want to see the progress of `tar' as it writes
831 files into the archive, you can use the `--verbose' option. In the
832 beginning, you may find it useful to use `--verbose' at all times; when
833 you are more accustomed to `tar', you will likely want to use it at
834 certain times but not at others. We will use `--verbose' at times to
835 help make something clear, and we will give many examples both using
836 and not using `--verbose' to show the differences.
838 Each instance of `--verbose' on the command line increases the
839 verbosity level by one, so if you need more details on the output,
842 When reading archives (`--list', `--extract', `--diff'), `tar' by
843 default prints only the names of the members being extracted. Using
844 `--verbose' will show a full, `ls' style member listing.
846 In contrast, when writing archives (`--create', `--append',
847 `--update'), `tar' does not print file names by default. So, a single
848 `--verbose' option shows the file names being added to the archive,
849 while two `--verbose' options enable the full listing.
851 For example, to create an archive in verbose mode:
853 $ tar -cvf afiles.tar apple angst aspic
858 Creating the same archive with the verbosity level 2 could give:
860 $ tar -cvvf afiles.tar apple angst aspic
861 -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
862 -rw-r--r-- gray/staff 11481 2006-06-09 12:06 angst
863 -rw-r--r-- gray/staff 23152 2006-06-09 12:06 aspic
865 This works equally well using short or long forms of options. Using
866 long forms, you would simply write out the mnemonic form of the option
869 $ tar --create --verbose --verbose ...
871 Note that you must double the hyphens properly each time.
873 Later in the tutorial, we will give examples using
874 `--verbose --verbose'.
876 The full output consists of six fields:
878 * File type and permissions in symbolic form. These are displayed
879 in the same format as the first column of `ls -l' output (*note
880 format=verbose: (fileutils)What information is listed.).
882 * Owner name and group separated by a slash character. If these
883 data are not available (for example, when listing a `v7' format
884 archive), numeric ID values are printed instead.
886 * Size of the file, in bytes.
888 * File modification date in ISO 8601 format.
890 * File modification time.
892 * File name. If the name contains any special characters (white
893 space, newlines, etc.) these are displayed in an unambiguous form
894 using so called "quoting style". For the detailed discussion of
895 available styles and on how to use them, see *note quoting
898 Depending on the file type, the name can be followed by some
899 additional information, described in the following table:
902 The file or archive member is a "symbolic link" and LINK-NAME
903 is the name of file it links to.
906 The file or archive member is a "hard link" and LINK-NAME is
907 the name of file it links to.
910 The archive member is an old GNU format long link. You will
911 normally not encounter this.
914 The archive member is an old GNU format long name. You will
915 normally not encounter this.
918 The archive member is a GNU "volume header" (*note Tape
921 `--Continued at byte N--'
922 Encountered only at the beginning of a multi-volume archive
923 (*note Using Multiple Tapes::). This archive member is a
924 continuation from the previous volume. The number N gives the
925 offset where the original file was split.
927 `unknown file type C'
928 An archive member of unknown type. C is the type character
929 from the archive header. If you encounter such a message, it
930 means that either your archive contains proprietary member
931 types GNU `tar' is not able to handle, or the archive is
935 For example, here is an archive listing containing most of the
936 special suffixes explained above:
938 V--------- 0/0 1536 2006-06-09 13:07 MyVolume--Volume Header--
939 -rw-r--r-- gray/staff 456783 2006-06-09 12:06 aspic--Continued at
941 -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
942 lrwxrwxrwx gray/staff 0 2006-06-09 13:01 angst -> apple
943 -rw-r--r-- gray/staff 35793 2006-06-09 12:06 blues
944 hrw-r--r-- gray/staff 0 2006-06-09 12:06 music link to blues
948 File: tar.info, Node: help tutorial, Prev: verbose tutorial, Up: Two Frequent Options
950 Getting Help: Using the `--help' Option
951 ---------------------------------------
954 The `--help' option to `tar' prints out a very brief list of all
955 operations and option available for the current version of `tar'
956 available on your system.
959 File: tar.info, Node: create, Next: list, Prev: Two Frequent Options, Up: Tutorial
961 2.6 How to Create Archives
962 ==========================
964 _(This message will disappear, once this node revised.)_
966 One of the basic operations of `tar' is `--create' (`-c'), which you
967 use to create a `tar' archive. We will explain `--create' first
968 because, in order to learn about the other operations, you will find it
969 useful to have an archive available to practice on.
971 To make this easier, in this section you will first create a
972 directory containing three files. Then, we will show you how to create
973 an _archive_ (inside the new directory). Both the directory, and the
974 archive are specifically for you to practice on. The rest of this
975 chapter and the next chapter will show many examples using this
976 directory and the files you will create: some of those files may be
977 other directories and other archives.
979 The three files you will archive in this example are called `blues',
980 `folk', and `jazz'. The archive is called `collection.tar'.
982 This section will proceed slowly, detailing how to use `--create' in
983 `verbose' mode, and showing examples using both short and long forms.
984 In the rest of the tutorial, and in the examples in the next chapter,
985 we will proceed at a slightly quicker pace. This section moves more
986 slowly to allow beginning users to understand how `tar' works.
990 * prepare for examples::
991 * Creating the archive::
997 File: tar.info, Node: prepare for examples, Next: Creating the archive, Up: create
999 2.6.1 Preparing a Practice Directory for Examples
1000 -------------------------------------------------
1002 To follow along with this and future examples, create a new directory
1003 called `practice' containing files called `blues', `folk' and `jazz'.
1004 The files can contain any information you like: ideally, they should
1005 contain information which relates to their names, and be of different
1006 lengths. Our examples assume that `practice' is a subdirectory of your
1009 Now `cd' to the directory named `practice'; `practice' is now your
1010 "working directory". (_Please note_: Although the full file name of
1011 this directory is `/HOMEDIR/practice', in our examples we will refer to
1012 this directory as `practice'; the HOMEDIR is presumed.
1014 In general, you should check that the files to be archived exist
1015 where you think they do (in the working directory) by running `ls'.
1016 Because you just created the directory and the files and have changed to
1017 that directory, you probably don't need to do that this time.
1019 It is very important to make sure there isn't already a file in the
1020 working directory with the archive name you intend to use (in this case,
1021 `collection.tar'), or that you don't care about its contents. Whenever
1022 you use `create', `tar' will erase the current contents of the file
1023 named by `--file=ARCHIVE-NAME' (`-f ARCHIVE-NAME') if it exists. `tar'
1024 will not tell you if you are about to overwrite an archive unless you
1025 specify an option which does this (*note backup::, for the information
1026 on how to do so). To add files to an existing archive, you need to use
1027 a different option, such as `--append' (`-r'); see *note append:: for
1028 information on how to do this.
1031 File: tar.info, Node: Creating the archive, Next: create verbose, Prev: prepare for examples, Up: create
1033 2.6.2 Creating the Archive
1034 --------------------------
1036 To place the files `blues', `folk', and `jazz' into an archive named
1037 `collection.tar', use the following command:
1039 $ tar --create --file=collection.tar blues folk jazz
1041 The order of the arguments is not very important, _when using long
1042 option forms_. You could also say:
1044 $ tar blues --create folk --file=collection.tar jazz
1046 However, you can see that this order is harder to understand; this is
1047 why we will list the arguments in the order that makes the commands
1048 easiest to understand (and we encourage you to do the same when you use
1049 `tar', to avoid errors).
1051 Note that the sequence `--file=collection.tar' is considered to be
1052 _one_ argument. If you substituted any other string of characters for
1053 `collection.tar', then that string would become the name of the
1054 archive file you create.
1056 The order of the options becomes more important when you begin to use
1057 short forms. With short forms, if you type commands in the wrong order
1058 (even if you type them correctly in all other ways), you may end up with
1059 results you don't expect. For this reason, it is a good idea to get
1060 into the habit of typing options in the order that makes inherent sense.
1061 *Note short create::, for more information on this.
1063 In this example, you type the command as shown above: `--create' is
1064 the operation which creates the new archive (`collection.tar'), and
1065 `--file' is the option which lets you give it the name you chose. The
1066 files, `blues', `folk', and `jazz', are now members of the archive,
1067 `collection.tar' (they are "file name arguments" to the `--create'
1068 operation. *Note Choosing::, for the detailed discussion on these.)
1069 Now that they are in the archive, they are called _archive members_,
1070 not files. (*note members: Definitions.).
1072 When you create an archive, you _must_ specify which files you want
1073 placed in the archive. If you do not specify any archive members, GNU
1074 `tar' will complain.
1076 If you now list the contents of the working directory (`ls'), you
1077 will find the archive file listed as well as the files you saw
1080 blues folk jazz collection.tar
1082 Creating the archive `collection.tar' did not destroy the copies of the
1083 files in the directory.
1085 Keep in mind that if you don't indicate an operation, `tar' will not
1086 run and will prompt you for one. If you don't name any files, `tar'
1087 will complain. You must have write access to the working directory, or
1088 else you will not be able to create an archive in that directory.
1090 _Caution_: Do not attempt to use `--create' (`-c') to add files to
1091 an existing archive; it will delete the archive and write a new one.
1092 Use `--append' (`-r') instead. *Note append::.
1095 File: tar.info, Node: create verbose, Next: short create, Prev: Creating the archive, Up: create
1097 2.6.3 Running `--create' with `--verbose'
1098 -----------------------------------------
1100 If you include the `--verbose' (`-v') option on the command line, `tar'
1101 will list the files it is acting on as it is working. In verbose mode,
1102 the `create' example above would appear as:
1104 $ tar --create --verbose --file=collection.tar blues folk jazz
1109 This example is just like the example we showed which did not use
1110 `--verbose', except that `tar' generated the remaining lines .
1112 In the rest of the examples in this chapter, we will frequently use
1113 `verbose' mode so we can show actions or `tar' responses that you would
1114 otherwise not see, and which are important for you to understand.
1117 File: tar.info, Node: short create, Next: create dir, Prev: create verbose, Up: create
1119 2.6.4 Short Forms with `create'
1120 -------------------------------
1122 As we said before, the `--create' (`-c') operation is one of the most
1123 basic uses of `tar', and you will use it countless times. Eventually,
1124 you will probably want to use abbreviated (or "short") forms of
1125 options. A full discussion of the three different forms that options
1126 can take appears in *note Styles::; for now, here is what the previous
1127 example (including the `--verbose' (`-v') option) looks like using
1130 $ tar -cvf collection.tar blues folk jazz
1135 As you can see, the system responds the same no matter whether you use
1136 long or short option forms.
1138 One difference between using short and long option forms is that,
1139 although the exact placement of arguments following options is no more
1140 specific when using short forms, it is easier to become confused and
1141 make a mistake when using short forms. For example, suppose you
1142 attempted the above example in the following way:
1144 $ tar -cfv collection.tar blues folk jazz
1146 In this case, `tar' will make an archive file called `v', containing
1147 the files `blues', `folk', and `jazz', because the `v' is the closest
1148 "file name" to the `-f' option, and is thus taken to be the chosen
1149 archive file name. `tar' will try to add a file called
1150 `collection.tar' to the `v' archive file; if the file `collection.tar'
1151 did not already exist, `tar' will report an error indicating that this
1152 file does not exist. If the file `collection.tar' does already exist
1153 (e.g., from a previous command you may have run), then `tar' will add
1154 this file to the archive. Because the `-v' option did not get
1155 registered, `tar' will not run under `verbose' mode, and will not
1156 report its progress.
1158 The end result is that you may be quite confused about what happened,
1159 and possibly overwrite a file. To illustrate this further, we will show
1160 you how an example we showed previously would look using short forms.
1164 $ tar blues --create folk --file=collection.tar jazz
1166 is confusing as it is. When shown using short forms, however, it
1167 becomes much more so:
1169 $ tar blues -c folk -f collection.tar jazz
1171 It would be very easy to put the wrong string of characters immediately
1172 following the `-f', but doing that could sacrifice valuable data.
1174 For this reason, we recommend that you pay very careful attention to
1175 the order of options and placement of file and archive names,
1176 especially when using short option forms. Not having the option name
1177 written out mnemonically can affect how well you remember which option
1178 does what, and therefore where different names have to be placed.
1181 File: tar.info, Node: create dir, Prev: short create, Up: create
1183 2.6.5 Archiving Directories
1184 ---------------------------
1186 You can archive a directory by specifying its directory name as a file
1187 name argument to `tar'. The files in the directory will be archived
1188 relative to the working directory, and the directory will be re-created
1189 along with its contents when the archive is extracted.
1191 To archive a directory, first move to its superior directory. If you
1192 have followed the previous instructions in this tutorial, you should
1198 This will put you into the directory which contains `practice', i.e.,
1199 your home directory. Once in the superior directory, you can specify
1200 the subdirectory, `practice', as a file name argument. To store
1201 `practice' in the new archive file `music.tar', type:
1203 $ tar --create --verbose --file=music.tar practice
1205 `tar' should output:
1211 practice/collection.tar
1213 Note that the archive thus created is not in the subdirectory
1214 `practice', but rather in the current working directory--the directory
1215 from which `tar' was invoked. Before trying to archive a directory
1216 from its superior directory, you should make sure you have write access
1217 to the superior directory itself, not only the directory you are trying
1218 archive with `tar'. For example, you will probably not be able to
1219 store your home directory in an archive by invoking `tar' from the root
1220 directory; *Note absolute::. (Note also that `collection.tar', the
1221 original archive file, has itself been archived. `tar' will accept any
1222 file as a file to be archived, regardless of its content. When
1223 `music.tar' is extracted, the archive file `collection.tar' will be
1224 re-written into the file system).
1226 If you give `tar' a command such as
1228 $ tar --create --file=foo.tar .
1230 `tar' will report `tar: ./foo.tar is the archive; not dumped'. This
1231 happens because `tar' creates the archive `foo.tar' in the current
1232 directory before putting any files into it. Then, when `tar' attempts
1233 to add all the files in the directory `.' to the archive, it notices
1234 that the file `./foo.tar' is the same as the archive `foo.tar', and
1235 skips it. (It makes no sense to put an archive into itself.) GNU `tar'
1236 will continue in this case, and create the archive normally, except for
1237 the exclusion of that one file. (_Please note:_ Other implementations
1238 of `tar' may not be so clever; they will enter an infinite loop when
1239 this happens, so you should not depend on this behavior unless you are
1240 certain you are running GNU `tar'. In general, it is wise to always
1241 place the archive outside of the directory being dumped.
1244 File: tar.info, Node: list, Next: extract, Prev: create, Up: Tutorial
1246 2.7 How to List Archives
1247 ========================
1249 Frequently, you will find yourself wanting to determine exactly what a
1250 particular archive contains. You can use the `--list' (`-t') operation
1251 to get the member names as they currently appear in the archive, as
1252 well as various attributes of the files at the time they were archived.
1253 For example, you can examine the archive `collection.tar' that you
1254 created in the last section with the command,
1256 $ tar --list --file=collection.tar
1258 The output of `tar' would then be:
1264 The archive `bfiles.tar' would list as follows:
1270 Be sure to use a `--file=ARCHIVE-NAME' (`-f ARCHIVE-NAME') option just
1271 as with `--create' (`-c') to specify the name of the archive.
1273 If you use the `--verbose' (`-v') option with `--list', then `tar'
1274 will print out a listing reminiscent of `ls -l', showing owner, file
1275 size, and so forth. This output is described in detail in *note
1276 verbose member listing::.
1278 If you had used `--verbose' (`-v') mode, the example above would
1281 $ tar --list --verbose --file=collection.tar folk
1282 -rw-r--r-- myself user 62 1990-05-23 10:55 folk
1284 It is important to notice that the output of `tar --list --verbose'
1285 does not necessarily match that produced by `tar --create --verbose'
1286 while creating the archive. It is because GNU `tar', unless told
1287 explicitly not to do so, removes some directory prefixes from file
1288 names before storing them in the archive (*Note absolute::, for more
1289 information). In other words, in verbose mode GNU `tar' shows "file
1290 names" when creating an archive and "member names" when listing it.
1291 Consider this example:
1293 $ tar cfv archive /etc/mail
1294 tar: Removing leading `/' from member names
1296 /etc/mail/sendmail.cf
1300 etc/mail/sendmail.cf
1303 This default behavior can sometimes be inconvenient. You can force
1304 GNU `tar' show member names when creating archive by supplying
1305 `--show-stored-names' option.
1307 `--show-stored-names'
1308 Print member (as opposed to _file_) names when creating the
1311 You can specify one or more individual member names as arguments when
1312 using `list'. In this case, `tar' will only list the names of members
1313 you identify. For example, `tar --list --file=afiles.tar apple' would
1316 Because `tar' preserves file names, these must be specified as they
1317 appear in the archive (i.e., relative to the directory from which the
1318 archive was created). Therefore, it is essential when specifying
1319 member names to `tar' that you give the exact member names. For
1320 example, `tar --list --file=bfiles.tar birds' would produce an error
1321 message something like `tar: birds: Not found in archive', because
1322 there is no member named `birds', only one named `./birds'. While the
1323 names `birds' and `./birds' name the same file, _member_ names by
1324 default are compared verbatim.
1326 However, `tar --list --file=bfiles.tar baboon' would respond with
1327 `baboon', because this exact member name is in the archive file
1328 `bfiles.tar'. If you are not sure of the exact file name, use
1329 "globbing patterns", for example:
1331 $ tar --list --file=bfiles.tar --wildcards '*b*'
1333 will list all members whose name contains `b'. *Note wildcards::, for
1334 a detailed discussion of globbing patterns and related `tar' command
1342 File: tar.info, Node: list dir, Up: list
1344 Listing the Contents of a Stored Directory
1345 ------------------------------------------
1347 To get information about the contents of an archived directory, use the
1348 directory name as a file name argument in conjunction with `--list'
1349 (`-t'). To find out file attributes, include the `--verbose' (`-v')
1352 For example, to find out about files in the directory `practice', in
1353 the archive file `music.tar', type:
1355 $ tar --list --verbose --file=music.tar practice
1359 drwxrwxrwx myself user 0 1990-05-31 21:49 practice/
1360 -rw-r--r-- myself user 42 1990-05-21 13:29 practice/blues
1361 -rw-r--r-- myself user 62 1990-05-23 10:55 practice/folk
1362 -rw-r--r-- myself user 40 1990-05-21 13:30 practice/jazz
1363 -rw-r--r-- myself user 10240 1990-05-31 21:49 practice/collection.tar
1365 When you use a directory name as a file name argument, `tar' acts on
1366 all the files (including sub-directories) in that directory.
1369 File: tar.info, Node: extract, Next: going further, Prev: list, Up: Tutorial
1371 2.8 How to Extract Members from an Archive
1372 ==========================================
1374 _(This message will disappear, once this node revised.)_
1376 Creating an archive is only half the job--there is no point in storing
1377 files in an archive if you can't retrieve them. The act of retrieving
1378 members from an archive so they can be used and manipulated as
1379 unarchived files again is called "extraction". To extract files from
1380 an archive, use the `--extract' (`--get' or `-x') operation. As with
1381 `--create', specify the name of the archive with `--file' (`-f')
1382 option. Extracting an archive does not modify the archive in any way;
1383 you can extract it multiple times if you want or need to.
1385 Using `--extract', you can extract an entire archive, or specific
1386 files. The files can be directories containing other files, or not. As
1387 with `--create' (`-c') and `--list' (`-t'), you may use the short or the
1388 long form of the operation without affecting the performance.
1392 * extracting archives::
1393 * extracting files::
1395 * extracting untrusted archives::
1396 * failing commands::
1399 File: tar.info, Node: extracting archives, Next: extracting files, Up: extract
1401 2.8.1 Extracting an Entire Archive
1402 ----------------------------------
1404 To extract an entire archive, specify the archive file name only, with
1405 no individual file names as arguments. For example,
1407 $ tar -xvf collection.tar
1411 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
1412 -rw-r--r-- me user 21 1996-09-23 16:44 blues
1413 -rw-r--r-- me user 20 1996-09-23 16:44 folk
1416 File: tar.info, Node: extracting files, Next: extract dir, Prev: extracting archives, Up: extract
1418 2.8.2 Extracting Specific Files
1419 -------------------------------
1421 To extract specific archive members, give their exact member names as
1422 arguments, as printed by `--list' (`-t'). If you had mistakenly
1423 deleted one of the files you had placed in the archive `collection.tar'
1424 earlier (say, `blues'), you can extract it from the archive without
1425 changing the archive's structure. Its contents will be identical to
1426 the original file `blues' that you deleted.
1428 First, make sure you are in the `practice' directory, and list the
1429 files in the directory. Now, delete the file, `blues', and list the
1430 files in the directory again.
1432 You can now extract the member `blues' from the archive file
1433 `collection.tar' like this:
1435 $ tar --extract --file=collection.tar blues
1437 If you list the files in the directory again, you will see that the file
1438 `blues' has been restored, with its original permissions, data
1439 modification times, and owner.(1) (These parameters will be identical
1440 to those which the file had when you originally placed it in the
1441 archive; any changes you may have made before deleting the file from
1442 the file system, however, will _not_ have been made to the archive
1443 member.) The archive file, `collection.tar', is the same as it was
1444 before you extracted `blues'. You can confirm this by running `tar'
1445 with `--list' (`-t').
1447 Remember that as with other operations, specifying the exact member
1448 name is important. `tar --extract --file=bfiles.tar birds' will fail,
1449 because there is no member named `birds'. To extract the member named
1450 `./birds', you must specify `tar --extract --file=bfiles.tar ./birds'.
1451 If you don't remember the exact member names, use `--list' (`-t') option
1452 (*note list::). You can also extract those members that match a
1453 specific "globbing pattern". For example, to extract from `bfiles.tar'
1454 all files that begin with `b', no matter their directory prefix, you
1457 $ tar -x -f bfiles.tar --wildcards --no-anchored 'b*'
1459 Here, `--wildcards' instructs `tar' to treat command line arguments as
1460 globbing patterns and `--no-anchored' informs it that the patterns
1461 apply to member names after any `/' delimiter. The use of globbing
1462 patterns is discussed in detail in *Note wildcards::.
1464 You can extract a file to standard output by combining the above
1465 options with the `--to-stdout' (`-O') option (*note Writing to Standard
1468 If you give the `--verbose' option, then `--extract' will print the
1469 names of the archive members as it extracts them.
1471 ---------- Footnotes ----------
1473 (1) This is only accidentally true, but not in general. Whereas
1474 modification times are always restored, in most cases, one has to be
1475 root for restoring the owner, and use a special option for restoring
1476 permissions. Here, it just happens that the restoring user is also the
1477 owner of the archived members, and that the current `umask' is
1478 compatible with original permissions.
1481 File: tar.info, Node: extract dir, Next: extracting untrusted archives, Prev: extracting files, Up: extract
1483 2.8.3 Extracting Files that are Directories
1484 -------------------------------------------
1486 Extracting directories which are members of an archive is similar to
1487 extracting other files. The main difference to be aware of is that if
1488 the extracted directory has the same name as any directory already in
1489 the working directory, then files in the extracted directory will be
1490 placed into the directory of the same name. Likewise, if there are
1491 files in the pre-existing directory with the same names as the members
1492 which you extract, the files from the extracted archive will replace
1493 the files already in the working directory (and possible
1494 subdirectories). This will happen regardless of whether or not the
1495 files in the working directory were more recent than those extracted
1496 (there exist, however, special options that alter this behavior *note
1499 However, if a file was stored with a directory name as part of its
1500 file name, and that directory does not exist under the working
1501 directory when the file is extracted, `tar' will create the directory.
1503 We can demonstrate how to use `--extract' to extract a directory
1504 file with an example. Change to the `practice' directory if you
1505 weren't there, and remove the files `folk' and `jazz'. Then, go back
1506 to the parent directory and extract the archive `music.tar'. You may
1507 either extract the entire archive, or you may extract only the files
1508 you just deleted. To extract the entire archive, don't give any file
1509 names as arguments after the archive name `music.tar'. To extract only
1510 the files you deleted, use the following command:
1512 $ tar -xvf music.tar practice/folk practice/jazz
1516 If you were to specify two `--verbose' (`-v') options, `tar' would have
1517 displayed more detail about the extracted files, as shown in the
1520 $ tar -xvvf music.tar practice/folk practice/jazz
1521 -rw-r--r-- me user 28 1996-10-18 16:31 practice/jazz
1522 -rw-r--r-- me user 20 1996-09-23 16:44 practice/folk
1524 Because you created the directory with `practice' as part of the file
1525 names of each of the files by archiving the `practice' directory as
1526 `practice', you must give `practice' as part of the file names when you
1527 extract those files from the archive.
1530 File: tar.info, Node: extracting untrusted archives, Next: failing commands, Prev: extract dir, Up: extract
1532 2.8.4 Extracting Archives from Untrusted Sources
1533 ------------------------------------------------
1535 Extracting files from archives can overwrite files that already exist.
1536 If you receive an archive from an untrusted source, you should make a
1537 new directory and extract into that directory, so that you don't have
1538 to worry about the extraction overwriting one of your existing files.
1539 For example, if `untrusted.tar' came from somewhere else on the
1540 Internet, and you don't necessarily trust its contents, you can extract
1545 $ tar -xvf ../untrusted.tar
1547 It is also a good practice to examine contents of the archive before
1548 extracting it, using `--list' (`-t') option, possibly combined with
1552 File: tar.info, Node: failing commands, Prev: extracting untrusted archives, Up: extract
1554 2.8.5 Commands That Will Fail
1555 -----------------------------
1557 Here are some sample commands you might try which will not work, and why
1560 If you try to use this command,
1562 $ tar -xvf music.tar folk jazz
1564 you will get the following response:
1566 tar: folk: Not found in archive
1567 tar: jazz: Not found in archive
1570 This is because these files were not originally _in_ the parent
1571 directory `..', where the archive is located; they were in the
1572 `practice' directory, and their file names reflect this:
1574 $ tar -tvf music.tar
1579 Likewise, if you try to use this command,
1581 $ tar -tvf music.tar folk jazz
1583 you would get a similar response. Members with those names are not in
1584 the archive. You must use the correct member names, or wildcards, in
1585 order to extract the files from the archive.
1587 If you have forgotten the correct names of the files in the archive,
1588 use `tar --list --verbose' to list them correctly.
1591 File: tar.info, Node: going further, Prev: extract, Up: Tutorial
1593 2.9 Going Further Ahead in this Manual
1594 ======================================
1596 _(This message will disappear, once this node revised.)_
1599 File: tar.info, Node: tar invocation, Next: operations, Prev: Tutorial, Up: Top
1601 3 Invoking GNU `tar'
1602 ********************
1604 _(This message will disappear, once this node revised.)_
1606 This chapter is about how one invokes the GNU `tar' command, from the
1607 command synopsis (*note Synopsis::). There are numerous options, and
1608 many styles for writing them. One mandatory option specifies the
1609 operation `tar' should perform (*note Operation Summary::), other
1610 options are meant to detail how this operation should be performed
1611 (*note Option Summary::). Non-option arguments are not always
1612 interpreted the same way, depending on what the operation is.
1614 You will find in this chapter everything about option styles and
1615 rules for writing them (*note Styles::). On the other hand, operations
1616 and options are fully described elsewhere, in other chapters. Here,
1617 you will find only synthetic descriptions for operations and options,
1618 together with pointers to other parts of the `tar' manual.
1620 Some options are so special they are fully described right in this
1621 chapter. They have the effect of inhibiting the normal operation of
1622 `tar' or else, they globally alter the amount of feedback the user
1623 receives about what is going on. These are the `--help' and
1624 `--version' (*note help::), `--verbose' (*note verbose::) and
1625 `--interactive' options (*note interactive::).
1630 * using tar options::
1640 File: tar.info, Node: Synopsis, Next: using tar options, Up: tar invocation
1642 3.1 General Synopsis of `tar'
1643 =============================
1645 The GNU `tar' program is invoked as either one of:
1647 tar OPTION... [NAME]...
1648 tar LETTER... [ARGUMENT]... [OPTION]... [NAME]...
1650 The second form is for when old options are being used.
1652 You can use `tar' to store files in an archive, to extract them from
1653 an archive, and to do other types of archive manipulation. The primary
1654 argument to `tar', which is called the "operation", specifies which
1655 action to take. The other arguments to `tar' are either "options",
1656 which change the way `tar' performs an operation, or file names or
1657 archive members, which specify the files or members `tar' is to act on.
1659 You can actually type in arguments in any order, even if in this
1660 manual the options always precede the other arguments, to make examples
1661 easier to understand. Further, the option stating the main operation
1662 mode (the `tar' main command) is usually given first.
1664 Each NAME in the synopsis above is interpreted as an archive member
1665 name when the main command is one of `--compare' (`--diff', `-d'),
1666 `--delete', `--extract' (`--get', `-x'), `--list' (`-t') or `--update'
1667 (`-u'). When naming archive members, you must give the exact name of
1668 the member in the archive, as it is printed by `--list'. For
1669 `--append' (`-r') and `--create' (`-c'), these NAME arguments specify
1670 the names of either files or directory hierarchies to place in the
1671 archive. These files or hierarchies should already exist in the file
1672 system, prior to the execution of the `tar' command.
1674 `tar' interprets relative file names as being relative to the
1675 working directory. `tar' will make all file names relative (by
1676 removing leading slashes when archiving or restoring files), unless you
1677 specify otherwise (using the `--absolute-names' option). *Note
1678 absolute::, for more information about `--absolute-names'.
1680 If you give the name of a directory as either a file name or a member
1681 name, then `tar' acts recursively on all the files and directories
1682 beneath that directory. For example, the name `/' identifies all the
1683 files in the file system to `tar'.
1685 The distinction between file names and archive member names is
1686 especially important when shell globbing is used, and sometimes a
1687 source of confusion for newcomers. *Note wildcards::, for more
1688 information about globbing. The problem is that shells may only glob
1689 using existing files in the file system. Only `tar' itself may glob on
1690 archive members, so when needed, you must ensure that wildcard
1691 characters reach `tar' without being interpreted by the shell first.
1692 Using a backslash before `*' or `?', or putting the whole argument
1693 between quotes, is usually sufficient for this.
1695 Even if NAMEs are often specified on the command line, they can also
1696 be read from a text file in the file system, using the
1697 `--files-from=FILE-OF-NAMES' (`-T FILE-OF-NAMES') option.
1699 If you don't use any file name arguments, `--append' (`-r'),
1700 `--delete' and `--concatenate' (`--catenate', `-A') will do nothing,
1701 while `--create' (`-c') will usually yield a diagnostic and inhibit
1702 `tar' execution. The other operations of `tar' (`--list', `--extract',
1703 `--compare', and `--update') will act on the entire contents of the
1706 Besides successful exits, GNU `tar' may fail for many reasons. Some
1707 reasons correspond to bad usage, that is, when the `tar' command is
1708 improperly written. Errors may be encountered later, while
1709 encountering an error processing the archive or the files. Some errors
1710 are recoverable, in which case the failure is delayed until `tar' has
1711 completed all its work. Some errors are such that it would not
1712 meaningful, or at least risky, to continue processing: `tar' then
1713 aborts processing immediately. All abnormal exits, whether immediate
1714 or delayed, should always be clearly diagnosed on `stderr', after a
1715 line stating the nature of the error.
1717 Possible exit codes of GNU `tar' are summarized in the following
1721 `Successful termination'.
1724 `Some files differ'. If tar was invoked with `--compare'
1725 (`--diff', `-d') command line option, this means that some files
1726 in the archive differ from their disk counterparts (*note
1727 compare::). If tar was given `--create', `--append' or `--update'
1728 option, this exit code means that some files were changed while
1729 being archived and so the resulting archive does not contain the
1730 exact copy of the file set.
1733 `Fatal error'. This means that some fatal, unrecoverable error
1736 If `tar' has invoked a subprocess and that subprocess exited with a
1737 nonzero exit code, `tar' exits with that code as well. This can
1738 happen, for example, if `tar' was given some compression option (*note
1739 gzip::) and the external compressor program failed. Another example is
1740 `rmt' failure during backup to the remote device (*note Remote Tape
1744 File: tar.info, Node: using tar options, Next: Styles, Prev: Synopsis, Up: tar invocation
1746 3.2 Using `tar' Options
1747 =======================
1749 GNU `tar' has a total of eight operating modes which allow you to
1750 perform a variety of tasks. You are required to choose one operating
1751 mode each time you employ the `tar' program by specifying one, and only
1752 one operation as an argument to the `tar' command (two lists of four
1753 operations each may be found at *note frequent operations:: and *note
1754 Operations::). Depending on circumstances, you may also wish to
1755 customize how the chosen operating mode behaves. For example, you may
1756 wish to change the way the output looks, or the format of the files
1757 that you wish to archive may require you to do something special in
1758 order to make the archive look right.
1760 You can customize and control `tar''s performance by running `tar'
1761 with one or more options (such as `--verbose' (`-v'), which we used in
1762 the tutorial). As we said in the tutorial, "options" are arguments to
1763 `tar' which are (as their name suggests) optional. Depending on the
1764 operating mode, you may specify one or more options. Different options
1765 will have different effects, but in general they all change details of
1766 the operation, such as archive format, archive name, or level of user
1767 interaction. Some options make sense with all operating modes, while
1768 others are meaningful only with particular modes. You will likely use
1769 some options frequently, while you will only use others infrequently, or
1770 not at all. (A full list of options is available in *note All
1773 The `TAR_OPTIONS' environment variable specifies default options to
1774 be placed in front of any explicit options. For example, if
1775 `TAR_OPTIONS' is `-v --unlink-first', `tar' behaves as if the two
1776 options `-v' and `--unlink-first' had been specified before any
1777 explicit options. Option specifications are separated by whitespace.
1778 A backslash escapes the next character, so it can be used to specify an
1779 option containing whitespace or a backslash.
1781 Note that `tar' options are case sensitive. For example, the
1782 options `-T' and `-t' are different; the first requires an argument for
1783 stating the name of a file providing a list of NAMEs, while the second
1784 does not require an argument and is another way to write `--list'
1787 In addition to the eight operations, there are many options to
1788 `tar', and three different styles for writing both: long (mnemonic)
1789 form, short form, and old style. These styles are discussed below.
1790 Both the options and the operations can be written in any of these three
1794 File: tar.info, Node: Styles, Next: All Options, Prev: using tar options, Up: tar invocation
1796 3.3 The Three Option Styles
1797 ===========================
1799 There are three styles for writing operations and options to the command
1800 line invoking `tar'. The different styles were developed at different
1801 times during the history of `tar'. These styles will be presented
1802 below, from the most recent to the oldest.
1804 Some options must take an argument. (For example, `--file' (`-f'))
1805 takes the name of an archive file as an argument. If you do not supply
1806 an archive file name, `tar' will use a default, but this can be
1807 confusing; thus, we recommend that you always supply a specific archive
1808 file name.) Where you _place_ the arguments generally depends on which
1809 style of options you choose. We will detail specific information
1810 relevant to each option style in the sections on the different option
1811 styles, below. The differences are subtle, yet can often be very
1812 important; incorrect option placement can cause you to overwrite a
1813 number of important files. We urge you to note these differences, and
1814 only use the option style(s) which makes the most sense to you until
1815 you feel comfortable with the others.
1817 Some options _may_ take an argument. Such options may have at most
1818 long and short forms, they do not have old style equivalent. The rules
1819 for specifying an argument for such options are stricter than those for
1820 specifying mandatory arguments. Please, pay special attention to them.
1824 * Long Options:: Long Option Style
1825 * Short Options:: Short Option Style
1826 * Old Options:: Old Option Style
1827 * Mixing:: Mixing Option Styles
1830 File: tar.info, Node: Long Options, Next: Short Options, Up: Styles
1832 3.3.1 Long Option Style
1833 -----------------------
1835 Each option has at least one "long" (or "mnemonic") name starting with
1836 two dashes in a row, e.g., `--list'. The long names are more clear than
1837 their corresponding short or old names. It sometimes happens that a
1838 single long option has many different names which are synonymous, such
1839 as `--compare' and `--diff'. In addition, long option names can be
1840 given unique abbreviations. For example, `--cre' can be used in place
1841 of `--create' because there is no other long option which begins with
1842 `cre'. (One way to find this out is by trying it and seeing what
1843 happens; if a particular abbreviation could represent more than one
1844 option, `tar' will tell you that that abbreviation is ambiguous and
1845 you'll know that that abbreviation won't work. You may also choose to
1846 run `tar --help' to see a list of options. Be aware that if you run
1847 `tar' with a unique abbreviation for the long name of an option you
1848 didn't want to use, you are stuck; `tar' will perform the command as
1851 Long options are meant to be obvious and easy to remember, and their
1852 meanings are generally easier to discern than those of their
1853 corresponding short options (see below). For example:
1855 $ tar --create --verbose --blocking-factor=20 --file=/dev/rmt0
1857 gives a fairly good set of hints about what the command does, even for
1858 those not fully acquainted with `tar'.
1860 Long options which require arguments take those arguments
1861 immediately following the option name. There are two ways of
1862 specifying a mandatory argument. It can be separated from the option
1863 name either by an equal sign, or by any amount of white space
1864 characters. For example, the `--file' option (which tells the name of
1865 the `tar' archive) is given a file such as `archive.tar' as argument by
1866 using any of the following notations: `--file=archive.tar' or `--file
1869 In contrast, optional arguments must always be introduced using an
1870 equal sign. For example, the `--backup' option takes an optional
1871 argument specifying backup type. It must be used as
1872 `--backup=BACKUP-TYPE'.
1875 File: tar.info, Node: Short Options, Next: Old Options, Prev: Long Options, Up: Styles
1877 3.3.2 Short Option Style
1878 ------------------------
1880 Most options also have a "short option" name. Short options start with
1881 a single dash, and are followed by a single character, e.g., `-t'
1882 (which is equivalent to `--list'). The forms are absolutely identical
1883 in function; they are interchangeable.
1885 The short option names are faster to type than long option names.
1887 Short options which require arguments take their arguments
1888 immediately following the option, usually separated by white space. It
1889 is also possible to stick the argument right after the short option
1890 name, using no intervening space. For example, you might write
1891 `-f archive.tar' or `-farchive.tar' instead of using
1892 `--file=archive.tar'. Both `--file=ARCHIVE-NAME' and `-f ARCHIVE-NAME'
1893 denote the option which indicates a specific archive, here named
1896 Short options which take optional arguments take their arguments
1897 immediately following the option letter, _without any intervening white
1900 Short options' letters may be clumped together, but you are not
1901 required to do this (as compared to old options; see below). When
1902 short options are clumped as a set, use one (single) dash for them all,
1903 e.g., ``tar' -cvf'. Only the last option in such a set is allowed to
1904 have an argument(1).
1906 When the options are separated, the argument for each option which
1907 requires an argument directly follows that option, as is usual for Unix
1908 programs. For example:
1910 $ tar -c -v -b 20 -f /dev/rmt0
1912 If you reorder short options' locations, be sure to move any
1913 arguments that belong to them. If you do not move the arguments
1914 properly, you may end up overwriting files.
1916 ---------- Footnotes ----------
1918 (1) Clustering many options, the last of which has an argument, is a
1919 rather opaque way to write options. Some wonder if GNU `getopt' should
1920 not even be made helpful enough for considering such usages as invalid.
1923 File: tar.info, Node: Old Options, Next: Mixing, Prev: Short Options, Up: Styles
1925 3.3.3 Old Option Style
1926 ----------------------
1928 _(This message will disappear, once this node revised.)_
1930 Like short options, "old options" are single letters. However, old
1931 options must be written together as a single clumped set, without
1932 spaces separating them or dashes preceding them(1). This set of
1933 letters must be the first to appear on the command line, after the
1934 `tar' program name and some white space; old options cannot appear
1935 anywhere else. The letter of an old option is exactly the same letter
1936 as the corresponding short option. For example, the old option `t' is
1937 the same as the short option `-t', and consequently, the same as the
1938 long option `--list'. So for example, the command `tar cv' specifies
1939 the option `-v' in addition to the operation `-c'.
1941 When options that need arguments are given together with the command,
1942 all the associated arguments follow, in the same order as the options.
1943 Thus, the example given previously could also be written in the old
1946 $ tar cvbf 20 /dev/rmt0
1948 Here, `20' is the argument of `-b' and `/dev/rmt0' is the argument of
1951 On the other hand, this old style syntax makes it difficult to match
1952 option letters with their corresponding arguments, and is often
1953 confusing. In the command `tar cvbf 20 /dev/rmt0', for example, `20'
1954 is the argument for `-b', `/dev/rmt0' is the argument for `-f', and
1955 `-v' does not have a corresponding argument. Even using short options
1956 like in `tar -c -v -b 20 -f /dev/rmt0' is clearer, putting all
1957 arguments next to the option they pertain to.
1959 If you want to reorder the letters in the old option argument, be
1960 sure to reorder any corresponding argument appropriately.
1962 This old way of writing `tar' options can surprise even experienced
1963 users. For example, the two commands:
1965 tar cfz archive.tar.gz file
1966 tar -cfz archive.tar.gz file
1968 are quite different. The first example uses `archive.tar.gz' as the
1969 value for option `f' and recognizes the option `z'. The second
1970 example, however, uses `z' as the value for option `f' -- probably not
1973 Old options are kept for compatibility with old versions of `tar'.
1975 This second example could be corrected in many ways, among which the
1976 following are equivalent:
1978 tar -czf archive.tar.gz file
1979 tar -cf archive.tar.gz -z file
1980 tar cf archive.tar.gz -z file
1982 As far as we know, all `tar' programs, GNU and non-GNU, support old
1983 options. GNU `tar' supports them not only for historical reasons, but
1984 also because many people are used to them. For compatibility with Unix
1985 `tar', the first argument is always treated as containing command and
1986 option letters even if it doesn't start with `-'. Thus, `tar c' is
1987 equivalent to `tar -c': both of them specify the `--create' (`-c')
1988 command to create an archive.
1990 ---------- Footnotes ----------
1992 (1) Beware that if you precede options with a dash, you are
1993 announcing the short option style instead of the old option style;
1994 short options are decoded differently.
1997 File: tar.info, Node: Mixing, Prev: Old Options, Up: Styles
1999 3.3.4 Mixing Option Styles
2000 --------------------------
2002 All three styles may be intermixed in a single `tar' command, so long
2003 as the rules for each style are fully respected(1). Old style options
2004 and either of the modern styles of options may be mixed within a single
2005 `tar' command. However, old style options must be introduced as the
2006 first arguments only, following the rule for old options (old options
2007 must appear directly after the `tar' command and some white space).
2008 Modern options may be given only after all arguments to the old options
2009 have been collected. If this rule is not respected, a modern option
2010 might be falsely interpreted as the value of the argument to one of the
2013 For example, all the following commands are wholly equivalent, and
2014 illustrate the many combinations and orderings of option styles.
2016 tar --create --file=archive.tar
2017 tar --create -f archive.tar
2018 tar --create -farchive.tar
2019 tar --file=archive.tar --create
2020 tar --file=archive.tar -c
2021 tar -c --file=archive.tar
2022 tar -c -f archive.tar
2023 tar -c -farchive.tar
2026 tar -f archive.tar --create
2027 tar -f archive.tar -c
2028 tar -farchive.tar --create
2029 tar -farchive.tar -c
2030 tar c --file=archive.tar
2031 tar c -f archive.tar
2034 tar f archive.tar --create
2035 tar f archive.tar -c
2038 On the other hand, the following commands are _not_ equivalent to
2041 tar -f -c archive.tar
2047 These last examples mean something completely different from what the
2048 user intended (judging based on the example in the previous set which
2049 uses long options, whose intent is therefore very clear). The first
2050 four specify that the `tar' archive would be a file named `-c', `c',
2051 `carchive.tar' or `archive.tarc', respectively. The first two examples
2052 also specify a single non-option, NAME argument having the value
2053 `archive.tar'. The last example contains only old style option letters
2054 (repeating option `c' twice), not all of which are meaningful (eg., `.',
2055 `h', or `i'), with no argument value.
2057 ---------- Footnotes ----------
2059 (1) Before GNU `tar' version 1.11.6, a bug prevented intermixing old
2060 style options with long options in some cases.
2063 File: tar.info, Node: All Options, Next: help, Prev: Styles, Up: tar invocation
2065 3.4 All `tar' Options
2066 =====================
2068 The coming manual sections contain an alphabetical listing of all `tar'
2069 operations and options, with brief descriptions and cross references to
2070 more in-depth explanations in the body of the manual. They also
2071 contain an alphabetically arranged table of the short option forms with
2072 their corresponding long option. You can use this table as a reference
2073 for deciphering `tar' commands in scripts.
2077 * Operation Summary::
2079 * Short Option Summary::
2082 File: tar.info, Node: Operation Summary, Next: Option Summary, Up: All Options
2089 Appends files to the end of the archive. *Note append::.
2093 Same as `--concatenate'. *Note concatenate::.
2097 Compares archive members with their counterparts in the file
2098 system, and reports differences in file size, mode, owner,
2099 modification date and contents. *Note compare::.
2103 Appends other `tar' archives to the end of the archive. *Note
2108 Creates a new `tar' archive. *Note create::.
2111 Deletes members from the archive. Don't try this on a archive on a
2112 tape! *Note delete::.
2116 Same `--compare'. *Note compare::.
2120 Extracts members from the archive into the file system. *Note
2125 Same as `--extract'. *Note extract::.
2129 Lists the members in an archive. *Note list::.
2133 Adds files to the end of the archive, but only if they are newer
2134 than their counterparts already in the archive, or if they do not
2135 already exist in the archive. *Note update::.
2139 File: tar.info, Node: Option Summary, Next: Short Option Summary, Prev: Operation Summary, Up: All Options
2146 Normally when creating an archive, `tar' strips an initial `/'
2147 from member names. This option disables that behavior. *Note
2151 (See `--newer', *note after::)
2154 A pattern must match an initial subsequence of the name's
2155 components. *Note controlling pattern-matching::.
2158 `--atime-preserve=replace'
2159 `--atime-preserve=system'
2160 Attempt to preserve the access time of files when reading them.
2161 This option currently is effective only on files that you own,
2162 unless you have superuser privileges.
2164 `--atime-preserve=replace' remembers the access time of a file
2165 before reading it, and then restores the access time afterwards.
2166 This may cause problems if other programs are reading the file at
2167 the same time, as the times of their accesses will be lost. On
2168 most platforms restoring the access time also requires `tar' to
2169 restore the data modification time too, so this option may also
2170 cause problems if other programs are writing the file at the same
2171 time. (Tar attempts to detect this situation, but cannot do so
2172 reliably due to race conditions.) Worse, on most platforms
2173 restoring the access time also updates the status change time,
2174 which means that this option is incompatible with incremental
2177 `--atime-preserve=system' avoids changing time stamps on files,
2178 without interfering with time stamp updates caused by other
2179 programs, so it works better with incremental backups. However,
2180 it requires a special `O_NOATIME' option from the underlying
2181 operating and file system implementation, and it also requires
2182 that searching directories does not update their access times. As
2183 of this writing (November 2005) this works only with Linux, and
2184 only with Linux kernels 2.6.8 and later. Worse, there is
2185 currently no reliable way to know whether this feature actually
2186 works. Sometimes `tar' knows that it does not work, and if you use
2187 `--atime-preserve=system' then `tar' complains and exits right
2188 away. But other times `tar' might think that the option works
2189 when it actually does not.
2191 Currently `--atime-preserve' with no operand defaults to
2192 `--atime-preserve=replace', but this may change in the future as
2193 support for `--atime-preserve=system' improves.
2195 If your operating system does not support
2196 `--atime-preserve=system', you might be able to preserve access
2197 times reliably by by using the `mount' command. For example, you
2198 can mount the file system read-only, or access the file system via
2199 a read-only loopback mount, or use the `noatime' mount option
2200 available on some systems. However, mounting typically requires
2201 superuser privileges and can be a pain to manage.
2205 During a `--create' operation, enables automatic compressed format
2206 recognition based on the archive suffix. The effect of this
2207 option is cancelled by `--no-auto-compress'. *Note gzip::.
2209 `--backup=BACKUP-TYPE'
2210 Rather than deleting files from the file system, `tar' will back
2211 them up using simple or numbered backups, depending upon
2212 BACKUP-TYPE. *Note backup::.
2216 With this option present, `tar' prints error messages for read
2217 errors with the block number in the archive file. *Note
2220 `--blocking-factor=BLOCKING'
2222 Sets the blocking factor `tar' uses to BLOCKING x 512 bytes per
2223 record. *Note Blocking Factor::.
2227 This option tells `tar' to read or write archives through `bzip2'.
2231 Check device numbers when creating a list of modified files for
2232 incremental archiving. This is the default. *Note device
2233 numbers::, for a detailed description.
2235 `--checkpoint[=NUMBER]'
2236 This option directs `tar' to print periodic checkpoint messages as
2237 it reads through the archive. It is intended for when you want a
2238 visual indication that `tar' is still running, but don't want to
2239 see `--verbose' output. You can also instruct `tar' to execute a
2240 list of actions on each checkpoint, see `--checklist-action'
2241 below. For a detailed description, see *note checkpoints::.
2243 `--checkpoint-action=ACTION'
2244 Instruct `tar' to execute an action upon hitting a breakpoint.
2245 Here we give only a brief outline. *Note checkpoints::, for a
2246 complete description.
2248 The ACTION argument can be one of the following:
2251 Produce an audible bell on the console.
2255 Print a single dot on the standard listing stream.
2258 Display a textual message on the standard error, with the
2259 status and number of the checkpoint. This is the default.
2262 Display STRING on the standard error. Before output, the
2263 string is subject to meta-character expansion.
2266 Execute the given COMMAND.
2269 Wait for TIME seconds.
2272 Output STRING on the current console (`/dev/tty').
2274 Several `--checkpoint-action' options can be specified. The
2275 supplied actions will be executed in order of their appearance in
2278 Using `--checkpoint-action' without `--checkpoint' assumes default
2279 checkpoint frequency of one checkpoint per 10 records.
2283 If this option was given, `tar' will check the number of links
2284 dumped for each processed file. If this number does not match the
2285 total number of hard links for the file, a warning message will be
2293 `tar' will use the `compress' program when reading or writing the
2294 archive. This allows you to directly act on archives while saving
2295 space. *Note gzip::.
2298 (See `--interactive'.) *Note interactive::.
2300 `--delay-directory-restore'
2301 Delay setting modification times and permissions of extracted
2302 directories until the end of extraction. *Note Directory
2303 Modification Times and Permissions::.
2307 When creating a `tar' archive, `tar' will archive the file that a
2308 symbolic link points to, rather than archiving the symlink. *Note
2313 When this option is specified, `tar' will change its current
2314 directory to DIR before performing any operations. When this
2315 option is used during archive creation, it is order sensitive.
2319 When performing operations, `tar' will skip files that match
2320 PATTERN. *Note exclude::.
2322 `--exclude-from=FILE'
2324 Similar to `--exclude', except `tar' will use the list of patterns
2325 in the file FILE. *Note exclude::.
2328 Exclude from dump any directory containing a valid cache directory
2329 tag file, but still dump the directory node and the tag file
2334 `--exclude-caches-under'
2335 Exclude from dump any directory containing a valid cache directory
2336 tag file, but still dump the directory node itself.
2340 `--exclude-caches-all'
2341 Exclude from dump any directory containing a valid cache directory
2342 tag file. *Note exclude::.
2344 `--exclude-tag=FILE'
2345 Exclude from dump any directory containing file named FILE, but
2346 dump the directory node and FILE itself. *Note exclude::.
2348 `--exclude-tag-under=FILE'
2349 Exclude from dump the contents of any directory containing file
2350 named FILE, but dump the directory node itself. *Note exclude::.
2352 `--exclude-tag-all=FILE'
2353 Exclude from dump any directory containing file named FILE. *Note
2357 Exclude from dump directories and files, that are internal for some
2358 widely used version control systems.
2364 `tar' will use the file ARCHIVE as the `tar' archive it performs
2365 operations on, rather than `tar''s compilation dependent default.
2366 *Note file tutorial::.
2370 `tar' will use the contents of FILE as a list of archive members
2371 or files to operate on, in addition to those specified on the
2372 command-line. *Note files::.
2375 Forces `tar' to interpret the file name given to `--file' as a
2376 local file, even if it looks like a remote tape drive name. *Note
2377 local and remote archives::.
2381 Selects output archive format. FORMAT may be one of the following:
2384 Creates an archive that is compatible with Unix V7 `tar'.
2387 Creates an archive that is compatible with GNU `tar' version
2391 Creates archive in GNU tar 1.13 format. Basically it is the
2392 same as `oldgnu' with the only difference in the way it
2393 handles long numeric fields.
2396 Creates a POSIX.1-1988 compatible archive.
2399 Creates a POSIX.1-2001 archive.
2402 *Note Formats::, for a detailed discussion of these formats.
2405 Files added to the `tar' archive will have a group ID of GROUP,
2406 rather than the group from the source file. GROUP is first decoded
2407 as a group symbolic name, but if this interpretation fails, it has
2408 to be a decimal numeric group ID. *Note override::.
2410 Also see the comments for the `--owner=USER' option.
2416 This option tells `tar' to read or write archives through `gzip',
2417 allowing `tar' to directly operate on several kinds of compressed
2418 archives transparently. *Note gzip::.
2420 `--hard-dereference'
2421 When creating an archive, dereference hard links and store the
2422 files they refer to, instead of creating usual hard link members.
2428 `tar' will print out a short message summarizing the operations and
2429 options to `tar' and exit. *Note help::.
2432 Ignore case when matching member or file names with patterns.
2433 *Note controlling pattern-matching::.
2435 `--ignore-command-error'
2436 Ignore exit codes of subprocesses. *Note Writing to an External
2439 `--ignore-failed-read'
2440 Do not exit unsuccessfully merely because an unreadable file was
2441 encountered. *Note Reading::.
2445 With this option, `tar' will ignore zeroed blocks in the archive,
2446 which normally signals EOF. *Note Reading::.
2450 Informs `tar' that it is working with an old GNU-format
2451 incremental backup archive. It is intended primarily for
2452 backwards compatibility only. *Note Incremental Dumps::, for a
2453 detailed discussion of incremental archives.
2456 Send verbose output to FILE instead of to standard output.
2458 `--info-script=SCRIPT-FILE'
2459 `--new-volume-script=SCRIPT-FILE'
2461 When `tar' is performing multi-tape backups, SCRIPT-FILE is run at
2462 the end of each tape. If SCRIPT-FILE exits with nonzero status,
2463 `tar' fails immediately. *Note info-script::, for a detailed
2464 discussion of SCRIPT-FILE.
2469 Specifies that `tar' should ask the user for confirmation before
2470 performing potentially destructive options, such as overwriting
2471 files. *Note interactive::.
2473 `--keep-newer-files'
2474 Do not replace existing files that are newer than their archive
2475 copies when extracting files from an archive.
2479 Do not overwrite existing files when extracting files from an
2480 archive. *Note Keep Old Files::.
2484 When creating an archive, instructs `tar' to write NAME as a name
2485 record in the archive. When extracting or listing archives, `tar'
2486 will only operate on archives that have a label matching the
2487 pattern specified in NAME. *Note Tape Files::.
2489 `--listed-incremental=SNAPSHOT-FILE'
2491 During a `--create' operation, specifies that the archive that
2492 `tar' creates is a new GNU-format incremental backup, using
2493 SNAPSHOT-FILE to determine which files to backup. With other
2494 operations, informs `tar' that the archive is in incremental
2495 format. *Note Incremental Dumps::.
2498 This option tells `tar' to read or write archives through `lzma'.
2502 This option tells `tar' to read or write archives through `lzop'.
2505 `--mode=PERMISSIONS'
2506 When adding files to an archive, `tar' will use PERMISSIONS for
2507 the archive members, rather than the permissions from the files.
2508 PERMISSIONS can be specified either as an octal number or as
2509 symbolic permissions, like with `chmod'. *Note override::.
2512 When adding files to an archive, `tar' will use DATE as the
2513 modification time of members when creating archives, instead of
2514 their actual modification times. The value of DATE can be either
2515 a textual date representation (*note Date input formats::) or a
2516 name of the existing file, starting with `/' or `.'. In the
2517 latter case, the modification time of that file is used. *Note
2522 Informs `tar' that it should create or otherwise operate on a
2523 multi-volume `tar' archive. *Note Using Multiple Tapes::.
2525 `--new-volume-script'
2531 When creating an archive, `tar' will only add files that have
2532 changed since DATE. If DATE begins with `/' or `.', it is taken
2533 to be the name of a file whose data modification time specifies
2534 the date. *Note after::.
2536 `--newer-mtime=DATE'
2537 Like `--newer', but add only files whose contents have changed (as
2538 opposed to just `--newer', which will also back up files for which
2539 any status information has changed). *Note after::.
2542 An exclude pattern can match any subsequence of the name's
2543 components. *Note controlling pattern-matching::.
2545 `--no-auto-compress'
2546 Disables automatic compressed format recognition based on the
2547 archive suffix. *Note --auto-compress::. *Note gzip::.
2550 Do not check device numbers when creating a list of modified files
2551 for incremental archiving. *Note device numbers::, for a detailed
2554 `--no-delay-directory-restore'
2555 Modification times and permissions of extracted directories are
2556 set when all files from this directory have been extracted. This
2557 is the default. *Note Directory Modification Times and
2561 Use case-sensitive matching. *Note controlling pattern-matching::.
2563 `--no-ignore-command-error'
2564 Print warnings about subprocesses that terminated with a nonzero
2565 exit code. *Note Writing to an External Program::.
2568 If the `--null' option was given previously, this option cancels
2569 its effect, so that any following `--files-from' options will
2570 expect their file lists to be newline-terminated.
2572 `--no-overwrite-dir'
2573 Preserve metadata of existing directories when extracting files
2574 from an archive. *Note Overwrite Old Files::.
2576 `--no-quote-chars=STRING'
2577 Remove characters listed in STRING from the list of quoted
2578 characters set by the previous `--quote-chars' option (*note
2582 With this option, `tar' will not recurse into directories. *Note
2587 When extracting an archive, do not attempt to preserve the owner
2588 specified in the `tar' archive. This the default behavior for
2591 `--no-same-permissions'
2592 When extracting an archive, subtract the user's umask from files
2593 from the permissions specified in the archive. This is the
2594 default behavior for ordinary users.
2597 Treat all input file or member names literally, do not interpret
2598 escape sequences. *Note input name quoting::.
2601 Do not use wildcards. *Note controlling pattern-matching::.
2603 `--no-wildcards-match-slash'
2604 Wildcards do not match `/'. *Note controlling pattern-matching::.
2607 When `tar' is using the `--files-from' option, this option
2608 instructs `tar' to expect file names terminated with NUL, so `tar'
2609 can correctly work with file names that contain newlines. *Note
2613 This option will notify `tar' that it should use numeric user and
2614 group IDs when creating a `tar' file, rather than names. *Note
2618 The function of this option depends on the action `tar' is
2619 performing. When extracting files, `-o' is a synonym for
2620 `--no-same-owner', i.e., it prevents `tar' from restoring
2621 ownership of files being extracted.
2623 When creating an archive, it is a synonym for `--old-archive'.
2624 This behavior is for compatibility with previous versions of GNU
2625 `tar', and will be removed in future releases.
2627 *Note Changes::, for more information.
2629 `--occurrence[=NUMBER]'
2630 This option can be used in conjunction with one of the subcommands
2631 `--delete', `--diff', `--extract' or `--list' when a list of files
2632 is given either on the command line or via `-T' option.
2634 This option instructs `tar' to process only the NUMBERth
2635 occurrence of each named file. NUMBER defaults to 1, so
2637 tar -x -f archive.tar --occurrence filename
2639 will extract the first occurrence of the member `filename' from
2640 `archive.tar' and will terminate without scanning to the end of
2644 Synonym for `--format=v7'.
2647 Used when creating an archive. Prevents `tar' from recursing into
2648 directories that are on different file systems from the current
2652 Overwrite existing files and directory metadata when extracting
2653 files from an archive. *Note Overwrite Old Files::.
2656 Overwrite the metadata of existing directories when extracting
2657 files from an archive. *Note Overwrite Old Files::.
2660 Specifies that `tar' should use USER as the owner of members when
2661 creating archives, instead of the user associated with the source
2662 file. USER is first decoded as a user symbolic name, but if this
2663 interpretation fails, it has to be a decimal numeric user ID.
2666 This option does not affect extraction from archives.
2668 `--pax-option=KEYWORD-LIST'
2669 This option is meaningful only with POSIX.1-2001 archives (*note
2670 posix::). It modifies the way `tar' handles the extended header
2671 keywords. KEYWORD-LIST is a comma-separated list of keyword
2672 options. *Note PAX keywords::, for a detailed discussion.
2676 Synonym for `--format=v7'.
2679 Same as `--format=posix'.
2682 Synonymous with specifying both `--preserve-permissions' and
2683 `--same-order'. *Note Setting Access Permissions::.
2686 (See `--same-order'; *note Reading::.)
2688 `--preserve-permissions'
2689 `--same-permissions'
2691 When `tar' is extracting an archive, it normally subtracts the
2692 users' umask from the permissions specified in the archive and uses
2693 that number as the permissions to create the destination file.
2694 Specifying this option instructs `tar' that it should use the
2695 permissions directly from the archive. *Note Setting Access
2698 `--quote-chars=STRING'
2699 Always quote characters from STRING, even if the selected quoting
2700 style would not quote them (*note quoting styles::).
2702 `--quoting-style=STYLE'
2703 Set quoting style to use when printing member and file names
2704 (*note quoting styles::). Valid STYLE values are: `literal',
2705 `shell', `shell-always', `c', `escape', `locale', and `clocale'.
2706 Default quoting style is `escape', unless overridden while
2707 configuring the package.
2709 `--read-full-records'
2711 Specifies that `tar' should reblock its input, for reading from
2712 pipes on systems with buggy implementations. *Note Reading::.
2714 `--record-size=SIZE'
2715 Instructs `tar' to use SIZE bytes per record when accessing the
2716 archive. *Note Blocking Factor::.
2719 With this option, `tar' recurses into directories (default).
2722 `--recursive-unlink'
2723 Remove existing directory hierarchies before extracting
2724 directories of the same name from the archive. *Note Recursive
2728 Directs `tar' to remove the source file from the file system after
2729 appending it to an archive. *Note remove files::.
2732 Disable use of some potentially harmful `tar' options. Currently
2733 this option disables shell invocation from multi-volume menu
2734 (*note Using Multiple Tapes::).
2737 Notifies `tar' that it should use CMD instead of the default
2738 `/usr/libexec/rmt' (*note Remote Tape Server::).
2741 Notifies `tar' that is should use CMD to communicate with remote
2742 devices. *Note Device::.
2747 This option is an optimization for `tar' when running on machines
2748 with small amounts of memory. It informs `tar' that the list of
2749 file arguments has already been sorted to match the order of files
2750 in the archive. *Note Reading::.
2753 When extracting an archive, `tar' will attempt to preserve the
2754 owner specified in the `tar' archive with this option present.
2755 This is the default behavior for the superuser; this option has an
2756 effect only for ordinary users. *Note Attributes::.
2758 `--same-permissions'
2759 (See `--preserve-permissions'; *note Setting Access Permissions::.)
2763 Assume that the archive media supports seeks to arbitrary
2764 locations. Usually `tar' determines automatically whether the
2765 archive can be seeked or not. This option is intended for use in
2766 cases when such recognition fails.
2769 Displays the default options used by `tar' and exits successfully.
2770 This option is intended for use in shell scripts. Here is an
2771 example of what you can see using this option:
2773 $ tar --show-defaults
2774 --format=gnu -f- -b20 --quoting-style=escape \
2775 --rmt-command=/usr/libexec/rmt --rsh-command=/usr/bin/rsh
2777 `--show-omitted-dirs'
2778 Instructs `tar' to mention the directories it is skipping when
2779 operating on a `tar' archive. *Note show-omitted-dirs::.
2781 `--show-transformed-names'
2782 `--show-stored-names'
2783 Display file or member names after applying any transformations
2784 (*note transform::). In particular, when used in conjunction with
2785 one of the archive creation operations it instructs `tar' to list
2786 the member names stored in the archive, as opposed to the actual
2787 file names. *Note listing member and file names::.
2791 Invokes a GNU extension when adding files to an archive that
2792 handles sparse files efficiently. *Note sparse::.
2794 `--sparse-version=VERSION'
2795 Specifies the "format version" to use when archiving sparse files.
2796 Implies `--sparse'. *Note sparse::. For the description of the
2797 supported sparse formats, *Note Sparse Formats::.
2799 `--starting-file=NAME'
2801 This option affects extraction only; `tar' will skip extracting
2802 files in the archive until it finds one that matches NAME. *Note
2805 `--strip-components=NUMBER'
2806 Strip given NUMBER of leading components from file names before
2807 extraction. For example, if archive `archive.tar' contained
2808 `/some/file/name', then running
2810 tar --extract --file archive.tar --strip-components=2
2812 would extract this file to file `name'.
2817 Alters the suffix `tar' uses when backing up files from the default
2818 `~'. *Note backup::.
2822 Specifies the length of tapes that `tar' is writing as being
2823 NUM x 1024 bytes long. *Note Using Multiple Tapes::.
2826 Reads the volume label. If an argument is specified, test whether
2827 it matches the volume label. *Note --test-label option::.
2829 `--to-command=COMMAND'
2830 During extraction `tar' will pipe extracted files to the standard
2831 input of COMMAND. *Note Writing to an External Program::.
2835 During extraction, `tar' will extract files to stdout rather than
2836 to the file system. *Note Writing to Standard Output::.
2839 Displays the total number of bytes transferred when processing an
2840 archive. If an argument is given, these data are displayed on
2841 request, when signal SIGNO is delivered to `tar'. *Note totals::.
2845 Sets the data modification time of extracted files to the
2846 extraction time, rather than the data modification time stored in
2847 the archive. *Note Data Modification Times::.
2849 `--transform=SED-EXPR'
2851 Transform file or member names using `sed' replacement expression
2852 SED-EXPR. For example,
2854 $ tar cf archive.tar --transform 's,^\./,usr/,' .
2856 will add to `archive' files from the current working directory,
2857 replacing initial `./' prefix with `usr/'. For the detailed
2858 discussion, *Note transform::.
2860 To see transformed member names in verbose listings, use
2861 `--show-transformed-names' option (*note show-transformed-names::).
2864 (See `--compress'. *note gzip::)
2867 (See `--gzip'. *note gzip::)
2871 Directs `tar' to remove the corresponding file from the file
2872 system before extracting it from the archive. *Note Unlink
2876 Enable unquoting input file or member names (default). *Note
2877 input name quoting::.
2879 `--use-compress-program=PROG'
2881 Instructs `tar' to access the archive through PROG, which is
2882 presumed to be a compression program of some sort. *Note gzip::.
2885 Display file modification dates in UTC. This option implies
2890 Specifies that `tar' should be more verbose about the operations
2891 it is performing. This option can be specified multiple times for
2892 some operations to increase the amount of information displayed.
2897 Verifies that the archive was correctly written when creating an
2898 archive. *Note verify::.
2901 Print information about the program's name, version, origin and
2902 legal status, all on standard output, and then exit successfully.
2906 Used in conjunction with `--multi-volume'. `tar' will keep track
2907 of which volume of a multi-volume archive it is working in FILE.
2911 Use wildcards when matching member names with patterns. *Note
2912 controlling pattern-matching::.
2914 `--wildcards-match-slash'
2915 Wildcards match `/'. *Note controlling pattern-matching::.
2919 Use `xz' for compressing or decompressing the archives. *Note
2923 ---------- Footnotes ----------
2925 (1) Earlier versions of GNU `tar' understood `-l' as a synonym for
2926 `--one-file-system'. The current semantics, which complies to UNIX98,
2927 was introduced with version 1.15.91. *Note Changes::, for more
2931 File: tar.info, Node: Short Option Summary, Prev: Option Summary, Up: All Options
2933 3.4.3 Short Options Cross Reference
2934 -----------------------------------
2936 Here is an alphabetized list of all of the short option forms, matching
2937 them with the equivalent long option.
2939 Short Option Reference
2940 --------------------------------------------------------------------------
2941 -A *note --concatenate::.
2942 -B *note --read-full-records::.
2943 -C *note --directory::.
2944 -F *note --info-script::.
2945 -G *note --incremental::.
2947 -K *note --starting-file::.
2948 -L *note --tape-length::.
2949 -M *note --multi-volume::.
2951 -O *note --to-stdout::.
2952 -P *note --absolute-names::.
2953 -R *note --block-number::.
2954 -S *note --sparse::.
2955 -T *note --files-from::.
2956 -U *note --unlink-first::.
2958 -W *note --verify::.
2959 -X *note --exclude-from::.
2960 -Z *note --compress::.
2961 -b *note --blocking-factor::.
2962 -c *note --create::.
2963 -d *note --compare::.
2965 -g *note --listed-incremental::.
2966 -h *note --dereference::.
2967 -i *note --ignore-zeros::.
2969 -k *note --keep-old-files::.
2970 -l *note --check-links::.
2972 -o When creating, *note --no-same-owner::, when extracting --
2973 *note --portability::.
2975 The latter usage is deprecated. It is retained for
2976 compatibility with the earlier versions of GNU `tar'. In
2977 future releases `-o' will be equivalent to
2978 `--no-same-owner' only.
2979 -p *note --preserve-permissions::.
2980 -r *note --append::.
2981 -s *note --same-order::.
2983 -u *note --update::.
2984 -v *note --verbose::.
2985 -w *note --interactive::.
2986 -x *note --extract::.
2990 File: tar.info, Node: help, Next: defaults, Prev: All Options, Up: tar invocation
2992 3.5 GNU `tar' documentation
2993 ===========================
2995 Being careful, the first thing is really checking that you are using
2996 GNU `tar', indeed. The `--version' option causes `tar' to print
2997 information about its name, version, origin and legal status, all on
2998 standard output, and then exit successfully. For example,
2999 `tar --version' might print:
3002 Copyright (C) 2008 Free Software Foundation, Inc.
3003 This is free software. You may redistribute copies of it under the terms
3004 of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
3005 There is NO WARRANTY, to the extent permitted by law.
3007 Written by John Gilmore and Jay Fenlason.
3009 The first occurrence of `tar' in the result above is the program name
3010 in the package (for example, `rmt' is another program), while the
3011 second occurrence of `tar' is the name of the package itself,
3012 containing possibly many programs. The package is currently named
3013 `tar', after the name of the main program it contains(1).
3015 Another thing you might want to do is checking the spelling or
3016 meaning of some particular `tar' option, without resorting to this
3017 manual, for once you have carefully read it. GNU `tar' has a short
3018 help feature, triggerable through the `--help' option. By using this
3019 option, `tar' will print a usage message listing all available options
3020 on standard output, then exit successfully, without doing anything else
3021 and ignoring all other options. Even if this is only a brief summary,
3022 it may be several screens long. So, if you are not using some kind of
3023 scrollable window, you might prefer to use something like:
3027 presuming, here, that you like using `less' for a pager. Other popular
3028 pagers are `more' and `pg'. If you know about some KEYWORD which
3029 interests you and do not want to read all the `--help' output, another
3030 common idiom is doing:
3032 tar --help | grep KEYWORD
3034 for getting only the pertinent lines. Notice, however, that some `tar'
3035 options have long description lines and the above command will list
3036 only the first of them.
3038 The exact look of the option summary displayed by `tar --help' is
3039 configurable. *Note Configuring Help Summary::, for a detailed
3042 If you only wish to check the spelling of an option, running `tar
3043 --usage' may be a better choice. This will display a terse list of
3044 `tar' option without accompanying explanations.
3046 The short help output is quite succinct, and you might have to get
3047 back to the full documentation for precise points. If you are reading
3048 this paragraph, you already have the `tar' manual in some form. This
3049 manual is available in a variety of forms from
3050 `http://www.gnu.org/software/tar/manual'. It may be printed out of the
3051 GNU `tar' distribution, provided you have TeX already installed
3052 somewhere, and a laser printer around. Just configure the
3053 distribution, execute the command `make dvi', then print `doc/tar.dvi'
3054 the usual way (contact your local guru to know how). If GNU `tar' has
3055 been conveniently installed at your place, this manual is also
3056 available in interactive, hypertextual form as an Info file. Just call
3057 `info tar' or, if you do not have the `info' program handy, use the
3058 Info reader provided within GNU Emacs, calling `tar' from the main Info
3061 There is currently no `man' page for GNU `tar'. If you observe such
3062 a `man' page on the system you are running, either it does not belong
3063 to GNU `tar', or it has not been produced by GNU. Some package
3064 maintainers convert `tar --help' output to a man page, using
3065 `help2man'. In any case, please bear in mind that the authoritative
3066 source of information about GNU `tar' is this Texinfo documentation.
3068 ---------- Footnotes ----------
3070 (1) There are plans to merge the `cpio' and `tar' packages into a
3071 single one which would be called `paxutils'. So, who knows if, one of
3072 this days, the `--version' would not output `tar (GNU paxutils) 3.2'
3075 File: tar.info, Node: defaults, Next: verbose, Prev: help, Up: tar invocation
3077 3.6 Obtaining GNU `tar' default values
3078 ======================================
3080 GNU `tar' has some predefined defaults that are used when you do not
3081 explicitly specify another values. To obtain a list of such defaults,
3082 use `--show-defaults' option. This will output the values in the form
3083 of `tar' command line options:
3086 --format=gnu -f- -b20 --quoting-style=escape
3087 --rmt-command=/etc/rmt --rsh-command=/usr/bin/rsh
3089 Notice, that this option outputs only one line. The example output
3090 above has been split to fit page boundaries.
3092 The above output shows that this version of GNU `tar' defaults to using
3093 `gnu' archive format (*note Formats::), it uses standard output as the
3094 archive, if no `--file' option has been given (*note file tutorial::),
3095 the default blocking factor is 20 (*note Blocking Factor::). It also
3096 shows the default locations where `tar' will look for `rmt' and `rsh'
3100 File: tar.info, Node: verbose, Next: checkpoints, Prev: defaults, Up: tar invocation
3102 3.7 Checking `tar' progress
3103 ===========================
3105 Typically, `tar' performs most operations without reporting any
3106 information to the user except error messages. When using `tar' with
3107 many options, particularly ones with complicated or
3108 difficult-to-predict behavior, it is possible to make serious mistakes.
3109 `tar' provides several options that make observing `tar' easier. These
3110 options cause `tar' to print information as it progresses in its job,
3111 and you might want to use them just for being more careful about what
3112 is going on, or merely for entertaining yourself. If you have
3113 encountered a problem when operating on an archive, however, you may
3114 need more information than just an error message in order to solve the
3115 problem. The following options can be helpful diagnostic tools.
3117 Normally, the `--list' (`-t') command to list an archive prints just
3118 the file names (one per line) and the other commands are silent. When
3119 used with most operations, the `--verbose' (`-v') option causes `tar'
3120 to print the name of each file or archive member as it is processed.
3121 This and the other options which make `tar' print status information
3122 can be useful in monitoring `tar'.
3124 With `--create' or `--extract', `--verbose' used once just prints
3125 the names of the files or members as they are processed. Using it
3126 twice causes `tar' to print a longer listing (*Note verbose member
3127 listing::, for the description) for each member. Since `--list'
3128 already prints the names of the members, `--verbose' used once with
3129 `--list' causes `tar' to print an `ls -l' type listing of the files in
3130 the archive. The following examples both extract members with long
3133 $ tar --extract --file=archive.tar --verbose --verbose
3134 $ tar xvvf archive.tar
3136 Verbose output appears on the standard output except when an archive
3137 is being written to the standard output, as with `tar --create --file=-
3138 --verbose' (`tar cfv -', or even `tar cv'--if the installer let
3139 standard output be the default archive). In that case `tar' writes
3140 verbose output to the standard error stream.
3142 If `--index-file=FILE' is specified, `tar' sends verbose output to
3143 FILE rather than to standard output or standard error.
3145 The `--totals' option causes `tar' to print on the standard error
3146 the total amount of bytes transferred when processing an archive. When
3147 creating or appending to an archive, this option prints the number of
3148 bytes written to the archive and the average speed at which they have
3151 $ tar -c -f archive.tar --totals /home
3152 Total bytes written: 7924664320 (7.4GiB, 85MiB/s)
3154 When reading an archive, this option displays the number of bytes
3157 $ tar -x -f archive.tar --totals
3158 Total bytes read: 7924664320 (7.4GiB, 95MiB/s)
3160 Finally, when deleting from an archive, the `--totals' option
3161 displays both numbers plus number of bytes removed from the archive:
3163 $ tar --delete -f foo.tar --totals --wildcards '*~'
3164 Total bytes read: 9543680 (9.2MiB, 201MiB/s)
3165 Total bytes written: 3829760 (3.7MiB, 81MiB/s)
3166 Total bytes deleted: 1474048
3168 You can also obtain this information on request. When `--totals' is
3169 used with an argument, this argument is interpreted as a symbolic name
3170 of a signal, upon delivery of which the statistics is to be printed:
3173 Print statistics upon delivery of signal SIGNO. Valid arguments
3174 are: `SIGHUP', `SIGQUIT', `SIGINT', `SIGUSR1' and `SIGUSR2'.
3175 Shortened names without `SIG' prefix are also accepted.
3177 Both forms of `--totals' option can be used simultaneously. Thus,
3178 `tar -x --totals --totals=USR1' instructs `tar' to extract all members
3179 from its default archive and print statistics after finishing the
3180 extraction, as well as when receiving signal `SIGUSR1'.
3182 The `--checkpoint' option prints an occasional message as `tar'
3183 reads or writes the archive. It is designed for those who don't need
3184 the more detailed (and voluminous) output of `--block-number' (`-R'),
3185 but do want visual confirmation that `tar' is actually making forward
3186 progress. By default it prints a message each 10 records read or
3187 written. This can be changed by giving it a numeric argument after an
3190 $ tar -c --checkpoint=1000 /var
3191 tar: Write checkpoint 1000
3192 tar: Write checkpoint 2000
3193 tar: Write checkpoint 3000
3195 This example shows the default checkpoint message used by `tar'. If
3196 you place a dot immediately after the equal sign, it will print a `.'
3197 at each checkpoint(1). For example:
3199 $ tar -c --checkpoint=.1000 /var
3202 The `--checkpoint' option provides a flexible mechanism for
3203 executing arbitrary actions upon hitting checkpoints, see the next
3204 section (*note checkpoints::), for more information on it.
3206 The `--show-omitted-dirs' option, when reading an archive--with
3207 `--list' or `--extract', for example--causes a message to be printed
3208 for each directory in the archive which is skipped. This happens
3209 regardless of the reason for skipping: the directory might not have
3210 been named on the command line (implicitly or explicitly), it might be
3211 excluded by the use of the `--exclude=PATTERN' option, or some other
3214 If `--block-number' (`-R') is used, `tar' prints, along with every
3215 message it would normally produce, the block number within the archive
3216 where the message was triggered. Also, supplementary messages are
3217 triggered when reading blocks full of NULs, or when hitting end of file
3218 on the archive. As of now, if the archive if properly terminated with
3219 a NUL block, the reading of the file may stop before end of file is
3220 met, so the position of end of file will not usually show when
3221 `--block-number' (`-R') is used. Note that GNU `tar' drains the
3222 archive before exiting when reading the archive from a pipe.
3224 This option is especially useful when reading damaged archives, since
3225 it helps pinpoint the damaged sections. It can also be used with
3226 `--list' (`-t') when listing a file-system backup tape, allowing you to
3227 choose among several backup tapes when retrieving a file later, in
3228 favor of the tape where the file appears earliest (closest to the front
3229 of the tape). *Note backup::.
3231 ---------- Footnotes ----------
3233 (1) This is actually a shortcut for `--checkpoint=N
3234 --checkpoint-action=dot'. *Note dot: checkpoints.
3237 File: tar.info, Node: checkpoints, Next: interactive, Prev: verbose, Up: tar invocation
3242 A "checkpoint" is a moment of time before writing Nth record to the
3243 archive (a "write checkpoint"), or before reading Nth record from the
3244 archive (a "read checkpoint"). Checkpoints allow to periodically
3245 execute arbitrary actions.
3247 The checkpoint facility is enabled using the following option:
3250 Schedule checkpoints before writing or reading each Nth record.
3251 The default value for N is 10.
3253 A list of arbitrary "actions" can be executed at each checkpoint.
3254 These actions include: pausing, displaying textual messages, and
3255 executing arbitrary external programs. Actions are defined using the
3256 `--checkpoint-action' option.
3258 `--checkpoint-action=ACTION'
3259 Execute an ACTION at each checkpoint.
3261 The simplest value of ACTION is `echo'. It instructs `tar' to
3262 display the default message on the standard error stream upon arriving
3263 at each checkpoint. The default message is (in POSIX locale) `Write
3264 checkpoint N', for write checkpoints, and `Read checkpoint N', for read
3265 checkpoints. Here, N represents ordinal number of the checkpoint.
3267 In another locales, translated versions of this message are used.
3269 This is the default action, so running:
3271 $ tar -c --checkpoint=1000 --checkpoint-action=echo /var
3275 $ tar -c --checkpoint=1000 /var
3277 The `echo' action also allows to supply a customized message. You
3278 do so by placing an equals sign and the message right after it, e.g.:
3280 --checkpoint-action="echo=Hit %s checkpoint #%u"
3282 The `%s' and `%u' in the above example are "meta-characters". The
3283 `%s' meta-character is replaced with the "type" of the checkpoint:
3284 `write' or `read' (or a corresponding translated version in locales
3285 other than POSIX). The `%u' meta-character is replaced with the
3286 ordinal number of the checkpoint. Thus, the above example could
3287 produce the following output when used with the `--create' option:
3289 tar: Hit write checkpoint #10
3290 tar: Hit write checkpoint #20
3291 tar: Hit write checkpoint #30
3293 Aside from meta-character expansion, the message string is subject to
3294 "unquoting", during which the backslash "escape sequences" are replaced
3295 with their corresponding ASCII characters (*note escape sequences::).
3296 E.g. the following action will produce an audible bell and the message
3297 described above at each checkpoint:
3299 --checkpoint-action='echo=\aHit %s checkpoint #%u'
3301 There is also a special action which produces an audible signal:
3302 `bell'. It is not equivalent to `echo='\a'', because `bell' sends the
3303 bell directly to the console (`/dev/tty'), whereas `echo='\a'' sends it
3304 to the standard error.
3306 The `ttyout=STRING' action outputs STRING to `/dev/tty', so it can
3307 be used even if the standard output is redirected elsewhere. The
3308 STRING is subject to the same modifications as with `echo' action. In
3309 contrast to the latter, `ttyout' does not prepend `tar' executable name
3310 to the string, nor does it output a newline after it. For example, the
3311 following action will print the checkpoint message at the same screen
3312 line, overwriting any previous message:
3314 --checkpoint-action="ttyout=\rHit %s checkpoint #%u"
3316 Another available checkpoint action is `dot' (or `.'). It instructs
3317 `tar' to print a single dot on the standard listing stream, e.g.:
3319 $ tar -c --checkpoint=1000 --checkpoint-action=dot /var
3322 For compatibility with previous GNU `tar' versions, this action can
3323 be abbreviated by placing a dot in front of the checkpoint frequency,
3324 as shown in the previous section.
3326 Yet another action, `sleep', pauses `tar' for a specified amount of
3327 seconds. The following example will stop for 30 seconds at each
3330 $ tar -c --checkpoint=1000 --checkpoint-action=sleep=30
3332 Finally, the `exec' action executes a given external program. For
3335 $ tar -c --checkpoint=1000 --checkpoint-action=exec=/sbin/cpoint
3337 This program is executed using `/bin/sh -c', with no additional
3338 arguments. Its exit code is ignored. It gets a copy of `tar''s
3339 environment plus the following variables:
3342 GNU `tar' version number.
3345 The name of the archive `tar' is processing.
3347 `TAR_BLOCKING_FACTOR'
3348 Current blocking factor (*note Blocking::).
3351 Number of the checkpoint.
3354 A short option describing the operation `tar' is executing. *Note
3355 Operations::, for a complete list of subcommand options.
3358 Format of the archive being processed. *Note Formats::, for a
3359 complete list of archive format names.
3361 Any number of actions can be defined, by supplying several
3362 `--checkpoint-action' options in the command line. For example, the
3363 command below displays two messages, pauses execution for 30 seconds
3364 and executes the `/sbin/cpoint' script:
3366 $ tar -c -f arc.tar \
3367 --checkpoint-action='\aecho=Hit %s checkpoint #%u' \
3368 --checkpoint-action='echo=Sleeping for 30 seconds' \
3369 --checkpoint-action='sleep=30' \
3370 --checkpoint-action='exec=/sbin/cpoint'
3372 This example also illustrates the fact that `--checkpoint-action'
3373 can be used without `--checkpoint'. In this case, the default
3374 checkpoint frequency (at each 10th record) is assumed.
3377 File: tar.info, Node: interactive, Prev: checkpoints, Up: tar invocation
3379 3.9 Asking for Confirmation During Operations
3380 =============================================
3382 Typically, `tar' carries out a command without stopping for further
3383 instructions. In some situations however, you may want to exclude some
3384 files and archive members from the operation (for instance if disk or
3385 storage space is tight). You can do this by excluding certain files
3386 automatically (*note Choosing::), or by performing an operation
3387 interactively, using the `--interactive' (`-w') option. `tar' also
3388 accepts `--confirmation' for this option.
3390 When the `--interactive' (`-w') option is specified, before reading,
3391 writing, or deleting files, `tar' first prints a message for each such
3392 file, telling what operation it intends to take, then asks for
3393 confirmation on the terminal. The actions which require confirmation
3394 include adding a file to the archive, extracting a file from the
3395 archive, deleting a file from the archive, and deleting a file from
3396 disk. To confirm the action, you must type a line of input beginning
3397 with `y'. If your input line begins with anything other than `y',
3398 `tar' skips that file.
3400 If `tar' is reading the archive from the standard input, `tar' opens
3401 the file `/dev/tty' to support the interactive communications.
3403 Verbose output is normally sent to standard output, separate from
3404 other error messages. However, if the archive is produced directly on
3405 standard output, then verbose output is mixed with errors on `stderr'.
3406 Producing the archive on standard output may be used as a way to avoid
3407 using disk space, when the archive is soon to be consumed by another
3408 process reading it, say. Some people felt the need of producing an
3409 archive on stdout, still willing to segregate between verbose output
3410 and error output. A possible approach would be using a named pipe to
3411 receive the archive, and having the consumer process to read from that
3412 named pipe. This has the advantage of letting standard output free to
3413 receive verbose output, all separate from errors.
3416 File: tar.info, Node: operations, Next: Backups, Prev: tar invocation, Up: Top
3418 4 GNU `tar' Operations
3419 **********************
3432 File: tar.info, Node: Basic tar, Next: Advanced tar, Up: operations
3434 4.1 Basic GNU `tar' Operations
3435 ==============================
3437 The basic `tar' operations, `--create' (`-c'), `--list' (`-t') and
3438 `--extract' (`--get', `-x'), are currently presented and described in
3439 the tutorial chapter of this manual. This section provides some
3440 complementary notes for these operations.
3444 Creating an empty archive would have some kind of elegance. One
3445 can initialize an empty archive and later use `--append' (`-r')
3446 for adding all members. Some applications would not welcome
3447 making an exception in the way of adding the first archive member.
3448 On the other hand, many people reported that it is dangerously too
3449 easy for `tar' to destroy a magnetic tape with an empty
3450 archive(1). The two most common errors are:
3452 1. Mistakingly using `create' instead of `extract', when the
3453 intent was to extract the full contents of an archive. This
3454 error is likely: keys `c' and `x' are right next to each
3455 other on the QWERTY keyboard. Instead of being unpacked, the
3456 archive then gets wholly destroyed. When users speak about
3457 "exploding" an archive, they usually mean something else :-).
3459 2. Forgetting the argument to `file', when the intent was to
3460 create an archive with a single file in it. This error is
3461 likely because a tired user can easily add the `f' key to the
3462 cluster of option letters, by the mere force of habit,
3463 without realizing the full consequence of doing so. The
3464 usual consequence is that the single file, which was meant to
3465 be saved, is rather destroyed.
3467 So, recognizing the likelihood and the catastrophic nature of these
3468 errors, GNU `tar' now takes some distance from elegance, and
3469 cowardly refuses to create an archive when `--create' option is
3470 given, there are no arguments besides options, and `--files-from'
3471 (`-T') option is _not_ used. To get around the cautiousness of
3472 GNU `tar' and nevertheless create an archive with nothing in it,
3473 one may still use, as the value for the `--files-from' option, a
3474 file with no names in it, as shown in the following commands:
3476 tar --create --file=empty-archive.tar --files-from=/dev/null
3477 tar cfT empty-archive.tar /dev/null
3482 A socket is stored, within a GNU `tar' archive, as a pipe.
3485 GNU `tar' now shows dates as `1996-08-30', while it used to show
3486 them as `Aug 30 1996'. Preferably, people should get used to ISO
3487 8601 dates. Local American dates should be made available again
3488 with full date localization support, once ready. In the meantime,
3489 programs not being localizable for dates should prefer
3490 international dates, that's really the way to go.
3492 Look up `http://www.cl.cam.ac.uk/~mgk25/iso-time.html' if you are
3493 curious, it contains a detailed explanation of the ISO 8601
3497 ---------- Footnotes ----------
3499 (1) This is well described in `Unix-haters Handbook', by Simson
3500 Garfinkel, Daniel Weise & Steven Strassmann, IDG Books, ISBN
3504 File: tar.info, Node: Advanced tar, Next: create options, Prev: Basic tar, Up: operations
3506 4.2 Advanced GNU `tar' Operations
3507 =================================
3509 Now that you have learned the basics of using GNU `tar', you may want
3510 to learn about further ways in which `tar' can help you.
3512 This chapter presents five, more advanced operations which you
3513 probably won't use on a daily basis, but which serve more specialized
3514 functions. We also explain the different styles of options and why you
3515 might want to use one or another, or a combination of them in your `tar'
3516 commands. Additionally, this chapter includes options which allow you
3517 to define the output from `tar' more carefully, and provide help and
3518 error correction in special circumstances.
3530 File: tar.info, Node: Operations, Next: append, Up: Advanced tar
3532 4.2.1 The Five Advanced `tar' Operations
3533 ----------------------------------------
3535 _(This message will disappear, once this node revised.)_
3537 In the last chapter, you learned about the first three operations to
3538 `tar'. This chapter presents the remaining five operations to `tar':
3539 `--append', `--update', `--concatenate', `--delete', and `--compare'.
3541 You are not likely to use these operations as frequently as those
3542 covered in the last chapter; however, since they perform specialized
3543 functions, they are quite useful when you do need to use them. We will
3544 give examples using the same directory and files that you created in
3545 the last chapter. As you may recall, the directory is called
3546 `practice', the files are `jazz', `blues', `folk', `rock', and the two
3547 archive files you created are `collection.tar' and `music.tar'.
3549 We will also use the archive files `afiles.tar' and `bfiles.tar'.
3550 The archive `afiles.tar' contains the members `apple', `angst', and
3551 `aspic'; `bfiles.tar' contains the members `./birds', `baboon', and
3554 Unless we state otherwise, all practicing you do and examples you
3555 follow in this chapter will take place in the `practice' directory that
3556 you created in the previous chapter; see *note prepare for examples::.
3557 (Below in this section, we will remind you of the state of the examples
3558 where the last chapter left them.)
3560 The five operations that we will cover in this chapter are:
3564 Add new entries to an archive that already exists.
3568 Add more recent copies of archive members to the end of an
3569 archive, if they exist.
3574 Add one or more pre-existing archives to the end of another
3578 Delete items from an archive (does not work on tapes).
3583 Compare archive members to their counterparts in the file system.
3586 File: tar.info, Node: append, Next: update, Prev: Operations, Up: Advanced tar
3588 4.2.2 How to Add Files to Existing Archives: `--append'
3589 -------------------------------------------------------
3591 _(This message will disappear, once this node revised.)_
3593 If you want to add files to an existing archive, you don't need to
3594 create a new archive; you can use `--append' (`-r'). The archive must
3595 already exist in order to use `--append'. (A related operation is the
3596 `--update' operation; you can use this to add newer versions of archive
3597 members to an existing archive. To learn how to do this with
3598 `--update', *note update::.)
3600 If you use `--append' to add a file that has the same name as an
3601 archive member to an archive containing that archive member, then the
3602 old member is not deleted. What does happen, however, is somewhat
3603 complex. `tar' _allows_ you to have infinite number of files with the
3604 same name. Some operations treat these same-named members no
3605 differently than any other set of archive members: for example, if you
3606 view an archive with `--list' (`-t'), you will see all of those members
3607 listed, with their data modification times, owners, etc.
3609 Other operations don't deal with these members as perfectly as you
3610 might prefer; if you were to use `--extract' to extract the archive,
3611 only the most recently added copy of a member with the same name as four
3612 other members would end up in the working directory. This is because
3613 `--extract' extracts an archive in the order the members appeared in
3614 the archive; the most recently archived members will be extracted last.
3615 Additionally, an extracted member will _replace_ a file of the same
3616 name which existed in the directory already, and `tar' will not prompt
3617 you about this(1). Thus, only the most recently archived member will
3618 end up being extracted, as it will replace the one extracted before it,
3621 There exists a special option that allows you to get around this
3622 behavior and extract (or list) only a particular copy of the file.
3623 This is `--occurrence' option. If you run `tar' with this option, it
3624 will extract only the first copy of the file. You may also give this
3625 option an argument specifying the number of copy to be extracted.
3626 Thus, for example if the archive `archive.tar' contained three copies
3627 of file `myfile', then the command
3629 tar --extract --file archive.tar --occurrence=2 myfile
3631 would extract only the second copy. *Note --occurrence: Option
3632 Summary, for the description of `--occurrence' option.
3634 If you want to replace an archive member, use `--delete' to delete
3635 the member you want to remove from the archive, , and then use
3636 `--append' to add the member you want to be in the archive. Note that
3637 you can not change the order of the archive; the most recently added
3638 member will still appear last. In this sense, you cannot truly
3639 "replace" one member with another. (Replacing one member with another
3640 will not work on certain types of media, such as tapes; see *note
3641 delete:: and *note Media::, for more information.)
3645 * appending files:: Appending Files to an Archive
3648 ---------- Footnotes ----------
3650 (1) Unless you give it `--keep-old-files' option, or the disk copy
3651 is newer than the the one in the archive and you invoke `tar' with
3652 `--keep-newer-files' option
3655 File: tar.info, Node: appending files, Next: multiple, Up: append
3657 4.2.2.1 Appending Files to an Archive
3658 .....................................
3660 _(This message will disappear, once this node revised.)_
3662 The simplest way to add a file to an already existing archive is the
3663 `--append' (`-r') operation, which writes specified files into the
3664 archive whether or not they are already among the archived files.
3666 When you use `--append', you _must_ specify file name arguments, as
3667 there is no default. If you specify a file that already exists in the
3668 archive, another copy of the file will be added to the end of the
3669 archive. As with other operations, the member names of the newly added
3670 files will be exactly the same as their names given on the command
3671 line. The `--verbose' (`-v') option will print out the names of the
3672 files as they are written into the archive.
3674 `--append' cannot be performed on some tape drives, unfortunately,
3675 due to deficiencies in the formats those tape drives use. The archive
3676 must be a valid `tar' archive, or else the results of using this
3677 operation will be unpredictable. *Note Media::.
3679 To demonstrate using `--append' to add a file to an archive, create
3680 a file called `rock' in the `practice' directory. Make sure you are in
3681 the `practice' directory. Then, run the following `tar' command to add
3682 `rock' to `collection.tar':
3684 $ tar --append --file=collection.tar rock
3686 If you now use the `--list' (`-t') operation, you will see that `rock'
3687 has been added to the archive:
3689 $ tar --list --file=collection.tar
3690 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
3691 -rw-r--r-- me user 21 1996-09-23 16:44 blues
3692 -rw-r--r-- me user 20 1996-09-23 16:44 folk
3693 -rw-r--r-- me user 20 1996-09-23 16:44 rock
3696 File: tar.info, Node: multiple, Prev: appending files, Up: append
3698 4.2.2.2 Multiple Members with the Same Name
3699 ...........................................
3701 You can use `--append' (`-r') to add copies of files which have been
3702 updated since the archive was created. (However, we do not recommend
3703 doing this since there is another `tar' option called `--update'; *Note
3704 update::, for more information. We describe this use of `--append'
3705 here for the sake of completeness.) When you extract the archive, the
3706 older version will be effectively lost. This works because files are
3707 extracted from an archive in the order in which they were archived.
3708 Thus, when the archive is extracted, a file archived later in time will
3709 replace a file of the same name which was archived earlier, even though
3710 the older version of the file will remain in the archive unless you
3711 delete all versions of the file.
3713 Supposing you change the file `blues' and then append the changed
3714 version to `collection.tar'. As you saw above, the original `blues' is
3715 in the archive `collection.tar'. If you change the file and append the
3716 new version of the file to the archive, there will be two copies in the
3717 archive. When you extract the archive, the older version of the file
3718 will be extracted first, and then replaced by the newer version when it
3721 You can append the new, changed copy of the file `blues' to the
3722 archive in this way:
3724 $ tar --append --verbose --file=collection.tar blues
3727 Because you specified the `--verbose' option, `tar' has printed the
3728 name of the file being appended as it was acted on. Now list the
3729 contents of the archive:
3731 $ tar --list --verbose --file=collection.tar
3732 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
3733 -rw-r--r-- me user 21 1996-09-23 16:44 blues
3734 -rw-r--r-- me user 20 1996-09-23 16:44 folk
3735 -rw-r--r-- me user 20 1996-09-23 16:44 rock
3736 -rw-r--r-- me user 58 1996-10-24 18:30 blues
3738 The newest version of `blues' is now at the end of the archive (note
3739 the different creation dates and file sizes). If you extract the
3740 archive, the older version of the file `blues' will be replaced by the
3741 newer version. You can confirm this by extracting the archive and
3742 running `ls' on the directory.
3744 If you wish to extract the first occurrence of the file `blues' from
3745 the archive, use `--occurrence' option, as shown in the following
3748 $ tar --extract -vv --occurrence --file=collection.tar blues
3749 -rw-r--r-- me user 21 1996-09-23 16:44 blues
3751 *Note Writing::, for more information on `--extract' and *Note
3752 -occurrence: Option Summary, for the description of `--occurrence'
3756 File: tar.info, Node: update, Next: concatenate, Prev: append, Up: Advanced tar
3758 4.2.3 Updating an Archive
3759 -------------------------
3761 _(This message will disappear, once this node revised.)_
3763 In the previous section, you learned how to use `--append' to add a
3764 file to an existing archive. A related operation is `--update' (`-u').
3765 The `--update' operation updates a `tar' archive by comparing the date
3766 of the specified archive members against the date of the file with the
3767 same name. If the file has been modified more recently than the
3768 archive member, then the newer version of the file is added to the
3769 archive (as with `--append').
3771 Unfortunately, you cannot use `--update' with magnetic tape drives.
3772 The operation will fail.
3774 Both `--update' and `--append' work by adding to the end of the
3775 archive. When you extract a file from the archive, only the version
3776 stored last will wind up in the file system, unless you use the
3777 `--backup' option. *Note multiple::, for a detailed discussion.
3784 File: tar.info, Node: how to update, Up: update
3786 4.2.3.1 How to Update an Archive Using `--update'
3787 .................................................
3789 You must use file name arguments with the `--update' (`-u') operation.
3790 If you don't specify any files, `tar' won't act on any files and won't
3791 tell you that it didn't do anything (which may end up confusing you).
3793 To see the `--update' option at work, create a new file,
3794 `classical', in your practice directory, and some extra text to the
3795 file `blues', using any text editor. Then invoke `tar' with the
3796 `update' operation and the `--verbose' (`-v') option specified, using
3797 the names of all the files in the practice directory as file name
3800 $ tar --update -v -f collection.tar blues folk rock classical
3805 Because we have specified verbose mode, `tar' prints out the names of
3806 the files it is working on, which in this case are the names of the
3807 files that needed to be updated. If you run `tar --list' and look at
3808 the archive, you will see `blues' and `classical' at its end. There
3809 will be a total of two versions of the member `blues'; the one at the
3810 end will be newer and larger, since you added text before updating it.
3812 (The reason `tar' does not overwrite the older file when updating it
3813 is because writing to the middle of a section of tape is a difficult
3814 process. Tapes are not designed to go backward. *Note Media::, for
3815 more information about tapes.
3817 `--update' (`-u') is not suitable for performing backups for two
3818 reasons: it does not change directory content entries, and it lengthens
3819 the archive every time it is used. The GNU `tar' options intended
3820 specifically for backups are more efficient. If you need to run
3821 backups, please consult *note Backups::.
3824 File: tar.info, Node: concatenate, Next: delete, Prev: update, Up: Advanced tar
3826 4.2.4 Combining Archives with `--concatenate'
3827 ---------------------------------------------
3829 Sometimes it may be convenient to add a second archive onto the end of
3830 an archive rather than adding individual files to the archive. To add
3831 one or more archives to the end of another archive, you should use the
3832 `--concatenate' (`--catenate', `-A') operation.
3834 To use `--concatenate', give the first archive with `--file' option
3835 and name the rest of archives to be concatenated on the command line.
3836 The members, and their member names, will be copied verbatim from those
3837 archives to the first one. (1) The new, concatenated archive will be
3838 called by the same name as the one given with the `--file' option. As
3839 usual, if you omit `--file', `tar' will use the value of the environment
3840 variable `TAPE', or, if this has not been set, the default archive name.
3842 To demonstrate how `--concatenate' works, create two small archives
3843 called `bluesrock.tar' and `folkjazz.tar', using the relevant files
3846 $ tar -cvf bluesrock.tar blues rock
3849 $ tar -cvf folkjazz.tar folk jazz
3853 If you like, You can run `tar --list' to make sure the archives contain
3854 what they are supposed to:
3856 $ tar -tvf bluesrock.tar
3857 -rw-r--r-- melissa user 105 1997-01-21 19:42 blues
3858 -rw-r--r-- melissa user 33 1997-01-20 15:34 rock
3859 $ tar -tvf jazzfolk.tar
3860 -rw-r--r-- melissa user 20 1996-09-23 16:44 folk
3861 -rw-r--r-- melissa user 65 1997-01-30 14:15 jazz
3863 We can concatenate these two archives with `tar':
3866 $ tar --concatenate --file=bluesrock.tar jazzfolk.tar
3868 If you now list the contents of the `bluesrock.tar', you will see
3869 that now it also contains the archive members of `jazzfolk.tar':
3871 $ tar --list --file=bluesrock.tar
3877 When you use `--concatenate', the source and target archives must
3878 already exist and must have been created using compatible format
3879 parameters. Notice, that `tar' does not check whether the archives it
3880 concatenates have compatible formats, it does not even check if the
3881 files are really tar archives.
3883 Like `--append' (`-r'), this operation cannot be performed on some
3884 tape drives, due to deficiencies in the formats those tape drives use.
3886 It may seem more intuitive to you to want or try to use `cat' to
3887 concatenate two archives instead of using the `--concatenate'
3888 operation; after all, `cat' is the utility for combining files.
3890 However, `tar' archives incorporate an end-of-file marker which must
3891 be removed if the concatenated archives are to be read properly as one
3892 archive. `--concatenate' removes the end-of-archive marker from the
3893 target archive before each new archive is appended. If you use `cat'
3894 to combine the archives, the result will not be a valid `tar' format
3895 archive. If you need to retrieve files from an archive that was added
3896 to using the `cat' utility, use the `--ignore-zeros' (`-i') option.
3897 *Note Ignore Zeros::, for further information on dealing with archives
3898 improperly combined using the `cat' shell utility.
3900 ---------- Footnotes ----------
3902 (1) This can cause multiple members to have the same name, for
3903 information on how this affects reading the archive, *note multiple::.
3906 File: tar.info, Node: delete, Next: compare, Prev: concatenate, Up: Advanced tar
3908 4.2.5 Removing Archive Members Using `--delete'
3909 -----------------------------------------------
3911 _(This message will disappear, once this node revised.)_
3913 You can remove members from an archive by using the `--delete' option.
3914 Specify the name of the archive with `--file' (`-f') and then specify
3915 the names of the members to be deleted; if you list no member names,
3916 nothing will be deleted. The `--verbose' option will cause `tar' to
3917 print the names of the members as they are deleted. As with
3918 `--extract', you must give the exact member names when using `tar
3919 --delete'. `--delete' will remove all versions of the named file from
3920 the archive. The `--delete' operation can run very slowly.
3922 Unlike other operations, `--delete' has no short form.
3924 This operation will rewrite the archive. You can only use
3925 `--delete' on an archive if the archive device allows you to write to
3926 any point on the media, such as a disk; because of this, it does not
3927 work on magnetic tapes. Do not try to delete an archive member from a
3928 magnetic tape; the action will not succeed, and you will be likely to
3929 scramble the archive and damage your tape. There is no safe way
3930 (except by completely re-writing the archive) to delete files from most
3931 kinds of magnetic tape. *Note Media::.
3933 To delete all versions of the file `blues' from the archive
3934 `collection.tar' in the `practice' directory, make sure you are in that
3935 directory, and then,
3937 $ tar --list --file=collection.tar
3942 $ tar --delete --file=collection.tar blues
3943 $ tar --list --file=collection.tar
3949 The `--delete' option has been reported to work properly when `tar'
3950 acts as a filter from `stdin' to `stdout'.
3953 File: tar.info, Node: compare, Prev: delete, Up: Advanced tar
3955 4.2.6 Comparing Archive Members with the File System
3956 ----------------------------------------------------
3958 _(This message will disappear, once this node revised.)_
3960 The `--compare' (`-d'), or `--diff' operation compares specified
3961 archive members against files with the same names, and then reports
3962 differences in file size, mode, owner, modification date and contents.
3963 You should _only_ specify archive member names, not file names. If you
3964 do not name any members, then `tar' will compare the entire archive.
3965 If a file is represented in the archive but does not exist in the file
3966 system, `tar' reports a difference.
3968 You have to specify the record size of the archive when modifying an
3969 archive with a non-default record size.
3971 `tar' ignores files in the file system that do not have
3972 corresponding members in the archive.
3974 The following example compares the archive members `rock', `blues'
3975 and `funk' in the archive `bluesrock.tar' with files of the same name
3976 in the file system. (Note that there is no file, `funk'; `tar' will
3977 report an error message.)
3979 $ tar --compare --file=bluesrock.tar rock blues funk
3982 tar: funk not found in archive
3984 The spirit behind the `--compare' (`--diff', `-d') option is to
3985 check whether the archive represents the current state of files on
3986 disk, more than validating the integrity of the archive media. For
3987 this later goal, *Note verify::.
3990 File: tar.info, Node: create options, Next: extract options, Prev: Advanced tar, Up: operations
3992 4.3 Options Used by `--create'
3993 ==============================
3995 The previous chapter described the basics of how to use `--create'
3996 (`-c') to create an archive from a set of files. *Note create::. This
3997 section described advanced options to be used with `--create'.
4001 * override:: Overriding File Metadata.
4002 * Ignore Failed Read::
4005 File: tar.info, Node: override, Next: Ignore Failed Read, Up: create options
4007 4.3.1 Overriding File Metadata
4008 ------------------------------
4010 As described above, a `tar' archive keeps, for each member it contains,
4011 its "metadata", such as modification time, mode and ownership of the
4012 file. GNU `tar' allows to replace these data with other values when
4013 adding files to the archive. The options described in this section
4014 affect creation of archives of any type. For POSIX archives, see also
4015 *note PAX keywords::, for additional ways of controlling metadata,
4016 stored in the archive.
4018 `--mode=PERMISSIONS'
4019 When adding files to an archive, `tar' will use PERMISSIONS for
4020 the archive members, rather than the permissions from the files.
4021 PERMISSIONS can be specified either as an octal number or as
4022 symbolic permissions, like with `chmod' (*Note Permissions:
4023 (fileutils)File permissions. This reference also has useful
4024 information for those not being overly familiar with the UNIX
4025 permission system). Using latter syntax allows for more
4026 flexibility. For example, the value `a+rw' adds read and write
4027 permissions for everybody, while retaining executable bits on
4028 directories or on any other file already marked as executable:
4030 $ tar -c -f archive.tar --mode='a+rw' .
4033 When adding files to an archive, `tar' will use DATE as the
4034 modification time of members when creating archives, instead of
4035 their actual modification times. The argument DATE can be either
4036 a textual date representation in almost arbitrary format (*note
4037 Date input formats::) or a name of the existing file, starting
4038 with `/' or `.'. In the latter case, the modification time of
4039 that file will be used.
4041 The following example will set the modification date to 00:00:00
4042 UTC, January 1, 1970:
4044 $ tar -c -f archive.tar --mtime='1970-01-01' .
4046 When used with `--verbose' (*note verbose tutorial::) GNU `tar'
4047 will try to convert the specified date back to its textual
4048 representation and compare it with the one given with `--mtime'
4049 options. If the two dates differ, `tar' will print a warning
4050 saying what date it will use. This is to help user ensure he is
4051 using the right date.
4055 $ tar -c -f archive.tar -v --mtime=yesterday .
4056 tar: Option --mtime: Treating date `yesterday' as 2006-06-20
4061 Specifies that `tar' should use USER as the owner of members when
4062 creating archives, instead of the user associated with the source
4063 file. The argument USER can be either an existing user symbolic
4064 name, or a decimal numeric user ID.
4066 There is no value indicating a missing number, and `0' usually
4067 means `root'. Some people like to force `0' as the value to offer
4068 in their distributions for the owner of files, because the `root'
4069 user is anonymous anyway, so that might as well be the owner of
4070 anonymous archives. For example:
4072 $ tar -c -f archive.tar --owner=0 .
4074 $ tar -c -f archive.tar --owner=root .
4077 Files added to the `tar' archive will have a group ID of GROUP,
4078 rather than the group from the source file. The argument GROUP
4079 can be either an existing group symbolic name, or a decimal
4083 File: tar.info, Node: Ignore Failed Read, Prev: override, Up: create options
4085 4.3.2 Ignore Fail Read
4086 ----------------------
4088 `--ignore-failed-read'
4089 Do not exit with nonzero on unreadable files or directories.
4092 File: tar.info, Node: extract options, Next: backup, Prev: create options, Up: operations
4094 4.4 Options Used by `--extract'
4095 ===============================
4097 _(This message will disappear, once this node revised.)_
4099 The previous chapter showed how to use `--extract' to extract an
4100 archive into the file system. Various options cause `tar' to extract
4101 more information than just file contents, such as the owner, the
4102 permissions, the modification date, and so forth. This section
4103 presents options to be used with `--extract' when certain special
4104 considerations arise. You may review the information presented in
4105 *note extract:: for more basic information about the `--extract'
4110 * Reading:: Options to Help Read Archives
4111 * Writing:: Changing How `tar' Writes Files
4112 * Scarce:: Coping with Scarce Resources
4115 File: tar.info, Node: Reading, Next: Writing, Up: extract options
4117 4.4.1 Options to Help Read Archives
4118 -----------------------------------
4120 _(This message will disappear, once this node revised.)_
4122 Normally, `tar' will request data in full record increments from an
4123 archive storage device. If the device cannot return a full record,
4124 `tar' will report an error. However, some devices do not always return
4125 full records, or do not require the last record of an archive to be
4126 padded out to the next record boundary. To keep reading until you
4127 obtain a full record, or to accept an incomplete record if it contains
4128 an end-of-archive marker, specify the `--read-full-records' (`-B')
4129 option in conjunction with the `--extract' or `--list' operations.
4132 The `--read-full-records' (`-B') option is turned on by default when
4133 `tar' reads an archive from standard input, or from a remote machine.
4134 This is because on BSD Unix systems, attempting to read a pipe returns
4135 however much happens to be in the pipe, even if it is less than was
4136 requested. If this option were not enabled, `tar' would fail as soon
4137 as it read an incomplete record from the pipe.
4139 If you're not sure of the blocking factor of an archive, you can
4140 read the archive by specifying `--read-full-records' (`-B') and
4141 `--blocking-factor=512-SIZE' (`-b 512-SIZE'), using a blocking factor
4142 larger than what the archive uses. This lets you avoid having to
4143 determine the blocking factor of an archive. *Note Blocking Factor::.
4147 * read full records::
4151 File: tar.info, Node: read full records, Next: Ignore Zeros, Up: Reading
4153 Reading Full Records
4154 ....................
4156 `--read-full-records'
4159 Use in conjunction with `--extract' (`--get', `-x') to read an
4160 archive which contains incomplete records, or one which has a
4161 blocking factor less than the one specified.
4164 File: tar.info, Node: Ignore Zeros, Prev: read full records, Up: Reading
4166 Ignoring Blocks of Zeros
4167 ........................
4169 Normally, `tar' stops reading when it encounters a block of zeros
4170 between file entries (which usually indicates the end of the archive).
4171 `--ignore-zeros' (`-i') allows `tar' to completely read an archive
4172 which contains a block of zeros before the end (i.e., a damaged
4173 archive, or one that was created by concatenating several archives
4176 The `--ignore-zeros' (`-i') option is turned off by default because
4177 many versions of `tar' write garbage after the end-of-archive entry,
4178 since that part of the media is never supposed to be read. GNU `tar'
4179 does not write after the end of an archive, but seeks to maintain
4180 compatibility among archiving utilities.
4184 To ignore blocks of zeros (i.e., end-of-archive entries) which may
4185 be encountered while reading an archive. Use in conjunction with
4186 `--extract' or `--list'.
4189 File: tar.info, Node: Writing, Next: Scarce, Prev: Reading, Up: extract options
4191 4.4.2 Changing How `tar' Writes Files
4192 -------------------------------------
4194 _(This message will disappear, once this node revised.)_
4198 * Dealing with Old Files::
4199 * Overwrite Old Files::
4201 * Keep Newer Files::
4203 * Recursive Unlink::
4204 * Data Modification Times::
4205 * Setting Access Permissions::
4206 * Directory Modification Times and Permissions::
4207 * Writing to Standard Output::
4208 * Writing to an External Program::
4212 File: tar.info, Node: Dealing with Old Files, Next: Overwrite Old Files, Up: Writing
4214 Options Controlling the Overwriting of Existing Files
4215 .....................................................
4217 When extracting files, if `tar' discovers that the extracted file
4218 already exists, it normally replaces the file by removing it before
4219 extracting it, to prevent confusion in the presence of hard or symbolic
4220 links. (If the existing file is a symbolic link, it is removed, not
4221 followed.) However, if a directory cannot be removed because it is
4222 nonempty, `tar' normally overwrites its metadata (ownership,
4223 permission, etc.). The `--overwrite-dir' option enables this default
4224 behavior. To be more cautious and preserve the metadata of such a
4225 directory, use the `--no-overwrite-dir' option.
4227 To be even more cautious and prevent existing files from being
4228 replaced, use the `--keep-old-files' (`-k') option. It causes `tar' to
4229 refuse to replace or update a file that already exists, i.e., a file
4230 with the same name as an archive member prevents extraction of that
4231 archive member. Instead, it reports an error.
4233 To be more aggressive about altering existing files, use the
4234 `--overwrite' option. It causes `tar' to overwrite existing files and
4235 to follow existing symbolic links when extracting.
4237 Some people argue that GNU `tar' should not hesitate to overwrite
4238 files with other files when extracting. When extracting a `tar'
4239 archive, they expect to see a faithful copy of the state of the file
4240 system when the archive was created. It is debatable that this would
4241 always be a proper behavior. For example, suppose one has an archive
4242 in which `usr/local' is a link to `usr/local2'. Since then, maybe the
4243 site removed the link and renamed the whole hierarchy from
4244 `/usr/local2' to `/usr/local'. Such things happen all the time. I
4245 guess it would not be welcome at all that GNU `tar' removes the whole
4246 hierarchy just to make room for the link to be reinstated (unless it
4247 _also_ simultaneously restores the full `/usr/local2', of course!) GNU
4248 `tar' is indeed able to remove a whole hierarchy to reestablish a
4249 symbolic link, for example, but _only if_ `--recursive-unlink' is
4250 specified to allow this behavior. In any case, single files are
4253 Finally, the `--unlink-first' (`-U') option can improve performance
4254 in some cases by causing `tar' to remove files unconditionally before
4258 File: tar.info, Node: Overwrite Old Files, Next: Keep Old Files, Prev: Dealing with Old Files, Up: Writing
4264 Overwrite existing files and directory metadata when extracting
4265 files from an archive.
4267 This causes `tar' to write extracted files into the file system
4268 without regard to the files already on the system; i.e., files
4269 with the same names as archive members are overwritten when the
4270 archive is extracted. It also causes `tar' to extract the
4271 ownership, permissions, and time stamps onto any preexisting files
4272 or directories. If the name of a corresponding file name is a
4273 symbolic link, the file pointed to by the symbolic link will be
4274 overwritten instead of the symbolic link itself (if this is
4275 possible). Moreover, special devices, empty directories and even
4276 symbolic links are automatically removed if they are in the way of
4279 Be careful when using the `--overwrite' option, particularly when
4280 combined with the `--absolute-names' (`-P') option, as this
4281 combination can change the contents, ownership or permissions of
4282 any file on your system. Also, many systems do not take kindly to
4283 overwriting files that are currently being executed.
4286 Overwrite the metadata of directories when extracting files from an
4287 archive, but remove other files before extracting.
4290 File: tar.info, Node: Keep Old Files, Next: Keep Newer Files, Prev: Overwrite Old Files, Up: Writing
4297 Do not replace existing files from archive. The
4298 `--keep-old-files' (`-k') option prevents `tar' from replacing
4299 existing files with files with the same name from the archive. The
4300 `--keep-old-files' option is meaningless with `--list' (`-t').
4301 Prevents `tar' from replacing files in the file system during
4305 File: tar.info, Node: Keep Newer Files, Next: Unlink First, Prev: Keep Old Files, Up: Writing
4310 `--keep-newer-files'
4311 Do not replace existing files that are newer than their archive
4312 copies. This option is meaningless with `--list' (`-t').
4315 File: tar.info, Node: Unlink First, Next: Recursive Unlink, Prev: Keep Newer Files, Up: Writing
4322 Remove files before extracting over them. This can make `tar' run
4323 a bit faster if you know in advance that the extracted files all
4324 need to be removed. Normally this option slows `tar' down
4325 slightly, so it is disabled by default.
4328 File: tar.info, Node: Recursive Unlink, Next: Data Modification Times, Prev: Unlink First, Up: Writing
4333 `--recursive-unlink'
4334 When this option is specified, try removing files and directory
4335 hierarchies before extracting over them. _This is a dangerous
4338 If you specify the `--recursive-unlink' option, `tar' removes
4339 _anything_ that keeps you from extracting a file as far as current
4340 permissions will allow it. This could include removal of the contents
4341 of a full directory hierarchy.
4344 File: tar.info, Node: Data Modification Times, Next: Setting Access Permissions, Prev: Recursive Unlink, Up: Writing
4346 Setting Data Modification Times
4347 ...............................
4349 Normally, `tar' sets the data modification times of extracted files to
4350 the corresponding times recorded for the files in the archive, but
4351 limits the permissions of extracted files by the current `umask'
4354 To set the data modification times of extracted files to the time
4355 when the files were extracted, use the `--touch' (`-m') option in
4356 conjunction with `--extract' (`--get', `-x').
4360 Sets the data modification time of extracted archive members to
4361 the time they were extracted, not the time recorded for them in
4362 the archive. Use in conjunction with `--extract' (`--get', `-x').
4365 File: tar.info, Node: Setting Access Permissions, Next: Directory Modification Times and Permissions, Prev: Data Modification Times, Up: Writing
4367 Setting Access Permissions
4368 ..........................
4370 To set the modes (access permissions) of extracted files to those
4371 recorded for those files in the archive, use `--same-permissions' in
4372 conjunction with the `--extract' (`--get', `-x') operation.
4374 `--preserve-permissions'
4375 `--same-permissions'
4377 Set modes of extracted archive members to those recorded in the
4378 archive, instead of current umask settings. Use in conjunction
4379 with `--extract' (`--get', `-x').
4382 File: tar.info, Node: Directory Modification Times and Permissions, Next: Writing to Standard Output, Prev: Setting Access Permissions, Up: Writing
4384 Directory Modification Times and Permissions
4385 ............................................
4387 After successfully extracting a file member, GNU `tar' normally
4388 restores its permissions and modification times, as described in the
4389 previous sections. This cannot be done for directories, because after
4390 extracting a directory `tar' will almost certainly extract files into
4391 that directory and this will cause the directory modification time to
4392 be updated. Moreover, restoring that directory permissions may not
4393 permit file creation within it. Thus, restoring directory permissions
4394 and modification times must be delayed at least until all files have
4395 been extracted into that directory. GNU `tar' restores directories
4396 using the following approach.
4398 The extracted directories are created with the mode specified in the
4399 archive, as modified by the umask of the user, which gives sufficient
4400 permissions to allow file creation. The meta-information about the
4401 directory is recorded in the temporary list of directories. When
4402 preparing to extract next archive member, GNU `tar' checks if the
4403 directory prefix of this file contains the remembered directory. If it
4404 does not, the program assumes that all files have been extracted into
4405 that directory, restores its modification time and permissions and
4406 removes its entry from the internal list. This approach allows to
4407 correctly restore directory meta-information in the majority of cases,
4408 while keeping memory requirements sufficiently small. It is based on
4409 the fact, that most `tar' archives use the predefined order of members:
4410 first the directory, then all the files and subdirectories in that
4413 However, this is not always true. The most important exception are
4414 incremental archives (*note Incremental Dumps::). The member order in
4415 an incremental archive is reversed: first all directory members are
4416 stored, followed by other (non-directory) members. So, when extracting
4417 from incremental archives, GNU `tar' alters the above procedure. It
4418 remembers all restored directories, and restores their meta-data only
4419 after the entire archive has been processed. Notice, that you do not
4420 need to specify any special options for that, as GNU `tar'
4421 automatically detects archives in incremental format.
4423 There may be cases, when such processing is required for normal
4424 archives too. Consider the following example:
4426 $ tar --no-recursion -cvf archive \
4427 foo foo/file1 bar bar/file foo/file2
4434 During the normal operation, after encountering `bar' GNU `tar' will
4435 assume that all files from the directory `foo' were already extracted
4436 and will therefore restore its timestamp and permission bits. However,
4437 after extracting `foo/file2' the directory timestamp will be offset
4440 To correctly restore directory meta-information in such cases, use
4441 `delay-directory-restore' command line option:
4443 `--delay-directory-restore'
4444 Delays restoring of the modification times and permissions of
4445 extracted directories until the end of extraction. This way,
4446 correct meta-information is restored even if the archive has
4447 unusual member ordering.
4449 `--no-delay-directory-restore'
4450 Cancel the effect of the previous `--delay-directory-restore'.
4451 Use this option if you have used `--delay-directory-restore' in
4452 `TAR_OPTIONS' variable (*note TAR_OPTIONS::) and wish to
4453 temporarily disable it.
4456 File: tar.info, Node: Writing to Standard Output, Next: Writing to an External Program, Prev: Directory Modification Times and Permissions, Up: Writing
4458 Writing to Standard Output
4459 ..........................
4461 To write the extracted files to the standard output, instead of
4462 creating the files on the file system, use `--to-stdout' (`-O') in
4463 conjunction with `--extract' (`--get', `-x'). This option is useful if
4464 you are extracting files to send them through a pipe, and do not need to
4465 preserve them in the file system. If you extract multiple members,
4466 they appear on standard output concatenated, in the order they are
4467 found in the archive.
4471 Writes files to the standard output. Use only in conjunction with
4472 `--extract' (`--get', `-x'). When this option is used, instead of
4473 creating the files specified, `tar' writes the contents of the
4474 files extracted to its standard output. This may be useful if you
4475 are only extracting the files in order to send them through a
4476 pipe. This option is meaningless with `--list' (`-t').
4478 This can be useful, for example, if you have a tar archive containing
4479 a big file and don't want to store the file on disk before processing
4480 it. You can use a command like this:
4482 tar -xOzf foo.tgz bigfile | process
4484 or even like this if you want to process the concatenation of the
4487 tar -xOzf foo.tgz bigfile1 bigfile2 | process
4489 However, `--to-command' may be more convenient for use with multiple
4490 files. See the next section.
4493 File: tar.info, Node: Writing to an External Program, Next: remove files, Prev: Writing to Standard Output, Up: Writing
4495 Writing to an External Program
4496 ..............................
4498 You can instruct `tar' to send the contents of each extracted file to
4499 the standard input of an external program:
4501 `--to-command=COMMAND'
4502 Extract files and pipe their contents to the standard input of
4503 COMMAND. When this option is used, instead of creating the files
4504 specified, `tar' invokes COMMAND and pipes the contents of the
4505 files to its standard output. COMMAND may contain command line
4506 arguments. The program is executed via `sh -c'. Notice, that
4507 COMMAND is executed once for each regular file extracted.
4508 Non-regular files (directories, etc.) are ignored when this option
4511 The command can obtain the information about the file it processes
4512 from the following environment variables:
4515 Type of the file. It is a single letter with the following meaning:
4524 Currently only regular files are supported.
4527 File mode, an octal number.
4530 The name of the file.
4533 Name of the file as stored in the archive.
4536 Name of the file owner.
4539 Name of the file owner group.
4542 Time of last access. It is a decimal number, representing seconds
4543 since the epoch. If the archive provides times with nanosecond
4544 precision, the nanoseconds are appended to the timestamp after a
4548 Time of last modification.
4551 Time of last status change.
4557 UID of the file owner.
4560 GID of the file owner.
4562 In addition to these variables, `TAR_VERSION' contains the GNU `tar'
4565 If COMMAND exits with a non-0 status, `tar' will print an error
4566 message similar to the following:
4568 tar: 2345: Child returned status 1
4570 Here, `2345' is the PID of the finished process.
4572 If this behavior is not wanted, use `--ignore-command-error':
4574 `--ignore-command-error'
4575 Ignore exit codes of subprocesses. Notice that if the program
4576 exits on signal or otherwise terminates abnormally, the error
4577 message will be printed even if this option is used.
4579 `--no-ignore-command-error'
4580 Cancel the effect of any previous `--ignore-command-error' option.
4581 This option is useful if you have set `--ignore-command-error' in
4582 `TAR_OPTIONS' (*note TAR_OPTIONS::) and wish to temporarily cancel
4586 File: tar.info, Node: remove files, Prev: Writing to an External Program, Up: Writing
4592 Remove files after adding them to the archive.
4595 File: tar.info, Node: Scarce, Prev: Writing, Up: extract options
4597 4.4.3 Coping with Scarce Resources
4598 ----------------------------------
4600 _(This message will disappear, once this node revised.)_
4608 File: tar.info, Node: Starting File, Next: Same Order, Up: Scarce
4613 `--starting-file=NAME'
4615 Starts an operation in the middle of an archive. Use in
4616 conjunction with `--extract' (`--get', `-x') or `--list' (`-t').
4618 If a previous attempt to extract files failed due to lack of disk
4619 space, you can use `--starting-file=NAME' (`-K NAME') to start
4620 extracting only after member NAME of the archive. This assumes, of
4621 course, that there is now free space, or that you are now extracting
4622 into a different file system. (You could also choose to suspend `tar',
4623 remove unnecessary files from the file system, and then restart the
4624 same `tar' operation. In this case, `--starting-file' is not necessary.
4625 *Note Incremental Dumps::, *Note interactive::, and *note exclude::.)
4628 File: tar.info, Node: Same Order, Prev: Starting File, Up: Scarce
4636 To process large lists of file names on machines with small
4637 amounts of memory. Use in conjunction with `--compare' (`--diff',
4638 `-d'), `--list' (`-t') or `--extract' (`--get', `-x').
4640 The `--same-order' (`--preserve-order', `-s') option tells `tar'
4641 that the list of file names to be listed or extracted is sorted in the
4642 same order as the files in the archive. This allows a large list of
4643 names to be used, even on a small machine that would not otherwise be
4644 able to hold all the names in memory at the same time. Such a sorted
4645 list can easily be created by running `tar -t' on the archive and
4648 This option is probably never needed on modern computer systems.
4651 File: tar.info, Node: backup, Next: Applications, Prev: extract options, Up: operations
4656 GNU `tar' offers options for making backups of files before writing new
4657 versions. These options control the details of these backups. They
4658 may apply to the archive itself before it is created or rewritten, as
4659 well as individual extracted members. Other GNU programs (`cp',
4660 `install', `ln', and `mv', for example) offer similar options.
4662 Backup options may prove unexpectedly useful when extracting archives
4663 containing many members having identical name, or when extracting
4664 archives on systems having file name limitations, making different
4665 members appear has having similar names through the side-effect of name
4666 truncation. (This is true only if we have a good scheme for truncated
4667 backup names, which I'm not sure at all: I suspect work is needed in
4668 this area.) When any existing file is backed up before being
4669 overwritten by extraction, then clashing files are automatically be
4670 renamed to be unique, and the true name is kept for only the last file
4671 of a series of clashing files. By using verbose mode, users may track
4672 exactly what happens.
4674 At the detail level, some decisions are still experimental, and may
4675 change in the future, we are waiting comments from our users. So,
4676 please do not learn to depend blindly on the details of the backup
4677 features. For example, currently, directories themselves are never
4678 renamed through using these options, so, extracting a file over a
4679 directory still has good chances to fail. Also, backup options apply
4680 to created archives, not only to extracted members. For created
4681 archives, backups will not be attempted when the archive is a block or
4682 character device, or when it refers to a remote file.
4684 For the sake of simplicity and efficiency, backups are made by
4685 renaming old files prior to creation or extraction, and not by copying.
4686 The original name is restored if the file creation fails. If a failure
4687 occurs after a partial extraction of a file, both the backup and the
4688 partially extracted file are kept.
4691 Back up files that are about to be overwritten or removed.
4692 Without this option, the original versions are destroyed.
4694 Use METHOD to determine the type of backups made. If METHOD is
4695 not specified, use the value of the `VERSION_CONTROL' environment
4696 variable. And if `VERSION_CONTROL' is not set, use the `existing'
4699 This option corresponds to the Emacs variable `version-control';
4700 the same values for METHOD are accepted as in Emacs. This option
4701 also allows more descriptive names. The valid METHODs are:
4705 Always make numbered backups.
4709 Make numbered backups of files that already have them, simple
4710 backups of the others.
4714 Always make simple backups.
4718 Append SUFFIX to each backup file made with `--backup'. If this
4719 option is not specified, the value of the `SIMPLE_BACKUP_SUFFIX'
4720 environment variable is used. And if `SIMPLE_BACKUP_SUFFIX' is not
4721 set, the default is `~', just as in Emacs.
4725 File: tar.info, Node: Applications, Next: looking ahead, Prev: backup, Up: operations
4727 4.6 Notable `tar' Usages
4728 ========================
4730 _(This message will disappear, once this node revised.)_
4732 You can easily use archive files to transport a group of files from one
4733 system to another: put all relevant files into an archive on one
4734 computer system, transfer the archive to another system, and extract
4735 the contents there. The basic transfer medium might be magnetic tape,
4736 Internet FTP, or even electronic mail (though you must encode the
4737 archive with `uuencode' in order to transport it properly by mail).
4738 Both machines do not have to use the same operating system, as long as
4739 they both support the `tar' program.
4741 For example, here is how you might copy a directory's contents from
4742 one disk to another, while preserving the dates, modes, owners and
4743 link-structure of all the files therein. In this case, the transfer
4744 medium is a "pipe", which is one a Unix redirection mechanism:
4746 $ (cd sourcedir; tar -cf - .) | (cd targetdir; tar -xf -)
4748 You can avoid subshells by using `-C' option:
4750 $ tar -C sourcedir -cf - . | tar -C targetdir -xf -
4752 The command also works using short option forms:
4754 $ (cd sourcedir; tar --create --file=- . ) \
4755 | (cd targetdir; tar --extract --file=-)
4757 $ tar --directory sourcedir --create --file=- . ) \
4758 | tar --directory targetdir --extract --file=-
4760 This is one of the easiest methods to transfer a `tar' archive.
4763 File: tar.info, Node: looking ahead, Prev: Applications, Up: operations
4765 4.7 Looking Ahead: The Rest of this Manual
4766 ==========================================
4768 You have now seen how to use all eight of the operations available to
4769 `tar', and a number of the possible options. The next chapter explains
4770 how to choose and change file and archive names, how to use files to
4771 store names of other files which you can then call as arguments to
4772 `tar' (this can help you save time if you expect to archive the same
4773 list of files a number of times), and so forth.
4775 If there are too many files to conveniently list on the command line,
4776 you can list the names in a file, and `tar' will read that file. *Note
4779 There are various ways of causing `tar' to skip over some files, and
4780 not archive them. *Note Choosing::.
4783 File: tar.info, Node: Backups, Next: Choosing, Prev: operations, Up: Top
4785 5 Performing Backups and Restoring Files
4786 ****************************************
4788 _(This message will disappear, once this node revised.)_
4790 GNU `tar' is distributed along with the scripts which the Free Software
4791 Foundation uses for performing backups. There is no corresponding
4792 scripts available yet for doing restoration of files. Even if there is
4793 a good chance those scripts may be satisfying to you, they are not the
4794 only scripts or methods available for doing backups and restore. You
4795 may well create your own, or use more sophisticated packages dedicated
4798 Some users are enthusiastic about `Amanda' (The Advanced Maryland
4799 Automatic Network Disk Archiver), a backup system developed by James da
4800 Silva `jds@cs.umd.edu' and available on many Unix systems. This is
4801 free software, and it is available at these places:
4803 http://www.cs.umd.edu/projects/amanda/amanda.html
4804 ftp://ftp.cs.umd.edu/pub/amanda
4806 This chapter documents both the provided shell scripts and `tar'
4807 options which are more specific to usage as a backup tool.
4809 To "back up" a file system means to create archives that contain all
4810 the files in that file system. Those archives can then be used to
4811 restore any or all of those files (for instance if a disk crashes or a
4812 file is accidentally deleted). File system "backups" are also called
4817 * Full Dumps:: Using `tar' to Perform Full Dumps
4818 * Incremental Dumps:: Using `tar' to Perform Incremental Dumps
4819 * Backup Levels:: Levels of Backups
4820 * Backup Parameters:: Setting Parameters for Backups and Restoration
4821 * Scripted Backups:: Using the Backup Scripts
4822 * Scripted Restoration:: Using the Restore Script
4825 File: tar.info, Node: Full Dumps, Next: Incremental Dumps, Up: Backups
4827 5.1 Using `tar' to Perform Full Dumps
4828 =====================================
4830 _(This message will disappear, once this node revised.)_
4832 Full dumps should only be made when no other people or programs are
4833 modifying files in the file system. If files are modified while `tar'
4834 is making the backup, they may not be stored properly in the archive,
4835 in which case you won't be able to restore them if you have to. (Files
4836 not being modified are written with no trouble, and do not corrupt the
4839 You will want to use the `--label=ARCHIVE-LABEL' (`-V
4840 ARCHIVE-LABEL') option to give the archive a volume label, so you can
4841 tell what this archive is even if the label falls off the tape, or
4844 Unless the file system you are dumping is guaranteed to fit on one
4845 volume, you will need to use the `--multi-volume' (`-M') option. Make
4846 sure you have enough tapes on hand to complete the backup.
4848 If you want to dump each file system separately you will need to use
4849 the `--one-file-system' option to prevent `tar' from crossing file
4850 system boundaries when storing (sub)directories.
4852 The `--incremental' (`-G') (*note Incremental Dumps::) option is not
4853 needed, since this is a complete copy of everything in the file system,
4854 and a full restore from this backup would only be done onto a completely
4857 Unless you are in a hurry, and trust the `tar' program (and your
4858 tapes), it is a good idea to use the `--verify' (`-W') option, to make
4859 sure your files really made it onto the dump properly. This will also
4860 detect cases where the file was modified while (or just after) it was
4861 being archived. Not all media (notably cartridge tapes) are capable of
4862 being verified, unfortunately.
4865 File: tar.info, Node: Incremental Dumps, Next: Backup Levels, Prev: Full Dumps, Up: Backups
4867 5.2 Using `tar' to Perform Incremental Dumps
4868 ============================================
4870 "Incremental backup" is a special form of GNU `tar' archive that stores
4871 additional metadata so that exact state of the file system can be
4872 restored when extracting the archive.
4874 GNU `tar' currently offers two options for handling incremental
4875 backups: `--listed-incremental=SNAPSHOT-FILE' (`-g SNAPSHOT-FILE') and
4876 `--incremental' (`-G').
4878 The option `--listed-incremental' instructs tar to operate on an
4879 incremental archive with additional metadata stored in a standalone
4880 file, called a "snapshot file". The purpose of this file is to help
4881 determine which files have been changed, added or deleted since the
4882 last backup, so that the next incremental backup will contain only
4883 modified files. The name of the snapshot file is given as an argument
4886 `--listed-incremental=FILE'
4888 Handle incremental backups with snapshot data in FILE.
4890 To create an incremental backup, you would use
4891 `--listed-incremental' together with `--create' (*note create::). For
4895 --file=archive.1.tar \
4896 --listed-incremental=/var/log/usr.snar \
4899 This will create in `archive.1.tar' an incremental backup of the
4900 `/usr' file system, storing additional metadata in the file
4901 `/var/log/usr.snar'. If this file does not exist, it will be created.
4902 The created archive will then be a "level 0 backup"; please see the
4903 next section for more on backup levels.
4905 Otherwise, if the file `/var/log/usr.snar' exists, it determines
4906 which files are modified. In this case only these files will be stored
4907 in the archive. Suppose, for example, that after running the above
4908 command, you delete file `/usr/doc/old' and create directory
4909 `/usr/local/db' with the following contents:
4915 Some time later you create another incremental backup. You will
4919 --file=archive.2.tar \
4920 --listed-incremental=/var/log/usr.snar \
4922 tar: usr/local/db: Directory is new
4927 The created archive `archive.2.tar' will contain only these three
4928 members. This archive is called a "level 1 backup". Notice that
4929 `/var/log/usr.snar' will be updated with the new data, so if you plan
4930 to create more `level 1' backups, it is necessary to create a working
4931 copy of the snapshot file before running `tar'. The above example will
4932 then be modified as follows:
4934 $ cp /var/log/usr.snar /var/log/usr.snar-1
4936 --file=archive.2.tar \
4937 --listed-incremental=/var/log/usr.snar-1 \
4940 Incremental dumps depend crucially on time stamps, so the results are
4941 unreliable if you modify a file's time stamps during dumping (e.g.,
4942 with the `--atime-preserve=replace' option), or if you set the clock
4945 Metadata stored in snapshot files include device numbers, which,
4946 obviously are supposed to be a non-volatile values. However, it turns
4947 out that NFS devices have undependable values when an automounter gets
4948 in the picture. This can lead to a great deal of spurious redumping in
4949 incremental dumps, so it is somewhat useless to compare two NFS devices
4950 numbers over time. The solution implemented currently is to considers
4951 all NFS devices as being equal when it comes to comparing directories;
4952 this is fairly gross, but there does not seem to be a better way to go.
4954 Apart from using NFS, there are a number of cases where relying on
4955 device numbers can cause spurious redumping of unmodified files. For
4956 example, this occurs when archiving LVM snapshot volumes. To avoid
4957 this, use `--no-check-device' option:
4960 Do not rely on device numbers when preparing a list of changed
4961 files for an incremental dump.
4964 Use device numbers when preparing a list of changed files for an
4965 incremental dump. This is the default behavior. The purpose of
4966 this option is to undo the effect of the `--no-check-device' if it
4967 was given in `TAR_OPTIONS' environment variable (*note
4970 There is also another way to cope with changing device numbers. It
4971 is described in detail in *note Fixing Snapshot Files::.
4973 Note that incremental archives use `tar' extensions and may not be
4974 readable by non-GNU versions of the `tar' program.
4976 To extract from the incremental dumps, use `--listed-incremental'
4977 together with `--extract' option (*note extracting files::). In this
4978 case, `tar' does not need to access snapshot file, since all the data
4979 necessary for extraction are stored in the archive itself. So, when
4980 extracting, you can give whatever argument to `--listed-incremental',
4981 the usual practice is to use `--listed-incremental=/dev/null'.
4982 Alternatively, you can use `--incremental', which needs no arguments.
4983 In general, `--incremental' (`-G') can be used as a shortcut for
4984 `--listed-incremental' when listing or extracting incremental backups
4985 (for more information, regarding this option, *note incremental-op::).
4987 When extracting from the incremental backup GNU `tar' attempts to
4988 restore the exact state the file system had when the archive was
4989 created. In particular, it will _delete_ those files in the file
4990 system that did not exist in their directories when the archive was
4991 created. If you have created several levels of incremental files, then
4992 in order to restore the exact contents the file system had when the
4993 last level was created, you will need to restore from all backups in
4994 turn. Continuing our example, to restore the state of `/usr' file
4995 system, one would do(1):
4998 --listed-incremental=/dev/null \
4999 --file archive.1.tar
5001 --listed-incremental=/dev/null \
5002 --file archive.2.tar
5004 To list the contents of an incremental archive, use `--list' (*note
5005 list::), as usual. To obtain more information about the archive, use
5006 `--listed-incremental' or `--incremental' combined with two `--verbose'
5009 tar --list --incremental --verbose --verbose archive.tar
5011 This command will print, for each directory in the archive, the list
5012 of files in that directory at the time the archive was created. This
5013 information is put out in a format which is both human-readable and
5014 unambiguous for a program: each file name is printed as
5018 where X is a letter describing the status of the file: `Y' if the file
5019 is present in the archive, `N' if the file is not included in the
5020 archive, or a `D' if the file is a directory (and is included in the
5021 archive). *Note Dumpdir::, for the detailed description of dumpdirs
5022 and status codes. Each such line is terminated by a newline character.
5023 The last line is followed by an additional newline to indicate the end
5026 The option `--incremental' (`-G') gives the same behavior as
5027 `--listed-incremental' when used with `--list' and `--extract' options.
5028 When used with `--create' option, it creates an incremental archive
5029 without creating snapshot file. Thus, it is impossible to create
5030 several levels of incremental backups with `--incremental' option.
5032 ---------- Footnotes ----------
5034 (1) Notice, that since both archives were created without `-P'
5035 option (*note absolute::), these commands should be run from the root
5038 (2) Two `--verbose' options were selected to avoid breaking usual
5039 verbose listing output (`--list --verbose') when using in scripts.
5041 Versions of GNU `tar' up to 1.15.1 used to dump verbatim binary
5042 contents of the DUMPDIR header (with terminating nulls) when
5043 `--incremental' or `--listed-incremental' option was given, no matter
5044 what the verbosity level. This behavior, and, especially, the binary
5045 output it produced were considered inconvenient and were changed in
5049 File: tar.info, Node: Backup Levels, Next: Backup Parameters, Prev: Incremental Dumps, Up: Backups
5051 5.3 Levels of Backups
5052 =====================
5054 An archive containing all the files in the file system is called a
5055 "full backup" or "full dump". You could insure your data by creating a
5056 full dump every day. This strategy, however, would waste a substantial
5057 amount of archive media and user time, as unchanged files are daily
5060 It is more efficient to do a full dump only occasionally. To back up
5061 files between full dumps, you can use "incremental dumps". A "level
5062 one" dump archives all the files that have changed since the last full
5065 A typical dump strategy would be to perform a full dump once a week,
5066 and a level one dump once a day. This means some versions of files
5067 will in fact be archived more than once, but this dump strategy makes
5068 it possible to restore a file system to within one day of accuracy by
5069 only extracting two archives--the last weekly (full) dump and the last
5070 daily (level one) dump. The only information lost would be in files
5071 changed or created since the last daily backup. (Doing dumps more than
5072 once a day is usually not worth the trouble).
5074 GNU `tar' comes with scripts you can use to do full and level-one
5075 (actually, even level-two and so on) dumps. Using scripts (shell
5076 programs) to perform backups and restoration is a convenient and
5077 reliable alternative to typing out file name lists and `tar' commands
5080 Before you use these scripts, you need to edit the file
5081 `backup-specs', which specifies parameters used by the backup scripts
5082 and by the restore script. This file is usually located in
5083 `/etc/backup' directory. *Note Backup Parameters::, for its detailed
5084 description. Once the backup parameters are set, you can perform
5085 backups or restoration by running the appropriate script.
5087 The name of the backup script is `backup'. The name of the restore
5088 script is `restore'. The following sections describe their use in
5091 _Please Note:_ The backup and restoration scripts are designed to be
5092 used together. While it is possible to restore files by hand from an
5093 archive which was created using a backup script, and to create an
5094 archive by hand which could then be extracted using the restore script,
5095 it is easier to use the scripts. *Note Incremental Dumps::, before
5096 making such an attempt.
5099 File: tar.info, Node: Backup Parameters, Next: Scripted Backups, Prev: Backup Levels, Up: Backups
5101 5.4 Setting Parameters for Backups and Restoration
5102 ==================================================
5104 The file `backup-specs' specifies backup parameters for the backup and
5105 restoration scripts provided with `tar'. You must edit `backup-specs'
5106 to fit your system configuration and schedule before using these
5109 Syntactically, `backup-specs' is a shell script, containing mainly
5110 variable assignments. However, any valid shell construct is allowed in
5111 this file. Particularly, you may wish to define functions within that
5112 script (e.g., see `RESTORE_BEGIN' below). For more information about
5113 shell script syntax, please refer to the definition of the Shell
5115 (http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#ta
5116 g_02). See also *note Bash Features: (bashref)Top.
5118 The shell variables controlling behavior of `backup' and `restore'
5119 are described in the following subsections.
5123 * General-Purpose Variables::
5124 * Magnetic Tape Control::
5126 * backup-specs example:: An Example Text of `Backup-specs'
5129 File: tar.info, Node: General-Purpose Variables, Next: Magnetic Tape Control, Up: Backup Parameters
5131 5.4.1 General-Purpose Variables
5132 -------------------------------
5134 -- Backup variable: ADMINISTRATOR
5135 The user name of the backup administrator. `Backup' scripts sends
5136 a backup report to this address.
5138 -- Backup variable: BACKUP_HOUR
5139 The hour at which the backups are done. This can be a number from
5140 0 to 23, or the time specification in form HOURS:MINUTES, or the
5143 This variable is used by `backup'. Its value may be overridden
5144 using `--time' option (*note Scripted Backups::).
5146 -- Backup variable: TAPE_FILE
5147 The device `tar' writes the archive to. If TAPE_FILE is a remote
5148 archive (*note remote-dev::), backup script will suppose that your
5149 `mt' is able to access remote devices. If RSH (*note RSH::) is
5150 set, `--rsh-command' option will be added to invocations of `mt'.
5152 -- Backup variable: BLOCKING
5153 The blocking factor `tar' will use when writing the dump archive.
5154 *Note Blocking Factor::.
5156 -- Backup variable: BACKUP_DIRS
5157 A list of file systems to be dumped (for `backup'), or restored
5158 (for `restore'). You can include any directory name in the list
5159 -- subdirectories on that file system will be included, regardless
5160 of how they may look to other networked machines. Subdirectories
5161 on other file systems will be ignored.
5163 The host name specifies which host to run `tar' on, and should
5164 normally be the host that actually contains the file system.
5165 However, the host machine must have GNU `tar' installed, and must
5166 be able to access the directory containing the backup scripts and
5167 their support files using the same file name that is used on the
5168 machine where the scripts are run (i.e., what `pwd' will print
5169 when in that directory on that machine). If the host that contains
5170 the file system does not have this capability, you can specify
5171 another host as long as it can access the file system through NFS.
5173 If the list of file systems is very long you may wish to put it in
5174 a separate file. This file is usually named `/etc/backup/dirs',
5175 but this name may be overridden in `backup-specs' using `DIRLIST'
5178 -- Backup variable: DIRLIST
5179 The name of the file that contains a list of file systems to backup
5180 or restore. By default it is `/etc/backup/dirs'.
5182 -- Backup variable: BACKUP_FILES
5183 A list of individual files to be dumped (for `backup'), or restored
5184 (for `restore'). These should be accessible from the machine on
5185 which the backup script is run.
5187 If the list of file systems is very long you may wish to store it
5188 in a separate file. This file is usually named
5189 `/etc/backup/files', but this name may be overridden in
5190 `backup-specs' using `FILELIST' variable.
5192 -- Backup variable: FILELIST
5193 The name of the file that contains a list of individual files to
5194 backup or restore. By default it is `/etc/backup/files'.
5196 -- Backup variable: MT
5197 Full file name of `mt' binary.
5199 -- Backup variable: RSH
5200 Full file name of `rsh' binary or its equivalent. You may wish to
5201 set it to `ssh', to improve security. In this case you will have
5202 to use public key authentication.
5204 -- Backup variable: RSH_COMMAND
5205 Full file name of `rsh' binary on remote machines. This will be
5206 passed via `--rsh-command' option to the remote invocation of GNU
5209 -- Backup variable: VOLNO_FILE
5210 Name of temporary file to hold volume numbers. This needs to be
5211 accessible by all the machines which have file systems to be
5214 -- Backup variable: XLIST
5215 Name of "exclude file list". An "exclude file list" is a file
5216 located on the remote machine and containing the list of files to
5217 be excluded from the backup. Exclude file lists are searched in
5218 /etc/tar-backup directory. A common use for exclude file lists is
5219 to exclude files containing security-sensitive information (e.g.,
5220 `/etc/shadow' from backups).
5222 This variable affects only `backup'.
5224 -- Backup variable: SLEEP_TIME
5225 Time to sleep between dumps of any two successive file systems
5227 This variable affects only `backup'.
5229 -- Backup variable: DUMP_REMIND_SCRIPT
5230 Script to be run when it's time to insert a new tape in for the
5231 next volume. Administrators may want to tailor this script for
5232 their site. If this variable isn't set, GNU `tar' will display
5233 its built-in prompt, and will expect confirmation from the
5234 console. For the description of the default prompt, see *note
5235 change volume prompt::.
5238 -- Backup variable: SLEEP_MESSAGE
5239 Message to display on the terminal while waiting for dump time.
5240 Usually this will just be some literal text.
5242 -- Backup variable: TAR
5243 Full file name of the GNU `tar' executable. If this is not set,
5244 backup scripts will search `tar' in the current shell path.
5247 File: tar.info, Node: Magnetic Tape Control, Next: User Hooks, Prev: General-Purpose Variables, Up: Backup Parameters
5249 5.4.2 Magnetic Tape Control
5250 ---------------------------
5252 Backup scripts access tape device using special "hook functions".
5253 These functions take a single argument - the name of the tape device.
5254 Their names are kept in the following variables:
5256 -- Backup variable: MT_BEGIN
5257 The name of "begin" function. This function is called before
5258 accessing the drive. By default it retensions the tape:
5263 mt -f "$1" retension
5266 -- Backup variable: MT_REWIND
5267 The name of "rewind" function. The default definition is as
5277 -- Backup variable: MT_OFFLINE
5278 The name of the function switching the tape off line. By default
5279 it is defined as follows:
5281 MT_OFFLINE=mt_offline
5287 -- Backup variable: MT_STATUS
5288 The name of the function used to obtain the status of the archive
5289 device, including error count. Default definition:
5298 File: tar.info, Node: User Hooks, Next: backup-specs example, Prev: Magnetic Tape Control, Up: Backup Parameters
5303 "User hooks" are shell functions executed before and after each `tar'
5304 invocation. Thus, there are "backup hooks", which are executed before
5305 and after dumping each file system, and "restore hooks", executed
5306 before and after restoring a file system. Each user hook is a shell
5307 function taking four arguments:
5309 -- User Hook Function: hook LEVEL HOST FS FSNAME
5313 Current backup or restore level.
5316 Name or IP address of the host machine being dumped or
5320 Full file name of the file system being dumped or restored.
5323 File system name with directory separators replaced with
5324 colons. This is useful, e.g., for creating unique files.
5326 Following variables keep the names of user hook functions
5328 -- Backup variable: DUMP_BEGIN
5329 Dump begin function. It is executed before dumping the file
5332 -- Backup variable: DUMP_END
5333 Executed after dumping the file system.
5335 -- Backup variable: RESTORE_BEGIN
5336 Executed before restoring the file system.
5338 -- Backup variable: RESTORE_END
5339 Executed after restoring the file system.
5342 File: tar.info, Node: backup-specs example, Prev: User Hooks, Up: Backup Parameters
5344 5.4.4 An Example Text of `Backup-specs'
5345 ---------------------------------------
5347 The following is an example of `backup-specs':
5349 # site-specific parameters for file system backup.
5351 ADMINISTRATOR=friedman
5353 TAPE_FILE=/dev/nrsmt0
5355 # Use `ssh' instead of the less secure `rsh'
5357 RSH_COMMAND=/usr/bin/ssh
5359 # Override MT_STATUS function:
5365 # Disable MT_OFFLINE function
5382 apple-gunkies:/com/mailer/gnu
5383 apple-gunkies:/com/archive/gnu"
5385 BACKUP_FILES="/com/mailer/aliases /com/mailer/league*[a-z]"
5388 File: tar.info, Node: Scripted Backups, Next: Scripted Restoration, Prev: Backup Parameters, Up: Backups
5390 5.5 Using the Backup Scripts
5391 ============================
5393 The syntax for running a backup script is:
5395 backup --level=LEVEL --time=TIME
5397 The `level' option requests the dump level. Thus, to produce a full
5398 dump, specify `--level=0' (this is the default, so `--level' may be
5399 omitted if its value is `0'). (1)
5401 The `--time' option determines when should the backup be run. TIME
5402 may take three forms:
5405 The dump must be run at HH hours MM minutes.
5408 The dump must be run at HH hours
5411 The dump must be run immediately.
5413 You should start a script with a tape or disk mounted. Once you
5414 start a script, it prompts you for new tapes or disks as it needs them.
5415 Media volumes don't have to correspond to archive files -- a
5416 multi-volume archive can be started in the middle of a tape that
5417 already contains the end of another multi-volume archive. The
5418 `restore' script prompts for media by its archive volume, so to avoid
5419 an error message you should keep track of which tape (or disk) contains
5420 which volume of the archive (*note Scripted Restoration::).
5422 The backup scripts write two files on the file system. The first is
5423 a record file in `/etc/tar-backup/', which is used by the scripts to
5424 store and retrieve information about which files were dumped. This
5425 file is not meant to be read by humans, and should not be deleted by
5426 them. *Note Snapshot Files::, for a more detailed explanation of this
5429 The second file is a log file containing the names of the file
5430 systems and files dumped, what time the backup was made, and any error
5431 messages that were generated, as well as how much space was left in the
5432 media volume after the last volume of the archive was written. You
5433 should check this log file after every backup. The file name is
5434 `log-MM-DD-YYYY-level-N', where MM-DD-YYYY represents current date, and
5435 N represents current dump level number.
5437 The script also prints the name of each system being dumped to the
5440 Following is the full list of options accepted by `backup' script:
5444 Do backup level LEVEL (default 0).
5448 Force backup even if today's log file already exists.
5452 Set verbosity level. The higher the level is, the more debugging
5453 information will be output during execution. Default LEVEL is
5454 100, which means the highest debugging level.
5458 Wait till TIME, then do backup.
5462 Display short help message and exit.
5466 Display information about the program's name, version, origin and
5467 legal status, all on standard output, and then exit successfully.
5469 ---------- Footnotes ----------
5471 (1) For backward compatibility, the `backup' will also try to deduce
5472 the requested dump level from the name of the script itself. If the
5473 name consists of a string `level-' followed by a single decimal digit,
5474 that digit is taken as the dump level number. Thus, you may create a
5475 link from `backup' to `level-1' and then run `level-1' whenever you
5476 need to create a level one dump.
5479 File: tar.info, Node: Scripted Restoration, Prev: Scripted Backups, Up: Backups
5481 5.6 Using the Restore Script
5482 ============================
5484 To restore files that were archived using a scripted backup, use the
5485 `restore' script. Its usage is quite straightforward. In the simplest
5486 form, invoke `restore --all', it will then restore all the file systems
5487 and files specified in `backup-specs' (*note BACKUP_DIRS:
5488 General-Purpose Variables.).
5490 You may select the file systems (and/or files) to restore by giving
5491 `restore' list of "patterns" in its command line. For example, running
5495 will restore all file systems on the machine `albert'. A more
5496 complicated example:
5498 restore 'albert:*' '*:/var'
5500 This command will restore all file systems on the machine `albert' as
5501 well as `/var' file system on all machines.
5503 By default `restore' will start restoring files from the lowest
5504 available dump level (usually zero) and will continue through all
5505 available dump levels. There may be situations where such a thorough
5506 restore is not necessary. For example, you may wish to restore only
5507 files from the recent level one backup. To do so, use `--level'
5508 option, as shown in the example below:
5512 The full list of options accepted by `restore' follows:
5516 Restore all file systems and files specified in `backup-specs'
5520 Start restoring from the given backup level, instead of the
5525 Set verbosity level. The higher the level is, the more debugging
5526 information will be output during execution. Default LEVEL is
5527 100, which means the highest debugging level.
5531 Display short help message and exit.
5535 Display information about the program's name, version, origin and
5536 legal status, all on standard output, and then exit successfully.
5538 You should start the restore script with the media containing the
5539 first volume of the archive mounted. The script will prompt for other
5540 volumes as they are needed. If the archive is on tape, you don't need
5541 to rewind the tape to to its beginning--if the tape head is positioned
5542 past the beginning of the archive, the script will rewind the tape as
5543 needed. *Note Tape Positioning::, for a discussion of tape positioning.
5545 *Warning:* The script will delete files from the active file
5546 system if they were not in the file system when the archive was
5549 *Note Incremental Dumps::, for an explanation of how the script makes
5553 File: tar.info, Node: Choosing, Next: Date input formats, Prev: Backups, Up: Top
5555 6 Choosing Files and Names for `tar'
5556 ************************************
5558 _(This message will disappear, once this node revised.)_
5560 Certain options to `tar' enable you to specify a name for your archive.
5561 Other options let you decide which files to include or exclude from the
5562 archive, based on when or whether files were modified, whether the file
5563 names do or don't match specified patterns, or whether files are in
5564 specified directories.
5566 This chapter discusses these options in detail.
5570 * file:: Choosing the Archive's Name
5571 * Selecting Archive Members::
5572 * files:: Reading Names from a File
5573 * exclude:: Excluding Some Files
5574 * wildcards:: Wildcards Patterns and Matching
5575 * quoting styles:: Ways of Quoting Special Characters in Names
5576 * transform:: Modifying File and Member Names
5577 * after:: Operating Only on New Files
5578 * recurse:: Descending into Directories
5579 * one:: Crossing File System Boundaries
5582 File: tar.info, Node: file, Next: Selecting Archive Members, Up: Choosing
5584 6.1 Choosing and Naming Archive Files
5585 =====================================
5587 _(This message will disappear, once this node revised.)_
5589 By default, `tar' uses an archive file name that was compiled when it
5590 was built on the system; usually this name refers to some physical tape
5591 drive on the machine. However, the person who installed `tar' on the
5592 system may not have set the default to a meaningful value as far as
5593 most users are concerned. As a result, you will usually want to tell
5594 `tar' where to find (or create) the archive. The `--file=ARCHIVE-NAME'
5595 (`-f ARCHIVE-NAME') option allows you to either specify or name a file
5596 to use as the archive instead of the default archive file location.
5598 `--file=ARCHIVE-NAME'
5600 Name the archive to create or operate on. Use in conjunction with
5603 For example, in this `tar' command,
5605 $ tar -cvf collection.tar blues folk jazz
5607 `collection.tar' is the name of the archive. It must directly follow
5608 the `-f' option, since whatever directly follows `-f' _will_ end up
5609 naming the archive. If you neglect to specify an archive name, you may
5610 end up overwriting a file in the working directory with the archive you
5611 create since `tar' will use this file's name for the archive name.
5613 An archive can be saved as a file in the file system, sent through a
5614 pipe or over a network, or written to an I/O device such as a tape,
5615 floppy disk, or CD write drive.
5617 If you do not name the archive, `tar' uses the value of the
5618 environment variable `TAPE' as the file name for the archive. If that
5619 is not available, `tar' uses a default, compiled-in archive name,
5620 usually that for tape unit zero (i.e., `/dev/tu00').
5622 If you use `-' as an ARCHIVE-NAME, `tar' reads the archive from
5623 standard input (when listing or extracting files), or writes it to
5624 standard output (when creating an archive). If you use `-' as an
5625 ARCHIVE-NAME when modifying an archive, `tar' reads the original
5626 archive from its standard input and writes the entire new archive to
5627 its standard output.
5629 The following example is a convenient way of copying directory
5630 hierarchy from `sourcedir' to `targetdir'.
5632 $ (cd sourcedir; tar -cf - .) | (cd targetdir; tar -xpf -)
5634 The `-C' option allows to avoid using subshells:
5636 $ tar -C sourcedir -cf - . | tar -C targetdir -xpf -
5638 In both examples above, the leftmost `tar' invocation archives the
5639 contents of `sourcedir' to the standard output, while the rightmost one
5640 reads this archive from its standard input and extracts it. The `-p'
5641 option tells it to restore permissions of the extracted files.
5643 To specify an archive file on a device attached to a remote machine,
5646 --file=HOSTNAME:/DEV/FILE-NAME
5648 `tar' will complete the remote connection, if possible, and prompt you
5649 for a username and password. If you use
5650 `--file=@HOSTNAME:/DEV/FILE-NAME', `tar' will complete the remote
5651 connection, if possible, using your username as the username on the
5654 If the archive file name includes a colon (`:'), then it is assumed
5655 to be a file on another machine. If the archive file is
5656 `USER@HOST:FILE', then FILE is used on the host HOST. The remote host
5657 is accessed using the `rsh' program, with a username of USER. If the
5658 username is omitted (along with the `@' sign), then your user name will
5659 be used. (This is the normal `rsh' behavior.) It is necessary for the
5660 remote machine, in addition to permitting your `rsh' access, to have
5661 the `rmt' program installed (This command is included in the GNU `tar'
5662 distribution and by default is installed under `PREFIX/libexec/rmt',
5663 were PREFIX means your installation prefix). If you need to use a file
5664 whose name includes a colon, then the remote tape drive behavior can be
5665 inhibited by using the `--force-local' option.
5667 When the archive is being created to `/dev/null', GNU `tar' tries to
5668 minimize input and output operations. The Amanda backup system, when
5669 used with GNU `tar', has an initial sizing pass which uses this feature.
5672 File: tar.info, Node: Selecting Archive Members, Next: files, Prev: file, Up: Choosing
5674 6.2 Selecting Archive Members
5675 =============================
5677 "File Name arguments" specify which files in the file system `tar'
5678 operates on, when creating or adding to an archive, or which archive
5679 members `tar' operates on, when reading or deleting from an archive.
5682 To specify file names, you can include them as the last arguments on
5683 the command line, as follows:
5684 tar OPERATION [OPTION1 OPTION2 ...] [FILE NAME-1 FILE NAME-2 ...]
5686 If a file name begins with dash (`-'), precede it with `--add-file'
5687 option to prevent it from being treated as an option.
5689 By default GNU `tar' attempts to "unquote" each file or member name,
5690 replacing "escape sequences" according to the following table:
5692 Escape Replaced with
5693 -----------------------------------------------------------
5694 \a Audible bell (ASCII 7)
5695 \b Backspace (ASCII 8)
5696 \f Form feed (ASCII 12)
5697 \n New line (ASCII 10)
5698 \r Carriage return (ASCII 13)
5699 \t Horizontal tabulation (ASCII 9)
5700 \v Vertical tabulation (ASCII 11)
5702 \N ASCII N (N should be an octal number
5705 A backslash followed by any other symbol is retained.
5707 This default behavior is controlled by the following command line
5711 Enable unquoting input file or member names (default).
5714 Disable unquoting input file or member names.
5716 If you specify a directory name as a file name argument, all the
5717 files in that directory are operated on by `tar'.
5719 If you do not specify files, `tar' behavior differs depending on the
5720 operation mode as described below:
5722 When `tar' is invoked with `--create' (`-c'), `tar' will stop
5723 immediately, reporting the following:
5726 tar: Cowardly refusing to create an empty archive
5727 Try `tar --help' or `tar --usage' for more information.
5729 If you specify either `--list' (`-t') or `--extract' (`--get',
5730 `-x'), `tar' operates on all the archive members in the archive.
5732 If run with `--diff' option, tar will compare the archive with the
5733 contents of the current working directory.
5735 If you specify any other operation, `tar' does nothing.
5737 By default, `tar' takes file names from the command line. However,
5738 there are other ways to specify file or member names, or to modify the
5739 manner in which `tar' selects the files or members upon which to
5740 operate. In general, these methods work both for specifying the names
5741 of files and archive members.
5744 File: tar.info, Node: files, Next: exclude, Prev: Selecting Archive Members, Up: Choosing
5746 6.3 Reading Names from a File
5747 =============================
5749 Instead of giving the names of files or archive members on the command
5750 line, you can put the names into a file, and then use the
5751 `--files-from=FILE-OF-NAMES' (`-T FILE-OF-NAMES') option to `tar'.
5752 Give the name of the file which contains the list of files to include
5753 as the argument to `--files-from'. In the list, the file names should
5754 be separated by newlines. You will frequently use this option when you
5755 have generated the list of files to archive with the `find' utility.
5757 `--files-from=FILE-NAME'
5759 Get names to extract or create from file FILE-NAME.
5761 If you give a single dash as a file name for `--files-from', (i.e.,
5762 you specify either `--files-from=-' or `-T -'), then the file names are
5763 read from standard input.
5765 Unless you are running `tar' with `--create', you can not use both
5766 `--files-from=-' and `--file=-' (`-f -') in the same command.
5768 Any number of `-T' options can be given in the command line.
5770 The following example shows how to use `find' to generate a list of
5771 files smaller than 400K in length and put that list into a file called
5772 `small-files'. You can then use the `-T' option to `tar' to specify
5773 the files from that file, `small-files', to create the archive
5774 `little.tgz'. (The `-z' option to `tar' compresses the archive with
5775 `gzip'; *note gzip:: for more information.)
5777 $ find . -size -400 -print > small-files
5778 $ tar -c -v -z -T small-files -f little.tgz
5780 In the file list given by `-T' option, any file name beginning with `-'
5781 character is considered a `tar' option and is processed accordingly.(1)
5782 For example, the common use of this feature is to change to another
5783 directory by specifying `-C' option:
5791 $ tar -c -f foo.tar --files-from list
5793 In this example, `tar' will first switch to `/etc' directory and add
5794 files `passwd' and `hosts' to the archive. Then it will change to
5795 `/lib' directory and will archive the file `libc.a'. Thus, the
5796 resulting archive `foo.tar' will contain:
5804 Notice that the option parsing algorithm used with `-T' is stricter
5805 than the one used by shell. Namely, when specifying option arguments,
5806 you should observe the following rules:
5808 * When using short (single-letter) option form, its argument must
5809 immediately follow the option letter, without any intervening
5810 whitespace. For example: `-Cdir'.
5812 * When using long option form, the option argument must be separated
5813 from the option by a single equal sign. No whitespace is allowed
5814 on any side of the equal sign. For example: `--directory=dir'.
5816 * For both short and long option forms, the option argument can be
5817 given on the next line after the option name, e.g.:
5827 If you happen to have a file whose name starts with `-', precede it
5828 with `--add-file' option to prevent it from being recognized as an
5829 option. For example: `--add-file=--my-file'.
5835 ---------- Footnotes ----------
5837 (1) Versions of GNU `tar' up to 1.15.1 recognized only `-C' option
5838 in file lists, and only if the option and its argument occupied two
5842 File: tar.info, Node: nul, Up: files
5844 6.3.1 `NUL' Terminated File Names
5845 ---------------------------------
5847 The `--null' option causes `--files-from=FILE-OF-NAMES' (`-T
5848 FILE-OF-NAMES') to read file names terminated by a `NUL' instead of a
5849 newline, so files whose names contain newlines can be archived using
5853 Only consider `NUL' terminated file names, instead of files that
5854 terminate in a newline.
5857 Undo the effect of any previous `--null' option.
5859 The `--null' option is just like the one in GNU `xargs' and `cpio',
5860 and is useful with the `-print0' predicate of GNU `find'. In `tar',
5861 `--null' also disables special handling for file names that begin with
5864 This example shows how to use `find' to generate a list of files
5865 larger than 800K in length and put that list into a file called
5866 `long-files'. The `-print0' option to `find' is just like `-print',
5867 except that it separates files with a `NUL' rather than with a newline.
5868 You can then run `tar' with both the `--null' and `-T' options to
5869 specify that `tar' get the files from that file, `long-files', to
5870 create the archive `big.tgz'. The `--null' option to `tar' will cause
5871 `tar' to recognize the `NUL' separator between files.
5873 $ find . -size +800 -print0 > long-files
5874 $ tar -c -v --null --files-from=long-files --file=big.tar
5876 The `--no-null' option can be used if you need to read both
5877 zero-terminated and newline-terminated files on the same command line.
5878 For example, if `flist' is a newline-terminated file, then the
5879 following command can be used to combine it with the above command:
5881 $ find . -size +800 -print0 |
5882 tar -c -f big.tar --null -T - --no-null -T flist
5884 This example uses short options for typographic reasons, to avoid
5887 GNU `tar' is able to automatically detect null-terminated file
5888 lists, so it is safe to use them even without the `--null' option. In
5889 this case `tar' will print a warning and continue reading such a file
5890 as if `--null' were actually given:
5892 $ find . -size +800 -print0 | tar -c -f big.tar -T -
5893 tar: -: file name read contains nul character
5895 The null terminator, however, remains in effect only for this
5896 particular file, any following `-T' options will assume newline
5897 termination. Of course, the null autodetection applies to these
5898 eventual surplus `-T' options as well.
5901 File: tar.info, Node: exclude, Next: wildcards, Prev: files, Up: Choosing
5903 6.4 Excluding Some Files
5904 ========================
5906 _(This message will disappear, once this node revised.)_
5908 To avoid operating on files whose names match a particular pattern, use
5909 the `--exclude' or `--exclude-from' options.
5912 Causes `tar' to ignore files that match the PATTERN.
5914 The `--exclude=PATTERN' option prevents any file or member whose
5915 name matches the shell wildcard (PATTERN) from being operated on. For
5916 example, to create an archive with all the contents of the directory
5917 `src' except for files whose names end in `.o', use the command `tar
5918 -cf src.tar --exclude='*.o' src'.
5920 You may give multiple `--exclude' options.
5922 `--exclude-from=FILE'
5924 Causes `tar' to ignore files that match the patterns listed in
5927 Use the `--exclude-from' option to read a list of patterns, one per
5928 line, from FILE; `tar' will ignore files matching those patterns. Thus
5929 if `tar' is called as `tar -c -X foo .' and the file `foo' contains a
5930 single line `*.o', no files whose names end in `.o' will be added to
5933 Notice, that lines from FILE are read verbatim. One of the frequent
5934 errors is leaving some extra whitespace after a file name, which is
5935 difficult to catch using text editors.
5937 However, empty lines are OK.
5940 Exclude files and directories used by following version control
5941 systems: `CVS', `RCS', `SCCS', `SVN', `Arch', `Bazaar',
5942 `Mercurial', and `Darcs'.
5944 As of version 1.22, the following files are excluded:
5946 * `CVS/', and everything under it
5948 * `RCS/', and everything under it
5950 * `SCCS/', and everything under it
5952 * `.git/', and everything under it
5958 * `.svn/', and everything under it
5960 * `.arch-ids/', and everything under it
5962 * `{arch}/', and everything under it
5984 When creating an archive, the `--exclude-caches' option family
5985 causes `tar' to exclude all directories that contain a "cache directory
5986 tag". A cache directory tag is a short file with the well-known name
5987 `CACHEDIR.TAG' and having a standard header specified in
5988 `http://www.brynosaurus.com/cachedir/spec.html'. Various applications
5989 write cache directory tags into directories they use to hold
5990 regenerable, non-precious data, so that such data can be more easily
5991 excluded from backups.
5993 There are three `exclude-caches' options, each providing a different
5994 exclusion semantics:
5997 Do not archive the contents of the directory, but archive the
5998 directory itself and the `CACHEDIR.TAG' file.
6000 `--exclude-caches-under'
6001 Do not archive the contents of the directory, nor the
6002 `CACHEDIR.TAG' file, archive only the directory itself.
6004 `--exclude-caches-all'
6005 Omit directories containing `CACHEDIR.TAG' file entirely.
6007 Another option family, `--exclude-tag', provides a generalization of
6008 this concept. It takes a single argument, a file name to look for.
6009 Any directory that contains this file will be excluded from the dump.
6010 Similarly to `exclude-caches', there are three options in this option
6013 `--exclude-tag=FILE'
6014 Do not dump the contents of the directory, but dump the directory
6015 itself and the FILE.
6017 `--exclude-tag-under=FILE'
6018 Do not dump the contents of the directory, nor the FILE, archive
6019 only the directory itself.
6021 `--exclude-tag-all=FILE'
6022 Omit directories containing FILE file entirely.
6024 Multiple `--exclude-tag*' options can be given.
6026 For example, given this directory:
6037 The `--exclude-tag' will produce the following:
6039 $ tar -cf archive.tar --exclude-tag=tagfile -v dir
6044 tar: dir/folk/: contains a cache directory tag tagfile;
6048 Both the `dir/folk' directory and its tagfile are preserved in the
6049 archive, however the rest of files in this directory are not.
6051 Now, using the `--exclude-tag-under' option will exclude `tagfile'
6052 from the dump, while still preserving the directory itself, as shown in
6055 $ tar -cf archive.tar --exclude-tag-under=tagfile -v dir
6060 ./tar: dir/folk/: contains a cache directory tag tagfile;
6063 Finally, using `--exclude-tag-all' omits the `dir/folk' directory
6066 $ tar -cf archive.tar --exclude-tag-all=tagfile -v dir
6070 ./tar: dir/folk/: contains a cache directory tag tagfile;
6071 directory not dumped
6075 * problems with exclude::
6078 File: tar.info, Node: problems with exclude, Up: exclude
6080 Problems with Using the `exclude' Options
6081 -----------------------------------------
6083 Some users find `exclude' options confusing. Here are some common
6086 * The main operating mode of `tar' does not act on a file name
6087 explicitly listed on the command line, if one of its file name
6088 components is excluded. In the example above, if you create an
6089 archive and exclude files that end with `*.o', but explicitly name
6090 the file `dir.o/foo' after all the options have been listed,
6091 `dir.o/foo' will be excluded from the archive.
6093 * You can sometimes confuse the meanings of `--exclude' and
6094 `--exclude-from'. Be careful: use `--exclude' when files to be
6095 excluded are given as a pattern on the command line. Use
6096 `--exclude-from' to introduce the name of a file which contains a
6097 list of patterns, one per line; each of these patterns can exclude
6098 zero, one, or many files.
6100 * When you use `--exclude=PATTERN', be sure to quote the PATTERN
6101 parameter, so GNU `tar' sees wildcard characters like `*'. If you
6102 do not do this, the shell might expand the `*' itself using files
6103 at hand, so `tar' might receive a list of files instead of one
6104 pattern, or none at all, making the command somewhat illegal.
6105 This might not correspond to what you want.
6109 $ tar -c -f ARCHIVE.TAR --exclude '*.o' DIRECTORY
6114 $ tar -c -f ARCHIVE.TAR --exclude *.o DIRECTORY
6116 * You must use use shell syntax, or globbing, rather than `regexp'
6117 syntax, when using exclude options in `tar'. If you try to use
6118 `regexp' syntax to describe files to be excluded, your command
6121 * In earlier versions of `tar', what is now the `--exclude-from'
6122 option was called `--exclude' instead. Now, `--exclude' applies
6123 to patterns listed on the command line and `--exclude-from'
6124 applies to patterns listed in a file.
6128 File: tar.info, Node: wildcards, Next: quoting styles, Prev: exclude, Up: Choosing
6130 6.5 Wildcards Patterns and Matching
6131 ===================================
6133 "Globbing" is the operation by which "wildcard" characters, `*' or `?'
6134 for example, are replaced and expanded into all existing files matching
6135 the given pattern. GNU `tar' can use wildcard patterns for matching
6136 (or globbing) archive members when extracting from or listing an
6137 archive. Wildcard patterns are also used for verifying volume labels
6138 of `tar' archives. This section has the purpose of explaining wildcard
6141 A PATTERN should be written according to shell syntax, using wildcard
6142 characters to effect globbing. Most characters in the pattern stand
6143 for themselves in the matched string, and case is significant: `a' will
6144 match only `a', and not `A'. The character `?' in the pattern matches
6145 any single character in the matched string. The character `*' in the
6146 pattern matches zero, one, or more single characters in the matched
6147 string. The character `\' says to take the following character of the
6148 pattern _literally_; it is useful when one needs to match the `?', `*',
6149 `[' or `\' characters, themselves.
6151 The character `[', up to the matching `]', introduces a character
6152 class. A "character class" is a list of acceptable characters for the
6153 next single character of the matched string. For example, `[abcde]'
6154 would match any of the first five letters of the alphabet. Note that
6155 within a character class, all of the "special characters" listed above
6156 other than `\' lose their special meaning; for example, `[-\\[*?]]'
6157 would match any of the characters, `-', `\', `[', `*', `?', or `]'.
6158 (Due to parsing constraints, the characters `-' and `]' must either
6159 come _first_ or _last_ in a character class.)
6161 If the first character of the class after the opening `[' is `!' or
6162 `^', then the meaning of the class is reversed. Rather than listing
6163 character to match, it lists those characters which are _forbidden_ as
6164 the next single character of the matched string.
6166 Other characters of the class stand for themselves. The special
6167 construction `[A-E]', using an hyphen between two letters, is meant to
6168 represent all characters between A and E, inclusive.
6170 Periods (`.') or forward slashes (`/') are not considered special
6171 for wildcard matches. However, if a pattern completely matches a
6172 directory prefix of a matched string, then it matches the full matched
6173 string: thus, excluding a directory also excludes all the files beneath
6178 * controlling pattern-matching::
6181 File: tar.info, Node: controlling pattern-matching, Up: wildcards
6183 Controlling Pattern-Matching
6184 ----------------------------
6186 For the purposes of this section, we call "exclusion members" all
6187 member names obtained while processing `--exclude' and `--exclude-from'
6188 options, and "inclusion members" those member names that were given in
6189 the command line or read from the file specified with `--files-from'
6192 These two pairs of member lists are used in the following operations:
6193 `--diff', `--extract', `--list', `--update'.
6195 There are no inclusion members in create mode (`--create' and
6196 `--append'), since in this mode the names obtained from the command
6197 line refer to _files_, not archive members.
6199 By default, inclusion members are compared with archive members
6200 literally (1) and exclusion members are treated as globbing patterns.
6208 # Member names are used verbatim:
6209 $ tar -xf foo.tar -v '[remarks]'
6211 # Exclude member names are globbed:
6212 $ tar -xf foo.tar -v --exclude '*.c'
6216 This behavior can be altered by using the following options:
6219 Treat all member names as wildcards.
6222 Treat all member names as literal strings.
6224 Thus, to extract files whose names end in `.c', you can use:
6226 $ tar -xf foo.tar -v --wildcards '*.c'
6230 Notice quoting of the pattern to prevent the shell from interpreting it.
6232 The effect of `--wildcards' option is canceled by `--no-wildcards'.
6233 This can be used to pass part of the command line arguments verbatim
6234 and other part as globbing patterns. For example, the following
6237 $ tar -xf foo.tar --wildcards '*.txt' --no-wildcards '[remarks]'
6239 instructs `tar' to extract from `foo.tar' all files whose names end in
6240 `.txt' and the file named `[remarks]'.
6242 Normally, a pattern matches a name if an initial subsequence of the
6243 name's components matches the pattern, where `*', `?', and `[...]' are
6244 the usual shell wildcards, `\' escapes wildcards, and wildcards can
6247 Other than optionally stripping leading `/' from names (*note
6248 absolute::), patterns and names are used as-is. For example, trailing
6249 `/' is not trimmed from a user-specified name before deciding whether
6252 However, this matching procedure can be altered by the options listed
6253 below. These options accumulate. For example:
6255 --ignore-case --exclude='makefile' --no-ignore-case ---exclude='readme'
6257 ignores case when excluding `makefile', but not when excluding `readme'.
6261 If anchored, a pattern must match an initial subsequence of the
6262 name's components. Otherwise, the pattern can match any
6263 subsequence. Default is `--no-anchored' for exclusion members and
6264 `--anchored' inclusion members.
6268 When ignoring case, upper-case patterns match lower-case names and
6269 vice versa. When not ignoring case (the default), matching is
6272 `--wildcards-match-slash'
6273 `--no-wildcards-match-slash'
6274 When wildcards match slash (the default for exclusion members), a
6275 wildcard like `*' in the pattern can match a `/' in the name.
6276 Otherwise, `/' is matched only by `/'.
6279 The `--recursion' and `--no-recursion' options (*note recurse::)
6280 also affect how member patterns are interpreted. If recursion is in
6281 effect, a pattern matches a name if it matches any of the name's parent
6284 The following table summarizes pattern-matching default values:
6286 Members Default settings
6287 --------------------------------------------------------------------------
6288 Inclusion `--no-wildcards --anchored
6289 --no-wildcards-match-slash'
6290 Exclusion `--wildcards --no-anchored
6291 --wildcards-match-slash'
6293 ---------- Footnotes ----------
6295 (1) Notice that earlier GNU `tar' versions used globbing for
6296 inclusion members, which contradicted to UNIX98 specification and was
6297 not documented. *Note Changes::, for more information on this and other
6301 File: tar.info, Node: quoting styles, Next: transform, Prev: wildcards, Up: Choosing
6303 6.6 Quoting Member Names
6304 ========================
6306 When displaying member names, `tar' takes care to avoid ambiguities
6307 caused by certain characters. This is called "name quoting". The
6308 characters in question are:
6310 * Non-printable control characters:
6311 Character ASCII Character name
6312 ---------------------------------------------------------------
6317 \r 13 Carriage return
6318 \t 9 Horizontal tabulation
6319 \v 11 Vertical tabulation
6323 * Single and double quotes (`'' and `"')
6327 The exact way `tar' uses to quote these characters depends on the
6328 "quoting style". The default quoting style, called "escape" (see
6329 below), uses backslash notation to represent control characters, space
6330 and backslash. Using this quoting style, control characters are
6331 represented as listed in column `Character' in the above table, a space
6332 is printed as `\ ' and a backslash as `\\'.
6334 GNU `tar' offers seven distinct quoting styles, which can be selected
6335 using `--quoting-style' option:
6337 `--quoting-style=STYLE'
6338 Sets quoting style. Valid values for STYLE argument are: literal,
6339 shell, shell-always, c, escape, locale, clocale.
6341 These styles are described in detail below. To illustrate their
6342 effect, we will use an imaginary tar archive `arch.tar' containing the
6345 # 1. Contains horizontal tabulation character.
6347 # 2. Contains newline character
6350 # 3. Contains a space
6352 # 4. Contains double quotes
6354 # 5. Contains single quotes
6356 # 6. Contains a backslash character:
6359 Here is how usual `ls' command would have listed them, if they had
6360 existed in the current working directory:
6373 No quoting, display each character as is:
6375 $ tar tf arch.tar --quoting-style=literal
6386 Display characters the same way Bourne shell does: control
6387 characters, except `\t' and `\n', are printed using backslash
6388 escapes, `\t' and `\n' are printed as is, and a single quote is
6389 printed as `\''. If a name contains any quoted characters, it is
6390 enclosed in single quotes. In particular, if a name contains
6391 single quotes, it is printed as several single-quoted strings:
6393 $ tar tf arch.tar --quoting-style=shell
6396 './a'\''single'\''quote'
6404 Same as `shell', but the names are always enclosed in single
6407 $ tar tf arch.tar --quoting-style=shell-always
6410 './a'\''single'\''quote'
6418 Use the notation of the C programming language. All names are
6419 enclosed in double quotes. Control characters are quoted using
6420 backslash notations, double quotes are represented as `\"',
6421 backslash characters are represented as `\\'. Single quotes and
6422 spaces are not quoted:
6424 $ tar tf arch.tar --quoting-style=c
6428 "./a\"double\"quote"
6434 Control characters are printed using backslash notation, a space is
6435 printed as `\ ' and a backslash as `\\'. This is the default
6436 quoting style, unless it was changed when configured the package.
6438 $ tar tf arch.tar --quoting-style=escape
6448 Control characters, single quote and backslash are printed using
6449 backslash notation. All names are quoted using left and right
6450 quotation marks, appropriate to the current locale. If it does not
6451 define quotation marks, use ``' as left and `'' as right quotation
6452 marks. Any occurrences of the right quotation mark in a name are
6453 escaped with `\', for example:
6457 $ tar tf arch.tar --quoting-style=locale
6460 `./a\'single\'quote'
6467 Same as `locale', but `"' is used for both left and right
6468 quotation marks, if not provided by the currently selected locale:
6470 $ tar tf arch.tar --quoting-style=clocale
6474 "./a\"double\"quote"
6479 You can specify which characters should be quoted in addition to
6480 those implied by the current quoting style:
6482 `--quote-chars=STRING'
6483 Always quote characters from STRING, even if the selected quoting
6484 style would not quote them.
6486 For example, using `escape' quoting (compare with the usual escape
6489 $ tar tf arch.tar --quoting-style=escape --quote-chars=' "'
6498 To disable quoting of such additional characters, use the following
6501 `--no-quote-chars=STRING'
6502 Remove characters listed in STRING from the list of quoted
6503 characters set by the previous `--quote-chars' option.
6505 This option is particularly useful if you have added `--quote-chars'
6506 to your `TAR_OPTIONS' (*note TAR_OPTIONS::) and wish to disable it for
6507 the current invocation.
6509 Note, that `--no-quote-chars' does _not_ disable those characters
6510 that are quoted by default in the selected quoting style.
6513 File: tar.info, Node: transform, Next: after, Prev: quoting styles, Up: Choosing
6515 6.7 Modifying File and Member Names
6516 ===================================
6518 `Tar' archives contain detailed information about files stored in them
6519 and full file names are part of that information. When storing file to
6520 an archive, its file name is recorded in it, along with the actual file
6521 contents. When restoring from an archive, a file is created on disk
6522 with exactly the same name as that stored in the archive. In the
6523 majority of cases this is the desired behavior of a file archiver.
6524 However, there are some cases when it is not.
6526 First of all, it is often unsafe to extract archive members with
6527 absolute file names or those that begin with a `../'. GNU `tar' takes
6528 special precautions when extracting such names and provides a special
6529 option for handling them, which is described in *note absolute::.
6531 Secondly, you may wish to extract file names without some leading
6532 directory components, or with otherwise modified names. In other cases
6533 it is desirable to store files under differing names in the archive.
6535 GNU `tar' provides several options for these needs.
6537 `--strip-components=NUMBER'
6538 Strip given NUMBER of leading components from file names before
6541 For example, suppose you have archived whole `/usr' hierarchy to a
6542 tar archive named `usr.tar'. Among other files, this archive contains
6543 `usr/include/stdlib.h', which you wish to extract to the current
6544 working directory. To do so, you type:
6546 $ tar -xf usr.tar --strip=2 usr/include/stdlib.h
6548 The option `--strip=2' instructs `tar' to strip the two leading
6549 components (`usr/' and `include/') off the file name.
6551 If you add the `--verbose' (`-v') option to the invocation above,
6552 you will note that the verbose listing still contains the full file
6553 name, with the two removed components still in place. This can be
6554 inconvenient, so `tar' provides a special option for altering this
6557 `--show-transformed-names'
6558 Display file or member names with all requested transformations
6563 $ tar -xf usr.tar -v --strip=2 usr/include/stdlib.h
6564 usr/include/stdlib.h
6565 $ tar -xf usr.tar -v --strip=2 --show-transformed usr/include/stdlib.h
6568 Notice that in both cases the file `stdlib.h' is extracted to the
6569 current working directory, `--show-transformed-names' affects only the
6570 way its name is displayed.
6572 This option is especially useful for verifying whether the invocation
6573 will have the desired effect. Thus, before running
6577 it is often advisable to run
6579 $ tar -t -v --show-transformed --strip=N
6581 to make sure the command will produce the intended results.
6583 In case you need to apply more complex modifications to the file
6584 name, GNU `tar' provides a general-purpose transformation option:
6586 `--transform=EXPRESSION'
6587 `--xform=EXPRESSION'
6588 Modify file names using supplied EXPRESSION.
6590 The EXPRESSION is a `sed'-like replace expression of the form:
6592 s/REGEXP/REPLACE/[FLAGS]
6594 where REGEXP is a "regular expression", REPLACE is a replacement for
6595 each file name part that matches REGEXP. Both REGEXP and REPLACE are
6596 described in detail in *note The "s" Command: (sed)The "s" Command.
6598 Any delimiter can be used in lieue of `/', the only requirement being
6599 that it be used consistently throughout the expression. For example,
6600 the following two expressions are equivalent:
6605 Changing delimiters is often useful when the REGEX contains slashes.
6606 For example, it is more convenient to write `s,/,-,' than `s/\//-/'.
6608 As in `sed', you can give several replace expressions, separated by
6611 Supported FLAGS are:
6614 Apply the replacement to _all_ matches to the REGEXP, not just the
6618 Use case-insensitive matching
6621 REGEXP is an "extended regular expression" (*note Extended regular
6622 expressions: (sed)Extended regexps.).
6625 Only replace the NUMBERth match of the REGEXP.
6627 Note: the POSIX standard does not specify what should happen when
6628 you mix the `g' and NUMBER modifiers. GNU `tar' follows the GNU
6629 `sed' implementation in this regard, so the interaction is defined
6630 to be: ignore matches before the NUMBERth, and then match and
6631 replace all matches from the NUMBERth on.
6634 In addition, several "transformation scope" flags are supported,
6635 that control to what files transformations apply. These are:
6638 Apply transformation to regular archive members.
6641 Do not apply transformation to regular archive members.
6644 Apply transformation to symbolic link targets.
6647 Do not apply transformation to symbolic link targets.
6650 Apply transformation to hard link targets.
6653 Do not apply transformation to hard link targets.
6655 Default is `rsh', which means to apply tranformations to both archive
6656 members and targets of symbolic and hard links.
6658 Default scope flags can also be changed using `flags=' statement in
6659 the transform expression. The flags set this way remain in force until
6660 next `flags=' statement or end of expression, whichever occurs first.
6663 --transform 'flags=S;s|^|/usr/local/|'
6665 Here are several examples of `--transform' usage:
6667 1. Extract `usr/' hierarchy into `usr/local/':
6669 $ tar --transform='s,usr/,usr/local/,' -x -f arch.tar
6671 2. Strip two leading directory components (equivalent to
6672 `--strip-components=2'):
6674 $ tar --transform='s,/*[^/]*/[^/]*/,,' -x -f arch.tar
6676 3. Convert each file name to lower case:
6678 $ tar --transform 's/.*/\L&/' -x -f arch.tar
6680 4. Prepend `/prefix/' to each file name:
6682 $ tar --transform 's,^,/prefix/,' -x -f arch.tar
6684 5. Archive the `/lib' directory, prepending `/usr/local' to each
6687 $ tar --transform 's,^,/usr/local/,S' -c -f arch.tar /lib
6689 Notice the use of flags in the last example. The `/lib' directory
6690 often contains many symbolic links to files within it. It may look,
6691 for example, like this:
6694 drwxr-xr-x root/root 0 2008-07-08 16:20 /lib/
6695 -rwxr-xr-x root/root 1250840 2008-05-25 07:44 /lib/libc-2.3.2.so
6696 lrwxrwxrwx root/root 0 2008-06-24 17:12 /lib/libc.so.6 -> libc-2.3.2.so
6699 Using the expression `s,^,/usr/local/,' would mean adding
6700 `/usr/local' to both regular archive members and to link targets. In
6701 this case, `/lib/libc.so.6' would become:
6703 /usr/local/lib/libc.so.6 -> /usr/local/libc-2.3.2.so
6705 This is definitely not desired. To avoid this, the `S' flag are
6706 used, which excludes symbolic link targets from filename
6707 transformations. The result is:
6709 $ tar --transform 's,^,/usr/local/,S', -c -v -f arch.tar \
6710 --show-transformed /lib
6711 drwxr-xr-x root/root 0 2008-07-08 16:20 /usr/local/lib/
6712 -rwxr-xr-x root/root 1250840 2008-05-25 07:44 /usr/local/lib/libc-2.3.2.so
6713 lrwxrwxrwx root/root 0 2008-06-24 17:12 /usr/local/lib/libc.so.6 ->
6716 Unlike `--strip-components', `--transform' can be used in any GNU
6717 `tar' operation mode. For example, the following command adds files to
6718 the archive while replacing the leading `usr/' component with `var/':
6720 $ tar -cf arch.tar --transform='s,^usr/,var/,' /
6722 To test `--transform' effect we suggest using
6723 `--show-transformed-names' option:
6725 $ tar -cf arch.tar --transform='s,^usr/,var/,' \
6726 --verbose --show-transformed-names /
6728 If both `--strip-components' and `--transform' are used together,
6729 then `--transform' is applied first, and the required number of
6730 components is then stripped from its result.
6732 You can use as many `--transform' options in a single command line
6733 as you want. The specified expressions will then be applied in order
6734 of their appearance. For example, the following two invocations are
6737 $ tar -cf arch.tar --transform='s,/usr/var,/var/' \
6738 --transform='s,/usr/local,/usr/,'
6739 $ tar -cf arch.tar \
6740 --transform='s,/usr/var,/var/;s,/usr/local,/usr/,'
6743 File: tar.info, Node: after, Next: recurse, Prev: transform, Up: Choosing
6745 6.8 Operating Only on New Files
6746 ===============================
6748 _(This message will disappear, once this node revised.)_
6750 The `--after-date=DATE' (`--newer=DATE', `-N DATE') option causes `tar'
6751 to only work on files whose data modification or status change times
6752 are newer than the DATE given. If DATE starts with `/' or `.', it is
6753 taken to be a file name; the data modification time of that file is
6754 used as the date. If you use this option when creating or appending to
6755 an archive, the archive will only include new files. If you use
6756 `--after-date' when extracting an archive, `tar' will only extract
6757 files newer than the DATE you specify.
6759 If you only want `tar' to make the date comparison based on
6760 modification of the file's data (rather than status changes), then use
6761 the `--newer-mtime=DATE' option.
6763 You may use these options with any operation. Note that these
6764 options differ from the `--update' (`-u') operation in that they allow
6765 you to specify a particular date against which `tar' can compare when
6766 deciding whether or not to archive the files.
6771 Only store files newer than DATE.
6773 Acts on files only if their data modification or status change
6774 times are later than DATE. Use in conjunction with any operation.
6776 If DATE starts with `/' or `.', it is taken to be a file name; the
6777 data modification time of that file is used as the date.
6779 `--newer-mtime=DATE'
6780 Acts like `--after-date', but only looks at data modification
6783 These options limit `tar' to operate only on files which have been
6784 modified after the date specified. A file's status is considered to
6785 have changed if its contents have been modified, or if its owner,
6786 permissions, and so forth, have been changed. (For more information on
6787 how to specify a date, see *note Date input formats::; remember that the
6788 entire date argument must be quoted if it contains any spaces.)
6790 Gurus would say that `--after-date' tests both the data modification
6791 time (`mtime', the time the contents of the file were last modified)
6792 and the status change time (`ctime', the time the file's status was
6793 last changed: owner, permissions, etc.) fields, while `--newer-mtime'
6794 tests only the `mtime' field.
6796 To be precise, `--after-date' checks _both_ `mtime' and `ctime' and
6797 processes the file if either one is more recent than DATE, while
6798 `--newer-mtime' only checks `mtime' and disregards `ctime'. Neither
6799 does it use `atime' (the last time the contents of the file were looked
6802 Date specifiers can have embedded spaces. Because of this, you may
6803 need to quote date arguments to keep the shell from parsing them as
6804 separate arguments. For example, the following command will add to the
6805 archive all the files modified less than two days ago:
6807 $ tar -cf foo.tar --newer-mtime '2 days ago'
6809 When any of these options is used with the option `--verbose' (*note
6810 verbose tutorial::) GNU `tar' will try to convert the specified date
6811 back to its textual representation and compare that with the one given
6812 with the option. If the two dates differ, `tar' will print a warning
6813 saying what date it will use. This is to help user ensure he is using
6814 the right date. For example:
6816 $ tar -c -f archive.tar --after-date='10 days ago' .
6817 tar: Option --after-date: Treating date `10 days ago' as 2006-06-11
6820 *Please Note:* `--after-date' and `--newer-mtime' should not be
6821 used for incremental backups. *Note Incremental Dumps::, for
6822 proper way of creating incremental backups.
6825 File: tar.info, Node: recurse, Next: one, Prev: after, Up: Choosing
6827 6.9 Descending into Directories
6828 ===============================
6830 _(This message will disappear, once this node revised.)_
6832 Usually, `tar' will recursively explore all directories (either those
6833 given on the command line or through the `--files-from' option) for the
6834 various files they contain. However, you may not always want `tar' to
6837 The `--no-recursion' option inhibits `tar''s recursive descent into
6838 specified directories. If you specify `--no-recursion', you can use
6839 the `find' utility for hunting through levels of directories to
6840 construct a list of file names which you could then pass to `tar'.
6841 `find' allows you to be more selective when choosing which files to
6842 archive; see *note files::, for more information on using `find' with
6846 Prevents `tar' from recursively descending directories.
6849 Requires `tar' to recursively descend directories. This is the
6852 When you use `--no-recursion', GNU `tar' grabs directory entries
6853 themselves, but does not descend on them recursively. Many people use
6854 `find' for locating files they want to back up, and since `tar'
6855 _usually_ recursively descends on directories, they have to use the
6856 `-not -type d' test in their `find' invocation (*note Type:
6857 (find)Type.), as they usually do not want all the files in a directory.
6858 They then use the `--files-from' option to archive the files located
6861 The problem when restoring files archived in this manner is that the
6862 directories themselves are not in the archive; so the
6863 `--same-permissions' (`--preserve-permissions', `-p') option does not
6864 affect them--while users might really like it to. Specifying
6865 `--no-recursion' is a way to tell `tar' to grab only the directory
6866 entries given to it, adding no new files on its own. To summarize, if
6867 you use `find' to create a list of files to be stored in an archive,
6870 $ find DIR TESTS | \
6871 tar -cf ARCHIVE -T - --no-recursion
6873 The `--no-recursion' option also applies when extracting: it causes
6874 `tar' to extract only the matched directory entries, not the files
6875 under those directories.
6877 The `--no-recursion' option also affects how globbing patterns are
6878 interpreted (*note controlling pattern-matching::).
6880 The `--no-recursion' and `--recursion' options apply to later
6881 options and operands, and can be overridden by later occurrences of
6882 `--no-recursion' and `--recursion'. For example:
6884 $ tar -cf jams.tar --no-recursion grape --recursion grape/concord
6886 creates an archive with one entry for `grape', and the recursive
6887 contents of `grape/concord', but no entries under `grape' other than
6891 File: tar.info, Node: one, Prev: recurse, Up: Choosing
6893 6.10 Crossing File System Boundaries
6894 ====================================
6896 _(This message will disappear, once this node revised.)_
6898 `tar' will normally automatically cross file system boundaries in order
6899 to archive files which are part of a directory tree. You can change
6900 this behavior by running `tar' and specifying `--one-file-system'.
6901 This option only affects files that are archived because they are in a
6902 directory that is being archived; `tar' will still archive files
6903 explicitly named on the command line or through `--files-from',
6904 regardless of where they reside.
6907 Prevents `tar' from crossing file system boundaries when
6908 archiving. Use in conjunction with any write operation.
6910 The `--one-file-system' option causes `tar' to modify its normal
6911 behavior in archiving the contents of directories. If a file in a
6912 directory is not on the same file system as the directory itself, then
6913 `tar' will not archive that file. If the file is a directory itself,
6914 `tar' will not archive anything beneath it; in other words, `tar' will
6915 not cross mount points.
6917 This option is useful for making full or incremental archival
6918 backups of a file system. If this option is used in conjunction with
6919 `--verbose' (`-v'), files that are excluded are mentioned by name on
6924 * directory:: Changing Directory
6925 * absolute:: Absolute File Names
6928 File: tar.info, Node: directory, Next: absolute, Up: one
6930 6.10.1 Changing the Working Directory
6931 -------------------------------------
6933 To change the working directory in the middle of a list of file names,
6934 either on the command line or in a file specified using `--files-from'
6935 (`-T'), use `--directory' (`-C'). This will change the working
6936 directory to the specified directory after that point in the list.
6938 `--directory=DIRECTORY'
6940 Changes the working directory in the middle of a command line.
6944 $ tar -c -f jams.tar grape prune -C food cherry
6946 will place the files `grape' and `prune' from the current directory
6947 into the archive `jams.tar', followed by the file `cherry' from the
6948 directory `food'. This option is especially useful when you have
6949 several widely separated files that you want to store in the same
6952 Note that the file `cherry' is recorded in the archive under the
6953 precise name `cherry', _not_ `food/cherry'. Thus, the archive will
6954 contain three files that all appear to have come from the same
6955 directory; if the archive is extracted with plain `tar --extract', all
6956 three files will be written in the current directory.
6958 Contrast this with the command,
6960 $ tar -c -f jams.tar grape prune -C food red/cherry
6962 which records the third file in the archive under the name `red/cherry'
6963 so that, if the archive is extracted using `tar --extract', the third
6964 file will be written in a subdirectory named `orange-colored'.
6966 You can use the `--directory' option to make the archive independent
6967 of the original name of the directory holding the files. The following
6968 command places the files `/etc/passwd', `/etc/hosts', and `/lib/libc.a'
6969 into the archive `foo.tar':
6971 $ tar -c -f foo.tar -C /etc passwd hosts -C /lib libc.a
6973 However, the names of the archive members will be exactly what they were
6974 on the command line: `passwd', `hosts', and `libc.a'. They will not
6975 appear to be related by file name to the original directories where
6976 those files were located.
6978 Note that `--directory' options are interpreted consecutively. If
6979 `--directory' specifies a relative file name, it is interpreted
6980 relative to the then current directory, which might not be the same as
6981 the original current working directory of `tar', due to a previous
6982 `--directory' option.
6984 When using `--files-from' (*note files::), you can put various `tar'
6985 options (including `-C') in the file list. Notice, however, that in
6986 this case the option and its argument may not be separated by
6987 whitespace. If you use short option, its argument must either follow
6988 the option letter immediately, without any intervening whitespace, or
6989 occupy the next line. Otherwise, if you use long option, separate its
6990 argument by an equal sign.
6992 For instance, the file list for the above example will be:
7000 To use it, you would invoke `tar' as follows:
7002 $ tar -c -f foo.tar --files-from list
7004 The interpretation of `--directory' is disabled by `--null' option.
7007 File: tar.info, Node: absolute, Prev: directory, Up: one
7009 6.10.2 Absolute File Names
7010 --------------------------
7012 _(This message will disappear, once this node revised.)_
7016 Do not strip leading slashes from file names, and permit file names
7017 containing a `..' file name component.
7019 By default, GNU `tar' drops a leading `/' on input or output, and
7020 complains about file names containing a `..' component. This option
7021 turns off this behavior.
7023 When `tar' extracts archive members from an archive, it strips any
7024 leading slashes (`/') from the member name. This causes absolute
7025 member names in the archive to be treated as relative file names. This
7026 allows you to have such members extracted wherever you want, instead of
7027 being restricted to extracting the member in the exact directory named
7028 in the archive. For example, if the archive member has the name
7029 `/etc/passwd', `tar' will extract it as if the name were really
7032 File names containing `..' can cause problems when extracting, so
7033 `tar' normally warns you about such files when creating an archive, and
7034 rejects attempts to extracts such files.
7036 Other `tar' programs do not do this. As a result, if you create an
7037 archive whose member names start with a slash, they will be difficult
7038 for other people with a non-GNU `tar' program to use. Therefore, GNU
7039 `tar' also strips leading slashes from member names when putting
7040 members into the archive. For example, if you ask `tar' to add the file
7041 `/bin/ls' to an archive, it will do so, but the member name will be
7044 If you use the `--absolute-names' (`-P') option, `tar' will do none
7045 of these transformations.
7047 To archive or extract files relative to the root directory, specify
7048 the `--absolute-names' (`-P') option.
7050 Normally, `tar' acts on files relative to the working
7051 directory--ignoring superior directory names when archiving, and
7052 ignoring leading slashes when extracting.
7054 When you specify `--absolute-names' (`-P'), `tar' stores file names
7055 including all superior directory names, and preserves leading slashes.
7056 If you only invoked `tar' from the root directory you would never need
7057 the `--absolute-names' option, but using this option may be more
7058 convenient than switching to root.
7061 Preserves full file names (including superior directory names) when
7062 archiving files. Preserves leading slash when extracting files.
7065 `tar' prints out a message about removing the `/' from file names.
7066 This message appears once per GNU `tar' invocation. It represents
7067 something which ought to be told; ignoring what it means can cause very
7068 serious surprises, later.
7070 Some people, nevertheless, do not want to see this message. Wanting
7071 to play really dangerously, one may of course redirect `tar' standard
7072 error to the sink. For example, under `sh':
7074 $ tar -c -f archive.tar /home 2> /dev/null
7076 Another solution, both nicer and simpler, would be to change to the `/'
7077 directory first, and then avoid absolute notation. For example:
7079 $ tar -c -f archive.tar -C / home
7081 ---------- Footnotes ----------
7083 (1) A side effect of this is that when `--create' is used with
7084 `--verbose' the resulting output is not, generally speaking, the same
7085 as the one you'd get running `tar --list' command. This may be
7086 important if you use some scripts for comparing both outputs. *Note
7087 listing member and file names::, for the information on how to handle
7091 File: tar.info, Node: Date input formats, Next: Formats, Prev: Choosing, Up: Top
7093 7 Date input formats
7094 ********************
7098 Our units of temporal measurement, from seconds on up to months,
7099 are so complicated, asymmetrical and disjunctive so as to make
7100 coherent mental reckoning in time all but impossible. Indeed, had
7101 some tyrannical god contrived to enslave our minds to time, to
7102 make it all but impossible for us to escape subjection to sodden
7103 routines and unpleasant surprises, he could hardly have done
7104 better than handing down our present system. It is like a set of
7105 trapezoidal building blocks, with no vertical or horizontal
7106 surfaces, like a language in which the simplest thought demands
7107 ornate constructions, useless particles and lengthy
7108 circumlocutions. Unlike the more successful patterns of language
7109 and science, which enable us to face experience boldly or at least
7110 level-headedly, our system of temporal calculation silently and
7111 persistently encourages our terror of time.
7113 ... It is as though architects had to measure length in feet,
7114 width in meters and height in ells; as though basic instruction
7115 manuals demanded a knowledge of five different languages. It is
7116 no wonder then that we often look into our own immediate past or
7117 future, last Tuesday or a week from Sunday, with feelings of
7118 helpless confusion. ...
7120 -- Robert Grudin, `Time and the Art of Living'.
7122 This section describes the textual date representations that GNU
7123 programs accept. These are the strings you, as a user, can supply as
7124 arguments to the various programs. The C interface (via the `get_date'
7125 function) is not described here.
7129 * General date syntax:: Common rules.
7130 * Calendar date items:: 19 Dec 1994.
7131 * Time of day items:: 9:20pm.
7132 * Time zone items:: EST, PDT, GMT.
7133 * Day of week items:: Monday and others.
7134 * Relative items in date strings:: next tuesday, 2 years ago.
7135 * Pure numbers in date strings:: 19931219, 1440.
7136 * Seconds since the Epoch:: @1078100502.
7137 * Specifying time zone rules:: TZ="America/New_York", TZ="UTC0".
7138 * Authors of get_date:: Bellovin, Eggert, Salz, Berets, et al.
7141 File: tar.info, Node: General date syntax, Next: Calendar date items, Up: Date input formats
7143 7.1 General date syntax
7144 =======================
7146 A "date" is a string, possibly empty, containing many items separated
7147 by whitespace. The whitespace may be omitted when no ambiguity arises.
7148 The empty string means the beginning of today (i.e., midnight). Order
7149 of the items is immaterial. A date string may contain many flavors of
7152 * calendar date items
7158 * day of the week items
7164 We describe each of these item types in turn, below.
7166 A few ordinal numbers may be written out in words in some contexts.
7167 This is most useful for specifying day of the week items or relative
7168 items (see below). Among the most commonly used ordinal numbers, the
7169 word `last' stands for -1, `this' stands for 0, and `first' and `next'
7170 both stand for 1. Because the word `second' stands for the unit of
7171 time there is no way to write the ordinal number 2, but for convenience
7172 `third' stands for 3, `fourth' for 4, `fifth' for 5, `sixth' for 6,
7173 `seventh' for 7, `eighth' for 8, `ninth' for 9, `tenth' for 10,
7174 `eleventh' for 11 and `twelfth' for 12.
7176 When a month is written this way, it is still considered to be
7177 written numerically, instead of being "spelled in full"; this changes
7178 the allowed strings.
7180 In the current implementation, only English is supported for words
7181 and abbreviations like `AM', `DST', `EST', `first', `January',
7182 `Sunday', `tomorrow', and `year'.
7184 The output of the `date' command is not always acceptable as a date
7185 string, not only because of the language problem, but also because
7186 there is no standard meaning for time zone items like `IST'. When using
7187 `date' to generate a date string intended to be parsed later, specify a
7188 date format that is independent of language and that does not use time
7189 zone items other than `UTC' and `Z'. Here are some ways to do this:
7191 $ LC_ALL=C TZ=UTC0 date
7192 Mon Mar 1 00:21:42 UTC 2004
7193 $ TZ=UTC0 date +'%Y-%m-%d %H:%M:%SZ'
7194 2004-03-01 00:21:42Z
7195 $ date --iso-8601=ns | tr T ' ' # --iso-8601 is a GNU extension.
7196 2004-02-29 16:21:42,692722128-0800
7197 $ date --rfc-2822 # a GNU extension
7198 Sun, 29 Feb 2004 16:21:42 -0800
7199 $ date +'%Y-%m-%d %H:%M:%S %z' # %z is a GNU extension.
7200 2004-02-29 16:21:42 -0800
7201 $ date +'@%s.%N' # %s and %N are GNU extensions.
7202 @1078100502.692722128
7204 Alphabetic case is completely ignored in dates. Comments may be
7205 introduced between round parentheses, as long as included parentheses
7206 are properly nested. Hyphens not followed by a digit are currently
7207 ignored. Leading zeros on numbers are ignored.
7209 Invalid dates like `2005-02-29' or times like `24:00' are rejected.
7210 In the typical case of a host that does not support leap seconds, a
7211 time like `23:59:60' is rejected even if it corresponds to a valid leap
7215 File: tar.info, Node: Calendar date items, Next: Time of day items, Prev: General date syntax, Up: Date input formats
7217 7.2 Calendar date items
7218 =======================
7220 A "calendar date item" specifies a day of the year. It is specified
7221 differently, depending on whether the month is specified numerically or
7222 literally. All these strings specify the same calendar date:
7224 1972-09-24 # ISO 8601.
7225 72-9-24 # Assume 19xx for 69 through 99,
7226 # 20xx for 00 through 68.
7227 72-09-24 # Leading zeros are ignored.
7228 9/24/72 # Common U.S. writing.
7230 24 Sept 72 # September has a special abbreviation.
7231 24 Sep 72 # Three-letter abbreviations always allowed.
7236 The year can also be omitted. In this case, the last specified year
7237 is used, or the current year if none. For example:
7244 For numeric months, the ISO 8601 format `YEAR-MONTH-DAY' is allowed,
7245 where YEAR is any positive number, MONTH is a number between 01 and 12,
7246 and DAY is a number between 01 and 31. A leading zero must be present
7247 if a number is less than ten. If YEAR is 68 or smaller, then 2000 is
7248 added to it; otherwise, if YEAR is less than 100, then 1900 is added to
7249 it. The construct `MONTH/DAY/YEAR', popular in the United States, is
7250 accepted. Also `MONTH/DAY', omitting the year.
7252 Literal months may be spelled out in full: `January', `February',
7253 `March', `April', `May', `June', `July', `August', `September',
7254 `October', `November' or `December'. Literal months may be abbreviated
7255 to their first three letters, possibly followed by an abbreviating dot.
7256 It is also permitted to write `Sept' instead of `September'.
7258 When months are written literally, the calendar date may be given as
7259 any of the following:
7266 Or, omitting the year:
7271 File: tar.info, Node: Time of day items, Next: Time zone items, Prev: Calendar date items, Up: Date input formats
7273 7.3 Time of day items
7274 =====================
7276 A "time of day item" in date strings specifies the time on a given day.
7277 Here are some examples, all of which represent the same time:
7282 20:02-0500 # In EST (U.S. Eastern Standard Time).
7284 More generally, the time of day may be given as
7285 `HOUR:MINUTE:SECOND', where HOUR is a number between 0 and 23, MINUTE
7286 is a number between 0 and 59, and SECOND is a number between 0 and 59
7287 possibly followed by `.' or `,' and a fraction containing one or more
7288 digits. Alternatively, `:SECOND' can be omitted, in which case it is
7289 taken to be zero. On the rare hosts that support leap seconds, SECOND
7292 If the time is followed by `am' or `pm' (or `a.m.' or `p.m.'), HOUR
7293 is restricted to run from 1 to 12, and `:MINUTE' may be omitted (taken
7294 to be zero). `am' indicates the first half of the day, `pm' indicates
7295 the second half of the day. In this notation, 12 is the predecessor of
7296 1: midnight is `12am' while noon is `12pm'. (This is the zero-oriented
7297 interpretation of `12am' and `12pm', as opposed to the old tradition
7298 derived from Latin which uses `12m' for noon and `12pm' for midnight.)
7300 The time may alternatively be followed by a time zone correction,
7301 expressed as `SHHMM', where S is `+' or `-', HH is a number of zone
7302 hours and MM is a number of zone minutes. The zone minutes term, MM,
7303 may be omitted, in which case the one- or two-digit correction is
7304 interpreted as a number of hours. You can also separate HH from MM
7305 with a colon. When a time zone correction is given this way, it forces
7306 interpretation of the time relative to Coordinated Universal Time
7307 (UTC), overriding any previous specification for the time zone or the
7308 local time zone. For example, `+0530' and `+05:30' both stand for the
7309 time zone 5.5 hours ahead of UTC (e.g., India). This is the best way to
7310 specify a time zone correction by fractional parts of an hour. The
7311 maximum zone correction is 24 hours.
7313 Either `am'/`pm' or a time zone correction may be specified, but not
7317 File: tar.info, Node: Time zone items, Next: Day of week items, Prev: Time of day items, Up: Date input formats
7322 A "time zone item" specifies an international time zone, indicated by a
7323 small set of letters, e.g., `UTC' or `Z' for Coordinated Universal
7324 Time. Any included periods are ignored. By following a
7325 non-daylight-saving time zone by the string `DST' in a separate word
7326 (that is, separated by some white space), the corresponding daylight
7327 saving time zone may be specified. Alternatively, a
7328 non-daylight-saving time zone can be followed by a time zone
7329 correction, to add the two values. This is normally done only for
7330 `UTC'; for example, `UTC+05:30' is equivalent to `+05:30'.
7332 Time zone items other than `UTC' and `Z' are obsolescent and are not
7333 recommended, because they are ambiguous; for example, `EST' has a
7334 different meaning in Australia than in the United States. Instead,
7335 it's better to use unambiguous numeric time zone corrections like
7336 `-0500', as described in the previous section.
7338 If neither a time zone item nor a time zone correction is supplied,
7339 time stamps are interpreted using the rules of the default time zone
7340 (*note Specifying time zone rules::).
7343 File: tar.info, Node: Day of week items, Next: Relative items in date strings, Prev: Time zone items, Up: Date input formats
7345 7.5 Day of week items
7346 =====================
7348 The explicit mention of a day of the week will forward the date (only
7349 if necessary) to reach that day of the week in the future.
7351 Days of the week may be spelled out in full: `Sunday', `Monday',
7352 `Tuesday', `Wednesday', `Thursday', `Friday' or `Saturday'. Days may
7353 be abbreviated to their first three letters, optionally followed by a
7354 period. The special abbreviations `Tues' for `Tuesday', `Wednes' for
7355 `Wednesday' and `Thur' or `Thurs' for `Thursday' are also allowed.
7357 A number may precede a day of the week item to move forward
7358 supplementary weeks. It is best used in expression like `third
7359 monday'. In this context, `last DAY' or `next DAY' is also acceptable;
7360 they move one week before or after the day that DAY by itself would
7363 A comma following a day of the week item is ignored.
7366 File: tar.info, Node: Relative items in date strings, Next: Pure numbers in date strings, Prev: Day of week items, Up: Date input formats
7368 7.6 Relative items in date strings
7369 ==================================
7371 "Relative items" adjust a date (or the current date if none) forward or
7372 backward. The effects of relative items accumulate. Here are some
7380 The unit of time displacement may be selected by the string `year'
7381 or `month' for moving by whole years or months. These are fuzzy units,
7382 as years and months are not all of equal duration. More precise units
7383 are `fortnight' which is worth 14 days, `week' worth 7 days, `day'
7384 worth 24 hours, `hour' worth 60 minutes, `minute' or `min' worth 60
7385 seconds, and `second' or `sec' worth one second. An `s' suffix on
7386 these units is accepted and ignored.
7388 The unit of time may be preceded by a multiplier, given as an
7389 optionally signed number. Unsigned numbers are taken as positively
7390 signed. No number at all implies 1 for a multiplier. Following a
7391 relative item by the string `ago' is equivalent to preceding the unit
7392 by a multiplier with value -1.
7394 The string `tomorrow' is worth one day in the future (equivalent to
7395 `day'), the string `yesterday' is worth one day in the past (equivalent
7398 The strings `now' or `today' are relative items corresponding to
7399 zero-valued time displacement, these strings come from the fact a
7400 zero-valued time displacement represents the current time when not
7401 otherwise changed by previous items. They may be used to stress other
7402 items, like in `12:00 today'. The string `this' also has the meaning
7403 of a zero-valued time displacement, but is preferred in date strings
7404 like `this thursday'.
7406 When a relative item causes the resulting date to cross a boundary
7407 where the clocks were adjusted, typically for daylight saving time, the
7408 resulting date and time are adjusted accordingly.
7410 The fuzz in units can cause problems with relative items. For
7411 example, `2003-07-31 -1 month' might evaluate to 2003-07-01, because
7412 2003-06-31 is an invalid date. To determine the previous month more
7413 reliably, you can ask for the month before the 15th of the current
7417 Thu, 31 Jul 2003 13:02:39 -0700
7418 $ date --date='-1 month' +'Last month was %B?'
7419 Last month was July?
7420 $ date --date="$(date +%Y-%m-15) -1 month" +'Last month was %B!'
7421 Last month was June!
7423 Also, take care when manipulating dates around clock changes such as
7424 daylight saving leaps. In a few cases these have added or subtracted
7425 as much as 24 hours from the clock, so it is often wise to adopt
7426 universal time by setting the `TZ' environment variable to `UTC0'
7427 before embarking on calendrical calculations.
7430 File: tar.info, Node: Pure numbers in date strings, Next: Seconds since the Epoch, Prev: Relative items in date strings, Up: Date input formats
7432 7.7 Pure numbers in date strings
7433 ================================
7435 The precise interpretation of a pure decimal number depends on the
7436 context in the date string.
7438 If the decimal number is of the form YYYYMMDD and no other calendar
7439 date item (*note Calendar date items::) appears before it in the date
7440 string, then YYYY is read as the year, MM as the month number and DD as
7441 the day of the month, for the specified calendar date.
7443 If the decimal number is of the form HHMM and no other time of day
7444 item appears before it in the date string, then HH is read as the hour
7445 of the day and MM as the minute of the hour, for the specified time of
7446 day. MM can also be omitted.
7448 If both a calendar date and a time of day appear to the left of a
7449 number in the date string, but no relative item, then the number
7453 File: tar.info, Node: Seconds since the Epoch, Next: Specifying time zone rules, Prev: Pure numbers in date strings, Up: Date input formats
7455 7.8 Seconds since the Epoch
7456 ===========================
7458 If you precede a number with `@', it represents an internal time stamp
7459 as a count of seconds. The number can contain an internal decimal
7460 point (either `.' or `,'); any excess precision not supported by the
7461 internal representation is truncated toward minus infinity. Such a
7462 number cannot be combined with any other date item, as it specifies a
7463 complete time stamp.
7465 Internally, computer times are represented as a count of seconds
7466 since an epoch--a well-defined point of time. On GNU and POSIX
7467 systems, the epoch is 1970-01-01 00:00:00 UTC, so `@0' represents this
7468 time, `@1' represents 1970-01-01 00:00:01 UTC, and so forth. GNU and
7469 most other POSIX-compliant systems support such times as an extension
7470 to POSIX, using negative counts, so that `@-1' represents 1969-12-31
7473 Traditional Unix systems count seconds with 32-bit two's-complement
7474 integers and can represent times from 1901-12-13 20:45:52 through
7475 2038-01-19 03:14:07 UTC. More modern systems use 64-bit counts of
7476 seconds with nanosecond subcounts, and can represent all the times in
7477 the known lifetime of the universe to a resolution of 1 nanosecond.
7479 On most hosts, these counts ignore the presence of leap seconds.
7480 For example, on most hosts `@915148799' represents 1998-12-31 23:59:59
7481 UTC, `@915148800' represents 1999-01-01 00:00:00 UTC, and there is no
7482 way to represent the intervening leap second 1998-12-31 23:59:60 UTC.
7485 File: tar.info, Node: Specifying time zone rules, Next: Authors of get_date, Prev: Seconds since the Epoch, Up: Date input formats
7487 7.9 Specifying time zone rules
7488 ==============================
7490 Normally, dates are interpreted using the rules of the current time
7491 zone, which in turn are specified by the `TZ' environment variable, or
7492 by a system default if `TZ' is not set. To specify a different set of
7493 default time zone rules that apply just to one date, start the date
7494 with a string of the form `TZ="RULE"'. The two quote characters (`"')
7495 must be present in the date, and any quotes or backslashes within RULE
7496 must be escaped by a backslash.
7498 For example, with the GNU `date' command you can answer the question
7499 "What time is it in New York when a Paris clock shows 6:30am on October
7500 31, 2004?" by using a date beginning with `TZ="Europe/Paris"' as shown
7501 in the following shell transcript:
7503 $ export TZ="America/New_York"
7504 $ date --date='TZ="Europe/Paris" 2004-10-31 06:30'
7505 Sun Oct 31 01:30:00 EDT 2004
7507 In this example, the `--date' operand begins with its own `TZ'
7508 setting, so the rest of that operand is processed according to
7509 `Europe/Paris' rules, treating the string `2004-10-31 06:30' as if it
7510 were in Paris. However, since the output of the `date' command is
7511 processed according to the overall time zone rules, it uses New York
7512 time. (Paris was normally six hours ahead of New York in 2004, but
7513 this example refers to a brief Halloween period when the gap was five
7516 A `TZ' value is a rule that typically names a location in the `tz'
7517 database (http://www.twinsun.com/tz/tz-link.htm). A recent catalog of
7518 location names appears in the TWiki Date and Time Gateway
7519 (http://twiki.org/cgi-bin/xtra/tzdate). A few non-GNU hosts require a
7520 colon before a location name in a `TZ' setting, e.g.,
7521 `TZ=":America/New_York"'.
7523 The `tz' database includes a wide variety of locations ranging from
7524 `Arctic/Longyearbyen' to `Antarctica/South_Pole', but if you are at sea
7525 and have your own private time zone, or if you are using a non-GNU host
7526 that does not support the `tz' database, you may need to use a POSIX
7527 rule instead. Simple POSIX rules like `UTC0' specify a time zone
7528 without daylight saving time; other rules can specify simple daylight
7529 saving regimes. *Note Specifying the Time Zone with `TZ': (libc)TZ
7533 File: tar.info, Node: Authors of get_date, Prev: Specifying time zone rules, Up: Date input formats
7535 7.10 Authors of `get_date'
7536 ==========================
7538 `get_date' was originally implemented by Steven M. Bellovin
7539 (<smb@research.att.com>) while at the University of North Carolina at
7540 Chapel Hill. The code was later tweaked by a couple of people on
7541 Usenet, then completely overhauled by Rich $alz (<rsalz@bbn.com>) and
7542 Jim Berets (<jberets@bbn.com>) in August, 1990. Various revisions for
7543 the GNU system were made by David MacKenzie, Jim Meyering, Paul Eggert
7546 This chapter was originally produced by Franc,ois Pinard
7547 (<pinard@iro.umontreal.ca>) from the `getdate.y' source code, and then
7548 edited by K. Berry (<kb@cs.umb.edu>).
7551 File: tar.info, Node: Formats, Next: Media, Prev: Date input formats, Up: Top
7553 8 Controlling the Archive Format
7554 ********************************
7556 Due to historical reasons, there are several formats of tar archives.
7557 All of them are based on the same principles, but have some subtle
7558 differences that often make them incompatible with each other.
7560 GNU tar is able to create and handle archives in a variety of
7561 formats. The most frequently used formats are (in alphabetical order):
7564 Format used by GNU `tar' versions up to 1.13.25. This format
7565 derived from an early POSIX standard, adding some improvements
7566 such as sparse file handling and incremental archives.
7567 Unfortunately these features were implemented in a way
7568 incompatible with other archive formats.
7570 Archives in `gnu' format are able to hold file names of unlimited
7574 Format used by GNU `tar' of versions prior to 1.12.
7577 Archive format, compatible with the V7 implementation of tar. This
7578 format imposes a number of limitations. The most important of them
7581 1. The maximum length of a file name is limited to 99 characters.
7583 2. The maximum length of a symbolic link is limited to 99
7586 3. It is impossible to store special files (block and character
7587 devices, fifos etc.)
7589 4. Maximum value of user or group ID is limited to 2097151
7592 5. V7 archives do not contain symbolic ownership information
7593 (user and group name of the file owner).
7595 This format has traditionally been used by Automake when producing
7596 Makefiles. This practice will change in the future, in the
7597 meantime, however this means that projects containing file names
7598 more than 99 characters long will not be able to use GNU `tar'
7599 1.22 and Automake prior to 1.9.
7602 Archive format defined by POSIX.1-1988 specification. It stores
7603 symbolic ownership information. It is also able to store special
7604 files. However, it imposes several restrictions as well:
7606 1. The maximum length of a file name is limited to 256
7607 characters, provided that the file name can be split at a
7608 directory separator in two parts, first of them being at most
7609 155 bytes long. So, in most cases the maximum file name
7610 length will be shorter than 256 characters.
7612 2. The maximum length of a symbolic link name is limited to 100
7615 3. Maximum size of a file the archive is able to accommodate is
7618 4. Maximum value of UID/GID is 2097151.
7620 5. Maximum number of bits in device major and minor numbers is
7624 Format used by Jo"rg Schilling `star' implementation. GNU `tar'
7625 is able to read `star' archives but currently does not produce
7629 Archive format defined by POSIX.1-2001 specification. This is the
7630 most flexible and feature-rich format. It does not impose any
7631 restrictions on file sizes or file name lengths. This format is
7632 quite recent, so not all tar implementations are able to handle it
7633 properly. However, this format is designed in such a way that any
7634 tar implementation able to read `ustar' archives will be able to
7635 read most `posix' archives as well, with the only exception that
7636 any additional information (such as long file names etc.) will in
7637 such case be extracted as plain text files along with the files it
7640 This archive format will be the default format for future versions
7644 The following table summarizes the limitations of each of these
7647 Format UID File Size File Name Devn
7648 --------------------------------------------------------------------
7649 gnu 1.8e19 Unlimited Unlimited 63
7650 oldgnu 1.8e19 Unlimited Unlimited 63
7651 v7 2097151 8GB 99 n/a
7652 ustar 2097151 8GB 256 21
7653 posix Unlimited Unlimited Unlimited Unlimited
7655 The default format for GNU `tar' is defined at compilation time.
7656 You may check it by running `tar --help', and examining the last lines
7657 of its output. Usually, GNU `tar' is configured to create archives in
7658 `gnu' format, however, future version will switch to `posix'.
7662 * Compression:: Using Less Space through Compression
7663 * Attributes:: Handling File Attributes
7664 * Portability:: Making `tar' Archives More Portable
7665 * cpio:: Comparison of `tar' and `cpio'
7668 File: tar.info, Node: Compression, Next: Attributes, Up: Formats
7670 8.1 Using Less Space through Compression
7671 ========================================
7675 * gzip:: Creating and Reading Compressed Archives
7676 * sparse:: Archiving Sparse Files
projects / tar / blob