mgorny at gentoo
Aug 17, 2012, 1:08 AM
Post #4 of 4
On Fri, 17 Aug 2012 03:23:52 +0200
Re: OpenRC and SystemD Config File Parity
[In reply to]
"Jason A. Donenfeld" <Jason [at] zx2c4> wrote:
> 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.
> - What is the current state of differences between config file formats
> and locations used for OpenRC/Baselayout and SystemD?
Some of the configs are systemd-specific and were adjusted in Gentoo.
For example, machine-id was moved from /var/lib/dbus to /etc.
With a few other configs, systemd supports both OpenRC and its own
format. When used with --with-distro=, it finds and reads Gentoo
configs; you can also replace them with native systemd files.
And finally, there are configs which are both used by systemd
and OpenRC, like binfmt.d, tmpfiles.d, modules-load.d. The former two
we adopted to avoid reinventing the wheel, not sure about the last one.
It's all on the wiki: http://wiki.gentoo.org/wiki/Systemd#Configuration
> - Is parity desirable? Are some people working on this?
Some people are thinking about this. Unit files are especially
desirable since that's what upstreams are often shipping. There's no
point in keeping init.d files in sync when we can use upstream-managed
> - Are there advantages / disadvantages? Which files, for what, and
The same as usual.
- users don't have to remember a few locations when working with
different distros or learn when switching,
- tools can be designed for a single location,
- upstream can provide some files for us.
- a bit more work on our side,
- a few people will complain about systemd dominating their systems,
- a few people will end up with broken systems through removing
everything looking suspiciously systemd-matic.