From: James Antill <jantill@redhat.com>
To: Stephen John Smoogen <smooge@gmail.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: gnuTAR support for SELinux context (beta)
Date: Tue, 01 Aug 2006 15:19:14 -0400 [thread overview]
Message-ID: <1154459954.2103.82.camel@code.and.org> (raw)
In-Reply-To: <80d7e4090608011150u48b0e124m1046145a1450b8a3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Tue, 2006-08-01 at 12:50 -0600, Stephen John Smoogen wrote:
> Doesn't the xattr support use an internally different tar format than
> the normal one? [From my reading of the star pages.] Would this stop
> it being readable from say Debian, Solaris etc that didn't know about
> this format
No, star requires you set the archive format to exustar ... my patches
for GNUtar only require the --xattr/--selinux option(s) and to not be
using v7 format.
Note that GNUtar can read exustar format archives, with xattr info. in
them, although I'm guessing all the details in the documentation is
still valid wrt. length limits ... and:
tar -cvf foo.tar foo --xattr --format=ustar
...does produce archives that can be extracted from star (including
xattr info.).
Saying that, debian/upstream/etc. GNUtar does issue warnings and a
delayed error exit code when it sees the xattr info. in an archive (but
it works just as though none of that info. were present). Which _could_
break scripts that expect a happy exit code, and might well confuse
users with the warnings.
--
James Antill <jantill@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-01 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 17:27 gnuTAR support for SELinux context (beta) James Antill
2006-08-01 17:40 ` Stephen John Smoogen
2006-08-01 18:28 ` Stephen Smalley
2006-08-01 18:50 ` Stephen John Smoogen
2006-08-01 19:19 ` James Antill [this message]
2006-08-01 19:02 ` James Antill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154459954.2103.82.camel@code.and.org \
--to=jantill@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=smooge@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.