If systemd was only managing services there would be less opposition. People opposed don’t want a single thing doing services and boot and user login and network management and…
IDK, ask them. There are some in this thread. I’m addressing the strawman argument that people against it are luddites set in their ways over their beloved cron jobs.
yeah I just hate the move away from flat text files honestly. Its one thing I did not like about windows NT with the registry. databasing up the config.
“I hate systemd, it’s bloated and overengineered” people stay, perched precariously on their huge tower of shell scripts and cron jobs.
If systemd was only managing services there would be less opposition. People opposed don’t want a single thing doing services and boot and user login and network management and…
Are they also opposed to coreutils being a single project with dozens of executables doing different things?
IDK, ask them. There are some in this thread. I’m addressing the strawman argument that people against it are luddites set in their ways over their beloved cron jobs.
And built poorly by people who don’t work well with others and then payola’ed onto the world.
Fucking UNIX is shell scripts and cron jobs, skippy. Add xinetd and you’re done.
yeah I just hate the move away from flat text files honestly. Its one thing I did not like about windows NT with the registry. databasing up the config.
Which part of systemd’s config is not text-based? The only “database” it uses for configuration is the filesystem
That’s bloat. I start all my services manually according to my needs. Why start cupsd BEFORE I need to print anything?
thats what systemd sockets are here for
or inetd!