On Sun, 26 May 2013 15:15:26 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> Cc: TomWij@gentoo.org

Please don't CC me, this causes duplicate mails; one of both does not
include reply-to. Nobody else that has responded to me did this before.

Unless you can give me an awesome procmail rule to process these... :)

> I don't know what is the state of your system when testing this but on
> my system /sbin/telinit is a symlink to /sbin/init. So replacing
> the latter also replaces telinit with something unexpected.

I did something like `mv /sbin/init{,.bak} ; mv systemd /sbin/init`

> Of course, the solution is to make telinit point to the real sysvinit
> executable. Not sure how well it will reboot then, however. It may be
> necessary to also change 'halt' to use 'telinit' if it uses 'init'
> directly.

Currently I use `systemctl reboot` and `systemctl poweroff`, I
actually have no idea how to make telinit work again with systemd.

> >  # /etc/init.d/ntpd start
> > ntpd             | * WARNING: ntpd is already starting
> >  # /etc/init.d/ntpd stop
> > ntpd             | * ERROR: ntpd stopped by something else
> 
> I think we fixed this already... well, not exactly this because openrc
> used to try to actually start stuff. I would consider this a
> regression since it had explanatory error messages.

The stop error is reasonable I think, the start error is indeed odd.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D