Tbf, disabling systemD autorun is the only thing I’ve ever user kwriteconfig6 for, because with it enabled bash scripts don’t run correctly.

Only thing I’ve had to edit in the terminal in the last several months has been automount on a hard drive.

I just use gnome disks for that. Tbh, that’s the only thing I use gnome disks for.

I don’t mind using the terminal, but how the fuck am I going to remember something like kwriteconfig6 --file startkderc --group General --key systemdBoot false? (In fact, there aren’t even man pages for that command). Like the scribbles of a mad man I’ve had to put down commands like that in a sort of personal instructions manual, because ain’t no way I’ll remember these commands by heart.
And you often end up just saving the most used commands as aliases or functions in the .bashrc meaning you don’t retain the syntax for the commands you use. Well, maybe I’m a unique case of fish memory… The thing about humans is that we greatly rely on our vision, and having GUI’s to show what’s possible greatly improve ones understanding of how to manage it going forward.

It is nice to have guard rails like a GUI until you grasp the possibilities, that’s how I’ve learned historically coming from DOS and Windows at least, but you can still mess things up plenty with this tool.

I switched to linux a little over a year ago and went with MX Linux because they have great GUI tools for windows refugees like myself, and because they don’t like systemd over there they use cron jobs. Now, having switched to Nobara I’ve just installed both SystemD Pilot here, but also found KCron, a KDE Cron configuration module which allows for the same functionality as what I’m used to.
If I just want to setup a “when system starts” daemon, is there really any difference in using one over the other? I guess it’s possible to shut down services more gracefully?

In any case, great job on this utility.