On Sun, 27 Sep 2015 21:00:09 +0200 Markus Grunwald <mar...@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:off > > I believe there was a deliberate decision not to include systemd in an upgrade, only in new installations. I tried an upgrade to systemd in unstable, after which it really was unstable, and I eventually reinstalled. When the time comes to upgrade my server, I'm currently inclined towards a reinstallation rather than upgrade in place. I've no doubt that an upgrade to systemd in a wheezy system already upgraded to jessie would be less of a problem than I had with unstable, but you really don't want avoidable trouble in a server. -- Joe
