All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: selinux@tycho.nsa.gov, refpolicy@oss1.tresys.com
Subject: Re: load_policy() with upstart on mint 9 fluxbox
Date: Wed, 20 Oct 2010 15:01:18 -0700	[thread overview]
Message-ID: <4CBF66AE.5040805@gmail.com> (raw)
In-Reply-To: <20101020015409.GA19663@hallyn.com>

o.k. finally connected the dots that I needed to create a initrd.img
in order for this to load(im a total newbie!!)

Anyways the policy loads everything went in and am now in full
enforcement mode.. only real issue is with lxde
same bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=552885

seems lxde is in /usr/sbin reason probably for the wrong filelabel..

Justin P. Mattock

--
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.

WARNING: multiple messages have this Message-ID (diff)
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] load_policy() with upstart on mint 9 fluxbox
Date: Wed, 20 Oct 2010 15:01:18 -0700	[thread overview]
Message-ID: <4CBF66AE.5040805@gmail.com> (raw)
In-Reply-To: <20101020015409.GA19663@hallyn.com>

o.k. finally connected the dots that I needed to create a initrd.img
in order for this to load(im a total newbie!!)

Anyways the policy loads everything went in and am now in full
enforcement mode.. only real issue is with lxde
same bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=552885

seems lxde is in /usr/sbin reason probably for the wrong filelabel..

Justin P. Mattock

  parent reply	other threads:[~2010-10-20 22:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 22:55 load_policy() with upstart on mint 9 fluxbox Justin P. Mattock
2010-10-19 22:55 ` [refpolicy] " Justin P. Mattock
2010-10-20  1:54 ` Serge E. Hallyn
2010-10-20  1:52   ` Justin P. Mattock
2010-10-20  1:52     ` [refpolicy] " Justin P. Mattock
2010-10-20  4:51   ` Justin P. Mattock
2010-10-20  4:51     ` [refpolicy] " Justin P. Mattock
2010-10-20 13:28   ` Justin P. Mattock
2010-10-20 13:28     ` [refpolicy] " Justin P. Mattock
2010-10-20 22:01   ` Justin P. Mattock [this message]
2010-10-20 22:01     ` Justin P. Mattock
2010-10-21  2:44     ` Serge E. Hallyn
2010-10-21  5:15       ` Justin P. Mattock
2010-10-21  5:15         ` [refpolicy] " Justin P. Mattock
2010-10-21  6:26         ` Shaz
2010-10-21  6:26           ` [refpolicy] " Shaz
2010-10-21  6:48           ` Justin P. Mattock
2010-10-21  6:48             ` [refpolicy] " Justin P. Mattock
2010-10-21  7:08             ` Shaz
2010-10-21  7:08               ` [refpolicy] " Shaz
2010-10-21 13:40               ` Justin P. Mattock
2010-10-21 13:40                 ` [refpolicy] " Justin P. Mattock
2010-10-21 14:36                 ` Shaz
2010-10-21 14:36                   ` [refpolicy] " Shaz
2010-10-21 14:54                   ` Justin P. Mattock
2010-10-21 14:54                     ` [refpolicy] " Justin P. Mattock
2010-10-24 23:39                   ` Russell Coker
2010-10-25 10:10                     ` Shaz
2010-10-25 12:16                       ` Russell Coker
2010-10-25 12:42                         ` Shaz

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=4CBF66AE.5040805@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=refpolicy@oss1.tresys.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=serge@hallyn.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.