From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: [PATCH] User Manual: Warn readers about mmap and SELinux issue.
Date: Wed, 4 Nov 2009 04:11:19 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911040409060.19894@localhost> (raw)
On some Linux distros, if you set the kernel /proc file
/proc/sys/vm/mmap_min_addr to zero, you will probably get an SELinux
violation if you're running SELinux in enforcing mode. Explain to the
reader how to get around that.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/docs/usermanual/chapters/getting_oe.xml b/docs/usermanual/chapters/getting_oe.xml
index e8d1f2c..1e0112b 100644
--- a/docs/usermanual/chapters/getting_oe.xml
+++ b/docs/usermanual/chapters/getting_oe.xml
@@ -257,7 +257,13 @@ MACHINE = "om-gta01"</screen>
If your system does not provide
the <filename>/etc/sysctl.conf</filename> mechanism, you can try adding
the above <command>echo</command> command line to
- your <filename>/etc/rc.local</filename>.
+ your <filename>/etc/rc.local</filename>. But that's not all.
+
+ On some systems (such as Fedora 11), changing that kernel setting
+ will cause an SELinux violation if you're running SELinux in enforcing
+ mode. If that's the case, you can either disable SELinux or run:
+
+ <screen># setsebool -P allow_unconfirmed_mmap_low 1</screen>
</para>
</note>
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-11-04 9:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.00.0911040409060.19894@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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