at the end}We will indicate those abbreviations appropriately to get
you used to seeing them. (Note that the ``old style'' option forms
exist in @GNUTAR{} for compatibility with Unix
-@command{tar}. We present a full discussion of this way of writing
-options and operations appears in @ref{Old Options}, and we discuss
-the other two styles of writing options in @ref{Mnemonic Options}, and
-@ref{Short Options}.)
+@command{tar}. In this book we present a full discussion of this way
+of writing options and operations (@pxref{Old Options}), and we discuss
+the other two styles of writing options (@xref{Mnemonic Options}, and
+@pxref{Short Options}).
In the examples and in the text of this tutorial, we usually use the
long forms of operations and options; but the ``short'' forms produce
@itemx -R
With this option present, @command{tar} prints error messages for read errors
-with the block number in the archive file. @FIXME-xref{}
+with the block number in the archive file. @xref{block-number}
@item --blocking-factor=@var{blocking}
@itemx -b @var{blocking}
@command{tar} will use the @command{compress} program when reading or
writing the archive. This allows you to directly act on archives
-while saving space. @FIXME-xref{}
+while saving space. @xref{gzip}.
@item --confirmation
-(See @option{--interactive}.) @FIXME-pxref{}
+(See @option{--interactive}.) @xref{interactive}.
@item --dereference
@itemx -h
When creating a @command{tar} archive, @command{tar} will archive the
file that a symbolic link points to, rather than archiving the
-symlink. @FIXME-xref{}
+symlink. @xref{dereference}.
@item --directory=@var{dir}
@itemx -C @var{dir}
Specifies that @command{tar} should ask the user for confirmation before
performing potentially destructive options, such as overwriting files.
-@FIXME-xref{}
+@xref{interactive}.
@item --keep-newer-files
When used in extract or list mode, this option instructs tar
to ignore any keywords matching the given @var{pattern} in the extended
header records. In both cases, matching is performed using the pattern
-matching notation described in @acronym{POSIX 1003.2}, 3.13 @FIXME-xref{see
-man 7 glob}. For example:
+matching notation described in @acronym{POSIX 1003.2}, 3.13
+(See @cite{glob(7)}). For example:
@smallexample
--pax-option delete=security.*
it might be excluded by the use of the @value{op-exclude} option, or
some other reason.
+@anchor{block-number}
If @value{op-block-number} is used, @command{tar} prints, along with
every message it would normally produce, the block number within the
archive where the message was triggered. Also, supplementary messages
@value{op-list} when listing a file-system backup tape, allowing you to
choose among several backup tapes when retrieving a file later, in
favor of the tape where the file appears earliest (closest to the
-front of the tape). @FIXME-xref{when the node name is set and the
-backup section written.}
+front of the tape). @xref{backup}.
@node interactive
@section Asking for Confirmation During Operations
-rw-rw-rw- melissa user 65 1997-01-30 14:15 jazz
@end smallexample
-We can concatenate these two archives with @command{tar}:
+We can concatenate these two archives with @command{tar}:
@smallexample
$ @kbd{cd ..}
$ @kbd{tar --concatenate --file=bluesrock.tar jazzfolk.tar}
@end smallexample
+The result of this command is the concatenation of the archive
+specified with @option{--file} option and the archives, given in the
+command line. The new, concatenated archive will be called by the
+same name as the one given with the @option{--file} option. As usual,
+if you omit @option{--file}, @command{tar} will use the value of the
+environment variable @env{TAPE}, or, if this has not been set, the
+default archive name.
+
+@FIXME{There is no way to specify a new name...}
+
If you now list the contents of the @file{bluesclass.tar}, you will see
that now it also contains the archive members of @file{jazzfolk.tar}:
When you use @option{--concatenate}, the source and target archives must
already exist and must have been created using compatible format
-parameters. @FIXME-pxref{Matching Format Parameters}The new,
-concatenated archive will be called by the same name as the first
-archive listed on the command line. @FIXME{is there a way to specify a
-new name?}
+parameters. Notice, that @command{tar} does not check whether the
+archives it concatenates have compatible formats, it does not
+even check if the files are really tar archives.
Like @value{op-append}, this operation cannot be performed on some
tape drives, due to deficiencies in the formats those tape drives use.
information on dealing with archives improperly combined using the
@command{cat} shell utility.
-@FIXME{this shouldn't go here. where should it go?} You must specify
-the source archives using @value{op-file} (@value{pxref-file}). If you
-do not specify the target archive, @command{tar} uses the value of the
-environment variable @env{TAPE}, or, if this has not been set, the
-default archive name.
-
@node delete
@subsection Removing Archive Members Using @option{--delete}
@UNREVISED
tar: funk not found in archive
@end smallexample
-@noindent
-@FIXME{what does this actually depend on? i'm making a guess,
-here.}Depending on the system where you are running @command{tar} and the
-version you are running, @command{tar} may have a different error message,
-such as:
-
-@smallexample
-funk: does not exist
-@end smallexample
-
-@FIXME-xref{somewhere, for more information about format parameters.
-Melissa says: such as "format variations"? But why? Clearly I don't
-get it yet; I'll deal when I get to that section.}
-
The spirit behind the @value{op-compare} option is to check whether the
archive represents the current state of files on disk, more than validating
the integrity of the archive media. For this later goal, @xref{verify}.
@subsection Changing How @command{tar} Writes Files
@UNREVISED
-@FIXME{need to mention the brand new option, --backup}
+@FIXME{Introductory paragraph}
@menu
* Dealing with Old Files::
or @value{op-extract}.
@end table
-@FIXME{we don't need/want --preserve to exist any more (from melissa:
-ie, don't want that *version* of the option to exist, or don't want
-the option to exist in either version?}
-
-@FIXME{i think this explanation is lacking.}
-
The @value{op-same-order} option tells @command{tar} that the list of file
names to be listed or extracted is sorted in the same order as the
files in the archive. This allows a large list of names to be used,
record file in @file{/etc/tar-backup/}, which is used by the scripts
to store and retrieve information about which files were dumped. This
file is not meant to be read by humans, and should not be deleted by
-them. @FIXME-xref{incremental and listed-incremental, for a more
-detailed explanation of this file.}
+them. @xref{Snapshot Files}, for a more detailed explanation of this
+file.
The second file is a log file containing the names of the file systems
and files dumped, what time the backup was made, and any error
head is on. Before writing an archive, you should make sure that no
data on the tape will be overwritten (unless it is no longer needed).
Before reading an archive, you should make sure the tape head is at
-the beginning of the archive you want to read. (The @code{restore}
-script will find the archive automatically. @FIXME-xref{Scripted Restoration}@xref{mt}, for
-an explanation of the tape moving utility.
+the beginning of the archive you want to read. You can do it manually
+via @code{mt} utility (@pxref{mt}). The @code{restore} script does
+that automatically (@pxref{Scripted Restoration}).
If you want to add new archive file entries to a tape, you should
advance the tape to the end of the existing file entries, backspace
@var{volume-label} as the name of the archive to the front of the archive
which will be displayed when the archive is listed with @value{op-list}.
If you are creating a multi-volume archive with
-@value{op-multi-volume}@FIXME-pxref{Using Multiple Tapes}, then the
-volume label will have
-@samp{Volume @var{nnn}} appended to the name you give, where @var{nnn} is
-the number of the volume of the archive. (If you use the @value{op-label}
-option when reading an archive, it checks to make sure the label on the
-tape matches the one you give. @value{xref-label}.
+@value{op-multi-volume} (@pxref{Using Multiple Tapes}), then the
+volume label will have @samp{Volume @var{nnn}} appended to the name
+you give, where @var{nnn} is the number of the volume of the archive.
+(If you use the @value{op-label} option when reading an archive, it
+checks to make sure the label on the tape matches the one you give.
+@value{xref-label}.
When @command{tar} writes an archive to tape, it creates a single
tape file. If multiple archives are written to the same tape, one
@value{op-multi-volume}, each volume of the archive will have an
archive label of the form @samp{@var{archive-label} Volume @var{n}},
where @var{n} is 1 for the first volume, 2 for the next, and so on.
-@FIXME-xref{Multi-Volume Archives, for information on creating multiple
-volume archives.}
+@xref{Using Multiple Tapes}, for information on creating multiple
+volume archives.
@cindex Volume label, listing
@cindex Listing volume label
projects / chaz / tar / commitdiff
