Posted Oct 25, 2012 5:49 UTC (Thu) by davidstrauss (subscriber, #85867)
Parent article: GNOME and/or systemd
tl;dr: Using systemd for much of GNOME only creates a hard dependency on Linux, not using systemd as the base system's init daemon.
It's a bit misleading to say that making systemd a dependency for user sessions inherently requires using it for boot or the base system. It should be possible to boot with Upstart, SysV init, or any system of your choice and still run "systemd --user" to manage the user session. I doubt this will ever be a first-class option, but we shouldn't prematurely rule it out.
Of course, if a utility running in the user session interacts with the core OS to *manage* user sessions and expects to find systemd there, running systemd in the user session alone won't be enough. That makes the power plugin different from other parts of GNOME that could use a user session instance of systemd for, say, launching applications and session services like PulseAudio.
Posted Oct 25, 2012 6:24 UTC (Thu) by davidstrauss (subscriber, #85867)
[Link]
That's interesting, given that systemd runs find in an austere container with no access to the base system. Maybe the user session mode requires interacting with the base systemd session management API. Regardless, I stand corrected.
GNOME and/or systemd
Posted Oct 25, 2012 9:45 UTC (Thu) by zuki (subscriber, #41808)
[Link]
> Now, Thomas' patch actually changes much less than people might
> think. This is because sd_booted() simply checks whether
> /sys/fs/cgroup/systemd is mounted. But to run --user on a foreign system
> you need to set that tree up anyway, as that is a requirement for
> systemd either way.