From owner-man-jp-reviewer@jp.FreeBSD.org Fri Dec 24 00:20:34 2004
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id iBNFKYJ77508;
	Fri, 24 Dec 2004 00:20:34 +0900 (JST)
	(envelope-from owner-man-jp-reviewer@jp.FreeBSD.org)
Received: from mail502.nifty.com (mail502.nifty.com [202.248.37.210])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet id iBNFKX877503
	for <man-jp-reviewer@jp.FreeBSD.org>; Fri, 24 Dec 2004 00:20:33 +0900 (JST)
	(envelope-from CQG00620@nifty.ne.jp)
Received: from nifty.ne.jp (ntceast018220.east.dup.ppp.infoweb.ne.jp [220.209.207.220])by mail502.nifty.com with ESMTP id iBNFK4Ue003844
	for <man-jp-reviewer@jp.FreeBSD.org>; Fri, 24 Dec 2004 00:20:05 +0900
Message-Id: <200412231520.iBNFK4Ue003844@mail502.nifty.com>
From: Watanabe Kazuhiro <CQG00620@nifty.ne.jp>
To: jpman reviewer <man-jp-reviewer@jp.FreeBSD.org>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5
 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/20.7
 (i386--freebsd) MULE/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=ISO-2022-JP
Reply-To: man-jp-reviewer@jp.FreeBSD.org
Precedence: list
Date: Fri, 24 Dec 2004 00:19:50 +0900
X-Sequence: man-jp-reviewer 4738
Subject: [man-jp-reviewer 4738] tar.5
Sender: owner-man-jp-reviewer@jp.FreeBSD.org
X-Originator: CQG00620@nifty.ne.jp
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+041223

$BEOJU0l42$G$9!#(B

tar.5 $B$NK]Lu$,=PMh$?$N$G!"%l%S%e!<$r$*4j$$$7$^$9!#(B

GNU tar $B$N(B "M" $B%U%i%0(B($B%^%k%A%\%j%e!<%`%"!<%+%$%V(B)$B$N@bL@$N$H$3$m$G!"(B

| -FreeBSD's version of GNU tar does not handle the corner case of an
| -archive's being continued in the middle of a long name or other
| -extension header.

$B$r(B

| +FreeBSD $BHG$N(B GNU tar $B$O!"(B $BD9$$L>A0$dB>$N3HD%%X%C%@$NCf$GB3$/$h$&$J%"!<%+%$%V$O(B
| +$B07$$$^$;$s!#(B

$B$HLu$7$^$7$?$,!"(B2$BF|$[$I9M$($F$b!"0UL#$,$o$+$j$^$;$s!#$=$&$$$&%X%C%@$H(B
$BAH$_9g$o$5$l$?7A$N%^%k%A%\%j%e!<%`%"!<%+%$%V$O07$($J$$$h!"$H$$$&$3$H$G(B
$B$7$g$&$+!#(B


--- tar.5.orig	Fri Dec 17 09:43:33 2004
+++ tar.5	Thu Dec 23 23:55:47 2004
@@ -22,60 +22,64 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\" $FreeBSD: src/lib/libarchive/tar.5,v 1.9 2004/08/07 17:24:50 kientzle Exp $
+.\" $FreeBSD: $
+.\" %FreeBSD: src/lib/libarchive/tar.5,v 1.9 2004/08/07 17:24:50 kientzle Exp %
+.\"
+.\" WORD:	reader		$BFI$_=P$7%W%m%0%i%`(B
+.\" WORD:	writer		$B:n@.%W%m%0%i%`(B
+.\" WORD:	zero byte	$B%P%$%H(B 0 [grep.1]
+.\" WORD:	store		$B5-O?$9$k(B
+.\"				$BJ]B8$9$k(B (restore$B$NH?0U8l$H$7$F(B) 
+.\" WORD:	textual		$B%F%-%9%H7A<0$N(B
 .\"
 .Dd May 20, 2004
 .Dt TAR 5
 .Os
-.Sh NAME
+.Sh $BL>>N(B
 .Nm tar
-.Nd format of tape archive files
-.Sh DESCRIPTION
-The
+.Nd $B%F!<%W%"!<%+%$%V%U%!%$%k$N%U%)!<%^%C%H(B
+.Sh $B2r@b(B
 .Nm
-archive format collects any number of files, directories, and other
-filesystem objects (symbolic links, device nodes, etc.) into a single
-stream of bytes.
-The format was originally designed to be used with
-tape drives that operate with fixed-size blocks, but is widely used as
-a general packaging mechanism.
-.Ss General Format
-A
+$B%"!<%+%$%V$N%U%)!<%^%C%H$O!"$$$/$D$b$N%U%!%$%k!"%G%#%l%/%H%j$d$3$NB>$N(B
+$B%U%!%$%k%7%9%F%`%*%V%8%'%/%H(B ($B%7%s%\%j%C%/%j%s%/!"%G%P%$%9%N!<%I$J$I(B)
+$B$r=8$a$F!"C10l$N%P%$%HNs$N%9%H%j!<%`$H$7$?$b$N$G$9!#(B
+$B$3$N%U%)!<%^%C%H$O85Mh!"8GDjD9$N%V%m%C%/$GA`:n$9$k%F!<%W%I%i%$%V$H6&$K(B
+$B;HMQ$5$l$k$h$&$K%G%6%$%s$5$l$F$$$^$7$?$,!"0lHLE*$J%Q%C%1!<%8%s%05!9=$H$7$F(B
+$B9-$/MQ$$$i$l$F$$$^$9!#(B
+.Ss $B%U%)!<%^%C%H$N35N,(B
 .Nm
-archive consists of a series of 512-byte records.
-Each filesystem object requires a header record which stores basic metadata
-(pathname, owner, permissions, etc.) and zero or more records containing any
-file data.
-The end of the archive is indicated by two records consisting
-entirely of zero bytes.
-.Pp
-For compatibility with tape drives that use fixed block sizes,
-programs that read or write tar files always read or write a fixed
-number of records with each I/O operation.
-These
-.Dq blocks
-are always a multiple of the record size.
-The most common block size\(emand the maximum supported by historic
-implementations\(emis 10240 bytes or 20 records.
-(Note: the terms
-.Dq block
-and
-.Dq record
-here are not entirely standard; this document follows the
-convention established by John Gilmore in documenting
-.Nm pdtar . )
-.Ss Old-Style Archive Format
-The original tar archive format has been extended many times to
-include additional information that various implementors found
-necessary.
-This section describes the variant implemented by the tar command
-included in
-.At v7 ,
-which is one of the earliest widely-used versions of the tar program.
+$B%"!<%+%$%V$O!"(B512 $B%P%$%H%l%3!<%I$N=89g$+$i$J$j$^$9!#(B
+$B3F%U%!%$%k%7%9%F%`%*%V%8%'%/%H$K$O!"4pK\E*$J%a%?%G!<%?(B ($B%Q%9L>!"=jM-<T!"(B
+$B%Q!<%_%C%7%g%s$J$I(B) $B$r5-O?$7$?%X%C%@%l%3!<%I$H!"%U%!%$%k%G!<%?$r4^$s$@(B
+0 $B8D$+$=$l0J>e$N%l%3!<%I$,I,MW$G$9!#(B
+$B%"!<%+%$%V$N=*C<$O!"A4$F$,%P%$%H(B 0 $B$N(B 2 $B$D$N%l%3!<%I$G<($5$l$^$9!#(B
+.Pp
+$B8GDj%V%m%C%/%5%$%:$r;HMQ$9$k%F!<%W%I%i%$%V$H$N8_49@-$N$?$a!"(B tar $B%U%!%$%k$r(B
+$BFI$_=q$-$9$k%W%m%0%i%`$O3F(B I/O $BA`:n$N:]$K!">o$K8GDj$7$?%l%3!<%I?t$G(B
+$BFI$_=q$-$r$7$^$9!#(B
+$B$3$l$i$N(B
+.Dq $B%V%m%C%/(B
+$B$O>o$K%l%3!<%I%5%$%:$NG\?t$G$9!#(B
+$B:G$b0lHLE*$J%V%m%C%/%5%$%:(B \(em $B$3$l$^$G$N<BAu$G:G$b%5%]!<%H$5$l$F$$$k(B
+$B%5%$%:(B \(em $B$O(B 10240 $B%P%$%H$+(B 20 $B%l%3!<%I$G$9!#(B
+($BCm0U(B: $B$3$3$G$N(B
+.Dq $B%V%m%C%/(B
+$B$*$h$S(B
+.Dq $B%l%3!<%I(B
+$B$H$$$&8@MU$O40A4$KI8=`$H$$$&$o$1$G$O$"$j$^$;$s!#(B
+$B$3$N%I%-%e%a%s%H$G$O!"(B John Gilmore $B$,(B
+.Nm pdtar
+$B$N%I%-%e%a%s%H$G3NN)$7$?$7$?47Nc$K1h$C$F$$$^$9!#(B)
+.Ss $B8E$$7A<0$N%"!<%+%$%V%U%)!<%^%C%H(B
+$B%*%j%8%J%k$N(B tar $B%"!<%+%$%V%U%)!<%^%C%H$O!"$?$/$5$s$N<BAu<T$,I,MW$K1~$8$F!"(B
+$BDI2C$N>pJs$r4^$a$k$?$a$K2?EY$b3HD%$5$l$F$-$^$7$?!#(B
+$B$3$N9`$G$O!"9-$/MxMQ$5$l$?:G=i4|$N%P!<%8%g%s$N(B tar $B%W%m%0%i%`$N$R$H$D$G!"(B
+.At v7
+$B$K4^$^$l$k(B tar $B%3%^%s%I$H$7$F<BAu$5$l$?HG$K$D$$$F2r@b$7$^$9!#(B
 .Pp
-The header record for an old-style
+$B8E$$7A<0$N(B
 .Nm
-archive consists of the following:
+$B%"!<%+%$%V$N%X%C%@%l%3!<%I$O!"<!$N$h$&$J9=@.$G$9(B:
 .Bd -literal -offset indent
 struct header_old_tar {
 	char name[100];
@@ -90,109 +94,112 @@
 	char pad[255];
 };
 .Ed
-All unused bytes in the header record are filled with nulls.
+$B%X%C%@%l%3!<%ICf$NA4$F$NL$;HMQ%P%$%H$O%L%k$GKd$a$i$l$^$9!#(B
 .Bl -tag -width indent
 .It Va name
-Pathname, stored as a null-terminated string.
-Early tar implementations only stored regular files (including
-hardlinks to those files).
-One common early convention used a trailing "/" character to indicate
-a directory name, allowing directory permissions and owner information
-to be archived and restored.
+$B%Q%9L>!#(B
+$B%L%kJ8;z$G=*$o$kJ8;zNs$H$7$F5-O?$7$^$9!#(B
+$B=i4|$N(B tar $B<BAu$G$O!"DL>o%U%!%$%k(B ($B$=$l$i$X$N%O!<%I%j%s%/$b4^$`(B)
+$B$N$_J]B8$7$^$7$?!#(B
+$B6&DL$7$?=i4|$N<h$j7h$a$N0l$D$H$7$F!"(B "/" $BJ8;z$rB3$1$k$3$H$G%G%#%l%/%H%jL>$r(B
+$BI=$7!"%G%#%l%/%H%j$N%Q!<%_%C%7%g%s$H=jM-<T>pJs$rJ]B8!"Cj=P$G$-$k$H$5$l$^$7$?!#(B
 .It Va mode
-File mode, stored as an octal number in ASCII.
+$B%U%!%$%k%b!<%I!#(B
+8 $B?J?t$N%"%9%-!<J8;z$H$7$F5-O?$7$^$9!#(B
 .It Va uid , Va gid
-User id and group id of owner, as octal numbers in ASCII.
+$B=jM-<T$N%f!<%6(B id $B$H%0%k!<%W(B id $B!#(B
+8 $B?J?t$N%"%9%-!<J8;z$G$9!#(B
 .It Va size
-Size of file, as octal number in ASCII.
-For regular files only, this indicates the amount of data
-that follows the header.
-In particular, this field was ignored by early tar implementations
-when extracting hardlinks.
-Modern writers should always store a zero length for hardlink entries.
+$B%U%!%$%k$N%5%$%:!#(B
+8 $B?J?t$N%"%9%-!<J8;z$G$9!#(B
+$BDL>o%U%!%$%k$K8B$C$F$O!"$3$N%X%C%@$KB3$/%G!<%?$NNL$r<($7$^$9!#(B
+$BFC$K!"=i4|$N(B tar $B<BAu$G$O%O!<%I%j%s%/$rE83+$9$k:]!"$3$N%U%#!<%k%I$O(B
+$BL5;k$5$l$F$$$^$7$?!#(B
+$B8=Be$N:n@.%W%m%0%i%`$J$i!"%O!<%I%j%s%/$N%(%s%H%j$G$OD9$5(B 0 $B$r5-O?$9$Y$-$G$9!#(B
 .It Va mtime
-Modification time of file, as an octal number in ASCII.
-This indicates the number of seconds since the start of the epoch,
-00:00:00 UTC January 1, 1970.
-Note that negative values should be avoided
-here, as they are handled inconsistently.
+$B%U%!%$%k$NJQ99F|;~!#(B
+8 $B?J?t$N%"%9%-!<J8;z$G$9!#(B
+$B$3$l$O4p=`;~E@(B (epoch) $B$G$"$k(B $B6(Dj@$3&;~(B (UTC) 1970 $BG/(B 1 $B7n(B 1 $BF|(B 00:00:00
+$B$+$i$NIC?t$rI=$7$^$9!#(B
+$B$J$*!"Ii$NCM$OIT9gM}$K07$o$l$k$N$G!"$3$3$G$OHr$1$k$Y$-$G$9!#(B
 .It Va checksum
-Header checksum, stored as an octal number in ASCII.
-To compute the checksum, set the checksum field to all spaces,
-then sum all bytes in the header using unsigned arithmetic.
-This field should be stored as six octal digits followed by a null and a space
-character.
-Note that many early implementations of tar used signed arithmetic
-for the checksum field, which can cause interoperability problems
-when transferring archives between systems.
-Modern robust readers compute the checksum both ways and accept the
-header if either computation matches.
+$B%X%C%@$N%A%'%C%/%5%`!#(B
+8 $B?J?t$N%"%9%-!<J8;z$H$7$F5-O?$7$^$9!#(B
+$B%A%'%C%/%5%`$r7W;;$9$k$K$O!"$3$N%A%'%C%/%5%`%U%#!<%k%I$rA4$F6uGr$GKd$a!"(B
+$B%X%C%@$NA4$F$N%P%$%H$rId9fL5$7$N;;K!$G9g7W$7$^$9!#(B
+$B$3$N%U%#!<%k%I$O!"(B 6 $B7e$N(B 8 $B?J?t$K!"%L%kJ8;z$H6uGrJ8;z$,B3$/7A$G5-O?$9$k(B
+$BI,MW$,$"$j$^$9!#(B
+$B$J$*!"$4$/=i4|$N(B tar $B<BAu$G$O!"Id9f$D$-$N;;K!$r%A%'%C%/%5%`%U%#!<%k%I$K(B
+$BMQ$$$F$*$j!"$3$l$O%"!<%+%$%V$r%7%9%F%`4V$GE>Aw$9$k:]$KAj8_1?MQ@-$N(B
+$BLdBj$r0z$-5/$3$7$^$9!#(B
+$B8=Be$N7xO4$JFI$_=P$7%W%m%0%i%`$O!"N>J}$N7W;;K!$G%A%'%C%/%5%`$r7W;;$7$F!"(B
+$B$I$A$i$N7W;;K!$K$h$k%X%C%@$G$b<u$1IU$1$^$9!#(B
 .It Va linkflag , Va linkname
-In order to preserve hardlinks and conserve tape, a file
-with multiple links is only written to the archive the first
-time it is encountered.
-The next time it is encountered, the
+$B%O!<%I%j%s%/$rJ]B8$7%F!<%W$rO2Hq$7$J$$$?$a$K!"J#?t$N%j%s%/$r;}$D%U%!%$%k$O(B
+$B:G=i$KI=$l$?;~$N$_!"%"!<%+%$%V$K=q$-9~$_$^$9!#(B
+$B<!$KI=$l$?;~!"(B
 .Va linkflag
-is set to an ASCII
+$B$K%"%9%-!<J8;z$N(B
 .Sq 1
-and the
+$B$,%;%C%H$5$l!"(B
 .Va linkname
-field holds the first name under which this file appears.
-(Note that regular files have a null value in the
+$B%U%#!<%k%I$K$3$N%U%!%$%k$,:G=i$KI=$l$?;~$N%U%!%$%kL>$r5-O?$7$^$9!#(B
+($B$J$*!"DL>o$N%U%!%$%k$N(B
 .Va linkflag
-field.)
+$B%U%#!<%k%I$O%L%kCM$G$9!#(B)
 .El
 .Pp
-Early tar implementations varied in how they terminated these fields.
-The tar command in
+$B=i4|$N(B tar $B<BAu$N!"$3$l$i$N%U%#!<%k%I$N=*C<J}K!$K$O$5$^$6$^$J$b$N$,(B
+$B$"$j$^$7$?!#(B
 .At v7
-used the following conventions (this is also documented in early BSD manpages):
-the pathname must be null-terminated;
-the mode, uid, and gid fields must end in a space and a null byte;
-the size and mtime fields must end in a space;
-the checksum is terminated by a null and a space.
-Early implementations filled the numeric fields with leading spaces.
-This seems to have been common practice until the
+$B$N(B tar $B%3%^%s%I$G$O!"<!$N$h$&$J<h$j7h$a$r$7$F$$$^$7$?(B ($B$3$l$O=i4|$N(B
+BSD man $B%Z!<%8$K$bJ8=q2=$5$l$F$$$^$9(B):
+$B%Q%9L>$O!"%L%kJ8;z$G=*$o$k$3$H!#(B
+mode, uid, gid $B%U%#!<%k%I$O6uGr$H%L%k%P%$%H$G=*$o$k$3$H!#(B
+size $B$H(B mtime $B%U%#!<%k%I$O6uGr$G=*$o$k$3$H!#(B
+$B%A%'%C%/%5%`$O%L%k$H6uGr$G=*$o$i$;$k!"$G$9!#(B
+$B=i4|$N<BAu$G$O!"?tCM%U%#!<%k%I$O6uGr$G;O$a$k7A$GKd$a$F$$$^$7$?!#(B
+$B$3$l$O(B
 .St -p1003.1
-standard was released.
-For best portability, modern implementations should fill the numeric
-fields with leading zeros.
-.Ss Pre-POSIX Archives
-An early draft of
+$BI8=`$,H/I=$5$l$k$^$G!"6&DL$N47=,$H$7$F9T$o$l$F$$$?$h$&$G$9!#(B
+$B0\?"@-$r:G$bNI$/$9$k$?$a$K!"8=Be$N<BAu$G$O!"?tCM%U%#!<%k%I$O(B
+0 $B$G;O$a$k7A$GKd$a$k$h$&$K$9$k$Y$-$G$9!#(B
+.Ss POSIX $B0JA0$N%"!<%+%$%V(B 
 .St -p1003.1-88
-served as the basis for John Gilmore's
+$B$N=i4|$N%I%i%U%H$O!"(B John Gilmore $B$N(B
 .Nm pdtar
-program and many system implementations from the late 1980s
-and early 1990s.
-These archives generally follow the POSIX ustar
-format described below with the following variations:
+$B%W%m%0%i%`$d!"(B 1980 $BG/Be=*$o$j$+$i(B 1990 $BG/Be;O$a$K$+$1$F$N%7%9%F%`$N(B
+$B<BAu$N4pAC$H$J$j$^$7$?!#(B
+$B$3$l$i$N%"!<%+%$%V$O!"8e$K=R$Y$k(B POSIX ustar $B%U%)!<%^%C%H$KBP$7$F!"(B
+$B<!$N$h$&$J0c$$$,$"$j$^$9(B:
 .Bl -bullet -compact -width indent
 .It
-The magic value is
+$B%^%8%C%/CM$O(B
 .Dq ustar\ \&
-(note the following space).
-The version field contains a space character followed by a null.
+$B$G$9(B ($B6uGr$,B3$$$F$$$kE@$KCm0U(B)$B!#(B
+version $B%U%#!<%k%I$O!"%L%k$,B3$/6uGrJ8;z$,4^$^$l$^$9!#(B
 .It
-The numeric fields are generally filled with leading spaces
-(not leading zeros as recommended in the final standard).
+$B?tCM%U%#!<%k%I$O!"0lHL$K6uGr$G;O$^$k7A$GKd$a$i$l$F$$$^$9(B ($B:G=*I8=`$N$h$&$K!"(B
+0 $B$G;O$^$k7A$G$O$J$$(B)$B!#(B
 .It
-The prefix field is often not used, limiting pathnames to
-the 100 characters of old-style archives.
+prefix $B%U%#!<%k%I$O$7$P$7$PMxMQ$5$l$:!"8E$$7A<0$N%"!<%+%$%V$N$h$&$K!"(B
+$B%Q%9L>$O(B 100 $BJ8;z$^$G$K@)8B$5$l$F$$$^$9!#(B
 .El
-.Ss POSIX ustar Archives
+.Ss POSIX ustar $B%"!<%+%$%V(B
 .St -p1003.1-88
-defined a standard tar file format to be read and written
-by compliant implementations of
+$B$O!"BP1~$7$?(B
 .Xr tar 1
-and
-.Xr pax 1 .
-This format is often called the
+$B$*$h$S(B
+.Xr pax 1
+$B<BAu$GFI$_=q$-$,=PMh$k!"I8=`E*$J(B tar $B%U%!%$%k%U%)!<%^%C%H$r(B
+$BDj5A$7$F$$$^$9!#(B
+$B$3$N%U%)!<%^%C%H$O!"%X%C%@Cf$N%^%8%C%/CM$+$i$7$P$7$P(B
 .Dq ustar
-format, after the magic value used
-in the header.
-(The name is an acronym for
-.Dq Unix Standard TAR. )
-It extends the historic format with new fields:
+$B%U%)!<%^%C%H$H$b8F$P$l$^$9!#(B
+($B$3$NL>A0$O(B
+.Dq Unix Standard TAR
+$B$NF,J8;z$G$9!#(B)
+$B$3$l$O:#$^$G$N%U%)!<%^%C%H$r?7$7$$%U%#!<%k%I$G3HD%$7$?$b$N$G$9(B:
 .Bd -literal -offset indent
 struct header_posix_ustar {
 	char name[100];
@@ -216,248 +223,235 @@
 .Ed
 .Bl -tag -width indent
 .It Va typeflag
-Type of entry.
-POSIX extended the earlier
+$B%(%s%H%j$N<oN`!#(B
+POSIX $B$O=i4|$N(B
 .Va linkflag
-field with several new type values:
+$B%U%#!<%k%I$r$$$/$D$+$N?7$7$$CM$G3HD%$7$^$7$?(B:
 .Bl -tag -width indent -compact
 .It Dq 0
-Regular file.
-NULL should be treated as a synonym, for compatibility purposes.
+$BDL>o%U%!%$%k!#(B
+$B8_49@-$r<h$k$?$a$K!"(B NULL $B$bF15A$H$7$F07$&$Y$-$G$9!#(B
 .It Dq 1
-Hard link.
+$B%O!<%I%j%s%/!#(B
 .It Dq 2
-Symbolic link.
+$B%7%s%\%j%C%/%j%s%/!#(B
 .It Dq 3
-Character device node.
+$B%-%c%i%/%?7?%G%P%$%9%N!<%I!#(B
 .It Dq 4
-Block device node.
+$B%V%m%C%/7?%G%P%$%9%N!<%I!#(B
 .It Dq 5
-Directory.
+$B%G%#%l%/%H%j!#(B
 .It Dq 6
-FIFO node.
+FIFO $B7?%N!<%I!#(B
 .It Dq 7
-Reserved.
-.It Other
-A POSIX-compliant implementation must treat any unrecognized typeflag value
-as a regular file.
-In particular, writers should ensure that all entries
-have a valid filename so that they can be restored by readers that do not
-support the corresponding extension.
-Uppercase letters "A" through "Z" are reserved for custom extensions.
-Note that sockets and whiteout entries are not archivable.
+$BM=Ls!#(B
+.It $B$3$NB>(B
+POSIX $B8_49<BAu$G$O!"M}2r$G$-$J$$$"$i$f$k(B typeflag $BCM$ODL>o%U%!%$%k$H$7$F(B
+$B07$o$J$1$l$P$J$j$^$;$s!#(B
+$BFC$K!":n@.%W%m%0%i%`$O!"BP1~$9$k3HD%5!G=$r%5%]!<%H$7$F$$$J$$FI$_=P$7%W%m%0%i%`(B
+$B$G$"$C$F$b!"$-$A$s$HE83+$G$-$k$h$&$J3N<B$J%U%!%$%kL>$rA4$F$N%(%s%H%j$K(B
+$B$D$1$k$h$&$KJ]>Z$9$kI,MW$,$"$j$^$9!#(B
+$BBgJ8;z%l%?!<$N(B "A" $B$+$i(B "Z" $B$O%+%9%?%`3HD%$N$?$a$KM=Ls$5$l$F$$$^$9!#(B
+$B$J$*!"%=%1%C%H$H%[%o%$%H%"%&%H%(%s%H%j$O%"!<%+%$%V$G$-$^$;$s!#(B
 .El
-It is worth noting that the
 .Va size
-field, in particular, has different meanings depending on the type.
-For regular files, of course, it indicates the amount of data
-following the header.
-For directories, it may be used to indicate the total size of all
-files in the directory, for use by operating systems that pre-allocate
-directory space.
-For all other types, it should be set to zero by writers and ignored
-by readers.
+$B%U%#!<%k%I$O!"FC$K$3$N%?%$%W$K$h$C$F0UL#$,0[$J$k$N$G!"$3$3$G?($l$F$*$-$^$9!#(B
+$BDL>o%U%!%$%k$KBP$7$F$O!"$b$A$m$s!"%X%C%@$KB3$/%G!<%?$NNL$r<($7$F$$$^$9!#(B
+$B%G%#%l%/%H%j$KBP$7$F$O!"%G%#%l%/%H%j%9%Z!<%9$r$"$i$+$8$a3d$jEv$F$k(B
+$B%*%Z%l!<%F%#%s%0%7%9%F%`$N$?$a$K!"%G%#%l%/%H%jCf$NA4$F$N%U%!%$%k$N9g7W%5%$%:$r(B
+$B<($9$N$K;H$o$l$^$9!#(B
+$B$3$l$i0J30$N%?%$%W$G$O!":n@.%W%m%0%i%`$O(B 0 $B$r%;%C%H$9$k$Y$-$G$9$7!"(B
+$BFI$_=P$7%W%m%0%i%`$OL5;k$9$k$Y$-$G$9!#(B
 .It Va magic
-Contains the magic value
+$B%^%8%C%/CM$G$"$k(B
 .Dq ustar
-followed by a NULL byte to indicate that this is a POSIX standard archive.
-Full compliance requires the uname and gname fields be properly set.
+$B$,!"%L%k%P%$%H$,B3$/7A$G4^$^$l$F$$$^$9!#$3$l$,(B POSIX $BI8=`%"!<%+%$%V$G$"$k$3$H$r(B
+$B<($7$F$$$^$9!#(B
+uname $B$H(B gname $B%U%#!<%k%I$,E,@Z$K%;%C%H$5$l$F$$$k$3$H$,5a$a$i$l$^$9!#(B
 .It Va version
-Version.
-This should be
+$B%P!<%8%g%s!#(B
+POSIX $BI8=`%"!<%+%$%V$G$O!"(B
 .Dq 00
-(two copies of the ASCII digit zero) for POSIX standard archives.
+($B%"%9%-!<?t;z$N(B 0 $B$,Fs$D(B) $B$G$"$k$Y$-$G$9!#(B
 .It Va uname , Va gname
-User and group names, as null-terminated ASCII strings.
-These should be used in preference to the uid/gid values
-when they are set and the corresponding names exist on
-the system.
+$B%f!<%65Z$S%0%k!<%WL>!#(B
+$B%L%kJ8;z$G=*$o$k%"%9%-!<J8;zNs$G$9!#(B
+$BBP1~$9$kL>A0$,%7%9%F%`$KB8:_$9$k;~$K$O!"$3$l$i$O(B uid/gid $B$NCM$h$j$b(B
+$BM%@h$7$F;HMQ$5$l$k$Y$-$G$9!#(B
 .It Va devmajor , Va devminor
-Major and minor numbers for character device or block device entry.
+$B%-%c%i%/%?7?%G%P%$%9%(%s%H%j$"$k$$$O%V%m%C%/7?%G%P%$%9%(%s%H%j$KBP$9$k!"(B
+$B%a%8%c!<HV9f$H%^%$%JHV9f$G$9!#(B
 .It Va prefix
-First part of pathname.
-If the pathname is too long to fit in the 100 bytes provided by the standard
-format, it can be split at any
+$B%Q%9L>$N:G=i$NItJ,!#(B
+$B%Q%9L>$,D92a$.$FI8=`%U%)!<%^%C%H$,Ds6!$9$k(B 100 $B%P%$%H$K<}$^$i$J$$>l9g!"(B
+$BG$0U$N(B
 .Pa /
-character with the first portion going here.
-If the prefix field is not empty, the reader will prepend
-the prefix value and a
+$BJ8;z$GJ,3d$7$F!":G=i$NItJ,$H$7$F$3$3$K5-O?$9$k$3$H$,=PMh$^$9!#(B
+prefix $B%U%#!<%k%I$,6u$G$J$$>l9g!"FI$_=P$7%W%m%0%i%`$O%U%k%Q%9L>$rF@$k$?$a$K!"(B
+prefix $B$NCM$H(B
 .Pa /
-character to the regular name field to obtain the full pathname.
+$BJ8;z$r!"DL>o$N(B name $B%U%#!<%k%I$NA0$KIU2C$7$^$9!#(B
 .El
 .Pp
-Note that all unused bytes must be set to
-.Dv NULL .
+$B$J$*!";HMQ$7$F$$$J$$A4$F$N%P%$%H$O(B
+.Dv NULL
+$B$r%;%C%H$7$J$1$l$P$J$j$^$;$s!#(B
 .Pp
-Field termination is specified slightly differently by POSIX
-than by previous implementations.
-The
+$B%U%#!<%k%I$N=*C<$O!"(B POSIX $B$G$O$=$l0JA0$N<BAu$H$O$9$3$70[$J$k7A$G(B
+$B;XDj$5$l$^$9!#(B
 .Va magic ,
 .Va uname ,
-and
 .Va gname
-fields must have a trailing
-.Dv NULL .
-The
+$B%U%#!<%k%I$O(B
+.Dv NULL
+$B$G=*$o$i$J$1$l$P$J$j$^$;$s!#(B
 .Va pathname ,
 .Va linkname ,
-and
 .Va prefix
-fields must have a trailing
+$B%U%#!<%k%I$O!"%U%#!<%k%IA4BN$r;HMQ$9$k>l9g$r=|$$$F(B
 .Dv NULL
-unless they fill the entire field.
-(In particular, it is possible to store a 256-character pathname if it
-happens to have a
+$B$G=*$o$i$J$1$l$P$J$j$^$;$s!#(B
+($BFC$K!"(B 156 $BHVL\$NJ8;z$,(B
 .Pa /
-as the 156th character.)
-POSIX requires numeric fields to be zero-padded in the front, and allows
-them to be terminated with either space or
+$B$G$"$k>l9g!"(B 256 $BJ8;z$N%Q%9L>$r5-O?$9$k$3$H$,=PMh$^$9!#(B)
+POSIX $B$G$O?tCM%U%#!<%k%I$O(B 0 $B$GKd$a$k7A$G;O$a$k$3$H$rMW5a$7$F$*$j!"(B
+$B$^$?=*C<$O6uGr$"$k$$$O(B
 .Dv NULL
-characters.
+$BJ8;z$N$I$A$i$G$b5vMF$7$F$$$^$9!#(B
 .Pp
-Currently, most tar implementations comply with the ustar
-format, occasionally extending it by adding new fields to the
-blank area at the end of the header record.
-.Ss Pax Interchange Format
-There are many attributes that cannot be portably stored in a
-POSIX ustar archive.
+$B8=:_$N$H$3$m!"$[$H$s$I$N(B tar $B<BAu$O(B ustar $B%U%)!<%^%C%H$KBP1~$7$F$*$j!"(B
+$B;~@^%X%C%@%l%3!<%I$N;D$j$NL$;HMQItJ,$K?7$7$$%U%#!<%k%I$rDI2C$7$F3HD%$7$F$$$^$9!#(B
+.Ss Pax $B8r49%U%)!<%^%C%H(B
+POSIX ustar $B%"!<%+%$%V$K!"2DHB@-$N$"$k7A$G5-O?$G$-$J$$B0@-$,B??t$"$j$^$9!#(B
 .St -p1003.1-2001
-defined a
-.Dq pax interchange format
-that uses two new types of entries to hold text-formatted
-metadata that applies to following entries.
-Note that a pax interchange format archive is a ustar archive in every
-respect.
-The new data is stored in ustar-compatible archive entries that use the
+$B$G$O!"B3$/%(%s%H%j$KE,MQ$9$k%F%-%9%H7A<0$N%a%?%G!<%?$r;}$C$?!"(B 2 $B$D$N?7$7$$(B
+$B%?%$%W$N%(%s%H%j$r;HMQ$9$k(B
+.Dq pax $B8r49%U%)!<%^%C%H(B
+$B$rDj5A$7$F$$$^$9!#(B
+$B$J$*!"(B pax $B8r49%U%)!<%^%C%H%"!<%+%$%V$O!"$"$i$f$kE@$G(B ustar $B%"!<%+%$%V$G$9!#(B
+$B?7$7$$%G!<%?$O(B ustar $B8_49$N%"!<%+%$%V%(%s%H%j$K!"(B typeflag $B$K(B
 .Dq x
-or
+$B$*$h$S(B
 .Dq g
-typeflag.
-In particular, older implementations that do not fully support these
-extensions will extract the metadata into regular files, where the
-metadata can be examined as necessary.
-.Pp
-An entry in a pax interchange format archive consists of one or
-two standard ustar entries, each with its own header and data.
-The first optional entry stores the extended attributes
-for the following entry.
-This optional first entry has an "x" typeflag and a size field that
-indicates the total size of the extended attributes.
-The extended attributes themselves are stored as a series of text-format
-lines encoded in the portable UTF-8 encoding.
-Each line consists of a decimal number, a space, a key string, an equals
-sign, a value string, and a new line.
-The decimal number indicates the length of the entire line, including the
-initial length field and the trailing newline.
-An example of such a field is:
+$B$r;HMQ$7$F5-O?$5$l$^$9!#(B
+$BFC$K!"$3$l$i$N3HD%5!G=$r40A4$K%5%]!<%H$7$J$$8E$$<BAu$G$O!"$3$N%a%?%G!<%?$r(B
+$BI,MW$K1~$8$F8!::$G$-$k$h$&!"DL>o%U%!%$%k$H$7$FE83+$9$k$G$7$g$&!#(B
+.Pp
+pax $B8r49%U%)!<%^%C%H%"!<%+%$%V$N%(%s%H%j$O!"(B 1 $B$D$+(B 2 $B$D$NI8=`(B ustar
+$B%(%s%H%j$r4^$_!"$=$l$>$l%X%C%@$H%G!<%?$r;}$A$^$9!#(B
+$B:G=i$N%*%W%7%g%s%(%s%H%j$O!"$3$l$KB3$/%(%s%H%j$KBP$9$k3HD%B0@-$r5-O?$7$F$$$^$9!#(B
+$B$3$N:G=i$N%*%W%7%g%s%(%s%H%j$O(B typeflag "x" $B$r;}$A!"(B size $B%U%#!<%k%I$O(B
+$B3HD%B0@-$N9g7W%5%$%:$rI=$7$F$$$^$9!#(B
+$B$3$N3HD%B0@-<+BN$O!"2DHB@-$N$"$k(B UTF-8 $B%(%s%3!<%G%#%s%0$GId9f2=$7$?!"(B
+$B%F%-%9%H7A<0$N9T$N=89g$H$7$F5-O?$5$l$^$9!#(B
+$B3F9T$O(B 10 $B?J?t!"6uGr!"%-!<J8;zNs!"Ey9f5-9f!"CMJ8;zNs!"2~9T$G9=@.$5$l$F(B
+$B$$$^$9!#(B
+10 $B?J?t$O!"9TA4BN$ND9$5$rI=$7!"$3$l$K$O$3$ND9$5%U%#!<%k%I<+?H$H2~9T$r(B
+$B4^$s$G$$$^$9!#(B
+$B%U%#!<%k%I$NNc$G$9(B:
 .Dl 25 ctime=1084839148.1212\en
-Keys in all lowercase are standard keys.
-Vendors can add their own keys by prefixing them with an all uppercase
-vendor name and a period.
-Note that, unlike the historic header, numeric values are stored using
-decimal, not octal.
-A description of some common keys follows:
+$BA4$F>.J8;z$N%-!<$OI8=`%-!<$G$9!#(B
+$B%Y%s%@$O!"A4$FBgJ8;z$N%Y%s%@L>$H%T%j%*%I$G;O$^$k!"FH<+$N%-!<$rDI2C$9$k$3$H$,(B
+$B$G$-$^$9!#(B
+$B$J$*!":#$^$G$N%X%C%@$H$O0[$J$j!"?tCM$O(B 8 $B?J?t$G$O$J$/!"(B 10 $B?J?t$G(B
+$B5-O?$5$l$^$9!#(B
+$B0J2<$O$$$/$D$+$N6&DL%-!<$K$D$$$F=R$Y$F$$$^$9!#(B
 .Bl -tag -width indent
 .It Cm atime , Cm ctime , Cm mtime
-File access, inode change, and modification times.
-These fields can be negative or include a decimal point and a fractional value.
+$B%U%!%$%k$N%"%/%;%9;~9o!"(B inode $BJQ99;~9o!"$*$h$S=$@5;~9o!#(B
+$BIi$NCM!"$b$7$/$O>.?tE@$dJ,?tCM$,;HMQ$G$-$^$9!#(B
 .It Cm uname , Cm uid , Cm gname , Cm gid
-User name, group name, and numeric UID and GID values.
-The user name and group name stored here are encoded in UTF8
-and can thus include non-ASCII characters.
-The UID and GID fields can be of arbitrary length.
+$B%f!<%6L>!"%0%k!<%WL>!"(B UID $B$*$h$S(B GID $B$N?tCM!#(B
+$B$3$3$K5-O?$9$k%f!<%6L>$H%0%k!<%WL>$O(B UTF8 $B$GId9f2=$5$l$k$N$G!"Hs%"%9%-!<J8;z$r(B
+$B4^$a$k$3$H$,$G$-$^$9!#(B
+UID $B$*$h$S(B GID $B%U%#!<%k%I$O!"G$0U$ND9$5$K=PMh$^$9!#(B
 .It Cm linkpath
-The full path of the linked-to file.
-Note that this is encoded in UTF8 and can thus include non-ASCII characters.
+$B%U%!%$%k$K%j%s%/$9$k%U%k%Q%9!#(B
+$B$J$*!"$3$l$O(B UTF8 $B$GId9f2=$5$l$k$N$G!"Hs%"%9%-!<J8;z$r4^$a$k$3$H$,=PMh$^$9!#(B
 .It Cm path
-The full pathname of the entry.
-Note that this is encoded in UTF8 and can thus include non-ASCII characters.
+$B%(%s%H%j$N%U%k%Q%9L>!#(B
+$B$J$*!"$3$l$O(B UTF8 $B$GId9f2=$5$l$k$N$G!"Hs%"%9%-!<J8;z$r4^$a$k$3$H$,=PMh$^$9!#(B
 .It Cm realtime.* , Cm security.*
-These keys are reserved and may be used for future standardization.
+$B$3$l$i$N%-!<$OM=Ls:Q$_$N$b$N$G!">-Mh$NI8=`2=$K$h$jMxMQ$5$l$k$G$7$g$&!#(B
 .It Cm size
-The size of the file.
-Note that there is no length limit on this field, allowing conforming
-archives to store files much larger than the historic 8GB limit.
+$B%U%!%$%k$N%5%$%:!#(B
+$B$J$*!"$3$N%U%#!<%k%I$KD9$5$N@)8B$O$J$$$N$G!"%"!<%+%$%V$K:#$^$G$N@)8B$N(B
+8GB $B$h$j$bBg$-$J%U%!%$%k$rJ]B8$5$;$k$3$H$,2DG=$G$9!#(B
 .It Cm SCHILY.*
-Vendor-specific attributes used by Joerg Schilling's
+Joerg Schilling $B$N(B
 .Nm star
-implementation.
+$B<BAu$G;H$o$l$k%Y%s%@8GM-$NB0@-!#(B
 .It Cm SCHILY.acl.access , Cm SCHILY.acl.default
-Stores the access and default ACLs as textual strings in a format
-that's an extension of the format specified by POSIX.1e draft 17.
-In particular, each user or group access specification can include a fourth
-colon-separated field with the numeric UID or GID.
-This allows ACLs to be restored on systems that may not have complete
-user or group information available (such as when NIS/YP or LDAP services
-are temporarily unavailable).
+POSIX.1e draft 17 $B$K5-=R$5$l$F$$$k%U%)!<%^%C%H$r3HD%$7$?$b$N$G!"(B
+$B%"%/%;%9$H%G%U%)%k%H$N(B ACL $B$r!"%F%-%9%H7A<0$NJ8;zNs$G5-O?$7$?$b$N!#(B
+$BFC$K!"3F%f!<%6$^$?$O%0%k!<%W$N%"%/%;%9L@:Y$r!"%3%m%s$G(B 4 $B$D$K6h@Z$C$?(B
+$B%U%#!<%k%I$G(B UID $B$^$?$O(B GID $B?tCM$H6&$K4^$a$k$3$H$,=PMh$^$9!#(B
+$B$3$l$K$h$j!"40A4$J%f!<%6Kt$O%0%k!<%W>pJs$,L5$$>l9g$G$b!"%7%9%F%`>e$G(B
+ACL $B$NI|85$,$G$-$^$9(B (NIS/YP $B$"$k$$$O(B LDAP $B%5!<%S%9$,0l;~E*$KMxMQ$G$-$J$$>l9g(B
+$B$J$I(B)$B!#(B
 .It Cm SCHILY.devminor , Cm SCHILY.devmajor
-The full minor and major numbers for device nodes.
+$B%G%P%$%9%N!<%I$N40A4$J%^%$%J$H%a%8%c!<HV9f!#(B
 .It Cm SCHILY.dev, Cm SCHILY.ino , Cm SCHILY.nlinks
-The device number, inode number, and link count for the entry.
-In particular, note that a pax interchange format archive using Joerg
-Schilling's
+$B%G%P%$%9HV9f!"(B inode $BHV9f!"$*$h$S%(%s%H%j$N%j%s%/%+%&%s%H!#(B
+$BFC$K!"(B Joerg Schilling $B$N(B
 .Cm SCHILY.*
-extensions can store all of the data from
-.Va struct stat .
+$B3HD%$rMQ$$$F!"(B pax $B8r49%U%)!<%^%C%H%"!<%+%$%V$K(B
+.Va struct stat
+$B$N%G!<%?$rA4$FJ]B8$9$k$3$H$,=PMh$^$9!#(B
 .It Cm VENDOR.*
-XXX document other vendor-specific extensions XXX
+XXX $BB>$N%Y%s%@8GM-3HD%$K4X$9$k%I%-%e%a%s%H(B XXX
 .El
 .Pp
-Any values stored in an extended attribute override the corresponding
-values in the regular tar header.
-Note that compliant readers should ignore the regular fields when they
-are overridden.
-This is important, as existing archivers are known to store non-compliant
-values in the standard header fields in this situation.
-There are no limits on length for any of these fields.
-In particular, numeric fields can be arbitrarily large.
-All text fields are encoded in UTF8.
-Compliant writers should store only portable 7-bit ASCII characters in
-the standard ustar header and use extended
-attributes whenever a text value contains non-ASCII characters.
+$B3HD%B0@-$K$h$j5-O?$5$l$?CM$O!"DL>o$N(B tar $B%X%C%@$NBP1~$9$kCM$r>e=q$-$7$^$9!#(B
+$B$J$*!"BP1~$9$kFI$_=P$7%W%m%0%i%`$J$i!">e=q$-$,$5$l$k$J$i$PDL>o%U%#!<%k%I$r(B
+$BL5;k$9$k$Y$-$G$9!#(B
+$B4{B8$N%"!<%+%$%P$O$3$N$h$&$J>r7o$K$*$$$F!"I8=`$N%X%C%@%U%#!<%k%I$K8_49@-$NL5$$(B
+$BCM$r5-O?$9$k$3$H$,CN$i$l$F$$$k$N$G!"$3$NE@$O=EMW$G$9!#(B
+$B$3$l$i$N%U%#!<%k%I$K$O!"D9$5$N@)8B$O$"$j$^$;$s!#(B
+$BFC$K!"?tCM%U%#!<%k%I$OG$0U$NBg$-$5$K$9$k$3$H$,=PMh$^$9!#(B
+$BA4$F$N%F%-%9%H%U%#!<%k%I$O!"(B UTF8 $B$GId9f2=$5$l$^$9!#(B
+$BBP1~$9$k:n@.%W%m%0%i%`$O!"I8=`(B ustar $B%X%C%@$K$O2DHB@-$N$"$k(B 7 $B%S%C%H%"%9%-!<(B
+$BJ8;z$N$_$r5-O?$9$k$Y$-$G!"%F%-%9%HCM$KHs%"%9%-!<J8;z$,4^$^$l$k>l9g$N$_$K!"(B
+$B3HD%B0@-$r;HMQ$9$k$Y$-$G$9!#(B
 .Pp
-In addition to the
+$B$3$l$^$G$K=R$Y$?(B
 .Cm x
-entry described above, the pax interchange format
-also supports a
+$B%(%s%H%j$K2C$($F!"(B pax $B8r49%U%)!<%^%C%H$O$^$?(B
 .Cm g
-entry.
-The
+$B%(%s%H%j$b%5%]!<%H$7$F$$$^$9!#(B
 .Cm g
-entry is identical in format, but specifies attributes that serve as
-defaults for all subsequent archive entries.
-The
+$B%(%s%H%j$OF1MM$N7A<0$G$9$,!"$3$l$KB3$/A4$F$N%"!<%+%$%V%(%s%H%j$KM?$($k(B
+$B%G%U%)%k%H$NB0@-$r;XDj$9$k$b$N$G$9!#(B
+$B$3$N(B
 .Cm g
-entry is not widely used.
+$B%(%s%H%j$O$"$^$j9-HO$K$OMQ$$$i$l$F$$$^$;$s!#(B
 .Pp
-Besides the new
+$B?7$7$$(B
 .Cm x
-and
+$B$H(B
 .Cm g
-entries, the pax interchange format has a few other minor variations
-from the earlier ustar format.
-The most troubling one is that hardlinks are permitted to have
-data following them.
-This allows readers to restore any hardlink to a file without
-having to rewind the archive to find an earlier entry.
-However, it creates complications for robust readers, as it is no longer
-clear whether or not they should ignore the size field for hardlink entries.
-.Ss GNU Tar Archives
-The GNU tar program started with a pre-POSIX format similar to that
-described earlier and has extended it using several different mechanisms:
-It added new fields to the empty space in the header (some of which was later
-used by POSIX for conflicting purposes);
-it allowed the header to be continued over multiple records;
-and it defined new entries that modify following entries
-(similar in principle to the
+$B%(%s%H%j$NB>$K$b!"(B pax $B8r49%U%)!<%^%C%H$O=i4|$N(B ustar $B%U%)!<%^%C%H$KBP$7$F!"(B
+$BB>$N:Y$+$$JQ2=$,$$$/$D$+$"$j$^$9!#(B
+$B:G$bLq2p$J$3$H$N0l$D$O!"%O!<%I%j%s%/$,$3$l$KB3$/%G!<%?$r;}$D$3$H$r5v2D$5$l$F(B
+$B$$$k$3$H$G$9!#(B
+$B$3$l$OFI$_=P$7%W%m%0%i%`$K!":G=i$N%(%s%H%j$rC5$9$?$a$K%"!<%+%$%V$r4,La$9$3$H(B
+$B$J$/!"$"$k%U%!%$%k$KBP$9$k%O!<%I%j%s%/$rE83+$9$k$N$r2DG=$K$7$^$9!#(B
+$B$7$+$7!"7xO4$JFI$_=P$7%W%m%0%i%`$KBP$7!"%O!<%I%j%s%/%(%s%H%j$N(B size $B%U%#!<%k%I$r(B
+$BL5;k$9$k$Y$-$+$I$&$+$O$C$-$j$H$7$J$$$H$$$&:.Mp$r@8$8$^$9!#(B
+.Ss GNU Tar $B%"!<%+%$%V(B
+GNU tar $B%W%m%0%i%`$O=i4|$K5-=R$5$l$?(B POSIX $B0JA0$N%U%)!<%^%C%H$K;w$?$b$N$+$i(B
+$B;O$^$j!"$$$/$D$+$N0[$J$k5!9=$G3HD%$5$l$F$$$^$9!#(B
+$B%X%C%@$NL$;HMQ6u4V$K?7$7$$%U%#!<%k%I$rDI2C(B ($B$=$l$i$N$$$/$D$+$O!"8e$K(B POSIX
+$B$K$FL7=b$9$kL\E*$G;HMQ$5$l$F$$$^$9(B)$B!#(B
+$B%X%C%@$,J#?t$N%l%3!<%I$K8Y$k$3$H$rG'$a$F$$$k!#$=$7$FB3$/%(%s%H%j$r=$>~$9$k(B
+$B?7$7$$%(%s%H%j$rDI2C(B ($BBgBN$K$*$$$FA0=R$N(B
 .Cm x
-entry described above, but each GNU special entry is single-purpose,
-unlike the general-purpose
+$B%(%s%H%j$K;w$F$$$^$9$,!"B?L\E*$J(B
 .Cm x
-entry).
-As a result, GNU tar archives are not POSIX compatible, although
-more lenient POSIX-compliant readers can successfully extract most
-GNU tar archives.
+$B%(%s%H%j$H$O0c$$!"(B GNU $B$N3FFCJL%(%s%H%j$OC10lL\E*$G$9(B)$B!"$H$$$C$?$b$N$G$9!#(B
+$B7k2L$H$7$F!"(B GNU tar $B%"!<%+%$%V$O!"$+$J$j42Bg$J(B POSIX $BBP1~$NFI$_=P$7(B
+$B%W%m%0%i%`$J$i$P!"BgDq$N(B GNU tar $B%"!<%+%$%V$r$&$^$/E83+$9$k$3$H$,(B
+$B$G$-$k$H$O$$$(!"(B POSIX $B$H$O8_49@-$,$"$j$^$;$s!#(B
 .Bd -literal -offset indent
 struct header_gnu_tar {
 	char name[100];
@@ -491,124 +485,111 @@
 .Ed
 .Bl -tag -width indent
 .It Va typeflag
-GNU tar uses the following special entry types, in addition to
-those defined by POSIX:
+GNU tar $B$O!"(B POSIX $B$GDj5A$5$l$F$$$k$b$N$K2C$(!"0J2<$NFCJL%(%s%H%j%?%$%W$r(B
+$B;HMQ$7$^$9(B:
 .Bl -tag -width indent
 .It "7"
-GNU tar treats type "7" records identically to type "0" records,
-except on one obscure RTOS where they are used to indicate the
-pre-allocation of a contiguous file on disk.
+GNU tar $B$O!"$"$kL5L>$N(B RTOS $B$G!"%G%#%9%/>e$KO"B3$7$?%U%!%$%k$r$"$i$+$8$a(B
+$B3d$jEv$F$k$?$a$K;HMQ$9$k$N$r=|$$$F!"%?%$%W(B "7" $B$r%?%$%W(B "0" $B$H$^$C$?$/F1Ey$K(B
+$B07$$$^$9!#(B
 .It "D"
-This indicates a directory entry.
-Unlike the POSIX-standard "5"
-typeflag, the header is followed by data records listing the names
-of files in this directory.
-Each name is preceded by an ASCII "Y"
-if the file is stored in this archive or "N" if the file is not
-stored in this archive.
-Each name is terminated with a null, and
-an extra null marks the end of the name list.
-The purpose of this
-entry is to support incremental backups; a program restoring from
-such an archive may wish to delete files on disk that did not exist
-in the directory when the archive was made.
-.Pp
-Note that the "D" typeflag specifically violates POSIX, which requires
-that unrecognized typeflags be restored as normal files.
-In this case, restoring the "D" entry as a file could interfere
-with subsequent creation of the like-named directory.
+$B%G%#%l%/%H%j%(%s%H%j$r0UL#$7$^$9!#(B
+POSIX $BI8=`$N(B typeflag "5" $B$H$O0[$J$j!"$3$N%X%C%@$K$O%G%#%l%/%H%jFb$K$"$k(B
+$B%U%!%$%k$NL>A0$N0lMw%G!<%?$,B3$-$^$9!#(B
+$B$b$7%U%!%$%k$,$3$N%"!<%+%$%V$KJ]B8$5$l$l$P!"%U%!%$%kL>$N@hF,$K%"%9%-!<J8;z$N(B
+"Y" $B$,DI2C$5$l$^$9$7!"J]B8$5$l$J$1$l$P!"(B "N" $B$,DI2C$5$l$^$9!#(B
+$BL>A0$O$=$l$>$l%L%k$G=*C<$5$l!"L>A0$N0lMw$N=*C<$K$ODI2C$N%L%k$,%^!<%/$5$l$^$9!#(B
+$B$3$N%(%s%H%j$NL\E*$O!"%$%s%/%j%a%s%?%k%P%C%/%"%C%W$r%5%]!<%H$9$k$3$H$K$"$j$^$9!#(B
+$B%W%m%0%i%`$,$3$N$h$&$J%"!<%+%$%V$rE83+$9$k>l9g!"%"!<%+%$%V$,:n@.$5$l$?;~$K(B
+$B%G%#%l%/%H%jFb$KB8:_$7$J$+$C$?%U%!%$%k$r!"%G%#%9%/$+$i:o=|$7$h$&$H$9$k$G$7$g$&!#(B
+.Pp
+$B$J$*!"M}2r$G$-$J$$(B typeflag $B$,DL>o%U%!%$%k$H$7$FE83+$5$l$k$3$H$rMW5a$7$F$$$k(B
+POSIX $B$K!"$3$N(B typeflag "D" $B$OL@3N$K0cH?$7$F$$$^$9!#(B
+$B$3$N>l9g!"DL>o%U%!%$%k$H$7$F(B "D" $B%(%s%H%j$,E83+$5$l$k$H!"$=$N$"$H$KF1L>$N(B
+$B%G%#%l%/%H%j$r:n@.$9$k$N$rK8$2$k2DG=@-$,$"$j$^$9!#(B
 .It "K"
-The data for this entry is a long linkname for the following regular entry.
+$B$3$N%(%s%H%j$KBP$9$k%G!<%?$O!"B3$/DL>o%(%s%H%j$KBP$9$kD9$$(B linkname $B$G$9!#(B
 .It "L"
-The data for this entry is a long pathname for the following regular entry.
+$B$3$N%(%s%H%j$KBP$9$k%G!<%?$O!"B3$/DL>o%(%s%H%j$KBP$9$kD9$$%Q%9L>$G$9!#(B
 .It "M"
-This is a continuation of the last file on the previous volume.
-GNU multi-volume archives guarantee that each volume begins with a valid
-entry header.
-To ensure this, a file may be split, with part stored at the end of one volume,
-and part stored at the beginning of the next volume.
-The "M" typeflag indicates that this entry continues an existing file.
-Such entries can only occur as the first or second entry
-in an archive (the latter only if the first entry is a volume label).
-The
+$BA0$N%\%j%e!<%`$N:G8e$N%U%!%$%k$NB3$-$G$9!#(B
+GNU $B%^%k%A%\%j%e!<%`%"!<%+%$%V$O!"3F%\%j%e!<%`$,@5$7$$%(%s%H%j%X%C%@$G(B
+$B;O$^$k$3$H$rJ]>Z$7$F$$$^$9!#(B
+$B$3$l$r3N<B$K$9$k$?$a!"%U%!%$%k$NJ,3d$O!"$"$k%\%j%e!<%`$N:G8e$H!"(B
+$B$3$l$KB3$/%\%j%e!<%`$N:G=i$KJ]B8$5$l$k$H8@$&7A$G$J$5$l$^$9!#(B
+$B$3$N(B typeflag "M" $B$O!"$3$N%(%s%H%j$,4{B8$N%U%!%$%k$NB3$-$G$"$k$3$H$r(B
+$B<($7$F$$$^$9!#(B
+$B$3$N%(%s%H%j$O!"%"!<%+%$%V$N:G=i$+FsHVL\$N%(%s%H%j$K$N$_I=$l$^$9(B
+($B8e<T$O:G=i$N%(%s%H%j$,%\%j%e!<%`%i%Y%k$G$"$k>l9g$N$_(B)$B!#(B
 .Va size
-field specifies the size of this entry.
-The
+$B%U%#!<%k%I$O!"$3$N%(%s%H%j$N%5%$%:$rI=$7$F$$$^$9!#(B
+369-380 $B%P%$%HL\$K$"$k(B
 .Va offset
-field at bytes 369-380 specifies the offset where this file fragment
-begins.
-The
+$B%U%#!<%k%I$O!"$3$N%U%!%$%k$NCGJR$,;O$^$k%*%U%;%C%H$rI=$7$F$$$^$9!#(B
 .Va realsize
-field specifies the total size of the file (which must equal
+$B%U%#!<%k%I$O!"$3$N%U%!%$%k$N9g7W%5%$%:$rI=$7$F$$$^$9(B ($B$3$l$O(B
 .Va size
-plus
-.Va offset ) .
-When extracting, GNU tar checks that the header file name is the one it is
-expecting, that the header offset is in the correct sequence, and that
-the sum of offset and size is equal to realsize.
-FreeBSD's version of GNU tar does not handle the corner case of an
-archive's being continued in the middle of a long name or other
-extension header.
+$B$H(B
+.Va offset
+$B$rB-$7$?$b$N$HF1$8$G$J$1$l$P$$$1$^$;$s(B)$B!#(B
+$BE83+$N;~!"(B GNU tar $B$O%X%C%@$N%U%!%$%kL>$,M=B,$7$?$b$N$+$I$&$+%A%'%C%/$7!"(B
+$B%X%C%@$N(B offset $B$,@5$7$/B3$$$F$$$k$+%A%'%C%/$7!"$=$7$F(B offset $B$H(B size $B$N(B
+$B9g7W$,(B realsize $B$HEy$7$$$+%A%'%C%/$7$^$9!#(B
+FreeBSD $BHG$N(B GNU tar $B$O!"(B $BD9$$L>A0$dB>$N3HD%%X%C%@$NCf$GB3$/$h$&$J%"!<%+%$%V$O(B
+$B07$$$^$;$s!#(B
 .It "N"
-Type "N" records are no longer generated by GNU tar.
-They contained a
-list of files to be renamed or symlinked after extraction; this was
-originally used to support long names.
-The contents of this record
-are a text description of the operations to be done, in the form
+$B%?%$%W(B "N" $B%l%3!<%I$r(B GNU tar $B$,@8@.$9$k$3$H$O$b$&$"$j$^$;$s!#(B
+$B$3$l$OE83+$r$7$?8e$K!"%j%M!<%`Kt$O%7%s%\%j%C%/%j%s%/$rD%$k%U%!%$%k$N0lMw$r(B
+$B4^$s$G$$$^$9!#$3$l$O85!9$OD9$$L>A0$r%5%]!<%H$9$k$N$K;HMQ$5$l$^$7$?!#(B
+$B$3$N%l%3!<%I$NFbMF$O!"9T$o$l$k$Y$-A`:n$r%F%-%9%H$G5-=R$7$?$b$N$G!"7A<0$O(B
 .Dq Rename %s to %s\en
-or
-.Dq Symlink %s to %s\en ;
-in either case, both
-filenames are escaped using K&R C syntax.
+$B$^$?$O(B
+.Dq Symlink %s to %s\en
+$B$H$J$C$F$$$^$9!#(B
+$B$I$A$i$N>l9g$b!"N>J}$N%U%!%$%kL>$O(B K&R C $B7A<0$G%(%9%1!<%W$5$l$^$9!#(B
 .It "S"
-This is a
-.Dq sparse
-regular file.
-Sparse files are stored as a series of fragments.
-The header contains a list of fragment offset/length pairs.
-If more than four such entries are required, the header is
-extended as necessary with
+.Dq $BAB$J(B
+$BDL>o%U%!%$%k$G$9!#(B
+$BAB$J%U%!%$%k$OCGJR$N=89g$H$7$FJ]B8$5$l$^$9!#(B
+$B%X%C%@$OCGJR$N(B offset/length $B%Z%"$N0lMw$r4^$s$G$$$^$9!#(B
+$B$b$7$=$N$h$&$J%(%s%H%j$,(B 4 $B$D0J>eI,MW$J$i!"I,MW$K1~$8$F(B
 .Dq extra
-header extensions (an older format that's no longer used), or
+$B%X%C%@3HD%(B ($B4{$K;H$o$l$F$$$J$$8E$$%U%)!<%^%C%H$G$9(B)$B!"$b$7$/$O(B
 .Dq sparse
-extensions.
+$B3HD%$rMQ$$$F%X%C%@$r3HD%$7$^$9!#(B
 .It "V"
-The
+$B$3$N(B
 .Va name
-field should be interpreted as a tape/volume header name.
-This entry should generally be ignored on extraction.
+$B%U%#!<%k%I$O!"%F!<%W$^$?$O%\%j%e!<%`$N%X%C%@L>>N$H2r<a$9$k$Y$-$G$9!#(B
+$B$3$N%(%s%H%j$O0lHLE*$K!"E83+$N:]$K$OL5;k$5$l$k$Y$-$G$9!#(B
 .El
 .It Va magic
-The magic field holds the five characters
+$B$3$N(B magic $B%U%#!<%k%I$O!"(B
 .Dq ustar
-followed by a space.
-Note that POSIX ustar archives have a trailing null.
+$B$N(B 5 $BJ8;z$H6uGr$,B3$/7A$GJ];}$5$l$F$$$^$9!#(B
+$B$J$*!"(B POSIX ustar $B%"!<%+%$%V$G$O!"%L%k$,B3$$$F$$$^$9!#(B
 .It Va version
-The version field holds a space character followed by a null.
-Note that POSIX ustar archives use two copies of the ASCII digit
-.Dq 0 .
+$B$3$N(B version $B%U%#!<%k%I$O!"6uGrJ8;z$H%L%k$,B3$/7A$GJ];}$5$l$F$$$^$9!#(B
+$B$J$*!"(B POSIX ustar $B%"!<%+%$%V$G$O!"%"%9%-!<?t;z$N(B
+.Dq 0
+$B$r(B 2 $B$D;HMQ$7$F$$$^$9!#(B
 .It Va atime , Va ctime
-The time the file was last accessed and the time of
-last change of file information, stored in octal as with
-.Va mtime.
+$B:G8e$K%U%!%$%k$,%"%/%;%9$5$l$?;~9o$H!":G8e$K%U%!%$%k>pJs$,JQ99$5$l$?;~9o$G$9!#(B
+.Va mtime
+$B$N$h$&$K!"(B 8 $B?J?t$G5-O?$5$l$^$9!#(B
 .It Va longnames
-This field is apparently no longer used.
+$B$3$N%U%#!<%k%I$O!"$I$&$d$i4{$K;HMQ$5$l$F$$$J$$$h$&$G$9!#(B
 .It Sparse Va offset / Va numbytes
-Each such structure specifies a single fragment of a sparse
-file.
-The two fields store values as octal numbers.
-The fragments are each padded to a multiple of 512 bytes
-in the archive.
-On extraction, the list of fragments is collected from the
-header (including any extension headers), and the data
-is then read and written to the file at appropriate offsets.
+$B$3$N9=B$BN$O!"AB$J%U%!%$%k$NCGJR$N$R$H$D$r;XDj$7$^$9!#(B
+2 $B$D$N%U%#!<%k%I$O!"(B 8 $B?J?t$NCM$r5-O?$7$^$9!#(B
+$B%"!<%+%$%VFb$GCGJR$O$=$l$>$l!"(B512 $B%P%$%H$NG\?t$K%Q%G%#%s%0$5$l$^$9!#(B
+$BE83+$K$*$$$F!"CGJR$N0lMw$,%X%C%@(B ($B3HD%%X%C%@$b4^$`(B) $B$+$i=8$a$i$l!"(B
+$BFI$_=P$7$?%G!<%?$rE,@Z$J%*%U%;%C%H$G=q$-=P$7$^$9!#(B
 .It Va isextended
-If this is set to non-zero, the header will be followed by additional
+$B$b$7$3$l$,Hs(B 0 $B$K%;%C%H$5$l$?>l9g!"%X%C%@$,DI2C$N(B
 .Dq sparse header
-records.
-Each such record contains information about as many as 21 additional
-sparse blocks as shown here:
+$B%l%3!<%I$KB3$-$^$9!#(B
+$B$=$l$>$l$N%l%3!<%I$O0J2<$K<($9DI2C$N(B sparse $B%V%m%C%/(B 21 $B8D$J$I$r4^$s$G$$$^$9(B:
 .Bd -literal -offset indent
 struct gnu_sparse_header {
 	struct {
@@ -620,96 +601,92 @@
 };
 .Ed
 .It Va realsize
-A binary representation of the file's complete size, with a much larger range
-than the POSIX file size.
-In particular, with
+$B%P%$%J%j7A<0$G%U%!%$%k$N40A4$J%5%$%:$rI=$7$?$b$N$G!"(B POSIX $B$N%U%!%$%k(B
+$B%5%$%:$h$j$bHO0O$,$h$jBg$-$/$J$C$F$$$^$9!#(B
+$BFC$K!"(B
 .Cm M
-type files, the current entry is only a portion of the file.
-In that case, the POSIX size field will indicate the size of this
-entry; the
+$B%?%$%W$N%U%!%$%k$K$*$$$F$O!"8=:_$N%(%s%H%j$O%U%!%$%k$N0lItJ,$N$_$G$9!#(B
+$B$3$N>l9g!"(B POSIX $B$N(B size $B%U%#!<%k%I$O$3$N%(%s%H%j$N%5%$%:$rI=$7$F$*$j!"(B
 .Va realsize
-field will indicate the total size of the file.
+$B%U%#!<%k%I$O%U%!%$%k$NAm%5%$%:$rI=$7$F$$$^$9!#(B
 .El
 .Ss Solaris Tar
-XXX More Details Needed XXX
+XXX $B$h$j>\:Y$J$b$N$,I,MW(B XXX
 .Pp
-Solaris tar (beginning with SunOS XXX 5.7 ?? XXX) supports an
+Solaris $B$N(B tar (SunOS XXX 5.7 ?? XXX $B$+$i(B) $B$O!"(B pax $B8r49%U%)!<%^%C%H$H(B
+$B4pK\E*$K$ONI$/;w$?(B
 .Dq extended
-format that is fundamentally similar to pax interchange format,
-with the following differences:
+$B%U%)!<%^%C%H$r%5%]!<%H$7$F$$$^$9$,!"<!$N$h$&$J0c$$$,$"$j$^$9(B:
 .Bl -bullet -compact -width indent
 .It
-Extended attributes are stored in an entry whose type is
-.Cm X ,
-not
-.Cm x ,
-as used by pax interchange format.
-The detailed format of this entry appears to be the same
-as detailed above for the
+$B3HD%B0@-$O(B pax $B8r49%U%)!<%^%C%H$N$h$&$J(B
+.Cm x
+$B%?%$%W$G$O$J$/!"(B
+.Cm X
+$B%?%$%W$N%(%s%H%j$K5-O?$5$l$^$9!#(B
+$B$3$N%(%s%H%j$N%U%)!<%^%C%H$N>\:Y$O!"A0=R$7$?(B
 .Cm x
-entry.
+$B%(%s%H%j$HF1$8$b$N$N$h$&$K8+$($^$9!#(B
 .It
-An additional
+$BDI2C$N(B
 .Cm A
-entry is used to store an ACL for the following regular entry.
-The body of this entry contains a seven-digit octal number
-(whose value is 01000000 plus the number of ACL entries)
-followed by a zero byte, followed by the
-textual ACL description.
+$B%(%s%H%j$O!"B3$/DL>o%(%s%H%j$N(B ACL $B$r5-O?$9$k$N$K;HMQ$5$l$^$9!#(B
+$B$3$N%(%s%H%j$NK\BN$K$O!"%P%$%H(B 0 $B$,B3$/(B 7 $B7e$N(B 8 $B?J?t(B (ACL $B%(%s%H%j$NCM$K(B
+01000000 $B$rB-$7$?$b$N(B) $B$K!"%F%-%9%H7A<0$N(B ACL $B$N2r@b$,B3$-$^$9!#(B
 .El
-.Ss Other Extensions
-One common extension, utilized by GNU tar, star, and other newer
+.Ss $B$=$NB>$N3HD%(B
+GNU tar$B!"(B star$B!"$*$h$SB>$N?7$7$$(B
 .Nm
-implementations, permits binary numbers in the standard numeric
-fields.
-This is flagged by setting the high bit of the first character.
-This permits 95-bit values for the length and time fields
-and 63-bit values for the uid, gid, and device numbers.
-GNU tar supports this extension for the
-length, mtime, ctime, and atime fields.
-Joerg Schilling's star program supports this extension for
-all numeric fields.
-Note that this extension is largely obsoleted by the extended attribute
-record provided by the pax interchange format.
-.Pp
-Another early GNU extension allowed base-64 values rather
-than octal.
-This extension was short-lived and such archives are almost never seen.
-However, there is still code in GNU tar to support them; this code is
-responsible for a very cryptic warning message that is sometimes seen when
-GNU tar encounters a damaged archive.
-.Sh SEE ALSO
+$B<BAu$GMxMQ$5$l$F$$$k6&DL$N3HD%$N0l$D$O!"I8=`$N?tCM%U%#!<%k%I$G$N%P%$%J%jCM$N(B
+$B;HMQ$r5v2D$7$F$$$k$H$$$&$b$N$G$9!#(B
+$B$3$l$O:G=i$NJ8;z$N9b0L%S%C%H$r%;%C%H$9$k$3$H$GM-8z$K$J$j$^$9!#(B
+$B$3$l$G(B length $B$*$h$S(B time $B%U%#!<%k%I$G(B 95 $B%S%C%H$NCM$,!"(B
+uid, gid $B$*$h$S%G%P%$%9HV9f%U%#!<%k%I$G(B 63 $B%S%C%H$NCM$,;HMQ2DG=$K$J$j$^$9!#(B
+GNU tar $B$O$3$N3HD%$r(B length, mtime, ctime, atime $B%U%#!<%k%I$G(B
+$B%5%]!<%H$7$F$$$^$9!#(B
+Joerg Schilling $B$N(B star $B%W%m%0%i%`$O$3$N3HD%$rA4$F$N?tCM%U%#!<%k%I$G(B
+$B%5%]!<%H$7$F$$$^$9!#(B
+$B$J$*!"(B pax $B8r49%U%)!<%^%C%H$,3HD%B0@-%l%3!<%I$rDs6!$9$k$h$&$K$J$C$?$N$G!"(B
+$B$3$N3HD%$OBgItJ,$,5l<0$N$b$N$H$J$j$^$9!#(B
+.Pp
+$BB>$K!"=i4|$N(B GNU $B3HD%$O(B 8 $B?J?t$NBe$o$j$K(B base-64 $B$NCM$r5v2D$7$F$$$^$7$?!#(B
+$B$3$N3HD%$OC;L?$@$C$?$N$G!"$=$N$h$&$J%"!<%+%$%V$O$[$H$s$I8+$i$l$J$$$G$7$g$&!#(B
+$B$7$+$7$J$,$i!"(B GNU tar $B$N%W%m%0%i%`%3!<%I$O$^$@$3$l$r%5%]!<%H$7$F$$$^$9!#(B
+$B$3$N%3!<%I$O!"(B GNU tar $B$,2u$l$?%"!<%+%$%V$K=P$/$o$7$?;~$K!"(B $B;~!9$H$F$b(B
+$BHkL)$a$$$?7Y9p%a%C%;!<%8$r=P$9860x$K$J$C$F$$$^$9!#(B
+.Sh $B4XO"9`L\(B
 .Xr ar 1 ,
 .Xr pax 1 ,
 .Xr tar 1
-.Sh STANDARDS
-The
+.Sh $B5,3J(B
 .Nm tar
-utility is no longer a part of POSIX or the Single Unix Standard.
-It last appeared in
-.St -susv2 .
-It has been supplanted in subsequent standards by
-.Xr pax 1 .
-The ustar format is currently part of the specification for the
+$B%f!<%F%#%j%F%#$O!"4{$K(B POSIX $B$"$k$$$O(B Single Unix Standard $B$N0lIt$G$O(B
+$B$"$j$^$;$s!#(B
+$B$3$l$,:G8e$KEP>l$7$?$N$O(B
+.St -susv2
+$B$G$9!#(B
+$B$3$l$O8e$NI8=`$G(B
+.Xr pax 1
+$B$K<h$C$FBe$o$i$l$^$7$?!#(B
+ustar $B%U%)!<%^%C%H$O8=:_$O!"(B
 .Xr pax 1
-utility.
-The pax interchange file format is new with
-.St -p1003.1-2001 .
-.Sh HISTORY
-A
+$B%f!<%F%#%j%F%#$N5,3J$N0lIt$H$J$C$F$$$^$9!#(B
+pax $B8r49%U%!%$%k%U%)!<%^%C%H$O(B
+.St -p1003.1-2001
+$B$G?7$7$/$J$j$^$7$?!#(B
+.Sh $BNr;K(B
 .Nm tar
-command appeared in Seventh Edition Unix, which was released in January, 1979.
-It replaced the
-.Nm tp
-program from Fourth Edition Unix which in turn replaced the
+$B%3%^%s%I$O!"(B 1979 $BG/(B 1 $B7n$K%j%j!<%9$5$l$?(B Seventh Edition Unix $B$+$i(B
+$BEP>l$7$^$7$?!#(B
+$B$3$l$O(B First Edition Unix $B$N(B
 .Nm tap
-program from First Edition Unix.
-John Gilmore's
+$B%W%m%0%i%`$rCV$-49$($?!"(B Fourth Edition Unix $B$N(B
+.Nm tp
+$B$rCV$-49$($^$7$?!#(B
+John Gilmore $B$K$h$k%Q%V%j%C%/%I%a%$%s<BAu$N(B
 .Nm pdtar
-public-domain implementation (circa 1987) was highly influential
-and formed the basis of GNU tar.
-Joerg Shilling's
+(1987 $BG/:"(B) $B$OBgJQ$J1F6A$r5Z$\$7!"(B GNU tar $B$N85$K$J$j$^$7$?!#(B
+Joerg Shilling $B$K$h$k(B
 .Nm star
-archiver is another open-source (GPL) archiver (originally developed
-circa 1985) which features complete support for pax interchange
-format.
+$B%"!<%+%$%P$OJL$N%*!<%W%s%=!<%9(B (GPL) $B%"!<%+%$%P$G(B ($B:G=i$N3+H/$O(B 1985 $BG/:"(B)$B!"(B
+pax $B8r49%U%)!<%^%C%H$N40A4$J%5%]!<%H5!G=$,$"$j$^$9!#(B

---
Watanabe Kazuhiro (CQG00620@nifty.ne.jp)
