Re: systemd bug closed - next steps?
On Tue 23 Sep 2014 at 21:09:30 +0200, Erwan David wrote:
> Le 23/09/2014 20:46, Brian a écrit :
> > You do not like that systemd will be the default init system for Jessie.
> > Tough. Exercise your choice not to have it. Or is easier to moan rather
> > than just get on with using sysvinit?
> >
> > As for your link, you could at least have quoted a primary source, the
> > mail from Joey Hess making the announcement. That way people could judge
> > for themselves rather than relying on your inconsequential remarks.
>
> That's just not the behaviour of _something meant to be a "default" with
> options.
> First, we see that other packages become dependant on it, making the
> "option" thing somewhat irrelevant.
>
> Next, other choices are done because of "integration" with systemd.
>
> Why ? why integration with a mere default choice among other choices
> woud be relevant ?
> Except if the agenda is *not* what was sold and agreed upon which was a
> mere *default*.
>
> Sorry, but this kind of things just make suspicious.
>
> What will next step be ?
Months ago I'd have written a mail advising you to install sysvinit-core
and systemd-shim and given details. Now I am getting weary. Do and say
what you want. It not will alter the fact that systemd will be the
default init system on Jessie.
Reply to: