From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5E0A81381F4 for ; Fri, 17 Aug 2012 08:08:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 43A5121C022; Fri, 17 Aug 2012 08:08:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 34CFCE06F4 for ; Fri, 17 Aug 2012 08:07:41 +0000 (UTC) Received: from pomiocik.lan (87-205-57-138.adsl.inetia.pl [87.205.57.138]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 291AD1B4001; Fri, 17 Aug 2012 08:07:38 +0000 (UTC) Date: Fri, 17 Aug 2012 10:08:21 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: Jason@zx2c4.com Subject: Re: [gentoo-dev] OpenRC and SystemD Config File Parity Message-ID: <20120817100821.14d8b256@pomiocik.lan> In-Reply-To: References: Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.11; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/WnlxbMwbbrJTafXpB+.zT2y"; protocol="application/pgp-signature" X-Archives-Salt: c56c1b0b-49ce-496a-b165-31753cf6e38b X-Archives-Hash: 926bc5f067042da8a4380ae59466d153 --Sig_/WnlxbMwbbrJTafXpB+.zT2y Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 17 Aug 2012 03:23:52 +0200 "Jason A. Donenfeld" 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 -- >=20 > 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=3D, 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 units. > - Are there advantages / disadvantages? Which files, for what, and > why? The same as usual. Adv: - 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. Disadv: - 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. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/WnlxbMwbbrJTafXpB+.zT2y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlAt+/kACgkQfXuS5UK5QB1DBgP7B2sGwRCSc2iPXA/rVmL3ANPx VR+eV+0fSp9ihMKtUEpdWpRbI/wvd7++jabOuVJho5k9oAb/5X/3FSaqV5GkGh4H n9/3eELbkieC3UC8e5ex3U/41qBESTTTxNtl7lQ+2SlGq3N5BEFLiu4Y2v6LnTim vYcutBhDC0GjwjfWKr4= =L/nq -----END PGP SIGNATURE----- --Sig_/WnlxbMwbbrJTafXpB+.zT2y--