|
|
This is a problem with the BSD tar supplied with Tiger, GNU tar and xtar have no such problem
You link does not work. I assume it did when you provided it but it does not now.
I believe the problem here is that in Tiger's tar is based off BSD tar. However xtar and Panther's tar are based off of GNU tar 1.13.25 (I'm not sure why Apple made the switch back to BSD for this utility). Anyway GNU tar 1.13.25 uses the GNU tar format by default. Archives in GNU format are able to hold pathnames of unlimited length. You can find more information on the variying tar formats on the GNU website: http://www.gnu.org/software/tar/manual/html_node/Formats.html#Formats In order to confirm the above I have just tested creating folders with very long names (well over 100 characters) and archived them with xtar. This resulted in no errors and both the long filenames and resource forks were preserved correctly. Therefore, based on your experience I would suggest that Tiger users use xtar rather than the tar supplied by Apple for imporant backups. (Note: I would advise doing your own testing of xtar to confirm what I have stated above).
To clarify, my tests included multipart tar backups.
As per the title I did also test multipart tar backups with long file names and resource forks. Again, I had no problems. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|