From: Bradley Chapman <kakadu@gmail.com>
To: russell@coker.com.au
Cc: selinux@tycho.nsa.gov
Subject: Re: An SELinux policy for Red Hat 9
Date: Fri, 9 Jul 2004 12:43:38 +0100 [thread overview]
Message-ID: <e294b46e0407090443663d55c4@mail.gmail.com> (raw)
In-Reply-To: <200407092111.55045.russell@coker.com.au>
Mr. Coker,
On Fri, 9 Jul 2004 21:11:55 +1000, Russell Coker <russell@coker.com.au> wrote:
>
>
> On Fri, 9 Jul 2004 06:17, Bradley Chapman <kakadu@gmail.com> wrote:
> > Does anyone know of a good place where I can start reading about how
> > to adapt, or obtain, an SELinux policy for Red Hat 9, running the
> > 2.6.7 kernel with the SELinux userspace package dated 20040628-16?
>
> Why would you want to do that? Consider Fedora Core 1 as RHL 10, and FC2 as
> RHL 11 an just upgrade a couple of versions to get SE Linux support.
I would do that - except for the fact that the system I want to run
SELinux on is my personal system, and upgrading it is currently not
something I wish to do. I may want to upgrade to FC2 later, but right
now I want to stick with RHL9.
>
> But if you REALLY want to use RHL 9, the current policy should work OK, you
> just have to make the appropriate changes to pam, logrotate, cron, coreutils,
> etc.
What sort of changes? Path changes?
Thanks,
Brad
--
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:[~2004-07-09 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 20:17 An SELinux policy for Red Hat 9 Bradley Chapman
2004-07-09 11:11 ` Russell Coker
2004-07-09 11:43 ` Bradley Chapman [this message]
2004-07-09 12:14 ` Stephen Smalley
2004-07-09 14:52 ` Bradley Chapman
2004-07-09 16:22 ` Stephen Smalley
2004-07-09 17:30 ` Valdis.Kletnieks
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=e294b46e0407090443663d55c4@mail.gmail.com \
--to=kakadu@gmail.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.