"If anyone can shed light on what some of the more mysterious parameters do please let me know!"
You can steal copy examples from here
Overview of functionality
"Keeping track of users and sessions, their processes and their idle state" and "shutdown/sleep inhibition logic for applications" is missing from the big pictures, which could link as table of contents.
It would be probably easier to just copy-paste these images and remove/add an appendix section for libinput and udev, since logind does only do the file-descriptor handling.
"This could probably be done by using the posix sessionids in most cases. But those are not reliable since processes can leave their session and make a new one. Now we don't know anymore what is going on!"
Examples for cases would help here
Writing udev functionality as a list ( defining set of hardware as Seat, ... ) would certainly help readability.
"If anyone can shed light on what some of the more mysterious parameters do please let me know!"
You can
stealcopy examples from hereOverview of functionality
"Keeping track of users and sessions, their processes and their idle state" and "shutdown/sleep inhibition logic for applications" is missing from the big pictures, which could link as table of contents.
It would be probably easier to just copy-paste these images and remove/add an appendix section for
libinputandudev, sinceloginddoes only do the file-descriptor handling."This could probably be done by using the posix sessionids in most cases. But those are not reliable since processes can leave their session and make a new one. Now we don't know anymore what is going on!"
Examples for cases would help here
Writing udev functionality as a list ( defining set of hardware as
Seat, ... ) would certainly help readability.