10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: Phuti
3 Replies
2. UNIX for Advanced & Expert Users
Not sure if this is really in the right forum but here goes....
Looking for a way to extract individual compressed files from a compressed tarball WITHOUT tar -zxvf and then recompressing. Basically we need to be able to chunk out an individual compressed file while it still remains... (6 Replies)
Discussion started by: athos
6 Replies
3. Shell Programming and Scripting
I would like to make a listing of files in a large directory and output it to tar.gz. Is it possible to do this in one command?
For example;
I would like the text output from this command to be outputted to a directory.tar.gz file.
ls -al -R /bigdir
Is it possible to do it in memory... (5 Replies)
Discussion started by: lewk
5 Replies
4. Shell Programming and Scripting
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... (6 Replies)
Discussion started by: mac4rfree
6 Replies
5. Shell Programming and Scripting
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)
Discussion started by: aamir1234
7 Replies
6. UNIX for Dummies Questions & Answers
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? (4 Replies)
Discussion started by: bcamp1973
4 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: tungaw2004
3 Replies
8. UNIX for Advanced & Expert Users
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)
Discussion started by: abhijeetkul
5 Replies
9. UNIX for Dummies Questions & Answers
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)
Discussion started by: VandeMatram
3 Replies
10. UNIX for Dummies Questions & Answers
hello
can i combine this 2 commands in one liner command? (1 Reply)
Discussion started by: umen
1 Replies
GIT-ARCHIVE(1) Git Manual GIT-ARCHIVE(1)
NAME
git-archive - Create an archive of files from a named tree
SYNOPSIS
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o | --output=<file>] [--worktree-attributes]
[--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>...]
DESCRIPTION
Creates an archive of the specified format containing the tree structure for the named tree, and writes it out to the standard output. If
<prefix> is specified it is prepended to the filenames in the archive.
git archive behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used as
the modification time of each file in the archive. In the latter case the commit time as recorded in the referenced commit object is used
instead. Additionally the commit ID is stored in a global extended pax header if the tar format is used; it can be extracted using git
get-tar-commit-id. In ZIP files it is stored as a file comment.
OPTIONS
--format=<fmt>
Format of the resulting archive: tar or zip. If this option is not given, and the output file is specified, the format is inferred from
the filename if possible (e.g. writing to "foo.zip" makes the output to be in the zip format). Otherwise the output format is tar.
-l, --list
Show all available formats.
-v, --verbose
Report progress to stderr.
--prefix=<prefix>/
Prepend <prefix>/ to each filename in the archive.
-o <file>, --output=<file>
Write the archive to <file> instead of stdout.
--worktree-attributes
Look for attributes in .gitattributes in working directory too.
<extra>
This can be any options that the archiver backend understands. See next section.
--remote=<repo>
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository.
--exec=<git-upload-archive>
Used with --remote to specify the path to the git-upload-archive on the remote side.
<tree-ish>
The tree or commit to produce an archive for.
<path>
Without an optional path parameter, all files and subdirectories of the current working directory are included in the archive. If one
or more paths are specified, only these are included.
BACKEND EXTRA OPTIONS
zip
-0
Store the files instead of deflating them.
-9
Highest and slowest compression level. You can specify any number from 1 to 9 to adjust compression speed and ratio.
CONFIGURATION
tar.umask
This variable can be used to restrict the permission bits of tar archive entries. The default is 0002, which turns off the world write
bit. The special value "user" indicates that the archiving user's umask will be used instead. See umask(2) for details. If --remote is
used then only the configuration of the remote repository takes effect.
tar.<format>.command
This variable specifies a shell command through which the tar output generated by git archive should be piped. The command is executed
using the shell with the generated tar file on its standard input, and should produce the final output on its standard output. Any
compression-level options will be passed to the command (e.g., "-9"). An output file with the same extension as <format> will be use
this format if no other format is given.
The "tar.gz" and "tgz" formats are defined automatically and default to gzip -cn. You may override them with custom commands.
tar.<format>.remote
If true, enable <format> for use by remote clients via git-upload-archive(1). Defaults to false for user-defined formats, but true for
the "tar.gz" and "tgz" formats.
ATTRIBUTES
export-ignore
Files and directories with the attribute export-ignore won't be added to archive files. See gitattributes(5) for details.
export-subst
If the attribute export-subst is set for a file then git will expand several placeholders when adding this file to an archive. See
gitattributes(5) for details.
Note that attributes are by default taken from the .gitattributes files in the tree that is being archived. If you want to tweak the way
the output is generated after the fact (e.g. you committed without adding an appropriate export-ignore in its .gitattributes), adjust the
checked out .gitattributes file as necessary and use --worktree-attributes option. Alternatively you can keep necessary attributes that
should apply while archiving any tree in your $GIT_DIR/info/attributes file.
EXAMPLES
git archive --format=tar --prefix=junk/ HEAD | (cd /var/tmp/ && tar xf -)
Create a tar archive that contains the contents of the latest commit on the current branch, and extract it in the /var/tmp/junk
directory.
git archive --format=tar --prefix=git-1.4.0/ v1.4.0 | gzip >git-1.4.0.tar.gz
Create a compressed tarball for v1.4.0 release.
git archive --format=tar.gz --prefix=git-1.4.0/ v1.4.0 >git-1.4.0.tar.gz
Same as above, but using the builtin tar.gz handling.
git archive --prefix=git-1.4.0/ -o git-1.4.0.tar.gz v1.4.0
Same as above, but the format is inferred from the output file.
git archive --format=tar --prefix=git-1.4.0/ v1.4.0^{tree} | gzip >git-1.4.0.tar.gz
Create a compressed tarball for v1.4.0 release, but without a global extended pax header.
git archive --format=zip --prefix=git-docs/ HEAD:Documentation/ > git-1.4.0-docs.zip
Put everything in the current head's Documentation/ directory into git-1.4.0-docs.zip, with the prefix git-docs/.
git archive -o latest.zip HEAD
Create a Zip archive that contains the contents of the latest commit on the current branch. Note that the output format is inferred by
the extension of the output file.
git config tar.tar.xz.command "xz -c"
Configure a "tar.xz" format for making LZMA-compressed tarfiles. You can use it specifying --format=tar.xz, or by creating an output
file like -o foo.tar.xz.
SEE ALSO
gitattributes(5)
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-ARCHIVE(1)