The "removing systemd" experiment
Round 2: Install the Magic Package and Then Remove systemd
To restore a working system right after installation, I'll introduce the no-systemd.deb
package (Listing 2). Now this looks a lot better! Only systemd and a few other packages are removed – not the entire desktop system – because an empty package (no-systemd
contains no files) is installed first, which fakes a systemd installation as the dependency for other packages (Listing 3).
Listing 2
Setting Up no-systemd
Listing 3
Building the no-systemd.deb Magic Package
libpam-systemd
is clearly a dependency for systemd; rfkill
has a hard-coded dependency on a package named systemd, which is probably a mistake and unnecessary. Rebuilding the package without this dependency should help.
After removing systemd and libpam-systemd followed by a reboot, I still can't get past the point where the graphical subsystem should start up, because the root filesystem stays mounted read-only; therefore, Xorg can't open its logfile at /var/log/Xorg.0.log
. Changing the root filesystem's mount mode to rw
instead of ro
in the bootloader's config is a quick workaround for now. A better fix would be to change the bootup procedure to remount/read-write at some point. Apparently, this is missing in my sysvinit.deb
package.
Now I have a working desktop – kind of. After using it awhile, you will realize that some things are dysfunctional, like configuring the network with the graphical NetworkManager GUI.
Round 3: Install SysVinit over systemd and Do a Lot of Post-Configuration
The reason the previous round failed to produce a fully working system is that some desktop components require the session management introduced by systemd-logind
, which is located inside the systemd package. After installing the SysVinit packages (which replace /sbin/init
by SysVinit's version plus the necessary basic startup scripts), I also need to install the systemd-shim package to start session management and other services automatically around systemd clients. Also, the policykit-1 package needs to be installed, and permissions for services like NetworkManager should be set to yes
instead of no
or auth_admin*
, if the session can't be detected properly, as shown in the excerpt in Listing 4 from /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
.
Listing 4
Setting Permissions
Also, newer versions of systemd require the cgroup mount point; otherwise, systemd-shim
won't be able to start systemd-logind
, so login sessions won't be reported to services that request information about the logged-in user. This would be a minimal subset of mounts that systemd-logind
expects. I put the following commands in my own startup scripts:
mkdir -p -m 0777 /cgroup/cpu mount -t cgroup cgroup -o cpu /cgroup/cpu mkdir -m 1777 /cgroup/cpu/user
It Works!
After round 3, the system looks very much like a Knoppix installation, in which the startup system is run through SysVinit, with other systemd components still present to make programs happy that are hard-coded with systemd dependencies (e.g., on systemd-logind
and the libsystemd0
library). Still, LXSession pops up a confusing hard-coded message (Figure 1) that is produced if systemd is not listening on D-Bus. The best way I found to circumvent this problem is to remove the erroneous error message from the lxsession source and recompile the package.
Also, the rfkill
tool has a confusing dependency on a package named (!) "systemd" instead of just the systemd provision in my no-systemd package. Downgrading rfkill
or recompiling without the hard-coded dependency fixes this issue.
« Previous 1 2 3 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Direct Download
Read full article as PDF:
Price $2.95
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Find SysAdmin Jobs
News
-
KDE Plasma 5.27 Beta is Ready for Testing
The latest beta iteration of the KDE Plasma desktop is now available and includes some important additions and fixes.
-
Netrunner OS 23 Is Now Available
The latest version of this Linux distribution is now based on Debian Bullseye and is ready for installation and finally hits the KDE 5.20 branch of the desktop.
-
New Linux Distribution Built for Gamers
With a Gnome desktop that offers different layouts and a custom kernel, PikaOS is a great option for gamers of all types.
-
System76 Beefs Up Popular Pangolin Laptop
The darling of open-source-powered laptops and desktops will soon drop a new AMD Ryzen 7-powered version of their popular Pangolin laptop.
-
Nobara Project Is a Modified Version of Fedora with User-Friendly Fixes
If you're looking for a version of Fedora that includes third-party and proprietary packages, look no further than the Nobara Project.
-
Gnome 44 Now Has a Release Date
Gnome 44 will be officially released on March 22, 2023.
-
Nitrux 2.6 Available with Kernel 6.1 and a Major Change
The developers of Nitrux have officially released version 2.6 of their Linux distribution with plenty of new features to excite users.
-
Vanilla OS Initial Release Is Now Available
A stock GNOME experience with on-demand immutability finally sees its first production release.
-
Critical Linux Vulnerability Found to Impact SMB Servers
A Linux vulnerability with a CVSS score of 10 has been found to affect SMB servers and can lead to remote code execution.
-
Linux Mint 21.1 Now Available with Plenty of Look and Feel Changes
Vera has arrived and although it is still using kernel 5.15, there are plenty of improvements sure to please everyone.