Originally posted by k1e0x
View Post
A lot of people keep suggesting "just read the man pages" and I have to wonder if those motherfuckers have ever actually typed "man systemd" in their life. If one wants to know setting kernel command line entries and some other things, it's fine, but its not like it has a comprehensive list of every systmed command. For that you have to go to the bottom of the man page and follow the man page rabbit hole. The man page rabbit hole sucks and we all know that one may or may not have good luck doing that. Basically, if one uses a random systemd system, there is no quick and simple way to see what systemd tools are installed outside of just trying what you can remember.
But that last problem, wasn't pointing out KDE nor system install locations...was highlighting that non-systemd programs use ctl so the dumb search method is only good to an extent. Random crap ending in ctl under /usr/local still may or may not be systemd related since the user might install a systemd component not used by default or might install something that ends in ctl.
If you can't search the package manager, if the man pages aren't sufficient, and since isn't a common naming scheme, you're up shit creek unless you're a goddamn Rainman.
Comment