UNIX admin <[EMAIL PROTECTED]> wrote:
> Heck, I can even leverage that "obsolete", "old" knowledge on the
> wow-oh-so-up-with-the-times-high-tech-and-snazzy-Linux:
>
> bzip2 -dc filename.tar.bz2 | tar xvf -
>
> will work *anywhere* (System V thinking)
>
> versus
>
> gtar xvfz filename.tar.bz2
>
> which will not even work (GNU, implementing tools inside of other tools,
> stifling flexibility)
>
> or
>
> gtar xvfz filename.tar.gz
>
> which is directly dependent on the GNU toolchain (aka a perfect example of
> your "if all I have is a hammer..." statement).
>
> And that was just a *trivial* example.
>
This is a result of badly planned options.
star prints the compression type since more than 10 years
and it autodecompresses since ~ 6 years. This is longer than
GNU tar did have bzip2 support at all.
The correct usage is just to let the tar archives decide what to do.
Many programs from the FSF today have a set of unmemorizable options
because every request for adding support to new features was answered
with a special option instead of thinking about how this feature could
be implemented in a more general way. star -find allows to avoid a dozen
specialized GNU tar options and to do this in a way that you need to know
anyway if you like to use find.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
[email protected]
