Re: Bug#727708: Fsck SystemD and its developers and its users. GR to override this please.
On Tue, 2014-02-11 at 10:08 +0100, Olav Vitters wrote:
> On Tue, Feb 11, 2014 at 06:49:56AM +0100, Svante Signell wrote:
> > Additionally a very good proposal for a PID 1 program was in
> > http://ewontfix.com/14/ "Broken by design: systemd", copied here for
> > convenience:
>
> I like how people copy/paste blog articles. Did you read this article?
Of course I've read it.
> It completely lacks detail and where it does, it is conflicting with
> itself.
>
> E.g. "Reboot to Upgrade", while a bit later: "systemd's systemctl has a
> daemon-reexec command to make systemd serialize its state, re-exec
> itself". Meaning: reboot to upgrade is not needed, answer is given in
> the same text. The objections to daemon-reexec are vague.
I'll do some more reading on daemon-rexec before saying more.
But: Don't you se the the current development is heading towards a
Windows locked-in situation, and a reboot is necessary for every
upgrade?
kdbus, udev, gnome, network-manager, pulseaudio, wayland, (add to the
list here)
Reply to: