It only gives the first file because you're telling xargs to only give it the first file. from man xargs:
Remove the -l and it will feed in more.
Be warned, however, that if there are enough files, xargs will be forced to call tar more than once, because it's unable to fit them all into one commandline. when this happens, tar will happily replace the archive it already created with a new one. To avoid this, you must tell tar to append (r, rather than c, option).
This doesn't work for compressed tarballs however -- you can't append to those. You must compress it later.
Hi,
There are 700 .pdf files in a certain directory on the server and I need to TAR them first and then compress them using GZIP to free up the space. The combined size of the .pdf files is 3gb. However, there is only 1gb of free space on the server. So as you can see when I try to TAR these... (3 Replies)
P0251WLADC.svm_wl1 > /svm_wl1/billing/data/server/archive/ALLEVT
$ du -k FEB2006
22050224 FEB2006
As you can see,i have a folder called "FEB2006" which is around 22 GB.
i guess zip or compress wont work...( i don know how do we compress a folder)
i wished to use ""tar" ( i suppose... (5 Replies)
Hi,
I would like to have a combined gzip and tar that will compress and create multiple output tar.gz files. I want to have multiple files output because i cannot create an archive because there is no more space on my harddisk. I cannot transfer it locally because of slow connection. I want to... (3 Replies)
Hi All
Can any body help me out.
Amoung tar and gzip whiich unix command is more practical with respect to space management and file restoration.
Eg if I use tar or gzip which will be more helpful to reduce the space and during the file restoration.
Please help me out.
regards... (3 Replies)
Hi All
I need guidance on this requirement .
We have a directory structure which has data of approx 100 GB
We need to tar the structure then zip it and create different files of not more than 10 GB
A separate tar file then a .gz should not be created , on the fly a script is needed... (7 Replies)
Hi all,
4 files are returned when i issue 'find . -mtime -1 -type f -ls'.
./ora_475244.aud
./ora_671958.aud
./ora_934052.aud
./ora_934050.aud
However, when I issued the below command:
tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -... (2 Replies)
Hello
I am trying to select multiple files older than 14 days and create a single compressed file out of it. (AIX Release 3 Version 5)
I am trying to achieve it by following
tar -cvf db01_log.tar `find . -name "db01*.log" -mtime +14" -print`| gzip > db01_log.tar
however it just... (7 Replies)
Hi,
I need to combined in 1 line the execution below :
find * -type f -mtime -$nb_days -print | xargs tar -cvf $MAITUT/BCK_DATA.tar
gzip $MAITUT/BCK_DATA.tar.gz
The fact that the TAR is very big, at the end I need to generate only the GZ file.
The option z on the tar... (2 Replies)
Hello,
I will like to execute a find, tar & gzip in one command.
find * -type f -mtime -$nb_days -print | xargs tar -cvf $MAITUT/BCK_DATA.tar
gzip $MAITUT/BCK_DATA.tar.gz
The fact that the TAR is very big, at the end I need to generate only a compress file.
Please note... (22 Replies)
Discussion started by: royinfo.alain
22 Replies
LEARN ABOUT DEBIAN
pristine-tar
PRISTINE-TAR(1) pristine-tar PRISTINE-TAR(1)NAME
pristine-tar - regenerate pristine tarballs
SYNOPSIS
pristine-tar [-vdk] gendelta tarball delta
pristine-tar [-vdk] gentar delta tarball
pristine-tar [-vdk] [-m message] commit tarball [upstream]
pristine-tar [-vdk] checkout tarball
pristine-tar [-vdk] list
DESCRIPTION
pristine-tar can regenerate an exact copy of a pristine upstream tarball using only a small binary delta file and the contents of the
tarball, which are typically kept in an upstream branch in version control.
The delta file is designed to be checked into version control along-side the upstream branch, thus allowing Debian packages to be built
entirely using sources in version control, without the need to keep copies of upstream tarballs.
pristine-tar supports compressed tarballs, calling out to pristine-gz(1), pristine-bz2(1), and pristine-xz(1) to produce the pristine gzip,
bzip2, and xz files.
COMMANDS
pristine-tar gendelta tarball delta
This takes the specified upstream tarball, and generates a small binary delta file that can later be used by pristine-tar gentar to
recreate the tarball.
If the delta filename is "-", it is written to standard output.
pristine-tar gentar delta tarball
This takes the specified delta file, and the files in the current directory, which must have identical content to those in the upstream
tarball, and uses these to regenerate the pristine upstream tarball.
If the delta filename is "-", it is read from standard input.
pristine-tar commit tarball [upstream]
pristine-tar commit generates a pristine-tar delta file for the specified tarball, and commits it to version control. The pristine-tar
checkout command can later be used to recreate the original tarball based only on the information stored in version control.
The upstream parameter specifies the tag or branch that contains the same content that is present in the tarball. This defaults to
"refs/heads/upstream", or if there's no such branch, any branch matching "upstream". The name of the tree it points to will be recorded
for later use by pristine-tar checkout. Note that the content does not need to be 100% identical to the content of the tarball, but if
it is not, additional space will be used in the delta file.
The delta files are stored in a branch named "pristine-tar", with filenames corresponding to the input tarball, with ".delta" appended.
This branch is created or updated as needed to add each new delta.
pristine-tar checkout tarball
This regenerates a copy of the specified tarball using information previously saved in version control by pristine-tar commit.
pristine-tar list
This lists tarballs that pristine-tar is able to checkout from version control.
OPTIONS -v
--verbose
Verbose mode, show each command that is run.
-d
--debug
Debug mode.
-k
--keep
Don't clean up the temporary directory on exit.
-m message
--message=message
Use this option to specify a custom commit message to pristine-tar commit.
EXAMPLES
Suppose you maintain the hello package, in a git repository. You have just created a tarball of the release, hello-1.0.tar.gz, which you
will upload to a "forge" site.
You want to ensure that, if the "forge" loses the tarball, you can always recreate exactly that same tarball. And you'd prefer not to keep
copies of tarballs for every release, as that could use a lot of disk space when hello gets the background mp3s and user-contributed levels
you are planning for version 2.0.
The solution is to use pristine-tar to commit a delta file that efficiently stores enough information to reproduce the tarball later.
cd hello
git tag -s 1.0
pristine-tar commit ../hello-1.0.tar.gz 1.0
Remember to tell git to push both the pristine-tar branch, and your tag:
git push --all --tags
Now it is a year later. The worst has come to pass; the "forge" lost all its data, you deleted the tarballs to make room for bug report
emails, and you want to regenerate them. Happily, the git repository is still available.
git clone git://github.com/joeyh/hello.git
cd hello
pristine-tar checkout ../hello-1.0.tar.gz
LIMITATIONS
Only tarballs, gzipped tarballs, bzip2ed tarballs, and xzed tarballs are currently supported.
Currently only the git revision control system is supported by the "checkout" and "commit" commands. It's ok if the working copy is not
clean or has uncommitted changes, or has changes staged in the index; none of that will be touched by "checkout" or "commit".
ENVIRONMENT
TMPDIR
Specifies a location to place temporary files, other than the default.
AUTHOR
Joey Hess <joeyh@debian.org>
Licensed under the GPL, version 2 or above.
perl v5.14.2 2013-06-01 PRISTINE-TAR(1)