From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Geoff Parker <geoffrey.parker@arthrex.com>
Subject: [nanbield][PATCH 4/7] ref-manual: variables: adding multiple groups in GROUPADD_PARAM
Date: Thu, 14 Mar 2024 10:15:05 +0100 [thread overview]
Message-ID: <20240314091508.84166-5-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240314091508.84166-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Geoff Parker <geoffrey.parker@arthrex.com>
Add missing documentation on how to add multiple groups with a single
GROUPADD_PARAM:${PN}
Signed-off-by: Geoff Parker <geoffrey.parker@arthrex.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 448bea9938..ec879f9f86 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -3234,6 +3234,14 @@ system and gives an overview of their function and contents.
GROUPADD_PARAM:${PN} = "-r netdev"
+ More than one group can be added by separating each set of different
+ groups' parameters with a semicolon.
+
+ Here is an example adding multiple groups from the ``useradd-example.bb``
+ file in the ``meta-skeleton`` layer::
+
+ GROUPADD_PARAM:${PN} = "-g 880 group1; -g 890 group2"
+
For information on the standard Linux shell command
``groupadd``, see https://linux.die.net/man/8/groupadd.
--
2.34.1
next prev parent reply other threads:[~2024-03-14 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:15 [nanbield][PATCH 0/7] documentation backports michael.opdenacker
2024-03-14 9:15 ` [nanbield][PATCH 1/7] ref-manual: tasks: do_cleanall: recommend using '-f' instead michael.opdenacker
2024-03-14 9:15 ` [nanbield][PATCH 2/7] ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a shared sstate michael.opdenacker
2024-03-14 9:15 ` [nanbield][PATCH 3/7] ref-manual: variables: correct sdk installation default path michael.opdenacker
2024-03-14 9:15 ` michael.opdenacker [this message]
2024-03-14 9:15 ` [nanbield][PATCH 5/7] dev-manual: packages: fix capitalization michael.opdenacker
2024-03-14 9:15 ` [nanbield][PATCH 6/7] contributor-guide: add notes for tests michael.opdenacker
2024-03-14 9:15 ` [nanbield][PATCH 7/7] manuals: document VIRTUAL-RUNTIME variables michael.opdenacker
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=20240314091508.84166-5-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=geoffrey.parker@arthrex.com \
/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