From: Daniel J Walsh <dwalsh@redhat.com>
To: russell@coker.com.au
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: restorecon and chroot
Date: Mon, 19 Jul 2010 09:55:20 -0400 [thread overview]
Message-ID: <4C445948.5000106@redhat.com> (raw)
In-Reply-To: <201007171514.16224.russell@coker.com.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/17/2010 01:14 AM, Russell Coker wrote:
> On Thu, 15 Jul 2010, Daniel J Walsh <dwalsh@redhat.com> wrote:
>> Why not just use setfiles, since you will need to specify the
>> file_context path anyways?
>
> setfiles requires that you specify the full path of the file_contexts file,
> this means that documentation that refers to it has to be distribution
> specific to a certain extent and it's annoying to use.
>
> Now if setfiles could default to using the same file_contexts file that
> restorecon uses then that objection would go away. Do you think we should
> change setfiles in such a manner?
>
Ok, so you want restorecon to use an alternate root dir. I
misunderstood. The reason I originally wrote restorecon was I got sick
of specifying the path.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkxEWUgACgkQrlYvE4MpobN69gCgxJpwK5FMgbc58v5pcVOjL91E
0zcAnAroL61TitjY3WvBCHotKdE5Oq6a
=Qi/5
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2010-07-19 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 4:27 restorecon and chroot Russell Coker
2010-07-15 13:43 ` Daniel J Walsh
2010-07-17 5:14 ` Russell Coker
2010-07-19 13:55 ` Daniel J Walsh [this message]
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=4C445948.5000106@redhat.com \
--to=dwalsh@redhat.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.