On Monday 30 June 2003 23:19, Fran=E7ois Pinard wrote: > [Jeff Epler] > > > the 100-char limit is traditional? > > Traditional. POSIX extends the limit somewhat, but the rules are > very strange. There are two separated fields in the header, and > whenever the second field is non-empty, a slash is to be _implied_ > between both, so you cannot cut the path string anywhere. > On HP-UX 11.x you hit the same problem than on Solaris, with a bit=20 different error message: bash-2.05a$ /usr/bin/tar xf Python-2.3b2.tar tar: ././@LongLink - cannot create tar: ././@LongLink - cannot create =2E.. I've run into the same problem with our in-house software - my=20 solution was to use HP-UX 11.x tar to create the archive, both GNU=20 tar and posix tar will correctly unpack it. Harri
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4