[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: tar(1) problem with long file names.
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: tar(1) problem with long file names.
- From: Hannah Schroeter <hannah_(_at_)_schlund_(_dot_)_de>
- Date: Sat, 22 Oct 2005 19:05:29 +0200
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
- Organization: Schlund + Partner AG
On Sat, Oct 22, 2005 at 01:43:03PM +0000, Christian Weisgerber wrote:
>Hannah Schroeter <hannah_(_at_)_schlund_(_dot_)_de> wrote:
>> Use a more apt data format in your use case. Ehm correcting myself:
>> According to pax(1), 100 is the limit for pathnames in the old tar
>> format, while the limit for ustar is 250. For *pathnames*!.
>> Perhaps you can use cpio (or pax with -x cpio).
>Actually, it's the SVR4 cpio format ("sv4cpio" or the variant
>"sv4crc") you want. 1024-char file/path names, 32-bit inode and
>device numbers, and even reasonably portable.
If the plain cpio format itself isn't up to the task, perhaps the pax
manual page should document its limitations. I went by the manual page
and saw no mention of restrictions there for cpio, either.
Still good to know about that recommendation, I might have some use for
Visit your host, monkey.org