Yeah the 'tar: Removing leading `/' from member names' warning is there for our own benefit so I guess it's simpler to just do everything in 3 steps and get around any issues ...
Hello all.
I have a tar file that contains a number of files that are stored in different directories.
If I extract this tar file with -xvf , the directories get created.
Is there a way to extract all of the files into one directory without creating the directories stored in the tar file. (9 Replies)
I have an interesting requirement. I have declaried an array like :-
arr=`find . ! -name "." | xargs -I {} echo {} | cut -c 2-${#}`
Then i will try to access the array elements like :-
i=0
for i in ${arr}; do
Here comes the confusions, the array elements are basically dir and files stored... (2 Replies)
hi,
I am in a weird situation. I have a parent tarball which contains 2 sub tarballs.
The structure is such :
Parent.tar.gz ---- > child1.tar.gz and child2.tar.gz
I need to get the size of the parent tarball without untaring it
I know that the command is gunzip -c parent.tar.gz | wc -c ... (1 Reply)
Hi,
I'm using a tar command
tar -xOvf /home/mytar.tar
My intention is to extract data in files which are inside various directories,
without extracting files to the disk.
Is this the best way to achieve it?
Thanks,
Chetan (3 Replies)
Hi,
I have tar filw which has multiple directories which contain files.
When i extract using tar -xf the directory structure also get extracted.
I require only files and not directory structures as there will be overhead of moving the files again.
So i searched here and got a solution but... (4 Replies)
Hi
Somebody must have done this before, but I can't seem to find any answer on my problem.
On HP-UX 11i v3 I have a relatively large tar ball (~120 GB), and I want to create the directory structure only from the archive.
There is no option to make a new archive with only the directory... (3 Replies)
#cat a
BAC064DAL
BAC063DAL
BAC056PHX
BAC066DAL
BAC062PHX
BAC062DAL
BAC060DAL
BAC058PHX
BAC054PHX
BAC051PHX
# for i in `cat a`
> do
> tar xvf $a/$a*.tar*
> done
tar: /*.tar*: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: /*.tar*: Cannot... (3 Replies)
Hi,
uname -a
SunOS mymac 5.11 11.2 sun4u sparc SUNW,SPARC-Enterprise
I need to tar a folder /tmp/moht but do not want these three folders to be included in the tar file -> savejpg, bmpsave and imgsave
I tried --exclude, -path, -not options but it says bad option
Can you help me with... (3 Replies)
I have a tar file hello.tar which is 95 GB.
hello.tar has many files and folders including some tar files as well.
I wish to create a new tar ball which should maintain only the folder structure of hello.tar and the tar ball within the hello.tar
So basically the idea is to untar... (2 Replies)
Hi Team,
Following unix command is throwing error. Can anyone please help me to fix the issue?
tar -cvf /aa/bb/cc/tarball1.tar /x/y/z1/abc.ksh /x/y/z2/pqr.txt /x/y/z3/lmn.tmp
Error message thrown:
tar: Removing leading `/' from member names
OS: uname -a
Linux xyz... (1 Reply)
Discussion started by: kmanivan82
1 Replies
LEARN ABOUT DEBIAN
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>. Only the common ar archive format is supported, with no long file name exten-
sions, but with file names containing an optional trailing slash, which limits their length to 15 characters (from the 16 allowed). File
sizes are limited to 10 ASCII decimal digits, allowing for up to approximately 9536.74 MiB member files.
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 2012-06-16 deb(5)