tar and gzip files Post: 302656689

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Combine tar and gzip together?

Hello I just wandering, instead to doing "tar cvf foo.tar * " and then gzip foo.tar , can't it be combined to one command ?

2. UNIX for Dummies Questions & Answers

can i tar and gzip in one liner ?

hello can i combine this 2 commands in one liner command?

3. UNIX for Dummies Questions & Answers

TAR and GZIP help

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...

4. UNIX for Advanced & Expert Users

tar/gzip/gz...which one to use?

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. UNIX for Dummies Questions & Answers

tar and gzip

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...

6. UNIX for Dummies Questions & Answers

shortcut for tar cvf - [filename] | gzip > [filename].tar.gz

i'd like to have an alias (or something similar) where i can type a command like "archive" and a filename and have it tar and gzip the file, so... $ archive filename results in filename.tar.gz...do i have to write a script to do this?

7. Shell Programming and Scripting

tar + gzip + split together

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...

8. Shell Programming and Scripting

tar and gzip problem

Hi Guys, I have a few files. i want to tar these files and zip it using gzip it. -rw-r----- 1 magesh magesh 12940369 Jul 27 09:26 dcx_imds_c.asc -rw-r----- 1 magesh magesh 1221391 Jul 27 09:27 dcx_imds_h.asc -rw-r----- 1 magesh magesh 1105673 Jul 27 09:27...

9. Shell Programming and Scripting

Need help to tar and gzip files per date

hi, I have multiple files created per date every day. I want to be able to tar all the files older than 7 days into a single file and then gzip that tarred file and move it to a separate partition. Then delete the actual files. Eg - "ls -l" shows Dec 8 has 6-8 files created. I want to tar...

10. UNIX for Dummies Questions & Answers

Create Tar and GZip files under Unix

Hi All I have 2 tar files and inside a Gzip file (actually its folder) that i got from a Unix user to check the code for him and find some problem. I decompress the Tar file and use 7-ZIP to open the Gzip file and Extract all folders and files. I found the code problem and change it but now when...

LEARN ABOUT NETBSD

deb

deb(5)                                                              dpkg suite                                                              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 since dpkg 0.93.76, and is generated by default since dpkg 1.2.0
       and 1.1.1elf (i386/ELF builds).

       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
       extensions,  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 (new  style  long
       pathnames  and  long  linknames,  supported  since dpkg 1.4.1.17; large file metadata since dpkg 1.18.24), and the POSIX ustar format (long
       names supported since dpkg 1.15.0).  Unrecognized tar typeflags are considered an error.  Each tar entry  size  inside  a  tar  archive  is
       limited to 11 ASCII octal digits, allowing for up to 8 GiB tar entries.  The GNU large file metadata support permits 95-bit tar entry sizes
       and negative timestamps, and 63-bit UID, GID and device numbers.

       The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only  one  line  is  present,  the
       format  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.  It is a tar archive containing the package control information, either not compressed
       (supported since dpkg 1.17.6), or compressed with gzip (with .gz extension), xz (with .xz extension, supported since 1.17.6) or zstd  (with
       .zst  extension, supported since 1.19.0.5ubuntu2), as a series of plain files, of which the file control is mandatory and contains the core
       control information, the conffiles, triggers, shlibs and symbols files contain optional control information,  and  the  preinst,  postinst,
       prerm  and  postrm  files  are  optional  maintainer  scripts.   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), zstd (with .zst
       extension, supported since 1.19.0.5ubuntu2), bzip2 (with .bz2 extension, 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 after
       debian-binary  and  before  control.tar  or 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.

MEDIA TYPE

   Current
       application/vnd.debian.binary-package

   Deprecated
       application/x-debian-package
       application/x-deb

SEE ALSO

       deb-old(5),  dpkg-deb(1), deb-control(5), deb-conffiles(5) deb-triggers(5), deb-shlibs(5), deb-symbols(5), deb-preinst(5), deb-postinst(5),
       deb-prerm(5), deb-postrm(5).

1.19.0.5                                                            2018-04-16                                                              deb(5)