| 1 |
On Fri, 17 Aug 2012 03:23:52 +0200 |
| 2 |
"Jason A. Donenfeld" <Jason@×××××.com> wrote: |
| 3 |
|
| 4 |
> This isn't a topic meant for bike shedding, but just kind of loose |
| 5 |
> exploratory inquiry. I saw a bug report about adding systemd's |
| 6 |
> tmpfiles.d config format support to OpenRC (accomplished) and then |
| 7 |
> some discussion about adding an ebuild utility function (dotmpfiles_d) |
| 8 |
> or digging up something from systemd.eclass for this. This whole |
| 9 |
> discussion got me thinking -- |
| 10 |
> |
| 11 |
> To what degree is there parity of configuration formats between OpenRC |
| 12 |
> and SystemD? Obviously there will never be any sort of parity ever for |
| 13 |
> Unit files, but what about for the general parameters of the system? |
| 14 |
> machine-id, locale, timezone, hostname, et cetera. |
| 15 |
|
| 16 |
> - What is the current state of differences between config file formats |
| 17 |
> and locations used for OpenRC/Baselayout and SystemD? |
| 18 |
|
| 19 |
Some of the configs are systemd-specific and were adjusted in Gentoo. |
| 20 |
For example, machine-id was moved from /var/lib/dbus to /etc. |
| 21 |
|
| 22 |
With a few other configs, systemd supports both OpenRC and its own |
| 23 |
format. When used with --with-distro=, it finds and reads Gentoo |
| 24 |
configs; you can also replace them with native systemd files. |
| 25 |
|
| 26 |
And finally, there are configs which are both used by systemd |
| 27 |
and OpenRC, like binfmt.d, tmpfiles.d, modules-load.d. The former two |
| 28 |
we adopted to avoid reinventing the wheel, not sure about the last one. |
| 29 |
|
| 30 |
It's all on the wiki: http://wiki.gentoo.org/wiki/Systemd#Configuration |
| 31 |
|
| 32 |
> - Is parity desirable? Are some people working on this? |
| 33 |
|
| 34 |
Some people are thinking about this. Unit files are especially |
| 35 |
desirable since that's what upstreams are often shipping. There's no |
| 36 |
point in keeping init.d files in sync when we can use upstream-managed |
| 37 |
units. |
| 38 |
|
| 39 |
> - Are there advantages / disadvantages? Which files, for what, and |
| 40 |
> why? |
| 41 |
|
| 42 |
The same as usual. |
| 43 |
|
| 44 |
Adv: |
| 45 |
- users don't have to remember a few locations when working with |
| 46 |
different distros or learn when switching, |
| 47 |
- tools can be designed for a single location, |
| 48 |
- upstream can provide some files for us. |
| 49 |
|
| 50 |
Disadv: |
| 51 |
- a bit more work on our side, |
| 52 |
- a few people will complain about systemd dominating their systems, |
| 53 |
- a few people will end up with broken systems through removing |
| 54 |
everything looking suspiciously systemd-matic. |
| 55 |
|
| 56 |
-- |
| 57 |
Best regards, |
| 58 |
Michał Górny |
Archives