hi,
i want to correct my command .
i am sure this will work
It might work, but it creates a compressed archive for each file being processed (and each of those archives has the same name) instead of creating one compressed archive containing all of the files being processed. (But I do not see an s modifier in the HP/UX tar man page.) And, it looks like the HP/UX version of tar wants -cv instead of just cv.) Furthermore it creates an uncompressed archive in the filesystem which the submitter of this thread wanted to avoid.
Last edited by Don Cragun; 08-13-2016 at 08:40 AM..
Reason: Add some notes based on the HP/UX tar man page.
This User Gave Thanks to Don Cragun For This Post:
Dear sirs,
I have some 4mm dat cartridges (4GB) made in a HP-UX 11.00 with a standard tar command (tar -cv files_to_backup) made with a scsi dat drive HP 35470A.
After more than one year I need to restore some data on a linux system (Red Hat 7.2) which has the same dat drive.
Now I tried... (4 Replies)
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
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)
How to search for all files with matching strings -->
find + tar + gzip + uunecode/email them in one command?
I am sure there is a right way to pass list of files to tar, then compress tar file. Then send that as attachment using uuencode in one command.. Can we do that!? (3 Replies)
Hi Guys,
I am using RHEL5 and Solaris 9 & 10.
I want to tar and gzip my files then remove them after a successful tar command...
Lets say I have files with extension .arc then I want to tar and gzip these files.
After successful tar command I want to remove all these files (i.e .arc).
... (3 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)
Discussion started by: royinfo.alain
2 Replies
LEARN ABOUT LINUX
deb
deb(5) Debian deb(5)NAME
deb - Debian binary package format
SYNOPSIS
filename.deb
DESCRIPTION
The .deb format is the Debian binary package file format. It is understood by dpkg 0.93.76 and later, and is generated by default by all
versions of dpkg since 1.2.0 and all i386/ELF versions since 1.1.1elf.
The format described here is used since Debian 0.93; details of the old format are described in deb-old(5).
FORMAT
The file is an ar archive with a magic value of !<arch>. The file names might contain a trailing slash.
The tar archives currently allowed are, the old-style (v7) format, the pre-POSIX ustar format, a subset of the GNU format (only the new
style long pathnames and long linknames, supported since dpkg 1.4.1.17), and the POSIX ustar format (long names supported since dpkg
1.15.0). Unrecognized tar typeflags are considered an error.
The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only one line is present, the for-
mat version number, 2.0 at the time this manual page was written. Programs which read new-format archives should be prepared for the minor
number to be increased and new lines to be present, and should ignore these if this is the case.
If the major number has changed, an incompatible change has been made and the program should stop. If it has not, then the program should
be able to safely continue, unless it encounters an unexpected member in the archive (except at the end), as described below.
The second required member is named control.tar.gz. It is a gzipped tar archive containing the package control information, as a series of
plain files, of which the file control is mandatory and contains the core control information. The control tarball may optionally contain
an entry for `.', the current directory.
The third, last required member is named data.tar. It contains the filesystem as a tar archive, either not compressed (supported since
dpkg 1.10.24), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since dpkg 1.15.6), bzip2 (with .bz2 exten-
sion, supported since dpkg 1.10.24) or lzma (with .lzma extension, supported since dpkg 1.13.25).
These members must occur in this exact order. Current implementations should ignore any additional members after data.tar. Further members
may be defined in the future, and (if possible) will be placed after these three. Any additional members that may need to be inserted
before data.tar and which should be safely ignored by older programs, will have names starting with an underscore, `_'.
Those new members which won't be able to be safely ignored will be inserted before data.tar with names starting with something other than
underscores, or will (more likely) cause the major version number to be increased.
SEE ALSO deb-old(5), dpkg-deb(1), deb-control(5).
Debian Project 2009-02-27 deb(5)