Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

IEEE Standards Interpretations for IEEE Std 1003.1™-2001 IEEE Standard for Information Technology - Portable Operating System Interface (POSIX®)

Copyright © 2006 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.

Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.

IEEE Standards Department Copyrights and Permissions 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA

Interpretation Request #11
Defect in XCU pax Relevant Sections: pax cpio symlinks The Shell and Utilities

The description of cpio Interchange Format does not define where the contents of a symbolic link is located in the archive.

Replace lines 27806-27807 with: "c_filesize Contains the length in octets of the data section following the header structure." On line 27827 insert after "manner dependent on the file.": "For regular files the data shall consist of the contents of the file. For symbolic links the data shall consist of the contents of the symbolic link." On line 27831 change "Only regular files have data to be restored" to "Only regular files and symbolic links have data to be restored". On line 27839 insert after "c_filesize equal to zero.": "Symbolic links shall be recorded with c_filesize equal to the length of the contents of the symbolic link."

Interpretation Response
The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale for Interpretation