10-02-2007
Doesn't look good
We had the exact same problem with tar where I worked before.
It showed that the tar binary that we were using had an known bug
that we didn't know about. I'm very keen to know how this thread will be solved, if it will ever be that is \=
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
--------------------------------------------------------------------------------
When I tried to decompress using TAR the following error was popped up..
tar: blocksize = 0
..Can anyone tell me wht this means and how to rectify this error... (1 Reply)
Discussion started by: hemin_pm
1 Replies
2. Solaris
When I tried to decompress using TAR the following error was popped up..
tar: blocksize = 0
..Can anyone tell me wht this means and how to rectify this error... (3 Replies)
Discussion started by: hemin_pm
3 Replies
3. UNIX for Advanced & Expert Users
Hi
i am facing one problem with one file dxagent.ss, this file has most of the binary contents.
when i m running following command on unix machine
tar xpf dxagent.ss
output should be: removing leading '/' from members name. and should create 'usr' and 'var' directory.
but i am getting some... (5 Replies)
Discussion started by: yogini nemade
5 Replies
4. AIX
When Im trying to untar a file I get an error message
tar: 0511-169 A directory checksum error on media; 804399248 not equal to 46325.
What can I do to untar my file
Thanks (3 Replies)
Discussion started by: joemad
3 Replies
5. Solaris
Hi,
WHile decompressing the files, i get the error tar: directory checksum error. After decompressing when i check the size of file, it is less than the original file. Due to this error, there is loss of data. How can this error be removed?
Thanks in advance. (7 Replies)
Discussion started by: agarwal
7 Replies
6. Linux
Hi
when use "tar cpvzf /dev/st0 --exclude=/proc --exclude-/lost+found --exclude=/mnt --exclude=/media --exclude=/sys /" to tape,
get the following message "tar: error exit delayed form pervious error",
What is the mean ? Please suggest some solution for these errors. thx (1 Reply)
Discussion started by: chayato
1 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: ahSher
2 Replies
8. Shell Programming and Scripting
Hi all,
I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to... (1 Reply)
Discussion started by: bashnewbee
1 Replies
9. Fedora
...... (3 Replies)
Discussion started by: larry burns
3 Replies
10. Shell Programming and Scripting
do you have idea what is the limit to zip the file.
+ tar -cvf - today.txt
tar: Size of today.txt >= 8GB. Not dumped. (3 Replies)
Discussion started by: ramkumar15
3 Replies
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)