View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000313 | 1003.1(2004)/Issue 6 | Shell and Utilities | public | 2010-09-17 08:00 | 2013-04-16 13:06 |
| Reporter | ajosey | Assigned To | ajosey | ||
| Priority | normal | Severity | Comment | Type | Clarification Requested |
| Status | Closed | Resolution | Accepted As Marked | ||
| Name | Andrew Josey | ||||
| Organization | The Open Group | ||||
| User Reference | kientzle:xcubug2.txt ern 180 | ||||
| Section | pax | ||||
| Page Number | 0 | ||||
| Line Number | 0 | ||||
| Interp Status | --- | ||||
| Final Accepted Text | 0000313:0000550 | ||||
| Summary | 0000313: pax non-empty prefix and an empty name | ||||
| Description | Edition of Specification (Year): 2004 Defect code : 3. Clarification required http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html The description of "ustar interchange format" describes a process for splitting pathnames between the prefix and the name fields. It is not clear from the description given whether it is legal for the name field to be empty. On the one hand, compatibility with legacy implementations (before the prefix field was common) would suggest that an empty name field should not be allowed. On the other hand, it seems consistent with the description for <prefix> + "/" + <name> to generate a pathname ending in "/" (a directory) if the name is empty. This would allow storing directories with names over 100 characters in some cases. | ||||
| Desired Action | Clarify the description to explain whether it is legal for there to be a non-empty prefix and an empty name. | ||||
| Tags | tc1-2008 | ||||
|
|
Add the following as a new paragraph to the pax APPLICATION USAGE section after (draft 5 of the revision page and line numbers) P3031, L100222: When all of the following are true: 1. a file of type directory is being placed into an archive, 2. the ustar archive format is being used, 3. the pathname of the directory is less than or equal to 155 bytes long (it will fit in the prefix field in the ustar header block), and 4. the last component of the pathname of the directory is longer than 100 bytes long (it will not fit in the name field in the ustar header block) some implementations of the pax utility will place the entire directory pathname in the prefix field, set the name field to an empty string, and place the directory in the archive. Other implementations of the pax utility will give an error under these conditions because the name field is not large enough to hold the last component of the directory name. This standard allows either behavior. However, when extracting a directory from a ustar format archive, this standard requires that all implementations be able to extract a directory even if the name field contains an empty string as long as the the prefix field does not also contain an empty string. Add this change to the list of stuff to be done in TC1 of the revision. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-09-17 08:00 | ajosey | New Issue | |
| 2010-09-17 08:00 | ajosey | Status | New => Under Review |
| 2010-09-17 08:00 | ajosey | Assigned To | => ajosey |
| 2010-09-17 08:00 | ajosey | Name | => Andrew Josey |
| 2010-09-17 08:00 | ajosey | Organization | => The Open Group |
| 2010-09-17 08:00 | ajosey | User Reference | => kientzle:xcubug2.txt ern 180 |
| 2010-09-17 08:00 | ajosey | Section | => pax |
| 2010-09-17 08:00 | ajosey | Page Number | => 0 |
| 2010-09-17 08:00 | ajosey | Line Number | => 0 |
| 2010-09-17 08:00 | ajosey | Interp Status | => --- |
| 2010-09-17 08:01 | ajosey | Note Added: 0000550 | |
| 2010-09-17 08:01 | ajosey | Status | Under Review => Resolved |
| 2010-09-17 08:01 | ajosey | Resolution | Open => Accepted As Marked |
| 2010-09-17 08:02 | ajosey | Final Accepted Text | => 0000313:0000550 |
| 2010-09-17 08:02 | ajosey | Tag Attached: tc1-2008 | |
| 2013-04-16 13:06 | ajosey | Status | Resolved => Closed |
