From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/17] SELinux Buildroot Additions
Date: Sat, 7 Sep 2013 12:44:31 +0200 [thread overview]
Message-ID: <20130907124431.25571c66@skate> (raw)
In-Reply-To: <OF299770B9.9F574639-ON86257BDE.00636F06-86257BDE.006395D0@rockwellcollins.com>
Dear Ryan Barnett,
On Fri, 6 Sep 2013 13:07:44 -0500, Ryan Barnett wrote:
> Clayton and I have been going back and forth on how best to do this, as
> the next set of patch that we want to release provides information on
> SELinux.
> You had provided feedback to Clayton on options for providing this
> information
> and I think it was agreed upon that the manual will be the best place for
> this.
> Is this correct?
This is correct.
> > In order to ease the review process, would it be possible to get a
> > short introduction to SELinux, and especially what tools are needed on
> > the host, what tools are needed on the target? I'm especially
> > interested in understanding why/if we need all this Python stuff on the
> > target.
>
> I believe the best way to answer to questions above about is add to the
> manual.
> As this way that we won't have to necessarily duplicate work (and
> motivates us
> to create the documentation). So hopefully by the middle of the week next
> week
> we can submit some documentation.
That would be good. However, I am not sure the questions I am asking
here match exactly what should be in the documentation. In the
documentation, we should explain how a Buildroot user can enable
SELinux support and make use of it on the target. While my questions
certainly overlap some of this, I believe we also need a few more
details of the internals to roughly understand what the different
packages are doing.
> Where would you like this documentation placed? Also how does one go about
> adding
> to the manual (I can't seem to find anything in the manual)? Or do we want
> to place
> this information on the buildroot wiki?
I believe the manual is a better place than the Buildroot Wiki. For
now, we've usually stored this kind of additional informations in the
"Details on Buildroot configuration" section. So something like:
diff --git a/docs/manual/configure.txt b/docs/manual/configure.txt
index 56b0469..0fc66c9 100644
--- a/docs/manual/configure.txt
+++ b/docs/manual/configure.txt
@@ -430,3 +430,8 @@ can be chosen from +System configuration+, +Init system+:
The solution recommended by Buildroot developers is to use the
*Busybox init* as it is sufficient for most embedded
systems. *systemd* can be used for more complex situations.
+
+SELinux support
+~~~~~~~~~~~~~~~
+
+Here put some details about the SELinux support.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-09-07 10:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 23:09 [Buildroot] [PATCH 00/17] SELinux Buildroot Additions Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 01/17] libsepol: new package Clayton Shotwell
2013-09-05 7:44 ` Thomas Petazzoni
2013-09-05 12:58 ` clshotwe at rockwellcollins.com
2013-09-05 13:19 ` Thomas Petazzoni
2013-09-05 16:46 ` Arnout Vandecappelle
2013-09-06 6:28 ` Thomas Petazzoni
2013-09-09 17:36 ` Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 02/17] libselinux: " Clayton Shotwell
2013-09-05 7:51 ` Thomas Petazzoni
2013-09-05 13:18 ` clshotwe at rockwellcollins.com
2013-09-04 23:09 ` [Buildroot] [PATCH 03/17] ustr: " Clayton Shotwell
2013-09-05 7:57 ` Thomas Petazzoni
2013-09-04 23:09 ` [Buildroot] [PATCH 04/17] libsemanage: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 05/17] checkpolicy: " Clayton Shotwell
2013-09-06 17:56 ` Thomas Petazzoni
2013-09-09 17:33 ` Clayton Shotwell
2013-09-11 16:44 ` Arnout Vandecappelle
2013-09-12 7:17 ` Thomas Petazzoni
2013-09-04 23:09 ` [Buildroot] [PATCH 06/17] sepolgen: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 07/17] setools: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 08/17] libcgroup: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 09/17] policycoreutils: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 10/17] python-pyxml: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 11/17] refpolicy: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 12/17] python-pyparsing: Add host build option Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 13/17] audit: new package Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 14/17] shadow: " Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 15/17] pcre: Add host build support Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 16/17] bzip2: Add host build shared library installation Clayton Shotwell
2013-09-04 23:09 ` [Buildroot] [PATCH 17/17] sqlite: Add host build support Clayton Shotwell
2013-09-06 17:49 ` [Buildroot] [PATCH 00/17] SELinux Buildroot Additions Thomas Petazzoni
2013-09-06 18:07 ` Ryan Barnett
2013-09-07 10:44 ` Thomas Petazzoni [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=20130907124431.25571c66@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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