logoalt Hacker News

bbarnettlast Saturday at 7:20 PM5 repliesview on HN

You can still use sysvinit, I've already tested servers and desktop builds.

From my build box:

  chroot $MOUNTPOINT/ /bin/bash -c "http_proxy=$aptproxy apt-get -y --purge --allow remove-essential install sysvinit-core sysvinit-utils systemd-sysv- systemd-"
There is a weird depends you cannot get around without simultaneously removing and installing in parallel. A Debian bug highlighted the above, with a "-" for systemd-sysv- systemd- as a fix, along with allow remove essential.

After this fix, sysvinit builds with debootstrap were almost identical as to bookworm. This includes for desktops.

As per with bookworm through buster, you'll still need something like this too:

  $ cat /etc/apt/preferences.d/systemd

  # this is the only systemd package that is required, so we up its priority first...
  Package: libsystemd0
  Pin: release trixie
  Pin-Priority: 700

  # exclude the rest
  Package: systemd
  Pin: release *
  Pin-Priority: -1

  Package: *systemd*
  Pin: release *
  Pin-Priority: -1

  Package: systemd:i386
  Pin: release *
  Pin-Priority: -1

  Package: systemd:amd64
  Pin: release *
  Pin-Priority: -1

Replies

JdeBPlast Monday at 7:59 AM

I can credit you, in version 1.42, with more than a hyperlink to random posts on Hacker News if you have something better elsewhere on the WWW. (-:

* https://jdebp.uk/Softwares/nosh/guide/services/systemd-login...

egorfinelast Saturday at 8:41 PM

Wait, sysvinit on debian 13 truly practically works?? as in, one can remove systemd and have a working server OS with sysv init??

show 2 replies
RVuRnvbM2elast Saturday at 10:21 PM

Why would you want to do this?

show 2 replies
forestolast Saturday at 10:15 PM

Thank you for sharing this. I'm inclined to adopt it in my lxc containers, at least.

dur-randirlast Sunday at 6:19 AM

I've been living with sysvinit up until Debian 11. Then it became unusable with lxc containers :(, so I had to bite the bullet. But for the basic system it indeed works.