Switching Init Systems on Artix Linux With the artix-init-set Helper

Artix Linux lets you change your system's PID 1 init—runit, s6, OpenRC, or dinit—without reinstalling. The catch? The helper that automates the swap, artix-init-set, streamlines the technical steps, but the new init brings service-bundle implications you need to handle. This post walks through the mechanism of switching and how to verify the result.

How the Modular Init Mechanism Works

Artix ships the meta-package artix-base, which contains init scripts for the four supported init systems and a helper utility that creates the required /sbin/init symlink. The design keeps the base system small because only the selected init's runtime dependencies are pulled in, while the unused init systems remain available as installable packages.

Switching init systems does not require reinstalling Artix; the same pacman-managed packages and kernel continue to work, preserving user data and configuration. However, changing the init system may break services that rely on init-specific scripts. Users must enable the corresponding service bundles for the new init.

Example: Switching to Runit

If you are currently using OpenRC and want to try runit for its speed and simplicity, follow these steps to transition. This assumes you have root privileges for all commands, run on the Artix machine itself.

1. Install the desired init system package:

   sudo pacman -S runit

2. Run the helper to swap the init binary symlink:

   sudo artix-init-set runit

3. Reboot the system to start the new PID 1:

   sudo reboot

Before step 2, confirm the helper exists in your release with pacman -Ql artix-base | grep init; the exact utility name can vary between releases. If it is missing, the fallback is a manual /sbin/init symlink, which risks an unbootable system if the target path is wrong—double-check the target is a valid binary before rebooting.

Verification Diagnostics

After reboot, you must verify that the system booted into the chosen init. Use the following commands to confirm the transition was successful and stable:

Confirm the symlink points to the correct binary:

ls -l /sbin/init

Check the process running PID 1:

ps -p 1 -o comm=

Ensure the service manager is active (for runit, check status):

sv status /var/service/*

Limitations and Trade-offs

The primary limitation is that service management is non-portable. If you move from OpenRC to runit, your services defined in /etc/init.d will not start. You must manually move service links to /var/service and use the runit-specific configuration.

Additionally, if the helper utility artix-init-set is missing in a specific release, manual symlink creation of /sbin/init is required. This demands careful handling to avoid an unbootable system; always ensure the target path is a valid binary before reboot.

Before switching, list the services you currently run under your existing init and plan how each maps to the new one—that checklist, plus the PID 1 verification above, is what turns a risky swap into a routine one. Artix's modular approach allows for flexibility, but it requires the user to be aware of which service-management syntax they are using.