1. How to chooseThree different desktop options are available.  Systemd and sysvinit are available for use on each iso.

Kennt wer Leute, die gerne als Linux-Sysadmin in einer coolen Firma in Wien arbeiten wollen? Wir suchen gerade jemanden, haben aber noch nicht offiziell ausgeschrieben, weil wir hoffen, hier schnelle...

This article will teach you what systemd is and why it replaced SysVinit; what systemd unit files are; how to list all and specific unit files; and how to view the content of a unit configuration file.

This article will teach you what systemd is and why it replaced SysVinit; what systemd unit files are; how to list all and specific unit files; and how to view the content of a unit configuration file.

Quote from: Jacob Alexander Tice on 10 October 2026, 20:10:55 > I also recognize how systemd gained traction and it ain't a mystery. Compared to specifically sysvinit, yeah systemd has benefits. When Systemd had it's first official release,...

The new version of the power management tool brings manual turbo control and numerous bug fixes for Linux laptops.

My Debian contributions this month were all sponsored by Freexian. You can also support my work directly via Liberapay or GitHub Sponsors. ## OpenSSH I worked with upstream to remove libselinux linkage from /usr/sbin/sshd. I applied a fix from Mark Robillard Jr to fix reload logic when using sysvinit. ## groff I upgraded from 1.24.1 to 1.24.2, which fixed a few command injection security vulnerabilities. ## parted I upgraded from 3.7 to 3.8, which fixed CVE-2026-89085 and CVE-2026-89088. ## Python packaging New upstream versions: * beaker (contributed supporting fix upstream) * bitstruct * cachelib * dep-logic * django-guardian * django-oauth-toolkit (fixing use of an old Bootstrap version) * django-polymorphic (contributed supporting fix upstream) * djangorestframework (fixing CVE-2026-73228 and CVE-2026-73229) * flask-security * isort * langtable * magic-wormhole-mailbox-server (fixing use of pkg_resources) * multipart * nagiosplugin * poetry-plugin-export * proglog (fixing use of pkg_resources) * prospector (fixing use of pkg_resources) * pybind11-stubgen * pydantic * pydantic-core * pytest-rerunfailures * python-anyio (fixing CVE-2026-63349, CVE-2026-63374, and CVE-2026-64847 and a build failure on Python 3.15) * python-asttokens * python-asyncvarlink * python-blockbuster (fixing a build failure on Python 3.15) * python-btrees * python-django-health-check * python-django-otp * python-django-simple-history * python-email-validator * python-forbiddenfruit * python-ldap * python-linuxnamespaces * python-plaster-pastedeploy * python-pydash * python-pyzipper (fixing CVE-2026-44722) * python-quart-trio * python-rich-click (fixing harlequin) * python-repoze.lru * python-repoze.tm2 (fixing use of pkg_resources) * python-time-machine * python-urllib3 (filed upstream issue with recent Python 3.14 versions) * python-vblf * quart * responses * sphinx-autodoc-typehints * storm (fixing a build failure with Python 3.15, which I helped to land upstream) * trove-classifiers * twine * vdirsyncer setuptools 84 is now in Debian and no longer contains `pkg_resources`. Removing uses of that module has been an ongoing project for a while now, but I did another batch of fixes this month: * flufl.password * junos-eznc * python-decopatch * python-launchpadlib * python-plaster-pastedeploy * python-pyramid-retry * sphinxcontrib-log-cabinet * sphinxcontrib-restbuilder * straight.plugin A new python-coverage version triggered several build regressions due to a known problem in pytest-cov. I worked around these by setting `COVERAGE_CORE=ctrace`: * aiosignal * frozenlist * python-cheroot * python-propcache Other build/test failures: * afew * django-downloadview * django-filter * django-polymorphic * drf-haystack * drf-yasg-nonfree * pydantic-core * pylint * pytest-openfiles * pytest-remotedata * python-aiohttp-oauthlib * python-cron-descriptor * python-django-nh3 * python-graphene * python-pydash * python-pysolr * python-time-machine * python-vblf * social-auth-core * sphinx-book-theme * tagpy: FTBFS against python 3.15rc2 * tagpy: TypeError: ‘include_dirs’ (if supplied) must be a list of strings * typer I investigated a build failure in python-proton-vpn-local-agent and proposed a fix upstream, but I’m not comfortable applying this in Debian without review. If you’re familiar with this code, please take a look. I fixed some other bugs: * python-pycudwt: Requires manual rebuild for python3.14-only transition * python-testing.postgresql: Fails to build source after successful build * tomopy: Requires manual rebuild for python3.14-only transition * typer: Fails to build source after successful build * vdirsyncer: Fails to build source after successful build ## Rust packaging rust-derivre had an invalid Section field, which I cleaned up.

Update: After running it in a systemd session, Epyrus with the bridge now runs in a sysvinit session and can receive and read emails, but won't send an email for me yet. I'll keep working on it and get it figured out to the degree I can and leave some how-to steps here. * * *

> If we have a lot of users who don't want to use systemd, then I might need to start testing that configuration. It's probably a Protonmail specific requirement that the initial setup be done in a systemd session, it's what they require with Proton VPN. But with MX Linux you can easily boot into systemd or sysvinit sessions at boot time, so it's simple to do initial systemd setup and then run the remainder of the time without systemd. Probably nothing for you as a developer to change. I'll test it some more to see if I'm right about this. * * *

> If we have a lot of users who don't want to use systemd, then I might need to start testing that configuration. It's probably a Protonmail specific requirement that the initial setup be done in a systemd session, it's what they require with Proton VPN. But with MX Linux you can easily boot into systemd or sysvinit sessions at boot time, so it's simple to do initial systemd setup and then run the remainder of the time without systemd. Probably nothing for you as a developer to change. I'll test it some more to see if I'm right about this. * * *

Devuan, I switched because I liked rolling release, and Devuan's only real init system is sysvinit, and the other two choices are just sysvinit wrappers, which is kinda lame.