Sorry, it"s just a piece from the Internet, but it explains why I messed with Turnstile, and I just like dinit. I did it for myself as best I could, and I share it with others. This is relevant for those who use KDE and Wayland.

" What's the point of running the graphical stack and session via Turnstile in Chimera Linux?

In the context of Chimera Linux, using Turnstile is a deliberate architectural choice. It provides all the power of systemd for managing user and graphical services while remaining completely independent from systemd itself and its philosophy.

Simply put, Turnstile solves three key problems that are critical for modern graphical environments:

     Automatic user service management: It automatically starts your personal instance of Dinit (or runit) right after you log in, and crucially, shuts it down properly when you log out.

     Proper application runtime environment: It creates and manages the XDG_RUNTIME_DIR (typically /run/user/1000), which is required for PipeWire, Wayland, and many other modern applications to function.

    Graphical session management: It provides targets like graphical.target, allowing you to start all your desktop environment services with a single command and manage them as a unified whole.

🖥️ How does this work in practice with the graphical stack?

The process is seamless but logical and elegant:

    Login: You enter your password in a display manager (e.g., SDDM). The PAM module pam_turnstile notifies the turnstiled daemon that a session is starting.

    Environment setup: Turnstile creates the /run/user/$(id -u) directory, sets environment variables (XDG_RUNTIME_DIR, DBUS_SESSION_BUS_ADDRESS), and launches your user instance of Dinit.

    Service startup: Your dinit --user receives a command to start the graphical.target. This target includes launching pipewire, wireplumber, dbus-daemon, and finally your Wayland compositor (e.g., labwc, sway).

    Work and logout: You use your system. When you log out, Turnstile signals your user Dinit to stop, which gracefully terminates all child processes and cleans up the /run/user directory.

🤔 Why use this instead of just elogind?

That's a fair question. Unlike elogind (which is essentially a stripped-out piece of systemd), Turnstile was designed from the ground up to be service manager agnostic.

    elogind only knows about systemd. It doesn't know how to directly manage Dinit or OpenRC.

    Turnstile is specifically built not to care what init system you're using. It simply executes a backend — a small script — which in turn launches your dinit --user or runsvdir.

Thanks to this architectural decision, Chimera Linux can have:

    System-wide Dinit for global services.

    User Dinit for your personal services, launched via Turnstile.

    seatd or elogind for device access.

All these different systems work together without interfering with each other, making Chimera Linux one of the most cohesive and thoughtfully designed distributions outside the systemd ecosystem."

No. I"m a regular user. I watched how Turnstile worked in Chimera Linux and tried to do the same in Devuan. To do this, I had to make my own Dinit-dbus file and modify the dinit backend script in Turnstile. This is an experiment. Through elogind, everything works perfectly. I also had to fix the work of dinit in cgroups. I hope my settings will interest someone and the developers will take care of the support of dinit in Devuan.

>>Why is turnstile related to which init system is in use?

Turnstile works with other init systems, but I fixed it work with dinit in this particular system. It will not work fully with the standard settings for the dinit backend - they are for Chimera Linux.

Or "simply" fixing its dinit backend?

I guess I don't understand why you would need to experiment with init systems while fixing the dinit backend for turnstile.

And turnstile in itself should be agnostic about init system.  It merely is a service that implements that concept of "User Services" where a user may set up "services" (programs) to start and restart when and while the user is logged in, and terminate when they log out.

Of course the ABI in detail has that start/restart as a 2-step matter with a "started" notification from the service control scripting separate from progress monitoring, and that's what the backend provides. The backend flavours, to me, only concerns which support utilities for process management would be expected.

But I may well have misunderstood it all. Why is turnstile related to which init system is in use?

  Turnstile - still in development...It's difficult with it.

Fixed Polkit, PackageKit