All of lore.kernel.org
 help / color / mirror / Atom feed
From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 3/5] init: in redhat derived distributions the kernel (systemd) dynamically transitions to init
Date: Sat, 07 Dec 2013 20:31:15 +0100	[thread overview]
Message-ID: <1386444675.18689.8.camel@d30> (raw)
In-Reply-To: <20131207191952.GA19217@d30>

On Sat, 2013-12-07 at 20:19 +0100, Dominick Grift wrote:
> I used the kernel_dyntrans_to() to stay consistent with the
> kernel_domtrans_to. I am not sure why this was done this way
> 
> init: systemd wants to block suspend in distro_redhat
> 
> Signed-off-by: Dominick Grift <dominick.grift@gmail.com>

Whoops these patches were sent from the wrong email address.
git-send-email or dependency is broken in fedora so i resorted to mutt
which was configured with this email address

Anyhow:

This might be a first step to supporting systemd.

Basically run the main component in init_t, and add the systemd specific
policy in a boolean init_systemd

These changes also only apply to rh derived distros (at least for now)

debian is not using systemd currently but is using some systemd
components

however these components are started by dbus system bus, and not by
systemd like they are in fedora for example

So that needs special attention

The main message of this patch i guess is that i suggest we take
advantage of Fedoras experience with systemd and follow suit as much as
possible

Earlier on i was hoping we could do more but now i am of the opinion
that this is probably best

      reply	other threads:[~2013-12-07 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 19:19 [refpolicy] [PATCH 3/5] init: in redhat derived distributions the kernel (systemd) dynamically transitions to init Dominick Grift
2013-12-07 19:31 ` Dominick Grift [this message]

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=1386444675.18689.8.camel@d30 \
    --to=dominick.grift@gmail.com \
    --cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.