Differences between revisions 13 and 35 (spanning 22 versions)
Revision 13 as of 2005-02-10 08:08:01
Size: 1669
Editor: anonymous
Comment:
Revision 35 as of 2019-08-15 16:24:37
Size: 1185
Editor: nodiscc
Comment: unlink non existing page
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
In computing, the '''tar file format''' is a type of archive file format: the *T*ape *AR*chive format. These files are produced by the ["Unix"] command tar and were standardized by POSIX.1-1998 and later POSIX.1-2001.
#language en
~-Translation(s): [[it/TarBall|Italiano]]-~
Line 4: Line 4:
It is used widely to archive and unarchive files, which means to accumulate a large collection of files into a single archive file (packer), while preserving FileSystem information such as user and group permissions, dates, and ["directory"] structures. ----
Line 6: Line 6:
'''Commonly a tar file is referred to as a tarball . Tarballs are ["source"] code''', not binary ["image"] DebianPackage s. DebianPackage s can be downloaded and installed using AptGet . A [[http://en.wikipedia.org/wiki/tarball|Tarball]] is a commonly used name to refer to an archive file in the {{{tar}}} (''Tape Archive'') format. These files are produced by the command [[https://en.wikipedia.org/wiki/Tar_(computing)|tar]].
Line 8: Line 8:
In the Unix philosophy of "one job, one program", it does not support compression directly. If you then want to compress your archive, you use a separate program that is specialised in compression. tar is most commonly used in tandem with an external compression utility such as ["gzip"] or ["bzip2"], since it has no built in data compression facilities. These compression utilities generally only compress a single file, hence the pairing with tar, which can produce a single file from many files. It is used widely to archive and unarchive files, which means to accumulate a large collection of files into a single archive file (packer), while preserving FileSystem information such as user and group permissions, dates, and directory structures. Tarballs are commonly used to pack [[source]] code.
Line 10: Line 10:
=== Filename extension ===
 * .tar , for tar file.
{{{tar}}} itself does not support compression directly. It is most commonly used in tandem with an external compression utility such as {{{gzip}}} or {{{bzip2}}}. These compression utilities generally only compress a single file, hence the pairing with tar, which can produce a single file from many files.

The [[MIME]] type of tar archives is {{{application/x-tar}}}

=== File extensions ===

 * .tar
Line 15: Line 20:
=== MIME-Type ===
 * application/x-tar
Line 18: Line 21:
== Installation ==
After unpacking and uncompressing, the installation procedure is the standard GNU one:
----
Line 21: Line 23:
$ ./configure

$ ["make"]

$ make install

See also:
 * {Wikipedia:tarball}
 * ["FileRoller"] in DebianGnome, that can uncompress and unpacked files.
CategoryCompression CategoryFileFormat

Translation(s): Italiano


A Tarball is a commonly used name to refer to an archive file in the tar (Tape Archive) format. These files are produced by the command tar.

It is used widely to archive and unarchive files, which means to accumulate a large collection of files into a single archive file (packer), while preserving FileSystem information such as user and group permissions, dates, and directory structures. Tarballs are commonly used to pack source code.

tar itself does not support compression directly. It is most commonly used in tandem with an external compression utility such as gzip or bzip2. These compression utilities generally only compress a single file, hence the pairing with tar, which can produce a single file from many files.

The MIME type of tar archives is application/x-tar

File extensions

  • .tar
  • .tar.gz or .tgz (only when compressed by gzip)
  • .tar.bz2 or .tbz (only when compressed by bzip2)


CategoryCompression CategoryFileFormat