Sponsored Content
Full Discussion: Reg: Gzip
Top Forums Shell Programming and Scripting Reg: Gzip Post 302147415 by porter on Tuesday 27th of November 2007 01:33:08 AM
Old 11-27-2007
gzip only compresses, it does not package up groups of files.

For that I recommend "tar".

For gzipped tar file the normal extension is either ".tar.gz" or ".tgz".

So use "tar" to package up the directory into one file, the gzip that tar file.

Code:
tar cf te55.tar te55 
gzip te55.tar

 

10 More Discussions You Might Find Interesting

1. SCO

reg:rm -R is not working

I am installing the my package in SCO unix 5.0 .so it will create some temporary directories and files and same will delete.So , 'rm -R ' is not working in system .in the package only it has given this command,so now without this command working we can not go forward. so kindly help in this... (1 Reply)
Discussion started by: mokri_1980
1 Replies

2. UNIX for Dummies Questions & Answers

Help with Reg. Expression

I need help with this: Can any one tell me what does these below mean: 1. "\(.\).*") != '/' 2. sed 's+^\./++;s+/.*++' 3. sed "s+${f}/+ + Thanks in advance (7 Replies)
Discussion started by: moe2266
7 Replies

3. Shell Programming and Scripting

Reg expression For

HI system.sysUpTime.0 : Timeticks: (1519411311) 175 days, 20:35:13.11 From the above output i need only 175days in a perl script.. Please Help (2 Replies)
Discussion started by: Harikrishna
2 Replies

4. UNIX for Dummies Questions & Answers

reg chown

hi i wrote a script to run 'C' executable which will create a new file, after that util is completed, i have to change the file ownership to some other user. for that i used "chown" for changing the file permission in Korn script :confused:but it is throwing error is "operation... (2 Replies)
Discussion started by: ilayans
2 Replies

5. Shell Programming and Scripting

Reg Ex question

Hi All, If I had a string that was a combination of plain text and quoted text - For ex String: This "sentence is" a combination of "multiple words" I wanted to know how I can write a reg-ex that splits the above string into the following result = This result = sentence is result = a... (7 Replies)
Discussion started by: garric
7 Replies

6. Solaris

doubt reg gzip,gunzip

Hi, Can anyone let me explain the difference between tar , uncompress,gzip and gunzip commands. both gzip and gunzip are same i think correct me if am wrong. (1 Reply)
Discussion started by: rogerben
1 Replies

7. Shell Programming and Scripting

Sorting - Reg.

Hi masters, I have one doubt, lets's say file1 has the following contents, 1 2.0 3.1 5.5 7 5.10 5.9 How to sort these contents to get the o/p like 1 2.0 3.1 5.5 5.9 5.10 7 (8 Replies)
Discussion started by: ecearund
8 Replies

8. AIX

reg DS_LVZ

HI in a vg i want to display the lv name & whether the LV is enabled with DS_LVZ parameter? I used #lsvg -o | grep vgname | lsvg -il this gives the output of lv's in the vg. buti treid with lsvg -o | grep vgname| lsvg -il | egrep "LOGICAL VOLUME|DS_LVZ" but No... (5 Replies)
Discussion started by: balumurugesh
5 Replies

9. Shell Programming and Scripting

Reg expressions

Hi, I would like to grep for a string within a tag, can someone provide some assistance in how to do it? So I would like to use the grep command to find a string like: <tag>sometext<tag> because the sometext can be any number of characters or an type of number or lettering, what expression... (1 Reply)
Discussion started by: cyberfrog
1 Replies

10. UNIX for Advanced & Expert Users

gzip vs pipe gzip: produce different file size

Hi All, I have a random test file: test.txt, size: 146 $ ll test.txt $ 146 test.txt Take 1: $ cat test.txt | gzip > test.txt.gz $ ll test.txt.gz $ 124 test.txt.gz Take 2: $ gzip test.txt $ ll test.txt.gz $ 133 test.txt.gz As you can see, gzipping a file and piping into gzip... (1 Reply)
Discussion started by: hanfresco
1 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)
All times are GMT -4. The time now is 07:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy