From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [patch 1/1] stuff to make refpolicy boot on fedora 13.
Date: Fri, 01 Oct 2010 14:00:57 -0400 [thread overview]
Message-ID: <4CA621D9.8000500@tresys.com> (raw)
In-Reply-To: <4CA5F99B.3090308@city-fan.org>
On 10/01/10 11:09, Paul Howarth wrote:
> On 01/10/10 15:52, Christopher J. PeBenito wrote:
>> On 10/01/10 10:30, Dominick Grift wrote:
>>> After some consideration i think you should probably ignore this whole patch or cherry pick only some fixes that you are positive about. Some of the stuff in the patch i have already changed like how interaction with keys is done.
>>> Also this patch was based on fedora 13, in fedora 14 some things have changed so on f14 this isnt enough to make it work.
>>>
>>> for example in f14 /usr/sbin/init is a symbolic link to /usr/sbin/upstart which is currently labeled bin_t so kernel_t never transitions to init_t (need to label /usr/sbin/upstart type initrc_t)
>>
>> Really? How can init not be in /sbin?
>
> systemd (the replacement init that will be in Fedora 15) lives in /bin
> as it call be a user session manager too.
My point was that it wouldn't be available if /usr was on a different
partition than /. But the /usr part was a typo from Dominick, so its a
moot point.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2010-10-01 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 19:37 [refpolicy] [patch 1/1] stuff to make refpolicy boot on fedora 13 Dominick Grift
2010-10-01 13:58 ` Christopher J. PeBenito
2010-10-01 14:30 ` Dominick Grift
2010-10-01 14:52 ` Christopher J. PeBenito
2010-10-01 15:09 ` Paul Howarth
2010-10-01 18:00 ` Christopher J. PeBenito [this message]
2010-10-01 15:10 ` Dominick Grift
2010-10-01 15:28 ` Daniel J Walsh
2010-10-01 19:01 ` Christopher J. PeBenito
2010-10-01 19:06 ` Dominick Grift
2010-10-04 9:18 ` Dominick Grift
2010-10-01 15:42 ` Daniel J Walsh
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=4CA621D9.8000500@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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.