From: Yi Zhao <yi.zhao@windriver.com>
To: yocto@lists.yoctoproject.org, joe_macdonald@mentor.com, joe@deserted.net
Subject: [meta-selinux][PATCH 1/4] SELinux-FAQ: remove references to poky-selinux distro
Date: Wed, 2 Nov 2022 15:30:49 +0800 [thread overview]
Message-ID: <20221102073052.1567876-1-yi.zhao@windriver.com> (raw)
Update SELinux-FAQ as the poky-selinux distro has been removed for a
long time.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
SELinux-FAQ | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/SELinux-FAQ b/SELinux-FAQ
index 8f56b2b..2ae6649 100644
--- a/SELinux-FAQ
+++ b/SELinux-FAQ
@@ -47,7 +47,6 @@ controls could be added to an operating system.
To enable SELinux features, this layers has done these works:
* new DISTRO_FEATURES "selinux" defined
- * new DISTRO "poky-selinux" defined, with DISTRO_FEATURES += "pam selinux"
* config file for Linux kernel to enable SELinux
* recipes for SELinux userland libraries and tools
* package group (packagegroup-core-selinux) for SELinux userland packages
@@ -67,7 +66,7 @@ After init Poky build environment, please follow these steps:
1. Add meta-selinux path to BUILDDIR/conf/bblayers.conf file.
- 2. Set DISTRO="poky-selinux" or add DISTRO_FEATURES:append=" pam selinux"
+ 2. Add DISTRO_FEATURES:append=" acl xattr pam selinux"
in BUILDDIR/conf/local.conf file.
3. Build the default selinux image.
@@ -94,7 +93,6 @@ the following steps:
$ bitbake core-image-custom
-
==============================================================================
3 - Using SELinux
@@ -109,7 +107,7 @@ Alternatively, you can add "selinux=0" to your kernel boot parameters. It is
not recommended but useful on some testing situations.
For example, when you are using qemu targets,
- $ runqemu qemumips core-image-selinux ext3 nographic bootparams="selinux=0"
+ $ runqemu qemumips core-image-selinux nographic bootparams="selinux=0"
The initial filesystem relabel step requires considerable memory and can result
in unexpected, sometimes impossible to reproduce, failures if an OOM condition
--
2.25.1
next reply other threads:[~2022-11-02 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 7:30 Yi Zhao [this message]
2022-11-02 7:30 ` [meta-selinux][PATCH 2/4] base-files: set correct label for /var/volatile Yi Zhao
2022-11-02 7:30 ` [meta-selinux][PATCH 3/4] libsepol: fix build failure for refpolicy-mls Yi Zhao
2022-11-02 7:30 ` [meta-selinux][PATCH 4/4] refpolicy: upgrade 20210908+git -> 20221101+git Yi Zhao
[not found] ` <20221107193343.jrkm4tdey75dwev6@siemens.com>
2022-11-08 2:29 ` Yi Zhao
[not found] ` <17257B1B9EFC9AB1.28792@lists.yoctoproject.org>
2022-11-09 3:47 ` [yocto] " Yi Zhao
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=20221102073052.1567876-1-yi.zhao@windriver.com \
--to=yi.zhao@windriver.com \
--cc=joe@deserted.net \
--cc=joe_macdonald@mentor.com \
--cc=yocto@lists.yoctoproject.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