From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] OpenRC and SystemD Config File Parity
Date: Fri, 17 Aug 2012 03:23:52 +0200 [thread overview]
Message-ID: <CAHmME9rQqAW2kCV25MhBTVq-0v1B4dxaX3gVhoV7fbkJf89hEQ@mail.gmail.com> (raw)
Hey everyone,
This isn't a topic meant for bike shedding, but just kind of loose
exploratory inquiry. I saw a bug report about adding systemd's
tmpfiles.d config format support to OpenRC (accomplished) and then
some discussion about adding an ebuild utility function (dotmpfiles_d)
or digging up something from systemd.eclass for this. This whole
discussion got me thinking --
To what degree is there parity of configuration formats between OpenRC
and SystemD? Obviously there will never be any sort of parity ever for
Unit files, but what about for the general parameters of the system?
machine-id, locale, timezone, hostname, et cetera.
I suppose when I refer to OpenRC, I'm really talking about Baselayout.
I guess more specifically what I'm wondering is:
- What is the current state of differences between config file formats
and locations used for OpenRC/Baselayout and SystemD?
- Is parity desirable? Are some people working on this?
- Are there advantages / disadvantages? Which files, for what, and why?
Anyway, if folks have opinions or thoughts, I'd love to hear them. But
this is just loose inquiry, not a pressing question for a project in
motion, so don't feel compelled to exsanguinate your soul here.
Jason
next reply other threads:[~2012-08-17 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 1:23 Jason A. Donenfeld [this message]
2012-08-17 5:33 ` [gentoo-dev] OpenRC and SystemD Config File Parity heroxbd
2012-08-17 5:47 ` Jason A. Donenfeld
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=CAHmME9rQqAW2kCV25MhBTVq-0v1B4dxaX3gVhoV7fbkJf89hEQ@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