Wow, seems like systemd is a quite a mess.
After an initial look at the codebase, it seems like since its a forever running process, everything was crammed into it from Laptop battery backlight brightness to absurd stuff like certificate validation?
Maybe I'm missing something but something odd about having so much unrelated functionality crammed into a single tool.
Need to look at breaking it into smaller tools that adhere to the Unix tools philosophy.
@bobdobberson yeah, definitely a whole bunch of sub-commands, that could be refactored as individual tools at the very least.
What's it supposed to do anyway? At the minimum simply be the one process from which every other process is forked, then fork a shell so the user can start using the system.
At most, service management, and then you can have each service do its thing like manage laptop brightness, ntp time sync etc. instead of building it all into systemd
mahadevank
Pope Bob the Unsane