On 28/09/2015 10:11, Brian wrote:
On Sun 27 Sep 2015 at 22:56:38 +0100, Joe wrote:On Sun, 27 Sep 2015 21:00:09 +0200 Markus Grunwald <markus@the-grue.de> wrote:Hello, after the update from wheezy to jessie, there is no systemd running on my machine. I had the impression, that systemd is installed automatically...? % dpkg -l \*systemd\* | egrep \^ii ii libsystemd0:amd64 215-17+deb8u2 amd64 systemd utility library % ps ax | grep system 3441 ? Ss 0:00 /usr/bin/dbus-daemon --system 16669 pts/1 S+ 0:00 grep --color=auto system % ps ax | head -n 2 PID TTY STAT TIME COMMAND 1 ? Ss 0:02 init [2] % dpkg -S /sbin/init sysvinit-core: /sbin/init I have to add that the machine is a vserver where I have influence on the kernel % cat /proc/cmdline root=/dev/xvda1 ip=95.129.55.223:127.0.255.255:95.129.55.193:255.255.255.192:vsrv28769.customer.xenway.de:eth0:offI believe there was a deliberate decision not to include systemd in an upgrade, only in new installations.Actually, the decision was the opposite of this. A dist-upgrade will install systemd-sysv unless steps are taken to prevent it happening. https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#systemd https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
Thanks, I haven't yet upgraded a wheezy to jessie.I had been under the impression, from previous systemd discussions, that an upgrade of stable would not by default switch to a systemd init. Clearly this is not the case, and it will.
I'm not at all keen on doing that, I still favour a clean systemd-based installation for my server, with the associated configuration work. An upgraded stable will never be quite identical with a clean installation with the same requested packages, and I'm not planning on asking for more trouble than is absolutely necessary.
-- Joe