Re: Bug#684396: ITP: openrc -- alternative boot mechanism that manages the services, startup and shutdown of a host
- To: email@example.com
- Subject: Re: Bug#684396: ITP: openrc -- alternative boot mechanism that manages the services, startup and shutdown of a host
- From: Matthias Klumpp <firstname.lastname@example.org>
- Date: Sun, 2 Sep 2012 14:43:45 +0200
- Message-id: <CAKNHny8z_gAwTqPZF_DA7FkhoSYY1yeWpoVh62SRjwzx-wP0aA@mail.gmail.com>
- In-reply-to: <1346578639.12827.2.camel@tomoe>
- References: <20120809130307.7498.64495.reportbug@localhost> <20120809135405.GA18318@bongo.bofh.it> <email@example.com> <1344552643.4958.7.camel@tomoyo> <20120810072322.GC10872@anguilla.debian.or.at> <1344585409.4874.20.camel@tomoe> <CAOVenEp82g82SZH2hZ2gZK43jBCu7=-Tm28OQj3aEk8req5iQA@mail.gmail.com> <1346399420.3479.446.camel@pi0307572> <F37B32A1-C915-4F40-9908-CB2858D3CFDD@physik.fu-berlin.de> <CAOVenEpJT63OYbPRtzZcDyk7XkZhi=1VN8sd0tnqd7gv9Pf0Kg@mail.gmail.com> <20120831200609.GA16744@physik.fu-berlin.de> <50418EF1.firstname.lastname@example.org> <1346578639.12827.2.camel@tomoe>
Just for the record (and I might be wrong with this information,
because I don't have it from a "official" Gentoo source):
I heard from a Gentoo dev that they will switch from OpenRC to
systemd, and find the possibility very funny that Gentoo switches to
systemd from OpenRC and Debian switches to OpenRC from init. :-)
So, it looks like Gentoo devs see value in systemd so they're consider
dropping OpenRC for systemd.
About the general issue: I think whoever wants to work on stuff should
be able to work on it, so having OpenRC packages is not really a bad
thing. So, if someone wants to do it, just do it :-)
For making OpenRC default I have an other opinion: I consider systemd
superior and I think making OpenRC default is just the wrong way. And
I very well think we can fully support systemd and kfreebsd. I already
build my packages with systemd(-logind) support in experimental and
use ConsoleKit for non-Linux ports, which works exttremely well.
With the new init-script-from-systemd generator, using sysvinit on
non-Linux systems should also be possible, although the non-Linux
porters might need to write some additional initscripts for more
complicated daemons, but this should be possible to do. (It's an
effort, sure, but it's worth it and a good compromise)
So, I don't really see any problem anymore with systemd support. And I
also have to agree with many points Josselin made (although I usually
disagree with him quite often) - Choice in core infrastructure is not
worth the effort just to have a choice. (This argument doesn't count
for desktop components, of course) - Instead, we at Debian should
provide a technically excellent OS, not a thing with many
Just my 2ct.
2012/9/2 Josselin Mouette <email@example.com>:
> Le samedi 01 septembre 2012 à 12:28 +0800, Thomas Goirand a écrit :
>> It goes from a more manageable code (for some parts, the same
>> feature as in systemd, but with a code that is 5 times smaller),
> Code size is a compelling argument only with the same set of features.
> Which is not the case.
>> to the fact that it may work with something else than Linux,
>> or the fact that it supports also mdev.
> Supporting mdev is not a feature. Please tell us about what features you
> intend to bring with that.
> Josselin Mouette /\./\
> « Sans puissance, la maîtrise n'est rien. »
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> Archive: http://lists.debian.org/1346578639.12827.2.camel@tomoe