3

While in the process of migrating some servers from my testing network, a few of them installed systemd; I was a bit surprised as I am using sysV, and have systemd pinned to -1.

What happened?

1 Answer 1

4

It seems my systemd pinning to -1 was not enough. There are a couple more packages belonging to system to APT pin too.

So, I changed my /etc/apt/preferences.d/01nosystemd to:

Package: systemd
Pin: origin ""
Pin-Priority: -1

Package: dh-systemd
Pin: origin ""
Pin-Priority: -1

Package: systemd-shim
Pin: origin ""
Pin-Priority: -1

Package: libpam-systemd
Pin: origin ""
Pin-Priority: -1

And also ran the commands:

sudo apt-mark hold systemd dh-systemd systemd-shim libpam-systemd

Additional note: libsystemd0 is not forgotten, simply it cannot be avoided so easily, due to several dependencies.

Link: linux.org wiki questions - Prevent systemd installation

3
  • 1
    For a similar reason (systemd suddenly installed on top of sysv, trouble when booting) I tried switching to Devuan (for the moment only on one of my machines). Works fine so far.
    – dirkt
    Oct 16, 2016 at 16:57
  • AFAIK Devuan only supports Jessie - I am trying Stretch now; systemd has to be cleaned before booting. Oct 16, 2016 at 17:45
  • 1
    Naming is different on Devuan (for whatever reason): testing = ascii, unstable = ceres. I've only tried stable = Jessie, though. And if course systemd has to be removed to get a clean boot.
    – dirkt
    Oct 16, 2016 at 19:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.