From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OpenRC and SystemD Config File Parity
Date: Fri, 17 Aug 2012 07:47:47 +0200 [thread overview]
Message-ID: <CAHmME9pyTh-RNicqfo+NDMW3EsE2+hGgJzUgnWT0WzMsmUxC=w@mail.gmail.com> (raw)
In-Reply-To: <86628iccb9.fsf@gentoo.org>
On Fri, Aug 17, 2012 at 7:33 AM, <heroxbd@gentoo.org> wrote:
> config file formats differs a lot, for OpenRC it's shell script, while
> for SystemD Microsoft ini/XDG Desktop Entry Specification.
Sorry, just to clarify and reiterate what I said before -- I am
excluding Unit files from this discussion, for obvious reasons. Unit
files are the ini files you commented there. My inquiries are directed
toward the other more global system configuration files that systemd
and openrc use. Again, the discussion is not about Unit files, ini, or
shell scripts vs systemd units; this is considered off-topic.
next prev parent reply other threads:[~2012-08-17 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 1:23 [gentoo-dev] OpenRC and SystemD Config File Parity Jason A. Donenfeld
2012-08-17 5:33 ` heroxbd
2012-08-17 5:47 ` Jason A. Donenfeld [this message]
2012-08-17 8:08 ` Michał Górny
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='CAHmME9pyTh-RNicqfo+NDMW3EsE2+hGgJzUgnWT0WzMsmUxC=w@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=gentoo-dev@lists.gentoo.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