From: bauen1 <j2468h@googlemail.com>
To: Ashish Mishra <ashishm@mvista.com>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: Failed to start Udev Kernel device manager
Date: Wed, 25 Nov 2020 12:13:25 +0100 [thread overview]
Message-ID: <5f39b0ed-ffdf-68c5-6725-b4c8b5908d71@gmail.com> (raw)
In-Reply-To: <CAP2Ojcipm0dYWcDLX1gpnXpZpuKZv_uDqFHY6Vh5jfLstGepLw@mail.gmail.com>
Hi,
On 11/24/20 9:32 AM, Ashish Mishra wrote:
> I am trying to understand the selinux policy aspect by adding the
> reference policy
> https://github.com/SELinuxProject/selinux
>
> I am trying to get the reference policy as part of proof of concept
> for another project.
> Hence I was using fedora as a base reference for our work .
You could try posting to selinux-refpolicy@vger.kernel.org , this mailing list is mostly for developing the kernel / userspace tools not a specific policy, I can also recommend the IRC channel #selinux on freenode for more interactive help.
--
bauen1
https://dn42.bauen1.xyz/
prev parent reply other threads:[~2020-11-25 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 8:32 Failed to start Udev Kernel device manager Ashish Mishra
2020-11-25 11:13 ` bauen1 [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=5f39b0ed-ffdf-68c5-6725-b4c8b5908d71@gmail.com \
--to=j2468h@googlemail.com \
--cc=ashishm@mvista.com \
--cc=selinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).