From: Ron Kuris <rk@unify.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: file context ordering
Date: Fri, 29 Jul 2005 11:53:36 -0700 [thread overview]
Message-ID: <42EA7B30.8090207@unify.com> (raw)
In-Reply-To: <1122660123.20983.58.camel@sgc>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christopher J. PeBenito wrote:
| On Thu, 2005-07-28 at 13:58 -0700, Ron Kuris wrote:
|
|> Use M4 diversions ... [snip]
|
|
| Well this is definitely an interesting solution. The problem is
| that it doesn't apply to the loadable policy modules, since the
| file contexts in a module don't have m4. Preserving m4 into the
| modules, and having semodule run m4 to reconstruct file_contexts is
| probably a bad idea. Adding a weight to specs, which is what Steve
| suggested, would be more general than leveraging m4.
|
I guess I don't know enough about the loadable module plans.
So that means the loadable modules cannot use any of the m4 macros either?
Ron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC6nswVkC/44kdyuYRAuoyAKDGKVk6aOCtUZg5hOKY6NrEQ3U2YgCfQnUx
ugMfR4Bw5R7AHr1cUwm/4wM=
=Tqmz
-----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.
next prev parent reply other threads:[~2005-07-29 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 19:16 file context ordering Christopher J. PeBenito
2005-07-28 20:58 ` Ron Kuris
2005-07-29 18:02 ` Christopher J. PeBenito
2005-07-29 18:53 ` Ron Kuris [this message]
2005-07-29 19:26 ` Christopher J. PeBenito
2005-07-29 10:26 ` Daniel J Walsh
2005-07-29 19:30 ` Christopher J. PeBenito
2005-07-29 12:44 ` Stephen Smalley
2005-07-29 20:09 ` Christopher J. PeBenito
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=42EA7B30.8090207@unify.com \
--to=rk@unify.com \
--cc=cpebenito@tresys.com \
--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.