public inbox for initramfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <colin-odJJhXpcy38dnm+yROfE0A@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Colin Guthrie <colin-odJJhXpcy38dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] systemd: add more groups to deal with tmpfiles handling.
Date: Tue,  7 Jun 2016 10:40:08 +0100	[thread overview]
Message-ID: <20160607094008.21012-1-colin@mageia.org> (raw)

Both 'utmp' and 'root' groups are mentioned in tmpfiles.d/systemd.conf
and as such should be included.

It's probably better to have something equiv to inst_rule_group_owner()
for udev rules which parses out users and groups and adds them to the
passwd/group db respectively.

Could also rely on sysusers but as the initramfs is static in this
sense, it's more efficient to pre-define the users IMO.
---
 modules.d/00systemd/module-setup.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/modules.d/00systemd/module-setup.sh b/modules.d/00systemd/module-setup.sh
index 951a5be..abe44d8 100755
--- a/modules.d/00systemd/module-setup.sh
+++ b/modules.d/00systemd/module-setup.sh
@@ -184,6 +184,8 @@ install() {
     grep '^systemd-journal:' /etc/group >> "$initdir/etc/group"
     grep '^wheel:' /etc/group >> "$initdir/etc/group"
     grep '^adm:' /etc/group >> "$initdir/etc/group"
+    grep '^utmp:' /etc/group >> "$initdir/etc/group"
+    grep '^root:' /etc/group >> "$initdir/etc/group"
 
     ln_r $systemdutildir/systemd "/init"
     ln_r $systemdutildir/systemd "/sbin/init"
-- 
2.8.3

             reply	other threads:[~2016-06-07  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  9:40 Colin Guthrie [this message]
     [not found] ` <20160607094008.21012-1-colin-odJJhXpcy38dnm+yROfE0A@public.gmane.org>
2016-06-07 10:04   ` [PATCH] systemd: add more groups to deal with tmpfiles handling Dracut GitHub Import Bot

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=20160607094008.21012-1-colin@mageia.org \
    --to=colin-odjjhxpcy38dnm+yrofe0a@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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