From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Reusing systemd unit file format / forking systemd (was: Going against co-maintainer's wishes (ref. bug 412697))
Date: Sun, 26 May 2013 05:49:48 -0400 [thread overview]
Message-ID: <CAGfcS_m8zLM9mwkHdvchLZ8uMMrJSza4K1qAiHE691qjyh4eVA@mail.gmail.com> (raw)
In-Reply-To: <CAB9SyzSJDaF22VX1+zfSbAD27jx+7rP9k7HrodRg3gCBufQa_Q@mail.gmail.com>
On Sun, May 26, 2013 at 4:32 AM, Ben de Groot <yngwin@gentoo.org> wrote:
> On 26 May 2013 15:37, Michał Górny <mgorny@gentoo.org> wrote:
>>
>> Considering the design of OpenRC itself, it wouldn't be *that hard*.
>> Actually, a method similar to one used in oldnet would simply work.
>> That is, symlinking init.d files to a common 'systemd-wrapper'
>> executable which would parse the unit files.
>
> I think this idea actually makes sense. Re-using upstream work seems a
> logical idea, and could ease maintenance. Of course the issue is
> whether the OpenRC devs see any benefit in this.
Init.d scripts are just shell scripts. All somebody needs to do is
write a shell script that parses a unit file and does what it says,
and exports an openrc-oriented init.d environment. That can be
packaged separately, or whatever, and maybe an eclass could make it
easy to install (point it at the upstream/filesdir unit and tell it
what to call the init.d script, and you get the appropriate
symlink/script).
The OpenRC devs don't have to endorse anything - sure it would make
sense to bundle it, but it could just as easily be pulled in as a dep
or used manually by a user.
The script could ignore any unit features that aren't implemented.
You can ignore settings like auto-restart/inetd and just use the
settings that get the daemon started.
Rich
next prev parent reply other threads:[~2013-05-26 9:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 16:14 [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697) Ben de Groot
2013-05-25 16:48 ` Michał Górny
2013-05-25 17:38 ` Rich Freeman
2013-05-25 20:02 ` Chí-Thanh Christopher Nguyễn
2013-05-25 20:40 ` Rich Freeman
2013-05-25 20:45 ` Michał Górny
2013-05-25 21:38 ` Luca Barbato
2013-05-26 7:23 ` Ben de Groot
2013-05-26 7:43 ` Michał Górny
2013-05-26 10:04 ` Rich Freeman
2013-05-26 15:21 ` Ben de Groot
2013-05-26 16:15 ` Rick "Zero_Chaos" Farina
2013-05-26 17:14 ` Matt Turner
2013-05-26 17:19 ` Andreas K. Huettel
2013-05-26 7:54 ` Pacho Ramos
2013-05-25 17:00 ` Pacho Ramos
2013-05-25 17:14 ` Carlos Silva
2013-05-26 7:15 ` Ben de Groot
2013-05-26 7:44 ` Pacho Ramos
2013-05-26 7:45 ` Michał Górny
2013-05-26 9:59 ` Luca Barbato
2013-05-25 18:13 ` Markos Chandras
2013-05-25 19:53 ` Anthony G. Basile
2013-05-25 19:58 ` Mike Gilbert
2013-05-25 21:55 ` Anthony G. Basile
2013-05-25 19:59 ` Rich Freeman
2013-05-26 7:00 ` Michał Górny
2013-05-26 7:22 ` Tiziano Müller
2013-05-26 7:46 ` Pacho Ramos
2013-05-26 7:49 ` Michał Górny
2013-05-26 7:00 ` Ben de Groot
2013-05-26 7:37 ` [gentoo-dev] Reusing systemd unit file format / forking systemd (was: Going against co-maintainer's wishes (ref. bug 412697)) Michał Górny
2013-05-26 8:32 ` Ben de Groot
2013-05-26 9:49 ` Rich Freeman [this message]
2013-05-26 10:12 ` Robert David
2013-05-26 10:31 ` Michał Górny
2013-05-26 11:12 ` Rich Freeman
2013-05-26 11:31 ` Robert David
2013-05-26 11:47 ` [gentoo-dev] Reusing systemd unit file format / forking systemd Luca Barbato
2013-05-26 10:23 ` Luca Barbato
2013-05-26 11:15 ` Michał Górny
2013-05-26 11:59 ` Luca Barbato
2013-05-26 13:35 ` Sergei Trofimovich
2013-05-26 14:22 ` Luca Barbato
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=CAGfcS_m8zLM9mwkHdvchLZ8uMMrJSza4K1qAiHE691qjyh4eVA@mail.gmail.com \
--to=rich0@gentoo.org \
--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