Bug 63671 - pax does not support long file names
Summary: pax does not support long file names
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: pax   
(Show other bugs)
Version: 1.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
Blocks: 67218
TreeView+ depends on / blocked
Reported: 2002-04-17 06:45 UTC by vvs
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-06-21 20:10:30 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description vvs 2002-04-17 06:45:24 UTC
Description of Problem:

According to pax(1) manpage it should support pathnames of 100 characters in
length in tar mode and 250 in ustar mode. Actually it supports only pathnames
with maximum of 99 characters in length in both modes.

Version-Release number of selected component (if applicable):


How Reproducible:


Steps to Reproduce:
1. Create file with name that has 100 or greater characters in length
2. pax -wv -x tar -f test1.tar filename
3. pax -wv -x ustar -f test2.tar filename

Actual Results:

File name too long

Expected Results:

It should either add it to tar successfully or documentation should be corrected
(which I doubt)

Additional Information:
GNU tar successfully added file with name as long as 255 characters (on ext3

Comment 1 Karsten Hopp 2002-07-03 14:54:51 UTC
you can use filename with up to 99 chars (+ the trailing \0 in strings) 
pathnames (directory name + filename) can have up to 250 chars. 
I've fixed the manpage to make that more obvious

Comment 2 vvs 2002-07-03 20:25:37 UTC
You mean it's a standard behaviour? Ok, then. But that makes it incompatible
with GNU tar. I've got an impression that it could be a universal substitute for
tar and cpio and started to use it everywhere. Well, back to the tar then.
<Sigh> May I suggest to make this incompatibility clear too?

Note You need to log in before you can comment on or make changes to this bug.