Gunnar Ritter <[EMAIL PROTECTED]> wrote:

> Joerg Schilling <[EMAIL PROTECTED]> wrote:
>
> > Gunnar Ritter <[EMAIL PROTECTED]> wrote:
> > > And by the way, does star also still need the "-U" option in addition
> > > to "x" to match historical tar behavior?
> > Did I miss somtheing and there is a POSIX standard for "star"?
>
> But Jörg, you were previously claiming that
>
> | The star commandline interface completely matches the historical tar 
> behavior
>
> and there is absolutely no "-U  restore files unconditionally" option
> with 7th edition, System V, or BSD tar since they do that by default
> with the "x" key.

Looks like you did not look close enough at star.....

Star is not _just one_ program like GNU tar but a group of programs
that all are implemented around a highly configurable archiver engine.

Star implements 15 archive formats:

        v7tar   Old UNIX V7 tar format
        tar     Old BSD tar format
        star    Old star format from 1985
        gnutar  GNU tar format 1989 (violates POSIX)
        ustar   Standard POSIX.1-1988 tar format
        xstar   Extended standard tar (star 1994)
        xustar  'xstar' format without tar signature
        exustar 'xustar' format - always x-header
        pax     Extended POSIX.1-2001 standard tar
        suntar  Sun's extended pre-POSIX.1-2001
        bin     cpio UNIX V7 binary format
        cpio    cpio POSIX.1-1988 format
        odc     cpio POSIX.1-1988 with SYSv compat
        asc     SYSvr4 cpio ascii expanded device #
        crc     'asc' format + CRC


by using a fine grained "property" structure that allows you
to to control how star deals with archive formats and that allows
you to create a new archive format (if it only needs already implemented
archive property elements) within a few minutes.


Star implements 3 general command line interface base types:

        TAR     any tar variant
        PAX     any pax variant
        CPIO    any cpio variant

and star implements 5 specific command line interface variants:

        star    Used when called as "star", "ustar" or with
                any unknown argv[0]

                The latter is true only if a "fat" binary
                is in use (see below).

        suntar  Used when called as "suntar", "tar" or
                any argv[0] that starts with a 't' past the
                rightmost '/'.


        gnutar  Used when called as "gnutar", "gtar" or
                any argv[0] that starts with a 'g' past the
                rightmost '/'.

        pax     Used when called as "spax", "pax" or
                any argv[0] that starts with a 'p' past the
                rightmost '/'.


        cpio    Used when called as "scpio", "cpio" or
                any argv[0] that starts with a 'c' past the
                rightmost '/'.

There is a tuneable #define PTYPE_DEFAULT that allows you to chose
the default CLI variant at compile time.


The "star" interface represents the preferred CLI and implements 
the sum of _all_ features from all possible CLI variants.

If you like to create any new CLI variant, it takes about one hour
to design it as you only need to implement a command line parser
for the CLI variant and set up the "tuneable" variable the right way.

------->

If you like to compare star's behavoir with POSIX or SUSv2, you of course
need to chose the right CLI variant for the test.

As you did like to compare with tar from SUSv2, you need to compare
against the "suntar" CLI. If you did check this CLI you would already
know that this CLI does not implement a -U option.....bummer.


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
opensolaris-discuss@opensolaris.org

Reply via email to