View Single Post

   
  #2 (permalink)  
Old 02-18-2008, 08:41 PM
Mark Hill
 
Posts: n/a
Default Re: [OT] huh? weird tar behaviour

On 2 Dec 2003 02:14:04 GMT,
Joost Kremers <joostkremers@yahoo.com> wrote:
>

....
>
> i do 'less MANIFEST-9.1.bz2' and *again* i get garbage!! 'tar tjf' gives
> the same errors.
>
> so i rename the file back to MANIFEST.bz2, and everything works fine again!

....
> HOW IS THIS POSSIBLE???!!! and what on earth is going on??!!
>
> btw, no problems with MANIFEST-9.0.bz2...


Looking at /usr/bin/lesspipe.sh, which is defined in $LESSOPEN, it seems
a *.1.bz2 file is treated as compressed *roff source. I think this is
the course of your problem. Here are the offending lines:

#v+
*.1.bz2|*.2.bz2|*.3.bz2|*.4.bz2|*.5.bz2|*.6.bz2|*. 7.bz2|*.8.bz2|*.9.bz2|*.n.bz2|*.man.bz2)
# compressed *roff src?
if bzip2 -dc "$1" | file - | grep roff 1> /dev/null ; then
bzip2 -dc "$1" | nroff -S -mandoc -
fi ;;
#v-

This is how a normal *.bz2 file is treated:
#v+
*.bz2) bzip2 -dc "$1" 2>/dev/null ;;
#v-

HTH.


--
Mark Hill <usenet@mark.ukfsn.org> (Yahoo address not read)
GPG KeyID: 4A3B58AC
Reply With Quote