On 03/07/07, Joerg Schilling <[EMAIL PROTECTED]> wrote: > Keith M Wesolowski <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 28, 2007 at 05:25:58PM +0200, Joerg Schilling wrote: > > > > > This is why I did propose to keep the old binary as /usr/bin/otar. > > > > Would star, when invoked as tar or suntar and given this option, > > invoke otar if it detects that it's being asked to read an "old" > > archive format? If so, you might be getting close to something > > acceptable. > > If you do not expect the features of star (e.g. auto compression detection/use > and auto-format detection and use) to work in this case, it could be done > easily. > > BTW: As Suntar -@ is documented while suntar -T is not, it would easier be > possible to implement read support for the suntar -@ archive format.
Actually, -T is documented, unless you are talking about the file format as James Carlson already pointed out: On 27/06/07, James Carlson <[EMAIL PROTECTED]> wrote: > I don't know what Joerg means by "undocumented." The -T option itself > is clearly documented in tar(1): > > T > > This modifier is only available if the system is config- > ured with Trusted Extensions. > > When this modifier is used with the function letter c, > r, or u for creating, replacing or updating a tarfile, > the sensitivity label associated with each archived file > and directory is stored in the tarfile. > > Specifying T implies the function modifier p. > [...] -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
