[oe] [PATCH] User Manual: Warn readers about mmap and SELinux issue.
Robert P. J. Day
rpjday at crashcourse.ca
Wed Nov 4 09:11:19 UTC 2009
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 at 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
========================================================================
More information about the Openembedded-devel
mailing list