[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, eric-list-openbsd-misc_(_at_)_catastrophe_(_dot_)_net
- Subject: Re: tar(1) problem with long file names.
- From: Jay Fenlason <hack_(_at_)_nerd-marrow_(_dot_)_com>
- Date: Fri, 21 Oct 2005 18:04:42 -0400
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org, eric-list-openbsd-misc_(_at_)_catastrophe_(_dot_)_net
On Fri, Oct 21, 2005 at 02:07:16PM -0500, eric wrote:
> It seems that tar(1) is only able to archive filenames of 100 characters or
> less. However, ufs can handle (I've been testing using touch(1)) filenames
> up to 255 characters. I tried to modify the following in src/bin/pax/tar.h
> #define TNMSZ 100 /* size of name field */
> #define TNMSZ 255 /* size of name field */
> But it didn't seem to work.
> Has anyone bumped into this and made a more reliable fix?
> The issue is that with NFS mounts of directories such as iTunes music
> directories, there's often longer file names than 100 characters. So doing
> backups or transporting the files is slightly difficult.
GNU tar uses a variety of ugly hacks to get around the 100 (original
tar) or 255 (ustar) character limit in file and path names.
Unfortunatly, only gnu tar can correctly extract such archives. If
you're willing to live with that restriction, it's in ports. Have