X-Git-Url: https://git.dogcows.com/gitweb?p=chaz%2Ftar;a=blobdiff_plain;f=doc%2Fintern.texi;h=f5169738672ff5d6cd8434bb038b5303248bbbca;hp=e6f9706e5c79f8588e1dd69c44c85d420ab02ddd;hb=45ccda119355a1087450039a250359c1d0de0d08;hpb=97bfe578edf7a92392896ddb4d401a11ad86808e

diff --git a/doc/intern.texi b/doc/intern.texi
index e6f9706..f516973 100644
--- a/doc/intern.texi
+++ b/doc/intern.texi
@@ -1,11 +1,12 @@
 @c This is part of the paxutils manual.
-@c Copyright (C) 2006 Free Software Foundation, Inc.
+@c Copyright (C) 2006, 2014 Free Software Foundation, Inc.
 @c This file is distributed under GFDL 1.1 or any later version
 @c published by the Free Software Foundation.
 
 @menu
 * Standard::           Basic Tar Format
 * Extensions::         @acronym{GNU} Extensions to the Archive Format
+* Sparse Formats::     Storing Sparse Files
 * Snapshot Files::
 * Dumpdir::
 @end menu
@@ -35,8 +36,6 @@ Archives are permitted to have more than one member with the same
 member name.  One way this situation can occur is if more than one
 version of a file has been stored in the archive.  For information
 about adding new versions of a file to an archive, see @ref{update}.
-@FIXME-xref{To learn more about having more than one archive member with the
-same name, see -backup node, when it's written.}
 
 In addition to entries describing archive members, an archive may
 contain entries which @command{tar} itself uses to store information.
@@ -95,7 +94,7 @@ The @code{name} field is the file name of the file, with directory names
 @FIXME{how big a name before field overflows?}
 
 The @code{mode} field provides nine bits specifying file permissions
-and three bits to specify the Set UID, Set GID, and Save Text
+and three bits to specify the Set @acronym{UID}, Set @acronym{GID}, and Save Text
 (@dfn{sticky}) modes.  Values for these bits are defined above.
 When special permissions are required to create a file with a given
 mode, and the user restoring files from the archive does not hold such
@@ -106,12 +105,12 @@ should be faked up when creating or updating an archive; e.g., the
 group permission could be copied from the @emph{other} permission.
 
 The @code{uid} and @code{gid} fields are the numeric user and group
-ID of the file owners, respectively.  If the operating system does
-not support numeric user or group IDs, these fields should be ignored.
+@acronym{ID} of the file owners, respectively.  If the operating system does
+not support numeric user or group @acronym{ID}s, these fields should
+be ignored.
 
 The @code{size} field is the size of the file in bytes; linked files
-are archived with this field specified as zero.  @FIXME-xref{Modifiers, in
-particular the @option{--incremental} (@option{-G}) option.}
+are archived with this field specified as zero.
 
 The @code{mtime} field is the data modification time of the file at
 the time it was archived.  It is the ASCII representation of the octal
@@ -257,7 +256,7 @@ The @code{magic} field indicates that this archive was output in
 the P1003 archive format.  If this field contains @code{TMAGIC},
 the @code{uname} and @code{gname} fields will contain the ASCII
 representation of the owner and group of the file respectively.
-If found, the user and group IDs are used rather than the values in
+If found, the user and group @acronym{ID}s are used rather than the values in
 the @code{uid} and @code{gid} fields.
 
 For references, see ISO/IEC 9945-1:1990 or IEEE Std 1003.1-1990, pages
@@ -320,6 +319,10 @@ use the @acronym{GNU}-added fields of the header, other versions of
 @command{tar} program will give an error, the most likely one being a
 checksum error.
 
+@node Sparse Formats
+@unnumberedsec Storing Sparse Files
+@include sparse.texi
+
 @node Snapshot Files
 @unnumberedsec Format of the Incremental Snapshot Files
 @include snapshot.texi