All of lore.kernel.org
 help / color / mirror / Atom feed
From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] RFC: direct_init_entry breaks direct_initrc
Date: Wed, 11 Dec 2013 11:31:12 +0100	[thread overview]
Message-ID: <1386757872.18689.96.camel@d30> (raw)
In-Reply-To: <20131211095203.GA6201@siphos.be>

On Wed, 2013-12-11 at 10:52 +0100, Sven Vermeulen wrote:

> > It's a bit harder to verify init related stuff now though because
> > gentoo, debian and fedora each use a different init systems now
> 
> Indeed. I wouldn't mind splitting the init code into their respective
> domains, although that will be a "hell of a job", while there are still
> important shared aspects to it.

Looking at Fedoras' solution i now think that this probably will not be
optimal although i cannot think of any really convincing arguments to
back up my statement, other then that it is probably a bit too late for
that now, and that it is probably not as efficient.

We can make the systemd specific policy conditional, and if we do that
consistent then that should probably be okay

Thanks

  reply	other threads:[~2013-12-11 10:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11  8:33 [refpolicy] RFC: direct_init_entry breaks direct_initrc Sven Vermeulen
2013-12-11  8:56 ` Dominick Grift
2013-12-11  9:52   ` Sven Vermeulen
2013-12-11 10:31     ` Dominick Grift [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-10 15:57 Dominick Grift
2013-12-10 16:00 ` Dominick Grift
2014-01-14 13:56 ` Christopher J. PeBenito
2014-01-14 14:02   ` Dominick Grift
2014-01-14 14:10     ` Christopher J. PeBenito
2014-01-14 14:48       ` Daniel J Walsh
2014-01-14 18:30       ` Dominick Grift
2014-01-14 20:44         ` Christopher J. PeBenito
2014-01-14 22:23           ` Dominick Grift
2014-01-15 13:01             ` Dominick Grift
2014-01-15 13:51             ` Christopher J. PeBenito
2014-01-15 15:44               ` Dominick Grift
2014-01-15 17:01                 ` Daniel J Walsh
2014-01-16 21:12                 ` Christopher J. PeBenito

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=1386757872.18689.96.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.