Debian TC vote on init system coupling

http://www.freedesktop.org/software/systemd/man/systemd-l...

> systemd-logind is a system service that manages user logins. It is responsible for:

> 1. Keeping track of users and sessions, their processes and their idle state

> 2. Providing PolicyKit-based access for users to operations such as system shutdown or sleep

> 3. Implementing a shutdown/sleep inhibition logic for applications

> 4. Handling of power/sleep hardware keys

> 5. Multi-seat management

> 6. Session switch management

> 7. Device access management for users

> 8. Automatic spawning of text logins (gettys) on virtual console activation and user runtime directory management

It seems quite easy to make basically a "no-op" DBus interface to fake logind. #1 is only minimally necessary, although I can't say how much is actually needed and the complexity. #2 is simple enough to invoke a SUID binary for the underlying scripts, although security leaves something to be desired. #3 is completely optional. #4 could be handled through Gnome by configuring custom keyboard shortcut commands (sprinkle in SUID as necessary). #5 and #6 can be ignored. #7 should be simple. Since there's no multi-seat, it's easy to run a udev script for changing owner/group of the devices and sending a DBus signal to Gnome of the hotplug event. #8 can be ignored in favor of fixed gettys. Runtime directories should be kept and could likely be managed by a Gnome startup script (or if necessary something inserted earlier in the login sequence).

There's no doubt that it will be messy and half-baked (especially as I've described it), but I think it could mostly work. Whether anyone would want to run or enjoying running it is another matter.