Fsize in default: stanza. Post: 302868155

Sponsored Content

Operating Systems AIX Fsize in default: stanza. Post 302868155 by Don Cragun on Saturday 26th of October 2013 08:13:50 AM

10-26-2013

Registered User

Quote:

Originally Posted by bakunin

The AIX tar adheres to the USTAR standard, which in turn means: no single input file processed by tar can be larger than 8 GB, but the archive itself can be of (nearly) unlimited size. The reason for the limitation is the data structure of the USTAR header which can't hold size information of more than 8 GB.

I hope this helps.

bakunin

The pax utility (with the -x pax option to set the archive format) provides extensions to the ustar archive format to remove the ustar format file size limits. When using the pax archive format, any size file can be saved in an archive as long as the archive created will fit into whatever device or filesystem is used to contain the archive.

Some implementations of cpio and tar (as well as the pax utility) are able to create and read pax format archives.

Don Cragun

View Public Profile for Don Cragun

Find all posts by Don Cragun

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

getting the stanza names if the pattern found

Hi Friends, I have a file as below : machine1: abc xyz qwerty machine2: jkl mno machine3: hhh kkk qwerty Now ...i need to find all the stanza names that have the pattern "qwerty'" in it...( i need to get the output as machine1 and machine3 since...

2. Shell Programming and Scripting

selecting the stanza fields

Hi Friends, I have a stanza file as below : CuDv: name = "hdisk34" status = 0 chgstatus = 3 ddins = "scsidisk" location = "06-08-02" parent = "fscsi0" connwhere = "W_0" PdDvLn = "disk/fcp/mpioosdisk" CuDv: ...

3. HP-UX

change ulimit fsize permanantly

Hi, on HP-UX when I run command ulimit -a I get time(seconds) 4096 file(blocks) unlimited data(kbytes) 1048576 stack(kbytes) 8192 memory(kbytes) unlimited coredump(blocks) 4194303 nofiles(descriptors) 4096 Now I want to change file(blocks) ...

4. Shell Programming and Scripting

How to extract entire stanza using awk?

Hello friends, I have a text file with lot of stanzas with each starting with "O-O-O. Sample file :- 1. d4 Nf6 2. c4 g6 3. Nc3 d5 4. cxd5 Nxd5 5. e4 Nxc3 6. bxc3 Bg7 7. Nf3 c5 8. Rb1 O-O 9. Be2 cxd4 10. cxd4 Qa5+ 11. Bd2 Qxa2 12. O-O Bg4 13. Bg5 h6 14. Be3

5. Shell Programming and Scripting

A Stanza File Parser in Pure ksh

As it was ultimately Don Craguns idea that saved the whole project i can as well give something back to the community. This is my stanza file parser, which was written only using ksh without any external programs. The stanza structure There is some inconsistency as to what exactly is meant by...

LEARN ABOUT DEBIAN

git-tar-tree

GIT-TAR-TREE(1) 						    Git Manual							   GIT-TAR-TREE(1)

NAME

       git-tar-tree - Create a tar archive of the files in the named tree object

SYNOPSIS

       git tar-tree [--remote=<repo>] <tree-ish> [ <base> ]

DESCRIPTION

       THIS COMMAND IS DEPRECATED. Use git archive with --format=tar option instead (and move the <base> argument to --prefix=base/).

       Creates a tar archive containing the tree structure for the named tree. When <base> is specified it is added as a leading path to the files
       in the generated tar archive.

       git tar-tree 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 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. It can be extracted using git get-tar-commit-id.

OPTIONS

       <tree-ish>
	   The tree or commit to produce tar archive for. If it is the object name of a commit object.

       <base>
	   Leading path to the files in the resulting tar archive.

       --remote=<repo>
	   Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.

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.

EXAMPLES

       git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)
	   Create a tar archive that contains the contents of the latest commit on the current branch, and extracts it in /var/tmp/junk directory.

       git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release.

       git tar-tree v1.4.0^{tree} git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release, but without a global extended pax header.

       git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar
	   Get a tarball v1.4.0 from example.com.

       git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar
	   Put everything in the current head's Documentation/ directory into git-1.4.0-docs.tar, with the prefix git-docs/.

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012							   GIT-TAR-TREE(1)