Talk:How to remove systemd from a Debian jessie/sid installation
This method doesn't work OOtB for an Amazon EC2 instance, instead, this small script (which does the same thing) can be called through the
apt-get -y install sysvinit-core sysvinit sysvinit-utils apt-get remove --purge --auto-remove systemd cat >/etc/apt/preferences.d/systemd<<EOF Package: systemd Pin: origin "" Pin-Priority: -1 Package: *systemd* Pin: origin "" Pin-Priority: -1 EOF
Instructions for OpenVZ containers
Debian Wheezy OpenVZ images in SolusVM come with upstart for init by default so it is only possible to upgrade them to Jessie with upstart.
It is still possible to have Jessie running sysvinit in OpenVZ if you are willing to:
- blacklist upstart & systemd in apt preferences
- dist-upgrade Squeeze ---> Wheezy (reboot)
- dist-upgrade again Wheezy --> Jessie.
I tried this on an Acer Revo; result - failure to boot. I've had success previously on (a) a Xen DOM0 and (b) several Xen DOMUs.
The solution was to use GRUB_CMDLINE_LINUX_DEFAULT=""
1. The 'init=' stanza is unneeded; init defaults to /sbin/init, which (after installing the sysv packages) was identical to /lib/sysvinit/init.
2. TtyS0 exists (according to dmesg); but I don't want to use a serial console - I have a keyboard and monitor connected to the machine, I don't want to juggle funny old-fashioned serial cables and soldering irons.
3. hvc0 is the Xen hypervisor console, and this machine is not running Xen. I suspect this caused the boot failure.