1 \input texinfo @c -*-texinfo-*-
2 @comment %**start of header
5 @settitle GNU tar @value{VERSION}
14 @c 1. Pay attention to @FIXME{}s and @UNREVISED{}s
15 @c 2. Before creating final variant:
16 @c 2.1. Run `make check-options' to make sure all options are properly
18 @c 2.2. Run `make master-menu' (see comment before the master menu).
20 @include rendition.texi
25 @c Put everything in one index (arbitrarily chosen to be the concept index).
33 This manual is for @acronym{GNU} @command{tar} (version
34 @value{VERSION}, @value{UPDATED}), which creates and extracts files
37 Copyright @copyright{} 1992, 1994, 1995, 1996, 1997, 1999, 2000, 2001,
38 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
41 Permission is granted to copy, distribute and/or modify this document
42 under the terms of the GNU Free Documentation License, Version 1.1 or
43 any later version published by the Free Software Foundation; with no
44 Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
45 and with the Back-Cover Texts as in (a) below. A copy of the license
46 is included in the section entitled "GNU Free Documentation License".
48 (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
49 this GNU Manual. Buying copies from GNU Press supports the FSF in
50 developing GNU and promoting software freedom.''
54 @dircategory Archiving
56 * Tar: (tar). Making tape (or disk) archives.
59 @dircategory Individual utilities
61 * tar: (tar)tar invocation. Invoking @GNUTAR{}.
64 @shorttitlepage @acronym{GNU} @command{tar}
67 @title @acronym{GNU} tar: an archiver tool
68 @subtitle @value{RENDITION} @value{VERSION}, @value{UPDATED}
69 @author John Gilmore, Jay Fenlason et al.
72 @vskip 0pt plus 1filll
78 @top @acronym{GNU} tar: an archiver tool
83 @cindex archiving files
85 The first part of this master menu lists the major nodes in this Info
86 document. The rest of the menu lists all the lower level nodes.
89 @c The master menu goes here.
91 @c NOTE: To update it from within Emacs, make sure mastermenu.el is
92 @c loaded and run texinfo-master-menu.
93 @c To update it from the command line, run
104 * Date input formats::
111 * Configuring Help Summary::
114 * Free Software Needs Free Documentation::
115 * Copying This Manual::
116 * Index of Command Line Options::
120 --- The Detailed Node Listing ---
124 * Book Contents:: What this Book Contains
125 * Definitions:: Some Definitions
126 * What tar Does:: What @command{tar} Does
127 * Naming tar Archives:: How @command{tar} Archives are Named
128 * Authors:: @GNUTAR{} Authors
129 * Reports:: Reporting bugs or suggestions
131 Tutorial Introduction to @command{tar}
134 * stylistic conventions::
135 * basic tar options:: Basic @command{tar} Operations and Options
136 * frequent operations::
137 * Two Frequent Options::
138 * create:: How to Create Archives
139 * list:: How to List Archives
140 * extract:: How to Extract Members from an Archive
143 Two Frequently Used Options
149 How to Create Archives
151 * prepare for examples::
152 * Creating the archive::
161 How to Extract Members from an Archive
163 * extracting archives::
166 * extracting untrusted archives::
172 * using tar options::
180 The Three Option Styles
182 * Long Options:: Long Option Style
183 * Short Options:: Short Option Style
184 * Old Options:: Old Option Style
185 * Mixing:: Mixing Option Styles
187 All @command{tar} Options
189 * Operation Summary::
191 * Short Option Summary::
203 Advanced @GNUTAR{} Operations
212 How to Add Files to Existing Archives: @option{--append}
214 * appending files:: Appending Files to an Archive
221 Options Used by @option{--create}
223 * override:: Overriding File Metadata.
224 * Ignore Failed Read::
226 Options Used by @option{--extract}
228 * Reading:: Options to Help Read Archives
229 * Writing:: Changing How @command{tar} Writes Files
230 * Scarce:: Coping with Scarce Resources
232 Options to Help Read Archives
234 * read full records::
237 Changing How @command{tar} Writes Files
239 * Dealing with Old Files::
240 * Overwrite Old Files::
245 * Data Modification Times::
246 * Setting Access Permissions::
247 * Directory Modification Times and Permissions::
248 * Writing to Standard Output::
249 * Writing to an External Program::
252 Coping with Scarce Resources
257 Performing Backups and Restoring Files
259 * Full Dumps:: Using @command{tar} to Perform Full Dumps
260 * Incremental Dumps:: Using @command{tar} to Perform Incremental Dumps
261 * Backup Levels:: Levels of Backups
262 * Backup Parameters:: Setting Parameters for Backups and Restoration
263 * Scripted Backups:: Using the Backup Scripts
264 * Scripted Restoration:: Using the Restore Script
266 Setting Parameters for Backups and Restoration
268 * General-Purpose Variables::
269 * Magnetic Tape Control::
271 * backup-specs example:: An Example Text of @file{Backup-specs}
273 Choosing Files and Names for @command{tar}
275 * file:: Choosing the Archive's Name
276 * Selecting Archive Members::
277 * files:: Reading Names from a File
278 * exclude:: Excluding Some Files
279 * wildcards:: Wildcards Patterns and Matching
280 * quoting styles:: Ways of Quoting Special Characters in Names
281 * transform:: Modifying File and Member Names
282 * after:: Operating Only on New Files
283 * recurse:: Descending into Directories
284 * one:: Crossing File System Boundaries
286 Reading Names from a File
292 * problems with exclude::
294 Wildcards Patterns and Matching
296 * controlling pattern-matching::
298 Crossing File System Boundaries
300 * directory:: Changing Directory
301 * absolute:: Absolute File Names
305 * General date syntax:: Common rules.
306 * Calendar date items:: 19 Dec 1994.
307 * Time of day items:: 9:20pm.
308 * Time zone items:: @sc{est}, @sc{pdt}, @sc{gmt}.
309 * Day of week items:: Monday and others.
310 * Relative items in date strings:: next tuesday, 2 years ago.
311 * Pure numbers in date strings:: 19931219, 1440.
312 * Seconds since the Epoch:: @@1078100502.
313 * Specifying time zone rules:: TZ="America/New_York", TZ="UTC0".
314 * Authors of get_date:: Bellovin, Eggert, Salz, Berets, et al.
316 Controlling the Archive Format
318 * Portability:: Making @command{tar} Archives More Portable
319 * Compression:: Using Less Space through Compression
320 * Attributes:: Handling File Attributes
321 * cpio:: Comparison of @command{tar} and @command{cpio}
323 Making @command{tar} Archives More Portable
325 * Portable Names:: Portable Names
326 * dereference:: Symbolic Links
327 * old:: Old V7 Archives
328 * ustar:: Ustar Archives
329 * gnu:: GNU and old GNU format archives.
330 * posix:: @acronym{POSIX} archives
331 * Checksumming:: Checksumming Problems
332 * Large or Negative Values:: Large files, negative time stamps, etc.
333 * Other Tars:: How to Extract GNU-Specific Data Using
334 Other @command{tar} Implementations
336 @GNUTAR{} and @acronym{POSIX} @command{tar}
338 * PAX keywords:: Controlling Extended Header Keywords.
340 How to Extract GNU-Specific Data Using Other @command{tar} Implementations
342 * Split Recovery:: Members Split Between Volumes
343 * Sparse Recovery:: Sparse Members
345 Using Less Space through Compression
347 * gzip:: Creating and Reading Compressed Archives
348 * sparse:: Archiving Sparse Files
350 Tapes and Other Archive Media
352 * Device:: Device selection and switching
353 * Remote Tape Server::
354 * Common Problems and Solutions::
355 * Blocking:: Blocking
356 * Many:: Many archives on one tape
357 * Using Multiple Tapes:: Using Multiple Tapes
358 * label:: Including a Label in the Archive
364 * Format Variations:: Format Variations
365 * Blocking Factor:: The Blocking Factor of an Archive
367 Many Archives on One Tape
369 * Tape Positioning:: Tape Positions and Tape Marks
370 * mt:: The @command{mt} Utility
374 * Multi-Volume Archives:: Archives Longer than One Tape or Disk
375 * Tape Files:: Tape Files
376 * Tarcat:: Concatenate Volumes into a Single Archive
381 * Standard:: Basic Tar Format
382 * Extensions:: @acronym{GNU} Extensions to the Archive Format
383 * Sparse Formats:: Storing Sparse Files
390 * PAX 0:: PAX Format, Versions 0.0 and 0.1
391 * PAX 1:: PAX Format, Version 1.0
395 * Generate Mode:: File Generation Mode.
396 * Status Mode:: File Status Mode.
397 * Exec Mode:: Synchronous Execution mode.
401 * GNU Free Documentation License:: License for copying this manual
407 @chapter Introduction
410 and manipulates @dfn{archives} which are actually collections of
411 many other files; the program provides users with an organized and
412 systematic method for controlling a large amount of data.
413 The name ``tar'' originally came from the phrase ``Tape ARchive'', but
414 archives need not (and these days, typically do not) reside on tapes.
417 * Book Contents:: What this Book Contains
418 * Definitions:: Some Definitions
419 * What tar Does:: What @command{tar} Does
420 * Naming tar Archives:: How @command{tar} Archives are Named
421 * Authors:: @GNUTAR{} Authors
422 * Reports:: Reporting bugs or suggestions
426 @section What this Book Contains
428 The first part of this chapter introduces you to various terms that will
429 recur throughout the book. It also tells you who has worked on @GNUTAR{}
430 and its documentation, and where you should send bug reports
433 The second chapter is a tutorial (@pxref{Tutorial}) which provides a
434 gentle introduction for people who are new to using @command{tar}. It is
435 meant to be self contained, not requiring any reading from subsequent
436 chapters to make sense. It moves from topic to topic in a logical,
437 progressive order, building on information already explained.
439 Although the tutorial is paced and structured to allow beginners to
440 learn how to use @command{tar}, it is not intended solely for beginners.
441 The tutorial explains how to use the three most frequently used
442 operations (@samp{create}, @samp{list}, and @samp{extract}) as well as
443 two frequently used options (@samp{file} and @samp{verbose}). The other
444 chapters do not refer to the tutorial frequently; however, if a section
445 discusses something which is a complex variant of a basic concept, there
446 may be a cross reference to that basic concept. (The entire book,
447 including the tutorial, assumes that the reader understands some basic
448 concepts of using a Unix-type operating system; @pxref{Tutorial}.)
450 The third chapter presents the remaining five operations, and
451 information about using @command{tar} options and option syntax.
453 @FIXME{this sounds more like a @acronym{GNU} Project Manuals Concept [tm] more
454 than the reality. should think about whether this makes sense to say
455 here, or not.} The other chapters are meant to be used as a
456 reference. Each chapter presents everything that needs to be said
457 about a specific topic.
459 One of the chapters (@pxref{Date input formats}) exists in its
460 entirety in other @acronym{GNU} manuals, and is mostly self-contained.
461 In addition, one section of this manual (@pxref{Standard}) contains a
462 big quote which is taken directly from @command{tar} sources.
464 In general, we give both long and short (abbreviated) option names
465 at least once in each section where the relevant option is covered, so
466 that novice readers will become familiar with both styles. (A few
467 options have no short versions, and the relevant sections will
471 @section Some Definitions
475 The @command{tar} program is used to create and manipulate @command{tar}
476 archives. An @dfn{archive} is a single file which contains the contents
477 of many files, while still identifying the names of the files, their
478 owner(s), and so forth. (In addition, archives record access
479 permissions, user and group, size in bytes, and data modification time.
480 Some archives also record the file names in each archived directory, as
481 well as other file and directory information.) You can use @command{tar}
482 to @dfn{create} a new archive in a specified directory.
485 @cindex archive member
488 The files inside an archive are called @dfn{members}. Within this
489 manual, we use the term @dfn{file} to refer only to files accessible in
490 the normal ways (by @command{ls}, @command{cat}, and so forth), and the term
491 @dfn{member} to refer only to the members of an archive. Similarly, a
492 @dfn{file name} is the name of a file, as it resides in the file system,
493 and a @dfn{member name} is the name of an archive member within the
498 The term @dfn{extraction} refers to the process of copying an archive
499 member (or multiple members) into a file in the file system. Extracting
500 all the members of an archive is often called @dfn{extracting the
501 archive}. The term @dfn{unpack} can also be used to refer to the
502 extraction of many or all the members of an archive. Extracting an
503 archive does not destroy the archive's structure, just as creating an
504 archive does not destroy the copies of the files that exist outside of
505 the archive. You may also @dfn{list} the members in a given archive
506 (this is often thought of as ``printing'' them to the standard output,
507 or the command line), or @dfn{append} members to a pre-existing archive.
508 All of these operations can be performed using @command{tar}.
511 @section What @command{tar} Does
514 The @command{tar} program provides the ability to create @command{tar}
515 archives, as well as various other kinds of manipulation. For example,
516 you can use @command{tar} on previously created archives to extract files,
517 to store additional files, or to update or list files which were already
520 Initially, @command{tar} archives were used to store files conveniently on
521 magnetic tape. The name @command{tar} comes from this use; it stands for
522 @code{t}ape @code{ar}chiver. Despite the utility's name, @command{tar} can
523 direct its output to available devices, files, or other programs (using
524 pipes). @command{tar} may even access remote devices or files (as archives).
526 You can use @command{tar} archives in many ways. We want to stress a few
527 of them: storage, backup, and transportation.
529 @FIXME{the following table entries need a bit of work.}
532 Often, @command{tar} archives are used to store related files for
533 convenient file transfer over a network. For example, the
534 @acronym{GNU} Project distributes its software bundled into
535 @command{tar} archives, so that all the files relating to a particular
536 program (or set of related programs) can be transferred as a single
539 A magnetic tape can store several files in sequence. However, the tape
540 has no names for these files; it only knows their relative position on
541 the tape. One way to store several files on one tape and retain their
542 names is by creating a @command{tar} archive. Even when the basic transfer
543 mechanism can keep track of names, as FTP can, the nuisance of handling
544 multiple files, directories, and multiple links makes @command{tar}
547 Archive files are also used for long-term storage. You can think of
548 this as transportation from the present into the future. (It is a
549 science-fiction idiom that you can move through time as well as in
550 space; the idea here is that @command{tar} can be used to move archives in
551 all dimensions, even time!)
554 Because the archive created by @command{tar} is capable of preserving
555 file information and directory structure, @command{tar} is commonly
556 used for performing full and incremental backups of disks. A backup
557 puts a collection of files (possibly pertaining to many users and
558 projects) together on a disk or a tape. This guards against
559 accidental destruction of the information in those files.
560 @GNUTAR{} has special features that allow it to be
561 used to make incremental and full dumps of all the files in a
565 You can create an archive on one system, transfer it to another system,
566 and extract the contents there. This allows you to transport a group of
567 files from one system to another.
570 @node Naming tar Archives
571 @section How @command{tar} Archives are Named
573 Conventionally, @command{tar} archives are given names ending with
574 @samp{.tar}. This is not necessary for @command{tar} to operate properly,
575 but this manual follows that convention in order to accustom readers to
576 it and to make examples more clear.
581 Often, people refer to @command{tar} archives as ``@command{tar} files,'' and
582 archive members as ``files'' or ``entries''. For people familiar with
583 the operation of @command{tar}, this causes no difficulty. However, in
584 this manual, we consistently refer to ``archives'' and ``archive
585 members'' to make learning to use @command{tar} easier for novice users.
588 @section @GNUTAR{} Authors
590 @GNUTAR{} was originally written by John Gilmore,
591 and modified by many people. The @acronym{GNU} enhancements were
592 written by Jay Fenlason, then Joy Kendall, and the whole package has
593 been further maintained by Thomas Bushnell, n/BSG, Fran@,{c}ois
594 Pinard, Paul Eggert, and finally Sergey Poznyakoff with the help of
595 numerous and kind users.
597 We wish to stress that @command{tar} is a collective work, and owes much to
598 all those people who reported problems, offered solutions and other
599 insights, or shared their thoughts and suggestions. An impressive, yet
600 partial list of those contributors can be found in the @file{THANKS}
601 file from the @GNUTAR{} distribution.
603 @FIXME{i want all of these names mentioned, Absolutely. BUT, i'm not
604 sure i want to spell out the history in this detail, at least not for
605 the printed book. i'm just not sure it needs to be said this way.
606 i'll think about it.}
608 @FIXME{History is more important, and surely more interesting, than
609 actual names. Quoting names without history would be meaningless. FP}
611 Jay Fenlason put together a draft of a @GNUTAR{}
612 manual, borrowing notes from the original man page from John Gilmore.
613 This was withdrawn in version 1.11. Thomas Bushnell, n/BSG and Amy
614 Gorin worked on a tutorial and manual for @GNUTAR{}.
615 Fran@,{c}ois Pinard put version 1.11.8 of the manual together by
616 taking information from all these sources and merging them. Melissa
617 Weisshaus finally edited and redesigned the book to create version
618 1.12. The book for versions from 1.14 up to @value{VERSION} were edited
619 by the current maintainer, Sergey Poznyakoff.
621 For version 1.12, Daniel Hagerty contributed a great deal of technical
622 consulting. In particular, he is the primary author of @ref{Backups}.
624 In July, 2003 @GNUTAR{} was put on CVS at savannah.gnu.org
625 (see @url{http://savannah.gnu.org/projects/tar}), and
626 active development and maintenance work has started
627 again. Currently @GNUTAR{} is being maintained by Paul Eggert, Sergey
628 Poznyakoff and Jeff Bailey.
630 Support for @acronym{POSIX} archives was added by Sergey Poznyakoff.
633 @section Reporting bugs or suggestions
636 @cindex reporting bugs
637 If you find problems or have suggestions about this program or manual,
638 please report them to @file{bug-tar@@gnu.org}.
640 When reporting a bug, please be sure to include as much detail as
641 possible, in order to reproduce it. @FIXME{Be more specific, I'd
642 like to make this node as detailed as 'Bug reporting' node in Emacs
646 @chapter Tutorial Introduction to @command{tar}
648 This chapter guides you through some basic examples of three @command{tar}
649 operations: @option{--create}, @option{--list}, and @option{--extract}. If
650 you already know how to use some other version of @command{tar}, then you
651 may not need to read this chapter. This chapter omits most complicated
652 details about how @command{tar} works.
656 * stylistic conventions::
657 * basic tar options:: Basic @command{tar} Operations and Options
658 * frequent operations::
659 * Two Frequent Options::
660 * create:: How to Create Archives
661 * list:: How to List Archives
662 * extract:: How to Extract Members from an Archive
667 @section Assumptions this Tutorial Makes
669 This chapter is paced to allow beginners to learn about @command{tar}
670 slowly. At the same time, we will try to cover all the basic aspects of
671 these three operations. In order to accomplish both of these tasks, we
672 have made certain assumptions about your knowledge before reading this
673 manual, and the hardware you will be using:
677 Before you start to work through this tutorial, you should understand
678 what the terms ``archive'' and ``archive member'' mean
679 (@pxref{Definitions}). In addition, you should understand something
680 about how Unix-type operating systems work, and you should know how to
681 use some basic utilities. For example, you should know how to create,
682 list, copy, rename, edit, and delete files and directories; how to
683 change between directories; and how to figure out where you are in the
684 file system. You should have some basic understanding of directory
685 structure and how files are named according to which directory they are
686 in. You should understand concepts such as standard output and standard
687 input, what various definitions of the term ``argument'' mean, and the
688 differences between relative and absolute path names. @FIXME{and what
692 This manual assumes that you are working from your own home directory
693 (unless we state otherwise). In this tutorial, you will create a
694 directory to practice @command{tar} commands in. When we show path names,
695 we will assume that those paths are relative to your home directory.
696 For example, my home directory path is @file{/home/fsf/melissa}. All of
697 my examples are in a subdirectory of the directory named by that path
698 name; the subdirectory is called @file{practice}.
701 In general, we show examples of archives which exist on (or can be
702 written to, or worked with from) a directory on a hard disk. In most
703 cases, you could write those archives to, or work with them on any other
704 device, such as a tape drive. However, some of the later examples in
705 the tutorial and next chapter will not work on tape drives.
706 Additionally, working with tapes is much more complicated than working
707 with hard disks. For these reasons, the tutorial does not cover working
708 with tape drives. @xref{Media}, for complete information on using
709 @command{tar} archives with tape drives.
711 @FIXME{this is a cop out. need to add some simple tape drive info.}
714 @node stylistic conventions
715 @section Stylistic Conventions
717 In the examples, @samp{$} represents a typical shell prompt. It
718 precedes lines you should type; to make this more clear, those lines are
719 shown in @kbd{this font}, as opposed to lines which represent the
720 computer's response; those lines are shown in @code{this font}, or
721 sometimes @samp{like this}.
723 @c When we have lines which are too long to be
724 @c displayed in any other way, we will show them like this:
726 @node basic tar options
727 @section Basic @command{tar} Operations and Options
729 @command{tar} can take a wide variety of arguments which specify and define
730 the actions it will have on the particular set of files or the archive.
731 The main types of arguments to @command{tar} fall into one of two classes:
732 operations, and options.
734 Some arguments fall into a class called @dfn{operations}; exactly one of
735 these is both allowed and required for any instance of using @command{tar};
736 you may @emph{not} specify more than one. People sometimes speak of
737 @dfn{operating modes}. You are in a particular operating mode when you
738 have specified the operation which specifies it; there are eight
739 operations in total, and thus there are eight operating modes.
741 The other arguments fall into the class known as @dfn{options}. You are
742 not required to specify any options, and you are allowed to specify more
743 than one at a time (depending on the way you are using @command{tar} at
744 that time). Some options are used so frequently, and are so useful for
745 helping you type commands more carefully that they are effectively
746 ``required''. We will discuss them in this chapter.
748 You can write most of the @command{tar} operations and options in any
749 of three forms: long (mnemonic) form, short form, and old style. Some
750 of the operations and options have no short or ``old'' forms; however,
751 the operations and options which we will cover in this tutorial have
752 corresponding abbreviations. @FIXME{make sure this is still the case,
753 at the end}We will indicate those abbreviations appropriately to get
754 you used to seeing them. (Note that the ``old style'' option forms
755 exist in @GNUTAR{} for compatibility with Unix
756 @command{tar}. In this book we present a full discussion of this way
757 of writing options and operations (@pxref{Old Options}), and we discuss
758 the other two styles of writing options (@xref{Long Options}, and
759 @pxref{Short Options}).
761 In the examples and in the text of this tutorial, we usually use the
762 long forms of operations and options; but the ``short'' forms produce
763 the same result and can make typing long @command{tar} commands easier.
764 For example, instead of typing
767 @kbd{tar --create --verbose --file=afiles.tar apple angst aspic}
773 @kbd{tar -c -v -f afiles.tar apple angst aspic}
779 @kbd{tar -cvf afiles.tar apple angst aspic}
783 For more information on option syntax, see @ref{Advanced tar}. In
784 discussions in the text, when we name an option by its long form, we
785 also give the corresponding short option in parentheses.
787 The term, ``option'', can be confusing at times, since ``operations''
788 are often lumped in with the actual, @emph{optional} ``options'' in certain
789 general class statements. For example, we just talked about ``short and
790 long forms of options and operations''. However, experienced @command{tar}
791 users often refer to these by shorthand terms such as, ``short and long
792 options''. This term assumes that the ``operations'' are included, also.
793 Context will help you determine which definition of ``options'' to use.
795 Similarly, the term ``command'' can be confusing, as it is often used in
796 two different ways. People sometimes refer to @command{tar} ``commands''.
797 A @command{tar} @dfn{command} is the entire command line of user input
798 which tells @command{tar} what to do --- including the operation, options,
799 and any arguments (file names, pipes, other commands, etc.). However,
800 you will also sometimes hear the term ``the @command{tar} command''. When
801 the word ``command'' is used specifically like this, a person is usually
802 referring to the @command{tar} @emph{operation}, not the whole line.
803 Again, use context to figure out which of the meanings the speaker
806 @node frequent operations
807 @section The Three Most Frequently Used Operations
809 Here are the three most frequently used operations (both short and long
810 forms), as well as a brief description of their meanings. The rest of
811 this chapter will cover how to use these operations in detail. We will
812 present the rest of the operations in the next chapter.
817 Create a new @command{tar} archive.
820 List the contents of an archive.
823 Extract one or more members from an archive.
826 @node Two Frequent Options
827 @section Two Frequently Used Options
829 To understand how to run @command{tar} in the three operating modes listed
830 previously, you also need to understand how to use two of the options to
831 @command{tar}: @option{--file} (which takes an archive file as an argument)
832 and @option{--verbose}. (You are usually not @emph{required} to specify
833 either of these options when you run @command{tar}, but they can be very
834 useful in making things more clear and helping you avoid errors.)
843 @unnumberedsubsec The @option{--file} Option
846 @xopindex{file, tutorial}
847 @item --file=@var{archive-name}
848 @itemx -f @var{archive-name}
849 Specify the name of an archive file.
852 You can specify an argument for the @option{--file=@var{archive-name}} (@option{-f @var{archive-name}}) option whenever you
853 use @command{tar}; this option determines the name of the archive file
854 that @command{tar} will work on.
857 If you don't specify this argument, then @command{tar} will examine
858 the environment variable @env{TAPE}. If it is set, its value will be
859 used as the archive name. Otherwise, @command{tar} will use the
860 default archive, determined at the compile time. Usually it is
861 standard output or some physical tape drive attached to your machine
862 (you can verify what the default is by running @kbd{tar
863 --show-defaults}, @pxref{defaults}). If there is no tape drive
864 attached, or the default is not meaningful, then @command{tar} will
865 print an error message. The error message might look roughly like one
869 tar: can't open /dev/rmt8 : No such device or address
870 tar: can't open /dev/rsmt0 : I/O error
874 To avoid confusion, we recommend that you always specify an archive file
875 name by using @option{--file=@var{archive-name}} (@option{-f @var{archive-name}}) when writing your @command{tar} commands.
876 For more information on using the @option{--file=@var{archive-name}} (@option{-f @var{archive-name}}) option, see
879 @node verbose tutorial
880 @unnumberedsubsec The @option{--verbose} Option
883 @xopindex{verbose, introduced}
886 Show the files being worked on as @command{tar} is running.
889 @option{--verbose} (@option{-v}) shows details about the results of running
890 @command{tar}. This can be especially useful when the results might not be
891 obvious. For example, if you want to see the progress of @command{tar} as
892 it writes files into the archive, you can use the @option{--verbose}
893 option. In the beginning, you may find it useful to use
894 @option{--verbose} at all times; when you are more accustomed to
895 @command{tar}, you will likely want to use it at certain times but not at
896 others. We will use @option{--verbose} at times to help make something
897 clear, and we will give many examples both using and not using
898 @option{--verbose} to show the differences.
900 Each instance of @option{--verbose} on the command line increases the
901 verbosity level by one, so if you need more details on the output,
904 When reading archives (@option{--list}, @option{--extract},
905 @option{--diff}), @command{tar} by default prints only the names of
906 the members being extracted. Using @option{--verbose} will show a full,
907 @command{ls} style member listing.
909 In contrast, when writing archives (@option{--create}, @option{--append},
910 @option{--update}), @command{tar} does not print file names by
911 default. So, a single @option{--verbose} option shows the file names
912 being added to the archive, while two @option{--verbose} options
913 enable the full listing.
915 For example, to create an archive in verbose mode:
918 $ @kbd{tar -cvf afiles.tar apple angst aspic}
925 Creating the same archive with the verbosity level 2 could give:
928 $ @kbd{tar -cvvf afiles.tar apple angst aspic}
929 -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
930 -rw-r--r-- gray/staff 11481 2006-06-09 12:06 angst
931 -rw-r--r-- gray/staff 23152 2006-06-09 12:06 aspic
935 This works equally well using short or long forms of options. Using
936 long forms, you would simply write out the mnemonic form of the option
940 $ @kbd{tar --create --verbose --verbose @dots{}}
944 Note that you must double the hyphens properly each time.
946 Later in the tutorial, we will give examples using @w{@option{--verbose
949 @anchor{verbose member listing}
950 The full output consists of six fields:
953 @item File type and permissions in symbolic form.
954 These are displayed in the same format as the first column of
955 @command{ls -l} output (@pxref{What information is listed,
956 format=verbose, Verbose listing, fileutils, GNU file utilities}).
958 @item Owner name and group separated by a slash character.
959 If these data are not available (for example, when listing a @samp{v7} format
960 archive), numeric ID values are printed instead.
962 @item Size of the file, in bytes.
964 @item File modification date in ISO 8601 format.
966 @item File modification time.
969 If the name contains any special characters (white space, newlines,
970 etc.) these are displayed in an unambiguous form using so called
971 @dfn{quoting style}. For the detailed discussion of available styles
972 and on how to use them, see @ref{quoting styles}.
974 Depending on the file type, the name can be followed by some
975 additional information, described in the following table:
978 @item -> @var{link-name}
979 The file or archive member is a @dfn{symbolic link} and
980 @var{link-name} is the name of file it links to.
982 @item link to @var{link-name}
983 The file or archive member is a @dfn{hard link} and @var{link-name} is
984 the name of file it links to.
987 The archive member is an old GNU format long link. You will normally
991 The archive member is an old GNU format long name. You will normally
994 @item --Volume Header--
995 The archive member is a GNU @dfn{volume header} (@pxref{Tape Files}).
997 @item --Continued at byte @var{n}--
998 Encountered only at the beginning of a multi-volume archive
999 (@pxref{Using Multiple Tapes}). This archive member is a continuation
1000 from the previous volume. The number @var{n} gives the offset where
1001 the original file was split.
1003 @item unknown file type @var{c}
1004 An archive member of unknown type. @var{c} is the type character from
1005 the archive header. If you encounter such a message, it means that
1006 either your archive contains proprietary member types @GNUTAR{} is not
1007 able to handle, or the archive is corrupted.
1012 For example, here is an archive listing containing most of the special
1013 suffixes explained above:
1017 V--------- 0/0 1536 2006-06-09 13:07 MyVolume--Volume Header--
1018 -rw-r--r-- gray/staff 456783 2006-06-09 12:06 aspic--Continued at
1020 -rw-r--r-- gray/staff 62373 2006-06-09 12:06 apple
1021 lrwxrwxrwx gray/staff 0 2006-06-09 13:01 angst -> apple
1022 -rw-r--r-- gray/staff 35793 2006-06-09 12:06 blues
1023 hrw-r--r-- gray/staff 0 2006-06-09 12:06 music link to blues
1031 @unnumberedsubsec Getting Help: Using the @option{--help} Option
1037 The @option{--help} option to @command{tar} prints out a very brief list of
1038 all operations and option available for the current version of
1039 @command{tar} available on your system.
1043 @section How to Create Archives
1046 @cindex Creation of the archive
1047 @cindex Archive, creation of
1048 One of the basic operations of @command{tar} is @option{--create} (@option{-c}), which
1049 you use to create a @command{tar} archive. We will explain
1050 @option{--create} first because, in order to learn about the other
1051 operations, you will find it useful to have an archive available to
1054 To make this easier, in this section you will first create a directory
1055 containing three files. Then, we will show you how to create an
1056 @emph{archive} (inside the new directory). Both the directory, and
1057 the archive are specifically for you to practice on. The rest of this
1058 chapter and the next chapter will show many examples using this
1059 directory and the files you will create: some of those files may be
1060 other directories and other archives.
1062 The three files you will archive in this example are called
1063 @file{blues}, @file{folk}, and @file{jazz}. The archive is called
1064 @file{collection.tar}.
1066 This section will proceed slowly, detailing how to use @option{--create}
1067 in @code{verbose} mode, and showing examples using both short and long
1068 forms. In the rest of the tutorial, and in the examples in the next
1069 chapter, we will proceed at a slightly quicker pace. This section
1070 moves more slowly to allow beginning users to understand how
1071 @command{tar} works.
1074 * prepare for examples::
1075 * Creating the archive::
1081 @node prepare for examples
1082 @subsection Preparing a Practice Directory for Examples
1084 To follow along with this and future examples, create a new directory
1085 called @file{practice} containing files called @file{blues}, @file{folk}
1086 and @file{jazz}. The files can contain any information you like:
1087 ideally, they should contain information which relates to their names,
1088 and be of different lengths. Our examples assume that @file{practice}
1089 is a subdirectory of your home directory.
1091 Now @command{cd} to the directory named @file{practice}; @file{practice}
1092 is now your @dfn{working directory}. (@emph{Please note}: Although
1093 the full path name of this directory is
1094 @file{/@var{homedir}/practice}, in our examples we will refer to
1095 this directory as @file{practice}; the @var{homedir} is presumed.
1097 In general, you should check that the files to be archived exist where
1098 you think they do (in the working directory) by running @command{ls}.
1099 Because you just created the directory and the files and have changed to
1100 that directory, you probably don't need to do that this time.
1102 It is very important to make sure there isn't already a file in the
1103 working directory with the archive name you intend to use (in this case,
1104 @samp{collection.tar}), or that you don't care about its contents.
1105 Whenever you use @samp{create}, @command{tar} will erase the current
1106 contents of the file named by @option{--file=@var{archive-name}} (@option{-f @var{archive-name}}) if it exists. @command{tar}
1107 will not tell you if you are about to overwrite an archive unless you
1108 specify an option which does this (@pxref{backup}, for the
1109 information on how to do so). To add files to an existing archive,
1110 you need to use a different option, such as @option{--append} (@option{-r}); see
1111 @ref{append} for information on how to do this.
1113 @node Creating the archive
1114 @subsection Creating the Archive
1116 @xopindex{create, introduced}
1117 To place the files @file{blues}, @file{folk}, and @file{jazz} into an
1118 archive named @file{collection.tar}, use the following command:
1121 $ @kbd{tar --create --file=collection.tar blues folk jazz}
1124 The order of the arguments is not very important, @emph{when using long
1125 option forms}. You could also say:
1128 $ @kbd{tar blues --create folk --file=collection.tar jazz}
1132 However, you can see that this order is harder to understand; this is
1133 why we will list the arguments in the order that makes the commands
1134 easiest to understand (and we encourage you to do the same when you use
1135 @command{tar}, to avoid errors).
1137 Note that the sequence
1138 @option{--file=@-collection.tar} is considered to be @emph{one} argument.
1139 If you substituted any other string of characters for
1140 @kbd{collection.tar}, then that string would become the name of the
1141 archive file you create.
1143 The order of the options becomes more important when you begin to use
1144 short forms. With short forms, if you type commands in the wrong order
1145 (even if you type them correctly in all other ways), you may end up with
1146 results you don't expect. For this reason, it is a good idea to get
1147 into the habit of typing options in the order that makes inherent sense.
1148 @xref{short create}, for more information on this.
1150 In this example, you type the command as shown above: @option{--create}
1151 is the operation which creates the new archive
1152 (@file{collection.tar}), and @option{--file} is the option which lets
1153 you give it the name you chose. The files, @file{blues}, @file{folk},
1154 and @file{jazz}, are now members of the archive, @file{collection.tar}
1155 (they are @dfn{file name arguments} to the @option{--create} operation.
1156 @xref{Choosing}, for the detailed discussion on these.) Now that they are
1157 in the archive, they are called @emph{archive members}, not files.
1158 (@pxref{Definitions,members}).
1160 When you create an archive, you @emph{must} specify which files you
1161 want placed in the archive. If you do not specify any archive
1162 members, @GNUTAR{} will complain.
1164 If you now list the contents of the working directory (@command{ls}), you will
1165 find the archive file listed as well as the files you saw previously:
1168 blues folk jazz collection.tar
1172 Creating the archive @samp{collection.tar} did not destroy the copies of
1173 the files in the directory.
1175 Keep in mind that if you don't indicate an operation, @command{tar} will not
1176 run and will prompt you for one. If you don't name any files, @command{tar}
1177 will complain. You must have write access to the working directory,
1178 or else you will not be able to create an archive in that directory.
1180 @emph{Caution}: Do not attempt to use @option{--create} (@option{-c}) to add files to
1181 an existing archive; it will delete the archive and write a new one.
1182 Use @option{--append} (@option{-r}) instead. @xref{append}.
1184 @node create verbose
1185 @subsection Running @option{--create} with @option{--verbose}
1187 @xopindex{create, using with @option{--verbose}}
1188 @xopindex{verbose, using with @option{--create}}
1189 If you include the @option{--verbose} (@option{-v}) option on the command line,
1190 @command{tar} will list the files it is acting on as it is working. In
1191 verbose mode, the @code{create} example above would appear as:
1194 $ @kbd{tar --create --verbose --file=collection.tar blues folk jazz}
1200 This example is just like the example we showed which did not use
1201 @option{--verbose}, except that @command{tar} generated the remaining lines
1203 (note the different font styles).
1209 In the rest of the examples in this chapter, we will frequently use
1210 @code{verbose} mode so we can show actions or @command{tar} responses that
1211 you would otherwise not see, and which are important for you to
1215 @subsection Short Forms with @samp{create}
1217 As we said before, the @option{--create} (@option{-c}) operation is one of the most
1218 basic uses of @command{tar}, and you will use it countless times.
1219 Eventually, you will probably want to use abbreviated (or ``short'')
1220 forms of options. A full discussion of the three different forms that
1221 options can take appears in @ref{Styles}; for now, here is what the
1222 previous example (including the @option{--verbose} (@option{-v}) option) looks like
1223 using short option forms:
1226 $ @kbd{tar -cvf collection.tar blues folk jazz}
1233 As you can see, the system responds the same no matter whether you use
1234 long or short option forms.
1236 @FIXME{i don't like how this is worded:} One difference between using
1237 short and long option forms is that, although the exact placement of
1238 arguments following options is no more specific when using short forms,
1239 it is easier to become confused and make a mistake when using short
1240 forms. For example, suppose you attempted the above example in the
1244 $ @kbd{tar -cfv collection.tar blues folk jazz}
1248 In this case, @command{tar} will make an archive file called @file{v},
1249 containing the files @file{blues}, @file{folk}, and @file{jazz}, because
1250 the @samp{v} is the closest ``file name'' to the @option{-f} option, and
1251 is thus taken to be the chosen archive file name. @command{tar} will try
1252 to add a file called @file{collection.tar} to the @file{v} archive file;
1253 if the file @file{collection.tar} did not already exist, @command{tar} will
1254 report an error indicating that this file does not exist. If the file
1255 @file{collection.tar} does already exist (e.g., from a previous command
1256 you may have run), then @command{tar} will add this file to the archive.
1257 Because the @option{-v} option did not get registered, @command{tar} will not
1258 run under @samp{verbose} mode, and will not report its progress.
1260 The end result is that you may be quite confused about what happened,
1261 and possibly overwrite a file. To illustrate this further, we will show
1262 you how an example we showed previously would look using short forms.
1267 $ @kbd{tar blues --create folk --file=collection.tar jazz}
1271 is confusing as it is. When shown using short forms, however, it
1272 becomes much more so:
1275 $ @kbd{tar blues -c folk -f collection.tar jazz}
1279 It would be very easy to put the wrong string of characters
1280 immediately following the @option{-f}, but doing that could sacrifice
1283 For this reason, we recommend that you pay very careful attention to
1284 the order of options and placement of file and archive names,
1285 especially when using short option forms. Not having the option name
1286 written out mnemonically can affect how well you remember which option
1287 does what, and therefore where different names have to be placed.
1290 @subsection Archiving Directories
1292 @cindex Archiving Directories
1293 @cindex Directories, Archiving
1294 You can archive a directory by specifying its directory name as a
1295 file name argument to @command{tar}. The files in the directory will be
1296 archived relative to the working directory, and the directory will be
1297 re-created along with its contents when the archive is extracted.
1299 To archive a directory, first move to its superior directory. If you
1300 have followed the previous instructions in this tutorial, you should
1309 This will put you into the directory which contains @file{practice},
1310 i.e., your home directory. Once in the superior directory, you can
1311 specify the subdirectory, @file{practice}, as a file name argument. To
1312 store @file{practice} in the new archive file @file{music.tar}, type:
1315 $ @kbd{tar --create --verbose --file=music.tar practice}
1319 @command{tar} should output:
1326 practice/collection.tar
1329 Note that the archive thus created is not in the subdirectory
1330 @file{practice}, but rather in the current working directory---the
1331 directory from which @command{tar} was invoked. Before trying to archive a
1332 directory from its superior directory, you should make sure you have
1333 write access to the superior directory itself, not only the directory
1334 you are trying archive with @command{tar}. For example, you will probably
1335 not be able to store your home directory in an archive by invoking
1336 @command{tar} from the root directory; @xref{absolute}. (Note
1337 also that @file{collection.tar}, the original archive file, has itself
1338 been archived. @command{tar} will accept any file as a file to be
1339 archived, regardless of its content. When @file{music.tar} is
1340 extracted, the archive file @file{collection.tar} will be re-written
1341 into the file system).
1343 If you give @command{tar} a command such as
1346 $ @kbd{tar --create --file=foo.tar .}
1350 @command{tar} will report @samp{tar: ./foo.tar is the archive; not
1351 dumped}. This happens because @command{tar} creates the archive
1352 @file{foo.tar} in the current directory before putting any files into
1353 it. Then, when @command{tar} attempts to add all the files in the
1354 directory @file{.} to the archive, it notices that the file
1355 @file{./foo.tar} is the same as the archive @file{foo.tar}, and skips
1356 it. (It makes no sense to put an archive into itself.) @GNUTAR{}
1357 will continue in this case, and create the archive
1358 normally, except for the exclusion of that one file. (@emph{Please
1359 note:} Other implementations of @command{tar} may not be so clever;
1360 they will enter an infinite loop when this happens, so you should not
1361 depend on this behavior unless you are certain you are running
1362 @GNUTAR{}. In general, it is wise to always place the archive outside
1363 of the directory being dumped.
1366 @section How to List Archives
1369 Frequently, you will find yourself wanting to determine exactly what a
1370 particular archive contains. You can use the @option{--list}
1371 (@option{-t}) operation to get the member names as they currently
1372 appear in the archive, as well as various attributes of the files at
1373 the time they were archived. For example, you can examine the archive
1374 @file{collection.tar} that you created in the last section with the
1378 $ @kbd{tar --list --file=collection.tar}
1382 The output of @command{tar} would then be:
1391 The archive @file{bfiles.tar} would list as follows:
1400 Be sure to use a @option{--file=@var{archive-name}} (@option{-f
1401 @var{archive-name}}) option just as with @option{--create}
1402 (@option{-c}) to specify the name of the archive.
1404 @xopindex{list, using with @option{--verbose}}
1405 @xopindex{verbose, using with @option{--list}}
1406 If you use the @option{--verbose} (@option{-v}) option with
1407 @option{--list}, then @command{tar} will print out a listing
1408 reminiscent of @w{@samp{ls -l}}, showing owner, file size, and so
1409 forth. This output is described in detail in @ref{verbose member listing}.
1411 If you had used @option{--verbose} (@option{-v}) mode, the example
1412 above would look like:
1415 $ @kbd{tar --list --verbose --file=collection.tar folk}
1416 -rw-r--r-- myself user 62 1990-05-23 10:55 folk
1419 @cindex listing member and file names
1420 @anchor{listing member and file names}
1421 It is important to notice that the output of @kbd{tar --list
1422 --verbose} does not necessarily match that produced by @kbd{tar
1423 --create --verbose} while creating the archive. It is because
1424 @GNUTAR{}, unless told explicitly not to do so, removes some directory
1425 prefixes from file names before storing them in the archive
1426 (@xref{absolute}, for more information). In other
1427 words, in verbose mode @GNUTAR{} shows @dfn{file names} when creating
1428 an archive and @dfn{member names} when listing it. Consider this
1433 $ @kbd{tar cfv archive /etc/mail}
1434 tar: Removing leading `/' from member names
1436 /etc/mail/sendmail.cf
1438 $ @kbd{tar tf archive}
1440 etc/mail/sendmail.cf
1445 @opindex show-stored-names
1446 This default behavior can sometimes be inconvenient. You can force
1447 @GNUTAR{} show member names when creating archive by supplying
1448 @option{--show-stored-names} option.
1451 @item --show-stored-names
1452 Print member (as opposed to @emph{file}) names when creating the archive.
1455 @cindex File name arguments, using @option{--list} with
1456 @xopindex{list, using with file name arguments}
1457 You can specify one or more individual member names as arguments when
1458 using @samp{list}. In this case, @command{tar} will only list the
1459 names of members you identify. For example, @w{@kbd{tar --list
1460 --file=afiles.tar apple}} would only print @file{apple}.
1462 Because @command{tar} preserves paths, file names must be specified as
1463 they appear in the archive (i.e., relative to the directory from which
1464 the archive was created). Therefore, it is essential when specifying
1465 member names to @command{tar} that you give the exact member names.
1466 For example, @w{@kbd{tar --list --file=bfiles.tar birds}} would produce an
1467 error message something like @samp{tar: birds: Not found in archive},
1468 because there is no member named @file{birds}, only one named
1469 @file{./birds}. While the names @file{birds} and @file{./birds} name
1470 the same file, @emph{member} names by default are compared verbatim.
1472 However, @w{@kbd{tar --list --file=bfiles.tar baboon}} would respond
1473 with @file{baboon}, because this exact member name is in the archive file
1474 @file{bfiles.tar}. If you are not sure of the exact file name,
1475 use @dfn{globbing patterns}, for example:
1478 $ @kbd{tar --list --file=bfiles.tar --wildcards '*b*'}
1482 will list all members whose name contains @samp{b}. @xref{wildcards},
1483 for a detailed discussion of globbing patterns and related
1484 @command{tar} command line options.
1491 @unnumberedsubsec Listing the Contents of a Stored Directory
1493 To get information about the contents of an archived directory,
1494 use the directory name as a file name argument in conjunction with
1495 @option{--list} (@option{-t}). To find out file attributes, include the
1496 @option{--verbose} (@option{-v}) option.
1498 For example, to find out about files in the directory @file{practice}, in
1499 the archive file @file{music.tar}, type:
1502 $ @kbd{tar --list --verbose --file=music.tar practice}
1505 @command{tar} responds:
1508 drwxrwxrwx myself user 0 1990-05-31 21:49 practice/
1509 -rw-r--r-- myself user 42 1990-05-21 13:29 practice/blues
1510 -rw-r--r-- myself user 62 1990-05-23 10:55 practice/folk
1511 -rw-r--r-- myself user 40 1990-05-21 13:30 practice/jazz
1512 -rw-r--r-- myself user 10240 1990-05-31 21:49 practice/collection.tar
1515 When you use a directory name as a file name argument, @command{tar} acts on
1516 all the files (including sub-directories) in that directory.
1519 @section How to Extract Members from an Archive
1522 @cindex Retrieving files from an archive
1523 @cindex Resurrecting files from an archive
1526 Creating an archive is only half the job---there is no point in storing
1527 files in an archive if you can't retrieve them. The act of retrieving
1528 members from an archive so they can be used and manipulated as
1529 unarchived files again is called @dfn{extraction}. To extract files
1530 from an archive, use the @option{--extract} (@option{--get} or
1531 @option{-x}) operation. As with @option{--create}, specify the name
1532 of the archive with @option{--file} (@option{-f}) option. Extracting
1533 an archive does not modify the archive in any way; you can extract it
1534 multiple times if you want or need to.
1536 Using @option{--extract}, you can extract an entire archive, or specific
1537 files. The files can be directories containing other files, or not. As
1538 with @option{--create} (@option{-c}) and @option{--list} (@option{-t}), you may use the short or the
1539 long form of the operation without affecting the performance.
1542 * extracting archives::
1543 * extracting files::
1545 * extracting untrusted archives::
1546 * failing commands::
1549 @node extracting archives
1550 @subsection Extracting an Entire Archive
1552 To extract an entire archive, specify the archive file name only, with
1553 no individual file names as arguments. For example,
1556 $ @kbd{tar -xvf collection.tar}
1563 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
1564 -rw-r--r-- me user 21 1996-09-23 16:44 blues
1565 -rw-r--r-- me user 20 1996-09-23 16:44 folk
1568 @node extracting files
1569 @subsection Extracting Specific Files
1571 To extract specific archive members, give their exact member names as
1572 arguments, as printed by @option{--list} (@option{-t}). If you had
1573 mistakenly deleted one of the files you had placed in the archive
1574 @file{collection.tar} earlier (say, @file{blues}), you can extract it
1575 from the archive without changing the archive's structure. Its
1576 contents will be identical to the original file @file{blues} that you
1579 First, make sure you are in the @file{practice} directory, and list the
1580 files in the directory. Now, delete the file, @samp{blues}, and list
1581 the files in the directory again.
1583 You can now extract the member @file{blues} from the archive file
1584 @file{collection.tar} like this:
1587 $ @kbd{tar --extract --file=collection.tar blues}
1591 If you list the files in the directory again, you will see that the file
1592 @file{blues} has been restored, with its original permissions, data
1593 modification times, and owner.@footnote{This is only accidentally
1594 true, but not in general. Whereas modification times are always
1595 restored, in most cases, one has to be root for restoring the owner,
1596 and use a special option for restoring permissions. Here, it just
1597 happens that the restoring user is also the owner of the archived
1598 members, and that the current @code{umask} is compatible with original
1599 permissions.} (These parameters will be identical to those which
1600 the file had when you originally placed it in the archive; any changes
1601 you may have made before deleting the file from the file system,
1602 however, will @emph{not} have been made to the archive member.) The
1603 archive file, @samp{collection.tar}, is the same as it was before you
1604 extracted @samp{blues}. You can confirm this by running @command{tar} with
1605 @option{--list} (@option{-t}).
1607 Remember that as with other operations, specifying the exact member
1608 name is important. @w{@kbd{tar --extract --file=bfiles.tar birds}}
1609 will fail, because there is no member named @file{birds}. To extract
1610 the member named @file{./birds}, you must specify @w{@kbd{tar
1611 --extract --file=bfiles.tar ./birds}}. If you don't remember the
1612 exact member names, use @option{--list} (@option{-t}) option
1613 (@pxref{list}). You can also extract those members that match a
1614 specific @dfn{globbing pattern}. For example, to extract from
1615 @file{bfiles.tar} all files that begin with @samp{b}, no matter their
1616 directory prefix, you could type:
1619 $ @kbd{tar -x -f bfiles.tar --wildcards --no-anchored 'b*'}
1623 Here, @option{--wildcards} instructs @command{tar} to treat
1624 command line arguments as globbing patterns and @option{--no-anchored}
1625 informs it that the patterns apply to member names after any @samp{/}
1626 delimiter. The use of globbing patterns is discussed in detail in
1629 You can extract a file to standard output by combining the above options
1630 with the @option{--to-stdout} (@option{-O}) option (@pxref{Writing to Standard
1633 If you give the @option{--verbose} option, then @option{--extract}
1634 will print the names of the archive members as it extracts them.
1637 @subsection Extracting Files that are Directories
1639 Extracting directories which are members of an archive is similar to
1640 extracting other files. The main difference to be aware of is that if
1641 the extracted directory has the same name as any directory already in
1642 the working directory, then files in the extracted directory will be
1643 placed into the directory of the same name. Likewise, if there are
1644 files in the pre-existing directory with the same names as the members
1645 which you extract, the files from the extracted archive will replace
1646 the files already in the working directory (and possible
1647 subdirectories). This will happen regardless of whether or not the
1648 files in the working directory were more recent than those extracted
1649 (there exist, however, special options that alter this behavior
1652 However, if a file was stored with a directory name as part of its file
1653 name, and that directory does not exist under the working directory when
1654 the file is extracted, @command{tar} will create the directory.
1656 We can demonstrate how to use @option{--extract} to extract a directory
1657 file with an example. Change to the @file{practice} directory if you
1658 weren't there, and remove the files @file{folk} and @file{jazz}. Then,
1659 go back to the parent directory and extract the archive
1660 @file{music.tar}. You may either extract the entire archive, or you may
1661 extract only the files you just deleted. To extract the entire archive,
1662 don't give any file names as arguments after the archive name
1663 @file{music.tar}. To extract only the files you deleted, use the
1667 $ @kbd{tar -xvf music.tar practice/folk practice/jazz}
1673 If you were to specify two @option{--verbose} (@option{-v}) options, @command{tar}
1674 would have displayed more detail about the extracted files, as shown
1675 in the example below:
1678 $ @kbd{tar -xvvf music.tar practice/folk practice/jazz}
1679 -rw-r--r-- me user 28 1996-10-18 16:31 practice/jazz
1680 -rw-r--r-- me user 20 1996-09-23 16:44 practice/folk
1684 Because you created the directory with @file{practice} as part of the
1685 file names of each of the files by archiving the @file{practice}
1686 directory as @file{practice}, you must give @file{practice} as part
1687 of the file names when you extract those files from the archive.
1689 @node extracting untrusted archives
1690 @subsection Extracting Archives from Untrusted Sources
1692 Extracting files from archives can overwrite files that already exist.
1693 If you receive an archive from an untrusted source, you should make a
1694 new directory and extract into that directory, so that you don't have
1695 to worry about the extraction overwriting one of your existing files.
1696 For example, if @file{untrusted.tar} came from somewhere else on the
1697 Internet, and you don't necessarily trust its contents, you can
1698 extract it as follows:
1701 $ @kbd{mkdir newdir}
1703 $ @kbd{tar -xvf ../untrusted.tar}
1706 It is also a good practice to examine contents of the archive
1707 before extracting it, using @option{--list} (@option{-t}) option, possibly combined
1708 with @option{--verbose} (@option{-v}).
1710 @node failing commands
1711 @subsection Commands That Will Fail
1713 Here are some sample commands you might try which will not work, and why
1716 If you try to use this command,
1719 $ @kbd{tar -xvf music.tar folk jazz}
1723 you will get the following response:
1726 tar: folk: Not found in archive
1727 tar: jazz: Not found in archive
1732 This is because these files were not originally @emph{in} the parent
1733 directory @file{..}, where the archive is located; they were in the
1734 @file{practice} directory, and their file names reflect this:
1737 $ @kbd{tar -tvf music.tar}
1743 @FIXME{make sure the above works when going through the examples in
1747 Likewise, if you try to use this command,
1750 $ @kbd{tar -tvf music.tar folk jazz}
1754 you would get a similar response. Members with those names are not in the
1755 archive. You must use the correct member names, or wildcards, in order
1756 to extract the files from the archive.
1758 If you have forgotten the correct names of the files in the archive,
1759 use @w{@kbd{tar --list --verbose}} to list them correctly.
1761 @FIXME{more examples, here? hag thinks it's a good idea.}
1764 @section Going Further Ahead in this Manual
1766 @FIXME{need to write up a node here about the things that are going to
1767 be in the rest of the manual.}
1769 @node tar invocation
1770 @chapter Invoking @GNUTAR{}
1773 This chapter is about how one invokes the @GNUTAR{}
1774 command, from the command synopsis (@pxref{Synopsis}). There are
1775 numerous options, and many styles for writing them. One mandatory
1776 option specifies the operation @command{tar} should perform
1777 (@pxref{Operation Summary}), other options are meant to detail how
1778 this operation should be performed (@pxref{Option Summary}).
1779 Non-option arguments are not always interpreted the same way,
1780 depending on what the operation is.
1782 You will find in this chapter everything about option styles and rules for
1783 writing them (@pxref{Styles}). On the other hand, operations and options
1784 are fully described elsewhere, in other chapters. Here, you will find
1785 only synthetic descriptions for operations and options, together with
1786 pointers to other parts of the @command{tar} manual.
1788 Some options are so special they are fully described right in this
1789 chapter. They have the effect of inhibiting the normal operation of
1790 @command{tar} or else, they globally alter the amount of feedback the user
1791 receives about what is going on. These are the @option{--help} and
1792 @option{--version} (@pxref{help}), @option{--verbose} (@pxref{verbose})
1793 and @option{--interactive} options (@pxref{interactive}).
1797 * using tar options::
1807 @section General Synopsis of @command{tar}
1809 The @GNUTAR{} program is invoked as either one of:
1812 @kbd{tar @var{option}@dots{} [@var{name}]@dots{}}
1813 @kbd{tar @var{letter}@dots{} [@var{argument}]@dots{} [@var{option}]@dots{} [@var{name}]@dots{}}
1816 The second form is for when old options are being used.
1818 You can use @command{tar} to store files in an archive, to extract them from
1819 an archive, and to do other types of archive manipulation. The primary
1820 argument to @command{tar}, which is called the @dfn{operation}, specifies
1821 which action to take. The other arguments to @command{tar} are either
1822 @dfn{options}, which change the way @command{tar} performs an operation,
1823 or file names or archive members, which specify the files or members
1824 @command{tar} is to act on.
1826 You can actually type in arguments in any order, even if in this manual
1827 the options always precede the other arguments, to make examples easier
1828 to understand. Further, the option stating the main operation mode
1829 (the @command{tar} main command) is usually given first.
1831 Each @var{name} in the synopsis above is interpreted as an archive member
1832 name when the main command is one of @option{--compare}
1833 (@option{--diff}, @option{-d}), @option{--delete}, @option{--extract}
1834 (@option{--get}, @option{-x}), @option{--list} (@option{-t}) or
1835 @option{--update} (@option{-u}). When naming archive members, you
1836 must give the exact name of the member in the archive, as it is
1837 printed by @option{--list}. For @option{--append} (@option{-r}) and
1838 @option{--create} (@option{-c}), these @var{name} arguments specify
1839 the names of either files or directory hierarchies to place in the archive.
1840 These files or hierarchies should already exist in the file system,
1841 prior to the execution of the @command{tar} command.
1843 @command{tar} interprets relative file names as being relative to the
1844 working directory. @command{tar} will make all file names relative
1845 (by removing leading slashes when archiving or restoring files),
1846 unless you specify otherwise (using the @option{--absolute-names}
1847 option). @xref{absolute}, for more information about
1848 @option{--absolute-names}.
1850 If you give the name of a directory as either a file name or a member
1851 name, then @command{tar} acts recursively on all the files and directories
1852 beneath that directory. For example, the name @file{/} identifies all
1853 the files in the file system to @command{tar}.
1855 The distinction between file names and archive member names is especially
1856 important when shell globbing is used, and sometimes a source of confusion
1857 for newcomers. @xref{wildcards}, for more information about globbing.
1858 The problem is that shells may only glob using existing files in the
1859 file system. Only @command{tar} itself may glob on archive members, so when
1860 needed, you must ensure that wildcard characters reach @command{tar} without
1861 being interpreted by the shell first. Using a backslash before @samp{*}
1862 or @samp{?}, or putting the whole argument between quotes, is usually
1863 sufficient for this.
1865 Even if @var{name}s are often specified on the command line, they
1866 can also be read from a text file in the file system, using the
1867 @option{--files-from=@var{file-of-names}} (@option{-T @var{file-of-names}}) option.
1869 If you don't use any file name arguments, @option{--append} (@option{-r}),
1870 @option{--delete} and @option{--concatenate} (@option{--catenate},
1871 @option{-A}) will do nothing, while @option{--create} (@option{-c})
1872 will usually yield a diagnostic and inhibit @command{tar} execution.
1873 The other operations of @command{tar} (@option{--list},
1874 @option{--extract}, @option{--compare}, and @option{--update})
1875 will act on the entire contents of the archive.
1878 @cindex return status
1879 Besides successful exits, @GNUTAR{} may fail for
1880 many reasons. Some reasons correspond to bad usage, that is, when the
1881 @command{tar} command is improperly written. Errors may be
1882 encountered later, while encountering an error processing the archive
1883 or the files. Some errors are recoverable, in which case the failure
1884 is delayed until @command{tar} has completed all its work. Some
1885 errors are such that it would not meaningful, or at least risky, to
1886 continue processing: @command{tar} then aborts processing immediately.
1887 All abnormal exits, whether immediate or delayed, should always be
1888 clearly diagnosed on @code{stderr}, after a line stating the nature of
1891 Possible exit codes of @GNUTAR{} are summarized in the following
1896 @samp{Successful termination}.
1899 @samp{Some files differ}. If tar was invoked with @option{--compare}
1900 (@option{--diff}, @option{-d}) command line option, this means that
1901 some files in the archive differ from their disk counterparts
1902 (@pxref{compare}). If tar was given @option{--create},
1903 @option{--append} or @option{--update} option, this exit code means
1904 that some files were changed while being archived and so the resulting
1905 archive does not contain the exact copy of the file set.
1908 @samp{Fatal error}. This means that some fatal, unrecoverable error
1912 If @command{tar} has invoked a subprocess and that subprocess exited with a
1913 nonzero exit code, @command{tar} exits with that code as well.
1914 This can happen, for example, if @command{tar} was given some
1915 compression option (@pxref{gzip}) and the external compressor program
1916 failed. Another example is @command{rmt} failure during backup to the
1917 remote device (@pxref{Remote Tape Server}).
1919 @node using tar options
1920 @section Using @command{tar} Options
1922 @GNUTAR{} has a total of eight operating modes which
1923 allow you to perform a variety of tasks. You are required to choose
1924 one operating mode each time you employ the @command{tar} program by
1925 specifying one, and only one operation as an argument to the
1926 @command{tar} command (two lists of four operations each may be found
1927 at @ref{frequent operations} and @ref{Operations}). Depending on
1928 circumstances, you may also wish to customize how the chosen operating
1929 mode behaves. For example, you may wish to change the way the output
1930 looks, or the format of the files that you wish to archive may require
1931 you to do something special in order to make the archive look right.
1933 You can customize and control @command{tar}'s performance by running
1934 @command{tar} with one or more options (such as @option{--verbose}
1935 (@option{-v}), which we used in the tutorial). As we said in the
1936 tutorial, @dfn{options} are arguments to @command{tar} which are (as
1937 their name suggests) optional. Depending on the operating mode, you
1938 may specify one or more options. Different options will have different
1939 effects, but in general they all change details of the operation, such
1940 as archive format, archive name, or level of user interaction. Some
1941 options make sense with all operating modes, while others are
1942 meaningful only with particular modes. You will likely use some
1943 options frequently, while you will only use others infrequently, or
1944 not at all. (A full list of options is available in @pxref{All Options}.)
1946 @vrindex TAR_OPTIONS, environment variable
1947 @anchor{TAR_OPTIONS}
1948 The @env{TAR_OPTIONS} environment variable specifies default options to
1949 be placed in front of any explicit options. For example, if
1950 @code{TAR_OPTIONS} is @samp{-v --unlink-first}, @command{tar} behaves as
1951 if the two options @option{-v} and @option{--unlink-first} had been
1952 specified before any explicit options. Option specifications are
1953 separated by whitespace. A backslash escapes the next character, so it
1954 can be used to specify an option containing whitespace or a backslash.
1956 Note that @command{tar} options are case sensitive. For example, the
1957 options @option{-T} and @option{-t} are different; the first requires an
1958 argument for stating the name of a file providing a list of @var{name}s,
1959 while the second does not require an argument and is another way to
1960 write @option{--list} (@option{-t}).
1962 In addition to the eight operations, there are many options to
1963 @command{tar}, and three different styles for writing both: long (mnemonic)
1964 form, short form, and old style. These styles are discussed below.
1965 Both the options and the operations can be written in any of these three
1968 @FIXME{menu at end of this node. need to think of an actual outline
1969 for this chapter; probably do that after stuff from chapter 4 is
1973 @section The Three Option Styles
1975 There are three styles for writing operations and options to the command
1976 line invoking @command{tar}. The different styles were developed at
1977 different times during the history of @command{tar}. These styles will be
1978 presented below, from the most recent to the oldest.
1980 Some options must take an argument. (For example, @option{--file}
1981 (@option{-f})) takes the name of an archive file as an argument. If
1982 you do not supply an archive file name, @command{tar} will use a
1983 default, but this can be confusing; thus, we recommend that you always
1984 supply a specific archive file name.) Where you @emph{place} the
1985 arguments generally depends on which style of options you choose. We
1986 will detail specific information relevant to each option style in the
1987 sections on the different option styles, below. The differences are
1988 subtle, yet can often be very important; incorrect option placement
1989 can cause you to overwrite a number of important files. We urge you
1990 to note these differences, and only use the option style(s) which
1991 makes the most sense to you until you feel comfortable with the others.
1993 Some options @emph{may} take an argument. Such options may have at
1994 most long and short forms, they do not have old style equivalent. The
1995 rules for specifying an argument for such options are stricter than
1996 those for specifying mandatory arguments. Please, pay special
2000 * Long Options:: Long Option Style
2001 * Short Options:: Short Option Style
2002 * Old Options:: Old Option Style
2003 * Mixing:: Mixing Option Styles
2007 @subsection Long Option Style
2009 Each option has at least one @dfn{long} (or @dfn{mnemonic}) name starting with two
2010 dashes in a row, e.g., @option{--list}. The long names are more clear than
2011 their corresponding short or old names. It sometimes happens that a
2012 single long option has many different names which are
2013 synonymous, such as @option{--compare} and @option{--diff}. In addition,
2014 long option names can be given unique abbreviations. For example,
2015 @option{--cre} can be used in place of @option{--create} because there is no
2016 other long option which begins with @samp{cre}. (One way to find
2017 this out is by trying it and seeing what happens; if a particular
2018 abbreviation could represent more than one option, @command{tar} will tell
2019 you that that abbreviation is ambiguous and you'll know that that
2020 abbreviation won't work. You may also choose to run @samp{tar --help}
2021 to see a list of options. Be aware that if you run @command{tar} with a
2022 unique abbreviation for the long name of an option you didn't want to
2023 use, you are stuck; @command{tar} will perform the command as ordered.)
2025 Long options are meant to be obvious and easy to remember, and their
2026 meanings are generally easier to discern than those of their
2027 corresponding short options (see below). For example:
2030 $ @kbd{tar --create --verbose --blocking-factor=20 --file=/dev/rmt0}
2034 gives a fairly good set of hints about what the command does, even
2035 for those not fully acquainted with @command{tar}.
2037 Long options which require arguments take those arguments
2038 immediately following the option name. There are two ways of
2039 specifying a mandatory argument. It can be separated from the
2040 option name either by an equal sign, or by any amount of
2041 white space characters. For example, the @option{--file} option (which
2042 tells the name of the @command{tar} archive) is given a file such as
2043 @file{archive.tar} as argument by using any of the following notations:
2044 @option{--file=archive.tar} or @option{--file archive.tar}.
2046 In contrast, optional arguments must always be introduced using
2047 an equal sign. For example, the @option{--backup} option takes
2048 an optional argument specifying backup type. It must be used
2049 as @option{--backup=@var{backup-type}}.
2052 @subsection Short Option Style
2054 Most options also have a @dfn{short option} name. Short options start with
2055 a single dash, and are followed by a single character, e.g., @option{-t}
2056 (which is equivalent to @option{--list}). The forms are absolutely
2057 identical in function; they are interchangeable.
2059 The short option names are faster to type than long option names.
2061 Short options which require arguments take their arguments immediately
2062 following the option, usually separated by white space. It is also
2063 possible to stick the argument right after the short option name, using
2064 no intervening space. For example, you might write @w{@option{-f
2065 archive.tar}} or @option{-farchive.tar} instead of using
2066 @option{--file=archive.tar}. Both @option{--file=@var{archive-name}} and
2067 @w{@option{-f @var{archive-name}}} denote the option which indicates a
2068 specific archive, here named @file{archive.tar}.
2070 Short options which take optional arguments take their arguments
2071 immediately following the option letter, @emph{without any intervening
2072 white space characters}.
2074 Short options' letters may be clumped together, but you are not
2075 required to do this (as compared to old options; see below). When
2076 short options are clumped as a set, use one (single) dash for them
2077 all, e.g., @w{@samp{@command{tar} -cvf}}. Only the last option in
2078 such a set is allowed to have an argument@footnote{Clustering many
2079 options, the last of which has an argument, is a rather opaque way to
2080 write options. Some wonder if @acronym{GNU} @code{getopt} should not
2081 even be made helpful enough for considering such usages as invalid.}.
2083 When the options are separated, the argument for each option which requires
2084 an argument directly follows that option, as is usual for Unix programs.
2088 $ @kbd{tar -c -v -b 20 -f /dev/rmt0}
2091 If you reorder short options' locations, be sure to move any arguments
2092 that belong to them. If you do not move the arguments properly, you may
2093 end up overwriting files.
2096 @subsection Old Option Style
2099 Like short options, @dfn{old options} are single letters. However, old options
2100 must be written together as a single clumped set, without spaces separating
2101 them or dashes preceding them@footnote{Beware that if you precede options
2102 with a dash, you are announcing the short option style instead of the
2103 old option style; short options are decoded differently.}. This set
2104 of letters must be the first to appear on the command line, after the
2105 @command{tar} program name and some white space; old options cannot appear
2106 anywhere else. The letter of an old option is exactly the same letter as
2107 the corresponding short option. For example, the old option @samp{t} is
2108 the same as the short option @option{-t}, and consequently, the same as the
2109 long option @option{--list}. So for example, the command @w{@samp{tar
2110 cv}} specifies the option @option{-v} in addition to the operation @option{-c}.
2112 When options that need arguments are given together with the command,
2113 all the associated arguments follow, in the same order as the options.
2114 Thus, the example given previously could also be written in the old
2118 $ @kbd{tar cvbf 20 /dev/rmt0}
2122 Here, @samp{20} is the argument of @option{-b} and @samp{/dev/rmt0} is
2123 the argument of @option{-f}.
2125 On the other hand, this old style syntax makes it difficult to match
2126 option letters with their corresponding arguments, and is often
2127 confusing. In the command @w{@samp{tar cvbf 20 /dev/rmt0}}, for example,
2128 @samp{20} is the argument for @option{-b}, @samp{/dev/rmt0} is the
2129 argument for @option{-f}, and @option{-v} does not have a corresponding
2130 argument. Even using short options like in @w{@samp{tar -c -v -b 20 -f
2131 /dev/rmt0}} is clearer, putting all arguments next to the option they
2134 If you want to reorder the letters in the old option argument, be
2135 sure to reorder any corresponding argument appropriately.
2137 This old way of writing @command{tar} options can surprise even experienced
2138 users. For example, the two commands:
2141 @kbd{tar cfz archive.tar.gz file}
2142 @kbd{tar -cfz archive.tar.gz file}
2146 are quite different. The first example uses @file{archive.tar.gz} as
2147 the value for option @samp{f} and recognizes the option @samp{z}. The
2148 second example, however, uses @file{z} as the value for option
2149 @samp{f} --- probably not what was intended.
2151 Old options are kept for compatibility with old versions of @command{tar}.
2153 This second example could be corrected in many ways, among which the
2154 following are equivalent:
2157 @kbd{tar -czf archive.tar.gz file}
2158 @kbd{tar -cf archive.tar.gz -z file}
2159 @kbd{tar cf archive.tar.gz -z file}
2162 @cindex option syntax, traditional
2163 As far as we know, all @command{tar} programs, @acronym{GNU} and
2164 non-@acronym{GNU}, support old options. @GNUTAR{}
2165 supports them not only for historical reasons, but also because many
2166 people are used to them. For compatibility with Unix @command{tar},
2167 the first argument is always treated as containing command and option
2168 letters even if it doesn't start with @samp{-}. Thus, @samp{tar c} is
2169 equivalent to @w{@samp{tar -c}:} both of them specify the
2170 @option{--create} (@option{-c}) command to create an archive.
2173 @subsection Mixing Option Styles
2175 All three styles may be intermixed in a single @command{tar} command,
2176 so long as the rules for each style are fully
2177 respected@footnote{Before @GNUTAR{} version 1.11.6,
2178 a bug prevented intermixing old style options with long options in
2179 some cases.}. Old style options and either of the modern styles of
2180 options may be mixed within a single @command{tar} command. However,
2181 old style options must be introduced as the first arguments only,
2182 following the rule for old options (old options must appear directly
2183 after the @command{tar} command and some white space). Modern options
2184 may be given only after all arguments to the old options have been
2185 collected. If this rule is not respected, a modern option might be
2186 falsely interpreted as the value of the argument to one of the old
2189 For example, all the following commands are wholly equivalent, and
2190 illustrate the many combinations and orderings of option styles.
2193 @kbd{tar --create --file=archive.tar}
2194 @kbd{tar --create -f archive.tar}
2195 @kbd{tar --create -farchive.tar}
2196 @kbd{tar --file=archive.tar --create}
2197 @kbd{tar --file=archive.tar -c}
2198 @kbd{tar -c --file=archive.tar}
2199 @kbd{tar -c -f archive.tar}
2200 @kbd{tar -c -farchive.tar}
2201 @kbd{tar -cf archive.tar}
2202 @kbd{tar -cfarchive.tar}
2203 @kbd{tar -f archive.tar --create}
2204 @kbd{tar -f archive.tar -c}
2205 @kbd{tar -farchive.tar --create}
2206 @kbd{tar -farchive.tar -c}
2207 @kbd{tar c --file=archive.tar}
2208 @kbd{tar c -f archive.tar}
2209 @kbd{tar c -farchive.tar}
2210 @kbd{tar cf archive.tar}
2211 @kbd{tar f archive.tar --create}
2212 @kbd{tar f archive.tar -c}
2213 @kbd{tar fc archive.tar}
2216 On the other hand, the following commands are @emph{not} equivalent to
2220 @kbd{tar -f -c archive.tar}
2221 @kbd{tar -fc archive.tar}
2222 @kbd{tar -fcarchive.tar}
2223 @kbd{tar -farchive.tarc}
2224 @kbd{tar cfarchive.tar}
2228 These last examples mean something completely different from what the
2229 user intended (judging based on the example in the previous set which
2230 uses long options, whose intent is therefore very clear). The first
2231 four specify that the @command{tar} archive would be a file named
2232 @option{-c}, @samp{c}, @samp{carchive.tar} or @samp{archive.tarc},
2233 respectively. The first two examples also specify a single non-option,
2234 @var{name} argument having the value @samp{archive.tar}. The last
2235 example contains only old style option letters (repeating option
2236 @samp{c} twice), not all of which are meaningful (eg., @samp{.},
2237 @samp{h}, or @samp{i}), with no argument value. @FIXME{not sure i liked
2238 the first sentence of this paragraph..}
2241 @section All @command{tar} Options
2243 The coming manual sections contain an alphabetical listing of all
2244 @command{tar} operations and options, with brief descriptions and cross
2245 references to more in-depth explanations in the body of the manual.
2246 They also contain an alphabetically arranged table of the short option
2247 forms with their corresponding long option. You can use this table as
2248 a reference for deciphering @command{tar} commands in scripts.
2251 * Operation Summary::
2253 * Short Option Summary::
2256 @node Operation Summary
2257 @subsection Operations
2265 Appends files to the end of the archive. @xref{append}.
2267 @opsummary{catenate}
2271 Same as @option{--concatenate}. @xref{concatenate}.
2277 Compares archive members with their counterparts in the file
2278 system, and reports differences in file size, mode, owner,
2279 modification date and contents. @xref{compare}.
2281 @opsummary{concatenate}
2285 Appends other @command{tar} archives to the end of the archive.
2292 Creates a new @command{tar} archive. @xref{create}.
2297 Deletes members from the archive. Don't try this on a archive on a
2298 tape! @xref{delete}.
2304 Same @option{--compare}. @xref{compare}.
2310 Extracts members from the archive into the file system. @xref{extract}.
2316 Same as @option{--extract}. @xref{extract}.
2322 Lists the members in an archive. @xref{list}.
2328 Adds files to the end of the archive, but only if they are newer than
2329 their counterparts already in the archive, or if they do not already
2330 exist in the archive. @xref{update}.
2334 @node Option Summary
2335 @subsection @command{tar} Options
2339 @opsummary{absolute-names}
2340 @item --absolute-names
2343 Normally when creating an archive, @command{tar} strips an initial
2344 @samp{/} from member names. This option disables that behavior.
2347 @opsummary{after-date}
2350 (See @option{--newer}, @pxref{after})
2352 @opsummary{anchored}
2354 A pattern must match an initial subsequence of the name's components.
2355 @xref{controlling pattern-matching}.
2357 @opsummary{atime-preserve}
2358 @item --atime-preserve
2359 @itemx --atime-preserve=replace
2360 @itemx --atime-preserve=system
2362 Attempt to preserve the access time of files when reading them. This
2363 option currently is effective only on files that you own, unless you
2364 have superuser privileges.
2366 @option{--atime-preserve=replace} remembers the access time of a file
2367 before reading it, and then restores the access time afterwards. This
2368 may cause problems if other programs are reading the file at the same
2369 time, as the times of their accesses will be lost. On most platforms
2370 restoring the access time also requires @command{tar} to restore the
2371 data modification time too, so this option may also cause problems if
2372 other programs are writing the file at the same time. (Tar attempts
2373 to detect this situation, but cannot do so reliably due to race
2374 conditions.) Worse, on most platforms restoring the access time also
2375 updates the status change time, which means that this option is
2376 incompatible with incremental backups.
2378 @option{--atime-preserve=system} avoids changing time stamps on files,
2379 without interfering with time stamp updates
2380 caused by other programs, so it works better with incremental backups.
2381 However, it requires a special @code{O_NOATIME} option from the
2382 underlying operating and file system implementation, and it also requires
2383 that searching directories does not update their access times. As of
2384 this writing (November 2005) this works only with Linux, and only with
2385 Linux kernels 2.6.8 and later. Worse, there is currently no reliable
2386 way to know whether this feature actually works. Sometimes
2387 @command{tar} knows that it does not work, and if you use
2388 @option{--atime-preserve=system} then @command{tar} complains and
2389 exits right away. But other times @command{tar} might think that the
2390 option works when it actually does not.
2392 Currently @option{--atime-preserve} with no operand defaults to
2393 @option{--atime-preserve=replace}, but this may change in the future
2394 as support for @option{--atime-preserve=system} improves.
2396 If your operating system does not support
2397 @option{--atime-preserve=@-system}, you might be able to preserve access
2398 times reliably by by using the @command{mount} command. For example,
2399 you can mount the file system read-only, or access the file system via
2400 a read-only loopback mount, or use the @samp{noatime} mount option
2401 available on some systems. However, mounting typically requires
2402 superuser privileges and can be a pain to manage.
2405 @item --backup=@var{backup-type}
2407 Rather than deleting files from the file system, @command{tar} will
2408 back them up using simple or numbered backups, depending upon
2409 @var{backup-type}. @xref{backup}.
2411 @opsummary{block-number}
2412 @item --block-number
2415 With this option present, @command{tar} prints error messages for read errors
2416 with the block number in the archive file. @xref{block-number}.
2418 @opsummary{blocking-factor}
2419 @item --blocking-factor=@var{blocking}
2420 @itemx -b @var{blocking}
2422 Sets the blocking factor @command{tar} uses to @var{blocking} x 512 bytes per
2423 record. @xref{Blocking Factor}.
2429 This option tells @command{tar} to read or write archives through
2430 @code{bzip2}. @xref{gzip}.
2432 @opsummary{checkpoint}
2433 @item --checkpoint[=@var{number}]
2435 This option directs @command{tar} to print periodic checkpoint
2436 messages as it reads through the archive. It is intended for when you
2437 want a visual indication that @command{tar} is still running, but
2438 don't want to see @option{--verbose} output. For a detailed
2439 description, see @ref{Progress information}.
2441 @opsummary{check-links}
2444 If this option was given, @command{tar} will check the number of links
2445 dumped for each processed file. If this number does not match the
2446 total number of hard links for the file, a warning message will be
2447 output @footnote{Earlier versions of @GNUTAR{} understood @option{-l} as a
2448 synonym for @option{--one-file-system}. The current semantics, which
2449 complies to UNIX98, was introduced with version
2450 1.15.91. @xref{Changes}, for more information.}.
2452 @opsummary{compress}
2453 @opsummary{uncompress}
2458 @command{tar} will use the @command{compress} program when reading or
2459 writing the archive. This allows you to directly act on archives
2460 while saving space. @xref{gzip}.
2462 @opsummary{confirmation}
2463 @item --confirmation
2465 (See @option{--interactive}.) @xref{interactive}.
2467 @opsummary{delay-directory-restore}
2468 @item --delay-directory-restore
2470 Delay setting modification times and permissions of extracted
2471 directories until the end of extraction. @xref{Directory Modification Times and Permissions}.
2473 @opsummary{dereference}
2477 When creating a @command{tar} archive, @command{tar} will archive the
2478 file that a symbolic link points to, rather than archiving the
2479 symlink. @xref{dereference}.
2481 @opsummary{directory}
2482 @item --directory=@var{dir}
2485 When this option is specified, @command{tar} will change its current directory
2486 to @var{dir} before performing any operations. When this option is used
2487 during archive creation, it is order sensitive. @xref{directory}.
2490 @item --exclude=@var{pattern}
2492 When performing operations, @command{tar} will skip files that match
2493 @var{pattern}. @xref{exclude}.
2495 @opsummary{exclude-from}
2496 @item --exclude-from=@var{file}
2497 @itemx -X @var{file}
2499 Similar to @option{--exclude}, except @command{tar} will use the list of
2500 patterns in the file @var{file}. @xref{exclude}.
2502 @opsummary{exclude-caches}
2503 @item --exclude-caches
2505 Exclude from dump any directory containing a valid cache directory
2506 tag file, but still dump the directory node and the tag file itself.
2510 @opsummary{exclude-caches-under}
2511 @item --exclude-caches-under
2513 Exclude from dump any directory containing a valid cache directory
2514 tag file, but still dump the directory node itself.
2518 @opsummary{exclude-caches-all}
2519 @item --exclude-caches-all
2521 Exclude from dump any directory containing a valid cache directory
2522 tag file. @xref{exclude}.
2524 @opsummary{exclude-tag}
2525 @item --exclude-tag=@var{file}
2527 Exclude from dump any directory containing file named @var{file}, but
2528 dump the directory node and @var{file} itself. @xref{exclude}.
2530 @opsummary{exclude-tag-under}
2531 @item --exclude-tag-under=@var{file}
2533 Exclude from dump the contents of any directory containing file
2534 named @var{file}, but dump the directory node itself. @xref{exclude}.
2536 @opsummary{exclude-tag-all}
2537 @item --exclude-tag-all=@var{file}
2539 Exclude from dump any directory containing file named @var{file}.
2543 @item --file=@var{archive}
2544 @itemx -f @var{archive}
2546 @command{tar} will use the file @var{archive} as the @command{tar} archive it
2547 performs operations on, rather than @command{tar}'s compilation dependent
2548 default. @xref{file tutorial}.
2550 @opsummary{files-from}
2551 @item --files-from=@var{file}
2552 @itemx -T @var{file}
2554 @command{tar} will use the contents of @var{file} as a list of archive members
2555 or files to operate on, in addition to those specified on the
2556 command-line. @xref{files}.
2558 @opsummary{force-local}
2561 Forces @command{tar} to interpret the filename given to @option{--file}
2562 as a local file, even if it looks like a remote tape drive name.
2563 @xref{local and remote archives}.
2566 @item --format=@var{format}
2567 @itemx -H @var{format}
2569 Selects output archive format. @var{Format} may be one of the
2574 Creates an archive that is compatible with Unix V7 @command{tar}.
2577 Creates an archive that is compatible with GNU @command{tar} version
2581 Creates archive in GNU tar 1.13 format. Basically it is the same as
2582 @samp{oldgnu} with the only difference in the way it handles long
2586 Creates a @acronym{POSIX.1-1988} compatible archive.
2589 Creates a @acronym{POSIX.1-2001 archive}.
2593 @xref{Formats}, for a detailed discussion of these formats.
2596 @item --group=@var{group}
2598 Files added to the @command{tar} archive will have a group id of @var{group},
2599 rather than the group from the source file. @var{group} is first decoded
2600 as a group symbolic name, but if this interpretation fails, it has to be
2601 a decimal numeric group ID. @xref{override}.
2603 Also see the comments for the @option{--owner=@var{user}} option.
2613 This option tells @command{tar} to read or write archives through
2614 @command{gzip}, allowing @command{tar} to directly operate on several
2615 kinds of compressed archives transparently. @xref{gzip}.
2621 @command{tar} will print out a short message summarizing the operations and
2622 options to @command{tar} and exit. @xref{help}.
2624 @opsummary{ignore-case}
2626 Ignore case when matching member or file names with
2627 patterns. @xref{controlling pattern-matching}.
2629 @opsummary{ignore-command-error}
2630 @item --ignore-command-error
2631 Ignore exit codes of subprocesses. @xref{Writing to an External Program}.
2633 @opsummary{ignore-failed-read}
2634 @item --ignore-failed-read
2636 Do not exit unsuccessfully merely because an unreadable file was encountered.
2639 @opsummary{ignore-zeros}
2640 @item --ignore-zeros
2643 With this option, @command{tar} will ignore zeroed blocks in the
2644 archive, which normally signals EOF. @xref{Reading}.
2646 @opsummary{incremental}
2650 Used to inform @command{tar} that it is working with an old
2651 @acronym{GNU}-format incremental backup archive. It is intended
2652 primarily for backwards compatibility only. @xref{Incremental Dumps},
2653 for a detailed discussion of incremental archives.
2655 @opsummary{index-file}
2656 @item --index-file=@var{file}
2658 Send verbose output to @var{file} instead of to standard output.
2660 @opsummary{info-script}
2661 @opsummary{new-volume-script}
2662 @item --info-script=@var{script-file}
2663 @itemx --new-volume-script=@var{script-file}
2664 @itemx -F @var{script-file}
2666 When @command{tar} is performing multi-tape backups, @var{script-file} is run
2667 at the end of each tape. If @var{script-file} exits with nonzero status,
2668 @command{tar} fails immediately. @xref{info-script}, for a detailed
2669 discussion of @var{script-file}.
2671 @opsummary{interactive}
2673 @itemx --confirmation
2676 Specifies that @command{tar} should ask the user for confirmation before
2677 performing potentially destructive options, such as overwriting files.
2680 @opsummary{keep-newer-files}
2681 @item --keep-newer-files
2683 Do not replace existing files that are newer than their archive copies
2684 when extracting files from an archive.
2686 @opsummary{keep-old-files}
2687 @item --keep-old-files
2690 Do not overwrite existing files when extracting files from an archive.
2691 @xref{Keep Old Files}.
2694 @item --label=@var{name}
2695 @itemx -V @var{name}
2697 When creating an archive, instructs @command{tar} to write @var{name}
2698 as a name record in the archive. When extracting or listing archives,
2699 @command{tar} will only operate on archives that have a label matching
2700 the pattern specified in @var{name}. @xref{Tape Files}.
2702 @opsummary{listed-incremental}
2703 @item --listed-incremental=@var{snapshot-file}
2704 @itemx -g @var{snapshot-file}
2706 During a @option{--create} operation, specifies that the archive that
2707 @command{tar} creates is a new @acronym{GNU}-format incremental
2708 backup, using @var{snapshot-file} to determine which files to backup.
2709 With other operations, informs @command{tar} that the archive is in
2710 incremental format. @xref{Incremental Dumps}.
2713 @item --mode=@var{permissions}
2715 When adding files to an archive, @command{tar} will use
2716 @var{permissions} for the archive members, rather than the permissions
2717 from the files. @var{permissions} can be specified either as an octal
2718 number or as symbolic permissions, like with
2719 @command{chmod}. @xref{override}.
2722 @item --mtime=@var{date}
2724 When adding files to an archive, @command{tar} will use @var{date} as
2725 the modification time of members when creating archives, instead of
2726 their actual modification times. The value of @var{date} can be
2727 either a textual date representation (@pxref{Date input formats}) or a
2728 name of the existing file, starting with @samp{/} or @samp{.}. In the
2729 latter case, the modification time of that file is used. @xref{override}.
2731 @opsummary{multi-volume}
2732 @item --multi-volume
2735 Informs @command{tar} that it should create or otherwise operate on a
2736 multi-volume @command{tar} archive. @xref{Using Multiple Tapes}.
2738 @opsummary{new-volume-script}
2739 @item --new-volume-script
2747 Assume that the archive media supports seeks to arbitrary
2748 locations. Usually @command{tar} determines automatically whether
2749 the archive can be seeked or not. This option is intended for use
2750 in cases when such recognition fails.
2753 @item --newer=@var{date}
2754 @itemx --after-date=@var{date}
2757 When creating an archive, @command{tar} will only add files that have changed
2758 since @var{date}. If @var{date} begins with @samp{/} or @samp{.}, it
2759 is taken to be the name of a file whose data modification time specifies
2760 the date. @xref{after}.
2762 @opsummary{newer-mtime}
2763 @item --newer-mtime=@var{date}
2765 Like @option{--newer}, but add only files whose
2766 contents have changed (as opposed to just @option{--newer}, which will
2767 also back up files for which any status information has
2768 changed). @xref{after}.
2770 @opsummary{no-anchored}
2772 An exclude pattern can match any subsequence of the name's components.
2773 @xref{controlling pattern-matching}.
2775 @opsummary{no-delay-directory-restore}
2776 @item --no-delay-directory-restore
2778 Setting modification times and permissions of extracted
2779 directories when all files from this directory has been
2780 extracted. This is the default. @xref{Directory Modification Times and Permissions}.
2782 @opsummary{no-ignore-case}
2783 @item --no-ignore-case
2784 Use case-sensitive matching.
2785 @xref{controlling pattern-matching}.
2787 @opsummary{no-ignore-command-error}
2788 @item --no-ignore-command-error
2789 Print warnings about subprocesses terminated with a non-zero exit
2790 code. @xref{Writing to an External Program}.
2792 @opsummary{no-overwrite-dir}
2793 @item --no-overwrite-dir
2795 Preserve metadata of existing directories when extracting files
2796 from an archive. @xref{Overwrite Old Files}.
2798 @opsummary{no-quote-chars}
2799 @item --no-quote-chars=@var{string}
2800 Remove characters listed in @var{string} from the list of quoted
2801 characters set by the previous @option{--quote-chars} option
2802 (@pxref{quoting styles}).
2804 @opsummary{no-recursion}
2805 @item --no-recursion
2807 With this option, @command{tar} will not recurse into directories.
2810 @opsummary{no-same-owner}
2811 @item --no-same-owner
2814 When extracting an archive, do not attempt to preserve the owner
2815 specified in the @command{tar} archive. This the default behavior
2818 @opsummary{no-same-permissions}
2819 @item --no-same-permissions
2821 When extracting an archive, subtract the user's umask from files from
2822 the permissions specified in the archive. This is the default behavior
2825 @opsummary{no-unquote}
2827 Treat all input file or member names literally, do not interpret
2828 escape sequences. @xref{input name quoting}.
2830 @opsummary{no-wildcards}
2831 @item --no-wildcards
2832 Do not use wildcards.
2833 @xref{controlling pattern-matching}.
2835 @opsummary{no-wildcards-match-slash}
2836 @item --no-wildcards-match-slash
2837 Wildcards do not match @samp{/}.
2838 @xref{controlling pattern-matching}.
2843 When @command{tar} is using the @option{--files-from} option, this option
2844 instructs @command{tar} to expect filenames terminated with @option{NUL}, so
2845 @command{tar} can correctly work with file names that contain newlines.
2848 @opsummary{numeric-owner}
2849 @item --numeric-owner
2851 This option will notify @command{tar} that it should use numeric user
2852 and group IDs when creating a @command{tar} file, rather than names.
2856 The function of this option depends on the action @command{tar} is
2857 performing. When extracting files, @option{-o} is a synonym for
2858 @option{--no-same-owner}, i.e., it prevents @command{tar} from
2859 restoring ownership of files being extracted.
2861 When creating an archive, it is a synonym for
2862 @option{--old-archive}. This behavior is for compatibility
2863 with previous versions of @GNUTAR{}, and will be
2864 removed in the future releases.
2866 @xref{Changes}, for more information.
2868 @opsummary{occurrence}
2869 @item --occurrence[=@var{number}]
2871 This option can be used in conjunction with one of the subcommands
2872 @option{--delete}, @option{--diff}, @option{--extract} or
2873 @option{--list} when a list of files is given either on the command
2874 line or via @option{-T} option.
2876 This option instructs @command{tar} to process only the @var{number}th
2877 occurrence of each named file. @var{Number} defaults to 1, so
2880 tar -x -f archive.tar --occurrence filename
2884 will extract the first occurrence of the member @file{filename} from @file{archive.tar}
2885 and will terminate without scanning to the end of the archive.
2887 @opsummary{old-archive}
2889 Synonym for @option{--format=v7}.
2891 @opsummary{one-file-system}
2892 @item --one-file-system
2893 Used when creating an archive. Prevents @command{tar} from recursing into
2894 directories that are on different file systems from the current
2895 directory @footnote{Earlier versions of @GNUTAR{} understood @option{-l} as a
2896 synonym for @option{--one-file-system}. This has changed in version
2897 1.15.91. @xref{Changes}, for more information.}.
2899 @opsummary{overwrite}
2902 Overwrite existing files and directory metadata when extracting files
2903 from an archive. @xref{Overwrite Old Files}.
2905 @opsummary{overwrite-dir}
2906 @item --overwrite-dir
2908 Overwrite the metadata of existing directories when extracting files
2909 from an archive. @xref{Overwrite Old Files}.
2912 @item --owner=@var{user}
2914 Specifies that @command{tar} should use @var{user} as the owner of members
2915 when creating archives, instead of the user associated with the source
2916 file. @var{user} is first decoded as a user symbolic name, but if
2917 this interpretation fails, it has to be a decimal numeric user ID.
2920 This option does not affect extraction from archives.
2922 @opsummary{transform}
2923 @item --transform=@var{sed-expr}
2925 Transform file or member names using @command{sed} replacement expression
2926 @var{sed-expr}. For example,
2929 $ @kbd{tar cf archive.tar --transform 's,^\./,usr/,' .}
2933 will add to @file{archive} files from the current working directory,
2934 replacing initial @samp{./} prefix with @samp{usr/}. For the detailed
2935 discussion, @xref{transform}.
2937 To see transformed member names in verbose listings, use
2938 @option{--show-transformed-names} option
2939 (@pxref{show-transformed-names}).
2941 @opsummary{quote-chars}
2942 @item --quote-chars=@var{string}
2943 Always quote characters from @var{string}, even if the selected
2944 quoting style would not quote them (@pxref{quoting styles}).
2946 @opsummary{quoting-style}
2947 @item --quoting-style=@var{style}
2948 Set quoting style to use when printing member and file names
2949 (@pxref{quoting styles}). Valid @var{style} values are:
2950 @code{literal}, @code{shell}, @code{shell-always}, @code{c},
2951 @code{escape}, @code{locale}, and @code{clocale}. Default quoting
2952 style is @code{escape}, unless overridden while configuring the
2955 @opsummary{pax-option}
2956 @item --pax-option=@var{keyword-list}
2957 This option is meaningful only with @acronym{POSIX.1-2001} archives
2958 (@pxref{posix}). It modifies the way @command{tar} handles the
2959 extended header keywords. @var{Keyword-list} is a comma-separated
2960 list of keyword options. @xref{PAX keywords}, for a detailed
2963 @opsummary{portability}
2965 @itemx --old-archive
2966 Synonym for @option{--format=v7}.
2970 Same as @option{--format=posix}.
2972 @opsummary{preserve}
2975 Synonymous with specifying both @option{--preserve-permissions} and
2976 @option{--same-order}. @xref{Setting Access Permissions}.
2978 @opsummary{preserve-order}
2979 @item --preserve-order
2981 (See @option{--same-order}; @pxref{Reading}.)
2983 @opsummary{preserve-permissions}
2984 @opsummary{same-permissions}
2985 @item --preserve-permissions
2986 @itemx --same-permissions
2989 When @command{tar} is extracting an archive, it normally subtracts the
2990 users' umask from the permissions specified in the archive and uses
2991 that number as the permissions to create the destination file.
2992 Specifying this option instructs @command{tar} that it should use the
2993 permissions directly from the archive. @xref{Setting Access Permissions}.
2995 @opsummary{read-full-records}
2996 @item --read-full-records
2999 Specifies that @command{tar} should reblock its input, for reading
3000 from pipes on systems with buggy implementations. @xref{Reading}.
3002 @opsummary{record-size}
3003 @item --record-size=@var{size}
3005 Instructs @command{tar} to use @var{size} bytes per record when accessing the
3006 archive. @xref{Blocking Factor}.
3008 @opsummary{recursion}
3011 With this option, @command{tar} recurses into directories.
3014 @opsummary{recursive-unlink}
3015 @item --recursive-unlink
3018 directory hierarchies before extracting directories of the same name
3019 from the archive. @xref{Recursive Unlink}.
3021 @opsummary{remove-files}
3022 @item --remove-files
3024 Directs @command{tar} to remove the source file from the file system after
3025 appending it to an archive. @xref{remove files}.
3027 @opsummary{restrict}
3030 Disable use of some potentially harmful @command{tar} options.
3031 Currently this option disables shell invocation from multi-volume menu
3032 (@pxref{Using Multiple Tapes}).
3034 @opsummary{rmt-command}
3035 @item --rmt-command=@var{cmd}
3037 Notifies @command{tar} that it should use @var{cmd} instead of
3038 the default @file{/usr/libexec/rmt} (@pxref{Remote Tape Server}).
3040 @opsummary{rsh-command}
3041 @item --rsh-command=@var{cmd}
3043 Notifies @command{tar} that is should use @var{cmd} to communicate with remote
3044 devices. @xref{Device}.
3046 @opsummary{same-order}
3048 @itemx --preserve-order
3051 This option is an optimization for @command{tar} when running on machines with
3052 small amounts of memory. It informs @command{tar} that the list of file
3053 arguments has already been sorted to match the order of files in the
3054 archive. @xref{Reading}.
3056 @opsummary{same-owner}
3059 When extracting an archive, @command{tar} will attempt to preserve the owner
3060 specified in the @command{tar} archive with this option present.
3061 This is the default behavior for the superuser; this option has an
3062 effect only for ordinary users. @xref{Attributes}.
3064 @opsummary{same-permissions}
3065 @item --same-permissions
3067 (See @option{--preserve-permissions}; @pxref{Setting Access Permissions}.)
3069 @opsummary{show-defaults}
3070 @item --show-defaults
3072 Displays the default options used by @command{tar} and exits
3073 successfully. This option is intended for use in shell scripts.
3074 Here is an example of what you can see using this option:
3077 $ tar --show-defaults
3078 --format=gnu -f- -b20 --quoting-style=escape \
3079 --rmt-command=/usr/libexec/rmt --rsh-command=/usr/bin/rsh
3082 @opsummary{show-omitted-dirs}
3083 @item --show-omitted-dirs
3085 Instructs @command{tar} to mention directories its skipping over when
3086 operating on a @command{tar} archive. @xref{show-omitted-dirs}.
3088 @opsummary{show-transformed-names}
3089 @opsummary{show-stored-names}
3090 @item --show-transformed-names
3091 @itemx --show-stored-names
3093 Display file or member names after applying any transformations
3094 (@pxref{transform}). In particular, when used in conjunction with one of
3095 archive creation operations it instructs tar to list the member names
3096 stored in the archive, as opposed to the actual file
3097 names. @xref{listing member and file names}.
3103 Invokes a @acronym{GNU} extension when adding files to an archive that handles
3104 sparse files efficiently. @xref{sparse}.
3106 @opsummary{sparse-version}
3107 @item --sparse-version=@var{version}
3109 Specified the @dfn{format version} to use when archiving sparse
3110 files. Implies @option{--sparse}. @xref{sparse}. For the description
3111 of the supported sparse formats, @xref{Sparse Formats}.
3113 @opsummary{starting-file}
3114 @item --starting-file=@var{name}
3115 @itemx -K @var{name}
3117 This option affects extraction only; @command{tar} will skip extracting
3118 files in the archive until it finds one that matches @var{name}.
3121 @opsummary{strip-components}
3122 @item --strip-components=@var{number}
3123 Strip given @var{number} of leading components from file names before
3124 extraction.@footnote{This option was called @option{--strip-path} in
3125 version 1.14.} For example, if archive @file{archive.tar} contained
3126 @file{/some/file/name}, then running
3129 tar --extract --file archive.tar --strip-components=2
3133 would extract this file to file @file{name}.
3135 @opsummary{suffix}, summary
3136 @item --suffix=@var{suffix}
3138 Alters the suffix @command{tar} uses when backing up files from the default
3139 @samp{~}. @xref{backup}.
3141 @opsummary{tape-length}
3142 @item --tape-length=@var{num}
3145 Specifies the length of tapes that @command{tar} is writing as being
3146 @w{@var{num} x 1024} bytes long. @xref{Using Multiple Tapes}.
3148 @opsummary{test-label}
3151 Reads the volume label. If an argument is specified, test whether it
3152 matches the volume label. @xref{--test-label option}.
3154 @opsummary{to-command}
3155 @item --to-command=@var{command}
3157 During extraction @command{tar} will pipe extracted files to the
3158 standard input of @var{command}. @xref{Writing to an External Program}.
3160 @opsummary{to-stdout}
3164 During extraction, @command{tar} will extract files to stdout rather
3165 than to the file system. @xref{Writing to Standard Output}.
3168 @item --totals[=@var{signo}]
3170 Displays the total number of bytes transferred when processing an
3171 archive. If an argument is given, these data are displayed on
3172 request, when signal @var{signo} is delivered to @command{tar}.
3179 Sets the data modification time of extracted files to the extraction time,
3180 rather than the data modification time stored in the archive.
3181 @xref{Data Modification Times}.
3183 @opsummary{uncompress}
3186 (See @option{--compress}. @pxref{gzip})
3191 (See @option{--gzip}. @pxref{gzip})
3193 @opsummary{unlink-first}
3194 @item --unlink-first
3197 Directs @command{tar} to remove the corresponding file from the file
3198 system before extracting it from the archive. @xref{Unlink First}.
3202 Enable unquoting input file or member names (default). @xref{input
3205 @opsummary{use-compress-program}
3206 @item --use-compress-program=@var{prog}
3208 Instructs @command{tar} to access the archive through @var{prog}, which is
3209 presumed to be a compression program of some sort. @xref{gzip}.
3214 Display file modification dates in @acronym{UTC}. This option implies
3221 Specifies that @command{tar} should be more verbose about the operations its
3222 performing. This option can be specified multiple times for some
3223 operations to increase the amount of information displayed.
3230 Verifies that the archive was correctly written when creating an
3231 archive. @xref{verify}.
3236 Print information about the program's name, version, origin and legal
3237 status, all on standard output, and then exit successfully.
3240 @opsummary{volno-file}
3241 @item --volno-file=@var{file}
3243 Used in conjunction with @option{--multi-volume}. @command{tar} will
3244 keep track of which volume of a multi-volume archive its working in
3245 @var{file}. @xref{volno-file}.
3247 @opsummary{wildcards}
3249 Use wildcards when matching member names with patterns.
3250 @xref{controlling pattern-matching}.
3252 @opsummary{wildcards-match-slash}
3253 @item --wildcards-match-slash
3254 Wildcards match @samp{/}.
3255 @xref{controlling pattern-matching}.
3258 @node Short Option Summary
3259 @subsection Short Options Cross Reference
3261 Here is an alphabetized list of all of the short option forms, matching
3262 them with the equivalent long option.
3264 @multitable @columnfractions 0.20 0.80
3265 @headitem Short Option @tab Reference
3267 @item -A @tab @ref{--concatenate}.
3269 @item -B @tab @ref{--read-full-records}.
3271 @item -C @tab @ref{--directory}.
3273 @item -F @tab @ref{--info-script}.
3275 @item -G @tab @ref{--incremental}.
3277 @item -K @tab @ref{--starting-file}.
3279 @item -L @tab @ref{--tape-length}.
3281 @item -M @tab @ref{--multi-volume}.
3283 @item -N @tab @ref{--newer}.
3285 @item -O @tab @ref{--to-stdout}.
3287 @item -P @tab @ref{--absolute-names}.
3289 @item -R @tab @ref{--block-number}.
3291 @item -S @tab @ref{--sparse}.
3293 @item -T @tab @ref{--files-from}.
3295 @item -U @tab @ref{--unlink-first}.
3297 @item -V @tab @ref{--label}.
3299 @item -W @tab @ref{--verify}.
3301 @item -X @tab @ref{--exclude-from}.
3303 @item -Z @tab @ref{--compress}.
3305 @item -b @tab @ref{--blocking-factor}.
3307 @item -c @tab @ref{--create}.
3309 @item -d @tab @ref{--compare}.
3311 @item -f @tab @ref{--file}.
3313 @item -g @tab @ref{--listed-incremental}.
3315 @item -h @tab @ref{--dereference}.
3317 @item -i @tab @ref{--ignore-zeros}.
3319 @item -j @tab @ref{--bzip2}.
3321 @item -k @tab @ref{--keep-old-files}.
3323 @item -l @tab @ref{--check-links}.
3325 @item -m @tab @ref{--touch}.
3327 @item -o @tab When creating, @ref{--no-same-owner}, when extracting ---
3328 @ref{--portability}.
3330 The later usage is deprecated. It is retained for compatibility with
3331 the earlier versions of @GNUTAR{}. In the future releases
3332 @option{-o} will be equivalent to @option{--no-same-owner} only.
3334 @item -p @tab @ref{--preserve-permissions}.
3336 @item -r @tab @ref{--append}.
3338 @item -s @tab @ref{--same-order}.
3340 @item -t @tab @ref{--list}.
3342 @item -u @tab @ref{--update}.
3344 @item -v @tab @ref{--verbose}.
3346 @item -w @tab @ref{--interactive}.
3348 @item -x @tab @ref{--extract}.
3350 @item -z @tab @ref{--gzip}.
3355 @section @GNUTAR{} documentation
3357 @cindex Getting program version number
3359 @cindex Version of the @command{tar} program
3360 Being careful, the first thing is really checking that you are using
3361 @GNUTAR{}, indeed. The @option{--version} option
3362 causes @command{tar} to print information about its name, version,
3363 origin and legal status, all on standard output, and then exit
3364 successfully. For example, @w{@samp{tar --version}} might print:
3367 tar (GNU tar) @value{VERSION}
3368 Copyright (C) 2006 Free Software Foundation, Inc.
3369 This is free software. You may redistribute copies of it under the terms
3370 of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
3371 There is NO WARRANTY, to the extent permitted by law.
3373 Written by John Gilmore and Jay Fenlason.
3377 The first occurrence of @samp{tar} in the result above is the program
3378 name in the package (for example, @command{rmt} is another program),
3379 while the second occurrence of @samp{tar} is the name of the package
3380 itself, containing possibly many programs. The package is currently
3381 named @samp{tar}, after the name of the main program it
3382 contains@footnote{There are plans to merge the @command{cpio} and
3383 @command{tar} packages into a single one which would be called
3384 @code{paxutils}. So, who knows if, one of this days, the
3385 @option{--version} would not output @w{@samp{tar (@acronym{GNU}
3388 @cindex Obtaining help
3389 @cindex Listing all @command{tar} options
3390 @xopindex{help, introduction}
3391 Another thing you might want to do is checking the spelling or meaning
3392 of some particular @command{tar} option, without resorting to this
3393 manual, for once you have carefully read it. @GNUTAR{}
3394 has a short help feature, triggerable through the
3395 @option{--help} option. By using this option, @command{tar} will
3396 print a usage message listing all available options on standard
3397 output, then exit successfully, without doing anything else and
3398 ignoring all other options. Even if this is only a brief summary, it
3399 may be several screens long. So, if you are not using some kind of
3400 scrollable window, you might prefer to use something like:
3403 $ @kbd{tar --help | less}
3407 presuming, here, that you like using @command{less} for a pager. Other
3408 popular pagers are @command{more} and @command{pg}. If you know about some
3409 @var{keyword} which interests you and do not want to read all the
3410 @option{--help} output, another common idiom is doing:
3413 tar --help | grep @var{keyword}
3417 for getting only the pertinent lines. Notice, however, that some
3418 @command{tar} options have long description lines and the above
3419 command will list only the first of them.
3421 The exact look of the option summary displayed by @kbd{tar --help} is
3422 configurable. @xref{Configuring Help Summary}, for a detailed description.
3425 If you only wish to check the spelling of an option, running @kbd{tar
3426 --usage} may be a better choice. This will display a terse list of
3427 @command{tar} option without accompanying explanations.
3429 The short help output is quite succinct, and you might have to get
3430 back to the full documentation for precise points. If you are reading
3431 this paragraph, you already have the @command{tar} manual in some
3432 form. This manual is available in a variety of forms from
3433 @url{http://www.gnu.org/software/tar/manual}. It may be printed out of the @GNUTAR{}
3434 distribution, provided you have @TeX{} already installed somewhere,
3435 and a laser printer around. Just configure the distribution, execute
3436 the command @w{@samp{make dvi}}, then print @file{doc/tar.dvi} the
3437 usual way (contact your local guru to know how). If @GNUTAR{}
3438 has been conveniently installed at your place, this
3439 manual is also available in interactive, hypertextual form as an Info
3440 file. Just call @w{@samp{info tar}} or, if you do not have the
3441 @command{info} program handy, use the Info reader provided within
3442 @acronym{GNU} Emacs, calling @samp{tar} from the main Info menu.
3444 There is currently no @code{man} page for @GNUTAR{}.
3445 If you observe such a @code{man} page on the system you are running,
3446 either it does not belong to @GNUTAR{}, or it has not
3447 been produced by @acronym{GNU}. Some package maintainers convert
3448 @kbd{tar --help} output to a man page, using @command{help2man}. In
3449 any case, please bear in mind that the authoritative source of
3450 information about @GNUTAR{} is this Texinfo documentation.
3453 @section Obtaining @GNUTAR{} default values
3455 @opindex show-defaults
3456 @GNUTAR{} has some predefined defaults that are used when you do not
3457 explicitly specify another values. To obtain a list of such
3458 defaults, use @option{--show-defaults} option. This will output the
3459 values in the form of @command{tar} command line options:
3463 @kbd{tar --show-defaults}
3464 --format=gnu -f- -b20 --quoting-style=escape
3465 --rmt-command=/etc/rmt --rsh-command=/usr/bin/rsh
3470 Notice, that this option outputs only one line. The example output above
3471 has been split to fit page boundaries.
3474 The above output shows that this version of @GNUTAR{} defaults to
3475 using @samp{gnu} archive format (@pxref{Formats}), it uses standard
3476 output as the archive, if no @option{--file} option has been given
3477 (@pxref{file tutorial}), the default blocking factor is 20
3478 (@pxref{Blocking Factor}). It also shows the default locations where
3479 @command{tar} will look for @command{rmt} and @command{rsh} binaries.
3482 @section Checking @command{tar} progress
3484 Typically, @command{tar} performs most operations without reporting any
3485 information to the user except error messages. When using @command{tar}
3486 with many options, particularly ones with complicated or
3487 difficult-to-predict behavior, it is possible to make serious mistakes.
3488 @command{tar} provides several options that make observing @command{tar}
3489 easier. These options cause @command{tar} to print information as it
3490 progresses in its job, and you might want to use them just for being
3491 more careful about what is going on, or merely for entertaining
3492 yourself. If you have encountered a problem when operating on an
3493 archive, however, you may need more information than just an error
3494 message in order to solve the problem. The following options can be
3495 helpful diagnostic tools.
3497 @cindex Verbose operation
3499 Normally, the @option{--list} (@option{-t}) command to list an archive
3500 prints just the file names (one per line) and the other commands are
3501 silent. When used with most operations, the @option{--verbose}
3502 (@option{-v}) option causes @command{tar} to print the name of each
3503 file or archive member as it is processed. This and the other options
3504 which make @command{tar} print status information can be useful in
3505 monitoring @command{tar}.
3507 With @option{--create} or @option{--extract}, @option{--verbose} used
3508 once just prints the names of the files or members as they are processed.
3509 Using it twice causes @command{tar} to print a longer listing
3510 (@xref{verbose member listing}, for the description) for each member.
3511 Since @option{--list} already prints the names of the members,
3512 @option{--verbose} used once with @option{--list} causes @command{tar}
3513 to print an @samp{ls -l} type listing of the files in the archive.
3514 The following examples both extract members with long list output:
3517 $ @kbd{tar --extract --file=archive.tar --verbose --verbose}
3518 $ @kbd{tar xvvf archive.tar}
3521 Verbose output appears on the standard output except when an archive is
3522 being written to the standard output, as with @samp{tar --create
3523 --file=- --verbose} (@samp{tar cfv -}, or even @samp{tar cv}---if the
3524 installer let standard output be the default archive). In that case
3525 @command{tar} writes verbose output to the standard error stream.
3527 If @option{--index-file=@var{file}} is specified, @command{tar} sends
3528 verbose output to @var{file} rather than to standard output or standard
3532 @cindex Obtaining total status information
3534 The @option{--totals} option causes @command{tar} to print on the
3535 standard error the total amount of bytes transferred when processing
3536 an archive. When creating or appending to an archive, this option
3537 prints the number of bytes written to the archive and the average
3538 speed at which they have been written, e.g.:
3542 $ @kbd{tar -c -f archive.tar --totals /home}
3543 Total bytes written: 7924664320 (7.4GiB, 85MiB/s)
3547 When reading an archive, this option displays the number of bytes
3552 $ @kbd{tar -x -f archive.tar --totals}
3553 Total bytes read: 7924664320 (7.4GiB, 95MiB/s)
3557 Finally, when deleting from an archive, the @option{--totals} option
3558 displays both numbers plus number of bytes removed from the archive:
3562 $ @kbd{tar --delete -f foo.tar --totals --wildcards '*~'}
3563 Total bytes read: 9543680 (9.2MiB, 201MiB/s)
3564 Total bytes written: 3829760 (3.7MiB, 81MiB/s)
3565 Total bytes deleted: 1474048
3569 You can also obtain this information on request. When
3570 @option{--totals} is used with an argument, this argument is
3571 interpreted as a symbolic name of a signal, upon delivery of which the
3572 statistics is to be printed:
3575 @item --totals=@var{signo}
3576 Print statistics upon delivery of signal @var{signo}. Valid arguments
3577 are: @code{SIGHUP}, @code{SIGQUIT}, @code{SIGINT}, @code{SIGUSR1} and
3578 @code{SIGUSR2}. Shortened names without @samp{SIG} prefix are also
3582 Both forms of @option{--totals} option can be used simultaneously.
3583 Thus, @kbd{tar -x --totals --totals=USR1} instructs @command{tar} to
3584 extract all members from its default archive and print statistics
3585 after finishing the extraction, as well as when receiving signal
3588 @anchor{Progress information}
3589 @cindex Progress information
3591 The @option{--checkpoint} option prints an occasional message
3592 as @command{tar} reads or writes the archive. It is designed for
3593 those who don't need the more detailed (and voluminous) output of
3594 @option{--block-number} (@option{-R}), but do want visual confirmation
3595 that @command{tar} is actually making forward progress. By default it
3596 prints a message each 10 records read or written. This can be changed
3597 by giving it a numeric argument after an equal sign:
3600 $ @kbd{tar -c --checkpoint=1000} /var
3601 tar: Write checkpoint 1000
3602 tar: Write checkpoint 2000
3603 tar: Write checkpoint 3000
3606 This example shows the default checkpoint message used by
3607 @command{tar}. If you place a dot immediately after the equal
3608 sign, it will print a @samp{.} at each checkpoint. For example:
3611 $ @kbd{tar -c --checkpoint=.1000} /var
3615 @opindex show-omitted-dirs
3616 @anchor{show-omitted-dirs}
3617 The @option{--show-omitted-dirs} option, when reading an archive---with
3618 @option{--list} or @option{--extract}, for example---causes a message
3619 to be printed for each directory in the archive which is skipped.
3620 This happens regardless of the reason for skipping: the directory might
3621 not have been named on the command line (implicitly or explicitly),
3622 it might be excluded by the use of the
3623 @option{--exclude=@var{pattern}} option, or some other reason.
3625 @opindex block-number
3626 @cindex Block number where error occurred
3627 @anchor{block-number}
3628 If @option{--block-number} (@option{-R}) is used, @command{tar} prints, along with
3629 every message it would normally produce, the block number within the
3630 archive where the message was triggered. Also, supplementary messages
3631 are triggered when reading blocks full of NULs, or when hitting end of
3632 file on the archive. As of now, if the archive if properly terminated
3633 with a NUL block, the reading of the file may stop before end of file
3634 is met, so the position of end of file will not usually show when
3635 @option{--block-number} (@option{-R}) is used. Note that @GNUTAR{}
3636 drains the archive before exiting when reading the
3637 archive from a pipe.
3639 @cindex Error message, block number of
3640 This option is especially useful when reading damaged archives, since
3641 it helps pinpoint the damaged sections. It can also be used with
3642 @option{--list} (@option{-t}) when listing a file-system backup tape, allowing you to
3643 choose among several backup tapes when retrieving a file later, in
3644 favor of the tape where the file appears earliest (closest to the
3645 front of the tape). @xref{backup}.
3648 @section Asking for Confirmation During Operations
3649 @cindex Interactive operation
3651 Typically, @command{tar} carries out a command without stopping for
3652 further instructions. In some situations however, you may want to
3653 exclude some files and archive members from the operation (for instance
3654 if disk or storage space is tight). You can do this by excluding
3655 certain files automatically (@pxref{Choosing}), or by performing
3656 an operation interactively, using the @option{--interactive} (@option{-w}) option.
3657 @command{tar} also accepts @option{--confirmation} for this option.
3659 @opindex interactive
3660 When the @option{--interactive} (@option{-w}) option is specified, before
3661 reading, writing, or deleting files, @command{tar} first prints a message
3662 for each such file, telling what operation it intends to take, then asks
3663 for confirmation on the terminal. The actions which require
3664 confirmation include adding a file to the archive, extracting a file
3665 from the archive, deleting a file from the archive, and deleting a file
3666 from disk. To confirm the action, you must type a line of input
3667 beginning with @samp{y}. If your input line begins with anything other
3668 than @samp{y}, @command{tar} skips that file.
3670 If @command{tar} is reading the archive from the standard input,
3671 @command{tar} opens the file @file{/dev/tty} to support the interactive
3674 Verbose output is normally sent to standard output, separate from
3675 other error messages. However, if the archive is produced directly
3676 on standard output, then verbose output is mixed with errors on
3677 @code{stderr}. Producing the archive on standard output may be used
3678 as a way to avoid using disk space, when the archive is soon to be
3679 consumed by another process reading it, say. Some people felt the need
3680 of producing an archive on stdout, still willing to segregate between
3681 verbose output and error output. A possible approach would be using a
3682 named pipe to receive the archive, and having the consumer process to
3683 read from that named pipe. This has the advantage of letting standard
3684 output free to receive verbose output, all separate from errors.
3687 @chapter @GNUTAR{} Operations
3700 @section Basic @GNUTAR{} Operations
3702 The basic @command{tar} operations, @option{--create} (@option{-c}),
3703 @option{--list} (@option{-t}) and @option{--extract} (@option{--get},
3704 @option{-x}), are currently presented and described in the tutorial
3705 chapter of this manual. This section provides some complementary notes
3706 for these operations.
3709 @xopindex{create, complementary notes}
3713 Creating an empty archive would have some kind of elegance. One can
3714 initialize an empty archive and later use @option{--append}
3715 (@option{-r}) for adding all members. Some applications would not
3716 welcome making an exception in the way of adding the first archive
3717 member. On the other hand, many people reported that it is
3718 dangerously too easy for @command{tar} to destroy a magnetic tape with
3719 an empty archive@footnote{This is well described in @cite{Unix-haters
3720 Handbook}, by Simson Garfinkel, Daniel Weise & Steven Strassmann, IDG
3721 Books, ISBN 1-56884-203-1.}. The two most common errors are:
3725 Mistakingly using @code{create} instead of @code{extract}, when the
3726 intent was to extract the full contents of an archive. This error
3727 is likely: keys @kbd{c} and @kbd{x} are right next to each other on
3728 the QWERTY keyboard. Instead of being unpacked, the archive then
3729 gets wholly destroyed. When users speak about @dfn{exploding} an
3730 archive, they usually mean something else :-).
3733 Forgetting the argument to @code{file}, when the intent was to create
3734 an archive with a single file in it. This error is likely because a
3735 tired user can easily add the @kbd{f} key to the cluster of option
3736 letters, by the mere force of habit, without realizing the full
3737 consequence of doing so. The usual consequence is that the single
3738 file, which was meant to be saved, is rather destroyed.
3741 So, recognizing the likelihood and the catastrophic nature of these
3742 errors, @GNUTAR{} now takes some distance from elegance, and
3743 cowardly refuses to create an archive when @option{--create} option is
3744 given, there are no arguments besides options, and
3745 @option{--files-from} (@option{-T}) option is @emph{not} used. To get
3746 around the cautiousness of @GNUTAR{} and nevertheless create an
3747 archive with nothing in it, one may still use, as the value for the
3748 @option{--files-from} option, a file with no names in it, as shown in
3749 the following commands:
3752 @kbd{tar --create --file=empty-archive.tar --files-from=/dev/null}
3753 @kbd{tar cfT empty-archive.tar /dev/null}
3756 @xopindex{extract, complementary notes}
3761 A socket is stored, within a @GNUTAR{} archive, as a pipe.
3763 @item @option{--list} (@option{-t})
3765 @GNUTAR{} now shows dates as @samp{1996-08-30},
3766 while it used to show them as @samp{Aug 30 1996}. Preferably,
3767 people should get used to ISO 8601 dates. Local American dates should
3768 be made available again with full date localization support, once
3769 ready. In the meantime, programs not being localizable for dates
3770 should prefer international dates, that's really the way to go.
3772 Look up @url{http://www.cl.cam.ac.uk/@/~mgk25/@/iso-time.html} if you
3773 are curious, it contains a detailed explanation of the ISO 8601 standard.
3778 @section Advanced @GNUTAR{} Operations
3780 Now that you have learned the basics of using @GNUTAR{}, you may want
3781 to learn about further ways in which @command{tar} can help you.
3783 This chapter presents five, more advanced operations which you probably
3784 won't use on a daily basis, but which serve more specialized functions.
3785 We also explain the different styles of options and why you might want
3786 to use one or another, or a combination of them in your @command{tar}
3787 commands. Additionally, this chapter includes options which allow you to
3788 define the output from @command{tar} more carefully, and provide help and
3789 error correction in special circumstances.
3791 @FIXME{check this after the chapter is actually revised to make sure
3792 it still introduces the info in the chapter correctly : ).}
3804 @subsection The Five Advanced @command{tar} Operations
3807 In the last chapter, you learned about the first three operations to
3808 @command{tar}. This chapter presents the remaining five operations to
3809 @command{tar}: @option{--append}, @option{--update}, @option{--concatenate},
3810 @option{--delete}, and @option{--compare}.
3812 You are not likely to use these operations as frequently as those
3813 covered in the last chapter; however, since they perform specialized
3814 functions, they are quite useful when you do need to use them. We
3815 will give examples using the same directory and files that you created
3816 in the last chapter. As you may recall, the directory is called
3817 @file{practice}, the files are @samp{jazz}, @samp{blues}, @samp{folk},
3818 @samp{rock}, and the two archive files you created are
3819 @samp{collection.tar} and @samp{music.tar}.
3821 We will also use the archive files @samp{afiles.tar} and
3822 @samp{bfiles.tar}. The archive @samp{afiles.tar} contains the members @samp{apple},
3823 @samp{angst}, and @samp{aspic}; @samp{bfiles.tar} contains the members
3824 @samp{./birds}, @samp{baboon}, and @samp{./box}.
3826 Unless we state otherwise, all practicing you do and examples you follow
3827 in this chapter will take place in the @file{practice} directory that
3828 you created in the previous chapter; see @ref{prepare for examples}.
3829 (Below in this section, we will remind you of the state of the examples
3830 where the last chapter left them.)
3832 The five operations that we will cover in this chapter are:
3837 Add new entries to an archive that already exists.
3840 Add more recent copies of archive members to the end of an archive, if
3845 Add one or more pre-existing archives to the end of another archive.
3847 Delete items from an archive (does not work on tapes).
3851 Compare archive members to their counterparts in the file system.
3855 @subsection How to Add Files to Existing Archives: @option{--append}
3859 If you want to add files to an existing archive, you don't need to
3860 create a new archive; you can use @option{--append} (@option{-r}).
3861 The archive must already exist in order to use @option{--append}. (A
3862 related operation is the @option{--update} operation; you can use this
3863 to add newer versions of archive members to an existing archive. To learn how to
3864 do this with @option{--update}, @pxref{update}.)
3866 If you use @option{--append} to add a file that has the same name as an
3867 archive member to an archive containing that archive member, then the
3868 old member is not deleted. What does happen, however, is somewhat
3869 complex. @command{tar} @emph{allows} you to have infinite number of files
3870 with the same name. Some operations treat these same-named members no
3871 differently than any other set of archive members: for example, if you
3872 view an archive with @option{--list} (@option{-t}), you will see all
3873 of those members listed, with their data modification times, owners, etc.
3875 Other operations don't deal with these members as perfectly as you might
3876 prefer; if you were to use @option{--extract} to extract the archive,
3877 only the most recently added copy of a member with the same name as four
3878 other members would end up in the working directory. This is because
3879 @option{--extract} extracts an archive in the order the members appeared
3880 in the archive; the most recently archived members will be extracted
3881 last. Additionally, an extracted member will @emph{replace} a file of
3882 the same name which existed in the directory already, and @command{tar}
3883 will not prompt you about this@footnote{Unless you give it
3884 @option{--keep-old-files} option, or the disk copy is newer than the
3885 the one in the archive and you invoke @command{tar} with
3886 @option{--keep-newer-files} option}. Thus, only the most recently archived
3887 member will end up being extracted, as it will replace the one
3888 extracted before it, and so on.
3890 There exists a special option that allows you to get around this
3891 behavior and extract (or list) only a particular copy of the file.
3892 This is @option{--occurrence} option. If you run @command{tar} with
3893 this option, it will extract only the first copy of the file. You
3894 may also give this option an argument specifying the number of
3895 copy to be extracted. Thus, for example if the archive
3896 @file{archive.tar} contained three copies of file @file{myfile}, then
3900 tar --extract --file archive.tar --occurrence=2 myfile
3904 would extract only the second copy. @xref{Option
3905 Summary,---occurrence}, for the description of @option{--occurrence}
3908 @FIXME{ hag -- you might want to incorporate some of the above into the
3909 MMwtSN node; not sure. i didn't know how to make it simpler...
3911 There are a few ways to get around this. (maybe xref Multiple Members
3912 with the Same Name.}
3914 @cindex Members, replacing with other members
3915 @cindex Replacing members with other members
3916 If you want to replace an archive member, use @option{--delete} to
3917 delete the member you want to remove from the archive, , and then use
3918 @option{--append} to add the member you want to be in the archive. Note
3919 that you can not change the order of the archive; the most recently
3920 added member will still appear last. In this sense, you cannot truly
3921 ``replace'' one member with another. (Replacing one member with another
3922 will not work on certain types of media, such as tapes; see @ref{delete}
3923 and @ref{Media}, for more information.)
3926 * appending files:: Appending Files to an Archive
3930 @node appending files
3931 @subsubsection Appending Files to an Archive
3933 @cindex Adding files to an Archive
3934 @cindex Appending files to an Archive
3935 @cindex Archives, Appending files to
3937 The simplest way to add a file to an already existing archive is the
3938 @option{--append} (@option{-r}) operation, which writes specified
3939 files into the archive whether or not they are already among the
3942 When you use @option{--append}, you @emph{must} specify file name
3943 arguments, as there is no default. If you specify a file that already
3944 exists in the archive, another copy of the file will be added to the
3945 end of the archive. As with other operations, the member names of the
3946 newly added files will be exactly the same as their names given on the
3947 command line. The @option{--verbose} (@option{-v}) option will print
3948 out the names of the files as they are written into the archive.
3950 @option{--append} cannot be performed on some tape drives, unfortunately,
3951 due to deficiencies in the formats those tape drives use. The archive
3952 must be a valid @command{tar} archive, or else the results of using this
3953 operation will be unpredictable. @xref{Media}.
3955 To demonstrate using @option{--append} to add a file to an archive,
3956 create a file called @file{rock} in the @file{practice} directory.
3957 Make sure you are in the @file{practice} directory. Then, run the
3958 following @command{tar} command to add @file{rock} to
3959 @file{collection.tar}:
3962 $ @kbd{tar --append --file=collection.tar rock}
3966 If you now use the @option{--list} (@option{-t}) operation, you will see that
3967 @file{rock} has been added to the archive:
3970 $ @kbd{tar --list --file=collection.tar}
3971 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
3972 -rw-r--r-- me user 21 1996-09-23 16:44 blues
3973 -rw-r--r-- me user 20 1996-09-23 16:44 folk
3974 -rw-r--r-- me user 20 1996-09-23 16:44 rock
3978 @subsubsection Multiple Members with the Same Name
3980 You can use @option{--append} (@option{-r}) to add copies of files
3981 which have been updated since the archive was created. (However, we
3982 do not recommend doing this since there is another @command{tar}
3983 option called @option{--update}; @xref{update}, for more information.
3984 We describe this use of @option{--append} here for the sake of
3985 completeness.) When you extract the archive, the older version will
3986 be effectively lost. This works because files are extracted from an
3987 archive in the order in which they were archived. Thus, when the
3988 archive is extracted, a file archived later in time will replace a
3989 file of the same name which was archived earlier, even though the
3990 older version of the file will remain in the archive unless you delete
3991 all versions of the file.
3993 Supposing you change the file @file{blues} and then append the changed
3994 version to @file{collection.tar}. As you saw above, the original
3995 @file{blues} is in the archive @file{collection.tar}. If you change the
3996 file and append the new version of the file to the archive, there will
3997 be two copies in the archive. When you extract the archive, the older
3998 version of the file will be extracted first, and then replaced by the
3999 newer version when it is extracted.
4001 You can append the new, changed copy of the file @file{blues} to the
4002 archive in this way:
4005 $ @kbd{tar --append --verbose --file=collection.tar blues}
4010 Because you specified the @option{--verbose} option, @command{tar} has
4011 printed the name of the file being appended as it was acted on. Now
4012 list the contents of the archive:
4015 $ @kbd{tar --list --verbose --file=collection.tar}
4016 -rw-r--r-- me user 28 1996-10-18 16:31 jazz
4017 -rw-r--r-- me user 21 1996-09-23 16:44 blues
4018 -rw-r--r-- me user 20 1996-09-23 16:44 folk
4019 -rw-r--r-- me user 20 1996-09-23 16:44 rock
4020 -rw-r--r-- me user 58 1996-10-24 18:30 blues
4024 The newest version of @file{blues} is now at the end of the archive
4025 (note the different creation dates and file sizes). If you extract
4026 the archive, the older version of the file @file{blues} will be
4027 replaced by the newer version. You can confirm this by extracting
4028 the archive and running @samp{ls} on the directory.
4030 If you wish to extract the first occurrence of the file @file{blues}
4031 from the archive, use @option{--occurrence} option, as shown in
4032 the following example:
4035 $ @kbd{tar --extract -vv --occurrence --file=collection.tar blues}
4036 -rw-r--r-- me user 21 1996-09-23 16:44 blues
4039 @xref{Writing}, for more information on @option{--extract} and
4040 @xref{Option Summary, --occurrence}, for the description of
4041 @option{--occurrence} option.
4044 @subsection Updating an Archive
4046 @cindex Updating an archive
4049 In the previous section, you learned how to use @option{--append} to
4050 add a file to an existing archive. A related operation is
4051 @option{--update} (@option{-u}). The @option{--update} operation
4052 updates a @command{tar} archive by comparing the date of the specified
4053 archive members against the date of the file with the same name. If
4054 the file has been modified more recently than the archive member, then
4055 the newer version of the file is added to the archive (as with
4058 Unfortunately, you cannot use @option{--update} with magnetic tape drives.
4059 The operation will fail.
4061 @FIXME{other examples of media on which --update will fail? need to ask
4062 charles and/or mib/thomas/dave shevett..}
4064 Both @option{--update} and @option{--append} work by adding to the end
4065 of the archive. When you extract a file from the archive, only the
4066 version stored last will wind up in the file system, unless you use
4067 the @option{--backup} option. @xref{multiple}, for a detailed discussion.
4074 @subsubsection How to Update an Archive Using @option{--update}
4076 You must use file name arguments with the @option{--update}
4077 (@option{-u}) operation. If you don't specify any files,
4078 @command{tar} won't act on any files and won't tell you that it didn't
4079 do anything (which may end up confusing you).
4081 @c note: the above parenthetical added because in fact, this
4082 @c behavior just confused the author. :-)
4084 To see the @option{--update} option at work, create a new file,
4085 @file{classical}, in your practice directory, and some extra text to the
4086 file @file{blues}, using any text editor. Then invoke @command{tar} with
4087 the @samp{update} operation and the @option{--verbose} (@option{-v})
4088 option specified, using the names of all the files in the practice
4089 directory as file name arguments:
4092 $ @kbd{tar --update -v -f collection.tar blues folk rock classical}
4099 Because we have specified verbose mode, @command{tar} prints out the names
4100 of the files it is working on, which in this case are the names of the
4101 files that needed to be updated. If you run @samp{tar --list} and look
4102 at the archive, you will see @file{blues} and @file{classical} at its
4103 end. There will be a total of two versions of the member @samp{blues};
4104 the one at the end will be newer and larger, since you added text before
4107 (The reason @command{tar} does not overwrite the older file when updating
4108 it is because writing to the middle of a section of tape is a difficult
4109 process. Tapes are not designed to go backward. @xref{Media}, for more
4110 information about tapes.
4112 @option{--update} (@option{-u}) is not suitable for performing backups for two
4113 reasons: it does not change directory content entries, and it
4114 lengthens the archive every time it is used. The @GNUTAR{}
4115 options intended specifically for backups are more
4116 efficient. If you need to run backups, please consult @ref{Backups}.
4119 @subsection Combining Archives with @option{--concatenate}
4121 @cindex Adding archives to an archive
4122 @cindex Concatenating Archives
4123 @opindex concatenate
4125 @c @cindex @option{-A} described
4126 Sometimes it may be convenient to add a second archive onto the end of
4127 an archive rather than adding individual files to the archive. To add
4128 one or more archives to the end of another archive, you should use the
4129 @option{--concatenate} (@option{--catenate}, @option{-A}) operation.
4131 To use @option{--concatenate}, give the first archive with
4132 @option{--file} option and name the rest of archives to be
4133 concatenated on the command line. The members, and their member
4134 names, will be copied verbatim from those archives to the first one.
4135 @footnote{This can cause multiple members to have the same name, for
4136 information on how this affects reading the archive, @ref{multiple}.}
4137 The new, concatenated archive will be called by the same name as the
4138 one given with the @option{--file} option. As usual, if you omit
4139 @option{--file}, @command{tar} will use the value of the environment
4140 variable @env{TAPE}, or, if this has not been set, the default archive name.
4142 @FIXME{There is no way to specify a new name...}
4144 To demonstrate how @option{--concatenate} works, create two small archives
4145 called @file{bluesrock.tar} and @file{folkjazz.tar}, using the relevant
4146 files from @file{practice}:
4149 $ @kbd{tar -cvf bluesrock.tar blues rock}
4152 $ @kbd{tar -cvf folkjazz.tar folk jazz}
4158 If you like, You can run @samp{tar --list} to make sure the archives
4159 contain what they are supposed to:
4162 $ @kbd{tar -tvf bluesrock.tar}
4163 -rw-r--r-- melissa user 105 1997-01-21 19:42 blues
4164 -rw-r--r-- melissa user 33 1997-01-20 15:34 rock
4165 $ @kbd{tar -tvf jazzfolk.tar}
4166 -rw-r--r-- melissa user 20 1996-09-23 16:44 folk
4167 -rw-r--r-- melissa user 65 1997-01-30 14:15 jazz
4170 We can concatenate these two archives with @command{tar}:
4174 $ @kbd{tar --concatenate --file=bluesrock.tar jazzfolk.tar}
4177 If you now list the contents of the @file{bluesrock.tar}, you will see
4178 that now it also contains the archive members of @file{jazzfolk.tar}:
4181 $ @kbd{tar --list --file=bluesrock.tar}
4188 When you use @option{--concatenate}, the source and target archives must
4189 already exist and must have been created using compatible format
4190 parameters. Notice, that @command{tar} does not check whether the
4191 archives it concatenates have compatible formats, it does not
4192 even check if the files are really tar archives.
4194 Like @option{--append} (@option{-r}), this operation cannot be performed on some
4195 tape drives, due to deficiencies in the formats those tape drives use.
4197 @cindex @code{concatenate} vs @command{cat}
4198 @cindex @command{cat} vs @code{concatenate}
4199 It may seem more intuitive to you to want or try to use @command{cat} to
4200 concatenate two archives instead of using the @option{--concatenate}
4201 operation; after all, @command{cat} is the utility for combining files.
4203 However, @command{tar} archives incorporate an end-of-file marker which
4204 must be removed if the concatenated archives are to be read properly as
4205 one archive. @option{--concatenate} removes the end-of-archive marker
4206 from the target archive before each new archive is appended. If you use
4207 @command{cat} to combine the archives, the result will not be a valid
4208 @command{tar} format archive. If you need to retrieve files from an
4209 archive that was added to using the @command{cat} utility, use the
4210 @option{--ignore-zeros} (@option{-i}) option. @xref{Ignore Zeros}, for further
4211 information on dealing with archives improperly combined using the
4212 @command{cat} shell utility.
4215 @subsection Removing Archive Members Using @option{--delete}
4217 @cindex Deleting files from an archive
4218 @cindex Removing files from an archive
4221 You can remove members from an archive by using the @option{--delete}
4222 option. Specify the name of the archive with @option{--file}
4223 (@option{-f}) and then specify the names of the members to be deleted;
4224 if you list no member names, nothing will be deleted. The
4225 @option{--verbose} option will cause @command{tar} to print the names
4226 of the members as they are deleted. As with @option{--extract}, you
4227 must give the exact member names when using @samp{tar --delete}.
4228 @option{--delete} will remove all versions of the named file from the
4229 archive. The @option{--delete} operation can run very slowly.
4231 Unlike other operations, @option{--delete} has no short form.
4233 @cindex Tapes, using @option{--delete} and
4234 @cindex Deleting from tape archives
4235 This operation will rewrite the archive. You can only use
4236 @option{--delete} on an archive if the archive device allows you to
4237 write to any point on the media, such as a disk; because of this, it
4238 does not work on magnetic tapes. Do not try to delete an archive member
4239 from a magnetic tape; the action will not succeed, and you will be
4240 likely to scramble the archive and damage your tape. There is no safe
4241 way (except by completely re-writing the archive) to delete files from
4242 most kinds of magnetic tape. @xref{Media}.
4244 To delete all versions of the file @file{blues} from the archive
4245 @file{collection.tar} in the @file{practice} directory, make sure you
4246 are in that directory, and then,
4249 $ @kbd{tar --list --file=collection.tar}
4254 $ @kbd{tar --delete --file=collection.tar blues}
4255 $ @kbd{tar --list --file=collection.tar}
4262 @FIXME{Check if the above listing is actually produced after running
4263 all the examples on collection.tar.}
4265 The @option{--delete} option has been reported to work properly when
4266 @command{tar} acts as a filter from @code{stdin} to @code{stdout}.
4269 @subsection Comparing Archive Members with the File System
4270 @cindex Verifying the currency of an archive
4274 The @option{--compare} (@option{-d}), or @option{--diff} operation compares
4275 specified archive members against files with the same names, and then
4276 reports differences in file size, mode, owner, modification date and
4277 contents. You should @emph{only} specify archive member names, not file
4278 names. If you do not name any members, then @command{tar} will compare the
4279 entire archive. If a file is represented in the archive but does not
4280 exist in the file system, @command{tar} reports a difference.
4282 You have to specify the record size of the archive when modifying an
4283 archive with a non-default record size.
4285 @command{tar} ignores files in the file system that do not have
4286 corresponding members in the archive.
4288 The following example compares the archive members @file{rock},
4289 @file{blues} and @file{funk} in the archive @file{bluesrock.tar} with
4290 files of the same name in the file system. (Note that there is no file,
4291 @file{funk}; @command{tar} will report an error message.)
4294 $ @kbd{tar --compare --file=bluesrock.tar rock blues funk}
4297 tar: funk not found in archive
4300 The spirit behind the @option{--compare} (@option{--diff},
4301 @option{-d}) option is to check whether the archive represents the
4302 current state of files on disk, more than validating the integrity of
4303 the archive media. For this later goal, @xref{verify}.
4305 @node create options
4306 @section Options Used by @option{--create}
4308 @xopindex{create, additional options}
4309 The previous chapter described the basics of how to use
4310 @option{--create} (@option{-c}) to create an archive from a set of files.
4311 @xref{create}. This section described advanced options to be used with
4315 * override:: Overriding File Metadata.
4316 * Ignore Failed Read::
4320 @subsection Overriding File Metadata
4322 As described above, a @command{tar} archive keeps, for each member it contains,
4323 its @dfn{metadata}, such as modification time, mode and ownership of
4324 the file. @GNUTAR{} allows to replace these data with other values
4325 when adding files to the archive. The options described in this
4326 section affect creation of archives of any type. For POSIX archives,
4327 see also @ref{PAX keywords}, for additional ways of controlling
4328 metadata, stored in the archive.
4332 @item --mode=@var{permissions}
4334 When adding files to an archive, @command{tar} will use
4335 @var{permissions} for the archive members, rather than the permissions
4336 from the files. @var{permissions} can be specified either as an octal
4337 number or as symbolic permissions, like with
4338 @command{chmod} (@xref{File permissions, Permissions, File
4339 permissions, fileutils, @acronym{GNU} file utilities}. This reference
4340 also has useful information for those not being overly familiar with
4341 the UNIX permission system). Using latter syntax allows for
4342 more flexibility. For example, the value @samp{a+rw} adds read and write
4343 permissions for everybody, while retaining executable bits on directories
4344 or on any other file already marked as executable:
4347 $ @kbd{tar -c -f archive.tar --mode='a+rw' .}
4350 @item --mtime=@var{date}
4353 When adding files to an archive, @command{tar} will use @var{date} as
4354 the modification time of members when creating archives, instead of
4355 their actual modification times. The argument @var{date} can be
4356 either a textual date representation in almost arbitrary format
4357 (@pxref{Date input formats}) or a name of the existing file, starting
4358 with @samp{/} or @samp{.}. In the latter case, the modification time
4359 of that file will be used.
4361 The following example will set the modification date to 00:00:00 UTC,
4365 $ @kbd{tar -c -f archive.tar --mtime='1970-01-01' .}
4369 When used with @option{--verbose} (@pxref{verbose tutorial}) @GNUTAR{}
4370 will try to convert the specified date back to its textual
4371 representation and compare it with the one given with
4372 @option{--mtime} options. If the two dates differ, @command{tar} will
4373 print a warning saying what date it will use. This is to help user
4374 ensure he is using the right date.
4379 $ @kbd{tar -c -f archive.tar -v --mtime=yesterday .}
4380 tar: Option --mtime: Treating date `yesterday' as 2006-06-20
4385 @item --owner=@var{user}
4388 Specifies that @command{tar} should use @var{user} as the owner of members
4389 when creating archives, instead of the user associated with the source
4390 file. The argument @var{user} can be either an existing user symbolic
4391 name, or a decimal numeric user ID.
4393 There is no value indicating a missing number, and @samp{0} usually means
4394 @code{root}. Some people like to force @samp{0} as the value to offer in
4395 their distributions for the owner of files, because the @code{root} user is
4396 anonymous anyway, so that might as well be the owner of anonymous
4397 archives. For example:
4401 $ @kbd{tar -c -f archive.tar --owner=0 .}
4403 $ @kbd{tar -c -f archive.tar --owner=root .}
4407 @item --group=@var{group}
4410 Files added to the @command{tar} archive will have a group id of @var{group},
4411 rather than the group from the source file. The argument @var{group}
4412 can be either an existing group symbolic name, or a decimal numeric group ID.
4415 @node Ignore Failed Read
4416 @subsection Ignore Fail Read
4419 @item --ignore-failed-read
4420 @opindex ignore-failed-read
4421 Do not exit with nonzero on unreadable files or directories.
4424 @node extract options
4425 @section Options Used by @option{--extract}
4428 @xopindex{extract, additional options}
4429 The previous chapter showed how to use @option{--extract} to extract
4430 an archive into the file system. Various options cause @command{tar} to
4431 extract more information than just file contents, such as the owner,
4432 the permissions, the modification date, and so forth. This section
4433 presents options to be used with @option{--extract} when certain special
4434 considerations arise. You may review the information presented in
4435 @ref{extract} for more basic information about the
4436 @option{--extract} operation.
4439 * Reading:: Options to Help Read Archives
4440 * Writing:: Changing How @command{tar} Writes Files
4441 * Scarce:: Coping with Scarce Resources
4445 @subsection Options to Help Read Archives
4446 @cindex Options when reading archives
4449 @cindex Reading incomplete records
4450 @cindex Records, incomplete
4451 @opindex read-full-records
4452 Normally, @command{tar} will request data in full record increments from
4453 an archive storage device. If the device cannot return a full record,
4454 @command{tar} will report an error. However, some devices do not always
4455 return full records, or do not require the last record of an archive to
4456 be padded out to the next record boundary. To keep reading until you
4457 obtain a full record, or to accept an incomplete record if it contains
4458 an end-of-archive marker, specify the @option{--read-full-records} (@option{-B}) option
4459 in conjunction with the @option{--extract} or @option{--list} operations.
4462 The @option{--read-full-records} (@option{-B}) option is turned on by default when
4463 @command{tar} reads an archive from standard input, or from a remote
4464 machine. This is because on BSD Unix systems, attempting to read a
4465 pipe returns however much happens to be in the pipe, even if it is
4466 less than was requested. If this option were not enabled, @command{tar}
4467 would fail as soon as it read an incomplete record from the pipe.
4469 If you're not sure of the blocking factor of an archive, you can
4470 read the archive by specifying @option{--read-full-records} (@option{-B}) and
4471 @option{--blocking-factor=@var{512-size}} (@option{-b
4472 @var{512-size}}), using a blocking factor larger than what the archive
4473 uses. This lets you avoid having to determine the blocking factor
4474 of an archive. @xref{Blocking Factor}.
4477 * read full records::
4481 @node read full records
4482 @unnumberedsubsubsec Reading Full Records
4484 @FIXME{need sentence or so of intro here}
4487 @opindex read-full-records
4488 @item --read-full-records
4490 Use in conjunction with @option{--extract} (@option{--get},
4491 @option{-x}) to read an archive which contains incomplete records, or
4492 one which has a blocking factor less than the one specified.
4496 @unnumberedsubsubsec Ignoring Blocks of Zeros
4498 @cindex End-of-archive blocks, ignoring
4499 @cindex Ignoring end-of-archive blocks
4500 @opindex ignore-zeros
4501 Normally, @command{tar} stops reading when it encounters a block of zeros
4502 between file entries (which usually indicates the end of the archive).
4503 @option{--ignore-zeros} (@option{-i}) allows @command{tar} to
4504 completely read an archive which contains a block of zeros before the
4505 end (i.e., a damaged archive, or one that was created by concatenating
4506 several archives together).
4508 The @option{--ignore-zeros} (@option{-i}) option is turned off by default because many
4509 versions of @command{tar} write garbage after the end-of-archive entry,
4510 since that part of the media is never supposed to be read. @GNUTAR{}
4511 does not write after the end of an archive, but seeks to
4512 maintain compatibility among archiving utilities.
4515 @item --ignore-zeros
4517 To ignore blocks of zeros (i.e., end-of-archive entries) which may be
4518 encountered while reading an archive. Use in conjunction with
4519 @option{--extract} or @option{--list}.
4523 @subsection Changing How @command{tar} Writes Files
4526 @FIXME{Introductory paragraph}
4529 * Dealing with Old Files::
4530 * Overwrite Old Files::
4532 * Keep Newer Files::
4534 * Recursive Unlink::
4535 * Data Modification Times::
4536 * Setting Access Permissions::
4537 * Directory Modification Times and Permissions::
4538 * Writing to Standard Output::
4539 * Writing to an External Program::
4543 @node Dealing with Old Files
4544 @unnumberedsubsubsec Options Controlling the Overwriting of Existing Files
4546 @xopindex{overwrite-dir, introduced}
4547 When extracting files, if @command{tar} discovers that the extracted
4548 file already exists, it normally replaces the file by removing it before
4549 extracting it, to prevent confusion in the presence of hard or symbolic
4550 links. (If the existing file is a symbolic link, it is removed, not
4551 followed.) However, if a directory cannot be removed because it is
4552 nonempty, @command{tar} normally overwrites its metadata (ownership,
4553 permission, etc.). The @option{--overwrite-dir} option enables this
4554 default behavior. To be more cautious and preserve the metadata of
4555 such a directory, use the @option{--no-overwrite-dir} option.
4557 @cindex Overwriting old files, prevention
4558 @xopindex{keep-old-files, introduced}
4559 To be even more cautious and prevent existing files from being replaced, use
4560 the @option{--keep-old-files} (@option{-k}) option. It causes @command{tar} to refuse
4561 to replace or update a file that already exists, i.e., a file with the
4562 same name as an archive member prevents extraction of that archive
4563 member. Instead, it reports an error.
4565 @xopindex{overwrite, introduced}
4566 To be more aggressive about altering existing files, use the
4567 @option{--overwrite} option. It causes @command{tar} to overwrite
4568 existing files and to follow existing symbolic links when extracting.
4570 @cindex Protecting old files
4571 Some people argue that @GNUTAR{} should not hesitate
4572 to overwrite files with other files when extracting. When extracting
4573 a @command{tar} archive, they expect to see a faithful copy of the
4574 state of the file system when the archive was created. It is debatable
4575 that this would always be a proper behavior. For example, suppose one
4576 has an archive in which @file{usr/local} is a link to
4577 @file{usr/local2}. Since then, maybe the site removed the link and
4578 renamed the whole hierarchy from @file{/usr/local2} to
4579 @file{/usr/local}. Such things happen all the time. I guess it would
4580 not be welcome at all that @GNUTAR{} removes the
4581 whole hierarchy just to make room for the link to be reinstated
4582 (unless it @emph{also} simultaneously restores the full
4583 @file{/usr/local2}, of course!) @GNUTAR{} is indeed
4584 able to remove a whole hierarchy to reestablish a symbolic link, for
4585 example, but @emph{only if} @option{--recursive-unlink} is specified
4586 to allow this behavior. In any case, single files are silently
4589 @xopindex{unlink-first, introduced}
4590 Finally, the @option{--unlink-first} (@option{-U}) option can improve performance in
4591 some cases by causing @command{tar} to remove files unconditionally
4592 before extracting them.
4594 @node Overwrite Old Files
4595 @unnumberedsubsubsec Overwrite Old Files
4600 Overwrite existing files and directory metadata when extracting files
4603 This causes @command{tar} to write extracted files into the file system without
4604 regard to the files already on the system; i.e., files with the same
4605 names as archive members are overwritten when the archive is extracted.
4606 It also causes @command{tar} to extract the ownership, permissions,
4607 and time stamps onto any preexisting files or directories.
4608 If the name of a corresponding file name is a symbolic link, the file
4609 pointed to by the symbolic link will be overwritten instead of the
4610 symbolic link itself (if this is possible). Moreover, special devices,
4611 empty directories and even symbolic links are automatically removed if
4612 they are in the way of extraction.
4614 Be careful when using the @option{--overwrite} option, particularly when
4615 combined with the @option{--absolute-names} (@option{-P}) option, as this combination
4616 can change the contents, ownership or permissions of any file on your
4617 system. Also, many systems do not take kindly to overwriting files that
4618 are currently being executed.
4620 @opindex overwrite-dir
4621 @item --overwrite-dir
4622 Overwrite the metadata of directories when extracting files from an
4623 archive, but remove other files before extracting.
4626 @node Keep Old Files
4627 @unnumberedsubsubsec Keep Old Files
4630 @opindex keep-old-files
4631 @item --keep-old-files
4633 Do not replace existing files from archive. The
4634 @option{--keep-old-files} (@option{-k}) option prevents @command{tar}
4635 from replacing existing files with files with the same name from the
4636 archive. The @option{--keep-old-files} option is meaningless with
4637 @option{--list} (@option{-t}). Prevents @command{tar} from replacing
4638 files in the file system during extraction.
4641 @node Keep Newer Files
4642 @unnumberedsubsubsec Keep Newer Files
4645 @opindex keep-newer-files
4646 @item --keep-newer-files
4647 Do not replace existing files that are newer than their archive
4648 copies. This option is meaningless with @option{--list} (@option{-t}).
4652 @unnumberedsubsubsec Unlink First
4655 @opindex unlink-first
4656 @item --unlink-first
4658 Remove files before extracting over them.
4659 This can make @command{tar} run a bit faster if you know in advance
4660 that the extracted files all need to be removed. Normally this option
4661 slows @command{tar} down slightly, so it is disabled by default.
4664 @node Recursive Unlink
4665 @unnumberedsubsubsec Recursive Unlink
4668 @opindex recursive-unlink
4669 @item --recursive-unlink
4670 When this option is specified, try removing files and directory hierarchies
4671 before extracting over them. @emph{This is a dangerous option!}
4674 If you specify the @option{--recursive-unlink} option,
4675 @command{tar} removes @emph{anything} that keeps you from extracting a file
4676 as far as current permissions will allow it. This could include removal
4677 of the contents of a full directory hierarchy.
4679 @node Data Modification Times
4680 @unnumberedsubsubsec Setting Data Modification Times
4682 @cindex Data modification times of extracted files
4683 @cindex Modification times of extracted files
4684 Normally, @command{tar} sets the data modification times of extracted
4685 files to the corresponding times recorded for the files in the archive, but
4686 limits the permissions of extracted files by the current @code{umask}
4689 To set the data modification times of extracted files to the time when
4690 the files were extracted, use the @option{--touch} (@option{-m}) option in
4691 conjunction with @option{--extract} (@option{--get}, @option{-x}).
4697 Sets the data modification time of extracted archive members to the time
4698 they were extracted, not the time recorded for them in the archive.
4699 Use in conjunction with @option{--extract} (@option{--get}, @option{-x}).
4702 @node Setting Access Permissions
4703 @unnumberedsubsubsec Setting Access Permissions
4705 @cindex Permissions of extracted files
4706 @cindex Modes of extracted files
4707 To set the modes (access permissions) of extracted files to those
4708 recorded for those files in the archive, use @option{--same-permissions}
4709 in conjunction with the @option{--extract} (@option{--get},
4710 @option{-x}) operation.
4713 @opindex preserve-permissions
4714 @opindex same-permissions
4715 @item --preserve-permissions
4716 @itemx --same-permissions
4717 @c @itemx --ignore-umask
4719 Set modes of extracted archive members to those recorded in the
4720 archive, instead of current umask settings. Use in conjunction with
4721 @option{--extract} (@option{--get}, @option{-x}).
4724 @node Directory Modification Times and Permissions
4725 @unnumberedsubsubsec Directory Modification Times and Permissions
4727 After successfully extracting a file member, @GNUTAR{} normally
4728 restores its permissions and modification times, as described in the
4729 previous sections. This cannot be done for directories, because
4730 after extracting a directory @command{tar} will almost certainly
4731 extract files into that directory and this will cause the directory
4732 modification time to be updated. Moreover, restoring that directory
4733 permissions may not permit file creation within it. Thus, restoring
4734 directory permissions and modification times must be delayed at least
4735 until all files have been extracted into that directory. @GNUTAR{}
4736 restores directories using the following approach.
4738 The extracted directories are created with the mode specified in the
4739 archive, as modified by the umask of the user, which gives sufficient
4740 permissions to allow file creation. The meta-information about the
4741 directory is recorded in the temporary list of directories. When
4742 preparing to extract next archive member, @GNUTAR{} checks if the
4743 directory prefix of this file contains the remembered directory. If
4744 it does not, the program assumes that all files have been extracted
4745 into that directory, restores its modification time and permissions
4746 and removes its entry from the internal list. This approach allows
4747 to correctly restore directory meta-information in the majority of
4748 cases, while keeping memory requirements sufficiently small. It is
4749 based on the fact, that most @command{tar} archives use the predefined
4750 order of members: first the directory, then all the files and
4751 subdirectories in that directory.
4753 However, this is not always true. The most important exception are
4754 incremental archives (@pxref{Incremental Dumps}). The member order in
4755 an incremental archive is reversed: first all directory members are
4756 stored, followed by other (non-directory) members. So, when extracting
4757 from incremental archives, @GNUTAR{} alters the above procedure. It
4758 remembers all restored directories, and restores their meta-data
4759 only after the entire archive has been processed. Notice, that you do
4760 not need to specify any special options for that, as @GNUTAR{}
4761 automatically detects archives in incremental format.
4763 There may be cases, when such processing is required for normal archives
4764 too. Consider the following example:
4768 $ @kbd{tar --no-recursion -cvf archive \
4769 foo foo/file1 bar bar/file foo/file2}
4778 During the normal operation, after encountering @file{bar}
4779 @GNUTAR{} will assume that all files from the directory @file{foo}
4780 were already extracted and will therefore restore its timestamp and
4781 permission bits. However, after extracting @file{foo/file2} the
4782 directory timestamp will be offset again.
4784 To correctly restore directory meta-information in such cases, use
4785 @option{delay-directory-restore} command line option:
4788 @opindex delay-directory-restore
4789 @item --delay-directory-restore
4790 Delays restoring of the modification times and permissions of extracted
4791 directories until the end of extraction. This way, correct
4792 meta-information is restored even if the archive has unusual member
4795 @opindex no-delay-directory-restore
4796 @item --no-delay-directory-restore
4797 Cancel the effect of the previous @option{--delay-directory-restore}.
4798 Use this option if you have used @option{--delay-directory-restore} in
4799 @env{TAR_OPTIONS} variable (@pxref{TAR_OPTIONS}) and wish to
4800 temporarily disable it.
4803 @node Writing to Standard Output
4804 @unnumberedsubsubsec Writing to Standard Output
4806 @cindex Writing extracted files to standard output
4807 @cindex Standard output, writing extracted files to
4808 To write the extracted files to the standard output, instead of
4809 creating the files on the file system, use @option{--to-stdout} (@option{-O}) in
4810 conjunction with @option{--extract} (@option{--get}, @option{-x}). This option is useful if you are
4811 extracting files to send them through a pipe, and do not need to
4812 preserve them in the file system. If you extract multiple members,
4813 they appear on standard output concatenated, in the order they are
4814 found in the archive.
4820 Writes files to the standard output. Use only in conjunction with
4821 @option{--extract} (@option{--get}, @option{-x}). When this option is
4822 used, instead of creating the files specified, @command{tar} writes
4823 the contents of the files extracted to its standard output. This may
4824 be useful if you are only extracting the files in order to send them
4825 through a pipe. This option is meaningless with @option{--list}
4829 This can be useful, for example, if you have a tar archive containing
4830 a big file and don't want to store the file on disk before processing
4831 it. You can use a command like this:
4834 tar -xOzf foo.tgz bigfile | process
4837 or even like this if you want to process the concatenation of the files:
4840 tar -xOzf foo.tgz bigfile1 bigfile2 | process
4843 However, @option{--to-command} may be more convenient for use with
4844 multiple files. See the next section.
4846 @node Writing to an External Program
4847 @unnumberedsubsubsec Writing to an External Program
4849 You can instruct @command{tar} to send the contents of each extracted
4850 file to the standard input of an external program:
4854 @item --to-command=@var{command}
4855 Extract files and pipe their contents to the standard input of
4856 @var{command}. When this option is used, instead of creating the
4857 files specified, @command{tar} invokes @var{command} and pipes the
4858 contents of the files to its standard output. @var{Command} may
4859 contain command line arguments. The program is executed via
4860 @code{sh -c}. Notice, that @var{command} is executed once for each regular file
4861 extracted. Non-regular files (directories, etc.) are ignored when this
4865 The command can obtain the information about the file it processes
4866 from the following environment variables:
4869 @vrindex TAR_FILETYPE, to-command environment
4871 Type of the file. It is a single letter with the following meaning:
4873 @multitable @columnfractions 0.10 0.90
4874 @item f @tab Regular file
4875 @item d @tab Directory
4876 @item l @tab Symbolic link
4877 @item h @tab Hard link
4878 @item b @tab Block device
4879 @item c @tab Character device
4882 Currently only regular files are supported.
4884 @vrindex TAR_MODE, to-command environment
4886 File mode, an octal number.
4888 @vrindex TAR_FILENAME, to-command environment
4890 The name of the file.
4892 @vrindex TAR_REALNAME, to-command environment
4894 Name of the file as stored in the archive.
4896 @vrindex TAR_UNAME, to-command environment
4898 Name of the file owner.
4900 @vrindex TAR_GNAME, to-command environment
4902 Name of the file owner group.
4904 @vrindex TAR_ATIME, to-command environment
4906 Time of last access. It is a decimal number, representing seconds
4907 since the epoch. If the archive provides times with nanosecond
4908 precision, the nanoseconds are appended to the timestamp after a
4911 @vrindex TAR_MTIME, to-command environment
4913 Time of last modification.
4915 @vrindex TAR_CTIME, to-command environment
4917 Time of last status change.
4919 @vrindex TAR_SIZE, to-command environment
4923 @vrindex TAR_UID, to-command environment
4925 UID of the file owner.
4927 @vrindex TAR_GID, to-command environment
4929 GID of the file owner.
4932 In addition to these variables, @env{TAR_VERSION} contains the
4933 @GNUTAR{} version number.
4935 If @var{command} exits with a non-0 status, @command{tar} will print
4936 an error message similar to the following:
4939 tar: 2345: Child returned status 1
4942 Here, @samp{2345} is the PID of the finished process.
4944 If this behavior is not wanted, use @option{--ignore-command-error}:
4947 @opindex ignore-command-error
4948 @item --ignore-command-error
4949 Ignore exit codes of subprocesses. Notice that if the program
4950 exits on signal or otherwise terminates abnormally, the error message
4951 will be printed even if this option is used.
4953 @opindex no-ignore-command-error
4954 @item --no-ignore-command-error
4955 Cancel the effect of any previous @option{--ignore-command-error}
4956 option. This option is useful if you have set
4957 @option{--ignore-command-error} in @env{TAR_OPTIONS}
4958 (@pxref{TAR_OPTIONS}) and wish to temporarily cancel it.
4962 @unnumberedsubsubsec Removing Files
4964 @FIXME{The section is too terse. Something more to add? An example,
4968 @opindex remove-files
4969 @item --remove-files
4970 Remove files after adding them to the archive.
4974 @subsection Coping with Scarce Resources
4977 @cindex Small memory
4978 @cindex Running out of space
4986 @unnumberedsubsubsec Starting File
4989 @opindex starting-file
4990 @item --starting-file=@var{name}
4991 @itemx -K @var{name}
4992 Starts an operation in the middle of an archive. Use in conjunction
4993 with @option{--extract} (@option{--get}, @option{-x}) or @option{--list} (@option{-t}).
4996 @cindex Middle of the archive, starting in the
4997 If a previous attempt to extract files failed due to lack of disk
4998 space, you can use @option{--starting-file=@var{name}} (@option{-K
4999 @var{name}}) to start extracting only after member @var{name} of the
5000 archive. This assumes, of course, that there is now free space, or
5001 that you are now extracting into a different file system. (You could
5002 also choose to suspend @command{tar}, remove unnecessary files from
5003 the file system, and then restart the same @command{tar} operation.
5004 In this case, @option{--starting-file} is not necessary.
5005 @xref{Incremental Dumps}, @xref{interactive}, and @ref{exclude}.)
5008 @unnumberedsubsubsec Same Order
5011 @cindex Large lists of file names on small machines
5013 @opindex preserve-order
5015 @itemx --preserve-order
5017 To process large lists of file names on machines with small amounts of
5018 memory. Use in conjunction with @option{--compare} (@option{--diff},
5019 @option{-d}), @option{--list} (@option{-t}) or @option{--extract}
5020 (@option{--get}, @option{-x}).
5023 The @option{--same-order} (@option{--preserve-order}, @option{-s}) option tells @command{tar} that the list of file
5024 names to be listed or extracted is sorted in the same order as the
5025 files in the archive. This allows a large list of names to be used,
5026 even on a small machine that would not otherwise be able to hold all
5027 the names in memory at the same time. Such a sorted list can easily be
5028 created by running @samp{tar -t} on the archive and editing its output.
5030 This option is probably never needed on modern computer systems.
5033 @section Backup options
5035 @cindex backup options
5037 @GNUTAR{} offers options for making backups of files
5038 before writing new versions. These options control the details of
5039 these backups. They may apply to the archive itself before it is
5040 created or rewritten, as well as individual extracted members. Other
5041 @acronym{GNU} programs (@command{cp}, @command{install}, @command{ln},
5042 and @command{mv}, for example) offer similar options.
5044 Backup options may prove unexpectedly useful when extracting archives
5045 containing many members having identical name, or when extracting archives
5046 on systems having file name limitations, making different members appear
5047 has having similar names through the side-effect of name truncation.
5048 (This is true only if we have a good scheme for truncated backup names,
5049 which I'm not sure at all: I suspect work is needed in this area.)
5050 When any existing file is backed up before being overwritten by extraction,
5051 then clashing files are automatically be renamed to be unique, and the
5052 true name is kept for only the last file of a series of clashing files.
5053 By using verbose mode, users may track exactly what happens.
5055 At the detail level, some decisions are still experimental, and may
5056 change in the future, we are waiting comments from our users. So, please
5057 do not learn to depend blindly on the details of the backup features.
5058 For example, currently, directories themselves are never renamed through
5059 using these options, so, extracting a file over a directory still has
5060 good chances to fail. Also, backup options apply to created archives,
5061 not only to extracted members. For created archives, backups will not
5062 be attempted when the archive is a block or character device, or when it
5063 refers to a remote file.
5065 For the sake of simplicity and efficiency, backups are made by renaming old
5066 files prior to creation or extraction, and not by copying. The original
5067 name is restored if the file creation fails. If a failure occurs after a
5068 partial extraction of a file, both the backup and the partially extracted
5072 @item --backup[=@var{method}]
5074 @vindex VERSION_CONTROL
5076 Back up files that are about to be overwritten or removed.
5077 Without this option, the original versions are destroyed.
5079 Use @var{method} to determine the type of backups made.
5080 If @var{method} is not specified, use the value of the @env{VERSION_CONTROL}
5081 environment variable. And if @env{VERSION_CONTROL} is not set,
5082 use the @samp{existing} method.
5084 @vindex version-control @r{Emacs variable}
5085 This option corresponds to the Emacs variable @samp{version-control};
5086 the same values for @var{method} are accepted as in Emacs. This option
5087 also allows more descriptive names. The valid @var{method}s are:
5092 @cindex numbered @r{backup method}
5093 Always make numbered backups.
5097 @cindex existing @r{backup method}
5098 Make numbered backups of files that already have them, simple backups
5103 @cindex simple @r{backup method}
5104 Always make simple backups.
5108 @item --suffix=@var{suffix}
5110 @cindex backup suffix
5111 @vindex SIMPLE_BACKUP_SUFFIX
5112 Append @var{suffix} to each backup file made with @option{--backup}. If this
5113 option is not specified, the value of the @env{SIMPLE_BACKUP_SUFFIX}
5114 environment variable is used. And if @env{SIMPLE_BACKUP_SUFFIX} is not
5115 set, the default is @samp{~}, just as in Emacs.
5120 @section Notable @command{tar} Usages
5123 @FIXME{Using Unix file linking capability to recreate directory
5124 structures---linking files into one subdirectory and then
5125 @command{tar}ring that directory.}
5127 @FIXME{Nice hairy example using absolute-names, newer, etc.}
5130 You can easily use archive files to transport a group of files from
5131 one system to another: put all relevant files into an archive on one
5132 computer system, transfer the archive to another system, and extract
5133 the contents there. The basic transfer medium might be magnetic tape,
5134 Internet FTP, or even electronic mail (though you must encode the
5135 archive with @command{uuencode} in order to transport it properly by
5136 mail). Both machines do not have to use the same operating system, as
5137 long as they both support the @command{tar} program.
5139 For example, here is how you might copy a directory's contents from
5140 one disk to another, while preserving the dates, modes, owners and
5141 link-structure of all the files therein. In this case, the transfer
5142 medium is a @dfn{pipe}, which is one a Unix redirection mechanism:
5145 $ @kbd{(cd sourcedir; tar -cf - .) | (cd targetdir; tar -xf -)}
5149 You can avoid subshells by using @option{-C} option:
5152 $ @kbd{tar -C sourcedir -cf - . | tar -C targetdir -xf -}
5156 The command also works using short option forms:
5159 $ @kbd{(cd sourcedir; tar --create --file=- . ) \
5160 | (cd targetdir; tar --extract --file=-)}
5162 $ @kbd{tar --directory sourcedir --create --file=- . ) \
5163 | tar --directory targetdir --extract --file=-}
5167 This is one of the easiest methods to transfer a @command{tar} archive.
5170 @section Looking Ahead: The Rest of this Manual
5172 You have now seen how to use all eight of the operations available to
5173 @command{tar}, and a number of the possible options. The next chapter
5174 explains how to choose and change file and archive names, how to use
5175 files to store names of other files which you can then call as
5176 arguments to @command{tar} (this can help you save time if you expect to
5177 archive the same list of files a number of times), and so forth.
5178 @FIXME{in case it's not obvious, i'm making this up in some sense
5179 based on my limited memory of what the next chapter *really* does. i
5180 just wanted to flesh out this final section a little bit so i'd
5181 remember to stick it in here. :-)}
5183 If there are too many files to conveniently list on the command line,
5184 you can list the names in a file, and @command{tar} will read that file.
5187 There are various ways of causing @command{tar} to skip over some files,
5188 and not archive them. @xref{Choosing}.
5191 @chapter Performing Backups and Restoring Files
5194 @GNUTAR{} is distributed along with the scripts
5195 which the Free Software Foundation uses for performing backups. There
5196 is no corresponding scripts available yet for doing restoration of
5197 files. Even if there is a good chance those scripts may be satisfying
5198 to you, they are not the only scripts or methods available for doing
5199 backups and restore. You may well create your own, or use more
5200 sophisticated packages dedicated to that purpose.
5202 Some users are enthusiastic about @code{Amanda} (The Advanced Maryland
5203 Automatic Network Disk Archiver), a backup system developed by James
5204 da Silva @file{jds@@cs.umd.edu} and available on many Unix systems.
5205 This is free software, and it is available at these places:
5208 http://www.cs.umd.edu/projects/amanda/amanda.html
5209 ftp://ftp.cs.umd.edu/pub/amanda
5214 Here is a possible plan for a future documentation about the backuping
5215 scripts which are provided within the @GNUTAR{}
5221 @item what are dumps
5222 @item different levels of dumps
5224 @item full dump = dump everything
5225 @item level 1, level 2 dumps etc
5226 A level @var{n} dump dumps everything changed since the last level
5229 @item how to use scripts for dumps (ie, the concept)
5231 @item scripts to run after editing backup specs (details)
5233 @item Backup Specs, what is it.
5235 @item how to customize
5236 @item actual text of script [/sp/dump/backup-specs]
5240 @item rsh doesn't work
5241 @item rtape isn't installed
5244 @item the @option{--incremental} option of tar
5247 @item write protection
5248 @item types of media, different sizes and types, useful for different things
5249 @item files and tape marks
5250 one tape mark between files, two at end.
5251 @item positioning the tape
5252 MT writes two at end of write,
5253 backspaces over one when writing again.
5259 This chapter documents both the provided shell scripts and @command{tar}
5260 options which are more specific to usage as a backup tool.
5262 To @dfn{back up} a file system means to create archives that contain
5263 all the files in that file system. Those archives can then be used to
5264 restore any or all of those files (for instance if a disk crashes or a
5265 file is accidentally deleted). File system @dfn{backups} are also
5269 * Full Dumps:: Using @command{tar} to Perform Full Dumps
5270 * Incremental Dumps:: Using @command{tar} to Perform Incremental Dumps
5271 * Backup Levels:: Levels of Backups
5272 * Backup Parameters:: Setting Parameters for Backups and Restoration
5273 * Scripted Backups:: Using the Backup Scripts
5274 * Scripted Restoration:: Using the Restore Script
5278 @section Using @command{tar} to Perform Full Dumps
5284 @cindex corrupted archives
5285 Full dumps should only be made when no other people or programs
5286 are modifying files in the file system. If files are modified while
5287 @command{tar} is making the backup, they may not be stored properly in
5288 the archive, in which case you won't be able to restore them if you
5289 have to. (Files not being modified are written with no trouble, and do
5290 not corrupt the entire archive.)
5292 You will want to use the @option{--label=@var{archive-label}}
5293 (@option{-V @var{archive-label}}) option to give the archive a
5294 volume label, so you can tell what this archive is even if the label
5295 falls off the tape, or anything like that.
5297 Unless the file system you are dumping is guaranteed to fit on
5298 one volume, you will need to use the @option{--multi-volume} (@option{-M}) option.
5299 Make sure you have enough tapes on hand to complete the backup.
5301 If you want to dump each file system separately you will need to use
5302 the @option{--one-file-system} option to prevent
5303 @command{tar} from crossing file system boundaries when storing
5306 The @option{--incremental} (@option{-G}) (@pxref{Incremental Dumps})
5307 option is not needed, since this is a complete copy of everything in
5308 the file system, and a full restore from this backup would only be
5309 done onto a completely
5312 Unless you are in a hurry, and trust the @command{tar} program (and your
5313 tapes), it is a good idea to use the @option{--verify} (@option{-W})
5314 option, to make sure your files really made it onto the dump properly.
5315 This will also detect cases where the file was modified while (or just
5316 after) it was being archived. Not all media (notably cartridge tapes)
5317 are capable of being verified, unfortunately.
5319 @node Incremental Dumps
5320 @section Using @command{tar} to Perform Incremental Dumps
5322 @dfn{Incremental backup} is a special form of @GNUTAR{} archive that
5323 stores additional metadata so that exact state of the file system
5324 can be restored when extracting the archive.
5326 @GNUTAR{} currently offers two options for handling incremental
5327 backups: @option{--listed-incremental=@var{snapshot-file}} (@option{-g
5328 @var{snapshot-file}}) and @option{--incremental} (@option{-G}).
5330 @opindex listed-incremental
5331 The option @option{--listed-incremental} instructs tar to operate on
5332 an incremental archive with additional metadata stored in a standalone
5333 file, called a @dfn{snapshot file}. The purpose of this file is to help
5334 determine which files have been changed, added or deleted since the
5335 last backup, so that the next incremental backup will contain only
5336 modified files. The name of the snapshot file is given as an argument
5340 @item --listed-incremental=@var{file}
5341 @itemx -g @var{file}
5342 Handle incremental backups with snapshot data in @var{file}.
5345 To create an incremental backup, you would use
5346 @option{--listed-incremental} together with @option{--create}
5347 (@pxref{create}). For example:
5350 $ @kbd{tar --create \
5351 --file=archive.1.tar \
5352 --listed-incremental=/var/log/usr.snar \
5356 This will create in @file{archive.1.tar} an incremental backup of
5357 the @file{/usr} file system, storing additional metadata in the file
5358 @file{/var/log/usr.snar}. If this file does not exist, it will be
5359 created. The created archive will then be a @dfn{level 0 backup};
5360 please see the next section for more on backup levels.
5362 Otherwise, if the file @file{/var/log/usr.snar} exists, it
5363 determines which files are modified. In this case only these files will be
5364 stored in the archive. Suppose, for example, that after running the
5365 above command, you delete file @file{/usr/doc/old} and create
5366 directory @file{/usr/local/db} with the following contents:
5369 $ @kbd{ls /usr/local/db}
5374 Some time later you create another incremental backup. You will
5378 $ @kbd{tar --create \
5379 --file=archive.2.tar \
5380 --listed-incremental=/var/log/usr.snar \
5382 tar: usr/local/db: Directory is new
5389 The created archive @file{archive.2.tar} will contain only these
5390 three members. This archive is called a @dfn{level 1 backup}. Notice
5391 that @file{/var/log/usr.snar} will be updated with the new data, so if
5392 you plan to create more @samp{level 1} backups, it is necessary to
5393 create a working copy of the snapshot file before running
5394 @command{tar}. The above example will then be modified as follows:
5397 $ @kbd{cp /var/log/usr.snar /var/log/usr.snar-1}
5398 $ @kbd{tar --create \
5399 --file=archive.2.tar \
5400 --listed-incremental=/var/log/usr.snar-1 \
5404 Incremental dumps depend crucially on time stamps, so the results are
5405 unreliable if you modify a file's time stamps during dumping (e.g.,
5406 with the @option{--atime-preserve=replace} option), or if you set the clock
5409 Metadata stored in snapshot files include device numbers, which,
5410 obviously is supposed to be a non-volatile value. However, it turns
5411 out that NFS devices have undependable values when an automounter
5412 gets in the picture. This can lead to a great deal of spurious
5413 redumping in incremental dumps, so it is somewhat useless to compare
5414 two NFS devices numbers over time. The solution implemented currently
5415 is to considers all NFS devices as being equal when it comes to
5416 comparing directories; this is fairly gross, but there does not seem
5417 to be a better way to go.
5419 Note that incremental archives use @command{tar} extensions and may
5420 not be readable by non-@acronym{GNU} versions of the @command{tar} program.
5422 @xopindex{listed-incremental, using with @option{--extract}}
5423 @xopindex{extract, using with @option{--listed-incremental}}
5424 To extract from the incremental dumps, use
5425 @option{--listed-incremental} together with @option{--extract}
5426 option (@pxref{extracting files}). In this case, @command{tar} does
5427 not need to access snapshot file, since all the data necessary for
5428 extraction are stored in the archive itself. So, when extracting, you
5429 can give whatever argument to @option{--listed-incremental}, the usual
5430 practice is to use @option{--listed-incremental=/dev/null}.
5431 Alternatively, you can use @option{--incremental}, which needs no
5432 arguments. In general, @option{--incremental} (@option{-G}) can be
5433 used as a shortcut for @option{--listed-incremental} when listing or
5434 extracting incremental backups (for more information, regarding this
5435 option, @pxref{incremental-op}).
5437 When extracting from the incremental backup @GNUTAR{} attempts to
5438 restore the exact state the file system had when the archive was
5439 created. In particular, it will @emph{delete} those files in the file
5440 system that did not exist in their directories when the archive was
5441 created. If you have created several levels of incremental files,
5442 then in order to restore the exact contents the file system had when
5443 the last level was created, you will need to restore from all backups
5444 in turn. Continuing our example, to restore the state of @file{/usr}
5445 file system, one would do@footnote{Notice, that since both archives
5446 were created without @option{-P} option (@pxref{absolute}), these
5447 commands should be run from the root file system.}:
5450 $ @kbd{tar --extract \
5451 --listed-incremental=/dev/null \
5452 --file archive.1.tar}
5453 $ @kbd{tar --extract \
5454 --listed-incremental=/dev/null \
5455 --file archive.2.tar}
5458 To list the contents of an incremental archive, use @option{--list}
5459 (@pxref{list}), as usual. To obtain more information about the
5460 archive, use @option{--listed-incremental} or @option{--incremental}
5461 combined with two @option{--verbose} options@footnote{Two
5462 @option{--verbose} options were selected to avoid breaking usual
5463 verbose listing output (@option{--list --verbose}) when using in
5466 @xopindex{incremental, using with @option{--list}}
5467 @xopindex{listed-incremental, using with @option{--list}}
5468 @xopindex{list, using with @option{--incremental}}
5469 @xopindex{list, using with @option{--listed-incremental}}
5470 Versions of @GNUTAR{} up to 1.15.1 used to dump verbatim binary
5471 contents of the DUMPDIR header (with terminating nulls) when
5472 @option{--incremental} or @option{--listed-incremental} option was
5473 given, no matter what the verbosity level. This behavior, and,
5474 especially, the binary output it produced were considered inconvenient
5475 and were changed in version 1.16}:
5478 @kbd{tar --list --incremental --verbose --verbose archive.tar}
5481 This command will print, for each directory in the archive, the list
5482 of files in that directory at the time the archive was created. This
5483 information is put out in a format which is both human-readable and
5484 unambiguous for a program: each file name is printed as
5491 where @var{x} is a letter describing the status of the file: @samp{Y}
5492 if the file is present in the archive, @samp{N} if the file is not
5493 included in the archive, or a @samp{D} if the file is a directory (and
5494 is included in the archive). @xref{Dumpdir}, for the detailed
5495 description of dumpdirs and status codes. Each such
5496 line is terminated by a newline character. The last line is followed
5497 by an additional newline to indicate the end of the data.
5499 @anchor{incremental-op}The option @option{--incremental} (@option{-G})
5500 gives the same behavior as @option{--listed-incremental} when used
5501 with @option{--list} and @option{--extract} options. When used with
5502 @option{--create} option, it creates an incremental archive without
5503 creating snapshot file. Thus, it is impossible to create several
5504 levels of incremental backups with @option{--incremental} option.
5507 @section Levels of Backups
5509 An archive containing all the files in the file system is called a
5510 @dfn{full backup} or @dfn{full dump}. You could insure your data by
5511 creating a full dump every day. This strategy, however, would waste a
5512 substantial amount of archive media and user time, as unchanged files
5513 are daily re-archived.
5515 It is more efficient to do a full dump only occasionally. To back up
5516 files between full dumps, you can use @dfn{incremental dumps}. A @dfn{level
5517 one} dump archives all the files that have changed since the last full
5520 A typical dump strategy would be to perform a full dump once a week,
5521 and a level one dump once a day. This means some versions of files
5522 will in fact be archived more than once, but this dump strategy makes
5523 it possible to restore a file system to within one day of accuracy by
5524 only extracting two archives---the last weekly (full) dump and the
5525 last daily (level one) dump. The only information lost would be in
5526 files changed or created since the last daily backup. (Doing dumps
5527 more than once a day is usually not worth the trouble).
5529 @GNUTAR{} comes with scripts you can use to do full
5530 and level-one (actually, even level-two and so on) dumps. Using
5531 scripts (shell programs) to perform backups and restoration is a
5532 convenient and reliable alternative to typing out file name lists
5533 and @command{tar} commands by hand.
5535 Before you use these scripts, you need to edit the file
5536 @file{backup-specs}, which specifies parameters used by the backup
5537 scripts and by the restore script. This file is usually located
5538 in @file{/etc/backup} directory. @xref{Backup Parameters}, for its
5539 detailed description. Once the backup parameters are set, you can
5540 perform backups or restoration by running the appropriate script.
5542 The name of the backup script is @code{backup}. The name of the
5543 restore script is @code{restore}. The following sections describe
5544 their use in detail.
5546 @emph{Please Note:} The backup and restoration scripts are
5547 designed to be used together. While it is possible to restore files by
5548 hand from an archive which was created using a backup script, and to create
5549 an archive by hand which could then be extracted using the restore script,
5550 it is easier to use the scripts. @xref{Incremental Dumps}, before
5551 making such an attempt.
5553 @node Backup Parameters
5554 @section Setting Parameters for Backups and Restoration
5556 The file @file{backup-specs} specifies backup parameters for the
5557 backup and restoration scripts provided with @command{tar}. You must
5558 edit @file{backup-specs} to fit your system configuration and schedule
5559 before using these scripts.
5561 Syntactically, @file{backup-specs} is a shell script, containing
5562 mainly variable assignments. However, any valid shell construct
5563 is allowed in this file. Particularly, you may wish to define
5564 functions within that script (e.g., see @code{RESTORE_BEGIN} below).
5565 For more information about shell script syntax, please refer to
5566 @url{http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#ta
5567 g_02, the definition of the Shell Command Language}. See also
5568 @ref{Top,,Bash Features,bashref,Bash Reference Manual}.
5570 The shell variables controlling behavior of @code{backup} and
5571 @code{restore} are described in the following subsections.
5574 * General-Purpose Variables::
5575 * Magnetic Tape Control::
5577 * backup-specs example:: An Example Text of @file{Backup-specs}
5580 @node General-Purpose Variables
5581 @subsection General-Purpose Variables
5583 @defvr {Backup variable} ADMINISTRATOR
5584 The user name of the backup administrator. @code{Backup} scripts
5585 sends a backup report to this address.
5588 @defvr {Backup variable} BACKUP_HOUR
5589 The hour at which the backups are done. This can be a number from 0
5590 to 23, or the time specification in form @var{hours}:@var{minutes},
5591 or the string @samp{now}.
5593 This variable is used by @code{backup}. Its value may be overridden
5594 using @option{--time} option (@pxref{Scripted Backups}).
5597 @defvr {Backup variable} TAPE_FILE
5599 The device @command{tar} writes the archive to. If @var{TAPE_FILE}
5600 is a remote archive (@pxref{remote-dev}), backup script will suppose
5601 that your @command{mt} is able to access remote devices. If @var{RSH}
5602 (@pxref{RSH}) is set, @option{--rsh-command} option will be added to
5603 invocations of @command{mt}.
5606 @defvr {Backup variable} BLOCKING
5608 The blocking factor @command{tar} will use when writing the dump archive.
5609 @xref{Blocking Factor}.
5612 @defvr {Backup variable} BACKUP_DIRS
5614 A list of file systems to be dumped (for @code{backup}), or restored
5615 (for @code{restore}). You can include any directory
5616 name in the list --- subdirectories on that file system will be
5617 included, regardless of how they may look to other networked machines.
5618 Subdirectories on other file systems will be ignored.
5620 The host name specifies which host to run @command{tar} on, and should
5621 normally be the host that actually contains the file system. However,
5622 the host machine must have @GNUTAR{} installed, and
5623 must be able to access the directory containing the backup scripts and
5624 their support files using the same file name that is used on the
5625 machine where the scripts are run (i.e., what @command{pwd} will print
5626 when in that directory on that machine). If the host that contains
5627 the file system does not have this capability, you can specify another
5628 host as long as it can access the file system through NFS.
5630 If the list of file systems is very long you may wish to put it
5631 in a separate file. This file is usually named
5632 @file{/etc/backup/dirs}, but this name may be overridden in
5633 @file{backup-specs} using @code{DIRLIST} variable.
5636 @defvr {Backup variable} DIRLIST
5638 A path to the file containing the list of the file systems to backup
5639 or restore. By default it is @file{/etc/backup/dirs}.
5642 @defvr {Backup variable} BACKUP_FILES
5644 A list of individual files to be dumped (for @code{backup}), or restored
5645 (for @code{restore}). These should be accessible from the machine on
5646 which the backup script is run.
5648 If the list of file systems is very long you may wish to store it
5649 in a separate file. This file is usually named
5650 @file{/etc/backup/files}, but this name may be overridden in
5651 @file{backup-specs} using @code{FILELIST} variable.
5654 @defvr {Backup variable} FILELIST
5656 A path to the file containing the list of the individual files to backup
5657 or restore. By default it is @file{/etc/backup/files}.
5660 @defvr {Backup variable} MT
5662 Full file name of @command{mt} binary.
5665 @defvr {Backup variable} RSH
5667 Full file name of @command{rsh} binary or its equivalent. You may wish to
5668 set it to @code{ssh}, to improve security. In this case you will have
5669 to use public key authentication.
5672 @defvr {Backup variable} RSH_COMMAND
5674 Full file name of @command{rsh} binary on remote machines. This will
5675 be passed via @option{--rsh-command} option to the remote invocation
5679 @defvr {Backup variable} VOLNO_FILE
5681 Name of temporary file to hold volume numbers. This needs to be accessible
5682 by all the machines which have file systems to be dumped.
5685 @defvr {Backup variable} XLIST
5687 Name of @dfn{exclude file list}. An @dfn{exclude file list} is a file
5688 located on the remote machine and containing the list of files to
5689 be excluded from the backup. Exclude file lists are searched in
5690 /etc/tar-backup directory. A common use for exclude file lists
5691 is to exclude files containing security-sensitive information
5692 (e.g., @file{/etc/shadow} from backups).
5694 This variable affects only @code{backup}.
5697 @defvr {Backup variable} SLEEP_TIME
5699 Time to sleep between dumps of any two successive file systems
5701 This variable affects only @code{backup}.
5704 @defvr {Backup variable} DUMP_REMIND_SCRIPT
5706 Script to be run when it's time to insert a new tape in for the next
5707 volume. Administrators may want to tailor this script for their site.
5708 If this variable isn't set, @GNUTAR{} will display its built-in
5709 prompt, and will expect confirmation from the console. For the
5710 description of the default prompt, see @ref{change volume prompt}.
5714 @defvr {Backup variable} SLEEP_MESSAGE
5716 Message to display on the terminal while waiting for dump time. Usually
5717 this will just be some literal text.
5720 @defvr {Backup variable} TAR
5722 Full file name of the @GNUTAR{} executable. If this is not set, backup
5723 scripts will search @command{tar} in the current shell path.
5726 @node Magnetic Tape Control
5727 @subsection Magnetic Tape Control
5729 Backup scripts access tape device using special @dfn{hook functions}.
5730 These functions take a single argument -- the name of the tape
5731 device. Their names are kept in the following variables:
5733 @defvr {Backup variable} MT_BEGIN
5734 The name of @dfn{begin} function. This function is called before
5735 accessing the drive. By default it retensions the tape:
5741 mt -f "$1" retension
5746 @defvr {Backup variable} MT_REWIND
5747 The name of @dfn{rewind} function. The default definition is as
5760 @defvr {Backup variable} MT_OFFLINE
5761 The name of the function switching the tape off line. By default
5762 it is defined as follows:
5765 MT_OFFLINE=mt_offline
5773 @defvr {Backup variable} MT_STATUS
5774 The name of the function used to obtain the status of the archive device,
5775 including error count. Default definition:
5787 @subsection User Hooks
5789 @dfn{User hooks} are shell functions executed before and after
5790 each @command{tar} invocation. Thus, there are @dfn{backup
5791 hooks}, which are executed before and after dumping each file
5792 system, and @dfn{restore hooks}, executed before and
5793 after restoring a file system. Each user hook is a shell function
5794 taking four arguments:
5796 @deffn {User Hook Function} hook @var{level} @var{host} @var{fs} @var{fsname}
5801 Current backup or restore level.
5804 Name or IP address of the host machine being dumped or restored.
5807 Full path name to the file system being dumped or restored.
5810 File system name with directory separators replaced with colons. This
5811 is useful, e.g., for creating unique files.
5815 Following variables keep the names of user hook functions
5817 @defvr {Backup variable} DUMP_BEGIN
5818 Dump begin function. It is executed before dumping the file system.
5821 @defvr {Backup variable} DUMP_END
5822 Executed after dumping the file system.
5825 @defvr {Backup variable} RESTORE_BEGIN
5826 Executed before restoring the file system.
5829 @defvr {Backup variable} RESTORE_END
5830 Executed after restoring the file system.
5833 @node backup-specs example
5834 @subsection An Example Text of @file{Backup-specs}
5836 The following is an example of @file{backup-specs}:
5839 # site-specific parameters for file system backup.
5841 ADMINISTRATOR=friedman
5843 TAPE_FILE=/dev/nrsmt0
5845 # Use @code{ssh} instead of the less secure @code{rsh}
5847 RSH_COMMAND=/usr/bin/ssh
5849 # Override MT_STATUS function:
5855 # Disable MT_OFFLINE function
5872 apple-gunkies:/com/mailer/gnu
5873 apple-gunkies:/com/archive/gnu"
5875 BACKUP_FILES="/com/mailer/aliases /com/mailer/league*[a-z]"
5879 @node Scripted Backups
5880 @section Using the Backup Scripts
5882 The syntax for running a backup script is:
5885 backup --level=@var{level} --time=@var{time}
5888 The @option{level} option requests the dump level. Thus, to produce
5889 a full dump, specify @code{--level=0} (this is the default, so
5890 @option{--level} may be omitted if its value is @code{0}).
5891 @footnote{For backward compatibility, the @code{backup} will also
5892 try to deduce the requested dump level from the name of the
5893 script itself. If the name consists of a string @samp{level-}
5894 followed by a single decimal digit, that digit is taken as
5895 the dump level number. Thus, you may create a link from @code{backup}
5896 to @code{level-1} and then run @code{level-1} whenever you need to
5897 create a level one dump.}
5899 The @option{--time} option determines when should the backup be
5900 run. @var{Time} may take three forms:
5903 @item @var{hh}:@var{mm}
5905 The dump must be run at @var{hh} hours @var{mm} minutes.
5909 The dump must be run at @var{hh} hours
5913 The dump must be run immediately.
5916 You should start a script with a tape or disk mounted. Once you
5917 start a script, it prompts you for new tapes or disks as it
5918 needs them. Media volumes don't have to correspond to archive
5919 files --- a multi-volume archive can be started in the middle of a
5920 tape that already contains the end of another multi-volume archive.
5921 The @code{restore} script prompts for media by its archive volume,
5922 so to avoid an error message you should keep track of which tape
5923 (or disk) contains which volume of the archive (@pxref{Scripted
5926 The backup scripts write two files on the file system. The first is a
5927 record file in @file{/etc/tar-backup/}, which is used by the scripts
5928 to store and retrieve information about which files were dumped. This
5929 file is not meant to be read by humans, and should not be deleted by
5930 them. @xref{Snapshot Files}, for a more detailed explanation of this
5933 The second file is a log file containing the names of the file systems
5934 and files dumped, what time the backup was made, and any error
5935 messages that were generated, as well as how much space was left in
5936 the media volume after the last volume of the archive was written.
5937 You should check this log file after every backup. The file name is
5938 @file{log-@var{mm-dd-yyyy}-level-@var{n}}, where @var{mm-dd-yyyy}
5939 represents current date, and @var{n} represents current dump level number.
5941 The script also prints the name of each system being dumped to the
5944 Following is the full list of options accepted by @code{backup}
5948 @item -l @var{level}
5949 @itemx --level=@var{level}
5950 Do backup level @var{level} (default 0).
5954 Force backup even if today's log file already exists.
5956 @item -v[@var{level}]
5957 @itemx --verbose[=@var{level}]
5958 Set verbosity level. The higher the level is, the more debugging
5959 information will be output during execution. Default @var{level}
5960 is 100, which means the highest debugging level.
5962 @item -t @var{start-time}
5963 @itemx --time=@var{start-time}
5964 Wait till @var{time}, then do backup.
5968 Display short help message and exit.
5972 Display information about the program's name, version, origin and legal
5973 status, all on standard output, and then exit successfully.
5977 @node Scripted Restoration
5978 @section Using the Restore Script
5980 To restore files that were archived using a scripted backup, use the
5981 @code{restore} script. Its usage is quite straightforward. In the
5982 simplest form, invoke @code{restore --all}, it will
5983 then restore all the file systems and files specified in
5984 @file{backup-specs} (@pxref{General-Purpose Variables,BACKUP_DIRS}).
5986 You may select the file systems (and/or files) to restore by
5987 giving @code{restore} list of @dfn{patterns} in its command
5988 line. For example, running
5995 will restore all file systems on the machine @samp{albert}. A more
5996 complicated example:
5999 restore 'albert:*' '*:/var'
6003 This command will restore all file systems on the machine @samp{albert}
6004 as well as @file{/var} file system on all machines.
6006 By default @code{restore} will start restoring files from the lowest
6007 available dump level (usually zero) and will continue through
6008 all available dump levels. There may be situations where such a
6009 thorough restore is not necessary. For example, you may wish to
6010 restore only files from the recent level one backup. To do so,
6011 use @option{--level} option, as shown in the example below:
6017 The full list of options accepted by @code{restore} follows:
6022 Restore all file systems and files specified in @file{backup-specs}
6024 @item -l @var{level}
6025 @itemx --level=@var{level}
6026 Start restoring from the given backup level, instead of the default 0.
6028 @item -v[@var{level}]
6029 @itemx --verbose[=@var{level}]
6030 Set verbosity level. The higher the level is, the more debugging
6031 information will be output during execution. Default @var{level}
6032 is 100, which means the highest debugging level.
6036 Display short help message and exit.
6040 Display information about the program's name, version, origin and legal
6041 status, all on standard output, and then exit successfully.
6044 You should start the restore script with the media containing the
6045 first volume of the archive mounted. The script will prompt for other
6046 volumes as they are needed. If the archive is on tape, you don't need
6047 to rewind the tape to to its beginning---if the tape head is
6048 positioned past the beginning of the archive, the script will rewind
6049 the tape as needed. @xref{Tape Positioning}, for a discussion of tape
6053 @strong{Warning:} The script will delete files from the active file
6054 system if they were not in the file system when the archive was made.
6057 @xref{Incremental Dumps}, for an explanation of how the script makes
6061 @chapter Choosing Files and Names for @command{tar}
6064 Certain options to @command{tar} enable you to specify a name for your
6065 archive. Other options let you decide which files to include or exclude
6066 from the archive, based on when or whether files were modified, whether
6067 the file names do or don't match specified patterns, or whether files
6068 are in specified directories.
6070 This chapter discusses these options in detail.
6073 * file:: Choosing the Archive's Name
6074 * Selecting Archive Members::
6075 * files:: Reading Names from a File
6076 * exclude:: Excluding Some Files
6077 * wildcards:: Wildcards Patterns and Matching
6078 * quoting styles:: Ways of Quoting Special Characters in Names
6079 * transform:: Modifying File and Member Names
6080 * after:: Operating Only on New Files
6081 * recurse:: Descending into Directories
6082 * one:: Crossing File System Boundaries
6086 @section Choosing and Naming Archive Files
6089 @cindex Naming an archive
6090 @cindex Archive Name
6091 @cindex Choosing an archive file
6092 @cindex Where is the archive?
6093 By default, @command{tar} uses an archive file name that was compiled when
6094 it was built on the system; usually this name refers to some physical
6095 tape drive on the machine. However, the person who installed @command{tar}
6096 on the system may not have set the default to a meaningful value as far as
6097 most users are concerned. As a result, you will usually want to tell
6098 @command{tar} where to find (or create) the archive. The
6099 @option{--file=@var{archive-name}} (@option{-f @var{archive-name}})
6100 option allows you to either specify or name a file to use as the archive
6101 instead of the default archive file location.
6104 @xopindex{file, short description}
6105 @item --file=@var{archive-name}
6106 @itemx -f @var{archive-name}
6107 Name the archive to create or operate on. Use in conjunction with
6111 For example, in this @command{tar} command,
6114 $ @kbd{tar -cvf collection.tar blues folk jazz}
6118 @file{collection.tar} is the name of the archive. It must directly
6119 follow the @option{-f} option, since whatever directly follows @option{-f}
6120 @emph{will} end up naming the archive. If you neglect to specify an
6121 archive name, you may end up overwriting a file in the working directory
6122 with the archive you create since @command{tar} will use this file's name
6123 for the archive name.
6125 An archive can be saved as a file in the file system, sent through a
6126 pipe or over a network, or written to an I/O device such as a tape,
6127 floppy disk, or CD write drive.
6129 @cindex Writing new archives
6130 @cindex Archive creation
6131 If you do not name the archive, @command{tar} uses the value of the
6132 environment variable @env{TAPE} as the file name for the archive. If
6133 that is not available, @command{tar} uses a default, compiled-in archive
6134 name, usually that for tape unit zero (i.e., @file{/dev/tu00}).
6136 @cindex Standard input and output
6137 @cindex tar to standard input and output
6138 If you use @file{-} as an @var{archive-name}, @command{tar} reads the
6139 archive from standard input (when listing or extracting files), or
6140 writes it to standard output (when creating an archive). If you use
6141 @file{-} as an @var{archive-name} when modifying an archive,
6142 @command{tar} reads the original archive from its standard input and
6143 writes the entire new archive to its standard output.
6145 The following example is a convenient way of copying directory
6146 hierarchy from @file{sourcedir} to @file{targetdir}.
6149 $ @kbd{(cd sourcedir; tar -cf - .) | (cd targetdir; tar -xpf -)}
6152 The @option{-C} option allows to avoid using subshells:
6155 $ @kbd{tar -C sourcedir -cf - . | tar -C targetdir -xpf -}
6158 In both examples above, the leftmost @command{tar} invocation archives
6159 the contents of @file{sourcedir} to the standard output, while the
6160 rightmost one reads this archive from its standard input and
6161 extracts it. The @option{-p} option tells it to restore permissions
6162 of the extracted files.
6164 @cindex Remote devices
6165 @cindex tar to a remote device
6167 To specify an archive file on a device attached to a remote machine,
6171 @kbd{--file=@var{hostname}:/@var{dev}/@var{file-name}}
6175 @command{tar} will complete the remote connection, if possible, and
6176 prompt you for a username and password. If you use
6177 @option{--file=@@@var{hostname}:/@var{dev}/@var{file-name}}, @command{tar}
6178 will complete the remote connection, if possible, using your username
6179 as the username on the remote machine.
6181 @cindex Local and remote archives
6182 @anchor{local and remote archives}
6183 If the archive file name includes a colon (@samp{:}), then it is assumed
6184 to be a file on another machine. If the archive file is
6185 @samp{@var{user}@@@var{host}:@var{file}}, then @var{file} is used on the
6186 host @var{host}. The remote host is accessed using the @command{rsh}
6187 program, with a username of @var{user}. If the username is omitted
6188 (along with the @samp{@@} sign), then your user name will be used.
6189 (This is the normal @command{rsh} behavior.) It is necessary for the
6190 remote machine, in addition to permitting your @command{rsh} access, to
6191 have the @file{rmt} program installed (This command is included in
6192 the @GNUTAR{} distribution and by default is installed under
6193 @file{@var{prefix}/libexec/rmt}, were @var{prefix} means your
6194 installation prefix). If you need to use a file whose name includes a
6195 colon, then the remote tape drive behavior
6196 can be inhibited by using the @option{--force-local} option.
6198 When the archive is being created to @file{/dev/null}, @GNUTAR{}
6199 tries to minimize input and output operations. The Amanda backup
6200 system, when used with @GNUTAR{}, has an initial sizing pass which
6203 @node Selecting Archive Members
6204 @section Selecting Archive Members
6205 @cindex Specifying files to act on
6206 @cindex Specifying archive members
6208 @dfn{File Name arguments} specify which files in the file system
6209 @command{tar} operates on, when creating or adding to an archive, or which
6210 archive members @command{tar} operates on, when reading or deleting from
6211 an archive. @xref{Operations}.
6213 To specify file names, you can include them as the last arguments on
6214 the command line, as follows:
6216 @kbd{tar} @var{operation} [@var{option1} @var{option2} @dots{}] [@var{file name-1} @var{file name-2} @dots{}]
6219 If a file name begins with dash (@samp{-}), precede it with
6220 @option{--add-file} option to prevent it from being treated as an
6223 @anchor{input name quoting}
6224 By default @GNUTAR{} attempts to @dfn{unquote} each file or member
6225 name, replacing @dfn{escape sequences} according to the following
6228 @multitable @columnfractions 0.20 0.60
6229 @headitem Escape @tab Replaced with
6230 @item \a @tab Audible bell (ASCII 7)
6231 @item \b @tab Backspace (ASCII 8)
6232 @item \f @tab Form feed (ASCII 12)
6233 @item \n @tab New line (ASCII 10)
6234 @item \r @tab Carriage return (ASCII 13)
6235 @item \t @tab Horizontal tabulation (ASCII 9)
6236 @item \v @tab Vertical tabulation (ASCII 11)
6237 @item \? @tab ASCII 127
6238 @item \@var{n} @tab ASCII @var{n} (@var{n} should be an octal number
6242 A backslash followed by any other symbol is retained.
6244 This default behavior is controlled by the following command line
6250 Enable unquoting input file or member names (default).
6254 Disable unquoting input file or member names.
6257 If you specify a directory name as a file name argument, all the files
6258 in that directory are operated on by @command{tar}.
6260 If you do not specify files, @command{tar} behavior differs depending
6261 on the operation mode as described below:
6263 When @command{tar} is invoked with @option{--create} (@option{-c}),
6264 @command{tar} will stop immediately, reporting the following:
6268 $ @kbd{tar cf a.tar}
6269 tar: Cowardly refusing to create an empty archive
6270 Try `tar --help' or `tar --usage' for more information.
6274 If you specify either @option{--list} (@option{-t}) or
6275 @option{--extract} (@option{--get}, @option{-x}), @command{tar}
6276 operates on all the archive members in the archive.
6278 If run with @option{--diff} option, tar will compare the archive with
6279 the contents of the current working directory.
6281 If you specify any other operation, @command{tar} does nothing.
6283 By default, @command{tar} takes file names from the command line. However,
6284 there are other ways to specify file or member names, or to modify the
6285 manner in which @command{tar} selects the files or members upon which to
6286 operate. In general, these methods work both for specifying the names
6287 of files and archive members.
6290 @section Reading Names from a File
6292 @cindex Reading file names from a file
6293 @cindex Lists of file names
6294 @cindex File Name arguments, alternatives
6295 Instead of giving the names of files or archive members on the command
6296 line, you can put the names into a file, and then use the
6297 @option{--files-from=@var{file-of-names}} (@option{-T
6298 @var{file-of-names}}) option to @command{tar}. Give the name of the
6299 file which contains the list of files to include as the argument to
6300 @option{--files-from}. In the list, the file names should be separated by
6301 newlines. You will frequently use this option when you have generated
6302 the list of files to archive with the @command{find} utility.
6306 @item --files-from=@var{file-name}
6307 @itemx -T @var{file-name}
6308 Get names to extract or create from file @var{file-name}.
6311 If you give a single dash as a file name for @option{--files-from}, (i.e.,
6312 you specify either @code{--files-from=-} or @code{-T -}), then the file
6313 names are read from standard input.
6315 Unless you are running @command{tar} with @option{--create}, you can not use
6316 both @code{--files-from=-} and @code{--file=-} (@code{-f -}) in the same
6319 Any number of @option{-T} options can be given in the command line.
6321 The following example shows how to use @command{find} to generate a list of
6322 files smaller than 400K in length and put that list into a file
6323 called @file{small-files}. You can then use the @option{-T} option to
6324 @command{tar} to specify the files from that file, @file{small-files}, to
6325 create the archive @file{little.tgz}. (The @option{-z} option to
6326 @command{tar} compresses the archive with @command{gzip}; @pxref{gzip} for
6330 $ @kbd{find . -size -400 -print > small-files}
6331 $ @kbd{tar -c -v -z -T small-files -f little.tgz}
6335 In the file list given by @option{-T} option, any file name beginning
6336 with @samp{-} character is considered a @command{tar} option and is
6337 processed accordingly.@footnote{Versions of @GNUTAR{} up to 1.15.1
6338 recognized only @option{-C} option in file lists, and only if the
6339 option and its argument occupied two consecutive lines.} For example,
6340 the common use of this feature is to change to another directory by
6341 specifying @option{-C} option:
6351 $ @kbd{tar -c -f foo.tar --files-from list}
6356 In this example, @command{tar} will first switch to @file{/etc}
6357 directory and add files @file{passwd} and @file{hosts} to the
6358 archive. Then it will change to @file{/lib} directory and will archive
6359 the file @file{libc.a}. Thus, the resulting archive @file{foo.tar} will
6364 $ @kbd{tar tf foo.tar}
6372 @xopindex{directory, using in @option{--files-from} argument}
6373 Notice that the option parsing algorithm used with @option{-T} is
6374 stricter than the one used by shell. Namely, when specifying option
6375 arguments, you should observe the following rules:
6379 When using short (single-letter) option form, its argument must
6380 immediately follow the option letter, without any intervening
6381 whitespace. For example: @code{-Cdir}.
6384 When using long option form, the option argument must be separated
6385 from the option by a single equal sign. No whitespace is allowed on
6386 any side of the equal sign. For example: @code{--directory=dir}.
6389 For both short and long option forms, the option argument can be given
6390 on the next line after the option name, e.g.:
6411 If you happen to have a file whose name starts with @samp{-},
6412 precede it with @option{--add-file} option to prevent it from
6413 being recognized as an option. For example: @code{--add-file=--my-file}.
6420 @subsection @code{NUL} Terminated File Names
6422 @cindex File names, terminated by @code{NUL}
6423 @cindex @code{NUL} terminated file names
6424 The @option{--null} option causes
6425 @option{--files-from=@var{file-of-names}} (@option{-T @var{file-of-names}})
6426 to read file names terminated by a @code{NUL} instead of a newline, so
6427 files whose names contain newlines can be archived using
6428 @option{--files-from}.
6433 Only consider @code{NUL} terminated file names, instead of files that
6434 terminate in a newline.
6437 The @option{--null} option is just like the one in @acronym{GNU}
6438 @command{xargs} and @command{cpio}, and is useful with the
6439 @option{-print0} predicate of @acronym{GNU} @command{find}. In
6440 @command{tar}, @option{--null} also disables special handling for
6441 file names that begin with dash.
6443 This example shows how to use @command{find} to generate a list of files
6444 larger than 800K in length and put that list into a file called
6445 @file{long-files}. The @option{-print0} option to @command{find} is just
6446 like @option{-print}, except that it separates files with a @code{NUL}
6447 rather than with a newline. You can then run @command{tar} with both the
6448 @option{--null} and @option{-T} options to specify that @command{tar} get the
6449 files from that file, @file{long-files}, to create the archive
6450 @file{big.tgz}. The @option{--null} option to @command{tar} will cause
6451 @command{tar} to recognize the @code{NUL} separator between files.
6454 $ @kbd{find . -size +800 -print0 > long-files}
6455 $ @kbd{tar -c -v --null --files-from=long-files --file=big.tar}
6458 @FIXME{say anything else here to conclude the section?}
6461 @section Excluding Some Files
6464 @cindex File names, excluding files by
6465 @cindex Excluding files by name and pattern
6466 @cindex Excluding files by file system
6467 To avoid operating on files whose names match a particular pattern,
6468 use the @option{--exclude} or @option{--exclude-from} options.
6472 @item --exclude=@var{pattern}
6473 Causes @command{tar} to ignore files that match the @var{pattern}.
6477 The @option{--exclude=@var{pattern}} option prevents any file or
6478 member whose name matches the shell wildcard (@var{pattern}) from
6480 For example, to create an archive with all the contents of the directory
6481 @file{src} except for files whose names end in @file{.o}, use the
6482 command @samp{tar -cf src.tar --exclude='*.o' src}.
6484 You may give multiple @option{--exclude} options.
6487 @opindex exclude-from
6488 @item --exclude-from=@var{file}
6489 @itemx -X @var{file}
6490 Causes @command{tar} to ignore files that match the patterns listed in
6494 @findex exclude-from
6495 Use the @option{--exclude-from} option to read a
6496 list of patterns, one per line, from @var{file}; @command{tar} will
6497 ignore files matching those patterns. Thus if @command{tar} is
6498 called as @w{@samp{tar -c -X foo .}} and the file @file{foo} contains a
6499 single line @file{*.o}, no files whose names end in @file{.o} will be
6500 added to the archive.
6502 @findex exclude-caches
6503 When creating an archive, the @option{--exclude-caches} option family
6504 causes @command{tar} to exclude all directories that contain a @dfn{cache
6505 directory tag}. A cache directory tag is a short file with the
6506 well-known name @file{CACHEDIR.TAG} and having a standard header
6507 specified in @url{http://www.brynosaurus.com/cachedir/spec.html}.
6508 Various applications write cache directory tags into directories they
6509 use to hold regenerable, non-precious data, so that such data can be
6510 more easily excluded from backups.
6512 There are three @samp{exclude-caches} option, providing a different
6513 exclusion semantics:
6516 @opindex exclude-caches
6517 @item --exclude-caches
6518 Do not archive the contents of the directory, but archive the
6519 directory itself and the @file{CACHEDIR.TAG} file.
6521 @opindex exclude-caches-under
6522 @item --exclude-caches-under
6523 Do not archive the contents of the directory, nor the
6524 @file{CACHEDIR.TAG} file, archive only the directory itself.
6526 @opindex exclude-caches-all
6527 @item --exclude-caches-all
6528 Omit directories containing @file{CACHEDIR.TAG} file entirely.
6532 Another option family, @option{--exclude-tag}, provides a generalization of
6533 this concept. It takes a single argument, a file name to look for.
6534 Any directory that contains this file will be excluded from the dump.
6535 Similarly to @samp{exclude-caches}, there are three options in this
6539 @opindex exclude-tag
6540 @item --exclude-tag=@var{file}
6541 Do not dump the contents of the directory, but dump the
6542 directory itself and the @var{file}.
6544 @opindex exclude-tag-under
6545 @item --exclude-tag-under=@var{file}
6546 Do not dump the contents of the directory, nor the
6547 @var{file}, archive only the directory itself.
6549 @opindex exclude-tag-all
6550 @item --exclude-tag-all=@var{file}
6551 Omit directories containing @var{file} file entirely.
6554 Multiple @option{--exclude-tag*} options can be given.
6556 For example, given this directory:
6571 The @option{--exclude-tag} will produce the following:
6574 $ @kbd{tar -cf archive.tar --exclude-tag=tagfile -v dir}
6579 tar: dir/folk/: contains a cache directory tag tagfile;
6584 Both the @file{dir/folk} directory and its tagfile are preserved in
6585 the archive, however the rest of files in this directory are not.
6587 Now, using the @option{--exclude-tag-under} option will exclude
6588 @file{tagfile} from the dump, while still preserving the directory
6589 itself, as shown in this example:
6592 $ @kbd{tar -cf archive.tar --exclude-tag-under=tagfile -v dir}
6597 ./tar: dir/folk/: contains a cache directory tag tagfile;
6601 Finally, using @option{--exclude-tag-all} omits the @file{dir/folk}
6605 $ @kbd{tar -cf archive.tar --exclude-tag-all=tagfile -v dir}
6609 ./tar: dir/folk/: contains a cache directory tag tagfile;
6610 directory not dumped
6614 * problems with exclude::
6617 @node problems with exclude
6618 @unnumberedsubsec Problems with Using the @code{exclude} Options
6620 @xopindex{exclude, potential problems with}
6621 Some users find @samp{exclude} options confusing. Here are some common
6626 The main operating mode of @command{tar} does not act on a path name
6627 explicitly listed on the command line if one of its file name
6628 components is excluded. In the example above, if
6629 you create an archive and exclude files that end with @samp{*.o}, but
6630 explicitly name the file @samp{dir.o/foo} after all the options have been
6631 listed, @samp{dir.o/foo} will be excluded from the archive.
6634 You can sometimes confuse the meanings of @option{--exclude} and
6635 @option{--exclude-from}. Be careful: use @option{--exclude} when files
6636 to be excluded are given as a pattern on the command line. Use
6637 @option{--exclude-from} to introduce the name of a file which contains
6638 a list of patterns, one per line; each of these patterns can exclude
6639 zero, one, or many files.
6642 When you use @option{--exclude=@var{pattern}}, be sure to quote the
6643 @var{pattern} parameter, so @GNUTAR{} sees wildcard characters
6644 like @samp{*}. If you do not do this, the shell might expand the
6645 @samp{*} itself using files at hand, so @command{tar} might receive a
6646 list of files instead of one pattern, or none at all, making the
6647 command somewhat illegal. This might not correspond to what you want.
6652 $ @kbd{tar -c -f @var{archive.tar} --exclude '*.o' @var{directory}}
6660 $ @kbd{tar -c -f @var{archive.tar} --exclude *.o @var{directory}}
6664 You must use use shell syntax, or globbing, rather than @code{regexp}
6665 syntax, when using exclude options in @command{tar}. If you try to use
6666 @code{regexp} syntax to describe files to be excluded, your command
6670 @FIXME{The change in semantics must have occurred before 1.11,
6671 so I doubt if it is worth mentioning at all. Anyway, should at
6672 least specify in which version the semantics changed.}
6673 In earlier versions of @command{tar}, what is now the
6674 @option{--exclude-from} option was called @option{--exclude} instead.
6675 Now, @option{--exclude} applies to patterns listed on the command
6676 line and @option{--exclude-from} applies to patterns listed in a
6682 @section Wildcards Patterns and Matching
6684 @dfn{Globbing} is the operation by which @dfn{wildcard} characters,
6685 @samp{*} or @samp{?} for example, are replaced and expanded into all
6686 existing files matching the given pattern. @GNUTAR{} can use wildcard
6687 patterns for matching (or globbing) archive members when extracting
6688 from or listing an archive. Wildcard patterns are also used for
6689 verifying volume labels of @command{tar} archives. This section has the
6690 purpose of explaining wildcard syntax for @command{tar}.
6692 @FIXME{the next few paragraphs need work.}
6694 A @var{pattern} should be written according to shell syntax, using wildcard
6695 characters to effect globbing. Most characters in the pattern stand
6696 for themselves in the matched string, and case is significant: @samp{a}
6697 will match only @samp{a}, and not @samp{A}. The character @samp{?} in the
6698 pattern matches any single character in the matched string. The character
6699 @samp{*} in the pattern matches zero, one, or more single characters in
6700 the matched string. The character @samp{\} says to take the following
6701 character of the pattern @emph{literally}; it is useful when one needs to
6702 match the @samp{?}, @samp{*}, @samp{[} or @samp{\} characters, themselves.
6704 The character @samp{[}, up to the matching @samp{]}, introduces a character
6705 class. A @dfn{character class} is a list of acceptable characters
6706 for the next single character of the matched string. For example,
6707 @samp{[abcde]} would match any of the first five letters of the alphabet.
6708 Note that within a character class, all of the ``special characters''
6709 listed above other than @samp{\} lose their special meaning; for example,
6710 @samp{[-\\[*?]]} would match any of the characters, @samp{-}, @samp{\},
6711 @samp{[}, @samp{*}, @samp{?}, or @samp{]}. (Due to parsing constraints,
6712 the characters @samp{-} and @samp{]} must either come @emph{first} or
6713 @emph{last} in a character class.)
6715 @cindex Excluding characters from a character class
6716 @cindex Character class, excluding characters from
6717 If the first character of the class after the opening @samp{[}
6718 is @samp{!} or @samp{^}, then the meaning of the class is reversed.
6719 Rather than listing character to match, it lists those characters which
6720 are @emph{forbidden} as the next single character of the matched string.
6722 Other characters of the class stand for themselves. The special
6723 construction @samp{[@var{a}-@var{e}]}, using an hyphen between two
6724 letters, is meant to represent all characters between @var{a} and
6727 @FIXME{need to add a sentence or so here to make this clear for those
6728 who don't have dan around.}
6730 Periods (@samp{.}) or forward slashes (@samp{/}) are not considered
6731 special for wildcard matches. However, if a pattern completely matches
6732 a directory prefix of a matched string, then it matches the full matched
6733 string: thus, excluding a directory also excludes all the files beneath it.
6736 * controlling pattern-matching::
6739 @node controlling pattern-matching
6740 @unnumberedsubsec Controlling Pattern-Matching
6742 For the purposes of this section, we call @dfn{exclusion members} all
6743 member names obtained while processing @option{--exclude} and
6744 @option{--exclude-from} options, and @dfn{inclusion members} those
6745 member names that were given in the command line or read from the file
6746 specified with @option{--files-from} option.
6748 These two pairs of member lists are used in the following operations:
6749 @option{--diff}, @option{--extract}, @option{--list},
6752 There are no inclusion members in create mode (@option{--create} and
6753 @option{--append}), since in this mode the names obtained from the
6754 command line refer to @emph{files}, not archive members.
6756 By default, inclusion members are compared with archive members
6757 literally @footnote{Notice that earlier @GNUTAR{} versions used
6758 globbing for inclusion members, which contradicted to UNIX98
6759 specification and was not documented. @xref{Changes}, for more
6760 information on this and other changes.} and exclusion members are
6761 treated as globbing patterns. For example:
6765 $ @kbd{tar tf foo.tar}
6770 # @i{Member names are used verbatim:}
6771 $ @kbd{tar -xf foo.tar -v '[remarks]'}
6773 # @i{Exclude member names are globbed:}
6774 $ @kbd{tar -xf foo.tar -v --exclude '*.c'}
6780 This behavior can be altered by using the following options:
6785 Treat all member names as wildcards.
6787 @opindex no-wildcards
6788 @item --no-wildcards
6789 Treat all member names as literal strings.
6792 Thus, to extract files whose names end in @samp{.c}, you can use:
6795 $ @kbd{tar -xf foo.tar -v --wildcards '*.c'}
6801 Notice quoting of the pattern to prevent the shell from interpreting
6804 The effect of @option{--wildcards} option is canceled by
6805 @option{--no-wildcards}. This can be used to pass part of
6806 the command line arguments verbatim and other part as globbing
6807 patterns. For example, the following invocation:
6810 $ @kbd{tar -xf foo.tar --wildcards '*.txt' --no-wildcards '[remarks]'}
6814 instructs @command{tar} to extract from @file{foo.tar} all files whose
6815 names end in @samp{.txt} and the file named @file{[remarks]}.
6817 Normally, a pattern matches a name if an initial subsequence of the
6818 name's components matches the pattern, where @samp{*}, @samp{?}, and
6819 @samp{[...]} are the usual shell wildcards, @samp{\} escapes wildcards,
6820 and wildcards can match @samp{/}.
6822 Other than optionally stripping leading @samp{/} from names
6823 (@pxref{absolute}), patterns and names are used as-is. For
6824 example, trailing @samp{/} is not trimmed from a user-specified name
6825 before deciding whether to exclude it.
6827 However, this matching procedure can be altered by the options listed
6828 below. These options accumulate. For example:
6831 --ignore-case --exclude='makefile' --no-ignore-case ---exclude='readme'
6835 ignores case when excluding @samp{makefile}, but not when excluding
6840 @opindex no-anchored
6842 @itemx --no-anchored
6843 If anchored, a pattern must match an initial subsequence
6844 of the name's components. Otherwise, the pattern can match any
6845 subsequence. Default is @option{--no-anchored} for exclusion members
6846 and @option{--anchored} inclusion members.
6848 @opindex ignore-case
6849 @opindex no-ignore-case
6851 @itemx --no-ignore-case
6852 When ignoring case, upper-case patterns match lower-case names and vice versa.
6853 When not ignoring case (the default), matching is case-sensitive.
6855 @opindex wildcards-match-slash
6856 @opindex no-wildcards-match-slash
6857 @item --wildcards-match-slash
6858 @itemx --no-wildcards-match-slash
6859 When wildcards match slash (the default for exclusion members), a
6860 wildcard like @samp{*} in the pattern can match a @samp{/} in the
6861 name. Otherwise, @samp{/} is matched only by @samp{/}.
6865 The @option{--recursion} and @option{--no-recursion} options
6866 (@pxref{recurse}) also affect how member patterns are interpreted. If
6867 recursion is in effect, a pattern matches a name if it matches any of
6868 the name's parent directories.
6870 The following table summarizes pattern-matching default values:
6872 @multitable @columnfractions .3 .7
6873 @headitem Members @tab Default settings
6874 @item Inclusion @tab @option{--no-wildcards --anchored --no-wildcards-match-slash}
6875 @item Exclusion @tab @option{--wildcards --no-anchored --wildcards-match-slash}
6878 @node quoting styles
6879 @section Quoting Member Names
6881 When displaying member names, @command{tar} takes care to avoid
6882 ambiguities caused by certain characters. This is called @dfn{name
6883 quoting}. The characters in question are:
6886 @item Non-printable control characters:
6888 @multitable @columnfractions 0.20 0.10 0.60
6889 @headitem Character @tab ASCII @tab Character name
6890 @item \a @tab 7 @tab Audible bell
6891 @item \b @tab 8 @tab Backspace
6892 @item \f @tab 12 @tab Form feed
6893 @item \n @tab 10 @tab New line
6894 @item \r @tab 13 @tab Carriage return
6895 @item \t @tab 9 @tab Horizontal tabulation
6896 @item \v @tab 11 @tab Vertical tabulation
6899 @item Space (ASCII 32)
6901 @item Single and double quotes (@samp{'} and @samp{"})
6903 @item Backslash (@samp{\})
6906 The exact way @command{tar} uses to quote these characters depends on
6907 the @dfn{quoting style}. The default quoting style, called
6908 @dfn{escape} (see below), uses backslash notation to represent control
6909 characters, space and backslash. Using this quoting style, control
6910 characters are represented as listed in column @samp{Character} in the
6911 above table, a space is printed as @samp{\ } and a backslash as @samp{\\}.
6913 @GNUTAR{} offers seven distinct quoting styles, which can be selected
6914 using @option{--quoting-style} option:
6917 @item --quoting-style=@var{style}
6918 @opindex quoting-style
6920 Sets quoting style. Valid values for @var{style} argument are:
6921 literal, shell, shell-always, c, escape, locale, clocale.
6924 These styles are described in detail below. To illustrate their
6925 effect, we will use an imaginary tar archive @file{arch.tar}
6926 containing the following members:
6930 # 1. Contains horizontal tabulation character.
6932 # 2. Contains newline character
6935 # 3. Contains a space
6937 # 4. Contains double quotes
6939 # 5. Contains single quotes
6941 # 6. Contains a backslash character:
6946 Here is how usual @command{ls} command would have listed them, if they
6947 had existed in the current working directory:
6965 No quoting, display each character as is:
6969 $ @kbd{tar tf arch.tar --quoting-style=literal}
6982 Display characters the same way Bourne shell does:
6983 control characters, except @samp{\t} and @samp{\n}, are printed using
6984 backslash escapes, @samp{\t} and @samp{\n} are printed as is, and a
6985 single quote is printed as @samp{\'}. If a name contains any quoted
6986 characters, it is enclosed in single quotes. In particular, if a name
6987 contains single quotes, it is printed as several single-quoted strings:
6991 $ @kbd{tar tf arch.tar --quoting-style=shell}
6994 './a'\''single'\''quote'
7004 Same as @samp{shell}, but the names are always enclosed in single
7009 $ @kbd{tar tf arch.tar --quoting-style=shell-always}
7012 './a'\''single'\''quote'
7022 Use the notation of the C programming language. All names are
7023 enclosed in double quotes. Control characters are quoted using
7024 backslash notations, double quotes are represented as @samp{\"},
7025 backslash characters are represented as @samp{\\}. Single quotes and
7026 spaces are not quoted:
7030 $ @kbd{tar tf arch.tar --quoting-style=c}
7034 "./a\"double\"quote"
7042 Control characters are printed using backslash notation, a space is
7043 printed as @samp{\ } and a backslash as @samp{\\}. This is the
7044 default quoting style, unless it was changed when configured the
7049 $ @kbd{tar tf arch.tar --quoting-style=escape}
7061 Control characters, single quote and backslash are printed using
7062 backslash notation. All names are quoted using left and right
7063 quotation marks, appropriate to the current locale. If it does not
7064 define quotation marks, use @samp{`} as left and @samp{'} as right
7065 quotation marks. Any occurrences of the right quotation mark in a
7066 name are escaped with @samp{\}, for example:
7072 $ @kbd{tar tf arch.tar --quoting-style=locale}
7075 `./a\'single\'quote'
7084 Same as @samp{locale}, but @samp{"} is used for both left and right
7085 quotation marks, if not provided by the currently selected locale:
7089 $ @kbd{tar tf arch.tar --quoting-style=clocale}
7093 "./a\"double\"quote"
7101 You can specify which characters should be quoted in addition to those
7102 implied by the current quoting style:
7105 @item --quote-chars=@var{string}
7106 Always quote characters from @var{string}, even if the selected
7107 quoting style would not quote them.
7110 For example, using @samp{escape} quoting (compare with the usual
7111 escape listing above):
7115 $ @kbd{tar tf arch.tar --quoting-style=escape --quote-chars=' "'}
7126 To disable quoting of such additional characters, use the following
7130 @item --no-quote-chars=@var{string}
7131 Remove characters listed in @var{string} from the list of quoted
7132 characters set by the previous @option{--quote-chars} option.
7135 This option is particularly useful if you have added
7136 @option{--quote-chars} to your @env{TAR_OPTIONS} (@pxref{TAR_OPTIONS})
7137 and wish to disable it for the current invocation.
7139 Note, that @option{--no-quote-chars} does @emph{not} disable those
7140 characters that are quoted by default in the selected quoting style.
7143 @section Modifying File and Member Names
7145 @command{Tar} archives contain detailed information about files stored
7146 in them and full file names are part of that information. When
7147 storing file to an archive, its file name is recorded in the archive
7148 along with the actual file contents. When restoring from an archive,
7149 a file is created on disk with exactly the same name as that stored
7150 in the archive. In the majority of cases this is the desired behavior
7151 of a file archiver. However, there are some cases when it is not.
7153 First of all, it is often unsafe to extract archive members with
7154 absolute file names or those that begin with a @file{../}. @GNUTAR{}
7155 takes special precautions when extracting such names and provides a
7156 special option for handling them, which is described in
7159 Secondly, you may wish to extract file names without some leading
7160 directory components, or with otherwise modified names. In other
7161 cases it is desirable to store files under differing names in the
7164 @GNUTAR{} provides two options for these needs.
7167 @opindex strip-components
7168 @item --strip-components=@var{number}
7169 Strip given @var{number} of leading components from file names before
7173 For example, suppose you have archived whole @file{/usr} hierarchy to
7174 a tar archive named @file{usr.tar}. Among other files, this archive
7175 contains @file{usr/include/stdlib.h}, which you wish to extract to
7176 the current working directory. To do so, you type:
7179 $ @kbd{tar -xf usr.tar --strip=2 usr/include/stdlib.h}
7182 The option @option{--strip=2} instructs @command{tar} to strip the
7183 two leading components (@file{usr/} and @file{include/}) off the file
7186 If you add to the above invocation @option{--verbose} (@option{-v})
7187 option, you will note that the verbose listing still contains the
7188 full file name, with the two removed components still in place. This
7189 can be inconvenient, so @command{tar} provides a special option for
7190 altering this behavior:
7192 @anchor{show-transformed-names}
7194 @opindex show-transformed-names
7195 @item --show-transformed-names
7196 Display file or member names with all requested transformations
7205 $ @kbd{tar -xf usr.tar -v --strip=2 usr/include/stdlib.h}
7206 usr/include/stdlib.h
7207 $ @kbd{tar -xf usr.tar -v --strip=2 --show-transformed usr/include/stdlib.h}
7212 Notice that in both cases the file is @file{stdlib.h} extracted to the
7213 current working directory, @option{--show-transformed-names} affects
7214 only the way its name is displayed.
7216 This option is especially useful for verifying whether the invocation
7217 will have the desired effect. Thus, before running
7220 $ @kbd{tar -x --strip=@var{n}}
7224 it is often advisable to run
7227 $ @kbd{tar -t -v --show-transformed --strip=@var{n}}
7231 to make sure the command will produce the intended results.
7233 In case you need to apply more complex modifications to the file name,
7234 @GNUTAR{} provides a general-purpose transformation option:
7238 @item --transform=@var{expression}
7239 Modify file names using supplied @var{expression}.
7243 The @var{expression} is a @command{sed}-like replace expression of the
7247 s/@var{regexp}/@var{replace}/[@var{flags}]
7251 where @var{regexp} is a @dfn{regular expression}, @var{replace} is a
7252 replacement for each file name part that matches @var{regexp}. Both
7253 @var{regexp} and @var{replace} are described in detail in
7254 @ref{The "s" Command, The "s" Command, The `s' Command, sed, GNU sed}.
7256 Supported @var{flags} are:
7260 Apply the replacement to @emph{all} matches to the @var{regexp}, not
7264 Use case-insensitive matching
7267 @var{regexp} is an @dfn{extended regular expression} (@pxref{Extended
7268 regexps, Extended regular expressions, Extended regular expressions,
7272 Only replace the @var{number}th match of the @var{regexp}.
7274 Note: the @var{posix} standard does not specify what should happen
7275 when you mix the @samp{g} and @var{number} modifiers. @GNUTAR{}
7276 follows the GNU @command{sed} implementation in this regard, so
7277 the interaction is defined to be: ignore matches before the
7278 @var{number}th, and then match and replace all matches from the
7283 Any delimiter can be used in lieue of @samp{/}, the only requirement being
7284 that it be used consistently throughout the expression. For example,
7285 the following two expressions are equivalent:
7294 Changing delimiters is often useful when the @var{regex} contains
7295 slashes. For example, it is more convenient to write @code{s,/,-,} than
7298 Here are several examples of @option{--transform} usage:
7301 @item Extract @file{usr/} hierarchy into @file{usr/local/}:
7304 $ @kbd{tar --transform='s,usr/,usr/local/,' -x -f arch.tar}
7307 @item Strip two leading directory components (equivalent to
7308 @option{--strip-components=2}):
7311 $ @kbd{tar --transform='s,/*[^/]*/[^/]*/,,' -x -f arch.tar}
7314 @item Prepend @file{/prefix/} to each file name:
7317 $ @kbd{tar --transform 's,^,/prefix/,' -x -f arch.tar}
7320 @item Convert each file name to lower case:
7323 $ @kbd{tar --transform 's/.*/\L&/' -x -f arch.tar}
7328 Unlike @option{--strip-components}, @option{--transform} can be used
7329 in any @GNUTAR{} operation mode. For example, the following command
7330 adds files to the archive while replacing the leading @file{usr/}
7331 component with @file{var/}:
7334 $ @kbd{tar -cf arch.tar --transform='s,^usr/,var/,' /}
7337 To test @option{--transform} effect we suggest using
7338 @option{--show-transformed-names} option:
7341 $ @kbd{tar -cf arch.tar --transform='s,^usr/,var/,' \
7342 --verbose --show-transformed-names /}
7345 If both @option{--strip-components} and @option{--transform} are used
7346 together, then @option{--transform} is applied first, and the required
7347 number of components is then stripped from its result.
7350 @section Operating Only on New Files
7353 @cindex Excluding file by age
7354 @cindex Data Modification time, excluding files by
7355 @cindex Modification time, excluding files by
7356 @cindex Age, excluding files by
7357 The @option{--after-date=@var{date}} (@option{--newer=@var{date}},
7358 @option{-N @var{date}}) option causes @command{tar} to only work on
7359 files whose data modification or status change times are newer than
7360 the @var{date} given. If @var{date} starts with @samp{/} or @samp{.},
7361 it is taken to be a file name; the data modification time of that file
7362 is used as the date. If you use this option when creating or appending
7363 to an archive, the archive will only include new files. If you use
7364 @option{--after-date} when extracting an archive, @command{tar} will
7365 only extract files newer than the @var{date} you specify.
7367 If you only want @command{tar} to make the date comparison based on
7368 modification of the file's data (rather than status
7369 changes), then use the @option{--newer-mtime=@var{date}} option.
7371 You may use these options with any operation. Note that these options
7372 differ from the @option{--update} (@option{-u}) operation in that they
7373 allow you to specify a particular date against which @command{tar} can
7374 compare when deciding whether or not to archive the files.
7379 @item --after-date=@var{date}
7380 @itemx --newer=@var{date}
7381 @itemx -N @var{date}
7382 Only store files newer than @var{date}.
7384 Acts on files only if their data modification or status change times are
7385 later than @var{date}. Use in conjunction with any operation.
7387 If @var{date} starts with @samp{/} or @samp{.}, it is taken to be a file
7388 name; the data modification time of that file is used as the date.
7390 @opindex newer-mtime
7391 @item --newer-mtime=@var{date}
7392 Acts like @option{--after-date}, but only looks at data modification times.
7395 These options limit @command{tar} to operate only on files which have
7396 been modified after the date specified. A file's status is considered to have
7397 changed if its contents have been modified, or if its owner,
7398 permissions, and so forth, have been changed. (For more information on
7399 how to specify a date, see @ref{Date input formats}; remember that the
7400 entire date argument must be quoted if it contains any spaces.)
7402 Gurus would say that @option{--after-date} tests both the data
7403 modification time (@code{mtime}, the time the contents of the file
7404 were last modified) and the status change time (@code{ctime}, the time
7405 the file's status was last changed: owner, permissions, etc.@:)
7406 fields, while @option{--newer-mtime} tests only the @code{mtime}
7409 To be precise, @option{--after-date} checks @emph{both} @code{mtime} and
7410 @code{ctime} and processes the file if either one is more recent than
7411 @var{date}, while @option{--newer-mtime} only checks @code{mtime} and
7412 disregards @code{ctime}. Neither does it use @code{atime} (the last time the
7413 contents of the file were looked at).
7415 Date specifiers can have embedded spaces. Because of this, you may need
7416 to quote date arguments to keep the shell from parsing them as separate
7417 arguments. For example, the following command will add to the archive
7418 all the files modified less than two days ago:
7421 $ @kbd{tar -cf foo.tar --newer-mtime '2 days ago'}
7424 When any of these options is used with the option @option{--verbose}
7425 (@pxref{verbose tutorial}) @GNUTAR{} will try to convert the specified
7426 date back to its textual representation and compare that with the
7427 one given with the option. If the two dates differ, @command{tar} will
7428 print a warning saying what date it will use. This is to help user
7429 ensure he is using the right date. For example:
7433 $ @kbd{tar -c -f archive.tar --after-date='10 days ago' .}
7434 tar: Option --after-date: Treating date `10 days ago' as 2006-06-11
7440 @strong{Please Note:} @option{--after-date} and @option{--newer-mtime}
7441 should not be used for incremental backups. @xref{Incremental Dumps},
7442 for proper way of creating incremental backups.
7446 @section Descending into Directories
7448 @cindex Avoiding recursion in directories
7449 @cindex Descending directories, avoiding
7450 @cindex Directories, avoiding recursion
7451 @cindex Recursion in directories, avoiding
7453 @FIXME{arrggh! this is still somewhat confusing to me. :-< }
7455 Usually, @command{tar} will recursively explore all directories (either
7456 those given on the command line or through the @option{--files-from}
7457 option) for the various files they contain. However, you may not always
7458 want @command{tar} to act this way.
7460 @opindex no-recursion
7461 The @option{--no-recursion} option inhibits @command{tar}'s recursive descent
7462 into specified directories. If you specify @option{--no-recursion}, you can
7463 use the @command{find} utility for hunting through levels of directories to
7464 construct a list of file names which you could then pass to @command{tar}.
7465 @command{find} allows you to be more selective when choosing which files to
7466 archive; see @ref{files}, for more information on using @command{find} with
7467 @command{tar}, or look.
7470 @item --no-recursion
7471 Prevents @command{tar} from recursively descending directories.
7475 Requires @command{tar} to recursively descend directories.
7476 This is the default.
7479 When you use @option{--no-recursion}, @GNUTAR{} grabs
7480 directory entries themselves, but does not descend on them
7481 recursively. Many people use @command{find} for locating files they
7482 want to back up, and since @command{tar} @emph{usually} recursively
7483 descends on directories, they have to use the @samp{@w{-not -type d}}
7484 test in their @command{find} invocation (@pxref{Type, Type, Type test,
7485 find, Finding Files}), as they usually do not want all the files in a
7486 directory. They then use the @option{--files-from} option to archive
7487 the files located via @command{find}.
7489 The problem when restoring files archived in this manner is that the
7490 directories themselves are not in the archive; so the
7491 @option{--same-permissions} (@option{--preserve-permissions},
7492 @option{-p}) option does not affect them---while users might really
7493 like it to. Specifying @option{--no-recursion} is a way to tell
7494 @command{tar} to grab only the directory entries given to it, adding
7495 no new files on its own. To summarize, if you use @command{find} to
7496 create a list of files to be stored in an archive, use it as follows:
7500 $ @kbd{find @var{dir} @var{tests} | \
7501 tar -cf @var{archive} -T - --no-recursion}
7505 The @option{--no-recursion} option also applies when extracting: it
7506 causes @command{tar} to extract only the matched directory entries, not
7507 the files under those directories.
7509 The @option{--no-recursion} option also affects how globbing patterns
7510 are interpreted (@pxref{controlling pattern-matching}).
7512 The @option{--no-recursion} and @option{--recursion} options apply to
7513 later options and operands, and can be overridden by later occurrences
7514 of @option{--no-recursion} and @option{--recursion}. For example:
7517 $ @kbd{tar -cf jams.tar --no-recursion grape --recursion grape/concord}
7521 creates an archive with one entry for @file{grape}, and the recursive
7522 contents of @file{grape/concord}, but no entries under @file{grape}
7523 other than @file{grape/concord}.
7526 @section Crossing File System Boundaries
7527 @cindex File system boundaries, not crossing
7530 @command{tar} will normally automatically cross file system boundaries in
7531 order to archive files which are part of a directory tree. You can
7532 change this behavior by running @command{tar} and specifying
7533 @option{--one-file-system}. This option only affects files that are
7534 archived because they are in a directory that is being archived;
7535 @command{tar} will still archive files explicitly named on the command line
7536 or through @option{--files-from}, regardless of where they reside.
7539 @opindex one-file-system
7540 @item --one-file-system
7541 Prevents @command{tar} from crossing file system boundaries when
7542 archiving. Use in conjunction with any write operation.
7545 The @option{--one-file-system} option causes @command{tar} to modify its
7546 normal behavior in archiving the contents of directories. If a file in
7547 a directory is not on the same file system as the directory itself, then
7548 @command{tar} will not archive that file. If the file is a directory
7549 itself, @command{tar} will not archive anything beneath it; in other words,
7550 @command{tar} will not cross mount points.
7552 This option is useful for making full or incremental archival backups of
7553 a file system. If this option is used in conjunction with
7554 @option{--verbose} (@option{-v}), files that are excluded are
7555 mentioned by name on the standard error.
7558 * directory:: Changing Directory
7559 * absolute:: Absolute File Names
7563 @subsection Changing the Working Directory
7565 @FIXME{need to read over this node now for continuity; i've switched
7566 things around some.}
7568 @cindex Changing directory mid-stream
7569 @cindex Directory, changing mid-stream
7570 @cindex Working directory, specifying
7571 To change the working directory in the middle of a list of file names,
7572 either on the command line or in a file specified using
7573 @option{--files-from} (@option{-T}), use @option{--directory} (@option{-C}).
7574 This will change the working directory to the specified directory
7575 after that point in the list.
7579 @item --directory=@var{directory}
7580 @itemx -C @var{directory}
7581 Changes the working directory in the middle of a command line.
7587 $ @kbd{tar -c -f jams.tar grape prune -C food cherry}
7591 will place the files @file{grape} and @file{prune} from the current
7592 directory into the archive @file{jams.tar}, followed by the file
7593 @file{cherry} from the directory @file{food}. This option is especially
7594 useful when you have several widely separated files that you want to
7595 store in the same archive.
7597 Note that the file @file{cherry} is recorded in the archive under the
7598 precise name @file{cherry}, @emph{not} @file{food/cherry}. Thus, the
7599 archive will contain three files that all appear to have come from the
7600 same directory; if the archive is extracted with plain @samp{tar
7601 --extract}, all three files will be written in the current directory.
7603 Contrast this with the command,
7606 $ @kbd{tar -c -f jams.tar grape prune -C food red/cherry}
7610 which records the third file in the archive under the name
7611 @file{red/cherry} so that, if the archive is extracted using
7612 @samp{tar --extract}, the third file will be written in a subdirectory
7613 named @file{orange-colored}.
7615 You can use the @option{--directory} option to make the archive
7616 independent of the original name of the directory holding the files.
7617 The following command places the files @file{/etc/passwd},
7618 @file{/etc/hosts}, and @file{/lib/libc.a} into the archive
7622 $ @kbd{tar -c -f foo.tar -C /etc passwd hosts -C /lib libc.a}
7626 However, the names of the archive members will be exactly what they were
7627 on the command line: @file{passwd}, @file{hosts}, and @file{libc.a}.
7628 They will not appear to be related by file name to the original
7629 directories where those files were located.
7631 Note that @option{--directory} options are interpreted consecutively. If
7632 @option{--directory} specifies a relative file name, it is interpreted
7633 relative to the then current directory, which might not be the same as
7634 the original current working directory of @command{tar}, due to a previous
7635 @option{--directory} option.
7637 When using @option{--files-from} (@pxref{files}), you can put various
7638 @command{tar} options (including @option{-C}) in the file list. Notice,
7639 however, that in this case the option and its argument may not be
7640 separated by whitespace. If you use short option, its argument must
7641 either follow the option letter immediately, without any intervening
7642 whitespace, or occupy the next line. Otherwise, if you use long
7643 option, separate its argument by an equal sign.
7645 For instance, the file list for the above example will be:
7658 To use it, you would invoke @command{tar} as follows:
7661 $ @kbd{tar -c -f foo.tar --files-from list}
7664 The interpretation of @option{--directory} is disabled by
7665 @option{--null} option.
7668 @subsection Absolute File Names
7672 @opindex absolute-names
7673 @item --absolute-names
7675 Do not strip leading slashes from file names, and permit file names
7676 containing a @file{..} file name component.
7679 By default, @GNUTAR{} drops a leading @samp{/} on
7680 input or output, and complains about file names containing a @file{..}
7681 component. This option turns off this behavior.
7683 When @command{tar} extracts archive members from an archive, it strips any
7684 leading slashes (@samp{/}) from the member name. This causes absolute
7685 member names in the archive to be treated as relative file names. This
7686 allows you to have such members extracted wherever you want, instead of
7687 being restricted to extracting the member in the exact directory named
7688 in the archive. For example, if the archive member has the name
7689 @file{/etc/passwd}, @command{tar} will extract it as if the name were
7690 really @file{etc/passwd}.
7692 File names containing @file{..} can cause problems when extracting, so
7693 @command{tar} normally warns you about such files when creating an
7694 archive, and rejects attempts to extracts such files.
7696 Other @command{tar} programs do not do this. As a result, if you
7697 create an archive whose member names start with a slash, they will be
7698 difficult for other people with a non-@GNUTAR{}
7699 program to use. Therefore, @GNUTAR{} also strips
7700 leading slashes from member names when putting members into the
7701 archive. For example, if you ask @command{tar} to add the file
7702 @file{/bin/ls} to an archive, it will do so, but the member name will
7703 be @file{bin/ls}.@footnote{A side effect of this is that when
7704 @option{--create} is used with @option{--verbose} the resulting output
7705 is not, generally speaking, the same as the one you'd get running
7706 @kbd{tar --list} command. This may be important if you use some
7707 scripts for comparing both outputs. @xref{listing member and file names},
7708 for the information on how to handle this case.}
7710 If you use the @option{--absolute-names} (@option{-P}) option,
7711 @command{tar} will do none of these transformations.
7713 To archive or extract files relative to the root directory, specify
7714 the @option{--absolute-names} (@option{-P}) option.
7716 Normally, @command{tar} acts on files relative to the working
7717 directory---ignoring superior directory names when archiving, and
7718 ignoring leading slashes when extracting.
7720 When you specify @option{--absolute-names} (@option{-P}),
7721 @command{tar} stores file names including all superior directory
7722 names, and preserves leading slashes. If you only invoked
7723 @command{tar} from the root directory you would never need the
7724 @option{--absolute-names} option, but using this option
7725 may be more convenient than switching to root.
7727 @FIXME{Should be an example in the tutorial/wizardry section using this
7728 to transfer files between systems.}
7730 @FIXME{Is write access an issue?}
7733 @item --absolute-names
7734 Preserves full file names (including superior directory names) when
7735 archiving files. Preserves leading slash when extracting files.
7739 @FIXME{this is still horrible; need to talk with dan on monday.}
7741 @command{tar} prints out a message about removing the @samp{/} from
7742 file names. This message appears once per @GNUTAR{}
7743 invocation. It represents something which ought to be told; ignoring
7744 what it means can cause very serious surprises, later.
7746 Some people, nevertheless, do not want to see this message. Wanting to
7747 play really dangerously, one may of course redirect @command{tar} standard
7748 error to the sink. For example, under @command{sh}:
7751 $ @kbd{tar -c -f archive.tar /home 2> /dev/null}
7755 Another solution, both nicer and simpler, would be to change to
7756 the @file{/} directory first, and then avoid absolute notation.
7760 $ @kbd{(cd / && tar -c -f archive.tar home)}
7762 $ @kbd{tar -c -f archive.tar -C / home}
7765 @include getdate.texi
7768 @chapter Controlling the Archive Format
7770 @cindex Tar archive formats
7771 Due to historical reasons, there are several formats of tar archives.
7772 All of them are based on the same principles, but have some subtle
7773 differences that often make them incompatible with each other.
7775 GNU tar is able to create and handle archives in a variety of formats.
7776 The most frequently used formats are (in alphabetical order):
7780 Format used by @GNUTAR{} versions up to 1.13.25. This format derived
7781 from an early @acronym{POSIX} standard, adding some improvements such as
7782 sparse file handling and incremental archives. Unfortunately these
7783 features were implemented in a way incompatible with other archive
7786 Archives in @samp{gnu} format are able to hold pathnames of unlimited
7790 Format used by @GNUTAR{} of versions prior to 1.12.
7793 Archive format, compatible with the V7 implementation of tar. This
7794 format imposes a number of limitations. The most important of them
7798 @item The maximum length of a file name is limited to 99 characters.
7799 @item The maximum length of a symbolic link is limited to 99 characters.
7800 @item It is impossible to store special files (block and character
7801 devices, fifos etc.)
7802 @item Maximum value of user or group ID is limited to 2097151 (7777777
7804 @item V7 archives do not contain symbolic ownership information (user
7805 and group name of the file owner).
7808 This format has traditionally been used by Automake when producing
7809 Makefiles. This practice will change in the future, in the meantime,
7810 however this means that projects containing filenames more than 99
7811 characters long will not be able to use @GNUTAR{} @value{VERSION} and
7812 Automake prior to 1.9.
7815 Archive format defined by @acronym{POSIX.1-1988} specification. It stores
7816 symbolic ownership information. It is also able to store
7817 special files. However, it imposes several restrictions as well:
7820 @item The maximum length of a file name is limited to 256 characters,
7821 provided that the filename can be split at directory separator in
7822 two parts, first of them being at most 155 bytes long. So, in most
7823 cases the maximum file name length will be shorter than 256
7825 @item The maximum length of a symbolic link name is limited to
7827 @item Maximum size of a file the archive is able to accommodate
7829 @item Maximum value of UID/GID is 2097151.
7830 @item Maximum number of bits in device major and minor numbers is 21.
7834 Format used by J@"org Schilling @command{star}
7835 implementation. @GNUTAR{} is able to read @samp{star} archives but
7836 currently does not produce them.
7839 Archive format defined by @acronym{POSIX.1-2001} specification. This is the
7840 most flexible and feature-rich format. It does not impose any
7841 restrictions on file sizes or filename lengths. This format is quite
7842 recent, so not all tar implementations are able to handle it properly.
7843 However, this format is designed in such a way that any tar
7844 implementation able to read @samp{ustar} archives will be able to read
7845 most @samp{posix} archives as well, with the only exception that any
7846 additional information (such as long file names etc.) will in such
7847 case be extracted as plain text files along with the files it refers to.
7849 This archive format will be the default format for future versions
7854 The following table summarizes the limitations of each of these
7857 @multitable @columnfractions .10 .20 .20 .20 .20
7858 @headitem Format @tab UID @tab File Size @tab Path Name @tab Devn
7859 @item gnu @tab 1.8e19 @tab Unlimited @tab Unlimited @tab 63
7860 @item oldgnu @tab 1.8e19 @tab Unlimited @tab Unlimited @tab 63
7861 @item v7 @tab 2097151 @tab 8GB @tab 99 @tab n/a
7862 @item ustar @tab 2097151 @tab 8GB @tab 256 @tab 21
7863 @item posix @tab Unlimited @tab Unlimited @tab Unlimited @tab Unlimited
7866 The default format for @GNUTAR{} is defined at compilation
7867 time. You may check it by running @command{tar --help}, and examining
7868 the last lines of its output. Usually, @GNUTAR{} is configured
7869 to create archives in @samp{gnu} format, however, future version will
7870 switch to @samp{posix}.
7873 * Compression:: Using Less Space through Compression
7874 * Attributes:: Handling File Attributes
7875 * Portability:: Making @command{tar} Archives More Portable
7876 * cpio:: Comparison of @command{tar} and @command{cpio}
7880 @section Using Less Space through Compression
7883 * gzip:: Creating and Reading Compressed Archives
7884 * sparse:: Archiving Sparse Files
7888 @subsection Creating and Reading Compressed Archives
7889 @cindex Compressed archives
7890 @cindex Storing archives in compressed format
7892 @GNUTAR{} is able to create and read compressed archives. It supports
7893 @command{gzip} and @command{bzip2} compression programs. For backward
7894 compatibility, it also supports @command{compress} command, although
7895 we strongly recommend against using it, since there is a patent
7896 covering the algorithm it uses and you could be sued for patent
7897 infringement merely by running @command{compress}! Besides, it is less
7898 effective than @command{gzip} and @command{bzip2}.
7900 Creating a compressed archive is simple: you just specify a
7901 @dfn{compression option} along with the usual archive creation
7902 commands. The compression option is @option{-z} (@option{--gzip}) to
7903 create a @command{gzip} compressed archive, @option{-j}
7904 (@option{--bzip2}) to create a @command{bzip2} compressed archive, and
7905 @option{-Z} (@option{--compress}) to use @command{compress} program.
7909 $ @kbd{tar cfz archive.tar.gz .}
7912 Reading compressed archive is even simpler: you don't need to specify
7913 any additional options as @GNUTAR{} recognizes its format
7914 automatically. Thus, the following commands will list and extract the
7915 archive created in previous example:
7918 # List the compressed archive
7919 $ @kbd{tar tf archive.tar.gz}
7920 # Extract the compressed archive
7921 $ @kbd{tar xf archive.tar.gz}
7924 The only case when you have to specify a decompression option while
7925 reading the archive is when reading from a pipe or from a tape drive
7926 that does not support random access. However, in this case @GNUTAR{}
7927 will indicate which option you should use. For example:
7930 $ @kbd{cat archive.tar.gz | tar tf -}
7931 tar: Archive is compressed. Use -z option
7932 tar: Error is not recoverable: exiting now
7935 If you see such diagnostics, just add the suggested option to the
7936 invocation of @GNUTAR{}:
7939 $ @kbd{cat archive.tar.gz | tar tfz -}
7942 Notice also, that there are several restrictions on operations on
7943 compressed archives. First of all, compressed archives cannot be
7944 modified, i.e., you cannot update (@option{--update} (@option{-u})) them or delete
7945 (@option{--delete}) members from them. Likewise, you cannot append
7946 another @command{tar} archive to a compressed archive using
7947 @option{--append} (@option{-r})). Secondly, multi-volume archives cannot be
7950 The following table summarizes compression options used by @GNUTAR{}.
7958 Filter the archive through @command{gzip}.
7960 You can use @option{--gzip} and @option{--gunzip} on physical devices
7961 (tape drives, etc.) and remote files as well as on normal files; data
7962 to or from such devices or remote files is reblocked by another copy
7963 of the @command{tar} program to enforce the specified (or default) record
7964 size. The default compression parameters are used; if you need to
7965 override them, set @env{GZIP} environment variable, e.g.:
7968 $ @kbd{GZIP=--best tar cfz archive.tar.gz subdir}
7972 Another way would be to avoid the @option{--gzip} (@option{--gunzip}, @option{--ungzip}, @option{-z}) option and run
7973 @command{gzip} explicitly:
7976 $ @kbd{tar cf - subdir | gzip --best -c - > archive.tar.gz}
7979 @cindex corrupted archives
7980 About corrupted compressed archives: @command{gzip}'ed files have no
7981 redundancy, for maximum compression. The adaptive nature of the
7982 compression scheme means that the compression tables are implicitly
7983 spread all over the archive. If you lose a few blocks, the dynamic
7984 construction of the compression tables becomes unsynchronized, and there
7985 is little chance that you could recover later in the archive.
7987 There are pending suggestions for having a per-volume or per-file
7988 compression in @GNUTAR{}. This would allow for viewing the
7989 contents without decompression, and for resynchronizing decompression at
7990 every volume or file, in case of corrupted archives. Doing so, we might
7991 lose some compressibility. But this would have make recovering easier.
7992 So, there are pros and cons. We'll see!
7997 Filter the archive through @code{bzip2}. Otherwise like @option{--gzip}.
8004 Filter the archive through @command{compress}. Otherwise like @option{--gzip}.
8006 The @acronym{GNU} Project recommends you not use
8007 @command{compress}, because there is a patent covering the algorithm it
8008 uses. You could be sued for patent infringement merely by running
8011 @opindex use-compress-program
8012 @item --use-compress-program=@var{prog}
8013 Use external compression program @var{prog}. Use this option if you
8014 have a compression program that @GNUTAR{} does not support. There
8015 are two requirements to which @var{prog} should comply:
8017 First, when called without options, it should read data from standard
8018 input, compress it and output it on standard output.
8020 Secondly, if called with @option{-d} argument, it should do exactly
8021 the opposite, i.e., read the compressed data from the standard input
8022 and produce uncompressed data on the standard output.
8025 @cindex gpg, using with tar
8026 @cindex gnupg, using with tar
8027 @cindex Using encrypted archives
8028 The @option{--use-compress-program} option, in particular, lets you
8029 implement your own filters, not necessarily dealing with
8030 compression/decompression. For example, suppose you wish to implement
8031 PGP encryption on top of compression, using @command{gpg} (@pxref{Top,
8032 gpg, gpg ---- encryption and signing tool, gpg, GNU Privacy Guard
8033 Manual}). The following script does that:
8039 -d) gpg --decrypt - | gzip -d -c;;
8040 '') gzip -c | gpg -s ;;
8041 *) echo "Unknown option $1">&2; exit 1;;
8046 Suppose you name it @file{gpgz} and save it somewhere in your
8047 @env{PATH}. Then the following command will create a compressed
8048 archive signed with your private key:
8051 $ @kbd{tar -cf foo.tar.gpgz --use-compress=gpgz .}
8055 Likewise, the following command will list its contents:
8058 $ @kbd{tar -tf foo.tar.gpgz --use-compress=gpgz .}
8062 The above is based on the following discussion:
8064 I have one question, or maybe it's a suggestion if there isn't a way
8065 to do it now. I would like to use @option{--gzip}, but I'd also like
8066 the output to be fed through a program like @acronym{GNU}
8067 @command{ecc} (actually, right now that's @samp{exactly} what I'd like
8068 to use :-)), basically adding ECC protection on top of compression.
8069 It seems as if this should be quite easy to do, but I can't work out
8070 exactly how to go about it. Of course, I can pipe the standard output
8071 of @command{tar} through @command{ecc}, but then I lose (though I
8072 haven't started using it yet, I confess) the ability to have
8073 @command{tar} use @command{rmt} for it's I/O (I think).
8075 I think the most straightforward thing would be to let me specify a
8076 general set of filters outboard of compression (preferably ordered,
8077 so the order can be automatically reversed on input operations, and
8078 with the options they require specifiable), but beggars shouldn't be
8079 choosers and anything you decide on would be fine with me.
8081 By the way, I like @command{ecc} but if (as the comments say) it can't
8082 deal with loss of block sync, I'm tempted to throw some time at adding
8083 that capability. Supposing I were to actually do such a thing and
8084 get it (apparently) working, do you accept contributed changes to
8085 utilities like that? (Leigh Clayton @file{loc@@soliton.com}, May 1995).
8087 Isn't that exactly the role of the
8088 @option{--use-compress-prog=@var{program}} option?
8089 I never tried it myself, but I suspect you may want to write a
8090 @var{prog} script or program able to filter stdin to stdout to
8091 way you want. It should recognize the @option{-d} option, for when
8092 extraction is needed rather than creation.
8094 It has been reported that if one writes compressed data (through the
8095 @option{--gzip} or @option{--compress} options) to a DLT and tries to use
8096 the DLT compression mode, the data will actually get bigger and one will
8097 end up with less space on the tape.
8101 @subsection Archiving Sparse Files
8102 @cindex Sparse Files
8104 Files in the file system occasionally have @dfn{holes}. A @dfn{hole}
8105 in a file is a section of the file's contents which was never written.
8106 The contents of a hole reads as all zeros. On many operating systems,
8107 actual disk storage is not allocated for holes, but they are counted
8108 in the length of the file. If you archive such a file, @command{tar}
8109 could create an archive longer than the original. To have @command{tar}
8110 attempt to recognize the holes in a file, use @option{--sparse}
8111 (@option{-S}). When you use this option, then, for any file using
8112 less disk space than would be expected from its length, @command{tar}
8113 searches the file for consecutive stretches of zeros. It then records
8114 in the archive for the file where the consecutive stretches of zeros
8115 are, and only archives the ``real contents'' of the file. On
8116 extraction (using @option{--sparse} is not needed on extraction) any
8117 such files have holes created wherever the continuous stretches of zeros
8118 were found. Thus, if you use @option{--sparse}, @command{tar} archives
8119 won't take more space than the original.
8125 This option instructs @command{tar} to test each file for sparseness
8126 before attempting to archive it. If the file is found to be sparse it
8127 is treated specially, thus allowing to decrease the amount of space
8128 used by its image in the archive.
8130 This option is meaningful only when creating or updating archives. It
8131 has no effect on extraction.
8134 Consider using @option{--sparse} when performing file system backups,
8135 to avoid archiving the expanded forms of files stored sparsely in the
8138 Even if your system has no sparse files currently, some may be
8139 created in the future. If you use @option{--sparse} while making file
8140 system backups as a matter of course, you can be assured the archive
8141 will never take more space on the media than the files take on disk
8142 (otherwise, archiving a disk filled with sparse files might take
8143 hundreds of tapes). @xref{Incremental Dumps}.
8145 However, be aware that @option{--sparse} option presents a serious
8146 drawback. Namely, in order to determine if the file is sparse
8147 @command{tar} has to read it before trying to archive it, so in total
8148 the file is read @strong{twice}. So, always bear in mind that the
8149 time needed to process all files with this option is roughly twice
8150 the time needed to archive them without it.
8151 @FIXME{A technical note:
8153 Programs like @command{dump} do not have to read the entire file; by
8154 examining the file system directly, they can determine in advance
8155 exactly where the holes are and thus avoid reading through them. The
8156 only data it need read are the actual allocated data blocks.
8157 @GNUTAR{} uses a more portable and straightforward
8158 archiving approach, it would be fairly difficult that it does
8159 otherwise. Elizabeth Zwicky writes to @file{comp.unix.internals}, on
8163 What I did say is that you cannot tell the difference between a hole and an
8164 equivalent number of nulls without reading raw blocks. @code{st_blocks} at
8165 best tells you how many holes there are; it doesn't tell you @emph{where}.
8166 Just as programs may, conceivably, care what @code{st_blocks} is (care
8167 to name one that does?), they may also care where the holes are (I have
8168 no examples of this one either, but it's equally imaginable).
8170 I conclude from this that good archivers are not portable. One can
8171 arguably conclude that if you want a portable program, you can in good
8172 conscience restore files with as many holes as possible, since you can't
8177 @cindex sparse formats, defined
8178 When using @samp{POSIX} archive format, @GNUTAR{} is able to store
8179 sparse files using in three distinct ways, called @dfn{sparse
8180 formats}. A sparse format is identified by its @dfn{number},
8181 consisting, as usual of two decimal numbers, delimited by a dot. By
8182 default, format @samp{1.0} is used. If, for some reason, you wish to
8183 use an earlier format, you can select it using
8184 @option{--sparse-version} option.
8187 @opindex sparse-version
8188 @item --sparse-version=@var{version}
8190 Select the format to store sparse files in. Valid @var{version} values
8191 are: @samp{0.0}, @samp{0.1} and @samp{1.0}. @xref{Sparse Formats},
8192 for a detailed description of each format.
8195 Using @option{--sparse-format} option implies @option{--sparse}.
8198 @section Handling File Attributes
8201 When @command{tar} reads files, it updates their access times. To
8202 avoid this, use the @option{--atime-preserve[=METHOD]} option, which can either
8203 reset the access time retroactively or avoid changing it in the first
8206 Handling of file attributes
8209 @opindex atime-preserve
8210 @item --atime-preserve
8211 @itemx --atime-preserve=replace
8212 @itemx --atime-preserve=system
8213 Preserve the access times of files that are read. This works only for
8214 files that you own, unless you have superuser privileges.
8216 @option{--atime-preserve=replace} works on most systems, but it also
8217 restores the data modification time and updates the status change
8218 time. Hence it doesn't interact with incremental dumps nicely
8219 (@pxref{Incremental Dumps}), and it can set access or data modification times
8220 incorrectly if other programs access the file while @command{tar} is
8223 @option{--atime-preserve=system} avoids changing the access time in
8224 the first place, if the operating system supports this.
8225 Unfortunately, this may or may not work on any given operating system
8226 or file system. If @command{tar} knows for sure it won't work, it
8227 complains right away.
8229 Currently @option{--atime-preserve} with no operand defaults to
8230 @option{--atime-preserve=replace}, but this is intended to change to
8231 @option{--atime-preserve=system} when the latter is better-supported.
8236 Do not extract data modification time.
8238 When this option is used, @command{tar} leaves the data modification times
8239 of the files it extracts as the times when the files were extracted,
8240 instead of setting it to the times recorded in the archive.
8242 This option is meaningless with @option{--list} (@option{-t}).
8246 Create extracted files with the same ownership they have in the
8249 This is the default behavior for the superuser,
8250 so this option is meaningful only for non-root users, when @command{tar}
8251 is executed on those systems able to give files away. This is
8252 considered as a security flaw by many people, at least because it
8253 makes quite difficult to correctly account users for the disk space
8254 they occupy. Also, the @code{suid} or @code{sgid} attributes of
8255 files are easily and silently lost when files are given away.
8257 When writing an archive, @command{tar} writes the user id and user name
8258 separately. If it can't find a user name (because the user id is not
8259 in @file{/etc/passwd}), then it does not write one. When restoring,
8260 it tries to look the name (if one was written) up in
8261 @file{/etc/passwd}. If it fails, then it uses the user id stored in
8262 the archive instead.
8264 @opindex no-same-owner
8265 @item --no-same-owner
8267 Do not attempt to restore ownership when extracting. This is the
8268 default behavior for ordinary users, so this option has an effect
8269 only for the superuser.
8271 @opindex numeric-owner
8272 @item --numeric-owner
8273 The @option{--numeric-owner} option allows (ANSI) archives to be written
8274 without user/group name information or such information to be ignored
8275 when extracting. It effectively disables the generation and/or use
8276 of user/group name information. This option forces extraction using
8277 the numeric ids from the archive, ignoring the names.
8279 This is useful in certain circumstances, when restoring a backup from
8280 an emergency floppy with different passwd/group files for example.
8281 It is otherwise impossible to extract files with the right ownerships
8282 if the password file in use during the extraction does not match the
8283 one belonging to the file system(s) being extracted. This occurs,
8284 for example, if you are restoring your files after a major crash and
8285 had booted from an emergency floppy with no password file or put your
8286 disk into another machine to do the restore.
8288 The numeric ids are @emph{always} saved into @command{tar} archives.
8289 The identifying names are added at create time when provided by the
8290 system, unless @option{--old-archive} (@option{-o}) is used. Numeric ids could be
8291 used when moving archives between a collection of machines using
8292 a centralized management for attribution of numeric ids to users
8293 and groups. This is often made through using the NIS capabilities.
8295 When making a @command{tar} file for distribution to other sites, it
8296 is sometimes cleaner to use a single owner for all files in the
8297 distribution, and nicer to specify the write permission bits of the
8298 files as stored in the archive independently of their actual value on
8299 the file system. The way to prepare a clean distribution is usually
8300 to have some Makefile rule creating a directory, copying all needed
8301 files in that directory, then setting ownership and permissions as
8302 wanted (there are a lot of possible schemes), and only then making a
8303 @command{tar} archive out of this directory, before cleaning
8304 everything out. Of course, we could add a lot of options to
8305 @GNUTAR{} for fine tuning permissions and ownership.
8306 This is not the good way, I think. @GNUTAR{} is
8307 already crowded with options and moreover, the approach just explained
8308 gives you a great deal of control already.
8310 @xopindex{same-permissions, short description}
8311 @xopindex{preserve-permissions, short description}
8313 @itemx --same-permissions
8314 @itemx --preserve-permissions
8315 Extract all protection information.
8317 This option causes @command{tar} to set the modes (access permissions) of
8318 extracted files exactly as recorded in the archive. If this option
8319 is not used, the current @code{umask} setting limits the permissions
8320 on extracted files. This option is by default enabled when
8321 @command{tar} is executed by a superuser.
8324 This option is meaningless with @option{--list} (@option{-t}).
8328 Same as both @option{--same-permissions} and @option{--same-order}.
8330 The @option{--preserve} option has no equivalent short option name.
8331 It is equivalent to @option{--same-permissions} plus @option{--same-order}.
8333 @FIXME{I do not see the purpose of such an option. (Neither I. FP.)
8334 Neither do I. --Sergey}
8339 @section Making @command{tar} Archives More Portable
8341 Creating a @command{tar} archive on a particular system that is meant to be
8342 useful later on many other machines and with other versions of @command{tar}
8343 is more challenging than you might think. @command{tar} archive formats
8344 have been evolving since the first versions of Unix. Many such formats
8345 are around, and are not always compatible with each other. This section
8346 discusses a few problems, and gives some advice about making @command{tar}
8347 archives more portable.
8349 One golden rule is simplicity. For example, limit your @command{tar}
8350 archives to contain only regular files and directories, avoiding
8351 other kind of special files. Do not attempt to save sparse files or
8352 contiguous files as such. Let's discuss a few more problems, in turn.
8354 @FIXME{Discuss GNU extensions (incremental backups, multi-volume
8355 archives and archive labels) in GNU and PAX formats.}
8358 * Portable Names:: Portable Names
8359 * dereference:: Symbolic Links
8360 * old:: Old V7 Archives
8361 * ustar:: Ustar Archives
8362 * gnu:: GNU and old GNU format archives.
8363 * posix:: @acronym{POSIX} archives
8364 * Checksumming:: Checksumming Problems
8365 * Large or Negative Values:: Large files, negative time stamps, etc.
8366 * Other Tars:: How to Extract GNU-Specific Data Using
8367 Other @command{tar} Implementations
8370 @node Portable Names
8371 @subsection Portable Names
8373 Use portable file and member names. A name is portable if it contains
8374 only ASCII letters and digits, @samp{/}, @samp{.}, @samp{_}, and
8375 @samp{-}; it cannot be empty, start with @samp{-} or @samp{//}, or
8376 contain @samp{/-}. Avoid deep directory nesting. For portability to
8377 old Unix hosts, limit your file name components to 14 characters or
8380 If you intend to have your @command{tar} archives to be read under
8381 MSDOS, you should not rely on case distinction for file names, and you
8382 might use the @acronym{GNU} @command{doschk} program for helping you
8383 further diagnosing illegal MSDOS names, which are even more limited
8387 @subsection Symbolic Links
8388 @cindex File names, using symbolic links
8389 @cindex Symbolic link as file name
8391 @opindex dereference
8392 Normally, when @command{tar} archives a symbolic link, it writes a
8393 block to the archive naming the target of the link. In that way, the
8394 @command{tar} archive is a faithful record of the file system contents.
8395 @option{--dereference} (@option{-h}) is used with @option{--create} (@option{-c}), and causes
8396 @command{tar} to archive the files symbolic links point to, instead of
8397 the links themselves. When this option is used, when @command{tar}
8398 encounters a symbolic link, it will archive the linked-to file,
8399 instead of simply recording the presence of a symbolic link.
8401 The name under which the file is stored in the file system is not
8402 recorded in the archive. To record both the symbolic link name and
8403 the file name in the system, archive the file under both names. If
8404 all links were recorded automatically by @command{tar}, an extracted file
8405 might be linked to a file name that no longer exists in the file
8408 If a linked-to file is encountered again by @command{tar} while creating
8409 the same archive, an entire second copy of it will be stored. (This
8410 @emph{might} be considered a bug.)
8412 So, for portable archives, do not archive symbolic links as such,
8413 and use @option{--dereference} (@option{-h}): many systems do not support
8414 symbolic links, and moreover, your distribution might be unusable if
8415 it contains unresolved symbolic links.
8418 @subsection Old V7 Archives
8419 @cindex Format, old style
8420 @cindex Old style format
8421 @cindex Old style archives
8422 @cindex v7 archive format
8424 Certain old versions of @command{tar} cannot handle additional
8425 information recorded by newer @command{tar} programs. To create an
8426 archive in V7 format (not ANSI), which can be read by these old
8427 versions, specify the @option{--format=v7} option in
8428 conjunction with the @option{--create} (@option{-c}) (@command{tar} also
8429 accepts @option{--portability} or @option{--old-archive} for this
8430 option). When you specify it,
8431 @command{tar} leaves out information about directories, pipes, fifos,
8432 contiguous files, and device files, and specifies file ownership by
8433 group and user IDs instead of group and user names.
8435 When updating an archive, do not use @option{--format=v7}
8436 unless the archive was created using this option.
8438 In most cases, a @emph{new} format archive can be read by an @emph{old}
8439 @command{tar} program without serious trouble, so this option should
8440 seldom be needed. On the other hand, most modern @command{tar}s are
8441 able to read old format archives, so it might be safer for you to
8442 always use @option{--format=v7} for your distributions. Notice,
8443 however, that @samp{ustar} format is a better alternative, as it is
8444 free from many of @samp{v7}'s drawbacks.
8447 @subsection Ustar Archive Format
8449 @cindex ustar archive format
8450 Archive format defined by @acronym{POSIX}.1-1988 specification is called
8451 @code{ustar}. Although it is more flexible than the V7 format, it
8452 still has many restrictions (@xref{Formats,ustar}, for the detailed
8453 description of @code{ustar} format). Along with V7 format,
8454 @code{ustar} format is a good choice for archives intended to be read
8455 with other implementations of @command{tar}.
8457 To create archive in @code{ustar} format, use @option{--format=ustar}
8458 option in conjunction with the @option{--create} (@option{-c}).
8461 @subsection @acronym{GNU} and old @GNUTAR{} format
8463 @cindex GNU archive format
8464 @cindex Old GNU archive format
8465 @GNUTAR{} was based on an early draft of the
8466 @acronym{POSIX} 1003.1 @code{ustar} standard. @acronym{GNU} extensions to
8467 @command{tar}, such as the support for file names longer than 100
8468 characters, use portions of the @command{tar} header record which were
8469 specified in that @acronym{POSIX} draft as unused. Subsequent changes in
8470 @acronym{POSIX} have allocated the same parts of the header record for
8471 other purposes. As a result, @GNUTAR{} format is
8472 incompatible with the current @acronym{POSIX} specification, and with
8473 @command{tar} programs that follow it.
8475 In the majority of cases, @command{tar} will be configured to create
8476 this format by default. This will change in the future releases, since
8477 we plan to make @samp{POSIX} format the default.
8479 To force creation a @GNUTAR{} archive, use option
8480 @option{--format=gnu}.
8483 @subsection @GNUTAR{} and @acronym{POSIX} @command{tar}
8485 @cindex POSIX archive format
8486 @cindex PAX archive format
8487 Starting from version 1.14 @GNUTAR{} features full support for
8488 @acronym{POSIX.1-2001} archives.
8490 A @acronym{POSIX} conformant archive will be created if @command{tar}
8491 was given @option{--format=posix} (@option{--format=pax}) option. No
8492 special option is required to read and extract from a @acronym{POSIX}
8496 * PAX keywords:: Controlling Extended Header Keywords.
8500 @subsubsection Controlling Extended Header Keywords
8504 @item --pax-option=@var{keyword-list}
8505 Handle keywords in @acronym{PAX} extended headers. This option is
8506 equivalent to @option{-o} option of the @command{pax} utility.
8509 @var{Keyword-list} is a comma-separated
8510 list of keyword options, each keyword option taking one of
8511 the following forms:
8514 @item delete=@var{pattern}
8515 When used with one of archive-creation commands,
8516 this option instructs @command{tar} to omit from extended header records
8517 that it produces any keywords matching the string @var{pattern}.
8519 When used in extract or list mode, this option instructs tar
8520 to ignore any keywords matching the given @var{pattern} in the extended
8521 header records. In both cases, matching is performed using the pattern
8522 matching notation described in @acronym{POSIX 1003.2}, 3.13
8523 (@pxref{wildcards}). For example:
8526 --pax-option delete=security.*
8529 would suppress security-related information.
8531 @item exthdr.name=@var{string}
8533 This keyword allows user control over the name that is written into the
8534 ustar header blocks for the extended headers. The name is obtained
8535 from @var{string} after making the following substitutions:
8537 @multitable @columnfractions .25 .55
8538 @headitem Meta-character @tab Replaced By
8539 @item %d @tab The directory name of the file, equivalent to the
8540 result of the @command{dirname} utility on the translated pathname.
8541 @item %f @tab The filename of the file, equivalent to the result
8542 of the @command{basename} utility on the translated pathname.
8543 @item %p @tab The process ID of the @command{tar} process.
8544 @item %% @tab A @samp{%} character.
8547 Any other @samp{%} characters in @var{string} produce undefined
8550 If no option @samp{exthdr.name=string} is specified, @command{tar}
8551 will use the following default value:
8557 @item globexthdr.name=@var{string}
8558 This keyword allows user control over the name that is written into
8559 the ustar header blocks for global extended header records. The name
8560 is obtained from the contents of @var{string}, after making
8561 the following substitutions:
8563 @multitable @columnfractions .25 .55
8564 @headitem Meta-character @tab Replaced By
8565 @item %n @tab An integer that represents the
8566 sequence number of the global extended header record in the archive,
8568 @item %p @tab The process ID of the @command{tar} process.
8569 @item %% @tab A @samp{%} character.
8572 Any other @samp{%} characters in @var{string} produce undefined results.
8574 If no option @samp{globexthdr.name=string} is specified, @command{tar}
8575 will use the following default value:
8578 $TMPDIR/GlobalHead.%p.%n
8582 where @samp{$TMPDIR} represents the value of the @var{TMPDIR}
8583 environment variable. If @var{TMPDIR} is not set, @command{tar}
8586 @item @var{keyword}=@var{value}
8587 When used with one of archive-creation commands, these keyword/value pairs
8588 will be included at the beginning of the archive in a global extended
8589 header record. When used with one of archive-reading commands,
8590 @command{tar} will behave as if it has encountered these keyword/value
8591 pairs at the beginning of the archive in a global extended header
8594 @item @var{keyword}:=@var{value}
8595 When used with one of archive-creation commands, these keyword/value pairs
8596 will be included as records at the beginning of an extended header for
8597 each file. This is effectively equivalent to @var{keyword}=@var{value}
8598 form except that it creates no global extended header records.
8600 When used with one of archive-reading commands, @command{tar} will
8601 behave as if these keyword/value pairs were included as records at the
8602 end of each extended header; thus, they will override any global or
8603 file-specific extended header record keywords of the same names.
8604 For example, in the command:
8607 tar --format=posix --create \
8608 --file archive --pax-option gname:=user .
8611 the group name will be forced to a new value for all files
8612 stored in the archive.
8616 @subsection Checksumming Problems
8618 SunOS and HP-UX @command{tar} fail to accept archives created using
8619 @GNUTAR{} and containing non-ASCII file names, that
8620 is, file names having characters with the eight bit set, because they
8621 use signed checksums, while @GNUTAR{} uses unsigned
8622 checksums while creating archives, as per @acronym{POSIX} standards. On
8623 reading, @GNUTAR{} computes both checksums and
8624 accept any. It is somewhat worrying that a lot of people may go
8625 around doing backup of their files using faulty (or at least
8626 non-standard) software, not learning about it until it's time to
8627 restore their missing files with an incompatible file extractor, or
8630 @GNUTAR{} compute checksums both ways, and accept
8631 any on read, so @acronym{GNU} tar can read Sun tapes even with their
8632 wrong checksums. @GNUTAR{} produces the standard
8633 checksum, however, raising incompatibilities with Sun. That is to
8634 say, @GNUTAR{} has not been modified to
8635 @emph{produce} incorrect archives to be read by buggy @command{tar}'s.
8636 I've been told that more recent Sun @command{tar} now read standard
8637 archives, so maybe Sun did a similar patch, after all?
8639 The story seems to be that when Sun first imported @command{tar}
8640 sources on their system, they recompiled it without realizing that
8641 the checksums were computed differently, because of a change in
8642 the default signing of @code{char}'s in their compiler. So they
8643 started computing checksums wrongly. When they later realized their
8644 mistake, they merely decided to stay compatible with it, and with
8645 themselves afterwards. Presumably, but I do not really know, HP-UX
8646 has chosen that their @command{tar} archives to be compatible with Sun's.
8647 The current standards do not favor Sun @command{tar} format. In any
8648 case, it now falls on the shoulders of SunOS and HP-UX users to get
8649 a @command{tar} able to read the good archives they receive.
8651 @node Large or Negative Values
8652 @subsection Large or Negative Values
8653 @cindex large values
8654 @cindex future time stamps
8655 @cindex negative time stamps
8658 The above sections suggest to use @samp{oldest possible} archive
8659 format if in doubt. However, sometimes it is not possible. If you
8660 attempt to archive a file whose metadata cannot be represented using
8661 required format, @GNUTAR{} will print error message and ignore such a
8662 file. You will than have to switch to a format that is able to
8663 handle such values. The format summary table (@pxref{Formats}) will
8666 In particular, when trying to archive files larger than 8GB or with
8667 timestamps not in the range 1970-01-01 00:00:00 through 2242-03-16
8668 12:56:31 @sc{utc}, you will have to chose between @acronym{GNU} and
8669 @acronym{POSIX} archive formats. When considering which format to
8670 choose, bear in mind that the @acronym{GNU} format uses
8671 two's-complement base-256 notation to store values that do not fit
8672 into standard @acronym{ustar} range. Such archives can generally be
8673 read only by a @GNUTAR{} implementation. Moreover, they sometimes
8674 cannot be correctly restored on another hosts even by @GNUTAR{}. For
8675 example, using two's complement representation for negative time
8676 stamps that assumes a signed 32-bit @code{time_t} generates archives
8677 that are not portable to hosts with differing @code{time_t}
8680 On the other hand, @acronym{POSIX} archives, generally speaking, can
8681 be extracted by any tar implementation that understands older
8682 @acronym{ustar} format. The only exception are files larger than 8GB.
8684 @FIXME{Describe how @acronym{POSIX} archives are extracted by non
8688 @subsection How to Extract GNU-Specific Data Using Other @command{tar} Implementations
8690 In previous sections you became acquainted with various quirks
8691 necessary to make your archives portable. Sometimes you may need to
8692 extract archives containing GNU-specific members using some
8693 third-party @command{tar} implementation or an older version of
8694 @GNUTAR{}. Of course your best bet is to have @GNUTAR{} installed,
8695 but if it is for some reason impossible, this section will explain
8696 how to cope without it.
8698 When we speak about @dfn{GNU-specific} members we mean two classes of
8699 them: members split between the volumes of a multi-volume archive and
8700 sparse members. You will be able to always recover such members if
8701 the archive is in PAX format. In addition split members can be
8702 recovered from archives in old GNU format. The following subsections
8703 describe the required procedures in detail.
8706 * Split Recovery:: Members Split Between Volumes
8707 * Sparse Recovery:: Sparse Members
8710 @node Split Recovery
8711 @subsubsection Extracting Members Split Between Volumes
8713 @cindex Mutli-volume archives, extracting using non-GNU tars
8714 If a member is split between several volumes of an old GNU format archive
8715 most third party @command{tar} implementation will fail to extract
8716 it. To extract it, use @command{tarcat} program (@pxref{Tarcat}).
8717 This program is available from
8718 @uref{http://www.gnu.org/@/software/@/tar/@/utils/@/tarcat.html, @GNUTAR{}
8719 home page}. It concatenates several archive volumes into a single
8720 valid archive. For example, if you have three volumes named from
8721 @file{vol-1.tar} to @file{vol-3.tar}, you can do the following to
8722 extract them using a third-party @command{tar}:
8725 $ @kbd{tarcat vol-1.tar vol-2.tar vol-3.tar | tar xf -}
8728 @cindex Mutli-volume archives in PAX format, extracting using non-GNU tars
8729 You could use this approach for most (although not all) PAX
8730 format archives as well. However, extracting split members from a PAX
8731 archive is a much easier task, because PAX volumes are constructed in
8732 such a way that each part of a split member is extracted to a
8733 different file by @command{tar} implementations that are not aware of
8734 GNU extensions. More specifically, the very first part retains its
8735 original name, and all subsequent parts are named using the pattern:
8738 %d/GNUFileParts.%p/%f.%n
8742 where symbols preceeded by @samp{%} are @dfn{macro characters} that
8743 have the following meaning:
8745 @multitable @columnfractions .25 .55
8746 @headitem Meta-character @tab Replaced By
8747 @item %d @tab The directory name of the file, equivalent to the
8748 result of the @command{dirname} utility on its full name.
8749 @item %f @tab The file name of the file, equivalent to the result
8750 of the @command{basename} utility on its full name.
8751 @item %p @tab The process ID of the @command{tar} process that
8752 created the archive.
8753 @item %n @tab Ordinal number of this particular part.
8756 For example, if the file @file{var/longfile} was split during archive
8757 creation between three volumes, and the creator @command{tar} process
8758 had process ID @samp{27962}, then the member names will be:
8762 var/GNUFileParts.27962/longfile.1
8763 var/GNUFileParts.27962/longfile.2
8766 When you extract your archive using a third-party @command{tar}, these
8767 files will be created on your disk, and the only thing you will need
8768 to do to restore your file in its original form is concatenate them in
8769 the proper order, for example:
8774 $ @kbd{cat GNUFileParts.27962/longfile.1 \
8775 GNUFileParts.27962/longfile.2 >> longfile}
8776 $ rm -f GNUFileParts.27962
8780 Notice, that if the @command{tar} implementation you use supports PAX
8781 format archives, it will probably emit warnings about unknown keywords
8782 during extraction. They will look like this:
8787 Unknown extended header keyword 'GNU.volume.filename' ignored.
8788 Unknown extended header keyword 'GNU.volume.size' ignored.
8789 Unknown extended header keyword 'GNU.volume.offset' ignored.
8794 You can safely ignore these warnings.
8796 If your @command{tar} implementation is not PAX-aware, you will get
8797 more warnings and more files generated on your disk, e.g.:
8801 $ @kbd{tar xf vol-1.tar}
8802 var/PaxHeaders.27962/longfile: Unknown file type 'x', extracted as
8804 Unexpected EOF in archive
8805 $ @kbd{tar xf vol-2.tar}
8806 tmp/GlobalHead.27962.1: Unknown file type 'g', extracted as normal file
8807 GNUFileParts.27962/PaxHeaders.27962/sparsefile.1: Unknown file type
8808 'x', extracted as normal file
8812 Ignore these warnings. The @file{PaxHeaders.*} directories created
8813 will contain files with @dfn{extended header keywords} describing the
8814 extracted files. You can delete them, unless they describe sparse
8815 members. Read further to learn more about them.
8817 @node Sparse Recovery
8818 @subsubsection Extracting Sparse Members
8820 @cindex sparse files, extracting with non-GNU tars
8821 Any @command{tar} implementation will be able to extract sparse members from a
8822 PAX archive. However, the extracted files will be @dfn{condensed},
8823 i.e., any zero blocks will be removed from them. When we restore such
8824 a condensed file to its original form, by adding zero bloks (or
8825 @dfn{holes}) back to their original locations, we call this process
8826 @dfn{expanding} a compressed sparse file.
8829 To expand a file, you will need a simple auxiliary program called
8830 @command{xsparse}. It is available in source form from
8831 @uref{http://www.gnu.org/@/software/@/tar/@/utils/@/xsparse.html, @GNUTAR{}
8834 @cindex sparse files v.1.0, extracting with non-GNU tars
8835 Let's begin with archive members in @dfn{sparse format
8836 version 1.0}@footnote{@xref{PAX 1}.}, which are the easiest to expand.
8837 The condensed file will contain both file map and file data, so no
8838 additional data will be needed to restore it. If the original file
8839 name was @file{@var{dir}/@var{name}}, then the condensed file will be
8840 named @file{@var{dir}/@/GNUSparseFile.@var{n}/@/@var{name}}, where
8841 @var{n} is a decimal number@footnote{technically speaking, @var{n} is a
8842 @dfn{process ID} of the @command{tar} process which created the
8843 archive (@pxref{PAX keywords}).}.
8845 To expand a version 1.0 file, run @command{xsparse} as follows:
8848 $ @kbd{xsparse @file{cond-file}}
8852 where @file{cond-file} is the name of the condensed file. The utility
8853 will deduce the name for the resulting expanded file using the
8854 following algorithm:
8857 @item If @file{cond-file} does not contain any directories,
8858 @file{../cond-file} will be used;
8860 @item If @file{cond-file} has the form
8861 @file{@var{dir}/@var{t}/@var{name}}, where both @var{t} and @var{name}
8862 are simple names, with no @samp{/} characters in them, the output file
8863 name will be @file{@var{dir}/@var{name}}.
8865 @item Otherwise, if @file{cond-file} has the form
8866 @file{@var{dir}/@var{name}}, the output file name will be
8870 In the unlikely case when this algorithm does not suite your needs,
8871 you can explicitly specify output file name as a second argument to
8875 $ @kbd{xsparse @file{cond-file} @file{out-file}}
8878 It is often a good idea to run @command{xsparse} in @dfn{dry run} mode
8879 first. In this mode, the command does not actually expand the file,
8880 but verbosely lists all actions it would be taking to do so. The dry
8881 run mode is enabled by @option{-n} command line argument:
8885 $ @kbd{xsparse -n /home/gray/GNUSparseFile.6058/sparsefile}
8886 Reading v.1.0 sparse map
8887 Expanding file `/home/gray/GNUSparseFile.6058/sparsefile' to
8888 `/home/gray/sparsefile'
8893 To actually expand the file, you would run:
8896 $ @kbd{xsparse /home/gray/GNUSparseFile.6058/sparsefile}
8900 The program behaves the same way all UNIX utilities do: it will keep
8901 quiet unless it has simething important to tell you (e.g. an error
8902 condition or something). If you wish it to produce verbose output,
8903 similar to that from the dry run mode, use @option{-v} option:
8907 $ @kbd{xsparse -v /home/gray/GNUSparseFile.6058/sparsefile}
8908 Reading v.1.0 sparse map
8909 Expanding file `/home/gray/GNUSparseFile.6058/sparsefile' to
8910 `/home/gray/sparsefile'
8915 Additionally, if your @command{tar} implementation has extracted the
8916 @dfn{extended headers} for this file, you can instruct @command{xstar}
8917 to use them in order to verify the integrity of the expanded file.
8918 The option @option{-x} sets the name of the extended header file to
8919 use. Continuing our example:
8923 $ @kbd{xsparse -v -x /home/gray/PaxHeaders.6058/sparsefile \
8924 /home/gray/GNUSparseFile.6058/sparsefile}
8925 Reading extended header file
8926 Found variable GNU.sparse.major = 1
8927 Found variable GNU.sparse.minor = 0
8928 Found variable GNU.sparse.name = sparsefile
8929 Found variable GNU.sparse.realsize = 217481216
8930 Reading v.1.0 sparse map
8931 Expanding file `/home/gray/GNUSparseFile.6058/sparsefile' to
8932 `/home/gray/sparsefile'
8937 @anchor{extracting sparse v.0.x}
8938 @cindex sparse files v.0.1, extracting with non-GNU tars
8939 @cindex sparse files v.0.0, extracting with non-GNU tars
8940 An @dfn{extended header} is a special @command{tar} archive header
8941 that precedes an archive member and contains a set of
8942 @dfn{variables}, describing the member properties that cannot be
8943 stored in the standard @code{ustar} header. While optional for
8944 expanding sparse version 1.0 members, use of extended headers is
8945 mandatory when expanding sparse members in older sparse formats: v.0.0
8946 and v.0.1 (The sparse formats are described in detail in @ref{Sparse
8947 Formats}.) So, for this format, the question is: how to obtain
8948 extended headers from the archive?
8950 If you use a @command{tar} implementation that does not support PAX
8951 format, extended headers for each member will be extracted as a
8952 separate file. If we represent the member name as
8953 @file{@var{dir}/@var{name}}, then the extended header file will be
8954 named @file{@var{dir}/@/PaxHeaders.@var{n}/@/@var{name}}, where
8955 @var{n} is an integer number.
8957 Things become more difficult if your @command{tar} implementation
8958 does support PAX headers, because in this case you will have to
8959 manually extract the headers. We recommend the following algorithm:
8963 Consult the documentation of your @command{tar} implementation for an
8964 option that prints @dfn{block numbers} along with the archive
8965 listing (analogous to @GNUTAR{}'s @option{-R} option). For example,
8966 @command{star} has @option{-block-number}.
8969 Obtain verbose listing using the @samp{block number} option, and
8970 find block numbers of the sparse member in question and the member
8971 immediately following it. For example, running @command{star} on our
8976 $ @kbd{star -t -v -block-number -f arc.tar}
8978 star: Unknown extended header keyword 'GNU.sparse.size' ignored.
8979 star: Unknown extended header keyword 'GNU.sparse.numblocks' ignored.
8980 star: Unknown extended header keyword 'GNU.sparse.name' ignored.
8981 star: Unknown extended header keyword 'GNU.sparse.map' ignored.
8982 block 56: 425984 -rw-r--r-- gray/users Jun 25 14:46 2006 GNUSparseFile.28124/sparsefile
8983 block 897: 65391 -rw-r--r-- gray/users Jun 24 20:06 2006 README
8989 (as usual, ignore the warnings about unknown keywords.)
8992 Let @var{size} be the size of the sparse member, @var{Bs} be its block number
8993 and @var{Bn} be the block number of the next member.
8997 @var{N} = @var{Bs} - @var{Bn} - @var{size}/512 - 2
9001 This number gives the size of the extended header part in tar @dfn{blocks}.
9002 In our example, this formula gives: @code{897 - 56 - 425984 / 512 - 2
9006 Use @command{dd} to extract the headers:
9009 @kbd{dd if=@var{archive} of=@var{hname} bs=512 skip=@var{Bs} count=@var{N}}
9013 where @var{archive} is the archive name, @var{hname} is a name of the
9014 file to store the extended header in, @var{Bs} and @var{N} are
9015 computed in previous steps.
9017 In our example, this command will be
9020 $ @kbd{dd if=arc.tar of=xhdr bs=512 skip=56 count=7}
9024 Finally, you can expand the condensed file, using the obtained header:
9028 $ @kbd{xsparse -v -x xhdr GNUSparseFile.6058/sparsefile}
9029 Reading extended header file
9030 Found variable GNU.sparse.size = 217481216
9031 Found variable GNU.sparse.numblocks = 208
9032 Found variable GNU.sparse.name = sparsefile
9033 Found variable GNU.sparse.map = 0,2048,1050624,2048,@dots{}
9034 Expanding file `GNUSparseFile.28124/sparsefile' to `sparsefile'
9040 @section Comparison of @command{tar} and @command{cpio}
9043 @FIXME{Reorganize the following material}
9045 The @command{cpio} archive formats, like @command{tar}, do have maximum
9046 pathname lengths. The binary and old ASCII formats have a max path
9047 length of 256, and the new ASCII and CRC ASCII formats have a max
9048 path length of 1024. @acronym{GNU} @command{cpio} can read and write archives
9049 with arbitrary pathname lengths, but other @command{cpio} implementations
9050 may crash unexplainedly trying to read them.
9052 @command{tar} handles symbolic links in the form in which it comes in BSD;
9053 @command{cpio} doesn't handle symbolic links in the form in which it comes
9054 in System V prior to SVR4, and some vendors may have added symlinks
9055 to their system without enhancing @command{cpio} to know about them.
9056 Others may have enhanced it in a way other than the way I did it
9057 at Sun, and which was adopted by AT&T (and which is, I think, also
9058 present in the @command{cpio} that Berkeley picked up from AT&T and put
9059 into a later BSD release---I think I gave them my changes).
9061 (SVR4 does some funny stuff with @command{tar}; basically, its @command{cpio}
9062 can handle @command{tar} format input, and write it on output, and it
9063 probably handles symbolic links. They may not have bothered doing
9064 anything to enhance @command{tar} as a result.)
9066 @command{cpio} handles special files; traditional @command{tar} doesn't.
9068 @command{tar} comes with V7, System III, System V, and BSD source;
9069 @command{cpio} comes only with System III, System V, and later BSD
9070 (4.3-tahoe and later).
9072 @command{tar}'s way of handling multiple hard links to a file can handle
9073 file systems that support 32-bit inumbers (e.g., the BSD file system);
9074 @command{cpio}s way requires you to play some games (in its "binary"
9075 format, i-numbers are only 16 bits, and in its "portable ASCII" format,
9076 they're 18 bits---it would have to play games with the "file system ID"
9077 field of the header to make sure that the file system ID/i-number pairs
9078 of different files were always different), and I don't know which
9079 @command{cpio}s, if any, play those games. Those that don't might get
9080 confused and think two files are the same file when they're not, and
9081 make hard links between them.
9083 @command{tar}s way of handling multiple hard links to a file places only
9084 one copy of the link on the tape, but the name attached to that copy
9085 is the @emph{only} one you can use to retrieve the file; @command{cpio}s
9086 way puts one copy for every link, but you can retrieve it using any
9090 What type of check sum (if any) is used, and how is this calculated.
9093 See the attached manual pages for @command{tar} and @command{cpio} format.
9094 @command{tar} uses a checksum which is the sum of all the bytes in the
9095 @command{tar} header for a file; @command{cpio} uses no checksum.
9098 If anyone knows why @command{cpio} was made when @command{tar} was present
9102 It wasn't. @command{cpio} first showed up in PWB/UNIX 1.0; no
9103 generally-available version of UNIX had @command{tar} at the time. I don't
9104 know whether any version that was generally available @emph{within AT&T}
9105 had @command{tar}, or, if so, whether the people within AT&T who did
9106 @command{cpio} knew about it.
9108 On restore, if there is a corruption on a tape @command{tar} will stop at
9109 that point, while @command{cpio} will skip over it and try to restore the
9112 The main difference is just in the command syntax and header format.
9114 @command{tar} is a little more tape-oriented in that everything is blocked
9115 to start on a record boundary.
9118 Is there any differences between the ability to recover crashed
9119 archives between the two of them. (Is there any chance of recovering
9120 crashed archives at all.)
9123 Theoretically it should be easier under @command{tar} since the blocking
9124 lets you find a header with some variation of @samp{dd skip=@var{nn}}.
9125 However, modern @command{cpio}'s and variations have an option to just
9126 search for the next file header after an error with a reasonable chance
9127 of resyncing. However, lots of tape driver software won't allow you to
9128 continue past a media error which should be the only reason for getting
9129 out of sync unless a file changed sizes while you were writing the
9133 If anyone knows why @command{cpio} was made when @command{tar} was present
9134 at the unix scene, please tell me about this too.
9137 Probably because it is more media efficient (by not blocking everything
9138 and using only the space needed for the headers where @command{tar}
9139 always uses 512 bytes per file header) and it knows how to archive
9142 You might want to look at the freely available alternatives. The
9143 major ones are @command{afio}, @GNUTAR{}, and
9144 @command{pax}, each of which have their own extensions with some
9145 backwards compatibility.
9147 Sparse files were @command{tar}red as sparse files (which you can
9148 easily test, because the resulting archive gets smaller, and
9149 @acronym{GNU} @command{cpio} can no longer read it).
9152 @chapter Tapes and Other Archive Media
9155 A few special cases about tape handling warrant more detailed
9156 description. These special cases are discussed below.
9158 Many complexities surround the use of @command{tar} on tape drives. Since
9159 the creation and manipulation of archives located on magnetic tape was
9160 the original purpose of @command{tar}, it contains many features making
9161 such manipulation easier.
9163 Archives are usually written on dismountable media---tape cartridges,
9164 mag tapes, or floppy disks.
9166 The amount of data a tape or disk holds depends not only on its size,
9167 but also on how it is formatted. A 2400 foot long reel of mag tape
9168 holds 40 megabytes of data when formatted at 1600 bits per inch. The
9169 physically smaller EXABYTE tape cartridge holds 2.3 gigabytes.
9171 Magnetic media are re-usable---once the archive on a tape is no longer
9172 needed, the archive can be erased and the tape or disk used over.
9173 Media quality does deteriorate with use, however. Most tapes or disks
9174 should be discarded when they begin to produce data errors. EXABYTE
9175 tape cartridges should be discarded when they generate an @dfn{error
9176 count} (number of non-usable bits) of more than 10k.
9178 Magnetic media are written and erased using magnetic fields, and
9179 should be protected from such fields to avoid damage to stored data.
9180 Sticking a floppy disk to a filing cabinet using a magnet is probably
9184 * Device:: Device selection and switching
9185 * Remote Tape Server::
9186 * Common Problems and Solutions::
9187 * Blocking:: Blocking
9188 * Many:: Many archives on one tape
9189 * Using Multiple Tapes:: Using Multiple Tapes
9190 * label:: Including a Label in the Archive
9192 * Write Protection::
9196 @section Device Selection and Switching
9200 @item -f [@var{hostname}:]@var{file}
9201 @itemx --file=[@var{hostname}:]@var{file}
9202 Use archive file or device @var{file} on @var{hostname}.
9205 This option is used to specify the file name of the archive @command{tar}
9208 If the file name is @samp{-}, @command{tar} reads the archive from standard
9209 input (when listing or extracting), or writes it to standard output
9210 (when creating). If the @samp{-} file name is given when updating an
9211 archive, @command{tar} will read the original archive from its standard
9212 input, and will write the entire new archive to its standard output.
9214 If the file name contains a @samp{:}, it is interpreted as
9215 @samp{hostname:file name}. If the @var{hostname} contains an @dfn{at}
9216 sign (@samp{@@}), it is treated as @samp{user@@hostname:file name}. In
9217 either case, @command{tar} will invoke the command @command{rsh} (or
9218 @command{remsh}) to start up an @command{/usr/libexec/rmt} on the remote
9219 machine. If you give an alternate login name, it will be given to the
9221 Naturally, the remote machine must have an executable
9222 @command{/usr/libexec/rmt}. This program is free software from the
9223 University of California, and a copy of the source code can be found
9224 with the sources for @command{tar}; it's compiled and installed by default.
9225 The exact path to this utility is determined when configuring the package.
9226 It is @file{@var{prefix}/libexec/rmt}, where @var{prefix} stands for
9227 your installation prefix. This location may also be overridden at
9228 runtime by using @option{rmt-command=@var{command}} option (@xref{Option Summary,
9229 ---rmt-command}, for detailed description of this option. @xref{Remote
9230 Tape Server}, for the description of @command{rmt} command).
9232 If this option is not given, but the environment variable @env{TAPE}
9233 is set, its value is used; otherwise, old versions of @command{tar}
9234 used a default archive name (which was picked when @command{tar} was
9235 compiled). The default is normally set up to be the @dfn{first} tape
9236 drive or other transportable I/O medium on the system.
9238 Starting with version 1.11.5, @GNUTAR{} uses
9239 standard input and standard output as the default device, and I will
9240 not try anymore supporting automatic device detection at installation
9241 time. This was failing really in too many cases, it was hopeless.
9242 This is now completely left to the installer to override standard
9243 input and standard output for default device, if this seems
9244 preferable. Further, I think @emph{most} actual usages of
9245 @command{tar} are done with pipes or disks, not really tapes,
9246 cartridges or diskettes.
9248 Some users think that using standard input and output is running
9249 after trouble. This could lead to a nasty surprise on your screen if
9250 you forget to specify an output file name---especially if you are going
9251 through a network or terminal server capable of buffering large amounts
9252 of output. We had so many bug reports in that area of configuring
9253 default tapes automatically, and so many contradicting requests, that
9254 we finally consider the problem to be portably intractable. We could
9255 of course use something like @samp{/dev/tape} as a default, but this
9256 is @emph{also} running after various kind of trouble, going from hung
9257 processes to accidental destruction of real tapes. After having seen
9258 all this mess, using standard input and output as a default really
9259 sounds like the only clean choice left, and a very useful one too.
9261 @GNUTAR{} reads and writes archive in records, I
9262 suspect this is the main reason why block devices are preferred over
9263 character devices. Most probably, block devices are more efficient
9264 too. The installer could also check for @samp{DEFTAPE} in
9265 @file{<sys/mtio.h>}.
9268 @xopindex{force-local, short description}
9270 Archive file is local even if it contains a colon.
9272 @opindex rsh-command
9273 @item --rsh-command=@var{command}
9274 Use remote @var{command} instead of @command{rsh}. This option exists
9275 so that people who use something other than the standard @command{rsh}
9276 (e.g., a Kerberized @command{rsh}) can access a remote device.
9278 When this command is not used, the shell command found when
9279 the @command{tar} program was installed is used instead. This is
9280 the first found of @file{/usr/ucb/rsh}, @file{/usr/bin/remsh},
9281 @file{/usr/bin/rsh}, @file{/usr/bsd/rsh} or @file{/usr/bin/nsh}.
9282 The installer may have overridden this by defining the environment
9283 variable @env{RSH} @emph{at installation time}.
9286 Specify drive and density.
9288 @xopindex{multi-volume, short description}
9290 @itemx --multi-volume
9291 Create/list/extract multi-volume archive.
9293 This option causes @command{tar} to write a @dfn{multi-volume} archive---one
9294 that may be larger than will fit on the medium used to hold it.
9295 @xref{Multi-Volume Archives}.
9297 @xopindex{tape-length, short description}
9299 @itemx --tape-length=@var{num}
9300 Change tape after writing @var{num} x 1024 bytes.
9302 This option might be useful when your tape drivers do not properly
9303 detect end of physical tapes. By being slightly conservative on the
9304 maximum tape length, you might avoid the problem entirely.
9306 @xopindex{info-script, short description}
9307 @xopindex{new-volume-script, short description}
9309 @itemx --info-script=@var{file}
9310 @itemx --new-volume-script=@var{file}
9311 Execute @file{file} at end of each tape. This implies
9312 @option{--multi-volume} (@option{-M}). @xref{info-script}, for a detailed
9313 description of this option.
9316 @node Remote Tape Server
9317 @section The Remote Tape Server
9319 @cindex remote tape drive
9321 In order to access the tape drive on a remote machine, @command{tar}
9322 uses the remote tape server written at the University of California at
9323 Berkeley. The remote tape server must be installed as
9324 @file{@var{prefix}/libexec/rmt} on any machine whose tape drive you
9325 want to use. @command{tar} calls @command{rmt} by running an
9326 @command{rsh} or @command{remsh} to the remote machine, optionally
9327 using a different login name if one is supplied.
9329 A copy of the source for the remote tape server is provided. It is
9330 Copyright @copyright{} 1983 by the Regents of the University of
9331 California, but can be freely distributed. It is compiled and
9332 installed by default.
9334 @cindex absolute file names
9335 Unless you use the @option{--absolute-names} (@option{-P}) option,
9336 @GNUTAR{} will not allow you to create an archive that contains
9337 absolute file names (a file name beginning with @samp{/}.) If you try,
9338 @command{tar} will automatically remove the leading @samp{/} from the
9339 file names it stores in the archive. It will also type a warning
9340 message telling you what it is doing.
9342 When reading an archive that was created with a different
9343 @command{tar} program, @GNUTAR{} automatically
9344 extracts entries in the archive which have absolute file names as if
9345 the file names were not absolute. This is an important feature. A
9346 visitor here once gave a @command{tar} tape to an operator to restore;
9347 the operator used Sun @command{tar} instead of @GNUTAR{},
9348 and the result was that it replaced large portions of
9349 our @file{/bin} and friends with versions from the tape; needless to
9350 say, we were unhappy about having to recover the file system from
9353 For example, if the archive contained a file @file{/usr/bin/computoy},
9354 @GNUTAR{} would extract the file to @file{usr/bin/computoy},
9355 relative to the current directory. If you want to extract the files in
9356 an archive to the same absolute names that they had when the archive
9357 was created, you should do a @samp{cd /} before extracting the files
9358 from the archive, or you should either use the @option{--absolute-names}
9359 option, or use the command @samp{tar -C / @dots{}}.
9361 @cindex Ultrix 3.1 and write failure
9362 Some versions of Unix (Ultrix 3.1 is known to have this problem),
9363 can claim that a short write near the end of a tape succeeded,
9364 when it actually failed. This will result in the -M option not
9365 working correctly. The best workaround at the moment is to use a
9366 significantly larger blocking factor than the default 20.
9368 In order to update an archive, @command{tar} must be able to backspace the
9369 archive in order to reread or rewrite a record that was just read (or
9370 written). This is currently possible only on two kinds of files: normal
9371 disk files (or any other file that can be backspaced with @samp{lseek}),
9372 and industry-standard 9-track magnetic tape (or any other kind of tape
9373 that can be backspaced with the @code{MTIOCTOP} @code{ioctl}.
9375 This means that the @option{--append}, @option{--concatenate}, and
9376 @option{--delete} commands will not work on any other kind of file.
9377 Some media simply cannot be backspaced, which means these commands and
9378 options will never be able to work on them. These non-backspacing
9379 media include pipes and cartridge tape drives.
9381 Some other media can be backspaced, and @command{tar} will work on them
9382 once @command{tar} is modified to do so.
9384 Archives created with the @option{--multi-volume}, @option{--label}, and
9385 @option{--incremental} (@option{-G}) options may not be readable by other version
9386 of @command{tar}. In particular, restoring a file that was split over
9387 a volume boundary will require some careful work with @command{dd}, if
9388 it can be done at all. Other versions of @command{tar} may also create
9389 an empty file whose name is that of the volume header. Some versions
9390 of @command{tar} may create normal files instead of directories archived
9391 with the @option{--incremental} (@option{-G}) option.
9393 @node Common Problems and Solutions
9394 @section Some Common Problems and their Solutions
9401 no such file or directory
9404 errors from @command{tar}:
9405 directory checksum error
9408 errors from media/system:
9419 @dfn{Block} and @dfn{record} terminology is rather confused, and it
9420 is also confusing to the expert reader. On the other hand, readers
9421 who are new to the field have a fresh mind, and they may safely skip
9422 the next two paragraphs, as the remainder of this manual uses those
9423 two terms in a quite consistent way.
9425 John Gilmore, the writer of the public domain @command{tar} from which
9426 @GNUTAR{} was originally derived, wrote (June 1995):
9429 The nomenclature of tape drives comes from IBM, where I believe
9430 they were invented for the IBM 650 or so. On IBM mainframes, what
9431 is recorded on tape are tape blocks. The logical organization of
9432 data is into records. There are various ways of putting records into
9433 blocks, including @code{F} (fixed sized records), @code{V} (variable
9434 sized records), @code{FB} (fixed blocked: fixed size records, @var{n}
9435 to a block), @code{VB} (variable size records, @var{n} to a block),
9436 @code{VSB} (variable spanned blocked: variable sized records that can
9437 occupy more than one block), etc. The @code{JCL} @samp{DD RECFORM=}
9438 parameter specified this to the operating system.
9440 The Unix man page on @command{tar} was totally confused about this.
9441 When I wrote @code{PD TAR}, I used the historically correct terminology
9442 (@command{tar} writes data records, which are grouped into blocks).
9443 It appears that the bogus terminology made it into @acronym{POSIX} (no surprise
9444 here), and now Fran@,{c}ois has migrated that terminology back
9445 into the source code too.
9448 The term @dfn{physical block} means the basic transfer chunk from or
9449 to a device, after which reading or writing may stop without anything
9450 being lost. In this manual, the term @dfn{block} usually refers to
9451 a disk physical block, @emph{assuming} that each disk block is 512
9452 bytes in length. It is true that some disk devices have different
9453 physical blocks, but @command{tar} ignore these differences in its own
9454 format, which is meant to be portable, so a @command{tar} block is always
9455 512 bytes in length, and @dfn{block} always mean a @command{tar} block.
9456 The term @dfn{logical block} often represents the basic chunk of
9457 allocation of many disk blocks as a single entity, which the operating
9458 system treats somewhat atomically; this concept is only barely used
9461 The term @dfn{physical record} is another way to speak of a physical
9462 block, those two terms are somewhat interchangeable. In this manual,
9463 the term @dfn{record} usually refers to a tape physical block,
9464 @emph{assuming} that the @command{tar} archive is kept on magnetic tape.
9465 It is true that archives may be put on disk or used with pipes,
9466 but nevertheless, @command{tar} tries to read and write the archive one
9467 @dfn{record} at a time, whatever the medium in use. One record is made
9468 up of an integral number of blocks, and this operation of putting many
9469 disk blocks into a single tape block is called @dfn{reblocking}, or
9470 more simply, @dfn{blocking}. The term @dfn{logical record} refers to
9471 the logical organization of many characters into something meaningful
9472 to the application. The term @dfn{unit record} describes a small set
9473 of characters which are transmitted whole to or by the application,
9474 and often refers to a line of text. Those two last terms are unrelated
9475 to what we call a @dfn{record} in @GNUTAR{}.
9477 When writing to tapes, @command{tar} writes the contents of the archive
9478 in chunks known as @dfn{records}. To change the default blocking
9479 factor, use the @option{--blocking-factor=@var{512-size}} (@option{-b
9480 @var{512-size}}) option. Each record will then be composed of
9481 @var{512-size} blocks. (Each @command{tar} block is 512 bytes.
9482 @xref{Standard}.) Each file written to the archive uses at least one
9483 full record. As a result, using a larger record size can result in
9484 more wasted space for small files. On the other hand, a larger record
9485 size can often be read and written much more efficiently.
9487 Further complicating the problem is that some tape drives ignore the
9488 blocking entirely. For these, a larger record size can still improve
9489 performance (because the software layers above the tape drive still
9490 honor the blocking), but not as dramatically as on tape drives that
9493 When reading an archive, @command{tar} can usually figure out the
9494 record size on itself. When this is the case, and a non-standard
9495 record size was used when the archive was created, @command{tar} will
9496 print a message about a non-standard blocking factor, and then operate
9497 normally. On some tape devices, however, @command{tar} cannot figure
9498 out the record size itself. On most of those, you can specify a
9499 blocking factor (with @option{--blocking-factor}) larger than the
9500 actual blocking factor, and then use the @option{--read-full-records}
9501 (@option{-B}) option. (If you specify a blocking factor with
9502 @option{--blocking-factor} and don't use the
9503 @option{--read-full-records} option, then @command{tar} will not
9504 attempt to figure out the recording size itself.) On some devices,
9505 you must always specify the record size exactly with
9506 @option{--blocking-factor} when reading, because @command{tar} cannot
9507 figure it out. In any case, use @option{--list} (@option{-t}) before
9508 doing any extractions to see whether @command{tar} is reading the archive
9511 @command{tar} blocks are all fixed size (512 bytes), and its scheme for
9512 putting them into records is to put a whole number of them (one or
9513 more) into each record. @command{tar} records are all the same size;
9514 at the end of the file there's a block containing all zeros, which
9515 is how you tell that the remainder of the last record(s) are garbage.
9517 In a standard @command{tar} file (no options), the block size is 512
9518 and the record size is 10240, for a blocking factor of 20. What the
9519 @option{--blocking-factor} option does is sets the blocking factor,
9520 changing the record size while leaving the block size at 512 bytes.
9521 20 was fine for ancient 800 or 1600 bpi reel-to-reel tape drives;
9522 most tape drives these days prefer much bigger records in order to
9523 stream and not waste tape. When writing tapes for myself, some tend
9524 to use a factor of the order of 2048, say, giving a record size of
9525 around one megabyte.
9527 If you use a blocking factor larger than 20, older @command{tar}
9528 programs might not be able to read the archive, so we recommend this
9529 as a limit to use in practice. @GNUTAR{}, however,
9530 will support arbitrarily large record sizes, limited only by the
9531 amount of virtual memory or the physical characteristics of the tape
9535 * Format Variations:: Format Variations
9536 * Blocking Factor:: The Blocking Factor of an Archive
9539 @node Format Variations
9540 @subsection Format Variations
9541 @cindex Format Parameters
9542 @cindex Format Options
9543 @cindex Options, archive format specifying
9544 @cindex Options, format specifying
9547 Format parameters specify how an archive is written on the archive
9548 media. The best choice of format parameters will vary depending on
9549 the type and number of files being archived, and on the media used to
9552 To specify format parameters when accessing or creating an archive,
9553 you can use the options described in the following sections.
9554 If you do not specify any format parameters, @command{tar} uses
9555 default parameters. You cannot modify a compressed archive.
9556 If you create an archive with the @option{--blocking-factor} option
9557 specified (@pxref{Blocking Factor}), you must specify that
9558 blocking-factor when operating on the archive. @xref{Formats}, for other
9559 examples of format parameter considerations.
9561 @node Blocking Factor
9562 @subsection The Blocking Factor of an Archive
9563 @cindex Blocking Factor
9565 @cindex Number of blocks per record
9566 @cindex Number of bytes per record
9567 @cindex Bytes per record
9568 @cindex Blocks per record
9571 @opindex blocking-factor
9572 The data in an archive is grouped into blocks, which are 512 bytes.
9573 Blocks are read and written in whole number multiples called
9574 @dfn{records}. The number of blocks in a record (i.e., the size of a
9575 record in units of 512 bytes) is called the @dfn{blocking factor}.
9576 The @option{--blocking-factor=@var{512-size}} (@option{-b
9577 @var{512-size}}) option specifies the blocking factor of an archive.
9578 The default blocking factor is typically 20 (i.e., 10240 bytes), but
9579 can be specified at installation. To find out the blocking factor of
9580 an existing archive, use @samp{tar --list --file=@var{archive-name}}.
9581 This may not work on some devices.
9583 Records are separated by gaps, which waste space on the archive media.
9584 If you are archiving on magnetic tape, using a larger blocking factor
9585 (and therefore larger records) provides faster throughput and allows you
9586 to fit more data on a tape (because there are fewer gaps). If you are
9587 archiving on cartridge, a very large blocking factor (say 126 or more)
9588 greatly increases performance. A smaller blocking factor, on the other
9589 hand, may be useful when archiving small files, to avoid archiving lots
9590 of nulls as @command{tar} fills out the archive to the end of the record.
9591 In general, the ideal record size depends on the size of the
9592 inter-record gaps on the tape you are using, and the average size of the
9593 files you are archiving. @xref{create}, for information on
9596 @FIXME{Need example of using a cartridge with blocking factor=126 or more.}
9598 Archives with blocking factors larger than 20 cannot be read
9599 by very old versions of @command{tar}, or by some newer versions
9600 of @command{tar} running on old machines with small address spaces.
9601 With @GNUTAR{}, the blocking factor of an archive is limited
9602 only by the maximum record size of the device containing the archive,
9603 or by the amount of available virtual memory.
9605 Also, on some systems, not using adequate blocking factors, as sometimes
9606 imposed by the device drivers, may yield unexpected diagnostics. For
9607 example, this has been reported:
9610 Cannot write to /dev/dlt: Invalid argument
9614 In such cases, it sometimes happen that the @command{tar} bundled by
9615 the system is aware of block size idiosyncrasies, while @GNUTAR{}
9616 requires an explicit specification for the block size,
9617 which it cannot guess. This yields some people to consider
9618 @GNUTAR{} is misbehaving, because by comparison,
9619 @cite{the bundle @command{tar} works OK}. Adding @w{@kbd{-b 256}},
9620 for example, might resolve the problem.
9622 If you use a non-default blocking factor when you create an archive, you
9623 must specify the same blocking factor when you modify that archive. Some
9624 archive devices will also require you to specify the blocking factor when
9625 reading that archive, however this is not typically the case. Usually, you
9626 can use @option{--list} (@option{-t}) without specifying a blocking factor---@command{tar}
9627 reports a non-default record size and then lists the archive members as
9628 it would normally. To extract files from an archive with a non-standard
9629 blocking factor (particularly if you're not sure what the blocking factor
9630 is), you can usually use the @option{--read-full-records} (@option{-B}) option while
9631 specifying a blocking factor larger then the blocking factor of the archive
9632 (i.e., @samp{tar --extract --read-full-records --blocking-factor=300}.
9633 @xref{list}, for more information on the @option{--list} (@option{-t})
9634 operation. @xref{Reading}, for a more detailed explanation of that option.
9637 @item --blocking-factor=@var{number}
9638 @itemx -b @var{number}
9639 Specifies the blocking factor of an archive. Can be used with any
9640 operation, but is usually not necessary with @option{--list} (@option{-t}).
9646 @item -b @var{blocks}
9647 @itemx --blocking-factor=@var{blocks}
9648 Set record size to @math{@var{blocks} * 512} bytes.
9650 This option is used to specify a @dfn{blocking factor} for the archive.
9651 When reading or writing the archive, @command{tar}, will do reads and writes
9652 of the archive in records of @math{@var{block}*512} bytes. This is true
9653 even when the archive is compressed. Some devices requires that all
9654 write operations be a multiple of a certain size, and so, @command{tar}
9655 pads the archive out to the next record boundary.
9657 The default blocking factor is set when @command{tar} is compiled, and is
9658 typically 20. Blocking factors larger than 20 cannot be read by very
9659 old versions of @command{tar}, or by some newer versions of @command{tar}
9660 running on old machines with small address spaces.
9662 With a magnetic tape, larger records give faster throughput and fit
9663 more data on a tape (because there are fewer inter-record gaps).
9664 If the archive is in a disk file or a pipe, you may want to specify
9665 a smaller blocking factor, since a large one will result in a large
9666 number of null bytes at the end of the archive.
9668 When writing cartridge or other streaming tapes, a much larger
9669 blocking factor (say 126 or more) will greatly increase performance.
9670 However, you must specify the same blocking factor when reading or
9671 updating the archive.
9673 Apparently, Exabyte drives have a physical block size of 8K bytes.
9674 If we choose our blocksize as a multiple of 8k bytes, then the problem
9675 seems to disappear. Id est, we are using block size of 112 right
9676 now, and we haven't had the problem since we switched@dots{}
9678 With @GNUTAR{} the blocking factor is limited only
9679 by the maximum record size of the device containing the archive, or by
9680 the amount of available virtual memory.
9682 However, deblocking or reblocking is virtually avoided in a special
9683 case which often occurs in practice, but which requires all the
9684 following conditions to be simultaneously true:
9687 the archive is subject to a compression option,
9689 the archive is not handled through standard input or output, nor
9690 redirected nor piped,
9692 the archive is directly handled to a local disk, instead of any special
9695 @option{--blocking-factor} is not explicitly specified on the @command{tar}
9699 If the output goes directly to a local disk, and not through
9700 stdout, then the last write is not extended to a full record size.
9701 Otherwise, reblocking occurs. Here are a few other remarks on this
9707 @command{gzip} will complain about trailing garbage if asked to
9708 uncompress a compressed archive on tape, there is an option to turn
9709 the message off, but it breaks the regularity of simply having to use
9710 @samp{@var{prog} -d} for decompression. It would be nice if gzip was
9711 silently ignoring any number of trailing zeros. I'll ask Jean-loup
9712 Gailly, by sending a copy of this message to him.
9715 @command{compress} does not show this problem, but as Jean-loup pointed
9716 out to Michael, @samp{compress -d} silently adds garbage after
9717 the result of decompression, which tar ignores because it already
9718 recognized its end-of-file indicator. So this bug may be safely
9722 @samp{gzip -d -q} will be silent about the trailing zeros indeed,
9723 but will still return an exit status of 2 which tar reports in turn.
9724 @command{tar} might ignore the exit status returned, but I hate doing
9725 that, as it weakens the protection @command{tar} offers users against
9726 other possible problems at decompression time. If @command{gzip} was
9727 silently skipping trailing zeros @emph{and} also avoiding setting the
9728 exit status in this innocuous case, that would solve this situation.
9731 @command{tar} should become more solid at not stopping to read a pipe at
9732 the first null block encountered. This inelegantly breaks the pipe.
9733 @command{tar} should rather drain the pipe out before exiting itself.
9736 @xopindex{ignore-zeros, short description}
9738 @itemx --ignore-zeros
9739 Ignore blocks of zeros in archive (means EOF).
9741 The @option{--ignore-zeros} (@option{-i}) option causes @command{tar} to ignore blocks
9742 of zeros in the archive. Normally a block of zeros indicates the
9743 end of the archive, but when reading a damaged archive, or one which
9744 was created by concatenating several archives together, this option
9745 allows @command{tar} to read the entire archive. This option is not on
9746 by default because many versions of @command{tar} write garbage after
9749 Note that this option causes @command{tar} to read to the end of the
9750 archive file, which may sometimes avoid problems when multiple files
9751 are stored on a single physical tape.
9753 @xopindex{read-full-records, short description}
9755 @itemx --read-full-records
9756 Reblock as we read (for reading 4.2BSD pipes).
9758 If @option{--read-full-records} is used, @command{tar}
9759 will not panic if an attempt to read a record from the archive does
9760 not return a full record. Instead, @command{tar} will keep reading
9761 until it has obtained a full
9764 This option is turned on by default when @command{tar} is reading
9765 an archive from standard input, or from a remote machine. This is
9766 because on BSD Unix systems, a read of a pipe will return however
9767 much happens to be in the pipe, even if it is less than @command{tar}
9768 requested. If this option was not used, @command{tar} would fail as
9769 soon as it read an incomplete record from the pipe.
9771 This option is also useful with the commands for updating an archive.
9777 @FIXME{Appropriate options should be moved here from elsewhere.}
9779 @cindex blocking factor
9780 @cindex tape blocking
9782 When handling various tapes or cartridges, you have to take care of
9783 selecting a proper blocking, that is, the number of disk blocks you
9784 put together as a single tape block on the tape, without intervening
9785 tape gaps. A @dfn{tape gap} is a small landing area on the tape
9786 with no information on it, used for decelerating the tape to a
9787 full stop, and for later regaining the reading or writing speed.
9788 When the tape driver starts reading a record, the record has to
9789 be read whole without stopping, as a tape gap is needed to stop the
9790 tape motion without loosing information.
9792 @cindex Exabyte blocking
9793 @cindex DAT blocking
9794 Using higher blocking (putting more disk blocks per tape block) will use
9795 the tape more efficiently as there will be less tape gaps. But reading
9796 such tapes may be more difficult for the system, as more memory will be
9797 required to receive at once the whole record. Further, if there is a
9798 reading error on a huge record, this is less likely that the system will
9799 succeed in recovering the information. So, blocking should not be too
9800 low, nor it should be too high. @command{tar} uses by default a blocking of
9801 20 for historical reasons, and it does not really matter when reading or
9802 writing to disk. Current tape technology would easily accommodate higher
9803 blockings. Sun recommends a blocking of 126 for Exabytes and 96 for DATs.
9804 We were told that for some DLT drives, the blocking should be a multiple
9805 of 4Kb, preferably 64Kb (@w{@kbd{-b 128}}) or 256 for decent performance.
9806 Other manufacturers may use different recommendations for the same tapes.
9807 This might also depends of the buffering techniques used inside modern
9808 tape controllers. Some imposes a minimum blocking, or a maximum blocking.
9809 Others request blocking to be some exponent of two.
9811 So, there is no fixed rule for blocking. But blocking at read time
9812 should ideally be the same as blocking used at write time. At one place
9813 I know, with a wide variety of equipment, they found it best to use a
9814 blocking of 32 to guarantee that their tapes are fully interchangeable.
9816 I was also told that, for recycled tapes, prior erasure (by the same
9817 drive unit that will be used to create the archives) sometimes lowers
9818 the error rates observed at rewriting time.
9820 I might also use @option{--number-blocks} instead of
9821 @option{--block-number}, so @option{--block} will then expand to
9822 @option{--blocking-factor} unambiguously.
9825 @section Many Archives on One Tape
9827 @FIXME{Appropriate options should be moved here from elsewhere.}
9829 @findex ntape @r{device}
9830 Most tape devices have two entries in the @file{/dev} directory, or
9831 entries that come in pairs, which differ only in the minor number for
9832 this device. Let's take for example @file{/dev/tape}, which often
9833 points to the only or usual tape device of a given system. There might
9834 be a corresponding @file{/dev/nrtape} or @file{/dev/ntape}. The simpler
9835 name is the @emph{rewinding} version of the device, while the name
9836 having @samp{nr} in it is the @emph{no rewinding} version of the same
9839 A rewinding tape device will bring back the tape to its beginning point
9840 automatically when this device is opened or closed. Since @command{tar}
9841 opens the archive file before using it and closes it afterwards, this
9842 means that a simple:
9845 $ @kbd{tar cf /dev/tape @var{directory}}
9849 will reposition the tape to its beginning both prior and after saving
9850 @var{directory} contents to it, thus erasing prior tape contents and
9851 making it so that any subsequent write operation will destroy what has
9854 @cindex tape positioning
9855 So, a rewinding device is normally meant to hold one and only one file.
9856 If you want to put more than one @command{tar} archive on a given tape, you
9857 will need to avoid using the rewinding version of the tape device. You
9858 will also have to pay special attention to tape positioning. Errors in
9859 positioning may overwrite the valuable data already on your tape. Many
9860 people, burnt by past experiences, will only use rewinding devices and
9861 limit themselves to one file per tape, precisely to avoid the risk of
9862 such errors. Be fully aware that writing at the wrong position on a
9863 tape loses all information past this point and most probably until the
9864 end of the tape, and this destroyed information @emph{cannot} be
9867 To save @var{directory-1} as a first archive at the beginning of a
9868 tape, and leave that tape ready for a second archive, you should use:
9871 $ @kbd{mt -f /dev/nrtape rewind}
9872 $ @kbd{tar cf /dev/nrtape @var{directory-1}}
9876 @dfn{Tape marks} are special magnetic patterns written on the tape
9877 media, which are later recognizable by the reading hardware. These
9878 marks are used after each file, when there are many on a single tape.
9879 An empty file (that is to say, two tape marks in a row) signal the
9880 logical end of the tape, after which no file exist. Usually,
9881 non-rewinding tape device drivers will react to the close request issued
9882 by @command{tar} by first writing two tape marks after your archive, and by
9883 backspacing over one of these. So, if you remove the tape at that time
9884 from the tape drive, it is properly terminated. But if you write
9885 another file at the current position, the second tape mark will be
9886 erased by the new information, leaving only one tape mark between files.
9888 So, you may now save @var{directory-2} as a second archive after the
9889 first on the same tape by issuing the command:
9892 $ @kbd{tar cf /dev/nrtape @var{directory-2}}
9896 and so on for all the archives you want to put on the same tape.
9898 Another usual case is that you do not write all the archives the same
9899 day, and you need to remove and store the tape between two archive
9900 sessions. In general, you must remember how many files are already
9901 saved on your tape. Suppose your tape already has 16 files on it, and
9902 that you are ready to write the 17th. You have to take care of skipping
9903 the first 16 tape marks before saving @var{directory-17}, say, by using
9907 $ @kbd{mt -f /dev/nrtape rewind}
9908 $ @kbd{mt -f /dev/nrtape fsf 16}
9909 $ @kbd{tar cf /dev/nrtape @var{directory-17}}
9912 In all the previous examples, we put aside blocking considerations, but
9913 you should do the proper things for that as well. @xref{Blocking}.
9916 * Tape Positioning:: Tape Positions and Tape Marks
9917 * mt:: The @command{mt} Utility
9920 @node Tape Positioning
9921 @subsection Tape Positions and Tape Marks
9924 Just as archives can store more than one file from the file system,
9925 tapes can store more than one archive file. To keep track of where
9926 archive files (or any other type of file stored on tape) begin and
9927 end, tape archive devices write magnetic @dfn{tape marks} on the
9928 archive media. Tape drives write one tape mark between files,
9929 two at the end of all the file entries.
9931 If you think of data as a series of records "rrrr"'s, and tape marks as
9932 "*"'s, a tape might look like the following:
9935 rrrr*rrrrrr*rrrrr*rr*rrrrr**-------------------------
9938 Tape devices read and write tapes using a read/write @dfn{tape
9939 head}---a physical part of the device which can only access one
9940 point on the tape at a time. When you use @command{tar} to read or
9941 write archive data from a tape device, the device will begin reading
9942 or writing from wherever on the tape the tape head happens to be,
9943 regardless of which archive or what part of the archive the tape
9944 head is on. Before writing an archive, you should make sure that no
9945 data on the tape will be overwritten (unless it is no longer needed).
9946 Before reading an archive, you should make sure the tape head is at
9947 the beginning of the archive you want to read. You can do it manually
9948 via @code{mt} utility (@pxref{mt}). The @code{restore} script does
9949 that automatically (@pxref{Scripted Restoration}).
9951 If you want to add new archive file entries to a tape, you should
9952 advance the tape to the end of the existing file entries, backspace
9953 over the last tape mark, and write the new archive file. If you were
9954 to add two archives to the example above, the tape might look like the
9958 rrrr*rrrrrr*rrrrr*rr*rrrrr*rrr*rrrr**----------------
9962 @subsection The @command{mt} Utility
9965 @FIXME{Is it true that this only works on non-block devices?
9966 should explain the difference, (fixed or variable).}
9967 @xref{Blocking Factor}.
9969 You can use the @command{mt} utility to advance or rewind a tape past a
9970 specified number of archive files on the tape. This will allow you
9971 to move to the beginning of an archive before extracting or reading
9972 it, or to the end of all the archives before writing a new one.
9973 @FIXME{Why isn't there an "advance 'til you find two tape marks
9976 The syntax of the @command{mt} command is:
9979 @kbd{mt [-f @var{tapename}] @var{operation} [@var{number}]}
9982 where @var{tapename} is the name of the tape device, @var{number} is
9983 the number of times an operation is performed (with a default of one),
9984 and @var{operation} is one of the following:
9986 @FIXME{is there any use for record operations?}
9991 Writes @var{number} tape marks at the current position on the tape.
9994 Moves tape position forward @var{number} files.
9997 Moves tape position back @var{number} files.
10000 Rewinds the tape. (Ignores @var{number}).
10004 Rewinds the tape and takes the tape device off-line. (Ignores @var{number}).
10007 Prints status information about the tape unit.
10011 @FIXME{Is there a better way to frob the spacing on the list?}
10013 If you don't specify a @var{tapename}, @command{mt} uses the environment
10014 variable @env{TAPE}; if @env{TAPE} is not set, @command{mt} will use
10015 the default device specified in your @file{sys/mtio.h} file
10016 (@code{DEFTAPE} variable). If this is not defined, the program will
10017 display a descriptive error message and exit with code 1.
10019 @command{mt} returns a 0 exit status when the operation(s) were
10020 successful, 1 if the command was unrecognized, and 2 if an operation
10023 @node Using Multiple Tapes
10024 @section Using Multiple Tapes
10026 Often you might want to write a large archive, one larger than will fit
10027 on the actual tape you are using. In such a case, you can run multiple
10028 @command{tar} commands, but this can be inconvenient, particularly if you
10029 are using options like @option{--exclude=@var{pattern}} or dumping entire file systems.
10030 Therefore, @command{tar} provides a special mode for creating
10031 multi-volume archives.
10033 @dfn{Multi-volume} archive is a single @command{tar} archive, stored
10034 on several media volumes of fixed size. Although in this section we will
10035 often call @samp{volume} a @dfn{tape}, there is absolutely no
10036 requirement for multi-volume archives to be stored on tapes. Instead,
10037 they can use whatever media type the user finds convenient, they can
10038 even be located on files.
10040 When creating a multi-volume archive, @GNUTAR{} continues to fill
10041 current volume until it runs out of space, then it switches to
10042 next volume (usually the operator is queried to replace the tape on
10043 this point), and continues working on the new volume. This operation
10044 continues until all requested files are dumped. If @GNUTAR{} detects
10045 end of media while dumping a file, such a file is archived in split
10046 form. Some very big files can even be split across several volumes.
10048 Each volume is itself a valid @GNUTAR{} archive, so it can be read
10049 without any special options. Consequently any file member residing
10050 entirely on one volume can be extracted or otherwise operated upon
10051 without needing the other volume. Sure enough, to extract a split
10052 member you would need all volumes its parts reside on.
10054 Multi-volume archives suffer from several limitations. In particular,
10055 they cannot be compressed.
10057 @GNUTAR{} is able to create multi-volume archives of two formats
10058 (@pxref{Formats}): @samp{GNU} and @samp{POSIX}.
10061 * Multi-Volume Archives:: Archives Longer than One Tape or Disk
10062 * Tape Files:: Tape Files
10063 * Tarcat:: Concatenate Volumes into a Single Archive
10067 @node Multi-Volume Archives
10068 @subsection Archives Longer than One Tape or Disk
10069 @cindex Multi-volume archives
10071 @opindex multi-volume
10072 To create an archive that is larger than will fit on a single unit of
10073 the media, use the @option{--multi-volume} (@option{-M}) option in conjunction with
10074 the @option{--create} option (@pxref{create}). A @dfn{multi-volume}
10075 archive can be manipulated like any other archive (provided the
10076 @option{--multi-volume} option is specified), but is stored on more
10077 than one tape or disk.
10079 When you specify @option{--multi-volume}, @command{tar} does not report an
10080 error when it comes to the end of an archive volume (when reading), or
10081 the end of the media (when writing). Instead, it prompts you to load
10082 a new storage volume. If the archive is on a magnetic tape, you
10083 should change tapes when you see the prompt; if the archive is on a
10084 floppy disk, you should change disks; etc.
10087 @item --multi-volume
10089 Creates a multi-volume archive, when used in conjunction with
10090 @option{--create} (@option{-c}). To perform any other operation on a multi-volume
10091 archive, specify @option{--multi-volume} in conjunction with that
10096 $ @kbd{tar --create --multi-volume --file=/dev/tape @var{files}}
10100 The method @command{tar} uses to detect end of tape is not perfect, and
10101 fails on some operating systems or on some devices. If @command{tar}
10102 cannot detect the end of the tape itself, you can use
10103 @option{--tape-length} option to inform it about the capacity of the
10106 @anchor{tape-length}
10108 @opindex tape-length
10109 @item --tape-length=@var{size}
10110 @itemx -L @var{size}
10111 Set maximum length of a volume. The @var{size} argument should then
10112 be the usable size of the tape in units of 1024 bytes. This option
10113 selects @option{--multi-volume} automatically. For example:
10116 $ @kbd{tar --create --tape-length=41943040 --file=/dev/tape @var{files}}
10120 @anchor{change volume prompt}
10121 When @GNUTAR{} comes to the end of a storage media, it asks you to
10122 change the volume. The built-in prompt for POSIX locale
10123 is@footnote{If you run @GNUTAR{} under a different locale, the
10124 translation to the locale's language will be used.}:
10127 Prepare volume #@var{n} for `@var{archive}' and hit return:
10131 where @var{n} is the ordinal number of the volume to be created and
10132 @var{archive} is archive file or device name.
10134 When prompting for a new tape, @command{tar} accepts any of the following
10139 Request @command{tar} to explain possible responses
10141 Request @command{tar} to exit immediately.
10142 @item n @var{file-name}
10143 Request @command{tar} to write the next volume on the file @var{file-name}.
10145 Request @command{tar} to run a subshell. This option can be disabled
10146 by giving @option{--restrict} command line option to
10147 @command{tar}@footnote{@xref{--restrict}, for more information about
10150 Request @command{tar} to begin writing the next volume.
10153 (You should only type @samp{y} after you have changed the tape;
10154 otherwise @command{tar} will write over the volume it just finished.)
10156 @cindex Volume number file
10158 @anchor{volno-file}
10159 @opindex volno-file
10160 The volume number used by @command{tar} in its tape-changing prompt
10161 can be changed; if you give the
10162 @option{--volno-file=@var{file-of-number}} option, then
10163 @var{file-of-number} should be an non-existing file to be created, or
10164 else, a file already containing a decimal number. That number will be
10165 used as the volume number of the first volume written. When
10166 @command{tar} is finished, it will rewrite the file with the
10167 now-current volume number. (This does not change the volume number
10168 written on a tape label, as per @ref{label}, it @emph{only} affects
10169 the number used in the prompt.)
10171 @cindex End-of-archive info script
10172 @cindex Info script
10173 @anchor{info-script}
10174 @opindex info-script
10175 @opindex new-volume-script
10176 If you want more elaborate behavior than this, you can write a special
10177 @dfn{new volume script}, that will be responsible for changing the
10178 volume, and instruct @command{tar} to use it instead of its normal
10179 prompting procedure:
10182 @item --info-script=@var{script-name}
10183 @itemx --new-volume-script=@var{script-name}
10184 @itemx -F @var{script-name}
10185 Specify the full name of the volume script to use. The script can be
10186 used to eject cassettes, or to broadcast messages such as
10187 @samp{Someone please come change my tape} when performing unattended
10191 The @var{script-name} is executed without any command line
10192 arguments. It inherits @command{tar}'s shell environment.
10193 Additional data is passed to it via the following
10194 environment variables:
10197 @vrindex TAR_VERSION, info script environment variable
10199 @GNUTAR{} version number.
10201 @vrindex TAR_ARCHIVE, info script environment variable
10203 The name of the archive @command{tar} is processing.
10205 @vrindex TAR_VOLUME, info script environment variable
10207 Ordinal number of the volume @command{tar} is about to start.
10209 @vrindex TAR_SUBCOMMAND, info script environment variable
10210 @item TAR_SUBCOMMAND
10211 Short option describing the operation @command{tar} is executing
10212 @xref{Operations}, for a complete list of subcommand options.
10214 @vrindex TAR_FORMAT, info script environment variable
10216 Format of the archive being processed. @xref{Formats}, for a complete
10217 list of archive format names.
10220 The volume script can instruct @command{tar} to use new archive name,
10221 by writing in to file descriptor 3 (see below for an example).
10223 If the info script fails, @command{tar} exits; otherwise, it begins
10224 writing the next volume.
10226 If you want @command{tar} to cycle through a series of files or tape
10227 drives, there are three approaches to choose from. First of all, you
10228 can give @command{tar} multiple @option{--file} options. In this case
10229 the specified files will be used, in sequence, as the successive
10230 volumes of the archive. Only when the first one in the sequence needs
10231 to be used again will @command{tar} prompt for a tape change (or run
10232 the info script). For example, suppose someone has two tape drives on
10233 a system named @file{/dev/tape0} and @file{/dev/tape1}. For having
10234 @GNUTAR{} to switch to the second drive when it needs to write the
10235 second tape, and then back to the first tape, etc., just do either of:
10238 $ @kbd{tar --create --multi-volume --file=/dev/tape0 --file=/dev/tape1 @var{files}}
10239 $ @kbd{tar cMff /dev/tape0 /dev/tape1 @var{files}}
10242 The second method is to use the @samp{n} response to the tape-change
10245 Finally, the most flexible approach is to use a volume script, that
10246 writes new archive name to the file descriptor #3. For example, the
10247 following volume script will create a series of archive files, named
10248 @file{@var{archive}-@var{vol}}, where @var{archive} is the name of the
10249 archive being created (as given by @option{--file} option) and
10250 @var{vol} is the ordinal number of the archive being created:
10255 echo Preparing volume $TAR_VOLUME of $TAR_ARCHIVE.
10257 name=`expr $TAR_ARCHIVE : '\(.*\)-.*'`
10258 case $TAR_SUBCOMMAND in
10260 -d|-x|-t) test -r $@{name:-$TAR_ARCHIVE@}-$TAR_VOLUME || exit 1
10265 echo $@{name:-$TAR_ARCHIVE@}-$TAR_VOLUME >&3
10269 The same script cant be used while listing, comparing or extracting
10270 from the created archive. For example:
10274 # @r{Create a multi-volume archive:}
10275 $ @kbd{tar -c -L1024 -f archive.tar -F new-volume .}
10276 # @r{Extract from the created archive:}
10277 $ @kbd{tar -x -f archive.tar -F new-volume .}
10282 Notice, that the first command had to use @option{-L} option, since
10283 otherwise @GNUTAR{} will end up writing everything to file
10284 @file{archive.tar}.
10286 You can read each individual volume of a multi-volume archive as if it
10287 were an archive by itself. For example, to list the contents of one
10288 volume, use @option{--list}, without @option{--multi-volume} specified.
10289 To extract an archive member from one volume (assuming it is described
10290 that volume), use @option{--extract}, again without
10291 @option{--multi-volume}.
10293 If an archive member is split across volumes (i.e., its entry begins on
10294 one volume of the media and ends on another), you need to specify
10295 @option{--multi-volume} to extract it successfully. In this case, you
10296 should load the volume where the archive member starts, and use
10297 @samp{tar --extract --multi-volume}---@command{tar} will prompt for later
10298 volumes as it needs them. @xref{extracting archives}, for more
10299 information about extracting archives.
10301 Multi-volume archives can be modified like any other archive. To add
10302 files to a multi-volume archive, you need to only mount the last
10303 volume of the archive media (and new volumes, if needed). For all
10304 other operations, you need to use the entire archive.
10306 If a multi-volume archive was labeled using
10307 @option{--label=@var{archive-label}} (@pxref{label}) when it was
10308 created, @command{tar} will not automatically label volumes which are
10309 added later. To label subsequent volumes, specify
10310 @option{--label=@var{archive-label}} again in conjunction with the
10311 @option{--append}, @option{--update} or @option{--concatenate} operation.
10313 Notice that multi-volume support is a GNU extension and the archives
10314 created in this mode should be read only using @GNUTAR{}. If you
10315 absolutely have to process such archives using a third-party @command{tar}
10316 implementation, read @ref{Split Recovery}.
10319 @subsection Tape Files
10322 To give the archive a name which will be recorded in it, use the
10323 @option{--label=@var{volume-label}} (@option{-V @var{volume-label}})
10324 option. This will write a special block identifying
10325 @var{volume-label} as the name of the archive to the front of the
10326 archive which will be displayed when the archive is listed with
10327 @option{--list}. If you are creating a multi-volume archive with
10328 @option{--multi-volume} (@pxref{Using Multiple Tapes}), then the
10329 volume label will have @samp{Volume @var{nnn}} appended to the name
10330 you give, where @var{nnn} is the number of the volume of the archive.
10331 (If you use the @option{--label=@var{volume-label}}) option when
10332 reading an archive, it checks to make sure the label on the tape
10333 matches the one you give. @xref{label}.
10335 When @command{tar} writes an archive to tape, it creates a single
10336 tape file. If multiple archives are written to the same tape, one
10337 after the other, they each get written as separate tape files. When
10338 extracting, it is necessary to position the tape at the right place
10339 before running @command{tar}. To do this, use the @command{mt} command.
10340 For more information on the @command{mt} command and on the organization
10341 of tapes into a sequence of tape files, see @ref{mt}.
10343 People seem to often do:
10346 @kbd{--label="@var{some-prefix} `date +@var{some-format}`"}
10349 or such, for pushing a common date in all volumes or an archive set.
10352 @subsection Concatenate Volumes into a Single Archive
10355 Sometimes it is necessary to convert existing @GNUTAR{} multi-volume
10356 archive to a single @command{tar} archive. Simply concatenating all
10357 volumes into one will not work, since each volume carries an additional
10358 information at the beginning. @GNUTAR{} is shipped with the shell
10359 script @command{tarcat} designed for this purpose.
10361 The script takes a list of files comprising a multi-volume archive
10362 and creates the resulting archive at the standard output. For example:
10365 @kbd{tarcat vol.1 vol.2 vol.3 | tar tf -}
10368 The script implements a simple heuristics to determine the format of
10369 the first volume file and to decide how to process the rest of the
10370 files. However, it makes no attempt to verify whether the files are
10371 given in order or even if they are valid @command{tar} archives.
10372 It uses @command{dd} and does not filter its standard error, so you
10373 will usually see lots of spurious messages.
10375 @FIXME{The script is not installed. Should we install it?}
10378 @section Including a Label in the Archive
10379 @cindex Labeling an archive
10380 @cindex Labels on the archive media
10381 @cindex Labeling multi-volume archives
10385 To avoid problems caused by misplaced paper labels on the archive
10386 media, you can include a @dfn{label} entry---an archive member which
10387 contains the name of the archive---in the archive itself. Use the
10388 @option{--label=@var{archive-label}} (@option{-V @var{archive-label}})
10389 option in conjunction with the @option{--create} operation to include
10390 a label entry in the archive as it is being created.
10393 @item --label=@var{archive-label}
10394 @itemx -V @var{archive-label}
10395 Includes an @dfn{archive-label} at the beginning of the archive when
10396 the archive is being created, when used in conjunction with the
10397 @option{--create} operation. Checks to make sure the archive label
10398 matches the one specified (when used in conjunction with any other
10402 If you create an archive using both
10403 @option{--label=@var{archive-label}} (@option{-V @var{archive-label}})
10404 and @option{--multi-volume} (@option{-M}), each volume of the archive
10405 will have an archive label of the form @samp{@var{archive-label}
10406 Volume @var{n}}, where @var{n} is 1 for the first volume, 2 for the
10407 next, and so on. @xref{Using Multiple Tapes}, for information on
10408 creating multiple volume archives.
10410 @cindex Volume label, listing
10411 @cindex Listing volume label
10412 The volume label will be displayed by @option{--list} along with
10413 the file contents. If verbose display is requested, it will also be
10414 explicitly marked as in the example below:
10418 $ @kbd{tar --verbose --list --file=iamanarchive}
10419 V--------- 0 0 0 1992-03-07 12:01 iamalabel--Volume Header--
10420 -rw-r--r-- ringo user 40 1990-05-21 13:30 iamafilename
10424 @opindex test-label
10425 @anchor{--test-label option}
10426 However, @option{--list} option will cause listing entire
10427 contents of the archive, which may be undesirable (for example, if the
10428 archive is stored on a tape). You can request checking only the volume
10429 by specifying @option{--test-label} option. This option reads only the
10430 first block of an archive, so it can be used with slow storage
10431 devices. For example:
10435 $ @kbd{tar --test-label --file=iamanarchive}
10440 If @option{--test-label} is used with a single command line
10441 argument, @command{tar} compares the volume label with the
10442 argument. It exits with code 0 if the two strings match, and with code
10443 2 otherwise. In this case no output is displayed. For example:
10447 $ @kbd{tar --test-label --file=iamanarchive 'iamalable'}
10449 $ @kbd{tar --test-label --file=iamanarchive 'iamalable' alabel}
10454 If you request any operation, other than @option{--create}, along
10455 with using @option{--label} option, @command{tar} will first check if
10456 the archive label matches the one specified and will refuse to proceed
10457 if it does not. Use this as a safety precaution to avoid accidentally
10458 overwriting existing archives. For example, if you wish to add files
10459 to @file{archive}, presumably labeled with string @samp{My volume},
10464 $ @kbd{tar -rf archive --label 'My volume' .}
10465 tar: Archive not labeled to match `My volume'
10470 in case its label does not match. This will work even if
10471 @file{archive} is not labeled at all.
10473 Similarly, @command{tar} will refuse to list or extract the
10474 archive if its label doesn't match the @var{archive-label}
10475 specified. In those cases, @var{archive-label} argument is interpreted
10476 as a globbing-style pattern which must match the actual magnetic
10477 volume label. @xref{exclude}, for a precise description of how match
10478 is attempted@footnote{Previous versions of @command{tar} used full
10479 regular expression matching, or before that, only exact string
10480 matching, instead of wildcard matchers. We decided for the sake of
10481 simplicity to use a uniform matching device through
10482 @command{tar}.}. If the switch @option{--multi-volume} (@option{-M}) is being used,
10483 the volume label matcher will also suffix @var{archive-label} by
10484 @w{@samp{ Volume [1-9]*}} if the initial match fails, before giving
10485 up. Since the volume numbering is automatically added in labels at
10486 creation time, it sounded logical to equally help the user taking care
10487 of it when the archive is being read.
10489 The @option{--label} was once called @option{--volume}, but is not
10490 available under that name anymore.
10492 You can also use @option{--label} to get a common information on
10493 all tapes of a series. For having this information different in each
10494 series created through a single script used on a regular basis, just
10495 manage to get some date string as part of the label. For example:
10499 $ @kbd{tar cfMV /dev/tape "Daily backup for `date +%Y-%m-%d`"}
10500 $ @kbd{tar --create --file=/dev/tape --multi-volume \
10501 --volume="Daily backup for `date +%Y-%m-%d`"}
10505 Also note that each label has its own date and time, which corresponds
10506 to when @GNUTAR{} initially attempted to write it,
10507 often soon after the operator launches @command{tar} or types the
10508 carriage return telling that the next tape is ready. Comparing date
10509 labels does give an idea of tape throughput only if the delays for
10510 rewinding tapes and the operator switching them were negligible, which
10511 is usually not the case.
10514 @section Verifying Data as It is Stored
10515 @cindex Verifying a write operation
10516 @cindex Double-checking a write operation
10521 @opindex verify, short description
10522 Attempt to verify the archive after writing.
10525 This option causes @command{tar} to verify the archive after writing it.
10526 Each volume is checked after it is written, and any discrepancies
10527 are recorded on the standard error output.
10529 Verification requires that the archive be on a back-space-able medium.
10530 This means pipes, some cartridge tape drives, and some other devices
10531 cannot be verified.
10533 You can insure the accuracy of an archive by comparing files in the
10534 system with archive members. @command{tar} can compare an archive to the
10535 file system as the archive is being written, to verify a write
10536 operation, or can compare a previously written archive, to insure that
10539 @xopindex{verify, using with @option{--create}}
10540 @xopindex{create, using with @option{--verify}}
10541 To check for discrepancies in an archive immediately after it is
10542 written, use the @option{--verify} (@option{-W}) option in conjunction with
10543 the @option{--create} operation. When this option is
10544 specified, @command{tar} checks archive members against their counterparts
10545 in the file system, and reports discrepancies on the standard error.
10547 To verify an archive, you must be able to read it from before the end
10548 of the last written entry. This option is useful for detecting data
10549 errors on some tapes. Archives written to pipes, some cartridge tape
10550 drives, and some other devices cannot be verified.
10552 One can explicitly compare an already made archive with the file
10553 system by using the @option{--compare} (@option{--diff}, @option{-d})
10554 option, instead of using the more automatic @option{--verify} option.
10557 Note that these two options have a slightly different intent. The
10558 @option{--compare} option checks how identical are the logical contents of some
10559 archive with what is on your disks, while the @option{--verify} option is
10560 really for checking if the physical contents agree and if the recording
10561 media itself is of dependable quality. So, for the @option{--verify}
10562 operation, @command{tar} tries to defeat all in-memory cache pertaining to
10563 the archive, while it lets the speed optimization undisturbed for the
10564 @option{--compare} option. If you nevertheless use @option{--compare} for
10565 media verification, you may have to defeat the in-memory cache yourself,
10566 maybe by opening and reclosing the door latch of your recording unit,
10567 forcing some doubt in your operating system about the fact this is really
10568 the same volume as the one just written or read.
10570 The @option{--verify} option would not be necessary if drivers were indeed
10571 able to detect dependably all write failures. This sometimes require many
10572 magnetic heads, some able to read after the writes occurred. One would
10573 not say that drivers unable to detect all cases are necessarily flawed,
10574 as long as programming is concerned.
10576 The @option{--verify} (@option{-W}) option will not work in
10577 conjunction with the @option{--multi-volume} (@option{-M}) option or
10578 the @option{--append} (@option{-r}), @option{--update} (@option{-u})
10579 and @option{--delete} operations. @xref{Operations}, for more
10580 information on these operations.
10582 Also, since @command{tar} normally strips leading @samp{/} from file
10583 names (@pxref{absolute}), a command like @samp{tar --verify -cf
10584 /tmp/foo.tar /etc} will work as desired only if the working directory is
10585 @file{/}, as @command{tar} uses the archive's relative member names
10586 (e.g., @file{etc/motd}) when verifying the archive.
10588 @node Write Protection
10589 @section Write Protection
10591 Almost all tapes and diskettes, and in a few rare cases, even disks can
10592 be @dfn{write protected}, to protect data on them from being changed.
10593 Once an archive is written, you should write protect the media to prevent
10594 the archive from being accidentally overwritten or deleted. (This will
10595 protect the archive from being changed with a tape or floppy drive---it
10596 will not protect it from magnet fields or other physical hazards).
10598 The write protection device itself is usually an integral part of the
10599 physical media, and can be a two position (write enabled/write
10600 disabled) switch, a notch which can be popped out or covered, a ring
10601 which can be removed from the center of a tape reel, or some other
10602 changeable feature.
10607 This appendix lists some important user-visible changes between
10608 version @GNUTAR{} @value{VERSION} and previous versions. An up-to-date
10609 version of this document is available at
10610 @uref{http://www.gnu.org/@/software/@/tar/manual/changes.html,the
10611 @GNUTAR{} documentation page}.
10614 @item Use of globbing patterns when listing and extracting.
10616 Previous versions of GNU tar assumed shell-style globbing when
10617 extracting from or listing an archive. For example:
10620 $ @kbd{tar xf foo.tar '*.c'}
10623 would extract all files whose names end in @samp{.c}. This behavior
10624 was not documented and was incompatible with traditional tar
10625 implementations. Therefore, starting from version 1.15.91, GNU tar
10626 no longer uses globbing by default. For example, the above invocation
10627 is now interpreted as a request to extract from the archive the file
10630 To facilitate transition to the new behavior for those users who got
10631 used to the previous incorrect one, @command{tar} will print a warning
10632 if it finds out that a requested member was not found in the archive
10633 and its name looks like a globbing pattern. For example:
10636 $ @kbd{tar xf foo.tar '*.c'}
10637 tar: Pattern matching characters used in file names. Please,
10638 tar: use --wildcards to enable pattern matching, or --no-wildcards to
10639 tar: suppress this warning.
10640 tar: *.c: Not found in archive
10641 tar: Error exit delayed from previous errors
10644 To treat member names as globbing patterns, use --wildcards option.
10645 If you want to tar to mimic the behavior of versions prior to 1.15.91,
10646 add this option to your @env{TAR_OPTIONS} variable.
10648 @xref{wildcards}, for the detailed discussion of the use of globbing
10649 patterns by @GNUTAR{}.
10651 @item Use of short option @option{-o}.
10653 Earlier versions of @GNUTAR{} understood @option{-o} command line
10654 option as a synonym for @option{--old-archive}.
10656 @GNUTAR{} starting from version 1.13.90 understands this option as
10657 a synonym for @option{--no-same-owner}. This is compatible with
10658 UNIX98 @command{tar} implementations.
10660 However, to facilitate transition, @option{-o} option retains its
10661 old semantics when it is used with one of archive-creation commands.
10662 Users are encouraged to use @option{--format=oldgnu} instead.
10664 It is especially important, since versions of @acronym{GNU} Automake
10665 up to and including 1.8.4 invoke tar with this option to produce
10666 distribution tarballs. @xref{Formats,v7}, for the detailed discussion
10667 of this issue and its implications.
10669 @FIXME{Change the first argument to tar-formats when the new Automake is
10670 out. The proposition to add @anchor{} to the appropriate place of its
10671 docs was accepted by Automake people --Sergey 2006-05-25}.
10672 @xref{Options, tar-v7, Changing Automake's Behavior,
10673 automake, GNU Automake}, for a description on how to use various
10674 archive formats with @command{automake}.
10676 Future versions of @GNUTAR{} will understand @option{-o} only as a
10677 synonym for @option{--no-same-owner}.
10679 @item Use of short option @option{-l}
10681 Earlier versions of @GNUTAR{} understood @option{-l} option as a
10682 synonym for @option{--one-file-system}. Since such usage contradicted
10683 to UNIX98 specification and harmed compatibility with other
10684 implementation, it was declared deprecated in version 1.14. However,
10685 to facilitate transition to its new semantics, it was supported by
10686 versions 1.15 and 1.15.90. The present use of @option{-l} as a short
10687 variant of @option{--check-links} was introduced in version 1.15.91.
10689 @item Use of options @option{--portability} and @option{--old-archive}
10691 These options are deprecated. Please use @option{--format=v7} instead.
10693 @item Use of option @option{--posix}
10695 This option is deprecated. Please use @option{--format=posix} instead.
10698 @node Configuring Help Summary
10699 @appendix Configuring Help Summary
10701 Running @kbd{tar --help} displays the short @command{tar} option
10702 summary (@pxref{help}). This summary is organized by @dfn{groups} of
10703 semantically close options. The options within each group are printed
10704 in the following order: a short option, eventually followed by a list
10705 of corresponding long option names, followed by a short description of
10706 the option. For example, here is an excerpt from the actual @kbd{tar
10710 Main operation mode:
10712 -A, --catenate, --concatenate append tar files to an archive
10713 -c, --create create a new archive
10714 -d, --diff, --compare find differences between archive and
10716 --delete delete from the archive
10719 @vrindex ARGP_HELP_FMT, environment variable
10720 The exact visual representation of the help output is configurable via
10721 @env{ARGP_HELP_FMT} environment variable. The value of this variable
10722 is a comma-separated list of @dfn{format variable} assignments. There
10723 are two kinds of format variables. An @dfn{offset variable} keeps the
10724 offset of some part of help output text from the leftmost column on
10725 the screen. A @dfn{boolean} variable is a flag that toggles some
10726 output feature on or off. Depending on the type of the corresponding
10727 variable, there are two kinds of assignments:
10730 @item Offset assignment
10732 The assignment to an offset variable has the following syntax:
10735 @var{variable}=@var{value}
10739 where @var{variable} is the variable name, and @var{value} is a
10740 numeric value to be assigned to the variable.
10742 @item Boolean assignment
10744 To assign @code{true} value to a variable, simply put this variable name. To
10745 assign @code{false} value, prefix the variable name with @samp{no-}. For
10750 # Assign @code{true} value:
10752 # Assign @code{false} value:
10758 Following variables are declared:
10760 @deftypevr {Help Output} boolean dup-args
10761 If true, arguments for an option are shown with both short and long
10762 options, even when a given option has both forms, for example:
10765 -f ARCHIVE, --file=ARCHIVE use archive file or device ARCHIVE
10768 If false, then if an option has both short and long forms, the
10769 argument is only shown with the long one, for example:
10772 -f, --file=ARCHIVE use archive file or device ARCHIVE
10776 and a message indicating that the argument is applicable to both
10777 forms is printed below the options. This message can be disabled
10778 using @code{dup-args-note} (see below).
10780 The default is false.
10783 @deftypevr {Help Output} boolean dup-args-note
10784 If this variable is true, which is the default, the following notice
10785 is displayed at the end of the help output:
10788 Mandatory or optional arguments to long options are also mandatory or
10789 optional for any corresponding short options.
10792 Setting @code{no-dup-args-note} inhibits this message. Normally, only one of
10793 variables @code{dup-args} or @code{dup-args-note} should be set.
10796 @deftypevr {Help Output} offset short-opt-col
10797 Column in which short options start. Default is 2.
10801 $ @kbd{tar --help|grep ARCHIVE}
10802 -f, --file=ARCHIVE use archive file or device ARCHIVE
10803 $ @kbd{ARGP_HELP_FMT=short-opt-col=6 tar --help|grep ARCHIVE}
10804 -f, --file=ARCHIVE use archive file or device ARCHIVE
10809 @deftypevr {Help Output} offset long-opt-col
10810 Column in which long options start. Default is 6. For example:
10814 $ @kbd{tar --help|grep ARCHIVE}
10815 -f, --file=ARCHIVE use archive file or device ARCHIVE
10816 $ @kbd{ARGP_HELP_FMT=long-opt-col=16 tar --help|grep ARCHIVE}
10817 -f, --file=ARCHIVE use archive file or device ARCHIVE
10822 @deftypevr {Help Output} offset doc-opt-col
10823 Column in which @dfn{doc options} start. A doc option isn't actually
10824 an option, but rather an arbitrary piece of documentation that is
10825 displayed in much the same manner as the options. For example, in
10826 the description of @option{--format} option:
10830 -H, --format=FORMAT create archive of the given format.
10832 FORMAT is one of the following:
10834 gnu GNU tar 1.13.x format
10835 oldgnu GNU format as per tar <= 1.12
10836 pax POSIX 1003.1-2001 (pax) format
10838 ustar POSIX 1003.1-1988 (ustar) format
10839 v7 old V7 tar format
10844 the format names are doc options. Thus, if you set
10845 @kbd{ARGP_HELP_FMT=doc-opt-col=6} the above part of the help output
10846 will look as follows:
10850 -H, --format=FORMAT create archive of the given format.
10852 FORMAT is one of the following:
10854 gnu GNU tar 1.13.x format
10855 oldgnu GNU format as per tar <= 1.12
10856 pax POSIX 1003.1-2001 (pax) format
10858 ustar POSIX 1003.1-1988 (ustar) format
10859 v7 old V7 tar format
10864 @deftypevr {Help Output} offset opt-doc-col
10865 Column in which option description starts. Default is 29.
10869 $ @kbd{tar --help|grep ARCHIVE}
10870 -f, --file=ARCHIVE use archive file or device ARCHIVE
10871 $ @kbd{ARGP_HELP_FMT=opt-doc-col=19 tar --help|grep ARCHIVE}
10872 -f, --file=ARCHIVE use archive file or device ARCHIVE
10873 $ @kbd{ARGP_HELP_FMT=opt-doc-col=9 tar --help|grep ARCHIVE}
10875 use archive file or device ARCHIVE
10880 Notice, that the description starts on a separate line if
10881 @code{opt-doc-col} value is too small.
10884 @deftypevr {Help Output} offset header-col
10885 Column in which @dfn{group headers} are printed. A group header is a
10886 descriptive text preceding an option group. For example, in the
10890 Main operation mode:
10892 -A, --catenate, --concatenate append tar files to
10894 -c, --create create a new archive
10897 @samp{Main operation mode:} is the group header.
10899 The default value is 1.
10902 @deftypevr {Help Output} offset usage-indent
10903 Indentation of wrapped usage lines. Affects @option{--usage}
10904 output. Default is 12.
10907 @deftypevr {Help Output} offset rmargin
10908 Right margin of the text output. Used for wrapping.
10911 @node Tar Internals
10912 @appendix Tar Internals
10913 @include intern.texi
10917 @include genfile.texi
10919 @node Free Software Needs Free Documentation
10920 @appendix Free Software Needs Free Documentation
10921 @include freemanuals.texi
10923 @node Copying This Manual
10924 @appendix Copying This Manual
10927 * GNU Free Documentation License:: License for copying this manual
10932 @node Index of Command Line Options
10933 @appendix Index of Command Line Options
10935 This appendix contains an index of all @GNUTAR{} long command line
10936 options. The options are listed without the preceding double-dash.
10937 For a cross-reference of short command line options, @ref{Short Option Summary}.
10950 @c Local variables:
10951 @c texinfo-column-for-description: 32
projects / chaz / tar / blob