#desktopbus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #desktopbus, aggregated by home.social.
-
The opposite is fun, too: when there's a system #DesktopBus broker running but it's not a systemd system, and logging in through a chain of intertwined mechanisms tries to auto-start #systemd.
-
hostnamectl gets its information across the #DesktopBus from hostnamed. And hostnamed in turn gets its information from reading the os-release file(s).
So when that someone has deleted your /etc/os-release (and /usr/lib/os-release and /run/os-release), you'll find that hostnamectl will not be able to give you the information. Because the information isn't there any more.
-
[…Continued]
The parallels to #utmps now show up, because that's also effectively a hook into login (except through libc rather than PAM) that talks to a server via IPC to maintain a login database, just one that doesn't couple to a whole shedload of extra stuff, or use #DesktopBus.
Whilst utmps is alright, I still think that kernels should just provide access to the session tables that they already maintain.
Moreover:
-
pam_systemd -> dbus-daemon -> systemd-logind -> dbus-daemon -> systemd
One could add more loops through dbus-daemon to make starting a dæmon at login even loopier, I suppose. (-:
It's interesting that @ska 's utmps would be a less circuitous way of achieving this. Because this is really just keying things off of insertions/deletions to an active logins table. One that has extra Desktop Bus compared to the original.
Lots of extra Desktop Bus.