16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

|<br />

cpio<br />

After the header information, namesize bytes of pathname are stored. namesize<br />

includes the null byte of the end of the pathname. After this, filesize bytes of the file<br />

contents are recorded.<br />

Binary headers contain the same information in 2-byte (short) and 4-byte (long)<br />

integers as follows:<br />

Bytes Field Names<br />

2 magic<br />

2 dev<br />

2 ino<br />

2 mode<br />

2 uid<br />

2 gid<br />

2 nlink<br />

2 rdev<br />

2 mtime<br />

2 namesize<br />

2 filesize<br />

After the header information comes the filename, with namesize rounded up to the<br />

nearest 2-byte boundary. Then the file contents appear as in the ASCII archive. The<br />

byte ordering of the 2- and 4-byte integers in the binary format is<br />

machine-dependent and thus portability of this format is not easily guaranteed.<br />

Related Information<br />

The compress, cpio, pax, and tar commands<br />

magic — Format of the /etc/magic file<br />

Description<br />

The file command uses the /etc/magic file in its attempt to identify the type of a<br />

binary file. Essentially, /etc/magic contains templates showing what different types<br />

of files look like.<br />

The magic file contains lines describing magic numbers, which identify particular<br />

types of files. Lines beginning with a > or & character represent continuation lines<br />

to a preceding main entry:<br />

> If the file command finds a match on the main entry line, these additional<br />

patterns are checked. Any pattern that matches is used. This may generate<br />

additional output; a single blank separates each matching line’s output if<br />

any output exists for that line.<br />

& If the file command finds a match on the main entry line, and a following<br />

continuation line begins with this character, that continuation line’s pattern<br />

must also match, or neither line is used. Output text associated with any<br />

line beginning with the & character is ignored.<br />

Each line consists of four fields, separated by one or more tabs:<br />

(a) The first field is a byte offset in the file, consisting of an optional offset<br />

operator and a value. In continuation lines, the offset immediately follows a<br />

continuation character.<br />

912 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference<br />

If no offset operator is specified, then the offset value indicates an offset<br />

from the beginning of the file.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!